CA Workload Automation

SE

Message Reference Guide

r11.3

Third Edition
This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as
the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This
Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA.
If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make
available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with
that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2015 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■ CA Workload Automation SE, formerly CA 7® Workload Automation
■ CA 1® Tape Management (CA 1)
■ CA ACF2™
■ CA JCLCheck™ Workload Automation (CA JCLCheck)
■ CA Librarian®
■ CA Netman™
■ CA NSM Job Management Option (CA NSM JMO)
■ CA Panvalet® for z/OS (CA Panvalet)
■ CA Top Secret®
■ CA Service Desk
■ CA Workload Automation Restart Option for z/OS Schedulers (CA WA Restart
Option), formerly CA 11™ Workload Automation Restart and Tracking
Contact CA Technologies
Contact CA Support

For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■ Online and telephone contact information for technical assistance and customer
services
■ Information about user communities and forums
■ Product and documentation downloads
■ CA Support policies and guidelines
■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our

short customer survey which is available on the CA Support website at
http://ca.com/docs.
Documentation Changes
We added the following new messages since the last release of this documentation:
■ CAL2E117E
■ CAL2E118E
■ CAL2E119I
■ CAL2E120E
■ CAL2E121E
■ CAL2E122E
■ CAL2E123E
■ CAL2E125I
■ CAL2E126I
■ CAL2E127I
■ CAL2E128I
■ CAL2E129I
■ CAL2E130I
■ CAL2E132E
■ CAL2E133I
■ CAL2E134E
■ CAL2E135E
■ CAL2E136I
■ CAL2E137I
■ CAL2E138I
■ CAL2E139E
■ CAL2E140E
■ CAL2E141E
■ CAL2E142I
■ CAL2E144I
■ CAL2E145I
■ CAL2E146E
■ CAL2E147I
■ CAL2E148I
■ CAL2E149I
■ CAL2E150I
■ CAL2E151E
■ CAL2E201E
■ CAL2E202E
■ CAL2E203E
■ CAL2E205E
■ CAL2E206E
■ CAL2E207E
■ CAL2E210I
■ CAL2E241E
■ CAL2E242E
■ CAL2E243E
■ CAL2E247E
■ CAL2E248E
■ CAL2E249E
■ CAL2E251I
■ CAL2E252I
■ CAL2E253E
■ CAL2E254E
■ CAL2E255E
■ CAL2E256E
■ CAL2E257E
■ CAL2E258E
■ CAL2E259E
■ CAL2E260E
■ CAL2E261I
■ CAL2E262E
■ CAL2E263I
■ CAL2M750I
■ CAL2M760I
■ CAL2M770I
■ CAL2M950E
■ CAL2M951E
■ CAL2M952W
Contents
Chapter 1: Introduction 13

Chapter 2: AFM - CA7R Messages 15

AFM Messages ........................................................................................................................................................... 15
AR Messages .............................................................................................................................................................. 17
BCLP Messages ........................................................................................................................................................... 25
BK0x Messages ........................................................................................................................................................... 45
BSTR Messages ........................................................................................................................................................... 54
BTSO Messages .......................................................................................................................................................... 61
CACR Messages .......................................................................................................................................................... 64
CAL2 Messages ........................................................................................................................................................... 83
CAXPS Messages....................................................................................................................................................... 595
CA7M Messages ....................................................................................................................................................... 597
CA7R Messages ........................................................................................................................................................ 605

Chapter 3: CA-7.A - CA-7.X Messages 607

CA-7.AIIS Through CA-7.DT70 Messages .................................................................................................................. 607
CA-7.D32V Through CA-7.VDB0 Messages ............................................................................................................... 639
CA-7.VTAM Through CA-7.V001 Messages .............................................................................................................. 785
Format for VSAM Database Messages ..................................................................................................................... 788
CA-7.V002 Through CA-7.V020 Messages ................................................................................................................ 790
CA-7.V101 Through CA-7.V199 Messages ................................................................................................................ 795
CA-7.V200 Through CA-7.V299 Messages ................................................................................................................ 819
CA-7.V300 Through CA-7.V329 Messages ................................................................................................................ 842
CA-7.V501 Through CA-7.V599 Messages ................................................................................................................ 850
CA-7.V601 Through CA-7.V636 Messages ................................................................................................................ 855
CA-7.V701 Through CA-7.V722 Messages ................................................................................................................ 866
CA-7.V801 Through CA-7.V815 Messages ................................................................................................................ 874
CA-7.V901 Through CA-7.V918 Messages ................................................................................................................ 879
CA-7.W Messages ..................................................................................................................................................... 885
CA-7.X Messages ...................................................................................................................................................... 885

Chapter 4: CA-7.000 - CA-7.1044 911

CA-7.000 Through CA-7.094 ..................................................................................................................................... 911
CA-7.100 Through CA-7.153 Messages .................................................................................................................... 931

Contents 9
CA-7.200 Through CA-7.260 ..................................................................................................................................... 938
CA-7.3XXX Through CA-7.378 ................................................................................................................................... 944
CA-7.400 Through CA-7.490 ..................................................................................................................................... 952
CA-7.500 Through CA-7.593 ..................................................................................................................................... 958
CA-7.601 Through CA-7.799 ..................................................................................................................................... 969
CA-7.800 Through CA-7.890 ................................................................................................................................... 1004
CA-7.900 Through CA-7.999 ................................................................................................................................... 1009
CA-7.1001 Through CA-7.1046 ............................................................................................................................... 1046

Chapter 5: CDSI - RSCx Messages 1057

CDSI Messages........................................................................................................................................................ 1057
CIAS Messages ........................................................................................................................................................ 1060
DPCH Messages ...................................................................................................................................................... 1073
DTxx Messages ....................................................................................................................................................... 1075
EDTx Messages ....................................................................................................................................................... 1088
GRLA Through GRLX Messages............................................................................................................................... 1093
HC25 Through HISx Messages ................................................................................................................................ 1097
HLP0 Through HS0x Messages ............................................................................................................................... 1111
INxx Messages ........................................................................................................................................................ 1131
JCKn Messages ....................................................................................................................................................... 1139
L2xxx Messages ...................................................................................................................................................... 1144
MLRF Through MNU0 Messages ............................................................................................................................ 1147
PCAL Messages ....................................................................................................................................................... 1154
QM Messages ......................................................................................................................................................... 1162
RMS1 Messages...................................................................................................................................................... 1224
RSCx Messages ....................................................................................................................................................... 1226

Chapter 6: SANx - SJR2 Messages 1241

SANx ....................................................................................................................................................................... 1241
SATO ....................................................................................................................................................................... 1250
SCMx Through SCM9 .............................................................................................................................................. 1255
SCNI Through SCN0 ................................................................................................................................................ 1322
SCO0 Through SCRJ ................................................................................................................................................ 1343
SDxx ........................................................................................................................................................................ 1351
SFCx ........................................................................................................................................................................ 1355
SFEx ........................................................................................................................................................................ 1381
SIRx ......................................................................................................................................................................... 1384
SJC0 ........................................................................................................................................................................ 1390
SJLx ......................................................................................................................................................................... 1394
SJRx ......................................................................................................................................................................... 1397

10 Message Reference Guide

Chapter 7: SLFA - SPOR Messages 1413
SLFA Through SLI7 .................................................................................................................................................. 1413
SMF0....................................................................................................................................................................... 1457
SMXx....................................................................................................................................................................... 1463
SMxx ....................................................................................................................................................................... 1482
SOxx ........................................................................................................................................................................ 1565
SPOx ....................................................................................................................................................................... 1566

Chapter 8: SPO0 - XTRK Messages 1595

SPO0 Through SPO9 ............................................................................................................................................... 1595
SPRG Through SRC2 ................................................................................................................................................ 1635
SSM0 Through SYS0 ................................................................................................................................................ 1655
TIQ1 Through Tnnn ................................................................................................................................................ 1696
UTLx ........................................................................................................................................................................ 1700
WPxx....................................................................................................................................................................... 1722
XAGT ....................................................................................................................................................................... 1735
XCAN....................................................................................................................................................................... 1738
XDSI ........................................................................................................................................................................ 1743
XKPI ........................................................................................................................................................................ 1744
XREF........................................................................................................................................................................ 1745
XTRE ....................................................................................................................................................................... 1747
XTRK ....................................................................................................................................................................... 1751

Appendix A: Database Verification (DBVR) 1753

000 Through 255 Messages.................................................................................................................................... 1753

Appendix B: Abend Codes 1779

Appendix C: Master Station Message Routing 1783

Contents 11
Chapter 1: Introduction
This guide lists the messages and codes produced by CA Workload Automation SE (CA
Workload Automation SE). This guide is intended for all users of CA Workload
Automation SE.

The messages and codes are arranged in alphanumeric order for easy reference. (This
includes messages with hex prefixes.) The basic format of the guide is to give the code
and message, an explanation of the error condition, and the required action to facilitate
recovery, where recovery is necessary.

Some of the messages produced are information messages and require no action. Some
messages have multiple reasons for the message.

Chapter 1: Introduction 13
Chapter 2: AFM - CA7R Messages
This chapter contains the AR through CA7R messages.

AFM Messages
This section contains the AFM messages.

AFM2-001

STORAGE OBTAIN failed

Reason:
A STORAGE OBTAIN for a work area for IAS control blocks has failed. The command
terminates.

Action:
Retry the command. If the problem persists, contact your installation specialist for
assistance.

AFM2-002

AFM Builder load failed

Reason:
Unable to access the IAS AFM Builder module.

Action:
Make sure CAIASBLD is in a library accessible from CA Workload Automation SE.

Note: CAIASBLD is in the CA Integrated Agent Services (CA IAS) load library.

AFM2-003

Invalid AFM format

Reason:
The AFM Builder returned an invalid AFM. This is an internal error.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 15

AFM Messages

AFM2-004

Security error

Reason:
Authorization for the signed on CA Workload Automation SE user has failed on an
external security call.

Action:
Ensure the user is authorized for the command.

Note: For more information about security for agent commands, see the Security
Reference Guide.

AFM2-007

IAS SEND_MESSAGE failed, rc=xxxx, reason

Reason:
An attempt to send to the agent has failed with the indicated return code and reason.

Action:
Ensure the target agent is available. Contact your installation specialist for assistance.

AFM2-008

Invalid SCT extension or WOB block

Reason:
An internal control block is not in the correct format. This is an internal error.

Action:
Contact your installation specialist for assistance.

16 Message Reference Guide

 AR Messages

AFM2-009

Timed out waiting on response

Reason:
A command has been sent to the target agent, but a response was not received within
the timeout interval.

Action:
Retry the command. If the problem persists, contact your installation specialist for
assistance.

AFM2-010

Invalid function

Reason:
An invalid function has been passed to the common command module. This is an
internal error.

Action:
Contact your installation specialist for assistance.

AR Messages
This section contains the AR messages.

ARHT ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Reason:
An ARF internal error occurred. Issued by SASSAIIS, SASSAILE, SASSAILS, SASSAISC.

ARQM ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Reason:
An ARF internal error occurred. Issued by SASSAIJC.

Chapter 2: AFM - CA7R Messages 17

AR Messages

AR31-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data.

Action:
Self-explanatory.

AR31-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

AR31-01

ww INVALID MACRO RETURN CODE nnnn

Reason:
An unexpected error condition was detected in program SASSAR31. The location in the
program is specified by ww and the value of register 15 is shown by nnnn. If nnnn=0000,
a CA Workload Automation SE data set may be out of space.

Action:
If nnnn=0000, check the system console for error messages. If the out-of-space
condition is indicated, increase the size of the failing data set. Otherwise, contact your
installation specialist for assistance.

AR31-02

ARFSET NOT FOUND

Reason:
The requested ARFSET was not found, or UID security has failed the request.

Action:
Check for correct input. If in error, correct and retry.

18 Message Reference Guide

 AR Messages

AR31-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The xxxxxxxx field is required and was not entered, or an invalid value was entered.

Action:
Enter a valid value for the indicated field.

AR31-07

ARFSET ALREADY EXISTS

Reason:
An attempt was made to add an ARFSET, but that ARFSET name already exists.

Action:
Change the ARFSET name to a unique value.

AR31-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT ARFSET

Reason:
An attempt was made to alter or add an ARFSET definition that is not accessible due to
UID security.

Action:
If you need to change an existing ARFSET or to add a new one, contact your installation
security administrator.

AR31-13

NO SAVE -- DEFINITION COUNT ZERO

Reason:
This message is issued if an attempt is made to save an ARFSET with no condition
definitions. A valid ARFSET contains at least one condition definition.

Action:
Define a valid condition definition and attempt the SAVE again.

Chapter 2: AFM - CA7R Messages 19

AR Messages

AR31-14

nnnn ARFIO ERROR R15=xxxx R0=yyyy R1=zzzz

Reason:
An error occurred while trying to update the ARF database. nnnn is the offset in
SASSAR31 where the error was detected. Additional diagnostic information is returned
in R15, R0, and R1. If R15=0010, a duplicate record is indicated.

Action:
Contact your installation specialist. For R15=0010, check the UID security of the ARFSET
being added.

AR31-15

ARFIO INIT FAILED

Reason:
ARF database processing indicated a bad return code.

Action:
Make sure that the RESTART statement in the initialization file uses ARF=YES or
ARF=MAINT.

AR31-16

RECORD NOT FOUND FOR UPDATE

Reason:
An attempt was made to replace an ARFSET definition that is not defined, or UID
security has failed the request.

Action:
Check for correct input. If in error, correct and retry.

20 Message Reference Guide

 AR Messages

AR31-17

RESPONSE ID IS MISSING OR INVALID

Reason:
This message is issued when an ARFSET is added or updated without supplying a valid
RESPONSE ID. This ID is required to log on to a CA Workload Automation SE internal
terminal when responses are to be executed. The ID must have the authority to execute
any of the commands implied in the recovery sequence. If external security with
SUBCHECK is used, this field will have the SUBCHECK process done.

Action:
Supply a valid RESPONSE ID and attempt the SAVE or REPLACE again.

AR31-18

EDIT FUNCTION SUCCESSFUL, ENTER SAVE OR REPL TO UPDATE ARFSET

Reason:
An ARFSET EDIT session ended with a SAVE command.

Action:
Perform one the following actions:
■ Issue a second SAVE command to retain a new ARFSET.
■ Issue a REPL command to update a previously existing ARFSET with changes made
in the EDIT session.

Note: This message does not appear when the EDIT session is ended with SS for a new
ARFSET or SR for an old ARFSET and the updates are retained.

AR31-19

EXIT FROM EDIT SUCCESSFUL, NO CHANGES TO ARFSET

Reason:
An ARFSET EDIT session ended with an EXIT command. No changes from the EDIT
session were retained for the ARFSET.

Action:
None.

Chapter 2: AFM - CA7R Messages 21

AR Messages

AR32-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

AR32-01

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSAR32. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn. If
nnnnnnnn=00000000, a CA Workload Automation SE data set may be out of space.

Action:
If nnnnnnnn=00000000, check the system console for error messages. If the
out-of-space condition is indicated, increase the size of the failing data set. Otherwise,
contact your installation specialist for assistance.

AR32-02

DEFINITION NOT FOUND

Reason:
The definition associated with the DEFID specified could not be located.

Action:
Supply a valid DEFID and retry the command.

AR32-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The xxxxxxxx field is required and was not entered, or an invalid value was entered.

Action:
Enter a valid value for the indicated field.

22 Message Reference Guide

 AR Messages

AR32-07

DEFINITION INDEX ALREADY EXISTS

Reason:
The DEFID value supplied is already associated with an existing definition in the set.

Action:
Supply a valid DEFID and retry the command.

AR32-14

xxxx(nnnn) INVALID VALUE FOR kkkkkkkk

Reason:
A valid value for the field kkkkkkkk was not supplied. The last four characters of the
name of the module detecting the error are xxxx. The program offset is nnnn. A detail
message usually accompanies this message. Detail messages include the following:
AO VALUE MUST BE + OR -
CONSULT DOCUMENTATION FOR VALID MODES
Indicates EM in error.
DATE OUT OF ALLOWABLE RANGE
EC, EE, JC, IS, LA, LB, LE, LS, OR S ARE VALID
Indicates TYPE value in error.
FROM D/T GREATER THAN TO D/T
HRC REQUIRES STEP, PROC AND PGM EQ *
Indicates Type JC CC/ABENDS error.
INTERNAL LOGIC ERROR
Contact CA Support.
INVALID DATA IN FIELD
INVALID DATE FORMAT
INVALID TIME FORMAT
NO OTHER FORMATS MAY BE USED WITH HRC
Indicates Type JC CC/ABENDS error.
REFER TO DOCUMENTATION FOR VALID FORMAT
RO VALUE MUST BE EQ IF SID VALUE IS 0
Indicates RO in error.

Chapter 2: AFM - CA7R Messages 23

AR Messages

RO VALUE MUST BE EQ OR NE
Indicates RO in error.
RO VALUE MUST BE EQ, NE, GT, GE, LT OR LE
Indicates RO in error.
UNRECOGNIZED RESERVED WORD
VALID FORMATS ARE: SYS, USR, CC, FL
Indicates Type SC CC/ABENDS error.
VALID FORMATS ARE: SYS, USR, CC, FL, JCL OR HRC
Indicates Type JC CC/ABENDS error.
VALID LOGICAL OPERATORS ARE: &, /
VALUE MUST BE BETWEEN 0 AND 255
VALUE MUST BE BETWEEN 0 AND 999
VALUE OF CODE INCONSISTENT WITH FORMAT

Action:
Correct and retry the command.

AR32-17

TOO MANY DEFINITIONS -- MAX IS 20

Reason:
Each ARFSET can only have 20 definition indexes.

Action:
Consolidate DEFIDs, or create a new ARFSET.

24 Message Reference Guide

 BCLP Messages

AR32-18

NEW DEFID REQUIRES ADD

Reason:
A SAVE command was entered while editing a new ARF definition. A DEFID value was
entered that had not been added to the ARFSET.

Action:
Perform the following actions:
■ Enter ADD in the function field to create the new definition for this ARFSET.
■ Enter SAVE, SR, or SS to update the ARFSET with the new definition and any other
changes made during the edit session.

AR32-19

CHANGE FOUND, REQUIRES REPL

Reason:
A SAVE command was entered while editing a new ARF definition. The currently
displayed DEFID was found to have one or more fields modified.

Action:
Perform the following actions:
■ Enter REPL in the function field to update the displayed definition for this ARFSET.
■ Enter SAVE, SR, or SS to update the ARFSET with that definition and any other
changes made during the edit session.

BCLP Messages
This section contains the BCLP messages.

Chapter 2: AFM - CA7R Messages 25

BCLP Messages

BCLP-00

INVALID MSG NUMBER - MSG NO=xx

Reason:
Message number xx was issued by SASSBCLP but was not found in the messages module
SASSBCLM. The program is aborted and no further processing is done.

Action:
For assistance, contact CA Support at ca.com/support.

BCLP-10

DATA SET SCRATCHED FROM VOL = xxxxxx AT hh:mm:ss ON yy.ddd

Reason:
On a REPLACE, the original data set on volume xxxxxx was scratched at the time and
date indicated. This is a normal information message on a REPLACE.

Action:
None.

BCLP-11

DATA SET ALLOCATED ON VOL = xxxxxx AT hh:mm:ss ON yy.ddd

Reason:
A data set has been allocated on volume xxxxxx at the time and date indicated. This is a
normal information message.

Action:
None.

BCLP-12

DATA SET ACCESS COMPLETE AT hh:mm:ss ON yy.ddd

Reason:
The data set has been successfully created or modified at the time and date indicated.
This is a normal information message.

Action:
None.

26 Message Reference Guide

 BCLP Messages

BCLP-13

DATA SET CATALOGED ON VOL = xxxxxx AT hh:mm:ss ON yy.ddd

Reason:
The data set has been successfully cataloged or recataloged on volume xxxxxx at the
time and date indicated. This is a normal information message.

Action:
None.

BCLP-14

DATA SET RECATALOGED ON VOL = xxxxxx AT hh:mm:ss ON yy.ddd

Reason:
The data set has been recataloged on volume xxxxxx at the time and date indicated. The
data set originally pointed to by the catalog was not scratched.

Action:
None.

BCLP-15

TYPE 99 RECORD CREATED AT hh:mm:ss ON yy.ddd

Reason:
A pseudo-SMF record (type-99) was successfully created at the time and date indicated.
This is a normal information message.

Action:
None.

BCLP-16

DATA SET PROCESSING COMPLETE AT hh:mm:ss ON yy.ddd

Reason:
All required actions for the data set were completed at the time and date indicated. This
is a normal information message.

Action:
None.

Chapter 2: AFM - CA7R Messages 27

BCLP Messages

BCLP-17

BATCH CARD LOAD PROCESSING COMPLETE AT hh:mm:ss ON yy.ddd

Reason:
All requests for data set processing have been completed at the time and date
indicated. This is a normal information message.

Action:
None.

BCLP-18

DATA SET SKIPPED DUE TO ERROR

Reason:
All processing for the data set was suspended because of the displayed errors. Any
actions noted as complete stand as noted.

Action:
Correct the errors displayed, restore the data set if necessary and rerun the Batch Card
Load Program (BCLP).

BCLP-19

DATA SET SKIPPED DUE TO EXIT REQUEST

Reason:
All processing for the data set was suspended because of a data set skip request by the
user exit routine. Any actions noted as complete stand as noted.

Action:
Correct as noted by the exit program and rerun BCLP.

28 Message Reference Guide

 BCLP Messages

BCLP-20

INVALID PARM FIELD

Reason:
The parameter field on the EXEC statement is invalid because of one of the following
reasons:
■ The keyword is not EXITPROG or ERROR.
■ The operand of EXITPROG is longer than eight characters.

The program is aborted.

Action:
Correct the parameter field and resubmit the job.

BCLP-21

ERROR CALCULATING TRACKS - RC=xxxx

Reason:
An error was returned from the TRKCALC macro while calculating space required for the
data set. An abend will occur.

Action:
Verify volume requested is a valid DASD device. If not, correct and rerun. If device is
DASD, save the JCL, SYSLOG and SYSUDUMP data. For assistance, contact CA Support at
ca.com/support.

BCLP-22

DDNAME/VOLSER DON'T MATCH dddddddd/vvvvvv

Reason:
The DDNAME (dddddddd) and VOLSER (vvvvvv) displayed do not match. This is a
warning message only; normal processing continues. Requests for a specific volume will
be satisfied by inspecting and assigning the volume by VOLSER. If the volume is not
specified in the JCL, the ddname must be U7VOLSER.

Action:
Verify that data sets are created on the volumes that you want.

Chapter 2: AFM - CA7R Messages 29

BCLP Messages

BCLP-23

NO DATA SET CONTROL CARDS

Reason:
No valid data set control statements were found. The job is ended without a dump.

Action:
Correct errors or enter control statements or both.

BCLP-24

INVALID RETURN CODE FROM EXIT

Reason:
The user exit program returned an invalid return code. The Batch Card Load Program is
aborted.

Action:
Correct the exit program and resubmit the job.

BCLP-30

MISSING OR INVALID OPERATOR

Reason:
The control statement operator was either missing or invalid. The data set request is
bypassed.

Action:
Correct control statement and resubmit.

BCLP-31

OUT OF PLACE OPTION CARD

Reason:
An OPTION statement was found but was not the first control statement encountered.
The Batch Card Load Program is aborted.

Action:
Examine, correct and resubmit.

30 Message Reference Guide

 BCLP Messages

BCLP-32

MISSING CONTROL CARD

Reason:
An EODS control statement was followed by a data statement without an intervening
data set control statement. All statements are bypassed until the next valid data set
control statement is found.

Action:
Examine, correct, and resubmit the data set request.

BCLP-33

INVALID CONTROL CARD - BLANK

Reason:
A control statement with a valid ID (&UCC7) was found but did not contain an operator
or keyword. All statements are bypassed until the next valid control statement (with
operator) is found.

Action:
Examine, correct, and resubmit the request.

BCLP-34

EXPECTED CONTINUATION NOT RECEIVED

Reason:
A control statement ending with a comma was not followed by another control
statement. The data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

Chapter 2: AFM - CA7R Messages 31

BCLP Messages

BCLP-35

INVALID CONTROL CARD - EXTENDS BEYOND COL 71

Reason:
A control statement was encountered that extended beyond column 71. The data set
request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-40

INVALID KEYWORD - xxxxxxxx

Reason:
Keyword xxxxxxxx is not a recognizable keyword. An attempt will be made to find the
next valid keyword. The data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-41

KEYWORD INVALID WITH OPERATOR - KW=xxxxxx

Reason:
Keyword xxxxxx is invalid with the operator entered. The remaining keywords are
examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-42

KEYWORD OPERAND TOO LONG - KW=xxx...

Reason:
The operand of keyword xxx... is longer than the maximum allowed. The remaining
keywords are examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

32 Message Reference Guide

 BCLP Messages

BCLP-43

UNBALANCED PARENTHESES IN KW=xxx...

Reason:
Keyword xxx... contains unbalanced parentheses. The remaining keywords are examined
and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-44

MISSING DSN

Reason:
The DSN keyword, required for all data set requests, is missing. The data set request is
bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-45

INVALID DSN - NODE LONGER THAN 8 CHARACTERS

Reason:
An operand of a DSN keyword contains a node longer than eight characters. The
maximum is eight characters. The remaining keywords are examined and the data set
request is bypassed.

Action:
Correct the error and resubmit the data set request.

Chapter 2: AFM - CA7R Messages 33

BCLP Messages

BCLP-46

ATTEMPT TO CREATE GDG GREATER THAN +1

Reason:
An attempt was made to create a Generation Data Group (GDG) data set with a relative
number greater than +1. The remaining keywords are checked for errors and the data
set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-47

CREATE NOT SPECIFIED WITH +1 GDG

Reason:
A data set name indicating a new generation of a GDG was encountered but the
operator was not CREATE. The remaining keywords are examined and the data set
request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-48

OPERAND OF KEYWORD NOT NUMERIC - KW=xxxxxx

Reason:
The operand of keyword xxxxxx must be numeric, but is not. The remaining keywords
are examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

34 Message Reference Guide

 BCLP Messages

BCLP-49

BLKSIZE NOT DIVISIBLE BY 80

Reason:
The operand of the keyword BLKSIZE is not divisible by 80. The remaining keywords are
examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-50

SCHID NOT IN THE RANGE 1 TO 255

Reason:
A schedule ID entered was not between 1 and 255. The remaining keywords are
examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-51

MAXJOBS NOT IN THE RANGE 1 TO 255

Reason:
The operand of the MAXJOBS keyword is not from 1 thorugh 255. The Batch Card Load
Program is aborted.

Action:
Correct the error and resubmit the data set request.

BCLP-52

MAXJOBS EXCEEDED

Reason:
The number of jobs entered on the JOBS keyword exceeded the maximum number
allowed. The remaining keywords are examined and the data set request is bypassed.

Action:
Use the MAXJOBS keyword on the OPTION control statement to increase the maximum
number of jobs allowed and resubmit the data set request.

Chapter 2: AFM - CA7R Messages 35

BCLP Messages

BCLP-53

JOBNAME NOT FOUND ON CA-7 JLIB - JOB=jobname

Reason:
The job name displayed (jobname) was entered in the JOB keyword but was not found
in the job data set, or the job names entered were not in collating sequence. The
remaining keywords are examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-54

I/O ERROR ON CA-7 JLIB

Reason:
An I/O error was encountered while accessing UCC7JLIB. The Batch Card Load Program
is aborted.

Action:
Correct the error and resubmit data set requests not processed.

BCLP-55

CAN NOT CATALOG THIS DATA SET

Reason:
An attempt was made to catalog a GDG version that had already been dropped. The
catalog operation is not done. Processing for the data set request continues. Since JCL
overrides may be required, the type-99 record is not created.

Action:
Check for JCL overrides. POST the requirement as complete.

36 Message Reference Guide

 BCLP Messages

BCLP-56

OPERAND OF VOL= NOT 6 CHARACTERS

Reason:
The operand of the keyword VOL is shorter or longer than six characters. The remaining
keywords are examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-57

OPERAND OF CVOL= NOT 6 CHARACTERS

Reason:
The operand of the keyword CVOL is shorter or longer than six characters. The Batch
Card Load Program is aborted.

Action:
Correct and resubmit the job.

BCLP-58

CVOL POINTS TO VOLUME WITH CA-7 IDS

Reason:
The volume that is specified with the CVOL keyword specifies the volume that contains
the CA Workload Automation SE Index Data Set (IDS). The remaining keywords are
examined and the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-70

ERROR ON SYSTEM CATALOG SEARCH - RC=

Reason:
A LOCATE issued against the Index data set (IDS) received the displayed return code. The
data set request is bypassed.

Action:
Correct the error. Resubmit the data set request.

Chapter 2: AFM - CA7R Messages 37

BCLP Messages

BCLP-71

GDG NOT CATALOGED

Reason:
A search for a GDG in the IDS determined that the data set was not cataloged. The data
set request is bypassed.

Action:
Catalog the GDG. Resubmit the data set request.

BCLP-72

ERROR ON SYSTEM CATALOG UPDATE - RC=

Reason:
An attempt to CATALOG or RECATALOG the data set resulted in the return code
displayed. The data set request is bypassed. All actions noted as complete are still
effective.

Action:
Correct the error and resubmit the data set request.

BCLP-73

VOLSER FROM VOL= OR CATALOG IS INVALID

Reason:
An attempt was made to assign a volume serial number either from the VOL keyword or
from the IDS. However, a CA Workload Automation SE DD statement does not represent
the volume. The data set request is bypassed.

Action:
Correct the VOLSER or add a DD statement for the volume and resubmit the data set
request.

38 Message Reference Guide

 BCLP Messages

BCLP-74

ERROR ON CA-7 IDS SEARCH - RC=

Reason:
The return code displayed was received in response to an attempt to LOCATE the data
set in the CA Workload Automation SE IDS. The data set request is bypassed.

Action:
Correct the problem and resubmit the data set request.

BCLP-75

INVALID CA-7 IDS ENTRY - ID=2 NOT FOUND

Reason:
The CA Workload Automation SE Index Data Set (IDS) entry was found but did not
contain a type-2 entry. The data set request is bypassed.

Action:
Correct the CA Workload Automation SE IDS and resubmit the data set request.
Consider adding the data set to the database from the DSN panel.

BCLP-76

UNABLE TO FIND DATA SET ON REPLACE

Reason:
On a request for the replacement of a data set, the data set was not found. The data set
request is bypassed.

Action:
Correct the error and resubmit the data set request.

Chapter 2: AFM - CA7R Messages 39

BCLP Messages

BCLP-77

MODDATA DATA SET FOUND ON NON-SPECIFIC REQ

Reason:
On a MODDATA request VOL was omitted and the data set was not cataloged. As a
result the first volume was assigned. However, the data set was found on that volume.
All further processing of this data set is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-78

CREATE SPECIFIED AND DATA SET FOUND ON VOL

Reason:
The operator CREATE was specified but the data set was found on the assigned volume.
The data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-79

REPLACE SPECIFIED AND DATA SET NOT ON VOL

Reason:
The operator REPLACE was specified but the data set was not found on the assigned
volume. The data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

40 Message Reference Guide

 BCLP Messages

BCLP-80

DURING VOL ROTATION THE DATA SET WAS FOUND

Reason:
After an initial insufficient space condition was encountered, volume rotation was
initiated. During rotation the data set name was found on a volume. All further
processing of the data set request is bypassed.

Action:
Correct the error and resubmit the data set request.

BCLP-81

ERROR ON OBTAIN - RC=

Reason:
The return code displayed was encountered after an attempt to OBTAIN the DSCB for
the data set. All further processing of this data set request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-82

REQUEST DENIED BY SECURITY, ACCESS = xxxxxxxx

Reason:
Data set action requested is not authorized by the security system for the USERID that
Batch Card Load is running under. The access indicated by xxxxxxxx in the message is
rejected. See the JOB statement USER parameter or /*LOGONID or /*JOBFROM
statements in the JCL for the USERID being checked.

Action:
Resubmit the job with a USERID authorized for the data set action that you want, or
contact your installation security administrator to arrange access for the USERID being
checked.

Chapter 2: AFM - CA7R Messages 41

BCLP Messages

BCLP-85

JOB NOT RUN SINCE LAST DATA SET UPDATE - JOB=

Reason:
The job displayed was entered on the JOB keyword and has not run since the last
update of this data set. All further processing of this data set request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-89

ERROR ON SCRATCH - RC=

Reason:
While scratching the data set, the displayed return code was encountered. All further
processing of this data set request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-90

BLKSIZE TOO LARGE FOR DEVICE(S)

Reason:
The block size requested is too large for the device assigned, or no volume capable of
containing the block size was found. All further processing of this data set request is
bypassed.

Action:
Either decrease the block size requested or add a device capable of containing the block
size. Resubmit the data set request.

42 Message Reference Guide

 BCLP Messages

BCLP-91

INSUFFICIENT SPACE ON DEVICE(S)

Reason:
For a specific volume request, the device did not have sufficient space to contain the
data set. For a non-specific volume request or when volume rotation is authorized, no
volume was found that had both sufficient space and could contain the requested block
size. All further processing of the data set request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-92

ERROR ON CA-7 SVC - RC=

Reason:
The CA Workload Automation SE SVC used to execute the ALLOCATE SVC returned the
code displayed. All further processing of the data set request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-93

ERROR ON ALLOCATE - RC=

Reason:
The ALLOCATE SVC returned the code displayed. All further processing of this data set
request is bypassed.

Action:
Correct the condition and resubmit the data set request.

BCLP-94

BLKSIZE MISSING FOR ALLOCATED DSN

Reason:
DSN was being replaced or created but was allocated without a block size.

Action:
Reallocate the data set and specify the block size.

Chapter 2: AFM - CA7R Messages 43

BCLP Messages

BCLP-95

NCF NOT INSTALLED

Reason:
The NCFNODE keyword was specified in PARM input to BCLP, but NCF is not installed.

Action:
Remove NCFNODE keyword from PARM input and retry if NCF routing is not required. If
NCF routing is needed, verify the CA Workload Automation SE NCF installation with your
installation specialist or systems programmer.

BCLP-96

UNDEFINED NCF NODE=xxxxxxxx

Reason:
The NCFNODE keyword specified in PARM input to BCLP requested a name not found in
the NCF Node Table. The invalid node is indicated by xxxxxxxx.

Action:
Remove NCFNODE keyword and retry if NCF routing is not required. If NCF routing is
needed, verify the node name specified with your installation specialist or systems
programmer.

BCLP-97

ALLVSAM ERROR ATTEMPTING TO INIT/CONN, RC=xxxx

Reason:
Errors occurred while attempting to initialize, connect, disconnect, or finish with an
ALLVSAM database. RC value gives error code that is further explained by WTO
messages.

Action:
Diagnose problem from WTO messages and take appropriate action.

44 Message Reference Guide

 BK0x Messages

BCLP-99

ICMDSECT NOT FOUND OR NOT MATCHED. INSTANCE NAME=xxxx

Reason:
The instance of CA Workload Automation SE that was requested was not active.

Action:
Ensure the CA Workload Automation SE instance is active before resubmitting BCLP.

BK0x Messages
This section contains the BK0x messages.

BK00.001

NO PARMS ENTERED

Reason:
The Backup/Reload program requires parameters to be supplied on the EXEC statement
in the JCL to specify which options are chosen.

Action:
Enter appropriate parameters in JCL and resubmit the job.

BK00.002

ONE OR MORE PARMS INVALID

Reason:
The parameters specified on the EXEC statement in the JCL had at least one invalid
specification.

Action:
Correct the parameters and resubmit the job.

Chapter 2: AFM - CA7R Messages 45

BK0x Messages

BK00.003

SPECIFIED EXIT ROUTINE NOT FOUND

Reason:
The exit routine requested to be called during this execution was not found in the load
library by BLDL. The exit name may have been spelled incorrectly or the library
containing the exit may not be concatenated with the JOBLIB/STEPLIB.

Action:
Check the spelling of the exit program name and correct it if necessary. If the exit
program name is correct, find in which library it exists and supply the appropriate DD
statement in the concatenation.

BK00.004

SVINIT FAILED

Reason:
The initialization of the CA Workload Automation SE Backup/Reload program failed.
Programs and parameters required to continue execution could not be initialized.

Action:
Save console listings and logs. Review any preceding messages (CA-7.Vxxx) for
explanation of errors. Contact your installation specialist for assistance.

BK00.005

SVCONN FAILED

Reason:
The CA Workload Automation SE databases could not be CONNected for this
Backup/Reload execution.

Action:
Save console listings and logs. Review any preceding messages (CA-7.Vxxx) for
explanation of errors. Contact your installation specialist for assistance.

46 Message Reference Guide

 BK0x Messages

BK00.006

xxxxxx FAILED FOR DDN=dddddddd

Reason:
A failure occurred on the file indicated by dddddddd. The operation that failed is
identified by xxxxxx.

Action:
Correct the error indicated by xxxxxx and retry. The most likely error is a missing DD
statement.

BK00.008

LOAD FAILED FOR SASSBK08

Reason:
A load attempt failed for module SASSBK08.

Action:
Verify that SASSBK08 is in an available library. Correct by specifying the library
containing SASSBK08.

BK00.x99

yyyyyy COMPLETED WITH ERRORS NOTED ABOVE

Reason:
The message indicates that the BACKUP or RELOAD operation completed, but some
records were found to be in error as noted by the preceding WTOs.

Action:
Examine the preceding WTO error messages from this run and correct the problems
noted. RELOAD can correct some errors noted during BACKUP. The Database
Verification program should be executed to check for possible related errors, especially
if RELOAD indicates error conditions.

Chapter 2: AFM - CA7R Messages 47

BK0x Messages

BK03.300

SVBACKUP FAILED, RC=xx, REAS=yyyy

Reason:
A failure occurred while putting data to the backup data set.

If RC=8, see REAS codes noted below.

■ 04 - VSVT PARAMETER ABSENT OR INVALID
■ 08 - RECRD PARAMETER ABSENT OR INVALID
■ 12 - KEYAD PARAMETER ABSENT OR INVALID
■ 16 - RECTYP PARAMETER ABSENT OR INVALID (bad data record)
■ 20 - DSTYPE PARAMETER ABSENT OR INVALID
■ 24 - CALLID PARAMETER ABSENT OR INVALID
■ 28 - SVAGNPCB MACRO FAILED ON FIND
■ 32 - SVGETTYP MACRO FAILED
■ 36 - SVGETLEN MACRO FAILED
■ 40 - RECORD SEQUENCE ERROR (previous messages show keys)
■ 44 - SVAGNPCB MACRO FAILED ON ASSIGN
■ 48 - VDVT EYECATCHER NOT 'VDVT'
■ 52 - ILLEGAL DATATYPE CODE
■ 56 - CALLID SPECIFIED NOT USED EXCLUSIVELY FOR BACKUP FUNCTION

Action:
Review the job's log for other error messages that should describe the problem.

48 Message Reference Guide

 BK0x Messages

BK06.600

SVRELOAD FAILED, RC=xx, REAS=yyyy

Reason:
A failure occurred while getting data from the backup data set.

If RC=8, see REAS codes noted below.

■ 00 - VSVT PARAMETER INVALID
■ 04 - KEYAD PARAMETER INVALID
■ 12 - RECTYP PARAMETER INVALID (bad data record)
■ 16 - DSTYPE PARAMETER INVALID
■ 24 - ACCTYP LOAD OR RELOAD NOT CONNECTED
■ 28 - SVAGNPCB FAILED ON FIND
■ 32 - CALLID ALREADY IN USE
■ 36 - KEY SEQUENCE ERROR (previous messages show keys)
■ 40 - VPCB INVALID. VPCBFLG
■ 44 - VDVT DAMAGED OR INVALID
■ 48 - DATATYPE NOT IN VDVT
■ 52 - SASSVZ00 ERROR ON OUTPUT
■ 56 - SVANGPCB FAILED ON ASSIGN
■ 60 - GET MACRO FAILED (IBM messages show error)
■ 64 - VPCB INVALID. VPCBFL7
■ 68 - SASSVZ00 ERROR ON INPUT
■ 72 - SASSV081 ABNORMAL COMP

Action:
Review the job's log for other error messages that should describe the problem.

Chapter 2: AFM - CA7R Messages 49

BK0x Messages

BK06.601

SVEXTPUT FAILED, RC=xx, REAS=yyyy

Reason:
A failure occurred while putting data to the database.

If RC=8, see REAS codes noted below.

■ 20 - Control Interval conflict (someone else updating DB)
■ 40 - Insufficient storage (increase region)

Action:
Review the job's log for other error messages that should describe the problem. Try
specifying a larger region for the job. If a larger region does not resolve the problem, use
disk spooling by including a DD statement for PDSWORK that references temporary disk.

BK06.602

BAD MEMBER ENTRY FOR KEY=kkkkkkkk, DSTYPE=ddd, INVALID BLOCK DROPPED

Reason:
An error was found while processing the member data for the key and data set
indicated. The data was not loaded to the database.

Action:
Check the indicated key for access using Database Maintenance and listing panels such
as JOB, LJOB, LPROS and DSN. For DSTYPE=JOB, try issuing a LOAD command to CA
Workload Automation SE to rebuild the member. The entry may have to be deleted and
added to the database.

BK06.604

DSDS ZERO REBUILT FOR RECTYP=rrrr

Reason:
A numbering control record (DS0, NW0, and so on) was missing or in error from the
backup file. RELOAD has rebuilt the ZERO record for the RECTYP indicated.

Action:
None.

50 Message Reference Guide

 BK0x Messages

BK06.605

RECORD INVALID, NOT RELOADED

Reason:
The record key indicated in the immediately preceding messages was invalid. The record
was not reloaded so as to prevent possible abend situations. Generally, the error is a
key edit failure that is probably an Index Data Set entry representing a noncatalogable
data set name.

Action:
If you want the record reloaded despite the errors identified in preceding messages,
rerun the RELOAD with the FORCE parameter; that is, OPT=(RELOAD,FORCE).

Note: Some error conditions will not be reloaded regardless of the FORCE parameter. If
the keys reported are needed, they must be added to the system and may require
cleanup of invalid keys.

BK07.700

OPEN FAILED FOR DDN=dddddddd

Reason:
The DD statement indicated could not be opened.

Action:
Verify that the DD statement noted is present, then check for other messages in the job
log. Correct any errors identified and retry.

Chapter 2: AFM - CA7R Messages 51

BK0x Messages

BK07.710

#DSD ENTRIES = nnnnnnnn DS0 VALUE = nnnnnnnn (dddddddd) HI DSNBR = dddddddd

Reason:
During a backup operation, utility SASSBK00 tracks the data set DSNBRs and produces
this WTO if the number exceeds 9,900,000. The characters nnnnnnnn represents a
hexadecimal number and dddddddd represents a decimal number. Although a return
code 399 is issued from the program execution, the backup data set is considered
successful if no other errors are encountered. This message provides a warning to clean
up any old and outdated data sets tracked by CA Workload Automation SE.

Action:
If this message appears in the JES job log of SASSBK00 backup execution, the limit of
maximum data set DSNBRs is approaching. Review all data sets and delete any unused
CA Workload Automation SE tracked data sets. If data sets are not cleaned up, CA
Workload Automation SE stops creating new entries to represent data sets, causing
problems in cycle executions.

BK08.800

PDSWORK NOT FOUND, CORE SPOOLING USED

Reason:
The DD statement for PDSWORK was not found so spooling of directory entries will be
done in memory rather than on disk.

Action:
None, this is normal and expected.

BK08.801

CANNOT USE TAPE DATA SET FOR PDSWORK

Reason:
The DD statement for PDSWORK was pointing to a tape device. Directory spooling is
only done on disk devices or in memory.

Action:
Change the DD statement to reference temporary disk storage or remove the DD
entirely.

52 Message Reference Guide

 BK0x Messages

BK08.802

GETMAIN FAILED, SPOOLING TERMINATED

Reason:
Directory spooling is being done in memory but storage is not available.

Action:
Try specifying a larger region for the job. If a larger region does not resolve the problem,
use disk spooling by including a DD statement for PDSWORK that references temporary
disk.

BK08.803

OPEN FAILED FOR PDSWORK, SPOOLING TERMINATED

Reason:
The PDSWORK file failed to open.

Action:
Check the job's log for error messages explaining the failure. Correct the problem and
retry.

BK08.804

NO DSDS ZERO FOUND FOR RECTYP=rrr

Reason:
A numbering control record (DS0, NW0, and so on) was missing or in error for the
RECTYP noted.

Action:
If this message appears from a BACKUP run, a RELOAD will correct the problem.
Otherwise, no action is required.

Chapter 2: AFM - CA7R Messages 53

BSTR Messages

BK08.805

INVALID RECORD TYPE, SPOOLING TERMINATED

Reason:
Directory spooling encountered a bad record type.

Action:
If doing a BACKUP, verify that the database is for CA Workload Automation SE and that
it has been initialized by the SASSCDSI program (install job N030). If doing a RELOAD,
verify that the backup file was created by SASSBK00.

BK08.806

NO xxxxxxxx FOUND FOR KEY=kkkkkkkk, DSTYPE=ddd

Reason:
Either DIRECTORY or MEMBER data for the noted key was missing.

Action:
Run Database Verification to identify any related database entries requiring correction.

BK08.807

DUPLICATE DIRECTORY DROPPED FOR KEY=kkkkkkkk, DSTYPE=ddd

Reason:
Multiple directory entries with the same key were processed. When this happens, the
first directory is used and subsequent entries are dropped.

Action:
Contact your installation specialist for assistance.

BSTR Messages
This section contains the BSTR messages.

54 Message Reference Guide

 BSTR Messages

BSTR-00

***INPUT TO BATCH TERMINAL***

Reason:
The original input is listed as part of the output processing messages from SASSBSTR.
This message indicates the start of the input statements.

Action:
None.

BSTR-00

***END OF INPUT***

Reason:
This message terminates the list of input statements.

Action:
None.

BSTR-10

CA-7 IS NOT ACTIVE

Reason:
CA Workload Automation SE must be active to process the batch terminal input. The
control record in the Communications data set or an operator's reply to a WTOR
indicates CA Workload Automation SE is not active.

Action:
Check the UCC7CMDS DD statement in the Batch Terminal Interface PROC and the CA
Workload Automation SE PROC to be sure that it is correct. If it is, resubmit the Batch
Terminal Interface job when CA Workload Automation SE is active.

Chapter 2: AFM - CA7R Messages 55

BSTR Messages

BSTR-11

INVALID PARM FIELD (xxxxxxxxxxxxxxxxxxxx) STARTING AT yyyyyyyyyyyy

Reason:
The PARM value on the SASSBSTR execute statement contains invalid data or incorrect
syntax. The exact reason for the error is described in the (xxxxxxxxxxxxxxxx) field of the
message. The text of the PARM value is in the yyyyyyyyyyyyyyy field starting at the point
where the error was recognized.

Action:
Correct the PARM value in error and resubmit the Batch Terminal Interface job. Possible
reason messages are in (xxxxxxxxxxxxxxxxx) and the corrective action is one of the
following:
INVALID DSN PREFIX
The data set name prefix on the DSNPFX= keyword is invalid. If the prefix begins
with a quote mark, it must end with a quote mark. The prefix must be 35 characters
or less (not including quotes).
INVALID INSTANCE
The CA Workload Automation SE tracking instance specified in the PARM field is not
a valid instance name or the instance has not been initialized.
INVALID TERMINAL
When used in the first position of the PARM field, the terminal number must be
between 0 and 8 (zero indicating Dynamic BTI Management). When used as
operands of the POOL= keyword, terminal numbers must be between 1 and 8.
INVALID TERMINAL LIST
When specifying a list or range of terminals on the POOL= keyword, you must
specify more than one terminal number.
INVALID TERMINAL RANGE
When specifying a range of terminals on the POOL= keyword, the format is
POOL=(x-y) where x and y are terminal numbers. The terminal number for y must
be greater than the terminal number for x.
NON-NUMERIC TERMINAL
Terminal numbers must be numeric.
UNKNOWN KEYWORD
The PARM value contains an invalid keyword. The valid keywords are POOL,
DSNPFX, NOMCHK, and NOWAIT.

56 Message Reference Guide

 BSTR Messages

BSTR-12

OPERATOR RESPONDED TO WTOR WITH CANCEL

Reason:
An operator replied CANCEL to a WTOR. Check your SYSOUT for information.

Action:
Determine the condition that caused the WTOR to be issued. Take any necessary
corrective action and resubmit the Batch Terminal Interface job.

BSTR-13

SYSIN DD STATEMENT MISSING

Reason:
The SYSIN file was omitted from the Batch Terminal Interface JCL.

Action:
Correct and resubmit the Batch Terminal Interface job.

BSTR-14

BATCHIN DD STATEMENT MISSING

Reason:
The BATCHIN DD statement, which identifies the input data set for the batch terminal,
was omitted from the JCL. This message only occurs when Dynamic BTI Management is
not being used.

Action:
Correct and resubmit the Batch Terminal Interface job.

BSTR-15

BATCHOUT DD STATEMENT MISSING

Reason:
The BATCHOUT DD statement, which identifies the output data set for the batch
terminal, was omitted from the interface JCL.

Action:
Correct and resubmit the Batch Terminal Interface job.

Chapter 2: AFM - CA7R Messages 57

BSTR Messages

BSTR-16

CA-7 UNABLE TO START BATCH TERMINAL

Reason:
Any of the following conditions may cause this message:
■ The PARM value on the SASSBSTR execute statement specified a relative batch
terminal that does not exist (for example, PARM=7 was specified but only four
batch terminals are defined in the product's initialization file).
■ The control record in the Communications data set indicates the specified batch
terminal is already in use. This may be due to an erroneous RESET reply to the
CA-7.252 WTOR, or a /START may have been issued from a CA Workload
Automation SE terminal.
■ No batch terminals are defined to CA Workload Automation SE.

Action:
If the PARM value is invalid, correct and resubmit the Batch Terminal Interface job. If a
RESET reply was inadvertently entered or if a /START was issued, make sure that data
center personnel understand the proper use of these commands. There should be no
problem in rerunning the interface job.

BSTR-17

BATCHOUT OVERFLOWED - OUTPUT TRUNCATED

Reason:
The Batchout data set is not large enough to handle the output for the Batch Terminal
Interface.

Action:
Increase the size of the Batchout data set and try running the interface again.

BSTR-18

ABOVE TRANSACTION IS INVALID FROM BATCH -- BYPASSED

Reason:
A system command such as /COPY was detected and bypassed. If executed, the
command could cause a system abend.

Action:
Remove the command from the SYSIN and resubmit the Batch Terminal Interface (BTI)
job, unless that was the only command in the SYSIN.

58 Message Reference Guide

 BSTR Messages

BSTR-19

BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON CARD

Reason:
The external security system would not authorize the owner of the BTI job to submit a
logon for operator ID specified on the /LOGON statement listed above this message.
Any messages returned by the external security system will be listed following this
message. The batch input statements following that logon will be skipped until another
/LOGON statement is encountered.

The owner of the BTI job is specified implicitly (the user that submits the job) or
explicitly through a USER= job parameter or equivalent.

Action:
Ensure the owner of the BTI job has SUBMIT authority for all operator IDs specified on
/LOGON statements used as batch input.

If you do not want submit security checking for CA Workload Automation SE batch jobs
(BTI, BCLP, and so on,), review the setting of the BSUBCHK option for this instance. For
more details on this option, see the Security Reference Guide.

BSTR-20

'SUBMIT' CLASS/RESOURCE NOT DEFINED TO EXTERNAL SECURITY. FUNCTION

ALLOWED

Reason:
An attempt was made to verify the authorization for the owner of the BTI job to submit
a logon for the operator ID specified on the /LOGON statement listed above this
message. The external security system responded with a return code 4, indicating
SUBMIT is not a defined resource. The /LOGON statement and the subsequent batch
input statements are processed normally.

All messages returned by the external security system are listed following this message.

Action:
If you want your external security system to control CA Workload Automation SE batch
jobs, the SUBMIT resource and applicable rules must be defined.

Note: For more information about implementation, see the Security Reference Guide.

Chapter 2: AFM - CA7R Messages 59

BSTR Messages

BSTR-23

UNABLE TO EXTRACT MODEL DSN FOR DYNAMIC ALLOCATION

Reason:
The DSN prefix extracted from the BATCHIN, BATCHOUT, or Communications data set is
greater than 35 characters.

Action:
Specify the data set name prefix of the BATCHIN/BATCHOUT data sets in the DSNPFX=
keyword on the PARM field of the SASSBSTR step execution statement.

BSTR-24

COMMUNICATIONS DATA SET DD MISSING (UCC7CMDS)

Reason:
The DD statement for the CA Workload Automation SE Communications data set is
missing from the JCL (DDNAME = UCC7CMDS).

Action:
Supply the proper UCC7CMDS DD statement.

BSTR-25

UNABLE TO ALLOCATE BATCHx#y. RC=cc ERR=eeee INFO=iiii DSN=ddddd...

Reason:
An error was encountered attempting to allocate DSN=ddd..... as DDNAME BATCHx#y
(where x is I or O, and y is the Batch Terminal number). The Dynamic Allocation return
code (RC=), error code (ERR=) and information codes (INFO=) that produced the error
are listed.

Action:
Confirm that the data set name (DSN=) is correct for your batch terminal data sets. If
not, specify the correct data set name prefix in the DSNPFX= keyword in the PARM data
on the SASSBSTR execution statement. If the data set name is correct, contact your
installation specialist for assistance.

60 Message Reference Guide

 BTSO Messages

BSTR-26

UNABLE TO OBTAIN JFCB FOR xxxxxxxx DD.

Reason:
An error was encountered issuing a RDJFCB request for ddname xxxxxxxx.

Action:
Contact your installation specialist for assistance.

BSTR-27

UNABLE TO LOCATE BATCH DATA SETS. MODEL DSN = xxxxx...

Reason:
The Dynamic BTI Management facility was unable to locate the BATCHIN data sets for
any of the batch terminals in the pool of available terminal numbers. The model DSN
used to attempt to allocate the BATCHIN data sets is listed in the message.

Action:
Confirm that the model DSN listed in the message has the correct format for your
BATCHIN/BATCHOUT data sets. If so, confirm that these data sets are cataloged and
accessible on the system where the BTI job is being executed. Also, if the POOL=
parameter is specified on the SASSBSTR execution PARM, check to ensure that the
terminal numbers specified for the terminal pool are actually defined to CA Workload
Automation SE and have BATCHIN/BATCHOUT data sets allocated for them.

If the model DSN listed in the message is NOT the correct format, specify the correct
data set name prefix in the DSNPFX= keyword in the PARM data on the SASSBSTR
execution statement.

BTSO Messages
This section contains the BTSO messages.

Chapter 2: AFM - CA7R Messages 61

BTSO Messages

BTSO-10

CA-7 IS NOT ACTIVE

Reason:
CA Workload Automation SE must be active to process the TSO input. The control record
in the Communications data set indicates it is not active.

Action:
If CA Workload Automation SE is active, reenter your data. If problem persists, contact
your installation specialist for assistance.

BTSO-11

INVALID PARM FIELD

Reason:
The PARM data in the CLIST is bad. The PARM must be exactly eight characters. The first
character must be a number from one to eight. The second character must be S or M.

Action:
Correct the CLIST and retry.

BTSO-13

UCC7IN DD STATEMENT MISSING

Reason:
The required DD statement is not allocated in your CLIST.

Action:
Correct the CLIST and retry.

BTSO-14

BATCHIN DD STATEMENT MISSING

Reason:
The required DD statement is not allocated in your CLIST.

Action:
Correct the CLIST and retry.

62 Message Reference Guide

 BTSO Messages

BTSO-15

BATCHOUT DD STATEMENT MISSING

Reason:
The required DD statement is not allocated in your CLIST.

Action:
Correct the CLIST and retry.

BTSO-16

CA-7 UNABLE TO START BATCH TERMINAL

Reason:
Either of two conditions may cause this message:
■ The PARM value specified a relative batch terminal that does not exist.
■ The control record in the Communications data set indicates the specified batch
terminal is already in use. This may be due to a /START being inadvertently issued
from the CA Workload Automation SE Master Terminal.

Action:
If the PARM value in the CLIST is invalid, correct and retry. If condition 2 occurred, make
sure that the data center personnel understand the proper use of the /START command.
You should be able to retry your command.

BTSO-17

TEMPFILE DD STATEMENT MISSING

Reason:
The required DD statement is not allocated in your CLIST.

Action:
Correct your CLIST and retry.

Chapter 2: AFM - CA7R Messages 63

CACR Messages

BTSO-18

BATCH TERMINAL IN USE

Reason:
The requested relative batch terminal is in use.

Action:
Wait a few minutes and try again. If the problem persists, check to see if someone is
entering multiple line input from a terminal. The data should be saved in a sequential
data set or PDS member, and UCC7IN changed to point there for multiple line input.

BTSO-19

BTERM FLAG RESET, SHUTDOWN ASSUMED

Reason:
The control record in the Communications data set indicates the batch terminal is no
longer in use. CA Workload Automation SE may have been shut down immediately after
your command.

Action:
If CA Workload Automation SE has not been shut down, check to see if PGM SASSBEND
or SASSICLR was executed during this time frame. These programs should execute only if
CA Workload Automation SE or SASSBSTR terminate abnormally (COND=ONLY).

CACR Messages
This section contains the CACR messages.

CACR501E

CA-DRIVER INITIALIZATION FAILED

Reason:
An unrecoverable error has occurred during storage allocation in initialization. CA Driver
terminates.

Action:
Increase the amount of virtual storage allocated to JES task.

64 Message Reference Guide

 CACR Messages

CACR503E

END OF PROCEDURE BEFORE DATA END

Reason:
CA Driver detected an end-of-file condition without a DEND statement during data
inclusion. Error statement issued.

Action:
Make sure DEND statement has been included.

CACR504E

IRRECOVERABLE ERROR IN DATA INCLUSION

Reason:
CA Driver cannot return to the procedure from which data inclusion has been invoked.
CA Driver terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CACR505E

SUBMIT END STATEMENT WITHOUT SUBMIT

Reason:
A SUBMIT END was detected without a corresponding submit statement. Error
statement issued.

Action:
Resubmit job without the SUBMIT END or include a SUBMIT statement previous to the
SUBMIT END statement.

CACR506E

SUBMIT END STATEMENT MISSING

Reason:
More than one SUBMIT statement detected without corresponding SUBMIT END
statement. Error statement issued.

Action:
Correct the job stream.

Chapter 2: AFM - CA7R Messages 65

CACR Messages

CACR507E

"varnam" WAS NOT DEFINED IN DPROC STATEMENT

Reason:
A variable name was detected on an EXEC statement that was not defined in a DPROC.
Error message issued. Variable value not assigned.

Action:
Add a definition for that variable in the DPROC statement for that procedure.

CACR508E

DATA STATEMENT IS INVALID

Reason:
A data statement can only be included in a cataloged procedure. Error message issued.

Action:
Remove DATA statement.

CACR509E

NAME IN DATA END DOES NOT MATCH

Reason:
Data verification facility detects a data name on a DEND statement that does not match
a name on corresponding DATA statement. Error message issued.

Action:
Fix names on DATA and DEND statements.

CACR510E

MODEL ON STATEMENT MISSING OR OUT OF SEQUENCE

Reason:
A MODEL ON statement was expected but not encountered. Issued by CA7ROOT.

Action:
Ensure a MODEL ON statement is present in the appropriate location.

66 Message Reference Guide

 CACR Messages

CACR511E

MODEL OFF STATEMENT MISSING OR OUT OF SEQUENCE

Reason:
A MODEL OFF statement was expected but not encountered. Issued by CA7ROOT.

Action:
Ensure a MODEL OFF statement is present in the appropriate location.

CACR512E

ENABLE/DISABLE NOT VALID IN PROCEDURE

Reason:
An ENABLE or DISABLE statement was encountered within a procedure. The command is
not valid within a procedure. Issued by CA7GETST.

Action:
Remove the ENABLE or DISABLE.

CACR515E

IRRECOVERABLE ERROR HAS OCCURED IN SCANNING DPROC STATEMENT

Reason:
An error occurred while processing a DPROC statement. Issued by CA7OPROC.

Action:
Verify that the statement is coded properly.

CACR516E

DPROC STATEMENT SYNTAX ERROR

Reason:
An error occurred while scanning a DPROC statement. Rest of DPROC statement is
ignored.

Action:
Correct error and resubmit job.

Chapter 2: AFM - CA7R Messages 67

CACR Messages

CACR518E

EXPECTED CONTINUATION DID NOT APPEAR

Reason:
CA Driver was expecting a continuation on an EXEC or DPROC statement and none was
found. Error message issued.

Action:
Check if continuation formats are being conformed to. Correct problem and resubmit
job.

CACR519E

STATEMENT HAS OVERRUN BOUNDARIES - REMAINDER TRUNCATED

Reason:
During variable substitution, more space on statement than is available is needed to
expand statement. Statement is truncated; editing continues.

Action:
Check default or assigned value for variables to correct problem.

CACR523E

LOOP COUNTER EXCEEDED FOR LABEL LABELNAM

Reason:
A label was unconditionally branched more times than specified in LCTR statement.
Branch is not taken.

Action:
Increase loop counter.

CACR525E

FORMAT ERROR ON LCTR STATEMENT

Reason:
The operand of a LCTR statement was not positive numeric. Error message issued. Loop
counter not assigned.

Action:
Correct operand of statement. Resubmit job.

68 Message Reference Guide

 CACR Messages

CACR527E

INVALID LABEL NAME ENCOUNTERED ON IF STATEMENT

INVALID LABEL NAME ENCOUNTERED ON GOTO STATEMENT

Reason:
The object of branch on an IF or GOTO statement exceeds eight characters in length.
Error message issued.

Action:
Make sure label names are eight characters or less.

CACR528E

IF OR GOTO STATEMENTS NOT VALID EXCEPT IN PROCEDURES

Reason:
An IF or GOTO statement was detected from reader. Error message issued.

Action:
Remove statement and resubmit job.

CACR529E

LABEL MISSING ON IF OR GOTO STATEMENT

Reason:
An IF or GOTO statement has no object of a branch. Error message issued.

Action:
Supply label for branching on IF or GOTO.

CACR532E

LABEL NAME EXCEEDS 8 CHARS - IGNORED

Reason:
An invalid label name was detected. Label is ignored.

Action:
Correct label name problem and resubmit job.

Chapter 2: AFM - CA7R Messages 69

CACR Messages

CACR533E

LABEL "labelnam" WAS PREVIOUSLY DEFINED - IGNORED

Reason:
A label name has been doubly defined. Error message issued.

Action:
Correct problem and resubmit job.

CACR535E

OVER 255 LABELS DEFINED - REST IGNORED

Reason:
Over 255 label names are defined in a procedure. Any more specified in that procedure
are ignored. The remainder of statement labels are ignored.

Action:
Reduce the number of labels and resubmit job.

CACR536E

ABORT STATEMENT VALID ONLY IN PROCEDURE - IGNORED

FLUSH STATEMENT VALID ONLY IN PROCEDURE - IGNORED

Reason:
An ABORT or FLUSH statement was detected from the reader. The statement is ignored.
An error message is issued.

Action:
Remove the statement and resubmit the job.

CACR537E

NEST LIMIT HAS BEEN EXCEEDED

Reason:
The maximum nest limit specified at generation time has been exceeded. An error
message is issued. Any further nesting is suppressed.

Action:
Increase the nest limit specified at CA Driver generation.

70 Message Reference Guide

 CACR Messages

CACR538E

TOO FEW OPERANDS ON IF STATEMENT

Reason:
An IF statement is missing operands or a valid relational operator. Error message issued.

Action:
Correct IF statement and resubmit job.

CACR539E

SECOND OPERAND MUST BE POSITIVE NUMERIC

Reason:
A conditional statement with a length attribute specified is being tested against a
non-numeric or negative value. Error message issued.

Action:
Correct the statement and resubmit job.

CACR540E

FORMAT ERROR ON IF STATEMENT

Reason:
A syntax error made it impossible for CA Driver to interpret statement. An error
message is issued.

Action:
Check the format of the statement.

CACR541E

INVALID OPERATION FIELD: xxx

Reason:
An invalid relational operator detected in an IF statement. Error message issued; IF
statement bypassed.

Action:
Correct to a valid relational operator.

Chapter 2: AFM - CA7R Messages 71

CACR Messages

CACR546E

NUMBER ATTRIBUTE ONLY VALID FOR ARRAYS

Reason:
The number attribute was requested for a nonarray variable. Error message issued.

Action:
Correct the statement and resubmit the job.

CACR549E

UNPAIRED DELIMITERS IN LITERAL EXPRESSION

Reason:
A character expression was being defined and the second delimiter was not detected by
CA Driver. Skips to next valid expression; expansion continues.

Action:
Correct statement and resubmit job.

CACR553E

PARM NAME LENGTH ERROR - NAME="varname"

Reason:
A variable name "varname" with over seven characters was detected. Error message
issued; name truncated.

Action:
Correct statement and resubmit job.

CACR554E

xxxxxxx IS NOT NUMERIC

Reason:
The specified field was expected to contain numeric data and did not. Error message
issued.

Action:
Check format of statement. Correct error and resubmit job.

72 Message Reference Guide

 CACR Messages

CACR555E

UNPAIRED PARENTHESES IN VARIABLE EXPRESSION

Reason:
A substring or array reference has not been closed with a right parenthesis. Error
message issued. Skip to next valid expression.

Action:
Correct statement and resubmit job.

CACR556E

NON-NUMERIC DISPLACEMENT IN SUBFIELD REFERENCE

Reason:
A subfield reference displacement has non-numeric data. Error message issued. Skip to
next valid expression.

Action:
Check subfield reference and correct.

CACR557E

NON-NUMERIC LENGTH IN SUBFIELD REFERENCE

Reason:
A subfield length reference has non-numeric data. Error message issued. Skip to next
valid expression.

Action:
Check subfield reference and correct.

CACR558E

INVALID DISPLACEMENT IN SUBFIELD REFERENCE

Reason:
Displacement of subfield exceeds the maximum length of a literal. Error message issued.

Action:
Check value assigned to variable. Correct statement and resubmit job.

Chapter 2: AFM - CA7R Messages 73

CACR Messages

CACR559E

INVALID LENGTH IN SUBFIELD REFERENCE

Reason:
Length of subfield exceeds maximum length of a literal. Error message issued.

Action:
Check value assigned to variable. Correct statement and resubmit job.

CACR560E

INVALID SUBFIELD REFERENCE IN EXPRESSION

Reason:
Subfield reference is outside the range of the value assigned to the variable. Error
message issued.

Action:
Check value assigned to variable. Correct statement and resubmit job.

CACR561E

NON-NUMERIC SUBSCRIPT VALUE

Reason:
A non-numeric subscript was detected. Error message issued.

Action:
Correct subscript and resubmit job.

CACR562E

SUBSCRIPT OUT OF RANGE - 1 ASSUMED

Reason:
A subscript was specified that is greater than what was defined in DPROC statement.
Error message issued.

Action:
Check DPROC statement and refer to array that has been previously defined.

74 Message Reference Guide

 CACR Messages

CACR563E

ARRAY ENTRY REFERENCED IS UNDEFINED

Reason:
An array member was referenced that has no assigned or default value. Error message
issued. Value not substituted.

Action:
Check EXEC statement that is used to expand procedure. Make sure entry has an
assigned value previous to reference.

CACR564E

VARIABLE NOT ARRAY ELEMENT - SUBSCRIPT IGNORED

Reason:
A subscript was used to refer to a variable that is not defined as an array. Error message
issued.

Action:
Check definition of variable in DPROC statement. Correct statement and resubmit job.

CACR565E

"varnam" HAS NO VALUE CLAUSE - VARIABLE NOT DEFINED

Reason:
A variable without a value clause was detected on an EXEC statement. Error message
issued.

Action:
Correct statement and resubmit job.

CACR566E

"varname" HAS NO ASSIGNED OR DEFAULT VALUE

Reason:
A variable was referenced that has no assigned or default value. Error message issued.

Action:
Correct statement and resubmit job.

Chapter 2: AFM - CA7R Messages 75

CACR Messages

CACR567E

ZERO LENGTH CHARACTER STRING - IGNORED

Reason:
Two commas in a row were detected by parser. Error message issued.

Action:
Correct error and resubmit job.

CACR568E

UNBALANCED DELIMITERS - IGNORED

Reason:
A character expression definition is not closed with a corresponding delimiter. Error
message issued.

Action:
Correct statement and resubmit job.

CACR569E

MORE THAN 64 VARIABLES GIVEN - NO MORE ACCEPTED

Reason:
A DPROC statement has definitions for more than 64 variables. Error message issued;
further definitions bypassed.

Action:
Correct DPROC statement and recatalog procedure.

CACR570E

NUMBER OF ARRAY VALUES EXCEED ARRAY DIM - NO MORE ACCEPTED

Reason:
More values than there are array members have been entered on a DPROC statement.
Error message issued.

Action:
Correct DPROC statement and recatalog procedure.

76 Message Reference Guide

 CACR Messages

CACR571E

COMMA MUST SEPARATE ARRAY VALUES

Reason:
An invalid delimiter was detected in an array definition in a DPROC or EXEC statement.
Error message issued.

Action:
Correct statement and resubmit job.

CACR572E

RIGHT PARENTHESIS DOES NOT CLOSE DIMENSION SPECIFICATION

Reason:
An array dimension is not enclosed in parentheses. Error message issued.

Action:
Correct dimension specification and recatalog procedure.

CACR573E

ARRAY DIMENSION IS GREATER THAN 64

Reason:
An array was defined with greater than 64 members. Error message issued; variable not
defined.

Action:
Correct DPROC statement and recatalog procedure.

CACR574E

"varnam" IS NOT ALPHANUMERIC

Reason:
A variable name containing nonalphanumeric characters was detected. An error
message issued. The variable is bypassed.

Action:
Correct the variable name and recatalog the procedure.

Chapter 2: AFM - CA7R Messages 77

CACR Messages

CACR575E

ARRAY DIMENSION IS INVALID OR GIVEN AS ZERO

Reason:
A non-numeric or zero dimension was detected in an array definition on a DPROC
statement. An error message is issued. The variable is not defined.

Action:
Correct the dimension and recatalog the procedure.

CACR576E

"varnam" IS NOT AN ARRAY VARIABLE

Reason:
An array definition was used to assign values to a nonarray variable. An error message is
issued. The value is not assigned.

Action:
Correct the statement and resubmit the job.

CACR577E

"varnam" HAS BEEN PREVIOUSLY DEFINED - IGNORED

Reason:
A variable is defined twice on a DPROC statement. An error message is issued. The
second definition is ignored.

Action:
Correct the DPROC statement and recatalog the procedure.

CACR578E

"varnam" WAS NOT PREVIOUSLY DEFINED - IGNORED

Reason:
A variable is referred to in an EXEC statement that was not previously defined in a
DPROC. Error message issued.

Action:
Correct procedure and resubmit job.

78 Message Reference Guide

 CACR Messages

CACR579E

PARM VALUE LENGTH EXCEEDS 64 - TRUNCATED

Reason:
The value clause in an EXEC or DPROC statement exceeds 64 characters in length. An
error message is issued. The value is truncated.

Action:
Correct the statement and resubmit the job.

CACR580E

SYNTAX ERROR DETECTED IN SCAN

Reason:
The EXEC or DPROC statement does not adhere to syntax rules for those statements.
Error message issued.

Action:
Correct statement and resubmit job.

CACR581E

SUBFIELDS IN ARRAY DEF NOT TERMINATED

Reason:
An array definition is not terminated with a closing parenthesis. An error message is
issued. The variable is not defined.

Action:
Check the array definition. Correct the statement and recatalog the procedure.

CACR582E

BAD EXEC FIELD: xxxxxxxxxxxxxxx

Reason:
An unidentifiable string has been detected in scanning an EXEC statement. An error
message is issued. Processing skips to the next valid field.

Action:
Correct the statement and resubmit the job.

Chapter 2: AFM - CA7R Messages 79

CACR Messages

CACR583E

FIRST CHAR OF PARM MUST BE ALPHABETIC

Reason:
A variable name with a numeric first character detected. An error message is issued. The
variable is not defined.

Action:
Change variable name to conform to coding rules.

CACR584E

SET STATEMENT FORMAT ERROR

Reason:
A syntax error was detected in scanning a SET statement. An error message is issued.
The statement is ignored.

Action:
Correct the statement and resubmit the job.

CACR585E

DIVISION BY ZERO IN SET

Reason:
An attempt was made to divide by zero in a set expression. An error message is issued.
The value is not SET.

Action:
Ensure that divisor is a nonzero number or a literal.

CACR586E

RESULT OF MATHEMATICAL EXPRESSION INVALID

Reason:
A result of over 65535 or less than -65535 was the result of a numeric expression. Error
message issued; value not assigned.

Action:
Correct statement and resubmit job.

80 Message Reference Guide

 CACR Messages

CACR587E

"varnam" IS A RESERVED VARIABLE

Reason:
A reserved variable (&DATE, &TIME, and so forth) was used for a variable name in an
EXEC or DPROC statement. Error message issued.

Action:
Change variable name and resubmit job.

CACR588E

NESTED PROC="procnam",NOT FOUND

Reason:
The requested "procnam" was not found in the CA Driver procedure library. Error
message issued.

Action:
Catalog the requested procedure.

CACR589E

VALID TYPE ATTRIBUTES ARE C,N,M, AND O

Reason:
A type attribute test in an IF statement was invalid. The valid attribute types are C, N, M,
and O.

Action:
Fix the attribute test and resubmit.

CACR590E

LABEL "label" IS NOT DEFINED

Reason:
A GOTO or IF statement detected a branch to a label not defined in that procedure.
Error message issued.

Action:
Make sure label is defined in procedure.

Chapter 2: AFM - CA7R Messages 81

CACR Messages

CACR591E

NO LABEL SPECIFIED IN STEP STATEMENT

Reason:
A step statement was found without a label identifier. Error message issued.

Action:
Place STEP label in position 3 of STEP statement.

CACR593E

ERROR WHILE LOAD/DELETE

Reason:
CA Workload Automation SE was not able to load or delete a module. Issued by
CA7SRVCB.

Action:
For assistance, contact CA Support at ca.com/support.

CACR594E

INVALID //*DVR COMMAND

Reason:
CA Workload Automation SE found a //*DVR command that could not be processed.
Issued by CA7ISTIB.

Action:
For assistance, contact CA Support at ca.com/support.

CACR999E

CA-DRIVER/OS ABNORMAL TERMINATION

Reason:
CA Driver has abended. CA Driver is deactivated.

Action:
Perform the following actions:
■ Gather the details of the problem.
■ For assistance, contact CA Support at http://ca.com/support.

82 Message Reference Guide

 CAL2 Messages

CAL2 Messages
This section contains the CAL messages.

CAL2A001E:

CA-7 Session Not initialized. CA-7 signon failed.

Reason:
The CA Workload Automation SE API interface was unable to establish an online session
with CA Workload Automation SE. The API attempted to sign on to CA Workload
Automation SE with the current user ID, but the signon was rejected.

Action:
Ensure your TSO user ID is defined as a valid user ID to CA Workload Automation SE.

CAL2A002E:

CA-7 Session Not initialized. VTAM connection failed.

Reason:
The CA Workload Automation SE API interface was unable to establish an online session
with CA Workload Automation SE. The API attempted to establish a VTAM interface with
CA Workload Automation SE but was unable to do so.

Action:
Ensure the CA7APPL= parameter in member CACCENV of your 'userid.VPOINT.PROFILE'
specifies the correct VTAM applid of the CA Workload Automation SE with which you
want to communicate. Also, ensure the CA7SESS= parameter specifies a valid ACB name
and that the ACBs are active. Check the system log messages for WTOs issued for your
TSO address space that may contain additional diagnostic information. For more
information, see the Diagnostics section of the Installation Guide.

Chapter 2: AFM - CA7R Messages 83

CAL2 Messages

CAL2A003E:

CA-7 Session Not initialized. Unknown init failure.

Reason:
The CA Workload Automation SE API interface was unable to establish an online session
with CA Workload Automation SE.

Action:
Check the system log messages for WTOs issued for your TSO address space that may
contain additional diagnostic information. For more information, see the Diagnostics
section of the Installation Guide.

CAL2A004I:

Please reissue request. CA-7 session reconnected.

Reason:
The API interface with CA Workload Automation SE was lost (probably because of a
timeout condition). The API has reestablished the connection.

Action:
Reissue the request that caused the message. The new request should be processed
normally.

CAL2A009E:

API Data validation error. Unable to process request.

Reason:
The CA Workload Automation SE API interface was unable to properly interpret the
information passed from the CA Workload Automation SE Address Space. The current
request has not been satisfied.

Action:
For assistance, contact CA Support at ca.com/support. Be prepared to describe the
exact sequence of events that led up to the above message.

84 Message Reference Guide

 CAL2 Messages

CAL2A011E:

DSNBR not allowed for add function.

Reason:
You are not allowed to specify a DSNBR when adding a data set. The DSNBR will be
assigned by CA Workload Automation SE when a successful add is completed.

Action:
Ensure the DSNBR field is empty when attempting an ADD function.

CAL2A012E:

Jobname or CA-7 Job number required.

Reason:
Restart request was made without specifying either the job name or CA 7 WA job
number.

Action:
Ensure that the job name or CA 7 WA job number (or both) are specified when
requesting a restart.

CAL2A013E:

Specify either jobname, or, job number.

Reason:
An Add Requirement request was made without specifying either a job name or CA 7
WA job number.

Action:
Ensure that the job name or CA 7 WA job number (or both) are specified when making
the request.

Chapter 2: AFM - CA7R Messages 85

CAL2 Messages

CAL2A014E:

Specify either dependent job, or, user requirement.

Reason:
An Add Requirement request was made without specifying either the dependent job
name or user requirement to be added.

Action:
Ensure that the dependent job name or user requirement is specified when making the
request.

CAL2A015E:

Action is required (ADD or SUB).

Reason:
An Adjust Schedule request was made without specifying whether to add to or subtract
from the due-out times for jobs/networks.

Action:
Specify either ADD (to add time to schedules) or SUB (to subtract times from schedules)
when making the request.

CAL2A016E:

Adjustment time is required.

Reason:
An Adjust Schedule request was made without specifying the number of minutes to be
added/subtracted from due-out times.

Action:
Specify the number of minutes to be used to adjust due-out times when making the
request.

86 Message Reference Guide

 CAL2 Messages

CAL2A017E:

Specify either Job criteria, or, Network Reference number.

Reason:
An Adjust Schedule request was made specifying both a CA 7 WA job number and a
network reference number.

Action:
Specify only the CA 7 WA job number (or ALL or ALLP) or the network reference number
when making the request. If you want to effect both, issue them as two separate
requests.

CAL2A018E:

Either Job, or, Reference number must be specified.

Reason:
An Adjust Schedule request was made without specifying either a CA 7 WA job number
or a network reference number.

Action:
Specify the CA 7 WA job number (or ALL or ALLP), or the network reference number
when making the request.

CAL2A019E:

Only one criteria can be specified at a time.

Reason:
A Hold Queues request was made with multiple selection criteria.

Action:
Specify only one of the selection criteria (job name, CA 7 WA job number, queue, or
network reference number) when making the request.

Chapter 2: AFM - CA7R Messages 87

CAL2 Messages

CAL2A020E:

No criteria supplied. No action taken.

Reason:
A Hold Queues request was made without specifying any selection criteria.

Action:
Specify one of the selection criteria (job name, CA 7 WA job number, queue, or network
reference number) when making the request.

CAL2A021E:

Invalid Queue type. Must be omitted or REQ, RDY or ACT.

Reason:
A List Queues request was made specifying an invalid queue type.

Action:
Leave the queue type blank (defaults to all queues) or specify REQ, RDY, or ACT when
making the request.

CAL2A022E:

Specified requirement not found.

Reason:
A request was made to post or unpost a job predecessor (requirement); however, the
specified predecessor could not be found.

Action:
One possible reason is that when the last requirement for a job is posted, you can no
longer list the predecessors. Reissue the VIEW command to reselect the job
predecessors to confirm whether there are still any outstanding predecessors. If there
are, but they cannot be posted, contact CA Support at ca.com/support for assistance.

88 Message Reference Guide

 CAL2 Messages

CAL2A023E:

Target task not found. Unable to process.

Reason:
A request was made to update an input or output network task in the preprocess or
postprocess queue; however, the specified network task could not be found.

Action:
One possible reason is that the task has already been satisfied. Reissue the VIEW
command to reselect the network tasks to confirm whether the task is still active. If it is,
but it cannot be updated, contact CA Support at ca.com/support for assistance.

CAL2A024E:

Missing or invalid action. Should be PRMP or NOPRMP.

Reason:
A request was made from the Queue Prompting Control panel; however, the action
code was missing or invalid.

Action:
This window can either initiate prompting (action=PRMP) or suspend prompting
(action=NOPRMP). Specify the wanted action and reissue the request.

CAL2A025E:

Specify either Job, or, Reference criteria.

Reason:
A request was made from the Queue Prompting Control panel; however, both job
number and network reference numbers were specified.

Action:
For a single request only one of these criteria may be specified. Reissue the request
specifying only one target (job number or network reference number).

Chapter 2: AFM - CA7R Messages 89

CAL2 Messages

CAL2A026E:

Neither Job nor Reference criteria specified.

Reason:
A request was made from the Queue Prompting Control panel; however, neither a job
number or a network reference number was specified.

Action:
For a single request only one of these criteria may be specified. Reissue the request
specifying only one target (either job number or network reference number).

CAL2A027E:

Only one criteria can be specified at a time.

Reason:
A request was made from the Release Queues panel; however, multiple selection
criteria were specified.

Action:
For a single request only one of these criteria may be specified. Reissue the request
specifying only one target (job name, job number, queue type, or network reference
number).

CAL2A028E:

No criteria supplied. No action taken.

Reason:
A request was made from the Release Queues panel; however, no selection criteria was
specified.

Action:
Reissue the request specifying target criteria (job name, job number, queue type, or
network reference number).

90 Message Reference Guide

 CAL2 Messages

CAL2A029E:

Invalid or missing action. Must be START or STOP.

Reason:
A request was made from the Queue Control panel; however, the action code was
missing or invalid.

Action:
This window is used to start (action=START) or stop (action=STOP) the queues. Specify
the wanted action and reissue the request.

CAL2A030E:

Invalid queue type. Must be ALL, REQ or RDY.

Reason:
A request was made from the Queue Control panel; however, the queue type was
missing or invalid. You can start/stop all of the queues (ALL), or only the request queue
(REQ) or only the ready queue (RDY).

Action:
Specify the queues that you want and reissue the request.

CAL2A031E:

API function error. IFUNC not VIEW or UPD.

Reason:
Internal error in the communication between the ViewPoint system and the CA
Workload Automation SE/API interface.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 91

CAL2 Messages

CAL2A032E:

Editor commands not allowed in command window.

Reason:
A CA Workload Automation SE editor command was entered in the CA Workload
Automation SE Command window.

Action:
Editor commands are not allowed in the CA Workload Automation SE Command
window. Use native CA Workload Automation SE or the CA Workload Automation
SE/ISPF interface to perform these functions.

CAL2A033E:

Job has no JCL attached.

Reason:
The CA Workload Automation SE Restart window was entered for a job that has no JCL.

Action:
Jobs without JCL cannot be submitted for restart.

CAL2A034I:

Job does not have a defined schedule

Reason:
A View function was performed to list the schedules for a job that has no schedules
defined.

Action:
If you want to define a schedule for the job, enter the job name and perform an add
function (edit/add).

CAL2A035I:

Schedule ID added

Reason:
The schedule ID entered has been added for the specified job.

Action:
None.

92 Message Reference Guide

 CAL2 Messages

CAL2A036E:

SCAL value MUST be supplied

Reason:
An attempt was made to add a job schedule without supplying a calendar (SCAL).

Action:
Specify the last two characters of the wanted calendar to be used for this schedule. See
the Database Maintenance Guide for more information about calendars.

CAL2A037I:

Schedule ID updated

Reason:
The schedule ID has been updated for the specified job.

Action:
None.

CAL2A038I:

Last schedule ID for this job deleted

Reason:
The schedule ID just deleted was the last one defined for this job.

Action:
None.

CAL2A039I:

Schedule ID deleted

Reason:
The schedule ID has been deleted as requested.

Action:
None.

Chapter 2: AFM - CA7R Messages 93

CAL2 Messages

CAL2A040E:

NETWORK DOES NOT HAVE A DEFINED SCHEDULE

Reason:
A View function was performed to list the schedules for an input network that has no
schedules defined.

Action:
If you want to define a schedule for the network, enter the network name and perform
an add function (edit/add).

CAL2A041E:

NETWORK NOT DEFINED AS INPUT NETWORK

Reason:
A View function was performed to list the schedules for a network that is not defined as
an input network.

Action:
Use the Output Network Scheduling window (PL2DB23) to maintain schedules for
output networks.

CAL2A042I:

Schedule ID deleted.

Reason:
The schedule ID has been deleted for the specified network.

Action:
None.

CAL2A043I:

Schedule ID added.

Reason:
The schedule ID has been added for the specified network.

Action:
None.

94 Message Reference Guide

 CAL2 Messages

CAL2A044E:

SCAL value must be supplied.

Reason:
An attempt was made to add a network schedule without supplying a calendar (SCAL).

Action:
Specify the last two characters of the wanted calendar to be used for this schedule. See
the Database Maintenance Guide for more information about calendars.

CAL2A045I:

Schedule ID updated.

Reason:
The schedule ID has been updated for the specified network.

Action:
None.

CAL2A046I:

Last schedule Id for this network deleted.

Reason:
The schedule ID just deleted was the last one defined for this network.

Action:
None.

CAL2A047E:

Network does not have any defined schedules.

Reason:
A View function was performed to list the schedules for an input network that has no
schedules defined.

Action:
If you want to define a schedule for the network, enter the network name and perform
an add function (edit/add).

Chapter 2: AFM - CA7R Messages 95

CAL2 Messages

CAL2A048E:

Network not defined as Output Network.

Reason:
A View function was performed to list the schedules for a network that is not defined as
an output network.

Action:
Use the Input Network Scheduling window (PL2DB22) to maintain schedules for input
networks.

CAL2A049I:

Schedule ID added.

Reason:
The schedule ID has been added for the specified network.

Action:
None.

CAL2A050E:

SCAL value must be supplied.

Reason:
An attempt was made to add a network schedule without supplying a calendar (SCAL).
Note: For more information about calendars, see the Database Maintenance Guide.

Action:
Specify the last two characters of the calendar that you want to use for this schedule.

CAL2A051I:

Schedule ID updated.

Reason:
The schedule ID has been updated for the specified network.

Action:
None.

96 Message Reference Guide

 CAL2 Messages

CAL2A052I:

Last schedule ID for this network deleted.

Reason:
The schedule ID just deleted was the last one defined for this network.

Action:
None.

CAL2A053I:

Schedule ID deleted.

Reason:
The schedule ID has been deleted for the specified network.

Action:
None.

CAL2A054I:

Verify transaction successful.

Reason:
The VERIFY transaction was completed without error.

Action:
None.

CAL2A055I:

JCLOVRD transaction successful.

Reason:
The JCL Override (JCLOVRD) transaction was completed without error.

Action:
None.

Chapter 2: AFM - CA7R Messages 97

CAL2 Messages

CAL2A056W:

Specified job not found in expected queue.

Reason:
The job selected for action from the PL2QM1 panel was not found in the selected CA
Workload Automation SE Queue. The job has probably moved to another queue. The
requested action was not attempted.

Action:
Return to the PL2QM1 panel and reissue the view request to determine whether this
job has changed queues. If you still want to perform an action on it, select it to transfer
to the PL2QM1B panel and reissue the action request.

CAL2A057E:

Unidentified internal function. No action taken.

Reason:
Internal error. Function code passed to the CA Workload Automation SE/API system was
not recognized by the API table processing module.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A058W:

Verify and Hold requirements cannot be unposted.

Reason:
Once a VERIFY or HOLD requirement has been posted, it cannot be unposted.

Action:
None.

98 Message Reference Guide

 CAL2 Messages

CAL2A059I:

Job has no unsatisfied predecessors.

Reason:
Request was issued with List ALL? = N (no). The job was found in the request queue but
there were no outstanding job predecessors.

Action:
None.

CAL2A060E:

Unique Job name or Number is required for CANCEL.

Reason:
A Cancel request was issued from the PL2QM1C panel without a CA 7 WA job number.
The job number is required for cancel.

Action:
Reissue the request with the correct CA Workload Automation SE Job Number for the
job to be canceled.

CAL2A061E:

Calendar Year and Calendar ID are required.

Reason:
A request to delete a CA Workload Automation SE base calendar was issued without
specifying both the year and ID of the calendar.

Action:
Reissue the request with both the year and ID of the Calendar to be deleted.

CAL2A062E:

Calendar ID is required.

Reason:
A request to act on a CA Workload Automation SE base calendar was issued without
specifying the name of the calendar.

Action:
Reissue the request with the name of the calendar to be acted upon.

Chapter 2: AFM - CA7R Messages 99

CAL2 Messages

CAL2A063E:

Jobtype is required.

Reason:
A request was made to act upon a job or network; however, the type was not specified.

Action:
Reissue the request with the correct job type (CPU, PRECPU, or POSTCPU).

CAL2A064E:

Jobtype is invalid.

Reason:
A request was made to act upon a job or network; however, the job type specified is
invalid.

Action:
Reissue the request with the correct job type (CPU, PRECPU, or POSTCPU).

CAL2A065E:

Your level of CA-7 does not support new calendar structure.

Reason:
A request was made to act upon a CA Workload Automation SE base calendar; however,
your level of CA Workload Automation SE does not support the new calendar update
features.

Action:
Confirm you are connected to the correct copy of CA Workload Automation SE. If so,
contact CA Support at ca.com/support for assistance.

100 Message Reference Guide

 CAL2 Messages

CAL2A067E:

SYSTEM is required.

Reason:
A request was made from the PL2DB46 panel (System documentation); however, no CA
Workload Automation SE System name was specified.

Action:
Reissue the request with the CA Workload Automation SE System name whose Prose
you want to edit.

CAL2A068W:

Reason:
A request was made for CA Workload Automation SE Prose; however, the requested
documentation was not found in the CA Workload Automation SE database.

Action:
Confirm you are specifying the correct information for the type of Prose you want to
access. If the Prose is not defined, you may create it by using the Edit/Edit function.

CAL2A069E:

Member and JCLID are required for Delete

Reason:
A request was made from the PL2DB7 panel to delete a job's JCL; however, the JCLID for
the JCL was not specified.

Action:
Reissue the request with the correct JCLID for the PDS that holds the job's JCL.

CAL2A070E:

Resource name missing or invalid.

Reason:
A request was made from one of the CA Workload Automation SE Virtual Resource
Management panels; however, the resource name was either not specified, or was
invalid.

Action:
Reissue the request with the correct VRM resource name.

Chapter 2: AFM - CA7R Messages 101

CAL2 Messages

CAL2A071W:

JCLID is required to create new members.

Reason:
A request was made from the PL2DB7 panel to create a new JCL member; however, the
JCLID for the JCL was not specified.

Action:
Reissue the request with the correct JCLID for the PDS that will hold the new member.

CAL2A071W:

Duplicate Jobnames in the Queue. No action taken.

Reason:
A request was received to act on a job in the CA Workload Automation SE queues. A job
name was specified, but no CA 7 WA job number. There are multiple occurrences of the
same job name in the queue. No action was taken since the request is ambiguous.

Action:
Use another path where you can select the exact job (with job number) that you want to
update.

CAL2A072W:

Duplicate Jobnames in the queue. No actions available.

Reason:
Control was transferred to the PL2QM1B panel with a job name, but no CA 7 WA job
number. There are multiple occurrences of that job name in the same CA Workload
Automation SE queue.

Action:
Requests to act upon that job on the PL2QM1B panel will be ignored. Use another path
to PL2QM1B where you can select the exact job you want to update.

102 Message Reference Guide

 CAL2 Messages

CAL2A073E:

CA-7 Job Number is required for this function.

Reason:
A request was made on the PL2QM1B to update a job, but the job number was not
specified.

Action:
Requests to act upon that job on the PL2QM1B panel will be ignored. Use another path
to PL2QM1B where you can select the exact job you want to update.

CAL2A075I:

Edit session has been cancelled.

Reason:
A CA Workload Automation SE API Edit session has been canceled without updating the
original text. This message is normal if no changes are made to the text, or, the user
explicitly chooses to cancel changes made during the edit session.

Action:
If you intended to save the changes, ensure you are saving the data before leaving the
text-edit session. Also ensure that you select the 'OK' option when prompted for save
confirmation.

CAL2A076E:

JOBNAME is required.

Reason:
A request was made for Job Prose, but the job name was not specified on the request.

Action:
Reissue the request providing the proper job name.

Chapter 2: AFM - CA7R Messages 103

CAL2 Messages

CAL2A077E:

NETWORK is required.

Reason:
A request was made for Network Prose, but the network was not specified on the
request.

Action:
Reissue the request providing the proper network.

CAL2A078E:

USERNAME is required.

Reason:
A request was made for User Prose, but the user identifier was not specified on the
request.

Action:
Reissue the request providing the proper user identifier.

CAL2A079E:

DSN is required.

Reason:
A request was made for Data Set Prose, but the data set name was not specified on the
request.

Action:
Reissue the request providing the proper data set name.

CAL2A080E:

JOBNAME, STEPNAME and DDNAME are required.

Reason:
A request was made for ddname Prose, but the job, step, or ddname were not specified
on the request.

Action:
Reissue the request providing all of the required columns.

104 Message Reference Guide

 CAL2 Messages

CAL2A081E:

Jobname is required.

Reason:
A request was made to act on a job definition in the CA Workload Automation SE
database. The job name was not specified on the request.

Action:
Reissue the request providing the job name.

CAL2A082I:

Submit Time has been turned off.

Reason:
A request was made to satisfy a Submit Time requirement for a job in the CA Workload
Automation SE request queue. Any outstanding Submit Time requirement for the job
has been satisfied.

Action:
No action required.

CAL2A083E:

Your level of CA-7 does not support this feature.

Reason:
A request was made to a CA Workload Automation SE/API table for information or
services that require a higher release of CA Workload Automation SE than what you are
currently executing.

Action:
If you have multiple copies of CA Workload Automation SE, confirm that you have
connected with the correct copy. If so, then you will need to upgrade to the current
release of CA Workload Automation SE to use the services you have requested.

Chapter 2: AFM - CA7R Messages 105

CAL2 Messages

CAL2A084E:

SAVE FAILED FOR xxxxxxxx : INVALID OR OMITTED JCLLIB DATA

Reason:
An invalid value was entered for JCLLIB.

Action:
Enter a valid JCLLIB value. Use /DISPLAY, ST=JCLVAR to find possible values.

CAL2A085E:

NAME OR JOBSET NAME OR MASK REQUIRED

Reason:
A request was made for a list of CA 7 WA jobs for JOBFLOW. However, no JOBSET (CA
Workload Automation SE system name) or JOBNAME argument was supplied.

Action:
Specify a search argument for JOBNAME, JOBSET or both.

CAL2A086E:

Too much data for single call. Please qualify request.

Reason:
A request was made to a CA Workload Automation SE/API table that caused an overflow
condition in the CA Workload Automation SE output. No data is returned to the caller.

Action:
Reissue the request with more specific search criteria.

CAL2A087E:

Job number found, but Job Name does not match request.

Reason:
The request included the job number, but the job name does not match the job number.

Action:
Verify the job number is correct and reenter the command.

106 Message Reference Guide

 CAL2 Messages

CAL2A088E:

FLOW_ID REQUIRED FOR DELETE

Reason:
Internal error. A call was made to the CA Workload Automation SE/API to delete a
JOBFLOW from the API structure. However, a flow-ID was not sent with the request.

Action:
Contact your installation specialist for assistance.

CAL2A089E:

ID/NAME/SCHID/DUPID REQUIRED FOR DELETE

Reason:
Internal error. A call was made to the CA Workload Automation SE/API to delete a
JOBFLOW element from the API structure. However, all of the information needed to
identify the element was not sent with the request.

Action:
Contact your installation specialist for assistance.

CAL2A090E:

INVALID PR_VIEW_TYPE

Reason:
Internal error. A call was made to the CA Workload Automation SE/API to build/update
a JOBFLOW in the API structure. However, the JOBFLOW type was not specified or was
invalid.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 107

CAL2 Messages

CAL2A091E:

INVALID DELETE TYPE REQUESTED

Reason:
Internal error. A call was made to the CA Workload Automation SE/API to delete
something from a JOBFLOW in the API structure. However, the type of delete was not
specified or was invalid.

Action:
Contact your installation specialist for assistance.

CAL2A094E:

TARGET_NODE and TARGET_SUBFILE are required.

Reason:
A request was made to act on an entry in the CA Workload Automation SE database.
Either the target node or the target subfile was not specified on the request. Issued by
TL2VXJOB.

Action:
Reissue the request providing the target node and target subfile.

CAL2A095E:

Year cannot be changed for calendars beginning with SCAL.

Reason:
An attempt was made to change the year for a calendar named SCALyyxx, where yy is
the last two digits of the year it represents and xx is a uniquely-identifying suffix.
Because the year is in the name of the calendar, the calendar's year cannot be changed.
Issued by TL2VCAL2.

Action:
If you want to create a calendar for a different year, use the ADD function of the DB.2.8
panel.

108 Message Reference Guide

 CAL2 Messages

CAL2A096E:

Disaster Recovery not supported by your release of CA-7

Reason:
An attempt was made to enter a disaster recovery class (DRCLASS) on a panel. Only CA
Workload Automation SE r11 and higher support the DRCLASS field. Issued by TL2DB1.

Action:
Clear the DRCLASS field and reenter the panel. If your site is running CA Workload
Automation SE r11 or higher, contact CA Support at ca.com/support for assistance.

CAL2A098E

Jobflow Illustrator requires CA 7 CCI Terminal Support.

Reason:
No CAICCI terminals are defined in the initialization file.

Action:
Add at least one CAICCI terminal to the initialization file.

CAL2A099E:

INVALID L2WKFLAG VALUE.

Reason:
Internal error. A flag used within the CA Workload Automation SE/API to build/update
JOBFLOW structures contained an invalid value.

Action:
Contact your installation specialist for assistance.

CAL2A104E:

No AFM criteria supplied. No action taken.

Reason:
A Pass-Thru AFM request did not include the AFM criteria.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 109

CAL2 Messages

CAL2A105E:

No AGENT supplied. No action taken.

Reason:
A Pass-Thru AFM request did not include the AGENT value.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A501E

NO xxxxxxxx VALUE SUPPLIED.

Reason:
The value supplied for a program parameter keyword is invalid. Default values are
supplied for these parameters in 'userid.VPOINT.PROFILE(CACCENV)'.

Action:
Correct the parameter values CA7APPL= and CA7SESS= and reexecute.

CAL2A502E

xxxxxxxx FAILED, R15 = nnnnnnnnn

Reason:
The VTAM macro named at xxxxxxxx failed. For more information, see IBM manual z/OS
Communications Server: SNA Programming.

Action:
If the error persists, contact your installation specialist for assistance.

CAL2A503E

INVALID ENTRY CODE, R1=nnnnnnnn.

Reason:
This is an internal error.

Action:
The error may be transient. Attempt to reexecute the CA Workload Automation SE API.
If the error persists, save all ISPF log and list output. Also collect any dumps that may
have been produced and contact your installation specialist for assistance.

110 Message Reference Guide

 CAL2 Messages

CAL2A504E

INVALID RETURN CODE, R15=nnnnnnnn.

Reason:
This is an internal error.

Action:
The error may be transient. Attempt to reexecute CA Workload Automation SE. If the
error persists, save all ISPF log and list output. Also collect any dumps that may have
been produced and contact your installation specialist for assistance.

CAL2A505E

SESSION TERMINATED DUE TO ERROR

Reason:
The CA Workload Automation SE terminal session under the CA Workload Automation
SE API has been terminated. The reasons for termination may be explained by previous
error messages.

Action:
See the previous error messages for information about the reason for termination. Take
the indicated action and attempt to execute the CA Workload Automation SE API again.
If the error persists, contact your installation specialist for assistance.

CAL2A506E

xxxxxxxx GENCB FAILED, R15 = nnnnnnnnn

Reason:
A GENCB macro failed for the VTAM control block named. R15 contains the return code
from the GENCB. For more information, see IBM manual z/OS Communications Server:
SNA Programming.

Action:
Specific information about the reason for the failure will be found in the
aforementioned publication. A common reason for a GENCB failure is an insufficient
region size for the CA Workload Automation SE API session. If the error persists, contact
your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 111

CAL2 Messages

CAL2A507E

SYNTAX ERROR PARSING ACB NAME FOR SESSION

Reason:
An error was encountered trying to parse the ACB name provided on the CA7SESS=
keyword in the CACCENV member of the Profile data set. For more information, see CA
Workload Automation SE/API Requirements in the Interface Reference Guide.

Action:
Make sure that the value supplied for the CA7SESS= parameter follows the format
XXXNNNN where it is the highest ACB defined to VTAM for CA Workload Automation SE
(for example, CA70010).

CAL2A508E

CONNECT ACB UNAVAILABLE OVER 10 SECONDS

Reason:
The ACB needed for the CA Workload Automation SE API session establishment could
not be OPENed during the time period allowed. The ACB used for session establishment
is the ACB name that ends with 0000. For more information about the definition of the
ACBs, see the Systems Programming Guide.

Note: A period of high activity could produce this message when many users are
attempting to establish CA Workload Automation SE terminal sessions under TSO-ISPF,
the CA Workload Automation SE API, or both.

Action:
If the message was produced during a period of high activity, simply wait a few minutes
and reexecute CA Workload Automation SE API. If an error condition seems possible
then attempt to activate the VTAM application where the ACBs are defined by issuing
the command:

v net,id=APPL,act

Replace APPL in this example with the name of the appropriate VTAM application. If this
fails, review the installation steps outlined in the Systems Programming Guide
pertaining to the definition of the VTAM ACBs for possible errors. If the error persists,
contact your installation specialist for assistance.

112 Message Reference Guide

 CAL2 Messages

CAL2A509E

xxxxxxxx ACB OPEN FAILED, ACBOFLGS = nnnnnnnn

Reason:
A VTAM OPEN macro failed for the ACB named by xxxxxxxx. The ACBOFLGS codes may
provide information as to the reason for the failure. For more information, see IBM
manual z/OS Communications Server: SNA Programming.

Action:
If the ACB named is the 0000 ACB, then this message will probably be accompanied by a
CAL2A508 message. In that event, see the recommended action for that message.
Otherwise, see the aforementioned IBM publication for information about the reasons
why VTAM failed the OPEN request. If the error persists, contact your installation
specialist for assistance.

CAL2A510E

RTNCD = xxxxxxxx, FDBK2 = yyyyyyyy

Reason:
This is an informational message that may be preceded by a message indicating an RPL
based VTAM macro failure. For information about the meaning of these codes, see IBM
manual z/OS Communications Server: SNA Programming.

Action:
None. See the action recommended for the message specific to the macro failure.

CAL2A511E

SESSION USER LIMIT REACHED, TRY AGAIN LATER

Reason:
All of the VTAM ACBs defined for use with the CA Workload Automation SE/TSO-ISPF
and CA Workload Automation SE API interface are currently in use by other ISPF or the
CA Workload Automation SE API sessions.

Action:
Wait a few minutes and try the interface again. If the problem persists, consider
increasing the number of VTAM ACBs.

Chapter 2: AFM - CA7R Messages 113

CAL2 Messages

CAL2A512E

xxxxxxxx TRANSLATION FAILED, R0 = nnnnnnnnn

Reason:
An error occurred during the attempt to evaluate an address. xxxxxxxx is the internal
function name and R0 contains the return code from the function routine.

Action:
Note the sequence of events that resulted in the failure. Collect all ISPF log and list
output from the time frame when the failure occurred. Contact your installation
specialist for assistance.

CAL2A513E

SCREEN TRANSLATION ERROR

Reason:
An error occurred during the attempt to build CA Workload Automation SE API output
for a CA Workload Automation SE panel. This message may be accompanied by others
that will give a reason for the error.

Action:
See the actions recommended for any accompanying messages.

CAL2A514E

ERROR DETECTED IN EDITOR

Reason:
An error occurred during an API edit session. This message may be accompanied by
others that will give a reason for the error.

Action:
See the actions recommended for any accompanying messages.

114 Message Reference Guide

 CAL2 Messages

CAL2A515E

xxxxxxxx FAILED, R0 = nnnnnnnnn

Reason:
The VTAM macro named at xxxxxxxx failed. For more information, see IBM manual z/OS
Communications Server: SNA Programming.

Action:
If the error persists, contact your installation specialist for assistance.

CAL2A516E

INVALID WRITE CONTROL CHARACTER - xx

Reason:
An invalid 3270 write control character was received from CA Workload Automation SE.
xx is the hex value of the character.

Action:
Because the problem is sometimes transient, reexecute the interface. If the problem
persists, contact your installation specialist for assistance.

CAL2A517E

INVALID 3270 DATASTREAM ORDER - xx

Reason:
An invalid 3270 datastream order character was received from CA Workload
Automation SE. xx is the hex value of the character.

Action:
Because the problem is sometimes transient, reexecute the interface. If the problem
persists, contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 115

CAL2 Messages

CAL2A518E

INVALID EDIT HEADER, EDIT SESSION TERMINATED

Reason:
Internal information needed to maintain Editor protocols between CA Workload
Automation SE and the API was missing or invalid.

Action:
If the CA Workload Automation SE API modules are accessed from a library other than
the CA Workload Automation SE production load library, then make sure that all of the
API modules are running at the same maintenance level as the CA Workload
Automation SE address space. If the problem persists, contact your installation specialist
for assistance.

CAL2A519E

UNABLE TO OPEN EDITOR WORK FILE

Reason:
The work file that was dynamically allocated for use in a CA Workload Automation SE
API edit session could not be opened.

Action:
This message may be accompanied by other messages. If so, see the actions
recommended for any accompanying messages. If there are no other messages, reenter
the edit session.

CAL2A520E

UNABLE TO COMPLETE VTAM CONNECTION WITH CA-7

Reason:
A VTAM REQSESS macro was issued to establish a session with CA Workload Automation
SE; however, no response from CA Workload Automation SE was received.

Action:
If CA Workload Automation SE was terminating during the attempt to connect to CA
Workload Automation SE from the CA Workload Automation SE API, you can ignore this
message. Reexecute the interface. If the condition persists, contact CA Support at
ca.com/support for assistance.

116 Message Reference Guide

 CAL2 Messages

CAL2A521E

NSEXIT CLEANUP REQUEST - LINK IS DOWN

Reason:
The VTAM link with CA Workload Automation SE is no longer active. There are several
possible explanations for this condition. For example, a VTAM command may have been
issued to inactivate the application, or CA Workload Automation SE may be down, or a
/CLOSE may have been issued to close the CA Workload Automation SE VTAM ACB. No
CA Workload Automation SE terminal sessions are available under the CA Workload
Automation SE API until the VTAM link is reestablished.

Action:
Determine the cause of the outage and reexecute the interface. If the error persists,
contact CA Support at ca.com/support for assistance.

CAL2A522E

NSPE RU RECEIVED - SESSION TERMINATED

Reason:
The NSEXIT exit was entered for a Network Services Procedure Error. For information
about the specific error conditions that might cause this condition, see IBM manual z/OS
Communications Server: SNA Programming.

Action:
Reexecute the interface. If the error persists and no VTAM problem is indicated, then
contact your installation specialist.

CAL2A523E

LOSTERM EXIT ENTERED - SESSION TERMINATED

Reason:
This exit may be entered under certain session outage conditions. For information about
the specific error conditions that might cause this condition, see IBM manual z/OS
Communications Server: SNA Programming.

Action:
Reexecute the interface. If the error persists and no VTAM problem is indicated, then
contact your installation specialist.

Chapter 2: AFM - CA7R Messages 117

CAL2 Messages

CAL2A524E

TPEND EXIT ENTERED - SESSION TERMINATED

Reason:
The TPEND exit was entered for this ACB. This exit may be entered in response to a
VTAM HALT command, or may be entered if VTAM terminates.

Action:
No CA Workload Automation SE session under CA Workload Automation SE API will be
available until the VTAM link between CA Workload Automation SE and the CA
Workload Automation SE API sessions is reestablished. If the error persists and no
problem can be detected in VTAM, then contact your installation specialist.

CAL2A525E

INVALID RESPONSE FROM CA-7 TO REQUEST FOR SLU ACBNAME

Reason:
A CA Workload Automation SE API session requested the assignment of an ACB name
for use in establishing a VTAM link. CA Workload Automation SE returned a response
not recognized by the requestor.

Action:
Review the following for possible error conditions:
■ Determine that the VTAM link is being attempted for the correct copy of CA
Workload Automation SE. Make sure that the ACB defined for that copy of CA
Workload Automation SE is named on the CA7APPL keyword in
'userid.VPOINT.PROFILE(CACCENV)'.
■ The value for the CA7SESS= keyword in 'userid.VPOINT.PROFILE(CACCENV)' must
match the VTAM ACF definitions.

Correct any parameter values that may be in error, and then reexecute the interface. If
the error persists, contact your installation specialist for assistance.

118 Message Reference Guide

 CAL2 Messages

CAL2A526E

SVC 99 ERROR, R15=xxxxxxxx, R0=xxxxxxxx

Reason:
An attempt to allocate an editor work file failed. The R15 and R0 values should indicate
the nature of the problem. For information about the return codes from dynamic
allocation, see the IBM manual z/OS MVS Programming: Authorized Assembler Services
Guide.

Action:
Correct the problem that prevented the successful dynamic allocation and reexecute
the interface.

CAL2A527E

CA-7 SCRGET DISP=FIRST FAILED. EDIT TERMINATED.

Reason:
CA Workload Automation SE encountered an error attempting to read Active Area data
for this terminal. The edit session is terminated.

Action:
If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2A530E

OPEN/CLOSE SUBTASK ENDED. TCBCMP= xxsssuuu

Reason:
The subtask that was created to handle OPEN and CLOSE requests for the VTAM ACBs
used for the CA Workload Automation SE terminal session ended. A nonzero TCBCMP
indicates an abnormal termination. In such a case, sss is the system abend code and uuu
is the user abend code.

Action:
Collect any dumps that may have been produced and contact CA Support at
ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 119

CAL2 Messages

CAL2A542E

ERROR OCCURRED IN SCIP EXIT

Reason:
The VTAM SCIP exit for this terminal session's ACB encountered an error.

Action:
Collect any console and dump information that may have been produced and contact
CA Support at ca.com/support for assistance.

CAL2A543E

VTAM LOGICAL ERROR EXIT ENTERED

Reason:
The VTAM LERAD exit for this terminal session's ACB was entered.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

CAL2A544E

VTAM SYNAD EXIT ENTERED

Reason:
The VTAM SYNAD exit for this terminal session's ACB was entered.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

120 Message Reference Guide

 CAL2 Messages

CAL2A546E

VTAM APPL FOR CA-7 NOT ACTIVE OR NOT ACCESSIBLE

Reason:
The VTAM APPL named on the CA7APPL= parameter in
'userid.VPOINT.PROFILE(CACCENV)' is not currently active or is not accessible in this
domain.

Action:
Make sure that the copy of CA Workload Automation SE associated with the VTAM APPL
named in the CA7APPL parameter is active and that the VTAM ACB is open. Make sure
that this APPL is accessible in the domain where the CA Workload Automation SE API
session is running.

CAL2A547E

CA-7 UNRESPONSIVE FOR 10 SECONDS, SESSION TERMINATED

Reason:
The CA Workload Automation SE API was invoked and timed out before CA Workload
Automation SE responded to the initialization calls.

Action:
Check the parameters in your API PROFILE data set, member CACCENV. Ensure that the
CA7APPL= keyword specifies the correct VTAM APPLid for the CA Workload Automation
SE you want to communicate with.

CAL2A548E

(aa bbb) xx...xx

Reason:
An error occurred when the CA Workload Automation SE API process attempted to log
on to a CA Workload Automation SE session. The prefix (aa bbbb) shows the module
name suffix and relative offset where the message was generated. The error message
returned from CA Workload Automation SE is shown in the body of this message
(xx...xx).

Action:
Perform the following actions:
■ Check the xx...xx error message.
■ Take the appropriate corrective actions.

Chapter 2: AFM - CA7R Messages 121

CAL2 Messages

CAL2A601E:

LAPI APIRB POINTER INVALID

Reason:
CA Workload Automation SE was unable to obtain or validate the API system request
block pointer (APIRB). Issued by L2SQL000.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A602E:

APIRB_SESSN_ANCHOR IS INVALID

Reason:
CA Workload Automation SE was unable to obtain or validate the request anchor. Issued
by L2SQL000.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A603E:

SQLCA POINTER IS INVALID

Reason:
CA Workload Automation SE was unable to obtain or validate the request control area
pointer (SQLCA). Issued by L2SQL000.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A605E

APIRB_SESSN_ANCHOR is zero.

Reason:
Internal error in the communication between the SQL interface online system and the
CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

122 Message Reference Guide

 CAL2 Messages

CAL2A610E

Table module does not begin with DESCRIBE.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A615E

(aa bbbb) BAD QSEQ - L2APIRB IS CLOSED. QUERY : cccccccc

Reason:
A validate call from an existing SQL Query request failed. aa is the caller's prefix. bbbb is
the offset into the table. cccccccc is the query type.

Action:
If this was during API startup, shut down the API server and make sure that the CA7APPL
points to the correct CA7SESS variable. Check to see if the major node defined for the
CA Workload Automation SE API session is active, and if not, activate it. If this was not
during startup, cancel the current request and retry your request. If the error persists,
contact your installation specialist for assistance.

CAL2A616E

(aa bbbb) L2APIRB ALLOCATION FAILED, R15=cccccccc

Reason:
An allocation request for the named API control block failed. R15 contains a
hexadecimal code that identifies the location within the API subroutine module.

Action:
This message more than likely followed the CAL2A615E message. Attempt to resolve the
prior message. If the errors persist, contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 123

CAL2 Messages

CAL2A618E

(xx yyyy) QUERY TYPE NOT SUPPORTED BY API TABLE : nnnnnnnnn

Reason:
A request is invalid for this panel.

Action:
Make sure that the latest maintenance is applied.

CAL2A620E

Unrecognized APIRB_QUERY_TYPE.

Reason:
Internal error in the communication between the SQL interface and the CA Workload
Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A630E

GETMAIN failure.

Reason:
The CA Workload Automation SE API interface was unable to acquire the storage
needed to satisfy the current request.

Action:
Increase your TSO region and retry the sequence of commands that led to the error.

CAL2A640E

Unrecognized verb in table module.

Reason:
Internal error in the communication between the SQL interface and the CA Workload
Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

124 Message Reference Guide

 CAL2 Messages

CAL2A650E

Conversion error from L2L10042 on xxxx at yyyy.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A660E

Unrecognized parm on xxxxx at yyyyy.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A670E

TOO MANY OPTIONS SELECTED. PLEASE RESPECIFY.

Reason:
The total length of the options specified on the request exceeded the limit for the API to
pass to CA Workload Automation SE. The request was not processed.

Action:
Respecify the request to limit the overall length of the options.

CAL2A700E

L2VDB for xxxxxxxx not found.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 125

CAL2 Messages

CAL2A705E

(aa bbbb) BAD QSEQ - REQ POINTS AT CLOSED RB. QUERY : cccccccc

Reason:
A call from an existing SQL Query request failed. aa is the caller's prefix. bbbb is the
offset into the table. cccccccc is the query type.

Action:
This message more than likely followed the CAL2A615E message. Attempt to resolve the
prior message. If the errors persist, contact your installation specialist for assistance.

CAL2A720E

L2VP not found.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A800E

Variable not found - xxxxxxxx.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A810E

QRYD_WHRNAMES pointer is zero.

Reason:
Internal error in the communication between the SQL interface and the CA Workload
Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

126 Message Reference Guide

 CAL2 Messages

CAL2A820E

Table col name not in QRYD_WHRNAMES.

Reason:
Internal error in the communication between the SQL interface and the CA Workload
Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A830E

Located WHRNAMES but WHRVALS is zero.

Reason:
Internal error in the communication between the SQL interface and the CA Workload
Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A840E

FREEMAIN error.

Reason:
Internal error in the CA Workload Automation SE API interface.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 127

CAL2 Messages

CAL2A850E

Not supported by your release of CA-7.

Reason:
The function you requested is not supported by the release of CA Workload Automation
SE that you are connected to. This usually means the CA Workload Automation SE API
you are using is at a higher release level than the CA Workload Automation SE you are
connected to, and you have requested a function that requires features contained in the
new release of CA Workload Automation SE.

Action:
Check the parameters in your API PROFILE data set, member CACCENV. Ensure that the
CA7APPL= keyword specifies the correct VTAM APPLid for the CA Workload Automation
SE you want to communicate with.

CAL2A890E

An error occurred in Jobflow Illustrator - RC=nnnnnnnn

Reason:
This message is issued when any nonzero return code is received from CA Workload
Automation SE Jobflow Illustrator and an error message was not provided. The return
code from CA Workload Automation SE is nnnnnnnn.

Action:
Review the SYSMSGS log in the CA Workload Automation SE Jobflow Illustrator output
and take appropriate action based on the error listed there.

CAL2A891E

Jobflow Illustrator internal error: RSN=reasoncode, RC=returncode

Reason:
An internal error has occurred in program L2L10080 while processing a VSQL request for
the CA Workload Automation SE Jobflow Illustrator.

The reason code and return code are displayed in the message. The following is a list of
reason codes associated with this message:
01
Indicates that module CAL2FSIM or L2L10081 could not be located
02
Indicates that CHKPOINT processing must be SAVE or LOAD.

128 Message Reference Guide

 CAL2 Messages

03
Indicates that the dataset name is missing on CHKPOINT LOAD.
04
Indicates that DYNALLOC failed for dataset name on CHKPOINT LOAD.
05
Indicates that DYNALLOC failed for dataset name on CHKPOINT SAVE.
06
Indicates that CMDPARM is missing and CHKPOINT=SAVE requested.
07
Indicates a missing CA Workload Automation SE LOGON ID.
08
Indicates a missing L2VD for column WK_7INST.
09
Indicates a missing L2VDHBA for column WK_7INST.
10
Indicates an Invalid L2HBVAL for column WK_7INST.
11
Indicates a missing L2VD for column WK_7NODE.
12
Indicates a missing L2VDHBA for column WK_7NODE.
13
Indicates an invalid L2HBVAL for column WK_7NODE.
14
Indicates a missing L2VD for column WK_7RECV.
15
Indicates a missing L2VDHBA for column WK_7RECV.
16
Indicates an invalid L2HBVAL for column WK_7RECV.
17
Indicates that a required column not found on WHERE clause.
18
Indicates a missing column value on WHERE clause.

Chapter 2: AFM - CA7R Messages 129

CAL2 Messages

19
Indicates a column value length invalid on WHERE clause.
20
Indicates a column value length exceeds maximum on WHERE clause.
21
Indicates that a CMDPARM value is missing on WHERE clause.
22
Indicates that a CMDPARM value length exceeds maximum on WHERE clause.
23
Indicates that a CMDPARM value length must be a least 6 positions.
24
Indicates that a CMDPARM value does not contain a valid command.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2A892E

Internal error in L2L10081 - message text

Reason:
This message is issued when an internal error occurs during CSV exit processing in CA
Workload Automation SE Jobflow Illustrator. The message text contains a description of
the error.

Action:
Contact your installation specialist for assistance.

CAL2A893E

Checkpoint allocation failed - RC=returncode, RSN=reasoncode

Reason:
Program L2L10080 was unable to dynamically allocate the checkpoint file as the result
of a SAVE or LOAD request. The message displays the return code and reason code.

Action:
Determine the reason for the failure, correct the problem, and resubmit the request.
Check the job log of the Schedule Server task, associated with the Jobflow Illustrator
Online session, for additional information.

130 Message Reference Guide

 CAL2 Messages

CAL2A894E

Unable to save the Checkpoint file due to setup

Reason:
Program L2L10080 was unable to save the checkpoint file as a result of a SAVE request
due to invalid Jobflow Illustrator variables in the CACCENV member of the PROFILE data
set.

Action:
Correct the Jobflow Illustrator variables in the CACCENV member of the PROFILE data
set, and resubmit the request. CAL2V70xE messages, found in the associated Schedule
Server task, show the exact cause of the error. The correct syntax for the WFDSN,
WFALLOC, and WFSPACE variables is described in the Jobflow Illustrator Microsoft Visio
Option Guide.

CAL2A895E

File not found-filename

Reason:
Program L2L10080 was unable to locate the checkpoint file as a result of a LOAD
request. The file name is listed in the message.

Action:
Correct the file name and resubmit the request.

CAL2A896I

Calling Jobflow Illustrator xxxx ...

Reason:
Program L2L10080 is calling a CA Workload Automation SE Jobflow Illustrator function in
response to a client request. The message lists the called function.

Action:
None.

Chapter 2: AFM - CA7R Messages 131

CAL2 Messages

CAL2A897I

Jobflow Illustrator xxxx RC=nnnnnnnn ...

Reason:
Program L2L10080 indicates the return code from the CA Workload Automation SE
Jobflow Illustrator function listed in the message. Additionally, if an error occurred, the
error message being returned to the client is appended to this message.

Action:
None.

CAL2A900E

API/CA-7 interface ended, unable to process request.

Reason:
The VTAM interface between the CA Workload Automation SE API and the CA Workload
Automation SE address space has terminated.

Action:
Check to ensure the CA Workload Automation SE address space is still active. If so, back
out of ViewPoint and reenter it. Access a CA Workload Automation SE data panel to
reestablish the connection. If the problem persists, contact CA Support at
ca.com/support for assistance.

CAL2C050I

XTM initialization in progress

Reason:
Initialization of CAICCI terminal interface system environment has begun.

Action:
None.

132 Message Reference Guide

 CAL2 Messages

CAL2C051I

XTM initialization complete

Reason:
This message reports successful initialization of CAICCI terminal interface system
environment.

Action:
None.

CAL2C052I

CCI Interface initialized

Reason:
The CAICCI INIT request was successful. CA Workload Automation SE is ready to accept
CAICCI terminal requests.

Action:
None.

CAL2C053I

CTI RECEIVER IS: #nnnnnnn CA-7 XTM xxxx

Reason:
The CAICCI terminal interface has successfully initialized. This message reports the name
of the CAICCI Terminal Interface (CTI) receiver where nnnnnnn is the name of the CAICCI
node and xxxx identifies the instance of CA Workload Automation SE that has initialized.
This information must be provided to the CAICCI Terminal Interface client to ensure
communication with the correct instance of CA Workload Automation SE. For more
information about the CA Workload Automation SE CAICCI Terminal Interface, see the
Interface Reference Guide.

CA Workload Automation SE uses the following hierarchy to determine the value of the
receiver name suffix (xxxx). If the XTMNAME keyword is coded on the SVCNO statement
in the product's initialization file, xxxx is the value of XTMNAME. If no XTMNAME
keyword is found, xxxx is the value of the RNAME keyword on the SVCNO statement. If
neither of these keywords is coded, xxxx is the instance name. For information about
initialization file parameters, see the Systems Programming Guide.

Action:
None.

Chapter 2: AFM - CA7R Messages 133

CAL2 Messages

CAL2C054E

CCI Interface initialization failed

Reason:
The CAICCI INIT request failed. CA Workload Automation SE cannot accept CAICCI
terminal requests.

Action:
An additional message specifying the reason for the CAICCI INIT failure will be issued.
The most likely reason is that CAICCI is not active. If this is the case, start CAICCI. When
CAICCI is initialized then issue the following CA Workload Automation SE command:
/OPEN,GROUP=name-of-CCI-group.

Note: For more information, see the discussion of the /OPEN command in the
Command Reference Guide.

CAL2C055E

text

Reason:
This is a message from CA Workload Automation SE XPS support. The text contains the
information.

Action:
Depending on the message, take any actions necessary.

CAL2C056E

Exceeded max num of RPLs

Reason:
An internal limit on the number of concurrent CAICCI terminal session requests was
exceeded. One or more CAICCI terminal transactions may have failed.

Action:
If the condition persists, contact your installation specialist for assistance.

134 Message Reference Guide

 CAL2 Messages

CAL2C300W

X2W0 ESTAE ENTERED - WIP=wwww (aaaa) (pppppppp): ddd...ddd

Reason:
The main task error routine has been entered for an abend in processing. The
where-in-program code is indicated by wwww. The abend code is indicated by aaaa
(hex). The abend PSW is indicated by pppppppp. If the PSW points to an address within
the main task program (CAL2X2W0), it is in the form of '+offset'. If not, it is the full eight
character PSW. The description of the action being taken by the recovery routine is
indicated by ddd...ddd. If the recovery routine attempts to continue processing, the
description is 'RETRY IS BEING ATTEMPTED'. If the abend occurred during a call to the
user print exit, no more calls are made to the print exit. If the recovery routine does not
attempt to continue, the description is 'ALLOWING ABEND TO PROCEED', and the task
abends.

Action:
Check your exit for errors if the abend occurred in the user print exit (WIP=M7EX).
Otherwise, contact CA Support at ca.com/support for assistance.

CAL2C301W

'SUBMIT' CLASS/RESOURCE NOT DEFINED TO EXTERNAL SECURITY FUNCTION

ALLOWED.

Reason:
An attempt was made to check the authorization for the owner of the current
environment to submit a CA Workload Automation SE logon for the operator ID
specified on the /LOGON command being processed. The external security system
responded with a return code 4, indicating SUBMIT is not a defined resource. The
/LOGON command and subsequent commands are processed normally. Any messages
returned by the external security system are listed following this message.

Action:
Define the SUBMIT resource and applicable rules if you want your external security
system to control CA Workload Automation SE External Communicators.

Note: For more information about implementation, see the Security Reference Guide.

Chapter 2: AFM - CA7R Messages 135

CAL2 Messages

CAL2C401I

SESSION INIT SENT TO : aaa...aaa/nnn...nnn

Reason:
This trace message indicates that a Session Initialization record was sent to CA Workload
Automation SE. The message displays the destination application and system names.
aaa...aaa is the CA Workload Automation SE Terminal receiver name. nnn...nnn is the
CAICCI node name.

Action:
None.

CAL2C402I

DATA CLOSE SENT. (EOD)

Reason:
This trace message indicates that a Data Close record was sent to CA Workload
Automation SE. (EOD) indicates the end of data on command input.

Action:
None.

CAL2C403I

DATA CLOSE RECEIVED.

Reason:
This trace message indicates that a Data Close record was received from CA Workload
Automation SE indicating the end of data on command output.

Action:
None.

136 Message Reference Guide

 CAL2 Messages

CAL2C404I

SESSION END SENT.

Reason:
This trace message indicates that a Session End record was sent to CA Workload
Automation SE.

Action:
None.

CAL2C405I

SUBSTITUTION INST USED: aaa...aaa/nnn...nnn

Reason:
This message indicates a substitution was made for the CA Workload Automation SE
instance value specified in the CA Workload Automation SE CAICCI interface
parameters. The CA Workload Automation SE CAICCI Terminal CAICCI receiver is
indicated where: aaa...aaa is the CA Workload Automation SE CAICCI Terminal receiver
name, and nnn...nnn is the CCI node name.

Note: For more information about situations where the CA Workload Automation SE
instance value can be automatically substituted, see the interface with CAICCI in the
Interface Reference Guide.

Action:
None.

CAL2C406I

COMPATIBILITY MODE ON/OFF

Reason:
This message indicates whether the CA Workload Automation SE system environment is
in release compatibility mode (ON) or (OFF). The message only appears when the CA
Workload Automation SE CAICCI interface is determining whether a substitution
instance is appropriate and tracing is enabled.

Note: For more information about situations where the CA Workload Automation SE
instance value can be automatically substituted, see the interface with CAICCI in the
Interface Reference Guide.

Action:
None.

Chapter 2: AFM - CA7R Messages 137

CAL2 Messages

CAL2C452I

(X2W) CCIF=ffff RC=rr CC=cc:

Reason:
This trace message indicates the completion of a specific CAICCI call. The function,
return code and condition code of the call to the CAICCI interface module are indicated
by ffff, rr and cc. The function, return code and condition code of the call to CAICCI itself
are indicated by f2f2, r2 and c2. If the function is a send or receive then the first 60
characters of the data is listed in rrr...rrr.

Action:
None.

CAL2C501I

***** INPUT TO CA-7 CCI BATCH INTERFACE *****

Reason:
This message is printed before listing the command input to the CA Workload
Automation SE CCI batch interface. The input commands are listed following this
message.

Action:
None.

CAL2C502I

***** END OF INPUT TO CA-7 CCI BATCH INTERFACE *****

Reason:
This message is printed after listing the command input to the CA Workload Automation
SE CCI batch interface.

Action:
None.

138 Message Reference Guide

 CAL2 Messages

CAL2C503W

***** NO CA-7 COMMANDS IN INPUT *****

Reason:
This message indicates that no CA Workload Automation SE commands were in the
input to the CA Workload Automation SE CAICCI interface.

Action:
Check to ensure that DDNAME SYSIN is in the JCL to invoke the CA Workload
Automation SE CAICCI interface. If you have overridden the DDNAME for command
input, ensure that the DDNAME in your JCL correctly corresponds to the override.

CAL2C504I

***** RESPONSES RECEIVED FROM CA-7 *****

Reason:
This message is printed before listing the command output sent from CA Workload
Automation SE to the CA Workload Automation SE CAICCI interface. The command
output lines are listed following this message.

Action:
None.

CAL2C505I

***** END OF CA-7 RESPONSES *****

Reason:
This message is printed after listing the command output sent from CA Workload
Automation SE to the CA Workload Automation SE CAICCI interface.

Action:
None.

Chapter 2: AFM - CA7R Messages 139

CAL2 Messages

CAL2C506W

***** NO CA-7 RESPONSES RECEIVED *****

Reason:
This message is printed to indicate that no command output was received from CA
Workload Automation SE.

Action:
Look for other messages in SYSPRINT or in the JES Log to indicate errors in the
commands or the interface. This message can also be produced for a CCI terminal during
a CA Workload Automation SE shutdown.

CAL2C508W

ERROR MSGS FOUND IN OUTPUT. MSGS MATCHED=xxxxx, HIGH CC=ccc

Reason:
This WTO is issued at the end of CA Workload Automation SE CCI Batch processing if any
lines in the CA Workload Automation SE output matched an entry in the user-defined
batch message table (SASSXXBT). The number of matches made (xxxxx) and the highest
condition code associated with those entries (ccc) are detailed. The return code of the
CA Workload Automation SE CCI Batch step is set to the highest condition code
matched.

Action:
None.

CAL2C509I

CA-7 CCI BATCH PROCESS COMPLETE. RC=rrrr CC=cccc

Reason:
The CA Workload Automation SE CCI Batch Interface module (CAL2X2WB) has
completed processing. The return code (rrrr) and condition code (cccc) from the process
are listed (in hexadecimal).

Action:
If the return codes, condition codes, or both are nonzero, see any messages preceding
this one. For an explanation of the return and condition codes, see External
Communicators in the Interface Reference Guide.

140 Message Reference Guide

 CAL2 Messages

CAL2C580W

WARNING - DD STATEMENT IS MISSING OR INVALID: dddddddd

Reason:
This DDNAME dddddddd is either missing from the JCL or is invalid. The DD statement is
optional and processing will continue without it.

Action:
If the DD was omitted on purpose, ignore the message. If not, correct the JCL to supply
the listed DD statement.

CAL2C581W

UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE REPORTED.

Reason:
This message is issued when a user-defined Batch Message Table (SASSXXBT) is
available, but the DD statement for the ERRORS file is not in the JCL. Normally, messages
from the Batch Message Table checking are routed to this ERRORS DD. Since this DD is
not available, the messages will not be produced. However, you will still get the
CAL2C508W message that informs you how many table matches were made, and what
the highest matched condition code is.

Action:
Add a DD statement for ERRORS. The format is the same as the existing SYSPRINT DD.

CAL2C582W

ERROR MSG TABLE MATCH (CC=ccc): ...text...

Reason:
This message is written to the ERRORS DD when a line in the CA Workload Automation
SE CCI Batch output matches an entry in the user-defined batch message table
(SASSXXBT). The condition code (CC=) that is associated with that table entry is listed.
Also, the text of the matching output line is displayed.

Action:
None.

Chapter 2: AFM - CA7R Messages 141

CAL2 Messages

CAL2C590E

INVALID PARAMETER LIST

Reason:
The parameter list passed to the CA Workload Automation SE CAICCI interface was
invalid. A return code of 16 is set and processing is terminated.

Action:
Correct the parameter list, and resubmit the job.

CAL2C591E

INVALID PARAMETER STARTING WITH (xxxxxxxx) - ABORTING

Reason:
A value (xxxxxxxx) in the parameter list passed to the CA Workload Automation SE
CAICCI interface was invalid. A return code of 16 is set and processing is terminated.

Action:
Correct the parameter list, and resubmit the job.

CAL2C592E

DD STATEMENT IS MISSING OR INVALID: dddddddd

Reason:
This DDNAME dddddddd is either missing from the JCL or is invalid. The DD statement is
optional and processing will continue without it.

Action:
If the DD was omitted on purpose, ignore the message. If not, correct the JCL to supply
the listed DD statement.

CAL2C593E

ERROR DURING DCB OPEN: dddddddd

Reason:
An error occurred attempting to open the DCB for ddname dddddddd. Processing
terminates.

Action:
Check the JCL, and correct the DD statement in error.

142 Message Reference Guide

 CAL2 Messages

CAL2C594E

UNABLE TO GETMAIN STORAGE FOR xxxxxxxx RC=rrrr

Reason:
An error occurred attempting to get storage for the xxxxxxxx control block. The return
code from the GETMAIN is rrrr. Processing terminates.

Action:
Increase the region size and resubmit the job.

CAL2C595E

UNABLE TO LOAD MODULE mmmmmmmm . RC=rrrr

Reason:
An error occurred attempting to load module mmmmmmmm. The return code from the
LOAD call is rrrr.

Action:
Check the STEPLIB DD statement in the JCL and ensure that the CA Workload
Automation SE load library (CAL2LOAD) is in the concatenation.

CAL2C596E

NON-ZERO RETURN FROM CA-7 CCI INTERFACE. RC=rrrr CC=cccc

Reason:
An error code was returned from the CA Workload Automation SE CAICCI interface
module (CAL2X2W0). The return code was rrrr, and the reason code was cccc.

Action:
See any messages in the JES Log indicating the nature of the error encountered.
Otherwise, contact CA Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 143

CAL2 Messages

CAL2C600W

VARIABLE xxxxxxxx COULD NOT BE RETRIEVED--CODE cc

Reason:
An error code was encountered in the CA Workload Automation SE CAICCI interface
REXX facility. The variable xxxxxxxx could not be accessed. The return code from the
access attempt was cc.

Action:
See the sample CA Workload Automation SE REXX CLIST (CA7REXX) in the CA CLIST
library (CAL2CLS0). Ensure that your execution of the facility does not specify invalid
values for variables that are available.

CAL2C601E

UNABLE TO ACCESS CA-7 MODULE CAL2X2W0

Reason:
An error occurred attempting to load module CAL2X2W0 (CA Workload Automation SE
CAICCI interface) from the CA Workload Automation SE CCI REXX facility.

Action:
Check the environment and ensure that the CA Workload Automation SE load library
(CAL2LOAD) is accessible.

CAL2C602E

CA-7 COMMAND STRING IS MISSING

Reason:
The CA Workload Automation SE CAICCI interface REXX facility was invoked, but no CA
Workload Automation SE commands were specified.

Action:
Execute the interface specifying one or more CA Workload Automation SE commands.
For an example, see the sample CA Workload Automation SE REXX EXEC (CA7REXX) in
the CA CLIST library (CAL2CLS0).

144 Message Reference Guide

 CAL2 Messages

CAL2C900I

CA-7 CCI Initialization Complete

Reason:
The CA Workload Automation SE CAICCI interface has completed its initialization. This is
a unique message ID that facilitates automation as necessary.

If you want to get the old text of the message (r11 and below) specify
CAL2C900=ORIGINAL on the OPTIONS statement in the product's initialization file. The
original text was "CAL2C900I Unicenter CA-7 CCI Initialization Complete".

Action:
None.

CAL2C900I

Unicenter CA-7 CCI Initialization Complete

Reason:
The CA Workload Automation SE CAICCI interface has completed its initialization. This is
a unique message ID that facilitates automation as necessary.

If you want the new message text, let the initialization file OPTIONS, CAL2C900=
statement to default to CURRENT. This preferred option, CURRENT, should be used if a
site is automating the message based on message ID alone. If automation is parsing the
text of the message, the OPTIONS,CAL2C900=ORIGINAL can be coded to continue to
display this message.

Action:
None.

CAL2C901E

INVALID PARAMETER: xxxxxxxx: ABORTING

Reason:
An invalid parameter (xxxxxxxx) was passed to the CA Workload Automation SE CAICCI
interface module.

Action:
Correct the specified parameter and resubmit/execute the interface.

Chapter 2: AFM - CA7R Messages 145

CAL2 Messages

CAL2C902E

UNABLE TO LOAD MODULE mmmmmmmm. RC=rrrr

Reason:
An error occurred attempting to load module mmmmmmmm. The return code from the
LOAD call is rrrr.

Action:
Check the STEPLIB DD statement in the JCL/environment and ensure that the CA
Workload Automation SE load library (CAL2LOAD) is in the concatenation.

CAL2C903E

CA-7 RECEIVER NOT FOUND (aaa...aaa/nnn...nnn)

Reason:
The CA Workload Automation SE CAICCI interface module could not locate the CA
Workload Automation SE CAICCI Terminal CAICCI receiver where aaa...aaa indicates the
CA Workload Automation SE CAICCI Terminal receiver name, and nnn...nnn indicates the
CAICCI node name.

Action:
Perform the following actions:
■ Verify that the CA Workload Automation SE address space is active.
■ Verify the product's initialization file to help ensure that one or more CAICCI
Terminals are defined (DEVICE=CCI).
■ Verify the CA Workload Automation SE JES Log for CA-7.XTM.... messages to
confirm that the CAICCI terminal interface has initialized properly.
■ Verify that the CA Workload Automation SE CAICCI interface is looking for CA
Workload Automation SE at the correct CAICCI node (nnn...nnn).
■ Verify the initialization file SVCNO statement to see whether RNAME or XTMNAME
is used. If used, you may need to change the PARM for the CAICCI process to reflect
the correct value.

Otherwise, contact CA Support at ca.com/support for assistance.

146 Message Reference Guide

 CAL2 Messages

CAL2C904E

BUFSIZE FROM CA-7 INVALID.

Reason:
The CA Workload Automation SE CAICCI interface module received an INIT response
record from CA Workload Automation SE that contained an invalid buffer size.
Processing is terminated.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2C905E

CA-7 XTM NOT RESPONDING (aaa...aaa/nnn...nnn)

Reason:
The CA Workload Automation SE CCI Terminal facility is not responding to calls from the
CA Workload Automation SE CAICCI interface. The CA Workload Automation SE CCI
Terminal CAICCI receiver is indicated where: aaa...aaa is the CA Workload Automation
SE CAICCI Terminal receiver name, and nnn...nnn is the CCI node name.

Action:
Check to ensure that the CA Workload Automation SE address space is active. If so,
check the CA Workload Automation SE JES Log for CA-7.XTM... messages to see if the
CCI terminal interface has encountered any errors. Otherwise, contact CA Support at
ca.com/support for assistance.

CAL2C906E

XTM xxxx FAILED. RC=rr RSN=cc TEXT=ttt...ttt

Reason:
The CA Workload Automation SE CCI Terminal facility returned an error when the CA
Workload Automation SE CAICCI interface attempted to initialize a session. The return
code (rr) reason code (cc) from CA Workload Automation SE are specified along with any
message sent from CA Workload Automation SE (ttt...ttt) and the type (xxxx) of request.

Action:
See the information supplied in the message and take any appropriate corrective
measures. Check the CA Workload Automation SE JES Log for CA-7.XTM... messages to
see if the CCI terminal interface has encountered any errors. Otherwise, contact CA
Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 147

CAL2 Messages

CAL2C907E

INVALID RECORD RECEIVED. REC = rrr...rrr

Reason:
The CA Workload Automation SE CCI Terminal facility returned an invalid record to the
CA Workload Automation SE CAICCI interface. The first 24 characters of the record are
listed (rrr...rrr).

Action:
For assistance, contact CA Support at ca.com/support.

CAL2C908E

UNEXPECTED REC RECEIVED. EXPECTED eeeeeee RECEIVED rrrrrrrr (zzzz)

Reason:
The CA Workload Automation SE CAICCI Terminal facility returned an unexpected record
to the CA Workload Automation SE CAICCI interface. The interface was expecting
eeeeeee, but received rrrrrrrr (record code zzzz).

Action:
For assistance, contact CA Support at ca.com/support.

CAL2C909E

INVALID BATCH CMD: ccc...ccc

Reason:
The CA Workload Automation SE CAICCI interface was passed a CA Workload
Automation SE command that is only valid in an online CA Workload Automation SE
session. The invalid batch command is listed (ccc...ccc). The command is not sent to CA
Workload Automation SE. Processing continues with the next command.

Action:
None.

148 Message Reference Guide

 CAL2 Messages

CAL2C910I

CA-7 XTM RECEIVER FOR CA-7 nnnn LOCATED AT NODE xxxxxxxx

Reason:
Dynamic location of CA Workload Automation SE is attempted if *AUTO* is specified for
the CA Workload Automation SE CCI Node parameter/variable. The CA Workload
Automation SE CAICCI Interface located a CA Workload Automation SE CAICCI XTM
receiver that matches the requested CA Workload Automation SE XTM indentifier (CA-7
nnnn) at the CCI node indicated (xxxxxxxx). Commands are routed to that copy of CA
Workload Automation SE.

Action:
None. This WTO is only issued if the Trace option is in effect.

CAL2C911E

UNABLE TO LOCATE CA-7 XTM RECEIVER FOR CA-7 xxxx

Reason:
Dynamic location of CA Workload Automation SE is attempted if *AUTO* is specified for
the CA Workload Automation SE CCI Node parameter/variable. The CA Workload
Automation SE CAICCI Interface could not locate a CA Workload Automation SE CAICCI
XTM receiver that matches the CA Workload Automation SE XTM identifier (CA-7 xxxx)
at any CCI node that is connected to the local environment. The CA Workload
Automation SE CAICCI Interface call fails. If message CAL2C405I follows this message, no
action is necessary.

Note: For more information about situations where the CA Workload Automation SE
instance value can be automatically substituted, see the CAICCI interface in Interface
Reference Guide.

Action:
Check to see if the correct CA Workload Automation SE XTM identifier (CA-7 xxxx) is
specified or defaulted to for the targeted copy of CA Workload Automation SE. If so,
check to ensure that CA Workload Automation SE is active and the CA Workload
Automation SE XTM receiver is enabled (check CA Workload Automation SE messages
prefixed with CA-7.XTM in the CA Workload Automation SE address space). If so, check
to ensure that the local CAICCI system is connected to the CAICCI system on the image
where the target CA Workload Automation SE is executing (check the local CAIENF
started task). Correct the errors and reissue the commands/job.

Chapter 2: AFM - CA7R Messages 149

CAL2 Messages

CAL2C912W

MULTIPLE CA-7 XTM RECEIVERS LOCATED FOR CA-7 xxxx. DEFAULTING TO LOCAL
NODE.

Reason:
Dynamic location of CA Workload Automation SE is attempted if *AUTO* is specified for
the CA Workload Automation SE CCI Node parameter/variable. The CA Workload
Automation SE CAICCI Interface located CA Workload Automation SE CAICCI XTM
receivers that match the CA Workload Automation SE XTM identifier (CA-7 xxxx) on
more than one CCI node that is connected to the local environment. The CA Workload
Automation SE CAICCI Interface call will attempt to direct commands to a matching copy
of CA Workload Automation SE on the local system (same system where the CA
Workload Automation SE CAICCI Interface is called).

Action:
Either specify an explicit CCI Node on the request to direct commands to that copy of CA
Workload Automation SE, or assign each copy of CA Workload Automation SE a unique
CA Workload Automation SE XTM identifier. CA Workload Automation SE XTM
identifiers can be assigned with the XTMNAME= keyword on the SVCNO statement in
the product's initialization file.

CAL2C913W

INIT RESPONSE FROM CA-7 ASSUMED LOST. ATTEMPTING TO CONTINUE BASED ON

TAP/R.

Reason:
CAICCI received a TAP or TAP response from CA Workload Automation SE while waiting
for an INIT response. If it has a valid SCTNAME, CAICCI assumes initialization is complete
and continues.

Action:
None.

150 Message Reference Guide

 CAL2 Messages

CAL2C914E

INIT RESPONSE FROM CA-7 ASSUMED LOST. SESSION BEING TERMINATED.

Reason:
The CA Workload Automation SE CAICCI interface requested a terminal session with CA
Workload Automation SE, but subsequently received a record from CA Workload
Automation SE that did not conform to the interface protocol. This condition is probably
transient and should not reoccur if the interface is retried.

Action:
To prevent further occurrences of this condition, ensure that all necessary CA Common
Services maintenance is applied. For assistance, contact CA Support at ca.com/support.

CAL2C926E

(ttt) SESSION BROKEN DUE TO UNEXPECTED END OF CA-7 ONLINE SYSTEM.

Reason:
This message is issued with the task ID ttt if the CA Workload Automation SE online task
unexpectedly abended while this CAICCI terminal was active. In this case, address the
errors as to why CA Workload Automation SE online task abended. If the CAICCI
terminal was updating the data set, the queues, or both, verify the updates in CA
Workload Automation SE before rerunning the job.

Action:
Review any preceding or following messages and take corrective actions indicated by
them. If there are no other messages, contact CA Support at ca.com/support for
assistance.

CAL2C927E

(ttt) CCI ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx

Reason:
The CAICCI subfunction module has encountered an error. The task calling the
subfunction is identified by ttt. The subfunction is indicated by fff, the return code and
condition codes are indicated by rr and cc. A text description of the error is indicated by
xxx...xxx.

Action:
Review any preceding or following messages and take corrective actions indicated by
them. If there are no other messages contact CA Support at ca.com/support for
assistance.

Chapter 2: AFM - CA7R Messages 151

CAL2 Messages

CAL2C928E

(ttt) CCIF CALL FAILED: FUNC=ffff RC=rr CC=cc

Reason:
The CAICCI subfunction module has encountered an internal error. The task calling the
subfunction is identified by ttd. The function is indicated by fff, the return code and
condition codes are indicated by rr and cc.

Action:
Review any preceding or following messages and take corrective actions indicated by
them. If there are no other messages, contact CA Support at ca.com/support for
assistance.

CAL2C950E

BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON COMMAND

Reason:
The external security system would not authorize the owner of the current environment
to submit a CA Workload Automation SE logon for the operator ID specified on the
/LOGON command being processed. Any messages returned by the external security
system will be listed following this message. The /LOGON command and subsequent
commands will be processed normally. The commands following that logon will be
skipped until another /LOGON statement is encountered.

Action:
Ensure the owner of the environment has SUBMIT authority for all operator IDs
specified on /LOGON statements.

If you do not want submit security checking for CA Workload Automation SE External
Communicators, review the setting of the BSUBCHK option for this instance. For more
details, see the Security Reference Guide.

152 Message Reference Guide

 CAL2 Messages

CAL2D001I

CA-7 IS STARTING IN DISASTER RECOVERY MODE

Reason:
CA Workload Automation SE has just been started. The parameters passed to CA
Workload Automation SE include "DRMODE=YES", causing CA Workload Automation SE
to start disaster recovery mode. Not all jobs will be scheduled or triggered in disaster
recovery mode. For more information about disaster recovery mode, see the Systems
Programming Guide.

Action:
None required. The /DRMODE,MODE=NORM command can be issued to turn off
disaster recovery mode, if you want.

CAL2D002I

CA-7 IS RUNNING IN DISASTER RECOVERY MODE

Reason:
The /DRMODE,MODE=DR command has been issued to switch CA Workload Automation
SE to disaster recovery mode. Not all jobs will be scheduled or triggered in disaster
recovery mode. For more information about disaster recovery mode, see the Systems
Programming Guide.

Action:
None required. The /DRMODE,MODE=NORM command can be issued to turn off
disaster recovery mode, if you want.

CAL2D003I

CA-7 IS NO LONGER RUNNING IN DISASTER RECOVERY MODE

Reason:
The /DRMODE,MODE=NORM command has been issued while CA Workload
Automation SE was executing in disaster recovery mode. Normal schedule scan, job
trigger, and job requirement processing resumes.

Note: For more information about disaster recovery mode, see the Systems
Programming Guide.

Action:
None.

Chapter 2: AFM - CA7R Messages 153

CAL2 Messages

CAL2D004W

CA-7 IS STARTING IN DISASTER RECOVERY MODE, PLEASE CONFIRM : (U)SE, (N)ORMAL

MODE, (C)ANCEL - RESPOND U, N, OR C

Reason:
CA Workload Automation SE is starting with the parameter DRMODE=YES, which causes
CA Workload Automation SE to start in disaster recovery mode. The DRMODE
initialization statement specifies VERIFY=YES, causing CA Workload Automation SE to
confirm disaster recovery mode with the operator before starting.

Action:
Perform one of the following actions:
■ Reply U to start in disaster recovery mode.
■ Reply N to start in normal mode.
■ Reply C to end immediately.

CAL2D005E

DRMODE,TRIGGERS= MUST BE "DR", "ALL", OR "NONEXEC"

Reason:
The value specified for the TRIGGERS= keyword is invalid. It must be DR, ALL, or
NONEXEC. Issued by SASSIDRM.

Action:
Correct the value and resubmit.

CAL2D006E

DRMODE,RQMTS= MUST BE "DR" OR "ALL"

Reason:
The value specified for the RQMTS= keyword is invalid. It must be DR or ALL. Issued by
SASSIDRM.

Action:
Correct the value and resubmit.

154 Message Reference Guide

 CAL2 Messages

CAL2D007E

DRCLASS VALUE LONGER THAN 8 CHARS, IGNORED

Reason:
A value was found on the DRCLASS initialization file statement that was longer than 8
characters. The value has been discarded. Any other valid values on the DRCLASS
statement are added to the list of active disaster recovery classes.

Action:
Correct the DRCLASS initialization file statement for the next start of CA Workload
Automation SE. The /DRCLASS command can be used to update the list of active disaster
recovery classes without restarting CA Workload Automation SE.

CAL2E001I

SMTP SERVER IP ADDRESS IS ip_address

Reason:
The EMAIL initialization file statement is being processed during CA Workload
Automation SE startup. The ESERVER keyword specifies either the name or IP address of
an SMTP email server. CA Workload Automation SE has been able to resolve the
ESERVER value to the specified IP address.

Action:
None.

Chapter 2: AFM - CA7R Messages 155

CAL2 Messages

CAL2E002E

UNABLE TO RESOLVE ESERVER NAME FUNC=xxxxxxxxxxxxxxxx RC=-nnnnnnnnn

REA=xxxxxxxx

Reason:
The EMAIL initialization file statement is being processed during CA Workload
Automation SE startup. The ESERVER keyword specifies either the name or IP address of
an SMTP email server. CA Workload Automation SE was unable, using TCP/IP services, to
resolve the ESERVER value to an IP address. The FUNC value is the last TCP/IP service
called (using the IBM EZASMI interface), and RC and REA show the return code and
reason code returned from the call.

Action:
Perform the action for the FUNC value specified:
INITAPI
Make sure that the CA Workload Automation SE started task has the same SYSTCPD
DD statement as the TCP/IP started task. If your TCP/IP started task uses STEPLIB,
add those libraries to the CA Workload Automation SE started task STEPLIB
concatenation.
GETADDRINFO
If RC = -00000001 and REA = 00000001, the ESERVER may have an IPv6 address.
Check with your systems programmer to verify that the version of TCP/IP used by
the TCP/IP started task supports IPv6 and that IPv6 is enabled. You can either
change your ESERVER to an SMTP server with an IPv4 address, enable IPv6 in your
existing TCP/IP, or change to a version of TCP/IP that supports IPv6. For other
combinations of RC and REA, see Other that follows.
Other
If the problem persists, see the IBM IP Sockets Application Programming Interface
Guide and Reference for information about the EZASMI function listed in the
message to determine what the reason code (ERRNO) means.

156 Message Reference Guide

 CAL2 Messages

CAL2E003E

DYNALLOC ERROR FOR xxxxxxxx ERROR=xxxx INFO=xxxx

Reason:
The EMAIL initialization file statement is being processed during CA Workload
Automation SE startup. The specified ddname could not be dynamically allocated.

Action:
Make sure the data set specified on the EMAIL initialization file option exists and is
available. Alternatively, you can specify a DD statement in the CA Workload Automation
SE started task JCL to allocate this data set.

CAL2E004E

EPORT VALUE INVALID, USING DEFAULT OF 25

Reason:
The EMAIL initialization file statement is being processed during CA Workload
Automation SE startup. The value on the EPORT keyword is zero, non-numeric, or
greater than 65535.

Action:
An EPORT value of 25 should be correct for most sites. If it is not for your site, correct
the EPORT value and restart CA Workload Automation SE.

CAL2E005E

ETIMEOUT VALUE INVALID, USING DEFAULT OF 10

Reason:
The EMAIL initialization file statement is being processed during CA Workload
Automation SE startup. The value on the ETIMEOUT keyword is either non-numeric or
outside of the range 5 to 20 seconds.

Action:
An ETIMEOUT value of 10 seconds is appropriate for most sites. If you need to adjust it,
you can correct the ETIMEOUT keyword and restart CA Workload Automation SE, or use
the /EADMIN command to change the ETIMEOUT value.

Chapter 2: AFM - CA7R Messages 157

CAL2 Messages

CAL2E006E

xxxxxxxx NOT ALLOCATED, EMAIL SUPPORT TURNED OFF

Reason:
The specified DD statement is required for email support but is not in the CA Workload
Automation SE started task JCL and was not dynamically allocated as part of the EMAIL
initialization file statement.

Action:
Either include the specified DD statement in the CA Workload Automation SE started
task JCL or update the EMAIL initialization file statement. Restart CA Workload
Automation SE.

CAL2E007E

EMAIL,ESERVER= IS REQUIRED

Reason:
CA Workload Automation SE found an EMAIL initialization file statement, but the
ESERVER keyword was not specified.

Action:
Correct the EMAIL statement and restart CA Workload Automation SE.

CAL2E008I

TCP/IP FUNCTION xxxxxxxxxxxx RETCODE=xxxxxxxxx ERRNO=xxxxxxxx

Reason:
The CA Workload Automation SE email trace is turned on. The specified TCP/IP function
has completed with the listed return code and error number. Remember that not all
nonzero return codes are errors. For example, the return code for the SEND and
RECEIVE functions is the number of bytes sent or received. Consult the IBM manual for
the EZASMI (TCP/IP) interface to learn more about the return codes from each TCP/IP
function.

Action:
None.

158 Message Reference Guide

 CAL2 Messages

CAL2E009E

TCP/IP INITAPI FAILED RETCODE=xxxxxxxxx ERRNO=xxxxxxxx

Reason:
The CA Workload Automation SE email feature tried to initialize a TCP/IP session but
failed. The return code and error number are listed.

Action:
Make sure that the SYSTCPD DD statement in the TCP/IP started task is included in the
CA Workload Automation SE started task. If the TCP/IP started task has a STEPLIB, add
those data sets to the CA Workload Automation SE started task STEPLIB. Make sure that
the user ID under which CA Workload Automation SE runs has an OMVS segment
(consult with your security administrator). Refer to the IBM manual for the EZASMI
(TCP/IP) interface for more information about the return and error codes from the
INITAPI function.

CAL2E010W

TCP/IP FUNCTION xxxxxxxxxxxx TIMED OUT

Reason:
CA Workload Automation SE waited the number of seconds specified on the EMAIL
ETIMEOUT option but never received notification that the specified TCP/IP function
ended. For some functions, such as INITAPI, a time-out is fatal and the email is not sent.
For other functions, such as RECEIVE, CA Workload Automation SE will continue sending
the email as if the time-out had not occurred.

Action:
You can increase the value of the EMAIL ETIMEOUT option if many time-outs are
occurring but emails are still being delivered.

CAL2E011I

LOCAL HOST NAME IS xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
CA Workload Automation SE has determined the local TCP/IP host name for the system
on which CA Workload Automation SE is executing. This information is used when
communicating with the SMTP (email) server.

Action:
None.

Chapter 2: AFM - CA7R Messages 159

CAL2 Messages

CAL2E012E

GETHOSTID CALL FAILED

Reason:
CA Workload Automation SE was unable to determine the TCP/IP name of the system
on which CA Workload Automation SE is executing. The information is required when
communicating with the SMTP (email) server. CA Workload Automation SE does not
send the email.

Action:
Determine why the EZASMI GETHOSTID call failed in the TCP/IP address space. If
necessary, you can turn on the CA Workload Automation SE email trace
(/EADMIN,TRC=Y) to obtain the actual return and reason codes returned from TCP/IP.

CAL2E013I

LOCAL HOST IP ADDRESS IS ip_address

Reason:
CA Workload Automation SE has determined the IP address of the system on which CA
Workload Automation SE is executing. CA Workload Automation SE will use the SMTP
(email) server on the execution system if the SMTP server specified on the EMAIL
ESERVER initialization file option becomes unavailable, or if the EMAIL ESERVER option
is not specified.

Action:
None.

CAL2E014E

COULD NOT CREATE SOCKET

Reason:
CA Workload Automation SE was unable to create a communication connection to
TCP/IP. CA Workload Automation SE does not send the email.

Action:
Determine why the EZASMI SOCKET call failed in the TCP/IP address space. If necessary,
you can turn on the CA Workload Automation SE email trace (/EADMIN,TRC=Y) to obtain
the actual return and reason codes returned from TCP/IP.

160 Message Reference Guide

 CAL2 Messages

CAL2E015E

COULD NOT CONNECT TO SMTP SERVER

Reason:
CA Workload Automation SE was unable to reach an SMTP (email) server. Both the
primary SMTP server (on the EMAIL ESERVER option) and the SMTP server on the local
system have been tried. CA Workload Automation SE does not send the email.

Action:
Determine why an SMTP server is not available. If using an SMTP server on another
system, make sure that system is up and can be reached from the system where CA
Workload Automation SE is executing. If necessary, you can turn on the CA Workload
Automation SE email trace (/EADMIN,TRC=Y) to obtain the actual return and reason
codes returned from TCP/IP.

CAL2E016W

CAN'T CONNECT TO SMTP SERVER, SWITCHING TO LOCAL HOST

Reason:
CA Workload Automation SE is unable to reach the primary SMTP (email) server
specified on the EMAIL ESERVER option. CA Workload Automation SE will next try to
contact the SMTP server on the system where CA Workload Automation SE is executing.
CA Workload Automation SE will try to use the primary SMTP server for every
subsequent email, but will only issue this message the first time the server cannot be
reached.

Action:
Determine why the primary SMTP server is not available and correct the problem.

CAL2E017I

RECV:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
The CA Workload Automation SE email trace is active. The specified data has been
received from the SMTP server through TCP/IP. Remember that the data was received in
ASCII and has been converted to EBCDIC before being displayed.

Action:
None.

Chapter 2: AFM - CA7R Messages 161

CAL2 Messages

CAL2E018I

SEND:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
The CA Workload Automation SE email trace is active. The specified data is being sent to
the SMTP server through TCP/IP. Remember that the data is converted to ASCII before
being sent.

Action:
None.

CAL2E019E

L2DATES ERROR REASON=xxxx

Reason:
The CA Workload Automation SE email interface encountered a problem converting a
date to/from Julian/Gregorian.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2E020I

WILL USE SMTP SERVER AT ip_address

Reason:
CA Workload Automation SE has determined the IP address of the SMTP (email) server
specified on the EMAIL EADDRLIB initialization file option.

Action:
None.

162 Message Reference Guide

 CAL2 Messages

CAL2E021W

ABORTING EMAIL DUE TO SHUTDOWN REQUEST

Reason:
CA Workload Automation SE was in the process of sending an email when a CA
Workload Automation SE shutdown request was received. The email is abandoned so
that CA Workload Automation SE can shut down immediately.

Action:
None.

CAL2E022I

EMAIL SUB-TASK AVAILABLE

Reason:
CA Workload Automation SE is initializing. The EMAIL initialization file statement has
been successfully processed. The email subtask has been started and is now ready to
process /EMAIL commands.

Action:
None.

CAL2E023W

nnn EMAILS NOT SENT AT SHUTDOWN

Reason:
CA Workload Automation SE is shutting down. The specified number of emails was
waiting to be sent, but have been discarded due to the shutdown.

Action:
None.

Chapter 2: AFM - CA7R Messages 163

CAL2 Messages

CAL2E024E

EMAIL PARMLIST INVALID - EMAIL NOT PROCESSED

Reason:
Program SASSETSK is unable to create a parameter block for program CAL2EML1. The
email is not sent.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2E025E

EMAIL KEYWORD xxxxxxxx VALUE IS TOO LONG--EMAIL DISABLED

Reason:
The specified keyword on the EMAIL initialization file statement has a value that is
longer than the maximum length allowed for that keyword. CA Workload Automation SE
continues to initialize, but the email interface will be disabled.

Action:
Correct the EMAIL initialization file statement and restart CA Workload Automation SE.

CAL2E026E

EMAIL SUBTASK taskname RETCODE=-xxxxxxxx ERRNO=xxxxxxxx

Reason:
The email subtask ended with the return code and error number shown.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2E027E

THIS VERSION OF TCPACCESS DOES NOT SUPPORT IPV6

Reason:
The email server specified has an IPv6 address and your version of TCPaccess does not
support IPv6. Email cannot be used.

Action:
Use an email server that has an IPv4 address or use a TCP/IP stack that supports IPv6.

164 Message Reference Guide

 CAL2 Messages

CAL2E028E

GETADDRINFO CALL FAILED

Reason:
CA Workload Automation SE was unable to determine the IP address of the system on
which CA Workload Automation SE is executing. The information is required when
communicating with the SMTP (email) server. CA Workload Automation SE does not
send the email.

Action:
Determine why the EZASMI GETADDRINFO call failed in the TCP/IP address space. If
necessary, you can turn on the CA Workload Automation SE email trace
(/EADMIN,TRC=Y) to obtain the actual return and reason codes returned from TCP/IP.

CAL2E117E

Unable to OPEN EVNTFILE

Reason:
CA7ONL requires an EVNTFILE DD statement. The OPTIONS statement specified
EVTBLDD=EVNTFILE. This feature requires an EVNTFILE DD statement in the CA7ONL JCL.
For more information about the Event File, see the Systems Programming Guide.

Action:
Correct the JCL and restart.

CAL2E118E

EVTBLDD=EVNTFILE but EVNTFILE not found

Reason:
CA7ONL requires an EVNTFILE DD statement. EVTBLDD=EVNTFILE was specified on the
OPTIONS statement. This feature requires an EVNTFILE DD statement in the CA7ONL
JCL. For more information about the Event File, see the Systems Programming Guide.

Action:
Correct the JCL and restart.

Chapter 2: AFM - CA7R Messages 165

CAL2 Messages

CAL2E119I

Found xxxxxxxx records on EVNTFILE

Reason:
xxxxxxxx records were found on the EVNTFILE at CA7ONL initialization. This count
includes a control record.

Action:
None.

CAL2E120E

Unable to acquire storage for CA7LOGIM

Reason:
Insufficient 31 bit storage was available for this operation.

Action:
Adjust the region parameter to ensure that CA7ONL has enough 31 bit storage and
restart CA7ONL. If the problem persists, contact CA Support at ca.com/support for
assistance.

CAL2E121E

Unable to acquire storage for EVTBLCPL

Reason:
Insufficient 31 bit storage was available for this operation.

Action:
Adjust the region parameter to ensure that CA7ONL has enough 31 bit storage and
restart CA7ONL. If the problem persists, contact CA Support at ca.com/support for
assistance.

166 Message Reference Guide

 CAL2 Messages

CAL2E122E

Invalid file format: EVNTFILE

Reason:
The Event File was not in the supported format.

Action:
Ensure the EVNTFILE DD statement is in the CA7ONL JCL and points to a valid Event File.
This file must be initialized using the SASSEFIN utility. For more information about the
Event File, see the Systems Programming Guide.

CAL2E123E

Nonzero return code from IARV64 GETSTOR; RC=xxxxxxxx, RS=yyyyyyyy

Reason:
Request for 64 bit storage failed.

Action:
Ensure that CA7ONL can acquire 64 bit storage and restart CA7ONL. If the problem
persists, contact CA Support at ca.com/support for assistance.

CAL2E125I

Latest event date/time : yyyy.ddd hh:mm:ss.th

Reason:
The latest event found on the Event File was recorded on the indicated date and time.

Action:
None.

CAL2E126I

Earliest event date/time : yyyy.ddd hh:mm:ss.th

Reason:
The earliest event found on the Event File was recorded on the indicated date and time.

Action:
None.

Chapter 2: AFM - CA7R Messages 167

CAL2 Messages

CAL2E127I

Table capacity: xxxxxxxx(yyyyyyyy) events

Reason:
The Event File is a wraparound file. The message reports xxxxxxxx, the total number of
writes to the Event File followed by yyyyyyyy, the maximum number of events that the
file can contain.

Action:
None.

CAL2E128I

Number of table writes: xxxxxxxx

Reason:
The Event File is a wraparound file. The message reports xxxxxxxx, the total number of
events currently written to the Event File.

Action:
None.

CAL2E129I

Number of table wraps: xxxxxxxx

Reason:
The Event File is a wraparound file. The message reports xxxxxxxx, the total number of
times the file has wrapped.

Action:
None.

168 Message Reference Guide

 CAL2 Messages

CAL2E130I

Found xxxxxxxx events on EVNTFILE

Reason:
xxxxxxxx records were found on the EVNTFILE at CA7ONL initialization. This count does
not include the control record.

Action:
None.

CAL2E131I

CA7LOGIM format successful; xxxxxxxx bytes acquired for table

Reason:
The message reports the number of bytes of 64 bit storage acquired for the event table
(in hex).

Action:
None.

CAL2E132E

Nonzero return code from IARV64 GETSTOR for table copy; RC=xxxxxxxx RS=yyyyyyyy

Reason:
CA7ONL cannot acquire sufficient 64 bit storage to initialize the event table.

Action:
Ensure that CA7ONL can acquire 64 bit storage for the event table and restart. If the
problem persists, contact CA Support at ca.com/support for assistance.

CAL2E133I

SASSEVCT ended

Reason:
SASSEVCT, the Event File update subtask, has ended.

Action:
None.

Chapter 2: AFM - CA7R Messages 169

CAL2 Messages

CAL2E134E

ATTACHX for SASSEVCT failed; R15(xxxxxxxx),R0(xxxxxxxx)

Reason:
CA7ONL cannot start SASSEVCT, the Event File update subtask.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2E135E

Unable to initialize SASSEVCT

Reason:
CA7ONL cannot start SASSEVCT, the Event File update subtask.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2E136I

Restarting SASSEVCT

Reason:
CA7ONL restarted SASSEVCT, the Event File update subtask.

Action:
None.

CAL2E137I

Initializing SASSEVCT

Reason:
The Event File update subtask, SASSEVCT is initializing.

Action:
None.

170 Message Reference Guide

 CAL2 Messages

CAL2E138I

SASSEVCT initialization complete

Reason:
The Event File update subtask initialization is complete.

Action:
None.

CAL2E139E

Unable to open EVNTFILE

Reason:
The Event File update subtask cannot open the Event File.

Note: For more information about the Event File, see the Systems Programming Guide.

Action:
Ensure that the EVNTFILE DD statement is in the CA7ONL JCL and points to a valid Event
File.

CAL2E140E

EVNTFILE invalid

Reason:
The Event File was not in the supported format.

Note: For more information about the Event File, see the Systems Programming Guide.

Action:
Ensure that the EVNTFILE DD statement is in the CA7ONL JCL and points to a valid Event
File. This file must be initialized using the SASSEFIN utility.

Chapter 2: AFM - CA7R Messages 171

CAL2 Messages

CAL2E141E

Unrecognized POST; EVTBLCPL_FLAG2=xx

Reason:
The Event File subtask received an unrecognized signal.

Action:
This condition is not expected in normal operation. For assistance, contact CA Support
at ca.com/support.

CAL2E142I

Terminating SASSEVCT

Reason:
The Event File subtask is ending.

Action:
None.

CAL2E144I

SASSEVCT does not support multiple invocations of recovery routine

Reason:
The Event File subtask recovery routine exceeded the limit on the number of retries.

Action:
None.

CAL2E145I

xxxxxxxx events to copy at termination

Reason:
The Event File subtask recovery routine found xxxxxxxx events to copy to the file.

Action:
None.

172 Message Reference Guide

 CAL2 Messages

CAL2E146E

ESTAEX failed; R15=xxxxxxxx, R0=xxxxxxxx

Reason:
The Event File subtask recovery environment cannot be established.

Action:
This condition is not expected in normal operation. For assistance, contact CA Support
at ca.com/support.

CAL2E147I

ESTAE entered; SDWA(xxxxxxxx) SDWAABCC(xxxxxxxx) SDWANXT1(xxxxxxxx)

Reason:
The Event File subtask recovery routine was entered.

Action:
None.

CAL2E148I

SASSEVCT terminating; forced by recovery

Reason:
The Event File subtask recovery routine has requested termination of the Event File
subtask.

Action:
None.

CAL2E149I

xxxxxxxx events to copy at ABTERM

Reason:
The Event File subtask recovery routine found xxxxxxxx events to copy at abnormal
termination.

Action:
None.

Chapter 2: AFM - CA7R Messages 173

CAL2 Messages

CAL2E150I

ESTAE entered; no SDWA R1=xxxxxxxx

Reason:
The Event File subtask recovery routine was entered.

Action:
None.

CAL2E151E

Recovery failed

Reason:
The Event File subtask recovery routine encountered a logic error.

Action:
This condition is not expected in normal operation. For assistance, contact CA Support
at ca.com/support.

CAL2E201E

Required SYSPRINT not found

Reason:
The SASSEFIN utility requires a SYSPRINT DD statement.

Note: For more information about SASSEFIN, see the Systems Programming Guide.

Action:
Add a DD statement for SYSPRINT and rerun the SASSEFIN utility.

CAL2E202E

Required EVNTFILE not found

Reason:
The SASSEFIN utility requires an EVNTFILE DD statement.

Note: For more information about SASSEFIN, see the Systems Programming Guide.

Action:
Add a DD statement for EVNTFILE and rerun the SASSEFIN utility.

174 Message Reference Guide

 CAL2 Messages

CAL2E203E

EVNTFILE improperly defined

Reason:
The Event File must be defined as one extent on a 3390 device.

Note: For more information about guidelines for the Event File, see the Systems
Programming Guide.

Action:
Correct the JCL and rerun the job.

CAL2E205E

Unable to OPEN SYSPRINT

Reason:
SASSEFIN requires that SYSPRINT be successfully opened for output processing.

Note: For more information about guidelines for the Event File, see the Systems
Programming Guide.

Action:
Correct the JCL and rerun the job.

CAL2E206E

Unable to OPEN EVNTFILE

Reason:
SASSEFIN requires that EVNTFILE be successfully opened for output processing.

Note: For more information about guidelines for the Event File, see the Systems
Programming Guide.

Action:
Correct the JCL and rerun the job.

Chapter 2: AFM - CA7R Messages 175

CAL2 Messages

CAL2E207E

EVNTFILE not single extent

Reason:
The Event File must be defined as one extent on a 3390 device.

Note: For more information about guidelines for the Event File, see the Systems
Programming Guide.

Action:
Correct the JCL and rerun the job.

CAL2E210I

EVNTFILE initialization complete

Reason:
The SASSEFIN utility has successfully initialized.

Action:
None.

CAL2E241E

Required SYSPRINT not found

Reason:
The SASSEVFE utility requires an SYSPRINT DD statement.

Note: For more information about SASSEVFE, see the Systems Programming Guide.

Action:
Add a DD statement for SYSPRINT and rerun the SASSEVFE utility.

176 Message Reference Guide

 CAL2 Messages

CAL2E242E

Required INTRVALS not found

Reason:
The SASSEVFE utility requires an INTRVALS DD statement.

Note: For more information about SASSEVFE and the allocation requirements for the
INTRVALS file, see the Systems Programming Guide.

Action:
Add a DD statement for INTRVALS and rerun the SASSEVFE utility.

CAL2E243E

Required LOGDATA not found

Reason:
The SASSEVFE utility requires a LOGDATA DD statement.

Note: For more information about SASSEVFE and the log data requirements for the
LOGDATA file, see the Systems Programming Guide.

Action:
Add a DD statement for LOGDATA and rerun the SASSEVFE utility.

CAL2E247E

Unable to OPEN SYSPRINT

Reason:
SASSEVFE requires that SYSPRINT is successfully opened for output processing.

Note: For more information about SASSEVFE, see the Systems Programming Guide.

Action:
Correct the JCL and rerun the job.

Chapter 2: AFM - CA7R Messages 177

CAL2 Messages

CAL2E248E

Unable to OPEN INTRVALS

Reason:
SASSEVFE requires that INTRVALS is successfully opened for output processing to create
the file.

Note: For more information about SASSEVFE, see the Systems Programming Guide.

Action:
Coorrect the JCL and rerun the job.

CAL2E249E

Unable to OPEN LOGDATA

Reason:
SASSEVFE requires that LOGDATA be successfully opened for input processing so that
log records can be processed.

Note: For more information about SASSEVFE, see the Systems Programming Guide.

Action:
Correct the JCL and rerun the job.

CAL2E251I

INTRVALS file created

Reason:
SASSEVFE created a file of interval records suitable for use with the SASSEVFF utility.

Action:
None.

178 Message Reference Guide

 CAL2 Messages

CAL2E252I

mmmmmmmm workload events found in nnnnnnnn log records

Reason:
SASSEVFE read nnnnnnnn log records from LOGDATA. Of these records, mmmmmmmm
were workload events.

Action:
None.

CAL2E253E

Required SYSPRINT not found

Reason:
The SASSEVFF utility requires an SYSPRINT DD statement.

Note: For more information about the SASSEVFF utility, see the Systems Programming
Guide.

Action:
Add a DD statement for SYSPRINT and rerun.

CAL2E254E

Required INTRVALS not found

Reason:
The SASSEVFF utility requires an INTRVALS DD statement.

Note: For more information about SASSEVFF and the allocation requirements for the
INTRVALS file, see the Systems Programming Guide.

Action:
Add a DD statement for INTRVALS and rerun the SASSEVFF utility.

Chapter 2: AFM - CA7R Messages 179

CAL2 Messages

CAL2E255E

Required module SASSSDTR not found

Reason:
The SASSEVFF utility failed to load the SASSSDTR module.

Note: For more information about SASSEVFF, see the Systems Programming Guide.

Action:
Ensure that the SASSSDTR module is included in the load library concatenation. Make
the necessary corrections and rerun the job.

CAL2E256E

Unable to OPEN SYSPRINT

Reason:
SASSEVFF requires that SYSPRINT is successfully opened for output processing.

Note: For more information about SASSEVFF, see the Systems Programming Guide.

Action:
Correct the JCL and rerun the job.

CAL2E257E

Unable to OPEN INTRVALS

Reason:
SASSEVFF requires that INTRVALS is successfully opened for input processing.

Note: For more information about SASSEVFF, see the Systems Programming Guide.

Action:
Correct the JCL and rerun the job.

180 Message Reference Guide

 CAL2 Messages

CAL2E258E

Error processing INTRVALS

Reason:
SASSEVFF cannot process the INTRVALS file. The problem is typically a result of
insufficient storage.

Note: For more information about SASSEVFF, see the Systems Programming Guide.

Action:
Change the region specification to Increase the storage available to the program if
indicated and rerun the job.

CAL2E259E

mmmmmmmm samples selected out of nnnnnnnn total samples

Reason:
SASSEVFF used mmmmmmmm samples to determine the interval with the greatest
number of events. The total number of samples evaluated was nnnnnnnn.

Action:
None.

CAL2E260E

Unable to determine maximum event interval

Reason:
SASSEVFF cannot determine the interval with the greatest number of events. The
INTRVALS file might not contain enought samples to determine the interval specified.

Note: For more information about SASSEVFE and SASSEVFF, see the Systems
Programming Guide.

Action:
Reduce the requested interval length or rerun SASSEVFE to create an INTRVALS file with
a greater number of samples.

Chapter 2: AFM - CA7R Messages 181

CAL2 Messages

CAL2E261I

mmmmmmmm events between yyyy.ddd hh:mm:ss:thijk and yyyy.ddd hh:mm:ss:thijk

Reason:
SASSEVFF found the highest number of events for the requested duration within the
interval specified in the message.

Note: For more information about SASSEVFF, see the Systems Programming Guide.

Action:
None.

CAL2E262E

Invalid value for NNHRS

Reason:
The parameter value for SASSEVFF must be nnHRS where nn is between 01 through 99.

Note: For more information about using SASSEVFF, see the Systems Programming
Guide.

Action:
Correct the JCL and rerun the job.

CAL2E263I

mmmmmmmm Event File tracks required

Reason:
SASSEVFF calculated the number of Event File tracks needed to accommodate the event
count in the CAL2E261I message.

Note: For more information about using SASSEVFF to size the Event File, see the
Systems Programming Guide.

Action:
None.

182 Message Reference Guide

 CAL2 Messages

CAL2FTXMI

CAL2FTXM entered OT adr/len xxxxxxxx/yyyyyyyy CT adr/len zzzzzzzz/wwwwwwww t

Reason:
Program CAL2FTXM has started processing. The object table address and length at entry
were xxxxxxxx and yyyyyyyy, respectively. The connection table address and length at
entry were zzzzzzzz and wwwwwwww, respectively. The type of table, t, is O for
expanding the object table and C for expanding the connection table.

Action:
None.

CAL2F10BI

Table building started

Reason:
Program CAL2FSIM has started the table building process.

Action:
None.

CAL2F10CI

Command processing started

Reason:
Program CAL2FSIM has started processing commands.

Action:
None.

CAL2F10EI

Exit processing started

Reason:
Program CAL2FSIM has started exit processing for a program call other than a
termination call.

Action:
None.

Chapter 2: AFM - CA7R Messages 183

CAL2 Messages

CAL2F10TI

Termination started

Reason:
Program CAL2FSIM has started termination processing.

Action:
None.

CAL2F100I

Jobflow Illustrator has started processing

Reason:
Jobflow Illustrator has started processing in simulation mode. This message is a WTO.

Action:
None.

CAL2F101F

SYSMSGS data set did not open

Reason:
The required SYSMSGS data set did not open. SYSMSGS is the data set to which
messages are written. This message is a WTO.

Action:
Ensure there is a SYSMSGS DD in your batch job or that the calling job or session
provides an area for the SYSMSGS data set. Next, resubmit the job or reissue the
command.

184 Message Reference Guide

 CAL2 Messages

CAL2F102F

Unknown program call. Parmlist is invalid. See R4.

Reason:
CA Workload Automation SE Jobflow Illustrator simulation mode driver program
CAL2FSIM was called by a program. The parmlist passed by the program was not a valid
parmlist in a format expected by CAL2FSIM. CAL2FSIM could not determine the type of
program call to process. This message was followed by a U0102 abend. The address of
the parmlist was saved in register 4.

Action:
Correct any errors in the parmlist generated by the calling program and rerun the
program.

CAL2F103I

CAL2FSIM Jobflow Illustrator has completed processing

Reason:
Jobflow Illustrator simulation mode has terminated processing.

Action:
None.

CAL2F104C

SVINIT bad init, rc= xxxxxxxx, rsn code= yyyyyyyy

Reason:
The initialization of the Jobflow Illustrator simulation mode driver program CAL2FSIM
failed. Programs and parameters required to continue execution could not be initialized.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 185

CAL2 Messages

CAL2F105C

SVCONN connection to CA 7 failed, return code= xxxxxxxx

Reason:
The Jobflow Illustrator simulation mode driver program CAL2FSIM could not connect to
the CA Workload Automation SE database.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F106I

Jobflow Illustrator built xxxxxxxxx job and yyyyyyyyy data set objects

Reason:
The Jobflow Illustrator simulation mode driver program CAL2FSIM built the number and
type of objects specified in its internal tables.

Action:
None.

CAL2F107E

DDname DBPARMS is DUMMY and cannot be allocated dynamically

Reason:
The Jobflow Illustrator simulation mode driver program CAL2FSIM attempted to allocate
the data set associated with the CA Workload Automation SE DBPARMS DD statement,
but the JCL for Jobflow Illustrator has the DBPARMS DD statement dummied out. The
dynamic allocation cannot occur.

Action:
Either remove the DBPARMS DD statement from the CA Workload Automation SE
Jobflow Illustrator JCL or replace it with one that contains a valid data set name.

186 Message Reference Guide

 CAL2 Messages

CAL2F108E

Dynamic alloc of SYSMSGS failed; rc=xxxxxxxx, rsn=yyyyyyyy

Reason:
Program CAL2FSIM was unable to dynamically allocate the data set associated with the
ddname of SYSMSGS. The DAIR return code was xxxxxxxx and the reason code was
yyyyyyyy.

Action:
Determine the reason for the failure and fix the cause. Then reissue the command. If
necessary, add a //SYSMSGS DD statement to your JCL.

CAL2F109E

Global address not found. Retry.

Reason:
An internal error occurred that caused the connection to be dropped. A new connection
will be established, and that should correct the problem.

Action:
Retry the action. If it does not work, contact your installation specialist for assistance.

CAL2F120W

No input jobs received for processing

Reason:
No jobs were specified to be processed. The issuing program is CAL2FTBS.

Action:
Ensure that at least one valid JOB statement is present in the PARMDEF file. Next,
resubmit the job or reissue the command.

Chapter 2: AFM - CA7R Messages 187

CAL2 Messages

CAL2F121C

Errors in retrieving data from CA 7; stopping execution

Reason:
Program CAL2FTBS received a nonzero return from the CA Workload Automation SE
CAICCI interface. One or more previous error messages detailed the errors. Jobflow
Illustrator terminated processing.

Action:
Follow the actions specified for the previous error messages.

CAL2F122E

Length error detected in xxxxxxxx; stopping execution

Reason:
Program CAL2FTBS could not process field xxxxxxxx because of a length error.

Action:
Contact your installation specialist for assistance.

CAL2F123E

CCI exit error: storage obtain failure

Reason:
Program CAL2FTBS encountered an internal error.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F124E

Storage obtain failure for CCI work area; stopping execution

Reason:
Program CAL2FTBS was unable to obtain storage for a work area.

Action:
Contact your installation specialist for assistance.

188 Message Reference Guide

 CAL2 Messages

CAL2F125E

Length error detected in input job name jjjjjjjj. Bypassing.

Reason:
Program CAL2FTBS encountered an unexpected length of a job whose name starts with
jjjjjjjj. Forecasting for this job, and any jobs or data sets triggered by this job, was
bypassed.

Action:
Contact your installation specialist for assistance.

CAL2F126W

Error return from forecast routine; stopping execution

Reason:
Program CAL2FTBS received an error return code from forecast job object routine
CAL2FOTJ and stopped processing.

Action:
Review the SYSMSGS file for any previous error messages and take appropriate action.

CAL2F127E

Julian date error; unable to map Greg date; execution halted

Reason:
Program CAL2FTBS encountered an error in a Julian date.

Action:
Contact your installation specialist for assistance.

CAL2F128E

No processing routine for CA 7 command entered

Reason:
Program CAL2FTBS encountered an internal error.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 189

CAL2 Messages

CAL2F129E

No data returned from CCI command execution. Stopping.

Reason:
Program CAL2FTBS queried the CA Workload Automation SE database to set up a
workflow. However, no data was returned.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F130E

CCI exit routine encountered error xxxx; halting execution

Reason:
Program CAL2FTBS received error code xxxx during a CAICCI operation.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F131E

CCI interface returned error: text

Reason:
Program CAL2FTBS received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. The return code was 8, and the reason code is
specified by text.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

190 Message Reference Guide

 CAL2 Messages

CAL2F132E

CCI interface abended with error xxxx; terminating execution

Reason:
Program CAL2FTBS received abend code xxxx during a CAICCI operation.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F133E

Parm list error between CAL2FTBS and CCI interface. Stopping.

Reason:
Program CAL2FTBS received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. The return code was 16, signifying an internal error
in a parameter list built by CAL2FTBS.

Action:
Contact your installation specialist for assistance.

CAL2F134E

Forecast command processor received no FROM= date info

Reason:
Program CAL2FTBS was expecting a FROM date to use when building the workflow. If a
FROM statement was not coded in the PARMDEF file, the current date should have been
used as the default. No date information was received, and processing terminated.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 191

CAL2 Messages

CAL2F135E

CA 7 logon failure: text

Reason:
Program CAL2FTBS received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. A description of the reason is shown in text.
Processing terminates.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F136E

Build failed because of command security

Reason:
Program CAL2FTBS received an error return code from an FJOB command because the
user ID did not have command authority to issue the command.

Action:
Ensure that the ID used to log on to CA Workload Automation SE Jobflow Illustrator has
command authority.

CAL2F170I

text

Reason:
text is the image of an INITDEF or PARMDEF record. If longer than 80 bytes, it is split
into 80-byte segments. The issuing program is CAL2FPRM.

Action:
None.

192 Message Reference Guide

 CAL2 Messages

CAL2F171E|C

Parm is invalid at text

Reason:
Program CAL2FPRM encountered an invalid keyword or value while parsing a parameter
string. Text gives an indication where the parameter is invalid.

Action:
Correct the keyword, the value, or both and resubmit the job or reissue the command.

CAL2F172C

Parentheses are unbalanced

Reason:
Program CAL2FPRM encountered an unbalanced set of parentheses while parsing a
parameter string.

Action:
Correct the parameter string and resubmit the job or reissue the command.

CAL2F173C

Parmlist is invalid. Eyecatcher is not "FINT" or "FBLD".

Reason:
CA Workload Automation SE Jobflow Illustrator is being called programmatically. On an
initialization call, the parmlist must begin with the eyecatcher FINT. On a table building
call, the parmlist must begin with the eyecatcher FBLD. Program CAL2FTBS could not
determine the type of program call because the parmlist did not begin with one of the
specified eyecatchers.

Action:
Ensure the parmlists are correct for each type of program call if you are the programmer
of the calling program. If you are not the programmer, contact your installation
specialist for assistance.

Chapter 2: AFM - CA7R Messages 193

CAL2 Messages

CAL2F174E

kkkkkkkk field is not a valid date/time

Reason:
A keyword field that should be in date/time format is not a valid date or time. The name
of the keyword is kkkkkkkk. The issuing program is CAL2FPRM.

Note: Most CA Workload Automation SE Jobflow Illustrator PARMDEF date/time

keywords are in the format (mmddyy,hhmm).

Action:
Ensure the value for the keyword is a valid date/time and also in the correct format.

CAL2F175E

JOB= is invalid when specifying EXTRACT=NO

Reason:
EXTRACT=NO is a parameter that indicates the user wants to start with an empty
workflow and manually add jobs or data sets. It is mutually exclusive to specify a JOB
keyword with this option.

Action:
Either remove the JOB keyword or specify EXTRACT=YES. Then resubmit the job or
reissue the command.

CAL2F176E

Error building tablename

Reason:
Program CAL2FPRM encountered an error while building internal table tablename. The
name of the table is either object or connection.

Action:
Contact your installation specialist for assistance.

194 Message Reference Guide

 CAL2 Messages

CAL2F177E

Invalid format for pppppppppp parameter

Reason:
Program CAL2FPRM attempted to parse parameter pppppppppp and was unable to do
so because the format was incorrect.

Action:
Correct the parameter and resubmit the job or reissue the command.

CAL2F178E

Value must be between 0 and 255

Reason:
Program CAL2FPRM encountered a value that was out of range for a keyword.

Action:
Review the SYSMSGS file for an earlier error message to identify the keyword in error.
Replace the value with a value in the range listed in the message text and resubmit the
job or reissue the command.

CAL2F179E

Maximum of 10 list items exceeded

Reason:
Program CAL2FPRM encountered a list with more than 10 values.

Action:
Decrease the number of values in the list to no more than 10 items. Then resubmit the
job or reissue the command.

Chapter 2: AFM - CA7R Messages 195

CAL2 Messages

CAL2F180C

dddddddd data set did not open correctly

Reason:
Program CAL2FPRM attempted to open data set with a ddname of dddddddd. The data
set did not open correctly. Jobflow Illustrator was run as a batch job or started task, and
dddddddd is either INITDEF or PARMDEF.

Action:
Ensure your JCL is correct and that the data set is correctly defined. Then resubmit the
job or started task.

CAL2F181E

Either SPAN= or TO= must be specified, but not both

Reason:
Program CAL2FPRM encountered both keywords SPAN and TO. The keywords are
mutually exclusive.

Action:
Remove one of the keywords and resubmit the job or reissue the command.

CAL2F182C

Default logon undetermined. Rerun specifying the LOGON parm.

Reason:
If the LOGON parameter is omitted, program CAL2FPRM attempts to determine the user
ID of the submitter. In this case, the attempt was unsuccessful and processing
terminated.

Action:
Rerun the job or reissue the command specifying the LOGON keyword in the INITDEF
file. Depending on your installation, a CA7PASS keyword may also be necessary.

196 Message Reference Guide

 CAL2 Messages

CAL2F183E

Parm has no value specified

Reason:
Program CAL2FPRM encountered a parameter keyword with no matching value.

Action:
Determine which keyword is in error using the messages in the SYSMSGS file. Add an
appropriate value to the keyword and resubmit the job or reissue the command.

CAL2F184E

The maximum number allowed is 10000000

Reason:
Program CAL2FPRM encountered a value that was out of range for a keyword.

Action:
Review the SYSMSGS file for an earlier message to identify the keyword in error.
Replace the value with a value in the range listed in the message text and resubmit the
job or reissue the command.

CAL2F185E

List contains no data

Reason:
Program CAL2FPRM encountered an empty list.

Action:
Perform the following actions:
■ Review the SYSMSGS file for an earlier message to identify the keyword in error.
■ Choose one of the following actions:
■ Place values within the parentheses.
■ Replace the list with a single value.
■ Resubmit the job or reissue the command.

Chapter 2: AFM - CA7R Messages 197

CAL2 Messages

CAL2F186E

Error calculating span

Reason:
Program CAL2FPRM was unable to calculate the span using the FROM and TO dates.

Action:
Contact your installation specialist for assistance.

CAL2F187E

Error calculating TO date

Reason:
Program CAL2FPRM was unable to calculate the TO date using the FROM date and
SPAN.

Action:
Contact your installation specialist for assistance.

CAL2F188E

Span cannot exceed 168 hours or one week

Reason:
Program CAL2FPRM encountered a FROM and TO date range that spanned more than
one week (168 hours).

Action:
Rerun the job or reissue the command with a different set of dates that are less than
one week apart.

CAL2F189E

FROM D/T is not earlier than TO D/T

Reason:
Program CAL2FPRM encountered a date and time on the FROM= keyword that was not
earlier than the date and time on the TO= keyword.

Action:
Change the date/time group on either or both keywords and resubmit the job.

198 Message Reference Guide

 CAL2 Messages

CAL2F19AI

Expanding tttttttttt table to xxxxxxxx hex bytes

Reason:
The CA Workload Automation SE Jobflow Illustrator internal table of type tttttttt ran out
of space. Program CAL2FTXM automatically rebuilt the table with a new size of xxxxxxxx.

Action:
None.

CAL2F190F

Could not increase table size

Reason:
Program CAL2FTXM attempted to increase the size of an internal table but was
unsuccessful. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F195E

Use parameter SIZE=PPPPPP. ttttttt table has over eeeeeee elements.

Reason:
While building the flow, the ttttttt table has grown too large for the SIZE parameter
specified during initialization (the default is SMALL). If ttttttt is OBJECT, the flow
contains at least eeeeeee jobs and data sets at this point. If ttttttt is CONNECT, the flow
contains at least eeeeeee connections at this point. Jobflow Illustrator terminates with
return code 8.

Note: PPPPPP is either MEDIUM or LARGE. As a guide, use SIZE=MEDIUM for flows that
will comprise between 10,000 and 100,000 jobs. Use SIZE=LARGE for flows over 100,000
jobs.

Action:
Rerun the job, using the SIZE initialization parameter in the message.

Chapter 2: AFM - CA7R Messages 199

CAL2 Messages

CAL2F20AI

(Re)chaining tttttttttt table

Reason:
Program CAL2FCHN chained together the free slots in the tttttttttt table.

Action:
None.

CAL2F200E

Table address 0 during rechain of xxxxxxxxxx table

Reason:
Program CAL2FCHN attempted to rechain the pointers in the xxxxxxxxxx table, but it
could not find the table because of an internal error. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F201F

xxxxxxxxxx header/global mismatch. Abending U0201.

Reason:
Program CAL2FCHN attempted to chain the pointers in the xxxxxxxxxx table, but there
was a mismatch between data in the table header and the Jobflow Illustrator global
data area. Processing terminates with a user abend U0201.

Action:
Contact your installation specialist for assistance.

CAL2F202F

xxxxxxxxxx table row sequence error. Abending U0202.

Reason:
Program CAL2FCHN attempted to chain the pointers in the xxxxxxxxxx table, but the row
numbers in the table were out of sequence. Processing terminates with a user abend
U0202.

Action:
Contact your installation specialist for assistance.

200 Message Reference Guide

 CAL2 Messages

CAL2F210W

Date/time field is not numeric

Reason:
Program CAL2FTIM encountered a date/time field that was not numeric. Processing
continues, but the date/times for this object are not recalculated. This message is
followed by Message CAL2F214I.

Action:
None, unless this becomes a problem. In that case, contact your installation specialist
for assistance.

CAL2F211W

Field is not a valid date

Reason:
Program CAL2FTIM encountered a date field that was not a valid date. Processing
continues, but the date/times for this object are not recalculated. This message is
followed by Message CAL2F214I.

Action:
None, unless this becomes a problem. In that case, contact your installation specialist
for assistance.

CAL2F212W

Field is not a valid time

Reason:
Program CAL2FTIM encountered a time field that was not a valid time. Processing
continues, but the date/times for this object are not recalculated. This message is
followed by Message CAL2F214I.

Action:
None, unless this becomes a problem. In that case, contact your installation specialist
for assistance.

Chapter 2: AFM - CA7R Messages 201

CAL2 Messages

CAL2F213E

Invalid function call

Reason:
Program CAL2FTIM encountered an internal error. Processing terminates. This message
is followed by Message CAL2F214I.

Action:
Contact your installation specialist for assistance.

CAL2F214I

P1=nn, P2=parm2, P3=parm3, PGM=xxxxxxxx, WIP=w[, JOB=jobname|, DSN=dsn]

Reason:
Program CAL2FTIM was passed an invalid parameter. The first parameter, nn, is a
function code. The second parameter, parm2, should be a date/time in the form
yyyydddshhmm. The third parameter, parm3, should be a hexadecimal number if P1 is
00 or 04 or a date/time if P1 is 08. PGM shows the calling program and WIP is a where in
(calling) program indicator. If a job or data set is associated with the date/time, its name
is displayed. If P1=08, the job or data set may relate to either parm2 or parm3. The WIP
indicator is necessary to determine which one.

Action:
None.

CAL2F220E

Unable to open checkpoint file DDNAME=xxxxxxxx

Reason:
Program CAL2FCKR was unable to open the checkpoint file on a TYPE=CKPT start. The
ddname of the file is xxxxxxxx. Processing terminates.

Action:
Ensure the JCL has a valid DD record named xxxxxxxx and that it defines the input
checkpoint file. Then resubmit the job.

202 Message Reference Guide

 CAL2 Messages

CAL2F221E

First checkpoint record is not the checkpoint header

Reason:
In reading the checkpoint file, program CAL2FCKR determined that the first record of
the file was not a valid header record. Processing terminates.

Action:
Validate that the file being read was created by CA Workload Automation SE Jobflow
Illustrator as the result of a SAVE command. The eyecatcher of the first record should be
@L2FCKHD in the first eight positions. If the file was correctly created and the
eyecatcher is incorrect, or the eyecatcher is correct and this message has been
generated, contact your installation specialist for assistance.

CAL2F222I

Checkpoint taken date time

Reason:
Program CAL2FCKR has read a checkpoint file that was originally written out at time on
date. Date is in the Julian format yyyyddd. Time is in the format hh.mm.ss.dddd, where
dddd is fractions of a second.

Action:
None.

CAL2F223E

Global in checkpoint is xxxx, expected yyyy

Reason:
Program CAL2FCKR was attempting to read a checkpoint file that was incompatible with
the current level of CA Workload Automation SE Jobflow Illustrator. The current level
was yyyy, and the level that created the checkpoint file was xxxx. Processing terminates.

Action:
Contact your installation specialist for assistance if you think that this message was
issued in error.

Chapter 2: AFM - CA7R Messages 203

CAL2 Messages

CAL2F224I

From checkpoint file: text

Reason:
This message is issued by program CAL2FCKR to display parameters and their values that
were saved in the checkpoint file and are being restored during a TYPE=CKPT start. Text
is typically a keyword and value pair, for example, CA7=CA71.

Action:
None.

CAL2F225I

Checkpoint file read: datasetname

Reason:
Program CAL2FCKR has read the checkpoint file from data set datasetname.

Action:
None.

CAL2F240E

Unable to open checkpoint file DDNAME=xxxxxxxx

Reason:
Program CAL2FCKW attempted to write a checkpoint file to a data set at ddname
xxxxxxxx, but the file could not be opened.

Action:
Ensure that a DD record of xxxxxxxx exists in the JCL and that it points to a valid output
file with the correct DCB attributes for a CA Workload Automation SE Jobflow Illustrator
checkpoint file. Then resubmit the job or reissue the command.

CAL2F241I

CHKPOINT data written to DSN datasetname

Reason:
Program CAL2FCKW has written a checkpoint file to data set datasetname.

Action:
None.

204 Message Reference Guide

 CAL2 Messages

CAL2F260E

Error rechaining the connection table

Reason:
After program CAL2FCHN rechained an internal table, program CAL2FCON encountered
an error while trying to use the table. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F261E

Zero table address on connection add attempt

Reason:
Program CAL2FCON attempted to use an internal table, but it could not find the table
because of an internal error. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F271W

Unable to obtain xxxx lock word. Lock being forced (LOC/CUR)

Reason:
Message writing program CAL2FMSG was unable to obtain a lock against the SYSMSGS
data set. xxxx is the lock title, LOC is the task ID of the owner task, and CUR is the task ID
of the current task. This message is issued as a WTO if the program has to wait three
seconds. Because the program waits until it eventually gets the lock and writes the
message, no data was lost.

Action:
None.

Chapter 2: AFM - CA7R Messages 205

CAL2 Messages

CAL2F280E

Dynamic alloc of DBPARMS failed; rc=xxxxxxxx, rsn=yyyyyyyy

Reason:
Program CAL2FDBP was unable to dynamically allocate the data set associated with the
ddname of DBPARMS. The DAIR return code was xxxxxxxx and the reason code was
yyyyyyyy.

Action:
Determine the reason for the failure and fix the cause. Then resubmit the job or reissue
the command. If necessary, add a valid DBPARMS DD statement to your CA Workload
Automation SE Jobflow Illustrator JCL.

CAL2F281E

Storage obtain failure for CCI work area; stopping execution

Reason:
Program CAL2FDBP was unable to obtain storage for a work area.

Action:
Contact your installation specialist for assistance.

CAL2F282E

Length error detected in xxxxxxxx; stopping execution

Reason:
Program CAL2FDBP could not process field xxxxxxxx because of a length error.

Action:
Contact your installation specialist for assistance.

CAL2F283E

CCI exit error: storage obtain failure

Reason:
Program CAL2FDBP encountered an internal error.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

206 Message Reference Guide

 CAL2 Messages

CAL2F284E

CA 7 logon failure: text

Reason:
Program CAL2FDBP received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. A description of the reason is shown in text.
Processing terminates.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F285E

No data returned from CCI command execution; stopping execution

Reason:
Program CAL2FDBP queried the CA Workload Automation SE database to determine
DBPARMS data. However, no data was returned.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F286E

CCI exit routine encountered error xxxx; stopping execution

Reason:
Program CAL2FDBP received error code xxxx during a CAICCI operation.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 207

CAL2 Messages

CAL2F287E

CCI interface returned error: text

Reason:
Program CAL2FDBP received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. The return code was 8, and the reason code is
specified by text.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F288E

CCI interface abended with error xxxx; stopping execution

Reason:
Program CAL2FDBP received abend code xxxx during a CAICCI operation.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F289E

Parm list error between CAL2FDBP and CCI interface. Stopping.

Reason:
Program CAL2FDBP received an error return code from the CA Workload Automation SE
CAICCI interface module CAL2X2W0. The return code was 16, signifying an internal error
in a parameter list built by CAL2FDBP.

Action:
Contact your installation specialist for assistance.

208 Message Reference Guide

 CAL2 Messages

CAL2F290E

Unable to allocate DBPARMS DD

Reason:
Program CAL2FDBP issued a /DISPLAY,DB=VSAM command but could not determine the
name of the DBPARMS data set to allocate.

Note: Dynamic allocation of DBPARMS is available only if the instance of CA Workload

Automation SE being modeled by Jobflow Illustrator is running at level r11.1 or higher.
This message is received if the instance of CA Workload Automation SE does not support
dynamic allocation of DBPARMS and in other circumstances.

Action:
Contact your installation specialist for assistance.

CAL2F291E

DBPARMS is a SYSIN data set. Unable to allocate.

Reason:
Program CAL2FDBP can dynamically allocate the CA Workload Automation SE DBPARMS
data set only if it is a permanent data set residing on DASD.

Action:
Either make the CA Workload Automation SE DBPARMS data set a permanent data set
or place a DBPARMS DD statement in your CA Workload Automation SE Jobflow
Illustrator JCL.

CAL2F292E

Error calculating length of DBPARMS data set

Reason:
Program CAL2FDBP encountered an internal error.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 209

CAL2 Messages

CAL2F293E

DDname xxxxxxxx DSN datasetname must be specified in the JCL

Reason:
Program CAL2FDBP determined that data set datasetname with ddname xxxxxxxx in the
DBPARMS data set is identified as ALLOCJCL and is dummied out in the JCL. The data set
cannot be allocated dynamically.

Action:
Ensure the data set is correctly specified in the CA Workload Automation SE Jobflow
Illustrator JCL.

CAL2F300C

Unable to load program xxxxxxxx

Reason:
Program CAL2FLDS was unable to load program xxxxxxxx.

Action:
Ensure program xxxxxxxx is either in a STEPLIB library or in a linklist library. Then
resubmit the job or reissue the command.

CAL2F31AI

Deleting job jjjjjjjj sss start ddddddd tttt fuzz fff

Reason:
Program CAL2FDLO is deleting job jjjjjjjj with SCHID sss whose start date/time is
ddddddd tttt with a fuzz (plus/minus time) of fff minutes.

Action:
None.

210 Message Reference Guide

 CAL2 Messages

CAL2F31BI

Matched job jjjjjjjj sss start ddddddd tttt end ddddddd tttt

Reason:
Program CAL2FDLO has matched a job to the delete criteria specified on the DELJOB
command. The job name is jjjjjjjj and SCHID is sss. The start and end date/times are
shown in the message.

Action:
None.

CAL2F31CI

Processing level xxxxx job jjjjjjjj sss ddddddd tttt

CAL2F31CI

Processing level xxxxx dsn datasetname sss ddddddd tttt

Reason:
Program CAL2FDLO is delete processing the job or data set shown in the message. The
recursion level is xxxxxx. The SCHID is sss and the object's start date/time is dddddddd
and tttt.

Action:
None.

CAL2F31DI

Second loop lvl xxxxxx. Triggers job jjjjjjjj sss ddddddd tttt

CAL2F31DI

Second loop lvl xxxxxx. Triggers dsn datasetname sss ddddddd tttt

Reason:
Program CAL2FDLO continues to process and has found a job or data set that is
triggered and that will be deleted. The job or data set is identified in the message.

Action:
None.

Chapter 2: AFM - CA7R Messages 211

CAL2 Messages

CAL2F31EI

Job jjjjjjjj sss ddddddd tttt is not a requirement connection. Reprocessing triggers.

Reason:
Program CAL2FDLO found a trigger connection where there should be none. The
program reprocesses triggers to see whether to delete any other jobs or data sets.

Action:
None.

CAL2F31FI

First loop lvl xxxxxx. jjjjjjjj sss ddddddd tttt

CAL2F31FI

First loop lvl xxxxxx. datasetname sss ddddddd tttt

Reason:
Program CAL2FDLO is processing a job or data set that will be deleted. The job or data
set is identified in the message.

Action:
None.

CAL2F31GI

Deleted objectname

Reason:
Program CAL2FDLO deleted the named object from the workflow internal tables.

Action:
None.

212 Message Reference Guide

 CAL2 Messages

CAL2F310E

No start or end date

Reason:
Program CAL2FDLO expects either a start or an end date with the DELJOB command. No
date is supplied. Processing terminates with return code 8.

Action:
Resubmit the job or reenter the command with either a start date or an end date, but
not both for the DELJOB command.

CAL2F311E

Bad build of job delete table

Reason:
Program CAL2FDLO encountered an error while creating an internal table. The DELJOB
process cannot continue. Processing terminates with return code 8.

Action:
Contact your installation specialist for assistance.

CAL2F312E

Multiple jobs met criteria. Narrow the limits.

Reason:
Program CAL2FDLO could not determine which one job to delete because more than
one job met the criteria on the DELJOB command.

Action:
Change the specification criteria. If you are using FUZZ, lower the number of minutes
specified, ensuring that the start/end date/time is close to the job you want to delete.

Chapter 2: AFM - CA7R Messages 213

CAL2 Messages

CAL2F313E

Bad build of job delete table

Reason:
Program CAL2FDLO encountered an error while creating an internal table. The DELJOB
process cannot continue. Processing terminates with return code 8.

Action:
Contact your installation specialist for assistance.

CAL2F314E

No job meets the delete criteria

Reason:
Program CAL2FDLO could not match a specific job to the criteria specified on the
DELJOB command. Processing terminates with return code 8.

Action:
Examine the specification criteria, ensuring that the job name and SCHID are correct.
Use the FUZZ keyword or expand the number of minutes if you are already using it.
Ensure the start/end date/time you specify is near the time of the job you are
attempting to delete.

CAL2F315W

Is a prerequisite and is made a soft object: objectname

Reason:
Program CAL2FDLO did not delete the named object because it is a prerequisite for
another job or data set. The named object has been converted to a soft object.

Action:
None.

214 Message Reference Guide

 CAL2 Messages

CAL2F317I

Workflow total xxxxxxxxx job and yyyyyyyyy data set objects. Some may be in delete
status.

Reason:
Program CAL2FDLO counted the number and type of objects specified in its internal
tables. This may not be the number of objects that appear on a flowchart.

Action:
None.

CAL2F320E

Zero table address on data set add

Reason:
Program CAL2FOTD attempted to use an internal table, but it could not find the table
because of an internal error. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F321W

Begin D/T for datasetname set to creation D/T

Reason:
In calculating a workflow, program CAL2FOTJ could not calculate a begin date/time for a
data set. The begin date/time was set equal to the creation date/time for the data set.

Action:
None.

CAL2F322E

Error rechaining the object table

Reason:
After program CAL2FCHN rechained an internal table, program CAL2FOTD encountered
an error while trying to use the table. Processing terminates.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 215

CAL2 Messages

CAL2F323W

End date/time field for datasetname invalid. Record skipped.

Reason:
In calculating a workflow, program CAL2FOTJ encountered an end date/time field that
could not be processed for data set datasetname in an internal table. The record is
skipped and processing continues.

Action:
None.

CAL2F324E

Invalid function

Reason:
Program CAL2FOTD encountered an internal error.

Action:
Contact your installation specialist for assistance.

CAL2F33AI

Connecting hard type objectname sss ddddddd tttt to objectname sss ddddddd tttt
[xxxxxx]

Reason:
Program CAL2FSCH has previously disconnected the first object from a soft object and is
now connecting it to a hard object in place of the soft object. objectname is the object
name, sss is the SCHID, ddddddd is the date, and tttt is the time. type is either dsn or
job. If the connection is a conditional or negative dependency, xxxxxx is CONDEP or
NEGDEP, respectively. Only the last 16 characters of the data set name are displayed.

Action:
None.

216 Message Reference Guide

 CAL2 Messages

CAL2F331W

Error processing soft object internal table

Reason:
The number of soft objects to be attached to a particular object has exceeded an
internal limit. The soft object under consideration is dropped and is not added to the
flow.

Action:
None.

CAL2F340E

Zero table address on job add

Reason:
Program CAL2FOTJ attempted to use an internal table, but it could not find the table
because of an internal error. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F341E

Date field is not a valid date - ddddd

Reason:
Program CAL2FOTJ encountered a date field ddddd that was not in correct Julian format
yyddd. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F342E

Time field is not a valid time - tttt

Reason:
Program CAL2FOTJ encountered a time field ttttt that was not a valid time in the format
hhmm (24-hour clock). Processing terminates.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 217

CAL2 Messages

CAL2F343E

Schedule ID field is not numeric - nnnnn

Reason:
Program CAL2FOTJ encountered a schedule ID field nnnnn that was not numeric.
Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F344E

Lead time field is invalid - nn

Reason:
Program CAL2FOTJ encountered a lead time field nn that was not numeric. Processing
terminates.

Action:
Contact your installation specialist for assistance.

CAL2F345E

Error building repeat information for job jjjjjjjj

Reason:
In building a workflow for repeat job jjjjjjjj, program CAL2FOTJ encountered one or more
numeric fields that could not be processed because they were not numeric. Processing
terminates.

Action:
Contact your installation specialist for assistance.

CAL2F346E

Error rechaining the object table

Reason:
After program CAL2FCHN rechained an internal table, program CAL2FOTJ encountered
an error while trying to use the table. Processing terminates.

Action:
Contact your installation specialist for assistance.

218 Message Reference Guide

 CAL2 Messages

CAL2F347E

Error reading job entry record for job jjjjjjjj. R0= xxxxxxxx, R15= yyyyyyyy

Reason:
Program CAL2FOTJ attempted to get data from the database for job jjjjjjjj and failed. If
R15=8, see the following R0 codes:
20
Control interval conflict (someone else updating database)
40
Insufficient storage (increase region)

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F348E

Global error. Too many sysids.

Reason:
Program CAL2FOTJ encountered an internal error.

Action:
Contact your installation specialist for assistance.

CAL2F349E

Error reading job elements for job jjjjjjjj

Reason:
Program CAL2FOTJ attempted to read information about job jjjjjjjj from the database
but encountered EOD (end-of-data) instead.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 219

CAL2 Messages

CAL2F350E

Error reading elements for data set DSxxxxxxxx

Reason:
Program CAL2FOTJ attempted to read information about data set DSxxxxxxxx from the
database but encountered EOD (end-of-data) instead.

Action:
Contact your installation specialist for assistance.

CAL2F351E

The maximum number of specified jobs, nnnnnnnn, was exceeded

Reason:
The user specified a MAXJOBS=nnnnnnnn keyword. Program CAL2FOTJ terminated
processing after attempting to process more than the specified number of jobs.

Action:
Increase the number of jobs on the MAXJOBS keyword if you need to process more jobs.
If your installation permits, you can set MAXJOBS=0 (no limit), or delete the keyword
because the default is MAXJOBS=0.

CAL2F352E

Schedule # field is invalid - xxxxxxxx

Reason:
Program CAL2FOTJ encountered a schedule # field that was not numeric. Processing
terminates.

Action:
Contact your installation specialist for assistance.

220 Message Reference Guide

 CAL2 Messages

CAL2F353E

Error processing schedule record SJnnnnnn for job jjjjjjjj

Reason:
Program CAL2FOTJ attempted to read information about schedule record SJnnnnnn
from the database but encountered an error.

Action:
Contact your installation specialist for assistance.

CAL2F36AI

Times for job jjjjjjjj have been delayed nnnnnnnn minutes by predecessor job xxxxxxxx

Reason:
Program CAL2FRCH has set back the begin and end times for job jjjjjjjj by nnnnnnnn
minutes because of the end time of predecessor job xxxxxxxx.

Action:
None.

CAL2F36BI

Connecting job jjjjjjj1 ss1 dddddd1 ttt1 as a prereq for job jjjjjjj2 ss2 dddddd2 ttt2

Reason:
Program CAL2FRCH was processing job jjjjjjj2 with a SCHID of ss2 and an end date/time
of dddddd2 ttt2. Job jjjjjjj1 with a SCHID of ss1 and an end date/time of dddddd1 ttt1
was identified as a requirement of that job and was added to the workflow.

Action:
None.

CAL2F36CI

Returned from CAL2FCON

Reason:
Program CAL2FRCH called and returned from program CAL2FCON.

Action:
None.

Chapter 2: AFM - CA7R Messages 221

CAL2 Messages

CAL2F36DI

Built softobj jjjjjjj1 ss1 dddddd1 ttt1 as a prereq for job jjjjjjj2 ss2 dddddd2 ttt2

Reason:
Program CAL2FRCH was processing job jjjjjjj2 with a SCHID of ss2 and an end date/time
of dddddd2 ttt2. Job jjjjjjj1 with a SCHID of ss1 and an end date/time of dddddd1 ttt1
was identified as a requirement of that job but could not be found in the database with
that time and SCHID. The job was added to the workflow anyway.

Action:
None.

CAL2F36EI

Building datasetname as a prereq for jjjjjjjj sss ddddddd tttt

Reason:
Program CAL2FRCH was processing job jjjjjjjj with a SCHID of sss and an end date/time of
ddddddd tttt. Data set datasetname was identified as a requirement of that job.

Action:
None.

CAL2F36FI

Connecting datasetname as a prereq for jjjjjjjj sss ddddddd tttt

Reason:
Program CAL2FRCH was processing job jjjjjjjj with a SCHID of sss and an end date/time of
ddddddd tttt. Data set datasetname was added to the workflow as a requirement for
that job.

Action:
None.

222 Message Reference Guide

 CAL2 Messages

CAL2F36GI

Times for job jjjjjjjj have been moved up nnnnnnnn minutes for predecessor job
xxxxxxxx

Reason:
Program CAL2FRCH has moved up the begin and end times for job jjjjjjjj by nnnnnnnn
minutes because of the end time of predecessor job xxxxxxxx.

Action:
None.

CAL2F360E

Error n processing job data set for job jjjjjjjj

Reason:
Program CAL2FRCH encountered an error while attempting to read information from
the database about job jjjjjjjj. N is an aid as to where in the program the error occurred.
Processing terminates.

Action:
Save console listings. Review any preceding messages (CA7.Vxxx) for an explanation of
errors. Contact your installation specialist for assistance.

CAL2F361E

Too many prerequisites for job jjjjjjjj. Process shorter span.

Reason:
In searching for requirements for job jjjjjjjj, program CAL2FRCH has encountered too
many possibilities to process for the span selected. Processing terminates.

Action:
Decrease the span of days or hours that the workflow covers and resubmit the job or
reissue the command.

Chapter 2: AFM - CA7R Messages 223

CAL2 Messages

CAL2F362W

Error recalculating times for job jjjjjjjj. Not done.

Reason:
Program CAL2FRCH attempted to recalculate the submit, begin, and end date/times for
job jjjjjjjj, probably as a result of a requirement. Because there was an error
recalculating one or more of the times, the times were not modified. Processing
continues.

Action:
None.

CAL2F363C

Unexpected EOD or error processing SASDS for DSxxxxxxxx

Reason:
Program CAL2FRCH attempted to read information about data set DSxxxxxxxx from the
database but encountered EOD (end-of-data) or an error.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Contact your installation specialist for assistance.

CAL2F364E

SASSMASK indicated a parameter list error

Reason:
Program CAL2FRCH received a return code from SASSMASK indicating there was an
internal error in CAL2FRCH. Processing terminates.

Action:
Contact your installation specialist for assistance.

224 Message Reference Guide

 CAL2 Messages

CAL2F365E

Invalid entry in global for number of schfilter entries

Reason:
Program CAL2FRCH encountered an internal table error. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F37AI

xxxxxxxx chain for job jjjjjjjj end ddddddd tttt

CAL2F37AI

xxxxxxxx chain for dsn datasetname end ddddddd tttt

Reason:
Program CAL2FCCH is checking the times for jobs triggered by job jjjjjjjj or data set
datasetname. The end date/time is ddddddd and tttt. If xxxxxxxx is Checking, the
process is beginning. If xxxxxxxx is Returned, the process is ending.

Action:
None.

CAL2F37BI

Processing level xxxxx job jjjjjjjj end ddddddd tttt sss

CAL2F37BI

Processing level xxxxx dsn datasetname end ddddddd tttt sss

CAL2F37BI

Returned level xxxxx job jjjjjjjj end ddddddd tttt sss

Chapter 2: AFM - CA7R Messages 225

CAL2 Messages

CAL2F37BI

Returned level xxxxx dsn datasetname end ddddddd tttt sss

Reason:
Program CAL2FCCH is checking the times for job jjjjjjjj or data set datasetname with
SCHID sss. The end date/time is ddddddd and tttt. The recursion level is xxxxx.

Action:
None.

CAL2F37CW

Job xxxxxxxx sss ddddddd tttt loops w/job yyyyyyyy sss ddddddd tttt. Deleting
connection.

Reason:
Program CAL2FCCH has determined that the first job, named xxxxxxxx, loops with the
second job, named yyyyyyyy. The connection between the jobs has been deleted. For
each job, the SCHID is sss, the Julian date is ddddddd, and the time is tttt.

Action:
None.

CAL2F37DI

Chk chain lp xxxxx obj yyyyy obj objectname sss end ddddddd tttt

Reason:
Program CAL2FCCH is checking object number yyyyy in the check chain table. The loop
number is xxxxx, the name of the object is objectname, its SCHID is sss, and its date/time
is ddddddd and tttt. Obj is either job or dsn.

Action:
None.

226 Message Reference Guide

 CAL2 Messages

CAL2F37EI

Checking connection to obj objectname sss end ddddddd tttt

Reason:
For the object listed in message CAL2F37DI (which should be displayed earlier), program
CAL2FCCH is checking the connection to the object listed in this message.

Action:
None.

CAL2F37FI

Times for connd object objectname01 sss1 have been delayed nnn mins by cur object
objectname02 sss2

Reason:
Program CAL2FCCH has recalculated the begin and end times for object objectname01
and set them back nnn minutes. The reason for the delay is objectname02. If the object
is a job, the full job name is given. If the object is a data set, only the last 12 characters
of the data set name are displayed in the message.

Action:
None.

CAL2F370E

Bad build of check chain table

Reason:
Program CAL2FCCH was unable to build an internal table.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 227

CAL2 Messages

CAL2F371W

Error recalc times for job jjjjjjjj. Times not recalculated.

Reason:
While creating a workflow, program CAL2FCCH attempted to recalculate the submit,
begin, and end times for job jjjjjjjj. Because the program encountered an error during
the calculations, the times are not recalculated. Processing continues.

Action:
None.

CAL2F372W

Error recalc times for job jjjjjjjj. Partially recalculated.

Reason:
While creating a workflow, program CAL2FCCH attempted to recalculate the submit,
begin, and end times for job jjjjjjjj. The program encountered an error during the
calculations. One or more of the times were successfully recalculated. However, at least
one of the times was not. Processing continues.

Action:
None.

228 Message Reference Guide

 CAL2 Messages

CAL2F373E

Object table contains no jobs or data sets

Reason:
Program CAL2FCCH encountered an empty table. One of the following reasons applies:
■ No scheduled jobs met all the specified PARMDEF criteria.
■ All jobs were deleted from the workflow.
■ The user did not have authority to issue a CA Workload Automation SE FJOB
command, which Jobflow Illustrator issues internally.
Jobflow Illustrator stops processing and sets return code 8.

Action:
Examine your PARMDEF parameters and SYSIN commands. Determine that you have
appropriate security authority by issuing the following command in CA Workload
Automation SE:

FJOB,JOB=jobname,LIST=NOSP,LVL=1,TRIG=N,FROM=(mmddyy,hhmm),SPAN=n,SCHID=id

where jobname is the name of any scheduled job in the flow you are creating, mmddyy
and hhmm are the starting date and time of the job, n is a number representing the
span of a flow in hours, and id is the schedule ID of the job. After your JCL examination
and security testing, if you believe that one or more jobs should be in the workflow,
contact your installation specialist for assistance.

CAL2F40AI

CAL2FTCH processing job jjjjjjjj end time ddddddd tttt [rc]

Reason:
Program CAL2FTCH is processing the triggers for job jjjjjjjj that has an end time of
ddddddd tttt. rc is the return code.

Action:
None.

Chapter 2: AFM - CA7R Messages 229

CAL2 Messages

CAL2F40BI

CAL2FTCR xxx lv nnnnn jb jjjjjjjj end time ddddddd tttt [rc]

Reason:
Program CAL2FTCH is processing triggered job jjjjjjjj. If xxx is ent, the process is starting.
If xxx is ret, the process is ending and rc is the return code. The recursion level is nnnnn.

Action:
None.

CAL2F40CI

CAL2FTCR xxx lv nnnnn ds datasetname end time ddddddd tttt [rc]

Reason:
Program CAL2FTCH is processing triggered data set datasetname. If xxx is ent, the
process is starting. If xxx is ret, the process is ending and rc is the return code. The
recursion level is nnnnn.

Action:
None.

CAL2F400C

Type not set for slot number nnnnnnnn. Slot not processed.

Reason:
Program CAL2FTCH encountered an internal object table error while processing a
trigger.

Action:
Contact your installation specialist for assistance.

230 Message Reference Guide

 CAL2 Messages

CAL2F401E

Error processing IDS for record idskey. Continuing.

Reason:
Program CAL2FTCH attempted to read index data set record idskey from the database
and encountered an error. The program was checking to see whether the data set being
retrieved from the database triggered any jobs. Because the retrieve operation failed,
any jobs that the data set might have triggered are not included in the workflow shown
as triggered by the data set. Processing continues.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Then contact your installation specialist for assistance.

CAL2F402C

SASSMASK indicated a parameter list error

Reason:
Program CAL2FTCH received a return code from SASSMASK indicating an internal error
in CAL2FTCH. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F403C

Invalid entry in global for number of schfilter entries

Reason:
Program CAL2FTCH encountered an internal table error. Processing terminates.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 231

CAL2 Messages

CAL2F404E

Error processing directory for job jjjjjjjj. Processing continuing.

Reason:
Program CAL2FTCH attempted to retrieve the directory for job jjjjjjjj from the database
and encountered an error. Processing continues after skipping this job.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Then contact your installation specialist for assistance.

CAL2F405C

Error processing job data set for job jjjjjjjj

Reason:
Program CAL2FTCH attempted to retrieve data about job jjjjjjjj from the database and
encountered an error. Processing terminates.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Then contact your installation specialist for assistance.

CAL2F406E

Unexpected EOD or error on SASDS for DSnnnnnnnn job=xxxxxxxx

Reason:
Program CAL2FTCH attempted to read information about data set DSnnnnnnnn from the
database but encountered an error or EOD (end-of-data) instead. The information was
about data sets created by job xxxxxxxx. Processing terminates.

Action:
Ensure that job xxxxxxxx actually creates or updates the data set with number
DSnnnnnnnn. Ensure data set number DSnnnnnnnn is defined in the CA Workload
Automation SE database, and that it exists. Review the job's log for other messages,
especially CA7.Vxxx messages, that could describe the problem. If all else fails, contact
your installation specialist for assistance.

232 Message Reference Guide

 CAL2 Messages

CAL2F407C

Error processing index data set for job jjjjjjjj

Reason:
Program CAL2FTCH attempted to read the index data set for job jjjjjjjj from the database
but encountered an error. Processing terminates.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Then contact your installation specialist for assistance.

CAL2F410E

Add attempt failed. Job already existed.

Reason:
Program CAL2FADO was processing an ADDJOB command that specified a job that was
already part of the workflow. The command failed and processing terminated.

Action:
Review the SYSMSGS file to determine which ADDJOB command generated this
message. Then remove that command before resubmitting the job or reissuing the
command.

CAL2F411E

Add job failed. Sysid did not meet specified criteria.

Reason:
Program CAL2FADO was processing an ADDJOB command. The sysid of the job in the
ADDJOB command did not match the sysid criteria specified in the PARMDEF criteria.
The command failed and processing terminated.

Action:
Ensure the sysid of the job being added matches the SYS criteria specified in the
PARMDEF file. Then resubmit the job or reissue the command.

Chapter 2: AFM - CA7R Messages 233

CAL2 Messages

CAL2F412W

Error reading directory for job jjjjjjjj. Elapsed time assumed to be 1 minute.

Reason:
Program CAL2FADO attempted to read the directory for job jjjjjjjj but encountered an
error. Because the job's average run time could not be determined, a time of one
minute was assumed. Processing continues.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. If necessary, contact your installation specialist for assistance.

CAL2F413W

Error calculating begin time for job jjjjjjjj. Elapsed time assumed to be 1 minute.

Reason:
Program CAL2FADO encountered an error while calculating the begin date/time for job
jjjjjjjj. An average run time of one minute for the job was assumed. Processing
continues.

Action:
None.

CAL2F414W

Error calculating end time for job jjjjjjjj. Elapsed time assumed to be 1 minute.

Reason:
Program CAL2FADO encountered an error while calculating the end date/time for job
jjjjjjjj. An average run time of one minute for the job was assumed. Processing
continues.

Action:
None.

234 Message Reference Guide

 CAL2 Messages

CAL2F415E

Both begin and end dates are zero for job jjjjjjjj

Reason:
Program CAL2FADO could not process a workflow for job jjjjjjjj because the job's begin
and end dates are zero in an internal table. Processing terminates.

Action:
Contact your installation specialist for assistance.

CAL2F416E

Cannot calculate time for job jjjjjjjj

Reason:
Program CAL2FADO received a nonzero return code from calculate time program
CAL2FTIM. Processing terminates.

Action:
Review the SYSMSGS log for a previous message that would describe this error.

CAL2F417E

Cannot define data set datasetname

Reason:
Program CAL2FADO attempted to read information about data set datasetname from
the database and encountered an error. Processing terminates.

Action:
Check to ensure the data set is defined in the database. Review the job's log for other
messages, especially CA7.Vxxx messages, that could describe the problem. Then contact
your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 235

CAL2 Messages

CAL2F418E

Unexpected EOD or error processing SASDS for data set datasetname

Reason:
Program CAL2FADO attempted to read information about data set datasetname from
the database but encountered an error or EOD (end-of-data) instead. Processing
terminates.

Action:
Review the job's log for other messages, especially CA7.Vxxx messages, that could
describe the problem. Then contact your installation's CA Workload Automation SE
specialist for assistance.

CAL2F419W

Begin D/T for data set datasetname set to creation D/T.

Reason:
Program CAL2FADO attempted to set the begin date/time for data set datasetname to
one minute prior to the creation date/time. An error was encountered, and the begin
date and time was set equal to the creation date and time. Processing continues.

Action:
None.

CAL2F420E

To add a job or data set, you must have a LOGON keyword in the INITDEF DD
statement or INIT call

Reason:
Adding a job or data set to a workflow requires access to the CA Workload Automation
SE database. Jobflow Illustrator gains access through a LOGON (and depending on your
installation, a CA7PASS) keyword.

Action:
Add the appropriate keywords to your JCL or calling program and resubmit.

236 Message Reference Guide

 CAL2 Messages

CAL2F421E

Add object failed. Date out of build span range.

Reason:
Program CAL2FADO was processing an ADDJOB or ADDDS command. The date/time on
the command did not fall within the span (between the FROM and TO times) specified in
the PARMDEF file. If only the time is specified, the date defaults to the current date.

Action:
Ensure the time specified for the job or data set being added matches the criteria
specified in the PARMDEF file. Then resubmit the job or reissue the command.

CAL2F422I

Workflow total xxxxxxxxx job and yyyyyyyyy data set objects

Reason:
Program CAL2FADO counted the number and type of objects specified in its internal
tables. This may not be the number of objects that appear on a flowchart.

Action:
None.

CAL2F43AI

Disconnecting type name sss ddddddd tttt from type name sss ddddddd tttt

Reason:
Program CAL2FDCN has disconnected the first object from the second object. The type
of object is either job or dsn. If type is job, name is the job name. If type is dsn, name is
the last 16 characters of the data set name. The object's schedule ID is sss. The object's
end date/time (if a job) or creation date/time (if a data set) is shown by ddddddd tttt.

Action:
None.

Chapter 2: AFM - CA7R Messages 237

CAL2 Messages

CAL2F43BI

No valid connection to disconnect

Reason:
Program CAL2FDCN attempted to disconnect a connection, but the connection in the
table was not valid. It may already have been deleted.

Action:
None.

CAL2F43CI

No forward connection to disconnect

Reason:
Program CAL2FDCN ran through the forward connections in the connection table to find
the object to disconnect and could not find the correct connection.

Action:
None.

CAL2F43DI

No back connection to disconnect

Reason:
Program CAL2FDCN ran through the back connections in the connection table to find
the object to disconnect and could not find the correct connection.

Action:
None.

CAL2F43EI

Deleted objectname

Reason:
Program CAL2FDCN deleted the named object from the workflow internal tables.

Action:
None.

238 Message Reference Guide

 CAL2 Messages

CAL2F461E

DD statement is missing - xxxxxxxx

Reason:
Program CAL2FSIN needed DD statement xxxxxxxx to continue processing. The DD
statement was missing from the JCL. Processing terminates.

Action:
Add the DD statement to the JCL and resubmit the job or reissue the command.

CAL2F462E

Unable to open SYSIN DD statement

Reason:
Program CAL2FSIN was unable to open the SYSIN input file. Processing terminates.

Action:
Examine the DD statement for correct values, including the spelling of the ddname.
Then resubmit the job or reissue the command.

CAL2F463E

Parameter list is missing on call

Reason:
Jobflow Illustrator was being called programmatically. Program CAL2FSIN looked for a
parameter list and failed to find one. Processing terminates.

Action:
Ensure that the parameter lists are correct for each type of program call if you are the
programmer of the calling program. If you are not the programmer, contact your
installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 239

CAL2 Messages

CAL2F464E

Parameter list call type invalid - xxxxxxxx

Reason:
Jobflow Illustrator was being called programmatically. Program CAL2FSIN looked for a
parameter list and failed to find a valid one. xxxxxxxx represents the first 4 bytes of the
area found. Processing terminates.

Action:
Ensure that the parameter lists are correct for each type of program call if you are the
programmer of the calling program. If you are not the programmer, contact your
installation specialist for assistance.

CAL2F465W

Required SYSIN data is missing

Reason:
Program CAL2FSIN encountered an empty SYSIN file. Return code 4 is set.

Action:
If you want output from CA Workload Automation SE Jobflow Illustrator, resubmit the
job or reissue the command with a valid command in the SYSIN file or program work
area.

CAL2F466E

Parameter list exit address is required

Reason:
Program CAL2FSIN encountered an invalid parameter list for the type of command
entered.

Action:
Ensure the parameter lists are correct for each type of program call if you are the
programmer of the calling program. If you are not the programmer, contact your
installation specialist for assistance.

240 Message Reference Guide

 CAL2 Messages

CAL2F467I

Input data missing - defaults will be used

Reason:
SYSIN data was not passed to program CAL2FSIN. Default values were used for certain
keywords. Processing continues.

Action:
None.

CAL2F468I

Calling xxxxxxxx ...

Reason:
The Jobflow Illustrator SYSIN processor CAL2FSIN is calling command processor
xxxxxxxx.

Action:
None.

CAL2F469I

xxxxxxxx returned RC=yyyyyyyy

Reason:
The Jobflow Illustrator command processor xxxxxxxx returned to program CAL2FSIN
with return code yyyyyyyy.

Action:
None.

CAL2F470I

text

Reason:
Program CAL2FSIN is echoing SYSIN data, either from a SYSIN DD statement or from the
SYSIN area of a program parameter list. Processing continues.

Action:
None.

Chapter 2: AFM - CA7R Messages 241

CAL2 Messages

CAL2F471E

Invalid or duplicate keyword starting with: xxxxxxxxxxxxxxxx

Reason:
Program CAL2FSIN has encountered an invalid or duplicate keyword command starting
with xxxxxxxxxxxxxxxx. Processing terminates.

Action:
Correct the SYSIN record and resubmit the job or reissue the command.

CAL2F472E

Invalid value for keyword - keyword

Reason:
Program CAL2FSIN encountered an invalid value for keyword keyword. Processing
terminates.

Action:
Correct the value and resubmit the job or reissue the command.

CAL2F473E

FROM keyword is required with SPAN

Reason:
Program CAL2FSIN encountered a FLOWCHART command that has a SPAN keyword
without a corresponding FROM keyword. If SPAN is specified, FROM is required.
Processing terminates.

Action:
Correct the FLOWCHART command and resubmit the job or reissue the command.

CAL2F474E

Value must be numeric for keyword - keyword

Reason:
Program CAL2FSIN encountered an invalid value for keyword. The value must be
numeric. Processing terminates.

Action:
Correct the value and resubmit the job or reissue the command.

242 Message Reference Guide

 CAL2 Messages

CAL2F475E

Value is missing or exceeds maximum size - keyword

Reason:
Program CAL2FSIN encountered an invalid value for keyword. The value is either missing
altogether or it exceeds the maximum length for this keyword. Processing terminates.

Action:
Correct the value and resubmit the job or reissue the command.

CAL2F476E

Invalid command - text

Reason:
Program CAL2FSIN encountered a text string that it could not recognize as a valid
command. Processing terminates.

Action:
Correct the command and resubmit the job or reissue the command.

CAL2F477E

Required parameter is missing - parm

Reason:
Program CAL2FSIN determined that required parameter parm is missing from the
command that was being processed. Processing terminates.

Action:
Correct the command and resubmit the job or reissue the command.

CAL2F478E

Syntax error occurred on statement: text

Reason:
Program CAL2FSIN encountered a syntax error in the piece of the command string that
is displayed in the message.

Action:
Correct the command syntax and resubmit the job or reissue the command.

Chapter 2: AFM - CA7R Messages 243

CAL2 Messages

CAL2F480W

Parse error occurred on record nnnn - RC=return code, RE=reason code, FB=feed back

Reason:
Program CAL2FSIN received a nonzero return code from the command parser program
CAL2FPAR when processing SYSIN record nnnn. The return code, reason code and feed
back are displayed in the message. Processing terminates.

Action:
Examine the input commands and correct any syntax errors and resubmit the job or
reissue the command. You can also browse the SYSMSGS data set for any other
messages that may be of assistance. If you are unable to determine the error, contact
your installation specialist for assistance.

CAL2F481E

Keyword is invalid or command is missing - keyword

Reason:
Program CAL2FSIN was processing a command in the SYSIN file and encountered
keyword keyword that is invalid for the command or the command is missing.
Processing terminates.

Action:
Examine the SYSMSGS data set to see which command was being processed. Correct the
keyword and insure that it is valid for the command entered. Correct the syntax and
resubmit the job or reissue the command.

CAL2F482E

Expected continuation not found on input record nnnnnnnn

Reason:
Program CAL2FSIN was processing SYSIN record nnnnnnnn and expected to find
continuation data. None was found. Processing terminates.

Action:
Correct the data and resubmit the job or reissue the command.

244 Message Reference Guide

 CAL2 Messages

CAL2F483E

TO and SPAN keywords are mutually exclusive

Reason:
Program CAL2FSIN encountered a FLOWCHART command that has both TO and SPAN
keywords. The keywords are mutually exclusive. Processing terminates.

Action:
Correct the FLOWCHART command and resubmit the job or reissue the command.

CAL2F484E

START and END keywords are mutually exclusive

Reason:
Program CAL2FSIN encountered a DELJOB command that has both START and END
keywords. The keywords are mutually exclusive. Processing terminates.

Action:
Correct the DELJOB command and resubmit the job or reissue the command.

CAL2F491I

Command completed successfully

Reason:
Program CAL2FSIN processed all SYSIN commands successfully.

Action:
None.

CAL2F492W

An error occurred processing the last command

Reason:
Program CAL2FSIN encountered an error while processing the previous command.
Processing terminates.

Action:
Review the SYSMSGS file for messages that would describe the error.

Chapter 2: AFM - CA7R Messages 245

CAL2 Messages

CAL2F499I

CAL2FSIN ended - RC=xxxxxxxx

Reason:
Jobflow Illustrator SYSIN processor CAL2FSIN terminated processing with return code
xxxxxxxx.

Action:
None.

CAL2F53AI

Row#nnnnnn OT#xxxxxx jjjjjjjj(yyy) [Head]

CAL2F53AI

Row#nnnnnn OT#xxxxxx datasetname [Head]

Reason:
Program CAL2FBOT is building the output table. nnnnnn is the output table row number.
xxxxxx is the object table row number. jjjjjjjj(yyy) is the job name and schedule ID and
datasetname is the data set name of the object being processed. If the object is the
head of a chain, Head is displayed.

Action:
None.

CAL2F53BI

con Row#nnnnnn OT#xxxxxx jjjjjjjj(yyy)

CAL2F53BI

con Row#nnnnnn OT#xxxxxx datasetname

Reason:
Program CAL2FBOT is building the output table. This message follows CAL2F53AI to
show the successors of the object described in CAL2F53AI. con indicates the type of
relationship, such as JTJ (job triggers job) or JCD (job creates data set). The remainder of
the message contains the same information as CAL2F53AI.

Action:
None.

246 Message Reference Guide

 CAL2 Messages

CAL2F53CI

Pass 1: xxxxxxxx yyyy

Reason:
Program CAL2FBOT is building the output table. xxxxxxxx is a job name or partial data
set name and yyyy is a schedule ID.

Action:
None.

CAL2F53DI

Pass 2: xxxxxxxx yyyy

Reason:
Program CAL2FBOT is building the output table. xxxxxxxx is a job name or partial data
set name and yyyy is a schedule ID.

Action:
None.

CAL2F53EI

Flow has xxxxxxx jobs; yyyyyyy data sets; zzzzzzz connections at this point

Reason:
Program CAL2FBOT has determined that the workflow contains xxxxxxxx jobs, yyyyyyy
data sets, and zzzzzzz connections at this point.

Action:
None.

Chapter 2: AFM - CA7R Messages 247

CAL2 Messages

CAL2F530E

No objects were found that matched the input requirements

Reason:
In creating a workflow, program CAL2FBOT could not find any jobs or data sets that
matched the requirements specified in the PARMDEF file. Processing terminates.

Action:
Verify the keywords specified in the PARMDEF file. Make note of the defaults for the
keywords that are omitted. Change the keywords to match at least one job that is
scheduled during the specified span and that meets all other criteria. If you feel that CA
Workload Automation SE should have produced a workflow containing one or more
jobs or data sets, contact your installation specialist for assistance.

CAL2F600E

Flowchart too big--max size is 999x999 pages

Reason:
Program CAL2FAFP attempted to generate a flowchart that exceeded the maximum size
of 999x999 pages. Either the number of rows or columns exceeded 999 pages.
Processing terminates.

Action:
Decrease the total number of jobs in the workflow. The easiest way to do that is to
decrease the span of the workflow. An alternative is to be more selective about the jobs
in the flow. If you are using a mask on the JOB keyword, specify more characters before
the mask character. If you have multiple JOB keywords, specify fewer of them. Next,
resubmit the job or reissue the command.

CAL2F62BI

CAL2FAFC ended - RC=xxxxxxxx

Reason:
Program CAL2FAFC has terminated processing with return code xxxxxxxx.

Action:
None.

248 Message Reference Guide

 CAL2 Messages

CAL2F621I

CSV records written=nnnnnnnn

Reason:
Program CAL2FAFC has successfully written nnnnnnnn comma-separated value records
to the FLOWCSV file.

Action:
None.

CAL2F622W

Exit terminated request due to error - RC=nnnnnnnn

Reason:
This message is displayed if program CAL2FAFC determines that the program exit has
returned a nonzero return code nnnnnnnn.

Action:
See the error message provided by the exit for additional information.

CAL2F64BI

CAL2FACP ended RC=xxxxxxxx

Reason:
Program CAL2FACP has terminated processing with return code xxxxxxxx.

Action:
None.

CAL2F641I

CSV records written=nnnnnnnn

Reason:
Program CAL2FACP has successfully written nnnnnnnn comma-separated value records
to the FLOWCSV file.

Action:
None.

Chapter 2: AFM - CA7R Messages 249

CAL2 Messages

CAL2F642W

Exit terminated request due to error - RC=nnnnnnnn

Reason:
This message is displayed if program CAL2FACP determines that the program exit has
returned a nonzero return code nnnnnnnn.

Action:
See the error message provided by the exit for additional information.

CAL2H001E

ARM ffffffffff ERR, RC=xx/rrrr,JOB=jjjjjjjj, ELM=eeeeeeeeeeeeeeee

Reason:
An error has occurred while executing the IBM IXCARM macro to interface with the IBM
Automatic Restart Management (ARM). fffffffffff indicates the requested function; xx
indicates the return code; rrrr indicates the reason code; jjjjjjjj indicates the job
requesting the ARM service; eeeeeeeeeeeeeeee indicates the element requesting the
ARM service.

The request fails.

Action:
See the IBM manual MVS Sysplex Services Reference for more information about
IXCARM return and reason codes. Contact your installation specialist for assistance.

CAL2H002I

ARM ffffffffff SUCCESSFUL,JOB=jjjjjjjj, ELM=eeeeeeeeeeeeeeee

Reason:
A request to the IBM Automatic Restart Management (ARM) was successful. fffffffffff
indicates the requested function. jjjjjjjj indicates the job requesting the ARM service.
eeeeeeeeeeeeeeee indicates the element requesting the ARM service.

Action:
None.

250 Message Reference Guide

 CAL2 Messages

CAL2H003E

OPS/MVS SSM ERR, RC=xx/rr, JOB=jjjjjjjj, APPL=aaaaaaaa, STATE=ssssssss

Reason:
An error has occurred while executing the CA OPS/MVS EMA OPAISTAT macro to
interface with CA OPS/MVS EMA System State Manager (SSM). xx indicates the return
code. rr indicates the reason code. jjjjjjjj indicates the job requesting the SSM service.
aaaaaaaa indicates the application name. ssssssss indicates the requested state.

The request fails.

Action:
Contact your installation specialist for assistance.

CAL2H004I

OPS/MVS SSM SET STATE=ssssssss, JOB=jjjjjjjj, APPL=aaaaaaaa

Reason:
A request to CA OPS/MVS EMA System State Manager (SSM) was successful. ssssssss
indicates the requested state. jjjjjjjj indicates the job requesting the SSM service.
aaaaaaaa indicates the application name requesting the SSM service.

Action:
None.

CAL2H005I

ARM INTERFACE ACTIVATED

Reason:
The interface to the IBM Automatic Restart Management (ARM) was activated through
the /STATEMGR command.

Action:
None.

Chapter 2: AFM - CA7R Messages 251

CAL2 Messages

CAL2H006I

ARM INTERFACE DEACTIVATED

Reason:
The interface to the IBM Automatic Restart Management (ARM) was deactivated
through the /STATEMGR command.

Action:
None.

CAL2H007I

OPS/MVS SSM INTERFACE ACTIVATED

Reason:
The interface to CA OPS/MVS EMA System State Manager (SSM) was activated through
the /STATEMGR command.

Action:
None.

CAL2H008I

OPS/MVS SSM INTERFACE DEACTIVATED

Reason:
The interface to CA OPS/MVS EMA System State Manager (SSM) was deactivated
through the /STATEMGR command.

Action:
None.

CAL2H009I

ARM Interface requested

Reason:
The interface to the IBM Automatic Restart Management (ARM) has been requested
through the STATEMGR initialization statement.

Action:
None.

252 Message Reference Guide

 CAL2 Messages

CAL2H010I

OPS/MVS SSM Interface requested

Reason:
The interface to CA OPS/MVS EMA System State Manager (SSM) has been requested
through the STATEMGR initialization statement.

Action:
None.

CAL2H011W

STATEMGR 'YES' values are ignored in batch mode, defaulting to

ARM=NO,OPSSSM=NO

Reason:
CA Workload Automation SE was started in batch mode, and the STATEMGR
initialization statement contained ARM=YES and/or OPSSSM=YES. The request to
activate either ARM, the CA OPS/MVS EMA SSM, or both is ignored. Processing
continues.

Action:
None.

CAL2H012E

STATEMGR,ARM=YES not honored with TYPE=DORM; dormant CA 7 abending

Reason:
CA Workload Automation SE was started in dormant mode, and the STATEMGR
initialization statement contained ARM=YES. The request to activate ARM is ignored,
and CA Workload Automation SE is abended with code U0915.

Action:
None if the primary CA Workload Automation SE was started with ARM=YES coded on
the STATEMGR initialization statement. Otherwise, perform the following actions:
■ Change ARM=YES to ARM=NO on the STATEMGR initialization statement.
■ Restart your dormant copy of CA Workload Automation SE.

Chapter 2: AFM - CA7R Messages 253

CAL2 Messages

CAL2H100E

HEALTH CHECKER xxxxx CANNOT LOCATE IVT

Reason:
An IBM Health checker routine cannot access the IVT. xxxxx indicates either an 'exit' or
'check' routine. This message is issued in the IBM Health Checker address space.
■ For an 'exit' routine, the IBM Health Checker exit routine terminates and does not
define the 'check' routines to IBM Health Checker.
■ For a 'check' routine, the IBM Health Checker check routine terminates this
iteration.

Action:
Run CAL2ENVR to obtain a System Configuration Report, and then contact your
installation specialist for assistance.

CAL2H101E

HZSADDCK ERROR R15=xx R0=rrrrrrrr

Reason:
An error has occurred in an IBM Health Checker exit routine for CA Workload
Automation SE while trying to add a check routine. xx indicates the return code in
Register 15 and rrrrrrrr indicates the reason code in Register 0. This message is issued in
the IBM Health Checker address space. The IBM Health Checker exit routine for CA
Workload Automation SE does not add the check routine but does continue on if there
are more checks to add.

Action:
See IBM Health Checker for z/OS User Guide for more information about HZSADDCK
return and reason codes. Contact your installation specialist for assistance.

254 Message Reference Guide

 CAL2 Messages

CAL2H102E

IEANTRT ERROR R15(xxxx)

Reason:
An error has occurred in an IBM Health Checker check routine for CA Workload
Automation SE trying to retrieve the token from a name/token pair. xxxx indicates the
return code in Register 15. The error is something other than a not found condition
(R15=4). This message is issued in the IBM Health Checker address space. The IBM
Health Checker check routine for CA Workload Automation SE terminates checking the
current CA Workload Automation SE instance and continues checking other instances if
they exist.

Action:
See the IBM manual MVS Assembler Services Reference for more information about
IEANTRT return codes. Contact your installation specialist for assistance.

CAL2H103E

HZSFMSG ERROR R15=xx R0=rrrr

Reason:
An error has occurred in an IBM Health Checker check routine for CA Workload
Automation SE trying to issue an IBM Health Checker formatted check message. xx
indicates the return code in Register 15 and rrrr indicates the reason code in Register 0.
This message is issued in the IBM Health Checker address space. The IBM Health
Checker check routine for CA Workload Automation SE terminates checking the current
CA Workload Automation SE instance and continues checking other instances if they
exist.

Action:
See IBM Health Checker for z/OS User Guide for more information about HZSFMSG
return and reason codes. Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 255

CAL2 Messages

CAL2H104E

ALESERV ERROR RC=xxxx

Reason:
An error has occurred in an IBM Health Checker check routine for CA Workload
Automation SE trying to retrieve the ALET for a CA Workload Automation SE address
space through the ALESERV macro. xxxx indicates the return code in Register 15. This
message is issued in the IBM Health Checker address space. The IBM Health Checker
check routine for CA Workload Automation SE terminates checking the current CA
Workload Automation SE instance and continues checking other instances if they exist.

Action:
See the IBM manual MVS Assembler Services Reference for more information about
ALESERV return codes. Contact your installation specialist for assistance.

CAL2H105E

GQSCAN ERROR R15=xx, R0=rr

Reason:
An error has occurred in an IBM Health Checker check routine for CA Workload
Automation SE trying to retrieve ENQ information through the GQSCAN macro. xx
indicates the return code in Register 15 and rr indicates the reason code in Register 0.
The error is something other than a not found condition (R15=4). This message is issued
in the IBM Health Checker address space. The IBM Health Checker check routine for CA
Workload Automation SE terminates checking the current CA Workload Automation SE
instance and continues checking other instances if they exist.

Action:
See the IBM manual MVS Assembler Services Reference for more information about
GQSCAN return and reason codes. Contact your installation specialist for assistance.

256 Message Reference Guide

 CAL2 Messages

CAL2H200E

The CA 7 Workload Automation online started task or job for instance xxxx is not
active on this system.

Reason:
An IBM Health Checker check routine has received a 'not found' condition when it
attempted to retrieve a name/token pair for the indicated CA Workload Automation SE
instance. xxxx indicates the specific CA Workload Automation SE instance. Either the
online task is not up or was starting and had not yet created the name/token pair. This
message is an exception message issued in the IBM Health Checker address space.

Action:
Determine whether the CA Workload Automation SE online task should be up, and start
it if necessary. If the CA Workload Automation SE online task is up, check for a
name/token pair error during initialization. Contact your installation specialist for
assistance.

CAL2H201E

The CA 7 Workload Automation online started task or job for instance xxxx appears to
be hung.

Reason:
An IBM Health Checker check routine has determined that the indicated CA Workload
Automation SE instance is not performing any activity. xxxx indicates the specific CA
Workload Automation SE instance. Either the online task itself is having problems and is
hung or other system conditions are forcing this task to hang. This message is an
exception message issued in the IBM Health Checker address space.

Action:
Determine the cause of the CA Workload Automation SE online task 'hang'. Contact your
installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 257

CAL2 Messages

CAL2H202E

The CA 7 Workload Automation ICOM started task or job for instance xxxx is not
active on this system.

Reason:
An IBM Health Checker check routine has received a 'not found' condition when it
attempted to retrieve information for an ENQ for the indicated ICOM instance. xxxx
indicates the specific ICOM instance. Either the ICOM task is not up or was starting and
had not yet created the ENQ. This message is an exception message issued in the IBM
Health Checker address space.

Action:
Determine whether the CA Workload Automation SE online task should be up and start
it if necessary. If the CA Workload Automation SE online task is up, check for a
name/token pair error during initialization. Contact your installation specialist for
assistance.

CAL2IXCM1

ENTERED SASSIXCM R9=xxxxxxxx R13=xxxxxxxx MSGLEN=xxxxxxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message is issued
upon entry to ICOM XCF message exit module SASSIXCM.

Action:
None.

CAL2IXCM2

MSG= eeeeee tttt llllllll dddddddd

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message describes an
XCF message that was received. The eyecatcher is eeeeee, the type is tttt, the message
length is llllllll, and data is in the field dddddddd.

Action:
None.

258 Message Reference Guide

 CAL2 Messages

CAL2IXCM3

xxxxxxxxxxxxxxxx MESSAGE Xnnnn

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An XCF type
xxxxxxxxxxxxxxxxxx message was received. The message number of this type of message
is nnnn.

Action:
None.

CAL2IXCM4

REPLIED TO MESSAGE TYPE=xxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. XCF message exit
SASSIXCM replied to an XCF message of type xxxx.

Action:
None.

CAL2IXCM5

POSTED eeeeeeee. ADDR=xxxxxxxx VALUE=vvvvvvvv SECS=ssssssss

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. ECB eeeeeeee at address
xxxxxxxx was posted. The contents of the ECB after posting were vvvvvvvv.
Timestamped seconds and fraction are shown by ssssssss.

Action:
None.

Chapter 2: AFM - CA7R Messages 259

CAL2 Messages

CAL2IXC01

FC=xxxx EPSW=eeeeeeee PSW=pppppppp R1=xxxxxxxx R11=xxxxxxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message is issued
upon entry to ICOM XCF message exit module SASSIXC0. The function code to be
performed is xxxx, the PSW at entry is eeeeeeee, and the current PSW is pppppppp. The
parmlist address is contained in R1 and the SICOMD address is in R11.

Action:
None.

CAL2IXC02

IXCMSGO R15=nnnn R0=nnnn MSGTYPE=xxxx MSGLEN=llll TOKN=tttttttt tttttttt

BFN=bbbbbbbb

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An XCF message was sent.
The return and reason codes were returned in registers 15 and 0. The message type
code is xxxx. The message length is llll, and the token of the group member receiving the
message is tttttttt tttttttt. BFN shows some data in the message.

Action:
None.

CAL2IXC03

GOODECB=xxxxxxxx BADECB=yyyyyyyy MSGOFLGS=zzzzzzzz

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. If the message sent in
Message CAL2IXC02 was received within the expected time, GOODECB is posted. If not,
BADECB is posted. For a description of MSGOFLGS, see MNPLMSGOFLAGS in IBM macro
IXCYMNPL.

Action:
None.

260 Message Reference Guide

 CAL2 Messages

CAL2IXC04

SEND GNAM xxxxxxxx MNAM xxxxxxxx TOKN xxxxxxxx MESG xxxxxxxx SECS=ssssssss
WIP w

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The addresses of the
following are displayed: group name, member name, token, and message. Timestamped
seconds and fraction are shown by ssssssss. WIP is a where in program indicator.

Action:
None.

CAL2IXC05

XCF TOKEN=xxxxxxxx xxxxxxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The XCF token for ICOM is
displayed.

Action:
None.

CAL2I001E

UNABLE TO OPEN SERVDESK DD

Reason:
Either CA Workload Automation SE is starting and is processing the SERVICEDESK
initialization file statement, or the /REFRESH,MOD=SERVDESK command has been
issued. CA Workload Automation SE is trying to process the filter rules for creating CA
Service Desk requests but cannot open ddname SERVDESK.

Action:
Ensure that the SERVDESK DD statement is correct in the CA Workload Automation SE
started task.

Chapter 2: AFM - CA7R Messages 261

CAL2 Messages

CAL2I002E

SERVDESK RULE TYPE INVALID ON LINE xxxx

Reason:
The SERVDESK rule starting on the specified line does not start with a recognized event
type, such as JOBCOMP or QFULL. CA Workload Automation SE continues reading the
SERVDESK file, attempting to locate other valid rules.

Action:
Perform the following actions:
■ Correct the SERVDESK file.
■ Issue the /REFRESH,MOD=SERVDESK command to reprocess the file.

CAL2I003E

SERVDESK SYNTAX ERROR ON LINE xxxx, COL xx

Reason:
CA Workload Automation SE found a syntax error in the SERVDESK rules on the specified
line and column. CA Workload Automation SE continues reading the SERVDESK file,
attempting to locate other valid rules.

Action:
Perform the following actions:
■ Correct the SERVDESK file.
■ Issue the /REFRESH,MOD=SERVDESK command to reprocess the file.

CAL2I004E

SERVDESK VALUE TOO LONG ON LINE xxxx, COL xx

Reason:
CA Workload Automation SE found a value longer than allowed in the SERVDESK rules
on the specified line and column. CA Workload Automation SE continues reading the
SERVDESK file, attempting to locate other valid rules.

Action:
Perform the following actions:
■ Correct the SERVDESK file.
■ Issue the /REFRESH,MOD=SERVDESK command to reprocess the file.

262 Message Reference Guide

 CAL2 Messages

CAL2I005E

SERVDESK NO STORAGE FOR RULE ENDING ON LINE xxxx

Reason:
CA Workload Automation SE was unable to obtain private storage above the 16 MB line
for the SERVDESK rule ending on the specified line number. CA Workload Automation SE
continues reading the SERVDESK file, attempting to process additional rules.

Action:
Determine why CA Workload Automation SE has insufficient private storage above the
16 MB line. CA Workload Automation SE may have to be restarted with a larger REGION.

CAL2I006E

SERVDESK EOF REACHED PREMATURELY

Reason:
CA Workload Automation SE reached end of file in the SERVDESK file before the end of a
rule. The partially read rule at the end of the SERVDESK file is discarded.

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

CAL2I007I

nnnn SERVDESK RULES LOADED

Reason:
CA Workload Automation SE has successfully loaded the specified number of rules from
the SERVDESK file and loaded them into storage.

Action:
None.

Chapter 2: AFM - CA7R Messages 263

CAL2 Messages

CAL2I008I

nnnn OLD SERVDESK RULES RELEASED

Reason:
CA Workload Automation SE has reloaded the SERVDESK rules because the
/REFRESH,MOD=SERVDESK command was issued. The previous set of rules has now
been released from storage.

Action:
None.

CAL2I009E

SERVDESK INVALID TIME ON LINE xxxx, COL xx

Reason:
CA Workload Automation SE is reading the SERVDESK file and found a syntax error in a
time value in the specified line and column. Valid times are in the format hhmm (hours
and minutes) and must be exactly four digits long. Times are expressed in 24-hour mode
(8:15 p.m. is expressed as 2015).

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

CAL2I010E

SERVDESK RULE MISSING EVENT= ON LINE xxxx

Reason:
CA Workload Automation SE is reading the SERVDESK file and found a rule without the
required EVENT= keyword. An event name is required for every rule and must be exactly
six characters long.

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

264 Message Reference Guide

 CAL2 Messages

CAL2I011E

SERVDESK INVALID EVENT= ON LINE xxxx

Reason:
CA Workload Automation SE is reading the SERVDESK file and found a rule ending on the
specified line with an invalid event name. Event names must be exactly six characters
long.

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

CAL2I012I

PRODUCT INTERFACE SUB-TASK AVAILABLE

Reason:
CA Workload Automation SE is starting. One or more product interfaces that use the
product interface subtask, such as CA Service Desk, have been enabled. The subtask is
now available for work.

Action:
None.

CAL2I013W

nnnn EVENTS NOT PROCESSED AT SHUTDOWN

Reason:
CA Workload Automation SE is shutting down. The specified number of events, such as
job completions, were waiting to be processed by the product interface subtask. The
events are discarded without being passed to any of the product interfaces.

Action:
None.

Chapter 2: AFM - CA7R Messages 265

CAL2 Messages

CAL2I014E

SERVDESK LINE nnnn INVALID xxxxxxxx

Reason:
CA Workload Automation SE is reading the SERVDESK file. The specified field has an
invalid value in the rule ending on the line number in the message. Most likely the field
has a zero length.

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

CAL2I015E

xxxxxxxxxxxxxxxxxxxx ERROR R15=xxxxxxxx R0=xxxxxxxx R1=xxxxxxxx

Reason:
CA Workload Automation SE tried to open a request in CA Service Desk and had the
listed error. The error may be in CA Service Desk, in the SOAP server, or in CAISDI/els.
The variable portion of the message identifies why CA Workload Automation SE was
trying to open a request.

Action:
For an explanation of the return codes on the message, see the topic CAISDI/els API
Return Codes in the Common Services Message Guide. For example, if R15=8 and R0=3,
the specified event is not defined to CAISDI/els.

266 Message Reference Guide

 CAL2 Messages

CAL2I016W

*** CAISDI/ELS HAS NOT RETURNED AFTER ONE MINUTE--SUBTASK WILL BE

DETACHED

Reason:
CA Workload Automation SE called CAISDI/els to open a request in CA Service Desk.
CAISDI/els has not ended after one minute, indicating a problem in either CAISDI/els or
CA Service Desk. CA Workload Automation SE detaches the task.

CA Workload Automation SE automatically reattaches a new subtask to attempt to

process requests from other products that use the Product Interface. The Product
Interface is permanently disabled if the subtask is detached five times (see Message
CAL2I025E). An S13E abend may occur when the subtask is detached and can be
ignored.

Action:
Determine why CA Service Desk has not returned control to CA Workload Automation
SE.

CAL2I017E

SERVDESK MISSING COMP= ON LINE xxxx

Reason:
CA Workload Automation SE is reading the SERVDESK rules and found a JOBCOMP rule
without a COMP= keyword. The completion code is required.

Action:
Correct the SERVDESK file, and then issue the /REFRESH,MOD=SERVDESK command to
reprocess the file.

CAL2I018E

PRODUCT INTERFACE TASK ABENDED

Reason:
The CA Workload Automation SE product interface task is attempting to recover from an
abend.

Action:
Note any additional messages issued by CA Workload Automation SE. If you are unable
to resolve the problem, contact CA Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 267

CAL2 Messages

CAL2I019E

PRODUCT INTERFACE IN ERROR: xxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
The CA Workload Automation SE product interface task detected an abend while calling
the specified product interface. CA Workload Automation SE will attempt to continue
processing with the next product interface.

Action:
Determine whether there is a problem with the specified product and correct it if
possible. If you are unable to resolve the problem, contact CA Support at
ca.com/support for assistance.

CAL2I020E

THE PRODUCT INTERFACE HAS ABENDED TWICE, DISABLED FOR text

Reason:
The product specified on the preceding CAL2I019E message appears to have a problem.
Rather than continue to call the interface and incur additional abends, CA Workload
Automation SE is disabling this product's interface. text describes the disabled interface.

Action:
Restart CA Workload Automation SE to reenable the product interface.

CAL2I021E

SERVDESK VALUE MISSING ON LINE xxxx, COL xx

Reason:
The CA Service Desk rules include a keyword without a value.

Action:
Correct the SERVDESK rules and issue the /REFRESH,MOD=SERVDESK command to
reload the rules.

268 Message Reference Guide

 CAL2 Messages

CAL2I022E

SERVDESK DUPLICATE KEYWORD ON LINE xxxx, COL xx

Reason:
The CA Service Desk rules contain a rule with the same keyword more than once.

Action:
Correct the SERVDESK rules and issue the /REFRESH,MOD=SERVDESK command to
reload the rules.

CAL2I023E

*** THE CA 11 API (U11SCHCC) CANNOT BE FOUND, NO FURTHER ATTEMPTS TO

INTERFACE WITH CA 11 WILL BE MADE.

Reason:
The CA Workload Automation SE attempt to load the CA WA Restart Option API
(U11SCHCC) failed. This most likely means the version of CA WA Restart Option you are
running does not contain the U11SCHCC API. This feature became available with CA WA
Restart Option r11.0. If you want to use the CA Workload Automation SE/CA WA Restart
Option condition code synchronization feature, you must be running a version of CA WA
Restart Option that includes the U11SCHCC API.

Action:
Set CONDCHK=NO on the RESTART file initialization statement until you are running a
newer version of CA WA Restart Option.

Chapter 2: AFM - CA7R Messages 269

CAL2 Messages

CAL2I024W

*** THE CA 11 API (U11SCHCC) HAS NOT RETURNED AFTER ONE MINUTE, SUBTASK
WILL BE DETACHED

Reason:
CA Workload Automation SE called the CA WA Restart Option API (U11SCHCC) to add
data to the CA WA Restart Option database. CA WA Restart Option has not returned
control after one minute, indicating CA WA Restart Option has a problem. CA Workload
Automation SE will detach the task.

CA Workload Automation SE will automatically reattach a new subtask to attempt to

process requests from other products that use the Product Interface. The Product
Interface is permanently disabled if the subtask is detached five times (see Message
CAL2I025E). An S13E abend may occur when the subtask is detached and can be
ignored.

Action:
Determine why CA WA Restart Option has not returned control to CA Workload
Automation SE.

CAL2I025E

*** THE PRODUCT INTERFACE SUBTASK HAS FAILED FIVE TIMES AND IS BEING
DISABLED.

Reason:
As a result of repeated detaches (see Messages CAL2I016W and CAL2I024W), the
Product Interface is being disabled.

Action:
Check the CA 7 WA job log for messages CAL2I106W (CA Workload Automation SE CA
Service Desk) and/or CAL2I024W (the CA WA Restart Option API -U11SCHCC) to
determine the cause of the problem. If you cannot resolve the problem, contact CA
Support at ca.com/support for assistance.

Note: You must restart CA Workload Automation SE to reenable the Product Interface.

270 Message Reference Guide

 CAL2 Messages

CAL2I026E

*** THE PRODUCT INTERFACE SUBTASK ATTACH HAS TIMED OUT. THE SUBTASK HAS
BEEN DISABLED.

Reason:
As a result of a detach (see Messages CAL2I016W and CAL2I024W), CA Workload
Automation SE attempted to reattach the Product Interface subtask. If the subtask is not
reattached in 15 seconds, the entire interface is disabled.

Action:
Check the CA 7 WA job log and system logs to see if any problems were occurring that
might cause the subtask attach to time out. If you are unable to resolve the problem,
contact CA Support at ca.com/support for assistance.

Note: You must restart CA Workload Automation SE to reenable the Product Interface.

CAL2I027I

- JFM INTERFACE ACTIVE

Reason:
JFM=Y was coded on the OPTIONS statement in the product's initialization file.

Action:
None.

CAL2I028I

- CPM INTERFACE ACTIVE FOR JFM

Reason:
CPM=JFM was coded on the OPTIONS statement in the product's initialization file.

Action:
None.

Chapter 2: AFM - CA7R Messages 271

CAL2 Messages

CAL2I029W

- CPM=JFM REQUIRES JFM=YES, CPM INTERFACE NOW INACTIVE

Reason:
CPM=JFM was coded on the OPTIONS statement in the product's initialization file, but
JFM=NO was also coded.

Action:
Critical Path Monitoring using JFM does not occur unless JFM is active and JFM=YES is
specified.

CAL2I100I

CA-7 GLOBAL VARIABLE NAMES PREFIX IS xxxx

Reason:
This message is displayed if global variable substitution is in effect. xxxx is a one- to
four-character field that displays the prefix that precedes global variables. The default
prefix is &: (ampersand followed by colon).

Action:
None.

CAL2I101E

INVALID VALUE FOR GVARLVL

Reason:
The GVARLVL value must be a numeric value from 1 to 255.

Action:
Correct the value.

272 Message Reference Guide

 CAL2 Messages

CAL2I102I

CA-7 GLOBAL RESERVED VARIABLE NAMES BEGIN WITH x

Reason:
The global reserved variable names all begin with a one-character prefix that is
modifiable by the installation. The default character is 7. This message displays the value
of the prefix character if a value other than the default is used.

Action:
None.

CAL2I103E

STORAGE failed for VRMINFO

Reason:
The attempt to obtain storage for an internal control block failed.

Action:
Verify the REGION size for CA Workload Automation SE and increase if needed.

CAL2I104E

RDJFCB failed for VRMINFO

Reason:
The attempt to build an internal control block failed.

Action:
Ensure that the CA Workload Automation SE JCL contains a CA7RSRC DD statement.

CAL2I701E

SEVERE ERROR; Could not locate SASSCIAS SCT

Reason:
An internal system error occurred when trying to establish the CA Integrated Agent
Services (CA IAS) interface.

Action:
For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 273

CAL2 Messages

CAL2I702W

Agent Jobs not active; AGENTJOB is set off

Reason:
This warning message indicates that the CA Integrated Agent Services (CA IAS) interface
was not initialized because the initialization file XPDEF statement had AGENTJOB=NO
coded or defaulted.

Action:
Change the product's initialization file XPDEF statement to have AGENTJOB=YES coded if
you want to initialize the CA Integrated Agent Services (CA IAS) interface.

Note: For more information about cross-platform scheduling, see the Interface
Reference Guide.

CAL2I703I

IAS Agent Job Initialization in progress

Reason:
This is an informational message indicating that CA Workload Automation SE is
initializing the CA Integrated Agent Services (CA IAS) interface.

Action:
None.

CAL2I704E

nnnnnnnn Unable to allocate IAS I/O Work Area

Reason:
The operating system returned a nonzero return code, indicated by nnnnnnnn, when
trying to obtain storage for the CA Integrated Agent Services (CA IAS) interface.

Action:
Ensure the CA Workload Automation SE Online region size is sufficient. If after
increasing the CA Workload Automation SE region size you get this same error, contact
CA Support at ca.com/support for assistance.

274 Message Reference Guide

 CAL2 Messages

CAL2I705E

nnnnnnnn nnnnnnnn nnnnnnnn IAS New Token Failure

Reason:
When CA Workload Automation SE initiates a new instance of the CA Integrated Agent
Services (CA IAS) interface, a nonzero return code was received. The nnnnnnnn fields
display the return code from the REQUEST=NEW and the object return and reason
codes.

Action:
Perform the following actions:
■ Check for other messages in the CA Workload Automation SE JES job log for any
possible actions to take.
■ Make a note of this message with the appropriate code if CA Workload Automation
SE still fails after taking the suggested actions.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I706E

nnnnnnnn nnnnnnnn nnnnnnnn IAS Initialization Request error

Reason:
When CA Workload Automation SE requests the initialization of the CA Integrated Agent
Services (CA IAS) interface, a nonzero return code was received. The nnnnnnnn fields
display the return code from the REQUEST=INITIALIZE and the object return and reason
codes.

Action:
Perform the following actions:
■ Check for other messages in the CA Workload Automation SE JES job log for any
possible actions to take.
■ Make a note of this message with the appropriate codes if CA Workload
Automation SE still fails after taking the suggested actions.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 275

CAL2 Messages

CAL2I707E

nnnnnnnn nnnnnnnn nnnnnnnn IAS Configuration Call failed; check messages

Reason:
When CA Workload Automation SE requests the configuration of the agents for the CA
Integrated Agent Services (CA IAS) interface, a nonzero return code was received. The
nnnnnnnn fields display the return code from the REQUEST=CONFIGURATION and the
object return and reason codes. In addition to this message, the JES job log should
contain messages reporting errors found in the IASAGENT and IASCRYPT definitions.

Action:
Perform the following actions:
■ Check for other messages in the CA Workload Automation SE JES job log for any
possible actions to take.
■ Correct all errors found in the IASGAENT and IASCRYPT definitions.

CAL2I708E

nnnnnnnn nnnnnnnn nnnnnnnn IAS TCP/IP Communications initialization failed; check

messages

Reason:
When CA Workload Automation SE requests the CA Integrated Agent Services (CA IAS)
interface to start TCP/IP communications, a nonzero return code was received. The
nnnnnnnn fields display the return code from the REQUEST=START_COMMUNICATIONS
and the object return and reason codes.

Action:
Perform the following actions:
■ Ensure that the TCP/IP communications are available.
■ Ensure that the Manager information is correct in the IASAGENT definition and a
duplicate port assignment has not occurred.
■ Make a note of this message with the appropriate codes if CA Workload
Automation SE still fails after taking the suggested actions.
■ For assistance, contact CA Support at http://ca.com/support.

276 Message Reference Guide

 CAL2 Messages

CAL2I709E

nnnnnnnn Unable to load CA 7 program aaaaaaaa for agent jobs

Reason:
The program aaaaaaaa was not found in the STEPLIB or linklist when CA Workload
Automation SE tried to load it for the CA Integrated Agent Services (CA IAS) interface.

Action:
Perform the following actions:
■ Ensure the availablity of the program either through a STEPLIB concatenation or
through the linklist.
■ Check the JES job log for any errors that may have occurred against the data set in
which the program may reside.

CAL2I710E

nnnnnnnn Shutdown failure for IAS TCP/IP Comm

Reason:
While CA Workload Automation SE is stopping the CA Integrated Agent Services (CA IAS)
interface, a nonzero return code was received. Shutdown continues.

Action:
Consider the following actions:
■ Keep records if this message persists during multiple CA Workload Automation SE
shutdowns.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 277

CAL2 Messages

CAL2I711E

nnnnnnnn IAS Termination failure during shut down

Reason:
A nonzero return code was received when CA Workload Automation SE requested
termination of all CA Integrated Agent Services (CA IAS) interface functions. Shutdown
continues.

Action:
Consider the following actions:
■ Keep records if this message persists during multiple CA Workload Automation SE
shutdowns.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I712E

Abend aaaaa in Job Feedback subtask; restart attempted

Reason:
An abend, aaaaa, occurred in the CA Workload Automation SE subtask that processes
agent job feedback data. The abend may be either a system abend (Saaa) or a user
abend (Unnnn). Because the subtask has not abended at least three times, the subtask is
reattached and processing continues.

Action:
Perform the following actions:
■ Determine why the abend may have occurred.
■ Ensure that Message CAL2I723I follows this message to state that the subtask was
reattached successfully.

278 Message Reference Guide

 CAL2 Messages

CAL2I714E

nnnnnnnn Unable to load IAS program CAIASBLD for agent job interface

Reason:
CA Workload Automation SE tried to load the CA Integrated Agent Services (CA IAS)
program CAIASBLD, but it was not found in either the STEPLIB or linklist.

Note: CA Integrated Agent Services (CA IAS) is a separate component from CA

Workload Automation SE.

Action:
Perform the following actions:
■ Determine where this program resides.
■ Ensure that CA Workload Automation SE has access to the library.
■ Check the JES job log for any errors that may have occurred involving the data set
where the program resides.

CAL2I715I

IAS Agent Job processing is now available

Reason:
This is an informational message indicating that CA Workload Automation SE has
completed the CA Integrated Agent Services (CA IAS) interface initialization and that CA
Workload Automation SE can now process agent jobs.

Action:
None.

CAL2I716I

IAS Agent Job Termination is complete

Reason:
This is an informational message indicating that CA Workload Automation SE has
terminated the CA Integrated Agent Services (CA IAS) interface successfully.

Action:
None.

Chapter 2: AFM - CA7R Messages 279

CAL2 Messages

CAL2I717E

nnnnnnnn IAS Configuration failure; correct displayed errors and issue reconfigure
command

Reason:
During CA Workload Automation SE initialization, and its connection to the CA
Integrated Agent Services (CA IAS) interface, a nonzero return code was received.

Action:
Perform the following actions:
■ Check for other messages in the CA Workload Automation SE JES job log for any
possible actions to take.
■ Make a note of this message with the appropriate code if CA Workload Automation
SE still fails after taking the suggested actions.
■ Issue the reconfigure command (/IAS,FUNC=RECONFIG).
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I718E

nnnnnnnn IAS Start Communications failure

Reason:
During CA Workload Automation SE initialization, and its connection to the CA
Integrated Agent Services (CA IAS) interface, a nonzero return code was received.

Action:
Perform the following actions:
■ Check for other messages in the CA Workload Automation SE JES job log for any
possible actions to take.
■ Make a note of this message with the appropriate code if CA Workload Automation
SE still fails after taking the suggested actions.
■ Issue the stop communications and start communications commands.
■ For assistance, contact CA Support at http://ca.com/support.

280 Message Reference Guide

 CAL2 Messages

CAL2I719E

nnnnnnnn IAS GET_RESPONSE program error; unable to retrieve messages

Reason:
When processing messages from the CA Integrated Agent Services (CA IAS) interface, a
nonzero return code was received, and CA Workload Automation SE is no longer able to
retrieve messages from CA IAS. This is generally a severe error, and CA IAS may not be
functioning properly.

Action:
Perform the following actions:
■ Try recycling CA Workload Automation SE Online to see if an initialization clears the
error.
■ Make a note of this message.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I720E

nnnnnnnn Agent Job Feedback task failure; abend follows

Reason:
During CA Workload Automation SE initialization, the CA Workload Automation SE
subtask that processes agent job feedback data was not attached successfully. Since the
CA Integrated Agent Services (CA IAS) feedback subtask is critical to processing agent
jobs, an abend of CA Workload Automation SE is produced.

Action:
Determine why the attach was not successful, such as unable to find the program
SASSCIJF or an I/O error.

Chapter 2: AFM - CA7R Messages 281

CAL2 Messages

CAL2I721E

Abend aaaaa in Job Feedback subtask more than 3 times; abend follows

Reason:
An abend, aaaaa, occurred in the CA Workload Automation SE subtask that processes
agent job feedback data. The abend may be either a system abend (Saaa) or a user
abend (Unnnn). Because the subtask has abended three times, the subtask is considered
nonoperational, and CA Workload Automation SE itself is terminated.

Action:
Perform the following actions:
■ Determine why the abend may have occurred.
■ Report all abends to CA Support, because the subtask has abended multiple times
previously.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I722E

nnnnnnnn Reattach of Job Feedback subtask failed; abend follows

Reason:
After an abend occurred in the CA Workload Automation SE subtask that processes
agent job feedback data, a reattach of the subtask was attempted, but it failed with a
nonzero return code. Because the CA Integrated Agent Services (CA IAS) feedback
subtask is critical to processing agent jobs, an abend of CA Workload Automation SE is
produced.

Action:
Perform the following actions:
■ Determine why the first abend occurred.
■ For assistance, contact CA Support at http://ca.com/support.

282 Message Reference Guide

 CAL2 Messages

CAL2I723I

IAS Job Feedback subtask re-attached successfully

Reason:
This is an informational message indicating that CA Workload Automation SE
successfully reattached the subtask that processes CA Integrated Agent Services (CA IAS)
feedback data.

Action:
Monitor the situation in case more abends should occur.

CAL2I724I

IAS Configuration successfully completed

Reason:
This informational message indicates that CA Integrated Agent Services (CA IAS)
configuration processing completed successfully.

Action:
None.

CAL2I725E

Internal control block (IASL) corrupted; abend follows; recycle CA 7

Reason:
When processing responses from CA Integrated Agent Services (CA IAS) or an agent, CA
Workload Automation SE detected the control block IASLDSCT is corrupted. A recycle of
CA Workload Automation SE should successfully restore this control block, but do some
research to determine why the control was corrupted in the first place.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 283

CAL2 Messages

CAL2I726I

hhhhhhhh AGSMFDATA storage release done

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the address hhhhhhhh containing the control
block AGSMFDATA has been freed successfully. CA Support would have requested the
tracing option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I727I

hhhhhhhh message queue entry process

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the address hhhhhhhh who entry is now being
processed by the job feedback subtask. CA Support would have requested the tracing
option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

284 Message Reference Guide

 CAL2 Messages

CAL2I728E

CA IAS ended code aaaaaa; CA IAS abended more than 3 times

Reason:
CA Integrated Agent Services (CA IAS) has abended with code aaaaaa at least three
times. As a result, the CA Workload Automation SE system marks the CA IAS component
inactive because CA IAS has had repeated problems.

Action:
Check for CA IAS messages (beginning with CAIASnnnnn) to determine what the
problems are. Once the problems have been addressed, recycle CA Workload
Automation SE. For assistance, contact CA Support at ca.com/support.

CAL2I729E

CA IAS ended code aaaaaa; CA IAS restart is attempted

Reason:
CA Integrated Agent Services (CA IAS) has abended with code aaaaaa. CA Workload
Automation SE attempts to restart the CA IAS interface.

Action:
Perform the following actions:
■ Watch for additional messages that show as CA IAS interface is reestablished.
■ Determine the problems causing CA IAS to abend.

For assistance, contact CA Support at ca.com/support.

CAL2I730E

nnnnnnnn nnnnnnnn nnnnnnnnn IAS Configuration failed on restart; check messages

Reason:
During the reattach of the CA Integrated Agent Services (CA IAS) interface, configuration
failed.

Action:
Perform the following actions:
■ Check for CA IAS messages that show errors with the agent configuration.
■ Correct errors in the agent configuration.

Chapter 2: AFM - CA7R Messages 285

CAL2 Messages

CAL2I731I

CA IAS restart configuration successfully completed; Agent Job processing soon

available

Reason:
After a previous abend in the CA Integrated Agent Services (CA IAS) interface, CA
Workload Automation SE has reattached the interface and made it through the restart
process.

Action:
None.

CAL2I732E

nnnnnnnn nnnnnnnn nnnnnnnn IAS New Token Failure on restart of CA IAS

Reason:
The CA Integrated Agent Services (CA IAS) interface had abended, and now CA Workload
Automation SE is trying to reestablish that interface. An error occurred on the first
interface call (NEW). An abend U0787 follows.

Action:
Perform the following actions:
■ Examine why CA IAS had abended in the first place.
■ Correct the reasons for that abend.
■ Restart CA Workload Automation SE and watch for the CA IAS interface to be
initialized.
■ If necessary, gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

286 Message Reference Guide

 CAL2 Messages

CAL2I733E

nnnnnnnn nnnnnnnn nnnnnnnn IAS Initialization Request error on restart of CA IAS

Reason:
The CA Integrated Agent Services (CA IAS) interface had abended, and now CA Workload
Automation SE is trying to reestablish that interface. An error occurred during the
restart of CA IAS. An abend U0787 follows.

Action:
Perform the following actions:
■ Examine why CA IAS had abended in the first place.
■ Correct the reasons for that abend.
■ Restart CA Workload Automation SE and watch for the CA IAS interface to be
initialized.
■ If necessary, gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I734I

hhhhhhhh IAS DIVR freed FREE_RESPONSE

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the address hhhhhhhh containing the CA IAS
control block has been freed successfully. CA Support would have requested the tracing
option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 287

CAL2 Messages

CAL2I735I

hhhhhhhh New DIVR to be processed

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the address hhhhhhhh containing the CA IAS
control block to be processed. CA Support would have requested the tracing option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I736E

CA IAS marked inactive due to excessive abends

Reason:
CA IAS component has ended with errors at least three times and is now marked
inactive. CA IAS cannot become active until a recycle of the CA 7 address space occurs.

Action:
Perform the following actions:
■ Determine why the CA IAS has ended with errors (see the previous CA IAS User
ABEND Codes U0791).
■ Correct these errors and then recycle the CA Workload Automation SE online
address space at the next opportunity.

288 Message Reference Guide

 CAL2 Messages

CAL2I740E

nnnnnnnn IAS Receiver Port is not receiving messages

Reason:
CA Integrated Agent Services (CA IAS) has sent CA Workload Automation SE a message
indicating that the TCP/IP receiver port is no longer active; thus, CA Workload
Automation SE is receiving no job feedback data. This could mean that jobs may be in
the ready or active queues when the agent has tried to send a status change, but CA
Workload Automation SE cannot receive those messages. nnnnnnnn represents the
return code.

Action:
Perform the following actions:
■ Ensure the state of the system's TCP/IP is functioning properly.
■ Ensure no other address space is using the receiver port (as indicated in the Agent
Definition file on the AGENTRCV keyword).
■ Issue the following /IAS commands in the sequence described when the issues are
resolved:
/IAS,FUNC=STOPCOM
/IAS,FUNC=STARTCOM

CAL2I741I

hhhhhhhh storage obtain done for DIVR hhhhhhhh

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the address hhhhhhhh has been obtained for
job feedback processing. CA Support would have requested the tracing option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 289

CAL2 Messages

CAL2I749E

DDName aaaaaaaa specifies DUMMY

Reason:
The agent job interface is to be activated using the XPDEF AGENTJOB=YES specification.
However, the CA7AGNT, IASAGENT, IASCRYPT, or IASCKPT ddname (as shown by
aaaaaaaa in the message) was specified as DD DUMMY. DUMMY data sets are not
permitted for these DD statements.

Action:
Perform the following actions:
■ Define the necessary file with appropriate data.
■ Add the data set name to the ddname in the CA7ONL JCL.
■ Restart CA Workload Automation SE.

CAL2I750E

DDName aaaaaaaa not found

Reason:
The agent job interface is to be activated using the XPDEF AGENTJOB=YES specification.
However, the CA7AGNT, IASAGENT, IASCRYPT, or IASCKPT ddname (as shown by
aaaaaaaa in the message) was not found in the CA7ONL JCL.

Action:
Perform the following actions:
■ Define the necessary file with appropriate data.
■ Add the ddname to the CA7ONL JCL.
■ Restart CA Workload Automation SE.

290 Message Reference Guide

 CAL2 Messages

CAL2I751E

Error during GENCB (EXLST) R15=nn

Reason:
When initializing the CA7AGNT VSAM file, an error nn occurred when generating the
exit list. CA Workload Automation SE abnormally terminates with a U0750.

Action:
Determine any errors occurring against the CA7AGNT file.

Note: Error codes are documented in the IBM manual DFSMS Macro Instructions for
Data Sets.

For assistance, contact CA Support at ca.com/support.

CAL2I752E

Error during GENCB (ACB) R15=nn

Reason:
When generating the VSAM ACB for the CA7AGNT VSAM file, error nn occurred. CA
Workload Automation SE abnormally terminates with a U0750.

Action:
Determine any errors occurring against the CA7AGNT file.

Note: Error codes are documented in the IBM manual DFSMS Macro Instructions for
Data Sets.

For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 291

CAL2 Messages

CAL2I753E

Error during GENCB (RPL) R15=nn

Reason:
When initializing the CA7AGNT VSAM file, an error nn occurred when generating the
request parameter list (RPL). CA Workload Automation SE abnormally terminates with a
U0750.

Action:
Determine any errors occurring against the CA7AGNT file.

Note: Error codes are documented in the IBM manual DFSMS Macro Instructions for
Data Sets.

For assistance, contact CA Support at ca.com/support.

CAL2I754E

Error during OPEN of CA7AGNT file R15=nn ER=nnn

Reason:
When opening the CA7AGNT file, return code and error code were returned indicating
the error.

Action:
Determine any errors occurring against the CA7AGNT file.

Note: Error codes are documented in the IBM manual DFSMS Macro Instructions for
Data Sets.

For assistance, contact CA Support at ca.com/support.

CAL2I755I

CA7AGNT file opened successfully R15=nn ER=nnn

Reason:
This informational message indicates the CA7AGNT file was opened successfully.

Action:
None.

292 Message Reference Guide

 CAL2 Messages

CAL2I756I

Requesting IAS interface shutdown

Reason:
An informational message indicates that CA Workload Automation SE is requesting
shutdown of the CA Integrated Agent Services (CA IAS) interface.

Action:
None.

CAL2I757I

IAS Interface Shutdown is complete

Reason:
This informational message indicates the CA Integrated Agent Services (CA IAS) interface
has completed its shutdown.

Action:
None.

CAL2I760E

Non-tracking instance of CA 7; feedback data not processed

Reason:
This message is issued if CA Workload Automation SE was starting as a non-tracking
instance, such as through batch. An agent job was submitted and job feedback data has
been received. Because no tracking is permitted for this instance, the feedback data is
discarded.

Action:
Ensure that any agent job submissions occur through a tracking instance of CA Workload
Automation SE.

Chapter 2: AFM - CA7R Messages 293

CAL2 Messages

CAL2I761I

Shutdown in progress for CA 7 IAS subtask interface

Reason:
This is an informational message indicating that CA Workload Automation SE has
notified the IAS subtask to start shutting itself down.

Action:
None.

CAL2I762E

CIAS Subtask Storage failure; no agent job processing permitted; verify region size

Reason:
During the job feedback subtask initialization, a working storage area could not be
obtained. This may be because insufficient storage has been allocated to CA Workload
Automation SE.

Action:
Consider the following actions:
■ Verify the region size of CA Workload Automation SE.
■ Increase the size so that agent job processing may occur if possible.
■ Ensure the product's initialization file statement XPDEF has AGENTJOB=NO coded if
CA Workload Automation SE will not submit agent jobs.

CAL2I763E

IAS CIJF Subtask detected invalid control block AGSMFDATA

Reason:
When processing job feedback for an agent job, CA Workload Automation SE detected
the control block AGSMFDATA is corrupted. The job feedback subtask abends, and CA
Workload Automation SE reattaches it. Insufficient information is available to determine
which job was involved with the error.

Action:
For assistance, contact CA Support at ca.com/support.

294 Message Reference Guide

 CAL2 Messages

CAL2I764I

CA 7 SMF REC : SMF=nn(aaaaaaaa) SVC=rc (AGJ ) jjjjjjjj

Reason:
If CA Workload Automation SE/CA Integrated Agent Services (CA IAS) interface tracing
has been activated, this message shows the pseudo-SMF record data that has been
chained to the SVC chain for processing by CA Workload Automation SE. The nn shows
the SMF record type. The aaaaaaaa is either JOBINIT, STEPTERM, or JOBTERM. rc is the
SVC return code. jjjjjjjj is the job name. CA Support would have requested the tracing
option.

Action:
Perform the following actions:
■ Forward this information, along with other trace messages written to the CA
Workload Automation SE JES job log, to CA Support.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I765E

INVALID L2AGIOPL PARAMETER LIST

Reason:
An internal program error occurred when requesting an operation on the CA7AGNT file.
An abend U760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 295

CAL2 Messages

CAL2I766E

CA7AGNT INTERNAL ERROR - INVALID REQUEST

Reason:
An internal program error occurred when requesting an input or output operation on
the CA7AGNT file. An abend U0760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I767E

INVALID RPL BLOCK ENCOUNTERED

Reason:
The CA7AGNT RPL block is corrupted in storage. An abend U0760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I768E

Record Storage Obtain Failure

Reason:
When retrieving a record from the CA7AGNT file, not enough storage was available to
save the record for processing. An abend U0760 follows.

Action:
Verify the REGION size for CA Workload Automation SE and increase if needed.

296 Message Reference Guide

 CAL2 Messages

CAL2I769E

CA7AGNT MACRO PROCESSING ERROR

Reason:
The VSAM macro to point to or get a record from the CA7AGNT file was not accepted by
VSAM, which may indicate an internal error. An abend U0760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I770E

CA7AGNT SHOWCB ERROR

Reason:
When trying to obtain the error codes from VSAM, the SHOWCB interface failed. An
abend U0760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I771E

CA7AGNT RECD ERROR R15 = nn FDBK =hhhhhhhh FUNC =nn

Reason:
An error was returned from trying to obtain a record from the CA7AGNT VSAM file. This
message is followed by Message CAL2I772E showing which record key is involved.
Processing continues, although data may not be written to the VSAM file.

Action:
Determine if there is any contention against the CA7AGNT file from another source.

Note: Error codes are documented in the IBM manual DFSMS Macro Instructions for
Data Sets.

For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 297

CAL2 Messages

CAL2I772E

CA7AGNT KEY = aaaaaaaaaa...

Reason:
This message is paired with Message CAL2I771E to display the VSAM record key that
incurred the error.

Action:
See message CAL2I771E.

CAL2I773E

CA7AGNT MODCB ERROR

Reason:
When trying to obtain the error codes from VSAM, the MODCB interface failed. An
abend U0760 follows.

Action:
Perform the following actions:
■ Gather the appropriate documentation.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2I776E

Unable to load job type table; check region size for sufficient storage

Reason:
During the CA Workload Automation SE initialization with the agent jobs feature (XPDEF
AGENTJOB=YES) active, there is insufficient region to load the table, which contains all
the supported job types. An abend U0776 follows.

Action:
Verify the REGION size for the CA Workload Automation SE address space is of sufficient
size to support the agent job interface.

298 Message Reference Guide

 CAL2 Messages

CAL2JR01E

DBIN data set OPEN failure

Reason:
The DBIN DD data set failed to open successfully. The DD statement is either missing or
does not point to a sequential backup of the CA Workload Automation SE database. This
message is issued by CAL2JRXD.

The program terminates with a U0002 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR02E

DBOUT data set OPEN failure

Reason:
The DBOUT DD data set failed to open successfully. The DD statement is either missing
or does not point to file that can contain a sequential backup of the CA Workload
Automation SE database. If the DD is DUMMIED it should carry a DCB parameter with
the correct characteristics: DCB=(RECFM=VB,LRECL=4096,BLKSIZE=23476). This message
is issued by CAL2JRXD.

The program terminates with a U0002 abend code.

Action:
Correct the JCL and resubmit the job.

Chapter 2: AFM - CA7R Messages 299

CAL2 Messages

CAL2JR03E

Unknown data type encountered

Reason:
Program CAL2JRXD encountered a record in the DBIN sequential backup that contains
an unknown record type.

The program terminates with a U0002 abend code.

Action:
Perform the following actions:
■ Confirm that the DBIN DD points to a valid database backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2JR04E

Unknown job member type encountered

Reason:
Program CAL2JRXD encountered a job member record in the DBIN sequential backup
that contains an unknown record sub-type.

The program terminates with a U0002 abend code.

Action:
Perform the following actions:
■ Confirm that the DBIN DD points to a valid database backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

300 Message Reference Guide

 CAL2 Messages

CAL2JR05E

SYSPRINT DD missing or invalid

Reason:
The SYSPRINT DD failed to open successfully. The DD statement is either missing or is
invalid. If the DD is DUMMIED it should carry a DCB parameter with the correct
characteristics: DCB=(RECFM=VB,LRECL=133,BLKSIZE=133). This message is issued by
CAL2JRXD.

The program terminates with a U0002 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR41E

QDUMPIN data set OPEN failure

Reason:
The QDUMPIN DD data set failed to open successfully. The DD statement is either
missing or does not point to a sequential backup of the CA Workload Automation SE
queues. This message is issued by CAL2JRXQ.

The program terminates with a U0003 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR42E

QDUMPOUT data set OPEN failure

Reason:
The QDUMPOUT DD data set failed to open successfully. The DD statement is either
missing or does not point to file that can contain a sequential backup of the CA
Workload Automation SE queues. If the DD is DUMMIED it should carry a DCB
parameter with the correct characteristics: DCB=(RECFM=VB,LRECL=256,BLKSIZE=6148).
This message is issued by CAL2JRXQ.

The program terminates with a U0003 abend code.

Action:
Correct the JCL and resubmit the job.

Chapter 2: AFM - CA7R Messages 301

CAL2 Messages

CAL2JR43E

Unknown data type encountered

Reason:
Program CAL2JRXQ encountered a record in the QDUMPIN sequential backup that
contains an unknown record type.

The program terminates with a U0003 abend code.

Action:
Perform the following actions:
■ Confirm that the QDUMPIN DD points to a valid queue backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2JR44E

QDUMPIN control record error

Reason:
The QDUMPIN DD data set does not point to a sequential backup of the CA Workload
Automation SE queues. The first record of the file is not a valid QDUMP control record.
This message is issued by CAL2JRXQ.

The program terminates with a U0003 abend code.

Action:
Correct the JCL and resubmit the job.

302 Message Reference Guide

 CAL2 Messages

CAL2JR45E

QDUMPIN not a valid queue dump data set

Reason:
The QDUMPIN DD data set points to a sequential backup of the CA Workload
Automation SE queues; however, the QDUMP control record does not indicate that the
queues were successfully unloaded. This message is issued by CAL2JRXQ.

The program terminates with a U0003 abend code.

Action:
Repeat the QDMP shutdown of CA Workload Automation SE to generate a valid QDUMP
file. Then resubmit the CAL2JRXQ job.

CAL2JR46E

SYSPRINT DD missing or invalid

Reason:
The SYSPRINT DD failed to open successfully. The DD statement is either missing or is
invalid. If the DD is DUMMIED it should carry a DCB parameter with the correct
characteristics: DCB=(RECFM=VB,LRECL=133,BLKSIZE=133). This message is issued by
CAL2JRXQ.

The program terminates with a U0003 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR61E

VRMIN data set OPEN failure

Reason:
The VRMIN DD data set failed to open successfully. The DD statement is either missing
or does not point to a sequential backup of the CA Workload Automation SE VRM file.
This message is issued by CAL2JRXV.

The program terminates with a U0004 abend code.

Action:
Correct the JCL and resubmit the job.

Chapter 2: AFM - CA7R Messages 303

CAL2 Messages

CAL2JR62E

VRMOUT data set OPEN failure

Reason:
The VRMOUT DD data set failed to open successfully. The DD statement is either missing
or does not point to file that can contain a sequential backup of the CA Workload
Automation SE VRM file. If the DD is DUMMIED it should carry a DCB parameter with the
correct characteristics: DCB=(RECFM=VB,LRECL=32700,BLKSIZE=32704). This message is
issued by CAL2JRXV.

The program terminates with a U0004 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR63E

Unknown data type encountered

Reason:
Program CAL2JRXV encountered a record in the VRMIN sequential backup that contains
an unknown record type.

The program terminates with a U0004 abend code.

Action:
Perform the following actions:
■ Confirm that the VRMIN DD points to a valid VRM file backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

304 Message Reference Guide

 CAL2 Messages

CAL2JR65E

SYSPRINT DD missing or invalid

Reason:
The SYSPRINT DD failed to open successfully. The DD statement is either missing or is
invalid. If the DD is DUMMIED it should carry a DCB parameter with the correct
characteristics: DCB=(RECFM=VB,LRECL=133,BLKSIZE=133). This message is issued by
CAL2JRXV.

The program terminates with a U0004 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR71E

ARFIN data set OPEN failure

Reason:
The ARFIN DD data set failed to open successfully. The DD statement is either missing or
does not point to a sequential backup of the CA Workload Automation SE ARF database.
This message is issued by CAL2JRXA.

The program terminates with a U0005 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR72E

ARFOUT data set OPEN failure

Reason:
The ARFOUT DD data set failed to open successfully. The DD statement is either missing
or does not point to a file that can contain a sequential backup of the CA Workload
Automation SE ARF file. If the DD is DUMMIED, it should carry a DCB parameter with the
correct characteristics: DCB=(RECFM=VB,LRECL=32700,BLKSIZE=32704). This message is
issued by CAL2JRXA.

The program terminates with a U0005 abend code.

Action:
Correct the JCL and resubmit the job.

Chapter 2: AFM - CA7R Messages 305

CAL2 Messages

CAL2JR73W

ARFSET aaaaaaaa has unrecognizable condition type

Reason:
Program CAL2JRXA encountered an ARF definition in the ARFIN sequential backup that
contains an unknown exception condition type.

The return code four (RC4) is issued when the program terminates.

Action:
Perform the following actions:
■ Confirm that the ARFIN DD points to a valid ARF file backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2JR74E

Unknown record type encountered

Reason:
Program CAL2JRXA encountered a record in the ARFIN sequential backup that contains
an unknown record type.

The program terminates with a U0005 abend code.

Action:
Perform the following actions:
■ Confirm that the ARFIN DD points to a valid ARF file backup that has not been
corrupted.
■ Correct the JCL and resubmit the job.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

306 Message Reference Guide

 CAL2 Messages

CAL2JR75E

SYSPRINT DD missing or invalid

Reason:
The SYSPRINT DD failed to open successfully. The DD statement is either missing or is
invalid. If the DD is DUMMIED, it should carry a DCB parameter with the correct
characteristics: DCB=(RECFM=VB,LRECL=133,BLKSIZE=133). This message is issued by
CAL2JRXA.

The program terminates with a U0005 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR76W

Commands within ARFSET can not be expanded beyond the 69-byte limit

Reason:
Program CAL2JRXA encountered an ARF record in the ARFIN sequential backup that
contains one or more commands that are trying to be expanded beyond the 69-byte
limit. This usually occurs when trying to rename a smaller name to a larger name.

The return code four (RC4) is issued when the program terminates.

Action:
Review the CAL2JRXA-01 report to find out the commands that were not changed. If you
want the changes, correct the RENAMES DD control file and resubmit the job.

CAL2JR81E

Invalid or omitted parmlist

Reason:
This indicates an internal error with the parameter list passed to CAL2JRXX.

The program terminates with a U0001 abend code.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 307

CAL2 Messages

CAL2JR82E

Unable to open RENAMES DD control file

Reason:
The RENAMES DD failed to open successfully. The DD statement is either missing or is
invalid. This message is issued by CAL2JRXX.

The program terminates with a U0001 abend code.

Action:
Correct the JCL and resubmit the job.

CAL2JR83W

RENAMES DD control file does not specify any jobname changes

Reason:
The RENAMES DD opened successfully; however, the file is either empty, or contains
only comment lines. This message is issued by CAL2JRXX.

The program terminates with a U0001 abend code.

Action:
Correct the RENAMES control file and resubmit the job.

CAL2JR84W

Potential new jobname already exists in the database (jjjjjjjj)

Reason:
One or more CA Workload Automation SE elements were changed to reflect the new job
name jjjjjjjj. However, that job name is already defined to the database. This message is
issued by CAL2JRXX.

The message is only a warning. Processing continues.

Action:
If the name change is intentional, no response is required. For example, if you change
JOBA to JOBB, and JOBB to JOBC, the resulting database has JOBB and JOBC.

However, if your RENAMES control file only directs to change JOBA to JOBB, the
resulting output contains two definitions for JOBB (the original one, and the old JOBA
that has been renamed). The VSAM reload process for the resulting output fails because
there are duplicate keys for JOBB.

308 Message Reference Guide

 CAL2 Messages

CAL2M001I

jobname(jobnumber) starting Jobflow Monitor; JFCNTWA at address

Reason:
The Jobflow Monitor address space is starting. The message lists the jobname and the
jobnumber. Additionally, the message lists the address of the Jobflow Monitor control
workarea (JFCNTWA).

Action:
None.

CAL2M002S

Terminating - Jobflow Monitor is not running APF authorized

Reason:
This message indicates that Jobflow Monitor is not running APF authorized. Ensure that
all STEPLIBs are APF authorized.
As a result of the error, Jobflow Monitor terminates.

Action:
Correct the problem. After the problem is corrected, restart the Jobflow Monitor task.
For assistance, contact CA Support at ca.com/support.

CAL2M003I

JobFlow Monitor address space initialization complete

Reason:
Jobflow Monitor has successfully completed its initialization process. Processing
continues.

Action:
None.

Chapter 2: AFM - CA7R Messages 309

CAL2 Messages

CAL2M004I

Value of CPM in instance is value

Reason:
The startup value of the CPM parameter in the CA Workload Automation SE instance
that is running is listed in the message. This message is an informational message.

Action:
None.

CAL2M005I

Jobflow Monitor Ended

Reason:
Jobflow Monitor Address Space ended.

Action:
None.

CAL2M006I

Tracking limited to CPM workload identified by (instance)

Reason:
The CA Workload Automation SE instance listed in the message is a dedicated Critical
Path Monitor query server and is used with the CPM server that is executing on this
LPAR. This message is informational.

Action:
None.

CAL2M007S

Terminating - An internal error has occurred in L2JFATCH

Reason:
An internal error has occurred in module L2JFATCH. As a result of the error, Jobflow
Monitor terminates.

Action:
For assistance, contact CA Support at ca.com/support.

310 Message Reference Guide

 CAL2 Messages

CAL2M008I

instance InitialBuild: jobs Jobs, datasets Dsets, triggers Trigs, requirements Rqmts,
required-by RqdBy

Reason:
This message is generated when Jobflow Monitor completes the initial build for a
specific monitored instance. The message lists the total for the jobs, data sets, triggers,
requirements, and required-by components that were built.

Action:
None.

CAL2M009S

Unable to create QueryWorker Thread

Reason:
Jobflow Monitor could not respond to a query request because a thread could not be
created. This message is followed by a CAL2M080E message with more information.

Action:
If the CAL2M080E message indicates that there was insufficient memory for the
request, retry the request after making additional memory available to Jobflow Monitor.
If the problem persists, contact CA support at ca.com/support for assistance.

CAL2M010S

Terminating - Unable to get storage for Control Work Area

Reason:
The primary control block structure does not have enough storage. Jobflow Monitor
terminates.

Action:
Check your system status.

Chapter 2: AFM - CA7R Messages 311

CAL2 Messages

CAL2M011W

Unable to open DDNAME CAJFLOG

Reason:
An OPEN error occurred on the data set associated with the DDNAME CAJFLOG. Jobflow
Monitor continues, but the diagnostic logging is not available. A CAL2M080E message
sometimes follows this message with more information.

Action:
Check your JCL to ensure that DDNAME CAJFLOG is specified and that the data set is
exclusive to this instance of Jobflow Monitor.

CAL2M012S

Terminating - Unable to establish L2JFLOGlock

Reason:
L2JFLOGlock is used to maintain the integrity of internal diagnostic logging and is
required. Jobflow Monitor terminates. A CAL2M080E message sometimes follows this
message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M013S

Terminating - init_Variables failed

Reason:
The init_Variables routine failed to initialize required external variables. Jobflow
Monitor terminates. This message should have been preceded by either the CAL2M074E
message or the CAL2M076E message, which provides more information.

Action:
For assistance, contact CA Support at ca.com/support.

312 Message Reference Guide

 CAL2 Messages

CAL2M014S

Terminating - Unable to define named handler

Reason:
Jobflow Monitor was unable to define the routine for the named handler that is listed in
the message. Jobflow Monitor terminates. A CAL2M080E message can follow this
message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M015S

Terminating - Unable to create WorkQueue for Control thread

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the control
thread. Jobflow Monitor terminates. Review any messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M016S

Terminating - Unable to create hashTable

Reason:
Jobflow Monitor was unable to create the required hashTable. Jobflow Monitor
terminates. Review any messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 313

CAL2 Messages

CAL2M017S

Terminating - Unable to create Command Processor

Reason:
Jobflow Monitor was unable to create the Command thread. Jobflow Monitor
terminates. A CAL2M080E message sometimes follows this message with more
information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M018S

Terminating - Unable to create Event Listener Control Thread

Reason:
Jobflow Monitor was unable to create the Event Listener Control thread. Jobflow
Monitor terminates. A CAL2M080E message sometimes follows this message with more
information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M019S

Terminating - Unable to create WorkQueue for Event Listener

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the Event
Listener thread. Jobflow Monitor terminates. Review any messages that preceded this
message.

Action:
For assistance, contact CA Support at ca.com/support.

314 Message Reference Guide

 CAL2 Messages

CAL2M020S

Terminating - Unable to create named Thread

Reason:
Jobflow Monitor was unable to create the named thread. The named thread is critical to
JFM. Jobflow Monitor terminates. Message CAL2M080E can follow with more
information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M021S

Terminating - Unable to create WorkQueue for named Thread

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the named
thread. Jobflow Monitor terminates. Review any messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M022W

CAJFLOG DD is not allocated - diagnostic logging will not be available

Reason:
This message is generated if the CAJFLOG DD is not currently allocated in the Jobflow
Monitor startup JCL and one of the following two conditions is true:
■ The LOGLEVEL command was issued.
■ The JBFLWAS member in the CAJFPARM data set contains a LOGLEVEL parameter
with a value greater than zero.

If this warning message is generated, diagnostic logging is not available.

Note: Use the LOGLEVEL command, LOGLEVEL parameter, or both only at the direction
of CA Support.

Action:
See the address space parameters and the operator statements in the Interface
Reference Guide.

Chapter 2: AFM - CA7R Messages 315

CAL2 Messages

CAL2M024S

Unable to get nnnn bytes of storage for the jflog control block

Reason:
An attempt to obtain nnnn bytes of storage for the jflog file control block listed in the
message was unsuccessful. As a result of the error, Jobflow Monitor terminates.

Action:
Increase the MEMLIMIT size on the Jobflow Monitor started task EXEC statement. Once
this has been completed, restart the Jobflow Monitor task.

CAL2M025S

Terminating - Unable to establish lock

Reason:
Jobflow Monitor was unable to initialize the lock named lock. This lock is critical to
Jobflow Monitor operations.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M026W

Dynamic allocation failed for log file ddname - rc=rc, error=error, info=info

Reason:
A dynamic allocation error occurred when allocating the ddname listed in the message.

Dynamic allocation automatically occurs when the PRINTLOG command is issued to

Jobflow Monitor.

The return code (rc), error code (error), and information code (info) are listed in the
message. Message CAL2M080E, which contains more information about the warning,
also accompanies this message.

As a result of this warning, the PRINTLOG command did not process successfully.

Action:
For assistance, contact CA Support at ca.com/support.

316 Message Reference Guide

 CAL2 Messages

CAL2M027W

Unable to open DDNAME ddname

Reason:
Jobflow Monitor was unable to open the log file associated with the ddname listed in
the message. Message CAL2M080E message follows this message with more
information.

As a result of this warning, the PRINTLOG command did not process successfully.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M028S

Terminating - Error occurred processing CAJFPARM(JBFLWAS)

Reason:
An error occurred processing the CAJFPARM data set member JBFLWAS, which contains
the address space parameters. Additional messages indicating the problem can precede
this message. As a result of the error, Jobflow Monitor terminates.

Action:
Correct the problem. After the problem is corrected, restart the Jobflow Monitor task.

CAL2M029S

Terminating - Error occurred processing CAJFPARM(JBFLWEV)

Reason:
An error occurred processing the CAJFPARM data set member JBFLWEV, which contains
the parameters that are required for event processing. Additional messages indicating
the problem can precede this message. As a result of the error, Jobflow Monitor
terminates.

Action:
Correct the problem. After the problem is corrected, restart the Jobflow Monitor task.

Chapter 2: AFM - CA7R Messages 317

CAL2 Messages

CAL2M030E

Unable to create MAIN Thread for monitor(xxxx)

Reason:
Jobflow Monitor was unable to create the MAIN thread for the monitor specified (xxxx).
Jobflow Monitor continues to run, but that monitor instance does not start. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M031E

Unable to create CPMPORT name token pair for monitor(xxxx) rc(nn)

Reason:
Jobflow Monitor was unable to create the name token pair CPM would use to
determine on which TCP/IP port to communicate with Jobflow Monitor. Jobflow
Monitor continues to run, and the specified monitor instance continues to run, but CPM
may not be able to communicate with the monitor instance.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M032E

Unable to locate MONITOR statement for xxxx

Reason:
The operator issued a start command for a monitor instance (xxxx), but no MONITOR
initialization statement is found for the instance in JBFLWMN member of the CAJFPARM
data set.

Action:
Perform the following actions:
■ Add the MONITOR initialization statement to JBFLWMN.
■ Reissue the start command.

318 Message Reference Guide

 CAL2 Messages

CAL2M033E

Unable to parse MONITOR statement for xxxx

Reason:
The operator issued a start command for the specified monitor instance. There were
errors parsing the MONITOR initialization statement.

Action:
Perform the following actions:
■ Correct the errors in the MONITOR initialization statement.
■ Reissue the start command.

CAL2M034E

Unable to delete CPMPORT name token pair (name) rc(nn)

Reason:
A monitor instance has terminated. Jobflow Monitor was unable to delete the name
token pair.

Action:
None.

CAL2M035E

Thread (name) terminated unexpectedly

Reason:
The indicated thread (name) terminated unexpectedly. A restart of Jobflow Monitor is
required.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 319

CAL2 Messages

CAL2M036W

Unable to OPEN CAJFPARM(JBFLWEV) default parameters in use

Reason:
Jobflow Monitor was unable to open the CAJFPARM data set to read the JBFLWEV
member, which contains the event processing parameters that are used for the address
space. A CAL2M080E message with more information can follow this message. The
default parameters are used.

Action:
None.

CAL2M037W

Unable to OPEN CAJFPARM(JBFLWAS) default parameters in use

Reason:
Jobflow Monitor was unable to open the CAJFPARM data set to read the JBFLWAS
member, which contains the address space parameters. A CAL2M080E message
sometimes follows this message with more information. The default parameters are
used.

Action:
None.

CAL2M038W

Unable to OPEN CAJFPARM(JBFLWMN) no Monitors will be active

Reason:
Jobflow Monitor was unable to open the CAJFPARM data set to read the JBFLWMN
member, which contains the MONITOR definitions. A CAL2M080E message sometimes
follows this message with more information. Jobflow Monitor remains active. The
default MONITOR parameters are used when a new instance is started.

Action:
None.

320 Message Reference Guide

 CAL2 Messages

CAL2M039E

Error reading CAJFPARM(JBFLWMN)

Reason:
Jobflow Monitor encountered an error reading JBFLWMN in the CAJFPARM data set. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M040E

Close for CAJFPARM(JBFLWMN) failed

Reason:
Jobflow Monitor was unable to close the CAJFPARM data set. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M041W

Unable to OPEN CAJFPARM(JBFLWIP) default PORT values in use

Reason:
Jobflow Monitor was unable to open the CAJFPARM data set to read the JBFLWIP
member, which contains the TCP/IP port definitions. A CAL2M080E message sometimes
follows this message with more information. Jobflow Monitor remains active. The
default PORT parameters are used.

Action:
None.

Chapter 2: AFM - CA7R Messages 321

CAL2 Messages

CAL2M042E

Error reading CAJFPARM(JBFLWIP)

Reason:
Jobflow Monitor encountered an error reading JBFLWIP in the CAJFPARM data set. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M043E

Close for CAJFPARM(JBFLWIP) failed

Reason:
Jobflow Monitor as unable to close the CAJFPARM data set. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M044W

Unable to create QRYPORT name token pair for monitor(xxxx) rc(nn)

Reason:
Jobflow Monitor was unable to create the name token pair for the monitor listed in the
message. The CA 7 Web Client uses this name token pair to determine on which TCP/IP
port to communicate with Jobflow Monitor. Jobflow Monitor continues to run, and the
specified monitor instance continues to run, but the CA 7 Web Client cannot always
communicate with Jobflow Monitor.
This message typically occurs when the name/token pair exists for the monitor listed in
the message. Usually, a different JFM task other than the one containing the
CAL2M044W error is monitoring the CA 7 instance.

Action:
Correct the problem. After the problem is corrected, restart the Jobflow Monitor task.
For assistance, contact CA Support at ca.com/support.

322 Message Reference Guide

 CAL2 Messages

CAL2M045W

Unexpected characters found parsing MONITOR: xxx...xxx

Reason:
While parsing the MONITOR statement in CAJFPARM(JBFLWMN), unexpected characters
(xxx...xxx) were found. Parsing continues, and the unexpected characters are ignored.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M046E

Error reading CAJFPARM(JBFLWAS)

Reason:
Jobflow Monitor encountered an error reading member JBFLWAS in the CAJFPARM data
set. A CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M047E

Close for CAJFPARM(JBFLWAS) failed

Reason:
Jobflow Monitor was unable to close the CAJFPARM data set. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 323

CAL2 Messages

CAL2M048W

Unexpected characters found parsing CAJFPARM(JBFLWEV): xxx

Reason:
Unexpected characters (xxx) were found during the parsing of the statements in
CAJFPARM(JBFLWEV). Parsing continues, and the unexpected characters are ignored.

Note: For more information about CAJFPARM(JBFLWEV) statements, see the Interface
Reference Guide.

Action:
Correct the statement in CAJFPARM(JBFLWEV).

CAL2M049W

Unexpected characters found parsing CAJFPARM(JBFLWAS): xxx

Reason:
While parsing the statements in CAJFPARM(JBFLWAS), unexpected characters (xxx) were
found. Parsing continues, and the unexpected characters are ignored.

Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Correct the statement in CAJFPARM(JBFLWAS).

CAL2M050E

Monitor(xxxx) will not be started due to MONITOR() statement errors

Reason:
A parsing error was found for the specified MONITOR statement for INSTANCE(xxxx).
The error is not ignored. The specified monitor is not started.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Review any messages that preceded this message.
■ Correct the error in the MONITOR statement in CAJFPARM(JBFLWMN).
■ Restart the monitor instance.

324 Message Reference Guide

 CAL2 Messages

CAL2M051E

INSTANCE is a required parameter

Reason:
While parsing the MONITOR statement, no INSTANCE was detected. An INSTANCE is
required to identify the instance of CA Workload Automation SE to monitor.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M052E

Invalid specification for LOGLEVEL: value

Reason:
The LOGLEVEL value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Correct the LOGLEVEL statement in CAJFPARM(JBFLWAS).

CAL2M053E

Invalid or duplicate specification for INSTANCE: value

Reason:
The INSTANCE value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

Chapter 2: AFM - CA7R Messages 325

CAL2 Messages

CAL2M054E

Invalid specification for TYPE: value

Reason:
The TYPE value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M057E

Invalid specification for SPAN: value

Reason:
The SPAN value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M058E

Invalid specification for REFRESH: value

Reason:
The REFRESH value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

326 Message Reference Guide

 CAL2 Messages

CAL2M059E

Invalid specification for HISTORY: value

Reason:
The HISTORY value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M060E

Invalid specification for CPMCCI: value

Reason:
The CPMCCI value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M061E

Invalid specification for JFMCCI: value

Reason:
The JFMCCI value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

Chapter 2: AFM - CA7R Messages 327

CAL2 Messages

CAL2M062E

Invalid specification for JFMCPMN: value

Reason:
The JFMCPMN value specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M063E

Invalid specification for CPMSRVR: value

Reason:
The CPMSRVR value that is specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M064E

Invalid specification for EVENTS: value

Reason:
The EVENTS value that is specified is incorrect.
Note: For more information about the EVENTS value, see the Interface Reference Guide.

Action:
Correct the EVENTS value in CAJFPARM(JBFLWAS).

328 Message Reference Guide

 CAL2 Messages

CAL2M065E

Invalid specification for FACILITY: value

Reason:
The FACILITY value that is specified is incorrect.
Note: For more information about the FACILITY value, see the Interface Reference
Guide.

Action:
Correct the FACILITY value in CAJFPARM(JBFLWAS).

CAL2M066E

Invalid specification for JFMNAME: value

Reason:
The JFMNAME value that is specified is incorrect.

Note: For more information about the JFMNAME value, see the Interface Reference
Guide.

Action:
Correct the JFMNAME value in CAJFPARM(JBFLWAS).

CAL2M067S

Unable to get nnnn bytes of storage for the jfevnWrapTraceTable

Reason:
An attempt to obtain nnnn bytes of storage for the wrap trace table was unsuccessful.
As a result of the error, Jobflow Monitor terminates.

Action:
Increase the MEMLIMIT size on the Jobflow Monitor started task EXEC statement. After
the size is increased, restart the Jobflow Monitor task.

Chapter 2: AFM - CA7R Messages 329

CAL2 Messages

CAL2M068S

Terminating - Unable to establish L2JFEVNlock

Reason:
Jobflow Monitor was unable to initialize the required L2JFEVNlock lock that is used to
maintain the integrity of the events table.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M069S

Unable to get nnnn bytes of storage for the jfevnComponentArea control block

Reason:
An attempt to obtain nnnn bytes of storage for the events table control block listed in
the message was unsuccessful. As a result of the error, Jobflow Monitor terminates.

Action:
Increase the MEMLIMIT size on the Jobflow Monitor started task EXEC statement. After
the size is increased, restart the Jobflow Monitor task.

CAL2M070E

hcreate() error

Reason:
Jobflow Monitor was unable to create the hashTable using the hcreate service. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M071E

HASH pthread_mutex_attr_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the hashTable. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

330 Message Reference Guide

 CAL2 Messages

CAL2M072E

HASH pthread_mutex_attr_settype() error

Reason:
Jobflow Monitor was unable to set up serialization for the hashTable. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M073E

HASH pthread_mutex_attr_setkind() error

Reason:
Jobflow Monitor was unable to set up serialization for the hashTable. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M074E

HASH pthread_mutex_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the hashTable. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M075E

Unable to initialize iTimerKey

Reason:
Jobflow Monitor was unable to initialize the global key iTimerKey. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 331

CAL2 Messages

CAL2M076E

Unable to initialize jfwaKey

Reason:
Jobflow Monitor was unable to initialize the global key jfwaKey. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M077E

Invalid keyword value combination: keyword1(value1) and keyword2(value2)

Reason:
The two keyword/value combinations specified in the message conflict.
Note: For more information about the keywords that are listed, see the Interface
Reference Guide.

Action:
Correct the keyword/values in CAJFPARM(JBFLWEV).

CAL2M078E

Error reading CAJFPARM(JBFLWEV)

Reason:
Jobflow Monitor encountered an error reading member JBFLWEV in the CAJFPARM data
set. A CAL2M080E message with more information can follow this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M079E

Close for CAJFPARM(JBFLWEV) failed

Reason:
Jobflow Monitor was unable to close the CAJFPARM data set. A CAL2M080E message
with more information can follow this message.

Action:
For assistance, contact CA Support at ca.com/support.

332 Message Reference Guide

 CAL2 Messages

CAL2M080E

text

Reason:
A bad return code was received from a C/LE run-time function. The text in this message
is generated by C/LE and further describes an error. This message usually appears with
another Jobflow Monitor error message.

Action:
Refer to the appropriate IBM documentation for more information.

CAL2M082I

JFM will read flow definitions for (instance)

Reason:
The PREDICTFLOWS value for the instance is YES. Jobflow Monitor (JFM) reads flow
definitions from the database that is associated with the instance.
Note: For more information about using the PREDICTFLOWS parameter, see the
Interface Reference Guide.

Action:
None.

CAL2M083I

Tracking entire workload for (instance)

Reason:
Jobflow Monitor is monitoring the entire workload for this instance.

Action:
None.

Chapter 2: AFM - CA7R Messages 333

CAL2 Messages

CAL2M084E

Monitor(instance) Terminating - Call to module L2JFDBIN failed RC(rc)

Reason:
An error occurred during access of the database for the specified monitor instance
(instance). The return code (rc) is listed in the message. The monitor instance
terminates.

Action:
Perform the following actions:
■ Review surrounding messages for more detailed information.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2M088E

Invalid specification for ENFDT: value

Reason:
The ENFDT value that is specified is incorrect.

Note: For more information about CAJFPARM(JBFLWMN) statements, see the Interface
Reference Guide.

Action:
Correct the MONITOR statement in CAJFPARM(JBFLWMN).

CAL2M089E

Invalid specification for GUARANTEED: value

Reason:
The GUARANTEED value that is specified is incorrect.
Note: For more information about the GUARANTEED value, see the Interface Reference
Guide.

Action:
Correct the GUARANTEED value in CAJFPARM(JBFLWEV).

334 Message Reference Guide

 CAL2 Messages

CAL2M090E

Invalid specification for CAPTURE: value

Reason:
The CAPTURE value that is specified is incorrect.
Note: For more information about the CAPTURE value, see the Interface Reference
Guide.

Action:
Correct the CAPTURE value in CAJFPARM(JBFLWEV).

CAL2M091E

Invalid specification for DURABLE: value

Reason:
The DURABLE value that is specified is incorrect.
Note: For more information about the DURABLE value, see the Interface Reference
Guide.

Action:
Correct the DURABLE value in CAJFPARM(JBFLWEV).

CAL2M093E

Invalid specification for MAXEVENTS: value

Reason:
The MAXEVENTS value that is specified is incorrect.
Note: For more information about the MAXEVENTS value, see the Interface Reference
Guide.

Action:
Correct the MAXEVENTS value in CAJFPARM(JBFLWEV).

Chapter 2: AFM - CA7R Messages 335

CAL2 Messages

CAL2M094E

Invalid specification for MAXSUBS: value

Reason:
The MAXSUBS value that is specified is incorrect.
Note: For more information about the MAXSUBS value, see the Interface Reference
Guide.

Action:
Correct the MAXSUBS value in CAJFPARM(JBFLWEV).

CAL2M095E

Invalid specification for PATHNAME: value

Reason:
The PATHNAME value that is specified is incorrect.
Note: For more information about the PATHNAME value, see the Interface Reference
Guide.

Action:
Correct the PATHNAME value in CAJFPARM(JBFLWEV).

CAL2M096E

Invalid specification for SUBSCRIBE: value

Reason:
The SUBSCRIBE value that is specified is incorrect.
Note: For more information about the SUBSCRIBE value, see the Interface Reference
Guide.

Action:
Correct the SUBSCRIBE value in CAJFPARM(JBFLWEV).

336 Message Reference Guide

 CAL2 Messages

CAL2M097E

Invalid specification for EXCLUDE: value

Reason:
The EXCLUDE value that is specified is incorrect.
Note: For more information about the EXCLUDE value, see the Interface Reference
Guide.

Action:
Correct the EXCLUDE value in CAJFPARM(JBFLWEV).

CAL2M098E

Invalid EXCLUDE EVENTNAME(value)

Reason:
The EVENTNAME value on the EXCLUDE statement is not a valid event name.
Note: For more information about the EVENTNAME value on the EXCLUDE statement,
see the Interface Reference Guide.

Action:
Correct the EVENTNAME value on the EXCLUDE statement in CAJFPARM(JBFLWEV).

CAL2M099W

EXCLUDE EVENTNAME(value) was already requested

Reason:
The EVENTNAME value on the EXCLUDE statement was previously requested on another
EXCLUDE statement.
As a result, this EXCLUDE statement is ignored.
Note: For more information about the EVENTNAME value on the EXCLUDE statement,
see the Interface Reference Guide.

Action:
Correct the EVENTNAME value on the EXCLUDE statement in CAJFPARM(JBFLWEV).

Chapter 2: AFM - CA7R Messages 337

CAL2 Messages

CAL2M100E

L2JFCHDB - Storage management error - U0403

Reason:
An invalid return code was received from a request for storage.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M101E

OUT OF SPACE IN JOB|DATASET DATA SET

Reason:
The Job or Dataset data set does not have enough space available.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Allocate more space to the data set.
■ Copy the data set.
■ Reinitialize CA Workload Automation SE.

CAL2M102E

ProcessLaterList pthread_mutex_destroy() error

Reason:
An error occurred when Jobflow Monitor attempted to destroy a mutex while
processing a ProcessLaterList. Message CAL2M080E can follow with more information.

Action:
For assistance, contact CA Support at ca.com/support.

338 Message Reference Guide

 CAL2 Messages

CAL2M103W

Unable to delete QRYPORT name token pair (name) rc(nn)

Reason:
A Jobflow Monitor instance has terminated. Jobflow Monitor was unable to delete the
name token pair.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M110E

LOAD error

Reason:
An error occurred attempting to load a module.

Action:
Perform the following actions:
■ Check your STEPLIB DD concatenation in your Jobflow Monitor startup JCL.
■ Verify that the CA Workload Automation SE libraries are in the concatenation.

For assistance, contact CA Support at ca.com/support.

CAL2M111W

__heaprpt error occurred

Reason:
An error occurred when calling the system __heaprpt function. This function is used
when the STATUS command is issued. As a result, the HEAP information is not
generated.

Action:
Perform the following actions:
■ Issue the STATUS command again.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 339

CAL2 Messages

CAL2M119E

IEANTRT LOAD FAILED

Reason:
Jobflow Monitor was unable to load z/OS name/token retrieve services. Name/token
services are unavailable, and CPM is not always able to send Jobflow Monitor requests.

Action:

For assistance, contact CA Support at ca.com/support.

CAL2M120E

IEANTCR LOAD FAILED

Reason:
Jobflow Monitor was unable to load z/OS name/token create services. Name/token
services are unavailable, and CPM may not be able to send Jobflow Monitor requests.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M121W

IEANTDL LOAD FAILED

Reason:
Jobflow Monitor was unable to load z/OS name/token delete services. The monitor
terminates.

Action:

For assistance, contact CA Support at ca.com/support.

CAL2M122W

IEANTRT LOAD FAILED

Reason:
Jobflow Monitor was unable to load z/OS name/token retrieve services. The monitor
terminates.

Action:
For assistance, contact CA Support at ca.com/support.

340 Message Reference Guide

 CAL2 Messages

CAL2M128E

(inst) CA7LOG event not active

Reason:
The CAIENF event that Jobflow Monitor requires is inactive. The monitor (inst)
terminates.

Action:
Perform the following actions:
■ Activate the CA7LOG event in CAIENF.
■ Restart the monitor.

If you continue to receive the message after successfully installing the event, contact CA
Support at ca.com/support for assistance.

CAL2M129W

(inst) Unexpected return from L2JFEV00 xxxxxxxx yyyyyyyy zzzzzzzz

Reason:
An event listener function returned an unexpected return code. The monitor (inst)
continues to listen for incoming events. The value of xxxxxxxx is the return code from
L2JFEV00. The values of yyyyyyyy and zzzzzzzz are for R15 and R0 returned by #ENF.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M130I

(inst) Work request ready: id key

Reason:
The event listener received a work request with the id and key listed for the instance
listed. This is an informational message.

Action:
None.

Chapter 2: AFM - CA7R Messages 341

CAL2 Messages

CAL2M131I

(inst) Event listener termination requested

Reason:
Jobflow Monitor is terminating the event listener for the indicated monitor (inst). This is
a status message.

Action:
None.

CAL2M132I

(inst) nnnnnnnn events recovered for warm start

Reason:
The event listener retrieved nnnnnnnn events from CAIENF during warm start
processing. This is a status message.

Action:
None.

CAL2M133E

(inst) Invalid parameter list

Reason:
The event listener was called with an invalid parameter list. The monitor (inst)
terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M134E

(inst) JFCNTWA pointer invalid

Reason:
The event listener was called with an invalid control block address. The monitor (inst)
terminates.

Action:
For assistance, contact CA Support at ca.com/support.

342 Message Reference Guide

 CAL2 Messages

CAL2M135E

(inst) JFWA pointer invalid

Reason:
The event listener was called with an invalid control block address. The monitor (inst)
terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M136E

(inst) STOP ECB pointer invalid

Reason:
The event listener was called with an invalid event control block address. The monitor
(inst) terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M137E

(inst) ENF not active

Reason:
The event listener did not receive events because CAIENF was not active. Event listener
functions are retried periodically until CAIENF is restarted or until the indicated monitor
(inst) is terminated.

Action:
If you continue to receive the message after CAIENF is restarted, contact CA Support at
ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 343

CAL2 Messages

CAL2M138E

(inst) CA7LOG event not defined

Reason:
The CAIENF event that Jobflow Monitor requires has not been defined. The monitor
(inst) terminates.

Action:
Perform the following actions:
■ Verify the installation of the DCM (CAL2DCM3) for the CA7LOG event.
■ Restart the monitor.

If you continue to receive the message after successfully installing the event, contact CA
Support at ca.com/support for assistance.

CAL2M139E

(inst) LOAD failed for L2JFEV00

Reason:
A module required for event processing could not be loaded. The monitor (inst)
terminates.

Action:
Perform the following actions:
■ Ensure that L2JFEV00 is in a library that Jobflow Monitor can access.
■ Restart the monitor.

If you continue to receive the message after performing these actions, contact CA
Support at ca.com/support for assistance.

344 Message Reference Guide

 CAL2 Messages

CAL2M140E

(inst) LOAD failed for L2JFQJDO

Reason:
A module required for event processing could not be loaded. The monitor (inst)
terminates.

Action:
Perform the following actions:
■ Ensure that L2JFQJDO is in a library that Jobflow Monitor can access.
■ Restart the monitor.

If you continue to receive the message after performing these actions, contact CA
Support at ca.com/support for assistance.

CAL2M141E

(inst) LOAD failed for SASSSTAT

Reason:
A module required for event processing could not be loaded. The monitor (inst)
terminates.

Action:
Perform the following actions:
■ Ensure that SASSSTAT is in a library that Jobflow Monitor can access.
■ Restart the monitor.

If you continue to receive the message after performing these actions, contact CA
Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 345

CAL2 Messages

CAL2M142E

(inst) LOAD failed for SASSLG00

Reason:
A module required for event processing could not be loaded. The monitor (inst)
terminates.

Action:
Perform the following actions:
■ Ensure that SASSLG00 is in a library that that Jobflow Monitor can access.
■ Restart the monitor.

If you continue to receive the message after performing these actions, contact CA
Support at ca.com/support for assistance.

CAL2M143E

(inst) Error return from L2JFEV00 xxxxxxxx yyyyyyyy zzzzzzzz

Reason:
An event listener function failed. The monitor (inst) terminates. If xxxxxxxx is 18, the
#ENF macro returned an error. yyyyyyyy and zzzzzzzz are the values of R15 and R0
returned by #ENF.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M144I

(inst) Event listener initializing

Reason:
The event listener for monitor (inst) is starting. This is a status message.

Action:
None.

346 Message Reference Guide

 CAL2 Messages

CAL2M145I

(inst) Starting recovery at yydddhhmmssth

Reason:
The event listener retrieves events needed for warm start processing. These events are
the CA7LOG events created during the warm start recovery interval. The interval begins
at the date and time in the message and ends at the date and time that the monitor
started. The #ENF CONTROL function requires the format of the date and time in the
message. The time portion of the message is presented in Coordinated Universal Time
(UTC) format. This message is a status message.

Action:
None.

CAL2M146I

(inst) No events recovered for warm start

Reason:
The event listener did not recover CA7LOG events created by the CA Workload
Automation SE instance (inst) during the warm start recovery interval. This is the period
that interval begins at the date and time in the CAL2M145I message and ends at the
date and time the monitor started. This is a status message. This message is issued with
Message CAL2M149W.

Action:
None if CA Workload Automation SE (inst) was not active during the warm start
recovery interval.

CAL2M147E

(inst) Could not extract SMF ID

Reason:
The event listener could not extract the SMF ID from the event for the instance listed in
the message.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 347

CAL2 Messages

CAL2M148E

(inst) Unrecognized return code rc

Reason:
The event listener received an unexpected return code when handling the log message.
The return code (rc) and instance are listed in the message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M149W

(inst) CA7LOG event not recorded by ENF

Reason:
CAIENF is not recording the event used by JFM (CA7LOG). This is a status message.
However, if CPM=JFM is specified on the OPTIONS statement in the initialization file for
(inst), CA7LOG events must be recorded to help ensure the accuracy of CPM.

Note: For information about recording CAIENF events, see the CA Common Services
documentation.

Action:
None.

CAL2M150S

Monitor(xxxx) Terminating - Unable to create WorkQueue for Main

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the specified
monitor instance (xxxx) Main thread. The monitor instance terminates. Review any
messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

348 Message Reference Guide

 CAL2 Messages

CAL2M151S

Monitor(xxxx) Terminating - Unable to create processLater list

Reason:
Jobflow Monitor was unable to create the required processLater list object for the
specified monitor instance (xxxx). The monitor instance terminates. Review any Jobflow
Monitor messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M152S

Monitor(xxxx) Terminating - rwlockattr_init() error

Reason:
Jobflow Monitor encountered an error trying to create and initialize the query lock for
the specified monitor instance (xxxx). The monitor instance terminates. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M153S

Monitor(xxxx) Terminating - rwlockattr_setpshared() error

Reason:
Jobflow Monitor encountered an error trying to create and initialize the query lock for
the specified monitor instance (xxxx). The monitor instance terminates. A CAL2M080E
message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 349

CAL2 Messages

CAL2M154S

Monitor(xxxx) Terminating - rwlock_init() error

Reason:
Jobflow Monitor encountered an error trying to create and initialize the query lock for
the specified monitor instance (xxxx). Processing continues. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M155E

Monitor(xxxx) rwlockattr_destroy() error

Reason:
Jobflow Monitor encountered an error trying to destroy the attributes for the query lock
for the specified monitor instance (xxxx). Processing continues. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M156E

Monitor(xxxx) rwlock_destroy() error at instance termination

Reason:
Jobflow Monitor encountered an error trying to destroy the query lock for or the
specified monitor instance (xxxx). Processing continues. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

350 Message Reference Guide

 CAL2 Messages

CAL2M157W

Monitor(xxxx) Unable to destroy workQueue object at instance end

Reason:
Jobflow Monitor encountered an error trying to destroy the work queue object for the
specified monitor instance (xxxx). Processing continues. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M158E

Monitor(xxxx) Terminating – CPM must be active for WARM start

Reason:
The Jobflow Monitor TYPE(WARM) parameter was specified in member JBFLWMN.
Attempts to interact with the servername specified in CPMCCI(servername) parameter,
or the default servername CPMSERVER, failed because CPM had not been started.
Message CAL2M159I follows this message.

Action:
When using the TYPE(WARM) parameter, verify that CPM is up and running before
attempting to start Jobflow Monitor.

CAL2M159E

Monitor(xxxx) termination requested due to error

Reason:
The Jobflow Monitor instance specified in xxxx has been stopped. Message CAL2M158E
precedes this message. This message is informational only.

Action:
See Message CAL2M158E for the specific action required.

Chapter 2: AFM - CA7R Messages 351

CAL2 Messages

CAL2M160S

Monitor(xxxx) Terminating - Unable to create WorkQueue for Status Update

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the specified
monitor instance (xxxx) StatusUpdate thread. The monitor instance terminates. Review
any messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M161S

Monitor(xxxx) Terminating - Unable to create Status Update Thread

Reason:
Jobflow Monitor was unable to create the StatusUpdate thread for the specified
monitor instance (xxxx). The monitor instance terminates. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M162S

Monitor(xxxx) Terminating - Unable to create WorkQueue for Structure Update

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the specified
monitor instance (xxxx) StructureUpdate thread. The monitor instance terminates.
Review any messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

352 Message Reference Guide

 CAL2 Messages

CAL2M163S

Monitor(xxxx) Terminating - Unable to create Structure Update Thread

Reason:
Jobflow Monitor was unable to create the StructureUpdate thread for the specified
monitor instance (xxxx). The monitor instance terminates. A CAL2M080E message
sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M164S

Monitor(xxxx) Terminating - Unable to create WorkQueue for Query Thread

Reason:
Jobflow Monitor was unable to create the required WorkQueue object for the specified
monitor instance (xxxx) Query thread. The monitor instance terminates. Review any
messages that preceded this message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M165S

Monitor(xxxx) Terminating - Unable to create Query Thread

Reason:
Jobflow Monitor was unable to create the Query thread for the specified monitor
instance (xxxx). The monitor instance terminates. A CAL2M080E message sometimes
follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 353

CAL2 Messages

CAL2M166S

Monitor(xxxx) Terminating - Unable to create ActiveJobTable

Reason:
Jobflow Monitor was unable to create the Active Job Table for the specified monitor
instance (xxxx). The monitor instance terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M167E

Monitor(xxxx) - Invalid XML request was received

Reason:
An XML request was received in Jobflow Monitor, and the request does not contain a
known type. The request is not processed.

Action:
Verify the XML request and verify that it contains a valid and known type and valid
parameters.

For assistance, contact CA Support at ca.com/support.

CAL2M168S

Monitor(xxxx) Terminating - idle Jobstream rwlock_init() error

Reason:
Jobflow Monitor encountered an error trying to create and initialize the idle Jobstream
lock for the specified monitor instance (xxxx). Processing continues. A CAL2M080E
message can follow with more information.

Action:
For assistance, contact CA Support at ca.com/support.

354 Message Reference Guide

 CAL2 Messages

CAL2M169E

Monitor(xxxx) idle Jobstream rwlock_destroy() error at termination

Reason:
Jobflow Monitor encountered an error trying to destroy the idle Jobstream lock for the
specified monitor instance (xxxx). Processing continues. A CAL2M080E message can
follow with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M170E

Monitor(instance) Terminating - Call to module L2JFDBIO RC(nn) token(value)

Reason:
An error occurred during initialization of the monitoring environment for the specified
monitor instance (instance) listed in the message. The return code from L2JFDBIO (nn) is
listed in the message along with the address of the JFDBIO control block (value). The
following return codes and reasons are the most likely cause of the problem:
20
CA7ONL for the specified tracking instance is not active on the LPAR hosting Jobflow
Monitor. Ensure that CA7ONL for the instance is completely initialized, and then
issue a modify to restart the instance in JFM.
24
DBPARMS could not be determined for the specified tracking instance.

44
JFM cannot load the module SASSSTAT.

48
JFM cannot locate the agent job type table (SVTAGTBL) in the monitored instance.

52
JFM cannot load module L2JFTC00.

64
The release of CA7ONL associated with the specified tracking instance is
incompatible with this release of Jobflow Monitor.

Chapter 2: AFM - CA7R Messages 355

CAL2 Messages

Action:
Perform the following actions:
■ Review surrounding messages for more detailed information.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2M171I

Monitor(xxxx) is stopping

Reason:
The monitor instance (xxxx) received a request to stop.

Action:
None.

CAL2M172E

Monitor(xxxx) received unexpected term from thread(value)

Reason:
The monitor instance (xxxx) received an unexpected thread termination request. A
restart of the monitor instance is required.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M173I

Monitor(xxxx) has ended

Reason:
The monitor instance (xxxx) has ended.

Action:
None.

356 Message Reference Guide

 CAL2 Messages

CAL2M174I

Monitor(xxxx) has started

Reason:
The monitor instance (xxxx) has started.

Action:
None.

CAL2M175I

Monitor(xxxx) warm starting from yyyy-mm-ddThh:mm:ss.000000-xx:zz

Reason:
Jobflow Monitor is initiating a warm start for the specified monitor instance (xxxx) from
the date and time specified. The xx:zz represents the time offset from the Coordinated
Universal Time (UTC) represented by hh:mm:ss.000000.

Action:
None.

CAL2M176I

Monitor(xxxx) has completed warm start processing

Reason:
Jobflow Monitor has completed the warm start for the specified monitor instance
(xxxx).

Action:
None.

CAL2M177I

Monitor(xxxx) found no CPM flows to recover

Reason:
Jobflow Monitor found no CPM flows that needed recovery for the specified monitor
instance (xxxx).

Action:
None.

Chapter 2: AFM - CA7R Messages 357

CAL2 Messages

CAL2M178I

Monitor(xxxx) text

Reason:
An error occurred for the monitor instance (xxxx) listed in the message. This message
provides more detailed information surrounding the error that occurred.

Action:
Perform the following actions:
■ Review surrounding messages for more detailed information.
■ Take appropriate action that is based on the text that the message provides.
■ For assistance, contact CA Support at http://ca.com/support.

CAL2M179I

Monitor(xxxx) TCP/IP Terminal Host Addr(xxxxxxxx), PORT(nnnnn)

Reason:
The Jobflow Monitor instance Terminal Host Address and Port are listed in this
informational message.

Action:
None.

CAL2M181E

ProcessLaterList pthread_mutex_attr_init() error

Reason:
An error occurred when calling pthread_mutex_attr_init. This message is followed by a
CAL2M080 message containing the reason for the error.

Action:
For assistance, contact CA Support at ca.com/support.

358 Message Reference Guide

 CAL2 Messages

CAL2M182E

ProcessLaterList pthread_mutex_attr_settype() error

Reason:
An error occurred when calling pthread_mutex_attr_settype. This message is followed
by a CAL2M080E message containing the reason for the error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M183E

ProcessLaterList pthread_mutex_attr_setkind() error

Reason:
An error occurred calling pthread_mutex_attr_setkind_np. This message is followed by
a CAL2M080E message containing the reason for the error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M184E

ProcessLaterList pthread_mutex_init() error

Reason:
An error occurred when calling pthread_mutex_init. This message is followed by a
CAL2M080E message containing the reason for the error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M185E

Unable to create the processLater linklist object

Reason:
An error occurred when creating the linklist object.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 359

CAL2 Messages

CAL2M186S

Monitor(xxxx) Terminating - Unable to create ActiveCPTable

Reason:
Jobflow Monitor was unable to create the ActiveCPTable for the specified monitor
instance (xxxx). The monitor instance terminates.

Action:

For assistance, contact CA Support at ca.com/support.

CAL2M190E

WorkQueue rwlockattr_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the WorkQueue object. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M191E

WorkQueue rwlockattr_setpshared() error

Reason:
Jobflow Monitor was unable to set up serialization for the WorkQueue object. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M192E

WorkQueue rwlock_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the WorkQueue object. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

360 Message Reference Guide

 CAL2 Messages

CAL2M193E

WorkQueue mutex_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the WorkQueue object. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M194E

WorkQueue cond_init() error

Reason:
Jobflow Monitor was unable to set up serialization for the WorkQueue object. A
CAL2M080E message sometimes follows this message with more information.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M195E

WorkQueue object validation error occurred - rc=rc

Reason:
An internal error occurred in Jobflow Monitor when it was attempting to validate an
object that entered the work queue. The return code (rc) is listed in the message. The
invalid work queue object is ignored, and processing continues.

Action:

For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 361

CAL2 Messages

CAL2M200E

Call to L2JFCONS failed

Reason:
A failure occurred in the interface to the operator console. Jobflow Monitor may or may
not respond to operator commands.

Action:
Perform the following actions:
■ Cancel the address space.
■ Restart it.

For assistance, contact CA Support at ca.com/support.

CAL2M201E

rtn unable to get storage for SSL object, len=nnnn

Reason:
The routine rtn attempted to obtain nnnn bytes of storage for an SSL management
object, and the storage request was unsuccessful.

Action:
Perform the following tasks:
■ Increase the MEMLIMIT size on the Jobflow Monitor started task EXEC statement.
■ Next, restart the Jobflow Monitor task.

CAL2M202E

rtn unable to open key database

Reason:
SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable
System SSL. The key database that the KEYDB DD in the Jobflow Monitor startup JCL
specified could not be opened in routine rtn.

Action:
Perform the following actions:
■ Specify a KEYDB DD statement with a valid path to a key database.
■ Verify that Jobflow Monitor is granted READ access to the key database.

362 Message Reference Guide

 CAL2 Messages

CAL2M203E

rtn unable to obtain key database path name, rc=nnn

Reason:
SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable
System SSL. The path name of the key database could not be obtained from the KEYDB
DD in the Jobflow Monitor startup JCL in routine rtn.

Action:
Perform the following actions:
■ Specify a KEYDB DD statement with a valid path to a key database.
■ Verify that Jobflow Monitor is granted READ access to the key database.
For assistance, contact CA Support at ca.com/support.

CAL2M204E

rtn error closing key database, rc=nnn(errno)

Reason:
SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable
System SSL. The key database was successfully opened, but an error occurred
attempting to close the key database in routine rtn.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M205E

rtn unable to open password stash file

Reason:
SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable
System SSL. The key database password stash file that the STASH DD in the Jobflow
Monitor startup JCL specified could not be opened in routine rtn.

Action:
Perform the following actions:
■ Specify a STASH DD statement with a valid path to a password stash file.
■ Verify that Jobflow Monitor is granted READ access to the password stash file.

Chapter 2: AFM - CA7R Messages 363

CAL2 Messages

CAL2M206E

rtn unable to obtain password stash file path name, rc=nnn

Reason:

SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable

System SSL. The path name of the key database password stash file could not be
obtained from the STASH DD in the Jobflow Monitor startup JCL in routine rtn.

Action:
Perform the following actions:
■ Specify a STASH DD statement with a valid path to a password stash file.
■ Verify that Jobflow Monitor is granted READ access to the password stash file.
For assistance, contact CA Support at ca.com/support.

CAL2M207E

rtn error closing password stash file, rc=nnn(errno)

Reason:
SSLRINGTYPE(KDB) was specified in the JBFLWAS configuration member to enable
System SSL. The key database password stash file was successfully opened, but an error
occurred attempting to close the password stash file in routine rtn.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M208E

rtn error opening SSL environment, rc=nnn

Reason:
SSLRINGTYPE(KDB) or SSLRINGTYPE(SAF) was specified in the JBFLWAS configuration
member to enable System SSL. An error occurred attempting to open the SSL
environment. nnn shows the gsk_environment_open function return code.

Action:
Examine the Jobflow Monitor log for additional diagnostic information.
For assistance, contact CA Support at ca.com/support.

364 Message Reference Guide

 CAL2 Messages

CAL2M209E

rtn error initializing SSL environment, rc=nnn

Reason:
SSLRINGTYPE(KDB) or SSLRINGTYPE(SAF) was specified in the JBFLWAS configuration
member to enable System SSL. An error occurred attempting to initialize the SSL
environment. nnn shows the gsk_environment_init function return code. Possible errors
include the following items:
■ Invalid or inaccessible key database.
■ Invalid or inaccessible key database password stash file.
■ Invalid key database password is contained in the password stash file.
■ Invalid or unauthorized user ID specified in the SAFRING configuration parameter.
■ Invalid or keyring name is specified in the SAFRING configuration parameter.

Action:
Perform the following actions:
■ Examine the Jobflow Monitor log for additional diagnostic information.
■ Correct configuration parameters as necessary.
■ Verify that proper access is granted to secured resources.
For assistance, contact CA Support at ca.com/support.

CAL2M210I

STOP requested for Jobflow Monitor address space

Reason:
The operator issued a stop command. The Jobflow Monitor address space stops.

Action:
None.

CAL2M211I

Command: value received

Reason:
The operator issued the specified command. Jobflow Monitor processes it.

Action:
None.

Chapter 2: AFM - CA7R Messages 365

CAL2 Messages

CAL2M212I

Command will be performed for Monitors: value

Reason:
The operator command issued is sent to the list of monitor instances for processing.

Action:
None.

CAL2M219E

An error occurred when stopping the Jobflow Monitor address space

Reason:
An error occurred in Jobflow Monitor when attempting to stop all processing threads.
One or more threads were unable to stop. Processing continues.

Action:
In this case, it is sometimes necessary to cancel the Jobflow Monitor address space to
bring it down. For assistance, contact CA Support at ca.com/support.

CAL2M220E

Command: value not processed

Reason:
The operator issued the specified command. Jobflow Monitor attempted to process it,
but errors occurred in the processing.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Review any Jobflow Monitor messages that may have been issued previously.
■ Correct command syntax as directed.
■ Verify that the monitor instance is active. If not, start the instance.
■ Reissue command.

366 Message Reference Guide

 CAL2 Messages

CAL2M221E

Invalid keyword: value

Reason:
An invalid keyword was detected.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

CAL2M222W

DDNAME CAJFCSV is missing and is required

Reason:
The CAJFCSV DDNAME is missing and is required for the CSV command. As a result, the
command is not processed.
This output file is required for the CSV command. The file must have been allocated with
the following attributes: RECFM=VB, LRECL=1028, BLKSIZE=6144, DSORG=PS. The file
must be allocated on a disk with sufficient space for the designated flow.

Action:
Perform the following actions:
■ Add the CAJFCSV DDNAME to the Jobflow Monitor task.
■ Restart the Jobflow Monitor task.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 2: AFM - CA7R Messages 367

CAL2 Messages

CAL2M223E

Invalid Refresh interval: value Must be 1-60 minutes

Reason:
The specified refresh interval is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

CAL2M224E

Invalid Monitor Span time: value Must be 1-72 hours

Reason:
The specified span value is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

368 Message Reference Guide

 CAL2 Messages

CAL2M225E

Invalid History period: value Must be 1-12 hours

Reason:
The specified history period value is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

CAL2M226E

Invalid or missing parameter on keyword ALTER: value

Reason:
An invalid or missing parameter was detected.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

Chapter 2: AFM - CA7R Messages 369

CAL2 Messages

CAL2M227E

Invalid CSV schdID value: value Must be 0-999

Reason:

The specified CSV schdID value is incorrect.

Note: For more information about the Jobflow Monitor commands, see the Interface
Reference Guide.

Action:

Perform the following actions:

■ Correct the command syntax.
■ Reissue the command.

CAL2M228E

Invalid CSV level value: value Must be 1-99

Reason:
The specified CSV level value is incorrect.

Note: For more information about the Jobflow Monitor commands, see the Interface
Reference Guide.

Action:

Perform the following actions:

■ Correct the command syntax.
■ Reissue the command.

370 Message Reference Guide

 CAL2 Messages

CAL2M229E

Invalid CSV depth value: value Must be 1-99

Reason:
The specified CSV depth value is incorrect.

Note: For more information about the Jobflow Monitor commands, see the Interface
Reference Guide.

Action:

Perform the following actions:

■ Correct the command syntax.
■ Reissue the command.

CAL2M230E

Invalid LOGLEVEL value value

Reason:
The value specified on the LOGLEVEL oommand is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

Chapter 2: AFM - CA7R Messages 371

CAL2 Messages

CAL2M231E

Invalid or missing parameter on keyword FACILITY: value

Reason:
The value that is specified on the FACILITY command is incorrect.
Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct the command syntax.
■ Reissue the command.

CAL2M232W

Error occurred opening DDNAME CAJFCSV

Reason:
An error occurred when opening the file associated with DDNAME CAJFCSV. This output
file is required for the CSV command. The file must have been allocated with the
following attributes: RECFM=VB, LRECL=1028, BLKSIZE=6144, DSORG=PS. The file must
be allocated on a disk with sufficient space for the designated flow. As a result, the CSV
command is not processed.

Action:
Perform the following actions:
■ Correct the file attributes associated with the output CAJFCSV file.
■ Ensure that the file has sufficient space.
■ Restart the Jobflow Monitor task using the corrected file.
■ Retry the CSV command.
■ For assistance, contact CA Support at http://ca.com/support.

372 Message Reference Guide

 CAL2 Messages

CAL2M233E

Invalid parameter on keyword ODUMP: value

Reason:
The specified ODUMP value is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct the command syntax.
■ Reissue the command.

CAL2M234E

Invalid parameter on keyword QUERY: value

Reason:
The specified QUERY value is incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct the command syntax.
■ Reissue the command.

Chapter 2: AFM - CA7R Messages 373

CAL2 Messages

CAL2M235E

Invalid parameter on keyword STATUS: value

Reason:
An invalid parameter was detected.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

CAL2M236E

INSTANCE keyword not specified, command rejected

Reason:
The required keyword INSTANCE was not specified.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

374 Message Reference Guide

 CAL2 Messages

CAL2M237E

INSTANCE keyword: value invalid, command rejected

Reason:
The value of the keyword INSTANCE was incorrect.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct command syntax.
■ Reissue the command.

CAL2M238W

The requested INSTANCE(S) are not available: value

Reason:
The operator command issued requested the listed monitor instances, but they are not
currently active.

Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Wait until the CA Workload Automation SE instances become active.
■ Start the monitor instances.
■ Reissue the command.

CAL2M239W

The requested INSTANCE(S) are already active: value

Reason:
An operator command was issued to start the listed monitor instances, but they are
already active. The command is ignored.

Action:
None.

Chapter 2: AFM - CA7R Messages 375

CAL2 Messages

CAL2M241I

The requested INSTANCE(S) will be started: value

Reason:
An operator command was issued to start the listed monitor instances.

Action:
None.

CAL2M242I

History interval will be set to value hours

Reason:
An ALTER HISTORY command was issued. The HISTORY interval is changing to the
specified interval.

Action:
None.

CAL2M243I

Refresh interval will be set to value minutes

Reason:
An ALTER REFRESH command was issued. The REFRESH interval is changing to the
specified interval.

Action:
None.

CAL2M244I

Span will be set to value hours

Reason:
An ALTER SPAN command was issued. The SPAN interval is changing to the specified
interval.

Action:
None.

376 Message Reference Guide

 CAL2 Messages

CAL2M245I

CSV data requested for the entire jobflow

Reason:
The CSV data request is for processing all jobs within the job flow.

Action:
None.

CAL2M246I

CSV data requested for the flow named: name

Reason:
The CSV data request is for processing for the specific job flow name that is listed in the
message.

Action:
None.

CAL2M247I

CSV data requested before and after job/schdid: jobname-schid, for number levels

Reason:
The CSV data request is processed for the jobs before and after the jobname and schid
listed in the message for the number of levels indicated.

Action:
None.

CAL2M248I

CSV data requested starting at job/schid: jobname schid, and depth: value

Reason:
The CSV data request is processed starting at the jobname and schid listed in the
message for the depth value indicated.

Action:
None.

Chapter 2: AFM - CA7R Messages 377

CAL2 Messages

CAL2M249I

LOGLEVEL will be set to value

Reason:
A LOGLEVEL command was issued. The LOGLEVEL is set to the value listed in the
message.

Action:
None.

CAL2M250I

FACILITY will be set to value

Reason:
A FACILITY command was issued. The FACILITY is set to the value listed in the message.

Action:
None.

CAL2M251I

Dump object will be set value

Reason:
The ODUMP data request is set to the value that is listed in the message.

Action:
None.

CAL2M252I

Query requested for jobStream: name

Reason:
The QUERY data request is entered for the name of the job stream that is listed in the
message.

Action:
None.

378 Message Reference Guide

 CAL2 Messages

CAL2M253I

Query requested for job: name

Reason:
The QUERY data request has been entered for the name of the job listed in the message.

Action:
None.

CAL2M254I

STOP monitor instance requested for: value

Reason:
A STOP command was issued for the list instances. The stop commands are routed for
processing.

Action:
None.

CAL2M256W

INSTANCE CA7n is terminating, retry START

Reason:
A STOP command for a monitor is in progress when a START command is issued.

Action:
Reissue the START command after receiving the following message:

CAL2M173I Monitor(CA7n) has ended

CAL2M257I

PRINTLOG request was processed to DDNAME: ddname

Reason:
The PRINTLOG command was issued and was processed successfully. The results of the
log are written to the ddname listed in the message.

Action:
None.

Chapter 2: AFM - CA7R Messages 379

CAL2 Messages

CAL2M258I

text

Reason:
Issuing the Jobflow Monitor HELP PRINTLOG command generates this message. The
message text varies. This is an informational message.

Action:
None.

CAL2M260E

Invalid parameter on keyword DLL: value

Reason:
An invalid parameter was detected.
Note: For more information about Jobflow Monitor commands, see the Interface
Reference Guide.

Action:
Perform the following actions:
■ Correct the command syntax.
■ Reissue the command.

CAL2M261I

CLEARLOG request was processed

Reason:
The CLEARLOG command was issued and was processed successfully. This message is
informational.

Action:
None.

380 Message Reference Guide

 CAL2 Messages

CAL2M262I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP CLEARLOG command
being issued. The message text varies. This message is informational.

Action:
None.

CAL2M270I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP or HELP HELP
command being issued. The message text varies. This is an informational message.

Action:
None.

CAL2M271I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP INSTANCE command
being issued. The message text varies. This is an informational message.

Action:
None.

CAL2M272I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP ALTER command
being issued. The message text varies. This is an informational message.

Action:
None.

Chapter 2: AFM - CA7R Messages 381

CAL2 Messages

CAL2M273I

text

Reason:
This message is generated when the Jobflow Monitor command HELP LOGLEVEL is
issued. The message text varies. This is an informational message.

Action:
None.

CAL2M274I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP RESOLVE command
being issued. The message text varies. This is an informational message.

Action:
None.

CAL2M275I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP STATUS command
being issued. The message text varies. This is an informational message.

Action:
None.

CAL2M276I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP START command
being issued. The message text varies. This is an informational message.

Action:
None.

382 Message Reference Guide

 CAL2 Messages

CAL2M277I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP STOP command being
issued. The message text varies. This is an informational message.

Action:
None.

CAL2M278E

Error retrieving process data

Reason:
An error occurred processing message data in L2JFCMD in routine getProcessData.

Action:
Perform the following actions:
■ Reenter the last command to Jobflow Monitor that caused the error.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2M279I

text

Reason:
This message is generated as a result of the Jobflow Monitor HELP FACILITY command
being issued. The message text varies. This message is informational.

Action:
None.

Chapter 2: AFM - CA7R Messages 383

CAL2 Messages

CAL2M280I

JOBFLOW MONITOR STORAGE REPORT

Reason:
A Jobflow Monitor STATUS(STORAGE) command was issued. This is an informational
message.

Action:
None.

CAL2M281I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the total, in use and available amount of Heap Storage Data. This is an informational
message.

Action:
None.

CAL2M282I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the current active threads, including the Current and High Water Mark (HWM) for 64
byte, 128 byte, 256 byte, 512 byte, 1024 byte and 2048 byte. This is an informational
message.

Action:
None.

384 Message Reference Guide

 CAL2 Messages

CAL2M283I

instance INSTANCE INFORMATION

Reason:
A Jobflow Monitor STATUS command was issued and the instance is listed in the
message. This is an informational message.

Action:
None.

CAL2M284I

JOBFLOW MONITOR STATUS - type REPORT

Reason:
This message is generated as a result of the Jobflow Monitor STATUS command being
issued. The message displays the type of report. This is an informational message.

Action:
None.

CAL2M285I

Assembly Information: version

Reason:
A Jobflow Monitor STATUS command was issued. The message displays the current
version of Jobflow Monitor. This is an informational message.

Action:
None.

CAL2M286I

state Instances: instance

Reason:
This message is generated as a result of the Jobflow Monitor STATUS command being
issued. The message displays the current state of the instance (Active, Starting or
Terminating). This is an informational message.

Action:
None.

Chapter 2: AFM - CA7R Messages 385

CAL2 Messages

CAL2M287I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the Process Data ID, User, MVS User, Size, System Time, User Time, Total Time, and
when the process started. This is an informational message.

Action:
None.

CAL2M288I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the current History, Span, Refresh Rate, DBPARMS DD (if applicable), Logging Severity,
and when the process started and stopped if applicable. This is an informational
message.

Action:
None.

CAL2M289I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the current Event information, including the Count, the Time Received, the Time
Created, and the Last Request if applicable. This is an informational message.

Action:
None.

386 Message Reference Guide

 CAL2 Messages

CAL2M290I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the current Object Counts, including the Current and High Water Mark (HWM) for Job,
Dataset, JobStream, Requirement, Requiredby, XML, and System. This is an
informational message.

Action:
None.

CAL2M291I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message text varies and shows
the current Total Cell Pool Counts, including the Current and High Water Mark (HWM)
for 64 byte, 128 byte, 256 byte, 512 byte, 1024 byte, and 2048 byte. This is an
informational message.

Action:
None.

CAL2M292I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message shows the Jobflow
Monitor Address Space options currently in effect. The message text varies. These
values come from the values in the CAJFPARM file, member JBFLWAS, that were used
when Jobflow Monitor was started.

Action:
None.

Chapter 2: AFM - CA7R Messages 387

CAL2 Messages

CAL2M293I

text

Reason:
A Jobflow Monitor STATUS command was issued. The message shows the Jobflow
Monitor Event Configuration options currently in effect. The message text varies. These
values come from the values in the CAJFPARM file, member JBFLWEV, that were used
when Jobflow Monitor was started.

Action:
None.

CAL2M295E

failed to get DLL information for name

Reason:
Jobflow Monitor was unable to obtain DLL information about the module name listed in
the message. The module must be a LE conforming module to obtain the DLL
information.

Action:
Verify the spelling and reenter the name of a LE conforming module to obtain the DLL
information.

CAL2M296E

module is an invalid DLL name

Reason:
The module name listed in the message is an invalid Jobflow Monitor DLL module name.

Action:
Enter the name of a valid LE conforming module to obtain the DLL information.

388 Message Reference Guide

 CAL2 Messages

CAL2M300W

Monitor(xxxx) unable to validate starting job(name) of critical path(name)

Reason:
CPM requested that the monitor instance (xxxx) return information about jobs in the
specified critical path. The monitor was unable to locate the starting job in its current
workload. The critical path is not monitored.

Action:
Validate the definition of the critical path in the CA Workload Automation SE database.

CAL2M301W

Monitor(xxxx) unable to validate ending job(name) of critical path(name)

Reason:
CPM requested that the monitor instance (xxxx) return information about jobs in the
specified critical path. The monitor was unable to validate that the ending job was a
valid CA 7 WA job. The critical path is not monitored.

Action:
Validate the definition of the critical path, the ending job in the CA Workload
Automation SE database, or both.

CAL2M310S

Terminating - Unable to create SSL management object

Reason:
SSLRINGTYPE(KDB) or SSLRINGTYPE(SAF) was specified in the JBFLWAS configuration
member to enable System SSL. An error occurred attempting to create an SSL
management object. The Jobflow Monitor terminates.

Action:
Review the previous error messages to determine the underlying cause.
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 389

CAL2 Messages

CAL2M311E

Error establishing SSL environment, SSL is unavailable

Reason:
SSLRINGTYPE(KDB) or SSLRINGTYPE(SAF) was specified in the JBFLWAS configuration
member to enable System SSL. An error occurred establishing the SSL environment. So,
Jobflow Monitor is unable to use SSL to secure data traffic. Jobflow Monitor continues
execution, but any PORT definitions specifying ENCR(SSL) are disabled.

Action:
Review previous error messages and the Jobflow Monitor log to determine the
underlying cause.
For assistance, contact CA Support at ca.com/support.

CAL2M312E

Error removing SSL environment

Reason:
SSLRINGTYPE(KDB) or SSLRINGTYPE(SAF) was specified in the JBFLWAS configuration
member to enable System SSL. A noncritical error occurred removing the SSL
environment during the Jobflow Monitor shutdown.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M313E

Invalid specification for SSLRINGTYPE: value

Reason:
The SSLRINGTYPE value that is specified is incorrect.
Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Correct the SSLRINGTYPE statement in CAJFPARM(JBFLWAS).

390 Message Reference Guide

 CAL2 Messages

CAL2M314E

Invalid specification for SSLCERTLABEL: value

Reason:
The SSLCERTLABEL value that is specified is incorrect.
Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Correct the SSLCERTLABEL statement in CAJFPARM(JBFLWAS).

CAL2M315E

Invalid specification for SAFRING: value

Reason:
The SAFRING value that is specified is incorrect.
Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Correct the SAFRING statement in CAJFPARM(JBFLWAS).

CAL2M316E

SSLCERTLABEL parameter requires SSLRINGTYPE parameter

Reason:
The SSLCERTLABEL parameter was specified, but the SSLRINGTYPE parameter was not
specified.
Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Specify a valid combination of SSLRINGTYPE and SSLCERTLABEL statements in
CAJFPARM(JBFLWAS).

Chapter 2: AFM - CA7R Messages 391

CAL2 Messages

CAL2M317E

SAFRING parameter requires SSLRINGTYPE(SAF) parameter

Reason:
The SAFRING parameter was specified, but the SSLRINGTYPE(SAF) parameter was not
specified.
Note: For more information about CAJFPARM(JBFLWAS) statements, see the Interface
Reference Guide.

Action:
Specify a valid combination of SSLRINGTYPE and SAFRING statements in
CAJFPARM(JBFLWAS).

CAL2M318W

ENCR(SSL) is invalid for NAME(portname), ENCR(NONE) forced

Reason:
The ENCR(SSL) parameter was specified for a PORT statement for a CPM port.
Note: For more information about CAJFPARM(JBFLWIP) statements, see the Interface
Reference Guide.

Action:
Correct the affected PORT statement in CAJFPARM(JBFLWIP).

CAL2M319W

ENCR(SSL) is unsupported, PORT statement bypassed

Reason:
The ENCR(SSL) parameter was specified for a PORT statement, and the required
statements to enable SSL support were not specified in CAJFPARM(JBFLWAS).
Note: For more information about CAJFPARM(JBFLWAS) and CAJFPARM(JBFLWIP)
statements, see the Interface Reference Guide.

Action:
Correct the affected PORT statement in CAJFPARM(JBFLWIP) or specify the required
statements to enable System SSL in CAJFPARM(JBFLWAS).

392 Message Reference Guide

 CAL2 Messages

CAL2M320W

ENCR invalid, PORT statement bypassed

Reason:
The ENCR value that is specified on the PORT statement is incorrect.
Note: For more information about CAJFPARM(JBFLWIP) statements, see the Interface
Reference Guide.

Action:
Correct the invalid ENCR parameter value on the PORT statement in
CAJFPARM(JBFLWIP).

CAL2M399E

rtn unable to get storage for LMP object, len=nnnn

Reason:
Routine rtn has attempted to obtain nnnn bytes of storage for an LMP object. The
storage request was unsuccessful.

Action:
Perform the following actions:
■ Increase the MEMLIMIT size on the Jobflow Monitor started task EXEC statement.
■ Next, restart the Jobflow Monitor task.

CAL2M400W

Error occurred opening USS directory

Reason:
Jobflow Monitor attempted to load durable subscriptions on a disk and encountered an
error trying to open the USS directory. The PATHNAME option found in the CAJFPARM
file, member JBFLWEV, indicates the USS directory. A CAL2M480W message with more
information can follow this message. Processing continues.
As a result of this error, durable subscriptions are not loaded into memory.

Action:
Verify that the PATHNAME option in the CAJFPARM file, member JBFLWEV, contains a
valid USS directory. Review the PATHNAME option for more information. Review
message CAL2M480W and take appropriate action that is based on the text in the
message. For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 393

CAL2 Messages

CAL2M401W

Error occurred closing USS directory

Reason:
Jobflow Monitor attempted to load durable subscriptions on a disk and encountered an
error trying to close the USS directory. The PATHNAME option found in the CAJFPARM
file, member JBFLWEV, indicates the USS directory. A CAL2M480W message can follow
this message with more information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

CAL2M402W

Error occurred opening file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to open a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

CAL2M403W

Unable to determine the size of file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to get the file statistics for a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

394 Message Reference Guide

 CAL2 Messages

CAL2M404W

Unable to get number bytes of storage for file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to get storage for a specific file.
The number of bytes in question and filename are listed in the message. The PATHNAME
option found in the CAJFPARM file, member JBFLWEV, indicates the filename in the USS
directory. A CAL2M480W message can follow with more information. Processing
continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. Increase the REGION size, the MEMLIMIT size, or both on the startup
Jobflow Monitor JCL and restart Jobflow Monitor. For assistance, contact CA Support at
ca.com/support.

CAL2M405W

Unable to read file: filename

Reason:

Jobflow Monitor processed durable subscriptions on a disk and encountered an error

trying to read a specific file.

The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 395

CAL2 Messages

CAL2M406W

Error occurred closing file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to close a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

CAL2M407W

Unable to parse XML document for file: filename, rc=return code

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to parse a specific file.
The return code is listed in the message. The PATHNAME option found in the CAJFPARM
file, member JBFLWEV, indicates the filename in the USS directory. A CAL2M480W
message can follow with more information. Processing continues.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M408W

Unable to obtain a query request block for file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to obtain a query request block for a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory.

Action:
For assistance, contact CA Support at ca.com/support.

396 Message Reference Guide

 CAL2 Messages

CAL2M409W

Unable to parse subscription for file: filename, rc=return code

Reason:

Jobflow Monitor encountered an error trying to parse a durable subscription in a

specific file. The filename of the durable subscription is listed in the message with the
return code. The PATHNAME option is found in the CAJFPARM file, member JBFLWEV.
The PATHNAME indicates the name of the USS file directory where durable
subscriptions are saved and processed from.

A CAL2M480W message can follow this message with more information. Processing
continues.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M410W

Subscription request is invalid for file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to verify a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 397

CAL2 Messages

CAL2M411W

Unable to create a new subscription for file: filename

Reason:
Jobflow Monitor processed durable subscriptions on a disk and encountered an error
trying to create a subscription for a specific file.
The PATHNAME option found in the CAJFPARM file, member JBFLWEV, indicates the
filename in the USS directory. A CAL2M480W message can follow with more
information. Processing continues.

Action:
Review message CAL2M480W and take appropriate action that is based on the text in
the message. For assistance, contact CA Support at ca.com/support.

CAL2M412W

Unable to get number bytes of storage for the jfsubComponentArea

Reason:
Jobflow Monitor initialized the global subscription control block and encountered an
error trying to get storage for the component area.
The number of bytes in question is listed in the message. A CAL2M413W message can
follow with more information. Processing continues.

Action:
Increase the REGION size, the MEMLIMIT size, or both on the startup Jobflow Monitor
JCL and restart Jobflow Monitor. For assistance, contact CA Support at ca.com/support.

CAL2M413W

Subscriptions will not be allowed for this execution of JFM

Reason:
A previous error accompanies this error describing the problem that occurred with
subscriptions in Jobflow Monitor. As a result, subscriptions are not allowed in Jobflow
Monitor for the duration of its processing. Processing continues.

Action:
Correct the problem that is listed and restart Jobflow Monitor. For assistance, contact
CA Support at ca.com/support.

398 Message Reference Guide

 CAL2 Messages

CAL2M414W

Terminating - Unable to establish subscription list lock

Reason:
Jobflow Monitor initialized the global subscription control block and encountered an
error trying to establish a mutex lock on the subscription list. A CAL2M413W message
accompanies this message with more information. Processing continues.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M415W

Terminating - Unable to establish durable subscription lock

Reason:
Jobflow Monitor initialized the global subscription control block and encountered an
error trying to establish a mutex lock on durable subscriptions. A CAL2M416W message
accompanies this message with more information. Processing continues.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M416W

Durable subscriptions will not be allowed for this execution of JFM

Reason:
A previous error accompanies this error describing the problem that occurred with
durable subscriptions in Jobflow Monitor. As a result, durable subscriptions are not
allowed in Jobflow Monitor for the duration of its processing. Processing continues.

Action:
Correct the problem that is listed and restart Jobflow Monitor. For assistance, contact
CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 399

CAL2 Messages

CAL2M417E

XML elements element1 and element2 are mutually exclusive

Reason:
The two XML elements that are listed in the message are mutually exclusive and cannot
be used in the same XML query simultaneously. Processing for this query terminates.

Action:
Correct and reissue the XML query.

CAL2M420I

CA 7 data extraction completed successfully

Reason:
Program L2JFBJAW completed, and the USS file containing the seed data was created.
The SYSPRINT file contains details, including the path and filename of the data.

Action:
Review the SYSPRINT file.

CAL2M421E

CA 7 data extraction was unsuccessful. See SYSPRINT for details.

Reason:
Program L2JFBJAW had errors. If a USS file was created, the contents are sometimes
incomplete. The SYSPRINT file contains detailed error messages, including return codes.

Action:
Review the SYSPRINT file and take appropriate action that is based on the text in the
messages. For assistance, contact CA Support at ca.com/support.

CAL2M422I

Data extract successfully started for instance

Reason:
An extract of CA 7 data has been successfully started for the listed CA 7 instance. This
message is informational.

Action:
None.

400 Message Reference Guide

 CAL2 Messages

CAL2M423I

Data extract continuing for instance; nnnnn jobs processed

Reason:
An extract of CA 7 data was previously started and is continuing for the listed CA 7
instance. This informational message lists the number of jobs processed.

Action:

None.

CAL2M424W

Data extract failed for instance; function=function, rc=rc

Reason:
An extract of CA 7 data has failed for the listed CA 7 instance. The message lists the
failing function and return code.

Action:
See message CAL2M425I for more diagnostic information. Take the appropriate action
that is based on the message text. For assistance, contact CA Support at
ca.com/support.

CAL2M425I

supplemental diagnostic information

Reason:
This informational message accompanies CAL2M424W and provides more diagnostic
information about the CA 7 data extract failure.

Action:
None.

Chapter 2: AFM - CA7R Messages 401

CAL2 Messages

CAL2M426I

Data extract successfully completed for instance

Reason:
An extract of CA 7 data has successfully completed for the listed CA 7 instance. This
message is informational.

Action:
None.

CAL2M480W

text

Reason:
A bad return code was received from a C/LE run-time function. C/LE generates the text
in this message, which further describes an error that has occurred. This message
usually appears as a result of another Jobflow Monitor message.

Action:
See the appropriate IBM documentation for more information.

CAL2M500E

Internal error occurred on virtual connection object, rc=rc

Reason:
An internal error occurred in ipGetCredentials as a result of calling ipValidateVconn. The
verification of a virtual connection object is not possible. As a result, the credentials on
the Authorization header from a connection are not verified. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

402 Message Reference Guide

 CAL2 Messages

CAL2M501E

No TCP/IP header was found on connection

Reason:
The TCP/IP header was missing on a client connection. As a result, the verification of the
credentials from the Authorization header is not possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M502E

Authorization header missing on connection

Reason:
The Authorization header was missing on a client connection. As a result, the
verification of the credentials from the Authorization header on the connection is not
possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M503E

Authorization value missing on connection

Reason:
The value on the Authorization header was missing on a client connection. As a result,
the verification of the credentials from the Authorization header on the connection is
not possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 403

CAL2 Messages

CAL2M504E

Authorization header is too short

Reason:
The Authorization header on a client connection is too short. As a result, the verification
of the credentials from the Authorization header on the connection is not possible. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M505E

Authorization header does not begin with Basic

Reason:
The Authorization header on a client connection does not begin with Basic. As a result,
the verification of the credentials from the Authorization header on the connection is
not possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M506E

Base64 decoding failed on connection, rc=rc

Reason:
The Base64 decoding failed on a client connection. As a result, the verification of the
credentials from the Authorization header on the connection is not possible. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

404 Message Reference Guide

 CAL2 Messages

CAL2M507E

No password found in authorization header

Reason:
No password was found in the authorization header on a client connection. As a result,
the verification of the credentials from the Authorization header on the connection is
not possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M508E

No userid found in authorization header

Reason:
No userid was found in the authorization header on a client connection. As a result, the
verification of the credentials from the Authorization header on the connection is not
possible. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M512E

Internal server error occurred during data receive, rc=rc

Reason:
An internal error has occurred when processing the content of the body portion of an
HTTP message from a client connection. The message lists the return code. The request
is not processed.

Action:
Retry the request.
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 405

CAL2 Messages

CAL2M513E

No method was found in request line

Reason:
No method was found on the request line that is being processed on a client
connection. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M514E

Method is not get or post(token): token

Reason:
The method that is specified on the request line from a client connection being
processed did not contain GET or POST. The message lists the tokens that are used on
the request. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M515E

No URI was found in request line

Reason:
No Uniform Resource Identifier (URI) was specified on the request line from a client
connection. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

406 Message Reference Guide

 CAL2 Messages

CAL2M516E

HTTP version not found in request line, no third token

Reason:
No HTTP version was found on the request line. The third token was not specified on a
client connection. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M517E

HTTP version not found in request line, third token too short

Reason:
No HTTP version was found on the request line. The third token was too short on a
client connection. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M518E

HTTP version not found in request line, third token not HTTP

Reason:
No HTTP version was found on the request line. The third token was not HTTP on a
client connection. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 407

CAL2 Messages

CAL2M519E

No HTTP headers

Reason:
No HTTP headers were found in the content that was supplied on a client connection.
The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M520E

Content length value is missing

Reason:
A client connection did not supply the content length header. The request is not
processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M521E

Bad content length value value

Reason:
A client connection supplied an invalid content length. The value is listed in the
message. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

408 Message Reference Guide

 CAL2 Messages

CAL2M522E

Unable to get HTTP body data

Reason:
Jobflow Monitor is unable to obtain and process the HTTP body data from the TCP/IP
socket during a client connection. The request is not processed.

Action:
Retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M523E

Content length value length not equal to body length of length

Reason:
A client connection supplied a data content length that is not the same as the remaining
body length. The message supplies both values. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M524E

Content length is required

Reason:
The required data content length is missing on a client connection. The request is not
processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 409

CAL2 Messages

CAL2M530E

Unable to queue work to JFM, rc=rc

Reason:
An attempt was made to queue a work request to Jobflow Monitor, and the attempt
was unsuccessful. The message lists the return code. The request is not processed.

Action:
Perform the following actions:
■ Look for messages in Jobflow Monitor.
■ Take appropriate action where necessary.
■ Retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M531E

Unable to create internal XML document

Reason:
An attempt was made to create an XML object that is based on the request, and the
attempt was unsuccessful. The request is not processed.

Action:
Perform the following actions:
■ Look for messages in Jobflow Monitor.
■ Take appropriate action where necessary.
■ Retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M532E

No request line is present

Reason:
An internal error has occurred. The request line is missing on the program call. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

410 Message Reference Guide

 CAL2 Messages

CAL2M533E

Request line is too short

Reason:
An internal error has occurred. The request line is too short on the program call. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M534E

Request URI is too long

Reason:
The length of the Uniform Resource Identifier (URI) that is specified on the request line
is greater than 255 characters. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M535E

Parm beginning with: parm, at offset length is too long, 256 max

Reason:
A parameter that is specified on the request line is longer than 256 characters. The
message lists the first portion of the parameter and the length. The request is not
processed.

Action:
Correct and retry the request.

Chapter 2: AFM - CA7R Messages 411

CAL2 Messages

CAL2M536E

Parm beginning with: parm, at offset length has no value

Reason:
The value from a parameter that is specified on the request line is missing. The message
lists the first portion of the parameter and the length. The request is not processed.

Action:
Correct and retry the request.

CAL2M537E

Filter parm beginning with: parm, at offset length is too long, 256 max

Reason:
The length of the value from a filter parameter that is specified on the request line is
greater than 256 characters. The message lists the first portion of the parameter and
the length. The request is not processed.

Action:
Correct and retry the request.

CAL2M538E

Filter parm beginning with: parm, at offset length has no value

Reason:
The value from a filter parameter that is specified on the request line is missing. The
message lists the first portion of the parameter and the length. The request is not
processed.

Action:
Correct and retry the request.

412 Message Reference Guide

 CAL2 Messages

CAL2M539E

Unable to get content data

Reason:
Jobflow Monitor was unable to obtain the content data from the request when creating
the internal XML object. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M540E

Unable to get content data length

Reason:
Jobflow Monitor was unable to obtain the content data length from the request when
creating the internal XML object. The request is not processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

CAL2M541E

Unable to parse XML document rc=rc

Reason:
Jobflow Monitor was unable to parse the XML document received on a request. The
return code is listed in the message. The request is not processed.

Action:
Perform the following actions:
■ Verify the contents on the request.
■ Correct and retry the request.

Chapter 2: AFM - CA7R Messages 413

CAL2 Messages

CAL2M542E

Unable to find the request line

Reason:
Jobflow Monitor was unable to locate the request line in the document received on a
request. The request is not processed.

Action:
Perform the following actions:
■ Verify the contents on the request.
■ Correct and retry the request.

CAL2M543E

Unable to obtain a query request block

Reason:
An internal error has occurred. Jobflow Monitor was unable to obtain a query request
block used to process the query. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M544E

Unable to parse client query, rc=rc

Reason:
Jobflow Monitor was unable to parse the input client request. The request is not
processed.

Action:
Correct and retry the request.
For assistance, contact CA Support at ca.com/support.

414 Message Reference Guide

 CAL2 Messages

CAL2M545E

Query is invalid:reason

Reason:
The input client request is invalid. The message lists the reason. The request is not
processed.

Action:
Correct and retry the request.

CAL2M546E

UserID is required

Reason:
The user ID is required when performing this request. The request is not processed.

Action:
Correct and retry the request.

CAL2M547E

Security error: error RC=rc reason=code, text

Reason:
A security error has occurred while processing a request. The message lists the error,
return code, reason code, and text. The request is not processed.

Action:
Perform the following tasks:
■ Take appropriate action that is based on the message.
■ If applicable, verify the Jobflow Monitor FACILITY setting.
■ Correct and retry the request.

Chapter 2: AFM - CA7R Messages 415

CAL2 Messages

CAL2M548E

Unable to find CA7 Instance ID

Reason:
The required ca7Instance element on the input request is missing. The request is not
processed.

Action:
Correct and retry the request.

CAL2M550E

CA7 Instance(instance) has a status of "status"

Reason:
Jobflow Monitor was unable to queue the request to the CA7 instance for processing
due to its status.
Only active CA7 instances can process requests. The request is not processed.
The CA7 instance status is one of the following items:
■ Undefined
■ Inactive
■ Starting
■ Active
■ Terminating

Action:
Perform the following actions:
■ Use the STATUS command to verify the status of the CA7 instance in Jobflow
Monitor.
■ Correct the problem and retry the request.

416 Message Reference Guide

 CAL2 Messages

CAL2M555E

Error occurred while processing escape sequence characters, rc=rc

Reason:
An error occurred while processing escape sequence characters in the request. The
message lists the return code from createEscapeSequences. The request is not
processed.
The following table lists special characters that are translated in a request to escape
sequence characters before processing the request:

Special Character Escape Sequence Description

& & Ampersand sign
' ' Single quote
" " Double quote
> > Greater than
< &lt; Less than

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M556E

L2JFCLI buffer is too short, buffer length=length

Reason:
An internal error has occurred. The length of the buffer that is supplied on the call to
function processCa7Buffer is too small. The message lists the length of the buffer. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 417

CAL2 Messages

CAL2M557E

Record at offset offset in buffer is too short, buffer length=length

Reason:
An internal error has occurred. The record at the offset listed in the message does not fit
in the buffer, whose length is also listed in the message. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M558E

L2JFCLI buffer is too short, at offset=offset, remaining length=length

Reason:
An internal error has occurred. The buffer is too small at the offset listed in the message
to hold the rest of the data. The message lists the remaining length of the data. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M559E

CA 7 credentials were not accepted; reason

Reason:
CA 7 did not accept the credentials of the user while processing the request. A login
error occurred. The message lists the reason. The request is not processed.

Action:
Perform the following tasks:
■ Take appropriate action that is based upon the reason.
■ If applicable, review the Jobflow Monitor FACILITY setting.
■ Correct and retry the request.

418 Message Reference Guide

 CAL2 Messages

CAL2M560E

Total output lines count exceeds maxRecs of count - output truncated

Reason:
The total number of output lines that the request generated exceeded the maxRecs
count that is specified on the input request. The message lists both counts. As a result,
the output from the request is truncated to the number of lines that is specified on
maxRecs. Processing continues.

Action:
Perform the following actions:
■ If applicable, increase the maxRecs count on the input request to accommodate
more lines of output from the request.
■ Correct and retry the request if applicable.

CAL2M561E

Timeout expired after number seconds waiting for data from CA7instance

Reason:
A timeout has occurred while processing a request to CA 7. The message lists the
number of seconds supplied (or defaulted) on the timeout element in the request.
Additionally, the message lists the CA7instance from the request. The output from the
request is truncated to the number of lines that is specified on maxRecs. The request is
not processed any further.

Action:
Perform the following actions:
■ Increase the number of seconds on the timeout parameter in the request or refine
the request.
■ If applicable, check Jobflow Monitor and CA 7 to determine a cause of the slow
response.
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 419

CAL2 Messages

CAL2M562E

Error receiving data responses from CA7, bytes=bytes

Reason:
An internal error occurred while processing the data that CA 7 returned from a request.
The message lists the number of bytes received on the request. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M563E

Bad transaction header on data request, eyecatcher=text

Reason:
An internal error occurred while processing the transaction header received in the data
packet on a request to CA 7. The transaction header is invalid. The message lists the
eyecatcher from the header. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M564E

Unsupported request encountered, function code=code

Reason:
An internal error occurred. An unsupported request was encountered. The message lists
the function code. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

420 Message Reference Guide

 CAL2 Messages

CAL2M566E

Error receiving block responses from CA7, bytes=bytes

Reason:
An internal error occurred. An error occurred while processing block data that CA 7
returned from a request. The message lists the number of bytes received on the
request. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M567E

Response length mismatch in data buffer, l1=length, l2=length, l2x=BDW

Reason:
An internal error occurred while processing the response that CA 7 returned from a
request. The length on the response is different from the length of the data buffer. The
message lists these values and the BDW. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M568E

Send failed attempting type request, bytes=bytes

Reason:
An internal error occurred while sending a request to CA 7 for processing. The message
lists the request type and the number of bytes. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 421

CAL2 Messages

CAL2M569E

Send failed attempting type request, tried number bytes, sent number bytes

Reason:
An internal error occurred while attempting to send a request to CA 7 for processing.
The message lists the request type, number of times attempted, and number of bytes
sent. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M570E

Receive failed attempting close response, errno=number, error:text

Reason:
An internal error occurred while attempting to receive the results from a close request
to CA 7. The message lists the error number and text. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M571E

Bad transaction header on close response, eyecatcher=text

Reason:
An internal error occurred while processing the close transaction header that was
received in the data packet on a request to CA 7. The transaction header is invalid. The
message lists the eyecatcher from the header. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

422 Message Reference Guide

 CAL2 Messages

CAL2M572E

Bad function code on close response, function code=code

Reason:
An internal error occurred. An unknown function code was returned as a result of a
close request to CA 7. The message lists the function code. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M573E

Bad return code from CA7 rc feedback

Reason:
An internal error occurred as a result of closing a web service request to CA Workload
Automation SE. The message lists the return code (rc) and the feedback code (if
available). The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M574E

Command is too long: Prefix=, ‘text‘, length=length

Reason:
An internal error occurred. An attempt was made to send a command to CA 7 whose
length exceeds 160 characters. The message lists the first portion of the command and
the length of the command. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 423

CAL2 Messages

CAL2M575E

Receive failed attempting data response, errno=number, error:text

Reason:
An internal error occurred. An error occurred while attempting to receive data results
from CA 7 as a result of a command. The message lists the error number and text. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M576E

Bad transaction header on data response, eyecatcher=text

Reason:
An internal error occurred while processing the transaction header received in the data
packet on a request to CA 7. The transaction header is invalid. The message lists the
eyecatcher from the header. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M577E

Bad function code on data response, function code=code

Reason:
An internal error occurred. An unknown function code was returned as a result of a
request to CA 7. The message lists the function code. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

424 Message Reference Guide

 CAL2 Messages

CAL2M578E

Receive failed attempting INIT response, errno=number, error:text

Reason:
An internal error occurred. The message lists the error code and message resulting from
an INIT request to CA 7. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M579E

Bad transaction header on INIT response, eyecatcher=text

Reason:
An internal error occurred. A bad transaction header was returned as a result of an INIT
request to CA 7. The message lists the eyecatcher from the header. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M580E

Bad function code on INIT response, function code=code

Reason:
An internal error occurred. An unknown function code was returned as a result of an
INIT request to CA 7. The message lists the function code. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 425

CAL2 Messages

CAL2M581E

CA7 server terminal is temporarily unavailable, function code=code: feedback

Reason:
An error occurred while processing your request to CA 7. The CA 7 server terminal is
temporarily unavailable and is unable to process your request. The message lists the
function code and feedback. The request is not processed.

Action:
Correct the problem in CA 7 and retry the request.

CAL2M582E

CA7 server returned the following error on INIT, function code=code: feedback

Reason:
An internal error occurred. An error occurred while processing an INIT request to CA 7.
An unknown function code was returned as a result of the request. The message lists
the function code and feedback. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M583E

The TCP/IP interface in CA7instance is not active

Reason:
The TCP/IP interface in the CA 7 instance that is listed in the message is not active. The
XML or web service request is not processed.

Action:
Perform the following actions:
■ Verify the TCP/IP settings in the CA Workload Automation SE.
■ If the settings in Jobflow Monitor are different, restart Jobflow Monitor or stop and
restart the Jobflow Monitor instance
■ Alternately, take corrective actions as necessary.
■ Retry the request.

426 Message Reference Guide

 CAL2 Messages

CAL2M584E

Unable to get connector

Reason:
An internal error occurred while processing an INIT request to CA 7. Jobflow Monitor
was unable to instantiate a new virtual connector object. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M585E

Unable to connect, rc=rc

Reason:
An error occurred when Jobflow Monitor attempted to connect to CA 7 as a result of
initiating an INIT command. The message lists the return code. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M586E

Invalid virtual connection object, rc=rc

Reason:
An internal error occurred in L2JFCLI when Jobflow Monitor attempted to create a
virtual connection object. The message lists the return code. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 427

CAL2 Messages

CAL2M590E

Invalid virtual connection object, rc=rc

Reason:
An internal error occurred in L2JFSEC when Jobflow Monitor attempted to create a
virtual connection object. The message lists the return code. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M591E

error

Reason:
An internal error occurred when Jobflow Monitor attempted to create a security
environment in a call to function pthread_security_np. The message lists the error. The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M599E

The keyword parameter is no longer supported in this query

Reason:
The keyword parameter that is specified in the message is no longer supported in this
XML query. The request is not processed.

Action:
Remove the parameter from the request and retry the request.

428 Message Reference Guide

 CAL2 Messages

CAL2M600E

No request found

Reason:
An internal error occurred when Jobflow Monitor attempted to locate the JF_Request
element tag from the XML document. The element was not located. The request is not
processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M601E

Request is too long

Reason:
An internal error occurred. The length of the XML request exceeds 256 characters. The
request is not processed.

Action:
Correct and retry the request.

CAL2M602E

Unknown query request:request

Reason:
An internal error occurred. The name of the XML request is invalid. The request is not
processed.

Action:
Correct and retry the request.

CAL2M603E

request is restricted and requires a license management key (LMP code)

Reason:
The XML request is restricted and requires a license management key (LMP code). The
request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 429

CAL2 Messages

CAL2M604E

The maxRecs value is not numeric

Reason:
The maxRecs value that is supplied on the XML request is not numeric. The request is
not processed.

Action:
Correct and retry the request.

CAL2M605E

The maxRecs parameter can not exceed 999,999,999

Reason:
The maxRecs value that is supplied on the XML request cannot exceed 999,999,999. The
request is not processed.

Action:
Correct and retry the request.

CAL2M606E

The element value length (length) is too long, maximum length allowed is maximum

Reason:
The element name listed in the message was supplied on an XML request, and the value
for the element is too long. The length of the element and the maximum length
permitted are also listed in the message. The request is not processed.

Action:
Correct and retry the request.

CAL2M607E

The refresh value is not numeric

Reason:
The refresh value that is supplied on the XML request is not numeric. The request is not
processed.

Action:
Correct and retry the request.

430 Message Reference Guide

 CAL2 Messages

CAL2M608E

Request request is not valid

Reason:
The XML request that is listed in the message is invalid. The request is not processed.

Action:
Correct and retry the request.

CAL2M609E

<persistMin> attr value (value) is not numeric

Reason:
The persistMin element value that is entered on the XML request is not numeric. The
message lists the value. The request is not processed.

Action:
Correct and retry the request.

CAL2M610E

<persistMin> attr value (value) must be between 1 and 1440, inclusive

Reason:
The persistMin element value that is entered on the XML request must be from 1
through 1440, inclusive. The message lists the value. The request is not processed.

Action:
Correct and retry the request.

CAL2M611E

<hours> attr value (value) is not numeric

Reason:
The hours element value that is entered on the XML request is not numeric. The
message lists the value. The request is not processed.

Action:
Correct and retry the request.

Chapter 2: AFM - CA7R Messages 431

CAL2 Messages

CAL2M612E

A job name or number is required

Reason:
A job name or job number is required on this XML request. The request is not
processed.

Action:
Correct and retry the request.

CAL2M613E

The job string is too long

Reason:
The job name that is entered on the XML request exceeds eight characters in length.
The request is not processed.

Action:
Correct and retry the request.

CAL2M614E

A Job element is required

Reason:
The Job element is required for this XML request. The request is not processed.

Action:
Correct and retry the request.

CAL2M615E

The timeout value must be numeric

Reason:
The timeout element value that is entered on the XML request is not numeric. The
message lists the value. The request is not processed.

Action:
Correct and retry the request.

432 Message Reference Guide

 CAL2 Messages

CAL2M616E

The timeout value must be between 1 and 3600, inclusive

Reason:
The timeout element value that is entered on the XML request must be from 1 through
3600, inclusive. The request is not processed.

Action:
Correct and retry the request.

CAL2M617E

Allocation of Command list failed

Reason:
An internal error occurred when Jobflow Monitor attempted allocate a command list to
process the request. The request is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M618E

The Job element is required, must be numeric, and cannot exceed 5 digits

Reason:
The Job element is required on the CA7CmdCancel XML request. The Job element must
be numeric and cannot exceed five digits. The request is not processed.

Action:
Correct and retry the request.

CAL2M619E

The JobNumber element must be numeric, and cannot exceed 5 digits

Reason:
The JobNumber element value that is entered on the CA7CmdRestart XML request is not
numeric or it exceeds five digits. The request is not processed.

Action:
Correct and retry the request.

Chapter 2: AFM - CA7R Messages 433

CAL2 Messages

CAL2M620E

Both JobName and JobNumber elements are required for autoselect

Reason:
When you specify autoselect, both JobName and JobNumber elements are required on
the CA7CmdRestart XML request. The request is not processed.

Action:
Correct and retry the request.

CAL2M621E

Invalid value in named element

Reason:
The named element that is entered on the XML request contains an invalid value. The
request is not processed.

Action:
Correct and retry the request.

CAL2M622E

The named element contains a non-printable character

Reason:
The named element that is entered on the XML request and listed in the message
contains a nonprintable character. The request is not processed.

Action:
Correct and retry the request.

CAL2M623E

A Command element is required

Reason:
The required Command element is missing from the XML request. The request is not
processed.

Action:
Correct and retry the request.

434 Message Reference Guide

 CAL2 Messages

CAL2M630E

Invalid return code from function - rc=rc,

Reason:
An internal error occurred. An invalid return code was received when processing a
Jobflow Monitor function. The message lists the function and return code. The request
is not processed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M631I

No data available

Reason:
No data was returned as a result of processing the XML request.

Action:
None.

CAL2M632W

Target job not found

Reason:
No jobs were found as a result of processing the XML request.

Action:
None.

CAL2M633E

The <jsName> provided (value) does not exist

Reason:
The jsName element that is provided on the XML request does not exist. The value is
listed in the message. The request is not processed.

Action:
Correct and retry the request. If a timeout occurred as a result of executing DELTA
requests, examine the persistMin value in the initial request. Adjust the value where
necessary.

Chapter 2: AFM - CA7R Messages 435

CAL2 Messages

CAL2M636E

Request to extract CA 7 data denied; another request is in progress

Reason:
A request to extract CA Workload Automation SE data has been made, and another
extract request is being processed. Only one extract process can run at a time. The
request is denied.

Action:
Request the CA Workload Automation SE data extract later.

CAL2M750I

Did not find event yydddhhmmssth between yydddhhmmssth and yydddhhmmssth

Reason:
CA-7 Server for iDash did not find an event for the indicated date and time in the
indicated range. Events are sometimes lost.

Action:
One or more events might have been lost. Reseeding can be required to resynchronize.
Contact CA Support at ca.com/support for iDash guidance.

CAL2M760I

Last retrieved event yydddhhmmssth not found between yydddhhmmssth and

yydddhhmmssth
Reason:
CA-7 Server for iDash did not find an event for the indicated date and time in the
indicated range. Events are sometimes lost.

Action:
One or more events might have been lost. Reseeding can be required to resynchronize.
Contact CA Support at ca.com/support for iDash guidance.

436 Message Reference Guide

 CAL2 Messages

CAL2M770I

Initial search did not locate event yydddhhmmssth between yydddhhmmssth and
yydddhhmmssth

Reason:
CA-7 Server for iDash did not find an event for the indicated date and time in the
indicated range. Events are sometimes lost.

Action:
One or more events might have been lost. Reseeding can be required to resynchronize.
Contact CA Support at ca.com/support for iDash guidance.

CAL2M801I

METRICS DATA WILL BE CAPTURED

Reason:
This informational message indicates that METRICS=YES was coded or defaulted on the
INIT initialization statement. The performance-related metrics data collection is starting
and is written to the log files.

Action:
None.

CAL2M802W

LOAD FAILED FOR xxxxxxxx, SKIPPING METRICS DATA COLLECTION

Reason:
A LOAD failed for the indicated module. This module is required for Metrics processing.
Metrics data collection is skipped for this iteration and processing continues. An error
count is incremented. If the maximum error count is exceeded, message CAL2M804E is
issued. Metrics data collection is turned off for this execution of CA Workload
Automation SE.

Action:
Verify that the indicated module is in a library accessible from CA Workload Automation
SE.

Chapter 2: AFM - CA7R Messages 437

CAL2 Messages

CAL2M803W

CALL TO xxxxxxxx FAILED, RC=xx, REAS=xx, SKIPPING METRICS DATA COLLECTION

Reason:
The indicated metrics collection module has ended with a nonzero return code. Metrics
data collection is skipped for this iteration. Processing continues. An error count is
incremented. If the maximum error count is exceeded, message CAL2M804E is issued.
Metrics data collection is turned off for this execution of CA Workload Automation SE.

Action:
Contact your installation specialist for assistance.

CAL2M804E

MAX ERROR COUNT EXCEEDED, METRICS DATA COLLECTION IS TURNED OFF

Reason:
The metrics error count maximum has been exceeded and metrics data collection and
logging has been turned off for this execution of CA Workload Automation SE.

Action:
Look for previous error messages in the job output and act as indicated for those
messages.

CAL2M900E

rtn unable to get storage for connection, len=value

Reason:
The operating system returned 0 from malloc instead of a storage pointer.

Action:
For assistance, contact CA Support at ca.com/support.

438 Message Reference Guide

 CAL2 Messages

CAL2M901E

rtn unable to initialize mutex, rc=nnn, error=error text

Reason:
The operating system returned a nonzero return code (rc) from pthread_mutex_init
instead of a rc of zero.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M905E

rtn unable to get linklist for name

Reason:
The internal link list routine failed to return a link list object for the name that is listed in
the message.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M906E

rtn unable to add port to portlist at value

Reason:
The internal portlist routine could not add an entry to the identified portlist.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M907E

rtn unable to start port name(value), rc=nn

Reason:
The specified IP port could not be started.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 439

CAL2 Messages

CAL2M910E

rtn bad port object passed value

Reason:
An internal error has occurred. A control block has an invalid footprint.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M911E

rtn unable to create named thread for port name(value)

Reason:
The z/OS language environment returned a null from the pthreadCreate function. The
message lists the routine (rtn), named thread, port name, and value.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M912E

rtn unable to get listener socket object

Reason:
A request for a listener socket failed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M913E

rtn unable to bind socket value for port name(value)

Reason:
The IP Bind function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

440 Message Reference Guide

 CAL2 Messages

CAL2M914E

rtn unable to listen on socket value for port name(value)

Reason:
The IP Listen function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M915E

rtn unable to accept socket value for port name(value)

Reason:
The IP accept function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M916E

rtn unable to create connection thread

Reason:
The z/OS language environment returned a null from the pthreadCreate function.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M917E

rtn unable to get expanded input buffer of value length

Reason:
A request for buffer storage failed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 441

CAL2 Messages

CAL2M918E

rtn unable to get input buffer of value length

Reason:
A request for buffer storage failed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M919E

rtn socket read error: rc=nn, text

Reason:
The IP Read function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M920E

rtn ioctl error: rc=nn, text

Reason:
The IP IOCTL function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M921E

rtn residual socket read error: rc=nn, text

Reason:
The IP Read function returned an error.

Action:
For assistance, contact CA Support at ca.com/support.

442 Message Reference Guide

 CAL2 Messages

CAL2M922E

rtn unable to get value http header array

Reason:
No storage was available for an HTTP header array.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M923E

rtn name(value) err=reason

Reason:
A preceding message listed an error for this port name and value. The message lists the
routine (rtn) and reason for the error. Most of the errors indicate that the requested
port number is not available.

Action:
Perform the following actions:
■ Change the port number.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2M930E

newipSocketObject unable to get storage for socket, len=value

Reason:
No storage was available to create a socket.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M931E

ipgetSocket unable to create OS socket for socket object value

Reason:
The IP Socket function failed.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 443

CAL2 Messages

CAL2M932E

ipSocketClose unable to close OS socket for socket object value, rc=nn error

Reason:
The IP Close function failed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M935E

sendData unable to send data for socket value, rc=nn error

Reason:
The IP write function failed.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2M936I

PORT(portname) assigned to NUMBER(nnnnn) ENCR(type)

Reason:
Processing of a PORT statement in JBFLWIP completed. If the port number 0 was
specified, the system-assigned port number is listed. The message lists the type of
encryption that is used on the PORT.

Action:
None.

CAL2M937E

Unable to retrieve port number for portname

Reason:
PORT statement using NUMBER(0) was unable to get a system-assigned number. Port
numbers may be in use or restricted for this host system.

Action:
Specify a port number above 5000.

444 Message Reference Guide

 CAL2 Messages

CAL2M938W

NAME invalid, PORT statement bypassed

Reason:
A PORT statement NAME was missing. A PORT was not set up.

Action:
Correct or remove the PORT statement from member JBFLWIP.

CAL2M939W

NUMBER invalid, PORT statement bypassed

Reason:
A PORT statement NUMBER was missing or invalid.. A PORT was not set up.

Action:
Correct or remove the PORT statement from member JBFLWIP.

CAL2M940W

CPMPORT name repeated, PORT statement bypassed

Reason:
A PORT statement with NAME(CPMPORT) has already been processed. Only one
CPMPORT is supported.

Action:
Remove the port statement from member JBFLWIP.

Chapter 2: AFM - CA7R Messages 445

CAL2 Messages

CAL2M941W

JFM unable to converse with CPM RC(n)

Reason:
The JFM monitor was started with TYPE(WARM) specified in the JBFLWMN member. A
CAICCI session was attempted with the server name specified in CPMCCI(servername) or
defaulting to CPMSERVER. The CAICCI session failed. The queries to update the status of
active flows were not completed.

Action:
Verify that the CPM Server is running.
Perform the following actions:
■ If CPM is not active, start CPM. Next stop and start the JFM monitor instance that
was performing a warm start when error was reported.
■ If CPM is active, review CPMPARMS to find set CCIApplication=...
If CCI Application is not specified, verify that the JBFLWMN monitor statement
either has no CPMCCI specified or specifies a default value: CPMCCI(CPMSERVER)
If CCIApplication is set in CPMPARMS, the CPMCCI must match the value for the
CCIApplication name.

CAL2M950E

L2JFSTxx(method name) was unable to track workload event for jjjjjjjj(nnnn)

Reason:
The CA7 instance monitor was unable to match an event for job name jjjjjjjj and CA7 job
number nnnn with any known active workload.

Action:
Save the output of this task and contact CA Support. Recycle the program to resume
workload monitoring and correct the error.

446 Message Reference Guide

 CAL2 Messages

CAL2M951E

L2JFSTRC(method name) was unable to add workload tracking for jjjjjjjj(nnnn)

Reason:
The CA7 instance monitor was unable to add job name jjjjjjjj with CA7 job number nnnn
to the monitored active workload.

Action:
Save the output of this task and contact CA Support. Recycle the program to resume
workload monitoring and correct the error.

CAL2M952W

L2JFSTRC(method name) encountered an unexpected error for jjjjjjjj(nnnn)

Reason:
The CA7 instance monitor was unable to find job name jjjjjjjj with CA7 job number nnnn
in the monitored active workload.

Action:
Save the output of this task and contact CA Support. This error is a non-critical error and
does not have any effect on this task or its services.

CAL2M991I

CA 7 ready for JFM start

Reason:
CA 7 has created a name/token pair that is used for communication between CA 7 and
JFM.

Action:
None.

Chapter 2: AFM - CA7R Messages 447

CAL2 Messages

CAL2P001E

INVALID PARMLIST RECEIVED: xxxxxxxx

Reason:
The CA Workload Automation SE CPM Flow Build program received an invalid parmlist.
The text xxxxxxxx describes the error.

Action:
Contact your installation specialist for assistance.

CAL2P002E

UNABLE TO GETMAIN STORAGE FOR xxxxxxxx RC=cccc

Reason:
The CA Workload Automation SE CPM Flow Build program could not obtain needed
storage for xxxxxxxx. The return code is cccc.

Action:
Increase the region size.

CAL2P003E

UNABLE TO LOAD MODULE xxxxxxxx. RC=cccc

Reason:
The CA Workload Automation SE CPM Flow Build program could not load program
module xxxxxxxx. The return code is cccc.

Action:
Verify that the steplib for the CPM task includes the CA Workload Automation SE
CAL2LOAD. For assistance, contact CA Support at ca.com/support.

448 Message Reference Guide

 CAL2 Messages

CAL2P004E

INVALID xxxxxxxx IN CA7PARMS STARTING WITH yyy...yyy

Reason:
The CA Workload Automation SE CPM Flow Build program encountered an error in the
CA7PARMS options. The type of error is described by xxxxxxxx, and the first 16 bytes of
the data in error is displayed in yyy...yyy.

Action:
Correct the statement in error.

CAL2P005E

ERROR FROM CA-7: xxx...xxx

Reason:
The CA Workload Automation SE CPM Flow Build program encountered an error
message in the output received from CA Workload Automation SE. The error message is
displayed in xxx...xxx.

Action:
If the nature of the error is obvious (security error, and so on), correct the source of the
problem. If not, consult your installation specialist for assistance.

CAL2P006E

ERROR FROM CA-7 CCI CALL : RC=rrrr CC=cccc

Reason:
The CA Workload Automation SE CPM Flow Build program encountered a bad return
code from the CA Workload Automation SE CAICCI interface when attempting to send a
command to CA Workload Automation SE.

Action:
If the nature of the error is obvious (CA Workload Automation SE is down) then correct
the source of the problem. If not, consult your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 449

CAL2 Messages

CAL2P007E

UNABLE TO RETRIEVE CPMPORT NUMBER FROM JFM FOR TOKEN NAME

JFMCA7xCPMPORT

Reason:
The name-token pair for the CA Workload Automation SE instance starting a flow was
not found. Jobflow Monitor (JFM) creates the pair for each instance that it is
monitoring. The x in JFMCA7xCMPORT is a numeric value (1-8) that represents the
instance.

Action:
Perform the following actions:
■ Verify that JFM is running with a MONITOR statement for the CA7x instance.
■ Browse the JFM output for the CAL2M031E, CAL2M062E, or CAL2M120E messages.

CAL2P008E

UNABLE TO CONSTRUCT A FLOW TABLE. RC=cccc yyyyyy

Reason:
Jobflow Monitor (JFM) was unable to provide information to complete the critical path.
yyyyyy can be blank or contain one of the following values:
■ startjob invalid
■ endjob invalid
■ XML format error
■ no jobs found

Action:
Review JFM output for related Messages CAL2M300W or CAL2M301W.

CAL2P009E

Non-zero return from TCP/IP interface. RC=rrrrrrrr CC=cccccccc WIP=xxxx.

Reason:
Communication to Jobflow Monitor failed. The current operation, identified by WIP,
returned failure codes.

Action:
For assistance, contact CA Support at ca.com/support.

450 Message Reference Guide

 CAL2 Messages

CAL2P010I

CONNECTING TO JFM PORT NUMBER nnnnn for flowname

Reason:
Communication to Jobflow Monitor starting for flow processing.

Action:
None.

CAL2P011E

UNABLE TO FIND ACTIVE PORT NUMBER FROM JFM FOR TOKEN NAME
JFMxxxxxyyyyActv

Reason:
The name-token pair for the CA Workload Automation SE instance starting a flow
(where xxxxx represents the port number and yyyy represents the TCP ASID) is not
active. Jobflow Monitor (JFM) creates the pair for each instance of CA Workload
Automation SE it is monitoring.

Action:
Perform the following actions:
■ Verify that JFM is running with a MONITOR statement for the CA7x instance.
■ Browse output of JFM for Messages CAL2M031E, CAL2M913E, and CAL2M923E.

Chapter 2: AFM - CA7R Messages 451

CAL2 Messages

CAL2P050I

REQUEST xxx: FUNC=ffff ARG=aaa...aaa RC=rrrr CC=cccc SUCC=ssss

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. Field xxx indicates IN or OUT to indicate whether the line traces the
receipt of a request or the results of a request. Field ffff indicates the function code for
the request. Based on the type of request involved, the message displays one or more of
the following fields:
aaa...aaa
Displays the job name and schedule ID for a READ request.
rrrr cccc
Shows the return code and condition code for the completion of a request.
ssss
Shows the number of successors returned for the argument job upon the successful
completion of a READ request.

Action:
None.

CAL2P051I

RETURN FROM CA-7 CCI CALL : RC=rrrr CC=cccc CMD=cccccccc

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled.
rrrr cccc
Shows the return code and condition code from the CA Workload Automation SE
CAICCI interface.
cccccccc
Shows the CA Workload Automation SE command sent through the CA Workload
Automation SE CAICCI interface.

Action:
None.

452 Message Reference Guide

 CAL2 Messages

CAL2P053I

** BREVFLOW HIT A NOT FOUND CONDITION

Reason:
A FLOWL command did not find the job.

Action:
Check the command for correct job name. Reissue the command.

CAL2P060I

**** CAL2CPCB AT INITIALIZATION ****

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. This message is the storage dump header for the primary control block
for the flow build process at the end of initialization processing.

Action:
None.

CAL2P061I

**** CMD INPUT TO CA-7 CCI ****

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. This message is the storage dump header for the command block being
passed to the CA Workload Automation SE CAICCI interface.

Action:
None.

Chapter 2: AFM - CA7R Messages 453

CAL2 Messages

CAL2P062I

**** CMD OUTPUT FROM CA-7 CCI: RC=rrrr CC=cccc ****

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. This message is the storage dump header for the command output
blocks that contain the CA Workload Automation SE output returned using the CA
Workload Automation SE CAICCI interface.

Action:
None.

CAL2P063I

**** READ CALL PARAMETER LIST

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. This message is the storage dump header for the parameter
information passed on the READ request. It is followed by the read results storage (see
CAL2P064I).

Action:
None.

CAL2P064I

**** READ RESULTS: RC=rrrr CC=cccc : ARGUMENT=aaa...aaa

Reason:
The CA Workload Automation SE CPM Flow Build program is running with the trace
option enabled. This message is the storage dump header for the buffer returned for a
READ request.
aaa...aaa
Displays the target job name and schedule ID.
rrrr cccc
Shows the return code and condition code for the completion of the READ request.

Action:
None.

454 Message Reference Guide

 CAL2 Messages

CAL2P099W

CPM Flow xxxxxxxx - yyyy.ddd hh:mm:ss.th deleted. Connected job count = 0.

Reason:
The CA Workload Automation SE CPM Flow, where xxxxxxxx is the flow name, was
automatically deleted as a result of the connected job count reaching zero. This can
occur if you cancel (in CA Workload Automation SE) a job that is not the last job in the
CPM flow or if the ending job in the CPM flow does not exist or is not triggered. The
starting date (Julian) and time for the flow are indicated on the message.

Action:
Check the CPM flow definition. If the ending job in the CPM flow does not exist or is not
executed, correct the flow definition.

CAL2P500I

Online calendar functions are available

Reason:
The online calendar PDS is defined and exists. Online access to the base calendars using
the DB.2.8 Calendar Maintenance panel or through other interfaces is enabled.

Action:
None.

CAL2P501W

Online calendar functions are not available

Reason:
The online calendar PDS does not exist. This PDS is the data set pointed to by
initialization file statement CALENDAR,DSN=. The online access to the base calendars
using the DB.2.8 Calendar Maintenance panel or through other interfaces is not
available. CA Workload Automation SE startup continues.

Action:
Perform the following actions:
■ Update the CALENDAR,DSN= initialization file statement with a valid data set.
■ Restart CA Workload Automation SE.

Chapter 2: AFM - CA7R Messages 455

CAL2 Messages

CAL2P502I

Perpetual calendar feature is available

Reason:
The perpetual calendar PDS is available. The members of the perpetual calendar PDS
contain criteria for automatically building base calendars.

Action:
None.

CAL2P503W

Perpetual calendar feature is not available

Reason:
Either one or both of the online calendar PDS and the perpetual calendar PDS do not
exist. These data sets are pointed to by initialization file statement
CALENDAR,DSN=x,PCALDSN=y. There will be no automatic building of base calendars
from perpetual calendar criteria. CA Workload Automation SE startup continues.

Action:
Perform the following actions:
■ Update the CALENDAR,DSN=x,PCALDSN=y initialization file statement with valid
data sets.
■ Restart CA Workload Automation SE.

CAL2P880E

CAL2CPMT RECEIVED INVALID PARM LIST

Reason:
The utility program CAL2CPMT was submitted with an invalid parameter list.

Action:
Correct the execution parameter list.

456 Message Reference Guide

 CAL2 Messages

CAL2P881E

INVALID PARAMETER STARTING WITH (xxxx=xxx) - ABORTING

Reason:
The utility program CAL2CPMT was submitted with an unsupported parameter type.

Action:
Correct the execution parameter.

CAL2P882E

PRINT DD IS INVALID OR UNAVAILABLE

Reason:
The utility program CAL2CPMT requires a PRINT DD file.

Action:
Add or correct the PRINT DD.

CAL2P884E

cpmservername CCI Receiver not found

Reason:
CA Critical Path Monitor (CA CPM) with CCIAPPLNAME=cpmservername is not active on
the local host. The default is CpmServer.

Action:
CAL2CPMT parameter CPM= defaults to CpmServer but may be specified on the execute
statement to match the CCIAPPLNAME set in the CA CPM options.

CAL2P885E

NO FLOWS FOUND THAT MATCH INPUT FLOW

Reason:
The utility program CAL2CPMT requested information from CA CPM, but the flow was
not found.

Action:
Verify that the flowname matches a flow that executed.

Chapter 2: AFM - CA7R Messages 457

CAL2 Messages

CAL2P886E

RETURNED FLOW DOES NOT MATCH INPUT FLOW

Reason:
CAL2PCPMT received flow information from CA CPM that does not match the first
parameter in the parameter list.

Action:
Verify that the flowname requested is correct.

CAL2P887E

CAL2CPMT CCI RECEIVE TIMEOUT

Reason:
CA CPM did not respond.

Action:
Verify that CA CPM is active.

CAL2P888I

Criteria(parm=value) Actual(value ) Result(Match)

Reason:
The utility program CAL2CPMT matched a value returned from CA CPM to an execution
parameter value.

Action:
None.

CAL2P889W

Criteria(parm=n) Actual(n ) Result(No Match)

Reason:
The utility program CAL2CPMT received a value from CA CPM that did not match an
execution parameter value.

Action:
Review the jobs in the flow to determine the reason for the differences between
expected and actual results.

458 Message Reference Guide

 CAL2 Messages

CAL2P889I

Processing Flow: flowname

Reason:
The utility program CAL2CPMT is requesting information from CA CPM for the named
flow.

Action:
None.

CAL2P891E

No TCT (SMF TIMING CONTROL TABLE) found, cannot use MAXAGE=JOB

Reason:
An SMF table is required to determine the start time of a job running CAL2CPMT.

Action:
Remove the MAXAGE=JOB parameter or change to number of hours to select previous
matching flowname.

CAL2P892I

CPM Test: result Flow: flowname Status: status Load: yyyy-mm-dd hh:mm

Reason:
Utility program CAL2CPMT completed the comparison of parameter values and
information received from CA CPM. A result of Passed indicates all values matched.
*Failed* indicates at least one value did not match.

Action:
Review the jobs in the flow to determine the reason for any differences between
expected and actual results.

CAL2R001I

Building IVT

Reason:
Initialization of the IVT (Instance Vector Table) has started on this LPAR.

Action:
None.

Chapter 2: AFM - CA7R Messages 459

CAL2 Messages

CAL2R002E

Error creating SSCT; R15 is nnnnnnnn

Reason:
An error code was returned when the #SUBSYS macro was issued to create an SSCT for
'CA-7'.

Action:
CA Workload Automation SE requires the use of the subsystem name 'CA-7'. Ensure that
there is no conflict over the use of this name on this LPAR. If this name not currently
used by another application, contact your installation specialist for assistance.

CAL2R003E

IVT invalid; data at xxxxxxxx does not begin with 'IVT'.

Reason:
The IVT address in the SSCT for CA Workload Automation SE does not point to a valid
IVT.

Action:
Run CAL2ENVR to obtain a CA Workload Automation SE System Configuration Report,
and then contact your installation specialist for assistance.

CAL2R004E

Current CA-7 system environment requires L2OPTS input

Reason:
The CA Workload Automation SE product initialization routine requires a CA Workload
Automation SE System Configuration file if the IVT has been created on this LPAR.

Action:
Add the L2OPTS DD statement to the CAS9 procedure. This statement must point to a
valid CA Workload Automation SE System Configuration file. For more information
about this required modification, see the Systems Programming Guide and the
Installation Guide.

460 Message Reference Guide

 CAL2 Messages

CAL2R005I

No L2OPTS and no IVT; using default CA-7 system configuration

Reason:
This message is issued as a non-deletable WTO to the master console. This message is
issued if no IVT is found on this LPAR and no CA Workload Automation SE System
Configuration file is present.

Action:
The CA Workload Automation SE product initialization routine will attempt to initialize
the CA Workload Automation SE system environment using default options. If these
defaults are acceptable, no action is required. If the defaults are not acceptable, you
must create a CA Workload Automation SE System Configuration file and add it to the
CAS9 procedure with the L2OPTS DD statement. For more information, see the Systems
Programming Guide and the Installation Guide.

CAL2R006I

Function successful: GLOBAL nnnnnn

Reason:
CAIRIM successfully executed the function named at nnnnnn.

Action:
None.

CAL2R009E

Unable to LOAD required module; EP=nnnnnnnn LMOD=pppppppp; RC=xxxxxxxx

Reason:
A request to load a module failed. The name of the module that could not be loaded is
declared at pppppppp. The entry point name is nnnnnnnn. The return code is xxxxxxxx.

Action:
Verify that the module named in the message is either in the linklist, in LPA, or in the
STEPLIB concatenation for CAIRIM. Also, verify that the LKED attributes of AMODE and
RMODE are correct.

Chapter 2: AFM - CA7R Messages 461

CAL2 Messages

CAL2R012I

SSCT created for ssss

Reason:
An SSCT was created during CA Workload Automation SE system initialization. Valid
values of ssss include CA-7, UC07, or UCT7.

Action:
None.

CAL2R013I

IVT initialized at xxxxxxxx

Reason:
Initialization of the IVT (Instance Vector Table) for this LPAR is complete. xxxxxxxx is the
address of the IVT.

Action:
None.

CAL2R015I

L2rrINIT ended; RC=xxxxxxxx

Reason:
The CA Workload Automation SE product initialization routine ended with the indicated
return code. The product release is rr. The return code is xxxxxxxx.

Action:
None.

CAL2R018I

Release rr SMF exit intercept nnnnnnnn ooooooo

Reason:
Operation ooooooo can be enabled or disabled. The CA Workload Automation SE
product initialization routine either added (enabled) or removed (disabled) the SMF
intercept named at nnnnnnnn. The release is rr.

Action:
None.

462 Message Reference Guide

 CAL2 Messages

CAL2R019I

Associated SVC nnn with routine at xxxxxxxx

Reason:
The routine at xxxxxxxx will be entered when the SVC named at nnn is issued.

Action:
None.

CAL2R020E

#SMFI failed for nnnnnnnn; RC was xxxxxxxx

Reason:
The CA Workload Automation SE product initialization routine issued #SMFI to create an
SMF exit intercept. The request failed. The message reports the return code from #SMFI
at xxxxxxxx. This message may be accompanied by other messages that give more
precise reasons for the error.

Action:
Run CAL2ENVR to obtain a CA Workload Automation SE System Configuration Report
and contact your installation specialist for assistance.

CAL2R023E

#SVCI failed; SVC=nnn ADDR=xxxxxxxx RC=yyyyyyyy

Reason:
An error code (yyyyyyyy) was received when the CA Workload Automation SE product
initialization routine issued the #SVCI macro to associate the SVC number (nnn) with the
routine located at xxxxxxxx. This message may be accompanied by other messages that
give more precise reasons for the error.

Action:
Run CAL2ENVR to obtain a CA Workload Automation SE System Configuration Report
and contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 463

CAL2 Messages

CAL2R026I

L2rrINIT (nnnn.nnn mm/dd/yy hhmm) entered on yyyy.ddd at hh:mm:ss:thijk

Reason:
This message identifies the version of the CA Workload Automation SE product
initialization routine (nnnn.nnn mm/dd/yy hhmm) and the date and time the module
was entered (yyyy.ddd at hh:mm:ss:thijk). The product release is rr.

Action:
None.

CAL2R027I

Preparing to disable xxxxxxxx

Reason:
The CA Workload Automation SE product initialization routine will attempt to remove
the SMF intercept named at xxxxxxxx.

Action:
None.

CAL2R030E

Error on stmt nnnn; cccccc xxxxxxxx

Reason:
An error was detected while processing a configuration statement. Statements are
processed in the order in which they occur in L2OPTS. nnnn is the number of the
statement in error. cccccc is the value entered for the instance. xxxxxxxx is the value
entered for the function.

Action:
Review accompanying messages for information about the specific reason for the error
and take corrective action.

464 Message Reference Guide

 CAL2 Messages

CAL2R031I

FORCESSCT specified; overlaying SSCTSUSE in CA7 SSCT

Reason:
The SSCT for CA Workload Automation SE was located, but the SSCTSUSE field was not
zero nor did it point to a valid IVT. Since FORCESSCT was specified, the SSCTSUSE field in
that SSCT is overlaid with the pointer to the CA Workload Automation SE IVT.

Action:
None.

CAL2R032E

INIT rejected; FORCESSCT not specified

Reason:
The SSCT for CA Workload Automation SE was located, but the SSCTSUSE field was not
zero, nor did it point to a valid IVT. Because FORCESSCT was not specified, L2B3INIT
does not create an IVT for this LPAR.

Action:
There may be a conflict over the use of the subsystem named 'CA-7'. CA Workload
Automation SE requires exclusive use of this subsystem. If FORCESSCT is specified, the
CA Workload Automation SE product initialization routine will overlay existing data in
the control block associated with this subsystem.

CAL2R033I

Attempting to restore SVC nnn with routine at xxxxxxxx

Reason:
An error occurred during the attempt to define the CA Workload Automation SE SVC.
The CA Workload Automation SE product initialization routine will attempt to associate
the SVC nnn with the routine at xxxxxxxx.

Action:
Review accompanying messages for information about the specific reason for the error.

Chapter 2: AFM - CA7R Messages 465

CAL2 Messages

CAL2R035I

Instance xxxx still active

Reason:
A GLOBAL DELETE was requested, but at least one instance was still active. The instance
identifier is xxxx.

Action:
Delete the active instances before issuing the GLOBAL DELETE, or issue GLOBAL DELETE
ALL to delete all active instances.

CAL2R036E

Input missing or invalid on one or more statements

Reason:
Required CA Workload Automation SE System Configuration file parameter input was
not detected or was invalid.

Action:
Ensure that the CA Workload Automation SE System Configuration file statement
parameters conform to rules documented in the Systems Programming Guide.

CAL2R037E

Exceeded maximum number of continuations

Reason:
The amount of storage needed to handle continuations for CA Workload Automation SE
System Configuration file statements exceeded the maximum allowable.

Action:
Correct the statement in error. If the statement needs to be continued, ensure that it
conforms to the rules in the Systems Programming Guide for continuation of CA
Workload Automation SE System Configuration file statements.

466 Message Reference Guide

 CAL2 Messages

CAL2R038E

(nnnn) No valid parameters entered for xxxxxxxx

Reason:
CA Workload Automation SE System Configuration file parameter input required for the
indicated function (xxxxxxxx) was not supplied.

Action:
Verify that the CA Workload Automation SE System Configuration file statement
parameters conform to rules documented in the Systems Programming Guide.

CAL2R039E

(nnnn) NCF keyword only valid on CA71

Reason:
The NCF keyword cannot be used on any instance other than CA71.

Action:
Remove the NCF keyword from the statement in error and resubmit CAIRIM.

CAL2R040E

(nnnn) Instance identification error

Reason:
The CA Workload Automation SE product initialization routine was unable to locate a
valid instance identifier. Valid instance identifiers are: GLOBAL, CA71, CA72, CA73, CA74,
CA75, CA76, CA77, and CA78. nnnn is the number of the statement in error.

Action:
Review the L2OPTS statement in error and take corrective action.

CAL2R041E

(nnnn) Verb validation error

Reason:
The CA Workload Automation SE product initialization routine did not recognize the
action requested. nnnn is the number of the statement in error.

Action:
Review the L2OPTS statement in error and take corrective action.

Chapter 2: AFM - CA7R Messages 467

CAL2 Messages

CAL2R042E

(nnnn) Keyword validation error. Data: xxxxxxxx

Reason:
An invalid keyword was detected. The first four bytes of the parameter in error are
reported at xxxxxxxx. nnnn is the number of the statement where the error was
detected.

Action:
Review the L2OPTS statement in error and take corrective action.

CAL2R043E

(nnnn) Duplicate keyword

Reason:
The CA Workload Automation SE product initialization routine detected a duplicate
keyword. The statement is rejected. nnnn is the number of the statement where the
duplicate keyword was detected.

Action:
Review the L2OPTS statement and remove the duplicate keyword.

CAL2R044E

(nnnn) System already initialized. GLOBAL xxxxx not allowed.

Reason:
The request is not compatible with the current system configuration. Requests for
GLOBAL INIT or GLOBAL INITC are not valid when the CA Workload Automation SE
system is already initialized. nnnn is the number of the statement in error.

Action:
If additional CA Workload Automation SE system configuration changes are required,
correct the L2OPTS statements and resubmit CAIRIM.

468 Message Reference Guide

 CAL2 Messages

CAL2R045E

(nnnn) System not initialized. GLOBAL REFResh not allowed

Reason:
The request is not compatible with the current system configuration. A GLOBAL REFResh
is not allowed unless the CA Workload Automation SE system has been initialized. nnnn
is the number of the statement in error.

Action:
Code the L2OPTS statements needed for the CA Workload Automation SE system
configuration that you want, and resubmit CAIRIM.

CAL2R046E

(nnnn) System not initialized. GLOBAL xxxxxx not allowed

Reason:
The request is not compatible with the current system configuration. The specified
function is not allowed unless the CA Workload Automation SE system has been
initialized. nnnn is the number of the statement in error.

Action:
Code the L2OPTS statements for the CA Workload Automation SE system configuration
that you want, and resubmit CAIRIM.

CAL2R047E

(nnnn) System not initialized. Instance ADD not allowed

Reason:
The request is not compatible with the current system configuration. The CA Workload
Automation SE system must be initialized to add an instance. nnnn is the number of the
statement in error.

Action:
Code the L2OPTS statements for the CA Workload Automation SE system configuration
that you want, and resubmit CAIRIM.

Chapter 2: AFM - CA7R Messages 469

CAL2 Messages

CAL2R048E

(nnnn) CA7x instance already active. ADD not allowed

Reason:
The request is not compatible with the current system configuration. An ADD is not valid
for an active instance. nnnn is the number of the statement in error.

Action:
Code the L2OPTS statements for the CA Workload Automation SE system configuration
that you want, and resubmit CAIRIM.

CAL2R049E

(nnnn) CA7x instance not active. UPD not allowed

Reason:
The request is not compatible with the current system configuration. An UPDate is not
valid unless the instance is active. nnnn is the number of the statement in error.

Action:
Code the L2OPTS statements for the CA Workload Automation SE system configuration
that you want, and resubmit CAIRIM.

CAL2R050E

(nnnn) CA7x instance not active. DEL not allowed

Reason:
The request is not compatible with the current system configuration. A DELete is not
valid unless the instance is active. nnnn is the number of the statement in error.

Action:
Code the L2OPTS statements for the CA Workload Automation SE system configuration
that you want, and resubmit CAIRIM.

470 Message Reference Guide

 CAL2 Messages

CAL2R051E

(nnnn) SVC and TSVC conflict

Reason:
The same value was coded for SVC and TSVC on the GLOBAL INITC statement in the CA
Workload Automation SE System Configuration file. If you intend to support a test copy
in compatibility mode the TSVC value cannot be the same as the SVC value. The CA
Workload Automation SE system environment was not initialized.

Action:
Ensure that SVC and TSVC have the correct values and resubmit CAIRIM.

CAL2R052E

(nnnn) Unable to locate xxxxxxxx

Reason:
The CA Workload Automation SE product initialization routine failed to locate a module.
The name of the module is reported at xxxxxxxx. nnnn is the number of the statement in
error.

Action:
If the module name reported in the message (xxxxxxxx) occurs on an L2OPTS statement,
ensure that it is correctly spelled on that statement. Also ensure that the module is
accessible from the CAIRIM procedure (either in a linklisted library or in the STEPLIB
concatenation).

CAL2R053E

(nnnn) Invalid alias

Reason:
The request for an alias is invalid. The alias must conform to the rules discussed in the
Systems Programming Guide.

Action:
Choose a valid alias and resubmit CAIRIM.

Chapter 2: AFM - CA7R Messages 471

CAL2 Messages

CAL2R054E

(nnnn) xxxxxxxx conflict; SVC already in use - sss

Reason:
The requested SVC number is associated with another application. xxxxxxxx is the
module name and sss is the number of the SVC. nnnn is the number of the statement in
error.

Action:
Choose a different SVC number or specify FORCESVC to associate the CA Workload
Automation SE SVC routines with this SVC number and resubmit CAIRIM.

CAL2R055I

(nnnn) FORCESVC specified

Reason:
This message announces that the FORCESVC option was specified.

Action:
None.

CAL2R056I

(nnnn) ICMDSECT built from yyyyyyyy

Reason:
This message is issued when CAIRIM initializes the CA Workload Automation SE system
environment without a System Configuration file. In this case the CA Workload
Automation SE product initialization routine attempts to locate ICMDSECT. If ICMDSECT
is located using the UC07 or UCT7 SSCT, the value of yyyyyyyyy is 'SSCT'. If ICMDSECT
cannot be so located, the CA Workload Automation SE product initialization routine will
attempt to find ICMDSECT in LPA. If ICMDSECT is found in LPA, the value of yyyyyyyyy is
'LPA'. If it is not found in LPA, the CA Workload Automation SE product initialization
routine will construct an ICMDSECT using default values. In that case, the value of
yyyyyyyyy is 'DEFAULTS.'

Action:
None.

472 Message Reference Guide

 CAL2 Messages

CAL2R057I

L2OPTS/nnnn xxxxxxxxxxxxxxxx

Reason:
This message echoes the L2OPTS statement. nnnn is the number of the statement.

Action:
None.

CAL2R059I

Preprocessing complete for default initialization

Reason:
Configuration settings for a default initialization were internally generated since no CA
Workload Automation SE System Configuration file was presented to the product
initialization routine.

Action:
None.

CAL2R064I

Previous CA-7 release detected: rr

Reason:
Structures associated with a previous release of CA Workload Automation SE were
detected by the CA Workload Automation SE product initialization routine. rr identifies
the release. This is a status message. A release upgrade is required and a GLOBAL
REFRESH statement is internally generated by the product initialization routine as
needed.

Action:
None.

Chapter 2: AFM - CA7R Messages 473

CAL2 Messages

CAL2R065E

UCC7NODE table invalid

Reason:
The NCF node table (UCC7NODE) is invalid and cannot be used.

Action:
The NCF node table does not begin with a valid eyecatcher. If NCF is to be used, ensure
that a valid NCF node table named UCC7NODE is either in linklist, LPA, or in the STEPLIB
concatenation of the CAIRIM procedure.

CAL2R066I

Dummy NCF node table; NCF option suppressed

Reason:
The default UCC7NODE table was located. NCF will not be used on this LPAR.

Action:
None.

CAL2R067E

NCF(nn) not found in the NCF node table

Reason:
The entry for the node ID specified could not be located in the NCF node table. nn is the
last two characters of the value specified on the NCF keyword.

Action:
If NCF is to be used, supply the correct node identifier and resubmit CAIRIM.

CAL2R068I

Host NCF node defaulting to first in node table

Reason:
UCC7NODE was reordered so that the entry with the SMFID for this LPAR is first in the
NCF node table.

Action:
None.

474 Message Reference Guide

 CAL2 Messages

CAL2R069E

xxxx table format invalid; module nnnnnnnn

Reason:
The indicated table contains invalid data. Values of xxxx include XJOB, XDSN, and XU83.
The name of the module in error is nnnnnnnn.

Action:
Verify the table named is correctly coded. Also ensure that the intended copy of the
module named is in the appropriate location.

CAL2R071I

Instance xxxx successfully nnnnnnnn

Reason:
Operation nnnnnnnn successfully completed for instance xxxx.

Action:
None.

CAL2R072E

xxxx nnnnnnnn failed

Reason:
The indicated function did not complete successfully. The name of the function is
reported at nnnnnnnn and the instance is named at xxxx.

Action:
Review accompanying messages for information about the specific reason for the error.

CAL2R073E

SVC initialization failed for xxxx

Reason:
The SVC initialization process did not complete successfully. The instance is reported at
xxxx.

Action:
Ensure that there is no conflict over the use of the SVC number. Review accompanying
messages for information about the specific reason for the error.

Chapter 2: AFM - CA7R Messages 475

CAL2 Messages

CAL2R074E

Function not recognized: xx

Reason:
CA Workload Automation SE did not recognize an internal function code, identified by
xx. Initialization terminates with return code 32.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2R075E

REFRESH required for upgrade; L2OPTS input ignored

Reason:
The product initialization module for CA Workload Automation SE (L2B3INIT) forced a
GLOBAL REFRESH to upgrade the CA Workload Automation SE system environment.
L2OPTS statements were not processed.

Action:
Run CAIRIM again to process the L2OPTS statements that were ignored now that the
system is upgraded.

CAL2R076I

Health Checker fffffff successful

Reason:
The CAIRIM function, fffffff, was successful for the IBM Health Checker interface.

Action:
None.

476 Message Reference Guide

 CAL2 Messages

CAL2R077I

Health Checker aaaaaa pppppp failed, R15(xxxx) R0(rrrr)

Reason:
The IBM Health Checker action, aaaaaa (ADD or DELETE) for routine and pppppp
(CHECKS or EXIT), failed. xxxx indicates the return code in Register 15. rrrr indicates the
reason code in Register 0.

Action:
Perform one of the following actions:
■ For routine, when pppppp is EXIT, the return and reason codes are for macro
CSVDYNEX. See the IBM manual MVS Authorized Assembler Services Reference for
more information about CSVDYNEX return and reason codes. Contact your
installation specialist for assistance.
■ For routine, pppppp is CHECKS, the return and reason codes are for macro
HZSCHECK. See IBM Health Checker for z/OS User Guide for more information about
HZSCHECK return and reason codes. Contact your installation specialist for
assistance.

CAL2S001E

- Unable to open L2OPTS

Reason:
Program CAL2SC80 was unable to open ddname L2OPTS for output. The job terminates
with return code 32, reason code 4.

Action:
Ensure the ddname is pointing to a valid data set that is not in use by another job or
started task. Then resubmit the job.

CAL2S002W

- No report generated

Reason:
Program CAL2SC80 was unable to open ddname SYSPRINT. The program continues but
no report is generated.

Action:
If a report is wanted, ensure the SYSPRINT ddname is pointing to a valid sysout class and
rerun the job.

Chapter 2: AFM - CA7R Messages 477

CAL2 Messages

CAL2S003E

- Unable to locate any active CA-7 instances

Reason:
Program CAL2SC80 was unable to continue because no instances of CA Workload
Automation SE were active. The program terminates with a return code 32, reason code
8.

Action:
Run CAIRIM, specifying GLOBAL INIT or GLOBAL INITC, as necessary, and also specifying
CA71 ADD. After initialization completes, rerun the CAL2SC80 job.

CAL2S010E

- Unable to open SYSPRINT DD

Reason:
Program CAL2ENVR was unable to open the SYSPRINT data set.

Action:
Ensure the JCL has a valid SYSPRINT DD record and resubmit the job.

CAL2S1100

- ssssssss selected to submit jjjjjjjj(nnnnn)

Reason:
This message can be issued if SUBMSGLVL=1 is specified. It is a status message that
names the output thread (at ssssssss) that is selected to submit the job named jjjjjjjj. The
CA 7 WA job number is also reported at (nnnnn).

Action:
None.

478 Message Reference Guide

 CAL2 Messages

CAL2S1101

- Selection scan suspended: no CA7JSOTs available; jjjjjjjj(nnnnn)

Reason:
This message can be issued if SUBMSGLVL=2 is specified. The job selection thread has
chosen a job to submit. If known, the job name is reported at jjjjjjjj, and the CA 7 WA job
number reported at (nnnnn). No submission output threads are available to process the
job. It need not imply an error condition but is likely due to the fact the output threads
are busy handling output for other jobs.

Action:
None.

CAL2S1102

- Unable to process ARF IS exception for jjjjjjjj(nnnnn)

Reason:
An ARF IS exception was detected for a job, but an error occurred during the attempt to
return the job to the request queue. The job name is reported at jjjjjjjj, the CA 7 WA job
number is reported at (nnnnn). This may indicate a serious error.

Action:
Contact your installation's CA Workload Automation SE technical specialist for
assistance.

CAL2S1111

- Ready queue is not memory resident

Reason:
Parallel Submission Processing requires INDEX=A on the FORMAT statement for the
ready queue in the product's initialization file. The value of PSP is set to N. CA Workload
Automation SE will submit jobs serially.

Action:
None if you do not intend to use Parallel Submission Processing.

Specify INDEX=A on the FORMAT statement for the ready queue in the product's
initialization file to use Parallel Submission Processing,

Chapter 2: AFM - CA7R Messages 479

CAL2 Messages

CAL2S1201

- Unable to locate submission output module: xxxxxxxx

Reason:
A BLDL failed for the module named at xxxxxxxx This is an error.

Action:
Perform the following actions:
■ Verify that the modules named are in the LINKLIST or in the STEPLIB concatenation
for CA Workload Automation SE.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2S1202

- MAXSUBOUT requested was xx; reducing request to maximum allowed (yy)

Reason:
This is a status message. The value of MAXSUBOUT (xx) exceeds the maximum number
of output threads supported. CA Workload Automation SE continues initialization using
the maximum number of output threads supported (yy).

Action:
Enter a correct value on the MAXSUBOUT keyword on the OPTIONS statement in the
product's initialization file.

Note: For more information about this keyword, see the Systems Programming Guide.

CAL2S1203

- Number of submission output threads requested = xx; number allocated = yy

Reason:
This is a status message. The value of xx and yy should be the same unless an error
occurred during thread allocation.

Action:
None.

480 Message Reference Guide

 CAL2 Messages

CAL2S1204

- PSP=N specified; MAXSUBOUT value ignored

Reason:
The MAXSUBOUT keyword was coded on the OPTIONS statement in the product's
initialization file. However, use of that keyword requires parallel submission processing.
The value of MAXSUBOUT is ignored.

Action:
None.

CAL2S1205

- SCT validation error

Reason:
This is an error message. The structure of the UCC7 load module is not valid. CA
Workload Automation SE requests abnormal termination. This is a serious error.

Action:
Contact your installation's CA Workload Automation SE technical specialist for
assistance.

CAL2S1206

- Number of output threads requested exceeds number of available internal readers

Reason:
CA Workload Automation SE was unable to dynamically allocate one or more internal
readers. The number of output threads is reduced to correspond to the number of
available internal readers.

Action:
None.

Chapter 2: AFM - CA7R Messages 481

CAL2 Messages

CAL2S1207

- Attempting internal reader allocations; DDNAME(CA7INTxx), BLKSIZE(080),

SYSOUT(X)

Reason:
This is a status message. CA Workload Automation SE attempts to allocate internal
readers with the indicated attributes.

Action:
None.

CAL2S1208

- DDNAME(nnnnnnnn) allocation failed; SVC 99 RC=cc S99ERROR(eeee) S99INFO(iiii)

Reason:
A request to dynamically allocate an internal reader failed. The number of submission
output threads will be reduced to correspond to the number of available internal
readers.

Action:
None.

CAL2S1209

- Internal readers successfully allocated

Reason:
This is a status message announcing that internal readers were allocated.

Action:
None.

482 Message Reference Guide

 CAL2 Messages

CAL2S1210

- Insufficient number of internal readers; value of PSP set to N

Reason:
The internal readers required by Parallel Submission Processing could not be allocated.
The value of PSP is set to N. CA Workload Automation SE will submit jobs serially.

Action:
None if you do not intend to use Parallel Submission Processing.

To use Parallel Submission Processing, perform the following actions:

■ Review the preceding messages.
■ Determine the reason that internal readers could not be allocated.

CAL2S1212

- NOTE! Parallel Submission Processing

- forced off (PSP=N);
- SASSXX02 exit NOT supported by PSP

Reason:
Parallel Submission Processing does not support use of the SASSXX02 exit. However, this
exit was located by CA Workload Automation SE. The value of PSP is dynamically
changed from the default of Y to N. CA Workload Automation SE will submit jobs
serially.

Action:
None if you do not intend to use Parallel Submission Processing.

If you do intend to use PSP, remove the SASSXX02 exit from the steplib or linklist library.

CAL2S1213

CA7INT01 FOUND / MAXSUBOUT NOT USED

Reason:
A DD statement with ddname CA7INT01 is found in the CA Workload Automation SE JCL.
This is an informational message.

Action:
None.

Chapter 2: AFM - CA7R Messages 483

CAL2 Messages

CAL2S1214

- APPLCTN=xxxxxxxx module not found. Exit ignored.

Reason:
The specified user exit was not found in a steplib or system library. The specification is
ignored.

Action:
If you do not intend to use the exit, remove the APPLCTN statement from the
initialization file. If you intend to use the exit, make sure the module is available in one
of the steplib libraries.

CAL2S1412

- WARNING! PSP=N specified. SASSXX20

- located, but SASSXX02 not found;
- SASSXX20 is NOT supported if PSP=N

Reason:
This is a warning message. CA Workload Automation SE located the SASSXX20 exit, but
this exit is not supported unless Parallel Submission Processing is in effect. The CA
Workload Automation SE exit used to modify statements when CA Workload
Automation SE submits jobs serially is SASSXX02. That exit was not found.

Action:
None unless you want to use an exit to modify statements when CA Workload
Automation SE submits jobs serially. In that case, use the SASSXX02 exit.

CAL2S1512W

PSP=YES Required for MULTIJOB=REQUEUE; Option reset to MULTIJOB=FLUSH

Reason:
The MULTIJOB security initialization option was changed from REQUEUE to FLUSH
because MULTIJOB=REQUEUE is supported only with active PSP.

Action:
None if FLUSH is suitable for you. Otherwise, specify PSP=Y on the OPTIONS statement
in the product's initialization file and restart CA Workload Automation SE.

484 Message Reference Guide

 CAL2 Messages

CAL2S2001

- Undefined function code in CA7JSOT: nn

Reason:
A submission output thread was posted with an unrecognized function code. This
message is an error.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2S2002

- Submission output subtask initialized; (ss tttttttt jjjjjjjj)

Reason:
This is a status message. The subtask for a submission output thread initialized. ss
identifies the submission output thread. The TCB address of the subtask is tttttttt and
the primary thread control block (7JSOT) address is jjjjjjjj.

Action:
None.

CAL2S2005

- ss posted tttttttt(jjjjjjjj); E/F=eeeeeeee/ffffffff; jjjjjjjj(nnnnn)

Reason:
This message can be issued when SUBMSGLVL=2 is specified. It is a diagnostic message
that is issued when the submission output subtask is posted.

Action:
None.

CAL2S2007

- ss(jjjjjjjj) dispatched; E/F=eeeeeeee/ffffffff; jjjjjjjj(nnnnn)

Reason:
This message can be issued when SUBMSGLVL=2 is specified. It is a diagnostic message
that is issued when the submission output main task thread is posted.

Action:
None.

Chapter 2: AFM - CA7R Messages 485

CAL2 Messages

CAL2S2012

- Submission output subtask for ssssssss ended; ECB=eecccccc

Reason:
This message is issued when a submission output subtask terminates. If the subtask was
in the process of submitting a job when the task ended, it should be returned to the
request queue with the status: R-JCLERR. When CA Workload Automation SE shuts
down, the message is also issued as part of normal task termination. In that case, the
message is not considered an error and does not require further attention.

Action:
None if cccccc is zero. If cccccc is not zero, it is considered an error. For assistance,
contact CA Support at ca.com/support for assistance.

CAL2S2013

- Shutdown requested for ssssssss

Reason:
This is a status message, which is issued during CA Workload Automation SE shutdown.

Action:
None.

CAL2S2014

- ssssssss initialized

Reason:
This is a status message, which is issued when a submission output thread is invoked for
the first time.

Action:
None.

486 Message Reference Guide

 CAL2 Messages

CAL2S2200

- ssssssss preprocessing security segment for jjjjjjjj

Reason:
This message can be issued when SUBMSGLVL=2 is specified.

Action:
None.

CAL2S2302

- ss tttttttt jjjjjjjj; aaaaaaaa bbbbbbbb ccccccccc mmmmmmmm

Reason:
This message is issued when a macro fails in a submission output subtask. ss identifies
the submission output thread, tttttttt is the address of the subtask TCB, and the macro
is named at mmmmmmmm. This message is an error indication.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2S2303

- Submission error: no JCL statements to submit

Reason:
This message is issued when JCL modification is complete and no JCL statements were
ready to submit. This message is an error indication.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2S2306

- ss substrt tttttttt(jjjjjjjj); jjjjjjjj(nnnnn)

Reason:
This status message can be issued if SUBMSGLVL=3. It is issued at start of internal reader
processing for a job. The job name is reported at jjjjjjjj, the CA 7 WA job number is
reported at (nnnnn).

Action:
None.

Chapter 2: AFM - CA7R Messages 487

CAL2 Messages

CAL2S2306

- ss subcomp tttttttt(jjjjjjjj); jjjjjjjj(nnnnn) JES#(aaaaaaaa)

Reason:
This status message can be issued if SUBMSGLVL=3. It is issued when internal reader
processing for a job is complete. The name of the job is reported at jjjjjjjj, the CA
Workload Automation SE job number is reported at (nnnnn), and the JES number for the
job is reported at (aaaaaaaa).

Action:
None.

CAL2S2401

- jjjjjjjj(nnnnn): PRE(rrr,rrr) PRC(rrr,rrr)

Reason:
This status message can be issued when SUBMSGLVL=3. The message is issued when job
submission processing for a job is complete. The submission output preprocessing
reason and return codes are reported at PRE(rrr,rrr), and the submission output
processing reason and return codes are reported at PRC(rrr,rrr).

Action:
None when both return code values are zero. Otherwise, the message indicates an
error. For assistance, contact CA Support at ca.com/support.

CAL2S5001I

SASSSO0x preprocessing XPJOB|agent submission for jjjjjjjj (nnnnn)

Reason:
This informational message is a result of tracing an XPJOB, and agent, or the
initialization file OPTION SUBMSGLVL parameter. This message indicates that job jjjjjjjj,
with CA Workload Automation SE number nnnnn has started the preprocessing stage of
the submission process in the subtask x.

Action:
None.

488 Message Reference Guide

 CAL2 Messages

CAL2S6001I

SASSSO0x Actual XPJOB|Agent submission process for jjjjjjjj

Reason:
This informational message is a result of tracing an XPJOB, an agent, or the initialization
file OPTION SUBMSGLVL parameter. This message indicates that job jjjjjjjj has started
the submission process of creating the actual data that will be sent across to the
destination platform.

Action:
None.

CAL2S6002I

SASSSO0x End of XPJOB|Agent submission process for jjjjjjjj

Reason:
This informational message is a result of tracing an XPJOB, an agent, or the initialization
file OPTION SUBMSGLVL parameter. This message indicates that job jjjjjjjj has ended the
transmission portion of the submission process.

Action:
None.

CAL2S6003W

CCI SEND returned RC greater than max

Reason:
A CA Workload Automation SE CAICCI SEND has encountered an unknown error and
returned a return code that is greater than the known maximum.

Action:
Ensure the CCI environment is not having problems in sending and receiving data.
Report this message and any related messages to CA Support.

Chapter 2: AFM - CA7R Messages 489

CAL2 Messages

CAL2S6004E

AGPSWD timeout waiting on IAS response, contact your CA 7 specialist

Reason:
A timeout occurred waiting for CA Integrated Agent Services (CA IAS) to respond to a
password maintenance request. CA IAS has failed to respond to a CA Workload
Automation SE AGPSWD terminal request for password maintenance.

Action:
Perform the following actions:
■ Contact your installation specialist for assistance.
■ Check for other CA Workload Automation SE messages that may indicate a problem
with CA IAS.

CAL2S6005E

Storage obtain failed for user AFM trace; tracing now set off

Reason:
A STORAGE OBTAIN for a log work area has failed. Tracing is set off.

Action:
If you require tracing, try to turn it on again with the '/IAS,FUNC=AGLOGON' command.
If the problem persists, contact your installation specialist for assistance.

CAL2S6006E

IAS DIV file is full, agent communication is stopped

Reason:
CA Workload Automation SE tried to send a message to an agent through CA Integrated
Agent Services (CA IAS), and the checkpoint file is full. The message is not sent.

Action:
Verify that your CA IAS checkpoint file is large enough. Contact your installation
specialist for assistance.

490 Message Reference Guide

 CAL2 Messages

CAL2S7001I

jjjjjjjj (nnnnn): PRE(rrr,rrr) PRC(rrr,rrr)

Reason:
This informational message is a result of tracing an XPJOB, an agent, or the initialization
file OPTION SUBMSGLVL parameter. This message indicates that job jjjjjjjj, with CA
Workload Automation SE number nnnnn, has completed the submission process with
the return and reason codes (rrr,rrr) for the preprocessing stage and the submission
processing stage of the submission process.

Action:
None if the PRE and PRC return codes are zero. If the PRE and PRC return codes are
nonzero, ensure that the XPJOB parameters or agent parameters are correctly coded,
and that CAICCI or TCP/IP is active and in communication with the destination node
where the job is destined. Because the job is redirected to the request queue, check the
status of the job there. If unable to resolve why the job is not getting submitted, contact
CA Support at ca.com/support for assistance.

CAL2T002E

Invalid port number

Reason:
The port number in the parameter list for program CAL2X2TB is invalid. The program
terminates with RC=16 and a condition code of 2.

Action:
Correct the port number and resubmit the job.

CAL2T003E

Parameter list is required

Reason:
A parameter list was not found. One is required.

Action:
Add a parameter list and resubmit the job.

Chapter 2: AFM - CA7R Messages 491

CAL2 Messages

CAL2T004E

Invalid parameter list

Reason:
The parameter list for program CAL2X2TB is invalid. The program terminates with RC=16
and a condition code of 1.

Action:
Correct the parameter list, and resubmit the job.

CAL2T005E

Invalid parameter starting with (parameter).

Reason:
The parameter list for program CAL2X2TB is invalid, starting with parameter. The
program terminates with RC=16 and a condition code of 2.

Action:
Correct the parameter list, and resubmit the job.

CAL2T006E

DD statement is missing or invalid: xxxxxxxx

Reason:
DD statement xxxxxxxx is either missing or invalid. The program terminates with RC=16
and a condition code of 3.

Action:
Correct the DD statement, and resubmit the job.

492 Message Reference Guide

 CAL2 Messages

CAL2T007E

Error during DCB open: xxxxxxxx

Reason:
Program CAL2X2TB tried to open DD statement xxxxxxxx and failed. The program
terminates with RC=16 and a condition code of 4.

Action:
Perform the following actions:
■ Ensure the DD statement is present and points to a valid data set.
■ Resubmit the job.

CAL2T008W

Warning - Print DD statement is missing or invalid: xxxxxxxx

Reason:
Program CAL2X2TB tried to open the print statement (the default name is SYSPRINT)
and failed. The job continues to execute.

Action:
No action is necessary if you meant to omit or dummy out the DD statement. Otherwise,
correct the DD statement, and resubmit the job.

CAL2T009E

Unable to obtain storage for xxxxxxxx. RC=nnnn.

Reason:
Program CAL2X2TB tried to obtain storage for a program, DCB, or routine, which is
named xxxxxxxx. The return code from the STORAGE OBTAIN macro is nnnn.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 493

CAL2 Messages

CAL2T010E

Unable to load module xxxxxxxx. RC=nnnn.

Reason:
Program CAL2X2TB tried to load module xxxxxxxx. The return code from the LOAD
macro is nnnn.

Action:
Contact your installation specialist for assistance.

CAL2T011E

Non-zero return code from CAL2X2T0. RC=xxxxxxxx CC=yyyyyyyy

Reason:
Program CAL2X2TB received a nonzero return code from CAL2X2T0. The return code is
xxxxxxxx, and the condition code is yyyyyyyy.

Action:
Contact your installation specialist for assistance.

CAL2T012I

CA 7 TCP/IP batch process complete. RC=xxxxxxxx CC=yyyyyyyy

Reason:
The TCP/IP batch process completed. The return code is xxxxxxxx, and the condition
code is yyyyyyyy.

Action:
None.

CAL2T013W

Error msgs found in output. Msgs matched=xxxxx, high CC=yyy.

Reason:
One or more messages found in the output matched messages in a user-supplied
message table. The number of messages matched is xxxxx. The highest condition code
encountered is yyy. The user-supplied message table determines the actions.

Action:
Contact your installation specialist for assistance.

494 Message Reference Guide

 CAL2 Messages

CAL2T014I

***** INPUT TO CA 7 TCP/IP BATCH INTERFACE *****

Reason:
This message prints before listing the command input to the CA Workload Automation
SE TCP/IP batch interface. The input commands are listed following this message.

Action:
None.

CAL2T015I

***** END OF INPUT TO CA 7 TCP/IP BATCH INTERFACE *****

Reason:
This message prints after listing the command input to the CA Workload Automation SE
TCP/IP batch interface.

Action:
None.

CAL2T016W

***** NO CA 7 COMMANDS IN INPUT *****

Reason:
This message indicates that no CA Workload Automation SE commands are in the input
to the CA Workload Automation SE TCP/IP interface.

Action:
Perform the following actions:
■ Check to ensure that DDNAME SYSIN is in the JCL to invoke the CA Workload
Automation SE TCP/IP interface.
■ If you overrode the DDNAME for command input, ensure that the DDNAME in your
JCL correctly corresponds to the override.

Chapter 2: AFM - CA7R Messages 495

CAL2 Messages

CAL2T017I

***** RESPONSES RECEIVED FROM CA 7 *****

Reason:
This message prints before listing the command output from CA Workload Automation
SE to the CA Workload Automation SE TCP/IP interface. The command output lines are
listed following this message.

Action:
None.

CAL2T018I

***** END OF CA 7 RESPONSES *****

Reason:
This message prints after listing the command output sent from CA Workload
Automation SE to the CA Workload Automation SE TCP/IP interface.

Action:
None.

CAL2T019W

***** NO CA 7 RESPONSES RECEIVED *****

Reason:
This message indicates that CA Workload Automation SE received no command output.
This message can also be produced for a TCP/IP terminal, which uses a CAICCI terminal,
during CA Workload Automation SE shutdown.

Action:
Look for other messages in SYSPRINT or in the JES log to indicate errors in the
commands or the interface.

496 Message Reference Guide

 CAL2 Messages

CAL2T020W

Unable to open ERRORS DD. Message table errors will not be reported.

Reason:
This message is issued when a user-defined Batch Message Table (SASSXXBT) is
available, but the DD statement for the ERRORS file is not in the JCL. Normally, messages
from the Batch Message Table checking are routed to this ERRORS DD. Because this DD
is not available, the messages are not produced. However, you still get the CAL2T013W
message that contains the number of table matches and the highest matched condition
code.

Action:
Add a DD statement for ERRORS.

Note: The format is the same as the existing SYSPRINT DD.

CAL2T021W

Error message table match. CC=xxx. ...text...

Reason:
This message is written to the ERRORS DD when a line in the CA Workload Automation
SE TCP/IP batch output matches an entry in the user-defined batch message table
SASSXXBT. The condition code that is associated with that table entry is listed. In
addition, the text of the matching output line is shown.

Action:
None.

CAL2T022I

User-defined message table SASSXXBT loaded

Reason:
The user-defined batch message table (SASSXXBT) loaded successfully.

Action:
None.

Chapter 2: AFM - CA7R Messages 497

CAL2 Messages

CAL2T023E

Invalid parameter: xxxxxxxx. Aborting.

Reason:
An invalid parameter (xxxxxxxx) was passed to the CA Workload Automation SE TCP/IP
interface module.

Action:
Correct the specified parameter and resubmit or execute the interface.

CAL2T024W

X2T0 ESTAE entered: WIP=wwww (aaaa) (pppppppp): ddd...ddd

Reason:
The main task error routine has been entered for an abend in processing.
wwww
Indicates the where-in-program code.
aaaa (hex)
Indicates the abend code.
pppppppp
Indicates the abend PSW.
If the PSW points to an address within the main task program (CAL2X2T0), it is in
the form of +offset. If not, it is the full eight-character PSW.
ddd...ddd
Indicates the description of the action that the recovery routine is taking.
If the recovery routine attempts to continue processing, the description is RETRY IS
BEING ATTEMPTED.
If the abend occurred during a call to the user print exit, no more calls are made to
the print exit.
If the recovery routine does not attempt to continue, the description is ALLOWING
ABEND TO PROCEED, and the task abends.

Action:
Perform the following actions:
■ Check your exit for errors if the abend occurred in the user print exit (WIP=M7EX).
■ If the problem persists, contact CA Support at ca.com/support for assistance.

498 Message Reference Guide

 CAL2 Messages

CAL2T025E

Bad return from TCP/IP interface. RC=rrrrrrrr CC=cccccccc R15=xxxxxxxx WIP=wwww

Reason:
Program CAL2X2T0 received a bad return code from a TCP/IP program. The return code
is rrrrrrrr, the condition code (error number) is cccccccc, and R15 is xxxxxxxx. The
program where-in-place indicator is wwww.

Action:
Contact your installation specialist for assistance.

CAL2T026E

Unable to load module xxxxxxxx. RC=rrrr.

Reason:
Program CAL2X2T0 encountered an error when attempting to load module xxxxxxxx.
The return code from the LOAD call is rrrr.

Action:
Perform the following actions:
■ Check the STEPLIB DD statement in the JCL and environment.
■ Verify that the CA Workload Automation SE load library (CAL2LOAD) is in the
concatenation.

CAL2T027I

Func=ffff RC=rrrr CC=cccc WIP=wwww: [ddd...ddd]

Reason:
This trace message indicates the completion of a specific TCP/IP call. The function,
return code, and condition code of the call to TCP/IP are indicated by ffff, rrrr, and cccc.
www is a where-in-program indicator. If the function is a SEND, RECV, or RCMP, the first
60 characters of the data are listed in ddd...ddd.

Action:
None.

Chapter 2: AFM - CA7R Messages 499

CAL2 Messages

CAL2T028I

Session INIT sent to port/address

Reason:
This trace message indicates that a session initialization record was sent to CA Workload
Automation SE at TCP/IP address listed at address with a 5-digit port number of port.

Action:
None.

CAL2T029E

CA 7 XTM not responding: port/address

Reason:
The CA Workload Automation SE TCP/IP facility is not responding to calls from the CA
Workload Automation SE TCP/IP interface. The CA Workload Automation SE TCP/IP
address and 5-digit port numbers are listed.

Action:
Perform the following actions:
■ Verify that the CA Workload Automation SE address space is active.
■ If so, check the CA Workload Automation SE JES log for CAL2Txxxx messages to see
whether the TCP/IP terminal interface encountered any errors.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2T030E

Invalid record received. WIP=wwww Rec = rrr…rrr

Reason:
The CA Workload Automation SE TCP/IP Terminal facility returned an invalid record to
the CA Workload Automation SE TCP/IP interface. The program where-in-place indicator
is wwww.The first 24 characters of the record are listed (rrr…rrr).

Action:
For assistance, contact CA Support at ca.com/support.

500 Message Reference Guide

 CAL2 Messages

CAL2T031W

INIT response from CA 7 assumed lost. Attempting to continue based on TAP/R.

Reason:
TCP/IP received a TAP or TAP response from CA Workload Automation SE while waiting
for an INIT response. TCP/IP assumes initialization is complete if it has a valid SCTNAME
and continues.

Action:
None.

CAL2T032E

INIT response from CA 7 assumed lost. Session being terminated.

Reason:
TCP/IP received a TAP or TAP response from CA Workload Automation SE while waiting
for an INIT response. TCP/IP cannot find a valid SCTNAME and cannot continue. The
session terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2T033E

Unexpected rec received. Expected xxxxxxxx. Received yyyyyyyy (zzzz).

Reason:
The CA Workload Automation SE TCP/IP Terminal facility returned an unexpected record
to the CA Workload Automation SE TCP/IP interface. The interface expected xxxxxxxx
but received yyyyyyyy (record code zzzz).

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 501

CAL2 Messages

CAL2T034E

XTM INIT failed. RC=rr. Text=ttt...ttt

Reason:
The CA Workload Automation SE TCP/IP Terminal facility returned an error when the CA
Workload Automation SE TCP/IP interface attempted to initialize a session. The return
code (rr) from CA Workload Automation SE is specified with any message sent from CA
Workload Automation SE (ttt...ttt).

Action:
Perform the following actions:
■ See the information supplied in the message.
■ Take any appropriate corrective measures.
■ Check the CA Workload Automation SE JES log for CAL2Txxxx messages to see
whether the TCP/IP terminal interface encountered any errors.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2T035E

Buffer size from CA 7 is invalid

Reason:
The CA Workload Automation SE TCP/IP interface module CAL2X2T0 received an INIT
response record from CA Workload Automation SE that contained an invalid buffer size.
Processing terminates.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2T036E

Invalid batch command: ccc...ccc

Reason:
The CA Workload Automation SE TCP/IP interface was passed a CA Workload
Automation SE command that is valid only in an online CA Workload Automation SE
session. The invalid batch command is listed (ccc...ccc). The command is not sent to CA
Workload Automation SE. Processing continues with the next command.

Action:
None.

502 Message Reference Guide

 CAL2 Messages

CAL2T037I

Data close sent. (EOD)

Reason:
This trace message indicates that a data close record was sent to CA Workload
Automation SE indicating the end of data on command input. If end of data has been
reached on command input, the message displays (EOD).

Action:
None.

CAL2T038I

Data close received

Reason:
This trace message indicates that a data close record was received from CA Workload
Automation SE indicating the end of data on command input.

Action:
None.

CAL2T039I

Session end sent

Reason:
This trace message indicates that a session end record was sent to CA Workload
Automation SE.

Action:
None.

Chapter 2: AFM - CA7R Messages 503

CAL2 Messages

CAL2T040E

Invalid SCT. Expected xxxxxxxx. Received yyyyyyyy.

Reason:
The CA Workload Automation SE TCP/IP interface received a TAP response record that
contained an unexpected SCT name. The expected SCT is xxxxxxxx. The received SCT is
yyyyyyyy.

Action:
For assistance, contact CA Support at ca.com/support.

CAL2T041I

TAP sent

Reason:
This trace message indicates that a TAP record was sent to CA Workload Automation SE.

Action:
None.

CAL2T042E

Mismatch. Instance specified is not using port number specified.

Reason:
The CA Workload Automation SE instance contacted by the port number specified is not
the same instance that is specified in the parameter list or interface.

Action:
Either correct the port number or change the instance name and resubmit or execute
the interface.

CAL2T049I

Unable to activate CTITRACE.

Reason:
The CAICCI and TCP/IP terminal trace data set could not be opened. CA Workload
Automation SE continues but does not write trace data to the CTITRACE data set.

Action:
Contact your installation specialist for assistance.

504 Message Reference Guide

 CAL2 Messages

CAL2T050I

TCP/IP host name is hostname

Reason:
The name of the TCP/IP host is hostname.

Action:
None.

CAL2T051I

TCP/IP host addr is address

Reason:
The address of the TCP/IP host is address. Addresses can be in either IPv4 format n.n.n.n
or IPv6 format x:x:x:x:x:x:x:x, where n is a decimal number from 0 through 255 and x is a
hexadecimal number from 0 through FFFF. Leading zeros can be displayed for both. The
short form of an IPv6 address using a double colon (::) can be used.

Action:
None.

CAL2T052I

TCP/IP terminal interface is terminating

Reason:
The TCP/IP terminal interface is terminating.

Action:
None.

Chapter 2: AFM - CA7R Messages 505

CAL2 Messages

CAL2T053E

TCP/IP terminal interface failed to initialize

Reason:
The TCP/IP terminal interface did not initialize completely.

Action:
Ensure TCP/IP is operational.
■ If it is not, start TCP/IP, and then issue the CA Workload Automation SE /OPEN
command to start the TCP/IP terminal interface.
Note: For command format, see the Systems Programming Guide.
■ If TCP/IP is operational, examine the CA Workload Automation SE online log for any
CAL2TxxxE messages, and take appropriate action for those messages.

CAL2T054E

TCP/IP has stopped. TCP/IP terminal interface is terminating.

Reason:
TCP/IP terminated unexpectedly. CA Workload Automation SE continues, but the TCP/IP
interface is not available.

Action:
Check the system log for any TCP/IP-related messages. For assistance, contact CA
Support at ca.com/support.

CAL2T055E

xxxxxx function failed. RC=rrrrrrrr CC=cccccccc. TCP/IP terminal interface is

terminating.

Reason:
The xxxxxx TCP/IP operation failed. The return code is rrrrrrrr, and the condition code
(error number) is cccccccc. CA Workload Automation SE continues, but the TCP/IP
interface is not available.

Action:
Contact your installation specialist for assistance.

506 Message Reference Guide

 CAL2 Messages

CAL2T056I

Session aaaaaaaa (ssssssss) identifier

Reason:
A TCP/IP terminal session performed action aaaaaaaa. The SCT name of the session is
ssssssss. The unique session identifier is shown.

Action:
None.

CAL2T057E

xxxxxx function failed. RC=rrrrrrrr CC=cccccccc R15=xxxxxxxx

Reason:
The xxxxxx TCP/IP operation failed. The return code is rrrrrrrr, the condition code (error
number) is cccccccc, and R15 is xxxxxxxx.

Action:
Contact your installation specialist for assistance.

CAL2T058E

Error closing session. RC=rrrrrrrr CC=cccccccc. TCP/IP terminal interface continuing.

Reason:
A TCP/IP session failed to close properly. The return code is rrrrrrrr, and the condition
code (error number) is cccccccc. TCP/IP processing continues.

Action:
Contact your installation specialist for assistance.

CAL2T060W

Variable varname could not be retrieved--code xx

Reason:
REXX could not retrieve the named variable. The REXX error code is shown as xx.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 507

CAL2 Messages

CAL2T061E

Unable to access CA 7 module CAL2X2T0

Reason:
The named variable could not be accessed. TCP/IP functions cannot occur.

Action:
Verify that the module is in a STEPLIB or SYSEXEC concatenation library.

CAL2T062E

CA 7 command string is missing

Reason:
No command string was found.

Action:
Consider the following actions:
■ Reenter the command and pass a command string.
Note: If you are using a semicolon for a command delimiter in a TSO/E
environment, it can conflict with the TSO delimiter.
■ Change the command delimiter in either the REXX EXEC (TSO/E environment) or
&prefix_DEBUG global value (GSS environment).

CAL2T065I

TCP/IP port number is nnnnn

Reason:
The number of the TCP/IP interface port is nnnnn.

Action:
None.

508 Message Reference Guide

 CAL2 Messages

CAL2T066W

No terminal available for session

Reason:
A TCP/IP session was attempted, but no terminal was available to handle the session.
The session was terminated.

Action:
If this message happens occasionally, no action may be required. However, if it happens
frequently, it is a sign that insufficient CCI terminals are defined. Define one or more
additional CCI terminals in the initialization file. Each CCI TERMINAL statement requires
a corresponding CCI LINE and CCI GROUP statement.

CAL2T070E

TCP/IP send error. Socket=nnnnn, RC=rrrrrrrr CC=cccccccc R15=xxxxxxxx ECB=yyyyyyyy

WIP=w

Reason:
An error occurred in program SASSTCP1 during a SEND operation to a TCP/IP terminal
client. The socket number is nnnnn, the return code is rrrrrrrr, the condition code (error
number) is cccccccc, and R15 is xxxxxxxx. The contents of the ECB are yyyyyyyy. The
program where-in-place indicator is w.

Action:
Contact your installation specialist for assistance.

CAL2T071E

CA 7 is shutting down; SEND aborted.

Reason:
A TCP/IP send operation to a terminal client was not performed because CA Workload
Automation SE was shutting down.

Action:
Check the output of the batch TCP/IP process to determine whether to rerun it after CA
Workload Automation SE comes back up.

Chapter 2: AFM - CA7R Messages 509

CAL2 Messages

CAL2T072E

No XTTA for the XTMB

Reason:
A TCP/IP send operation was not performed because of a control block mismatch.

Action:
Contact your installation specialist for assistance.

CAL2T073E

No buffer addr supplied in XTM

Reason:
Building a buffer is required before a TCP/IP SEND is performed. In this case, no buffer
address is available. The request is rejected.

Action:
Check the output of the batch TCP/IP process to determine whether to rerun it.

CAL2T074E

No buffer length supplied in XTM

Reason:
Building a buffer is required before a TCP/IP SEND is performed. In this case, the buffer
length is zero. The request is rejected.

Action:
Check the output of the batch TCP/IP process to determine whether to rerun it.

CAL2T075E

Buffer length error

Reason:
Building a buffer is required before a TCP/IP SEND is performed. In this case, the buffer
length is incorrect. The request is rejected.

Action:
Check the output of the batch TCP/IP process to determine whether to rerun it.

510 Message Reference Guide

 CAL2 Messages

CAL2T076E

Data length exceeds buffer capacity

Reason:
Building a buffer is required before a TCP/IP SEND is performed. In this case, the buffer
was not large enough to contain the transaction data. The request is rejected.

Action:
Check the output of the batch TCP/IP process to determine whether to rerun it.

CAL2U900I

Status of CA7LOG ENF Event is xxxxxxxx

Reason:
The CAL2LOGU utility reports the status of the CA7LOG ENF EVENT as the following:
■ A status of RECORD indicates CA7LOG events have been written to the ENF
database.
■ A status of ACTIVE indicates these events are only reported by CAL2LOGU when
they occur while CAL2LOGU is running.

Action:
None.

CAL2U901E

Invalid status for CA7LOG ENF Event (xxxxxxxx). Process aborted.

Reason:
CAL2LOGU reports a negative status for CA7LOG ENF Events.

Action:
Verify that CA7LOG events have been added to the CAIENF database.

Chapter 2: AFM - CA7R Messages 511

CAL2 Messages

CAL2U903E

Invalid parameter starting with (parm). Process aborted.

Reason:
A parameter for CAL2LOGU utility was improperly specified.

Action:
Correct the listed parameter.

CAL2U904I

Parmlist format is 'Instance,Start-Date/Time (yyyydddhhmmssth)'

Reason:
CAL2LOGU utility information message follows a reported error.

Action:
None.

CAL2U905I

All parms are optional. Partial start Date/Time can be specified (e.g. yyyyddd)

Reason:
CAL2LOGU utility information message follows a reported error.

Action:
None.

CAL2U906E

PRINT DD is invalid or unavailable. Process aborted.

Reason:
Required SYSOUT file not found.

Action:
Correct JCL error.

512 Message Reference Guide

 CAL2 Messages

CAL2U907I

Status of CABMSSTA ENF Event is xxxxxxxx

Reason:
The CABMSSTA utility reports the status of the CABMSSTA ENF EVENT as the following:
■ A status of RECORD indicates CABMSSTA events are written to the CAIENF
database.
■ A status of ACTIVE indicates these events are only reported by CAL2CPMU when
they occur while CAL2CPMU is running.

Action:
None.

CAL2U908E

Invalid status for CABMSSTA ENF Event (xxxxxxxx). Process aborted.

Reason:
CAL2CPMU reports a negative status for CABMSSTA ENF Events.

Action:
Verify that CABMSSTA events have been added to the CAIENF database.

CAL2U909E

ENF CALL FAILED : FUNC= .... RC= ..

Reason:
CAIENF, the CA Event Notification Facility, set a nonzero return code.

Action:
Perform the following actions:
■ Verify that CA7LOG events have been added to the CAIENF database.
■ Verify that CAIENF was initialized.

Chapter 2: AFM - CA7R Messages 513

CAL2 Messages

CAL2V001I

Add successfully completed.

Reason:
The requested add function processed without error.

Action:
None.

CAL2V002I

Update successfully completed.

Reason:
The requested update function processed without error.

Action:
None.

CAL2V003I

Delete successfully completed.

Reason:
The requested delete function processed without error.

Action:
None.

CAL2V004I

Rename successfully completed.

Reason:
The requested rename function processed without error.

Action:
None.

514 Message Reference Guide

 CAL2 Messages

CAL2V005I

Enter Schid and Jobname or Network.

Reason:
Too few parameters were specified to perform the current function.

Action:
Specify either a job name and schedule ID (Schid) or a network name and schedule ID
(Schid).

CAL2V006I

Generic or specific Jobname required.

Action:
This message is issued from the List Job panel (PL2GLJOB) when no job ame parameter
has been specified.

Action:
To generate a List Job transaction you must specify some kind of job name parameter.
This can be fully generic (%), partially generic (ABC%), or a specific job name.

CAL2V007I

All tasks processed. None remain for specified criteria.

Reason:
This message is issued from the QM - Output Networks panel when all tasks for the
specified criteria have been posted or canceled.

Action:
None.

CAL2V100E

INVALID VALUE FOR VARIABLE LENGTH

Reason:
A global variable appears to have zero length and cannot be processed.

Action:
Correct the variable.

Chapter 2: AFM - CA7R Messages 515

CAL2 Messages

CAL2V701W

CA7APPL= VARIABLE NOT FOUND. DEFAULT USED.

Reason:
The keyword variable CA7APPL was not found in the CACCENV member of the API
PROFILE data set. The CA Workload Automation SE API attempts to use the default value
(CA7).

Action:
Check the parameters in your API PROFILE data set, member CACCENV. Ensure that the
CA7APPL= keyword specifies the correct VTAM APPLid for the CA Workload Automation
SE you want to communicate with.

CAL2V702W

CA7SESS= VARIABLE NOT FOUND. DEFAULT USED.

Reason:
The keyword variable CA7SESS was not found in the CACCENV member of the API
PROFILE data set. The CA Workload Automation SE API attempts to use the default value
(CA70010).

Action:
Check the parameters in your API PROFILE data set, member CACCENV. Ensure that the
CA7SESS= keyword specifies the high number of the range of ACBs to be used by the
API. If no special ACBs have been defined for the API you may be able to specify
TSO0999 and use ACBs generated for TSO.

CAL2V703W

SECURITY CHECK FAILED FOR CA7USER= VALUE. ALTERNATE USERID IGNORED.

Reason:
The keyword variable CA7USER was found in the CACCENV member of the API PROFILE
data set. External security has denied use of this ID to the owner of the API session.

Action:
The CA7USER parameter is ignored and an attempt is made to sign on to CA Workload
Automation SE using the API owner ID.

516 Message Reference Guide

 CAL2 Messages

CAL2V704E

WFDSN= Variable invalid. Workflow Save not enabled.

Reason:
Program L2L10080 was unable to save the checkpoint file as a result of a SAVE request.
The Jobflow Illustrator variable WFDSM, in the CACCENV member of the Schedule
Server task PROFILE data set, is incorrect.

Note: The correct syntax for the variable is described in the Jobflow Illustrator
Microsoft Visio Option Guide.

Action:
Perform the following actions:
■ Correct the Jobflow Illustrator variable WFDSN in the CACCENV member of the
PROFILE data set.
■ Resubmit the request.

CAL2V705E

WFALLOC= Variable invalid. Workflow Save not enabled.

Reason:
Program L2L10080 was unable to save the checkpoint file as a result of a SAVE request.
The Jobflow Illustrator variable WFALLOC, in the CACCENV member of the Schedule
Server task PROFILE data set, is incorrect.

Note: The correct syntax for the variable is described in the Jobflow Illustrator
Microsoft Visio Option Guide.

Action:
Perform the following actions:
■ Correct the Jobflow Illustrator variable WFALLOC in the CACCENV member of the
PROFILE data set.
■ Resubmit the request.

Chapter 2: AFM - CA7R Messages 517

CAL2 Messages

CAL2V706E

WFSPACE= Variable invalid. Workflow Save not enabled.

Reason:
Program L2L10080 was unable to save the checkpoint file as a result of a SAVE request.
The Jobflow Illustrator variable WFSPACE, in the CACCENV member of the Schedule
Server task PROFILE data set, is incorrect.

Note: The correct syntax for the variable is described in the Jobflow Illustrator
Microsoft Visio Option Guide.

Action:
Perform the following actions:
■ Correct the Jobflow Illustrator variable WFSPACE in the CACCENV member of the
PROFILE data set.
■ Resubmit the request.

CAL2W100I

CA-7 IBM WLM RESOURCE SET TO sss. RES=rrr...rrr

Reason:
The IBM Workload Management resource associated with CA Workload Automation SE
(rrr...rrr) has been set to the state indicated by sss (either ON or OFF).

Action:
None.

CAL2W101E

CA-7 IBM WLM RES SET sss ERR. RES=rrr...rrr RC=xxxx CC=cccc/cccc
...error text...

Reason:
An error was encountered attempting to set the state (sss) of the IBM Workload
Management resource associated with CA Workload Automation SE (rrr...rrr). The
return code (xxxx) and condition code (cccc/cccc) returned from the call to set the state
are indicated. A short text message may also indicate the nature of the error.

Action:
Confirm that the resource name for CA Workload Automation SE is spelled correctly.
Confirm that IBM WLM is active and that the resource name specified for CA Workload
Automation SE is defined in the active WLM policy.

518 Message Reference Guide

 CAL2 Messages

CAL2W102W

LOAD FAILED FOR MODULE mmmmmmmm. RC=xxxx

Reason:
An error was encountered attempting to load a CA Workload Automation SE module.
The return code (xxxx) from the load call is indicated.

Action:
Confirm that the CA Workload Automation SE load library is accessible through STEPLIB
or LINKLIST. Confirm that sufficient REGION size is available.

CAL2W103W

VRM IN MAINT MODE. WLM SCHENV= PROCESSING DISABLED.

Reason:
The CA Workload Automation SE initialization options specified that IBM WLM
scheduling environment insertion should be performed by CA Workload Automation SE.
However, VRM must be active to support this feature (DBASE,RSRC=YES). The CA
Workload Automation SE scheduling environment feature is disabled.

Action:
Specify RSRC=YES on the DBASE statement in the product's initialization file if you want
to engage CA Workload Automation SE scheduling environment insertion.

CAL2W110I

ICOM IBM WLM RESOURCE SET TO sss. RES=rrr...rrr

Reason:
The IBM Workload Management resource associated with ICOM (rrr...rrr) has been set
to the state indicated by sss (either ON or OFF).

Action:
None.

Chapter 2: AFM - CA7R Messages 519

CAL2 Messages

CAL2W111E

ICOM IBM WLM RES SET sss ERR. RES=rrr...rrr RC=xxxx CC=cccc/cccc
...error text...

Reason:
An error was encountered attempting to set the state (sss) of the IBM Workload
Management resource associated with ICOM (rrr...rrr). The return code (xxxx) and
condition code (cccc/cccc) returned from the call to set the state are indicated. A short
text message may also indicate the nature of the error.

Action:
Confirm that the resource name for ICOM is spelled correctly. Confirm that IBM WLM is
active and that the resource name specified for ICOM is defined in the active WLM
policy.

CAL2XCFM1

ENTERED SASSXCFM. SVT R12=xxxxxxxx MSGLEN=llllllll

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message is issued
upon entry to CA Workload Automation SE XCF message exit module SASSXCFM. The
address of UCC7SVT is in R12, and the length of the message received is llllllll.

Action:
None.

CAL2XCFM2

MSG= eeeeee tttt llllllll dddddddd

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message describes an
XCF message that was received. The eyecatcher is eeeeee, the type is tttt, the message
length is llllllll, and data is in the field dddddddd.

Action:
None.

520 Message Reference Guide

 CAL2 Messages

CAL2XCFM3

ECB ADDR= xxxxxxxx CONTENTS= cccccccc

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An ECB at address
xxxxxxxx has contents cccccccc.

Action:
None.

CAL2XCFM4

xxxxxxxxxx MESSAGE Xnnnn

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An XCF type xxxxxxxxxx
message was received. The message number of this type of message is nnnn.

Action:
None.

CAL2XCFM5

POSTED nnnnnnnn[-cc] VALUE=xxxxxxxx SECS=ssssssss

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An ECB with name
nnnnnnnn was posted with condition code cc. The contents of the ECB is xxxxxxxx.
Timestamped seconds and fraction are shown by ssssssss.

Action:
None.

Chapter 2: AFM - CA7R Messages 521

CAL2 Messages

CAL2XCF01

FC=xxxx EPSW=eeeeeeee PSW=pppppppp SECS=xxxxxxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message is issued
upon entry to CA Workload Automation SE XCF message exit module SASSXCF0. The
function code to be performed is xxxx, the PSW at entry is eeeeeeee, and the current
PSW is pppppppp. Timestamped seconds and fraction are shown by ssssssss.

Action:
None.

CAL2XCF02

IXCMSGO R15=nnnn R0=nnnn MSGTYPE=xxxx MSGLEN=llll TOKN=tttttttt tttttttt

BFN=bbbbbbbb

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. An XCF message was sent.
The return and reason codes were returned in registers 15 and 0. The message type
code is xxxx. The message length is llll, and the token of the group member receiving the
message is tttttttt tttttttt. BFN shows some data in the message.

Action:
None.

CAL2XCF03

GOODECB=xxxxxxxx BADECB=yyyyyyyy MSGOFLGS=zzzzzzzz

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. If the message sent in
Message CAL2XCF02 was received within the expected time, GOODECB is posted. If not,
BADECB is posted. For a description of MSGOFLGS, see MNPLMSGOFLAGS in IBM macro
IXCYMNPL.

Action:
None.

522 Message Reference Guide

 CAL2 Messages

CAL2XCF04

SEND ERROR GMFL=xxxxxxxx WIP y

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. A message failed to send
properly. Flags in the XCF group member are shown as xxxxxxxx. The location in
program SASSXCF0 is designated by y.

Action:
None.

CAL2XCF05

SEND GNAM xxxxxxxx MNAM xxxxxxxx TOKN xxxxxxxx MESG xxxxxxxx

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The addresses of the
following are displayed: group name, member name, token, and message.

Action:
None.

CAL2XC01I

XCFDS on xxxxxx ddd

Reason:
This informational message is produced each time ICOM is started if XCF is elected. The
message tells where the XCF data set is located. Issued by SASSINXD.
xxxxxx
Specifies the disk volume on which the data set resides.
ddd
Specifies SHR if the unit is SYSGENed as SHR. Otherwise, it is blanks.

Action:
None.

Chapter 2: AFM - CA7R Messages 523

CAL2 Messages

CAL2XC02E

XCF IXCMSGI FAILED. R15=nnnn R0=nnnn.

Reason:
The ICOM XCF message exit tried to retrieve an XCF message and failed. R15 contains
the return code, and R0 contains the reason code. Issued by SASSIXCM.

Action:
Perform the following actions:
■ Research the return and reason codes for the IXCMSGI macro in the IBM manual
MVS Programming: Sysplex Services Reference.
■ Contact either your local systems programmer or your installation specialist for
assistance.

CAL2XC03I

CA 7 WILL NOT USE XCF

Reason:
The use of XCF was not specified. Issued by SASSLINK.

Action:
None.

CAL2XC04E

SYSPRINT FAILED TO OPEN

Reason:
SASSXDSI attempted to open the SYSPRINT data set and was unsuccessful.

Action:
Perform the following actions:
■ Ensure that the JCL contains a SYSPRINT DD statement.
■ Resubmit the job.

524 Message Reference Guide

 CAL2 Messages

CAL2XC05E

ERROR INITIALIZING XCF CONTROL BLOCKS. USING COMMDS. INXD RC=nnnn

Reason:
SASSICMX attempted to initialize control blocks used by ICOM for XCF processing and
was unsuccessful. ICOM continues to process using the COMMDS data set. The return
code from SASSINXD was nnnn.

Action:
Contact your installation specialist for assistance.

CAL2XC06E

EXCESSIVE xxxxx ERRORS ON XCF DATA SET. SWITCHING TO COMMDS.

Reason:
SASSICMX is performing I/O to the XCF data set and is getting either READ or WRITE
errors, as designated by xxxxx. The number of errors is sufficient to stop using XCF and
to switch to using COMMDS to communicate with CA Workload Automation SE. ICOM
continues to process.

Action:
Perform the following actions:
■ Examine the job log for any I/O errors.
■ Contact your installation's systems programmer or CA Workload Automation SE
specialist for assistance, as appropriate.

CAL2XC07E

SYSPRINT FAILED TO OPEN

Reason:
SASSXKPI attempted to open the SYSPRINT data set and was unsuccessful.

Action:
Perform the following actions:
■ Ensure there is a SYSPRINT DD statement in the JCL.
■ Resubmit the job.

Chapter 2: AFM - CA7R Messages 525

CAL2 Messages

CAL2XC08E

XCF XCFMSGI FAILED. R15=nnnn R0=nnnn.

Reason:
The CA Workload Automation SE XCF message exit tried to retrieve an XCF message and
failed. R15 contains the return code, and R0 contains the reason code. Issued by
SASSXCFM.

Action:
Perform the following actions:
■ Research the return and reason codes for the IXCMSGI macro in the IBM manual
MVS Programming: Sysplex Services Reference.
■ Contact either your local systems programmer or your installation specialist for
assistance.

CAL2XC09E

XCF MESSAGE RECEIVED IN INCORRECT FORMAT

Reason:
The CA Workload Automation SE XCF message exit received a message that it could not
process because the message was not formatted properly. Issued by SASSXCFM.

Action:
Contact your installation specialist for assistance.

526 Message Reference Guide

 CAL2 Messages

CAL2XC10E

CANNOT CONTACT CA 7 VIA XCF. TRACKING DATA IS QUEUEING UP. WAITING xxxx
MINUTES. WIP n.

Reason:
The use of XCF was specified, but ICOM could not contact CA Workload Automation SE
through XCF. WIP stands for "where in place" in the ICOM program the WTO is issued.
The following values for WIP give further explanation:
1
Indicates the SMF tracking data is being written to the XCF data set and continues
until the data set is full.
2
Indicates the data is being buffered in CSA, and the message is reissued every
minute.
3
Indicates ICOM has lost communication with CA Workload Automation SE. The
message is issued once a minute for two minutes. If, by the end of that time, ICOM
still cannot communicate with CA Workload Automation SE, ICOM turns off the use
of XCF to communicate with CA Workload Automation SE.
4
Indicates ICOM has determined that CA Workload Automation SE has just joined
the XCF group, but CA Workload Automation SE is not communicating properly with
ICOM. The message is issued once a minute for two minutes. If, by the end of that
time, ICOM still cannot communicate properly with CA Workload Automation SE,
ICOM turns off the use of XCF to communicate with CA Workload Automation SE.

Action:
Determine the cause of the message. Usually, CA Workload Automation SE is not active
or was not started specifying the use of XCF. If necessary, contact either your local
systems programmer or your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 527

CAL2 Messages

CAL2XC11I

XCF RECOVERY IN PROGRESS. ATTEMPTING TO JOIN GROUP xxxxxxxx.

Reason:
ICOM has determined that it is not a member of XCF group xxxxxxxx and is attempting
to rejoin the group. If the join is successful, ICOM continues. If the join is unsuccessful,
Message CAL2XC12E is issued.

Action:
None.

CAL2XC12E

XCF GROUP JOIN FAILED

Reason:
ICOM was not able to rejoin the XCF group listed in Message CAL2XC11I.

Action:
Contact your installation specialist for assistance.

CAL2XC13I

CROSS-SYSTEM COUPLING FACILITY (XCF) SUBTASK IS ACTIVE

Reason:
The cross-system coupling facility (XCF) subtask, program SASSXMGR, has started.

Action:
None.

528 Message Reference Guide

 CAL2 Messages

CAL2XC14E

XCFCKPT MISSING OR INVALID

Reason:
ither the XCFCKPT DD is missing or program SASSINXD could not build the XCFCKPT
control block or open the XCFCKPT data set. This message is followed by CAL2XC20E.
Issued by SASSLINK.

Action:
Add the XCFCKPT DD statement if it is missing from the JCL. Otherwise, contact your
installation specialist for assistance. Ensure that the XCFCKPT data set is properly
formatted before using it. If necessary, use initialization job CA07N707.

CAL2XC15E

I/O ERROR ON XCFCKPT DATA SET. WIP x.

Reason:
SASSXMGR sustained an I/O error reading from or writing to the XCFCKPT data set. The
following values for WIP give further explanation:
1
Indicates a read failed for relative block 0, which is the SMF block. XCF is turned off,
and the COMMDS is used for SMF records.
2
Indicates a write failed for relative block 0. A sporadic instance may not be a
problem. However, if it happens frequently, or if CA Workload Automation SE
crashes before a good write occurs, a problem with SMF extract records being lost
during recovery may occur when CA Workload Automation SE restarts.
3
Indicates a write failed for relative block 0. An online command was issued to delete
one or more records in the XCFCKPT data set, and the delete operation failed.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 529

CAL2 Messages

CAL2XC16I

XCF SUBTASK HAS RECEIVED A STOP COMMAND

Reason:
The cross-system coupling facility (XCF) subtask, program SASSXMGR, has received a
request to terminate. CA Workload Automation SE is probably shutting down.

Action:
None.

CAL2XC17E

NO SMF BUFFER POINTER TABLE. TURNING OFF USE OF XCF.

Reason:
Program SASSXCFM did not find the SMF buffer pointer table. XCF is turned off, and the
COMMDS is used for SMF records.

Action:
Contact your installation specialist for assistance.

CAL2XC18I

CA 7 JOINED XCF GROUP xxxxxxxx AS MEMBER yyyyyyyyyyyy

Reason:
CA Workload Automation SE has successfully joined the XCF group named xxxxxxxx. The
CA Workload Automation SE member name is yyyyyyyyyyyy. If this message follows
Message CAL2XC35E, ignore Message CAL2XC18I (see message CAL2XC35E). Issued by
SASSLINK.

Action:
None.

530 Message Reference Guide

 CAL2 Messages

CAL2XC19E

CA 7 FAILED TO JOIN XCF GROUP xxxxxxxx

Reason:
CA Workload Automation SE attempted to join XCF group xxxxxxxx but was
unsuccessful. This message is followed by Message CAL2XC20E. Issued by SASSLINK.

Action:
Contact your installation specialist for assistance.

CAL2XC20E

CA 7 CAN NOT USE XCF

Reason:
An error occurred that prevents the use of the cross-system coupling facility. Issued by
SASSLINK.

Action:
Perform the following actions:
■ Check the system log for any other messages that might relate to this error.
■ Contact your installation specialist for assistance.

CAL2XC21I

ICOM JOINED XCF GROUP xxxxxxxx AS MEMBER yyyyyyyyyyyy [**NOTIFY ONLY**]

Reason:
ICOM has successfully joined the XCF group named xxxxxxxx. The ICOM member name is
yyyyyyyyyyyy. If initialization parameter XCF=NOTIFY was specified, **NOTIFY ONLY** is
displayed to verify that XCF is used only to notify CA Workload Automation SE that SMF
data has been written to the COMMDS.

Action:
None.

Chapter 2: AFM - CA7R Messages 531

CAL2 Messages

CAL2XC22E

ICOM FAILED TO JOIN XCF GROUP xxxxxxxx

Reason:
ICOM attempted to join the listed XCF group but was unsuccessful. Program SASSICMI
ends with a U0008 abend.

Action:
Contact your installation specialist for assistance.

CAL2XC23E

XCF DATA SET FAILED TO OPEN

Reason:
SASSICMI attempted to open the XCF data set and was unsuccessful.

Action:
Ensure that an XCFDS DD statement is in the ICOM JCL and that it points to an XCF data
set. If it does, contact your installation specialist for assistance.

CAL2XC24E

NO SPACE FOR XCF DATA SET CONTROL BLOCKS

Reason:
SASSICMI attempted to build internal control blocks for the XCF data set but was
unsuccessful.

Action:
Perform the following actions:
■ Increase the region for the job or job step.
■ Resubmit the job.

532 Message Reference Guide

 CAL2 Messages

CAL2XC25W

WARNING! COUPLING FACILITY NO LONGER SUPPORTED. CHANGE ICOM PARAMETER

LIST. PARM IGNORED.

Reason:
Starting with r11.3, the ICOM coupling facility is no longer supported. This message was
issued because SASSICMI detected the character in the ICOM parameter list that tells
ICOM to use the coupling facility. ICOM continues to initialize, ignoring the now
superfluous character.

Action:
Remove the ICOM coupling facility character in the parameter list before the next time
the job is submitted.

CAL2XC26W

ONLY SMFXCF=NO IS VALID FOR BATCH. IGNORED.

Reason:
When CA Workload Automation SE is started in batch, the only valid SMFXCF keyword
on an SMF initialization file statement is SMFXCF=NO. The keyword is ignored. Issued by
SASSISMF.

Action:
Remove the SMFXCF keyword or the entire SMF statement from your batch initialization
file.

CAL2XC27E

BAD LOAD OF XCF MODULE

Reason:
SASSLINK attempted to load the XCF support modules. One or more modules failed to
load. This message is followed by Message CAL2XC20E.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 533

CAL2 Messages

CAL2XC28E

SASSIXCM MESSAGE EXIT ERROR

Reason:
ICOM XCF message exit SASSIXCM encountered an error. An SVC dump accompanies
this message the first time it occurs.

Action:
Contact your installation specialist for assistance.

CAL2XC29E

SASSXCFM MESSAGE EXIT ERROR

Reason:
CA Workload Automation SE XCF message exit SASSXCFM encountered an error. An SVC
dump accompanies this message the first time it occurs.

Action:
Contact your installation specialist for assistance.

CAL2XC30E

POST ERRET EXIT. R15=nnnnnnnn

Reason:
CA Workload Automation SE XCF message exit SASSXCFM attempted to post an ECB and
encountered an error. The return code is posted in R15.

Action:
Contact your installation specialist for assistance.

534 Message Reference Guide

 CAL2 Messages

CAL2XC31E

XCFGRP PARM REQUIRES XCF PARM

Reason:
The ICOM XCFGRP parameter requires that you code the XCF parameter. This message
is followed by Message CA-7.589 and a U0001 abend.

Action:
Perform the following actions:
■ Correct the parameter list.
■ Resubmit the job.

CAL2XC32E

ANOTHER CA 7 IS ALREADY A MEMBER OF XCF GROUP xxxxxxxx

Reason:
CA Workload Automation SE is attempting to join XCF group xxxxxxxx, but another
instance of CA Workload Automation SE, possibly on another system, is already a
member of that group. Only one instance of CA Workload Automation SE can be a
member of an XCF group. This message is followed by a U0032 abend. Issued by
SASSLINK.

Action:
Perform the following actions:
■ Change the SMFXCF parameter on the SMF initialization statement to specify the
name of an XCF group or a different XCF group.
■ Resubmit the job.

Note: ICOMs for this CA Workload Automation SE must use the same XCF group name
as this CA Workload Automation SE.

Chapter 2: AFM - CA7R Messages 535

CAL2 Messages

CAL2XC33E

SASSXCFG GROUP EXIT ERROR

Reason:
The CA Workload Automation SE XCF group exit SASSXCFG has taken an error. The first
time this happens, an SDUMP is taken.

Action:
Perform the following actions:
■ Contact your installation specialist for assistance.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2XC34E

SASSIXCG GROUP EXIT ERROR

Reason:
The ICOM XCF group exit SASSIXCG has taken an error. The first time this happens, an
SDUMP is taken.

Action:
Perform the following actions:
■ Contact your installation specialist for assistance.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2XC35E

XCFCKPT DATA SET IS NOT FORMATTED. XCF WILL NOT BE USED!

Reason:
The XCF checkpoint data set must be formatted before it can be used. Message
CAL2XC18I, stating that CA Workload Automation SE has joined an XCF group, should be
issued before Message CAL2XC35E, but because of timing issues, is usually issued after.
If Message CAL2XC18I is issued after message CAL2XC35E, ignore Message CAL2XC18I.

Action:
Perform the following actions:
■ Format the XCFCKPT data set with installation job CA07N707.
■ Restart CA Workload Automation SE.

536 Message Reference Guide

 CAL2 Messages

CAL2XC36I

ICOM CONTACTED CA 7 XCF GROUP MEMBER xxxxxxxxxxxx

Reason:
ICOM is in communication with a CA Workload Automation SE that has the XCF group
member name of xxxxxxxxxxxx. Issued by SASSIXC0 at ICOM initialization or SASSIXCG if
CA Workload Automation SE joins the XCF group after ICOM is initialized. If the message
is issued by SASSIXCG, the STC or JOB number is not available to be shown in the
message.

Action:
None.

CAL2XC37I

ICOM IS [NOT] USING XCF

Reason:
This message is the response to an XCF=STAT reply to ICOM. The message shows
whether ICOM is using XCF. If ICOM is using XCF, Messages CAL2XC38I and CAL2XC39I
follow. Message CAL2XC40I also follows if CA Workload Automation SE is not a member
of the XCF group.

Action:
None.

CAL2XC38I

XCF GROUP NAME: xxxxxxxx

Reason:
This message is the response to an XCF=STAT reply to ICOM and follows message
CAL2XC37I. xxxxxxxx shows the XCF group name to which ICOM belongs. If any
members are active in the group, they are listed on Message CAL2XC39I, which follows.

Action:
None.

Chapter 2: AFM - CA7R Messages 537

CAL2 Messages

CAL2XC39I

ACTIVE MEMBER NAME: xxxxxxxxxxxx

Reason:
This message is the response to an XCF=STAT reply to ICOM and follows Message
CAL2XC38I. xxxxxxxxxxxx shows the name of an active member of the XCF group. The
message repeats for each active member in the group.

Action:
None.

CAL2XC40I

CA 7 IS NOT A MEMBER OF THE XCF GROUP

Reason:
This message is the response to an XCF=STAT reply to ICOM and follows the last
message CAL2XC39I if CA Workload Automation SE is not a member of the XCF group.

Action:
None.

CAL2XC41I

SYNCHRONIZING WITH CA 7

Reason:
ICOM has established contact with CA Workload Automation SE and is synchronizing
tracking data.

Action:
None.

538 Message Reference Guide

 CAL2 Messages

CAL2XC42E

READ FAILED ON XCF DATA SET RBN 0

Reason:
ICOM tried to read relative block zero of the XCF data set and failed.

Action:
Ensure that the XCF data set was properly formatted.

Consider the following actions:

■ If it is unformatted, run initialization job CA07N707.
■ If it is properly formatted, contact your installation specialist for assistance.

CAL2XC43E

SASSICMX CANNOT LOCATE THE ICMDSECT. TURNING OFF USE OF XCF.

Reason:
Program SASSICMX could not find the ICMDSECT control block for the instance of CA
Workload Automation SE. The use of XCF for communicating with CA Workload
Automation SE is being turned off.

Action:
Contact your installation specialist for assistance.

CAL2XC44E

CA 7 IS NOT PROCESSING SMF BUFFERS. PRBN=xxxx PRBR=yyyy.

Reason:
CA7ONL has stopped processing SMF buffers sent by ICOM. PRBN displays the number
of the last buffer processed. PRBR displays the number of the last buffer received by
CA7ONL. This message is followed by CAL2XC45W.

Action:
See Message CAL2XC45W.

Chapter 2: AFM - CA7R Messages 539

CAL2 Messages

CAL2XC45W

ICOM IS TURNING OFF USE OF XCF; REVERTING TO USE OF COMMDS. CALL SUPPORT.

Reason:
For a reason described in an earlier message, ICOM has stopped using XCF to send SMF
buffers to CA7ONL and switched to COMMDS. The XCFDS and XCFCKPT data sets are
now out of synchronization and action must be taken before XCF can be used again.

Action:
Before using XCF again, perform one of the following procedures:
■ For assistance, contact CA Support at http://ca.com/support.
■ Perform the following actions:
– Shut down ICOM.
– Use job N705 in JCLLIB to reinitialize the XCFDS data set.
– Do one of the following:
■ Issue the online /XCF command for the ICOM that switched to COMMDS.
■ Shut down CA7ONL. Use job N707 in JCLLIB to reinitialize the XCFCKPT data
set.
– Now, you can safely restart ICOM specifying XCF=SMF. If CA7ONL was shut
down, you can restart it and use XCF.

CAL2XMGR1

FECQ=xxxxxxxx 0ECB=xxxxxxxx FECB=xxxxxxxx XECB=xxxxxxxx FEC2=xxxxxxxx WIP=w

SECS=ssssssss

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message gives the
contents of various ECBs. WIP is a where-in-program indicator. Timestamped seconds
and fraction are shown by ssssssss.

Action:
None.

540 Message Reference Guide

 CAL2 Messages

CAL2XMGR2

AT xxxxxxxx R13=xxxxxxxx SECS=ssssssss FLG=ffffffff

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. xxxxxxxx is a
where-in-program indicator for SASSXMGR. Timestamped seconds and fraction are
shown by ssssssss. Additional debugging data is shown in ffffffff.

Action:
None.

CAL2XMGR3

FFCL=xxxxxxxx FPCL=xxxxxxxx FCCL=xxxxxxxx WIP=w SECS=ssssssss

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message gives the
addresses of the first, previous, and current cells on the cell pool chain. WIP is a
where-in-program indicator. Timestamped seconds and fraction are shown by ssssssss.

Action:
None.

CAL2XMGR4

SENT BUFFER xxxx TO SASSSMF0 SECS=ssssssss

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The message indicates
that program SASSXMGR sent SMF buffer number xxxx to program SASSSMF0.
Timestamped seconds and fraction are shown by ssssssss.

Action:
None.

Chapter 2: AFM - CA7R Messages 541

CAL2 Messages

CAL2XMGR5

XCF MESSAGE SEND FAILED R15=xxxxxxxx R0=xxxxxxxx MSGTYPE=xxxx WIP=w

Reason:
This message is issued as part of tracing and debugging CA Workload Automation SE.
The message is only activated when working with CA Support. The send of an XCF
message failed. Return and reason codes are shown in R15 and R0, respectively. WIP is a
where-in-program indicator.

Action:
None.

CAL2X001I

CA-7 Cross-Platform Submit Process Starting - yyyy/ddd hh:mm:ss.th

Reason:
The CA Workload Automation SE Cross-Platform submission process has been initiated.
The starting date (Julian) and time are indicated on the message.

Action:
None.

CAL2X002I

Job jjjjjjj (####) submitted to node nnnnnnnn

Reason:
A CA Workload Automation SE Cross-Platform job request for job jjjjjjj, job number
####, has been sent to CAICCI node nnnnnnnn.

Action:
None.

542 Message Reference Guide

 CAL2 Messages

CAL2X003I

CA-7 Cross-Platform Submit Process Complete - yyyy/ddd hh:mm:ss.th

Reason:
The CA Workload Automation SE Cross-Platform submission process has completed. The
completion date (Julian) and time are indicated on the message.

Action:
If the Cross-Platform request was successfully sent to the target node, the submit step
will complete with a return code of zero. If the request was not sent successfully, the
submission step will abend with a user abend code. If so, see the previous messages for
an indication of the specific error encountered.

CAL2X004W

Warning - CA-7 Cross-Platform Tracker for mmmmmmm is not active on this LPAR.

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) is handling a
cross-platform request; however, there is no High Availability Option (XPHAO=)
specification on the request, and there is no CA Workload Automation SE Cross-Platform
Tracker (XTRK) task for the specified monitor name (mmmmmmmm) active on the LPAR
where this CA7TOUNI batch job is executing.

Note: The job initiation and termination feedback for this cross-platform request is not
returned to the submitting CA Workload Automation SE without a Cross-Platform
Tracker (XTRK) running on the LPAR where the CA7TOUNI job executes.

Action:
Perform the following actions:
■ Confirm that the monitor name specified is correct for the copy of CA Workload
Automation SE that submitted the CA7TOUNI batch job.
■ Check that the CA7TOUNI job should be running on the LPAR where it executed.
■ Check the XTRK started task or CA Workload Automation SE ICOM where XTRK
should be running as a subtask and start XTRK.

If CA7TOUNI ran on the wrong LPAR or ran with the wrong monitor name, perform the
following tasks:
■ Confirm that the cross-platform task ran successfully.
■ Requeue and force-complete the job in the CA Workload Automation SE queues.

Chapter 2: AFM - CA7R Messages 543

CAL2 Messages

CAL2X005W

CAICCI Receiver 'SUBMITC Server' not found at node nnnnnnnnn

Reason:
The CA Workload Automation SE Cross-Platform submission process was unable to send
the request because CAICCI could not locate the target scheduling system at node
nnnnnnnn.

Action:
Check the CAICCI TCPIP Gateway task to determine whether the local MVS system has a
connection to the target node. If they are connected, check the target system to
determine whether the CA scheduling system is active. Once the CAICCI connection has
been established, and/or the target scheduling system is activated, the CA Workload
Automation SE Cross-Platform Submit job can be rerun.

CAL2X006W

pppppppp from ssssssss IGNORED: ...reason...

Reason:
The CA Workload Automation SE Cross-Platform submission process encountered an
input parameter pppppppp from the source ssssssss (EXECPARM, PROFILE or SYSIN) that
was ignored. The reason for the exception is described (...reason...). The submit process
continues.

Action:
Check the parameter that caused the exception, and correct it if needed.

CAL2X008E

Required Parameter missing (pppppppp) - process aborted.

Reason:
The required parameter pppppppp was not provided to the CA Workload Automation SE
Cross-Platform submission process. Processing cannot continue without it.

Note: The submission process will be UNSUCCESSFUL.

Action:
Perform the following actions:
■ Specify the parameter.
■ Rerun the CA Workload Automation SE Cross-Platform Submit job.

544 Message Reference Guide

 CAL2 Messages

CAL2X009E

One or more Parameters in error - process aborted.

Reason:
One or more parameters supplied to the CA Workload Automation SE Cross-Platform
submission process were in error.

Note: The submission process will be UNSUCCESSFUL.

Action:
Perform the following actions:
■ See the messages describing the specific errors encountered.
■ Correct the parameters.
■ Rerun the CA Workload Automation SE Cross-Platform Submit job.

CAL2X010W

SUBPASS from ssssssss ignored : NOT FROM SAME SOURCE AS SUBUSER

Reason:
The SUBPASS parameter was obtained from the source ssssssss (SYSIN or PROFILE). This
is not the same source as the SUBUSER parameter in effect. The SUBPASS parameter will
be ignored and the request will be sent without a password.

Action:
Determine whether the password specified in SUBPASS should be used with the
request. If so, it and the SUBUSER parameter must be specified in the same place (for
example, both in SYSIN).

CAL2X011W

DOMAIN from ssssssss ignored : NOT FROM SAME SOURCE AS NODE

Reason:
The DOMAIN parameter was obtained from the source ssssssss (SYSIN or PROFILE). This
is not the same source as the NODE parameter in effect. The DOMAIN parameter will be
ignored and the request will be sent without it.

Action:
Determine whether the domain specified in DOMAIN should be used with the request. If
so, it and the NODE parameter must be specified in the same place (for example, both in
SYSIN).

Chapter 2: AFM - CA7R Messages 545

CAL2 Messages

CAL2X014E

Request NOT submitted : Job jjjjjjj (####) Node nnnnnnnnn

Reason:
The CA Workload Automation SE Cross-Platform submission process was unable to send
the request to the target scheduling system at node nnnnnnnn. The job name and CA 7
WA job number indicated by jjjjjjj (####).

Action:
See the previous messages for an indication of the specific error encountered. Once the
problem has been addressed the CA Workload Automation SE Cross-Platform Submit
job can be rerun.

CAL2X015E

UNABLE TO LOAD MODULE CAL2CCIF. RC=cccc - process aborted.

Reason:
An attempt to load the CA Workload Automation SE Cross-Platform CAICCI function
module CAL2CCIF failed. The return code from the load call is cccc.

Action:
The submission process will be UNSUCCESSFUL. Confirm that the submission job is using
the correct level of the CA Workload Automation SE load library using STEPLIB or linklist.

CAL2X016E

ffffffff DD STATEMENT MISSING - process aborted.

Reason:
The DD statement for the required file ffffffff was not found in the submit job JCL.

Action:
Supply the proper JCL and rerun.

546 Message Reference Guide

 CAL2 Messages

CAL2X017E

OPEN FAILED FOR ffffffff DD - process aborted.

Reason:
An attempt to open the required file ffffffff was not successful.

Action:
Check the Job Log for related messages. Correct the error and rerun.

CAL2X018E

RDJFCB FAILED FOR ffffffff DD - process aborted.

Reason:
An attempt to read the JFCB for required file ffffffff was not successful.

Action:
Check the Job Log for related messages. Correct the error and rerun.

CAL2X020I

Parameters in effect for this execution :

Reason:
This is an informational message indicating that the following messages will describe the
parameters that are in effect for this execution of the CA Workload Automation SE
Cross-Platform submission process.

Action:
None.

Chapter 2: AFM - CA7R Messages 547

CAL2 Messages

CAL2X021I

pppppppp from ssssssss: ...value...

Reason:
This is an informational message indicating a parameter that is in effect for this
execution of the CA Workload Automation SE Cross-Platform submission process. The
parameter is indicated by pppppppp. The source for the parameter is indicated by
ssssssss (EXECPARM, SYSIN or PROFILE). The first 32 characters of the parameter value
are indicated by ...value.... If the value is longer than 32 characters, ...value.... will be
followed by ' ...'.

Action:
None. The value for SUBPASS, if specified, will always appear as 14 asterisks regardless
of the length or content of the password.

CAL2X022E

CCIF ERROR FUNC=ffff RC=rr CC=cc TEXT=xxxx...xxxx

Reason:
A call to the CAICCI sub-function module has encountered an error. The specific function
being performed is indicated by ffff (INIT, TERM, and so forth). The return code (rr) and
condition code (cc) from the error are also indicated. A text description of the error is
indicated by xxxx..xxxx.

Action:
Perform the following actions:
■ Take corrective action based upon the error text listed. For example, if CAICCI is not
active, start it.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CAL2X023E

CCIF CALL FAILED : FUNC=ffff RC=rr CC=cc

Reason:
A call to the CAICCI sub-function module has encountered an error. The specific function
being performed is indicated by ffff (INIT, TERM, and so forth). The return code (rr) and
condition code (cc) from the sub-function are also indicated.

Action:
For assistance, contact CA Support at ca.com/support.

548 Message Reference Guide

 CAL2 Messages

CAL2X030E

CA-7 ICMDSECT not present on system - process aborted.

Reason:
The CA Workload Automation SE Cross-Platform submission process could not locate
the CA Workload Automation SE ICMDSECT control block on the local system.

Action:
Ensure that CAIRIM has initialized the CA Workload Automation SE system interfaces on
the system where the submission process is executing. Or, run the submission process
on a system where CA Workload Automation SE or ICOM is already active.

CAL2X031E

CA-7 ICMDSECT IS INVALID - process aborted.

Reason:
The CA Workload Automation SE ICMDSECT control block located on the current system
is invalid.

Action:
Ensure that CAIRIM has initialized the CA Workload Automation SE system interfaces on
the system where the submission process is executing. Or, run the submission process
on a system where CA Workload Automation SE or ICOM is already active.

CAL2X032E

SUBMIT CHECK failed for SUBUSER: xxxxxxxx Current User: uuuuuuuu

Reason:
A call to the external security system to check the authority of the user ID the submit
job is running under (uuuuuuuu) to submit on behalf of the SUBUSER user ID (xxxxxxxx)
returned an error code.

Action:
See the Security Reference Guide for a discussion of the security requirements for
Cross-Platform submission. Change the external security rules, or change the SUBUSER
value or the user ID under which the submit job executes.

Chapter 2: AFM - CA7R Messages 549

CAL2 Messages

CAL2X033W

WARNING: Using id=ROOT may violate security on target system

Reason:
A user ID of ROOT was sent with the request. Since this is a restricted ID on UNIX
systems, it could represent a breach of security.

Action:
None if the use of ROOT is correct. However, we recommend that ROOT not be used to
submit jobs to CA NSM JMO. Misuse of this user ID can have serious and unexpected
consequences. See the parameter SUBROOT to control use of this ID.

CAL2X034E

ERROR: Use of id=ROOT not allowed - process aborted.

Reason:
A user ID of ROOT was specified for this request. However, the SUBROOT parameter was
set to or defaulted to NO so the request will not be honored.

Action:
We do not recommend that the use of ROOT to submit jobs to CA NSM JMO. Misuse of
this user ID can have serious and unexpected consequences. If you want to use ROOT,
you must specify SUBROOT=YES in the PROFILE parameters for the submission job.

CAL2X035E

EXTRACT of current Userid failed : RC=xx - Process aborted.

Reason:
An attempt to extract the user ID of the current environment failed.

Action:
Correct any errors indicated in the Job Log and rerun.

550 Message Reference Guide

 CAL2 Messages

CAL2X040I

ssssssss input : xxx...xxx

Reason:
These messages are produced if the trace option has been turned on. A message will be
produced for each line of parameter input read. The source of the input is indicated by
ssssssss (EXECPARM, SYSIN or PROFILE). The actual input is echoed in the area indicated
by xxx...xxx.

Action:
These trace messages may be helpful if you are getting a parameter exception error and
are having trouble determining exactly which line is producing the error.

CAL2X041I

tttttttttttt: Card length = ccc Total Length = lll

Reason:
These messages are produced if the trace option has been turned on. A message will be
produced for each line of parameter input that is part of a continuation set and will
follow the CAL2X040I message displaying the line. The message will be identified by
'Continuation' or 'Continue End' in tttttttttttt to indicate whether the parameter
continuation is complete. The length of the parameter value on the current statement is
indicated by ccc. The total length of the parameter value so far (including the current
line) is indicated by lll.

Action:
These trace messages may be helpful if you are getting a parameter exception error and
are having trouble determining exactly that line is producing the error.

CAL2X042I

CCIF CALL FUNC=fff1 RC=r1 CC=c1 : CCI FUNC=fff2 RC=r2 CC=c2

Reason:
These messages are produced if the trace option has been turned on. A message will
isproduced for each call to the CCI Function module. The current CAICCI Function
module's function is indicated by fff1. The return code and condition code from the
CAICCI Function module are indicated by r1 and c1. The CAICCI function is indicated by
fff2. The return code and condition code from CAICCI are indicated by r2 and c2.

Action:
CA Support may need these trace messages to assist in diagnosing error situations.

Chapter 2: AFM - CA7R Messages 551

CAL2 Messages

CAL2X043I

SUBMIT CHECK called for SUBUSER: uuuuuuuu Current User: cccccccc RC=rc

Reason:
This message is produced if the trace option has been turned on and a call is made to
check the current users authority to submit on behalf of the user ID specified in
SUBUSER. The return code from the call is indicated by rc.

Action:
None.

CAL2X044W

Node xxxxxxxx is not connected to the local CCI.

Reason:
A CAICCI SEND failed. An inquiry showed that the listed node is not connected to the
local CAICCI. The following are possible reasons:
■ The node specified by xxxxxxxx is not active.
■ The node specified by xxxxxxxx is not defined.
■ The remote configuration file for node xxxxxxxx does not have an entry for the
system where CA Workload Automation SE is running.

Action:
Perform the following actions:
■ Check the remote configuration file (CCIRMTD.RC) for the node specified to
determine that the LOCAL and REMOTE settings are correct.
■ Issue the CCII command at the node specified to see whether it is active.

552 Message Reference Guide

 CAL2 Messages

CAL2X045W

Node xxxxxxxx is connected to the local CCI, but the SUBMITC Server is not active.

Reason:
A CAICCI SEND failed. An inquiry showed that the listed node is connected to the local
CAICCI, but the SUBMITC Server is not active.

Action:
Perform the following actions:
■ Check the CAICCI TCP/IP Gateway task to determine whether the local MVS system
has a connection to the target node.
■ If they are connected, check the target system to determine whether the CA
scheduling system is active.
■ Once the CAICCI connection has been established, and/or the target scheduling
system is activated, the CA Workload Automation SE Cross-Platform Submit job can
be rerun.

CAL2X050E

xxxxxxxx MODULE NOT FOUND

Reason:
Module xxxxxxxx, needed by the Conversion Utility (program SASSX2UN), could not be
found. As a result, the conversion utility program is terminated.

Note: Either the CA Workload Automation SE installation had errors or a module was
deleted from the CA Workload Automation SE load library.

Action:
Contact your installation specialist for assistance.

CAL2X051E

BAD RETURN FROM THE SASSMEML MODULE, DO NOT HAVE PDSDD MEMBER LIST

Reason:
There was a problem with the PDSDD DD statement data set used in the conversion
utility job.

Action:
Check the PDSDD DD statement data set, which must be a PDS and must have members.

Chapter 2: AFM - CA7R Messages 553

CAL2 Messages

CAL2X052E

SASSMEML MODULE CONTROL BLOCK INVALID, PDSDD STATEMENT CANNOT BE

PROCESSED

Reason:
There was a problem with the PDSDD DD statement data set used in the conversion
utility job.

Action:
Check the PDSDD DD statement data set, which must be a PDS and must have members.

CAL2X053E

UNABLE TO OPEN xxxxxxxx DD FILE

Reason:
There was a problem opening the file specified by xxxxxxxx when running the
conversion utility job.

Action:
Check the appropriate DD statement data set for errors.

CAL2X054E

NO MEMBERS FOUND IN JCL PDSDD FILE

Reason:
There was a problem with the PDSDD DD statement data set used in the conversion
utility job.

Action:
Check the PDSDD DD statement data set, which must be a PDS and must have members.

554 Message Reference Guide

 CAL2 Messages

CAL2X055W

RESTMASK NOT PROVIDED. NO RESTORE/BACKOUT CAPABILITY REQUESTED

Reason:
For the conversion utility job, a RESTMASK keyword and value were not provided in the
SYSIN DD statement.

Action:
None. This is a warning message. Be aware that if this keyword is not provided, no
backup of your CA7TOUNI job definitions is performed during the conversion. If a
restore is necessary, you need to redefine your jobs to CA Workload Automation SE.

CAL2X056I

PDS HAS THE SUBROOT PARAMETER, SEE XPSDEF INIT DECK PARAMETER FOR
SUBROOT DETAILS

Reason:
A member containing the CA7TOUNI SUBROOT parameter was found when converting
the CA7TOUNI job definition to a XPJOB definition.

Note: For more information about the equivalent SUBROOT capability for XPJOB
definitions, see the XPSDEF initialization statement in the Systems Programming Guide.

Action:
None.

CAL2X057E

UNKNOWN KEYWORD IN SASSX2UN SYSIN FILE

Reason:
An unknown keyword was specified in the conversion utility job. Valid conversion utility
keywords are RESTMASK, RMSEXEC, MEMBER, and PDSDDDSN.

Note: For more information about these keywords, see the Interface Reference Guide.

Action:
Correct the invalid keyword.

Chapter 2: AFM - CA7R Messages 555

CAL2 Messages

CAL2X058E

INVALID NAME FOR RMS JCL PROCEDURE

Reason:
The value specified for the RMSEXEC keyword used in the Conversion Utility was invalid.
The value must conform to standard IBM JCL procedure naming conventions.

Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Correct the invalid value.

CAL2X059E

INVALID OFFSET POSITION IN RESTORE MASK, MUST BE 1-8

Reason:
The offset value specified for the RESTMASK keyword used in the conversion utility was
invalid. It must be a number from 1 to 8.

Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Correct the invalid value.

CAL2X060E

INVALID SUBSTITUTION CHARACTER IN RESTORE MASK, ALPHANUMERIC OR

NATIONAL REQUIRED

Reason:
The substitution value specified for the RESTMASK keyword used in the Conversion
Utility was invalid. The substitution value in the RESTMASK supplies a new member
name. As such, it must be an alphanumeric or national character. The member name
must adhere to standard IBM data set member name standards.
Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Correct the invalid value.

556 Message Reference Guide

 CAL2 Messages

CAL2X061E

IF OFFSET POSITION = 1, MASK MUST BE ALPHA OR NATIONAL CHARACTER

Reason:
The offset value/substitution value specified for the RESTMASK keyword used in the
conversion utility was invalid. This occurs when the offset value is 1 and the substitution
character is a numeric. The substitution value in the RESTMASK supplies a new member
name. As such, it must be an alpha or national character. The member name must
adhere to standard IBM data set member name standards.
Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Correct the invalid value.

CAL2X062E

NUMBER OF SYSIN MEMBER= CARDS EXCEEDED. LIMIT IS 512.

Reason:
The maximum number of SYSIN DD MEMBER= cards that can be specified for the
conversion utility has been exceeded. A maximum of 512 MEMBER cards can be
entered.
Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Specify a mask instead of an actual member name to reduce the number of MEMBER
cards because masking is allowed.

CAL2X063E

SASSMEML - PARSER BAD RC *'

Reason:
The parameter list passed to SASSMEML is incorrect.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 2: AFM - CA7R Messages 557

CAL2 Messages

CAL2X064E

SASSMEML - FILINIT BAD RC *

Reason:
There was a problem opening the PDSDD input file.

Action:
Perform the following actions:
■ Check the PDSDD DD input file.
■ Make sure you can browse the members in the data set.

CAL2X065E

INVALID DATA SET NAME ON SYSIN PDSDDDSN= CARD.

Reason:
The value specified for the PDSDDDSN keyword used in the conversion utility was
invalid. The value must conform to standard IBM JCL data set naming conventions.

Note: For more information about the conversion utility, see the Interface Reference
Guide.

Action:
Correct the invalid value.

CAL2X101I

CA-7 CROSS-PLATFORM TRACKING SYSTEM (XTRK) IS INITIALIZING (rxx)

Reason:
The initializiation process for the CA Workload Automation SE Cross-Platform Tracker
(XTRK) has begun. The notation xx.x indicates the product release of CA Workload
Automation SE.

Action:
None.

558 Message Reference Guide

 CAL2 Messages

CAL2X102I

CA-7 CROSS-PLATFORM TRACKING SUB-TASK ACTIVE: ttt...ttt

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) subtask ttt...ttt has
initialized.

Action:
None.

CAL2X103I

CA-7 CROSS-PLATFORM TRACKING (XTRK) IS ACTIVE FOR xxxx

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has initialized and is
now active. The value of xxxx indicates the instance name for the copy of CA Workload
Automation SE being tracked.

Action:
None.

CAL2X104I

XTRK MONITOR=mmmmmmm LOCAL NODE=nnnn HAO PRIMARY=xxxxxxx

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has initialized and is
now active. This message indicates the monitor name (mmmmmmm) and the local
CAICCI node name (nnnn) that comprise the local host ID for XTRK. If this copy of CA
Workload Automation SE is executing with the High Availability Option (HAO), the HAO
name is listed in the PRIMARY field.

Action:
None.

Chapter 2: AFM - CA7R Messages 559

CAL2 Messages

CAL2X107I

CROSS-PLATFORM TRACKING (XTRK) HAS RECEIVED A STOP COMMAND

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has received a stop
command either from an operator command or CA Workload Automation SE ICOM.

Action:
None.

CAL2X108I

ALL CA-7 CROSS-PLATFORM TRACKING SUB-TASKS HAVE TERMINATED

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) subtasks have
terminated.

Action:
None.

CAL2X109I

CA-7 CROSS-PLATFORM TRACKING (XTRK) HAS TERMINATED

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) system has completed
its termination process.

Action:
None.

560 Message Reference Guide

 CAL2 Messages

CAL2X140W

*WARNING* CA-7 XTRK CKPT FILE HOST SYSTEM ID CONFLICT *WARNING*

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has encountered a
conflict between the host system ID in the XTRK Checkpoint file and the host system ID
of the current environment. The host system ID is made up of the monitor name and the
local CAICCI node name and the High Availability Option (HAO) Primary Name. This
indicates that either the HAO name, the monitor, or the CAICCI node name has changed,
or XTRK has been started using the wrong Checkpoint file.

Action:
This message will be followed by highlighted messages CAL2X141W and CAL2X142I.

CAL2X141W

xxxx: MONITOR=mmmmmmm NODE=nnn...nnn

Reason:
Two versions of this message will be displayed following CAL2X140W. The message
where xxxx=CKPT indicates the Monitor and CAICCI node name and High Availabilty
Option (HAO) Primary Name carried in the XTRK Checkpoint file currently being
accessed. The message where xxxx=LOCAL indicates the Monitor name and HAO
Primary Name specified in the current XTRK startup parameters and the CAICCI node
name of the local CAICCI environment.

Action:
These messages will be followed by WTOR message CAL2X142I.

Chapter 2: AFM - CA7R Messages 561

CAL2 Messages

CAL2X142I

OVERRIDE THE CA-7 XTRK CKPT FILE SYSTEM ID? (REPLY Y FOR YES, ANY OTHER
CHARACTER FOR NO)

Reason:
This WTOR follows messages CAL2X140W and CAL2X141I. This WTOR allows the
operator to either override the XTRK Checkpoint Host System ID and continue
processing, or indicate that the XTRK system should terminate so that the XTRK
Checkpoint file is not corrupted.

This message follows messages CAL2X140W and CAL2X141I. The most likely reason for
this situation is attempting to use the same checkpoint file for more than one copy of
the Cross-Platform Tracker.

Action:
Perform one of the following actions:
■ Reply Y to this message to update the checkpoint file with the new local
information if the CA Workload Automation SE Monitor name, the local CAICCI
Node name, or the High Availability Option (HAO) Primary Name have been
deliberately changed.
■ Reply with any character other than Y to this message, and the XTRK system
terminates if the CA Workload Automation SE Monitor name, the local CAICCI Node
name, or the HAO Primary Name have not been deliberately changed.

CAL2X143I

*NOTE* HAO ENABLED CA-7 XTRK IS NOW ACTIVE ON A NEW CCI NODE *NOTE*

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has initialized on a new
host system with an existing High Availability Option (HAO) Primary Name. The host
system ID in the XTRK Checkpoint file and the host system ID have the same HAO
Primary name and monitor names, but the CAICCI node name is different from that of
the local environment. This message is normal if a copy of CA Workload Automation SE
is manually moved, or 'fails over' to a different LPAR.

Action:
None if this is what you intended. If not, shut down CA Workload Automation SE and
determine the correct XTRK checkpoint file for this copy of CA Workload Automation SE.

562 Message Reference Guide

 CAL2 Messages

CAL2X144I

*NOTE* CA-7 XTRK IS NOW USING A PRIMARY NAME WHICH MAKES IT HAO ENABLED
*NOTE*

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has initialized with a
High Availability Option (HAO) primary name, but the host system ID in the XTRK
checkpoint file has a blank HAO primary name. This message is normal if you have just
added an HAO primary name to CA Workload Automation SE.

Action:
None if this is what you intended.

Note: When XTRK comes up with an HAO primary name, it does not receive feedback
for any previously submitted cross-platform jobs that did not reflect that HAO primary
name.

CAL2X150I

XTRK COMMAND PROCESSING COMPLETE: ccc...ccc

Reason:
Processing for the XTRK operator command ccc...ccc has completed.

Action:
None.

CAL2X151W

INVALID XTRK COMMAND IGNORED: ccc...ccc

Reason:
An invalid operator command (ccc...ccc) was passed to the CA Workload Automation SE
Cross-Platform Tracker (XTRK). The command was ignored.

Action:
If the command was intended for XTRK, correct and reissue it.

Chapter 2: AFM - CA7R Messages 563

CAL2 Messages

CAL2X152W

XTRK COMMAND PROCESS ERROR: ccc...ccc

Reason:
An error was encountered attempting to process the CA Workload Automation SE
Cross-Platform Tracker (XTRK) command (ccc...ccc).

Action:
Review any preceding or following messages and take corrective action as indicated by
them. If there are no other messages and the problem is impacting normal processing,
contact CA Support at ca.com/support for assistance.

CAL2X154I

xxx NODE NAME=

Reason:
This message is issued in response to a NODEN CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. For each entry in the XTRK node table two of
these messages will be issued. The first where xxx=CCI to indicate the CAICCI node
name, and the second where xxx=TNG to indicate the TNG node name. These names
should be the same unless a CAICCI alias is being used.

Action:
None.

CAL2X155I

NODE STATUS LAST ACTIVITY CHECKPOINT DATE/TIME [FLAGS]

Reason:
This message is issued in response to a NODE CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. This is the title line indicating the information
in the columns of message CAL2X156I that follows.

Action:
None.

564 Message Reference Guide

 CAL2 Messages

CAL2X156I

nnn...nnn ssssssssss yyyy/ddd hh:mm:ss.th yyy2/dd2 hh:mm:ss.th [ffffffff]

Reason:
This message is issued in response to a NODE CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. A message is issued for each entry in the XTRK
node table where nnn...nnn is the CAICCI node name, sssssss is the status of the XTRK
connection with that node, yy/ddd... is the date and time of the Last Activity with that
node, and yyy2/dd2.... is the Checkpoint date/time for that node. Flags may be shown in
ffffffff. Possible status values are the following:
ACTIVE
Indicates synchronization complete, active connection.
NO CONTACT
Indicates XTRK has not been able to send a record to this node, nor has it ever
received a record from this node.
LOSTCONN
Indicates contact with this node had been established, but has since been lost.
SYNCH
Indicates XTRK is currently performing Checkpoint Synchronization with this node.

Action:
None.

CAL2X157I

XTRK xxxx TABLE DOES NOT HAVE ANY ENTRIES.

Reason:
This message is issued in response to a NODE or XEVT SNAP CA Workload Automation SE
Cross-Platform Tracker (XTRK) command (where xxxx is either NODE or XEVT). There are
no entries in the XTRK Node table or External events to display/snap.

Action:
None.

Chapter 2: AFM - CA7R Messages 565

CAL2 Messages

CAL2X158I

NO XTRK NODE TABLE ENTRIES MATCH SELECT CRITERIA.

Reason:
This message is issued in response to a NODE CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. However, no XTRK Node table entries match
the selection criteria specified on the command.

Action:
None.

CAL2X159I

TRACE STATUS: PRT(p) CON(c) PRTDD(dddddddd,ddddd) SNAPDD(sssss,ssss)

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) was passed a TRC
command. This message indicates the status of the XTRK Trace facility. The following
information is provided:
PRT(p)
Specifies the current print trace code.
CON(c)
Specifies the current console trace code.
PRTDD(...
Specifies the trace print ddname (dddddddd), and the status of the DD (OPEN,
CLOSED or DUMMY).
SNAPDD(...
Specifies the trace snap ddname (dddddddd), and the status of the DD (OPEN,
CLOSED or DUMMY).

Action:
None.

566 Message Reference Guide

 CAL2 Messages

CAL2X160W

UNABLE TO HONOR SNAP COMMAND. SNAP IS CLOSED, OR SNAP DD IS NOT

AVAILABLE.

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) received a valid SNAP
command. However, the request could not be satisfied because the XTRK trace SNAP
DCB is closed, or the XSNAP DD is not in the JCL or is dummied.

Action:
Issue the XTRK Trace Status command (TRC with no operands) to determine the status
of the SNAP trace. If it is closed, issue the open command: TRC(OPEN,SNAP) then reissue
the snap request. If the XSNAP DD is dummied, XTRK will have to be terminated, the
appropriate DD statement added to the JCL, and XTRK restarted before the SNAP
command can be honored.

CAL2X161W

UNABLE TO OBTAIN xxxx LOCK WORD. LOCK BEING FORCED (own/cur).

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) message function
module could not obtain the internal lock for the print or snap dd indicated by xxxx, PRT
or SNAP). The task-id that owns the lock is indicated by own and the task-id that is
forcing control of the lock is cur. After one minute the lock is forced.

Action:
If the message is issued repeatedly, contact CA Support at ca.com/support for
assistance.

CAL2X162W

cc...cc COMMAND FAILED: xxx...xxx

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) rejected an ADDNODE
or DELNODE command (cc...cc). The reason is indicated by xxx...xxx. For ADDNODE,
'NODE ENTRY ALREADY EXISTS'. For DELNODE, 'NODE NOT FOUND IN TABLE'.

Action:
Check to ensure that your spelling of the node name is correct. Use the NODE command
to list existing entries in the XTRK node table.

Chapter 2: AFM - CA7R Messages 567

CAL2 Messages

CAL2X170I

XTRK SYNCHRONIZATION (yyyy/ddd hh:mm:ss.th) NODE=nnn...nnn

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has completed the
Checkpoint Synchronization process with the remote node indicated by NODE=. The
Checkpoint date and time used for synchronization is indicated by yyyy/ddd
hh:mm:ss.th. If synchronization is performed for a node that has already been
synchronized the term 'RE-SYNCH' will appear in the message instead of
'SYNCHRONIZATION'.

Action:
None.

CAL2X171I

XTRK HAS CONTACTED NODE nnn...nnn

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) has sent a record to
node nnn...nnn using CAICCI to attempt to initiate the Cross-Platform Checkpoint
Synchronization process with that node.

Action:
None.

CAL2X174W

XTRK UNABLE TO CONTACT NODE nnn...nnn

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) was unable to send a
record to node nnn...nnn using CAICCI to attempt to initiate the Cross-Platform
Checkpoint Synchronization process with that node. XTRK will continue to attempt to
contact this node; however, this message will not be repeated.

Action:
If this node should be connected, check the CAICCI definitions on both the mainframe
and remote systems. If this node is no longer part of the Cross-Platform system, use the
DELNODE command to delete the node and prevent further messages.

568 Message Reference Guide

 CAL2 Messages

CAL2X177W

XTRK HAS LOST CONTACT WITH nnn...nnn

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) was unable to send a
record to node nnn...nnn even though XTRK had previously communicated with that
node. XTRK will continue to attempt to contact this node; however, this message will
not be repeated.

Action:
Check the CAICCI definitions on both the mainframe and remote systems.

CAL2X178W

XTRK MGR POSTED WITH UNKNOWN COMMAND CODE.

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) tracking manager
subtask was posted with an operator command. However, the command code is not
defined to the manager.

Action:
For assistance, contact CA Support at http://ca.com/support.

CAL2X179I

CCI ALIAS xxxxxxxx HAS REPLACED NODE yyyyyyyy

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) found CAICCI node
yyyyyyyy and replaced it with its associated CAICCI alias xxxxxxxx. The entry for node
yyyyyyyy, in the XTRK checkpoint file, is marked for deletion. This situation can occur
when an alias is added to a node name that is already in use and that node name is less
than or equal to eight characters.

Action:
None.

Chapter 2: AFM - CA7R Messages 569

CAL2 Messages

CAL2X181I

XTRK EXTERNAL EVENT TABLE RE-BUILT. ALL NODES WILL BE RE-SYNCHRONIZED

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) External Event table has
been redefined because of a BLDXEVT operator command. The XTRK Manager subtask
will be posted to force a new Checkpoint Synchronization process for each remote node
in the XTRK Node table.

Action:
None.

CAL2X182W

XTRK EXTERNAL EVENT TABLE NOT BUILT: xxx...xxx

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) encountered serious
errors attempting to build an External Event table from the rules pointed to by the
XEVENTS DD statement. The specific reason is indicated by xxx...xxx.

Action:
If you want to have External Event definitions, correct the errors indicated and recycle
XTRK, or issue the BLDXEVT command.

CAL2X183W

XTRK EXTERNAL EVENT TABLE DOES NOT HAVE ANY ENTRIES.

Reason:
This message is issued in response to an XEVT or SNAP CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. There are no entries in the XTRK External
Event table to display/snap.

Action:
None.

570 Message Reference Guide

 CAL2 Messages

CAL2X184W

NO XTRK EXTERNAL EVENT TABLE ENTRIES MATCH SELECT CRITERIA.

Reason:
This message is issued in response to an XEVT or SNAP CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. However, no XTRK External Event table entries
match the selection criteria specified on the command.

Action:
None.

CAL2X185I

TRIGID TYPE XEVENT ENTRY INFORMATION

Reason:
This message is issued in response to an XEVT CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. This is the title line indicating the information
in the columns of message CAL2X186I that follows.

Action:
None.

CAL2X186I

tttttttt xxx = iii...iii

Reason:
This message is issued in response to an XEVT CA Workload Automation SE
Cross-Platform Tracker (XTRK) command. A set of these messages will be issued for each
entry in the XTRK External Event table. Where:
tttttttt
Indicates the trigger ID for the event
xxxx
Indicates the keyword for the information listed
iii...iii
Indicates information from the table entry

Action:
None.

Chapter 2: AFM - CA7R Messages 571

CAL2 Messages

CAL2X199I

VALID CMDS ARE: STOP,ADDNODE,BLDXEVT,DELNODE,NODE,NODEN,NODEX,

PING,SNAP,TRC AND XEVT

Reason:
An invalid operator command (ccc...ccc) was passed to the CA Workload Automation SE
Cross-Platform Tracker (XTRK). The command was ignored. This message lists the valid
XTRK command verbs.
Note: For more information about XTRK commands and their syntax, see the Interface
Reference Guide.

Action:
Use a valid XTRK command verbs.

CAL2X201I

XTRK FBK xxxxxxxx (yyyy/ddd hh:mm:ss.th) tttttttt iii...iii nnn...nnn

Reason:
A Feedback event was received by the CA Workload Automation SE Cross-Platform
Tracker (XTRK). Where:
xxxxxxxx
Indicates whether the feedback was processed, in error, and so forth...
yyyy/ddd...
Indicates the date and time in the event.
tttttttt
Indicates the type of feedback event (JOBINITU, JOBTERMU, and so forth).
iii...iii
Indicates the job name or file name from the feedback.
nnn...nnn
Indicates the CAICCI node that sent the feedback.

Action:
None.

572 Message Reference Guide

 CAL2 Messages

CAL2X202E

XTRK FBK RECORD FORMAT ERROR: xxx...xxx REC=rrr...rrr NODE=nnn...nnn

Reason:
A Feedback record received by the CA Workload Automation SE Cross-Platform Tracker
(XTRK) was in error. Where:
xxx...xxx
Indicates the specific error:
■ 'INVALID RECTYPE'
■ 'INVALID BLKSIZE'
■ 'INVALID LRECL '
■ 'BAD DATE/TIME '
■ 'PREPERR: xxxx '
REC=
Indicates the first 16 characters of the feedback record
NODE=
Indicates the CAICCI node that sent the feedback

Action:
Research the reason for the bad feedback event record. It is possible a cross-platform
job may not be properly tracked, and a manual requeue or cancel will be required.

CAL2X203I

FILE=xxxx name

Reason:
This is a continuation of Message CAL2X202E when the feedback record is for a DSN.
xxxx is a tag for the first line. The extended file name or DSN is name.

Action:
See Message CAL2X202E.

Chapter 2: AFM - CA7R Messages 573

CAL2 Messages

CAL2X290W

#XNT FAILED : RC=xx RS=yyyy MSG=zzzzzzzzzzz

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) attempted to invoke the
CAICCI #XNT function. The attempt failed with return code xx, reason code yyyy, and
message zzzzzzzzzzz. The #XNT function is used in certain situations to determine
whether node names have associated aliases (see message CAL2X179I). The most typical
#XNT failure is when CAS9VTAM is back-leveled.

Action:
Check CAS9 for the CAS9075I message for Reason Code 144 (CAS9VTAM back-leveled).
The release must be 2.1 or higher. For all other messages, if the message is issued
repeatedly, contact CA Support at ca.com/support for assistance.

CAL2X301I

CA-7 SMF REC: SMF=xx(tttttttt) SVC=xx (.UNI) iii...iii

Reason:
A CA Workload Automation SE pseudo-SMF record was generated based on information
in a Cross-Platform Feedback record. Where:
SMF=xx
Indicates the SMF record type (in hex) and a literal
■ 'STEPTERM'
■ 'JOBTERM'
■ 'DSCLOSE'
■ 'JOBINIT'
SVC=
Indicates the return code from the CA Workload Automation SE SVC
.UNI
Indicates either 7XPJ for CA Workload Automation SE XPJOB jobs, 7UNI for CA
Workload Automation SE Cross-Platform jobs, or XUNI for CA Workload Automation
SE Cross-Platform External tracking jobs/data sets
iii...iii
Indicates the related job name or data set name

Action:
None.

574 Message Reference Guide

 CAL2 Messages

CAL2X372I

SETUP REQUEST FROM NODE nnn...nnn

Reason:
A request to initiate Checkpoint Synchronization (1 rec) was received by the CA
Workload Automation SE Cross-Platform Tracker (XTRK). The CAICCI node requesting
setup is indicated by nnn...nnn.

Action:
None.

CAL2X374W

XTRK RECEIVED UNKNOWN RECTYPE: rrrrrrrr/nnn...

Reason:
An unknown record type was received by the CA Workload Automation SE
Cross-Platform Tracker (XTRK). The first eight characters of the record are indicated by
rrrrrrrr. The CAICCI node that sent the record is indicated by nnn....

Action:
None.

CAL2X400I

XTRK SYSTEM ENTERED IN xxx..xxx

Reason:
This message indicates the mode that the CA Workload Automation SE Cross-Platform
Tracker (XTRK) was entered in. The value xxx...xxx will be 'SUB-PGM MODE' if XTRK is
running under CA7ICOM, or 'STC/JOB MODE' if XTRK is running as an independent job or
started task.

Action:
None.

Chapter 2: AFM - CA7R Messages 575

CAL2 Messages

CAL2X450I

(ttt) TABF EXIT: FUNC=ffff RC=rrrr CC=cccccccc

Reason:
This message indicates an exit from the CA Workload Automation SE Cross-Platform
Tracker (XTRK) Node Table function module.
ttt
Indicates the taskid that called the function
ffff
Indicates the function code for the call
rrrr
Indicates the return code for the call (R15)
ccc...
Indicates the condition code for the call (R0)

Action:
None.

CAL2X451I

(TAB) CKPF CALL: FUNC=ffff RC=rrrr CC=cccc

Reason:
This message indicates a return from a call by the CA Workload Automation SE
Cross-Platform Tracker (XTRK) Node Table function module to the Checkpoint file
function module.
ffff
Indicates the function code for the call.
rrrr
Indicates the return code for the call (R15).
cccc
Indicates the condition code for the call (R0).

Action:
None.

576 Message Reference Guide

 CAL2 Messages

CAL2X452I

(tid) CCIF CALL: FUNC=ffff RC=rr CC=cc:

CCI FUNC=f2f2 RC=r2 CC=c2 (r/nnnnnnnn)

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) task has called the CCI
sub-function module. The calling task is identified by tid.. The specific function (INIT,
TERM, and so forth) is indicated by ffff. The return code (rr) and condition code (cc) are
also indicated. The specific CAICCI function performed is indicated by f2f2 and the
CAICCI return code (r2) and condition code (c2) are also indicated. If the specific
function is a Receive Completion (RCMP) or send (SEND or SNDX) the first byte of the
record received or sent (record type) and the related CAICCI node are indicated by
(r/nnnnnnnn).

Action:
None.

CAL2X471I

MGR POSTED FOR COMMAND

Reason:
This message indicates that the XTRK Manager task has been posted for special
processing.

Action:
None.

CAL2X472I

(MGR) PERFORMING PING LOOP PROCESS

Reason:
This message indicates that the XTRK Manager task has initiated the process where an
attempt is made to send each CAICCI node in the XTRK node table either a setup record
(4) or dummy record (0).

Action:
None.

Chapter 2: AFM - CA7R Messages 577

CAL2 Messages

CAL2X475I

(MGR) CCI RECEIVE RTN ENTERED

Reason:
This message indicates that the XTRK Manager task has received a record from CAICCI.

Action:
None.

CAL2X480I

(ttt) EVTF EXIT: FUNC=ffff RC=rc CC=cccccccc

Reason:
This message indicates an exit from the CA Workload Automation SE Cross-Platform
Tracker (XTRK) External Event Table function module.
ttt
Indicates the taskid that called the function
ffff
Indicates the function code for the call
rrrr
Indicates the return code for the call (R15)
ccc...
Indicates the condition code for the call (R0)

Action:
None.

578 Message Reference Guide

 CAL2 Messages

CAL2X801E

SYNTAX ERROR NEAR LINE llll COLUMN cc CODEx

Reason:
A syntax error was detected while processing a rule in the CA Workload Automation SE
Cross-Platform Tracker (XTRK) External Events file (XEVENTS DD). The syntax error was
detected near line llll, column cc. The code is for internal debugging purposes.
Processing continues with the next external event rule.

Action:
Correct the syntax errors on the indicated lines and either terminate and restart XTRK,
or issue the BLDXEVT command to rebuild the External Events table.

CAL2X802E

PREMATURE EOF WHILE PROCESSING DATA, LINE lllll

Reason:
An incomplete EVENT( was detected while processing the Cross-Platform Tracker (XTRK)
External Events file (XEVENTS DD). The error was detected near line lllll. Processing
continues with the next external event rule.

Action:
Correct the syntax errors on the indicated lines and either terminate and restart XTRK,
or issue the BLDXEVT command to rebuild the External Events table.

CAL2X803E

PREMATURE EOF, LINE lllll

Reason:
An incomplete EVENT( was detected while processing the Cross-Platform Tracker (XTRK)
External Events file (XEVENTS DD). The error was detected near line llll. Processing
continues with the next external event rule.

Action:
Correct the syntax errors on the indicated lines and either terminate and restart XTRK,
or issue the BLDXEVT command to rebuild the External Events table.

Chapter 2: AFM - CA7R Messages 579

CAL2 Messages

CAL2X804E

ERROR NEAR LINE lllll COLUMN cc: xxx...xxx

Reason:
A syntax or logic error was detected while processing the Cross-Platform Tracker (XTRK)
External Events file (XEVENTS DD). The error was detected near line llll column cc. The
specific nature of the error is indicated by the text xxx...xxx. Processing continues with
the next external event rule.

Action:
Correct the syntax errors on the indicated lines and either terminate and restart XTRK,
or issue the BLDXEVT command to rebuild the External Events table.

CAL2X900W

CA-7 XTRK WAITING FOR ENF/CCI TO BECOME ACTIVE.

Reason:
This message is issued as a non-deletable WTO to the master console. The CA Workload
Automation SE Cross-Platform Tracker (XTRK) has detected that the CAIENF (Event
Notification Facility), CAICCI (Common Communications Facility), or both are not active
on the local system. If the XTRK subtasks were already active they will be terminated.
No cross-platform communication occurs while XTRK is in this state.

XTRK will check for ENF/CCI availability every two minutes until they become active or
XTRK is shut down. In either case, this WTO is deleted from the master console.

Action:
Check the system for the CAIENF started task (default name=ENF). Check the console log
for any messages indicating a problem with CAIENF, CAICCI, or both.

Start the CAIENF task. If CAIENF activation is successful, it causes CAICCI to be initialized
also. The next time XTRK checks for ENF/CCI availability, it detects them and starts the
XTRK subtasks to perform the CA Workload Automation SE Cross-Platform Tracking
functions.

580 Message Reference Guide

 CAL2 Messages

CAL2X901W

CA-7 XTRK WAITING FOR CA-7 CAS9 INITIALIZATION.

Reason:
This message is issued as a non-deletable WTO to the master console. The CA Workload
Automation SE Cross-Platform Tracker (XTRK) has detected that the CA Workload
Automation SE SMF and SVC interfaces have not been initialized on the local system.
These interfaces are initialized using the CAIRIM CAS9 initialization procedure. If the
XTRK subtasks were already active, they are terminated. No cross-platform
communication occurs while XTRK is in this state.

XTRK checks for CA Workload Automation SE CAS9 initialization every two minutes until
it detects them or XTRK is shut down. In either case, this WTO is deleted from the
master console.

Check the second XTRK JCL parameter and confirm that it points to the correct instance
name of the associated copy of CA Workload Automation SE. For example: CA71, TEST,
and so forth. If not specified, the default is the production (CA71) instance.

Action:
Run the CAIRIM CAS9 procedure to initialize the CA Workload Automation SE SMF and
SVC interfaces on the local system. See the Systems Programming Guide for specific
information about CA Workload Automation SE and CAIRIM.

The next time XTRK checks for CA Workload Automation SE interface initialization, it
detects them and starts the XTRK subtasks to perform the CA Workload Automation SE
Cross-Platform Tracking functions.

CAL2X902E

INVALID PARAMETER STARTING WITH (xxx..xxx) - ABORTING

Reason:
An invalid parameter was passed to the CA Workload Automation SE Cross-Platform
Tracker (XTRK). The value in error is indicated by xxx...xxx.

Action:
Correct the parameter error and restart XTRK.

Chapter 2: AFM - CA7R Messages 581

CAL2 Messages

CAL2X903E

INVALID TRACE CODE(S) SPECIFIED - ABORTING

Reason:
An invalid parameter was passed to the CA Workload Automation SE Cross-Platform
Tracker (XTRK). The value in error is the trace codes that must be two numeric digits.

Note: For more information about XTRK trace codes, see the Interface Reference Guide.

Action:
Correct the parameter error and restart XTRK.

CAL2X904E

UNABLE TO LOAD MODULE mmm..mmm. RC=rrrr

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) was unable to load
module mmm...mmm. The return code from the LOAD macro is indicated by rrrr.

Action:
Ensure that the CA Workload Automation SE load library (CAL2LOAD) is specified in the
STEPLIB or LINKLIST concatenation. Also, ensure that there is sufficient REGION available
for processing. Restart XTRK.

CAL2X905E

XTRK SUB-TASK ENDED PREMATURELY: tttttttt (mmmmmmmm) TCBCMP=ccccccc

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subtask terminated
outside of normal shutdown processing. The title of the subtask is indicated by ttttt and
the module name is indicated by mmmmmmmm. The task completion code is indicated
by cccccc. This message may be preceded by other messages indicating the nature of
the error. The XTRK system shuts down any other subtasks that are active.

Action:
Review any preceding or following messages and take corrective action if needed. If
there are no other messages, contact CA Support at ca.com/support for assistance.

582 Message Reference Guide

 CAL2 Messages

CAL2X906E

SUBTASK HAS NOT RESPONDED TO TERM CALL: xxx...xxx

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subtask has not responded
to a termination signal during normal shutdown processing. The title of the subtask is
indicated by xxx...xxx. The subtask is forced to terminate (detached) by the main task,
and XTRK termination processing proceeds.

Action:
Review any preceding messages and take corrective action indicated by them. If there
are no other messages, contact CA Support at ca.com/support for assistance.

CAL2X907E

ERROR RETURN FROM ATTACH FOR xxxxxxxx RC=rrrr

Reason:
The CA Workload Automation SE Cross-Platform Tracker (XTRK) was unable to attach a
subtask during initialization processing. The module being attached is indicated by
xxxxxxxx. The return code from the attach process is indicated by rrrr. The XTRK system
terminates with a return code of 12. One possible reason for this error is insufficient
storage.

Action:
Try increasing the region XTRK is running in. If this does not correct the problem, contact
CA Support at ca.com/support for assistance.

CAL2X908E

STARTUP OF SUBTASK xxxxxxxx FAILED. COMP=cccccc

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subtask could not initialize
properly. The subtask module is indicated by mmmmmmmm. The return code from the
subtask is cccccc. The XTRK system shuts down any active tasks and terminates.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, contact CA Support at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 583

CAL2 Messages

CAL2X909E

SUBTASK HAS NOT RESPONDED TO INIT CALL: xxx...xxx

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subtask did not complete
initialization within two minutes of being engaged. The subtask title is indicated by
xxx...xxx. XTRK shuts down any active tasks and terminates with a return code of 8.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, contact CA Support at ca.com/support for assistance.

CAL2X910E

XTRK ffff OF ddddddddd FAILED. RC=rc CC=cc

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) main task call to a
subfunction module failed. The function is indicated by ffff (INIT, TERM, and so forth),
the subfunction is indicated by ddddddddd (TABLE FUNC, TRACE FUNC, and so forth). If
the error occurs during initialization processing, the XTRK system will shut down any
active tasks and terminate. If the error occurs during XTRK command processing, the
command will be rejected, and normal processing will continue.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

584 Message Reference Guide

 CAL2 Messages

CAL2X911W

XTRK ESTAE ENTERED - WIP=ww (cccc) (pppppppp): ddd........ddd

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) main task error routine
has been entered for an abend in its own processing, or the processing of a task above
it. The code is indicated by ww. The abend code is indicated by cccc (hex). The abend
PSW is indicated by pppppppp. If the PSW points to an address within the XTRK main
task program it will be in the form of '+ offset'. If not, it will be the full eight character
PSW. The description of the action being taken is ddd......ddd. If the recovery routine will
attempt to continue processing the description will be 'RETRY IS BEING ATTEMPTED'.

If the recovery is successful, XPS will continue its normal processing. If the error
occurred in the task that attached XTRK, or the error is persistent, or the error is of a
critical nature the description will be 'ALLOWING ABEND TO PROCEED'. In this case the
XTRK system will be terminated with the original error.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

CAL2X912E

*WARNING* XTRK RECOVERY PROCESS FAILED. ESTAE REENTERED. *WARNING*

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) main task error routine
has been entered again for an abend in its own processing, or the processing of a task
above it, signifying the recovery process has failed. This message is preceded by
Message CAL2X911W, which contains details of the error recovery attempt. Issued by
CAL2XTRK.

Action:
See Message CAL2X911W.

Chapter 2: AFM - CA7R Messages 585

CAL2 Messages

CAL2X914E

INVALID OR MISSING MONITOR NAME - ABORTING

Reason:
An invalid MONITOR name parameter was passed to the CA Workload Automation SE
Cross-Platform Tracker (XTRK). Monitor names should be seven alphanumeric
characters. It should match the MONITOR name being used for CA7TOUNI
Cross-Platform jobs that this XTRK system will track.

Note: For more information about XTRK parameters, see the Interface Reference Guide.

Action:
Correct the parameter error and restart XTRK.

CAL2X915E

MISSING OR INVALID XTRK PARM LIST - ABORTING

Reason:
An invalid parameter list was passed to the CA Workload Automation SE Cross-Platform
Tracker (XTRK).

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

CAL2X925E

XTRK MGR TASK RECEIVED INVALID PARM LIST

Reason:
An invalid parameter list was passed to the CA Workload Automation SE Cross-Platform
Tracker (XTRK) manager subtask. The subtask terminates, which will cause XTRK to
terminate.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

586 Message Reference Guide

 CAL2 Messages

CAL2X926E

CA-7 CROSS-PLATFORM TRACKER ALREADY ACTIVE ON THIS SYSTEM

Reason:
CAICCI indicates that there is already a CA Workload Automation SE Cross-Platform
Tracker (XTRK) active at this CAICCI Node for the Monitor name specified in the XTRK
startup parameters. Only one copy of XTRK can be active for a given monitor name at a
given CAICCI Node. The copy of XTRK issuing this message terminates.

Action:
Determine where the other copy of XTRK is executing. You may still have a copy of the
pre-Release 3.3 Tracker (CA7FMUNI) executing. If so, stop it and start the XTRK system.
Check to ensure the correct monitor name is specified in the XTRK parameters.

CAL2X927E

(tid) sss ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subfunction module has
encountered an error. The calling task is identified by tid. The subfunction is indicated
by sss (CCI, ENF and so forth). The specific function being performed is indicated by ffff
(INIT, TERM, and so forth. The return code (rr) and condition code (cc) from the error
are also indicated. A text description of the error is indicated by xxxx....xxxx. The calling
XTRK task may or may not terminate processing based upon the error encountered.
Other messages may follow this one.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 587

CAL2 Messages

CAL2X928E

(tid) ssss CALL FAILED: FUNC=ffff RC=rr CC=cc

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subfunction module has
encountered an internal error. The calling task is identified by tid.. The subfunction
module is indicated by ssss (CCIF, ENFF, and so forth). The specific function being
performed is indicated by ffff (INIT, TERM, and so forth). The return code (rr) and
condition code (cc) from the subfunction are also indicated. The calling XTRK task may
or may not terminate processing based on the error encountered. Other messages may
follow this one.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

CAL2X929E

XTRK xxxxxxxxxx FUNCTION ERROR: FUNC=ffff RC=rrrr CC=cccc

Reason:
A CA Workload Automation SE Cross-Platform Tracker (XTRK) subfunction module has
encountered an internal error processing a request from the main task. The subfunction
module is indicated by xxxx... (NODE TABLE, XEVT TABLE, or CA Workload Automation SE
SMF). The specific function being performed is indicated by ffff (internal numeric
function code). The return code (rrrr) and condition code (cccc) from the subfunction
are also indicated. The calling XTRK task may or may not terminate processing based on
the error encountered. Other messages may follow this one.

Action:
Review any preceding messages and take corrective actions indicated by them. If there
are no other messages, and the problem is impacting processing, contact CA Support at
ca.com/support for assistance.

588 Message Reference Guide

 CAL2 Messages

CAL2100I

- UNAUTHORIZED CA-7 OPERATOR ID

Reason:
A user attempted to log on to CA Workload Automation SE using an ID that was not
defined in the module that was named on the SECURITY statement in the product's
initialization file. The module is named at the NAME= position on the statement. Issued
by SASSSSEC.

Action:
Retry the logon using a different ID or define the ID in the security module.

CAL2101I

- LOGON FORMAT INCORRECT

Reason:
This message may be issued in the online environment when a /LOGON command is
attempted. The message may be issued in the batch environment in the event that the
command format does not conform to the syntax described for /LOGON in the
Command Reference Guide. Issued by SASSSSEC.

Action:
Correct the command and reenter.

CAL2102I

- LOGON REJECTED BY USER EXIT

Reason:
The logon attempt was rejected by SASSXXLX.

Action:
SASSXXLX is a user exit. It is NOT supplied with CA Workload Automation SE. Consult the
person responsible for maintenance of this exit at your site.

Chapter 2: AFM - CA7R Messages 589

CAL2 Messages

CAL2103I

- USER NOT AUTHORIZED FOR CA-7 COMMANDS

Reason:
The logon attempt was rejected because the user does not have sufficient authority to
execute CA Workload Automation SE commands. This condition may result even if the
USERID is valid in the external security system (for example, CA ACF2, CA Top Secret, or
IBM RACF). If COMMAND was not specified in the EXTERNAL= sublist on the SECURITY
statement in the product's initialization file, command security will be controlled
through the module named by the NAME= keyword on the SECURITY statement. Issued
by SASSSSEC.

Action:
If use of CA Workload Automation SE commands is to be secured using CA Workload
Automation SE native security, then USERIDs and security levels must be defined in the
CA Workload Automation SE security module. For more information, see the Security
Reference Guide.

CAL2120I

- UNRECOGNIZED TRANSACTION

Reason:
The command input did not match any entry in SASSTRAN. Issued by SASSSSEC.

Action:
Correct the command input and reenter.

CAL2122I

- OPERATOR NOT AUTHORIZED FOR APPLICATION

Reason:
This message is issued when CA Workload Automation SE native security is being used
to control command access. A command was attempted that belongs to an application
that is not associated with the user in the module named on the NAME= parameter of
the SECURITY statement in the product's initialization file. Issued by SASSSSEC.

Action:
If access to the command is needed, contact your installation security administrator.

590 Message Reference Guide

 CAL2 Messages

CAL2124I

- UNDEFINED TRANSACTION CODE

Reason:
The command input exceeded the maximum length allowable for a CA Workload
Automation SE transaction. Issued by SASSSSEC.

Action:
Correct the command input and reenter.

CAL2140I

- UNABLE TO LOAD SASSDSCR

Reason:
An error occurred attempting to load SASSDSCR. Issued by SASSSSEC during panel access
validation.

Action:
This is a serious error. Ensure that a usable copy of SASSDSCR resides on a library
accessible by CA Workload Automation SE.

CAL2141I

- UNRECOGNIZED ACCESS REQUEST

Reason:
A value was entered in the FUNCTION field of a CA Workload Automation SE panel that
was not defined in SASSDSCR. Issued by SASSSSEC during panel access validation.

Action:
Correct the command input and reenter.

Chapter 2: AFM - CA7R Messages 591

CAL2 Messages

CAL2142I

- INSUFFICIENT AUTHORITY FOR PANEL ACCESS

Reason:
The application access level for the user is insufficient for the type of access requested.
The level associated with the application to which the panel belongs is defined for the
user in the module named by the NAME= keyword on the SECURITY statement in the
product's initialization file. Issued by SASSSSEC during panel validation.

Action:
If access to the panel is needed, contact your installation security administrator.

CAL2143I

- PANEL NOT DEFINED

Reason:
Access was requested for a panel that is not defined in SASSDSCR. Issued by SASSSSEC
during panel validation.

Action:
Contact your installation specialist for assistance.

CAL2160I

- DATA SET ACCESS REJECTED (UID)

Reason:
Data set access was denied based on the UID associated with the user in the module
named on the NAME= parameter of the SECURITY statement in the product's
initialization file. This value was compared with the UID values associated with the data
set entries in the USERID module. Issued by SASSSSEC during data set access validation.

Action:
If access to the data set is needed, contact the person responsible for maintaining CA
Workload Automation SE security at your site.

592 Message Reference Guide

 CAL2 Messages

CAL2170I

- ACCESS DENIED BASED ON UID

Reason:
Access to database or queue information about the job was denied based on the UID
associated with the user in the module named on the NAME= parameter of the
SECURITY statement in the product's initialization file. This value was compared with the
UID value associated with the job on the DB.1 panel. Issued by SASSSSEC during job
access validation.

Action:
If access to the job is needed, contact the person responsible for maintaining CA
Workload Automation SE security at your site.

CAL2200E

CROSS-PLATFORM {ROUTER|TRACKER} IS NOT ACTIVE

Reason:
The Cross-Platform Scheduling router or tracker task is no longer active in the CA
Workload Automation SE address space. Refer to any preceding messages for
indications of errors that may have caused the router to terminate. This is issued as a
highlighted, nondeletable WTO. If the XPS router or tracker is manually restarted, the
WTO is automatically deleted.

Action:
Address any errors indicated by previous router messages. Restart the XPS router or
tracker manually using the /XTASK command, or recycle the CA Workload Automation
SE address space.

Chapter 2: AFM - CA7R Messages 593

CAL2 Messages

CAL2201I

CA7 DATA SET DSNBR IS OVER 9,900,000; COMMENCE CLEAN UP OF DSNAMES

Reason:
This highlighted and non-deletable warning message is issued once each time CA
Workload Automation SE assigns a data set DSNBR on or above 9,900,000 and CA
Workload Automation SE has not issued this WTO before. This implies that each time CA
Workload Automation SE is recycled, this WTO is issued if a data set DSNBR greater than
9,900,000 is assigned.

Action:
This warning message should prompt an examination of data sets defined to the CA
Workload Automation SE system, since only 100,000 numbers remain to be assigned.
Execute the CA Earl/CA Easytrieve report CA7xx701 to determine which data sets are
not referencing any jobs, and commence cleaning up data set entries.

CAL2202I

CA7 DATA SET DSNBR IS 9,999,999; RESETTING START COUNT TO 1 FOR DS DSNBRS

Reason:
The maximum data set DSNBR has been assigned, and the next assignment of a data set
DSNBR will be attempted from number 1. This message is issued as highlighted and
non-deletable. CA Workload Automation SE will not reassign a number that is currently
active. If the number is already active, CA Workload Automation SE will obtain the next
number and see if it is in use, and proceed to search until an unused number is found.
This may cause additional overhead for the operation that encountered the condition
since CA Workload Automation SE will search for an unused DSNBR and ensure it is not
active at the time of the DSNBR assignment.

Action:
This warning message should prompt an examination of data sets defined to the CA
Workload Automation SE system. Tools to assist in determining eligible data sets for
clean up include the XREF report on the SASSBK00 backup operation (must specify
OPT=XREF in the execution parameters), using command LDSN,DSN=,LIST=USERS (if no
users, the data set may be eligible), and the CA Earl/CA Easytrieve report CA7xx701.

594 Message Reference Guide

 CAXPS Messages

CAL2203E

CA7 EXHAUSTED ALL DS DSNBRS; EXAMINE AND TAKE ACTION TO FREE DS DSNBRS

Reason:
This highlighted and non-deletable error message indicates that there is no unused data
set DSNBR that may be assigned to a new data set defined in CA Workload Automation
SE. The current data set asking for a new number is denied the request. Until data set
DSNBRs are freed, no new data sets will be defined to CA Workload Automation SE.

Action:
Take immediate action to delete data sets that no longer need to be defined to CA
Workload Automation SE.

CAL2210E

DSN TABLE OVERFLOW; OUTPUT DSN NOT CAPTURED, DSN=xxxx...xxxx

Reason:
The internal table for completion processing has overflowed, and the information about
the named data set was lost. Only this creation of the data set and possibly requirement
posting were lost. The data set named in this message may cause a job to be triggered
or a requirement to be satisfied. You may need to manually demand or post a job or
requirement.

Action:
Contact your installation specialist for assistance.

CAXPS Messages
This section contains the CAXPS messages.

Chapter 2: AFM - CA7R Messages 595

CAXPS Messages

CAXPS801I

PARMLIST FORMAT IS 'TARGET-FLOW,TARGET-MONITOR,START-DATE/TIME

(YYYYDDDHHMMSSTH)'

Reason:
The Cross-Platform Scheduling Router (XPS) Feedback Utility program was invoked with
an invalid parameter list. This message (and CAXPS802I) follows message CAXPS902E
and describes the correct format of the parameter list.

Action:
Correct the parameter list and resubmit the Feedback Utility JCL.

CAXPS802I

ALL PARMS ARE OPTIONAL. PARTIAL START DATE/TIME CAN BE SPECIFIED (E.G.
1999063)

Reason:
The Cross-Platform Scheduling Router (XPS) Feedback Utility program was invoked with
an invalid parameter list. This message (and CAXPS801I) follows message CAXPS902E
and describes the correct format of the parameter list.

Action:
Correct the parameter list and resubmit the Feedback Utility JCL.

CAXPS902E

INVALID PARAMETER STARTING WITH (pppppppp) - ABORTING

Reason:
The Cross-Platform Scheduling Router (XPS) was engaged with a parameter list that
contained an invalid keyword or value. The invalid parameter/value is indicated by
pppppppp.

Action:
Correct the parameter in error and restart XPS.

596 Message Reference Guide

 CA7M Messages

CAXPS904E

UNABLE TO LOAD MODULE mmmmmmmm . RC=cccc

Reason:
The Cross-Platform Scheduling Router (XPS) was unable to load needed module into
storage during startup. The module name is indicated by mmmmmmmm. The system
return code from load is indicated by cccc.

Action:
Review the JCL for XPS and confirm the correct load library is in the STEPLIB DD or the
library is linklisted. If these are correct, the problem may be insufficient storage.
Increase the region size and try again.

CAXPS925E

tid TASK RECEIVED INVALID PARM LIST

Reason:
A Cross-Platform Scheduling Router (XPS) subtask was engaged with a missing or invalid
parameter list. The subtask ID is indicated by tid. The subtask terminates with a return
code of 16.

Action:
For assistance, contact CA Support at ca.com/support.

CAXPS950E

PRINT DD IS INVALID OR UNAVAILABLE

Reason:
The Cross-Platform Scheduling Router (XPS) has determined that the DD statement for
print output is either not defined or is invalid.

Action:
Review the requirements for the function being performed and correct the JCL.

CA7M Messages
This section contains the CA7M messages.

Chapter 2: AFM - CA7R Messages 597

CA7M Messages

CA7M0000

I mmmmmmmm(nnnn) #CCI Initialization completed for tttttttt

Reason:
#CCI initialization is complete for the task named at tttttttt. Possible values of tttttttt
are: MONITOR, ROUTER, and TRACKER. These are CA Workload Automation SE XPS
subtasks. The message is issued from the module named at mmmmmmmm, offset
nnnn.

Action:
None.

CA7M0001

I mmmmmmmm(nnnn) Task initializing for tttttttt

Reason:
The subtask named at tttttttt is starting. Possible values for tttttttt are MONITOR,
ROUTER, and TRACKER. The message is issued from the module named at
mmmmmmmm, offset nnnn.

Action:
None.

CA7M0002

I mmmmmmmm(nnnn) Task initialization complete for tttttttt

Reason:
Initialization is complete for the task named at tttttttt. Possible values for tttttttt are
MONITOR, ROUTER, and TRACKER. The message is issued from the module named at
mmmmmmmm, offset nnnn.

Action:
None.

598 Message Reference Guide

 CA7M Messages

CA7M0003

I mmmmmmmm(nnnn) CCI macro failure on tttttttt. Func was ffff. RC = nnnnnnnnn

Reason:
A CCI macro failure was detected on the subtask named at tttttttt. The function
attempted is named at ffff. The return code is reported at nnnnnnnn. The message is
issued from the module named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0004

I mmmmmmmm(nnnn) FDBVDESC:

Reason:
A CCI macro failure was detected. A description of the error follows FDBVDESC:. The
message is issued from the module named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0005

I mmmmmmmm(nnnn) STIMER issued for tttttttt. Interval is nnnnnnnnn

Reason:
An STIMER was issued for the task named at tttttttt. The interval for the STIMER is
reported as a hex value in hundredths of seconds. This value appears at nnnnnnnn. This
is only an informational message. The message is issued from the module named at
mmmmmmmm, offset nnnn.

Action:
None.

Chapter 2: AFM - CA7R Messages 599

CA7M Messages

CA7M0006

I mmmmmmmm(nnnn) Invalid numerics found in field length. Task: tttttttt

Reason:
Invalid data was detected in an XPS scheduling request. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0007

I mmmmmmmm(nnnn) Required keyword value not supplied. Task: tttttttt

Reason:
Invalid data was detected in an XPS scheduling request. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0008

I mmmmmmmm(nnnn) No space in L2CMAREA for keyword. Task: tttttttt

Reason:
The XPS scheduling request was not parsed successfully. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

600 Message Reference Guide

 CA7M Messages

CA7M0009

I mmmmmmmm(nnnn) No space in L2CMAREA for keyword value. Task: tttttttt

Reason:
The XPS scheduling request was not parsed successfully. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0010

I mmmmmmmm(nnnn) Invalid length for keyword value. Task: tttttttt

Reason:
The XPS scheduling request was not parsed successfully. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0011

I mmmmmmmm(nnnn) Invalid data in field. Field = ffffffff Task: tttttttt

Reason:
The parameters supplied in the XPS scheduling request did not provide valid values for
the CA Workload Automation SE scheduling command used to satisfy the request.
tttttttt is the subtask that detected the error. The message is issued from the module
named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 601

CA7M Messages

CA7M0012

I mmmmmmmm(nnnn) Data rejected from: nnnnnnnnnnnnnnnnnnnn. Task: tttttttt

Reason:
This message reports the origin of the invalid XPS scheduling request. tttttttt is the
subtask that detected the error. The message is issued from the module named at
mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0014

I mmmmmmmm(nnnn) nnnnnnnnn failed for tttttttt. RC: nnnnnnnnn

Reason:
This message reports a macro failure on the subtask named at tttttttt. The return code is
reported at nnnnnnnn. The message is issued from the module named at
mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

CA7M0015

I mmmmmmmm(nnnn) ATTACH successful for nnnnnnnn. TCB at tttttttt

Reason:
This message reports that an ATTACH task successfully initiated processing for the
module named at nnnnnnnn. The address of the task TCB is tttttttt. The message was
issued from mmmmmmmm at offset nnnn.

Action:
None.

602 Message Reference Guide

 CA7M Messages

CA7M0016

I mmmmmmmm(nnnn) L2CCISD waiting for post. Task: tttttttt

Reason:
This message reports that the task attaching the XPS ROUTER is waiting for input. This is
an informational message. The message was issued from mmmmmmmm at offset nnnn.

Action:
None.

CA7M0017

I mmmmmmmm(nnnn) L2CCISD posted CAXPSYSD. Task: tttttttt

Reason:
The XPS ROUTER has been posted for action. This is an informational message. The
message was issued from mmmmmmmm at offset nnnn.

Action:
None.

CA7M0018

E mmmmmmmm(nnnn) Error. LOC=xxxxxxxx R15=yyyyyyyy R0 = zzzzzzzz

Reason:
An error was detected by the module named at mmmmmmmm. The location within the
module is reported at xxxxxxxx. The values of R15 and R0 are also reported. The
message is issued from the module named at mmmmmmmm, offset nnnn.

Action:
Contact your installation specialist for assistance.

Chapter 2: AFM - CA7R Messages 603

CA7M Messages

CA7M0019

E mmmmmmmm(nnnn) Error scheduling command.

Reason:
An error occurred during the attempt to schedule an internal terminal command for
cross-platform scheduling. The most likely cause is an invalid logonid. The message is
issued from the module named at mmmmmmmm, offset nnnn.

Action:
Examine the browse data set for the DEMAND or RUN command that was issued for this
cross-platform scheduling request. An error message should be produced for the
command. See the discussion of the message in this guide.

CA7M0020

E mmmmmmmm(nnnn) Error. RC=xxxxxxxx

Reason:
An error was detected by the module named at mmmmmmmm. The error return code is
reported at xxxxxxxx. The message is issued by the module named at mmmmmmmm,
offset nnnn. For SASSTRX0 RC=4, a TRX terminal could not be obtained.

Action:
Contact your installation specialist for assistance. For SASSTRX0 RC=4, you may need to
add one or more TRX terminals to the product's initialization file. This would only be
needed if the message is issued frequently.

CA7M0022

I pppppppp (nnnn) : Request received for ffff. Task: tttttttt

Reason:
A request named at ffff was received for the subtask named at tttttttt. The message is
issued by the module named at pppppppp, offset (nnnn).

Action:
None.

604 Message Reference Guide

 CA7R Messages

CA7M0025

I pppppppp (nnnn) : RECEIVE posted.

Reason:
The CCI receiver for the XPS Manager was posted for work. The program that issued the
message is named at pppppppp, offset (nnnn).

Action:
None.

CA7M0026

I pppppppp (nnnn) : RECEIVE issued.

Reason:
The XPS Manager issued a CCI RECEIVE. The program that issued the message is named
at pppppppp; offset (nnnn).

Action:
None.

CA7R Messages
This section contains the CA7R messages.

CA7R.W600

ERROR ON LOOP ENQ

Reason:
Workload planning program SASSWRSU was not able to obtain a necessary enqueue.
The program terminates with a U0600 abend.

Action:
Wait a few moments and try again. If the program continues to fail, contact CA Support
at ca.com/support for assistance.

Chapter 2: AFM - CA7R Messages 605

CA7R Messages

CA7R.W606

INTERNAL ERROR DURING RESOURCE COUNT PROCESSING

Reason:
Workload planning program SASSWRSU encountered an internal error. The program
terminates with a U0606 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA7R.733

GET ERROR ON ACTIVE RCT RECORD CHAIN

Reason:
An error occurred trying to get an entry in the VRM RCT chain.

Action:
Possible timing problem exists. If the error persists, contact your installation specialist
for assistance.

CA7R.734

UPDATE ERROR ON ACTIVE RCT RECORD CHAIN

Reason:
An error occurred trying to update an entry in the VRM RCT chain.

Action:
Possible timing problem exists. If the error persists, contact your installation specialist
for assistance.

CA7R.735

NO RESOURCE COUNT RECORD MATCH WITH PROCESSING

Reason:
A VRM RCT entry was not found.

Action:
Possible timing problem exists. If the error persists, contact your installation specialist
for assistance.

606 Message Reference Guide

Chapter 3: CA-7.A - CA-7.X Messages
This chapter contains the CA-7.A through CA-7.X messages.

CA-7.AIIS Through CA-7.DT70 Messages

This topic contains the CA-7.AIIS through CA-7.DT70 messages.

CA-7.AIIS

- ERROR: text

Reason:
An ARF condition was detected for a job, but an error occurred. This message is
accompanied by one or more additional messages. text provides supplementary
information about the error.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

CA-7.AIIS

- INVALID SASSARHT ADDRESS

Reason:
CA Workload Automation SE was unable to locate a module needed for ARF monitoring.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 607

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.AIIS

- SQ ERROR AT xxxx ERR=cccc

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job. xxxx is the
offset in SASSAIIS where the error occurred.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

CA-7.AIIS

- UNABLE TO LOCATE ARF TRAILER.

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at http://ca.com/support for assistance.

CA-7.AIJC

ERROR: ARQM ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Reason:
An error occurred processing an ARF request. The R15, R0, and R1 values help to
determine the cause.

Action:
Contact your installation specialist for assistance. If R15=10 and R0=6, the original job
may have been canceled.

608 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.AIJC

- INVALID SASSARQM ADDRESS

Reason:
CA Workload Automation SE was unable to locate a module needed for ARF monitoring.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.AIJC

- JC ERROR FOR jjjjjjjj (nnnn)

Reason:
An ARF condition was detected for the job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

CA-7.AIJC

- SQ ERROR AT xxxx ERR=cccc

Reason:
An ARF condition was detected for a job, but an error occurred on a CA Workload
Automation SE queue access macro. ARF was unable to format information about the
error in the ARF trailer segment for the job. xxxx indicates the offset into SASSAIJC
where the error occurred.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 609

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.AIJC

- UNABLE TO LOCATE ARF TRAILER.

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

CA-7.AILE

- INVALID SASSARHT ADDRESS

Reason:
CA Workload Automation SE was unable to locate a module needed for ARF monitoring.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.AILS

- ERROR: text

Reason:
An ARF condition was detected for a job, but an error occurred. This message is
accompanied by one or more additional messages. text provides supplementary
information about the error.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

CA-7.AILS

- INVALID SASSARHT ADDRESS

Reason:
CA Workload Automation SE was unable to locate a module needed for ARF monitoring.

Action:
For assistance, contact CA Support at ca.com/support.

610 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.AILS

- SQ ERROR AT xxxx ERR=cccc

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at http://ca.com/support for assistance.

CA-7.AILS

- UNABLE TO LOCATE ARF TRAILER.

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at http://ca.com/support for assistance.

CA-7.AISC

- ERROR: text

Reason:
An ARF condition was detected for a job, but an error occurred. This message is
accompanied by one or more additional messages. text provides supplementary
information about the error.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 611

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.AISC

- INVALID SASSARHT ADDRESS

Reason:
CA Workload Automation SE was unable to locate a module needed for ARF monitoring.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.AISC

- SQ ERROR AT xxxx ERR=cccc

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at http://ca.com/support for assistance.

CA-7.AISC

- UNABLE TO LOCATE ARF TRAILER.

Reason:
An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.

Action:
Check the CA Workload Automation SE log for any additional error messages and
contact CA Support at http://ca.com/support for assistance.

CA-7.ARF0

- ERROR FOR JOB (nnnn): ARGR R15=xxxxxxxx R0=yyyyyyyy R1=zzzzzzzz. SET=ssssssss

Reason:
An error occurred while trying to locate the next ARF response in an ARFSET for a job.

Action:
For assistance, contact CA Support at ca.com/support.

612 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.ARF0

- ERROR FOR JOB (nnnn): UNABLE TO RESPOND TO cc CONDITION IN SET=ssssssss

Reason:
An error occurred while trying to respond to an ARF exception condition. The code
indicating the type of response to be executed was not recognized by SASSARF0.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.ARF0

ERROR FOR JOB (nnnn): ARQM R15=xxxxxxxx R0=yyyyyyyy R1=zzzzzzzz. SET=ssssssss

Reason:
An error occurred while trying to update the status of an ARF response in the ARF
queue.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.ARF0

ERROR FOR JOB (nnnn): RC FROM SASSTRX0 IS xxxxxxxx, SET=ssssssss.

Reason:
An error occurred while trying to schedule a command on a TRXDV terminal during a
response to an ARF exception.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 613

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.A001

- ARF Response job (nnnn) jjjjjjjj Type=cc Intercept=xxxx at hh:mm:ss.th

Reason:
This message is issued as part of the ARF response defined on an AM action statement.
The name and CA 7 WA job number of the job in ARF recovery is reported along with
the type of ARF exception condition detected. The intercept number indicates how
many exceptions of this type have been detected since the last startup of CA Workload
Automation SE.

Action:
None.

CA-7.A002

- (nnnn) TYPE=cc INDEX=ii

Reason:
This message is issued as part of the ARF response defined on an AM action statement.
The CA 7 WA job number of the job in ARF recovery is reported followed by an
indication of the type of exception condition detected. The index value is the value of
the DEFID of the condition definition containing the AM action statement.

Action:
None.

CA-7.A003

- (nnnn) ARF Set=ssssssss yyy/ddd hh:mm:ss.th

Reason:
This message is issued as part of the ARF response requested on an AM action
statement. The CA 7 WA job number of the job in ARF recovery is reported followed by
the name of the ARFSET in containing the AM action statement. The date and time
following the ARFSET name identifies the instance of the ARFSET definition that is used
for ARF monitoring.

Action:
None.

614 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.BSTR

BTERM FLAG RESET, MAY NEED TO RESUBMIT

Reason:
CA Workload Automation SE terminated while a batch terminal interface was active.
Issued by SASSBSTR.

Action:
Check that CA Workload Automation SE is active. Resubmit the SASSBSTR job. The
transactions from the preceding SASSBSTR run may already have been processed by CA
Workload Automation SE.

CA-7.BSTR-19

BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON CARD

Reason:
The current USERID is not authorized to submit for the OPERID in the /LOGON
statement.

Action:
Change either the USERID or the OPERID in the /LOGON statement. If the statement is
correct, check with the person who is responsible for security for CA Workload
Automation SE.

CA-7.BSTR-21

BATCH TERMINAL # x ALLOCATED.

Reason:
This informational message shows which BTI terminal is locked.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 615

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.BSTR-22

BATCH TERMINAL # x RELEASED.

Reason:
This informational message shows that the locked BTI terminal has been unlocked.

Action:
None.

CA-7.BSTR-28

UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE REPORTED.

Reason:
This message is issued when a user-defined BTI Message Table is available, but the DD
statement for the ERRORS file is not in the JCL. Normally, messages from the BTI
Message Table checking are routed to this ERRORS DD. Since this DD is not available, the
messages will not be produced. However, you will still get the CA-7.BSTR-30 WTO that
informs you how many table matches were made, and what the highest matched
condition code is.

Action:
Add a DD statement for ERRORS. The format is the same as the existing SYSPRINT DD.

CA-7.BSTR-29

* ERROR MSG TABLE MATCH (CC=ccc) : text

Reason:
An error was encountered, and the error file with a ddname of ERRORS could not be
opened. The error is described by text. The condition code set by the error is ccc.

Action:
Correct the error and resubmit the job. Ensure a proper ERRORS DD statement is
present in the job.

616 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.BSTR-30

ERROR MSGS FOUND IN OUTPUT. MSGS MATCHED =xxxxx, HIGH CC=ccc.

Reason:
One or more errors were encountered. The number of error messages that matched the
message table was xxxxx. The highest condition code encountered was ccc.

Action:
Correct the errors and resubmit the job.

CA-7.BTMV

xx yy tttttt VSAM IDS [(OPEN)|(CLOSE)] ACB FAILURE

Reason:
The OPEN or (CLOSE) for the VSAM IDS was unsuccessful. If xx=04, this indicates that the
VSAM IDS was not opened or closed in a normal way (such as when CA Workload
Automation SE abends rather than shuts down normally). No action is required. Another
CA-7.BTMV message should follow indicating the verify macro completed successfully.
Issued by SASSBTMV.

If xx=08 or greater, the pack on which the VSAM IDS resides may have had an I/O error.
If xx=08, the following are possible reasons for the error:
■ There was not enough space to do a normal VSAM OPEN (or CLOSE).
■ If a security package is being used, CA Workload Automation SE may not have
authorization to access the IDS.

Action:
If xx=08 or greater, CA Workload Automation SE will abend with a U0955 abend. If
xx=08, first verify the CWORK parameter value in the CA Workload Automation SE
Execution JCL. If the CWORK value is high enough, check for security package definitions
for the VSAM IDS to ensure that CA Workload Automation SE can access it. For more
information, see the Systems Programming Guide.

If none of the above applies, the IDS may need to be verified through IDCAMS or a
database recovery may need to be done.

Chapter 3: CA-7.A - CA-7.X Messages 617

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.BTMV

VERIFY MACRO COMPLETED SUCCESSFULLY

Reason:
This is an informational message following the previous CA-7.BTMV message indicating
an OPEN ACB failure. Issued by SASSBTMV.

Action:
None.

CA-7.BTMX

- ABEND xxxx IN SUBTASK (yyyyyyy ; zz)

Reason:
This WTO is produced if the CA Workload Automation SE subtask has abended. The
subtask is reinstated and the terminal in control that caused the abend is logged off. If it
is a virtual terminal, it is disconnected.

The xxxx is the abend code. The yyyyyyy is the terminal name. The zz is the code that the
SASSBTMX module uses to determine what processing to perform. More CA-7.BTMX
messages sometimes follow that display information about the PSW and the contents of
the SASSBTMX program registers.

Action:
CA Workload Automation SE stays up and running. Only the terminal user that issued
the command is disconnected. This user can log back on and can continue. Depending
on the command that was being processed at the time of the failure, storage may not
be freed or a data set may be left enqueued (for example, JCL panel getting an S913
abend due to security access).

CA-7.CCIL

Fast shutdown of SASSCCIL tasks started.

Reason:
A shutdown of CA Workload Automation SE XPS subtasks was requested.

Action:
None.

618 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CCIL

Fast shutdown of SASSCCIL tasks ended.

Reason:
The requested shutdown of CA Workload Automation SE XPS subtasks is completed.

Action:
None.

CA-7.CCIL

- No internal terminals for XPS SERVER requests.

Reason:
At least one terminal must be defined with DEVICE=TRXDV for use with cross-platform
scheduling.
Note: For more information about defining internal terminals, see the Systems
Programming Guide.

Action:
If cross-platform scheduling is to be used, ensure that at least one internal terminal is
defined and restart CA Workload Automation SE.

CA-7.CCIL

SEVERE ERROR; Could not locate SCT.

Reason:
An error occurred while trying to locate a system control block. The problem is likely
due to a storage overlay. CA Workload Automation SE abnormally terminates.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 619

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CCIL

- XPS SERVER requests will be rejected.

Reason:
No XPS SERVER facilities are available because no internal terminals have been defined.
Note: For information about defining internal terminals (DEVICE=TRXDV), see the
Systems Programming Guide.

Action:
If cross-platform scheduling is to be used, ensure that at least one internal terminal is
defined and restart CA Workload Automation SE.

CA-7.CDIO

- COMDS VOLUME STATUS HAS CHANGED. ICOM AND CA-7 MUST BE RECYCLED.

Reason:
This message is produced if the status changes for the disk drive containing the volume
on which the Communications data set resides. The particular status checked is the
share indication. Normally, this status will never change. However, one example of how
it can change is by doing a CPU split or merge operation.

Action:
CA Workload Automation SE and all the ICOMs must be stopped and restarted as soon
as possible. Any delays in doing this can cause SMF tracking information (that CA
Workload Automation SE puts in the Communications data set) to be lost.

620 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CHDO

PAGE ERROR FOR TERM xxxxxxx

Reason:
CA Workload Automation SE is unable to read a message from the scratch queue. The
message may have been written to the scratch queue incorrectly. Issued by SASSCHDO.

Action:
The WTO is informational and no action is required unless terminal xxxxxxx hangs. In
that case, we recommend the following steps:
1. Enter /STOP,T=xxxxxxx
2. Enter /PURGPG,LT=xxxxxxx
3. Enter /START,T=xxxxxxx

If the previous steps do not work, try starting CA Workload Automation SE with a
TYPE=ERST. It may be necessary to relink CA Workload Automation SE (N520 of install
jobs) to execute a DMPQ/MOVQ start up, or both.

CA-7.CHDO

MESSAGE ALREADY QUEUED FOR TERM xxxxxxx

Reason:
A message is trying to be processed for a terminal when one is already in process. Issued
by SASSCHDO.

Action:
The WTO is informational and no action is required unless terminal xxxxxxx hangs. In
that case, we recommend the following steps:
1. Enter /STOP,T=xxxxxxx
2. Enter /PURGPG,LT=xxxxxxx
3. Enter /START,T=xxxxxxx

If the previous steps do not work, try starting CA Workload Automation SE with a
TYPE=ERST.

Chapter 3: CA-7.A - CA-7.X Messages 621

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CMGR

SKIP TRAILER BLOCK

Reason:
During CA Workload Automation SE startup (after a power failure, cancel, and so forth),
an invalid block of trailer terminal commands was found in the communications data
set. Any commands in this block that were not processed prior to the previous CA
Workload Automation SE termination would be ignored.

Action:
None required, though it may be possible that one or more trailer commands will not be
processed.

CA-7.CPMA

FLOW ADD Error for xxxxxxxx ; Already on CRQ chain

Reason:
A logic error occurred during FLOW initiation for the FLOW named xxxxxxxx.

Action:
Contact your installation specialist for assistance.

CA-7.CPMA

FLOW ADD Error for xxxxxxxx ; Already on flow chain

Reason:
A logic error occurred during FLOW initiation for the FLOW named xxxxxxxx.

Action:
Contact your installation specialist for assistance.

CA-7.CPMA

FLOW ADD Error for xxxxxxxx RSPLFDBK=yyyyyyyy

Reason:
An I/O error occurred during FLOW initiation for the FLOW named xxxxxxxx. yyyyyyyy is
the VSAM feedback.

Action:
Contact your installation specialist for assistance.

622 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CPMA

FLOW ADD Error for xxxxxxxx ; Storage not available

Reason:
An error occurred during FLOW initiation for the FLOW named xxxxxxxx. A flow record
cannot be created in memory because of a shortage of available storage.

Action:
Contact your installation specialist for assistance.

CA-7.CPMA

FLOW fff Error for xxxxxxxx zzzzz RC=yyyyyyyy

Reason:
A queue I/O error occurred during FLOW initiation for the FLOW named xxxxxxxx. The
function is fff, zzzzz is the SQ macro that failed. yyyyyyyy is the SQ macro return code.

Action:
Contact your installation specialist for assistance.

CA-7.CPMA

Unable to track flow for xxxxxxxx

Reason:
An error occurred during FLOW initiation for the FLOW named xxxxxxxx. CA Workload
Automation SE cannot communicate information about the FLOW to CA OPS/MVS EMA.
This message is accompanied by one or more diagnostic messages that provide
additional information about the underlying error.

Action:
Contact your installation specialist with the output that includes these messages.

Chapter 3: CA-7.A - CA-7.X Messages 623

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.CPMP

- ffffff error -- xxxxxxxx (nnnn) in yyyyyyyy/zzzzzzzz (mmmm) yyyy.ddd hh:mm:ss.th

AA/rrrrrrrr

Reason:
An I/O error occurred while trying to update the FLOW record during FLOW purge
processing. ffffff is the function attempted. xxxxxxxx is the name of the job, (nnnn)
reports the CA Workload Automation SE job number. The name of the flow is yyyyyyyy
and zzzzzzzz is the name of the starting job in the flow. The CA Workload Automation SE
job number for the starting job is (mmmm). AA is a code used to locate where in
SASSCPMP the error was detected and rrrrrrrr is the VSAM feedback code.

Action:
Contact your installation specialist for assistance.

CA-7.CPMT

- Unable to track xxxxxxxx (nnnn) in yyyyyyyy/zzzzzzzz (mmmm) yyyy.ddd hh:mm:ss.th

AA/00000000

Reason:
An I/O error occurred during FLOW propagation. xxxxxxxx is the name of the job, (nnnn)
reports the CA Workload Automation SE job number. The name of the flow is yyyyyyyy
and zzzzzzzz is the name of the starting job in the flow. The CA Workload Automation SE
job number for the starting job is (mmmm). AA is a code used to locate where in
SASSCPMT the error was detected and rrrrrrrr is the VSAM feedback code.

Action:
Contact your installation specialist for assistance.

CA-7.DRVR

- AUTOMATIC WARM (ERST) START IN PROCESS.

Reason:
An automatic restart has been specified in the driver control statement. The driver is
automatically restarting CA Workload Automation SE. Issued by SASSDRVR.

Action:
None.

624 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DRVR

- CA-7 ENDED WITH A xyyyy

Reason:
This message appears after CA Workload Automation SE terminates and the driver
receives control. x is either an S for a system abend or a U for user abend or condition
code. Issued by SASSDRVR.

Action:
If an automatic restart has been specified, then CA Workload Automation SE will
automatically be restarted. If an automatic restart has not been specified or this
termination is subsequent to an automatic restart, then the driver will require an
operator response for restarting or stopping.

CA-7.DRVR

- DRIVER SUBTASK ENDED.

Reason:
The Driver subtask ended.

Action:
See the following CA-7.DRVR EOT for TCB message.

CA-7.DRVR

- EOT FOR TCB AT nnnnnnnn TCBCMPF=nnnnnnnn L2DRVA_TCB-nnnnnnnn

SCTADDR=nnnnnnnn TERMnnnn.

Reason:
JCL syntax invoked and error occurred.

Action:
Contact your installation specialist for assistance.

CA-7.DRVR

- INVALID PARM= OR DRVRIN DATA

Reason:
Either the PARM data on the EXEC statement for the CA Workload Automation SE driver
is invalid or data supplied on the driver control statement is incorrect. A U101 abend
accompanies this message. Issued by SASSDRVR.

Chapter 3: CA-7.A - CA-7.X Messages 625

CA-7.AIIS Through CA-7.DT70 Messages

Possible problems include the following:

■ No PARM specified.
■ TYPE=xxxx omitted from the PARM data.
■ Too much PARM data.
■ Unable to open DRVRIN.
■ No *DRVR* control statement.
■ Invalid control statement data.

Action:
Correct and resubmit the job.

CA-7.DRVR

- OK.

Reason:
The driver acknowledges that the chosen restart option is valid. The driver is restarting
CA Workload Automation SE. Issued by SASSDRVR.

Action:
None.

CA-7.DRVR

- SELECT A RESTART (TYPE=) OPTION (FORM,COLD,MOVQ,WARM,ERST,STOP)

Reason:
This message indicates the driver is waiting for input to start or restart CA Workload
Automation SE. This message appears for the initial start of CA Workload Automation SE
under the driver and for all subsequent restarts. Issued by SASSDRVR.

Action:
Reply one of the following:
■ FORM - For a CA Workload Automation SE format queue restart.
■ COLD - For a CA Workload Automation SE cold start.
■ WARM - For a CA Workload Automation SE warm start.
■ ERST - For a CA Workload Automation SE emergency restart.
■ MOVQ - To reload the queues from a previous /SHUTDOWN,DMPQ.
■ STOP - To terminate the driver.

626 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DRVR

- SHUTDOWN IN PROGRESS

Reason:
The driver acknowledges that the STOP option has been chosen. The driver is shutting
down. Issued by SASSDRVR.

Action:
None.

CA-7.DRVR

- THE CA-7 DRIVER IS ACTIVE. xxx...x

Reason:
This initial message indicates that the driver is active. xxx...x is the 40 bytes of comments
from the driver control statement. Issued by SASSDRVR.

Action:
None.

CA-7.DRVR

- UNABLE TO END SUBTASK, R1 = L2DRVA_TCB

Reason:
An attempt was made to detach the CA Driver subtask, but an internal control block
mismatch occurred.

Action:
Contact your installation specialist for assistance.

CA-7.DT60-01

UNABLE TO OPEN SYSPRINT FILE

Reason:
The open failed for the SYSPRINT output file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

Chapter 3: CA-7.A - CA-7.X Messages 627

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT60-01

VSAM PROCESSING ERROR RC=xx FDBK=yyyy

Reason:
Nonzero return code from VSAM.

Action:
See the IBM manual DFSMS Macro Instructions for Data Sets for the return code and
feedback codes listed in this message.

CA-7.DT60-02

UNABLE TO OPEN JOBREPT REPORT FILE

Reason:
The open failed for the JOBREPT output file.

Action:
Examine the DD statement for correct values, including spelling to the ddname.

CA-7.DT60-03

UNABLE TO OPEN SYSIN FILE

Reason:
The open failed for the SYSIN input file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

CA-7.DT60-05

ERROR READING RESOURCE FILE (CA7RSRC).

Reason:
The read of the resource file gave a nonzero return code.

Action:
None.

628 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT60-06

SYSIN CONTROL CARDS ARE REQUIRED.

Reason:
At least one SYSIN control statement is required.

Action:
Code valid control statements.

CA-7.DT60-06

INVALID CONTROL CARD SPECIFIED.

Reason:
First character of control statement is blank.

Action:
Code valid command in first column.

CA-7.DT60-07

INVALID CONTROL CARD SPECIFIED.

Reason:
Control statement did not specify JOB= in first four positions or first character after JOB=
not alpha.

Action:
Check for correct spelling of keyword. Check for correct operand; must have at least one
character if using generic that is JOB=A*.

CA-7.DT60-08

UNABLE TO OPEN RESREPT REPORT FILE.

Reason:
The open failed for the RESREPT output file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

Chapter 3: CA-7.A - CA-7.X Messages 629

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT60-08

UNRECOGNIZED PARM VALUE SPECIFIED.

Reason:
PARM not 'REPORT', 'ALLJOBS', or both.

Action:
Check for correct spelling of PARMs.

CA-7.DT62-01

REPORT PARAMETER PROCESSED

Reason:
The REPORT parameter was specified for the job run.

Action:
None. The parameter was accepted.

CA-7.DT62-02

INVALID PARAMETERS, REPORT RUN ONLY

Reason:
Parameters other than REPORT or PASSWORD were specified for the job run.

Action:
Enter REPORT or PASSWORD (not both), or do not specify a parameter value. For more
information, see the Database Maintenance Guide.

CA-7.DT62-03

PASSWORD PARAMETER PROCESSED

Reason:
The PASSWORD parameter was specified for the job run.

Action:
None. The parameter was accepted.

630 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT62-04

PASSWORD PARAMETER MUST BE SPECIFIED BY ITSELF, ONLY A REPORT WILL BE

GENERATED

Reason:
Both the PASSWORD and REPORT parameters were specified for the job run.

Action:
Enter REPORT or PASSWORD (not both), or do not specify a parameter value. For more
information, see the Database Maintenance Guide.

CA-7.DT62-05

VSAM PROCESSING ERROR RC=xx FDBK=yyyy

Reason:
A nonzero return code from VSAM was returned.

Action:
See the IBM manual DFSMS Macro Instructions for Data Sets for the return code and
feedback code listed in this message.

CA-7.DT62-06

ERROR READING RESOURCE FILE (CA7RSRC).

Reason:
The program could not open or read the file specified in the CA7RSRC DD statement.

Action:
Validate the file pointed to by the CA7RSRC statement exists and is used by CA
Workload Automation SE. For more information, see the Database Maintenance Guide.

CA-7.DT62-07

UNABLE TO OPEN DT62INPT INPUT FILE

Reason:
A DD statement, DT62INPT, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the DT62INPT file. For more information, see the
Database Maintenance Guide.

Chapter 3: CA-7.A - CA-7.X Messages 631

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT62-08

UNABLE TO OPEN DT62NODE OUTPUT FILE

Reason:
A DD statement, DT62NODE, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the DT62NODE file. For more information, see the
Database Maintenance Guide.

CA-7.DT62-09

UNABLE TO OPEN DT62XPWD OUTPUT FILE

Reason:
A DD statement, DT62XPWD, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the DT62XPWD file. For more information, see the
Database Maintenance Guide.

CA-7.DT62-10

UNABLE TO OPEN NODEREPT OUTPUT FILE

Reason:
A DD statement, NODEREPT, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the NODEREPT file. For more information, see the
Database Maintenance Guide.

CA-7.DT62-11

UNABLE TO OPEN NMTCHRPT OUTPUT FILE

Reason:
A DD statement, NMTCHRPT, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the NMTCHRPT file. For more information, see the
Database Maintenance Guide.

632 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT62-12

UNABLE TO OPEN NODPREPT OUTPUT FILE

Reason:
A DD statement, NODPREPT, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the NODPREPT file. For more information, see the
Database Maintenance Guide.

CA-7.DT62-13

UNABLE TO OPEN OWNPREPT OUTPUT FILE

Reason:
A DD statement, OWNPREPT, is missing from the JCL.

Action:
Provide the JCL necessary to allocate the OWNPREPT file. For more information, see the
Database Maintenance Guide.

CA-7.DT70-20

UNABLE TO OPEN SYSPRINT FILE.

Reason:
The open failed for the SYSPRINT output file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

CA-7.DT70-21

UNABLE TO OPEN ARFREPT REPORT FILE.

Reason:
The open failed for the ARFREPT output file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

Chapter 3: CA-7.A - CA-7.X Messages 633

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT70-22

UNABLE TO OPEN SYSIN FILE.

Reason:
The open failed for the SYSIN input file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

CA-7.DT70-23

UNABLE TO OPEN DT70ADDS FILE.

Reason:
The open failed for the DT70ADDS output file.

Action:
Examine the DD statement for correct values, including spelling of the ddname.

CA-7.DT70-24

SYSIN CONTROL CARDS ARE REQUIRED.

Reason:
At least one SYSIN control statement is required.

Action:
Code valid control statements.

CA-7.DT70-25

INVALID CONTROL CARD SPECIFIED.

Reason:
First character of control statement is blank.

Action:
Code valid command in first column.

634 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT70-26

INVALID CONTROL CARD SPECIFIED.

Reason:
Control statement did not specify ARFSET= in first position or ARFSET= is not alpha.

Action:
Check for correct spelling of keyword. Check for correct operand.

CA-7.DT70-27

UNRECOGNIZED PARM VALUE SPECIFIED.

Reason:
PARM not 'REPORT', 'ALLSETS', or both.

Action:
Check for correct spelling of PARMS.

CA-7.DT70-28

INVALID DEFINITION TYPE FOUND.

Reason:
The current ARFSET contains a definition with an invalid definition TYPE. Message
CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-30

INVALID ENTRY MODE REL OPER FOUND.

Reason:
The current ARFSET contains a definition with an invalid relative operator code for the
entry mode type.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

Chapter 3: CA-7.A - CA-7.X Messages 635

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT70-31

INVALID RESTART REL OPER FOUND.

Reason:
The current ARFSET contains a definition with an invalid relative operator code for the
restart mode.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-32

INVALID ENTRY MODE FOUND.

Reason:
The current ARFSET contains a definition with an invalid entry mode specification.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-33

ERROR RETURN FROM REPORT MODULE-SASSDT72.

Reason:
The ARF DBT subfunction module SASSDT72, which prints information about the current
ARFSET, returned an error.

Action:
Correct the ARFSET definition in error and rerun the job.

636 Message Reference Guide

 CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT70-34

ERROR LOADING REPORT MODULE-SASSDT72.

Reason:
The ARF DBT subfunction module SASSDT72 could not be loaded.

Action:
Ensure that the CA Workload Automation SE load library is accessible, and the job is
running with a large enough REGION specification.

CA-7.DT70-35

ERROR LOADING DATE CONVERTER - L2DATES.

Reason:
The ARF DBT subfunction module L2DATES could not be loaded.

Action:
Ensure that the CA Workload Automation SE load library is accessible, and the job is
running with a large enough REGION specification.

CA-7.DT70-36

ERROR CONVERTING DATE ENCOUNTERED.

Reason:
The current ARFSET contains an invalid date specification.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-37

ERROR CONVERTING TIME ENCOUNTERED.

Reason:
The current ARFSET contains an invalid time specification.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

Chapter 3: CA-7.A - CA-7.X Messages 637

CA-7.AIIS Through CA-7.DT70 Messages

CA-7.DT70-38

INVALID RESPONSE TYPE ENCOUNTERED.

Reason:
The current ARFSET contains a definition with an invalid response type specification.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-39

INVALID DISPOSITION TYPE ENCOUNTERED.

Reason:
The current ARFSET contains a definition with an invalid disposition type specification.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

CA-7.DT70-40

INVALID CONDITION CODE ENCOUNTERED.

Reason:
The current ARFSET contains a definition with an invalid condition code specification.

Message CA-7.DT70-49 follows indicating the current ARFSET and definition.

Action:
Correct the ARFSET definition in error and rerun the job.

638 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.DT70-49

ERROR ARFSET: xxxxxxxx DEFID: nnn

Reason:
This message indicates the current ARFSET (xxxxxxxx) and Definition ID (nnn) in which an
error has been detected.

Action:
See the preceding specific error message. Correct the ARFSET definition in error and
rerun the job.

CA-7.DT70-50

ERROR READING ARFSET FILE (CA7ARFDB).

Reason:
An error occurred attempting to read the ARFSET file.

Action:
Confirm that the CA7ARFDB DD statement points to a valid CA Workload Automation SE
ARF VSAM file.

CA-7.D32V Through CA-7.VDB0 Messages

This topic contains the CA-7.D32V through CA-7.VDB0 messages.

CA-7.D32V

FREE FOR VTAM VIRTUAL ENTRY FAILED

Reason:
Unable to find current terminal entry in logon ID table. Issued by SASSD32V.

Action:
If error persists, contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 639

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.D32V

MESSAGE ALREADY QUEUED

Reason:
CA Workload Automation SE has automatically corrected an internal control block
pointer error. This is an informational message.

Action:
None.

CA-7.D32V

(xx,yy) SYN CLSDST FOR xxxxxxx

Reason:
A VTAM CLSDST macro has been issued for terminal xxxxxxx. xx and yy represent the
return codes from registers 15 and 0 respectively. Issued by SASSDRVR. The message is
in response to a requested disconnection of the terminal from the CA Workload
Automation SE application.

Action:
None.

CA-7.FBAT

EXTRANEOUS DATA BYPASSED

Reason:
The input to a batch terminal contains a transaction that is too large.

Action:
Check the batch terminal input. Make sure there are no continuation indicators in
column 72 except on transactions where it is valid.

640 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.FXTM

EXTRANEOUS DATA BYPASSED

Reason:
Program SASSFXTM encountered more data than it could handle. The data is truncated.

Action:
This may or may not be a problem. Check the CA Workload Automation SE log for any
additional error messages and, if necessary, contact CA Support at ca.com/support for
assistance.

CA-7.HALT

- REQUESTING SASSCCIL TERMINATION.

Reason:
CA Workload Automation SE XPS subtask termination is requested. This occurs as part of
normal CA Workload Automation SE shutdown.

Action:
None.

CA-7.HALT

- REQUESTING SHUTDOWN OF PROBLEM MANAGEMENT SUBTASK

Reason:
The problem management subtask is shut down during normal termination of CA
Workload Automation SE.

Action:
None.

CA-7.HALT

- REQUESTING XPS ROUTER TERMINATION

Reason:
The XPS Router subtask is shut down during normal termination of CA Workload
Automation SE.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 641

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.HALT

- REQUESTING XPS TRACKER TERMINATION

Reason:
The XPS Tracker subtask is shut down during normal termination of CA Workload
Automation SE.

Action:
None.

CA-7.HLTD

- ALLVSAM ERROR ATTEMPTING TO DISCON/FINISH, RC=xxxx

Reason:
Errors occurred while attempting to initialize, connect, disconnect or finish with an
ALLVSAM database. RC value gives error code that is further explained by WTO
messages. Issued by SASSHLTD.

Action:
None. System will continue shutdown process.

CA-7.IARE

- ARF HOOK PROCESSING ACTIVATED

Reason:
The CA Workload Automation SE startup parameters included a 'RESTART,ARF=YES' or
'RESTART,ARF=MAINT' control statement requesting ARF processing. The ARF Hook Test
Tables have been acquired and initialized.

Action:
None.

642 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IARE

- ARF HOOK PROCESSING WILL NOT BE USED

Reason:
The CA Workload Automation SE startup parameters indicated ARF hook processing
would not be used. The ARF Hook Test Tables were not built.

Action:
None.

CA-7.IARE

- ARF DATA BASE WILL NOT BE USED

Reason:
The CA Workload Automation SE startup parameters indicated not to use ARF.

Action:
None.

CA-7.IARE

- ARF ENVIRONMENT HAS BEEN INITIALIZED

Reason:
The CA Workload Automation SE startup parameters included a 'RESTART,ARF=YES' or
'RESTART,ARF=MAINT' control statement requesting ARF processing. All ARF control
blocks are built, and the ARF database is OPEN and ready for processing.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 643

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IARE

- ERROR: RC=xxxx RS=rrrr INF=iiii

Reason:
An error occurred during ARF environmental initialization. The return, reason, and
information codes define the problem exactly. See the list of return codes that follows.

Action:
RC=04
GETMAIN failed for AVT. The AVT is not initialized. Retry later.
RC=08
SASSTMNT table handler routine is not available. Job table was not initialized.
RC=12
SASSTMNT failed to initialize job table.
RC=16
GETMAIN failed for HTT. ARF HTT not initialized. Retry later.
RC=20
GETMAIN failed for ARF statistics area. Retry later.
RC=24
SASSTMNT table handler not available. Not initialized.
RC=28
SASSTMNT failed to initialize an HTTE's table area.
RC=32
'ARFIO STARTUP' failed.
RC=36
'ARFIO INIT' failed.
RC=40
'ARFIO SEQ' failed.
RC=44
'ARFIO GETNEXT' failed.
RC=48
GETMAIN failed for AAR. ARF active queue is not rebuilt.

644 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

RC=52
'ARFIO ENDREQ' failed.
RC=56
LOAD EP=SASSARJI failed.
RC=60
LOAD EP=SASSARHT failed.
RC=64
LOAD EP=SASSARJP failed.
RC=68
LOAD EP=SASSARQM failed.
RC=72
LOAD EP=SASSARGR failed.
RC=76
LOAD EP=SASSARMS failed

CA-7.IARI

- ARF DATA BASE IS NOW ONLINE

Reason:
The CA Workload Automation SE startup parameters included a 'RESTART,ARF=YES' or
'RESTART,ARF=MAINT' control statement requesting ARF processing. The ARF database
is required for ARF to process. This message indicates the entire ARF database access
environment has been built, and the ARF DB is ready for access.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 645

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IARI

- ARF DB INIT ERROR: RC=xxxx RS=rrrr INF=iiii

Reason:
An error has occurred during ARF database startup. The return, reason, and information
codes define the problem exactly. See the list of return codes that follows.

Action:
In all probability the ARF database is not operational. ARF processing will be disabled for
this execution of CA Workload Automation SE.
RC=0004
The ARF database was already open.
RC=0008
The ARF I/O routine, SASSARIO, was not loaded.
RC=0012
GETMAIN for ARF ACB failed.
RC=0016
GENCB BLK=ACB for ARF DB ACB failed.
RC=0020
Issued by 'ARFIO STARTUP' macro when this module not found.
RC=0024
GETMAIN for an ARFIO (AIO) area failed.
RC=0028
GETMAIN for an ARFIO (AIO) buffer failed.
RC=0032
GETMAIN for an ARFIO (AIO) RPL failed.
RC=0036
GENCB for an ARFIO (AIO) RPL failed.
RC=0040
RDJFCB failed for ARF database ddname.

646 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

RC=0044
LOCATE for ARF database DSN failed.
RC=0048
MVS Catalog record for ARF database cluster was found, but a problem was
detected. The reason code clarifies the problem:
RS=1
Catalog entity has no NAME field.
RS=2
ARF database is not a VSAM Cluster.
RS=3
ARF database is VSAM, but has no components.
RS=4
The primary ASSOC entity is not a Data component.
RS=5
The primary ASSOC entity has no NAME field.
RC=0052
LOCATE for ARF database VSAM data component failed.
RC=0056
MVS Catalog record for ARF database data component as found, but a problem was
detected. The information code clarifies the problem:
INF=1
Catalog entity has no High Used RBA field.
RC=0060
MODCB for ARF DB ACB STRNO=1 (Load processing) failed.
RC=0064
OPEN for Load (Create) failed.
RC=0068
GETMAIN for Load RPL failed.
RC=0072
GENCB for Load RPL failed.

Chapter 3: CA-7.A - CA-7.X Messages 647

CA-7.D32V Through CA-7.VDB0 Messages

RC=0076
PUT for initial (create) record failed.
RC=0080
CLOSE from Load (Create) failed.
RC=0084
MODCB for ARF DB ACB STRNO=max (return to normal) failed.
RC=0088
Normal OPEN for ARF database had a problem. The reason code is OPEN's return
code:
RS=4
Warning message was issued, but ARF DB is OPEN.
RS=8
ARF DB OPEN failed.
The information code is OPEN's reason code:
INF=104
VSAM timestamp in ARF DB does not match timestamp in ICF catalog (volume
restore has occurred).
INF=128
CA7ARFDB DD is missing or invalid.
INF=136
CA Workload Automation SE REGION size is too small to OPEN.
INF=168
ARF DB is currently OPEN for update by another address space.

CA-7.IARR

- ERROR LOCATING ARF SEGMENT FOR jjjjjjjj (nnnn)

Reason:
Program SASSIARR could not locate the ARF segment for job jjjjjjjj with job number
nnnn.

Action:
For assistance, contact CA Support at ca.com/support.

648 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IARR

- SASSIARR PROCESSING BYPASSED.

Reason:
Only part of the ARF initialization processing has been done. This is normal if the CA
Workload Automation SE startup parameters included a RESTART control statement
with ARF=NO or ARF=MAINT.

Action:
Check for previous error messages, and make necessary corrections.

CA-7.IARR

- SASSARJI ERROR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz jjjjjjjj (nnnn)

Reason:
Program SASSIARR called program SASSARJI, which sent back a return code greater than
4. The contents of SASSARJI's registers 15, 0, and 1 are shown by xxxxxxxx, yyyyyyyy, and
zzzzzzzz, respectively. The job name is jjjjjjjj and the job number is nnnn.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IARR

- SQGET ERROR ON qqqqqqqq QUEUE, R15=xxxx AT +nnnn

Reason:
An attempt failed when reading a record from the qqqqqqqq queue. The return code
from SQGET is xxxx. The offset into program SASSIARR is nnnn.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 649

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IARR

- xxxxx ARF TRAILERS FOUND ON qqqqqqqq QUEUE, yyyyy RECONNECTED.

Reason:
If ARF is used, CA Workload Automation SE reads the queues at initialization and
attempts to locate all jobs using ARF that ARF was monitoring at the time of the last
/SHUTDOWN. To determine the jobs, CA Workload Automation SE reads the request,
ready and active queues. To resume ARF monitoring for a job, CA Workload Automation
SE must relocate the ARFSET that it used at the time of the /SHUTDOWN. When the
ARFSET is relocated, the job is said to be reconnected.
In this message, the name of the queue read is qqqqqqqq. The number of jobs found on
the queue that was monitored at the time of the last /SHUTDOWN is xxxxx The number
of jobs for which ARF resumed monitoring is yyyyy.

Action:
None.

CA-7.IARR

- xxxx JOBS ON qqqqqqqq QUEUE, yyyyy JOBS USING ARF.

Reason:
If ARF is used, CA Workload Automation SE reads the queues at initialization and
attempts to locate all jobs using ARF that ARF was monitoring at the time of the last
/SHUTDOWN. To determine the jobs, CA Workload Automation SE reads the request,
ready, and active queues.
In this message, the name of the queue read is qqqqqqqq. The number of jobs found on
the queue is xxxxx. The number of jobs monitored by ARF is yyyyy.

Action:
None.

CA-7.ICM1-90

NCF NODE TABLE NOT DEFINED - IPL REQUIRED

Reason:
The NCF node control table was not found. ICOM continues without NCF support active.

Action:
The ICOM reply NCF=YES can only be entered if NCF is properly installed.

650 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.ICM1-91

NETWORK COMMUNICATION FACILITY NOT ACTIVE

Reason:
The CA Workload Automation SE NCF interface is not active. This is an informative
message only. Processing continues without NCF support active.

Action:
None, unless NCF should be active. If so, it should be started.

CA-7.ICM1-92

NCF IS PRESENT - LOCAL NODE=xxxxxxxx

Reason:
The CA Workload Automation SE NCF interface is active with your installation's node ID
as shown. Processing continues.

Action:
None.

CA-7.IFOR

- WARNING! CA-7 QUEUES SHOULD RESIDE ON DEVICES OF THE SAME TYPE

Reason:
CA Workload Automation SE issues this message if all nine queue data sets do not reside
on the same device type (different volumes are all right, but the device type must be the
same).

Action:
CA Workload Automation SE can issue the message (and it is all right) if you are using
VIO feature for the SCRQ and DQTQ and if VIO data sets are allocated on a different
device type. If all the non-VIO queue data sets do not reside on the same device type,
serious errors could result including U0710, U0305, and S0C3.

Chapter 3: CA-7.A - CA-7.X Messages 651

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJCK

- AUTOPROC OPTION SPECIFIED BUT USER HAS SYSPROC DD.

Reason:
The AUTOPROC option is not allowed if the DD statement for SYSPROC is found.

Action:
If the AUTOPROC option is wanted, remove the SYSPROC DD statement from the CA
Workload Automation SE startup PROC.

CA-7.IJCK

- AUTOPROC OPTION SPECIFIED BUT USER NOT AUTHORIZED.

Reason:
The AUTOPROC option is allowed only if CA Workload Automation SE is APF authorized.

Action:
If the AUTOPROC option is wanted, make certain that CA Workload Automation SE is
APF authorized.

CA-7.IJCK

- AUTOPROC OPTION SPECIFIED BUT USER NOT JES2.

Reason:
The AUTOPROC option is allowed only if CA Workload Automation SE is running in a JES2
environment.

Action:
Remove the AUTOPROC option from the options file.

CA-7.IJCK

- BUFSIZE VALUE INVALID, DEFAULT USED

Reason:
The value specified exceeded the allowable buffer size. The default value of 100 is used.

Action:
Correct the BUFSIZE value for the next run.

652 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJCK

- CA-JCLCHECK LOADED.

Reason:
The CA JCLCheck full interface is loaded and will be used for syntax checking.

Action:
None.

CA-7.IJCK

- ERROR IN JCLCHECK USER OPTIONS AT POSITION xxx ON CARD yyy .

Reason:
An error occurred during processing CA JCLCheck user options at the specified position
(counting from column 1) on the statement indicated. Processing continues with the
next option.

Action:
Correct indicated errors and rerun.

CA-7.IJCK

- JCLCHECK COMMON COMPONENT INTERFACE LOADED.

Reason:
The JCLCHECK common component interface module CAZ2CJCL is loaded and will be
used for JCL syntax checking.

Action:
None.

CA-7.IJCK

- JCLCHECK INTERFACE BUFFER SIZE IS nnnnn .

Reason:
The nnnnn value indicates the buffer size used by the JCLCHECK interface.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 653

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJCK

- MAXIMUM NUMBER OF CA-7/CA-JCLCHECK INTERFACE USERS IS nnnnn .

Reason:
This message is produced when the MAXUSERS parameter is coded.

Action:
None.

CA-7.IJCK

- MAXUSERS SPECIFIED ZERO VALUE.

Reason:
MAXUSERS=0 was coded on the JCLCHECK statement. The interface is effectively
disabled.

Action:
If a MAXUSERS limit is wanted, code a nonzero value on the keyword.

CA-7.IJCK

- MULTIPLE JCLCHECK STATEMENTS IGNORED.

Reason:
More than one JCLCHECK statement was found in the initialization file of CA Workload
Automation SE. Only the first one is honored. Issued by SASSIJCK.

Action:
Remove the extraneous JCLCHECK statements.

CA-7.IJCK

- MULTIPLE KEYWORDS IGNORED. KW=xxxxxxxx.

Reason:
Multiple occurrences of the same JCLCHECK statement keyword were encountered.
Only the first occurrence is honored.

Action:
Remove the extraneous JCLCHECK statement keywords.

654 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJCK

- NO MAXUSERS VALUE SPECIFIED.

Reason:
This message is produced when the MAXUSERS parameter is not coded.

Action:
None.

CA-7.IJCK

- NO SYSPROC/AUTOPROC, INTERFACE DISABLED.

Reason:
The SYSPROC DD statement was not found in the CA Workload Automation SE startup
PROC, and AUTOPROC was not a valid specification. The CA Workload Automation SE CA
JCLCheck interface is disabled.

Action:
Perform one of the following actions:
■ Code a SYSPROC DD statement in the CA Workload Automation SE startup PROC
pointing to your installation procedure libraries.
■ Code AUTOPROC in the options file.

CA-7.IJCK

- REQUIRED SYSPROC DD NOT FOUND

Reason:
A SYSPROC DD statement was not coded in the CA Workload Automation SE startup
procedure, and the AUTOPROC option is not used. The interface is disabled.

Action:
Perform one of the following actions:
■ Add a SYSPROC DD statement to the CA Workload Automation SE startup JCL.
■ Add an AUTOPROC option to the initialization file.

Chapter 3: CA-7.A - CA-7.X Messages 655

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJCK

- SEVERE ERROR PROCESSING USER OPTIONS.

Reason:
An error occurred processing CA JCLCheck user options. Processing terminated.

Action:
Examine the options file for syntax errors and rerun.

CA-7.IJCK

- THE FOLLOWING JCLCHECK OPTIONS IN EFFECT :

Reason:
This message is a summary of the CA JCLCheck options that are used when JCLCHECK is
called from the interface. Another CA-7.IJCK message listing the CA JCLCheck option in
effect follows this message.

Action:
None.

CA-7.IJCK

- UNABLE TO LOAD JCLCHECK, INTERFACE DISABLED.

Reason:
The JCLCHECK module could not be loaded. The interface is disabled.

Action:
Verify that the JCLCHECK module is resident or in a library in the STEPLIB concatenation
for CA Workload Automation SE.

CA-7.IJCK

- UNABLE TO OPEN DDNAME=xxxxxxxx, KEYWORD BYPASSED.

Reason:
An attempt to OPEN the JCLCHECK options file failed.

Action:
Verify that the name on the DD statement defining the options file matches the
DDNAME parameter on the JCLCHECK statement.

656 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJLM-01

- NO STORAGE AVAILABLE

Reason:
No storage was available to construct a JCL table entry.

Action:
CA Workload Automation SE abnormally terminates with a U0001. Increase the region
size specified for CA Workload Automation SE and restart CA Workload Automation SE.

CA-7.IJLM-02

- GENERIC GET FAILED.

Reason:
Unable to locate first JCL record, CA Workload Automation SE abnormally terminates
with a U0002.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IJLM-03

- GET FOR UPDATE FAILED.

Reason:
Unable to acquire JCL record for update, CA Workload Automation SE abnormally
terminates with a U0003.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IJLM-04

- DELETE FAILED.

Reason:
Unable to delete JCL record, CA Workload Automation SE abnormally terminates with a
U0004.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 657

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJLM-05

- ADD FAILED.

Reason:
Unable to add JCL record, CA Workload Automation SE abnormally terminates with a
U0005.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IJLM-07

UNABLE TO OBTAIN NODE TABLE AREA

Reason:
Insufficient storage exists for CA Workload Automation SE to obtain storage for the
initial XPJOB Node Table where nodes and related information are listed. CA Workload
Automation SE keeps the destination nodes for XPJOB types in storage to permit fast
access during job submission.

Action:
Ensure the region provided to CA Workload Automation SE is sufficient to support the
XPJOB environment. If region is coded on the JCL JOB or EXEC (execute) statement,
increase the region coded. If no region is coded or region defaults to an installation
standard, review the default allowed and adjust accordingly.

CA-7.IJLM-08

I/O ERROR WHEN READING NODE RECORDS

Reason:
During CA Workload Automation SE initialization, the XPJOB Node Table is built from
records stored in the VRM VSAM file. The program building the node table encountered
an I/O error.

Note: The VRM file may be exclusively held by another address space or may have
some type of I/O error.

Action:
Verify that the VRM file is accessible and can be read by programs. To ensure nothing is
wrong with the VRM file, try reading the file through an IDCAMS PRINT operation or
some interactive utility that reads VSAM files. If the VRM file appears to be intact,
gather the output from this execution of CA Workload Automation SE and contact CA
Support at http://ca.com/support for assistance.

658 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJLM-09

XPDEF INTERNAL ENVIRONMENT INITIALIZATION COMPLETE; nnnnnn NODE RECORDS

READ

Reason:
The successful initialization of the XPJOB environment is complete. The value nnnnnn
shows how many node records were read from the VRM file and placed into the
in-storage Node Table.

Action:
None.

CA-7.IJLM-10

UNABLE TO OBTAIN XPDEF TABLE

Reason:
Insufficient storage exists for CA Workload Automation SE to obtain storage for the
XPJOB Table where information about the environment is kept.

Action:
Ensure the region provided to CA Workload Automation SE is sufficient to support the
XPJOB environment. If region is coded on the JCL JOB or EXEC (execute) statement,
increase the region coded. If no region is coded or region defaults to an installation
standard, review the default allowed and adjust accordingly.

CA-7.IJLM-11

No CCI Communications area established

Reason:
The final check during initialization determined that no CAICCI Communications Area is
established. This means that CAICCI cannot be invoked. To enable XPJOB submission and
other CAICCI functions require that this area is established.

Note: This could indicate an error during CA Workload Automation SE initialization

processing.

Action:
Collect the CA Workload Automation SE Job data and any other information and contact
CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 659

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IJLM-14

No CA-7 Tracker Checkpoint DD (XCKPT) present; no internal tracker for XPJOBs

Reason:
XPJOB submission requires an internal CA Workload Automation SE tracking system
(XTRK), but the required DD statement XCKPT is not present in the CA Workload
Automation SE online JCL.

Action:
None. If you want to enable XPJOB submission, add the tracking system DD statements
to the CA Workload Automation SE online JCL and recycle CA Workload Automation SE
online system.

CA-7.IJLM-20

- JCLDSENT RECORD CONVERTED.

Reason:
During startup of CA Workload Automation SE, a symbolic JCL data set entry in the
database was found in an old format, and has been automatically converted to the new
format. The message is issued only once, even if multiple entries are converted.

Action:
None.

CA-7.ILCA

- xxxxxxxx NOW ON CALENDAR LIBRARY

Reason:
The module named at xxxxxxxx has been copied from the CA Workload Automation SE
load library to the PDS named on the CALENDAR statement in the product's initialization
file.

Action:
None.

660 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.ILCA

- xxxxxxxx LOAD FAILED

Reason:
CA Workload Automation SE was unable to LOAD the calendar module even though a
CALBLK statement was found that named the calendar. This calendar could not be
copied to the PDS named on the CALENDAR statement.

Action:
Ensure that the calendar resides on a library in the CA Workload Automation SE STEPLIB
concatenation.

CA-7.ILCA

- xxxxxxxx ALREADY ON CALENDAR LIBRARY

Reason:
The module named was not copied from STEPLIB to the calendar PDS because a module
with the same name was found on the calendar PDS.

Action:
If the module in the STEPLIB is to replace the module in the calendar PDS, use the
REFRESH function on the CALMOD panel, otherwise no action is required.

CA-7.ILCA

- xxxxxxxx ERROR IN ADDING TO CALENDAR LIB

Reason:
An error occurred while trying to add a module to the calendar PDS. An additional
diagnostic message accompanies this message.

Action:
Respond to the CA-7.ILCA message indicating the reason for the failure to add the
calendar.

Chapter 3: CA-7.A - CA-7.X Messages 661

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.ILCA

- text

Reason:
Check Message SM50-14 for a comparison of the text value.

Action:
Take the action as indicated for the SM50-14 message.

CA-7.INAP

- INSUFFICIENT STORAGE

Reason:
Storage sufficient to build an AINB control block was not available in subpool 7. VTAM
user data accompanying the VTAM LOGON will not be recognized by CA Workload
Automation SE. A CA Workload Automation SE /LOGON will be required AFTER the
terminal is connected to CA Workload Automation SE.

Action:
Increase the region size specified for CA Workload Automation SE and restart CA
Workload Automation SE.

CA-7.INCD

- COMMDS ON xxxxxx ddd

Reason:
This informational message is produced each time CA Workload Automation SE or ICOM
is started, at online startup, or for each run of the BTI (SASSBSTR). The message tells
where the Communications data set is located. Issued by SASSINCD. Where:
■ xxxxxx = The disk volume on which the data set resides.
■ ddd = SHR if the unit is SYSGENed as SHR; otherwise, it is blanks.

Action:
None.

662 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INIO

- PRIOR-RUN Q ALLOCATION ERROR

Reason:
The CA Workload Automation SE PRNQ data set allocation is less than three tracks.

Action:
Allocate the PRNQ with enough tracks to hold all jobs. Each track of the PRNQ can hold
165 jobs.

CA-7.INIT

- CA-DRIVER INTERFACE INITIALIZATION FAILED

Reason:
The CA-Driver automatic parameter substitution facility has not initialized properly.

Action:
See the other initialization messages. If the problem persists, contact your installation
specialist for assistance.

CA-7.INIT

- CA-DRIVER INTERFACE INITIALIZED

Reason:
The CA-Driver automatic parameter substitution facility has been made active based on
the presence of the CARPROC DD statement.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 663

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INIT

- DPROC CONCATENATION ERROR

Reason:
The data set name specified on the DRPROC keyword of the JCL statement of the
initialization file could not be concatenated above the data sets on the CARPROC DD
statement.

Action:
Perform the following actions:
■ Verify that the data set name on the JCL DRPROC keyword is valid.
■ Verify that a CARPROC DD statement is in the CA Workload Automation SE PROC
and that its data sets are valid.

CA-7.INIT

- INIT STATEMENT OPTION aaaa OBSOLETE - IGNORED

Reason:
The initialization file INIT statement, CONFIG keyword, coded an option, aaaa, that is
now obsolete in the CA Workload Automation SE execution and is now ignored. The
options include MCPU, MVT, VS1, VS2, SVS, MSP, ASP, HASP, or JES1.

Action:
Remove the option from the CONFIG keyword of the initialization file INIT statement.

CA-7.INIT

- UNABLE TO LOAD CA7AGENB

Reason:
The CA-Driver automatic parameter substitution facility has not initialized correctly. The
CA7AGENB options table could not be located.

Action:
Confirm that the correct CA Workload Automation SE load library is accessible through
steplib, linklib, or LPA. If the problem persists, contact your installation specialist for
assistance.

664 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INIT

- UNABLE TO LOAD CA7MDRV0

Reason:
The CA-Driver automatic parameter substitution facility has not initialized correctly. The
module CA7MDRV0 could not be located.

Action:
Confirm that the correct CA Workload Automation SE load library is accessible to the CA
Workload Automation SE address space through steplib, linklib, or LPA. If the problem
persists, contact your installation specialist for assistance.

CA-7.INTM

- ATTACH FOR SASSPM00 FAILED, R15=xxxxxxxx

Reason:
The ATTACH for the problem management subtask failed. The return code from ATTACH
is supplied in the message.

Action:
Contact your installation specialist for assistance.

CA-7.INTM

- CA-NETMAN INTERFACE INITIALIZATION FAILED DUE TO PREVIOUSLY NOTED

ERRORS.

Reason:
CA Netman interface initialization failed.

Action:
For more information about the reasons for the failure, see the previous error
messages.

Chapter 3: CA-7.A - CA-7.X Messages 665

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INTM

- CA-NETMAN INTERFACE INITIALIZATION COMPLETE.

Reason:
The CA Netman interface is initialized.

Action:
None.

CA-7.INTM

- DATA TRUNCATED.

Reason:
A value for one or more variables on a NETMAN statement was truncated because of
space limitations. The length of a single transaction as defined in a statement in the
NETMAN file cannot exceed 1000 bytes.

Action:
None.

CA-7.INTM

- DBASENM VALUE NOT SUPPLIED.

Reason:
The CA Netman database name is required.

Action:
Supply the appropriate CA Netman database name.

CA-7.INTM

- INVALID CONTINUATION FOR NETMAN STATEMENT.

Reason:
A rule for continuation of a model transaction was violated. The length of a model
transaction cannot exceed 1000 bytes.

Action:
Indicate a continuation by ending a model transaction line with a '+'. for the DBASENM
keyword on the NETMAN statement.

666 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INTM

- INVALID VALUE FOR KEYWORD, KEYWORD WAS xxxxxxxx

Reason:
An invalid value was supplied for the keyword named.
Note: For more information about the NETMAN statement, see the Systems
Programming Guide.

Action:
Correct the keyword value and retry.

CA-7.INTM

- LENGTH OF xxxxxxxx VALUE EXCEEDED MAXIMUM ALLOWABLE.

Reason:
Length of the value supplied for the NETMAN statement keyword named is greater than
the maximum permitted.

Action:
Correct the keyword value and retry.

CA-7.INTM

- MULTIPLE NETMAN STATEMENTS IGNORED.

Reason:
More than one NETMAN statement was found in the initialization file. Only one is
honored.

Action:
None.

CA-7.INTM

- MUST BE AT LEAST MVS SP 2 TO USE CA-NETMAN INTERFACE.

Reason:
The operating system level was not MVS SP 2 or higher. The operating system level must
be at least MVS SP 2 to use the CA Netman interface.

Action:
Verify the operating system level.

Chapter 3: CA-7.A - CA-7.X Messages 667

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INTM

- NORMAL COMPLETIONS WILL BE IGNORED.

Reason:
Unless GOODCOMP=Y is specified on the NETMAN statement, jobs that complete
normally whose restart count is zero are ignored by the problem management interface.

Action:
None.

CA-7.INTM

- ONE OR MORE PARAMETERS REQUIRED BY SASSNTMV NOT SUPPLIED.

Reason:
This message indicates an internal error. At least one required parameter was not
supplied on a call to SASSNTMV.

Action:
Contact your installation specialist for assistance.

CA-7.INTM

- ONE OR MORE VARIABLES UNDEFINED.

Reason:
Values for one or more of the variables on a NETMAN statement could not be resolved.
Note: For more information about permitted NETMAN statement variables, see the
Interface Reference Guide.

Action:
Verify the variables.

668 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INTM

- OPEN FAILED FOR NETMAN DD.

Reason:
The OPEN for the model transaction file failed. This OPEN is attempted when the
initialization file includes the NETMAN statement.

Action:
If you plan to use the CA Netman interface, verify that a NETMAN DD statement is in the
JCL for CA Workload Automation SE.

CA-7.INTM

- UNABLE TO ACQUIRE SUFFICIENT STORAGE FOR PROBLEM MANAGEMENT SYSTEM

INTERFACE

Reason:
Not enough storage was available to initialize the problem management interface. The
interface requires approximately 1 MB of virtual storage above the 16-MB line.

Action:
Verify that sufficient storage is available and retry.

CA-7.INTM

- UNABLE TO LOAD INTERFACE MODULE, NAME=xxxxxxxx

Reason:
An error occurred during the attempt to load the module named in the error message.

Action:
Verify that the module named resides on a library that is accessible to CA Workload
Automation SE and retry.

Chapter 3: CA-7.A - CA-7.X Messages 669

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INTM

- UNABLE TO LOAD PROCESSING EXIT xxxxxxxx

Reason:
An error occurred during the attempt to load the module named in the error message.
The NETMAN statement keyword EXIT= determines this name.

Action:
Verify that the module named resides on a library that is accessible to CA Workload
Automation SE and retry.

CA-7.INTM

- UNKNOWN ERROR RETURNED FROM SASSNTMV.

Reason:
This message indicates an internal error. An unrecognized return code from SASSNTMV
was received.

Action:
Contact your installation specialist for assistance.

CA-7.INVT

- NO. OF ISPF USERS EXCEEDS 255

Reason:
The number of CA Workload Automation SE ISPF users has exceeded 255, which is the
maximum.

Action:
Wait for one or more of the current users to log off before trying to log on again.

670 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INVT

- NO. OF ISPF USERS EXCEEDS VIRTUAL TERMINALS

Reason:
The number of CA Workload Automation SE ISPF users has exceeded the number of
virtual terminals that can be used simultaneously.

Action:
If the number of virtual terminals generated is less than 255, the number can be
increased by specifying additional terminals on the TNAME keyword for the LINE
statement on the product's initialization file. Another option is for the user to wait for
one or more of the other users to log off before trying to log on again.

CA-7.INWC

- NO TRX TERMINALS DEFINED, SWITCHING TO ARF=MAINT

Reason:
CA Workload Automation SE detected ARF=Y is specified on the RESTART statement, but
no TRX devices are defined. ARF requires at least one GROUP statement with
DEVICE=TRXDV. See the Systems Programmer Guide for more information. If no TRX
device is defined, then ARF is switched to run in MAINT mode. In MAINT mode, ARF
does not track job exceptions and does not execute recovery actions.

Action:
Define at least one TRX device for use with ARF.

CA-7.INWC

TRX INIT ERR CODE nn

Reason:
An error occurred during CA Workload Automation SE startup that relates to the TRX
terminals. If nn is 08, check to see if more than 10 TRX terminals are being defined. No
more than 10 TRX terminals are permitted. A U0880 abend occurs.

Action:
Correct the problem and restart CA Workload Automation SE.

Chapter 3: CA-7.A - CA-7.X Messages 671

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.INW3

DELETE JOBS/NETWORK? REPLY YES/NO.

xxxxxxxx HAS BEEN DELETED FROM yyyyyyyy

Reason:
CA Workload Automation SE has detected bad pointers to the TRLQ. CA Workload
Automation SE will attempt to recover during WARM or ERST initialization by deleting
the bad jobs or networks. Issued by SASSINW3.

Action:
If the operator replies NO, then no deletions will be done. If the operator replies YES, CA
Workload Automation SE will delete the bad jobs/networks. For either a YES or NO
response, the third WTO message will be issued for every bad job, network, or both
where xxxxxxxx is the job or network name and yyyyyyyy is the queue from which it was
deleted. If the operator replied NO, CA Workload Automation SE will abend, usually with
a U0927.

Note: CA Workload Automation SE cannot initialize correctly with bad TRLQ pointers.

The jobs, networks, or both that were deleted will need to be analyzed to determine
whether they must be resubmitted. Also, triggers and dependencies affected by the
deleted entries will have to be handled manually. However, if the yyyyyyyy value
indicates the UCC7PRNQ, then no actions will be required.

CA-7.INW3

- UNABLE TO LOAD SASSQGET

Reason:
Program SASSINW3 was unable to load program SASSQGET.

Action:
Ensure SASSQGET is either in a STEPLIB library or a linklist library.

672 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IOPT

- CA-DRIVER COMMENT INDICATOR IS: nnnnnnnn

Reason:
This message reports the value of the DPROCCOM keyword on the OPTIONS statement
in the product's initialization file. CA-Driver procedure statements that begin with
nnnnnnnn will not appear in expansions.

Action:
None.

CA-7.IOPT

- CA-7 WILL WAKE UP EVERY xxxx SECONDS TO READ THE COMMDS.

Reason:
CMGRDELAY=YES was specified on the OPTIONS statement in the product's initialization
file. This message simply reports the number of seconds, xxxx, that will elapse between
the CA Workload Automation SE reads of the communications data set. The xxxx value is
either FIVE or TEN.

Action:
None.

CA-7.IOPT

CPM ACTIVE

Reason:
CPM=Y was coded on the OPTIONS statement in the initialization file of CA Workload
Automation SE.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 673

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IOPT

- CPM REQUIRES AT LEAST ONE CCI DEVICE

Reason:
CPM=Y was coded on the OPTIONS statement in the product's initialization file, but no
terminals were defined with DEVICE=CCI.

Action:
Define at least one terminal specifying DEVICE=CCI.

CA-7.IOPT

- CPM REQUIRES RSRC=Y ON DBASE STMT

Reason:
CPM=Y was coded on the OPTIONS statement in the product's initialization file, but VRM
was not activated. VRM must be active to use CPM.

Action:
Activate VRM by coding RSRC=YES on the DBASE statement. The DBASE statement must
precede the OPTIONS statements.

CA-7.IOPT

- INVALID REPLY

Reason:
The response to the CA-7.IOPT WTOR was invalid.

Action:
Reply either YES or NO.

CA-7.IOPT

- INVALID VALUE FOR MAXRINGSZ.

Reason:
The MAXRINGSZ value must be from one to ten.

Action:
Correct the value.

674 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IOPT

- LOAD WILL BUILD VRM DEVICE DEFS

Reason:
This informational message indicates that the job LOADs will build VRM device
definitions as needed.

Action:
None.

CA-7.IOPT

- REQUESTED OPTIONS UNDEFINED n

Reason:
An incorrect value, n, was coded for the JSOP keyword.

Action:
Correct the JSOP value.

CA-7.IOPT

- SASSDTAB REQUIRED FOR VRM DEVICE DEFS

Reason:
Module SASSDTAB could not be loaded.

Action:
Place the SASSDTAB module in the appropriate library.

Chapter 3: CA-7.A - CA-7.X Messages 675

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IOPT

- SHOULD CA-7 READ COMMDS EVERY FIVE SECONDS? REPLY TO CONFIRM (YES/NO)

Reason:
CMGRDELAY=YES was specified on the OPTIONS statement in the product's initialization
file.
Note: Use this keyword only in consultation with CA Support. Inappropriate use of this
option could adversely affect CA Workload Automation SE performance.

Action:
Perform one of the following actions:
■ Reply YES to cause CA Workload Automation SE to wake up every five seconds to
read the communications data set.
■ REPLY NO to cause CA Workload Automation SE to continue to wake up every ten
seconds for this purpose.

CA-7.IOPT

- USING JOB SUBMISSION OPTION n

Reason:
This message declares the value coded for the JSOP keyword on the OPTIONS
statement. If multiple values are coded, additional instances of the message are issued.

Action:
None.

CA-7.IOPT

- USING SUBMSGLVL=n

Reason:
This message is issued for each value of SUBMSGLVL that is coded on the OPTIONS
statement in the product's initialization file.

Action:
None.

676 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IOPT

- VRM DEVICE DEFS USED AT SUBMISSION

Reason:
This informational message indicates that VRM device definitions are used at
submission time.

Action:
None.

CA-7.IOPT

- VRMDD REQUIRES RSRC=Y OR MAINT ON DBASE STMT

Reason:
The VRMDD keyword is only valid when using RSRC=YES or RSRC=MAINT.

Action:
Perform one of the following actions:
■ Remove VRMDD from the OPTIONS statement.
■ Add the appropriate RSRC value on the DBASE statement.

CA-7.IOPT

- xxxxxxxx REQUIRED FOR VARIABLE SUBSTITUTION

Reason:
Global variable substitution has been specified, and the listed module could not be
loaded.

Action:
Confirm that the module is accessible through steplib, linklib, or LPA. If the problem
persists, contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 677

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IRES

- UNABLE TO LOAD SASSENFT, CA-7 WILL NOT CREATE EVENT RECORDS.

Reason:
The CA Workload Automation SE ENF event definition table could not be loaded.

Action:
Ensure that SASSENFT resides on a library accessible to CA Workload Automation SE and
retry.

CA-7.IRES

- UNABLE TO LOAD SASSENFO, CA-7 WILL NOT CREATE EVENT RECORDS.

Reason:
The CA Workload Automation SE module that creates ENF events could not be loaded.

Action:
Ensure that SASSENFO resides on a library accessible to CA Workload Automation SE
and retry.

CA-7.IRES

- UNABLE TO ACQUIRE SUFFICIENT STORAGE FOR ENF EVENT CREATION

Reason:
Insufficient storage was available for CAIENF event work areas.

Action:
Increase the region size for CA Workload Automation SE by 1 MB and retry.

CA-7.IRST

- ARF MONITORING ACTIVATED

Reason:
The Automatic Recovery Facility (ARF) has been made fully active based upon the
ARF=YES keyword on the RESTART initialization statement.

Action:
None.

678 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IRST

- ARF DATA BASE SERVICES REQUESTED

Reason:
The database services for the Automatic Recovery Facility (ARF) has been made active
based upon ARF=MAINT keyword on the RESTART initialization statement. However, CA
Workload Automation SE will not monitor jobs for ARF recovery while in maintenance
mode.

Action:
None.

CA-7.ISEC

INSUFFICIENT STORAGE FOR UID TABLE

Reason:
Program SASSISEC was unable to obtain storage for the UID table.

Action:
Increase the region size for CA Workload Automation SE by 1 MB and retry.

CA-7.ISVC

- XPS SERVER NOT INITIALIZED.

Reason:
CA Workload Automation SE will not initiate XPS SERVER functions. This message is
produced in response to options specified on the SVCNO statement in the product's
initialization file.

Action:
If CA Workload Automation SE XPS SERVER functions are needed, specify the
appropriate options on the SVCNO statement and restart CA-7.

Chapter 3: CA-7.A - CA-7.X Messages 679

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.ISVC

- ROUTER=YES IGNORED BECAUSE MONITOR=NO.

Reason:
The XPS ROUTER will not run as a CA Workload Automation SE subtask unless CA
Workload Automation SE is an XPS SERVER.

Action:
If the XPS ROUTER is to run as a subtask of this copy of CA Workload Automation SE,
then specify an appropriate value for MONITOR. See the Systems Programming Guide
for information about the SVCNO initialization file statement keywords MONITOR and
ROUTER.

CA-7.ISVC

- XPS TRACKER WILL RUN IN THIS ADDRESS SPACE

Reason:
The XPS Tracker executes as a subtask of this copy of CA Workload Automation SE.

Action:
None.

CA-7.ISVC

- XPS SERVER INITIALIZED. MONITOR VALUE: nnnnnnn

Reason:
The CA Workload Automation SE XPS SERVER has been initialized. The monitor value is
reported.

Action:
None.

680 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.ISVC

- XPS ROUTER WILL NOT RUN IN THIS ADDRESS SPACE

Reason:
The XPS ROUTER will not run in this address space. This message may be issued during
the initialization of the test copy of CA Workload Automation SE. In the typical
configuration the XPS ROUTER runs as a subtask of the production copy of CA Workload
Automation SE. In such a case, the test copy of CA Workload Automation SE may act as a
second CA Workload Automation SE XPS SERVER on the same machine by specifying the
appropriate value on the MONITOR keyword of the SVCNO statement. No additional
copies of the XPS ROUTER may be activated. Although there may be up to two CA
Workload Automation SE XPS SERVERs at a CAIENF node, there must be only one active
copy of the XPS ROUTER.

Action:
Consider the following actions:
■ If the XPS ROUTER is active on another copy of CA Workload Automation SE at this
CAIENF node, no action is required.
■ If the XPS ROUTER is not active on another copy of CA Workload Automation SE at
this CAIENF node, code ROUTER=YES on the SVCNO statement in the product's
initialization file.

CA-7.ISVC

- XPS ROUTER WILL RUN IN THIS ADDRESS SPACE

Reason:
The XPS ROUTER runs as a subtask of this copy of CA Workload Automation SE. One and
only one copy of the XPS ROUTER must be active at any CAIENF node where CA
Workload Automation SE XPS SERVER functions are required.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 681

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-02

ACTIVE JOB CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup, VRM found no active records on the job
chain.

Action:
None.

CA-7.IVRM-03

ACTIVE JOB CHAIN CREATED

Reason:
During CA Workload Automation SE startup, VRM rebuilt the active job chain.

Action:
None.

CA-7.IVRM-04

CO-REQ RSRC ACTIVE CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup, VRM found no active records on the co-req
chain.

Action:
None.

CA-7.IVRM-05

RESOURCE COUNT ACTIVE CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup, VRM found no active records on the
resource count chain.

Action:
None.

682 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-06

NON-FREED RSRC CHAIN CREATED

Reason:
During CA Workload Automation SE ERST, WARM, or MOVQ startup, VRM found active
nonfreed resource records.

Action:
None.

CA-7.IVRM-07

NON-FREED RSRC CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup, VRM found no active records for nonfreed
resources.

Action:
None.

CA-7.IVRM-08

VRM INITIALIZATION COMPLETE

Reason:
This message is displayed during CA Workload Automation SE startup when VRM is
initialized.

Action:
None.

CA-7.IVRM-09

CO-REQUISITE RSRC RECORDS DELETED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM deleted all active
corequisite resource records.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 683

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-10

RESOURCE COUNT RECORDS UPDATED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM updated all active
resource count records to clear the inuse count.

Action:
None.

CA-7.IVRM-11

CA-7 COLD START - ALL PREVIOUS RESOURCE RECORDS DELETED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM deleted all active
resource records. The RM.7 definitions will be retained, but the CURR IN USE counts will
be cleared (set to zero).

Action:
None.

CA-7.IVRM-12

ERROR ON GETUPD CO-REQUISITE RESOURCE RECORD

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on a GET
for an update of a corequisite job resource record. CA Workload Automation SE
abnormally terminates with a U0128.

Action:
For assistance, contact CA Support at ca.com/support.

684 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-13

ERROR ON GETUPD RESOURCE COUNT RECORD

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on a GET
for update of a resource count record. CA Workload Automation SE abnormally
terminates with a U0139.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IVRM-14

ERROR ON DELETE CO-REQ RSRC RECORD

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on a
delete of a corequisite resource record. CA Workload Automation SE terminates with a
U0130.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IVRM-15

ERROR ON UPDATE RESOURCE COUNT RECORD

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on an
update of a resource count record. CA Workload Automation SE abnormally terminates
with a U0138.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 685

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-16

NO CO-REQUISITE RESOURCE RECORD(S) TO BE DELETED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM did not locate any
corequisite resource records to delete.

Action:
None.

CA-7.IVRM-16

MANUAL RESOURCE COUNT CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup, VRM found no active records on the
manual resource count chain.

Action:
None.

CA-7.IVRM-17

NO RESOURCE COUNT RECORD(S) TO BE DELETED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM did not locate any
resource count resource records.

Action:
None.

CA-7.IVRM-18

ERROR ON GET - ACTIVE JOB RESOURCE RECORD.

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred during a
GET of an active job resource record. CA Workload Automation SE abnormally
terminates with a U0124.

Action:
For assistance, contact CA Support at ca.com/support.

686 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-19

ERROR ON ERASE ACTIVE JOB RESOURCE RECORD.

Reason:
During CA Workload Automation SE COLD for FORM startup, an error occurred on
delete of an active job resource record. CA Workload Automation SE abnormally
terminates with a U0122 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IVRM-20

ALL ACTIVE JOB RESOURCE RECORDS DELETED.

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM deleted all active job
resource records.

Action:
None.

CA-7.IVRM-21

NO NON-FREED RESOURCE RECORDS TO BE DELETED.

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM did not locate any
nonfreed resource records to be deleted.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 687

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-22

ERROR ON DELETE OF NON-FREED RESOURCE RECORD.

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on a
delete of a nonfreed resource record. CA Workload Automation SE terminates with a
U0131.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IVRM-23

ERROR ON GETUPD FOR NON-FREED RESOURCE RECORD.

Reason:
During CA Workload Automation SE COLD or FORM startup, an error occurred on an
update of a nonfreed resource record. CA Workload Automation SE terminates with a
U0132.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.IVRM-24

NO ACTIVE JOB RESOURCE RECORD(S) TO BE DELETED.

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM did not locate any
active resource records to delete.

Action:
None.

CA-7.IVRM-25

CO-REQUISITE RESOURCE CHAIN CREATED

Reason:
During CA Workload Automation SE startup, VRM rebuilt the corequisite resource chain.

Action:
None.

688 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-26

RESOURCE COUNT CHAIN CREATED

Reason:
During CA Workload Automation SE ERST, WARM, or MOVQ startup, VRM found active
resource count records in the VRM database.

Action:
None.

CA-7.IVRM-27

NON-FREED RESOURCE RECORD(S) DELETED

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM deleted all nonfreed
active job resource records.

Action:
None.

CA-7.IVRM-28

NO STORAGE AVAILABLE FOR @RSRCPL

Reason:
Program SASSIVRM was unable to obtain storage for the RSRCPL control block. Either
the system was busy or there was insufficient storage.

Action:
Try again. If the system was busy, it should free up after a short time. If that does not
work, increase the region size for CA Workload Automation SE by 1 MB and retry.

CA-7.IVRM-29

NO MANUAL RESOURCE COUNT RECORDS TO BE DELETED.

Reason:
During CA Workload Automation SE COLD or FORM startup, VRM did not locate any
manual resource count records to delete.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 689

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IVRM-30

CPM FLOW CHAIN NOT CREATED

Reason:
During CA Workload Automation SE startup no active FLOW records were found. If
CPM=JFM, this initialization message appears with TYPE=WARM. FLOW records are not
kept. Commands FLOWL and FLOWD are disabled.

To obtain FLOW status, see the CA Critical Path Monitor User Guide.

Action:
None.

CA-7.IVRM-31

NO CPM FLOW RECORDS TO DELETE.

Reason:
During a start of CA Workload Automation SE, no FLOW records were found.

Action:
None.

CA-7.IVRM-40

nnnnn VRM ACTIVE RECORDS NOT CHAINED

Reason:
At least on VRM active record (X record) was found, and the job was not in the queue.
The nnnnn is the number of these records found. A log record is written for each job.

Action:
None.

690 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.IXTM

- Term in skip mode (xxxxxxxx/jjjjjjjj/nnnnnnnn)

Reason:
An input was received by CA Workload Automation SE for a CAICCI terminal, and the
terminal is already processing a CA Workload Automation SE command. xxxxxxxx is the
SCT name used by this session, jjjjjjjj is the job/task name of the partner, and nnnnnnnn
is the job number of the partner.

Action:
The input is ignored.

CA-7.IXTM

- Not open for read (xxxxxxxx/jjjjjjjj/nnnnnnnn)

Reason:
An input was received by CA Workload Automation SE for a CAICCI terminal, and the
terminal is not opened for READ operations. xxxxxxxx is the SCT name used by this
session, jjjjjjjj is the job/task name of the partner, and nnnnnnnn is the job number of
the partner.

Action:
The input is ignored.

CA-7.I31S

Allocated xxxxxxxx bytes for N31 storage; yyyyyyyy requested

Reason:
Storage was obtained for various scheduling functions.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 691

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.I315

- Allocated aaaaaaaa bytes for N31 storage; bbbbbbbb requested

Reason:
This informational message is issued during a startup of CA Workload Automation SE.
The message displays the number of bytes obtained for the N31 pool (aaaaaaaa), and
the amount requested (bbbbbbbb). Usually the aaaaaaaa value and the bbbbbbbb value
are the same.

Action:
If the aaaaaaaa value and the bbbbbbbb value are not the same, consider increasing
the CA Workload Automation SE REGION size by 16 MB.

CA-7.I32V

FREE FOR VIRTUAL TERMINAL FAILED

Reason:
The logon ID for a terminal defined as virtual could not be found. The terminal could not
be freed. Issued by SASSD32V and SASSI32V.

Action:
If error persists, contact your installation's CA Workload Automation SE specialist for
assistance.

692 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.I32V

APPLID(aaaaaaa) TERM(ttttttt) LU(lllllll) [LOCAL SNA]

Reason:
A successful connection has been made to CA Workload Automation SE, where:
aaaaaaa
CA Workload Automation SE application name.
ttttttt
CA Workload Automation SE terminal name.
lllllll
VTAM Logical Unit.

If the connection is SNA, LOCAL SNA displays.

Action:
None.

CA-7.I32V

RPL ACTIVE -- NOT RESET

Reason:
A request was made to modify a request parameter list (RPL) and the RPL was busy.

Action:
Try again after a short while.

CA-7.JCKI

- UNABLE TO ATTACH JCLCHECK SUBTASK

Reason:
An error occurred attempting to ATTACH the subtask that calls the JCLCHECK module.
Issued by SASSJCKI.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 693

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.JCKI

- LIMIT OF INTERFACE USERS REACHED, TRY AGAIN LATER

Reason:
The limit set by the MAXUSERS value on the JCLCHECK statement in the product's
initialization file was reached. Issued by SASSJCKI.

Action:
Wait and try the command again later or increase the MAXUSERS value.

CA-7.JCKI

- JCLCHECK SUBTASK ENDED ABNORMALLY, TCBCMP=xxyyyzzz

Reason:
A JCLCHECK subtask abended. yyy is the system abend code (hex) and zzz is the user
abend code (hex). Issued by SASSJCKI.

Action:
If the yyy value in the TCBCMP field is 80A, try increasing the region size for CA
Workload Automation SE, otherwise collect any dumps produced and contact your
installation specialist for assistance.

CA-7.JCKI

- DETACH FAILED FOR JCLCHECK SUBTASK

Reason:
An error occurred attempting to DETACH the subtask that calls the JCLCHECK module.
Issued by SASSJCKI.

Action:
No action is necessary unless the message appears frequently. In that case, save console
logs, run report HR02 for the time around the error and contact CA Support at
ca.com/support for assistance.

694 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.JCKI

- JCLCHECK SUBTASK INITIALIZATION FAILED

Reason:
An attempt to start the task that calls the JCLCHECK module has failed. Issued by
SASSJCKI.

Action:
Contact your installation specialist for assistance.

CA-7.JCLERR

text

Reason:
Some error occurred during JCL submission, requiring CA Workload Automation SE to
flush the job by causing a JCL error. This message only appears in a // JCL statement. The
text part of the message is the same as an error message issued to the master station to
describe the error. The text part of the message can be found elsewhere in this manual.

Action:
Correct the error and reexecute the job.

CA-7.LGON

VTAM INQUIRE FAILED FOR xxxxxxx / zzzzzzzz

Reason:
This WTO is produced if the VTAM INQUIRE macro has a bad return code. xxxxxxx is the
CA Workload Automation SE terminal name. zzzzzzzz is the VTAMID. This WTO is
followed by another for CA-7.V001 displaying the bad code. Issued by SASSLGON.

Action:
If the terminal indicated cannot be used by CA Workload Automation SE, check the
VTAM codes in the V001 messages. If you are unable to resolve the problem, contact
your installation's CA Workload Automation SE specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 695

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LGON

- SHOWCB FAILED, DIRECT LOGON REJECTED

Reason:
A VTAM SHOWCB macro failed during the attempt to build CA Workload Automation SE
logon information from the VTAM user data supplied on the connection request. A CA
Workload Automation SE /LOGON will be required after the terminal is connected to CA
Workload Automation SE.

Action:
If the problem persists, contact CA Support at ca.com/support for assistance.

CA-7.LGON

- ERROR LOCATING SCT FOR xxxxxxxx

Reason:
The SCT named at xxxxxxxx could not be found to build the CA Workload Automation SE
logon information from the VTAM user data supplied on the connection request. A CA
Workload Automation SE /LOGON is required after the terminal is connected to CA
Workload Automation SE.

Action:
If the problem persists, contact CA Support at ca.com/support for assistance.

CA-7.LINK

- ALESERV EXTRACT FAILED R15(xxxx)

Reason:
An error has occurred during CA Workload Automation SE initialization trying to retrieve
the ALET for the CA Workload Automation SE online address space through the ALESERV
macro. xxxx indicates the return code in Register 15. The IBM Health Checker interface,
if requested through CAIRIM processing, will not be able to monitor this instance of CA
Workload Automation SE. CA Workload Automation SE initialization continues.

Action:
See the IBM MVS Assembler Services Reference for more information about ALESERV
return codes. Contact your installation specialist for assistance.

696 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LINK

- HEALTH CHECKER INTERFACE WILL NOT CHECK INSTANCE iiii

Reason:
An error has occurred during CA Workload Automation SE initialization performing
setup functions required to enable the interface to IBM Health Checker. A previous
error message describes the error. The IBM Health Checker interface, if requested
through CAIRIM processing, will not be able to monitor this instance of CA Workload
Automation SE. CA Workload Automation SE initialization continues.

Action:
Contact your installation specialist for assistance.

CA-7.LINK

- L2DATES SERVICE INIT COMPLETE

Reason:
The internal date services routines have initialized successfully.

Action:
None.

CA-7.LINK

- L2DATES SERVICE INIT FAILED

Reason:
The internal date services routines did not initialize properly.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 697

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LINK

- NAME/TOKEN ADD FAILED R15(xxxx)

Reason:
An error has occurred during CA Workload Automation SE initialization trying to create a
name/token pair through the IEANTCR macro. xxxx indicates the return code in Register
15. The IBM Health Checker interface, if requested through CAIRIM processing, will not
be able to monitor this instance of CA Workload Automation SE. CA Workload
Automation SE initialization continues.

Action:
See the IBM MVS Assembler Services Reference for more information about IEANTCR
return codes. Contact your installation specialist for assistance.

CA-7.LINK

- SASSTMNT SERVICE INIT COMPLETE

Reason:
The internal table services routines have initialized successfully.

Action:
None.

CA-7.LINK

- SASSTMNT SERVICE INIT FAILED

Reason:
The internal table services routines did not initialize properly.

Action:
Contact your installation specialist for assistance.

CA-7.LINK

- SASSTZNO SERVICE INIT COMPLETE

Reason:
The time zone offset service routine initialized successfully.

Action:
None.

698 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LINK

- SASSTZNO SERVICE INIT FAILED

Reason:
The time zone offset service routine did not initialize properly.

Action:
Contact your installation specialist for assistance.

CA-7.LMGR

- /AUTO ERROR

Reason:
A recursive error occurred. /AUTO processing "woke up" while already processing
another command. /AUTO processing is turned off, and the terminal is placed in SKIP
mode. The terminal can be logged off.

Action:
Log off the terminal (if necessary) and log on again. If the problem persists, contact CA
Support at ca.com/support for assistance.

CA-7.LMGR

ERROR CODE=FVn TERM=xxxxxxx

Reason:
An error was detected by CA Workload Automation SE while attempting to process an
internal CA Workload Automation SE terminal buffer. xxxxxxx is the terminal associated
with the error. n is an error code used for debugging. Issued by SASSLMGR.

Action:
If the terminal continues to process normally, no action is required. Otherwise, the
following sequence of CA Workload Automation SE commands should be used to regain
the terminal:
■ /STOP,T=xxxxxxx
■ /PURGPG,LT=xxxxxxx
■ /START,T=xxxxxxx

Where xxxxxxx is the terminal name from the error message. /PURGPG may require a
station name other than the one indicated in message.

Note: If printer problem, station is probably MASTER.

Chapter 3: CA-7.A - CA-7.X Messages 699

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LMGR

MESSAGE ALREADY QUEUED FOR TERM tttttttt

Reason:
Terminal tttttttt was placed on the I/O queue for a message, but a message was already
queued for the terminal.

Action:
Log off the terminal and log on again. If the problem persists, contact CA Support at
ca.com/support for assistance.

CA-7.LOST

- (xx,yy) SYN CLSDST FOR xxxxxxx

Reason:
The connection was lost between the terminal xxxxxxx and CA Workload Automation SE.
This message may be accompanied by other terminal error messages including
CA-7.V001. The return codes from registers 15 and 0 are represented by xx and yy,
respectively. Issued by SASSLOST.

Action:
If the terminal is not connected to CA Workload Automation SE, try the following
sequence of commands to regain it:
■ /STOP,T=xxxxxxx
■ /CLOSE,T=xxxxxxx
■ Then vary the terminal inactive and active through VTAM.
■ /OPEN,T=xxxxxxx
■ /START,T=xxxxxxx

If the terminal is still not connected, then shut down CA Workload Automation SE and
bring it back up with a specific TYPE=ERST.

700 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.LOST

RPL ACTIVE -- CLSDST NOT DONE

Reason:
The CA Workload Automation SE VTAM lost terminal exit routine was entered, and the
RPL still shows to be active.

Action:
None. This is an informational message.

CA-7.MAIN

- CORE TAG CHECK FAILED, R1=xxxxxxxx R6=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
Contact your installation specialist for assistance.

CA-7.MAIN

- LENGTH CHECK FAILED, R0=xxxxxxxx R1=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
Contact your installation specialist for assistance.

CA-7.MAIN

- R10=xxxxxxxx R11=xxxxxxxx R14=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 701

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.MA31

- CORE TAG CHECK FAILED, R1=xxxxxxxx R6=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
If a WARM start of CA Workload Automation SE fails, attempt an ERST start. If the
problem persists, contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.MA31

- LENGTH CHECK FAILED, R0=xxxxxxxx R1=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
If a WARM start of CA Workload Automation SE fails, attempt an ERST start. If the
problem persists, contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.MA31

- R10=xxxxxxxx R11=xxxxxxxx R14=xxxxxxxx

Reason:
A storage integrity violation is suspected.

Action:
If a WARM start of CA Workload Automation SE fails, attempt an ERST start. If the
problem persists, contact your installation specialist for assistance.

702 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC101

UNKNOWN COMMAND IGNORED

Reason:
An operator command was not entered properly. A parameter was missing or
incorrectly specified. The command is ignored, and processing continues.

Action:
Enter the correct command.

CA-7.NC102

VTAM TERMINATION CODE=xxxx

Reason:
The VTAM subtask terminated abnormally. xxxx is the completion code from the
subtask. The level of this error is catastrophic. Processing halts.

Action:
Find the cause of the termination and correct. Contact your installation specialist for
assistance.

CA-7.NC103

INVALID PARAMETER ENTERED

Reason:
The JCL parameter on the EXEC statement was not coded correctly. The level of this
error is serious. Processing halts.

Action:
Correct the JCL parameter and rerun the job.

Chapter 3: CA-7.A - CA-7.X Messages 703

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC104

UNKNOWN NODE TABLE FULL

Reason:
The Unknown Node Table has no more room. The table contains information about
nodes that have data but are not in the node table. The level of this error is serious.
Data for that node and all future unknown nodes will be lost. Processing continues.

Action:
Do a STATUS command to display the undeliverable block counts. If any unknown nodes
have zero undeliverable blocks, a SHUTDOWN and STARTUP clear them from the
Unknown Node Table. In addition, to make room in the Unknown Node Table, data is
sometimes purged before the SHUTDOWN/STARTUP. Verify that the node table
(UCC7NODE) specifies the correct node names. If you must enlarge the Unknown Node
Table, contact CA Support at ca.com/support for assistance.

CA-7.NC105

SHUTDOWN COMPLETE

Reason:
The shutdown process has been completed successfully. Processing continues.

Action:
Issue a STOP or STARTUP command.

CA-7.NC106

INTERNAL LOGIC ERROR - ABENDING

Reason:
The program has detected an illogical situation. The level of this error is catastrophic.
The task terminates abnormally. This error is probably a program error.

Action:
Save all JCL, console listings and dumps and report the problem to CA Support. For
assistance, contact CA Support at ca.com/support.

704 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC107

NODE TABLE (tttttttt) NOT FOUND - ABENDING

Reason:
The load of the node table was not successful. (tttttttt) is the member name of the node
table not found. The level of this error is catastrophic. Processing halts, and the program
abnormally terminates.

Action:
Perform the following actions:
■ Verify that the TABLE= parameter on the EXEC statement contains the correct table
name.
■ Verify that the JOBLIB/STEPLIB cards provide the library that contains the table
specified.
■ If no TABLE= parameter is specified, verify that a node table exists with the name
UCC7NODE.

CA-7.NC108

ERROR PROCESSING UDQ FILE - ABENDING

Reason:
An error has occurred opening or reading the Undeliverable queue. The level of this
error is catastrophic. Processing halts, and the program abnormally terminates.

Action:
Contact your installation specialist for assistance. Verify that the file exists and is
correct. If not a user error, save all listings and dumps and contact CA Support at
ca.com/support for assistance.

CA-7.NC109

CA-7/NCF INTERNAL ERROR - xxxxx

Reason:
CA Workload Automation SE has detected an internal error that cannot be processed.
xxxxx is the internal error code. The level of this error is catastrophic. Processing halts
and the program abnormally terminates.

Action:
Contact your installation specialist for assistance. Save all listings and dumps and
contact CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 705

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC110

ERROR PROCESSING NCF FILE - ABENDING

Reason:
An error has occurred opening or accessing the CA Workload Automation SE NCF
Communications data set. The level of this error is catastrophic. Processing halts and the
program abnormally terminates.

Action:
Contact your installation specialist for assistance. Verify that the file exists and is
correct. If not a user error, save all listings and dumps and contact CA Support at
ca.com/support for assistance.

CA-7.NC113

CA-7 SYSTEM INTERFACES NOT PRESENT IN THE SYSTEM - ABENDING

Reason:
A control block set up by CAS9 for CA Workload Automation SE could not be found.

Action:
Run CAIRIM to initialize the CA71 instance.

CA-7.NC114

CA-7 SYSTEM INTERFACES NOT INITIALIZED TO SUPPORT NCF - ABENDING

Reason:
The instance control block (ICMDSECT) does not indicate that NCF is installed.

Action:
Run CAIRIM to initialize the CA71 instance.

CA-7.NC115

CA-7 SESSION ALREADY ACTIVE

Reason:
The user logged on to a terminal, and the session was already active. Processing
continues.

Action:
None.

706 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC190

xx..xx

Reason:
This is a redisplay of the modify input to NCF.

Action:
None.

CA-7.NC191

------------------ CA-7/NCF VTAM STATUS ------------------

Reason:
This is heading output for the NCF STATUS command.

Action:
None.

CA-7.NC192

--NODE-- (ID) - STATUS- -LUTYPE- -RECV- -SENT- UNDL -PURG-

Reason:
This is the heading for the NCF STATUS command.

Action:
None.

CA-7.NC193

xx..xx

Reason:
This is a data line for an NCF node.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 707

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC194

NCF QUEUE..xxx% USED UND QUEUE..yyy% USED

Reason:
This is a final line of output from an NCF STATUS command.

Action:
None.

CA-7.NC201

eeeeeeee (mmmmmmmm) oooooooo R15=cc RTNCD(FDBK2)=rr(ff)

SSENSMI(USENSEI)=ss(:h

Reason:
This message occurs when a VTAM error is encountered for a RECEIVE or a SETLOGON
macro. For a further explanation of the error, see the "Return Code and Sense Fields"
section in the IBM manual z/OS Communications Server: SNA Programming.

eeeeeeee is a text representation of the error condition that has occurred.

mmmmmmmm is the VTAM macro name that caused the error.

oooooooo is a representation of any special options that were used in the invocation of
the macro.

cc is the hex value contained in register 15 on exit from the macro.

rr is the hex value for the RTNCD field in the RPL.

ff is the hex value for the FDBK2 field in the RPL.

ss is the hex value for SSENSMI field in the RPL.

uuuu is the hex value for USENSEI field in the RPL.

Action:
The system action is dependent on the macro involved and the type of error. See the
following table. If any error is not listed in the table, the default action, which is to
continue processing, is used.

Macro RTNCD FDBK2 Action

RECEIVE X'10' X'07' Terminate the session

708 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

Macro RTNCD FDBK2 Action

X'10' X'09' Terminate the session
X'14' User abend 3318
SETLOGON X'14' User abend 3318

Attempt to determine the severity and cause of the error. If unable to determine and fix
the cause of the problem, contact CA Support at ca.com/support for assistance.

CA-7.NC202

VTAM ERROR (OPEN) nnnnnnnn ERROR=ee

Reason:
An error occurred during the OPEN ACB to establish communication with VTAM. The
level of this error is catastrophic. The program ends with an abnormal termination.

nnnnnnnn is the APPLID that was trying to OPEN the ACB.

ee is the error field in the ACB after the unsuccessful OPEN of the ACB. See the IBM
manual z/OS Communications Server: SNA Programming under the OPEN macro for an
explanation of the error codes.

Action:
Contact your installation specialist for assistance. Check the nodes (APPL) and cross
domains to make sure they are active in VTAM. Verify that the ACF/VTAM parameters
are specified correctly. See the specific error code values for the resolution. Check the
UCC7NODE module to make sure the entries are specified correctly and that the first
entry is the local node.

CA-7.NC203

NETWORK INITIALIZATION LIMIT EXCEEDED - PROCESSING CONTINUES

Reason:
This message is a warning message. Not all the asynchronous OPNDSTs completed
within the time limit specified in the JCL parameter. Data transmission commences, and
the outstanding OPNDSTs complete without waiting for the asynchronous ones.
Processing continues.

Action:
Contact your installation specialist for assistance.
If this message occurs frequently, you can increase the system initialization parameter
TIME= on the JCL. If a SEND data is attempted before the logon completes for that node,
all data for that node goes to the Undeliverable queue.

Chapter 3: CA-7.A - CA-7.X Messages 709

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC204

UNDELIVERABLE DATA FILE FULL - DATA LOST

Reason:
The Undeliverable queue is full. Data must be purged or sent before any more data can
be written to this data set. Warning messages should have preceded this error at 80
percent, 85 percent, 90 percent, and 95 percent plus. The level of this error is serious.
Undeliverable data is lost. Processing continues.

Action:
Inactive nodes can be logged on to receive data or a PURGE command can be issued to
make room on the data set. If this situation occurs regularly, increase the size of the
Undeliverable queue.

CA-7.NC205

NODE NOT FOUND IN UCC7NODE TABLE, DATA UNDELIVERABLE. NODE=nnnnnnnn

Reason:
This is a warning message. Data was read from the NCF Communications data set for a
node that was not defined in the UCC7NODE table. An entry was created in the
Unknown Node Table and all its data will go to the Undeliverable queue. nnnnnnnn is
the node that was not found in the table. Processing continues.

Action:
Contact your installation specialist for assistance. Determine whether the node table
was specified correctly. If the node is incorrect or the data is not needed, it may be
purged.

710 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC206

UNDELIVERABLE QUEUE THRESHOLD REACHED - xxx PERCENT FULL

Reason:
This is a warning message. This message will be produced the first time the UDQ
(Undeliverable queue) percentage exceeds 80 percent, 85 percent, and 90 percent. It
will be produced for every WRITE operation that exceeds 95 percent. The threshold is
reset whenever the percentage drops below 80 percent. xxx is the actual percentage of
space used in the Undeliverable queue. Processing continues.

Action:
Perform the following actions:
■ Issue the STATUS command and then look for inactive nodes.
■ Remove data from the Undeliverable queue, either by LOGON or PURGE
commands, before it becomes full and data is lost.
If this occurs frequently, increase the size of the Undeliverable queue.

CA-7.NC207

UNKNOWN NODE TABLE FULL - LOSING STATUS INFORMATION FOR NODE=nnnnnnnn

Reason:
This message is a warning message. The Unknown Node Table has no more room for
this node. Statistics are not kept for this node, and its data cannot be purged from the
UDQ. This message is only produced once when the limit is exceeded. nnnnnnnn is the
unknown node name. Processing continues.

Action:
If any entries in the table have zero undeliverable blocks, perform a
SHUTDOWN/STARTUP to purge them from the table. Verify that the node table contains
all possible entries necessary to prevent this situation from happening.

Chapter 3: CA-7.A - CA-7.X Messages 711

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC208

ERROR PROCESSING UDQ FILE - ABENDING

Reason:
An error occurred accessing the Undeliverable queue. The error could have occurred on
an OPEN, READ or WRITE operation. The level of this error is catastrophic. Processing
halts with abnormal termination.

Action:
Ensure the Undeliverable queue exists and is contained in the JCL. Contact your
installation specialist for assistance. Evaluate the I/O operation that was being
performed at the time the error occurred. Rebuild the data set only if necessary.

CA-7.NC209

ERROR PROCESSING NCF FILE - ABENDING

Reason:
An error occurred accessing the CA Workload Automation SE NCF Communications data
set. The error could have occurred on an OPEN, READ or WRITE operation. The level of
this error is catastrophic. Processing halts with abnormal termination.

Action:
Ensure that the CA Workload Automation SE NCF Communications data set exists and is
contained in the JCL. Contact your installation specialist for assistance. Evaluate the I/O
operation that was being performed at the time the error occurred. Rebuild the data set
only if necessary.

712 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC301

eeeeeeee (mmmmmmmm) oooooooo R15=cc RTNCD(FDBK2)=rr(ff)

SSENSMI(USENSEI)=ss(:h

Reason:
This message will occur when a VTAM error is encountered for an OPNDST, SEND,
CLSDST or TERMSESS macro. For further explanation of the error, see the "Return Code
and Sense Fields" section in the IBM manual z/OS Communications Server: SNA
Programming.

eeeeeeee is a text representation of the error condition that has occurred.

mmmmmmmm is the VTAM macro name that caused the error.

oooooooo is a representation of any special options that were used in this invocation of
the macro.

cc is the hex value contained in register 15 on exit from the macro.

rr is the hex value for the RTNCD field in the RPL.

ff is the hex value for the FDBK2 field in the RPL.

ss is the hex value for SSENSMI field in the RPL.

uuuu is the hex value for USENSEI field in the RPL.

Action:
The system action is dependent on the macro involved and the type of error. See the
following table. If any error is not listed in the table, the default action, which is to
continue processing, will be used.

Macro RTNCD FDBK2 Action

OPNDST X'14' - User abend 3318
SEND X'10' X'07' Terminate the session
X'10' X'09' Terminate the session
X'14' User abend 3318
CLSDST X'14' User abend 3318
TERMSESS X'14' User abend 3318

Chapter 3: CA-7.A - CA-7.X Messages 713

CA-7.D32V Through CA-7.VDB0 Messages

Consult the explanation of the error in the IBM manual z/OS Communications Server:
SNA Programming under "Return Code and Sense Fields." Attempt to determine the
severity and cause of the error. If unable to determine and fix the cause of the problem,
contact CA Support at ca.com/support for assistance.

CA-7.NC302

SESSION ESTABLISHED WITH NODE (nnnnnnnn)

Reason:
This message is produced following successful processing of a CA Workload Automation
SE NCF LOGON command. Communication is now established with the node specified.
Processing continues.

Action:
None.

CA-7.NC303

LOGOFF REQUEST COMPLETE FOR NODE=nnnnnnnn

Reason:
Communications have been discontinued with the node specified in the message. The
break in communications was initiated by this node. nnnnnnnn is the node with which
communications have been broken. Processing continues.

Action:
None.

714 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC304

LOGON FAILED - NODE (xxxxxxxx)

Reason:
This message should follow an error message (CA-7.NC301 or CA-7.NC502) describing
the reason why the session could not be established. It is for information only, but may
indicate an error condition. Processing continues.

Action:
Contact your installation specialist for assistance. Correct the cause of the failure, if
possible. Otherwise get SYSLOG and TRACE output and then contact CA Support at
ca.com/support for assistance.

Note: The cause of error may have been detected at the remote node. Be sure to
review the console output at that site before assuming that the problem is with CA
Workload Automation SE NCF.

Chapter 3: CA-7.A - CA-7.X Messages 715

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC501

eeeeeeee (mmmmmmmm) oooooooo R15=cc RTNCD(FDBK2)=rr(ff)

SSENSMI(USENSEI)=ss(:h

Reason:
This message will occur when a VTAM error is encountered for a SEND or a RECEIVE
macro. For further explanation of the error, see the "Return Code and Sense Fields"
section in the IBM manual z/OS Communications Server: SNA Programming.

eeeeeeee is a text representation of the error condition that has occurred.

mmmmmmmm is the VTAM macro name that caused the error.

oooooooo is a representation of any special options that were used in this invocation of
the macro.

cc is the hex value contained in register 15 on exit from the macro.

rr is the hex value for the RTNCD field in the RPL.

ff is the hex value for the FDBK2 field in the RPL.

ss is the hex value for SSENSMI field in the RPL.

uuuu is the hex value for USENSEI field in the RPL.

Action:
The system action is dependent on the macro involved and the type of error. See the
following table. If any error is not listed in the table, the default action, which is to
continue processing, will be used.

Macro RTNCD FDBK2 Action

SEND X'10' X'07' Terminate the session
X'10' X'09' Terminate the session
X'14' User abend 3318
RECEIVE X'10' X'07' Terminate the session
X'10' X'09' Terminate the session
X'14' User abend 3318

Consult the explanation of the error in the IBM manual z/OS Communications Server:
SNA Programming under "Return Code and Sense Fields." Attempt to determine the
severity and cause of the error. If unable to determine and fix the cause of the problem,
contact CA Support at ca.com/support for assistance.

716 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC502

ICR FROM NODE (nnnnnnnn) REJECTED, ENTRY FOR NODE (nnnnnnnn) INDICATES ID
X'nn'

Reason:
During establishment of a session between your installation's NCF node and the node
indicated, a serious mismatch between the two nodes' network definitions has been
detected (that is, one or the other node table was coded incorrectly). The node cannot
be logged on because the integrity of the NCF network would be compromised.

Action:
Contact your installation specialist for assistance. Ensure that the network is correctly
defined to all nodes. If the problem cannot be corrected, save all listings and dumps and
contact CA Support at ca.com/support for assistance.

CA-7.NC503

WARNING: ICR FROM NODE (nnnnnnnn) INDICATES NCF NODE (nnnnnnnn) IS MISSING
FROM THE LOCAL NCT

Reason:
(See next message.)

Action:
(See next message.)

CA-7.NC503

WARNING: ICR FROM NODE (nnnnnnnn) INDICATES NCF NODE (nnnnnnnn) IS RELATED
TO JES NODE (nnnnnnnn)

Note: One or the other of the above messages will appear. The following write-up
applies equally to either message.

Reason:
During establishment of a session between your installation's NCF node and the node
indicated, a discrepancy has been detected between the two nodes' network
definitions. Session establishment continues. Missing entries may or may not indicate
that one or the other node table is in error, depending on the intended configuration of
the network.

Action:
Contact your installation specialist for assistance. Correct JES nodes in error as soon as
possible, but they are not critical to the performance of NCF.

Chapter 3: CA-7.A - CA-7.X Messages 717

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC504

SHUTDOWN IN PROGRESS. ICR FROM (xxxxxxxx) REJECTED

Reason:
An initialization control record (ICR) was received from node xxxxxxxx attempting to
establish a connection, but the receiving node was in the process of shutting down.

Action:
The connection attempt is rejected.

CA-7.NC602

VTAM ERROR (LOSTERM) NODE=nnnnnnnn CODE=cc

Reason:
The LOSTERM exit has been entered for the node specified in the message. The level of
this error is serious.

nnnnnnnn is the node that initiated the LOSTERM condition.

cc is the LOSTERM reason code. See the IBM manual z/OS Communications Server: SNA
Programming in the "Using Exit Routines" section under the LOSTERM exit.

Action:
The action depends on the value of the reason code.

Reason code Meaning

X'00' - X'0B' Ignore the condition and continue.
X'0C' - X'1C' Terminate the session.
X'1D' - X'FF' Print message and continue.

Correct the problem and resubmit.

718 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC701

VTAM NSEXIT (CLEANUP) NODE=nnnnnnnn mmm...

Reason:
This is a warning message. A cleanup session request has been received from VTAM
because communication with the node specified has been terminated abnormally.

nnnnnnnn is the node of the session that VTAM needs cleaning up.

mmm... is an optional text message to indicate that the node specified in the message
could not be found in the node control table.

The node specified in the message is marked as "not in session."

Action:
Verify that the node should no longer be operational. If it should be in operation,
contact your installation specialist for assistance. Correct the error and resubmit.

CA-7.NC702

VTAM NSEXIT (NSPE) NODE=nnnnnnnn

Reason:
This message is a warning message. VTAM has detected a Network Services Procedure
Error (NSPE) on a session initiation request that was responded to positively. However,
something happened that made it impossible to ensure that the session will be set up
successfully. nnnnnnnn is the node name whose session is in question. Processing
continues.

Action:
Correct the error and resubmit.

CA-7.NC703

VTAM NSEXIT (NOTIFY) NODE=nnnnnnnn

Reason:
This message is a warning message. A session initiation request was responded to
positively, but something happened that made it impossible to ensure that the session is
set up correctly. nnnnnnnn is the node whose session is in question. Processing
continues.

Action:
Correct the error and resubmit.

Chapter 3: CA-7.A - CA-7.X Messages 719

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC801

eeeeeeee (mmmmmmmm) oooooooo R15=cc RTNCD(FDBK2)=rr(ff)

SSENSMI(USENSEI)=ss(:h

Reason:
A VTAM error has occurred as a result of an OPNSEC or SESSIONC macro. See the
"Return Code and Sense Fields" section of the IBM manual z/OS Communications Server:
SNA Programming for a more detailed explanation.

eeeeeeee is a text representation of the error condition that has occurred.

mmmmmmmm is the VTAM macro name that caused the error.

oooooooo is a representation of any special options that were used in this invocation of
the macro.

cc is the hex value contained in register 15 on exit from the macro.

rr is the hex value for the RTNCD field in the RPL.

ff is the hex value for the FDBK2 field in the RPL.

ss is the hex value for SSENSMI field in the RPL.

uuuu is the hex value for USENSEI field in the RPL.

Action:
The system action is dependent on the macro involved and the type of error. See the
following table. If any error is not listed in the table, the default action, which is to
continue processing, is used.

Macro RTNCD FDBK2 Action

OPNSEC X'14' User abend 3318
SESSIONC X'10' X'07' Terminate the session
X'10' X'09' Terminate the session
X'14' Terminate the session

Consult the explanation of the error in the IBM manual z/OS Communications Server:
SNA Programming under "Return Code and Sense Fields." Attempt to determine the
severity and cause of the error. If unable to determine and fix the cause of the problem,
contact CA Support at ca.com/support for assistance.

720 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NC803

LOGOFF COMPLETE FROM NODE=nnnnnnnn

Reason:
The node specified in the message initiated and completed a termination of
communications. nnnnnnnn is the node that initiated the cessation of communications.
Processing continues.

Action:
None.

CA-7.NC901

VTAM TPEND (HALT)

Reason:
This message is a warning message. A VTAM command was issued to do a controlled
shutdown of the application. All nodes are marked to log off. Processing continues.

Action:

Issue a LOGON command for each node when communication is reestablished.

CA-7.NC902

VTAM TPEND (HALT,CANCEL)

Reason:
This is a warning message. A VTAM command was issued to cancel the application
immediately. The VTAM application is terminated with a zero return code.

Action:
Start the VTAM application when the VTAM problem is resolved. Contact your
installation specialist for assistance. Correct the error and resubmit.

Chapter 3: CA-7.A - CA-7.X Messages 721

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NSXT

- CLEANUP REQUESTED FOR xxxxxxx

Reason:
An error was detected by CA Workload Automation SE on the terminal shown. This
message may be accompanied by other terminal error messages. Issued by SASSNSXT.

Action:
None. This message indicates that CA Workload Automation SE is attempting to clean up
its own error on the terminal shown. If another CA Workload Automation SE message
appears, see the action to correct it.

CA-7.NSXT

- UNKNOWN VTAM CODE

Reason:
The VTAM Network Services Exit routine in CA Workload Automation SE received
control from VTAM with an unknown code. Issued by SASSNSXT.

Action:
The exit ignores the request and passes a code of zero to VTAM.

722 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NSXT

- (xx,yy) SYN CLSDST FOR xxxxxxx

Reason:
The connection was lost between the terminal xxxxxxx and CA Workload Automation SE.
This message may be accompanied by other terminal error messages including
CA-7.V001. The return codes from registers 15 and 0 are represented by xx and yy,
respectively. Issued by SASSNXST.

Action:
If the terminal is not connected to CA Workload Automation SE, try the following
sequence of commands to regain it:
■ /STOP,T=xxxxxxx
■ /CLOSE,T=xxxxxxx
■ Then vary the terminal inactive and active through VTAM.
■ /OPEN,T=xxxxxxx
■ /START,T=xxxxxxx
■ If the terminal is still not connected, then shut down CA Workload Automation SE
and bring it back up with a specific TYPE=ERST.

CA-7.NTMV

- Unable to evaluate variable in L2NTR at xxxxxxxx, first 16 bytes are:

yyyyyyyyyyyyyyyy

Reason:
An error occurred attempting to evaluate the variable data at the address xxxxxxxx. The
first 16 bytes at that location are yyyyyyyyyyyyyyyy.

Action:
Ensure that the intended variable was properly named in the model NETMAN
transaction file and retry.

Chapter 3: CA-7.A - CA-7.X Messages 723

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NTM0

- No plist address supplied for SASSNTM0.

Reason:
Insufficient storage was available for ENF event work areas.

Action:
Increase the region size for CA Workload Automation SE by 1 MB and retry.

CA-7.NTM0

- Address of problem data not supplied for SASSNTM0.

Reason:
This is an internal error. No problem data was supplied on a call to SASSNTM0.

Action:
Contact your installation specialist for assistance.

CA-7.NTM0

- CA-NETMAN database name not supplied for MGPTUPD transaction.

Reason:
This message indicates an internal error. No NETMAN database name was supplied on a
call to SASSNTM0.

Action:
Contact your installation specialist for assistance.

CA-7.NTM0

Address of NTMAPI not supplied for SASSNTM0.

Reason:
This message indicates an internal error. No NTMAPI address was supplied on a call to
SASSNTM0.

Action:
Contact your installation specialist for assistance.

724 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NTM0

- NTMAPI called, RC=xxxxxxxx

Reason:
The NETMAN API was called, and a nonzero return code was received.

Action:
Contact your installation specialist for assistance.

CA-7.NUC

- ARF INITIALIZATION FAILED.

Reason:
Initialization of the CA Workload Automation SE ARF facility encountered an error. A
U1004 abend will occur.

Action:
See any preceding messages relating to ARF. Correct any errors and restart CA Workload
Automation SE.

CA-7.NUC

- CA-7 JSCB AUTHORIZED

Reason:
This message is displayed when PGM=UCC7 is APF authorized as required.

Action:
None.

CA-7.NUC

- CA-7 JSCB NOT AUTHORIZED

Reason:
This message is displayed when PGM=UCC7 is not APF authorized (a U0988 abend also
occurs).

Action:
Link program UCC7 with AC=1, and verify that all STEPLIBs are APF authorized.

Chapter 3: CA-7.A - CA-7.X Messages 725

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.NUC

- DORMANT START UP IN PROCESS

Reason:
This CA Workload Automation SE was started with TYPE=DORM specified. Issued by
SASSNUC.

Action:
None.

CA-7.NUC

- MVS PROGRAM MANAGEMENT USED

Reason:
This message is displayed when the OS LOADER was requested.

Action:
None.

CA-7.NUC

- UNABLE TO SUPPORT SGETM31/SPUTM31

Reason:
SGETM/SPUTM services are unavailable for storage above the 16-MB line.

Action:
Verify that the SASSI31S module resides in a load library accessible to CA Workload
Automation SE.

CA-7.PM00

- Problem Management subtask termination requested.

Reason:
Termination was requested for the problem management interface.

Action:
None.

726 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.PM00

- Unable to acquire FREE chain. FREEMAIN required.

Reason:
The problem management subtask was unable to reuse problem data because of
contention with the CA Workload Automation SE main task. An OS FREEMAIN will be
requested.

Action:
Occasional occurrences of this message present no cause for concern. However, should
this message be issued frequently consider increasing the region for CA Workload
Automation SE. If the message persists, contact your installation specialist for
assistance.

CA-7.PM00

- FREEMAIN failed.

Reason:
A nonzero return code was received on an OS FREEMAIN issued by the problem
management subtask.

Action:
None.

CA-7.PM10

- End-of-Task Exit TCB address did not match L2PMA_PM00TCB.

- L2PMA at xxxxxxxx. L2PMA_PM00TCB=yyyyyyyy

Reason:
The end of task exit for the problem management subtask was entered. The TCB
address at entry did not match the TCB address in the L2PMA.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 727

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.PM10

- SASSPM10 entered for TCB at xxxxxxxx TCBCMPF= ffffffff

Reason:
Problem Management program SASSPM10 was entered, and the TCB for the task was
located at xxxxxxxx. The TCB's flags are ffffffff.

Action:
None.

CA-7.PM10

- Problem Management subtask ended.

Reason:
The end of task exit for the problem management subtask was entered. This message
should only be produced at CA Workload Automation SE termination.

Action:
None.

CA-7.PM10

- End-of-Task Exit could not locate L2PMA.

Reason:
The end of task exit for the problem management subtask was entered. The L2PMA
could not be located.

Action:
Contact your installation specialist for assistance.

CA-7.PM10

- End-of-Task Exit could not locate UCC7SVT.

Reason:
The end of task exit for the problem management subtask was entered. The UCC7SVT
could not be located.

Action:
Contact your installation specialist for assistance.

728 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.PPJC

- Storage request exceeds maximum allowable. Data lost.

Reason:
A limit on the amount of storage to be used by the problem management interface has
been reached. Problem data for job completions will be lost.

Action:
Contact your installation specialist for assistance.

CA-7.PPJC

- GETMAIN failed. Unable to chain job completion data.

Reason:
The problem management subtask was unable to process job completion data because
of a GETMAIN failure.

Action:
Contact your installation specialist for assistance.

CA-7.PPJC

- Chaining error. Data lost.

Reason:
The problem management subtask was unable to process job completion data because
of an internal error in chaining. This error is probably due to a storage overlay.

Action:
Contact your installation specialist for assistance.

CA-7.QMGET

text

Reason:
Program SASSQGET encountered an internal error, described by text.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 729

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.QMGO

DQTQ OVERLAP | WRAP AROUND

Reason:
Too many messages are queued to a terminal. Message is followed by an S0C3 abend of
CA Workload Automation SE. Issued by SASSQMGO.

Action:
Restart CA Workload Automation SE with TYPE=ERST that will clear out the messages in
the DQTQ and Scratch queue.

CA-7.RLOG

UNABLE TO ADD ENTRY TO RUNLOG. NAME=xxxxxxxx

Reason:
The daily run log has filled up. The xxxxxxxx indicates the job name or network name
trying to be added. The message is informational.

Action:
None.

CA-7.RLOG

ERROR TRYING TO ADD RLOG FOR TODAY'S DATE

Reason:
An attempt to add a new RLOG header entry failed. The PRNQ may be full.

Action:
Use the /DISPLAY,Q=ALL command to see if the PRNQ is full. Also, a trigger loop (JOBA
triggers JOBB, and JOBB triggers JOBA) can cause the problem.

CA-7.RSC5-01

JOB NOT FOUND IN READY QUEUE

Reason:
An entry was not found in a VRM table.

Action:
None.

730 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.RSC5-02

I/O ERROR ON READ OF READY QUEUE

Reason:
An error occurred trying to read a CA Workload Automation SE queue.

Action:
If the problem persists, contact your installation specialist for assistance.

CA-7.RW005

RESOURCE FILE SUCCESSFULLY CLOSED

Reason:
This message is issued at the end of the WLP processing of the VRM database.

Action:
None.

CA-7.RW100

@RSRCPL INVALID PARAMETER LIST

Reason:
An internal control block error occurred during WLP. Issued by SASSWRAC, which
terminates with a U0100 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.RW101

INVALID REQUEST SASSWRAC

Reason:
Program SASSWRAC encountered a request that was not valid. The program terminates
with a U0101 abend.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 731

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.RW101

SHOWCB ERROR

Reason:
Program SASSWRAC attempted to access a data set and failed. The program terminates
with a U0101 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.RW102

VSAM RECD ERROR R15 = xx FDBK = cccccccc FUN= ff

CA-7.RW102A

RECORD KEY = key

Reason:
Program SASSWRAC attempted to access a data set and failed. The return code in R15 is
xx, the feedback code is cccccccc, and the function code is ff. The record key is key.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.RW103

MODCB ERROR

Reason:
Program SASSWRAC attempted to get a record and failed. The program terminates with
a U0103 abend.

Action:
For assistance, contact CA Support at ca.com/support.

732 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.RW105

ERROR ON VSAM MACRO

Reason:
Program SASSWRAC attempted to get a record and failed. The program terminates with
a U0105 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.RW500

ERROR ON DEQUEUE OF RESOURCE

Reason:
An internal error occurred during WLB processing. Issued by SASSWCMP.

Action:
None.

CA-7.RW506

NO RESOURCE COUNT RECORD MATCH WITH PROCESSING

Reason:
An internal error occurred during WLB processing. Issued by SASSWCMP.

Action:
None.

CA-7.RW901

ERROR DURING GENCB (EXLST) R15=xx

Reason:
An error occurred during WLP processing of the VRM database. The return code is
shown as xx. CA Workload Automation SE terminates with a U0001 abend. Issued by
SASSWXIN.

Action:
Ensure the VRM database is properly defined. If necessary, contact CA Support at
http://ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 733

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.RW902

ERROR DURING GENCB (ACB) R15=xx

Reason:
An error occurred during WLP processing of the VRM database. The return code is
shown as xx. CA Workload Automation SE terminates with a U0002 abend. Issued by
SASSWXIN.

Action:
Ensure the VRM database is properly defined. If necessary, contact CA Support at
http://ca.com/support for assistance.

CA-7.RW903

ERROR DURING OPEN RSRC FILE R15=xx ER=yyy

Reason:
An error occurred during WLP opening of the VRM database. The return code is shown
as xx. The value of the error flags is yyy. CA Workload Automation SE terminates with a
U0003 abend. Issued by SASSWXIN.

Action:
Use the return code and error flags to determine the source of the error and correct it.

CA-7.RW904

RSRC FILE SUCCESSFULLY OPEN R15=xx ER=yyy

Reason:
This message is issued at the start of the WLP processing of the VRM database.

Action:
None.

CA-7.RW905

DDNAME CA7RSRC NOT FOUND

Reason:
The DD statement for CA7RSRC is missing. The WLP job abends with a U0105.

Action:
Check the JCL used by the WLP job.

734 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.RW906

ERROR DURING GENCB (RPL) R15=xx

Reason:
An error occurred during WLP processing of the VRM database. The return code is
shown as xx. CA Workload Automation SE terminates with a U0006 abend. Issued by
SASSWXIN.

Action:
Ensure the VRM database is properly defined. If necessary, contact CA Support at
http://ca.com/support for assistance.

CA-7.R107

MANUAL RESOURCE COUNT CHAIN CREATED

Reason:
During CA Workload Automation SE startup, a resource count chain was created. Issued
by SASSIVRM.

Action:
None.

CA-7.R137

VRM FULL SUPPORT ACTIVE

Reason:
The Virtual Resource Management facility (VRM) has been made fully active based upon
the RSRC=YES keyword (or default) on the DBASE initialization statement.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 735

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R138

VRM MAINT SUPPORT ACTIVE

Reason:
The database services for the Virtual Resource Management facility (VRM) has been
made active based upon RSRC=MAINT keyword on the DBASE initialization statement.
However, CA Workload Automation SE will not honor virtual resource requirements
while in maintenance mode.

Action:
None.

CA-7.R148

ERROR ON DELETE MANUAL RESOURCE COUNT RECORD

Reason:
Program SASSIVRM was not able to delete a manual resource count record. The
program terminates with a U0148 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R149

ERROR ON GETUPD MANUAL RESOURCE COUNT RECORD

Reason:
Program SASSIVRM was not able to obtain or update a manual resource count record.
The program terminates with a U0149 abend.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R150

MANUAL RESOURCE COUNT RECORDS DELETED

Reason:
Program SASSIVRM has deleted one or more manual resource count records.

Action:
None.

736 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R152

CPM FLOW CHAIN CREATED

Reason:
During CA Workload Automation SE startup, the chain of FLOW records was rebuilt.

Action:
None.

CA-7.R154

ERROR ON DELETE CPM FLOW RECORD

Reason:
CA Workload Automation SE was unable to delete a CPM FLOW record during
initialization.

Action:
Contact your installation specialist for assistance.

CA-7.R155

ERROR ON GETUPD CPM FLOW RECORD

Reason:
CA Workload Automation SE was unable to get a CPM FLOW record for update during
initialization.

Action:
Contact your installation specialist for assistance.

CA-7.R156

CPM FLOW RECORDS DELETED

Reason:
CA Workload Automation SE deleted CPM FLOW records during a COLD or FORM start.
This message also appears if a WARM start changes the OPTION CPM=YES to CPM=JFM.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 737

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R157

Unable to add all CPM Flow records - Storage shortage encountered

Reason:
CA Workload Automation SE was unable to create one or more in-memory CPM FLOW
records during initialization because of a shortage of storage. This message is a WTO
that is highlighted and non-scrollable.

Action:
Contact your installation specialist for assistance.

CA-7.R160

One or more CPM Flows have no jobs connected (STRANDED FLOWS)

Reason:
One or more active CPM Flows added from the database do not have any active jobs
connected. These flows will never complete normally and should be removed manually.
This message is a WTO that is highlighted and non-scrollable.

Action:
Refer to Message CA-7.R161 which should follow this message.

CA-7.R161

Issue CA 7 command 'FLOWD,FLOW=*ALL*,JOBCNT=0' to discard them

Reason:
One or more active CPM Flows added from the database do not have any active jobs
connected. These flows will never complete normally and should be removed manually
(see Message CA-7.R160). This message is a WTO that is highlighted and non-scrollable.

Action:
Use the FLOWL command to list flows to determine which ones are stranded (zero
connected jobs). You can delete these flows individually, or you can issue the command
FLOWD,FLOW=*ALL,JOBCNT=0 to delete all stranded flows.

738 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R32V

RPL RESET

Reason:
A CA Workload Automation SE VTAM RPL was left in an unusable state. CA Workload
Automation SE has restored the RPL to a usable state. This is an informational message
issued by SASSR32V.

Action:
None.

CA-7.R503

ERROR ON ADD OF MANUAL RESOURCE RECORD

Reason:
During job completion, an error occurred on an add of a manual job resource record.

Action:
Processing continues. Check for messages CA-7.XRAC-03 and CA-7.XRAC-06 for a
description of the error.

CA-7.R601

ERROR ON DELETE OF RESOURCE RECORD.

Reason:
During processing of a PRSCF transaction, VRM was unable to delete a record related to
the resource being freed. This message is issued by module SASSSPOR.

Action:
Processing continues. See messages CA-7.IVRM-02 and CA-7.IVRM-03 for specific details
about the error.

Chapter 3: CA-7.A - CA-7.X Messages 739

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R602

ERROR ON GET OF RESOURCE RECORD

Reason:
An error occurred when trying to obtain or update a record related to the resource
being freed. Issued by SASSSPOR.

Action:
Processing continues. See messages CA-7.IVRM-02 and CA-7.IVRM-03 for specific details
about the error.

CA-7.R603

ERROR ON DELETE OF CO-REQUISITE RESOURCE.

Reason:
An error occurred when deleting a corequisite resource record. This message is issued
by module SASSSPOR.

Action:
Processing continues. See messages CA-7.IVRM-02 and CA-7.IVRM-03 for specific details
about the error.

CA-7.R604

ERROR ON GET CO-REQUISITE RESOURCE RECORD.

Reason:
An error occurred on a GET to a corequisite resource record. This message is issued by
module SASSSPOR.

Action:
Processing continues. See messages CA-7.IVRM-02 and CA-7.IVRM-03 for specific details
about the error.

740 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R610

ERROR ON ADD OF CO-REQUISITE RESOURCE RECORD

Reason:
An error occurred on add of a corequisite resource record. This message is issued by
module SASSSPOR.

Action:
Processing continues. See Messages CA-7.XRAC-02 and CA-7.XRAC-03 for specific details
about the error.

CA-7.R612

RECORD NOT FOUND WITH GET FOR UPDATE

Reason:
An invalid return code was received during VSAM I/O processing. This message is issued
by module SASSSPOR.

Action:
None.

CA-7.R613

UPDATE ERROR ON ACTIVE RESOURCE CHAIN

Reason:
An invalid return code was received during VSAM I/O processing. This message is issued
by module SASSSPOR.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 741

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R620

ERROR ON LOOP ENQ

Reason:
During submission, an error occurred during VRM ENQ processing. This message is
issued by module SASSXRSU. CA Workload Automation SE abnormally terminates with a
U0620.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R621

GET ERROR ON ACTIVE JOB RESOURCE CHAIN

Reason:
During submission, an error occurred during a GET for an active job resource record. CA
Workload Automation SE abnormally terminates with a U0621.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R622

UPD ERROR ON ACTIVE JOB RESOURCE CHAIN

Reason:
During submission, an error occurred during an update of an active job resource record.
CA Workload Automation SE abnormally terminates with a U0622.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R701

GET ERROR ON ACTIVE RESOURCE RECORD CHAIN

Reason:
An error occurred during a GET of an active resource record when a cancel command
was issued.

Action:
None.

742 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R702

DELETE ERROR ON ACTIVE RECORD CHAIN

Reason:
An error occurred during a delete of an active resource record when a cancel command
was entered. Issued by SASSRCAN.

Action:
None.

CA-7.R731

GET ERROR ON ACTIVE RESOURCE RECORD CHAIN.

Reason:
At job-step end, an error occurred during a GET of an active resource record.

Action:
See messages CA-7.XRAC-02 and CA-7.XRAC-03 for specific details about the error.

CA-7.R732

UPDATE ERROR ON ACTIVE RESOURCE RECORD CHAIN.

Reason:
At job-step end, an error occurred during an update of an active resource record.

Action:
See messages CA-7.XRAC-02 and CA-7.XRAC-03 for specific details about the error.

CA-7.R901

ERROR DURING GENCB (EXLST) R15=xx

Reason:
During CA Workload Automation SE startup, an error xx (R15) occurred on VSAM control
block generation (exlst). CA Workload Automation SE abnormally terminates with a
U0001.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 3: CA-7.A - CA-7.X Messages 743

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R902

ERROR DURING GENCB (ACB) R15=xx

Reason:
During CA Workload Automation SE startup, an error xx (R15) occurred on VSAM control
block generation (ACB). CA Workload Automation SE abnormally terminates with a
U0002.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R903

ERROR DURING OPEN RESOURCE FILE R15=xx ER=aaa

Reason:
During CA Workload Automation SE startup, an error occurred on the resource file
open. CA Workload Automation SE abnormally terminates with a U0003.

Action:
For assistance, contact CA Support at ca.com/support.
Check the value in R15 and ACBERFLG (aaa) and correct the error.

Note: The ACBERFLG values can be found in the "OPEN Reason Codes in the ACBERFLG
Field of the ACB" section of the IBM Manual DFSMS Macro Instructions for Data Sets.

CA-7.R904

RESOURCE FILE OPENED. R15=xx ER=xxx

Reason:
During CA Workload Automation SE startup, the resource file was successfully opened.
For ER=118, the file was not properly closed, but OPEN's implicit verify was successfully
executed.

Action:
None.

744 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.R905

DDNAME CA7RSRC NOT FOUND

Reason:
During CA Workload Automation SE startup, the ddname corresponding to the VRM
resource file was not found. CA Workload Automation SE abnormally terminates with a
U0105.

Action:
Ensure that the CA Workload Automation SE startup JCL procedure contains the
CA7RSRC DD and filename.

CA-7.R906

ERROR DURING GENCB (RPL) R15=xx

Reason:
During CA Workload Automation SE startup, an error xx (R15) occurred on VSAM control
block generation (RPL). CA Workload Automation SE abnormally terminates with a
U0006.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.R907

DDNAME CA7RSRC POINTS TO DUMMY FILE - U0907

Reason:
The DD statement for the CA Workload Automation SE VRM VSAM file (CA7RSRC) does
not point to an actual data set. This data set is required for CA Workload Automation SE
operations. CA Workload Automation SE abends with a U0107.

Action:
Provide a CA7RSRC DD statement that points to a valid CA Workload Automation SE
VRM data set and restart CA Workload Automation SE.

Chapter 3: CA-7.A - CA-7.X Messages 745

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SCMK

- /CLOSE SUCCESSFUL FOR xxxxxxxx

Reason:
The CAICCI terminal xxxxxxxx has been closed.

Action:
None.

CA-7.SCNJ

SKIPPED DUPLICATE SCHEDULE MEMBER

Reason:
During a Schedule Scan, a schedule member was read that this same run of Schedule
Scan had already processed. The duplicate member is bypassed. This situation can
possibly occur when the Dataset data set is being updated while Schedule Scan runs.
Issued by SASSSCNJ.

Action:
None.

CA-7.SCRJ

- xxxxxxxx(nnnn), ARJP R15=yyyyyyyy, R0=zzzzzzzz, R1=wwwwwwww

Reason:
An error occurred while attempting to delete ARF control blocks that are no longer
needed for a job.

Action:
This is an ARF internal error. The message is issued for debugging purposes and does not
necessarily indicate a problem with ARF functionality. However, if the message is issued
repeatedly or if it accompanies other error messages, contact CA Support at
ca.com/support for assistance.

746 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SFER-08

JOB xxxxxxxx HAS MORE THAN 254 REQUIREMENTS.

Reason:
RQMT255=YES is specified in the product's initialization file OPTIONS statement. Any job
entering the REQQ with more than 255 requirements has the first 254 requirements
added and then a special user requirement with text of SFER-08: JOB HAS MORE THAN
254 RQMTS.

Action:
Post this user requirement manually.

CA-7.SJLV

- One or more VRM Devices dropped for xxxxxxxx

Reason:
An error occurred while trying to dynamically update the record of VRM devices. One or
more VRM device definitions were not updated. This could occur if the number of VRM
resources exceeds the database record capacity.

Action:
Contact your installation specialist for assistance. The following items may be required
to diagnose the error:
■ RM.1 output for the job in error.
■ Listing of the current SASSDTAB module.

CA-7.SJLV

- VRM IO err X FUNC=GETUPD RC=xxxxxxxx REASON=yyyyyyyy JOB=nnnnnnnn

Reason:
An error occurred while trying to dynamically update VRM resource definitions. X is a
code indicating the type of record on the VRM database. FUNC is the function
attempted. The program return code is reported at RC and REASON is the VSAM
feedback.

Action:
Contact your installation specialist for assistance. The following items may be required
to diagnose the error:
■ RM.1 output for the job in error.
■ Listing of the current SASSDTAB module.

Chapter 3: CA-7.A - CA-7.X Messages 747

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SJLV

- Unable to update VRM Device Definitions. Length=nnnnnnnn Maxlen=xxxxxxxx

Job=yyyyyyyy

Reason:
The record of VRM resources does not fit in the buffer allocated. The Length value is the
size of the VRM record retrieved, and Maxlen is the size of the working buffer.

Action:
Contact your installation specialist for assistance. RM.1 output for the job in error may
be required.

CA-7.SJL0

- VRM DEVICE TABLE SPACE EXCEEDED.

Reason:
The size of the table of VRM Devices that is built during LOAD completion had to be
increased. This is an informational message.

Action:
None.

CA-7.SJL0

- RQMT LOAD TABLE OVERFLOW

Reason:
An attempt was made to LOAD a job into CA Workload Automation SE. The table that is
set up to contain requirements for the job cannot handle all of this job's requirements.
Issued by SASSSJL0.

Action:
The load on the job will be successful despite this message. Use
LJOB,JOB=jobname,LIST=RQMT to see if the necessary requirements have been built for
the job. If all of these requirements are not included, contact your installation specialist
for assistance.

748 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMFI-33

CPU xxxx IPL - REQUEUING ACTIVE JOBS.

Reason:
This message is a WTO. An IPL of a system within the CA Workload Automation SE
complex was detected, and the AUTOREQ option is in effect. All jobs in the Active queue
for the affected CPU (xxxx) will be automatically requeued to the Request queue with a
status of R-REQUE.

Action:
Analyze each job moved into the Request queue to determine any corrective actions.
Once the appropriate steps have been taken, Job Restart must be used to resubmit
these jobs.

CA-7.SMFI-34

AUTO-REQUEUE FEATURE INACTIVE - IPL RECORDS IGNORED.

Reason:
An IPL of a system within the CA Workload Automation SE complex was detected, and
the AUTOREQ option is not in effect. Any jobs active on systems at the point of an IPL
will be left in the Active queue. Jobs left in the Active queue following a system failure
such as this must be manually requeued to the Request queue (see the REQUEUE
command). This message is displayed only once.

Action:
All jobs left stranded in the Active queue following the system failure must be manually
requeued to the Request queue (see the REQUEUE command).

To activate the Auto-Requeue feature, see the AUTOREQ keyword on the OPTIONS
initialization statement in the Systems Programming Guide.

Chapter 3: CA-7.A - CA-7.X Messages 749

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMF0

BAD SMF REC - BLOCK BYPASSED

Reason:
This message is a WTO. An SMF block in the Communications data set has a value of
zero in the first two bytes, or a value that is larger than the LRECL of the CA Workload
Automation SE log file. Issued by SASSSMF0.

Action:
The bad block is skipped. Data in this block is not processed. This could result in:
■ Outstanding data set requirements.
■ Jobs staying in the ready queue.
■ Jobs staying in the active queue.

CA-7.SMF2

JOB jjjjjjjj NOT ADDED TO ACTIVE QUEUE.

Reason:
This WTO is issued when an external job initiation occurs but CA Workload Automation
SE is unable to add it to the active queue. This could occur if the active queue was full or
if there was already a job in the ready or active queue by the same name.

Action:
None. This job will not be represented in the CA Workload Automation SE queues.

750 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMF3

JOB xxxxxxxx (nnnn/jjjjjjj/systemnm) ON cccc FAILED: rrrrrrrrrrrrrrrrrrrr

Reason:
The job indicated by xxxxxxxx on CPU ID cccc failed for the reason indicated by
rrrrrrrrrrrrrrrrrrrr. The jjjjjjj is the JES job number, if available. The nnnn is the CA 7 WA
job number, and systemnm is the CA Workload Automation SE system name (from the
job definition panel) if available. For CA7TOUNI and XPJOB type jobs, 7UNI or 7XPJ is
substituted for the CPU ID. For agent jobs, AGJ is substituted for the CPU ID. This WTO is
only produced if the WTO= keyword is specified on the RESTART statement in the
initialization file.

The possible reason values are:

■ ABEND Snnn
■ ABEND Unnnn
■ JCL ERROR
■ JOB CC nnnn
■ STEP ssssssss CC nnnn
■ STEP ssssssss FLUSHED

Action:
See the SMF0-33 messages in the CA Workload Automation SE Browse data set for jobs
that are automatically requeued. Appropriate action should be taken to resolve the
restart situation for the job. This may involve canceling or restarting the job on CA
Workload Automation SE.

CA-7.SMF3

- UNABLE TO UPDATE ARF TRAILER FOR jjjjjjjj (nnnn)

Reason:
An error occurred while trying to evaluate an ARF 'late at job end' exception (LE).
However, ARF could not report the error because of an error encountered while trying
to update the trailer queue.

Action:
ARF cannot properly proceed with recovery from the late condition. Manual recovery
procedures should be employed to address the problem. If necessary, cancel the job
and retry. If the problem persists, contact CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 751

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMF3C

- ARF ERROR: message text

Reason:
This message is produced following message CA-7.SMF3. The message text contains
additional details about the error.

Action:
Use the message text with message CA-7.SMF3 to resolve the error.

CA-7.SMF3D

- UNABLE TO READ SEGMENT 12 FOR xxxxxxxx (nnnn)

Reason:
During job termination, CA Workload Automation SE was attempting to read segment
12 of the queue record for job name xxxxxxxx, job number nnnn, and failed. This
message usually indicates a problem with the CA Workload Automation SE queues.
Processing continues; however, the CA Workload Automation SE/CA WA Restart Option
Condition Code Check synchronization feature is prevented from reflecting the job's
correct failure step.

Action:
Check the CA 7 WA job log to see if there are other queue record errors. If you are
unable to resolve the problem, contact CA Support at ca.com/support for assistance.

CA-7.SMF3E

- PRODUCT INTERFACE NOT ACTIVE, NO COMMUNICATION WITH CA 11

Reason:
During job termination, CA Workload Automation SE was attempting to use the Product
Interface to send information to CA WA Restart Option, but the Product Interface was
never initialized during CA Workload Automation SE startup. Processing continues;
however the CA Workload Automation SE/CA WA Restart Option Condition Code Check
synchronization feature is prevented from reflecting the job's correct failure step.

Action:
Check the CA Workload Automation SE Job Log for message 'CAL2I012I PRODUCT
INTERFACE SUB-TASK AVAILABLE'. If this message is not found, contact CA Support at
ca.com/support for assistance.

752 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMF4

JOB xxxxxxxx (nnnn/jjjjjjj/systemnm) ON cccc STEP pppppppp.ssssssss yyyy

Reason:
The procstep/step indicated by pppppppp.ssssssss for job xxxxxxxx on CPU ID cccc
completed with the indicated code. For CA7TOUNI and XPJOB type jobs, the execution
node is substituted for pppppppp.ssssssss and 7UNI or 7XPJ is substituted for the CPU
ID. For agent jobs, AGJ is substituted for the CPU ID, and the agent name where the job
is routed replaces pppppppp.ssssssss. This WTO is produced when the WTOSTEP
keyword is used on the CA Workload Automation SE RESTART initialization statement.
The default ROUTCDE is 2 (Master Console), this can be overridden by the ROUTCDE=
keyword on the RESTART statement.

The CA 7 WA job number (nnnn), JES job number (jjjjjjj) if available, and CA Workload
Automation SE system name (systemnm) if available are also provided.

The following are possible values for the termination code (yyyy):
Uyyyy
Indicates a User Abend code
Syyy
Indicates a System Abend code
JCLER
Indicates a JCL Error
Cyyyy
Indicates a condition code failure
yyyy
Indicates a step condition code (not a failure)

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 753

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SMF5

- DSNAME LENGTH ERROR, JOB=jjjjjjjj, DSN=datasetname

Reason:
Program SASSSMF5 encountered a data set name that was longer than 44 characters.
The job containing the data set name is shown as jjjjjjjj and the first 44 characters of the
data set name are displayed. Processing continues.

Action:
Correct the invalid data set name in the job specified in the CA Workload Automation SE
database.

CA-7.SMF5

OUTPUT DATA SET NOT POSTED TO CA-7

Reason:
The Trailer queue was full at the time that CA Workload Automation SE received a data
set update SMF record. When CA Workload Automation SE attempted to update the
job's record in the Active queue, an error occurred.

Action:
Verify the space allocation of the Trailer queue (it may need to be increased). If this data
set was supposed to trigger jobs or post requirements, manual intervention is required
to cause those events to occur.

CA-7.SM5B

- SUBTASK FAILURE LIMIT EXCEEDED FOR xxx...x

Reason:
While processing the JCL data set xxx...x, a failure (abend) occurred, and the data set has
been disabled. All jobs using this file are left in SKELETON status.

Action:
Correct the error and then recycle CA Workload Automation SE to regain use of the JCL
data set.

754 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SORRY

- TERMINAL NOT DEFINED TO CA-7

Reason:
A remote 3270 terminal (BTAM) has been used to input a command and the terminal is
not defined to CA Workload Automation SE. Issued by SASSI32R.

Action:
If the terminal is to be used, it must be defined with a TERM statement in the
initialization file.

CA-7.SSM0

- UNABLE TO PROCESS ARF EXCEPTION - IS

Reason:
An IS condition for the job was detected by ARF, but the job could not be requeued
because of an internal error.

Action:
Contact your installation specialist for assistance.

CA-7.SSM1

- TABLE FULL

Reason:
More than 4000 jobs have been submitted by CA Workload Automation SE causing an
internal table to become full. Possibly some mutually exclusive requirements will not be
honored. Issued by SASSSSM1.

Action:
If more than 4000 jobs are in the ready or active queues at any one time, contact CA
Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 755

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.STAT-01

MERGE DATE NOT SPECIFIED.

Reason:
The DATE parameter is missing.

Action:
Correct the JCL and rerun the job.

CA-7.STAT-02

UNRECOGNIZED PARM VALUE SPECIFIED.

Reason:
The parameter contains invalid data.

Action:
Correct the parameter and rerun the job.

CA-7.STAT-03

INVALID PARM SPECIFIED.

Reason:
The parameter contains invalid data.

Action:
Correct the parameter and rerun the job.

CA-7.STAT-04

PARM DATE SPECIFIED IS GREATER THAN CURRENT DATE.

Reason:
An invalid date was specified.

Action:
Correct the DATE and rerun the job.

756 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.STAT-04

UNABLE OPEN OLD STAT FILE (STATOLD)

Reason:
The STATOLD DD file failed open processing.

Action:
Make sure that the STATOLD DD is specified and points to the correct file.

CA-7.STAT-05

UNABLE OPEN CUR STAT FILE (STATCUR)

Reason:
The STATCUR DD file failed open processing.

Action:
Make sure that the STATCUR DD is specified and points to the correct file.

CA-7.STAT-06

UNABLE OPEN NEW STAT FILE (STATNEW)

Reason:
The STATNEW DD file failed open processing.

Action:
Make sure that the STATNEW DD is specified and points to the correct file.

CA-7.STAT-100

STATISTIC FILES MERGED.

Reason:
The STAT file has been successfully merged.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 757

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCA-01

INVALID PARAMETERS AT ENTRY

Reason:
Invalid calling parameters were detected for the job, started task or TSO user. The
SASSSVCA program can only be called from another program that must supply a
correctly formatted parameter list, such as SASSTRLR or U7SVC. This is a critical error
that will cause a U0001 abend and dump.

Action:
Be sure that CA Workload Automation SE modules in the STEPLIB or LINKLIST are at the
same release and generation levels to avoid possible incompatibilities. Save all output
from the task and contact CA Support at ca.com/support for assistance.

CA-7.SVCA-02

CONTROL MODULE NOT LOADED, SVC UNKNOWN

Reason:
The instance control block (ICMDSECT) could not be located. This is a critical error that
will cause a U0002 abend and dump.

Action:
Verify that CAIRIM has run to initialize the CA Workload Automation SE system
environment on this LPAR. Also ensure that the instance to be used has been added. If
the problem persists, save all output from the task and contact CA Support at
ca.com/support for assistance.

CA-7.SVCA-03

(taskname) INVALID /LOGON FORMAT, DEFAULT OPID ASSIGNED

Reason:
An error was detected in the format of a /LOGON statement for the job, started task or
TSO user identified by the taskname. This is a minor error that will cause a return code
of 4.

Action:
Since commands will not be passed without a security ID, the default ID of CA7DUMMY
is assigned to the commands. See the Security Reference Guide for information about
extracting security IDs and the default used. It is assumed that the default ID is defined
with minimal authority.

758 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCA-04

(taskname) SECURITY EXTRACT FAILED, DEFAULT OPID ASSIGNED

Reason:
An error was detected while trying to extract the security ID of the current user for the
job, started task or TSO user identified by the taskname. This is a minor error that will
cause a return code of 4.

Action:
Since commands will not be passed without a security ID, the default ID of CA7DUMMY
is assigned to the commands. See the Security Reference Guide for information about
extracting security IDs and the default used. It is assumed that the default ID has been
defined for access to CA Workload Automation SE with appropriate authority.

CA-7.SVCA-05

(taskname) SUBMIT CHECK FAILED, SKIPPING INPUT UNTIL NEXT /LOGON

Reason:
A /LOGON was attempted for an ID other than the extracted security ID, but the
required authorization was not defined for the job, started task or TSO user identified by
the taskname. This is a serious error that will cause a return code of 16.

Action:
Since authorization failed for submitting this ID, all commands will be skipped until the
next /LOGON. Commands following the failing /LOGON will not be passed to CA
Workload Automation SE. However, a specially formatted /LOGON statement indicating
the error is passed for reporting purposes.

CA-7.SVCA-06

(taskname) SUBMIT SECURITY NOT DEFINED, OPID CHECKING BYPASSED

Reason:
The security interface indicated that no security definitions exist for the SUBMIT
resource for the job, started task or TSO user identified by the taskname. This is a minor
error that will cause a return code of 4.

Action:
If the security system allows processing of undefined resources, this condition will result
in error messages only and the commands will be passed to CA Workload Automation
SE. If the security system does not allow processing of undefined resources, no
commands will be passed to CA Workload Automation SE.

Chapter 3: CA-7.A - CA-7.X Messages 759

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCA-07

(taskname) BUFFER SIZE EXCEEDED, SKIPPING INPUT UNTIL NEXT /LOGON

Reason:
The commands between /LOGON statements have exceeded the allowable block size
for the job, started task or TSO user identified by the taskname. This is a serious error
that will cause a return code of 8.

Action:
Try inserting additional /LOGON statements in the command stream to force blocking.
Since the commands are passed in a variable record format, the number of commands
that will fit in a block are likewise variable. For large command streams, some
experimentation may be required. To have the current or defaulted security ID used, a
blank /LOGON statement can be inserted in the stream.

CA-7.SVCA-99

(taskname) INVALID RETURN FROM CA-7 SVC, RC=hhhhhhhh

Reason:
An invalid return code has been detected from the CA Workload Automation SE SVC
while passing commands for the job, started task or TSO user identified by the
taskname. The return code from the SVC is indicated in hexadecimal by hhhhhhhh. This
is a serious error that will cause a return code of 8.

Action:
Verify that the correct SVC number is being used. If the SVC appears to be in order, save
all output from the task and contact CA Support at ca.com/support for assistance.

760 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCT000E

INDICATOR BYTE NOT SET.

Reason:
The code indicating that the job was submitted by CA Workload Automation SE was not
found at the location in the SMF Common Parameter Area that was specified on the
GLOBAL INIT statement in the System Configuration File. This may indicate a tracking
error.

Action:
Make the appropriate corrections in case:
■ The U7TESTSV job was not demanded by CA Workload Automation SE.
■ Column 71 of the first JOB statement has been modified or columns 70/71 are not
blank.
■ There is a conflict over the use of either the USERID field or the RDRTIME field in
the SMF Common Parameter Area so that the CA Workload Automation SE
indicator byte has been overlaid (probably by another UJV exit).
■ The CA Workload Automation SE UJV exit is not getting control. This may occur if
the IEFUJV exit is not linked properly.

CA-7.SVCT001E

INDICATOR BYTE IN ICM4 IS INVALID.

Reason:
The SMF indicator byte within an ICMDSECT control block has become corrupted. This
message is generated by U7TESTSV.

Action:
Examine the report generated by program U7TESTSV to determine which CA Workload
Automation SE instance has an invalid SMF indicator byte. Then run a CAIRIM
initialization to delete and add that instance.

CA-7.SVCT002E

CA-7 IS NOT INITIALIZED.

Reason:
CA Workload Automation SE control blocks are not initialized.

Action:
Run CAIRIM to initialize the product.

Chapter 3: CA-7.A - CA-7.X Messages 761

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCT003E

TCT VALUE IS ZERO.

Reason:
A system control block contains an invalid address field.

Action:
Contact your local systems programmer to determine whether there are any system
problems. If there are none, contact CA Support at ca.com/support for assistance.

CA-7.SVCT005E

BLDL FAILED.

Reason:
An attempt to locate the UJV, U83, U84 exits failed because of an I/O error.

Action:
This is a severe error. If there is no problem accessing modules on the library where the
UJV, U83 and U84 exits are located, contact CA Support at ca.com/support for
assistance.

CA-7.SVCT006W

xxxxxxxx FOUND IN STEPLIB.

Reason:
The module named xxxxxxxx was located in one of the libraries in the STEPLIB
concatenation, probably the CA Workload Automation SE load library.

Action:
The module named cannot be properly validated because only the copy accessed by
SMF (residing in LPA) will be used in job tracking. Any modules named IEFUJV, IEFU83,
IEFU84, CA7UJV, CA7U83, or CA7U84 on any library in the STEPLIB concatenation should
be renamed to allow the validation to proceed.

762 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCT011E

ICOM FOR xxxx NOT ACTIVE ON THIS CPU.

Reason:
Program U7TESTSV checks the indicator byte to determine under which instance of CA
Workload Automation SE the program is running. Next, it checks to determine whether
SASSICOM is running for that instance. If the indicator byte is set, xxxx is the instance
name. If the indicator byte is not set (see message CA-7.SVCT000E), xxxx defaults to
CA71.

Action:
If message CA-7.SVCT000E is generated, follow the instructions for that message first.
Next, start SASSICOM for the specified instance.

CA-7.SVCT013E

UNABLE TO LOAD xxxxxxxx

Reason:
An attempt to LOAD the module named at xxxxxxxx failed.

Action:
Review any IBM messages associated with the LOAD failure and make appropriate
corrections. Make sure that the module named is in LPA.

CA-7.SVCT019E

UNABLE TO OPEN SYSPRINT DCB.

Reason:
The system could not open the SYSPRINT DCB to write the report.

Action:
Ensure the JCL is correct and resubmit the job.

Chapter 3: CA-7.A - CA-7.X Messages 763

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVCT098I

BAD TERMINATION. ERR CODE = xxxxxxxx

Reason:
This signifies abnormal termination. The errors that caused the abnormal termination
should be indicated in previous messages whose prefix ends with E or W. The ERR CODE
value is an internal code used by CA Support for debugging purposes.

Action:
None. See the previous messages.

CA-7.SVCT099I

NORMAL TERMINATION FOR THIS JOB IS A U0099 ABEND.

Reason:
This signifies normal termination. No problems were found with the CA Workload
Automation SE SVC or CA Workload Automation SE SMF exits.

Action:
None.

CA-7.SVC3

POSSIBLE TRACKING DATA LOST IN CSA

Reason:
A CSA storage overlay has been detected by CA Workload Automation SE. An external
source has overlaid a chain used by CA Workload Automation SE.

The loss of tracking data can result in various CA Workload Automation SE problems. For
example:
■ A job may stay in the ACTQ and never go back to the REQQ for completion
processing.
■ A job may stay in the RDYQ and never go to the ACTQ.
■ A data set posting may never automatically occur.

Action:
Many CSA overlays cause the entire system to fail; hence, an IPL should be done as soon
as possible. CA Workload Automation SE can sometimes recognize if its data has been
overlaid and attempts a partial recovery; however, since CSA has been overlaid, an IPL
should be scheduled as soon as possible.

764 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.SVC4

POSSIBLE TRAILER DATA LOST IN CSA

Reason:
See CA-7.SVC3.

Action:
See CA-7.SVC3.

Also, the loss of Trailer data can result in commands not being given to CA Workload
Automation SE. For example a SASSTRLR or U7SVC DEMAND command may be lost.

CA-7.SVC9

POSSIBLE TRACKING DATA LOST IN CSA

Reason:
See CA-7.SVC3.

Action:
See CA-7.SVC3.

CA-7.S3

NCF INTERFACE IS INACTIVE

Reason:
CA Workload Automation SE NCF is not active and the NCF data is discarded. Processing
continues. A job belonging to CA Workload Automation SE at a remote node is executing
without the support of CA Workload Automation SE NCF and its SMF/Trailer data has
been lost.

Action:
If possible, activate the CA Workload Automation SE NCF interface and promptly inform
the Production Control Supervisor.

Note: This message may be associated with CA Workload Automation SE NCF incoming
data. For appropriate action, see the documentation for the INCOMING DATA REJECTED
message.

Verify that CA Workload Automation SE NCF has been properly installed.

Chapter 3: CA-7.A - CA-7.X Messages 765

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.S3

INVALID NCF NODE ID xx (HEX)

Reason:
The NCF node identifier shown is invalid. The data is discarded and processing
continues.

Action:
Promptly inform the Production Control Supervisor. Each defined CA Workload
Automation SE identifier in the NCF node control table must represent one and only one
NCF node and may have any value except X'00', X'40', or X'E0' through X'FF'.

CA-7.S3

DATA FOR JOB xxxxxxxx DISCARDED

Reason:
SMF or Trailer data for the job shown has been discarded.

Action:
See the two preceding messages.

CA-7.S3

INCOMING DATA REJECTED

Reason:
NCF is receiving data but the CA Workload Automation SE NCF interface is not active or
the incoming data does not belong to your installation's CA Workload Automation SE
node. The NCF node from which the data was received is logged off. No data is lost.

Action:
If possible, activate the CA Workload Automation SE NCF interface. Verify proper
installation of CA Workload Automation SE NCF. This verification requires coordination
with remote nodes. If the problem persists, contact your installation specialist for
assistance.

766 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.S9

BLOCKED RECORD EXCEEDS BUFFER SIZE

Reason:
A set of blocked Trailer records exceeds the buffer size for trailers. The blocked set of
records will be skipped and ICOM will continue to process other records. Trailer data has
been discarded, but the processing continues. This could indicate an erroneous or
incomplete installation or upgrade.

Action:
Contact your installation specialist to verify the installation of CA Workload Automation
SE. Some data has been lost from Trailer Step or U7SVC input that could affect
production work.

CA-7.S9

NO BUFFER FOR OUTBOUND DATA

Reason:
The NCF buffer pointer is zero. SMF or Trailer data has been discarded, but the
processing continues. Promptly inform the Production Control Supervisor.

Action:
Verify proper installation of CA Workload Automation SE NCF.

CA-7.S9

DATA FOR JOB xxxxxxxx DISCARDED

Reason:
SMF or Trailer data for the job shown has been discarded.

Action:
See the two preceding messages.

Chapter 3: CA-7.A - CA-7.X Messages 767

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.S9

INCOMING DATA REJECTED

Reason:
NCF is receiving data but the CA Workload Automation SE NCF interface is not active or
the incoming data does not belong to your installation's CA Workload Automation SE
node.The NCF node from which the data was received is logged off. No data is lost.

Action:
If possible, activate the CA Workload Automation SE NCF interface. If the problem
persists, contact your installation specialist for assistance. Verify proper installation of
CA Workload Automation SE NCF. This requires coordination with remote nodes.

CA-7.TARI

- ARF DATA BASE IS NOW OFFLINE

Reason:
The 'ARFIO SHUTDOWN' call to SASSTARI has completed successfully. The ARF database
is now closed, but the ACB and buffer pool has been retained.

Action:
None.

CA-7.TARI

- ARF DATA BASE WAS NOT ONLINE

Reason:
An 'ARFIO SHUTDOWN' call to SASSTARI was performed to CLOSE the ARF database, but
the ARF database was not OPEN. This is accompanied with a return code of 4.

Action:
None.

768 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TARI

- ARF DATA BASE SHUTDOWN COMPLETE

Reason:
The 'ARFIO SHUTDOWN' call to SASSTARI has completed successfully.

Action:
None.

CA-7.TARI

- ARF DB TERM ERROR: RC=xxxx RS=rrrr INF=iiii

Reason:
An error has occurred during ARF database shutdown. The return, reason and
information codes define the problem exactly. See the list of return codes that follows.

Action:
The ARF database may still be OPEN. CA Workload Automation SE shutdown continues.
RC=0004
ARF database was not OPEN.
RC=0008
ARF initialization did not complete, CLOSE not attempted.
RC=0012
ARF database was never initialized.
RC=0016
ARF database CLOSE failed. R0=00CLOSE return code. R1=CLOSE reason code.
RS=0004
The ARF database did not CLOSE properly.
The information code explains why the CLOSE failed.
INF=0004
Data set is already closed.
INF=0132
Uncorrectable I/O error occurred while reading the JFCB.

Chapter 3: CA-7.A - CA-7.X Messages 769

CA-7.D32V Through CA-7.VDB0 Messages

INF=0136
Not enough virtual storage to complete the CLOSE request.
INF=0144
Uncorrectable I/O error occurred while updating the ICF catalog records.
INF=0148
Error occurred during catalog search.
INF=0184
Uncorrectable error occurred while completing the outstanding requests.

CA-7.TRLR-00

(taskname) PROCESS {STARTING|COMPLETE} JOBSTEP=ssssssss,

PROCSTEP=pppppppp, NODE=nnnnnnnn, OPT=oooooooo, CA7=CA7n

Reason:
This is an informational message indicating the start or completion of Trailer program
processing. The name of the job executing the program is indicated by taskname. The
job-step name is indicated by ssssssss. The procedure step name is indicated by
pppppppp. The NCF node name, if present, is indicated by nnnnnnnn. Any PARM options
are indicated by oooooooo. The CA Workload Automation SE instance number to which
this trailer execution was directed is shown in CA7n.

Action:
None.

CA-7.TRLR-01

(taskname) UNABLE TO LOAD xxxxxxxx, NO INPUT PROCESSED

Reason:
The module xxxxxxxx could not be loaded by the Trailer program running under the job,
started task or TSO user identified by taskname. This is a serious error that will cause a
return code of 8.

Action:
Verify that the named module is available in STEPLIB or a LINKLIST library. If module is
present and problem persists, save job logs and contact CA Support at ca.com/support
for assistance.

770 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TRLR-02

(taskname) PARM=ACT REQUESTED BUT ICOM IS NOT ACTIVE

Reason:
The parameter value of ACT was specified but ICOM for the instance was not active on
the CPU where taskname was executed. This is a serious error that will cause a return
code of 8.

Action:
Determine whether ICOM must really be active for the commands being processed. If
ICOM does not need to be active, remove the ACT parameter and rerun the job. If ICOM
must be active, verify that an ICOM for the instance is installed and active on the CPU in
question. If this does not work, save the job logs and contact CA Support at
ca.com/support for assistance.

CA-7.TRLR-03

(taskname) DDN=CA7IN/SYSIN MISSING

Reason:
No DD statement was found to supply input to the Trailer program. The program looks
first for CA7IN then for SYSIN. Either ddname may be supplied, but only one will be
used. This is a serious error that will cause a return code of 8.

Action:
Check your JCL for the ddnames indicated. Verify that one or the other is specified.

CA-7.TRLR-04

(taskname) DDN=CA7PRINT/SYSPRINT/SYSOUT MISSING

Reason:
No DD statement was found to supply output from the Trailer program. The program
looks first for CA7PRINT then for SYSPRINT and finally for SYSOUT. Either ddname may
be supplied, but only one will be used. This is a serious error that will cause a return
code of 8.

Action:
Check your JCL for the ddnames indicated. Verify that one or the other is specified.

Chapter 3: CA-7.A - CA-7.X Messages 771

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TRLR-05

(taskname) DDN=xxxxxxxx OPEN FAILED

Reason:
The ddname specified by xxxxxxxx could not be opened. This is a serious error that will
cause a return code of 8.

Action:
Verify that the JCL for the specified ddname consists of the correct types of parameters
for the indicated name. Correct any errors and rerun the job.

CA-7.TRLR-06

(taskname) SASSTRAN TABLE FORMAT ERROR, PROCESSING TERMINATED

Reason:
The SASSTRAN module had an invalid format. The SASSTRAN module is used to screen
commands by application area. Internal security levels are ignored for this purpose. This
is a serious error that will cause a return code of 8.

Action:
Verify that the STEPLIB points to a library for the current release level of CA Workload
Automation SE. Also, verify that no libraries in the STEPLIB concatenation contain old
versions of SASSTRAN.

CA-7.TRLR-07

(taskname) ERROR PROCESSING {PARM} INPUT

Reason:
An error occurred processing input indicated. The type of input will be indicated as
PARM or DATA depending on whether it came from PARM or DD input. This is a serious
error that will cause a return code of 8. The parameters TEST=YES and CA7=nnnn are
mutually exclusive.

Action:
The PARM or DATA causing the error will be listed just before this message. Correct the
error and rerun.

772 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TRLR-08

(taskname) NCF ROUTING REQUESTED BUT NCF NOT INSTALLED

Reason:
The NCFNODE= parameter was specified but NCF is not installed. This is a serious error
that will cause a return code of 8. This message can also be issued if you specify a CA7=
parameter value other than CA71.

Action:
If NCF routing is not required, remove the NCFNODE= parameter and rerun the job. If
NCF routing is wanted, verify the NCF installation. Note, that beginning with CA
Workload Automation SE r11, NCF can only be used by the CA71 instance. If you have
specified the CA7= parameter, it must equal CA71.

For information about installing and verifying the NCF component, see the Interface
Reference Guide.

CA-7.TRLR-09

(taskname) NCF ROUTING REQUESTED BUT NODE (xxxxxxxx) NOT FOUND

Reason:
NCF routing was requested using the NCFNODE= parameter but the node indicated by
xxxxxxxx was not found in the UCC7NODE table. This is a serious error that will cause a
return code of 8.

Action:
Verify the node name requested and check that it is in the UCC7NODE module installed
or initialized by CAIRIM.

CA-7.TRLR-10

COMMAND NOT IN SPO0 APPLICATION

Reason:
The command listed immediately before this message is not in the SPO0 application
group and may not be issued. The specified command will not be passed to CA
Workload Automation SE for processing, but any other commands in this stream will be
passed. This is a minor error that will cause a return code of 4.

Action:
Determine whether another command will satisfy your purpose and change the
command accordingly or remove it from the input stream. If the command must be
used, consider the U7SVC program that is not restricted to SPO0 commands.

Chapter 3: CA-7.A - CA-7.X Messages 773

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TRLR-11

(taskname) xxxx NOT MATCHED IN ICMDSECT

Reason:
The instance name xxxx was not found in the instance control block (ICMDSECT). This
name is used for enqueuing certain items (SVC chained data, and so on). No data was
processed because a mismatch could cause system and data integrity problems.

Action:
Ensure that the CA Workload Automation SE system environment was properly
initialized using CAIRIM. Also ensure that the target instance is active. If you want to
verify the status of the CA Workload Automation SE system environment, run the
CAL2ENVR utility. If NCF routing is required and you have entered the NCFNODE=
parameter, the CA7= parameter must specify CA71 and not an alias name.

CA-7.TRLR-99

(taskname) ERROR RETURN FROM SASSSVCA, RC=hhhhhhhh

Reason:
An invalid return code was returned from the SASSSVCA program. The code returned is
indicated in hexadecimal by hhhhhhhh. Error messages from SASSSVCA probably
precede this one and will detail the error. This is a serious error that will cause a return
code matching the one from SASSSVCA.

Action:
See the preceding messages for corrective action.

CA-7.TRLR-nn

(taskname) INPUT--> x...x

Reason:
This message will follow another error message concerning input errors, and lists the
input causing the error. The nn will be replaced by the message number that identifies
the actual error.

Action:
See the preceding messages for corrective action.

774 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.TVRM-03

RESOURCE FILE SUCCESSFULLY CLOSED

Reason:
During CA Workload Automation SE shutdown. VRM has closed the VRM database file.

Action:
None.

CA-7.UJV

NCF NODE CONTROL TABLE NOT DEFINED

Reason:
The NCF node control table was not found.

Action:
See the message that follows.

CA-7.UJV

INVALID NCF NODE ID xx (HEX)

Reason:
The NCF node identifier shown is invalid.

Action:
See the message that follows.

CA-7.UNLK

CHAIN SERIALIZATION ERROR. SCT=xxxxxxxx

Reason:
A CA Workload Automation SE execution thread did not release all of its chain locks
before releasing control. The address of the SCT is listed in the message. Any locks still
held by the SCT are released by the process that produces this message.

Action:
For assistance in debugging the error if the message occurs more than once, contact CA
Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 775

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SMF01

DATE/TIME FORMAT INVALID

Reason:
One or both of the date/time fields was not numeric or did not fall within the proper
columns. Program U7SMF01 sets RC=4.

Action:
Ensure the date/time fields are numeric and that they begin in columns 20 and/or 30.
Then resubmit the job.

CA-7.U7SMF01

ERROR READING FROM SMFMANX

Reason:
Program U7SMF01 could not read a record from the SMFMANX data set. Return code 20
is set.

Action:
Ensure the SMFMANX DD statement is pointing to an SMF data set. If it is, contact your
local systems programmer for assistance. If the input file is a sequential file, ddname
SMFSEQ should be used.

CA-7.U7SMF01

ERROR WRITING TO SNAPDD

Reason:
A SNAPDD DD statement was provided, but program U7SMF01 could not write a SNAP.
The program sets RC=3.

Action:
Verify that the SNAPDD DD statement points to SYSOUT or to a data set that has the
following attributes: DSORG=PS,RECFM=VBA,MACRF=(W),BLKSIZE=nnn,LRECL=125, and
DDNAME=any name but SYSABEND, SYSMDUMP, or SYSUDUMP. BLKSIZE must be either
882 or 1632.
Then resubmit the job.

776 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SMF01

SMFMANX / SMFSEQ MISSING

Reason:
The JCL must contain either a SMFMANX DD statement or a SMFSEQ DD statement.
Neither is present. Program U7SMF01 sets RC=2.

Action:
Correct the JCL to add the appropriate missing DD statement and resubmit the job.

CA-7.U7SMF01

SYSIN MISSING

Reason:
The JCL must contain a SYSIN DD statement. It is missing. Program U7SMF01 sets RC=1.

Action:
Correct the JCL to add the missing DD statement and resubmit the job.

CA-7.U7SVC-00

(taskname) PROCESS {STARTING|COMPLETE} JOBSTEP=ssssssss,

PROCSTEP=pppppppp, NODE=nnnnnnnn, OPT=oooo

Reason:
This is an informational message indicating the start or completion of U7SVC program
processing. The name of the job executing the program is indicated by taskname. The
job-step name is indicated by ssssssss. The procedure step name is indicated by
pppppppp. The NCF node name, if present, is indicated by nnnnnnnn. Any PARM options
are indicated by oooo.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 777

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SVC-01

(taskname) UNABLE TO LOAD xxxxxxxx, NO INPUT PROCESSED

Reason:
A load was attempted for module name xxxxxxxx but failed. The name of the job,
started task or TSO user who invoked U7SVC is shown as taskname. This is a serious
error that will cause a return code of 8.

Action:
Verify that the named module is available in STEPLIB or a LINKLIST library. Also, check
CAIRIM that may be responsible for loading the module.

CA-7.U7SVC-02

(taskname) DDN=CA7DATA/UCC7DATA MISSING AND NO PARM INPUT

Reason:
Neither of the ddnames indicated was found and no parameter input was present for
this execution of U7SVC. The name of the job, started task or TSO user who invoked
U7SVC is shown as taskname. This is a serious error that will cause a return code of 8.

Action:
Since no input was detected, no processing occurred. Supply PARM= input or DD input
using one of the ddnames indicated and rerun the job or reissue the request.

CA-7.U7SVC-03

(taskname) DDN=xxxxxxxx OPEN FAILED, {NO} PARM DATA PROCESSED

Reason:
The DD indicated by xxxxxxxx could not be opened. If parameter data was processed,
the value for NO will be blanked. This is a serious error that will cause a return code of 8
if no parameter data was processed. If parameter data was processed, it is considered a
minor error and will return a code of 4.

Action:
Verify the JCL parameters for the named DD statement. Correct any errors and retry the
request.

778 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SVC-04

(taskname) ERROR PROCESSING xxxx INPUT

Reason:
An error occurred while processing input. The type of input (xxxx) will be indicated as
PARM or DATA depending on whether it came from PARM or DD. This is a serious error
that will cause a return code of 8.

Action:
Examine the input listed for errors, correct and resubmit.

CA-7.U7SVC-05

(taskname) NCF ROUTING REQUESTED BUT NCF NOT INSTALLED

Reason:
The NCFNODE= parameter was specified but NCF is not installed. This is a serious error
that will cause a return code of 8.

Action:
If NCF routing is not required, remove the NCFNODE= parameter and rerun the job. If
NCF routing is wanted, verify the NCF installation. See the Interface Reference Guide for
information about installing and verifying the NCF component.

CA-7.U7SVC-06

(taskname) NCF ROUTING REQUESTED BUT NODE (xxxxxxxx) NOT FOUND

Reason:
NCF routing was requested using the NCFNODE= parameter but the node indicated by
xxxxxxxx was not found in the UCC7NODE table. This is a serious error that will cause a
return code of 8.

Action:
Verify the node name requested and check that it is in the UCC7NODE module installed
or initialized by CAIRIM.

Chapter 3: CA-7.A - CA-7.X Messages 779

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SVC-07

(taskname) DATASET NAME MISSING OR TOO LONG

Reason:
A D= command contained a data set name with too many characters. This is a minor
error that will cause a return code of 4. Only this D= command will be skipped.

Action:
Perform the following actions:
■ Check the D= command and correct the data set name.
■ Reissue the request.

CA-7.U7SVC-08

(taskname) VOLSER ENTRY FOR DATASET INVALID

Reason:
A D= command contained a volume serial entry that is invalid. This is a minor error that
will cause a return code of 4. Only this D= command will be skipped.

Action:
Perform the following actions:
■ Check the D= command and correct the volume serial entry.
■ Reissue the request.

CA-7.U7SVC-09

(taskname) SCHID ENTRY FOR DATASET INVALID

Reason:
A D= command contained a schedule ID entry that is invalid. This is a minor error that
will cause a return code of 4. Only this D= command will be skipped.

Action:
Perform the following actions:
■ Check the D= command and correct the schedule ID entry.
■ Reissue the request.

780 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SVC-10

(taskname) LTERM ENTRY FOR DATASET INVALID

Reason:
A D= command contained a logical terminal entry that is invalid. This is a minor error
that will cause a return code of 4. Only this D= command will be skipped.

Action:
Perform the following actions:
■ Check the D= command and correct the logical terminal entry.
■ Reissue the request.

CA-7.U7SVC-11

(taskname) DATASET CREATE {REJECTED} BY SECURITY

Reason:
A security error occurred for a D= command. Depending on the security package
involved, the message will indicate that the request was REJECTED or IGNORED. The
request may be IGNORED if security is undefined or the data set is unprotected.
Requests that are IGNORED cause a return code of 4 and are considered minor errors
that are passed on to CA Workload Automation SE. Errors that are REJECTED are
considered serious errors that are not passed to CA Workload Automation SE, but cause
a return code matching that returned by the security interface.

Action:
Correct any security definitions required before issuing the request again. Security
requires that the issuer have CREATE authority for the data set indicated.

CA-7.U7SVC-12

(taskname) xxxx NOT MATCHED IN ICMDSECT

Reason:
The name xxxx was not matched in the instance control block (ICMDSECT). Since this
name is used for enqueuing certain items (SVC chained data, and so on), such a
mismatch could cause system and data integrity problems. No data was processed.

Action:
Be sure the system was initialized using CAIRIM. Also ensure that the target instance is
active. If you want to verify the status of the CA Workload Automation SE system
environment, run the CAL2ENVR utility.

Chapter 3: CA-7.A - CA-7.X Messages 781

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U7SVC-98

(taskname) ERROR RETURN FROM CA-7 SVC, RC=hhhhhhhh

Reason:
For the job, started task or TSO user identified by taskname, an invalid return code has
been detected from the CA Workload Automation SE SVC while passing commands. The
return code from the SVC is indicated in hexadecimal by hhhhhhhh. This is a serious
error that will cause a return code of 8.

Action:
Verify that the correct SVC number is being used. If the SVC appears to be in order, save
all output from the task and contact CA Support at ca.com/support for assistance.

CA-7.U7SVC-99

(taskname) ERROR RETURN FROM SASSSVCA, RC=hhhhhhhh

Reason:
An invalid return code was returned from the SASSSVCA program. The code returned is
indicated in hexadecimal by hhhhhhhh. Error messages from SASSSVCA probably
precede this one and will detail the error. This is a serious error that will cause a return
code matching the one listed from SASSSVCA.

Action:
See the preceding messages for corrective action.

CA-7.U7SVC-nn

(taskname) INPUT--> x...x

Reason:
This message will follow another error message about input errors and lists the input
causing the error. The nn will be replaced by the message number that identifies the
actual error.

Action:
See the preceding messages for corrective action.

782 Message Reference Guide

 CA-7.D32V Through CA-7.VDB0 Messages

CA-7.U83

SASSU83 ENTERED

Reason:
This WTO is produced when a job is submitted to a CA Workload Automation SE system
that has a step name of CA7B$$4U in it and a data set open occurs. (To be sure that a
data set open occurs, use a STEPLIB DD in the JCL.) CA Support sometimes requests that
you run a job with this step name in it to be sure that SASSU83 is getting control.

Action:
None.

CA-7.U84

- LCT COULD NOT BE FOUND

Reason:
The Linkage Control Table (LCT) could not be found in core for a job run under CA
Workload Automation SE. The LCT is searched for during step and job termination.
Issued by SASSU84.

This message is produced when an initiator abends.

Action:
Determine the cause of the initiator abend. This message is a result of an initiator abend
and not the cause of the abend. This message is informational only.

CA-7.U84

SASSU84 ENTERED

Reason:
This WTO is produced when a job is submitted to a CA Workload Automation SE system
that has a step name of CA7B$$4U in it. CA Support sometimes requests that you run a
job with this step name in it to be sure that SASSU84 is getting control.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 783

CA-7.D32V Through CA-7.VDB0 Messages

CA-7.VDB0

- No records written to VRMOUT.

Reason:
Self-explanatory. A U3000 abend occurs.

Action:
Ensure that the correct database is being used, and rerun the job.

CA-7.VDB0

- No report will be written to SYSPRINT.

Reason:
The SYSPRINT DD failed the OPEN processing.

Action:
If the report is needed, add the SYSPRINT DD to the JCL and rerun the job.

CA-7.VDB0

- Non-zero return code from SORT.

Reason:
The SORT has returned a nonzero return code. Check the output for SORT errors.

Action:
Correct the errors and rerun the job.

CA-7.VDB0

- SASSVDB0 abended because of possible SORT error.

Reason:
The SORT has returned a non-zero return code. CA Workload Automation SE terminates
with a U4000 abend. Issued by SASSVDB0.

Action:
Check the output for SORT errors and rerun the job after correcting them.

784 Message Reference Guide

 CA-7.VTAM Through CA-7.V001 Messages

CA-7.VDB0

- VRMIN DD statement must be supplied.

Reason:
The VRMIN DD is missing or specified incorrectly. A U1000 abend occurs.

Action:
Correct the problem and rerun the job.

CA-7.VDB0

- VRMOUT DD statement must be supplied.

Reason:
The VRMOUT DD is missing or specified incorrectly. A U1100 abend occurs.

Action:
Correct the problem and rerun the job.

CA-7.VTAM Through CA-7.V001 Messages

This topic contains the CA-7.VTAM through CA-7.V001 messages.

CA-7.VTAM

- TPEND EXIT REQUESTED VTAM ACB CLOSE

Reason:
The CA Workload Automation SE TPEND exit has been scheduled by VTAM. This exit is
given control whenever VTAM terminates abnormally or is shut down (HALT). The ACB
linking the CA Workload Automation SE application to VTAM is closed. Issued by
SASSLMGR.

Action:
After VTAM has been restarted, an /OPEN,GROUP=groupname must be done from a
non-VTAM terminal to OPEN the ACB and allow access to CA Workload Automation SE
through VTAM terminals.

Chapter 3: CA-7.A - CA-7.X Messages 785

CA-7.VTAM Through CA-7.V001 Messages

CA-7.VTAM

- SASSLMGR NOT ASSEMBLED FOR VTAM

Reason:
The program that handles the CA Workload Automation SE TP control has not been
assembled for VTAM. When a user who does not have VTAM macros modifies or applies
fixes to this module, it must be assembled with the &VTAM symbolic set to NO. If this
occurred, subsequent attempts to use VTAM without reassembly with &VTAM set to
YES result in this message. A U0499 abend accompanies this message. Issued by
SASSLMGR.

Action:
Perform the following actions:
■ Verify the source statement sequence # 00007000.
■ Verify that the &VTAM symbolic is being set to YES.
■ Assemble and link edit SASSLMGR.
■ Link edit the CA Workload Automation SE nucleus again.

CA-7.VTAM

- CONNECTION (xxxxxxxx) COMPLETE

Reason:
This informational message indicates that the VTAM terminal (node name xxxxxxxx) is
successfully connected to CA Workload Automation SE. Issued by SASSI32V.

Action:
None.

CA-7.VTAM

- DISCONNECTED

Reason:
This informational message indicates that the VTAM terminal is disconnected from CA
Workload Automation SE.

Action:
None.

786 Message Reference Guide

 CA-7.VTAM Through CA-7.V001 Messages

CA-7.V001

rc yy 00 00000000 tttttt 0000000 00 xxxxxxxx

Reason:
rc is the return code from an ACB OPEN or CLOSE failure, or a SETLOGON failure. For an
open or close failure, yy is the ACBERFLG field. tttttt is the time of day and xxxxxxxx is
the operation that failed, either OPEN, CLOSE or SETLOGON. Issued by SASSBTMV.

Action:
For OPEN/CLOSE, verify that the APPL specified on the UCC7VTAM statement is the
name of the APPL macro defining CA Workload Automation SE to VTAM. For SETLOGON,
verify that the CA Workload Automation SE application in VTAM is allowing LOGONs to
be queued. A VTAM operator command (DISPLAY) can be used to determine application
status.

CA-7.V001

rc aa bb ssssssss hhmmss nnnnnnn cc d xxxxxxxxxx

Reason:
This is a VTAM I/O completion message with the following fields:
rc
Specifies the return code in R15 from the CHECK macro, or xx if the CHECK macro
was not issued.
aa
Specifies the RPLRTNCD (RTNCD) field from the RPL involved with the request.
bb
Specifies the RPLFDB2 (FDBK2) field from the RPL involved with the request.
ssssssss
Specifies the sense information from the RPL. RPLSSEI (SSENSEI) is the first two
positions, RPLSSMI (SSENSMI) is the next two positions, and RPLUSNSI (USENSEI) is
the last four positions.
hhmmss
Specifies the time of day.
nnnnnnn
Specifies the CA Workload Automation SE terminal name (the NAME on the TERM
statement). This may be all Xs if the terminal name is not available.

Chapter 3: CA-7.A - CA-7.X Messages 787

Format for VSAM Database Messages

cc
Specifies the RPLREQ field from the RPL.
d
Specifies either a C if a CHECK macro has been issued, or an R if the CHECK macro
was not issued because the original macro request (RPLREQ) was not accepted.
xxxxxxx
Specifies a general error description.

Issued by SASSI32V.

Action:
See Appendix C of the IBM ACF/VTAM Macro Language Reference Manual for a detailed
explanation of the RPLRTNCD, RPLFDB2, RPLSSEI, RPLSSMI, RPLUSNSI return code fields.
In Appendix H, the IFGRPL DSECT defines the RPLREQ field. Contact your installation
specialist for assistance if an analysis of the error message does not clarify the problem.

Format for VSAM Database Messages

This topic contains the VSAM database messages.

788 Message Reference Guide

 Format for VSAM Database Messages

CA-7.Vnnn

s mmmm (dddd) message text

This message is the format of VSAM database error messages displayed as a WTO. Some
of these messages, called noncrux messages, contain RC=xx REAS=yy. Others, called crux
messages, do not contain RC=xx REAS=yy. A crux message is the first message to appear
when a problem occurs. As the system backs out to successively higher logic levels,
other messages related to the problem occur and display the return codes and reason
codes that they received from the lower level.
Vnnn
The unique message number. This is the primary sequence of the following VSAM
messages. The following conventions have been observed in the numbering of
VSAM system messages:
002 - 099
Common messages issued within all modules.
100 - 299
Messages issued within functional modules.
300 - 499
Messages issued within subroutine modules.
500 - 599
Messages issued within environment modules.
600 - 699
Messages issued on return from external routines.
700 - 799
Messages issued on return from functional modules.
800 - 899
Messages issued on return from subroutine modules.
900 - 999
Messages issued on return from environment modules.

Chapter 3: CA-7.A - CA-7.X Messages 789

CA-7.V002 Through CA-7.V020 Messages

s
Severity indicator. Contains one of the following values:
I
Information
W
Warning
E
Error
mmmm
The last four characters of the module name (for example, V0A0).
dddd
Displacement within the module issuing the error message.
xx
Return code displayed only for noncrux messages. Contains one of the following:
04
Warning.
08
Error encountered, processing cannot continue.
12
Error encountered, system cannot recover.
yy
Reason code displayed only for noncrux messages.
message text
A brief description of the problem encountered.

CA-7.V002 Through CA-7.V020 Messages

This topic contains the CA-7.V002 through CA-7.V020 messages.

790 Message Reference Guide

 CA-7.V002 Through CA-7.V020 Messages

CA-7.V002

s mmmm (dddd) VCTL EYECATCHER NOT 'VCTL'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V003

s mmmm (dddd) VDVT EYECATCHER NOT 'VDVT'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V004

s mmmm (dddd) VSCB EYECATCHER NOT 'VSCB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V005

s mmmm (dddd) VACB EYECATCHER NOT 'VACB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 791

CA-7.V002 Through CA-7.V020 Messages

CA-7.V007

s mmmm (dddd) VCPH EYECATCHER NOT 'VCPH'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V008

s mmmm (dddd) VCRD EYECATCHER NOT 'VCRD'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V009

s mmmm (dddd) VDCB EYECATCHER NOT 'VDCB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V010

s mmmm (dddd) VDGP EYECATCHER NOT 'VDGP'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

792 Message Reference Guide

 CA-7.V002 Through CA-7.V020 Messages

CA-7.V011

s mmmm (dddd) VDTP EYECATCHER NOT 'VDTP'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V012

s mmmm (dddd) VETB EYECATCHER NOT 'VETB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V013

s mmmm (dddd) VHDR EYECATCHER NOT 'VHDR'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V014

s mmmm (dddd) VMSG EYECATCHER NOT 'VMSG'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 793

CA-7.V002 Through CA-7.V020 Messages

CA-7.V015

s mmmm (dddd) VPCB EYECATCHER NOT 'VPCB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V016

s mmmm (dddd) VRCB EYECATCHER NOT 'VRCB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V017

s mmmm (dddd) VRPL EYECATCHER NOT 'VRPL'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V018

s mmmm (dddd) VWCB EYECATCHER NOT 'VWCB'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

794 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V019

s mmmm (dddd) VWRK EYECATCHER NOT 'VWRK'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V020

s mmmm (dddd) VSVT EYECATCHER NOT 'VSVT'

Reason:
The control block identifier could not be located. The control block is either missing or
overwritten.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V101 Through CA-7.V199 Messages

This topic contains the CA-7.V101 through CA-7.V199 messages.

CA-7.V101

s mmmm (dddd) MESSAGE TRACE TABLE UNAVAILABLE

Reason:
A CA Workload Automation SE VSAM message trace table was not allocated during the
initialization.

Action:
Processing continues without the message trace table.

Chapter 3: CA-7.A - CA-7.X Messages 795

CA-7.V101 Through CA-7.V199 Messages

CA-7.V102

s mmmm (dddd) CA-7 VSAM DATABASE NOT ON A DASD DEVICE

Reason:
The CA Workload Automation SE VSAM database must be on a direct-access device.
Initialization cannot continue.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V103

s mmmm (dddd) STORAGE FOR VSVT/VSCB NOT OBTAINED

Reason:
CPU storage for required control blocks could not be acquired. The initialization of CA
Workload Automation SE cannot continue.

Action:
Increase region and retry. If problem persists, save console listings and logs. Contact
your installation specialist for assistance.

CA-7.V104

s mmmm (dddd) COLUMN 1 OF DBPARMS STATEMENT NON-BLANK

Reason:
This message is informational only. It indicates that column 1 of a DBPARMS statement
was nonblank. Since only columns 2-71 are valid for DBPARMS information, the
information in column 1 will be discarded. Syntax errors may result.

Action:
If syntax errors occur on DBPARMS statement, or DBPARMS data is rejected for any
reason, check to see if this error is present. If so, shift data to column 2 and retry.

796 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V108

s mmmm (dddd) MISSING DBPARMS DD STATEMENT

Reason:
The DBPARMS DD statement was not found in the JCL. This data set is required for
VSAM database support. The initialization of CA Workload Automation SE cannot
continue.

Action:
Update the JCL to include a DBPARMS data set. Save console listings and logs.

Note: For more information about the format of this data set, see the Systems
Programming Guide.

If you have added the DD statement and the problem persists, contact your installation
specialist for assistance.

CA-7.V109

s mmmm (dddd) DBPARMS OPEN FAILURE

Reason:
The DBPARMS data set specified in the JCL could not be opened. The initialization of CA
Workload Automation SE cannot continue.

Action:
Check the allocation of the data set as described in the Systems Programming Guide.
Verify data set and retry. If failure persists, contact your installation specialist for
assistance.

CA-7.V110

s mmmm (dddd) SYNAD ERROR ROUTINE ENTERED

Reason:
An error occurred during initialization of the VSAM databases. The initialization of CA
Workload Automation SE cannot continue. The DBPARMS DD statement may be
pointing to a PDS without specifying the member name.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 797

CA-7.V101 Through CA-7.V199 Messages

CA-7.V111

s mmmm (dddd) DYNALLOC RX=xxxx,ERRCD=xxxx,INFOCD=xxxx,DSN=x...x

Reason:
An error occurred during dynamic allocation of the VSAM databases. The reason code,
error code, information code, and data set name are shown. The initialization of CA
Workload Automation SE cannot continue.

Action:
Ensure that the VSAM database data set names match what is specified in the DBPARMS
data set. Also, verify that ddnames for the database do not exist in the execution JCL.
Correct the error and try again. If the problem persists, save console listings and logs.
Contact your installation specialist for assistance.

CA-7.V112

s mmmm (dddd) DBPARMS NOT FOUND

Reason:
The parameters describing the VSAM database could not be found in internal control
blocks.

Action:
Check UCC7DBASE statements in the DBPARMS data set for correct values. If a problem
persists, save console listings and logs. Contact your installation specialist for assistance.

Note: For more information about the DBPARMS statement, see the Systems
Programming Guide.

CA-7.V113

s mmmm (dddd) INVALID TYPE DEFINITION ON DBPARMS

Reason:
The parameters describing the VSAM database do not conform with the Data Type
Vector Table definition in program SASSVY00. The data type may be invalid.

Action:
Check UCC7DBASE statements in the DBPARMS data set for correct values. If a problem
persists, save console listings and logs. Contact your installation specialist for assistance.

Note: For more information about DBPARMS statements, see the Systems
Programming Guide

798 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V114

s mmmm (dddd) DATASET HAS NO DATATYPES DEFINED

Reason:
The parameters describing the VSAM database contain a definition of a data set but do
not include DATATYPE definitions. DATATYPE must be specified for each VSAM data set.

Action:
Review the DBPARMS data set DATATYPE definitions. Correct and reinitialize CA
Workload Automation SE. If a problem persists, save console listings and logs. Contact
your installation specialist for assistance.

Note: For more information about DBPARMS statements, see the Systems
Programming Guide

CA-7.V115

s mmmm (dddd) NON-TERMINAL DYNALLOC ERROR - INFOCD=xxxx,DSN=x...x

Reason:
Dynamic allocation of the VSAM database received a nonfatal error as shown by
INFOCD. Allocation should have been completed, but attention should be given to the
error code.

Action:
Review the INFOCD. If unable to determine the cause, save console listings and logs.
Contact your installation specialist for assistance.

CA-7.V116

s mmmm (dddd) CALLID SPECIFIED NOT USED EXCLUSIVELY FOR

BACKUP FUNCTION

Reason:
The Caller's ID was used for a call other than BACKUP. This is an internal functional
error.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 799

CA-7.V101 Through CA-7.V199 Messages

CA-7.V117

s mmmm (dddd) NUMBER OF VSAM DATASETS EXCEEDS LIMIT

Reason:
The number of VSAM data sets specified during initialization exceeds the number
supported. Initialization cannot continue.

Action:
Be sure DBPARMS statements define only three data sets. If problem persists after
correcting DBPARMS, save console listings and logs. Contact your installation specialist
for assistance.

CA-7.V118

s mmmm (dddd) DATATYPE CODE DUPLICATION IN DBPARMS

Reason:
A DATATYPE entry in the VSAM database definition in DBPARMS has been repeated.
Data types may not span multiple VSAM data sets.

Action:
Correct the DBPARMS parameters to match the database or else back up the database
using program SASSBK00 and reload according to the new DATATYPE configuration.
Contact your installation specialist for assistance.

CA-7.V119

s mmmm (dddd) NUMBER OF DATATYPE CODES EXCEEDS LIMIT

Reason:
The number of DATATYPEs specified in DBPARMS exceeds the number permitted
according to table SASSVY00.

Action:
Correct the DBPARMS parameters to match the number of allowed DATATYPEs. For
more information, see the Systems Programming Guide.

800 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V120

s mmmm (dddd) DATATYPE NOT DEFINED TO VSAM SYSTEM

Reason:
The DATATYPE encountered has not been defined in the Data Relationships Table,
SASSVY00.

Action:
Check the DBPARMS parameters for invalid DATATYPE entries and correct. For more
information, see the Systems Programming Guide.

CA-7.V121

s mmmm (dddd) DATATYPE INVALID FOR SPECIFIED DATASET

Reason:
The DATATYPE encountered was not defined in the specified data set. The DBPARMS
specifications may be incorrect.

Action:
Check the DBPARMS parameters for invalid or missing DATATYPE entries and correct.
For more information, see the Systems Programming Guide.

CA-7.V122

s mmmm (dddd) DATATYPE REQUIRED FOR DATASET UNSPECIFIED

Reason:
A DATATYPE on a VSAM database was not defined in DBPARMS.

Action:
Check the DBPARMS parameters for missing DATATYPE entries and correct. For more
information, see the Systems Programming Guide.

Chapter 3: CA-7.A - CA-7.X Messages 801

CA-7.V101 Through CA-7.V199 Messages

CA-7.V123

s mmmm (dddd) PARAMETER xxxxxx ABSENT OR INVALID

Reason:
A required DBPARMS parameter was not found or contained invalid data. The called
program returns to the caller with an error code. Other messages usually follow.

Action:
Correct the parameter. If problems persist, save console listings and logs. Contact your
installation specialist for assistance.

CA-7.V124

s mmmm (dddd) VSAM KEY NOT IN ASCENDING SEQUENCE

Reason:
A key sequence error was detected while attempting to write to the Backup data set.
The record in error is not written.

Action:
The database record which was in error may need to be reentered correctly after
reload, corrected on the existing database, or both. Save console listings and logs.
Contact your installation specialist for assistance.

CA-7.V126

s mmmm (dddd) ACCTYP=LOAD SPECIFIED WITH SOME OTHER ACCTYP

Reason:
An invalid combination of ACCESS TYPE parameters was used in the call to the VSAM
Connection module. The parameters of the executing program must be specified
correctly.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

802 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V127

s mmmm (dddd) INCOMPATIBLE ACCTYPS xxxxxx AND yyyyyy SPECIFIED

Reason:
An invalid combination of ACCESS TYPE parameters was used in the call to the VSAM
Connection module. The parameters of the executing program must be specified
correctly.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V128

s mmmm (dddd) INCOMPATIBLE ACCSYNS ASYN AND SYNC SPECIFIED

Reason:
An invalid combination of ACCESS parameters, (SYNChronous and ASYNchronous) was
used in the call to the VSAM Connection module. The parameters of the executing
program must be specified correctly by the calling program.

Action:
Correct and resubmit. Save console listings and logs. Contact your installation specialist
for assistance.

CA-7.V129

s mmmm (dddd) ACCSYN=xxxxxx SPECIFIED, BUT yyyyyy SPECIFIED PREVIOUSLY

Reason:
An invalid combination of ACCESS parameters was used in the call to the VSAM
Connection module. The parameters of the executing program must be specified
correctly by the calling program.

Action:
Correct and resubmit. Save console listings and logs. Contact your installation specialist
for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 803

CA-7.V101 Through CA-7.V199 Messages

CA-7.V130

s mmmm (dddd) ACCTYP=xxxxxx SPECIFIED, BUT yyyyyy SPECIFIED PREVIOUSLY

Reason:
An invalid combination of ACCESS TYPE parameters was used in the call to the VSAM
Connection module. BKUP may have been specified after a RELD request. The
parameters of the executing program must be specified correctly by the calling
program.

Action:
Correct and resubmit. Save console listings and logs. Contact your installation specialist
for assistance.

CA-7.V131

s mmmm (dddd) DATASET NOT VSAM, DSN=x...x

Reason:
DBPARMS referenced data set x...x, but the data set is not a VSAM data set.

Action:
Check DSN and DD values in both DBPARMS and execution JCL. Correct the reference so
that a VSAM file is being referenced. Also verify that the ALLVSAM database was
requested. If the problem persists, save the listings and contact your installation
specialist for assistance.

804 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V132

s mmmm (dddd) VSAM DATASET NOT INITIALIZED BY RELOAD, DSN=x...x

Reason:
One of two situations has occurred:
■ If the action taken was not a RELOAD, the data set is empty and unusable.
■ If the action taken was a RELOAD, the data set is not empty and does not contain
the CNTL records required by CA Workload Automation SE.

Action:
Proceed as follows:
■ If the action was not a RELOAD, initialize the data set by performing a RELOAD from
a null backup data set.
■ If the action taken was a RELOAD, verify that DBPARMS is referencing the correct
DSN. If the DSN is correct, use IDCAMS to DELETE the DSN; then retry the RELOAD.
This may be required if the database is on SMS controlled volumes.
■ If the problem persists, save the listings and contact your installation specialist for
assistance.

CA-7.V133

s mmmm (dddd) CALLID xxxxxxxx STILL ACTIVE AT DISCONNECT

Reason:
A thread identified by CALLID was active during DISCONNECT processing. The use of one
of the "fast shutdown" options probably caused this message.

Action:
None.

CA-7.V134

s mmmm (dddd) ATTEMPTED TO DISCONNECT ACCESS TYPE NOT CONNECTED

Reason:
A request to DISCONNECT during termination was for an invalid ACCESS TYPE (for
example, RELD was requested when BKUP was CONNECTed).

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 805

CA-7.V101 Through CA-7.V199 Messages

CA-7.V135

s mmmm (dddd) CONNECTION FAILED DUE TO ABOVE ERRORS

Reason:
A request to CONNECT to the VSAM database failed because of errors found earlier in
the execution.

Action:
See the preceding messages. Save console listings and logs. Contact your installation
specialist for assistance.

CA-7.V136

s mmmm (dddd) LIST CONNECTION SUCCESSFUL

Reason:
A request to CONNECT to the VSAM database for LISTing data was successful.

Action:
None.

CA-7.V137

s mmmm (dddd) ATTEMPTED TO CLOSE BACKUP DD WHEN NOT OPENED

Reason:
A request to close the Backup data set failed because the data set had already been
closed or had not been opened.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V139

s mmmm (dddd) VSAM DATABASE CLOSE FAILED

Reason:
A request to close the VSAM database failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

806 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V140

s mmmm (dddd) END-OF-DATA DETECTED ON BACKUP DD

Reason:
An unexpected END-OF-DATA condition was detected on the Backup data set.

Action:
Verify that the data set being used as input to the database load is the proper Backup
data set. Save console listings and logs. Contact your installation specialist for
assistance.

CA-7.V143

s mmmm (dddd) VRCB SEARCH FAILED

Reason:
A VRCB for a specific data type could not be found on VRCB chain.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V145

s mmmm (dddd) SUBROUTINE MODULE LOAD SEQUENCE FAILED

Reason:
An SVLOAD request for a subroutine could not be completed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V146

s mmmm (dddd) ENVIRONMENT MODULE LOAD SEQUENCE FAILED

Reason:
Initialization requested a load of an environment module which failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 807

CA-7.V101 Through CA-7.V199 Messages

CA-7.V147

s mmmm (dddd) FUNCTIONAL MODULE LOAD SEQUENCE FAILED

Reason:
Initialization requested a load of a main line module which failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V148

s mmmm (dddd) TABLE MODULE LOAD SEQUENCE FAILED

Reason:
Initialization requested a load of a table module which failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V150

s mmmm (dddd) VCTL TOO LARGE FOR BACKUP DD LRECL

Reason:
The LRECL for the Backup data set is smaller than the size of the internal control block
which contains the DBPARMS parameters.

Action:
Increase the LRECL on the BACKUP DD statement and resubmit. Minimum LRECL is 3122.
Contact your installation specialist for assistance as necessary.

CA-7.V151

s mmmm (dddd) UCC7VSAM INITIALIZATION COMPLETE

Reason:
The VSAM databases are ready for processing.

Action:
None.

808 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V152

s mmmm (dddd) ABEND xxx-xx DETECTED IN OPEN/CLOSE/EOV

FOR BACKUP DD - action

Reason:
An abnormal condition occurred while processing the Backup data set.

Action:
Save console listings and logs. If abend code is 002-18, increase the LRECL in the
BACKUP DD. Minimum LRECL is 3122. Contact your installation specialist for assistance.

CA-7.V154

s mmmm (dddd) RELEASE CALLED FOR RELOAD BEFORE EOD DETECTED

Reason:
Termination was requested before all data was processed on the Backup data set.

Action:
The database may need to be reloaded. Save console listings and logs. Contact your
installation specialist for assistance.

CA-7.V155

s mmmm (dddd) SPECIFIED CALLID ALREADY IN USE

Reason:
The CALLER ID used for backup or reload operations cannot be used for any other
purpose while connected for BKUP or RELD. Either BKUP or RELD connection was in
effect and the CALLER ID used for backup or reload was also used for another purpose
(such as to read the VSAM database).

Action:
Correct CALLID conflict and resubmit. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 809

CA-7.V101 Through CA-7.V199 Messages

CA-7.V156

s mmmm (dddd) SPECIFIED DATATYPE NOT DEFINED IN VDVT

Reason:
The DATATYPE encountered has not been defined.

Action:
See program SASSVY00 for definition of data types and relationships.

CA-7.V157

s mmmm (dddd) RELOAD ATTEMPTED W/O LOAD OR RELOAD ACCESS TYPE

CONNECTED

Reason:
A database RELOAD request was made without previously setting up a LOAD/RELOAD
environment.

Action:
Ensure that the job specified the proper parameters on the EXEC statement. Correct the
parameters and resubmit. For more information, see the Systems Programming Guide.

CA-7.V158

s mmmm (dddd) ERROR IN LAST RECORD FLAG

Reason:
The last Record Flag was expected to be turned on in the VPCB, but it was not.

Action:
Verify that the BACKUP DD input to the RELOAD program is correct. Only backup files
created by SASSBK00 can be reloaded. Save console listings and logs. Contact your
installation specialist for assistance.

810 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V159

s mmmm (dddd) RELOAD EOD LOGIC ERROR

Reason:
Program SASSV080 could not complete End-Of-Data processing properly. EOD may have
been detected twice.

Action:
Verify that the BACKUP DD input to the RELOAD program is correct. Only backup files
created by SASSBK00 can be reloaded. Save console listings and logs. Contact your
installation specialist for assistance.

CA-7.V160

s mmmm (dddd) NORMAL CONNECTION ATTEMPTED WITH DBTYPE NOT ALLVSAM

Reason:
The JCL used to execute the job had a parameter other than ALLVSAM when a NORMAL
allocation (CONNECTION) of VSAM databases was requested.

Action:
Correct the JCL and resubmit.

CA-7.V161

s mmmm (dddd) CALLID xxxxxxxx INVALID TYPE/DATATYPE COMBINATION

Reason:
An invalid data set type or data record type was specified. This is probably a
programming error.

Action:
Save console listings and logs, plus any panel messages and commands issued. Contact
your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 811

CA-7.V101 Through CA-7.V199 Messages

CA-7.V166

s mmmm (dddd) DBPARMS DDNAME IS xxxxxxxx

Reason:
This informational message reflects the ddname that is for the database parameter
information.

Action:
None.

CA-7.V167

s mmmm (dddd) DBPARMS PARSE COMPLETE

Reason:
The parse of DBPARMS completed successfully.

Action:
None.

CA-7.V168

s mmmm (dddd) DBPARMS ERROR: IDCAMS CTL STMT SYNTAX ERROR

Reason:
IDCAMS detected a syntax error on DBPARMS input control statements.

Action:
Correct IDCAMS control statement in DBPARMS data set.

CA-7.V169

s mmmm (dddd) DBPARMS ERROR: PARAMETER ABSENT OR INVALID - x...x

Reason:
Parameter x...x is absent or invalid.

Action:
Correct DBPARMS statement and retry.

812 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V170

s mmmm (dddd) DBPARMS ERROR: DDNAME PARAMETER NOT SPECIFIED WITH

ALLOCJCL

Reason:
A DDNAME parameter is required if ALLOCJCL is specified.

Action:
Include DDNAME parameter and retry.

CA-7.V171

s mmmm (dddd) DBPARMS ERROR: ALLOCDYN/ALLOCJCL PARAMETERS MUTUALLY

EXCLUSIVE

Reason:
ALLOCDYN and ALLOCJCL may not both be specified.

Action:
Eliminate either ALLOCDYN or ALLOCJCL and retry.

CA-7.V172

s mmmm (dddd) DBPARMS ERROR: DATATYPES/STRINGS PARAMETERS

INCOMPATIBLE

Reason:
Number of data types specified differs from number of string specifications.

Action:
See that the number of entries for DATATYPE parameter is same as the number of
entries for STRINGS parameter.

Chapter 3: CA-7.A - CA-7.X Messages 813

CA-7.V101 Through CA-7.V199 Messages

CA-7.V173

s mmmm (dddd) DBPARMS ERROR: ALLOCJCL SPECIFIED FOR DDN=xxxxxxxx BUT

DSNAME CONFLICT EXISTS

Reason:
An error was detected for a UCC7DBASE entry in DBPARMS. The error is associated with
DDN=xxxxxxxx. The data set referenced by the DDN in the JCL does not match the NAME
indicated for the DEFINE CLUSTER entry in DBPARMS.

Action:
Perform one of the following actions:
■ Correct the DDNAME entry in DBPARMS.
■ Change the NAME in IDCAMSDEFINE in DBPARMS.
■ Change the DSN in the JCL.

CA-7.V175

s mmmm (dddd) CALLID xxxxxxxx TERM=YES REQUIRES TYPE=OUTP

Reason:
The TERM=YES parameter on an SVEXTPUT macro is specified only internally within the
VSAM system. When used, always use it for TYPE=OUTP.

Action:
Verify that TERM=YES is required. If not, take it off and retry. If so, use TYPE=OUTP or
contact your installation specialist for assistance.

CA-7.V176

s mmmm (dddd) CALLID xxxxxxxx ACCTYP=RELD REQUIRES TYPE=ADD/CAT/OUTP

Reason:
If a database reload has been requested by specifying ACCTYP=RELD on the SVCONN
macro, then SVEXTPUT may only be issued with TYPE=ADD/CAT/OUTP.

Action:
Verify that TYPE=ADD, CAT or OUTP for all SVEXTPUT calls executed.

814 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V177

s mmmm (dddd) CALLID xxxxxxxx LOGIC ERROR ENCOUNTERED

Reason:
An error occurred while attempting to write to or delete an entry in the VSAM database.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V178

s mmmm (dddd) CALLID xxxxxxxx RECRD/BLKAD PARAMETERS NOT ALLOWED ON

TYPE=UPDT OR TYPE=DELT/UNCT

Reason:
An SVEXTPUT macro call was issued with TYPE=UPDT or TYPE=DELT/UNCT which
included a RECRD or BLKAD parameter. These parameters may not be used with the
specified TYPE.

Action:
Correct SVEXTPUT macro call and retry.

CA-7.V179

s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT REQUIRES LAST ACCESS IN UPDATE

MODE

Reason:
An SVEXTPUT macro call was issued with TYPE=UPDT, but a previous SVEXTGET macro
had not been issued for that entry specifying the UPDATE parameter.

Action:
Issue an SVEXTGET call for UPDATE mode before issuing the SVEXTPUT macro,
TYPE=UPDT and retry.

Chapter 3: CA-7.A - CA-7.X Messages 815

CA-7.V101 Through CA-7.V199 Messages

CA-7.V180

s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT REQUIRES EXISTING VBUF/VRPL

Reason:
The VBUF or VRPL control blocks required for this SVEXTPUT call were not found.

Action:
Check that no external macro calls were issued prior to the SVEXTPUT call which would
cause update intent to be released. If none found, save console listings and logs and
contact your installation specialist for assistance.

CA-7.V181

s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON TYPE=RCAT

Reason:
SVEXTPUT was called with TYPE=RCAT, but no RECRD parameter was provided pointing
to the record to be output.

Action:
Provide RECRD parameter and retry.

CA-7.V182

s mmmm (dddd) CALLID xxxxxxxx BLKAD PARAMETER NOT ALLOWED ON TYPE=RCAT

Reason:
SVEXTPUT was called with TYPE=RCAT, and a BLKAD parameter was provided.

Action:
Provide RECRD parameter instead of BLKAD and retry.

CA-7.V183

s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT/REPL/RCAT REQUIRES EXISTING VPCB

Reason:
SVEXTPUT was called with TYPE=UPDT or REPL or RCAT but no previous SVEXTGET had
been done.

Action:
Retrieve record with UPDATE intent before SVEXTPUT call and retry.

816 Message Reference Guide

 CA-7.V101 Through CA-7.V199 Messages

CA-7.V184

s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON TYPE=ADD/CAT

Reason:
SVEXTPUT was called with TYPE=ADD or CAT but no RECRD parameter was provided.

Action:
Add RECRD parameter to calling sequence and retry.

CA-7.V185

s mmmm (dddd) CALLID xxxxxxxx BLKAD PARAMETER NOT ALLOWED ON

TYPE=ADD/CAT

Reason:
SVEXTPUT was called with TYPE=ADD or CAT and a BLKAD parameter was included in
the calling sequence.

Action:
Ensure that calling sequence provides a RECRD parameter but no BLKAD parameter and
retry.

CA-7.V186

s mmmm (dddd) CALLID xxxxxxxx EXISTING VBUF/VRPL NOT ALLOWED ON

TYPE=ADD/CAT

Reason:
SVEXTPUT was called with TYPE=ADD or CAT and a VBUF or VRPL control block was
found to already exist for the data type to be added or cataloged.

Action:
Ensure that record being added or cataloged is not already present in database. If it is
there, either remove it or do not try to add it. If it is not already there, save console
listings and logs and contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 817

CA-7.V101 Through CA-7.V199 Messages

CA-7.V187

s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON TYPE=OUTP FOR

DS DS

Reason:
SVEXTPUT was called with TYPE=OUTP and DSTYPE=DS but no RECRD parameter was
provided.

Action:
Add RECRD parameter to SVEXTPUT call and retry.

CA-7.V188

s mmmm (dddd) CALLID xxxxxxxx BLKAD PARAMETER NOT ALLOWED ON TYPE=OUTP

FOR DS DS

Reason:
SVEXTPUT was called with TYPE=OUTP and DSTYPE=DS and BLKAD parameter was used.

Action:
Ensure that SVEXTPUT calling sequence contains no BLKAD parameter and includes a
RECRD parameter and retry.

CA-7.V189

s mmmm (dddd) CALLID xxxxxxxx RECRD OR BLKAD PARAMETER REQUIRED ON

TYPE=OUTP FOR JOB DS

Reason:
SVEXTPUT was called with TYPE=OUTP and DSTYPE=JOB but no RECRD or BLKAD
parameter was provided.

Action:
Ensure that SVEXTPUT calling sequence includes either a RECRD or BLKAD parameter
and retry.

818 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V190

s mmmm (dddd) CALLID xxxxxxxx TYPE=OUTP REQUIRE EXISTING VBUF/VRPL IN OUTP

MODE

Reason:
SVEXTPUT was called with TYPE=OUTP but no previous SVEXTGET had been executed
with UPDATE intent.

Action:
Issue an SVEXTGET with UPDATE intent prior to the SVEXTPUT call and retry.

CA-7.V199

s mmmm (dddd) NOT ENOUGH SPACE IN WORK AREA FOR USE BY MODULE xxxxxxxx

Reason:
SVSTATUS needed more work area to pass requested data than was provided. If the
calling program is employing the technique suggested below, this message may be
normal.

Action:
The amount of work area required will be returned by SVSTATUS at offset 2 from the
start of the work area. Allocate that much space before calling SVSTATUS. (If work area
required will vary, a trial call of SVSTATUS can be made specifying a 4-byte work area.
SVSTATUS will then return with this message and the exact amount of storage required
in the work area. The correct amount of storage can then be acquired and another call
of SVSTATUS made.)

CA-7.V200 Through CA-7.V299 Messages

This topic contains the CA-7.V200 through CA-7.V299 messages.

Chapter 3: CA-7.A - CA-7.X Messages 819

CA-7.V200 Through CA-7.V299 Messages

CA-7.V200

s mmmm (dddd) KEYNAME xxxxxxxx UNKNOWN TO SASSV090 STATUS MODULE

Reason:
SVSTATUS macro was called specifying a keyblock which pointed to a keyname unknown
to the Status Module, SASSV090.

Action:
Check all keyblocks in calling sequence. See that spelling of each keyname pointed to is
correct and retry.

CA-7.V202

s mmmm (dddd) MORE WORK AREA REQUIRED THAN AVAILABLE

Reason:
SVSTATUS needed more work area to pass requested data than was provided. If the
calling program is employing the technique suggested below, this message may be
normal.

Action:
The amount of work area required will be returned by SVSTATUS at offset 2 from the
start of the work area. Allocate that much space before calling SVSTATUS. (If work area
required will vary, a trial call of SVSTATUS can be made specifying a 4-byte work area.
SVSTATUS will then return with this message and the exact amount of storage required
in the work area. The correct amount of storage can then be acquired and another call
of SVSTATUS made.)

CA-7.V203

s mmmm (dddd) DBPARMS VDCB NOT AVAILABLE

Reason:
SVSTATUS macro was called requesting DBPARMS information before SVINIT macro was
issued to read DBPARMS data set.

Action:
Issue SVSTATUS call after SVINIT call and retry.

820 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V204

s mmmm (dddd) DBPARMS STATEMENTS NOT AVAILABLE

Reason:
SVSTATUS macro was called requesting DBPARMS information before SVINIT macro was
issued to read DBPARMS data set.

Action:
Issue SVSTATUS call after SVINIT call and retry.

CA-7.V205

s mmmm (dddd) BACKUP VDCB NOT AVAILABLE

Reason:
SVSTATUS macro was called requesting BACKUP information before SVCONN macro was
issued to open Backup data set, creating the VDCB.

Action:
Issue SVSTATUS call after SVCONN call and retry.

CA-7.V206

s mmmm (dddd) VSAMDB VCTL NOT AVAILABLE

Reason:
SVSTATUS macro was called requesting VSAM database information before SVINIT
macro was issued to build database control blocks such as VCTL from which SVSTATUS
gets information.

Action:
Issue SVSTATUS call after SVINIT call and retry.

Chapter 3: CA-7.A - CA-7.X Messages 821

CA-7.V200 Through CA-7.V299 Messages

CA-7.V207

s mmmm (dddd) KEYNAME xxxxxxxx IS NOT CONTROL BLOCK ANCHORED OFF VSCB

Reason:
This message is not issued unless the branch control table in SASSV090 contains control
block names which are not anchored off VSCB. This could only happen if a system
modification were made to the VSCB but no corresponding change was made to the
SASSV090 control table.

Action:
Check for any changes made and correct. If unable to determine the cause, save console
logs and listings. Contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.V208

s mmmm (dddd) REQUIRED DDNAME PARAMETER NOT SPECIFIED - DSN=x...x

Reason:
DDNAME is required for each data set on the DBPARMS cards if ALLOCJCL were
specified.

Action:
Add DDNAME parameter to DBPARMS where required and retry.

CA-7.V209

s mmmm (dddd) DATA SET HAS NO TYPES DEFINED - DSN=x...x

Reason:
Each data set defined in the DBPARMS statements must have at least one data type
defined for it.

Action:
Add DATATYPE parameter to DBPARMS for DSN=x...x and retry.

822 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V210

s mmmm (dddd) NOT ALL DATATYPES DEFINED IN DBPARMS

Reason:
Each legal data type must be specified once and only once in the DATATYPE parameter
on the DBPARMS statements.

Action:
Check DBPARMS DATATYPE specifications to be sure all data types are included and
retry.

CA-7.V213

s mmmm (dddd) REQUESTED CONTROL BLOCK xxxx NOT AVAILABLE OR EYECATCHER

INCORRECT

Reason:
The user called the SVSTATUS macro requesting control block xxxx as the keyname in
the keyblock specified. There are two possible reasons for this error. Either the location
pointed to by the VSCB for that control block does not contain the proper eyecatcher for
the control block indicating a system problem or the VSCB pointer is zero, indicating the
control block does not exist.

Action:
Most VSAM control blocks anchored off the VSCB are created at initialization time. A
few, such as the BACKUP VDCB, are only present after connection has been performed.
Ensure that SVINIT and SVCONN have been called before SVSTATUS. If not, correct code
and retry. Otherwise, save console logs and listings. Contact your installation specialist
for assistance.

CA-7.V214

s mmmm (dddd) VCTL TOO LARGE FOR VSAM LRECL - DSN=x...x

Reason:
The VCTL is written out to the database for record keeping and documentation
purposes. It is required that the LRECL for the database be large enough to handle it.

The smallest maximum record size is approximately 3122. For more information about
DBPARMS statements and reloading the database, see the Systems Programming Guide.

Action:
Increase maximum value in RECORDSIZE parameter for the identified data set in the
DBPARMS statements, and then reload the database.

Chapter 3: CA-7.A - CA-7.X Messages 823

CA-7.V200 Through CA-7.V299 Messages

CA-7.V215

s mmmm (dddd) WORKAREA MUST BE AT LEAST 4 BYTES LONG

Reason:
The work area passed to SVSTATUS must be at least 4 bytes long for status to put a
2-byte length available and a 2-byte length needed field in.

Action:
Specify a work area length of at least 4 in SVSTATUS call and retry.

CA-7.V216

s mmmm (dddd) GET FOR UPDATE WITHOUT ACCESS TYPE NORMAL

Reason:
The use of SVEXTGET with UPDATE intent specified indicates the intention of modifying
an existing database. This may only be done if access type specified on SVCONN macro
was NORMAL.

Action:
Resolve SVCONN and SVEXTGET incompatibilities and retry. Contact your installation
specialist for assistance, saving console listings and logs.

CA-7.V217

s mmmm (dddd) GET CALLED WITHOUT CALLID PROVIDED

Reason:
SVEXTGET macro requires CALLID parameter.

Action:
Add CALLID parameter to SVEXTGET call and retry.

CA-7.V218

s mmmm (dddd) GET CALLED WITHOUT KEYAD PROVIDED FOR CALLID xxxxxxxx

Reason:
SVEXTGET macro requires KEYAD parameter.

Action:
Add KEYAD parameter to SVEXTGET call and retry.

824 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V219

s mmmm (dddd) GET CALLED WITHOUT RECTYP PROVIDED FOR CALLID xxxxxxxx

Reason:
SVEXTGET macro requires RECTYP parameter.

Action:
Add RECTYP parameter to SVEXTGET call and retry.

CA-7.V220

s mmmm (dddd) GET CALLED WITHOUT DSTYPE PROVIDED FOR CALLID xxxxxxxx

Reason:
SVEXTGET macro requires DSTYPE parameter.

Action:
Add DSTYPE parameter to SVEXTGET call and retry.

CA-7.V221

s mmmm (dddd) GET CALLED WITHOUT RETTYP PROVIDED FOR CALLID xxxxxxxx

Reason:
SVEXTGET macro requires RETTYP parameter.

Action:
Add RETTYP parameter to SVEXTGET call and retry.

CA-7.V222

s mmmm (dddd) GET CALLED WITHOUT A VALID RETTYP PROVIDED FOR CALLID
xxxxxxxx

Reason:
RETTYP parameter not valid.

Action:
Ensure that SVEXTGET call specified a valid RETTYP.

Chapter 3: CA-7.A - CA-7.X Messages 825

CA-7.V200 Through CA-7.V299 Messages

CA-7.V223

s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=UNIQUE and DSTYPE pointed to a location containing
blanks or ALL. When a retrieval type is unique, a specific DSTYPE must be given or
pointed to.

Action:
Specify DS or JOB or IDS for DSTYPE and retry.

CA-7.V224

s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO RECTYP VALUE FOR
CALLID xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=UNIQUE and RECTYP pointed to a location containing
blanks or ALL. When a retrieval type is unique, a specific RECTYP must be given.

Action:
Specify DIR or MEM or IDS for RECTYP and retry.

CA-7.V225

s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO KEYAD VALUE FOR
CALLID xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=UNIQUE and KEYAD pointed to an invalid location. When
retrieval type is unique, a specific key must be provided at location KEYAD.

Action:
Point KEYAD at key of the wanted record and retry.

826 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V226

s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND KEYAD VALUE IS LESS THAN
SPACES FOR CALLID xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=UNIQUE and KEYAD pointed to a location containing no
key. When retrieval type is unique, a specific key must be provided at location KEYAD.

Action:
Point KEYAD at key of the wanted record and retry.

CA-7.V227

s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO DSTYPE VALUE FOR CALLID
xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=NODE and DSTYPE pointed to a location containing blanks
or ALL. When the retrieval type is node, a specific DSTYPE must be provided.

Action:
Point DSTYPE at a location containing JOB or DS or IDS.

CA-7.V228

s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO RECTYP VALUE FOR CALLID
xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=NODE and RECTYP pointed to a location containing blanks
or ALL. When the retrieval type is node, a specific RECTYP must be provided.

Action:
Point RECTYP at a location containing DIR or MEM or IDS.

Chapter 3: CA-7.A - CA-7.X Messages 827

CA-7.V200 Through CA-7.V299 Messages

CA-7.V229

s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO KEYAD VALUE FOR CALLID
xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=NODE and KEYAD pointed to an invalid location. When
retrieval type is NODE, a specific key must be provided at location KEYAD.

Action:
Point KEYAD at key of the wanted record and retry.

CA-7.V230

s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND KEYAD VALUE IS LESS THAN
SPACES FOR CALLID xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=NODE and KEYAD pointed to a location containing no key.
When retrieval type is NODE, a specific key must be provided at location KEYAD.

Action:
Point KEYAD at key of the wanted record and retry.

CA-7.V231

s mmmm (dddd) GET CALLED WITH RETTYP=FIRSTX AND NO KEYAD VALUE FOR CALLID
xxxxxxxx

Reason:
On an SVEXTGET call, RETTYP=FIRSTx and KEYAD pointed to an invalid location. When
retrieval type is FIRSTx, KEYAD must point to a location to contain key returned.

Action:
Point KEYAD at valid address and retry.

828 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V232

s mmmm (dddd) GET CALLED WITH RETTYP=FIRSTX AND COULD NOT DETERMINE THE
(X) VALUE FOR CALLID xxxxxxxx

Reason:
FIRSTx was specified for RETTYP on an SVEXTGET call where x was not a legal value.

Action:
Correct x value in macro call and retry.

CA-7.V233

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO DSTYPE VALUE FOR CALLID
xxxxxxxx

Reason:
SVEXTGET RETTYP=DIR macro call must include a specific DSTYPE value (other than
blanks or ALL) to avoid ambiguities.

Action:
Point DSTYPE to a location containing DS or JOB or IDS. Retry.

CA-7.V234

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO RECTYP VALUE FOR CALLID
xxxxxxxx

Reason:
SVEXTGET RETTYP=DIR macro call must include RECTYP=MEM.

Action:
Include RECTYP=MEM and retry.

CA-7.V235

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO KEYAD VALUE FOR CALLID
xxxxxxxx

Reason:
SVEXTGET RETTYP=DIR was called but KEYAD pointed to an invalid location.

Action:
Point KEYAD to location of valid key and retry.

Chapter 3: CA-7.A - CA-7.X Messages 829

CA-7.V200 Through CA-7.V299 Messages

CA-7.V236

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND KEYAD VALUE IS LESS THAN
SPACES FOR CALLID xxxxxx

Reason:
SVEXTGET macro, RETTYP=DIR was issued but KEYAD location pointed to did not contain
a valid key.

Action:
Point KEYAD to location of valid key and retry.

CA-7.V237

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND DETERMINED DATATYPE CODE IS
INVALID FOR CALLID xxxxxxxx

Reason:
Either DSTYPE, RECTYP and KEYAD form an illegal combination (for example,
DSTYPE=JOB, RECTYP=IDS) or the SASSVY00 table is invalid.

Action:
Verify that the specified DSTYPE, RECTYP, and KEYAD parameters specify a valid
combination. If not, correct and retry. If unresolved, save console log and listings and
contact your installation specialist for assistance.

CA-7.V238

s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND PRECEDING RETTYP=FIRST/NODE

NOT FOUND FOR CALLID xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=DIR requires a previous SVEXTGET call specifying
RETTYP=FIRSTX or NODE.

Action:
Try request again, if problem persists, verify that previous SVEXTGET specified the same
DSTYPE as this call and that RECTYP=DIR was specified with RETTYP=FIRSTx or NODE.
Save console listings and logs, then contact your installation specialist for assistance.

830 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V239

s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO DSTYPE VALUE FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT was specified and the location pointed to by
DSTYPE was invalid.

Action:
Verify that DSTYPE points to a valid address to contain the DSTYPE returned and retry.

CA-7.V240

s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO RECTYP VALUE FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT was specified and the location pointed to by
RECTYP was invalid.

Action:
Verify that RECTYP points to a valid address to contain the RECTYP returned and retry.

CA-7.V241

s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO KEYAD VALUE FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT was specified and the location pointed to by
KEYAD was invalid.

Action:
Verify that KEYAD points to a valid address to contain the key returned and retry.

Chapter 3: CA-7.A - CA-7.X Messages 831

CA-7.V200 Through CA-7.V299 Messages

CA-7.V242

s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND KEYAD VALUE IS LESS THAN
SPACES FOR CALLID xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT was specified and KEYAD did not contain a
valid key. KEYAD must point to the key which was returned on the previous SVEXTGET
RETTYP=FIRSTX/NEXT call.

Action:
Verify that KEYAD points to the previous key returned and retry.

CA-7.V243

s mmmm (dddd) RETTYP=NEXT REQUESTED WHEN INITIAL GET WAS NOT FOUND,
CALLID xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT must be preceded by a RETTYP=FIRSTX call.

Action:
Verify that a previous SVEXTGET RETTYP=FIRSTX is executed and retry.

CA-7.V244

s mmmm (dddd) RETTYP=NEXT REQUESTED WHEN INITIAL RETTYP NOT SET UP, CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NEXT must be preceded by a RETTYP=FIRSTX call.

Action:
Verify that a previous SVEXTGET RETTYP=FIRSTX is executed and retry.

832 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V245

s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO DSTYPE VALUE FOR CALLID
xxxxxxxx

Reason:
A SVEXTGET call specifying RETTYP=NREC must specify DSTYPE pointing to a valid
location containing the DSTYPE from a previous call.

Action:
Verify that DSTYPE points to a valid location and contains the DSTYPE returned from the
previous call.

CA-7.V246

s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO RECTYP VALUE FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NREC must specify RECTYP pointing to a valid
location containing the RECTYP from a previous call.

Action:
Verify that RECTYP points to a valid location and contains the RECTYP returned from the
previous call. Retry.

CA-7.V247

s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO KEYAD VALUE FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NREC must specify KEYAD pointing to a valid
location containing the key from a previous call.

Action:
Verify that KEYAD points to a valid location and contains the key returned from the
previous call. Retry.

Chapter 3: CA-7.A - CA-7.X Messages 833

CA-7.V200 Through CA-7.V299 Messages

CA-7.V248

s mmmm (dddd) RETTYP=NREC AND KEYAD VALUE IS LESS THAN SPACES FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NREC must specify KEYAD pointing to a valid
location containing the key from a previous call.

Action:
Verify that KEYAD points to a valid location and contains the key returned from the
previous call and retry.

CA-7.V249

s mmmm (dddd) RETTYP=NREC AND CORRESPONDING RETTYP NOT SETUP FOR CALLID
xxxxxxxx

Reason:
An SVEXTGET call specifying RETTYP=NREC must be preceded by an SVEXTGET call
specifying RETTYP=UNIQUE/FIRSTX/ NEXT/NODE.

Action:
Verify that previous SVEXTGET call will be performed and retry. If unresolved, save
console logs and listings and contact your installation specialist for assistance.

CA-7.V250

s mmmm (dddd) LOGIC ERROR IN GET, OBTAIN VRPL WHEN VRPL ALREADY EXISTED
FOR CALLID xxxxxxxx

Reason:
Although SVEXTGET call passed all checks for order of VSAM calls, a VRPL already
existed when the system expected to create one.

Action:
Check that all constraints regarding ordering of SVEXTGET and SVEXTPUT calls have
been complied with. If not, correct problem and retry. If unresolved, save console log
and listings and contact your installation's CA Workload Automation SE specialist for
assistance.

834 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V251

s mmmm (dddd) LOGIC ERROR IN GET, GET RECORD WITHOUT A VRPL FOR CALLID
xxxxxxxx

Reason:
Although SVEXTGET call passed all checks for order of VSAM calls, a VRPL was expected
to exist but did not.

Action:
Check that all constraints regarding ordering of SVEXTGET and SVEXTPUT calls have
been complied with. If not, correct problem and retry. If unresolved, save console log
and listings and contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.V252

s mmmm (dddd) LOGIC ERROR IN GET, RELEASE VRPL WHEN VRPL DOES NOT EXIST
FOR CALLID xxxxxxxx

Reason:
An SVEXTGET call attempted to release a VRPL which did not exist.

Action:
Check that all constraints regarding ordering of SVEXTGET and SVEXTPUT calls have
been complied with. If not, correct problem and retry. If unresolved, save console log
and listings and contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.V253

s mmmm (dddd) INVALID DATATYPE xxxx FOR SVEXTPUT TYPE=DELT/UNCT

Reason:
Either SVEXTPUT was called with an illegal DSTYPE, RECTYPE and KEYAD combination or
module SASSVY00 is invalid.

Action:
Check that DSTYPE, RECTYP and KEYAD are compatible. If not, correct problem and
retry. If unresolved, save console log and listings and contact your installation's CA
Workload Automation SE specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 835

CA-7.V200 Through CA-7.V299 Messages

CA-7.V254

s mmmm (dddd) VPCB FOR SVEXTGET NOT FOUND FOR CALLID = xxxxxxxx

Reason:
An SVEXTGET call attempted to locate a VPCB which did not exist.

Action:
Check that all constraints regarding ordering of SVEXTGET and SVEXTPUT calls have
been complied with. If not, correct problem and retry. If unresolved, save console log
and listings and contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.V259

s mmmm (dddd) RECRD/BLKAD PARAMETER NOT ALLOWED FOR TYPE = DELT/UNCT

Reason:
SVEXTPUT TYPE=DELT/UNCT specified a RECRD or BLKAD parameter.

Action:
Remove RECRD or BLKAD parameter from SVEXTPUT call and retry.

CA-7.V260

s mmmm (dddd) CONTROL INTERVAL CONFLICT FOR CALLID = xxxxxxxx

Reason:
Same CALLID has requested update intent on two different DSTYPEs. This is legal, but by
chance, access to both requests require the same VSAM control interval. This can only
occur if data types with different DSTYPES are specified in the DBPARMS statements to
be on the same VSAM data set and will probably only occur if the physical data set is
very small. This can only occur if the governor module SASSV004 is not being used.

Action:
Reconfigure database so that data types with different DSTYPEs do not share the same
VSAM data set.

836 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V261

s mmmm (dddd) BACKUP CONNECTION MADE TO DSN = x...x

Reason:
Data set x...x has been opened for output and will be used as the destination for
database backup. Access type = BKUP is in effect. Normal message.

Action:
None.

CA-7.V262

s mmmm (dddd) RELOAD CONNECTION MADE TO DSN = x...x

Reason:
Data set x...x has been opened for input and will be used as source for RELOAD
operation. Access type RELOAD is in effect. Normal message.

Action:
None.

CA-7.V263

s mmmm (dddd) NORM CONNECTION MADE TO DSN = x...x

Reason:
The VSAM cluster x...x has been opened for input and output. Access type = NORM is in
effect. This is an informational message.

Action:
None.

CA-7.V264

s mmmm (dddd) NORMIN CONNECTION MADE TO DSN = x...x

Reason:
The VSAM cluster x...x has been opened for input only. Access type = NORMIN is in
effect. This is an informational message.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 837

CA-7.V200 Through CA-7.V299 Messages

CA-7.V265

s mmmm (dddd) CONNECTION COMPLETED SUCCESSFULLY

Reason:
No error. This is an informational message indicating completion of SVCONN processing.

Action:
None.

CA-7.V266

s mmmm (dddd) DISCONNECTED DSN = x...x

Reason:
No error. This is an informational message indicating close of data set DSN = x...x.

Action:
None.

CA-7.V267

s mmmm (dddd) DISCONNECTION COMPLETED SUCCESSFULLY

Reason:
No error. This is an informational message indicating completion of SVDISCON
processing.

Action:
None.

CA-7.V268

s mmmm (dddd) RETTYP=NEXT REQUESTED AFTER EOD REACHED FOR CALLID xxxxxxxx

Reason:
SVEXTGET attempted for next record key after reaching end of data.

Action:
Save console listings and logs, plus any panel messages and commands issued. Contact
your installation specialist for assistance.

838 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V269

s mmmm (dddd) RETTYP=NREC REQUESTED AFTER EOD REACHED FOR CALLID xxxxxxxx

Reason:
SVEXTGET attempted for next logical record after reaching end of data.

Action:
Save console listings and logs, plus any panel messages and commands issued. Contact
your installation specialist for assistance.

CA-7.V270

s mmmm (dddd) RECORD FAILED KEY EDIT

Reason:
A record containing an invalid key was encountered. Keys are invalid if they have
noncatalogable characters or nodes in them. This message is followed by messages
V271, V272, and V273 that list the invalid key. The first four characters of the key
identify the data type as defined in the Systems Programming Guide.

Action:
Execute the SASSBK00 program with an OPTION of RELOAD to remove these errors from
the database.

CA-7.V271

s mmmm (dddd) KEY=C'...'

Reason:
This identifies a key in character format. See also messages V272 and V273.

Action:
None.

CA-7.V272

s mmmm (dddd) KEY=Z'...'

Reason:
This identifies the zone portion of a key. See also messages V271 and V273.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 839

CA-7.V200 Through CA-7.V299 Messages

CA-7.V273

s mmmm (dddd) KEY=N'...'

Reason:
This identifies the numeric portion of a key. See also messages V271 and V272.

Action:
None.

CA-7.V274

s mmmm (dddd) RECORD ABOVE INVALID, DROPPED FROM BACKUP

Reason:
The record identified in the immediately preceding messages is invalid as described in
those messages. It was not written to the backup.

Action:
None.

CA-7.V275

s mmmm (dddd) BACKUP FORMAT INVALID (NO 'CNTL') - RECORD=x...x

Reason:
The file referenced as reload input did not match the format expected. It did not begin
with CNTL records created by a backup run. x...x is the content of the record read from
the input file in character format.

Action:
Use a file created by the backup option of the SASSBK00 program.

CA-7.V276

s mmmm (dddd) DUPLICATE KEY DETECTED, RECORD DROPPED BY RELOAD

Reason:
A duplicate key from a backup file was encountered during reload processing. It has
been dropped and not reloaded.

Action:
None.

840 Message Reference Guide

 CA-7.V200 Through CA-7.V299 Messages

CA-7.V280

s mmmm (dddd) RECORD FAILED EDIT

Reason:
A record failed an edit because it has one or more noncatalogable characters. This
message is followed by messages V281, V282, and V283 that list the invalid record. The
first four characters of the key identify the data type as defined in the Systems
Programming Guide.

Action:
Program SASSBK00 can be executed with an option of RELOAD to remove these errors
from the database.

CA-7.V281

s mmmm (dddd) REC=C'...'

Reason:
This identifies a record in character format. See also messages V282 and V283.

Action:
None.

CA-7.V282

s mmmm (dddd) REC=Z'...'

Reason:
This identifies the zone portion of a record. See also messages V281 and V283.

Action:
None.

CA-7.V283

s mmmm (dddd) REC=N'...'

Reason:
This identifies the numeric portion of a record. See also messages V281 and V282.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 841

CA-7.V300 Through CA-7.V329 Messages

CA-7.V300 Through CA-7.V329 Messages

This topic contains the CA-7.V300 through CA-7.V329 messages.

CA-7.V301

s mmmm (dddd) NO HITS on ANY SPECIFIED AGENDA OPERATION

Reason:
An error occurred during analysis of the list of operations to be performed on the
parameters passed to the next program.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V302

s mmmm (dddd) SPECIFIED PARAMETER LIST DID NOT BEGIN WITH 'PLST'

Reason:
The header of the parameter list did not contain the ID 'PLST'.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V303

s mmmm (dddd) SPECIFIED AGENDA DID NOT BEGIN WITH 'AGEN'

Reason:
The header of the AGENDA list did not contain the ID 'AGEN'.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

842 Message Reference Guide

 CA-7.V300 Through CA-7.V329 Messages

CA-7.V304

s mmmm (dddd) S-CON IN PARAMETER LIST SPECIFIED INVALID BASE REGISTER

Reason:
The S-CON to be used to find other data to be passed to this program used an invalid
base register. This may be an internal logic error.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V305

s mmmm (dddd) END OF AGENDA NOT FOUND

Reason:
The AGENDA list used to define functions to be performed on the parameters passed in
the parameter list did not have the end of the list identified. This may be an internal
logic error.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V306

s mmmm (dddd) END OF PARAMETER LIST NOT FOUND

Reason:
The parameter list passed to this program did not have the end of the list identified. This
may be an internal logic error.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 843

CA-7.V300 Through CA-7.V329 Messages

CA-7.V307

s mmmm (dddd) VALDAT OPERATION DETECTED INVALID PARAMETER FOR MODULE

SASSV0xx

Reason:
Program SASSVZ00 detected an invalid parameter to be passed to the program (module)
shown. This may be an internal logic error.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V308

s mmmm (dddd) PARAMETER FOR xxxxxx OPERATION NOT FOUND

Reason:
Program SASSVZ00 attempted the specified operation on the parameter to be passed to
the next program and the parameter was not in the parameter list. This may be an
internal logic error.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V309

s mmmm (dddd) VPCB TO BE ASSIGNED ALREADY EXISTED

Reason:
A PCB was requested for this function but the PCB was already on the chain.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V310

s mmmm (dddd) RELEASE PCB REQUESTED, BUT NOT FOUND

Reason:
A PCB for this function was requested to be released but it was not on the chain.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

844 Message Reference Guide

 CA-7.V300 Through CA-7.V329 Messages

CA-7.V311

s mmmm (dddd) VPCB CHAIN INVALID

Reason:
A search down the PCB chain found an invalid address.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V312

s mmmm (dddd) FIND PCB REQUESTED, BUT NOT FOUND

Reason:
A request for a specific PCB (for example, to continue an operation) failed to find that
PCB.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V313

s mmmm (dddd) CHAIN REQUESTED, ALREADY CHAINED

Reason:
A request to chain together two control blocks found that the chain was already in
place.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V314

s mmmm (dddd) UNCHAIN REQUESTED, NOT CHAINED

Reason:
A request to unchain two control blocks found that the chain did not exist.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 845

CA-7.V300 Through CA-7.V329 Messages

CA-7.V315

s mmmm (dddd) SPECIFIED CHAIN AND SPECIFIED CONTROL BLOCK NOT COMPATIBLE

Reason:
A request to unchain two control blocks found that the control blocks were not the
same type. Program SASSVZ50 could not complete the chaining for the Functional
module or the Subroutine.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V317

s mmmm (dddd) ERROR CONVERTING S-CON

Reason:
During the resolution of the base register, the offset of the S-type address constant or
both, program SASSVZ00 could not compute a valid address.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V318

s mmmm (dddd) INVALID SYMBOLIC VALUE FOR EXTERNAL PARAMETER.

Reason:
A request from the calling program used a symbolic parameter which was unknown to
the VSAM system.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V319

s mmmm (dddd) INVALID NUMERIC VALUE FOR EXTERNAL PARAMETER.

Reason:
A request from the calling program used a numeric value which did not correspond to
any known symbolic parameter in the VSAM system.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

846 Message Reference Guide

 CA-7.V300 Through CA-7.V329 Messages

CA-7.V320

s mmmm (dddd) DSTYPE, RECTYP, KEYAD COMBINATION NOT A LEGAL DATATYPE.

Reason:
The VSAM record service request for a specified type of record could not be satisfied.
The record is not defined to the VSAM database in the form requested.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V321

s mmmm (dddd) PTR-TO-VAL PARAMETER FORMAT REQUIRED FOR PUTPARM

OPERATION

Reason:
The PUTPARM operation of the Parameter Reformatter subroutine requires the
Pointer-to-Value parameter format. This form of parameter was not found.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V322

s mmmm (dddd) INVALID PARAMETER VALUE IN AGENDA

Reason:
The result of the conversion of the parameters into codes/values was invalid. For
example, a DSTYPE value was supposed to be IDS but a different code was found.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 847

CA-7.V300 Through CA-7.V329 Messages

CA-7.V323

s mmmm (dddd) DSTYPE AND RECTYP MUST BE NON-ZERO

Reason:
An external macro call specified a DSTYPE or RECTYPE value of 0 when a specific value
was required. Either ALL was specified or the parameter pointed to a location containing
blanks or ALL.

Action:
Correct the external macro call to point to a location containing a specific value for
DSTYPE and RECTYP. Contact your installation specialist for assistance if unable to
determine cause.

CA-7.V324

s mmmm (dddd) INVALID DSTYPE xxxx

Reason:
An illegal DSTYPE xxxx was specified.

Action:
Correct the external macro call to specify a legal DSTYPE.

CA-7.V325

s mmmm (dddd) VSAM KEYS NOT IN ASCENDING SEQUENCE

Reason:
A sequence error was detected either on the backup data set or during sequential
access of the VSAM database.

Action:
Correct the sequence problem and retry or contact your installation specialist for
assistance, if needed.

848 Message Reference Guide

 CA-7.V300 Through CA-7.V329 Messages

CA-7.V326

s mmmm (dddd) xxxKEY NOT VALID FOR THIS SEQUENCE

Reason:
A sequence error was detected either on the backup data set or during sequential
access of the VSAM database. If xxx is NEW and RELOAD was being attempted, the
backup data set was not created by the BACKUP option of SASSBK00.

Action:
Correct sequence problem and retry or contact your installation specialist for assistance,
if needed.

CA-7.V327

s mmmm (dddd) REQUIRED DATATYPE NOT PRESENT IN SEQUENCE

Reason:
Certain data types are required within the CA Workload Automation SE database and
must be present. One of these data types was not present in sequence.

Action:
Correct sequence problem and retry.

CA-7.V328

s mmmm (dddd) ERROR xx FOR MESSAGE yyy s mmmm (dddd)

Reason:
Module SASSVZ70 was unable to process a caller's message. The module attempting to
issue the message is identified in the second mmmm field. The displacement of the
SASSVZ70 linkage instructions within the caller is denoted by the second dddd field. The
message number causing the error is indicated by yyy, and the error code is xx. For error
code 16, the system's WTO buffers may be nearly full.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 849

CA-7.V501 Through CA-7.V599 Messages

CA-7.V329

s mmmm (dddd) TERM NOT VALID WITH POST OPERATION

Reason:
The SVRESRC macro was called for POST operation and TERM was specified. Internal
problem.

Action:
Remove TERM parameter and retry. Contact your installation specialist for assistance.

CA-7.V501 Through CA-7.V599 Messages

This topic contains the CA-7.V501 through CA-7.V599 messages.

CA-7.V501

s mmmm (dddd) HEADER OF SPECIFIED CELL POOL DAMAGED

Reason:
An Environment module has encountered an "internal" UCC7VSAM cell pool whose
header has been damaged by an overlay.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V502

s mmmm (dddd) CELL TO BE FREED WAS NOT ALLOCATED

Reason:
An Environment module has detected an attempt to free a cell in an "internal" cell pool
which is not found in the pool's chain of allocated cells.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

850 Message Reference Guide

 CA-7.V501 Through CA-7.V599 Messages

CA-7.V505

s mmmm (dddd) INVALID CELL POOL ID

Reason:
An Environment module cannot locate a cell pool containing the pool ID specified by a
caller of the module.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V506

s mmmm (dddd) CELL POOL WITH ALLOC CELL(S) CANNOT BE FREED

Reason:
Module SASSVx60 has detected an attempt to free an entire cell pool which contains
allocated cells.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V508

s mmmm (dddd) CELL POOL FULL AND SECONDARY POOL EXTENT CANNOT BE
OBTAINED

Reason:
Module SASSVx70 failed in its attempt to allocate a cell from a cell pool whose primary
extent is completely filled. The pool was created with a secondary cell count of zero;
therefore, no secondary pool extent will be acquired.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 851

CA-7.V501 Through CA-7.V599 Messages

CA-7.V509

s mmmm (dddd) CPOOL GET MACRO FAILED

Reason:
An attempt to get a cell from a cell pool through the CPOOL macro failed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V511

s mmmm (dddd) SGETM FAILED

Reason:
Internal storage allocation request failed.

Action:
Check storage pools by issuing /DISPLAY,Q=ALL. If available NSP space is low according
to the /DISPLAY,Q=ALL, increase region size and try again. If available NSP space seems
sufficient, the problem may be due to temporary load in system. Try the request again.

CA-7.V512

s mmmm (dddd) INVALID CSIZE PARAMETER

Reason:
Module SASSVx90 has detected an attempt to build a cell pool whose cells have a
negative or zero length, or a length exceeding 4088.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

852 Message Reference Guide

 CA-7.V501 Through CA-7.V599 Messages

CA-7.V513

s mmmm (dddd) INVALID PCELLCT PARAMETER

Reason:
Module SASSVx90 has detected an attempt to build a cell pool with a primary cell count
which is negative or zero.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V515

s mmmm (dddd) ECB ADDRESS NOT ON FULLWORD BOUNDARY

Reason:
The Event Control Block address must be on a fullword boundary. This address or the
ECB may be in error.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V516

s mmmm (dddd) BIT 0 OF ECB NOT 1 OR BIT 1 NOT 0

Reason:
The Event Control Block contains unexpected or invalid indicators.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 853

CA-7.V501 Through CA-7.V599 Messages

CA-7.V517

s mmmm (dddd) ECB ALREADY WAITING

Reason:
A WAIT was specified, but the Event Control Block is already waiting.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V518

s mmmm (dddd) PARAMETER ECB SPECIFIED AND COUNT NOT 1

Reason:
A process requiring an ECB was requested without proper setup.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V519

s mmmm (dddd) COUNT GREATER THAN NUMBER OF ENTRIES IN ECBLIST

Reason:
The parameters for event processing are invalid.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V520

s mmmm (dddd) ECB ALLOCATED ABOVE 16MB LINE

Reason:
An ECB has an address which cannot be accessed by this system.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

854 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V527

s mmmm (dddd) REQUESTED SIZE OF CELL POOL EXTENT EXCEEDS 16 MBYTES

Reason:
Module SASSVx90 has detected an attempt to build a cell pool with an excessively large
primary or secondary extent.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V601 Through CA-7.V636 Messages

This topic contains the CA-7.V601 through CA-7.V636 messages.

CA-7.V601

s mmmm (dddd) GETMAIN MACRO FAILED

Reason:
A request for processor storage could not be completed.

Action:
Increase region size. Save console listings and logs. Contact your installation specialist
for assistance.

CA-7.V602

s mmmm (dddd) BLDL MACRO FAILED FOR xxxxxxxx

Reason:
A request for BLDL service for a member of a partitioned data set had a fatal error.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 855

CA-7.V601 Through CA-7.V636 Messages

CA-7.V603

s mmmm (dddd) GENCB FOR xxx FAILED, DSN=x...x

Reason:
A request to generate VSAM control block xxx failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

CA-7.V604

s mmmm (dddd) SHOWCB FOR xxx FAILED, DSN=x...x

Reason:
A request to show data from VSAM control block xxx failed.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

856 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V605

s mmmm (dddd) VSAM OPEN FAILED, DSN=x...x

Reason:
VSAM open failed for data set x...x. If RC=8, REAS may be one of the following:
■ 128 - DD statement is missing
■ 131 - Incorrect volume
■ 136 - Insufficient storage
■ 148 - No record in catalog
■ 168 - DSN not on volume specified in DBPARMS
■ 180 - Probably wrong DSN on STEPCAT

Action:
Save console listings and logs. Contact your installation specialist for assistance.
■ 128 - May need IDCAMS delete as first step
■ 131 - May need IDCAMS delete as first step
■ 136 - Increase storage
■ 148 - May require STEPCAT
■ 168 - Check DBPARMS
■ 180 - Check STEPCAT

CA-7.V606

s mmmm (dddd) VSAM OPEN NON-TERMINAL ERROR, DSN=x...x

Reason:
VSAM open warning message.

Action:
Run an IDCAMS verify against data set x...x. Save console listings and logs. Contact your
installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 857

CA-7.V601 Through CA-7.V636 Messages

CA-7.V607

s mmmm (dddd) VSAM GET FAILED FOR CALLID tttttttt

Reason:
An error occurred while attempting to read a record where tttttttt is the program,
system function, or user terminal issuing the request.

Message CA-7.V636 follows this message. CA-7.V636 identifies the data set and the key
of the failing request. For a description of the return (RC) and reason (REAS) codes, see
the IBM manual DFSMS Macro Instructions for Data Sets.

Action:
Correct the error indicated by the return and reason codes; then retry the request if
necessary.

CA-7.V608

s mmmm (dddd) VSAM CLOSE FAILED, DSN=x...x

Reason:
VSAM CLOSE failed for data set x...x.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V609

s mmmm (dddd) MODCB FOR xxx FAILED, DSN=x...x

Reason:
VSAM modify control block function failed for control block xxx.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

858 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V610

s mmmm (dddd) IDCAMS ABENDED, [S/xxx | U/nnnn]

Reason:
DBPARMS IDCAMS control statements defined by user were submitted to IDCAMS
during connection and IDCAMS abended with a system or user abend code of xxx or
nnnn.

Action:
Check IDCAMS control statements submitted in DBPARMS data set by submitting them
to IDCAMS independent of CA Workload Automation SE. If they are handled by IDCAMS
correctly then save listings and logs and contact your installation's CA Workload
Automation SE specialist for assistance. If IDCAMS gives errors or abends when
executed directly, then correct the control statement or call IBM IDCAMS support.

CA-7.V611

s mmmm (dddd) IDCAMS COMPLETED, RC=nnnn

Reason:
IDCAMS was called and completed the requested action with the return code shown.

Action:
If the return code (RC=nnnn) is not zero, an error occurred. See preceding and following
messages for more information. Correct any errors in IDCAMS control statements in
DBPARMS statements and retry. Contact your installation specialist for assistance.

CA-7.V612

s mmmm (dddd) IDCAMS message text

Reason:
Normal message returned by interface with IDCAMS. IDCAMS message text will be
supplied by IDCAMS.

Action:
None unless IDCAMS message text indicates an error. See the IBM Access Method
Services Manual or IBM Messages and Codes Manual for your operating system for
details about the message returned.

Chapter 3: CA-7.A - CA-7.X Messages 859

CA-7.V601 Through CA-7.V636 Messages

CA-7.V613

s mmmm (dddd) VSAM PUT FAILED FOR CALLID tttttttt

Reason:
An error occurred while attempting to write a record where tttttttt is the program,
system function, or user terminal issuing the request.

Message V613 is followed by message CA-7.V636, which identifies the data set and the
key of the failing request. For a description of the return (RC) and reason (REAS) codes,
see the IBM manual DFSMS Macro Instructions for Data Sets.

Note: If RC=0 and REAS=0, the key is invalid.

If RC=8 and REAS=8, a duplicate key is detected.
If RC=8 and REAS=28, the VSAM data set is out of space.

Action:
Correct the error and retry the request if necessary.

CA-7.V614

s mmmm (dddd) OUT OF SPACE ON VSAM PUT FOR DATA TYPE xxxx

Reason:
An output operation detected insufficient space where xxxx is the type of data being
output.

This message is:

■ Nonrollable until CA Workload Automation SE terminates.
■ Issued once per data type.
■ Followed by messages CA-7.V613 that identifies the caller and CA-7.V636 which
identifies the data set and the key of the failing request.

Action:
We recommend the following steps:
1. Bring down CA Workload Automation SE.
2. Back up the database.
3. Increase the space allocated to file noted in message CA-7.V636.
4. Reload the database.

Note: If IDCAMS is used for backup and reload, be sure you adjust the DBPARMS
definition to match what was done with IDCAMS.

860 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V615

s mmmm (dddd) VSAM ENDREQ FAILED, DSN=x...x

Reason:
Error occurred processing a VSAM ENDREQ macro request. This error could cause
incomplete output/update processing or later hang conditions related to exclusive
control being retained.

Action:
Correct error conditions indicated by preceding IBM messages, if any. If hang condition
occurs, CA Workload Automation SE must be shut down and restarted with
TYPE=WARM or TYPE=ERST. If condition recurs, save console listings and logs. Then
contact your installation specialist for assistance.

CA-7.V616

s mmmm (dddd) DELETE MACRO FAILED FOR zzzzzzzz

Reason:
Module name zzzzzzzz could not be deleted after being used.

Action:
None; unless accompanied by IBM messages indicating severe error. If error persists,
save console listings and logs. Contact your installation specialist for assistance.

CA-7.V617

s mmmm (dddd) ATTACH MACRO FAILED FOR IDCAMS

Reason:
Unable to attach program IDCAMS as required to perform DELETE and DEFINE functions
during database reload. Most likely cause of failure is insufficient memory. This message
should be preceded by IBM messages identifying the exact cause of failure.

Action:
Try increasing region size, and see the IBM messages and documentation for more
details. If problem persists, save console listings and logs. Then contact your installation
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 861

CA-7.V601 Through CA-7.V636 Messages

CA-7.V618

s mmmm (dddd) SGETM MACRO FAILED

Reason:
A CA Workload Automation SE storage control service routine failed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V619

s mmmm (dddd) SBLDL MACRO FAILED FOR xxxxxxxx

Reason:
A request for BLDL service for a load library failed.

Action:
Be sure member exists on the CA Workload Automation SE load library. If so, save
console listings and logs. Contact your installation specialist for assistance.

CA-7.V620

s mmmm (dddd) OSDELETE MACRO FAILED FOR xxxxxxxx

Reason:
A request to delete a module from storage could not be completed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V621

s mmmm (dddd) FREEMAIN MACRO FAILED

Reason:
An attempt to free processor storage could not be completed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

862 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V623

s mmmm (dddd) LOAD MACRO FAILED FOR xxxxxxxx

Reason:
An attempt to load a program into memory failed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V624

s mmmm (dddd) ERASE RPL= NOT ACCEPTED FOR CALLID = xxxxxxxx

Reason:
VSAM macro ERASE RPL= did not work.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V625

s mmmm (dddd) ERASE RPL= RETURNED VSAM ERROR FOR CALLID = xxxxxxxx

Reason:
VSAM macro ERASE RPL= returned an error condition.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V626

s mmmm (dddd) POINT RPL= RETURNED VSAM ERROR FOR CALLID = xxxxxxxx

Reason:
VSAM macro POINT RPL= returned an error condition.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 863

CA-7.V601 Through CA-7.V636 Messages

CA-7.V627

s mmmm (dddd) PUT MACRO FAILED--LRECL TOO SMALL FOR VCTL ON BACKUP DD

Reason:
The LRECL of the Backup data set was exceeded by the length of the segment containing
the DBPARMS (VCTL) data. The write failed.

Action:
Change the DCB parameter in the backup data set to specify a larger LRECL.

CA-7.V628

s mmmm (dddd) OPEN FAILED FOR BACKUP DD

Reason:
An attempt to open the BACKUP data set failed.

Action:
Ensure that the BACKUP DD statement is correct in the execution JCL. Verify that the
proper parameters were specified on the EXEC statement. Correct and resubmit.

CA-7.V629

s mmmm (dddd) RDJFCB FAILED FOR BACKUP DD

Reason:
An attempt to read the JFCB failed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V630

s mmmm (dddd) BACKUP DD CLOSE FAILED

Reason:
A request to close the BACKUP data set failed.

Action:
Save console listings and logs. Contact your installation's CA Workload Automation SE
specialist for assistance.

864 Message Reference Guide

 CA-7.V601 Through CA-7.V636 Messages

CA-7.V631

s mmmm (dddd) GET MACRO FAILED

Reason:
An end-of-data condition was detected (possibly unexpected) on the BACKUP data set.

Action:
Verify that the data set being used as input to the database load is the proper BACKUP
data set. Save console listings and logs. Contact your installation's CA Workload
Automation SE specialist for assistance.

CA-7.V632

s mmmm (dddd) DYNUNALLOC FAILED - RC=xxxx,ERRCD=xxxx, INFOCD=xxxx,DSN=x...x

Reason:
Attempt to unallocate data set x...x failed. The RC, ERRCD and INFOCD codes are those
returned by the IBM dynamic allocation macro call and can be checked in the IBM
documentation for that macro.

Action:
Research IBM documentation for codes produced in this message. Save console listings
and logs. Contact your installation's CA Workload Automation SE specialist for assistance
if unable to resolve problem.

CA-7.V633

s mmmm (dddd) NON-TERMINAL DYNUNALLOC ERROR - INFOCD=xxxx,DSN=x...x

Reason:
Attempt to unallocate data set x...x failed. The INFOCD code is that returned by the IBM
dynamic allocation macro call and can be checked in the IBM documentation for that
macro.

Action:
Research IBM documentation for codes produced in this message. Save console listings
and logs. Contact your installation's CA Workload Automation SE specialist for assistance
if unable to resolve problem.

Chapter 3: CA-7.A - CA-7.X Messages 865

CA-7.V701 Through CA-7.V722 Messages

CA-7.V634

s mmmm (dddd) RDJFCB FAILED FOR DDN=xxxxxxxx

Reason:
Could not read JFCB for DD statement xxxxxxxx. The probable cause of the error is a
missing DD statement.

Action:
Check that the DD statement is correct. Add the DD statement and try again. If problem
persists, save console listings and logs. Contact your installation's CA Workload
Automation SE specialist for assistance.

CA-7.V635

s mmmm (dddd) I/O ERROR ABEND on BACKUP DD - Text

Reason:
An abnormal condition occurred while processing the backup data set.

Action:
Change the I/O device or volume and resubmit. Save console listings and logs. Contact
your installation specialist for assistance.

CA-7.V636

s mmmm (dddd) DSN=x...x, KEY=y...y

Reason:
This message follows error messages CA-7.V607, CA-7.V613, or CA-7.614. Message
CA-7.V636 identifies the data set and the key for the failing request.

Note: The key is always displayed as characters even though it may be in binary format
on the database. If message V613 preceded this message and indicated an invalid key
condition, the key is displayed in hexadecimal format.

Action:
Follow the action recommended for the message that precedes V636.

CA-7.V701 Through CA-7.V722 Messages

This topic contains the CA-7.V701 through CA-7.V722 messages.

866 Message Reference Guide

 CA-7.V701 Through CA-7.V722 Messages

CA-7.V701

s mmmm (dddd) ERROR RETURNED FROM DATABASE GOVERNOR SASSV004

Reason:
Database governor, SASSV004, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V702

s mmmm (dddd) ERROR RETURNED FROM CONTROL CARD GET ROUTINE SASSV001

Reason:
Control Card Get module, SASSV001, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V703

s mmmm (dddd) ERROR RETURNED FROM CONTROL CARD PARSE ROUTINE SASSV002

Reason:
Control Card Parse module, SASSV002, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 867

CA-7.V701 Through CA-7.V722 Messages

CA-7.V704

s mmmm (dddd) ERROR RETURNED FROM CONTROL BLOCK BUILD ROUTINE SASSV003

Reason:
Control Block Build module, SASSV003, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V705

s mmmm (dddd) ERROR RETURNED FROM LOAD CONNECTION MODULE SASSV021

Reason:
Load Connection module, SASSV021, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V706

s mmmm (dddd) ERROR RETURNED FROM RELOAD CONNECTION MODULE SASSV022

Reason:
Reload Connection module, SASSV022, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

868 Message Reference Guide

 CA-7.V701 Through CA-7.V722 Messages

CA-7.V707

s mmmm (dddd) ERROR RETURNED FROM NORMAL CONNECTION MODULE SASSV024

Reason:
Normal Connection module, SASSV024, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V708

s mmmm (dddd) ERROR RETURNED FROM BACKUP CONNECTION MODULE SASSV023

Reason:
Backup Connection module, SASSV023, encountered an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V709

s mmmm (dddd) ERROR RETURNED FROM SASSV021 ATTEMPTING TO OPEN BACKUP

DD FOR OUTPUT

Reason:
Load Connection module, SASSV021, encountered an error attempting to open the
BACKUP DD data set for output.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 869

CA-7.V701 Through CA-7.V722 Messages

CA-7.V710

s mmmm (dddd) ERROR RETURNED FROM SASSV040 ATTEMPTING TO DISCONNECT

ACCESS TYPE

Reason:
Disconnect module, SASSV040, encountered an error attempting to disconnect an
access type.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V711

s mmmm (dddd) ERROR RETURNED FROM SASSV020 ATTEMPTING TO RECONNECT

ACCESS TYPE

Reason:
Connect module, SASSV020, encountered an error attempting to reconnect an access
type.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V712

s mmmm (dddd) DISCONNECT FAILED FOR ACCESS TYPE xxxxxx

Reason:
Disconnect module, SASSV040, encountered an error disconnecting access type xxxxxx.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

870 Message Reference Guide

 CA-7.V701 Through CA-7.V722 Messages

CA-7.V713

s mmmm (dddd) RECONNECT FAILED FOR ACCESS TYPE xxxxxx

Reason:
Connect module, SASSV020, encountered an error reconnecting access type xxxxxx.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V714

s mmmm (dddd) SVBACKUP FAILED DURING TERMINATION

Reason:
Backup processing failed during termination. Error causing this failing is described by
preceding error messages.

Action:
Take corrective action described for error messages preceding this one. Any backup file
created may be incomplete and should not be used for reload if another is available.

CA-7.V715

s mmmm (dddd) SVEXTPUT FAILED DURING TERMINATION

Reason:
Put processing was in progress when termination occurred. Additional error messages
should precede this on giving a further description of the problem.

Action:
Save console listings and logs. Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 871

CA-7.V701 Through CA-7.V722 Messages

CA-7.V716

s mmmm (dddd) ERROR RETURNED FROM SASSV021 ATTEMPTING TO OPEN BACKUP

DD FOR INPUT

Reason:
Backup Connect module, SASSV021, encountered an error attempting to open BACKUP
DD for input.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V717

s mmmm (dddd) ERROR RETURNED FROM SASSV081 DURING SPECIAL LOAD

Reason:
Special Load module, SASSV081, encountered an error during special load process.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V718

s mmmm (dddd) ERROR RETURNED FROM SASSV028 IDCAMS INTERFACE MODULE

Reason:
IDCAMS Interface module, SASSV028, encountered an error submitting IDCAMS
statements from DBPARMS to IDCAMS for execution during connection process.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

872 Message Reference Guide

 CA-7.V701 Through CA-7.V722 Messages

CA-7.V719

s mmmm (dddd) CALLID xxxxxxxx SVEXTGET FAILED

Reason:
SVEXTGET call internal to VSAM failed.

Action:
Look up explanation of the crux message preceding this message on the console log.
Save console logs and listings. Contact your installation specialist for assistance.

CA-7.V720

s mmmm (dddd) ERROR RETURNED FROM SASSV029 VCTL PUT MODULE

Reason:
Call of module SASSV029 returned an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V721

s mmmm (dddd) ERROR IN MODULE xxxxxxxx FOR KEYNAME xxxxxxxx

Reason:
Call of Status module, SASSV09x, failed while processing KEYNAME xxxxxxxx.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 873

CA-7.V801 Through CA-7.V815 Messages

CA-7.V722

s mmmm (dddd) CALLID xxxxxxxx SVEXTPUT TYPE=DELT FAILED

Reason:
SVEXTPUT call internal to VSAM failed.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V801 Through CA-7.V815 Messages

This topic contains the CA-7.V801 through CA-7.V815 messages.

CA-7.V801

s mmmm (dddd) ERROR IN PARAMETER LIST OR AGENDA DETECTED BY REFORMATTER

SASSVZ00

Reason:
An error occurred in the Reformatter subroutine module SASSVZ00.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V802

s mmmm (dddd) SVCHAIN FAILED ATTEMPTING TO CHAIN xxxx CONTROL BLOCK

Reason:
The control block chain for control block xxxx is incorrect.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

874 Message Reference Guide

 CA-7.V801 Through CA-7.V815 Messages

CA-7.V803

s mmmm (dddd) SVCHAIN FAILED ATTEMPTING TO UNCHAIN xxxx CONTROL BLOCK

Reason:
The control block chain for control block xxxx is incorrect.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V804

s mmmm (dddd) SVAGNPCB FAILED ON ASSIGN

Reason:
The Assign PCB module, SASSVZ10, was unable to assign a new VPCB control block as
requested.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V805

s mmmm (dddd) SVAGNPCB FAILED ON FIND

Reason:
The Assign PCB module, SASSVZ10, was unable to find an existing VPCB control block as
requested.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 875

CA-7.V801 Through CA-7.V815 Messages

CA-7.V806

s mmmm (dddd) SVAGNPCB FAILED ON RELEASE

Reason:
The Assign PCB module, SASSVZ10, was unable to release an existing VPCB control block
as requested, probably because the control block chain was invalid.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V807

s mmmm (dddd) SVAGNRPL FAILED ON ASSIGN

Reason:
The Assign RPL module, SASSVZ20, was unable to assign a new VRPL control block as
requested.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V808

s mmmm (dddd) SVAGNRPL FAILED ON RELEASE

Reason:
The Assign RPL module, SASSVZ20, was unable to release an existing VRPL control block
as requested, probably because the control block chain was invalid.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

876 Message Reference Guide

 CA-7.V801 Through CA-7.V815 Messages

CA-7.V809

s mmmm (dddd) SVRESRC FAILED ON WAIT

Reason:
The Wait and Post Resource module, SASSVZ30, was unable to wait on requested
resource.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V810

s mmmm (dddd) SVRESRC FAILED ON POST

Reason:
The Wait and Post Resource module, SASSVZ30, was unable to post the requested
resource.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V811

s mmmm (dddd) TRANSFER INTERFACE (SASSVZ60) FAILED

Reason:
An External module was called using an external macro call, but an error occurred
during transfer to the module.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 877

CA-7.V801 Through CA-7.V815 Messages

CA-7.V812

s mmmm (dddd) SVGETTYP FAILED

Reason:
The Get Type subroutine, SASSVZ40, was unable to return the requested data type.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V813

s mmmm (dddd) SVGETLEN FAILED

Reason:
The Get Length subroutine, SASSVZ80, was unable to return the requested record
length.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V814

s mmmm (dddd) SVCVPARM FAILED

Reason:
The Convert Parameter subroutine, SASSVZ90, was unable to convert the requested
parameters.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

878 Message Reference Guide

 CA-7.V901 Through CA-7.V918 Messages

CA-7.V815

s mmmm (dddd) SVSEQCHK FAILED

Reason:
The Sequence Check module, SASSVZA0, was unable to verify the correct key sequence.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V901 Through CA-7.V918 Messages

This topic contains the CA-7.V901 through CA-7.V918 messages.

CA-7.V901

s mmmm (dddd) SVGETCPL FAILED OBTAINING xxxx CELL POOL

Reason:
The Get Cell Pool module, SASSVx90, was unable to allocate the requested cell pool.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V902

s mmmm (dddd) SVGETCEL FAILED OBTAINING A xxxx CONTROL BLOCK

Reason:
The Get Cell module, SASSVx70, was unable to obtain the requested cell from an
existing cell pool.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 879

CA-7.V901 Through CA-7.V918 Messages

CA-7.V903

s mmmm (dddd) SVLOAD DID NOT FIND MODULE xxxxxxxx

Reason:
The Load module, SASSVxD0, was unable to find the requested module in any accessible
load library.

Action:
Check that the module named is in the library referenced by STEPLIB or JOBLIB DD
statements. Look up explanation of crux message preceding this message on console
log. Save console logs and listings. Contact your installation's CA Workload Automation
SE specialist for assistance.

CA-7.V904

s mmmm (dddd) SVLOAD FAILED FOR MODULE xxxxxxxx

Reason:
The Load module, SASSVxD0, was unable to load the requested module.

Action:
Replace module named in load library and try again. Look up explanation of crux
message preceding this message on console log. Save console logs and listings. Contact
your installation's CA Workload Automation SE specialist for assistance.

CA-7.V905

s mmmm (dddd) SVGETM FAILED FOR xxxx CONTROL BLOCK

Reason:
The GETMAIN module, SASSVx80, was unable to acquire the requested storage for
control block xxxx.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

880 Message Reference Guide

 CA-7.V901 Through CA-7.V918 Messages

CA-7.V906

s mmmm (dddd) SVGETM FAILED GETTING WORKING STORAGE

Reason:
The GETMAIN module, SASSVx80, was unable to acquire the requested storage.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V907

s mmmm (dddd) RC=xx REAS=yy SVGETM FAILED ACQUIRING DBPARMS DCB

Reason:
The GETMAIN module, SASSVx80, was unable to acquire the requested storage for a
VDCB for the DBPARMS data set.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V908

s mmmm (dddd) RC=xx REAS=yy SVFRECEL FAILURE FOR xxxx CONTROL BLOCK

Reason:
The Free Cell module, SASSVx40, was unable to return the requested control block to
the free pool.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 881

CA-7.V901 Through CA-7.V918 Messages

CA-7.V909

s mmmm (dddd) SVFRECPL FAILURE FOR xxxx CELL POOL

Reason:
The Free Cell Pool module, SASSVx40, was unable to delete the requested cell pool.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V910

s mmmm (dddd) SVPUTM FAILURE RELEASING xxxx CONTROL BLOCK

Reason:
The FREEMAIN module, SASSVx50, was unable to free the requested storage.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V911

s mmmm (dddd) SVPUTM FAILURE RELEASING WORKING STORAGE

Reason:
The FREEMAIN module, SASSVx50, was unable to free the requested storage.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

882 Message Reference Guide

 CA-7.V901 Through CA-7.V918 Messages

CA-7.V912

s mmmm (dddd) SVPUTM FAILURE RELEASING DBPARMS DCB

Reason:
The FREEMAIN module, SASSVx50, was unable to free the requested storage for the
DBPARMS VDCB.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V913

s mmmm (dddd) SVPOST MACRO FAILURE

Reason:
The Post module, SASSVxA0, was unable to post the requested ECB.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V914

s mmmm (dddd) SVWAIT MACRO FAILURE

Reason:
The Wait module, SASSVxC0, was unable to set up the requested ECB.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 883

CA-7.V901 Through CA-7.V918 Messages

CA-7.V915

s mmmm (dddd) SVDELETE FAILED FOR MODULE xxxxxxxxx

Reason:
The Delete module, SASSVxE0, was unable to delete the requested module.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V916

s mmmm (dddd) SVLINK FAILED FOR MODULE xxxxxxxxx

Reason:
The Link module, SASSVxF0, was unable to link to the requested module.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.V917

s mmmm (dddd) SVGETM FAILED

Reason:
The GETMAIN module, SASSVx80, was unable to allocate the requested storage.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

884 Message Reference Guide

 CA-7.W Messages

CA-7.V918

s mmmm (dddd) SVPUTM MACRO FAILED

Reason:
The SVPUTM macro returned an error condition.

Action:
Look up explanation of crux message preceding this message on console log. Save
console logs and listings. Contact your installation's CA Workload Automation SE
specialist for assistance.

CA-7.W Messages
This topic contains the CA-7.W messages.

CA-7.WTO

xxxxx..........xxxxx

Reason:
This message appears at the OS console when a CA Workload Automation SE terminal
operator issues the /WTO command. The xxxxx..........xxxxx is the message text entered
by the operator issuing the /WTO.

Action:
None.

CA-7.X Messages
This topic contains the CA-7.X messages.

CA-7.XABD-nn

text

Reason:
An error occurred accessing VRM definitions.

Action:
Contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 885

CA-7.X Messages

CA-7.XRAC-01

INVALID PARAMETER LIST - @RSRCPL

Reason:
The VRM VSAM processing module SASSXRAC received an internal request for service
using an invalid parameter list. This message is associated with a user 100 abend.

Action:
Contact your installation specialist for assistance.

CA-7.XRAC-02

VRM INTERNAL ERROR - INVALID REQUEST

Reason:
The VRM VSAM processing module SASSXRAC received an unidentified request type.
This message is associated with a user 101 abend.

Action:
Contact your installation specialist for assistance.

CA-7.XRAC-03

VSAM RECD ERROR R15 = xx FDBK = xxxxxxxx FUNC = xx

Reason:
An I/O error has occurred in the VRM VSAM processing module SASSXRAC. Register 15 is
the return code and the FDBK field indicates the feedback code as a result of the I/O. If
R15=08, a duplicate record has been found.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

886 Message Reference Guide

 CA-7.X Messages

CA-7.XRAC-04

SHOWCB ERROR

Reason:
An internal VSAM macro error has occurred in the VSAM processing module SASSXRAC.
This message is associated with a user 101 abend.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

CA-7.XRAC-05

MODCB ERROR

Reason:
An internal VSAM macro error has occurred in the VSAM processing module SASSXRAC.
This message is associated with a user 101 abend.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

CA-7.XRAC-06

RECORD KEY = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
An error has occurred in the VRM VSAM processing module SASSXRAC. An invalid record
or record key was found.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 887

CA-7.X Messages

CA-7.XRAC-07

VSAM MACRO PROCESSING ERROR

Reason:
An internal VSAM macro error has occurred in the VSAM processing module SASSXRAC.
This message is associated with a user 105 abend.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

CA-7.XSEC

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:
This message is issued as part of tracing/debugging the CA Workload Automation SE
interface with external security packages. The message is only activated when working
with CA Support. The message text is variable.

Action:
None.

CA-7.XTM0

- ffff note: mm-mm (aabbccdd) nn-nn

Reason:
An exception was detected for a CAICCI function request. ffff is the name of the CAICCI
function that was attempted such as 'SEND' or 'RECV'. mm-mm is the message in the
CAICCI feedback area. The FDBVRC codes from the CAICCI feedback area are reported at
aabbccdd. nn-nn is the CAICCI node name of the session partner.

Action:
Contact your installation specialist for assistance.

888 Message Reference Guide

 CA-7.X Messages

CA-7.XTM0

- Bad load of SASSXTM5

Reason:
Module SASSXTM5 could not be loaded.

Action:
Confirm that the module is accessible through steplib, linklib, or LPA. If the problem
persists, contact your installation specialist for assistance.

CA-7.XTM0

- RECEIVE error; Data dropped.

Reason:
CA Workload Automation SE could not allocate a buffer for an incoming CAICCI terminal
request.

Action:
Contact your installation specialist for assistance.

CA-7.XTM0

- Session ended (nnnnnnnn) xx-xx

Reason:
A CAICCI terminal session ended. nnnnnnnn is the CA Workload Automation SE SCT
name of the terminal handling the request. The CAICCI node name of the session
partner is reported at xx-xx.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 889

CA-7.X Messages

CA-7.XTM0

- Session started (nnnnnnnn) xx-xx

Reason:
A CAICCI terminal session started. nnnnnnnn is the CA Workload Automation SE SCT
name of the terminal handling the request. The CAICCI node name of the session
partner is reported at xx-xx.

Action:
None.

CA-7.XTM0

- Session TERM (nnnnnnnn) xx-xx

Reason:
A CAICCI terminal session has terminated with an error. nnnnnnnn is the CA Workload
Automation SE SCT name of the terminal handling the request. The CAICCI node name
of the session partner is reported at xx-xx.

Action:
Check for other messages that may indicate what caused the error if the problem
persists.

CA-7.XTM0

- Session TIMEOUT (nnnnnnnn) xx-xx

Reason:
A CAICCI terminal session has timed out. nnnnnnnn is the CA Workload Automation SE
SCT name of the terminal handling the request. The CAICCI node name of the session
partner is reported at xx-xx. This message is usually an informational message.

Action:
Check for other messages that may indicate what caused the timeout if the problem
persists.

890 Message Reference Guide

 CA-7.X Messages

CA-7.XTM1

- CA-7 shutting down; SEND aborted.

Reason:
A CA Workload Automation SE CAICCI SEND has not been done because CA Workload
Automation SE is being shut down.

Action:
You need to check the output of the batch CAICCI process to see whether it needs to be
rerun after CA Workload Automation SE is back up.

CA-7.XTM1

- No buffer addr supplied in XTM

Reason:
A buffer must be built before a CAICCI SEND can be done. In this case, there is no buffer
address. The request is rejected.

Action:
Check the output of the batch CAICCI process to determine whether it needs to be
rerun.

CA-7.XTM1

- No buffer leng supplied in XTM

Reason:
A buffer must be built before a CAICCI SEND can be done. In this case, the buffer length
is zero. The request is rejected.

Action:
Check the output of the batch CAICCI process to determine whether it needs to be
rerun.

Chapter 3: CA-7.A - CA-7.X Messages 891

CA-7.X Messages

CA-7.XTM1

- Data length exceeds buffer capacity

Reason:
A buffer must be built before a CAICCI SEND can be done. In this case, the buffer was
not large enough to contain the transaction data. The request is rejected.

Action:
Check the output of the batch CAICCI process to determine whether it needs to be
rerun.

CA-7.XTM1

- ffff NOTE: message (aabbccdd) nodename

Reason:
An exception was detected for a CAICCI function request. ffff is the name of the CAICCI
function that was attempted, such as SEND or RECV. message is the message in the
CAICCI feedback area. The FDBVRC codes from the CAICCI feedback area are reported at
aabbccdd. The CAICCI node name of the session partner is nodename.
Note: Notice that this message is identical to the CA-7.XTM0 ffff note message.

Action:
Contact your installation specialist for assistance.

CA-7.XTM3

- Unable to activate CTITRACE.

Reason:
The CAICCI and TCP/IP terminal trace data set could not be opened. CA Workload
Automation SE continues but does not write trace data to the CTITRACE data set.

Action:
Contact your installation specialist for assistance.

892 Message Reference Guide

 CA-7.X Messages

CA-7.X001

- NO xxxxxxxx VALUE SUPPLIED.

Reason:
The value supplied for a program parameter keyword is invalid. Default values are
supplied for these parameters in CA7CLIST.

Action:
Correct the parameter values and execute CA7CLIST again.

CA-7.X002

- (xx yyyy) xxxxxxxx FAILED, R15 = nnnnnnnn

Reason:
The named Dialog Manager (xxxxxxxx) macro failed. The value in R15 is the return code
from the macro. If nnnnnnnn is 0000000C, check that the ISPPLIB contains the necessary
CA Workload Automation SE modules. See the appropriate IBM ISPF documentation.

Action:
Save ISPF log and list output for this session and contact CA Support at ca.com/support
for assistance.

CA-7.X003

- INVALID ENTRY CODE, R1 = nnnnnnnn

Reason:
This is an internal error. The error may be transient.

Action:
Attempt to reexecute CA7CLIST. If the error persists, save all ISPF log and list output.
Also collect any dumps that may have been produced and contact your installation's CA
Workload Automation SE specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 893

CA-7.X Messages

CA-7.X004

- INVALID RETURN CODE, R15 = nnnnnnnn

Reason:
This is an internal error.

Action:
The error may be transient. Attempt to reexecute CA7CLIST. If the error persists, save all
ISPF log and list output. Also collect any dumps that may have been produced and
contact your installation's CA Workload Automation SE specialist for assistance.

CA-7.X005

- (xx yyyy) SESSION TERMINATED DUE TO ERROR

Reason:
The CA Workload Automation SE terminal session under ISPF has been terminated. The
reasons for termination may be explained by previous error messages.

Action:
See the previous error messages for information about the reason for termination. Take
the indicated action and attempt to execute CA7CLIST again. If the error persists,
contact your installation's CA Workload Automation SE specialist for assistance.

CA-7.X006

- xxxxxxxx GENCB FAILED, R15 = nnnnnnnn

Reason:
A GENCB macro failed for the VTAM control block named. R15 contains the return code
from the GENCB. See the IBM manual z/OS Communications Server: SNA Programming.
Specific information about the reason for the failure will be found in the
aforementioned publication. A common reason for a GENCB failure is an insufficient
region size for the ISPF session.

Action:
Contact your installation specialist for assistance if the error persists.

894 Message Reference Guide

 CA-7.X Messages

CA-7.X007

- SYNTAX ERROR PARSING ACB NAME FOR SESSION

Reason:
An internal error was encountered trying to parse the ACB name provided on the
SESSAPL keyword in CA7CLIST.

Action:
Make sure that the value supplied for the SESSAPL parameter matches the value on the
SLUACB keyword on the UCC7VTAM statement in the initialization file. Also make sure
that the values conform to the naming conventions outlined in the Systems
Programming Guide. If the error persists, contact your installation's CA Workload
Automation SE specialist for assistance.

CA-7.X008

- CONNECT ACB UNAVAILABLE OVER 10 SECONDS

Reason:
The ACB needed for CA Workload Automation SE/TSO-ISPF session establishment could
not be OPENed during the time period allowed. The ACB used for session establishment
is the ACB name that ends with 0000. For more information about defining the ACBs,
see the Systems Programming Guide.

Note: This message could be produced during a period of high activity when there are
many users attempting to establish CA Workload Automation SE terminal sessions
under TSO-ISPF.

Action:
If the message was produced during a period of high activity, simply wait a few minutes
and re-execute the CLIST. If an error condition seems possible then attempt to activate
the VTAM application where the ACBs are defined by issuing the command:

v net,id=APPL,act

where APPL in this example should be replaced by the name of the appropriate VTAM
application. If this fails, review the installation steps outlined in the Systems
Programming Guide pertaining to the definition of the VTAM ACBs for possible errors. If
the error persists, contact your installation's CA Workload Automation SE specialist for
assistance.

Chapter 3: CA-7.A - CA-7.X Messages 895

CA-7.X Messages

CA-7.X009

- xxxxxxxx ACB OPEN FAILED, ACBOFLGS = nnnnnnnn

Reason:
A VTAM OPEN macro failed for the ACB named by xxxxxxxx. The ACBOFLGS codes may
provide information as to the reason for the failure. See the IBM manual z/OS
Communications Server: SNA Programming.

Action:
If the ACB named is the 0000 ACB, then this message will probably be accompanied by a
CA-7.X008 message. In that event, see the recommended action for that message.
Otherwise, see the aforementioned IBM publication for information about the reasons
why VTAM failed the OPEN request. If the error persists, contact your installation
specialist for assistance.

CA-7.X010

- RTNCD = xxxxxxxx, FDBK2 = yyyyyyyy

Reason:
This is an informational message which may be preceded by a message indicating an RPL
based VTAM macro failure. For information about the meaning of these codes, see the
IBM manual z/OS Communications Server: SNA Programming.

Action:
None. See the action recommended for the message specific to the macro failure.

CA-7.X011

- SESSION USER LIMIT REACHED, TRY AGAIN LATER

Reason:
All of the VTAM ACBs defined for use with the CA Workload Automation SE/TSO-ISPF
interface are currently in use by other ISPF sessions.

Action:
Wait a few minutes and try the interface again. If the problem persists, consider
increasing the number of VTAM ACBs.

896 Message Reference Guide

 CA-7.X Messages

CA-7.X012

- xxxxxxxx TRANSLATION FAILED, R0 = nnnnnnnn

Reason:
An error occurred during the attempt to evaluate an address. xxxxxxxx is the internal
function name and R0 contains the return code from the function routine.

Action:
Note the sequence of events that resulted in the failure. Collect all ISPF log and list
output from the time frame when the failure occurred. Contact your installation's CA
Workload Automation SE specialist for assistance.

CA-7.X013

- SCREEN TRANSLATION ERROR

Reason:
An error occurred during the attempt to build ISPF output for a CA Workload
Automation SE panel. This message may be accompanied by others which will give a
reason for the error.

Action:
See the actions recommended for any accompanying messages.

CA-7.X014

- ERROR DETECTED IN EDITOR

Reason:
An error occurred during an ISPF edit session for CA Workload Automation SE. This
message may be accompanied by others which will give a reason for the error.

Action:
See the actions recommended for any accompanying messages.

Chapter 3: CA-7.A - CA-7.X Messages 897

CA-7.X Messages

CA-7.X015

- xxxxxxxx FAILED, R0 = nnnnnnnn

Reason:
The VTAM macro named at xxxxxxxx failed. See the IBM manual z/OS Communications
Server: SNA Programming for further information.

Action:
If the error persists, contact your installation's CA Workload Automation SE specialist for
assistance.

CA-7.X016

- INVALID WRITE CONTROL CHARACTER - xx

Reason:
An invalid 3270 write control character was received from CA Workload Automation SE.
xx is the hex value of the character.

Action:
The problem may be transient. Reexecute the interface. If the problem persists, contact
your installation's CA Workload Automation SE specialist for assistance.

CA-7.X017

- INVALID 3270 DATASTREAM ORDER - xx

Reason:
An invalid 3270 datastream order character was received from CA Workload
Automation SE. xx is the hex value of the character.

Action:
The problem may be transient. Reexecute the interface. If the problem persists, contact
your installation's CA Workload Automation SE specialist for assistance.

898 Message Reference Guide

 CA-7.X Messages

CA-7.X018

- INVALID EDIT HEADER, EDIT SESSION TERMINATED

Reason:
Internal information needed to maintain Editor protocols between CA Workload
Automation SE and TSO-ISPF was missing or invalid.

Action:
If the L2ISPFxx modules are accessed from a library other than the CA Workload
Automation SE production load library, then make sure that all L2ISPFxx modules are
running at the same maintenance level as the modules that are executing in the CA
Workload Automation SE address space. If the problem persists, contact your
installation specialist for assistance.

CA-7.X019

- UNABLE TO OPEN EDITOR WORK FILE

Reason:
The work file that was dynamically allocated for use in a CA Workload Automation
SE/TSO-ISPF edit session could not be opened.

Action:
This message may be accompanied by other messages, for example, CA-7.X026. If so,
see the action recommended for those messages. If this message is produced without
accompanying messages, then simply reexecute the CA Workload Automation SE CLIST.

CA-7.X020

- UNABLE TO COMPLETE VTAM CONNECTION WITH CA-7

Reason:
A VTAM REQSESS macro was issued to establish a session with CA Workload Automation
SE; however, no response from CA Workload Automation SE was received.

Action:
This message may be ignored if CA Workload Automation SE was terminating during the
attempt to connect to CA Workload Automation SE from ISPF. Reexecute the interface.
If the condition persists, contact CA Support at ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 899

CA-7.X Messages

CA-7.X021

- NSEXIT CLEANUP REQUEST - LINK IS DOWN

Reason:
The VTAM link with CA Workload Automation SE is no longer active. There are several
possible explanations for this condition. For example, a VTAM command may have been
issued to inactivate the application, or CA Workload Automation SE may be down, or a
/CLOSE may have been issued to close the CA Workload Automation SE VTAM ACB.

Action:
No CA Workload Automation SE terminal sessions will be available under ISPF until the
VTAM link is reestablished. Determine the cause of the outage and reexecute the
interface. If the error persists, contact CA Support at ca.com/support for assistance.

CA-7.X022

- NSPE RU RECEIVED - SESSION TERMINATED

Reason:
The NSEXIT exit was entered for a Network Services Procedure Error. See the IBM
manual z/OS Communications Server: SNA Programming for information on the specific
error conditions that might cause this condition.

Action:
Reexecute the interface. If the error persists and no VTAM problem is indicated, then
contact your installation specialist for assistance.

CA-7.X023

- LOSTERM EXIT ENTERED - SESSION TERMINATED

Reason:
This exit may be entered under certain session outage conditions. See the IBM manual
z/OS Communications Server: SNA Programming for information on the specific error
conditions that might cause this condition.

Action:
Re-execute the interface. If the error persists and no VTAM problem is indicated, then
contact your installation specialist for assistance.

900 Message Reference Guide

 CA-7.X Messages

CA-7.X024

- TPEND EXIT ENTERED - SESSION TERMINATED

Reason:
The TPEND exit was entered for this ACB. This exit may be entered in response to a
VTAM HALT command, or may be entered if VTAM terminates.

Action:
No CA Workload Automation SE session under ISPF will be available until the VTAM link
between CA Workload Automation SE and the ISPF sessions is reestablished. If the error
persists and no problem can be detected in VTAM, then contact your installation's CA
Workload Automation SE specialist for assistance.

CA-7.X025

- INVALID RESPONSE FROM CA-7 TO REQUEST FOR SLU ACBNAME

Reason:
An ISPF session requested the assignment of an ACB name for use in establishing a
VTAM link. CA Workload Automation SE returned a response not recognized by the
requestor.

Action:
Review the following for possible error conditions:
■ Determine that the VTAM link is being attempted for the correct copy of CA
Workload Automation SE. Make sure that the ACB defined for that copy of CA
Workload Automation SE is named on the CA7APL keyword in CA7CLIST.
■ The value for the SESSAPL keyword in CA7CLIST must match the VTAM ACB
definitions.

Correct any parameter values that may be in error, then reexecute the interface. If the
error persists, contact your installation specialist for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 901

CA-7.X Messages

CA-7.X026

- SVC 99 ERROR, R15 = xxxxxxxx, R0 = yyyyyyyy

Reason:
An attempt to allocate an editor work file failed. The R15 and R0 values should indicate
the nature of the problem. For information about the return codes from dynamic
allocation, see the IBM manual z/OS MVS Programming: Authorized Assembler Services
Guide.

Action:
Correct the problem that prevented the successful dynamic allocation and re-execute
the interface. If xxxxxxxx=00000004 and yyyyyyyy=02180000, change the CALL
statement in the CA7CLIST to add a UNIT=3390 to the calling parameters.

CA-7.X027

- CA-7 SCRGET DISP=FIRST FAILED, EDIT TERMINATED

Reason:
CA Workload Automation SE encountered an error attempting to read Active Area data
for this terminal. The edit session will be terminated.

Action:
If the problem persists, contact CA Support at ca.com/support for assistance.

CA-7.X028

- CA-7 SCRGET DISP=NEXTE FAILED, EDIT TERMINATED

Reason:
CA Workload Automation SE encountered an error attempting to read Active Area data
for this terminal. The edit session will be terminated.

Action:
If the problem persists, contact CA Support at ca.com/support for assistance.

902 Message Reference Guide

 CA-7.X Messages

CA-7.X029

- ***WARNING*** LINK ENDED DURING EDIT, DATA NOT SAVED

Reason:
The VTAM link with CA Workload Automation SE was terminated during the edit
session. The CA Workload Automation SE terminal session ended and any data being
edited was lost.

Action:
If the link ended because the TIMLIM value for the terminal expired, consider increasing
this value. If other messages indicate that the link ended due to error, consult the
recommendations accompanying those messages.

CA-7.X030

- OPEN/CLOSE SUBTASK ENDED. TCBCMP= xxsssuuu

Reason:
The subtask that was created to handle OPEN and CLOSE requests for the VTAM ACBs
used for the CA Workload Automation SE terminal session ended. A nonzero TCBCMP
indicates an abnormal termination. In such a case, sss is the system abend code and uuu
is the user abend code.

Action:
Collect any dumps that may have been produced and contact CA Support at
ca.com/support for assistance.

CA-7.X031

- xxxxxxxx POSTING ERROR.

Reason:
There was a VTAM error between CA Workload Automation SE and the caller. The
transaction was ignored. Processing continues.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 903

CA-7.X Messages

CA-7.X032

- ERROR RETURN FROM SASSPCEJ, EDIT TERMINATED

Reason:
An error was encountered during the attempt to load the ISPF editor.

Action:
If the error persists, contact CA Support at ca.com/support for assistance.

CA-7.X033

- INVALID FOOTER CODE, EDIT TERMINATED

Reason:
Invalid data was received from CA Workload Automation SE during the attempt to load
the ISPF editor.

Action:
If the error persists, contact CA Support at ca.com/support for assistance.

CA-7.X034

- CA-7 TERMINAL SESSION ENDED

Reason:
This message may be issued if one of the following conditions is true:
■ The VLOGOFF PF key was pressed.
■ CA Workload Automation SE detected no terminal activity for a time period in
excess of the value specified on the TERM statement keyword, TIMLIM. CA
Workload Automation SE will not recognize any terminal activity during an ISPF edit
session.
■ A /CLOSE,T= command was issued for this terminal.

Action:
None.

904 Message Reference Guide

 CA-7.X Messages

CA-7.X035

- xxxxxxxx NSEXIT SHOWCB FAILED

Reason:
A SHOWCB macro failed in the VTAM NSEXIT that was established for the ACB used in
the VTAM link with CA Workload Automation SE. xxxxxxxx is the name of the CA
Workload Automation SE program that issued the message.

Action:
This message is informational but may be helpful in debugging situations.

CA-7.X036

- xxxxxxxx NSEXIT UNKNOWN RU TYPE

Reason:
An unknown request unit was received by the VTAM NSEXIT used in the link with CA
Workload Automation SE. xxxxxxxx is the name of the CA Workload Automation SE
program that issued the message.

Action:
This message is informational but may be helpful in debugging situations.

CA-7.X037

- xxxxxxxx NSEXIT CLEANUP REQUEST

Reason:
A CLEANUP request was received by the VTAM NSEXIT used in the link with CA
Workload Automation SE. xxxxxxxx is the name of the CA Workload Automation SE
program that issued the message.

Action:
None.

Chapter 3: CA-7.A - CA-7.X Messages 905

CA-7.X Messages

CA-7.X038

- xxxxxxxx NSEXIT NSPE RU RECEIVED

Reason:
A Network Services Procedure Error RU was received. xxxxxxxx is the name of the CA
Workload Automation SE program that issued the message.

Action:
None.

CA-7.X039

- xxxxxxxx LOSTERM EXIT ENTERED

Reason:
The LOSTERM exit associated with the ACB for this terminal session was entered. The CA
Workload Automation SE terminal session will be terminated. xxxxxxxx is the name of
the CA Workload Automation SE program that issued the message.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

CA-7.X040

- xxxxxxxx TPEND EXIT ENTERED

Reason:
The TPEND exit associated with the ACB for this terminal session was entered. The CA
Workload Automation SE terminal session will be terminated. This exit may be entered
in the event of a VTAM outage or in response to certain VTAM operator commands. This
exit will be entered in response to a VARY NET,INACT for the application and will also be
entered in response to a VTAM HALT command. xxxxxxxx is the name of the CA
Workload Automation SE program that issued the message.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

906 Message Reference Guide

 CA-7.X Messages

CA-7.X041

- CHECK FAILED on xxxxxxxx

Reason:
A nonzero return was received for a CHECK macro issued in a VTAM RESP RPL exit.
xxxxxxxx indicates the macro that was issued using this RPL. This may result in session
termination.

Action:
Collect any console and dump information that may have been produced and contact
CA Support at ca.com/support for assistance. If no other CA-7.Xnnn messages are
produced at the same time, this message can be ignored.

CA-7.X042

- ERROR OCCURRED IN SCIP EXIT

Reason:
The VTAM SCIP exit for this terminal session's ACB encountered an error.

Action:
Collect any console and dump information that may have been produced and contact
CA Support at ca.com/support for assistance.

CA-7.X043

- VTAM LOGICAL ERROR EXIT ENTERED

Reason:
The VTAM LERAD exit for this terminal session's ACB was entered.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

Chapter 3: CA-7.A - CA-7.X Messages 907

CA-7.X Messages

CA-7.X044

- VTAM SYNAD EXIT ENTERED

Reason:
The VTAM SYNAD exit for this terminal session's ACB was entered.

Action:
If this message is produced and there are no accompanying messages indicating either
VTAM or CA Workload Automation SE error conditions, contact CA Support at
ca.com/support for assistance.

CA-7.X045

- ERROR IN VGET FROM APPLICATION POOL

Reason:
An attempt to read a variable from the CA7 application profile failed.

Action:
If the error persists, contact CA Support at ca.com/support for assistance.

CA-7.X046

- VTAM APPL FOR CA-7 NOT ACTIVE OR NOT ACCESSIBLE

Reason:
The VTAM APPL named on the CA7APL parameter in the CA7CLIST is not currently active
or is not accessible in this domain.

Action:
Make sure that the copy of CA Workload Automation SE associated with the VTAM APPL
named in the CA7APL parameter is active and that the VTAM ACB is open. Make sure
that this APPL is accessible in the domain where the ISPF session is running.

908 Message Reference Guide

 CA-7.X Messages

CA-7.X046

- LAST 4 CHARACTERS OF SESSAPL MUST BE NUMERIC

Reason:
An internal error was encountered on the SASSAPL keyword in CA7CLIST.

Action:
Make sure that the last four characters supplied for the SESSAPL parameter are
numeric.

CA-7.X047

- CA-7 UNRESPONSIVE FOR 10 SECONDS, SESSION TERMINATED

Reason:
The ISPF interface was invoked and timed out before the CA Workload Automation SE
logon panel could be returned.

Action:
Check for performance problems on the system where the ISPF session was invoked.

CA-7.X048

- UNABLE TO DISPLAY PANEL CA7@PRIM, RC=xx

Reason:
An error occurred during an ISPF edit session for CA Workload Automation SE. The xx is
the ISPF return code from IBM.

Action:
Execute CA7CLIST again. If the error persists, contact your installation specialist for
assistance.

Chapter 3: CA-7.A - CA-7.X Messages 909

Chapter 4: CA-7.000 - CA-7.1044
This chapter contains the CA-7.000 through CA-7.1nnn messages.

CA-7.000 Through CA-7.094

CA-7.000

rxx.x(nnnn) EMERGENCY RESTART COMPLETE AT hh:mm:ss ON yy.ddd

Reason:
An emergency restart (ERST) of CA Workload Automation SE has been successfully
completed. The notation rxx.x(nnnn) indicates the product release (rxx.x) and the
product level (nnnn) of CA Workload Automation SE. Issued by SASSCHDE.

Action:
None.

CA-7.001

- rxx.x(nnnn) COLD START COMPLETE AT hh:mm:ss ON yy.ddd.

Reason:
COLD start initialization completed successfully. The notation rxx.x(nnnn) indicates the
product release (rxx.x) and the product level (nnnn) of CA Workload Automation SE.
Issued by SASSINWC.

Action:
None.

CA-7.002

- rxx.x(nnnn) RESTART COMPLETE AT hh:mm:ss ON yy.ddd

Reason:
Restart initialization of CA Workload Automation SE completed successfully. The
notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of
CA Workload Automation SE. Issued by SASSINWC.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 911

CA-7.000 Through CA-7.094

CA-7.003

rxx.x(nnnn) PHASE [(I)|(II)] SHUTDOWN IN PROGRESS AT hh:mm:ss ON yy.ddd

x...x
PHASE [(I)|(II)] SHUTDOWN COMPLETE AT hh:mm:ss

Reason:
Phase I or Phase II of the CA Workload Automation SE shutdown process has been
completed. The notation rxx.x(nnnn) indicates the product release (rxx.x) and the
product level (nnnn) of CA Workload Automation SE. Issued by SASSCHDS or SASSSCM2.
Values for x...x are:
■ ALL SYSTEM FUNCTIONS COMPLETE
■ FOLLOWING SYSTEM FUNCTIONS ARE ACTIVE:
- each active CA Workload Automation SE system function listed -
■ TERM ******** IS NOT LOGGED OFF

Action:
None.

CA-7.004

READY TO ACCEPT MODIFY (taskname)

Reason:
This WTO is issued when the MVS console is defined as a terminal to CA Workload
Automation SE and opened. Replies must be entered in top line or batch command
format and sequence. /LOGON must be entered before commands are accepted and
/LOGOFF should be entered when finished. The job or started task executing CA
Workload Automation SE is identified by taskname. Issued by SASSRCSL.

Action:
Enter appropriate command to use console as terminal to CA Workload Automation SE,
using OS MODIFY commands.

912 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.005

rxx.x(nnnn) OPERATOR IS LOGGED OFF

Reason:
This is the usual message that appears when an operator logs off a CA Workload
Automation SE terminal. The notation rxx.x(nnnn) indicates the product release (rxx.x)
and the product level (nnnn) of CA Workload Automation SE. Issued by SASSCHDS.

Action:
None.

CA-7.006

rxx.x(nnnn) REQUESTED MODULE xxxxxxxx NOT FOUND

Reason:
The CA Workload Automation SE module shown could not be found. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE. Issued by SASSCHDS, SASSCHED, SASSEMGR or SASSHALT.

Action:
Make sure the module is in the CA Workload Automation SE load library. Also check to
ensure that there is an APPLCTN statement in the product's initialization file or in the
SASSPROG module for the module.

CA-7.007

- rxx.x(nnnn) REQUESTED FORMAT BLOCK xxxxxxxx NOT FOUND

Reason:
A format block was not found to process a message or panel. The notation rxx.x(nnnn)
indicates the product release (rxx.x) and the product level (nnnn) of CA Workload
Automation SE. Issued by SASSCHDM or SASSCHDS.

Action:
Perform the following actions:
■ Examine module SASSFMTH or SASSFMTA for the requested format block.
■ Verify that you have FMTBLK statements in the initialization file for SASSFMTH and
SASSFMTA.
■ Issue a /RELINK,FM= command specifying the format block in the message when a
module is already defined.

Chapter 4: CA-7.000 - CA-7.1044 913

CA-7.000 Through CA-7.094

CA-7.008

- rxx.x(nnnn) INPUT FORMAT ERROR FOR APPLICATION xxxxxxxx FORMAT BLOCK

SFMxxxxx TERMINAL xxxxxxx

Reason:
An error occurred formatting the input to the application indicated. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE. Issued by SASSCHDS.

Action:
If problem recurs, do a /RELINK for both application and format block named. If problem
continues, reassemble and link edit the format block, then do the /RELINK again. If all
else fails, contact your installation specialist for assistance.

Note: A condition code of 2 on a format block assembly is normal.

CA-7.009

- rxx.x(nnnn) OUTPUT FORMAT ERROR FOR APPLICATION xxxxxxxx FORMAT BLOCK

SFMxxxxx TERMINAL xxxxxxx

Reason:
An error occurred formatting the output from the application indicated. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE. Issued by SASSCHDM.

Action:
Same as for Message CA-7.008.

CA-7.010

- UNIDENTIFIED COMMAND, PLEASE RE-ENTER

Reason:
Either the command could not be identified as a valid CA Workload Automation SE
command or a shutdown is in progress. Issued by SASSCHDS.

Action:
If a shutdown is not in progress, check for command spelling errors, correct and retry. If
a shutdown is in progress, you cannot enter commands. If the /SHUTDOWN was
entered at your terminal, you cannot enter a /LOGOFF for your terminal.

914 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.011

- APPLICATION DWELL TIME EXCEEDED

Reason:
A value was supplied for the APDWELL parameter of the RESIDENT statement, and
command processing has exceeded that time value. For a batch-only run, this value
defaults to one (1) hour.

Action:
Remove or increase the APDWELL value. Alternately, specify values on the command
effected to limit its processing and reduce the time required.

CA-7.012

- REQUEST FOR rrrrrrrr ACCESS DENIED BY ssssssss.

---text---

Reason:
Access has been denied to the resource identified by rrrrrrrr. Resources can be the
following:
■ CA-7
■ COMMAND
■ FUNCTION
■ DATASET
■ JOB

The security identified by ssssssss denied access. Sources can be the following:
■ CA-7
■ SECURITY
■ USER EXIT

The text provides a further description of the access denial, that can be a message from
a user exit, feedback from external security, or a clarification message from CA
Workload Automation SE.

Action:
Review the message to determine which type of resource is involved and which security
is controlling access. To allow access, change the security identified.

Chapter 4: CA-7.000 - CA-7.1044 915

CA-7.000 Through CA-7.094

CA-7.014

- rxx.x(nnnn) UNRECOVERED ERROR ON TERM xxxxxxxx

Reason:
An unrecoverable I/O error occurred on the terminal indicated by xxxxxxxx. The
notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of
CA Workload Automation SE. Issued by SASSCHDM, SASSEMGR.

Action:
Examine the hardware for problems. If terminals have been added or changed, review
the parameters coded in the initialization file for correctness. If BTAM, verify that the
initialization file statements correspond to the DD statements in the CA Workload
Automation SE execution JCL. If the hardware has no problems and the error persists,
contact your installation specialist for assistance. If the terminal is a batch terminal, run
SASSBEND and try again.

CA-7.015

- rxx.x(nnnn) UNKNOWN ERROR TYPE ON TERM xxxxxxx

Reason:
The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level
(nnnn) of CA Workload Automation SE. CA Workload Automation SE detected an error
on the terminal with ID number xxxxxxx. Issued by SASSCHDS.

Action:
If the terminal is a printer, a /START command may have been issued to it. Use the
/OPEN,T= command instead; otherwise, contact your installation specialist for
assistance.

CA-7.016

TRAP PROGRAM FAILED

Reason:
The CA Workload Automation SE trap facility has failed because of a program problem.
Issued by SASSTRA0.

Action:
Contact your installation specialist for assistance.

916 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.017

TWO ABENDS AND NO FIXES

Reason:
While already processing an abend, the trap facility encountered a second abend.
CA-7.016 message (issued by SASSTRA0) and a U0001 abend dump will accompany this
message. Issued by SASSTRA0.

Action:
Contact your installation specialist for assistance.

CA-7.018

- OS STOP INVALID, USE /SHUTDOWN

Reason:
An OS STOP command was entered at a console. However, CA Workload Automation SE
security requires that an operator log in to the console terminal and issue a
/SHUTDOWN.

Action:
If a shutdown of CA Workload Automation SE is wanted, log on to the console with a
valid ID, and then issue the /SHUTDOWN command.

CA-7.019

- rxx.x(nnnn) CA-7 CANCELED

Reason:
This message is a normal informational response to /DUMP or /DMP1 command.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 917

CA-7.000 Through CA-7.094

CA-7.020

- rxx.x(nnnn) DISK QUEUE TABLE I/O ERROR

Reason:
An I/O error occurred while purging Disk Queue Table tracks, or more than 256 pages
were built for an online terminal. The notation rxx.x(nnnn) indicates the product release
(rxx.x) and the product level (nnnn) of CA Workload Automation SE. Issued by
SASSCHDM, SASSEMGR, SASSCHDS.

Action:
If a command could produce 256 or more pages of output, try requesting less
information or try input through a batch terminal.

CA-7.021

- rxx.x(nnnn) SPACE HAS BEEN EXCEEDED IN THE DISK QUEUE TABLE

Reason:
The Disk Queue Table is not large enough for the volume of messages and number of
terminals in use. A message loop can also produce this message. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE. Issued by SASSCHDM.

Action:
Try increasing size of Disk Queue Table. The DMPQ/MOVQ process must be done to
increase the size of any queue. Contact your installation specialist for assistance, if
needed.

CA-7.022

- LOGON FORMAT INCORRECT

Reason:
A user attempted to log on to CA Workload Automation SE. A second message describes
why the logon failed.

Action:
Consult the action of the second message.

918 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.022

- rxx.x(nnnn) LOGON FORMAT INCORRECT AT tttttttt

Reason:
An attempt was made to log on to a CA Workload Automation SE terminal (tttttttt). The
format of the logon was incorrect. The notation rxx.x(nnnn) indicates the product
release (rxx.x) and the product level (nnnn) of CA Workload Automation SE. Issued by
SASSCHDS. Also, if the SECURITY statement in the product's initialization file specifies
APPL checking, this setting sometimes causes the failure.

Action:
Correct the logon format and reissue the command.

CA-7.022

rxx.x(nnnn) LOGON REJECTED BY CA-7 AT tttttttt

Reason:
An attempt was made to log on to CA Workload Automation SE terminal tttttttt with a
USERID that is not defined to the CA Workload Automation SE internal security module.
The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level
(nnnn) of CA Workload Automation SE.

Action:
Correct the logon USERID and reissue the command.

CA-7.022

rxx.x(nnnn) LOGON REJECTED BY SECURITY AT tttttttt

Reason:
An attempt was made to log on to CA Workload Automation SE terminal tttttttt with a
USERID that has been rejected by the external security package. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE.

Action:
The error message from the security package explains the reason for error. Take the
appropriate action based on the message.

Chapter 4: CA-7.000 - CA-7.1044 919

CA-7.000 Through CA-7.094

CA-7.022

rxx.x(nnnn) LOGON REJECTED BY USER EXIT AT tttttttt

Reason:
An attempt was made to log on to CA Workload Automation SE terminal tttttttt with a
USERID that was rejected by your site's user exit (SASSXXLX). The notation rxx.x(nnnn)
indicates the product release (rxx.x) and the product level (nnnn) of CA Workload
Automation SE.

Action:
Correct the logon and reissue the command.

CA-7.022

rxx.x(nnnn) LOGON REJECTED BY UNKNOWN AT tttttttt

Reason:
An attempt was made to log on to CA Workload Automation SE terminal tttttttt with a
USERID that is not defined to the CA Workload Automation SE internal security module.
The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level
(nnnn) of CA Workload Automation SE.

Action:
Correct the logon USERID and reissue the command.

CA-7.023

- rxx.x(nnnn) OPERATOR IS LOGGED ON TO TERMINAL xxxxxxx AT hh:mm:ss ON yy.ddd

Reason:
This message typically appears when an operator logs on to a non-VTAM CA Workload
Automation SE terminal. The notation rxx.x(nnnn) indicates the product release (rxx.x)
and the product level (nnnn) of CA Workload Automation SE. xxxxxxx is the terminal
name; hhmmss and yyddd indicate current time and date, respectively. Issued by
SASSCHDS.

Action:
None.

920 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.023

- LOGON ACCEPTED, PRESS ENTER FOR MENU OR ENTER COMMAND

Reason:
This message typically appears when an operator logs on to a VTAM CA Workload
Automation SE terminal.

Action:
None.

CA-7.024

/LOGOFF SUCCESSFUL

Reason:
A user has issued the /LOGOFF command from a CA Workload Automation SE native
VTAM terminal.

Action:
None.

CA-7.024

rxx.x(nnnn) OPERATOR AT TERMINAL (tttttttt) LOGGED OFF AT

hh:mm:ss ON yy.ddd

Reason:
The /LOGOFF command was issued from the terminal tttttttt at date and time shown.
The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level
(nnnn) of CA Workload Automation SE.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 921

CA-7.000 Through CA-7.094

CA-7.025

- rxx.x(nnnn) APPLICATION MODULE - xxxxxxxx REQUIREMENTS EXCEED POOL - yyyy

Reason:
Application module xxxxxxxx attempted to perform some request that exceeded
available space in storage pool yyyy. The notation rxx.x(nnnn) indicates the product
release (rxx.x) and the product level (nnnn) of CA Workload Automation SE. Issued by
SASSCHED.
The probable cause of the error is setting JDPL or DSPL equal to zero (0) in the
initialization file RESIDENT statement.

Action:
Perform the following actions:
■ Correct JDPL or DSPL entries for the type of database being used. See the Systems
Programming Guide.
■ Examine the size of pool yyyy to assure sufficient resource for future requests.

CA-7.026

- rxx.x(nnnn) CA-7 SHUTDOWN COMPLETE

Reason:
The shutdown is complete and CA Workload Automation SE has terminated. The
notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of
CA Workload Automation SE. Issued by SASSHALT.

Action:
None.

CA-7.027

- rxx.x(nnnn) FACILITY NOT AVAILABLE IN YOUR SYSTEM.

Reason:
An attempt has been made to use a facility not available in your system. The notation
rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of CA
Workload Automation SE. Issued by SASSCHED, SASSCHDS.

Action:
None.

922 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.028

- rxx.x(nnnn) xxxxxxxx IS AN UNDEFINED TRANSACTION CODE

Reason:
The command entered was rejected because it could not be located in the system
tables. The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product
level (nnnn) of CA Workload Automation SE. Issued by SASSCHDS.

Action:
Check for spelling error and retry.

CA-7.029

- rxx.x(nnnn) EXPECTED CONTINUATION CARD NOT RECEIVED BEFORE EOD

TRANSACTION IGNORED.

Reason:
A batch execution of CA Workload Automation SE encountered end of data when it
expected continuation of transaction input. The notation rxx.x(nnnn) indicates the
product release (rxx.x) and the product level (nnnn) of CA Workload Automation SE.
Issued by SASSCHDS.

Action:
Examine the format of the transaction for an incorrect continuation indicator. Correct
the error and retry.

CA-7.031

- rxx.x(nnnn) REQUEST COMPLETED.

Reason:
This message is a typical informational response to /RESET or /SWAP.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 923

CA-7.000 Through CA-7.094

CA-7.032

- rxx.x(nnnn) APPLICATION MODULE - xxxxxxxx REQUIREMENTS EXCEED POOL - pppp

POOL SIZE - ssssss SIZE REQUESTED - rrrrrrrr SESSION CANCELED

Reason:
The application program identified by xxxxxxxx has requested more memory than is
defined to storage pool identified by pppp. The pool size is noted by ssssss. The
requested memory is noted by rrrrrrrr. The value of pppp can be one of the following:
JOBP
Job pool
DSNP
Dataset pool
APLP
Application pool
MSGP
Message pool
NSP
Nonspecific pool

The size of the APLP, JOBP, and DSNP pools are set using keywords on the RESIDENT
statement in the initialization file.

Action:
Try increasing the values on the RESIDENT statement. The region size where CA
Workload Automation SE is executing determines the size of the other pools. Try
increasing the region or decreasing the values for CWORK or CABND.

924 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.033

- rxx.x(nnnn) APPLICATION MODULE - xxxxxxxx RELEASED STORAGE FROM WRONG

POOL SESSION CANCELED

Reason:
The program identified by xxxxxxxx violated storage controls by attempting to release
storage from one pool that belonged to a different pool.

Action:
Save all console output. Swap logs so that the current log is dumped. After log dump is
complete, request report HR02 for the terminal where the message was issued.
Approximately one hour before when the message appeared is adequate in most cases.
Have the preceding information available. For assistance, contact CA Support at
ca.com/support.

CA-7.034

- rxx.x(nnnn) APPLICATION - xxxxxxxx REQUESTED - ssssss BYTES FROM POOL - pppp

POOL SIZE - ssssss SIZE REMAINING - rrrrrrrr SESSION CANCELED

Reason:
The application program identified by xxxxxxxx has requested more memory than is
available in storage pool identified by pppp. The pool size is noted by ssssss. The
requested memory is noted by rrrrrrrr. The value of pppp can be one of the following:
JOBP
Job pool
DSNP
Dataset pool
APLP
Application pool
MSGP
Message pool
NSP
Nonspecific pool

Action:
The size of the APLP, JOBP, and DSNP pools are set using keywords on the RESIDENT
statement in the initialization file. Try increasing the values on that statement. The
region size where CA Workload Automation SE is executing determines the size of the
other pools. Try increasing the region or decreasing the values for CWORK or CABND.

Chapter 4: CA-7.000 - CA-7.1044 925

CA-7.000 Through CA-7.094

CA-7.035

- rxx.x(nnnn) PAGES PURGED. TERMINAL HAS xxxx MESSAGES WAITING (TO RETRIEVE
NEXT MESSAGE ENTER /NXTMSG)

Reason:
This message is the response to either the /NXTMSG or the /PURGPG command. When
/NXTMSG is issued and are no messages are waiting for the terminal, this message is
returned with xxxx set to NO. When /PURGPG is issued, this message is returned with
xxxx set to the number of messages waiting. If xxxx is not zero, the second line of the
message appears.

Action:
None.

CA-7.038

- rxx.x(nnnn) INVALID REQUEST FOR PAGE SERVICE

Reason:
A /PAGE command was issued from a batch terminal or when no pages existed. The
notation rxx.x(nnnn) indicates the product release (rxx.x) and the product level (nnnn) of
CA Workload Automation SE. Issued by SASSCHDS.

Action:
Delete /PAGE command from the batch terminal input.

CA-7.039

- rxx.x(nnnn) MSG LOST - TERMINAL NOT AVAILABLE

Reason:
The terminal could not be found in the CA Workload Automation SE internal table of
terminals and logical terminals. The notation rxx.x(nnnn) indicates the product release
(rxx.x) and the product level (nnnn) of CA Workload Automation SE. Issued by
SASSEMGR, SASSCHDM.

Action:
Contact your installation specialist for assistance.

926 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.042

- rxx.x(nnnn) SECURITY REQUIRES LOGON FOR THIS COMMAND.

Reason:
This message occurs when a command is used that requires security checking but the
terminal has not been logged on. The notation rxx.x(nnnn) indicates the product release
(rxx.x) and the product level (nnnn) of CA Workload Automation SE. Issued by
SASSCHDS.

Action:
Issue the /LOGON command, and then reenter the command.

CA-7.043

- rxx.x(nnnn) YOU ARE NOT AUTHORIZED FOR THIS COMMAND.

Reason:
This message occurs when a command is issued that fails the security check of the
operator. The notation rxx.x(nnnn) indicates the product release (rxx.x) and the product
level (nnnn) of CA Workload Automation SE. Issued by SASSCHDS.

Action:
None. If you want the operator to issue this command, change either the security level
of the operator or the security level for the command in the SASSDSCR module.

CA-7.050

- CA-7 NOW LOGGING ON ALOGx

Reason:
This message indicates the current Log data set to which CA Workload Automation SE is
writing records of its activity. If the primary log is in use, x is 1. If the secondary log is in
use, x is 2. Issued by SASSINWC.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 927

CA-7.000 Through CA-7.094

CA-7.051

- ENTER DUMP FOR ALOG1 AND ALOG2

or

- ENTER DUMP FOR ALOGx

Reason:
A job must be submitted to dump the primary Log data set (if x=1), the secondary Log
data set (if x=2), or both logs when so indicated. Issued by SASSINWC.

Action:
Submit the appropriate job to dump the specified Log data set. This submission must be
done before you can initialize CA Workload Automation SE.

CA-7.052

- LOG CONTROL FLAG IS INVALID

Reason:
An invalid log control flag was found in the Checkpoint record during initialization.
Issued by SASSINWC.

Action:
Contact your installation specialist for assistance.

CA-7.053

MASTER TERMINAL NOT DEFINED

Reason:
A Master Terminal has not been defined for CA Workload Automation SE.

Action:
Issued by SASSCHDE. Ensure that the product's initialization file contains one TERM
statement with CONS=MASTR specified to designate a Master Terminal.

928 Message Reference Guide

 CA-7.000 Through CA-7.094

CA-7.060

- xxxxx FAILED FOR BSAM DATASET, DDN=xxxxxxxxx (R15=nnnnnnnn)

Reason:
CA Workload Automation SE is unable to open the Browse data set. R15 shows code as:
■ 08 - DSN not found in catalog
■ 0C - Data set not found on volume
■ 10 - Invalid DSORG
■ 14 - Invalid DCB attribute
■ 18 - DASD volume not available
■ 1C - Member not found
■ 20 - Write I/O error
■ 24 - Data set is password-protected
■ 28 - Data set is busy
■ 2C - Member already exists
■ 30 - New name already exists
■ 34 - Store error
■ 38 - Data set out of space
■ 3C - Data set is date protected
■ 40 - Invalid parameter data
■ 54 - Data set is user ID protected or user-exit SASSXX07 denied access
■ 58 - Invalid DDNAME specified

Issued by SASSDLOG.

Action:
If unable to resolve the problem, contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 929

CA-7.000 Through CA-7.094

CA-7.093

CA-7/VTAM LOGON FOR xxxxxxxx REJECTED. VTAM ID NOT DEFINED.

Reason:
A VTAM terminal with the node name xxxxxxxx attempted log on to CA Workload
Automation SE. The logon was rejected because the VTAM terminal is not defined to CA
Workload Automation SE with a TERM statement in the initialization file. Issued by
SASSLGON. Another possibility is that all the CA Workload Automation SE virtual
terminals (as defined in the initialization file - VTM#nnn) are already in use.

Action:
If the terminal should not have access to CA Workload Automation SE, no action is
required. If the user wants to access CA Workload Automation SE from the terminal, a
TERM statement must be added to the initialization file with other changes needed to
add a terminal. If the problem is because all the virtual terminals are in use, wait a few
minutes until someone else logs off or increase the number of virtual terminals.

CA-7.094

- TERMINAL BUSY/STOPPED.

Reason:
The terminal used to input the command is busy or has been stopped. Issued by
SASSW32V, SASSW32R.

Action:
The terminal can be started by issuing a /START,T=termname from another authorized
terminal.

930 Message Reference Guide

 CA-7.100 Through CA-7.153 Messages

CA-7.100 Through CA-7.153 Messages

CA-7.100

LOAD DATA FOR JOB xxxxxxxx CREATED. (JOB FLUSHED) nnnn

Reason:
This is an information message issued by the CA Workload Automation SE load step. The
step is added to a user's JCL stream to cause the addition or replacement of job records
in the CA Workload Automation SE database. The message indicates that the records
necessary to load a job into the database have been created. When JOB FLUSHED
appears in the message, a load-only run without actual execution of the user's job is
being performed. Following the execution of the CA Workload Automation SE load step,
all remaining JCL will be flushed. The CA Workload Automation SE instance name is
identified in nnnn. Issued by SASSJJCL.

Action:
None.

CA-7.101

COULD NOT READ JOB CONTROL TABLE - U0101

Reason:
The CA Workload Automation SE load step could not read the Job Control Table (JCT).
Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

CA-7.102

PROGRAM SASSJJCL NOT FIRST STEP OF JOB - U0102

Reason:
The CA Workload Automation SE load step was not inserted as the first step of the job
being loaded. Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 931

CA-7.100 Through CA-7.153 Messages

CA-7.103

COULD NOT WRITE JOB CONTROL TABLE - U0103

Reason:
The CA Workload Automation SE load step was unable to write to the Job Control Table
(JCT). Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

CA-7.104

PROGRAM SASSJJCL ONLY STEP IN JOB - U0104

Reason:
The job being loaded contains only the CA Workload Automation SE load step. Issued by
SASSJJCL.

Action:
Review the JCL for the job; the job must have at least one step. Reload the job.

CA-7.105

EXPECTED STEP CONTROL TABLE NOT READ - U0105

Reason:
The CA Workload Automation SE load step expected to read a Step Control Table (SCT)
entry; the data received was not an SCT. Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

CA-7.106

EXPECTED SIOT/JFCB RECORDS NOT READ - U0106

Reason:
The CA Workload Automation SE load step expected to read a Step I/O Table (SIOT)
entry or a Job File Control Block (JFCB) entry; the data received was not a SIOT or JFCB.
Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

932 Message Reference Guide

 CA-7.100 Through CA-7.153 Messages

CA-7.107

EXPECTED SSWA RECORDS NOT READ - U0107

Reason:
There was an error while attempting to examine, modify, or delete records used to
update the CA Workload Automation SE database. CA Workload Automation SE
terminates with a U0107 abend. Issued by SASSJJCL.

Action:
Contact your installation specialist for assistance.

CA-7.107

UNKNOWN OPERATING SYSTEM - U0107

Reason:
The CA Workload Automation SE load step was unable to determine the operating
system in which it was executing. Issued by SASSJJQM.

Action:
Contact your installation specialist for assistance.

CA-7.108

QUEUE RECORD ID FROM JOB QUEUE NOT CORRECT - U0108

Reason:
The CA Workload Automation SE load step encountered an incorrect queue record ID in
the Job queue. Issued by SASSJJQM.

Action:
Ensure that CAIRIM has run to initialize the CA Workload Automation SE system
environment and the target instance has been added. If the problem persists, contact
your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 933

CA-7.100 Through CA-7.153 Messages

CA-7.109

BAD RETURN FROM JOB QUEUE MANAGER - U0109

Reason:
The CA Workload Automation SE load step has detected an unknown return code from
the Job Queue Manager. Issued by SASSJJQM.

Action:
Contact your installation specialist for assistance.

CA-7.110

BAD USER SVC - U0110

Reason:
The CA Workload Automation SE load step has determined that the CA Workload
Automation SE SVC is incorrect. Issued by SASSJJCL.

Action:
Ensure that CAIRIM has run to initialize the CA Workload Automation SE system
environment and the target instance has been added. If the problem persists, contact
your installation specialist for assistance.

CA-7.111

nnnn NOT MATCHED IN ICMDSECT

Reason:
The CA Workload Automation SE load step has determined that the instance control
block (ICMDSECT) is not correct for the CA Workload Automation SE instance named in
nnnn.

Action:
Ensure that CAIRIM has run to initialize the CA Workload Automation SE system
environment and the target instance has been added. If the problem persists, contact
your installation specialist for assistance.

934 Message Reference Guide

 CA-7.100 Through CA-7.153 Messages

CA-7.112

nnnnnnnn LOAD RECORDS CHANGED BY SASSXX12

Reason:
If the user exit SASSXX12 is used, it can modify records. This message indicates how
many records were changed.

Action:
None.

CA-7.113

nnnnnnnn LOAD RECORDS DELETED BY SASSXX12

Reason:
If the user exit SASSXX12 is used, it can delete records. This message indicates how
many records were deleted.

Action:
None.

CA-7.114

UNABLE TO OPEN EXTRACE DD

Reason:
CA Workload Automation SE could not open the trace data set that has a ddname of
EXTRACE. Issued by SASSJJCL.

Action:
Ensure the JCL is correct and resubmit the job.

CA-7.115

UNABLE TO LOAD SASSPMDD, PERM DDNAME PROCESSING TERMINATED

Reason:
CA Workload Automation SE was not able to load program SASSPMDD. Issued by
SASSJJCL.

Action:
Ensure program SASSPMDD is in the CA Workload Automation SE load library. If it is,
contact CA Support at ca.com/support for assistance.

Chapter 4: CA-7.000 - CA-7.1044 935

CA-7.100 Through CA-7.153 Messages

CA-7.116

INVALID PARAMETER

Reason:
The parameters TEST=YES and CA7=nnnn, where nnnn is a CA Workload Automation SE
instance name, are mutually exclusive. Issued by SASSJJCL. Either:
■ Both parameters appear in the parameter list, or
■ nnnn is greater than four characters

Action:
Correct the JCL by removing one of the parameters or specifying a one- to
four-character instance name.

CA-7.150

- CA-7 VRM ACTIVE RESOURCE RECORDS UNLOADED

Reason:
The VRM active resource records were successfully unloaded during DMPQ (Dump
queue) shutdown processing. Issued by SASINQD.

Action:
None.

CA-7.151

- NO ACTIVE RESOURCE RECORDS FOUND

Reason:
CA Workload Automation SE found no VRM active resource records on the VRM
database component to unload during DMPQ (Dump queue) shutdown processing.

Action:
None.

936 Message Reference Guide

 CA-7.100 Through CA-7.153 Messages

CA-7.152

- ARF ACTIVE RECORDS UNLOADED

Reason:
The ARF active records were successfully unloaded during DMPQ (Dump queue)
shutdown processing. Issued by SASSINQD.

Action:
None.

CA-7.153

- NO ARF ACTIVE RECORDS FOUND

Reason:
CA Workload Automation SE found no ARF active records on the ARF database
component to unload during DMPQ (Dump queue) shutdown processing.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 937

CA-7.200 Through CA-7.260

CA-7.200 Through CA-7.260

CA-7.200

- BOTH LOG FILES ARE FULL,

DUMP LOG FILES,
THEN REPLY "LOGP" IF PRIMARY WAS DUMPED,
OR REPLY "LOGS" IF SECONDARY WAS DUMPED,
AWAITING REPLY: LOGP, LOGS, OR CANCEL

Reason:
Both Log data sets are full; at least one log must be dumped before CA Workload
Automation SE execution can continue. This message could appear during initialization if
CA Workload Automation SE could not determine which log file was last in use at
shutdown. Issued by SASSBTMG.
The jobs to dump the Log data sets have been submitted (either manually or
automatically by CA Workload Automation SE) but have not run.

Action:
Take the required action to cause execution of one of the dump jobs by submitting
outside of CA Workload Automation SE. When the job has successfully completed, reply
to the outstanding WTOR with either LOGP (primary) or LOGS (secondary) to indicate
which log was dumped.

CA-7.201

- CANCEL REQUESTED

Reason:
An operator replied CANCEL to the outstanding CA-7.200 WTOR. Issued by SASSBTMG.

Action:
Dump the Log data sets and then restart CA Workload Automation SE.

938 Message Reference Guide

 CA-7.200 Through CA-7.260

CA-7.202

- ERROR ON LOG DATASET ERROR CODE=x

Reason:
x has two values:
■ If x=1, the audit flags indicate that both log files are active.
■ If x=2, the open for the Log data set failed.

Issued by SASSBTMG.

Action:
Obtain the dump and then contact your installation specialist for assistance.

CA-7.203

- OUT OF SPACE IN INDEX DATA SET

Reason:
The CA Workload Automation SE IDS is out of space. Issued by SASSBTMG, SASSVSM1,
SASSSCM2.

Action:
Allocate more space to the data set after shutting down CA Workload Automation SE.
Copy the data set and reinitialize CA Workload Automation SE.

CA-7.204

- OUT OF SPACE IN xxxxxx DATA SET DIRECTORY

Reason:
Not enough space is available in the data set directory indicated by xxxxxx. This message
only pertains to PDS data sets. Issued by SASSBTMG, SASSSCM2.

Action:
Shut down CA Workload Automation SE, allocate more directory blocks, copy the data
set, and reactivate CA Workload Automation SE.

Chapter 4: CA-7.000 - CA-7.1044 939

CA-7.200 Through CA-7.260

CA-7.205

- OUT OF SPACE IN xxxxxx DATA SET

Reason:
Not enough space is available in the Job or Dataset data set. xxxxxx indicates the data
set. Issued by SASSCHDB, SASSSCM2.

Action:
Allocate more space to the data set after shutting down CA Workload Automation SE.
Copy the data set and reinitialize CA Workload Automation SE.

CA-7.206

- PDS DATA BASE MUST BE SINGLE EXTENT, PLEASE REALLOCATE

Reason:
An error condition occurred while trying to output to a PDS database file. The error
indicated a multiple extent PDS that CA Workload Automation SE does not support.
Reallocate the file in question as a single extent PDS to avoid unpredictable errors.
Issued by SASSDBMG.

Action:
Shut down CA Workload Automation SE, back up the database, reallocate the PDS files
in the database as single extent files, then reload the database, and restart CA Workload
Automation SE.
An alternative to reallocating is to convert to the ALLVSAM form of the database.

940 Message Reference Guide

 CA-7.200 Through CA-7.260

CA-7.252

BATCH TERMINAL #n IN USE. REPLY WAIT, CANCEL, OR RESET

Reason:
The control record in the Communications data set indicates the specified batch
terminal is already in use. The value of n denotes the batch terminal number being
used. Issued by SASSBSTR.

Action:
The status of the batch terminal can be determined by entering
/DISPLAY,T=batchtermname. Reply should be as follows:
WAIT
If the batch terminal is truly busy, (SKIP status).
CANCEL
If the status display indicates that the terminal is BUSY (SKIP status) and you do not
want to wait for the completion of the job currently using the Batch Terminal.
RESET
If the status display indicates the terminal is stopped. CA Workload Automation SE
will reset the status indicated in the Communications data set allowing the job to
run. A previous BTI job was probably canceled.

CA-7.253

ALL AVAILABLE BATCH TERMS IN USE. REPLY WAIT OR CANCEL.

Reason:
This message is issued when the Dynamic BTI Management option is in use; but, all
terminals in the batch terminal pool have been busy for five minutes. Issued by
SASSBSTR.

Action:
Perform one of the following actions:
■ Reply WAIT to instruct the program to keep looking until a batch terminal becomes
available.
■ Reply CANCEL to terminate the batch BTI job so that it can be resubmitted at a later
time.

Chapter 4: CA-7.000 - CA-7.1044 941

CA-7.200 Through CA-7.260

CA-7.254

IS CA-7 ACTIVE?? REPLY YES OR NO

Reason:
The control record in the Communications data set indicates that CA Workload
Automation SE is active but 60 seconds have elapsed and the batch terminal has not
been started. Issued by SASSBSTR.

Action:
If CA Workload Automation SE is active, reply YES; if not, reply NO. Check the JCL for the
batch terminal interface to make sure the correct Communications data set is being
used.

CA-7.255

WAITING FOR CA-7 TO COME UP. REPLY 'END' TO TERMINATE BTI JOB.

Reason:
The CA Workload Automation SE Communciations data set indicates the CA Workload
Automation SE address space is not active. This WTOR allows you the opportunity to
terminate the BTI job rather than having it wait for CA Workload Automation SE to
become active.

Action:
Take no action if you want the BTI job to wait for CA Workload Automation SE to come
up. When CA Workload Automation SE becomes active, this WTOR is automatically
deleted and the BTI job proceeds with normal processing. If CA Workload Automation
SE will be down for some time and you do not want the BTI job to wait for it, reply END.
The BTI step will terminate with a return code of 8.

CA-7.256

SYSPRINT DD STATEMENT MISSING

Reason:
The SYSPRINT DD was omitted from the batch terminal interface JCL. Issued by
SASSBSTR.

Action:
Correct the JCL and resubmit the job.

942 Message Reference Guide

 CA-7.200 Through CA-7.260

CA-7.256

UCC7OUT DD STATEMENT MISSING

Reason:
UCC7OUT DD was omitted and the file could not be opened. Issued by SASSBTSO.

Action:
Correct and retry.

CA-7.257

BTERM FLAG RESET, CA-7 SHUTDOWN ASSUMED

Reason:
The control record in the Communications data set indicates the batch terminal is no
longer in use. CA Workload Automation SE might have been shut down immediately
following batch terminal processing. Or, a bad run of SASSBEND to clear the BTERM flags
might have occurred. The shutdown case is assumed. Issued by SASSBSTR.

Action:
If CA Workload Automation SE has not been shut down, check to see if PGM SASSBEND
or SASSICLR was executed during this time frame. These programs should execute only if
CA Workload Automation SE or SASSBSTR terminate abnormally (COND=ONLY).

CA-7.258

*WARNING* ERROR RECOVERY UNABLE TO FREE BTI TERMINAL #n. *WARNING*

Reason:
This message is issued when the error recovery routines are unable to reset the usage
flags for a batch terminal in the CA Workload Automation SE Communications data set.
The specified batch terminal will remain unavailable until these flags are reset. Issued by
SASSBSTR.

Action:
Execute SASSBEND to reset the flags for the specified batch terminal.

Chapter 4: CA-7.000 - CA-7.1044 943

CA-7.3XXX Through CA-7.378

CA-7.260

I/O ERROR ON BATCH TERMINAL

Reason:
Batch terminal processing detected an I/O error on a batch data set. Issued by
SASSIBAT.

Action:
Check DCB specifications for batch data sets and retry. The BUFSIZE on the LINE
statement in the initialization file should be the same as the BLKSIZE of the batch input
data set.

CA-7.3XXX Through CA-7.378

CA-7.3XXX

CURRENT NUMBER OF SMF RECORDS IN CSA = xxxxx

Reason:
This message is produced if the number of chained SMF records in CSA is a multiple of
1024.

Action:
None.

CA-7.3XXX

STOPPING CAPTURE OF SMF 0E RECORDS

Reason:
This message is produced for the first occurrence of an input data set SMF record
(type-14) when the number of chained SMF records is at least 1024. This message is a
WTO that is highlighted and non-scrollable.

Action:
In general, no action is required. The statistics reflected by GRAPHJ,ID=450 will not
include the SMF records that are skipped. In addition, the effects will be similar to using
PERFORM=1 in the INIT file.

944 Message Reference Guide

 CA-7.3XXX Through CA-7.378

CA-7.3XXX

STOPPING CAPTURE OF SMF 0F RECORDS

Reason:
This message is produced for the first occurrence of an output data set SMF record
(type-15) when the number of chained SMF records is at least 4096. This message is a
WTO that is highlighted and non-scrollable.

Action:
Skipping the SMF output data set records can affect all data set postings and data set
triggering. Also, the statistics reflected by GRAPHJ,ID=460 do not include the SMF
records that are skipped.

CA-7.3XXX

RESUMING CAPTURE OF SMF DATA

Reason:
This message is produced for the first occurrence of either an SMF type-14 or -15 record
when the chained record count is reduced to 200 and the capturing of SMF type-14 or
-15 records has been previously suspended.

Action:
None.

CA-7.301

- SASSEMGR - ERROR xxx OCCURRED PROCESSING ERROR yyy

Reason:
Another error occurred while trying to process an error. The current session is canceled.
Issued by SASSEMGR.

Action:
If xxx=007 and yyy=001, look for a missing FMTBLK statement in the initialization file or
more than 32767 logical terminals defined.

If xxx=009 and yyy=001, more than one terminal is defined with the same name.

Enter the next command; contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 945

CA-7.3XXX Through CA-7.378

CA-7.302

- SASSEMGR - SCT WITHOUT A TSRLIST

Reason:
No TSRLIST could be found for the SCT issuing the error message. Issued by SASSEMGR.

Action:
Contact your installation specialist for assistance.

CA-7.302

- SASSSCM2 SASSHALT SCT NOT FOUND

Reason:
A search of the SCTs for SASSHALT has failed. Issued by SASSSCM2.

Action:
Contact your installation specialist for assistance.

CA-7.303

- SASSSCM2 SCT TO BE LOGGED OFF NOT FOUND

Reason:
The SCT for the terminal to log off cannot be found. Probable control block error. Issued
by SASSSCM2.

Action:
Contact your installation specialist for assistance.

946 Message Reference Guide

 CA-7.3XXX Through CA-7.378

CA-7.303

- SASSEMGR - SYSTEM SCT ERROR

Reason:
A system SCT received an invalid error message request. Issued by SASSEMGR.

Action:
Perform the following actions:
■ Examine the RESIDENT statement in the initialization file.
■ Verify that the parameter APGPL is coded and that it is large enough. Do not use a
value less than 204800.
■ Examine the LOGP and LOGS data sets. They must be allocated with at least two
tracks.
For assistance, contact CA Support at ca.com/support.

CA-7.305

- SCRATCH QUEUE SPACE EXHAUSTED - U0305.

Reason:
All the Scratch queue (UCC7SCRQ) tracks are allocated, and no additional tracks are
available. Issued by SASSDAIO.

Action:
ERST start CA Workload Automation SE (TYPE=ERST). All messages and scratch areas are
purged. Note the Action for Message CA-7.306, which should eliminate the abend.

Chapter 4: CA-7.000 - CA-7.1044 947

CA-7.3XXX Through CA-7.378

CA-7.306

- **WARNING** 80% xxxxxxx QUEUE UTILIZATION **WARNING**

Reason:
Eighty percent of the queue indicated by xxxxxxx has been used. One of the following
values replaces xxxxxxx, indicating which queue has reached 80 percent use: SCRATCH,
DQTABLE, TRAILER, REQUEST, READY, ACTIVE, or PRRNQ.

Action:
Perform one of the following actions:
■ Recycle CA Workload Automation SE using TYPE=ERST if xxxxxxx indicates SCRATCH
or DQTABLE.
■ Verify the allocation of the queue with the command /DISPLAY,Q=ALL if xxxxxxx
indicates TRAILER.
To reduce trailer queue usage, delete retained JCL for jobs (see the PRRNJCL
command) or delete jobs from the request, ready, or active queues.
■ Determine whether workflow is flowing through the system or whether the ready
queue is in a stopped state if xxxxxxx indicates REQUEST.
To prevent workflow from entering the queues, you can enter STOP,Q=REQ until
that workflow starts moving through the queues again. If you entered the STOP
command, enter the START command to resume workflow through the queues.
■ Determine why jobs are being held in the ready queue if xxxxxxx indicates READY.
Is the ready queue stopped? Are VRM resources properly configured?
■ Determine whether ICOM is active on LPARs where CA Workload Automation SE
submits jobs if xxxxxxx indicates ACTIVE.
If ICOMs are active, are there any issues in the operating system, especially SMF
feedback area?
■ Determine what jobs you can delete from the prior run queue and delete them if
xxxxxxx indicates PRRNQ.

To prevent future space shortages, consider increasing the size of the queue indicated
by xxxxxxx.

948 Message Reference Guide

 CA-7.3XXX Through CA-7.378

CA-7.307

- **xxxxxxx QUEUE TRACK SHORTAGE RELIEVED**.

Reason:
The use of the queue indicated by xxxxxxx has dropped below 70 percent. This message
occurs after Message CA-7.306 is issued.

Action:
None.

CA-7.360

- LTERM=xxxxxxxx (yyyyyyy) HAS nnnn MESSAGES QUEUED.

Reason:
For information only. nnnn messages are queued to the logical terminal xxxxxxxx and
physical terminal yyyyyyy. Issued by SASSQMGO.

Action:
None.

CA-7.370

BAD RESERVE-ENQUEUE MACRO RETURN.

Reason:
A bad return code was received from the SCOMRD macro during a read of the
Communications data set. Issued by SASSCMGR. A serious problem exists within CA
Workload Automation SE.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 949

CA-7.3XXX Through CA-7.378

CA-7.371

I/O ERROR ON RBN0 READ.

Reason:
An I/O error occurred while attempting to read the RBN0 control record in the
Communications data set. Issued by SASSCMGR. This message sometimes indicates a
serious problem.

Note: If error occurs during initialization, the Communications data set may never have
been formatted.

Action:
Contact your installation specialist for assistance. If the Communications data set has
never been initialized (formatted), run the CDSI installation job.

CA-7.372

COMM DATA SET NOT ENQUEUED.

Reason:
A DEQUEUE was attempted during a write of a record that was not ENQUEUED. Issued
by SASSCMGR. A serious problem exists within CA Workload Automation SE.

Action:
Contact your installation specialist for assistance.

CA-7.373

BAD RELEASE/DEQUEUE MACRO RETURN.

Reason:
A bad return code was received from the SCOMWR macro during a write of the RBN0
control record in the Communications data set. Issued by SASSCMGR. A serious problem
exists within CA Workload Automation SE.

Action:
Contact your installation specialist for assistance.

950 Message Reference Guide

 CA-7.3XXX Through CA-7.378

CA-7.374

I/O ERROR ON WRITE.

Reason:
An I/O error occurred while attempting to write the RBN0 control record in the
Communications data set. Issued by SASSCMGR.

Action:
This could be a serious problem. Contact your installation specialist for assistance.

CA-7.375

SMF SCT NOT AVAILABLE - NO RECORD RETURNED.

Reason:
An SCT for the SMF routines could not be located, resulting in a condition that does not
permit the processing of any SMF data. Issued by SASSCMGR.

Action:
A serious problem exists within CA Workload Automation SE. Contact your installation
specialist for assistance.

CA-7.376

TRAILER LINE AREA NOT AVAILABLE - NO RECORDS RETURNED.

Reason:
A line for the Trailer Step routines could not be located, resulting in a condition that
does not permit the processing of any trailer commands. Issued by SASSCMGR.

A serious problem exists in CA Workload Automation SE.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 951

CA-7.400 Through CA-7.490

CA-7.377

UNABLE TO OPEN UCC7STAT FILE

Reason:
The Statistics data set could not be opened, possibly because of a missing DD statement.
Issued by SASSCMGR.

Action:
No action is needed for CA Workload Automation SE to execute; however, no statistics
can be gathered and no graphing done. Add a DD statement to the execution JCL if
statistics features are wanted.

CA-7.378

I/O ERROR ON UCC7STAT FILE

Reason:
An I/O error occurred while attempting to write to the Statistics data set. Issued by
SASSCMGR.

Action:
If the Statistics data set has just been allocated (for new users), it must be initialized by
the SASSCDSI program before it can be used by CA Workload Automation SE. If it has
been reallocated on another pack, the old Statistics data set should be copied to the
newly allocated data set. Contact your installation specialist for assistance.

CA-7.400 Through CA-7.490

CA-7.400

- MAIN STORAGE MANAGER ERROR - U0400

Reason:
Invalid data was passed to the CA Workload Automation SE main storage manager. A
user 400 abend results. Issued by SASSMAIN, SASSF32V.

Action:
Restart CA Workload Automation SE with a TYPE=ERST. Contact your installation
specialist if the condition persists.

952 Message Reference Guide

 CA-7.400 Through CA-7.490

CA-7.401

- SCHEDULER INITIALIZATION REQUIRES MORE STORAGE

Reason:
Core was not available for a TSRLIST for Schedule Scan or for SASSCHED. (SASSCHED's
TSRLIST is used to write COLD/RESTART messages.) Issued by SASSCHED.

Action:
Increase the REGION size in the CA Workload Automation SE execution JCL and resubmit
the job.

CA-7.402

SYSTEM ERROR. CODE = xxxx

Reason:
A system error occurred. This message is usually preceded by a CA-7.404 message.
Issued by SASSNUC.

Action:
Contact your installation specialist for assistance. Be sure to have any CA-7.404
messages available.

CA-7.403

- SASSxxxx - STORAGE MANAGEMENT ERROR - U0403

Reason:
An invalid return code was received from a request for core. Issued by SASSCHDB,
SASSCHDM, SASSCHDQ, SASSCHDS, SASSCHDW, SASSCHED.

Action:
For PDS/VSAM, examine the Job data set block size. The size must be 1024. For
assistance, contact CA Support at ca.com/support.

Chapter 4: CA-7.000 - CA-7.1044 953

CA-7.400 Through CA-7.490

CA-7.404

ATTACH FOR SASSBTMG FAILED. CODE = xxyyyyyy

Reason:
CA Workload Automation SE was unable to attach the subtask manager. Issued by
SASSNUC.

Action:
Contact your installation specialist for assistance.

CA-7.404

SUBTASK xxxx TERMINATED. TCBCMP = xxyyyzzz

Reason:
CA Workload Automation SE SUBTASK xxxx has terminated. yyy is the system abend
code and zzz is the user abend code. Both are in hex. Issued by SASSNUC.

Action:
If TCBCMP field is nonzero, contact your installation specialist for assistance. If TCBCMP
field is zero, the SUBTASK has completed normally and no action is required.

CA-7.405

- SASSCHDM - ERROR DURING ABEND DUMP - U0405

Reason:
CA Workload Automation SE module encountered an error while putting out SNAP
dump for an abend. Issued by SASSCHDM.

Action:
Contact your installation specialist for assistance.

CA-7.406

- SASSCHDM - INVALID MESSAGE REQUEST - U0406

Reason:
An invalid SPUTMSG has been issued. Issued by SASSCHDM.

Action:
Contact your installation specialist for assistance.

954 Message Reference Guide

 CA-7.400 Through CA-7.490

CA-7.407

- SASSCHDM - MSG SWITCH ERROR - U0407

Reason:
No format block was available to output the SPUTMSG request. Possible module load
failure. Issued by SASSCHDM.

Action:
Verify that FMTBLK statements for both SASSFMTA and SASSFMTH are in the
initialization file and that both specify ATTR=LOAD. If both are present, contact your
installation specialist for assistance.

CA-7.408

SASSSN00 ERROR CODE = xx

Reason:
A call to program SASSSN00 resulted in a non-zero return code, which is xx. CA
Workload Automation SE terminates with a U0408 abend. Issued by SASSCHED.

Action:
If xx=12, the CA Workload Automation SE region size needs to be increased. For any
other return code, contact your installation specialist for assistance.

CA-7.410

- UCC7DUMP DATASET FAILED TO OPEN

Reason:
An attempt to OPEN the data set defined by the UCC7DUMP DD statement has failed.
Issued by SASSNUC.

Action:
Verify that the UCC7DUMP DD statement is present in the CA Workload Automation SE
JCL; if it is, contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 955

CA-7.400 Through CA-7.490

CA-7.411

CUSTOMIZED VERSION OF EBCDIC/ASCII TRANSLATE TABLES IN CAL2XLAT DETECTED

Reason:
The user loaded a custom version of the EBCDIC/ASCII translate tables.

Action:
None.

CA-7.412

- ERROR WRITING CA-7 NUMBER TABLE - U0412

Reason:
An I/O error occurred while attempting to write a Checkpoint record for the CA
Workload Automation SE number table. CA Workload Automation SE abends. Issued by
SASSNUC.

Action:
Contact your installation specialist for assistance.

CA-7.413

- ERROR USING SNAT -- MUST HAVE A TSRLIST

Reason:
An attempt was made to use the CA Workload Automation SE Number Allocator Table
without a TSR list. Issued by SASSNUC.

Action:
Contact your installation specialist for assistance.

CA-7.444

(/DMP1)
(/DUMP) COMMAND ACCEPTED - U0444

Reason:
A /DUMP or /DMP1 request has been accepted for processing. Issued by SASSSCM3.

Action:
None.

956 Message Reference Guide

 CA-7.400 Through CA-7.490

CA-7.445

- OUT OF SPACE ON LOG FILE.

Reason:
During a batch-only run of CA Workload Automation SE, the primary Log file filled up
and a swap was attempted. Issued by SASSLOGM.

Action:
Increase the space allocation to the primary Log file, or assign the primary Log file to a
tape and start CA Workload Automation SE again.

CA-7.490

xxxxxxxx IS FULL

Reason:
During a startup of CA Workload Automation SE the xxxxxxxx queue file was found to be
full. Issued by SASSINW3.

Action:
None. This is an informational message. You should probably consider increasing the
size of the indicated queue.

Chapter 4: CA-7.000 - CA-7.1044 957

CA-7.500 Through CA-7.593

CA-7.500 Through CA-7.593

CA-7.500

CHECKPOINT ERROR. REPLY Y TO CONTINUE WITHOUT CHECKPOINTING.

Reason:
An error has occurred during CA Workload Automation SE system checkpoint activity
because of one of the following:
■ The Checkpoint data set is on a device type different from the queues.
■ The Checkpoint data set was not allocated on a cylinder boundary.
■ Not enough space is allocated to the Checkpoint data set.
■ An I/O error.

Issued by SASSCKPT.

Action:
CA Workload Automation SE remains in a wait state until a reply of Y is done. Recycle CA
Workload Automation SE as soon as possible. Reply Y and shut down CA Workload
Automation SE as soon as possible or cancel CA Workload Automation SE with a dump.

When Checkpointing is not done, Schedule Scan can rescan previous time frames
bringing in jobs that have already executed. Also, WLB definitions do not always reflect
current values. The queue data sets do not show jobs that should be showing. All of
these things can happen when CA Workload Automation SE is not recycled as soon as
possible.

CA-7.510

- CA-7 SHUTDOWN COMPLETE

Reason:
Self-explanatory. Issued by SASSHALT.

Action:
None.

958 Message Reference Guide

 CA-7.500 Through CA-7.593

CA-7.511

- BATCH TEST HAS EXCEEDED TIME - U0511

Reason:
The time limit imposed on batch execution of CA Workload Automation SE has been
exceeded. The default is one hour. Issued by SASSHALT.

Action:
Increase the TIMLIM value on the INIT statement in the product's initialization file and
resubmit the run. If the failure recurs, contact your installation specialist for assistance.

CA-7.512

- COMDS IS BUSY SHUTDOWN IS WAITING

Reason:
CA Workload Automation SE is attempting to update the RBN0 control record of the
Communications data set during shutdown. The update is waiting for the data set to
become available. Issued by SASSHALT.

Action:
No action is necessary unless the message persists, in which case, contact your
installation specialist for assistance.

CA-7.514

- RBN-ZERO ERROR RETURN CODE = xx

Reason:
An invalid return code (indicated by xx) was received from an attempt to update the
RBN0 control record during shutdown. Issued by SASSHALT.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 959

CA-7.500 Through CA-7.593

CA-7.554

- I/O ERROR READING LOG DATASET MUST COLD START

Reason:
An unrecoverable I/O error occurred while attempting to process the Log data set
during initialization. CA Workload Automation SE is not initialized. Issued by SASSINE1.

Action:
To attempt to recover without a COLD start, scratch and reallocate the Log data set in
error. If problem remains, CA Workload Automation SE must be COLD started
(TYPE=COLD).

CA-7.560

- SASSMA31 - STORAGE NOT AVAILABLE, ZERO BYTES REQUESTED.

Reason:
If a request for core cannot be satisfied and NCWT is specified on the INIT statement in
the CA Workload Automation SE initialization file, CA Workload Automation SE abends.
Issued by SASSMAIN.

Note: This situation should never occur in online mode. Omit NCWT from the INIT
statement, thus allowing this wait during online execution.

Action:
Contact your installation specialist for assistance.

CA-7.560

- SASSMAIN - STORAGE NOT AVAILABLE. ZERO BYTES REQUESTED.

Reason:
The CA Workload Automation SE main storage manager received a request for 0 (zero)
bytes of main storage. Issued by SASSMAIN.

Action:
If a WARM start of CA Workload Automation SE fails, attempt a specific ERST start. If the
problem persists, contact your installation specialist for assistance.

960 Message Reference Guide

 CA-7.500 Through CA-7.593

CA-7.560

SASSMA31 - STORAGE NOT AVAILABLE,NO WAIT REQUESTED - U560

Reason:
If a request for core cannot be satisfied and NCWT has been specified on the INIT
statement in the CA Workload Automation SE initialization file, CA Workload
Automation SE will abend. Issued by SASSMA31.

Action:
This should never occur in online mode. Omit NCWT from the INIT statement to permit
the wait during online execution.

CA-7.560

SASSMA31 - STORAGE NOT AVAILABLE. ZERO BYTES REQUESTED

Reason:
CA Workload Automation SE cannot honor a request for zero bytes of storage above the
16 MB line. Issued by SASSMA31.

Action:
If a WARM start of CA Workload Automation SE fails, attempt an ERST start. If the
problem persists, contact your installation specialist for assistance.

CA-7.565

SASSXTQV STORAGE SHORTAGE aaaa bbbb

Reason:
The instorage trailer queue is unable to get more storage. CA Workload Automation SE
abends with a S0C3.

Action:
If aaaa is less then bbbb, increase the REGION for CA Workload Automation SE. For
example, if the REGION is currently 50 MB, increase the value to 80 MB.

Chapter 4: CA-7.000 - CA-7.1044 961

CA-7.500 Through CA-7.593

CA-7.574

(taskname) ENTER REQUEST FOR ICOM (xxxx)

Reason:
This is an outstanding WTOR for ICOM. Replies may be used to display control blocks for
ICOM processing or to shut down ICOM. The name of the job or started task executing
ICOM is indicated by taskname, and the instance name for CA Workload Automation SE
is noted by xxxx. Issued by SASSICOM.

Note: If the NOWTOR DD statement in included in the CA7ICOM JCL procedure, this
WTOR is not issued.

Action:
Enter the appropriate reply for the wanted action. A MODIFY command may be used
instead of a WTOR reply.

Note: For reply formats, see the Systems Programming Guide.

962 Message Reference Guide

 CA-7.500 Through CA-7.593

CA-7.575

SMF - aaaa(bbbb),cccccccc(dddddddd) xxx

TRL - aaaa(bbbb),cccccccc(dddddddd) xxx
DDNAME={yyyyyyyy|**NONE**}

Reason:
This is the response to a D=STAT reply to the CA-7.574 WTOR. The first line provides
SMF statistics, the second line provides Trailer Step statistics, and the third line indicates
the ddname used for submit.
aaaa
Indicates current number of records chained.
bbbb
Indicates maximum number of records chained since last IPL.
cccccccc
Indicates current number of bytes used.
dddddddd
Indicates maximum number of bytes used since the last IPL.
xxx
Indicates YES or NO to indicate whether records are being collected.

Issued by SASSICM1.

Action:
None.

CA-7.576

xxxxxxxx aaaaaaaa bbbbbbbb cccccccc dddddddd

Reason:
This is the response to a D=DSECT, D=ICOM, or D=SVC reply to the CA-7.574 WTOR.
Several lines may be dumped showing the beginning of the ICOM work area ICMDSECT,
module SASSICOM, or the SVC. The address of the core is indicated by xxxxxxxx. Issued
by SASSICOM.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 963

CA-7.500 Through CA-7.593

CA-7.577

DDNAME ERROR. CANNOT SUBMIT JOB(S).

Reason:
An error occurred while attempting to use a Submit data set. The probable cause is a
missing DD statement. Issued by SASSASP, SASSHASP, SASSJES1, SASSJES2, SASSJES3.

Action:
If job submission by ICOM is necessary, stop ICOM. Add the missing DD statement for
the Submit data set to the ICOM JCL and resubmit. If the error persists, contact your
installation specialist for assistance.

CA-7.578

xxx...x SUBTASK ENDED. TCBCMP= ccc...c

Reason:
The subtask specified by xxx...x has terminated; the TCB completion code is given by
ccc...c. If ICOM was not being normally stopped, then an error has occurred. Issued by
SASSICM1.

Action:
If an abnormal subtask termination has occurred, ICOM should be canceled with a
dump. Contact your installation specialist when the dump is available.

964 Message Reference Guide

 CA-7.500 Through CA-7.593

CA-7.579

ICOM [(TRAILER)|(SUBMIT)|(SMF)] SUBTASK WAITING FOR xxxx SECONDS. CODE= y[y]

Reason:
A subtask of ICOM has been waiting for xxxx seconds for the Communications data set.
The location in the subtask module where the wait occurred is indicated by y:
■ If y=A, ICOM is trying to get control of the Communications data set to submit a job.
■ If y=B, ICOM is trying to post to the Communications data set.
■ If y=00, the Communications DSN is busy.
■ If y=04, the Communications data set is full.
■ If y=08, the NCF Communications data set is busy.

Issued by SASSJES2 and SASSJES3.

Action:
This could indicate that the Communications data set is on a high-access disk pack;
better response is provided if it is on a low-access pack. If the message persists, cancel
ICOM with a dump. When the dump is available, contact CA Support at ca.com/support
for assistance.

CA-7.580

RJP INPUT QUEUE FULL

Reason:
More input commands have been entered than there is room for in the
Communications data set. Issued by SASSICM1.

Action:
If CA Workload Automation SE is not active, this could be completely normal. Otherwise,
increase the specification on the *CDSINIT* and reinitialize the Communications data
set. (Do not reinitialize the database.)

Chapter 4: CA-7.000 - CA-7.1044 965

CA-7.500 Through CA-7.593

CA-7.581

BAD DATA. CODE= x

Reason:
The reply to the CA-7.574 WTOR was specified incorrectly. The x will indicate one of the
following:
■ A - Invalid command
■ B - Not enough data supplied
■ C - Invalid SUB command data
■ D - Invalid command

Issued by SASSICM1.

Action:
Reenter the reply to the WTOR specifying the correct data and format. See the Systems
Programming Guide for reply format.

CA-7.582

ERROR RETURN CODE= xxxx

Reason:
A return code of 4 indicates an operator attempted to delete a chain of SMF records (by
a response to ICOM's outstanding WTOR) while ICOM had the chain enqueued. Issued
by SASSICM1.

Action:
Wait a few minutes, and reenter the response.

CA-7.583

ANOTHER ICOM IS ACTIVE FOR xxxx

Reason:
Another copy of ICOM is already active on this CPU. The value of xxxx indicates the CA
Workload Automation SE instance name against which ICOM is running. In compatibility
mode, xxxx is either UC07 or UCT7. Issued by SASSICMI.

Action:
Verify that the correct version of ICOM is active.

966 Message Reference Guide

 CA-7.500 Through CA-7.593

CA-7.583

ANOTHER CA-7 IS ACTIVE FOR xxxx

Reason:
Another copy of CA Workload Automation SE is already active on this CPU. The value of
xxxx indicates the instance name. In compatibility mode, xxxx is either UC07 or UCT7.
Issued by SASSISVC.

Action:
Verify that the correct version of CA Workload Automation SE is active. If another CA
Workload Automation SE is not active, use the RNAME keyword on the SVCNO
statement of the initialization file to override UC07 or UCT7.

CA-7.584

xxxx NOT MATCHED IN ICMDSECT

Reason:
Be sure the system was initialized using CAIRIM.

If the xxxx value is ICOM, the ICMDSECT is the wrong format.

If the xxxx value is the CA Workload Automation SE instance name, either the ICMDSECT
was not found or the instance is not active. Ensure that the instance was added using
CAIRIM.

If the xxxx value is an alias name, ensure that the alias was specified with CAIRIM and
that the CA Workload Automation SE instance was made active.

Action:
Ensure that CAIRIM has initialized the CA Workload Automation SE system environment
and activated the target instance of CA Workload Automation SE.

Chapter 4: CA-7.000 - CA-7.1044 967

CA-7.500 Through CA-7.593

CA-7.585

TASKNAME: jjjjjjjj

Reason:
This message is the response to a D=EXTJOB reply to ICOM. Several lines may be listed
showing all of the entries in the current SASSEXTL table. This table is used to determine
which SMF data is to be collected for tasks submitted outside of CA Workload
Automation SE. Issued by SASSICM1.

Action:
None.

CA-7.586

XU83 TABLE ENTRY INVALID.

Reason:
This message is the response to a D=XU83 reply to ICOM when one or more entries in
the SASSXU83 table is invalid. The entry is not JOB, DD, or DSN. Issued by SASSICOM.

Action:
Verify that CAIRIM loaded the correct version of SASSXU83 table.

CA-7.589

INVALID ICOM PARM KEYWORD(S).

Reason:
One or more values specified in the ICOM execution parameters was invalid. ICOM does
not initialize.

Note: For information about valid ICOM parameters, see the Systems Programming
Guide.

Action:
Correct the parameters and restart ICOM.

968 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.590

XMONITOR= KEYWORD IGNORED: XCKPT DD NOT FOUND/DUMMIED.

Reason:
Although the XMONITOR= keyword was specified in the ICOM execution parameters,
the required Cross-Platform Tracking Checkpoint file (XCKPT DD) was not found or is a
DUMMY DD. ICOM initializes without the Cross-Platform Tracker (XTRK).

Note: For information about valid ICOM parameters, see the Systems Programming
Guide.

For information about the CA Workload Automation SE Cross-Platform Tracker, see the
Interface Reference Guide.

Action:
Correct the parameters and restart ICOM.

CA-7.592

XTRK TASK NOT ACTIVE UNDER ICOM

Reason:
Altthough an XTRK= command was issued for ICOM, the Cross-Platform Tracker (XTRK)
is not active as an ICOM subtask at this time.

Action:
None.

CA-7.601 Through CA-7.799

CA-7.601

[(LIBRARIAN)|(PANVALET)] MODULE IN USE FOR 30 SECONDS

Reason:
The interface module for CA Librarian or CA Panvalet for z/OS access has been in
continuous use for over 30 seconds. This probably means a wait or lockout condition has
developed because of access from some other activity in the host system. Issued by
SASSLIBR, SASSPANV.

Action:
Determine the cause of the delay and correct.

Chapter 4: CA-7.000 - CA-7.1044 969

CA-7.601 Through CA-7.799

CA-7.602

Agent Job Interface not active for this CA 7 execution

Reason:
The agent job interface will not be active for this CA Workload Automation SE execution
because XPDEF AGENTJOB=NO was coded or defaulted.

Note: For more information about cross-platform scheduling, see the Interface
Reference Guide.

Action:
None, unless you want to activate the agent job interface. If so, you must code XPDEF
AGENTJOB=YES in the product's initialization file and recycle CA Workload Automation
SE.

CA-7.603

Agent Job Interface active for this CA 7 execution

Reason:
The agent job interface is active for this CA Workload Automation SE execution because
XPDEF AGENTJOB=YES was coded.

Note: For more information about cross-platform scheduling, see the Interface
Reference Guide.

Action:
None.

CA-7.604

LOCAL JESNODE UNKNOWN

Reason:
During processing of the RESTART initialization file statement, an attempt to find the CA
Workload Automation SE IVT control block failed. As a result, CA Workload Automation
SE cannot determine if there is a local JESNODE for use with the CA Workload
Automation SE/CA WA Restart Option Condition Code synchronization feature. Failure
to find the CA Workload Automation SE IVT may indicate a more serious problem.

Action:
Run the environmental report (CAL2ENVR) to determine whether the IVT is initialized. If
it is not, submit CAIRIM. For assistance, contact CA Support at ca.com/support for
assistance.

970 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.610

INVALID MESSAGE ID REQUESTED

Reason:
A module requested a WTO that has not been defined.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.611

ERROR OCCURRED DURING FIRST PASS

Reason:
A logic error occurred while counting groups, lines and terminals.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.612

RESIDENT STATEMENT MUST BE FIRST

Reason:
First statement was not a RESIDENT statement.

Action:
Provide a RESIDENT statement ahead of all others.

CA-7.613

INIT STATEMENT IS REQUIRED

Reason:
An INIT statement must be provided.

Action:
Provide and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 971

CA-7.601 Through CA-7.799

CA-7.614

SVCNO STATEMENT IS REQUIRED

Reason:
An SVCNO statement must be provided.

Action:
Provide and resubmit.

CA-7.615

APPLCTN STATEMENT IS REQUIRED

Reason:
At least one APPLCTN statement must be provided.

Action:
Provide and resubmit.

CA-7.616

FMTBLK STATEMENT IS REQUIRED

Reason:
At least one FMTBLK statement must be provided.

Action:
Provide and resubmit.

CA-7.617

GROUP STATEMENT IS REQUIRED

Reason:
At least one GROUP statement must be provided.

Action:
Provide and resubmit.

972 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.618

LINE STATEMENT IS REQUIRED

Reason:
At least one LINE statement must be provided.

Action:
Provide and resubmit.

CA-7.619

SECURITY STATEMENT IS REQUIRED

Reason:
A SECURITY statement must be provided.

Action:
Provide and resubmit.

CA-7.620

FORMAT STATEMENT IS REQUIRED

Reason:
A FORMAT statement must be provided.

Action:
Provide and resubmit.

CA-7.621

DAIO STATEMENT IS REQUIRED

Reason:
A DAIO statement must be provided.

Action:
Provide and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 973

CA-7.601 Through CA-7.799

CA-7.622

UNKNOWN STATEMENT TYPE

Reason:
The statement is not a continuation of a previous statement and does not begin with a
valid statement ID.

Action:
Correct and resubmit.

CA-7.623

TERM STATEMENT IS REQUIRED

Reason:
At least one TERM statement must be provided.

Action:
Provide and resubmit.

CA-7.624

ONLY ONE OF THESE STATEMENTS ALLOWED

Reason:
Have already processed a statement of this type.

Action:
Correct and resubmit.

CA-7.625

ERROR OCCURRED WHILE SCANNING FOR A KEYWORD

Reason:
A logic error occurred looking for the next keyword.

Action:
For assistance, contact CA Support at ca.com/support.

974 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.626

INVALID OR UNKNOWN KEYWORD

Reason:
The keyword is not valid for this statement.

Action:
Correct and resubmit.

CA-7.627

Y, N, YES, NO ARE ONLY VALID VALUES

Reason:
Only the indicated values are valid.

Action:
Correct and resubmit.

CA-7.628

APPL KEYWORD IS REQUIRED / INCORRECT

Reason:
A valid APPL keyword is required to provide the ID.

Action:
Provide and resubmit.

CA-7.629

GROUP COUNT EXCEEDS FIRST PASS COUNT

Reason:
A logic error occurred while counting groups, lines and terminals.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 4: CA-7.000 - CA-7.1044 975

CA-7.601 Through CA-7.799

CA-7.630

GROUP NAME CANNOT EXCEED 7 CHARACTERS

Reason:
The name of the group must be seven characters or less.

Action:
Correct and resubmit.

CA-7.631

UNRECOGNIZED VALUE

Reason:
The value is not valid for this keyword.

Action:
Correct and resubmit.

CA-7.632

UCC7VTAM STATEMENT WAS NOT PROVIDED

Reason:
The DEVICE value indicates VTAM terminals but no UCC7VTAM statement was provided.

Action:
Correct and resubmit.

CA-7.633

NAME, LNAME, DEVICE KEYWORDS ARE REQUIRED

Reason:
The keywords must be provided.

Action:
Provide and resubmit.

976 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.634

UNKNOWN PF/PA KEY ID

Reason:
Valid PF key IDs are 01-24; PA keys are 01-03.

Action:
Correct and resubmit.

CA-7.635

VALUE MUST BE NUMERIC

Reason:
Value for this keyword must be numeric.

Action:
Correct and resubmit.

CA-7.636

VALUE MUST BE GREATER THAN ZERO

Reason:
Value must be numeric and greater than zero.

Action:
Correct and resubmit.

CA-7.637

VALUE MUST BE NO MORE THAN 255

Reason:
Value must not be greater than 255.

Action:
Correct and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 977

CA-7.601 Through CA-7.799

CA-7.638

NAME, TNAME KEYWORDS REQUIRED FOR VTAM

Reason:
These keywords are required for VTAM terminals.

Action:
Provide and resubmit.

CA-7.639

NAME, TNAME, BUFSIZE KEYWORDS REQUIRED FOR NON-VTAM

Reason:
These keywords are required for non-VTAM terminals.

Action:
Provide and resubmit.

CA-7.640

PRINTER DEVICE NOT ALLOWED AS A CONSOLE

Reason:
PRINTER=YES is not allowed with CONS=.

Action:
Correct and resubmit.

CA-7.641

YES IS ONLY VALID VALUE

Reason:
If used, must specify YES as the value.

Action:
Correct and resubmit.

978 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.642

NON-ZERO SVC RETURN CODE FOR SVC IN ICMDSECT

Reason:
The SVC number defined in ICMDSECT (the instance control block created when the
instance is added by CAIRIM) is not properly defined to MVS.

Action:
Ensure that the target instance was added by CAIRIM. Provide correct SVC number and
resubmit.

CA-7.643

VIRTUAL TERM COUNT MUST AGREE WITH LINE STATEMENT

Reason:
VTM# value in LINE statement must be used here.

Action:
Correct and resubmit.

CA-7.644

NAME, DEVICE, NLINE, LINLEN KEYWORDS REQUIRED

Reason:
The keywords are required.

Action:
Provide each and resubmit.

CA-7.645

ADRCHR KEYWORD REQUIRED FOR BTAM TYPE

Reason:
This keyword is required for BTAM terminals.

Action:
Provide and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 979

CA-7.601 Through CA-7.799

CA-7.646

INCORRECT NLGRP VALUE IGNORED

Reason:
Does not agree with number of GROUP statements.

Action:
None.

CA-7.647

INCORRECT NLINE VALUE IGNORED

Reason:
Does not agree with number of LINE statements.

Action:
None.

CA-7.648

INCORRECT NLTERM VALUE IGNORED

Reason:
Does not agree with number of nonprinter terminals.

Action:
None.

CA-7.649

INCORRECT NLPRT VALUE IGNORED

Reason:
Does not agree with number of terminals with PRINTER=YES.

Action:
None.

980 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.650

CUST ID CANNOT BE BLANK

Reason:
A value must be given for customer ID.

Action:
Provide and resubmit.

CA-7.651

CONFIG, TYPE KEYWORDS ARE REQUIRED

Reason:
These keywords are required on the INIT statement.

Action:
Provide and resubmit.

CA-7.652

SASSVC KEYWORD IS REQUIRED

Reason:
The indicated required keyword was not found.

Action:
Provide and resubmit.

CA-7.653

VALUE HAS TOO MANY CHARACTERS

Reason:
No acceptable value has this many characters.

Action:
Correct and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 981

CA-7.601 Through CA-7.799

CA-7.654

VALUE HAS TOO FEW CHARACTERS

Reason:
No acceptable value has this few characters.

Action:
Correct and resubmit.

CA-7.655

APPLCTNS MUST BE GROUPED TOGETHER

Reason:
APPLCTN statements all reside together.

Action:
Correct and resubmit.

CA-7.656

XPJOB INTERNALIZATION NOT ACTIVE FOR THIS EXECUTION OF CA-7

Reason:
This informational message is issued when the XPDEF initialization statement has the
parameter XSUBMIT=NO, which indicates that the XPJOB environment should not be
initialized.

Action:
None, if this is what you intended. If you want to set up an XPJOB environment, change
the XPDEF initialization statement to have XSUBMIT=YES and the appropriate XPDEF
parameters, and then recycle CA Workload Automation SE.

CA-7.657

NAME KEYWORD IS REQUIRED

Reason:
The indicated required keyword was not found.

Action:
Provide and resubmit.

982 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.658

STN KEYWORD MUST BE LAST KEYWORD

Reason:
No other keywords can follow the STN keyword.

Action:
Correct and resubmit.

CA-7.659

VALUE IS TOO HIGH

Reason:
The value exceeds the allowable upper limit.

Action:
Correct and resubmit.

CA-7.660

RANGE END LESS THAN START

Reason:
The ending range value cannot be lower than the starting value.

Action:
Correct and resubmit.

CA-7.661

STN KEYWORD IS REQUIRED

Reason:
The indicated required keyword was not found.

Action:
Provide and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 983

CA-7.601 Through CA-7.799

CA-7.662

STNCAL STATEMENT MUST FOLLOW STATIONS STATEMENT(S)

Reason:
STATIONS statements must occur in the initialization file before the STNCAL statement.

Action:
Resequence and resubmit.

CA-7.663

TRMID KEYWORD MUST BE FIRST

Reason:
The TRMID keyword must precede STANIDS or LTERM.

Action:
Correct and resubmit.

CA-7.664

STATION NAME ALREADY DEFINED

Reason:
Station names can only be defined once.

Action:
Correct and resubmit.

CA-7.665

PROGRAM ERROR BUILDING STATION ID LIST

Reason:
Station ID list incorrect.

Action:
Check the STANIDS list for correct names.

984 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.666

TRMID, STANIDS/LTERM KEYWORDS ARE REQUIRED

Reason:
Two keywords are required in STATIONS statements.

Action:
Provide both and resubmit.

CA-7.667

REQUIRED KEYWORD(S) MISSING

Reason:
At least one required keyword was not found.

Action:
Provide and resubmit.

CA-7.668

DDNAME NOT DEFINED IN THE JCL

Reason:
This DDNAME value does not exist in the JCL.

Action:
Correct and resubmit.

CA-7.669

DDNAME KEYWORD IS REQUIRED

Reason:
The indicated required keyword was not found.

Action:
Provide and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 985

CA-7.601 Through CA-7.799

CA-7.670

DISP KEYWORD IS REQUIRED

Reason:
The indicated required keyword was not found.

Action:
Provide and resubmit.

CA-7.671

DAIO STATEMENT MUST FOLLOW FORMAT STATEMENTS

Reason:
This statement can only reside after all FORMATs.

Action:
Correct and resubmit.

CA-7.672

Y, YES, N, NO, A, ALL ARE ONLY VALID VALUES

Reason:
This keyword will only accept the indicated values.

Action:
Correct and resubmit.

CA-7.673

DASD KEYWORD IS REQUIRED

Reason:
This required keyword was not found.

Action:
Provide and resubmit.

986 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.674

MAINID TABLE IS FULL

Reason:
The MAINID values in CPU statements have exceeded the total number allowed.

Action:
Correct and resubmit.

CA-7.675

TRM DEFINITION ERROR IN SECURITY MODULE

Reason:
An error exists in the defined TRM values in the security module.

Action:
Correct, reassemble and resubmit.

CA-7.676

DEFINED IN SECURITY MODULE BUT NO APPLCTN FOUND

Reason:
An application was defined in the security module but no APPLCTN statement was
provided.

Action:
Provide the APPLCTN statement and resubmit.

CA-7.677

APPL DIRECTORY HAS NOT BEEN BUILT

Reason:
The internal directory of applications was not built.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 4: CA-7.000 - CA-7.1044 987

CA-7.601 Through CA-7.799

CA-7.678

NO TRMSECUR POINTER IN TRMDEF

Reason:
No address found for security in a terminal block.

Action:
Contact your installation specialist.

CA-7.679

OPER ID INDEX CANNOT BE ZERO

Reason:
Operator ID must not be zero.

Action:
Correct and resubmit.

CA-7.680

OPERID/APPLID DEFINITION ERROR

Reason:
An error exists in the defined OPID/APLID values in the security module.

Action:
Correct, reassemble and resubmit.

CA-7.681

INDEX VALUE ALREADY DEFINED

Reason:
Each library must have a unique INDEX value.

Action:
Assign unique values and resubmit.

988 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.682

FOUND U7 DDS BUT PERFORM OPTION 8 WAS NOT SPECIFIED

Reason:
The PERFORM option values conflict with the DD statements found in the JCL.

Action:
Correct and resubmit.

CA-7.683

ALT LIBRARY MUST BE DEFINED FIRST

Reason:
The ALT value must reference a library that is defined in the initialization file ahead of
the reference.

Action:
Resequence the JCL statements and resubmit.

CA-7.684

LIBRARY CANNOT BE ALTERNATE FOR ITSELF

Reason:
The ALT and INDEX values cannot be the same.

Action:
Correct and resubmit.

CA-7.685

PARAMETER LIST IS INVALID

Reason:
The value indicated is either invalid or exceeds the maximum number of values allowed
in the list.

Action:
Correct the indicated value or reduce the number of values and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 989

CA-7.601 Through CA-7.799

CA-7.686

INVALID JCL LIBRARY NAME

Reason:
A JCL library name must consist of an ampersand (&) followed by up to 15 alphanumeric
characters.

Action:
Correct and resubmit.

CA-7.687

NO XPJOB TABLE FOUND WHILE PROCESSING XPDEF

Reason:
After processing the XPDEF initialization statement, there is no table containing the
values set by the statement.

Action:
Verify that no other messages regarding the XPDEF statement were issued. Since this is
a program problem, capture the output and the initialization file used and contact CA
Support at ca.com/support for assistance.

CA-7.688

PARM VALUES INCONSISTENT WITH SYMBOLIC DEFINITION

Reason:
An error was detected for a symbolic JCL library JCL statement. The following conditions
can cause this error:
■ DYN=2 was not specified.
■ DYN=2 was specified, but dynamic allocation is not enabled (see PERFORM keyword
on INIT statement).
■ DSORG=PDS was not specified or defaulted.
■ A value was specified for the MCD= keyword.

Action:
Correct and resubmit.

990 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.689

DUPLICATE ENTRY FOUND

Reason:
A duplicate GROUP name was found in the initialization file. Issued by SASSIGRP.

Action:
Either change or remove the duplicate entry.

CA-7.690

MUTUALLY EXCLUSIVE KEYWORDS FOUND

Reason:
The parameters TEST=YES and CA7=nnnn where nnnn is a CA Workload Automation SE
instance name, are mutually exclusive. Issued by SASSISVC.

Action:
Remove one of the keyword parameters.

CA-7.691

DBASE RSRC KEYWORD ERROR; VRM REQUIRED FOR XPJOB PROCESSING

Reason:
To support the XPJOB environment, the presence of the Virtual Resource Management
(VRM) VSAM file is required. This file is activated to CA Workload Automation SE
processing through the DBASE RSRC keyword.

Action:
Verify the DBASE initialization file statement has RSRC=MAINT or RSRC=YES coded.

Chapter 4: CA-7.000 - CA-7.1044 991

CA-7.601 Through CA-7.799

CA-7.693

PRINT TRACE DSNAME OR UNIT MISSING

Reason:
There is a mismatch on the XPDEF initialization statement between the keywords
PRINTDS and PRINTUNIT. If the PRINTDS contains a data set name, a management class
or DASD device type must be coded in the PRINTUNIT keyword.

Action:
Change the PRINTDS, the PRINTUNIT, or both so that a full data set allocation can be
performed to write the XPJOB trace output.

CA-7.694

SNAP TRACE DSNAME OR UNIT MISSING

Reason:
There is a mismatch on the XPDEF initialization statement between the keywords
SNAPDS and SNAPUNIT. If the SNAPDS contains a data set name, a management class or
DASD device type must be coded in the SNAPUNIT keyword.

Action:
Change the SNAPDS, the SNAPUNIT, or both so that a full data set allocation can be
performed to write the XPJOB trace output.

CA-7.695

XPJOB PASSWORD LOCATION CODES OWNER BEFORE DATABASE

Reason:
On the XPDEF statement, the PSWDLOC parameter has OWNER coded before
DATABASE, which means that the owner field is always used instead of the CA Workload
Automation SE database information. Because the OWNER field implies that no
passwords are sent to the target destination, this may not be the intended order of the
PSWDLOC options.

Action:
This is issued as an informational message only, but action may be necessary if you do
not intend to use the OWNER field as the primary source of the XPJOB user ID.

992 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.696

NO CCI MONITOR NAME PROVIDED ON SVCNO STMT

Reason:
To support the XPJOB environment, CAICCI communications are required. These
communications require a monitor name for the CA-7 instance through which CA
Workload Automation SE will connect to CAICCI. The SVCNO initialization statement has
MONITOR=NO coded.

Note: This name is used to connect to the CAICCI communications facility.

Action:
Change the SVCNO MONITOR keyword from NO to YES or to contain some specific name
coded.

CA-7.697

XPDEF statement present. All XPS SVCNO values have been reset.

Reason:
Because CA Workload Automation SE encountered an XPDEF statement that defines the
cross-platform environment, any cross-platform values coded on the SVCNO statement
have been overridden by the specifications on the XPDEF statement. If no parameters
for the monitor, server, or router were coded, the defaults are used.

Action:
None required, but to eliminate this message, update the CA Workload Automation SE
Online Initialization File to move the cross-platform keywords to the XPDEF statement,
and remove them from the SVCNO statement.

CA-7.699

EXTERNAL SECURITY INTERFACE INSTALLED

Reason:
The SECURITY statement of the initialization file contained the EXTERNAL keyword.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 993

CA-7.601 Through CA-7.799

CA-7.699

INTERNAL SECURITY BEING USED

Reason:
All security access will be handled by CA Workload Automation SE internal security.

Action:
None.

CA-7.699

NO DEFAULT ID SUPPLIED FOR XPS

Reason:
No default user ID was supplied for the SECURITY statement keyword XPSSID. All XPS
scheduling requests must include a valid user ID.

Action:
This is a warning message. Because no user ID was coded on the XPSSID keyword, CA
Workload Automation SE will be unable to honor cross-platform scheduling requests
that do not contain a user ID.
We recommend that you supply a user ID as the value of the XPSSID keyword on the
SECURITY statement. This user ID will be used for any cross-platform scheduling request
that does not contain a user ID.

CA-7.700

I/O ERROR DURING WRITE OF TRACK TABLE - U0700

Reason:
An I/O error has occurred while writing to the track allocator table for the output queue.
Issued by SASSHALT, SASSQMG, SASSQMGO, SASSQMGQ.

Action:
Contact your installation specialist for assistance.

994 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.701

MAIN STORAGE REQUEST ERROR FROM SASSQMG - U0701

Reason:
An invalid return code was received from a request for core. Issued by SASSQMG.

Action:
Contact your installation specialist for assistance.

CA-7.702

QUEUE MANAGER PAGE OUT ERROR - U0702

Reason:
An output page was found to contain less than four bytes of data. Issued by SASSQMG.

Action:
Contact your installation specialist for assistance.

CA-7.710

I/O ERROR IN xxx QUEUE.

Reason:
An I/O error was encountered while attempting to read or write the queue data set
identified by xxx. Issued by SASSDAIO.

Action:
If the error is in the Trailer queue, message CA-7.INW3 is also sometimes issued at the
OS console. This message indicates a bad pointer in the queue. See the required action
for CA-7.INW3. Contact your installation specialist for assistance, especially when IBM
error messages indicating chaining checks accompany the error.

If xxx is DQT, the user could have issued a generic type list or forecast command that
caused over 255 pages of output. If this amount of output is the situation, run this using
the Batch Terminal Interface.

If the queues are moved to a different device type, verify the following:
■ The DEVICE parameter on the DAIO statement reflects the device change.
■ All queues and the Checkpoint data set are on the same device type.

Chapter 4: CA-7.000 - CA-7.1044 995

CA-7.601 Through CA-7.799

CA-7.711

IOB FOR COMPLETED ECB NOT FOUND - U0711

Reason:
A search for an I/O block for a completed I/O activity has failed. Issued by SASSDAIO.

Action:
Contact your installation specialist for assistance.

CA-7.714

WRITE ERROR nn hh

Reason:
An error has been detected writing to a batch terminal. The nn indicates the return code
from the write macro, and the hh indicates the CSW status from the job. Issued by
SASSFBAT.

Action:
This condition can occur if the batch terminal output data set is too small. To see if this
is the case, review the SYSPRINT messages in the batch terminal job. If the data set is
too small, reallocate the data set and rerun the job. If the size of the batch terminal
output data set appears to be sufficient or other errors are indicated, contact your
installation specialist for assistance.

CA-7.729

CA 11 INTERFACE DISABLED, CANNOT ACCESS RMS MODULES

Reason:
CA WA Restart Option modules used by the CA Workload Automation SE/CA WA Restart
Option interface were not found. CA Workload Automation SE submits jobs without
inserting the CA WA Restart Option RMS step. The cancel and restart functions do not
attempt to interface with CA WA Restart Option. This is similar to coding RMS=NO on
the RESTART file initialization statement.

Action:
Ensure the CA WA Restart Option load library is in the link list, or part of the CA
Workload Automation SE STEPLIB concatenation.

996 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.730

CA-11 INACTIVE, DO YOU WANT JOBS SUBMITTED? (YES/NO/NO11)

Reason:
This WTOR is issued under these conditions:
■ The RESTART statement is present in the initialization file.
■ RMS=NO is not specified on the RESTART statement.
■ CA WA Restart Option is not active when CA Workload Automation SE is started.
■ CA WA Restart Option terminates while CA Workload Automation SE is active. In
this case the WTOR is not issued until the next time CA Workload Automation SE
attempts to communicate with CA WA Restart Option (for example XRST or
CANCEL).
■ CA WA Restart Option is using [set the dad variable for your book], and the
Multi-User Facility is down.

All CA Workload Automation SE processing is suspended until a response is received.

Action:
Issue the appropriate response to the WTOR. If the reply is YES, CA Workload
Automation SE will submit jobs and attempt to use the CA WA Restart Option interface
as if CA WA Restart Option were active. Jobs that are defined with INSERT-RMS=Y will
have the CA WA Restart Option RMS step inserted when submitted. If the reply is NO,
any jobs that are defined with INSERT-RMS=Y will not be submitted (will remain in the
Ready queue) when their requirement count becomes zero. The restart functions of CA
Workload Automation SE will still attempt to interface with CA WA Restart Option.

If the reply is NO11, all jobs will be submitted without an inserted CA WA Restart Option
RMS step. The restart functions will not attempt to interface with CA WA Restart
Option. To activate the interface (after CA WA Restart Option is active), the SUBMIT
command must be issued.

If CA WA Restart Option is started after responding to the WTOR, the interface may be
activated by issuing the SUBMIT command or by canceling or restarting a job.

Chapter 4: CA-7.000 - CA-7.1044 997

CA-7.601 Through CA-7.799

CA-7.731

CA-7 WILL SUBMIT JOBS WITH THE CA-11 STEP.

Reason:
The reply to the CA-7.730 WTOR was YES. After CA Workload Automation SE completes
initialization, jobs are submitted as if the CA WA Restart Option interface is active.

Action:
If CA WA Restart Option is started after responding to the WTOR, activate the interface
by issuing the SUBMIT command or by canceling or restarting a job.

CA-7.732

CA-7 WILL NOT SUBMIT CA-11 JOBS.

Reason:
The reply to the CA-7.730 WTOR was NO. CA Workload Automation SE will not submit
any jobs that are defined as INSERT-RMS=Y. These jobs will remain in the Ready queue
until the interface is available or the job is changed to not require the RMS step.

Action:
If CA WA Restart Option is started after responding to the WTOR, the interface may be
activated by issuing the SUBMIT command or by canceling or restarting a job.

CA-7.733

CA-7 WILL STOP SUBMITTING CA-11 JOBS.

Reason:
The reply to the CA-7.730 WTOR was NO. CA Workload Automation SE stops submitting
any jobs that are defined as INSERT-RMS=Y. These jobs remain in the ready queue until
the interface is available or the job is changed to not require the RMS step.

Action:
If CA WA Restart Option is started after responding to the WTOR, the interface can be
activated by issuing the SUBMIT command or by canceling or restarting a job.

998 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.734

CA-11 PROCEDURE NAME BLANK IN CA-11 OPTIONS TABLE.

Reason:
CA WA Restart Option was not fully initialized when CA Workload Automation SE was
started so the CA WA Restart Option options table did not have the RMS procedure
name filled in. Also, the PROCRMS keyword was not specified on the RESTART
statement in the initialization file.

Action:
Respond to the WTOR that follows. Only NO or NO11 will be accepted. If the PROCRMS
keyword was specified on the RESTART statement, this message would not be issued.

CA-7.735

INVALID REPLY, MUST BE "YES", "NO", OR "NO11".

Reason:
An invalid reply was made to the CA-7.730 WTOR.

Action:
The CA-7.730 WTOR is reissued, prompting for a valid reply.

CA-7.736

THE CA-11 INTERFACE IS NOW ACTIVE.

Reason:
The CA Workload Automation SE interface with CA WA Restart Option was not active
prior to this message but has now been activated. The interface can be activated by
issuing the SUBMIT command or, if the previous WTOR reply was YES or NO, by
canceling or restarting a job.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 999

CA-7.601 Through CA-7.799

CA-7.737

THE CA-11 INTERFACE HAS BEEN DEACTIVATED.

Reason:
The reply to the CA-7.730 WTOR was NO11. CA Workload Automation SE will submit
jobs without inserting the CA WA Restart Option RMS step. The cancel and restart
functions will not attempt to interface with CA WA Restart Option. This has the same
effect as coding RMS=NO on the RESTART statement in the initialization file.

Action:
If CA WA Restart Option is started after responding to the WTOR, the interface may be
activated by issuing the SUBMIT command.

CA-7.738

WARNING! RESTART CONDCHK=YES SPECIFIED WITH RMS=NO.

Reason:
RMS=NO is specified on the RESTART initialization statement. CONDCHK=YES is invalid
and is ignored. CA Workload Automation SE continues to initialize.

Action:
None.

CA-7.740

CA-7 DORMANT START. REPLY "YES" TO TAKE OVER OR "STOP" TO END.

Reason:
TYPE=DORM.

Action:
None is required. To manually cause the dormant copy of CA Workload Automation SE
to complete initialization, reply YES. To terminate the dormant CA Workload
Automation SE with a U0777 abend, reply STOP.

1000 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.741

INVALID WTOR REPLY

Reason:
This WTO is issued by SASSLINK when an invalid reply is entered for the CA-7.740 or
CA-7.743 WTOR. The original WTOR is reissued.

Action:
Issue a valid reply for the reissued WTOR.

CA-7.742

CAN NOT INITIALIZE, ENQ HELD BY OTHER TASK

Reason:
A reply of YES was issued to the CA-7.740 WTOR but another CA-7 task is already
holding the ENQ. The dormant copy cannot complete initialization without obtaining the
ENQ. Issued by SASSLINK.

Action:
Determine whether another CA Workload Automation SE is running that already has the
same ENQ issued as the dormant CA Workload Automation SE. If the dormant CA
Workload Automation SE is supposed to take over, shut down the other CA Workload
Automation SE task.

CA-7.743

MAIN CA-7 INACTIVE - DORM WILL TAKE OVER UNLESS "STOP" REPLY.

Reason:
The dormant copy of CA Workload Automation SE determined that the main copy is not
active. This WTOR indicates that the dormant copy will take over for the main copy
unless a reply of STOP is received within a specified number of seconds. This WTOR is
issued by SASSLINK.

Action:
None required. If you do not want the dormant copy of CA Workload Automation SE to
take over, reply STOP and it will terminate with a U0777 abend.

Chapter 4: CA-7.000 - CA-7.1044 1001

CA-7.601 Through CA-7.799

CA-7.744

RESUME INITIALIZATION PROCESS

Reason:
The dormant copy of CA Workload Automation SE determined that the main copy is not
active. This WTO indicates that the dormant copy is going to complete initialization and
take over the CA Workload Automation SE functions for the main CA Workload
Automation SE. Issued by SASSLINK.

Action:
None.

1002 Message Reference Guide

 CA-7.601 Through CA-7.799

CA-7.750

SASSLOGM - LOGGING ERROR x

Reason:
The following shows the values of x:
1
An error condition was encountered in the SLOG macro.
2
An invalid request has been issued for the SLOG macro.
3
An active buffer could not be found for the Log data set. Most likely the buffer
status area of memory has been overlaid.
4
An I/O error was encountered on the Log data set.

Issued by SASSLOGM.

Action:
When x equals:
1
Contact your installation specialist for assistance.
2
Contact your installation specialist for assistance.
3
Cancel CA Workload Automation SE with a dump and then use the emergency
restart (TYPE=ERST) procedure to reinitialize CA Workload Automation SE. Contact
your installation specialist when the dump is available.
4
CA Workload Automation SE abends with a U0750. If the I/O error is permanent, it
is necessary to move the Log data set. When the error has been corrected, CA
Workload Automation SE should be reinitialized using the emergency restart
(TYPE=ERST) procedure.

Chapter 4: CA-7.000 - CA-7.1044 1003

CA-7.800 Through CA-7.890

CA-7.777

REPLY WAS STOP, NOW TERMINATING

Reason:
A response of STOP was issued to the CA-7.740 or CA-7.743 WTOR. CA Workload
Automation SE terminates with a U0777 abend. Issued by SASSLINK.

Action:
None.

CA-7.799

SVC DUMP BEING PRODUCED.

Reason:
A CSA storage overlay was detected. An external source has overlaid a chain that CA
Workload Automation SE uses. To assist in determining the cause of the overlay, CA
Workload Automation SE is scheduling an SVC dump. This dump only occurs the first
time an overlay is detected after the CA Workload Automation SE CAIRIM initialization.
The SVC dump title is CA Workload Automation SE CSA INFO.

The CA-7.SVC3 or CA-7.SVC4 WTO follows this WTO and indicates the CA Workload
Automation SE data that might have been lost.

Action:
Examine the SVC dump to try to determine the cause of the storage overlay.

CA-7.800 Through CA-7.890

CA-7.800

MONITOR HAS TIMED OUT

Reason:
While running ARTS or TIQ under CA Workload Automation SE, the session timed out
after the number of minutes specified on the MONLIM parameter on the TERM
statement in the initialization file (the default is two minutes). This will only occur if the
session is inactive for this amount of time.

Action:
No action is required unless the limit is too small for the particular terminal. If the limit
is too small, then either add a MONLIM parameter to the TERM statement or increase
the present value.

1004 Message Reference Guide

 CA-7.800 Through CA-7.890

CA-7.820

UNRECOVERED ERROR ON (xxxxxxx)

Reason:
An unrecoverable I/O error has occurred on the terminal specified by xxxxxxx. No abend
will occur; output for the terminal will be queued in the output queue. Issued by
SASSLMGR.

Action:
Verify that terminal name is defined in the initialization file. Terminal and line should be
checked out and restarted by someone responsible for TP network maintenance.

CA-7.821

UNKNOWN ERROR ON (xxxxxxx)

Reason:
An I/O has completed for a terminal that cannot be found in the CA Workload
Automation SE control blocks. No abend occurs. Issued by SASSLMGR.

Action:
Contact your installation specialist for assistance.

CA-7.822

(xxxxxxx) CLOSED

Reason:
If the message is for a batch terminal, then the batch terminal has completed processing
of the batch input data. This message is for information only. Otherwise, the error limit
for the specified terminal has been reached and the terminal has been stopped. Issued
by SASSCHDS, SASSLMGR.

Action:
Terminal should be checked, restarted, or both by someone responsible for TP network
maintenance.

Chapter 4: CA-7.000 - CA-7.1044 1005

CA-7.800 Through CA-7.890

CA-7.823

LINE (xxxxxxx) CLOSED

Reason:
The error limit for the line specified by xxxxxxx has been reached and the line has been
stopped. Issued by SASSLMGR.

Action:
Line should be checked out, restarted, or both by someone responsible for TP network
maintenance.

CA-7.824

INT REQ LINE= xxxxxxx TERM= xxxxxxxx [S/S= xxxx | VTAM NODE=yyyyyyyy]

Reason:
Intervention is required on the specified line, terminal, or both. Either the status sense
(S/S) or the VTAM NODE name is given. Issued by SASSI32R, SASSI32V.

Action:
Someone responsible for TP network maintenance should check line and terminal, take
required action, or both.

CA-7.851

RJP TERMINAL NOT DEFINED

Reason:
The RJP or MCS terminal that entered the command is not defined or is incorrectly
defined in the initialization file. Issued by SASSIRJP.

Action:
Verify that the initialization file is correct.

1006 Message Reference Guide

 CA-7.800 Through CA-7.890

CA-7.852

RJP TERMINAL HAS BEEN CLOSED

Reason:
The CA Workload Automation SE Master Terminal Operator (MTO) has stopped this
RJP/MCS terminal. Issued by SASSIRJP.

Action:
Start the terminal to continue processing.

CA-7.853

REQUEST IGNORED -- INPUT PENDING

Reason:
A second command has been entered before the first command completed. Issued by
SASSIRJP.

Action:
Reenter the command after the response to the original input has been received.

CA-7.860

I/O ERROR ON RJP OUTPUT

Reason:
An I/O error was encountered in accessing the Communications data set. Issued by
SASSRWTR.

Action:
Contact your installation specialist for assistance.

CA-7.861

I/O ERROR ON RJP INPUT

Reason:
An I/O error has been encountered in accessing the Communications data set. Issued by
SASSRRDR.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1007

CA-7.800 Through CA-7.890

CA-7.871

RJP LINE NOT DEFINED

Reason:
This CPU has not been defined as a line in the initialization file. Issued by SASSRRDR.

Action:
Verify that the initialization file is correct.

CA-7.872

RJP LINE HAS BEEN CLOSED

Reason:
The CA Workload Automation SE Master Terminal Operator (MTO) has stopped the line
for this CPU. Issued by SASSRRDR.

Action:
Start the line to continue processing.

CA-7.873

RJP LINE IS BUSY

Reason:
A unique timing situation has caused the line to appear busy. Issued by SASSRRDR.

Action:
Reenter your command. If the problem persists, contact your installation specialist for
assistance.

CA-7.890

NUMBER OF QUEUE IOBS SET TO nnn

Reason:
The number of IOBS is set to nnn. The nnn comes from the IOBS value on the DAIO
statement. This value is automatically changed if the specified value is less than 5, or if
PSP=Y is used, the value is set to be at least the value of MAXSUBOUT plus 5.

Action:
None.

1008 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.900 Through CA-7.999

CA-7.900

BLDL FAILED FOR MODULE NAME xxxxxxxx - U0900

Reason:
Module name xxxxxxxx is not on the CA Workload Automation SE load library or an I/O
error has occurred. This is a warning message if no dump is produced. Issued by
SASSLINK.

Action:
If a U0900 abend is produced, contact your installation specialist for assistance.
Otherwise, no action is required.

CA-7.901

INVALID APPLCTN, FMTBLK OR CALBLK LOAD MODULE OF xxxxxxxx

Reason:
The load module xxxxxxxx specified in either an APPLCTN, FMTBLK or CALBLK NAME
parameter is invalid or does not exist on CA Workload Automation SE load library.
Issued by SASSIFCA.

Action:
Verify that the name specified exists on CA Workload Automation SE load library. If the
module exists, check the assembly listing for a valid assembly and link edit. The last
statement assembled must specify ATTR=LAST.

CA-7.902

INVALID REPLY xxxx

Reason:
The reply xxxx provided to WTOR CA-7.905 did not match the valid replies of OK or a
valid CA Workload Automation SE startup option.

Action:
When the WTOR CA-7.905 is reissued, enter a valid reply. See Message CA-7.905.

Chapter 4: CA-7.000 - CA-7.1044 1009

CA-7.900 Through CA-7.999

CA-7.904

SASSQM51 MISSING OR IN ERROR, RESTART INTERFACE TO CA-11 DISABLED

Reason:
During initialization of the interface with CA WA Restart Option, the module SASSQM51,
which performs restart and cancel interfacing, either was not found or the wrong
version of the interface was indicated. Issued by SASSIRST.

Action:
If the interface with CA WA Restart Option (for restarts) is wanted, assemble and link
edit module SASSQM51. Be sure the CA WA Restart Option macro library precedes the
CA Workload Automation SE macro library in the assembly step. The module must be
linked into a load library included in the STEPLIB concatenation for CA Workload
Automation SE.

CA-7.905

VERIFY TYPE=xxxx START-UP OPTION.

REPLY 'OK' OR NEW OPTION

Reason:
A cold type of start option is being attempted for CA Workload Automation SE (COLD,
FORM, MOVQ). The operator must reply to let CA Workload Automation SE initialize. If
TYPE=Z is displayed, an invalid reply was provided in the previous WTOR answer; see the
valid replies that follow in the Action. Issued by SASSINIT.

Action:
Consider the following actions:
■ A reply of OK lets CA Workload Automation SE initialize with the startup option
printed in the message.
■ A reply of WARM or ERST causes CA Workload Automation SE to initialize with that
particular option.
■ A reply of COLD, FORM, or MOVQ causes the reissuing of this WTOR.
■ Any other reply also causes the reissuing of this WTOR.

1010 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.906

LOAD FAILED FOR MODULE xxxxxxxx

Reason:
An attempt to load module xxxxxxxx failed. Either the module does not exist on the CA
Workload Automation SE load library or there is a program problem. Issued by SASSISEC.
CA Workload Automation SE terminates with a U0414 abend.

Action:
Make sure the module exists on the CA Workload Automation SE load library. If the load
failed on a USERID module, verify that the SECURITY statement in the initialization file
has a USER parameter. Check that the last USERID macro has LAST=YES coded. If the
load failed on the SECURITY module, verify that the NAME parameter on the SECURITY
statement points to the correct member on the load library.

If module xxxxxxxx is not a security module, verify that the module is defined to CA
Workload Automation SE by an APPLCTN statement in the initialization file or in the
SASSPROG module.

CA-7.907

INITIALIZATION REQUIRES MORE STORAGE

Reason:
Region size is too small.

Action:
Increase REGION size in CA Workload Automation SE JCL and resubmit.

CA-7.908

SECURITY MODULE FORMAT ERROR, REASSEMBLE

Reason:
Format of security module is invalid. Internal controls for the operator IDs are in error.

Action:
Correct and reassemble the security module in error or use another security module. If
the problem persists, contact your installation specialist.

Chapter 4: CA-7.000 - CA-7.1044 1011

CA-7.900 Through CA-7.999

CA-7.909

INITIALIZATION REQUIRES MORE CORE TO LOAD RESIDENT MODULES - U0909

Reason:
Core required to load CA Workload Automation SE resident modules is not available.
Issued by SASSLDDL.

Action:
Increase REGION size in CA Workload Automation SE JCL and resubmit the job.

CA-7.910

ILLEGAL CARD OR SEQ. ERROR IN INIT DECK

Reason:
An invalid statement or a sequence error has been found in the product's initialization
file. The statement in error will be listed following the message. Issued by SASSICRD.

Action:
Review the initialization file documentation and make all necessary changes.

CA-7.910

MASTER LTERM SPECIFICATION OMITTED

Reason:
One terminal must be defined as MASTER.

Action:
Define and resubmit.

CA-7.910

CUST,ID= STATEMENT IS REQUIRED

Reason:
A CUST statement with an ID parameter is required.

Action:
Provide the statement and resubmit.

1012 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.911

VTNAME SPECIFIED BUT NOT USED

Reason:
A UCC7VTAM statement was provided, but no terminals were defined to use VTAM.

Action:
Correct and resubmit.

CA-7.912

DDNAME UCC7IN FAILED OPEN

Reason:
An error occurred trying to open the UCC7IN data set.

Action:
Probable DD statement error. Correct and resubmit.

CA-7.912

DDNAME UCC7OUT FAILED OPEN

Reason:
An error occurred trying to open the UCC7OUT data set.

Action:
Probable DD statement error. Correct and resubmit.

CA-7.913

NETWORK TYPE CONFLICTS WITH GROUP STATEMENT

Reason:
The type of terminals defined in a GROUP statement disagrees with the NETWORK value
in the RESIDENT statement.

Action:
Correct and resubmit.

Chapter 4: CA-7.000 - CA-7.1044 1013

CA-7.900 Through CA-7.999

CA-7.914

GROUP COUNT CONFLICTS WITH RESIDENT NLGRP VALUE

Reason:
A logic error has occurred with GROUP statement processing.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.914

LINE COUNT CONFLICTS WITH RESIDENT NLINE VALUE

Reason:
A logic error has occurred with LINE statement processing.

Action:
For assistance, contact CA Support at ca.com/support.

CA-7.914

LOCATE FAILED FOR JCL DATA SET x...x

Reason:
The data set name specified in the JCL statement in the product's initialization file is not
cataloged, and no VOLSER parameter was given. Issued by SASSINWC.

Action:
Catalog the JCL data set or provide a VOLSER parameter.

CA-7.914

TERM COUNT CONFLICTS WITH RESIDENT NLTERM, NLPRT SUM

Reason:
A logic error has occurred with TERM statement processing.

Action:
For assistance, contact CA Support at ca.com/support.

1014 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.915

RDJFCB FAILED FOR JCL DATASET ON VOL xxxxxx

Reason:
The volume indicated by xxxxxx is not defined with a DD statement in the CA Workload
Automation SE execution JCL. This prevented CA Workload Automation SE from
accessing a JCL data set on that volume. Issued by SASSINWC.

Action:
Add a DD statement to the CA Workload Automation SE JCL defining the volume. It will
be necessary to reinitialize CA Workload Automation SE before the volume will be
accessible.

CA-7.916

DSN x...x NOT ON VOL volume

Reason:
The format-1 label for the JCL data set indicated by x...x could not be found on the
volume indicated. Issued by SASSINWC.

Action:
Verify the system catalog entry and the VOLSER specified to CA Workload Automation
SE. Make any necessary corrections.

CA-7.917

JCL DATASET(S) INVALID

Reason:
Errors were detected in the JCL statements in the initialization file. Issued by SASSINWC.

Action:
Correct the errors and resubmit the CA 7 WA job.

Chapter 4: CA-7.000 - CA-7.1044 1015

CA-7.900 Through CA-7.999

CA-7.918

TERMINAL - xxxxxxx HAS NO LTERM DESIGNATED.

Reason:
A TERM statement was found in the initialization file without a corresponding LTERM
designated in the STATIONS statement. Issued by SASSINTP. CA Workload Automation
SE will abend with a U0918 code following this message.

Action:
Verify that there is a STATIONS statement in the initialization file for the TERM xxxxxx,
check that all STANIDS are unique, and that continuation statements are coded
properly. See the Systems Programming Guide for the correct coding.

CA-7.919

TERMINAL - xxxxxxx HAS NO OPERATOR ID DESIGNATED.

Reason:
A TERM statement for a terminal that can receive input was found in the initialization
file without a corresponding operator from the module identified by the SECURITY
statement. Issued by SASSINTP.

Action:
Specify at least one operator as valid to use each terminal defined for input.

Note: For more information about the SECURITY macro definition, see the Systems
Programming Guide.

CA-7.920

I/O ERROR FORMATTING xxxxxxxx

Reason:
An error occurred while formatting the queue identified by xxxxxxxx. Issued by
SASSINIO.

Action:
Have dump and system log available. For assistance, contact CA Support at
ca.com/support.

1016 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.921

DEVICE NOT SUPPORTED - U0921

Reason:
The DAIO statement in the product's initialization file has an invalid device specification.
Issued by SASSINIO.

Action:
Specify a correct device type and resubmit. See the Systems Programming Guide for
valid device types.

CA-7.922

INITIALIZATION REQUIRES MORE CORE - U0922

Reason:
Core allocated for CA Workload Automation SE has been exceeded by initialization.
Issued by SASSINIO.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

CA-7.923

INVALID SCT - SASSDAIO NOT FOUND - U0923

Reason:
The SCT control block for SASSDAIO could not be found. Issued by SASSINIO.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1017

CA-7.900 Through CA-7.999

CA-7.924

QUEUE FORMAT INCORRECT - xxxxxxxx - U0924

Reason:
The queue specified by xxxxxxxx is not in the format expected by CA Workload
Automation SE. The data on the pack on which the queue resides may have been
compressed, or the queue may have been moved. Another symptom may be that CA
Workload Automation SE abended with a U0710 earlier, indicating an I/O error in the
queue. Issued by SASSINW3.

Action:
If any of the queues have been moved, a FORM start will be required. If not, a COLD
start may resolve the problem. If unable to initialize CA Workload Automation SE with a
COLD start, formatting of the queues affected will be necessary. See the Systems
Programming Guide on recovery aids that may be used to help to rebuild the queues.

CA-7.925

LOG DATASET AREAS INITIALIZED

Reason:
The buffers and control blocks for the Log data sets have been initialized. Issued by
SASSINLG.

Action:
None.

CA-7.925

QUEUE xxxxxxxx NOT DEFINED IN INIT DECK - U0925

Reason:
The name of the queue file not defined in the CA Workload Automation SE initialization
file is indicated by xxxxxxxx. Issued by SASSINW3.

Action:
Check the FORMAT statements in the initialization file, make any necessary corrections,
and then resubmit the CA 7 WA job.

1018 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.926

I/O ERROR OR UNEXPECTED EOD ON QUEUE xxxxxxxx - U0926

Reason:
The name of the queue where an I/O error or unexpected end-of-data (EOD) was
encountered is indicated by xxxxxxxx. Issued by SASSINW3.

Action:
Contact your installation specialist for assistance.

CA-7.926

NO CORE FOR LOG DCB AND BUFFERS

Reason:
Insufficient core was available for initialization of the Log data set work areas. Issued by
SASSINLG.

Action:
Increase the REGION size (in the CA Workload Automation SE JCL) and resubmit the job
to initialize CA Workload Automation SE.

CA-7.927

LOG NOT ACTIVE

Reason:
The ALOG1/ALOG2 statements were omitted from the initialization file. No logging will
occur. Issued by SASSINLG.

Action:
If logging is wanted, CA Workload Automation SE must be shut down, the
ALOG1/ALOG2 statements added to the initialization file, and then CA Workload
Automation SE brought back up.

Chapter 4: CA-7.000 - CA-7.1044 1019

CA-7.900 Through CA-7.999

CA-7.927

UNABLE TO INVERSE PURGE TRACK CELL - U0927

Reason:
A problem was encountered in trying to reconstruct the queues during a WARM or ERST
start. Normally, this will be due to a queue file having been moved prior to the
attempted initialization. Issued by SASSINW3.

Action:
If the error occurred during a WARM start, then try ERST. If the error is in the Scratch
queue or Disk Queue Table queue, then ERST should resolve the problem. If ERST does
not work, contact your installation specialist for assistance. See CA-7.INW3.

CA-7.928

LOG DATASET [(CLOSED)|(OPENED)]

Reason:
A Log data set has been successfully opened or closed. This occurs when the logs are
swapped, at online startup, and at CA Workload Automation SE shutdown time. Issued
by SASSBTMG.

Action:
None.

CA-7.928

xxxxxxxx HAS nnnnnn AVAILABLE TRACKS, REQUIRED STORAGE=ssssss

Reason:
The queue file indicated by xxxxxxxx has nnnnnn number of available tracks and its
in-memory table requires storage of ssssss as indicated in the message text. If the queue
is not located in storage, the ssssss can reflect zeros. This informational message is
issued for WARM starts and emergency restarts (ERSTs). Issued by SASSINW3.

Action:
None.

1020 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.929

SASSINW3 REQUIRES MORE CORE FOR INITIALIZATION - U0929

Reason:
More core is required by the initialization module SASSINW3. Issued by SASSINW3.

Action:
Increase the REGION size in the CA Workload Automation SE execution JCL and resubmit
the job.

CA-7.930

TERMINAL CONTROL BLOCK INVALID - U0930

Reason:
Invalid information was specified on a TERM statement in the product's initialization file.
If remote BTAM terminals (3270R) are being used, the LINE statement in the
initialization file probably contains an error. Issued by SASSINTP.

For 3270Rs, all terminal names with the same control unit addresses (first two bytes of
ADRCHR) must be contiguous in the TNAME parameter of the LINE statement.

Action:
Correct the error and resubmit.

CA-7.931

BLDL FAILED FOR MODULE NAME xxxxxxxx - U0931

Reason:
The module specified by xxxxxxxx is not on the CA Workload Automation SE load library
or an I/O error has occurred. Issued by SASSINTP.

Action:
Verify that the module was not inadvertently deleted from the load library. If present,
contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1021

CA-7.900 Through CA-7.999

CA-7.932

INITIALIZATION REQUIRES MORE CORE - U0932

Reason:
The core allocated for initialization has been exceeded. Issued by SASSINTP.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

CA-7.933

NO SCRATCH QUEUE SPACE....ALL MESSAGES PURGED

Reason:
CA Workload Automation SE may have previously abended with all the Scratch queue
space allocated (usually a U0305 abend). All purged Scratch queue space is released, all
messages are queued and scratch work areas (active areas) are allocated at the time CA
Workload Automation SE came down last. This message is also issued when a
TYPE=ERST is done. Issued by SASSINW3.

Action:
None.

CA-7.934

UNRECOVERABLE ERROR DURING QUEUE UNLOAD

Reason:
An unrecoverable error was detected while attempting to unload the CA Workload
Automation SE queue files. This message will cause a U0934 abend. Issued by
SASSINQD.

Action:
A WTO of INQD-xx is issued. See that message for the required action. Do not attempt
to start CA Workload Automation SE with a MOVQ startup. CA Workload Automation SE
can be started with a TYPE=WARM or ERST.

1022 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.935

UNRECOVERABLE ERROR DURING QUEUE RELOAD.

Reason:
An unrecoverable error was found during the CA Workload Automation SE queue reload
function. This message causes a U0935 abend. Issued by SASSINQB.

Action:
Contact your installation specialist for assistance.

CA-7.936

QUEUES SUCCESSFULLY RELOADED.

Reason:
The CA Workload Automation SE queues are successfully reloaded. Issued by SASSINQB.

Action:
None.

CA-7.937

CA-7 QUEUES SUCCESSFULLY UNLOADED

Reason:
The CA Workload Automation SE queues were successfully unloaded. Issued by
SASSINQD.

Action:
None.

CA-7.938

VRM ACTIVE RESOURCE RECORDS RELOADED.

Reason:
The VRM active resource records found on the CA7VDMP dump queue file were
successfully reloaded.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1023

CA-7.900 Through CA-7.999

CA-7.939

NO xxx ACTIVE RESOURCE RECORDS RELOADED

Reason:
CA Workload Automation SE produces this message when ARF or VRM (indicated by the
xxx) records are being reloaded during a MOVQ operation. This message indicates no
such records were found in the input data to be reloaded.

Action:
None.

CA-7.940

ARF ACTIVE RESOURCE RECORDS RELOADED

Reason:
The ARF active resource records found on the CA7VDMP dump queue file were
successfully reloaded.

Action:
None.

CA-7.940

INITIALIZATION REQUIRES MORE CORE - U0940

Reason:
The core allocated for initialization has been exceeded. Issued by SASSINWC.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

1024 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.941

HIJBNUM CANNOT BE CHANGED

Reason:
An attempt was made to change the highest allowable CA Workload Automation SE job
number (defined by the HIJBNUM parameter of the initialization file SCHEDULE
statement) during a WARM start or emergency restart (ERST). This change is not valid
except during cold type starts. COLD, MOVQ or FORM. Issued by SASSINW2.

Action:
Reset HIJBNUM back to the original value or do a cold type start.

CA-7.942

NUMBER OF STATIONS CANNOT BE CHANGED

Reason:
An attempt was made to change the number of stations or logical terminal names prior
to initializing CA Workload Automation SE with a WARM start. STATION statement
changes require an ERST start of CA Workload Automation SE. Issued by SASSINW2.

Action:
If STATION statement changes are required, an ERST or COLD start initialization of CA
Workload Automation SE is necessary.

CA-7.943

ERROR READING NAT CHECKPOINT RECORD

Reason:
The Checkpoint record for the CA Workload Automation SE Job Number Allocator Table
could not be read during initialization. Issued by SASSINW2.

Action:
A COLD start initialization of CA Workload Automation SE must be done. If the
Checkpoint data set has been moved, it must be on the same device type with the
queue data sets.

Chapter 4: CA-7.000 - CA-7.1044 1025

CA-7.900 Through CA-7.999

CA-7.944

ERROR READING LTERM CHECKPOINT RECORD

Reason:
The logical terminal checkpoint record could not be read during initialization. Issued by
SASSINW2.

Action:
A COLD start initialization of CA Workload Automation SE must be done. If the
Checkpoint data set has been moved, it must be on the same device type with the
queue data sets.

CA-7.945

STATION NAME CANNOT CHANGE

Reason:
An attempt was made to change a station name or logical terminal name (defined by
the STANIDS parameter on the STATION statement in the initialization file) prior to a
WARM start of CA Workload Automation SE. Issued by SASSINW2.

Action:
If a station name or logical terminal name must be changed, it will be necessary to do an
ERST start initialization of CA Workload Automation SE.

CA-7.946

PREMATURE END DURING STATION MERGE

Reason:
An error was encountered while verifying that the station and logical terminal names,
specified in the initialization file, agreed with the contents of the Checkpoint record.
Issued by SASSINW2.

Action:
An ERST start should be attempted. If that fails, then a COLD start must be done.

1026 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.947

ERROR READING CHECKPOINT ID RECORD

Reason:
An unrecoverable I/O error occurred while reading the Checkpoint ID record during
initialization. Issued by SASSINW0.

Action:
A FORM start initialization of CA Workload Automation SE must be done. If the
Checkpoint data set or one or more of the queue files has been moved, they must all
reside on the same device type. The Checkpoint data set must be allocated as one
cylinder on a cylinder boundary.

If CA Workload Automation SE was just taken down with a /SHUTDOWN,DMPQ then a

MOVQ can be done instead of a FORM start.

CA-7.948

ERROR READING CHECKPOINT RECORD

Reason:
An unrecoverable I/O error occurred while reading the Checkpoint record during
initialization. Issued by SASSINW0.

Action:
A FORM start initialization of CA Workload Automation SE must be done. If the
Checkpoint data set has been moved, it must be on the same device type as the queues.
The Checkpoint data set must be allocated as one cylinder on a cylinder boundary.

If CA Workload Automation SE was just taken down with a /SHUTDOWN,DMPQ then a

MOVQ can be done instead of a FORM start.

CA-7.949

WARM START ASSUMED

Reason:
This message indicates that a WARM start of CA Workload Automation SE is possible
and will be performed even though emergency restart (ERST) was specified. Issued by
SASSINW0.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1027

CA-7.900 Through CA-7.999

CA-7.950

EMERGENCY RESTART ASSUMED

Reason:
This message indicates that an emergency restart (ERST) of CA Workload Automation SE
is necessary and will be performed even though a WARM start was specified. Issued by
SASSINW0.

Action:
None.

CA-7.951

I/O ERROR READING DSN DIRECTORIES

Reason:
An I/O error occurred while attempting to read a database directory. Database may not
have been initialized using CDSI program. Issued by SASSINDB.

Action:
If error recurs, contact your installation specialist for assistance. If this is a new
installation, run job N030 from stage II installation and retry.

CA-7.953

DATASET ZERO RECORD NOT FOUND FOR TYPE xx

Reason:
Unable to initialize one of the CA Workload Automation SE database data sets. Control
records were not found on the Dataset data set. Type is DS, NW, PP, SI, SJ or SO. Data
set may not have been properly initialized. Issued by SASSINDB.

Action:
If data set was not initialized, use CDSI to do so; otherwise, use SASSBK00 to back up
and reload the database.

1028 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.954

DATASET FAILED TO OPEN - DDNAME = xxxxxxxx - U0954

Reason:
The data set defined by ddname xxxxxxxx failed OPEN. Issued by SASSINDB, SASSINWC.

Action:
Verify that the ddname is present in the CA Workload Automation SE JCL. If the required
DD statement is present, contact your installation specialist for assistance.

CA-7.955

ALLVSAM ERROR ATTEMPTING TO INIT/CONN, RC=xxxx

Reason:
Errors occurred while attempting to connect or disconnect from the database. RC value
gives an error code that is further explained by WTO messages. Issued by SASSINDB.

Action:
Diagnose problem from WTO messages and take appropriate action.

CA-7.955

VTAM ACB FAILED OPEN DURING INIT

Reason:
During CA Workload Automation SE initialization, an attempt was made to open the
VTAM ACB specified on the UCC7VTAM statement in the initialization file. The open was
not successful.

Action:
Verify that the ACB (APPL) for CA Workload Automation SE is defined correctly to VTAM
and that it is active. After verifying the ACB, issue the command /OPEN,GROUP=(the
first VTAM group in the initialization file) from a non-VTAM CA Workload Automation SE
terminal to enable VTAM access to CA Workload Automation SE.

Chapter 4: CA-7.000 - CA-7.1044 1029

CA-7.900 Through CA-7.999

CA-7.956

UNABLE TO LOAD xxxxxxxx - U0956

Reason:
VSAM/VTAM initialization is unable to load the module specified by xxxxxxxx. Issued by
SASSINVS, SASSINVT.

Action:
Verify the module exists on a CA Workload Automation SE load library.

CA-7.957

INITIALIZATION REQUIRES MORE CORE - U0957

Reason:
Self-explanatory. Issued by SASSINVS, SASSINVT.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

CA-7.958

INVALID SHOWCB RETURN CODE - U0958

Reason:
The SHOWCB issued during CA Workload Automation SE initialization has received a
nonzero return code. Register 15 at the time of abend contains the return code. Issued
by SASSINVT.

Action:
Contact your installation specialist for assistance.

CA-7.958

INVALID VSAM SHOWCB RET CODE (xx) - U0958

Reason:
The SHOWCB issued during CA Workload Automation SE initialization has received a
nonzero return code. Register 15 at the time of abend contains the return code that
appears as xx in the message. Issued by SASSINVS.

Action:
Contact your installation specialist for assistance.

1030 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.958

GENCB ERROR - R15=xx , R0=yyyy

Reason:
The GENCB macro failed while attempting to generate VTAM control blocks. CA
Workload Automation SE terminates with a U0958 abend. Issued by SASSINVT.

Action:
Consult either the IBM manual DFSMS Macro Instructions for Data Sets for the topic on
GENCB errors or the IBM manual z/OS Communications Server: SNA Programming for
the values of xx and yyyy. Correct the error indicated by the codes from the message,
and then retry. If the problem persists, contact CA Support at ca.com/support for
assistance.

CA-7.959

INVALID SASSDBMG (VSAM) ECFLIST - U0959

Reason:
The CA Workload Automation SE database manager ECFLIST control block is invalid for
the Index data set. Issued by SASSINVS.

Action:
Contact your installation specialist for assistance.

CA-7.959

INVALID SASSLMGR ECFLIST - U0959

Reason:
The CA Workload Automation SE line manager ECFLIST control block is invalid. Issued by
SASSINVT.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1031

CA-7.900 Through CA-7.999

CA-7.960

CHECKPOINT DATA SET FAILED OPEN - U0960

Reason:
Self-explanatory. Issued by SASSINCM.

Action:
Verify that the UCC7CKPT DD statement is in the CA Workload Automation SE JCL.

CA-7.960

GENCB FAILED FOR fff, DDNAME=dddddddd, R15=xxxxxxxx, R0=yyyyyyyy

Reason:
In attempting to set up one of the CA Workload Automation SE submit data sets, an
error occurred. The function is shown as fff and can be ACB or RPL. The ddname of the
data set is dddddddd. Registers 15 and 0 after the GENCB operations are also displayed.
Issued by SASSINCM.

Action:
Contact your installation specialist for assistance.

CA-7.960

VTAM ID TABLE ERROR - U0960

Reason:
The VTAMID (node name) table built during initialization is not large enough. Issued by
SASSINVT.

Action:
Contact your installation specialist for assistance.

1032 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.961

BLDL FAILED FOR MODULE NAME xxxxxxxx

Reason:
This is a warning message unless a U0961 dump is produced. The BLDL failed for a
module, calendar block, or format block specified by an APPLCTN, FMTBLK or CALBLK
initialization file statement. The module should exist in the CA Workload Automation SE
load library. Issued by SASSINAP.

Action:
Contact your installation specialist for assistance to ensure that the missing module
should not, in fact, be present.

CA-7.962

CA-7 REGION SIZE IS TOO SMALL - U0962

Reason:
Self-explanatory. Issued by SASSINAP.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

CA-7.963

RMODE invalid for APPLCTN module xxxxxxxx; ATTR=PERM ignored

Reason:
CA Workload Automation SE respects ATTR=PERM only when the module is linked
RMODE=24. In this case, the PERM attribute is ignored, and the module is loaded in the
CA Workload Automation SE application pool.

Action:
None. If the PERM attribute is required, relink the module and ensure RMODE=24.

Chapter 4: CA-7.000 - CA-7.1044 1033

CA-7.900 Through CA-7.999

CA-7.964

APPLCTN CARD MISSING FOR SASSxxxx

Reason:
The APPLCTN statement for the specified program module has been omitted from the
product's initialization file. Issued by SASSINAP.

Action:
Add the missing APPLCTN statement to the initialization file or to the SASSPROG module
and reinitialize CA Workload Automation SE. If the xxxx does not refer to a valid name
(for example, contains blanks or special characters), check the SASSTRAN load module.

CA-7.965

UID RESOURCE TABLE LOADED - xxxxxxxx

Reason:
This message is issued during CA Workload Automation SE initialization after loading the
UID Resource Table specified on the SECURITY statement, with the UID= parameter in
the product's initialization file.

Action:
None.

CA-7.966

UID RESOURCE TABLE CONTAINS A RESOURCE NAME WITH A RESERVED PREFIX OF L2

Reason:
While loading the UID Resource Table specified on the SECURITY initialization
statement, a resource name was encountered that started with a reserved prefix of L2.

Action:
See the Security Reference Guide for more information about defining a UID Resource
Table.

1034 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.966

WORKLOAD BALANCING MODULE LOADED - xxxxxxxx

Reason:
This message indicates that the Workload Balancing module xxxxxxxx was loaded as a
default during CA Workload Automation SE initialization. This message is informational
only. Issued by SASSIOPT.

Action:
None.

CA-7.967

STORAGE UNAVAILABLE FOR WLB MODULE - xxxxxxxx

Reason:
An attempt was made to load a default Workload Balancing module xxxxxxxx during CA
Workload Automation SE initialization; however, the storage was not available. Issued
by SASSIOPT.

Action:
Ensure that the module name specified on the CA Workload Automation SE initialization
file OPTIONS statement, keyword DFLTWLB= is a valid Workload Balancing module. If
the module is valid, contact your installation specialist for assistance.

CA-7.968

WLB MODULE NAME FORMAT INCORRECT - xxxxxxxx

Reason:
An attempt was made to load the Workload Balancing module xxxxxxxx during CA
Workload Automation SE initialization; however, the module name format was
incorrect. Workload Balancing modules have a naming requirement of UCC7Ryyy where
yyy can be specified by the user.

Action:
Check the name specified on the OPTIONS statement, keyword DFLTWLB= in the
product's initialization file.

Chapter 4: CA-7.000 - CA-7.1044 1035

CA-7.900 Through CA-7.999

CA-7.969

WLB MODULE NOT FOUND - xxxxxxxx

Reason:
An attempt was made to load the Workload Balancing module xxxxxxxx during CA
Workload Automation SE initialization; however, the module was not found.

Action:
Ensure that the Workload Balancing module name is correct and that the module
resides in a load library accessible by CA Workload Automation SE during startup.

CA-7.970

DATE/TIME OR REPLY INVALID

Reason:
An error occurred while attempting to validate date/time values or an unknown value
was replied to the CA-7.973 WTOR. Issued by SASSINW0.

Action:
If CA-7.973 was not produced, disable the VALIDATE option in the initialization file and
retry.

If CA-7.973 was produced, it will be reissued. See CA-7.973 for valid replies.

CA-7.971

LAST SSCAN - yy.ddd/hh:mm, LAST CKPT - yy.ddd/hh:mm:ss

Reason:
Date/time validation was requested and checkpoint information is outside the
requested range. This WTO will be followed by a request to verify system date and time.
Issued by SASSINW0.

Action:
None.

1036 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.972

CURRENT SYSTEM DATE/TIME-yy.ddd/hh:mm:ss

Reason:
As part of date/time validation, the system values are displayed. Issued by SASSINW0.

Action:
None.

CA-7.973

DATE/TIME VERIFICATION NECESSARY, REPLY: 'U' TO PROCEED OR 'NOSCAN' TO

DISABLE SSCAN

Reason:
Date/time validation was requested and verification is required to continue startup.
Issued by SASSINW0.

Action:
Verify the system date and reply with one of the values indicated or cancel CA Workload
Automation SE. If system date as noted in CA-7.972 is correct and CA-7.971 was not
produced, reply with U. If system clock is incorrect, reset the date and time and then
reply U. If in doubt or values in CA-7.971 are questionable, reply NOSCAN and use the
SSCAN command to establish scheduling values for schedule scan after initialization.

CA-7.974

SCHEDULE SCAN HAS BEEN DISABLED

Reason:
NOSCAN was replied to CA-7.973. Issued by SASSINW0.

Action:
None. CA Workload Automation SE will initialize without automatic scheduling. Use the
SSCAN command after CA Workload Automation SE is initialized to set scheduling values
for CA Workload Automation SE.

Chapter 4: CA-7.000 - CA-7.1044 1037

CA-7.900 Through CA-7.999

CA-7.975

READ ERROR ON CHECKPOINTED TAT FOR xxxxxxxx QUEUE - U0975

Reason:
An unrecoverable I/O error occurred while attempting to read the checkpoint track
allocator table for the queue data set specified by xxxxxxxx. Issued by SASSINW1.

Action:
A COLD start initialization of CA Workload Automation SE must be done. When a
TYPE=COLD is specified, the initialization file FORMAT statement for the queue in error
must specify DISP=F. For TYPE=FORM, no initialization file changes are needed.

CA-7.976

TRACK ALLOCATOR TABLE ERROR FOR QUEUE xxxxxxxx - U0976

Reason:
The checkpoint track allocator table for the queue specified by xxxxxxxx is invalid for the
queue data set currently referenced by the CA Workload Automation SE JCL. Probable
cause is changing queue data set allocation without doing a FORM (or MOVQ) type of
initialization of CA Workload Automation SE. Issued by SASSINW1.

Action:
A FORM (or MOVQ) type of initialization of CA Workload Automation SE must be done if
the specified queue has been reallocated. If the original queue is available, change the
JCL to point to this data set and do a WARM start initialization of CA Workload
Automation SE. If a queue data set must be reallocated, shut down CA Workload
Automation SE with a DMPQ and reinitialize with a MOVQ after the queue reallocation.

CA-7.977

SASSINW1 REQUIRES MORE CORE FOR INITIALIZATION - U0977

Reason:
The module does not have sufficient core for initialization. Issued by SASSINW1.

Action:
Increase the REGION size on the CA Workload Automation SE execute statement and
reattempt the initialization.

1038 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.978

PRIOR RUN QUEUE IS BEING REUSED

Reason:
This message indicates that the Prior-run queue has been reinitialized and all data
previously collected by CA Workload Automation SE has been scratched. Issued by
SASSINW1.

Action:
None.

CA-7.979

CA-7TRLQ TAT INVALID FOR PRIOR RUN QUEUE - U0979

Reason:
The Trailer queue Track Allocator Table (TAT) is in error or the Trailer queue was not
defined in the initialization file. When the Prior-run queue is reinitialized and found to
be available from the previous CA Workload Automation SE execution, the Trailer queue
must also be available. If the Trailer queue has been reformatted, the Prior-run queue
must also be reformatted. Issued by SASSINW1.

Action:
Specify the Trailer queue in the initialization file if it was missing. If not, specify DISP=F
for the Trailer queue and Prior-run queue and do a COLD start of CA Workload
Automation SE to reformat these queues. A FORM start could also be done.

CA-7.980

xxxxxxxx DD SET UP FOR SUBMIT

Reason:
The internal reader and submit data sets have been set up and are ready to receive jobs.
This message appears for a default internal reader under ddname UCC7IRDR and also
for each submit data set. The default ddname UCC7IRDR can be overridden on the CPU
statement. This name is used only to ensure that CA Workload Automation SE can
successfully open an internal reader if Parallel Submission Processing (PSP) is active.
Issued by SASSINCM.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1039

CA-7.900 Through CA-7.999

CA-7.981

xxxxxxxx DATASET FAILED OPEN

Reason:
The data set specified by xxxxxxxx could not be opened. Issued by SASSINCM.

Action:
Verify that the DD statement is present and correct in the CA Workload Automation SE
JCL. If the message is for the COMM data set, make sure it is allocated on a device type
that is supported.

Note: For the Submit data set the file must be one contiguous extent. DCB attributes
for the data set must be: DCB=(RECFM=F,BLKSIZE=80,LRECL=80).

CA-7.982

xxxxxxxx DATASET FAILED CLOSE

Reason:
The data set specified by xxxxxxxx could not be closed. Issued by SASSINCM.

Action:
Contact your installation specialist for assistance.

CA-7.983

xxxxxxxx - NO CORE FOR DATASET

Reason:
The Submit data set specified by xxxxxxxx could not be established due to insufficient
core. Issued by SASSINCM.

Action:
Increase the REGION size in the CA Workload Automation SE JCL.

1040 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.984

xxxxxxxx - SUBMIT DATA SET NOT AVAILABLE

Reason:
The Submit data set specified by ddname xxxxxxxx could not be found in the CA
Workload Automation SE JCL. CA Workload Automation SE will be unable to submit JCL
to this data set. The ddname is defined in the product's initialization file with a CPU
statement. Issued by SASSINCM.

Action:
To submit jobs to this data set, CA Workload Automation SE must be shut down, the
appropriate DD statement added to the JCL and CA Workload Automation SE
reinitialized. If submission to that data set is not required, the CPU statement defining
the ddname may be changed (or omitted) prior to the next initialization of CA Workload
Automation SE.

CA-7.985

CPU SUBMIT CONTROL TABLE NOT ACTIVE

Reason:
The CPU statements were omitted from the initialization file or the RUNOPT field of the
INIT statement specified MAINT or REPT. CA Workload Automation SE does no
submitting. Issued by SASSINCM.

Action:
If submitting is wanted, the CPU statements must be added to the initialization file and
CA Workload Automation SE must be restarted with a RUNOPT other than REPT or
MAIN.

CA-7.986

COMMUNICATION DATA SET IS NOT ACTIVE

Reason:
The Communications data set is not used by CA Workload Automation SE. This is
because of initialization with RUNOPT=REPT in the INIT statement in the CA Workload
Automation SE initialization file. Issued by SASSINCM.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1041

CA-7.900 Through CA-7.999

CA-7.987

'MAINT' or 'REPT' RUN - NO SUBMIT

Reason:
RUNOPT=MAIN or REPT was specified on the INIT statement in the initialization file. No
jobs will be submitted by CA Workload Automation SE. Issued by SASSSJC0.

Action:
If submission is wanted, the initialization file must be changed and CA Workload
Automation SE must be reinitialized.

CA-7.988

CA-7 MUST RUN APF AUTHORIZED - U0988

Reason:
This message is produced during CA Workload Automation SE startup if one or more of
the libraries in the CA Workload Automation SE STEPLIB concatenation are not APF
authorized. CA Workload Automation SE abends with a user 988 immediately following
this message.

Action:
Ensure all libraries in the CA Workload Automation SE STEPLIB concatenation are APF
authorized and restart CA Workload Automation SE.

CA-7.989

LENGTH OF WLB MODULE NOT CORRECT

Reason:
The size of the UCC7Rxxx WLB module is not valid. This could cause an overlay of
storage resulting in S0Cx abends.

Action:
Reassemble and link edit the UCC7Rxxx module.

1042 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.990

SCT CHAIN IS INCORRECT

Reason:
Invalid System Control Table (SCT) chain. Issued by SASSNUC.

Action:
Contact your installation specialist for assistance.

CA-7.991

BLDL/SLOAD FAILED FOR SASSLINK.

Reason:
An I/O error occurred or SASSLINK is not on a CA Workload Automation SE load library.
Issued by SASSNUC.

Action:
Check the CA Workload Automation SE load library for the SASSLINK module. For
assistance, contact CA Support at ca.com/support for assistance.

CA-7.992

INITIALIZATION DESTROYED SCT CHAIN

Reason:
The SCT chain set up during initialization is not valid. Issued by SASSNUC.

Action:
Contact your installation specialist for assistance.

CA-7.993

CA-7 INITIALIZATION COMPLETE FOR xxxx INSTANCE NAME IS yyyy

Reason:
Central Control System CA Workload Automation SE initialization successfully
completed. The value for xxxx indicates the instance name, or alias, of the copy of CA
Workload Automation SE. The value for yyyy indicates the tracking instance name. If CA
Workload Automation SE is running in batch, yyyy can be NONE. Issued by SASSNUC.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1043

CA-7.900 Through CA-7.999

CA-7.994

STORAGE POOLS NEED MORE STORAGE.

Reason:
Pool specifications are too large for REGION size. Issued by SASSNUC. CA Workload
Automation SE will abend with a U0994 code following this message.

Action:
Increase REGION size or reduce the CWORK value.

CA-7.995

CA-7.LOADLIB FAILED TO OPEN.

Reason:
Unable to open CA Workload Automation SE load library, possibly because of missing
STEPLIB statement. Issued by SASSNUC.

Action:
Perform the following actions:
■ Examine the JCL.
■ Add a STEPLIB DD pointing to the CA Workload Automation SE load library. The
ddname must be STEPLIB.

CA-7.996

STAE EXIT COULD NOT BE ESTABLISHED - U0996

Reason:
A STAE exit could not be set up during CA Workload Automation SE initialization. Issued
by SASSNUC.

Action:
Contact your installation specialist for assistance.

1044 Message Reference Guide

 CA-7.900 Through CA-7.999

CA-7.997

INVALID PARM DATA.

Reason:
Invalid PARM data has been specified in the CA Workload Automation SE JCL. Issued by
SASSNUC.

Action:
Verify the PARM values. Make any necessary corrections and resubmit the job.

CA-7.998

INITIALIZATION DECK EDIT COMPLETE

Reason:
Editing of the initialization file has completed without detecting any errors. Issued by
SASSNUC.

Action:
None.

CA-7.999

EXTERNAL SECURITY REQUIRES LOGON

Reason:
Issued by SASSINAP when EXTERNAL= parameter detected but LOGON not specified.
LOGON control is a prerequisite for any use of external security.

Action:
If external security is to be used, include LOGON in the EXTERNAL= sublist on the
SECURITY statement.

CA-7.999

PROPAGATE ONLY VALID WITH RACF

Reason:
The SECURITY statement in the CA Workload Automation SE initialization file indicated
PROPAGATE=YES, and the system is not using RACF.

Action:
Remove the PROPAGATE=YES specification.

Chapter 4: CA-7.000 - CA-7.1044 1045

CA-7.1001 Through CA-7.1046

CA-7.999

UNABLE TO EXTRACT GLOBAL ID

Reason:
The product's initialization file indicated that external security control was requested
and CAS9 SSF services failed to extract the USERID associated with CA Workload
Automation SE. This message may be issued if the external security system (for example,
CA ACF2, CA Top Secret, or IBM RACF) is not active. Modules involved in detecting and
reporting this condition include SASSINAP, SASSXSEC and CAS9SEC.

Action:
If EXTERNAL=(LOGON,...) is specified on the SECURITY statement in the product's
initialization file, verify that the security system is active and restart CA Workload
Automation SE.

CA-7.1001 Through CA-7.1046

CA-7.1001

MSMR subtask initialization complete

Reason:
The task that issues CAICCI send requests for CA Workload Automation SE Master
Station Message Routing is ready for work.

Action:
None.

CA-7.1002

MSMR subtask terminating

Reason:
The task that issues CAICCI send requests for CA Workload Automation SE Master
Station Message Routing is terminating in response to a shutdown request.

Action:
None.

1046 Message Reference Guide

 CA-7.1001 Through CA-7.1046

CA-7.1003

Unable to acquire FREE chain. FREEMAIN required.

Reason:
The task that issues CAICCI send requests for CA Workload Automation SE Master
Station Message Routing could not return a message element to the free queue to be
reused. A FREEMAIN will be issued to release the storage.

Action:
None.

CA-7.1004

FREEMAIN failed.

Reason:
The task that issues CAICCI send requests for CA Workload Automation SE Master
Station Message Routing has issued a FREEMAIN to release storage for a message
element. The request failed.

Action:
If the message occurs frequently, contact your installation technical specialist for
assistance.

CA-7.1017

MSMR Subtask ended

Reason:
The task that issues CAICCI send requests for CA Workload Automation SE Master
Station Message Routing has terminated.

Action:
None.

Chapter 4: CA-7.000 - CA-7.1044 1047

CA-7.1001 Through CA-7.1046

CA-7.1018

MSMR end of task exit TCB address did not match L2EMSVT_EM00TCB.

Reason:
The end of task exit for the MSMR subtask was entered, but the TCB address of the
terminating task did not match the TCB address of the MSMR subtask that was recorded
when the subtask initiated. CA Workload Automation SE may be unable to restart
MSMR processing.

Action:
If CA Workload Automation SE is unable to restart MSMR processing, recycle the CA
Workload Automation SE started task to resume message routing. If the problem
persists, contact your installation specialist for assistance.

CA-7.1019

MSMR end of task exit could not locate L2EMSVT

Reason:
The end of task exit for the MSMR subtask was entered, but a critical MSMR control
block could not be located. CA Workload Automation SE may be unable to restart MSMR
processing.

Action:
If CA Workload Automation SE is unable to restart MSMR processing, recycle the CA
Workload Automation SE started task to resume message routing. If the problem
persists, contact your installation specialist for assistance.

CA-7.1020

MSMR end of task exit could not locate UCC7SVT

Reason:
The end of task exit for the MSMR subtask was entered, but a critical CA Workload
Automation SE control block could not be located. CA Workload Automation SE may be
unable to restart MSMR processing.

Action:
If CA Workload Automation SE is unable to restart MSMR processing, recycle the CA
Workload Automation SE started task to resume message routing. If the problem
persists, contact your installation specialist for assistance.

1048 Message Reference Guide

 CA-7.1001 Through CA-7.1046

CA-7.1021

MSMR end of task exit entered; TCB at xxxxxxxx TCBCMPF=yyyyyyyy

Reason:
The end of task exit for the MSMR subtask was entered. This message reports the
address of the TCB and the completion code for the MSMR subtask.

Action:
None.

CA-7.1022

L2EMSVT at xxxxxxxx L2EMSVT_EM00TCB=yyyyyyyy

Reason:
This message reports the address of a critical MSMR control block and the address of
the MSMR subtask TCB.

Action:
None.

CA-7.1023

Master Station Message Routing error

Reason:
An error occurred during the attempt to route a master station message to a remote
node.

Action:
None.

CA-7.1024

FFFF: RC(xx) REASON(aa bb dc dd) Node: yyyy....yyyy

Reason:
An error occurred during the attempt to route a master station message to a remote
node. This message reports the function in error along with status details that may be
useful for diagnosing the problem. This message is followed by a CA-7.1025 message.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1049

CA-7.1001 Through CA-7.1046

CA-7.1025

FDBK: xxxx...xxxx

Reason:
An error occurred during the attempt to route a master station message to a remote
node. This message reports a reason for the error. This message is preceded by a
CA-7.1024 message.

Action:
Contact your installation specialist for assistance.

CA-7.1026

Requesting shutdown of MSMR subtask

Reason:
A shutdown of the MSMR subtask has been requested.

Action:
None.

CA-7.1027

DETACHed MSMR subtask

Reason:
A request to delete the TCB for the MSMR subtask has been executed.

Action:
None.

CA-7.1028

Deleting existing message selection table

Reason:
The message selection table that was previously built from the CA Workload
Automation SE MSMR Control File (MSGRCNTL) is being deleted.

Action:
None.

1050 Message Reference Guide

 CA-7.1001 Through CA-7.1046

CA-7.1029

Building message selection table

Reason:
CA Workload Automation SE is building a message selection table using the CA
Workload Automation SE MSMR Control File (MSGRCNTL) as input.

Action:
None.

CA-7.1030

Message selection table processed

Reason:
The message selection table is ready to be used for CA Workload Automation SE Master
Station Message Routing.

Action:
None.

CA-7.1031

MSMR terminated due to abovementioned errors

Reason:
Errors were detected during the attempt to process the message selection table. This
table is built from statements in the CA Workload Automation SE MSMR Control File
(associated with the MSGRCNTL DD statement). No master station messages will be
routed.

Action:
Correct the errors indicated and either recycle CA Workload Automation SE or issue
/REFRESH,MOD=MSGRCNTL to reprocess the CA Workload Automation SE MSMR
Control File.

Chapter 4: CA-7.000 - CA-7.1044 1051

CA-7.1001 Through CA-7.1046

CA-7.1032

Invalid node length

Reason:
An error occurred parsing nodes on the TO keyword in the CA Workload Automation SE
MSMR Control File.

Action:
Correct the errors indicated and either recycle CA Workload Automation SE or issue
/REFRESH,MOD=MSGRCNTL to reprocess the CA Workload Automation SE MSMR
Control File.

CA-7.1033

Invalid syntax on stmt xxxxx

Reason:
A syntax error was detected on a statement in the CA Workload Automation SE MSMR
Control File (MSGRCNTL). The number of the statement is reported at xxxxx.

Action:
Correct the statement in error and either recycle CA Workload Automation SE or issue
/REFRESH,MOD=MSGRCNTL to reprocess the CA Workload Automation SE MSMR
Control File.

CA-7.1034

GETMAIN failed

Reason:
A request for storage was denied during the attempt to process a message selection
table for CA Workload Automation SE MSMR.

Action:
The region size for CA Workload Automation SE may need to be increased. If that fails to
correct the problem, the number of statements in the CA Workload Automation SE
MSMR Control FIle (MSGRCNTL) may need to be decreased. If that fails, contact your
installation technical specialist for assistance.

1052 Message Reference Guide

 CA-7.1001 Through CA-7.1046

CA-7.1035

Invalid value for .....

Reason:
A syntax error was detected during the attempt to process a message selection table for
CA Workload Automation SE MSMR.

Action:
Correct the statement in error. Either recycle CA Workload Automation SE or issue
/REFRESH,MOD=MSGRCNTL to reprocess the CA Workload Automation SE MSMR
Control File.

CA-7.1036

Unable to load SASSPPBR

Reason:
CA Workload Automation SE was unable to load a module needed for CA Workload
Automation SE MSMR. No master station messages will be routed.

Action:
Ensure that SASSPPBR is in a library in the CA Workload Automation SE STEPLIB
concatenation or a library that has been linklisted and recycle CA Workload Automation
SE.

CA-7.1037

Unable to locate L2ENFT

Reason:
CA Workload Automation SE was unable to locate an internal control structure needed
for MSMR. No master station messages will be routed.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1053

CA-7.1001 Through CA-7.1046

CA-7.1039

#CCI xxxx failed for nnnn...nnnn

Reason:
CA Workload Automation SE issued a request to CAICCI for Master Station Message
Routing. This message reports the attempted function and the CAICCI node that was the
object of the request. Message CA-7.1040 follows this message andthat details the
reason for the failure.

Action:
Refer to text of CA-7.1040 for more information.

CA-7.1040

#CCI FDBVDESC: . ...

Reason:
CA Workload Automation SE issued a CAICCI request for Master Station Message
Routing. The request failed. This message reports details on the reason for the failure.
Message 1039 precedes this message. The text of this message sometimes indicates a
temporary problem that is relieved without user intervention.

Action:
Contact your installation specialist for assistance if the message suggests a more serious
problem.

CA-7.1041

SASSEM00 ATTACH xxxxxxxx yyyyyyyy

Reason:
CA Workload Automation SE issued an ATTACH for SASSEM00. R15 on return from the
ATTACH is reported at xxxxxxxx. The address of the TCB is reported at yyyyyyyy.

Action:
None.

1054 Message Reference Guide

 CA-7.1001 Through CA-7.1046

CA-7.1042

No nodes specified

Reason:
The CAICCI nodes of event consoles that are to receive messages from CA Workload
Automation SE must be specified on the TO keyword on the first non-comment
statement in the CA Workload Automation SE MSMR Control File (DD name
MSGRCNTL). If no nodes are specified, no messages will be routed.

Action:
Ensure that the TO keyword is coded on the first non-comment statement in the CA
Workload Automation SE MSMR Control File. Also ensure that at least one valid node is
coded on that keyword. After making these changes, either recycle the CA Workload
Automation SE started task or issue the /REFRESH,MOD=MSGRCNTL command to
reprocess the CA Workload Automation SE MSMR Control File.

CA-7.1043

Reinstating MSMR subtask

Reason:
CA Workload Automation SE is restarting the subtask that handles routing of master
station messages.

Action:
None.

CA-7.1044

Storage request exceeds maximum allowable; data lost

Reason:
CA Workload Automation SE limits the amount of storage that can be used by CA
Workload Automation SE MSMR. This limit has been exceeded. CA Workload
Automation SE may fail to route one or more master station messages.

Action:
Contact your installation specialist for assistance.

Chapter 4: CA-7.000 - CA-7.1044 1055

CA-7.1001 Through CA-7.1046

CA-7.1045

GETMAIN failed. Unable to chain L2EMSG

Reason:
CA Workload Automation SE MSMR needed to obtain storage to chain one or more
master station messages, and the attempt failed. CA Workload Automation SE may fail
to route one or more master station messages.

Action:
Contact your installation specialist for assistance.

CA-7.1046

Chaining error. Data lost.

Reason:
CA Workload Automation SE MSMR attempted to chain one or more master station
messages together, and the attempt failed. CA Workload Automation SE may fail to
route one or more master station messages.

Action:
Contact your installation specialist for assistance.

1056 Message Reference Guide

Chapter 5: CDSI - RSCx Messages
This chapter contains the CDSI through RSCx messages.

CDSI Messages
CDSI-00

INITIALIZATION COMPLETE.

Reason:
The Communications data set has been successfully initialized.

Note: These are 1024-byte blocks and each block may contain multiple logical records.

Action:
None.

CDSI-10

UCC7CMDS DD STATEMENT MISSING

Reason:
The DD statement defining the Communications data set was omitted from the
initialization JCL.

Action:
Add the required DD statement and resubmit the job.

CDSI-11

TOO MUCH INPUT DATA

Reason:
The number of *CPU* statements specified exceeds 11, which is the maximum
permitted.

Action:
Reduce the number of *CPU* statements to no more than 11 and resubmit the job.

Chapter 5: CDSI - RSCx Messages 1057

CDSI Messages

CDSI-12

REQUIRED INPUT MISSING

Reason:
The first statement in the input stream must be *CDSINIT* and there must be at least
one *CPU* statement.

Action:
Correct the input data and resubmit the job.

CDSI-13

INVALID INPUT CARD

Reason:
The error is due to one of the following:
■ The first statement was not *CDSINIT*.
■ One of the statements following the *CDSINIT* was not a *CPU* statement.
■ A *CPU* statement had a blank in the first position of the ddname.

Action:
Correct the statements in error and resubmit the job.

CDSI-14

INVALID NUMERIC DATA

Reason:
The trailer records value specified on the *CDSINIT* statement was invalid.

Action:
Correct the error and resubmit the job.

CDSI-15

ICOM DATA SET TOO SMALL

Reason:
Not enough space was allocated for the Communications data set.

Action:
Increase the space allocation. Resubmit the job.

1058 Message Reference Guide

 CDSI Messages

CDSI-16

ICOM DATA SET MUST BE SINGLE EXTENT

Reason:
The Communications data set was not allocated a single, contiguous extent.

Action:
Scratch and reallocate the data set with CONTIG specified in the JCL.

CDSI-21

UCC7STAT DD STATEMENT MISSING, STAT FILE NOT FORMATTED

Reason:
Self-explanatory.

Action:
None, unless you want STAT file formatting, in which case add the UCC7STAT DD
statement and resubmit the job. This data set must be initialized before CA Workload
Automation SE is initialized for the first time. After that, initialization of the Statistics
data set should not be necessary.

CDSI-22

DATASET DATASET CONTROL MEMBER FOUND BUT NOT REFORMATTED

Reason:
Initialization attempted for Dataset data set but control members were already there.

Action:
If reinitializing Dataset data set, scratch and reallocate the data set. Otherwise, remove
the UCC7DLIB DD statement from the execution JCL.

Chapter 5: CDSI - RSCx Messages 1059

CIAS Messages

CDSI-31

ALLVSAM ERROR ATTEMPTING INIT/CONN/DISCON/FINISH, RC=xxxx

Reason:
Errors occurred while attempting to initialize, connect, disconnect or finish with an
ALLVSAM database. RC value gives error code that is further explained by WTO
messages.

Action:
Diagnose problem from WTO messages and take appropriate action.

CDSI-32

ALLVSAM ERROR ON DSDS, RC=xxxx

Reason:
Logic or I/O error occurred while accessing data set directory type entries. RC value
gives error code and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

CIAS Messages
CIAS-00

IAS Interface started

Reason:
This is an informational message indicating that messages have been received from the
CA Integrated Agent Services (CA IAS) interface.

Action:
None.

1060 Message Reference Guide

 CIAS Messages

CIAS-01

Job aaaaaaaa(nnnn) sent to agent successfully

Reason:
This is an informational message indicating job aaaaaaaa with CA 7 WA job number
nnnn has been sent to the destination agent.

Action:
None.

CIAS-02

Job aaaaaaaa(nnnn) Queue record not found

Reason:
The queue record for the job aaaaaaaa with CA 7 WA job number was not found when
job feedback data was received from an agent. The job was probably canceled from the
queues before the agent could respond with some feedback information.

Action:
None.

CIAS-03

Job aaaaaaaa(nnnn) agent not found; check AGENTDEF configuration

Reason:
Job aaaaaaaa with CA 7 WA job number nnnn is destined for an agent that is not
defined to CA Workload Automation SE.

Action:
Perform the following actions:
■ Verify the correct agent destination for the job.
■ Use queue update to correct the agent destination.
■ Contact your installation specialist to have the agent defined to CA Workload
Automation SE if the agent destination is valid.

Chapter 5: CDSI - RSCx Messages 1061

CIAS Messages

CIAS-04

Job aaaaaaaa(nnnn) errors returned on SQGET Update nnnnn

Reason:
When trying to retrieve job data (SQGET) for job aaaaaaaa with CA 7 WA job number
nnnn, a nonzero return code nnnn was received.

Action:
Perform the following actions:
■ Verify that CA Workload Automation SE is responding correctly to other queue
requests (such as LQ,JOB=).
■ Contact your installation specialist if you have CA Workload Automation SE
problems.

CIAS-05

Job aaaaaaaa(nnnn) errors on Agent Segment Q Replace nnnn

Reason:
When trying to replace the agent segment for job aaaaaaaa with CA 7 WA job number
nnnn, a nonzero return code nnnn was received.

Action:
Perform the following actions:
■ Verify that CA Workload Automation SE is responding correctly to other queue
requests (such as LQ,JOB=).
■ Contact your installation specialist if you have CA Workload Automation SE
problems.

CIAS-06

Job aaaaaaaa(nnnn) sssssssssssssss

Reason:
For job aaaaaaaa with CA 7 WA job number nnnn, the current status returned from the
agent is the string ssssssssssssss (up to 60 bytes).

Action:
None.

1062 Message Reference Guide

 CIAS Messages

CIAS-07

aaaaaaaaaaaaaaaa pppppppppppppppp Agent/Plugin is now active

Reason:
The agent (aaaaaaaaaaaaaaaa) and its plugin (ppppppppppppppppp) have connected
to CA Workload Automation SE through CA Integrated Agent Services (CA IAS)
successfully.

Action:
None.

CIAS-08

Unsolicited message from IAS; Return code nnnn

Reason:
CA Workload Automation SE received an unsolicited message (a message that was not
acknowledged), and CA Integrated Agent Services (CA IAS) could not determine how to
deal with it.

Action:
For assistance, contact CA Support at ca.com/support.

CIAS-09

ssssssss

Reason:
CA Integrated Agent Services (CA IAS) returned the message sssssss from processing.

Action:
Consult the CA IAS Message Reference Guide to determine an action.

Chapter 5: CDSI - RSCx Messages 1063

CIAS Messages

CIAS-10

Job aaaaaaaa(nnnn) waiting on agent activation rrrr hhmm yy.ddd

Reason:
Job aaaaaaaa with job number nnnn is waiting for the agent to become active. rrrr is
the return code returned from CA Integrated Agent Services (CA IAS).

Action:
Perform the following actions:
■ Determine why the agent is not active.
■ Activate the agent where the job is destined.

CIAS-11

Job aaaaaaaa(nnnn) not found in Ready Queue

Reason:
The queue record for the job aaaaaaaa with CA 7 WA job number was not found in the
ready queue.

Action:
Perform the following actions:
■ Verify that the job is still present in the CA Workload Automation SE queues or if
the job was canceled.
■ Determine why the job may not have been found in the ready queue when the job
initiation feedback data was received from the agent if the job was not canceled.

CIAS-12

Job aaaaaaaa(nnnn) errors returned on SQGET rrrr

Reason:
When trying to retrieve job data (SQGET) for job aaaaaaaa, with CA 7 WA job number
nnnn, a nonzero return code rrrr was received.

Action:
Perform the following actions:
■ Verify that CA Workload Automation SE is responding correctly to other queue
requests (such as LQ,JOB=).
■ Contact your installation specialist if you have CA Workload Automation SE
problems.

1064 Message Reference Guide

 CIAS Messages

CIAS-14

IAS interface error with GET_RESPONSE Negative RC=nnnn

Reason:
CA Workload Automation SE received a negative response from CA Integrated Agent
Services (CA IAS) when trying to retrieve agent messages. Because the return code is
negative, this message indicates internal CA IAS problems.

Action:
For assistance, contact CA Support at ca.com/support.

CIAS-15

IAS interface error with GET_RESPONSE Positive RC=nnnn

Reason:
CA Workload Automation SE received a positive return code from CA Integrated Agent
Services (CA IAS) when trying to retrieve agent messages. This generally indicates an
interface error with this particular message.

Note: This message is expected after the command /IAS,FUNC=STOPCOM is issued

because CA Workload Automation SE asks for the next response after receiving the
response that IP communications have been stopped (CAIAS1106I IP shutdown...). If the
message is issued at other times, the message can indicate another problem.

Action:
Monitor CA Workload Automation SE to ensure no other messages are affected.

Consider the following actions:

■ If the messages occur multiple times, try recycling CA Workload Automation SE.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

Chapter 5: CDSI - RSCx Messages 1065

CIAS Messages

CIAS-16

Job aaaaaaaa(nnnn) errors on Job Queue Header Replace rrrr

Reason:
When trying to replace the header segment for job aaaaaaaa with CA 7 WA job number
nnnn, a nonzero return code rrrr was received.

Action:
Perform the following actions:
■ Verify that CA Workload Automation SE is responding correctly to other queue
requests (such as LQ,JOB=).
■ Contact your installation specialist for assistance if you have CA Workload
Automation SE problems.

CIAS-17

Job aaaaaaaa(nnnn) Agent segment not found in queues

Reason:
The agent segment for job aaaaaaaa with CA 7 WA job number nnnn was not found in
the queue record.

Action:
Perform the following actions:
■ Verify the job is an agent job.
■ Issue LQ,JOB=,LIST=ALL to determine if you have a queue problem.
■ Contact your installation specialist for assistance if you have CA Workload
Automation SE problems.

1066 Message Reference Guide

 CIAS Messages

CIAS-18

Job aaaaaaaa(nnnn) errors on Agent Segment Q record GET nnnn

Reason:
When trying to retrieve the agent segment data (SQGET) for job aaaaaaaa with CA 7
WA job number nnnn, a nonzero return code nnnn was received.

Action:
Perform the following actions:
■ Verify that CA Workload Automation SE is responding correctly to other queue
requests (such as LQ,JOB=).
■ Contact your installation specialist for assistance if you have CA Workload
Automation SE problems.

CIAS-19

Unknown Agent Response ssss

Reason:
An agent received an unknown message. The message information begins with the data
indicated by ssss (up to 50 bytes). This message indicates an internal error.

Action:
For assistance, contact CA Support at ca.com/support.

CIAS-20

Subtask SASSCIJF abended on Job aaaaaaaa(nnnn) with code ccccc

Reason:
The agent job feedback subtask abended with abend code ccccc when processing job
aaaaaaaa with CA 7 WA job number nnnn. The subtask stops processing this job, and it
needs to be manually attended.

Action:
Ensure that the job feedback subtask SASSCIJF is reattached through messages issued to
the JES job log. If the subtask abends three or more times, CA Workload Automation SE
terminates with abend U0785.

Chapter 5: CDSI - RSCx Messages 1067

CIAS Messages

CIAS-21

IAS Free Response failed, RC=rrrr Address hhhhhhhh for job aaaaaaaa(nnnn)

Reason:
CA Workload Automation SE requested CA Integrated Agent Services (CA IAS) to free the
response for job aaaaaaaa with CA 7 WA job number nnnn with the return code rrrr.

Action:
Monitor for other CIAS-21 messages.

Note: If multiple messages are received, this could indicate issues with the CA
Integrated Agent Services (CA IAS) component. This could introduce storage problems in
CA Workload Automation SE if CA IAS is unable to free its storage.

CIAS-22

Job aaaaaaaa(nnnn) failed to get requeued RC=rrrr; Job should be requeued to REQQ

Reason:
CA Workload Automation SE was trying to requeue job aaaaaaaa with CA Workload
Automation SE job number nnnn to the request queue. CA Workload Automation SE
program SASSSQM7 issued the return code rrrr.

Action:
Perform the following actions:
■ Manually requeue the job to the request queue.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

CIAS-23

Job aaaaaaaa(nnnn) job status update failed RC=rrrr; Verify job status

Reason:
CA Workload Automation SE was unable to update the job status from recent job
feedback data.

Action:
Perform the following actions:
■ Verify what the job status should be in CA Workload Automation SE.
■ Move the job appropriately.
■ If the problem persists, contact CA Support at ca.com/support for assistance.

1068 Message Reference Guide

 CIAS Messages

CIAS-30

Job aaaaaaaa(nnnn) Requeued; agent no longer defined RC=rr,rr

Reason:
Job aaaaaaaa with CA 7 WA job number nnnn was requeued to the request queue with
a status N-FAIL because the agent is no longer defined to CA Workload Automation SE in
the agent definition file. The agent was probably removed from the agent definition as a
result of a reconfigure command.

Action:
Add the agent back to the agent definition file if the agent is to remain defined to CA
Workload Automation SE.

CIAS-31

Job aaaaaaaa(nnnn) Requeued; unable to send to agent RC=rr,rr

Reason:
Job aaaaaaaa with CA Workload Automation SE job number nnnn was requeued to the
request queue with a status N-FAIL because the request could not get sent to the agent
immediately.

Action:
Perform the following actions:
■ Verify that the agent is active and connected to CA Workload Automation SE.
■ Restart the job once the agent has established communications with CA Workload
Automation SE.

CIAS-32

Job aaaaaaaa(nnnn) was canceled RC=rr,rr

Reason:
This is an informational message indicating job aaaaaaaa with CA 7 WA job number
nnnn was canceled by a user and purged from the CA Integrated Agent Services (CA IAS)
queues.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1069

CIAS Messages

CIAS-33

Job aaaaaaaa(nnnn) requeued; agent queue purged RC=rr,rr

Reason:
This is an informational message indicating job aaaaaaaa with CA 7 WA job number
nnnn was requeued to the request queue with an N-FAIL status because the agent
queues were purged due to a reconfiguration of the agents.

Action:
Consider the following actions:
■ If the agent should not have been reconfigured out of the network, add the agent
definition back into the Agent Definition file and issue the reconfigure command
again. Next, restart the job from the request queue.
■ If the agent will not longer be active, either cancel the job or use the queue update
screen to redirect the job to the correct destination agent.

CIAS-34

TCP/IP Receiver Port not accepting messages

Reason:
The TCP/IP receiver port is not receiving messages according to CA Integrated Agent
Services (CA IAS). As a result, CA Workload Automation SE has temporaily stopped
sending jobs to agents because of the inability to receive the job feedback.

Action:
Perform the following actions:
■ Determine why the TCP/IP receiver port is not functioning properly.
■ Issue the /IAS,FUNC=-STARTCOM command to reinitialize the communications
interface.

CIAS-35

Unknown Agent Message sssssssssssssss

Reason:
An agent received an unknown message. The message information begins with the data
indicated by ssssssssssssss (up to 50 bytes). This message indicates an internal error.

Action:
For assistance, contact CA Support at ca.com/support.

1070 Message Reference Guide

 CIAS Messages

CIAS-37

nn nnn Unable to connect or send to agent aaaa...aaaa

Reason:
CA Integrated Agent Services (CA IAS) encountered an error trying to connect to agent
aaaa...aaaa. The nn error code is the return code from the GET_RESPONSE request, and
the nnn is the internal CA IAS code indicating the error.

Action:
Perform the following actions:
■ Ensure the agent is active on the distributed platform.
■ Ensure there are no network (TCP/IP) problems (Can you ping the host address?).

If unable to determine the problem, supply this message, the CA Workload Automation
SE log data and any other pertinent information to your installation specialist.

CIAS-38

nn nnn Unable to process message to/from agent aaaa...aaaa

Reason:
CA Integrated Agent Services (CA IAS) could not process a message destined for or sent
from the agent aaaa...aaaa. The nn error code is the return code from the
GET_RESPONSE request, and the nnn is the internal CA IAS code indicating the error.
This message could be due to mismatching encryption keys, an invalid agent definition,
or other internal reasons.

Action:
Perform the following actions:
■ Ensure the agent definition for this agent is valid.
■ Ensure the encryption keys used between CA Workload Automation SE and the
agent match identically.

If unable to determine the problem, supply this message, the CA Workload Automation
SE log data and any other pertinent information to your installation specialist.

Chapter 5: CDSI - RSCx Messages 1071

CIAS Messages

CIAS-39

nn nnn No data received from agent aaaa...aaaa

Reason:
A null message (a message with no data) was received from agent aaaa...aaaa. The nn
error code is the return code from the GET_RESPONSE request, and the nnn is the
internal CA IAS code indicating the error. This message probably represents an error on
the agent side.

Action:
Determine whether the agent is operating properly. If unable to determine the problem,
supply this message, the CA Workload Automation SE log data and any other pertinent
information to your installation specialist.

CIAS-41

Agent agentname is not receiving messages

Reason:
CA Workload Automation SE cannot connect to agent agentname during initialization or
when a /IAS,FUNC=RECONFIG is issued.

Action:
Consider the following actions:
■ Determine whether the agent is active.
■ Determine whether the domain name or IP address is valid.
■ Determine whether you have an encryption problem. Look for CIAS-09 CIAS11001I
Response code=00000006, reason-00000063 messages in the CA 7 browse log.
■ For assistance, contact CA Support at http://ca.com/support.

After the problem is resolved, restart the agent to reestablish a connection to the agent.
If that fails, issue the /IAS,FUNC=RECONFIG command to reestablish a connection to the
agent.

1072 Message Reference Guide

 DPCH Messages

CIAS-99

Unknown MSGBYTE received

Reason:
A CA Workload Automation SE program in the CA Integrated Agent Services (CA IAS)
interface issued a message byte (MSGBYTE) that is not recognized. This message
indicates an internal error.

Action:
For assistance, contact CA Support at ca.com/support.

DPCH Messages
This subsection contains the CA Workload Automation SE DPCH messages. The
messages are produced by SASSDPCH. Each message is accompanied by a return code.

DPCH-01

FWLPDATA DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname FWLPDATA. Probable missing or incorrectly spelled
ddname in the DD statement. A condition code of 8 is set.

Action:
Provide a correct DD statement and retry.

DPCH-02

DISPATCH DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname DISPATCH. Probable missing or incorrectly spelled
ddname in the DD statement. A condition code of 8 is set.

Action:
Provide a correct DD statement and retry.

Chapter 5: CDSI - RSCx Messages 1073

DPCH Messages

DPCH-03

NO YYDDD FOUND IN J RECORD

Reason:
The scheduled date, in Julian format, must immediately follow the J (in column 1) of
each record. A J record was found but without a valid 5-digit date in the next 5
positions. Probable user error. Should not occur if input was provided by an FWLP
command. A condition code of 8 is set.

Action:
Correct the invalid date format and retry.

DPCH-05

ERROR FOUND DURING JOB NAME PROCESSING

Reason:
No job name was found in a J record. Probable user error. Should not occur if input was
provided by an FWLP command. Should occur only if at least one job name character
does not occur in column 9 of the J record. A condition code of 8 is set.

Action:
Correct the invalid job name and retry.

DPCH-06

ERROR FOUND PROCESSING TIME VALUES

Reason:
Did not find valid time fields in a J record. Probable user error. Should not occur if input
was provided by an FWLP command. Should occur only if at least one time value of four
characters is not found or if incorrect termination of the time parameters is found. A
condition code of 8 is set.

Action:
Correct the invalid time fields and retry.

1074 Message Reference Guide

 DTxx Messages

DPCH-07

NO FLWP DATA RECORDS PROCESSED

Reason:
Did not find any valid FWLP records in the FWLPDATA data set. Probably one of the
following user errors:
■ DD statement FWLPDATA pointed to the wrong data set.
■ No jobs were scheduled in the time period requested for the FWLP command
issued to create the data set.
■ A manually provided data set was empty.

A condition code of 4 is set.

Action:
Retry with the correct data set.

DTxx Messages
DT10-01

INVALID PARM DATA STARTING WITH x IN POSITION nnn

Reason:
The PARM values contain an error beginning with the character shown in position nnn of
the PARM data. The first position of the PARM data is position 1.

Action:
Correct the error and rerun.

DT10-12

CANNOT OPEN DDN=DT10IN

Reason:
An error occurred trying to open the input data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DT10IN.

Chapter 5: CDSI - RSCx Messages 1075

DTxx Messages

DT10-16

CANNOT OPEN DDN=DT10OUT

Reason:
An error occurred trying to open the output data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DT10OUT.

DT10-20

BAD LSYS GROUP END, NOT SLIC-00

Reason:
The SLIC-nn message terminating the output produced for an LSYS command indicates
that an error occurred. That is, the nn value is not zero.

Action:
Correct the cause of the nonzero completion message in the previous BTI step and
rerun.

DT10-24

BAD LJOB GROUP END, NOT SLIA-00

Reason:
The SLIA-nn message terminating the output produced for an LJOB command indicates
that an error occurred. That is, the nn value is not zero.

Action:
Correct the cause of the nonzero completion message in the previous BTI step and
rerun.

1076 Message Reference Guide

 DTxx Messages

DT10-28

INTERNAL ERROR PROCESSING A JOB

Reason:
The program sets a flag when it starts to process the data generated by an LSYS
command. Another flag is set on for the processing of an LJOB command. These flags
are reset when their corresponding SLIx-nn termination message is encountered in the
input. All other commands will have been ignored. This message indicates the program
has reached a point where either one or the other of the two flags should have been set
on but neither was set. It suggests that either the program code or the input file has
been tampered with.

Action:
Establish the integrity of the program code, the input data, or both and rerun.

DT10-32

END OF FILE REACHED BUT /LOGON EXPECTED

Reason:
No /LOGON command could be found in the input data set.

Action:
Either the previous BTI step completed abnormally or the wrong data set was used as
input to SASSDT10. Ensure that CA Workload Automation SE is active when the BTI step
is rerun.

DT10-36

END OF FILE REACHED BUT SLIC-00 EXPECTED FOR LSYS GROUP

Reason:
The program reached end-of-file during processing of LSYS command output without
finding the SLIC-nn message that would indicate routine completion of the command.
The output data set being produced will be incomplete. Probably caused by exceeding
the capacity of the Batchout data set during the previous BTI step.

Action:
Increase the allocation for the Batchout data set and rerun the job.

Chapter 5: CDSI - RSCx Messages 1077

DTxx Messages

DT10-40

END OF FILE REACHED BUT SLIA-00 EXPECTED FOR LJOB GROUP

Reason:
The program reached end-of-file during processing of LJOB command output without
finding the SLIA-nn message that would indicate routine completion of the command.
The output data set being produced will be incomplete. Probably caused by exceeding
the capacity of the Batchout data set during the previous BTI step.

Action:
Increase the allocation for the Batchout data set and rerun the job.

DT10-44

NUMBER OF JOBS HAS EXCEEDED TABLE CAPACITY

Reason:
The number of unique job names requested exceeds the capacity of the internal job
name table. See the Database Maintenance Guide for a discussion of the design
limitations for this process.

Action:
Divide the commands into multiple runs or contact your installation specialist to enlarge
the table capacity.

DT20-01

INVALID PARM DATA STARTING WITH x IN POSITION nnn

Reason:
The PARM values contain an error beginning with the character shown in position nnn of
the PARM data. The first position of the PARM data is position 1.

Action:
Correct the error and rerun.

1078 Message Reference Guide

 DTxx Messages

DT20-04

GETMAIN FAILED FOR TABLES

Reason:
Space for all of the internal tables could not be obtained with the GETMAIN macro.

Action:
Increase the region and retry. If problem persists, contact your installation specialist for
assistance.

DT20-08

CANNOT OPEN DDN=DT20CR01

Reason:
An error occurred trying to open the output control report data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DT20CR01.

DT20-12

CANNOT OPEN DDN=DT20IN

Reason:
An error occurred trying to open the input data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DT20IN.

DT20-16

CANNOT OPEN DDN=DT20OUT

Reason:
An error occurred trying to open the output data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DT20OUT.

Chapter 5: CDSI - RSCx Messages 1079

DTxx Messages

DT20-20

INVALID COMMAND IN INPUT

Reason:
SASSDT10 generates LJOB,JOB=xxxxxxxx LIST=mmmm commands in which mmmmm can
be either STEPDD, TRIG, or RQMT. Only these three command variants can be accepted
by SASSDT20. Some other command was found in the input data. The control report will
provide an indication as to the last job and variant that was completed. The offending
record will not be printed.

Action:
If the file was corrupted manually, correct the error and rerun. Otherwise, contact your
installation specialist for assistance.

DT20-24

END OF FILE REACHED BUT /LOGON EXPECTED

Reason:
No /LOGON command could be found in the input data set.

Action:
Either the previous BTI step completed abnormally or the wrong data set was used as
input to SASSDT20.

DT20-28

END OF FILE REACHED BUT SLIA-00 EXPECTED FOR LJOB GROUP

Reason:
The program reached end-of-file during processing of LJOB command output and
without finding the SLIA-nn message that would indicate routine completion of the
command. The output data set being produced will be incomplete. Probably caused by
exceeding the capacity of the Batchout data set during the previous BTI step.

Action:
Increase the allocation for the Batchout data set and rerun the job.

1080 Message Reference Guide

 DTxx Messages

DT20-32

NUMBER OF xxxxxxxx HAS EXCEEDED TABLE CAPACITY

Reason:
An internal table capacity has been exceeded. The specific table is indicated by xxxxxxxx
that will be either JOBS, SYSTEMS, NETWORKS, or DATASETS. See the Database
Maintenance Guide for a discussion of the design limitations for this process.

Action:
Divide the requested workload into multiple smaller groups or contact your installation
specialist to enlarge the table capacities.

DT20-36

WRONG SUBROUTINE ENTERED FOR COMMAND

Reason:
Each submodule tests the first record in the work file to ensure the driver (DT20) called
it correctly. This test will catch logic errors and any errors in accessing the work file.
Erroneous use of DISP=MOD in the WORKFILE DD statement will also cause this error.

Action:
If the DISP is incorrect, make the necessary correction and rerun. Otherwise, contact
your installation specialist for assistance.

DT20-40

SUBROUTINE (DT2x) REACHED EOF ON TEMPFILE BUT NO 'SLIA-00'

Reason:
Submodules decrease a record counter (established by the driver SASSDT20) each time
a record is read from the work file. If the count of records left has reached zero when
another record is needed, this error message is generated. This is a probable logic error
in the submodule indicated. (If the DT20IN file did not contain the SLIA-nn message for
the group, the driver would have terminated with message DT20-28.)

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1081

DTxx Messages

DT20-44

FAILED TO OPEN OUTPUT DATASET FILE

Reason:
An error occurred trying to open the Dataset data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DATASET.

DT30-01

INVALID PARM DATA STARTING WITH x IN POSITION nnn

Reason:
The PARM values contain an error beginning with the character shown in position nnn of
the PARM data. The first position of the PARM data is position 1.

Action:
Correct the error and rerun.

DT30-04

GETMAIN FAILED FOR TABLES

Reason:
Space for all of the internal tables could not be obtained using the GETMAIN macro.

Action:
Increase the region and retry. If problem persists, contact your installation specialist for
assistance.

DT30-08

CANNOT OPEN DDN=xxxxxxxx

Reason:
The xxxxxxxx represents the DDNAME of the file for which the open failed.

Action:
Examine the DD statement for correct values including the spelling of the ddname.

1082 Message Reference Guide

 DTxx Messages

DT30-12

FAILED TO OPEN INPUT FILE

Reason:
An error occurred trying to open the input data set.

Action:
Examine the DD statement for correct values including the spelling of the ddname
DBMLISTS.

DT30-24

END OF FILE REACHED BUT /LOGON EXPECTED

Reason:
No /LOGON command could be found in the input data set.

Action:
Either the previous BTI step completed abnormally or the wrong data set was used as
input to SASSDT30.

DT30-32

NUMBER OF ENTRIES HAS EXCEEDED CAPACITY OF xxxxxxxxxx TABLE

Reason:
An internal table capacity has been exceeded. The specific table is indicated by
xxxxxxxxxx that will be either PROC NAME, JCL MEMBER, INLINEPROC or JCL LIBR. See
the Database Maintenance Guide for a discussion of the design limitations for the first
three. The limit for JCL LIBR is 254.

Action:
Divide the requested workload into multiple smaller groups or contact your installation
specialist for assistance in enlarging the table capacities.

Chapter 5: CDSI - RSCx Messages 1083

DTxx Messages

DT30-36

WRONG SUBROUTINE ENTERED FOR COMMAND

Reason:
Each submodule tests the first record on the work file to ensure the driver (DT30) called
it correctly. This test will catch logic errors and any errors accessing the work file.
Erroneous use of DISP=MOD on the WORKFILE DD statement will also cause this error.

Action:
If the DISP was incorrect, make the necessary correction and rerun. Otherwise, contact
your installation specialist for assistance.

DT30-40

SUBROUTINE (DT3xx) REACHED EOF ON TEMPFILE BUT NO 'mmmm-00'

Reason:
The submodules decrease a record counter (established by driver SASSDT30) each time
a record is read from the work file. If the count of records left has reached zero when
another record is needed, this error message is generated. The xx value identifies the
submodule that encountered the error condition. mmmm is the routine completion
message prefix that was expected to be found (for example, SLIA-00). (If the DBMLISTS
file had not contained the 'mmmm-00' message, the driver would have generated one in
an effort to continue.) This is probably a logic error in the code.

This error can also result if the Batchout data set in the previous BTI run was too small.
In that case, message BSTR-17 will have been written as the last record. That is, the last
record input to the DT30 step.

Action:
If this did not result from a DASD space problem, contact your installation specialist for
assistance.

1084 Message Reference Guide

 DTxx Messages

DT32-01

DOES NOT RECOGNIZE PROS-TYPE HEADING. NO PROSE OUTPUT PROVIDED

Reason:
Submodule SASSDT32 could not find the PROS-TYPE heading in the input. The message
appears on the job SYSOUT listing only. An attempt is made by the driver to continue
with the remainder of the input file. One group of prose should be missing from the
DBMADDS1 file for each occurrence of this message. This is a probable system error.

Action:
Contact your installation specialist for assistance.

DT33-01

DS NUMBER MISSING FROM LDSN COMMAND -- OUTPUT IS SUPPRESSED

Reason:
Submodule SASSDT33 found LDSN command output that did not contain a data set
number. Probable system error.

Action:
Contact your installation specialist for assistance.

DT34-01

DSORG ERROR - WILL TRY TO TREAT AS PDS, AT SEQ# xxxxxxxx

Reason:
Submodule SASSDT34 encountered a set of JCL for which the JCL library DSORG value
was something other than PDS, LIB or PAN. The program will try to process the data as if
it were PDS and continue. xxxxxxxx is the sequence number in the DBMADDS1 and
DT30CR01 files at which this batch of JCL can be found. Probable system error.

Action:
None if the JCL is to be placed in a PDS. Otherwise, contact your installation specialist
for assistance.

Chapter 5: CDSI - RSCx Messages 1085

DTxx Messages

DT35-01

JOB NAME MISSING FROM LJOB COMMAND -- OUTPUT IS SUPPRESSED

Reason:
Submodule SASSDT35 found LJOB command output that did not contain a job name.
Probable system error.

Action:
Contact your installation specialist for assistance.

DT35-02

xxxxxxxx AND/OR yyyyyyyy DDS MISSING; REQUIRED FOR zzzzz DATA, ABEND=S000
U0008 ISSUED

Reason:
You are missing DD statements that are required for the jobs you are transporting to a
new database. These statements are in pairs and depend on the job type, XPJOBs or
agent jobs.

If you are transporting XPJOBs (zzzzz), you need the VRMXREFS and DT30CR10 DD
statements.

If you are transporting agent (zzzzz) jobs, you need the AGENTDIV and DT30CR11 DD
statements.

Action:
Perform the following actions:
■ Add the required DD statements to the job.
■ See member CA07N830, created during the CA Workload Automation SE SYSGEN
process, for allocation details for these files.

DT35-36

SUBMODULE T3xx REJECTS THIS FIRST RECORD:

Reason:
The submodule identified in this message expected a particular record when it was first
entered, but that record was not found. Control will be returned to the main driver that
will issue DT30-36 before aborting. Probable system error.

Action:
Contact your installation specialist for assistance.

1086 Message Reference Guide

 DTxx Messages

DT35-40

SCAL NOT FOUND, JOB xxxxxxxx, SCHD NOT PROCESSED.

Reason:
Submodule SASST354 could not find the SCAL value while processing a job schedule.
Schedule processing for this job is skipped. The message also appears, followed by a line
of asterisks, on the DT30CR02 control report. Probable system error.

Action:
Contact your installation specialist for assistance.

DT36-04

NO INPUT LEFT FOR NTWK=xxxxxxxx SCHEDULES #2 LINE nnnnnnnn

Reason:
Submodule SASSDT36 could find no schedules defined for the network indicated by
xxxxxxxx in the message. Control report DT30CR02, DATA BASE ADDS - PART 2, will
reflect the last command generated prior to this condition using sequence number
nnnnnnnn as indicated. Probable system error.

Action:
Contact your installation specialist for assistance.

DT36-08

TYPE NOT INPUT NOR OUTPT FOR NTWK=xxxxxxxx

Reason:
Submodule SASSDT36 found a TYPE value other than INPUT or OUTPT within the LNTWK
data. Processing for this network is suspended without generating any commands to
move the network. This message also appears, followed by a line of asterisks, on the
DT30CR02 control report. Probable system error.

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1087

EDTx Messages

DT36-36

SUBMODULE T361 REJECTS THIS FIRST RECORD:

Reason:
Submodule SASST361 was given its first record to process and the record was not the
STATION NAMES section of LNTWK data. Control will be returned to the main driver that
will then issue message DT30-36. This is a probable system error.

Action:
Contact your installation specialist for assistance.

DT36-40

DELETED WITHOUT ADDING, NW=xxxxxxxx RPT=y LINE=nnnnnnnn

Reason:
Submodule SASST361, having already generated a command to delete the indicated
network at the sending site, did not find the section of data titled SCHEDULES in the
LNTWK data. The value of y indicates the control report and nnnnnnnn indicates the
command sequence number where the condition was found. This message is written
twice to SYSOUT to identify control report and line number in each of the xxxDELTS and
xxxADDS1 files where this condition occurred. Probable system error.

Action:
Contact your installation specialist for assistance.

EDTx Messages
EDTx-00

COMMAND PROCESSED.

Reason:
The text editor command has been successfully processed.

Action:
None.

1088 Message Reference Guide

 EDTx Messages

EDTx-01

xx INVALID MACRO CALL RETURN CODE = nn.

Reason:
An unexpected macro return code has been received. xx is the macro location in the
program and nn is the return code from register 15.

Action:
Contact your installation specialist for assistance.

EDTx-11

INVALID COMMAND, RE-ENTER

Reason:
An invalid command has been entered. The following are some of the reasons for invalid
commands:
■ An invalid command name.
■ Non-numeric data specified for a numeric parameter.
■ A beginning sequence number greater than an ending sequence number.
■ Invalid or omitted EDIT delimiters.
■ Not enough or too many parameters specified on the command.
■ An invalid value specified for a numeric parameter.

Action:
Review the available commands and parameters, and reenter the command.

EDTx-12

ENTER COMMAND

Reason:
This is an informational message issued when the text editor has been entered from one
of the Database Maintenance functions. It indicates the text editor is available for
processing the Edit Work File (EWF).

Action:
None.

Chapter 5: CDSI - RSCx Messages 1089

EDTx Messages

EDTx-13

INVALID PASSED DATA SEGMENT

Reason:
The function invoking the text editor has passed invalid data into the Active Area.

Action:
Contact your installation specialist for assistance.

EDTx-14

LINE NOT FOUND IN RANGE

Reason:
No lines in the range of the parameters are specified on the command. For example,
you cannot delete lines 300 through 500 when no lines have sequence numbers greater
than 299 and less than 501 in the EWF.

Action:
Possible user error. Examine the sequence numbers specified on the command for
validity. Examine the contents of the EWF to verify condition.

EDTx-15

EWF EMPTY

Reason:
The EWF has no lines for the command to process.

Action:
None.

1090 Message Reference Guide

 EDTx Messages

EDTx-16

UNABLE TO LOAD xxxxxxxx RC=nn

Reason:
The text editor is unable to load module xxxxxxxx. nn is the return code from the SLOAD
macro.

Action:
Check module SASSPROG for the module name and APPLCTN macro. If they are not
located there, check the product's initialization file for an APPLCTN statement for the
module xxxxxxxx. Verify that the module exists on the CA Workload Automation SE load
library. If the problem persists, contact your installation specialist for assistance.

EDTx-17

NUMBER OF LINES EXCEEDS SWF SPACE - DATA LOST

Reason:
The number of lines has exceeded the amount of space available for the SWF.

Action:
Examine the EWF contents. Lines may have been lost. The maximum number of lines
available in the EWF depend on:
■ The type of device on which the Scratch queue is allocated.
■ The amount of space allocated.
■ The SWFTRK parameter on the DAIO initialization file statement.

EDTx-18

ACTIVE FILE NOT IN SEQUENCE...XSEQ ASSUMED

Reason:
When the text editor was invoked, the Active Area was found to be out of sequence.
External sequence numbering has been assumed and the EWF has been sequenced
using the system default increment.

Action:
XSEQ OFF may be used to set external sequencing off. RENUM may be used to
resequence the EWF. If external sequencing is wanted, no action is necessary.

Chapter 5: CDSI - RSCx Messages 1091

EDTx Messages

EDTx-19

EDIT LIST / FULL EDIT MODE INVALID

Reason:
The edit list mode (EDIT LIST) command is valid for 3270-type terminals only.

Action:
Use other forms of the EDIT commands or perform the operations on a 3270-type
terminal.

EDTx-20

EDIT STRING NOT FOUND IN RANGE

Reason:
String 1 of the EDIT command was not found in the range lines specified.

Action:
This may occur under the following conditions:
■ The string was specified incorrectly.
■ The line number range is incorrect.
■ The edit scan columns are set improperly (via STATUS).

EDTx-21

XPJOB JCL COMMAND NOT ALLOWED; USE LJCK

Reason:
In the Edit Facility for either JCL or QJCL, one of the JCLxx commands was attempted.
These include JCL, JCLL, JCLS, JCLSS, and JCLSR. XPJOB jobs cannot have their parameter
data validated through the JCL or QJCL Edit facilities.

Action:
Exit the Edit Facility and use the LJCK command.

1092 Message Reference Guide

 GRLA Through GRLX Messages

GRLA Through GRLX Messages

GRLA-01

LOGSTATS DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname LOGSTATS. Probable missing or incorrectly spelled
ddname in the DD statement. A U0001 abend follows this message.

Action:
Provide a correct DD statement and retry.

GRLA-02

ERROR RETURNED BY SASSHDAT

Reason:
An error occurred while trying to convert a Julian date to Gregorian format. Probable
user error. A U0001 abend follows this message.

Action:
Provide correct dates for FROM and THRU values and resubmit.

Chapter 5: CDSI - RSCx Messages 1093

GRLA Through GRLX Messages

GRLP-01

INVALID PARM DATA STARTING WITH

error-condition-text

Reason:
An error was found in the specified parameters. A two-line message is produced with
the second line identifying the specific error found. The second line may be either of the
following:

UNKNOWN KEYWORD IN POSITION nn

where the nn indicates the position in the parameter string in which the unknown
keyword was found. POSITION is relative to 1, with the first nonblank character entered
being position 1, and includes any commas between keywords. A U0001 abend follows
this message.

INVALID VALUE FOR KEYWORD xxxx

where the value for xxxx indicates the keyword for which an invalid value was entered.
A U0001 abend follows this message.

Action:
Correct the PARM data and retry.

GRLP-02

'THRU' VALUE NOT HIGHER THAN 'FROM'

Reason:
The selection date/time range was specified incorrectly. Value for keyword THRU must
be higher than the value for keyword FROM. A U0001 abend follows this message.

Action:
Provide a correct date/time range and retry.

1094 Message Reference Guide

 GRLA Through GRLX Messages

GRLP-03

INVALID DATE/TIME RANGE LITERALS

Reason:
Values provided for FROM and THRU did not contain valid date/time values or range
literals. A U0001 abend follows this message.

Action:
Provide correct date/time range and retry.

GRLP-04

NO PARM OR SYSIN DATA FOUND

Reason:
No PARM was provided and no data was found in the SYSIN data set. Abend U0001
occurs to force report parameter specifications.

Action:
Provide PARM or SYSIN input indicating report span and record types. Resubmit the job.

GRLP-05

LOGSTATS DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname LOGSTATS. Probable missing or incorrectly spelled
ddname in the DD statement. A U0001 abend follows this message.

Action:
Provide a correct DD statement and retry.

GRLX-01

LOGIN DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname LOGIN. Probable missing or incorrectly spelled
ddname in the DD statement. A U0001 abend follows this message.

Action:
Provide a correct DD statement and retry.

Chapter 5: CDSI - RSCx Messages 1095

GRLA Through GRLX Messages

GRLX-02

LOGOUT DATA SET OPEN FAILURE

Reason:
An OPEN error occurred for ddname LOGOUT. Probable missing or incorrectly spelled
ddname in the DD statement. A U0001 abend follows this message.

Action:
Provide a correct DD statement and retry.

GRLX-03

LOGIN DATA SET OUT OF SEQUENCE

Reason:
A sequence error occurred in the LOGIN data set. Due to the way date/time range logic
is applied, the input data must be in ascending date/time sequence. A U0001 abend
follows this message.

This error can occur if an extract is attempted against an active Log data set; that is, one
to which CA Workload Automation SE is currently writing. Since reading stops once the
THRU value is reached, undetected sequence errors may exist beyond that date/time.

Action:
Determine cause of sequence error, sort the data if necessary, and retry. If an active log
is needed, perform a /SWAP command to begin recording on the alternate Log, and run
again. Be sure to always use the SASSHIS5 program to dump the log files.

GRLX-04

NO RECORDS FOUND BETWEEN FROM AND THRU VALUES

Reason:
This is an informational message. No records were found with creation date/time
occurring between the FROM and THRU values requested by the user. A condition code
of 4 is set.

Action:
Provide correct parameters, correct data set, or both and retry.

1096 Message Reference Guide

 HC25 Through HISx Messages

HC25 Through HISx Messages

HC25-01

Unable to open xxxxxxxx file

Reason:
The open for file xxxxxxxx failed. The program terminates.

Action:
Verify that the DD statement xxxxxxxx is present in the JCL and has the correct
information.

HC25-02

REPORTx is empty

Reason:
The file specified by REPORTx, where x is 1 or 2, contains no data. The program
terminates.

Action:
Verify that DD statement xxxxxxxx contains the correct information.

HC25-03

REPORTx First record is not a control record

Reason:
The first record in the file specified by REPORTx, where x is 1 or 2, is not a valid control
record. The program terminates.

Action:
Verify the following:
■ DD statement REPORTx contains the correct information.
■ SASSHIS8 report 25 created the file.

Chapter 5: CDSI - RSCx Messages 1097

HC25 Through HISx Messages

HC25-04

REPORTx Control data does not match

Reason:
The first record in files REPORT1 and REPORT2 contains control data that does not
match. The program terminates.

Action:
Verify that files REPORT1 and REPORT2 were created with the same report type in the
SASSHIS8 report 25 control card. If the reports contain JES data, verify that the data is
for the same JES type (JES2/JES3).

HC25-05

REPORTx Missing initial header records

Reason:
The initial header records following the control record in the file specified by REPORTx,
where x is 1 or 2, are missing or incomplete. The program terminates.

Action:
Verify the following:
■ DD statement REPORTx contains the correct information.
■ SASSHIS8 report 25 created the file.

HC25-06

REPORTx No detail records

Reason:
The file specified by REPORTx, where x is 1 or 2, contains no report detail records. The
program terminates.

Action:
Verify the following:
■ DD statement REPORTx contains the correct information.
■ SASSHIS8 report 25 created the file.

1098 Message Reference Guide

 HC25 Through HISx Messages

HC25-07

REPORTx Data out of sequence

Reason:
The file specified by REPORTx, where x is 1 or 2, contains no report detail records. The
program terminates.

Action:
Verify the following:
■ DD statement REPORTx contains the correct information.
■ SASSHIS8 report 25 created the file.

HC25-08

STORAGE OBTAIN for workarea failed

Reason:
STORAGE OBTAIN for a required work area has failed. The program terminates.

Action:
Increase REGION= and retry. If problem persists contact your installation specialist for
assistance.

HC25-10

Load failed for xxxxxxxx

Reason:
A LOAD failed for the indicated module. This module is required for the report. The
program terminates.

Action:
Verify that the indicated module is in a library accessible by the metrics compare utility
JCL.

Chapter 5: CDSI - RSCx Messages 1099

HC25 Through HISx Messages

HC25-11

L2DATES Error converting dates

Reason:
An error occurred converting dates in program L2DATES. The program terminates. This
message indicates an internal error and should not occur.

Action:
For assistance, contact CA Support at ca.com/support.

HC25-12

Report loop detected

Reason:
A report line has repeated too many times. A loop is suspected. The program
terminates. This error indicates an internal error and should not occur.

Action:
Verify that SASSHIS8 report 25 created the files for REPORT1 and REPORT2. For
assistance, contact CA Support at ca.com/support.

HC25-99

Terminating because of prior error

Reason:
The metrics compare utility is terminating because of a prior error. No report is
generated. The report program terminates.

Action:
Look for previous error messages in the job output and act as indicated for those
messages.

1100 Message Reference Guide

 HC25 Through HISx Messages

HEDT-01

xxxxxxxx SEVERITY SCALE NOT FOUND.

Reason:
This message will appear whenever the required Severity Scale (used by SASSHR04 and
SASSHR05) cannot be found.

Action:
The severity scale module name suffix (xx) in the control statement refers to module
name SASSDSxx, and it must be on the CA Workload Automation SE load library. If it is
there, be sure the module suffix specified on the control statement is correct.

HEDT-02

xxxxxxxx SEVERITY SCALE HAS INVALID SIGN.

Reason:
This message will appear whenever one or more severity levels contain an invalid sign
(not a + or a -).

Action:
Correct the Severity Scale and rerun the job. See CAL2OPTN member AL2UM31.

HEDT-03

xxxxxxxx SEVERITY SCALE HAS NON-NUMERIC.

Reason:
This message will appear whenever one or more severity levels contain a non-numeric
entry.

Action:
Correct the Severity Scale and rerun the job. See CAL2OPTN member AL2UM31.

Chapter 5: CDSI - RSCx Messages 1101

HC25 Through HISx Messages

HEDT-04

xxxxxxxx SEVERITY SCALE HAS INVALID ID.

Reason:
This message will appear whenever the ID code in the Severity Scale does not match the
last two characters of the module name of the Severity Scale.

Action:
Correct the Severity Scale and rerun the job. See CAL2OPTN member AL2UM31.

HEDT-05

xxxxxxxx SEVERITY SCALE NOT IN SEQUENCE.

Reason:
This message will appear whenever one or more severity entries in the Severity Scale
are not in ascending sequence by value.

Action:
Correct the Severity Scale and rerun the job. See CAL2OPTN member AL2UM31.

HE00-04

I/O ERROR ON LOG INPUT...FORCED EOF.

Reason:
An I/O error occurred during a GET from the log data input. The report data may be
truncated.

Action:
Rerun the job. If the error reoccurs, contact your installation specialist for assistance.

HE00-05

INVALID RECORD LENGTH, RECORD SKIPPED.

Reason:
A record on the log, history or archive file has an invalid length. The record is ignored
and the program continues to read the next record.

Action:
None.

1102 Message Reference Guide

 HC25 Through HISx Messages

HIS5-01

PARM=

Reason:
This message will appear whenever the PARM option is used.

Action:
None.

HIS5-02

ERRORS FOUND - RUN HALTED

Reason:
This message will appear whenever an unrecoverable error is found to exist. This
message is always preceded by an explanation of the errors.

Action:
Correct the error and resubmit the job.

HIS5-03

INVALID PURGE DATE

Reason:
This message will appear if the Julian date (yyddd) field in PARM is found to be in error.

Action:
Correct the error and resubmit the job.

HIS5-04

INVALID SORT SIZE

Reason:
This message will appear if the Sort Size (nnnnn) field in PARM is found to be in error.

Action:
Correct the error and resubmit the job.

Chapter 5: CDSI - RSCx Messages 1103

HC25 Through HISx Messages

HIS5-05

SORT COMPLETION INVALID, RC=nnnn

Reason:
An error was detected by the Internal Sort and a bad return code was issued.

Action:
Correct the error and resubmit the job.

HIS5-06

LOG HISTORY FILE SEQUENCE ERROR

Reason:
Log history records are not in the correct order. May have been dumping the disk Log
file currently in use or the previous dump run was in error.

Action:
Correct the error and resubmit.

HIS5-07

ERROR ON LOG DUMP FILE

Reason:
Error has occurred reading the disk Log file. May have been dumping the disk Log file
currently in use or the previous dump run was in error.

Action:
Correct the error and resubmit.

HIS6-01

PARM= PURGE=yyddd,yyddd

Reason:
This message will always appear to show the period of time for which log records are to
be deleted.

Action:
None.

1104 Message Reference Guide

 HC25 Through HISx Messages

HIS6-02

INVALID KEYWORD.

Reason:
This message will appear if the first characters of PARM data are not PURGE.

Action:
Correct the PARM data and resubmit the job.

HIS6-03

FROM DATE NOT VALID.

Reason:
This message will appear if the FROM date was found to be in error.

Action:
Correct the FROM date and resubmit the job.

HIS6-04

THRU DATE NOT VALID.

Reason:
This message will appear if the THRU date was found to be in error.

Action:
Correct the THRU date and resubmit the job.

HIS6-05

FROM DATE IS GREATER THAN THRU DATE.

Reason:
This message will appear if the FROM date is found to be greater than the THRU date.

Action:
Correct the date field in error and resubmit the job.

Chapter 5: CDSI - RSCx Messages 1105

HC25 Through HISx Messages

HIS6-10

ERRORS FOUND - RUN ENDED.

Reason:
This message will appear if one or more of the error messages HIS6-01 through HIS6-05
are present.

Action:
Correct the error and resubmit the job.

HIS8-01

EDIT MODULE NOT FOUND.

Reason:
The edit module SASSHSxx (xx=report ID) was not found in the CA Workload Automation
SE load library.

Action:
Make the required SASSHSxx module available to the system and rerun the job.

HIS8-02

EXTRACT MODULE NOT FOUND.

Reason:
The extract module SASSHExx (xx=report ID) was not found in the CA Workload
Automation SE load library.

Action:
Make the required SASSHExx module available and rerun the job.

HIS8-03

REPORT MODULE NOT FOUND.

Reason:
The report module SASSHRxx (xx=report ID) was not found in the CA Workload
Automation SE load library.

Action:
Make the required SASSHRxx module available and rerun the job.

1106 Message Reference Guide

 HC25 Through HISx Messages

HIS8-04

DUPLICATED CONTROL CARD.

Reason:
The control statement shown duplicates a previous one.

Action:
Change either the request ID or the report ID in the control statements involved to
eliminate the duplication and rerun the job.

HIS8-05

E15 DRIVER SASSHE00 NOT FOUND.

Reason:
The extract driver SASSHE00 was not found in the library.

Action:
Make sure this module is in the CA Workload Automation SE load library, which must be
referenced by the STEPLIB DD in the SASSHIS8 JCL.

HIS8-06

E35 DRIVER SASSHR00 NOT FOUND.

Reason:
The report driver SASSHR00 was not found in the library.

Action:
Make sure this module is in the CA Workload Automation SE load library, which must be
referenced by the STEPLIB DD in the SASSHIS8 JCL.

HIS8-07

TOO MANY REPORTS REQUESTED.

Reason:
More than 50 reports were requested.

Action:
Break up the run into multiple runs and rerun the job.

Chapter 5: CDSI - RSCx Messages 1107

HC25 Through HISx Messages

HIS8-08

SORT NOT SUCCESSFULLY COMPLETED.

Reason:
The internal sort was not successful.

Action:
Determine the nature of the problem and correct it, if possible. If not possible to
correct, contact your installation specialist for assistance.

HIS8-09

NO CONTROL CARD ERRORS DETECTED.

Reason:
The control statement has been accepted.

Action:
None.

HIS8-10

ERRORS DETECTED - EXECUTION HALTED.

Reason:
One of the messages (with the exception of HIS8-09) in this message list was issued.

Action:
Correct all the errors indicated and rerun the job.

HIS8-11

FROM TIME NOT VALID.

Reason:
The FROM time is not valid.

Action:
Correct the FROM time or eliminate it and rerun the job.

1108 Message Reference Guide

 HC25 Through HISx Messages

HIS8-12

FROM DATE NOT VALID.

Reason:
The FROM date is not valid.

Action:
Correct the FROM date or eliminate it and rerun the job.

HIS8-13

THRU TIME NOT VALID.

Reason:
The THRU time is not valid.

Action:
Correct the THRU time or eliminate it and rerun the job.

HIS8-14

THRU DATE NOT VALID.

Reason:
The THRU date is not valid.

Action:
Correct the THRU date or eliminate it and rerun the job.

HIS8-15

FROM PERIOD GREATER THAN THRU PERIOD.

Reason:
The FROM date and time combination is greater than the THRU date and time
combination.

Action:
Correct the date/time combinations or eliminate them and rerun the job.

Chapter 5: CDSI - RSCx Messages 1109

HC25 Through HISx Messages

HIS8-16

PARM= DATA IS INVALID.

Reason:
The data entered in the PARM operand of the EXEC statement contains an error.

Action:
Correct the error and rerun the job.

HIS8-17

NO INPUT REPORT REQUESTS FOUND.

Reason:
No requests for reports were found on control statements.

Action:
Correct control statements to specify reports that you want.

HIS8-18

CONTROL CARD EDIT FINAL RESULTS.

Reason:
Edit results are provided after this message.

Action:
None.

HIS8-19

SASSMASK MODULE NOT LOADED

Reason:
Module SASSMASK could not be loaded.

Action:
Make sure this module is in the CA Workload Automation SE load library, which must be
referenced by the STEPLIB DD in the SASSHIS8 JCL.

1110 Message Reference Guide

 HLP0 Through HS0x Messages

HLP0 Through HS0x Messages

HLP0-00

HELP REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request has been successfully processed.

Action:
None.

HLP0-01

text

Reason:
An error occurred while processing the HELP command as indicated by text. The values
for text are detailed under message SM50-14.

Action:
Verify that the Help data set was allocated during CA Workload Automation SE
installation, and that a JCL statement in the initialization file defines the data set with an
INDEX=255. Verify that the volume on which the data set resides is available to CA
Workload Automation SE. Also, see message SM50-14 for other possible actions.

HLP0-02

MEMBER ...membername WAS NOT FOUND ON PDS...datasetname, VOLSER=volume

Reason:
The indicated member was not found on the data set specified. The data set resides on
the volume noted.

Action:
Verify that the specified membername, datasetname, and volume are correct. If all are
correct, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1111

HLP0 Through HS0x Messages

HLP0-03

THE JCL INDEX TABLE IS NOT AVAILABLE

Reason:
No JCL statements were defined in the initialization file for CA Workload Automation SE.
The HELP command requires the HELP data set to be defined on a JCL statement in the
initialization file with INDEX=255.

Action:
Add a JCL statement to the initialization file for the HELP data set using INDEX=255; then
reinitialize CA Workload Automation SE.

HLP0-04

THE HELP DATASET IS NOT IN THE JCL INDEX TABLE.

Reason:
An attempt was made to access the Help data set and the data set is not in the JCL
statements in the initialization file.

Action:
A JCL statement must be added to the initialization file with INDEX=255. This is the index
number reserved for the Help data set.

HLP0-05

function IS NOT A DEFINED APPLICATION OR COMMAND

Reason:
The function value specified is an incorrect request for the HELP command.
Note: For more information about the HELP command, its format, and the options
available, see the Command Reference Guide.

Action:
Correct the input request and try again.

1112 Message Reference Guide

 HLP0 Through HS0x Messages

HLPM-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Awaiting your choice of HELP functions.

Action:
Select a tutorial by entering the values that you want and pressing Enter. To transfer to
another menu or formatted input panel, enter a FUNCTION value. Otherwise, position
the cursor to the top line and enter a command.

HLPM-02

MUST SPECIFY INDEX, AN APPLICATION OR A COMMAND

Reason:
One of the indicated fields must be provided for any request.

Action:
Provide a field and retry.

HLPM-05

INVALID VALUE FOR FIELD: xxxxxxxx

Reason:
An error was detected with the contents of the indicated field. The cursor will be
positioned to that field.

Action:
Correct and retry.

Chapter 5: CDSI - RSCx Messages 1113

HLP0 Through HS0x Messages

HR25-01

Log file incomplete, no xxxxxxxx Metrics records

Reason:
The input log file to the SASSHIS8 25 report does not contain any metrics records for
type xxxxxxxx. The type can be daily’ hourly, or minute. No report is generated. The
report program terminates.

Action:
Verify the following:
■ DDNAME UCC7HIST points to the correct log data set.
■ The correct time interval has been requested through the SASSHIS8 25 report
control statement.
■ Metrics data collection was turned on in CA Workload Automation SE for the
requested time period.

HR25-02

No log records selected

Reason:
The input log file to the SASSHIS8 25 report does not contain any metrics or statistics
records. No report is generated. The report program terminates.

Action:
Verify the following:
■ DDNAME UCC7HIST points to the correct log data set.
■ The correct time interval has been requested through the SASSHIS8 25 report
control statement.
■ Metrics data collection was turned on in CA Workload Automation SE for the
requested time period.

1114 Message Reference Guide

 HLP0 Through HS0x Messages

HR25-03

xxxxxxxx OPEN error, file not created, processing continues

Reason:
The open for file xxxxxxxx failed. The file is not created, but the metrics report is still
produced.

Action:
Verify that the DD statement xxxxxxxx has the correct information.

HR25-04

STORAGE OBTAIN failed

Reason:
STORAGE OBTAIN for a required work area has failed. No report is generated. The
report program terminates.

Action:
Increase REGION= and retry. If problem persists contact your installation specialist for
assistance.

HR25-05

Log date out of sequence

Reason:
The input log file contains data out of sequence. No report is generated. The report
program terminates.

Action:
Contact your installation specialist for assistance.

HR25-10

Load failed for xxxxxxxx

Reason:
A LOAD failed for the indicated module. This module is required for the Metrics report.
No report is generated. The report program terminates.

Action:
Verify that the indicated module is in a library accessible by the SASSHIS8 JCL.

Chapter 5: CDSI - RSCx Messages 1115

HLP0 Through HS0x Messages

HR25-11

Error converting dates

Reason:
An error occurred converting dates in program L2DATES. No report is generated. The
report program terminates. This message indicates an internal error and should not
occur.

Action:
For assistance, contact CA Support at ca.com/support.

HR25-13

xxxxxxxx DD statement missing, file not created, processing continues

Reason:
The indicated DD statement is missing in the SASSHIS8 JCL. The file is not created but
the metrics report is still produced.

Action:
Add the indicated DD statement to the SASSHIS8 JCL and rerun the job.

HR25-14

xxxxxxxx create requires report type = A, file not created, processing continues

Reason:
A SASSHIS8 control card option requested creation of the file identified by xxxxxxxx, but
the report type requested in the control card was not A (ALL). This file is created only
when all reports are requested. The file is not created, but the metrics report is still
produced.

Action:
If you want the file created, change the report type in the control card to A for ALL;
otherwise no action is required.

1116 Message Reference Guide

 HLP0 Through HS0x Messages

HR25-15

Unknown record type(x), ignoring

Reason:
An invalid record type was encountered when creating the CSV file. x identifies the type.
The record is skipped, and processing continues. This message indicates an internal
error and should not occur.

Action:
For assistance, contact CA Support at ca.com/support.

HS01-01

INVALID SYSTEM ID

Reason:
The system ID contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS01-02

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct and rerun the job.

HS02-01

INVALID OPERATOR ID

Reason:
The operator ID contains an error.

Action:
Correct or eliminate this operand and rerun the job.

Chapter 5: CDSI - RSCx Messages 1117

HLP0 Through HS0x Messages

HS02-02

INVALID TERMINAL ID

Reason:
The terminal ID contains an error.

Action:
Correct the error and rerun the job.

HS02-03

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct and rerun the job.

HS02-04

INVALID SCREEN PAGING OPTION

Reason:
The panel paging option contains an invalid value.

Action:
Correct or eliminate this operand and rerun the job.

HS02-05

INVALID BLANK LINE OPTION

Reason:
The blank line option contains an invalid value.

Action:
Correct or eliminate this operand and rerun the job.

1118 Message Reference Guide

 HLP0 Through HS0x Messages

HS03-01

INVALID RECORD TYPE

Reason:
The record type contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

HS03-02

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

HS04-01

INVALID JOB NAME

Reason:
The job name value contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS04-02

INVALID CA-7 NUMBER

Reason:
The CA Workload Automation SE number contains an error.

Action:
Correct or eliminate this operand and rerun the job.

Chapter 5: CDSI - RSCx Messages 1119

HLP0 Through HS0x Messages

HS04-03

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

HS04-04

INVALID TIME ZONE OPTION

Reason:
The only valid entries for time zone are 7, E, and blank.

Action:
Correct or eliminate this operand and rerun the job.

HS05-01

INVALID STATION ID

Reason:
The workstation name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS05-02

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

1120 Message Reference Guide

 HLP0 Through HS0x Messages

HS05-03

INVALID NETWORK ID

Reason:
The network name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS05-04

INVALID SUB-ID

Reason:
The sub-ID contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS05-05

INVALID CA-7 NUMBER

Reason:
The CA Workload Automation SE number contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS05-06

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

Chapter 5: CDSI - RSCx Messages 1121

HLP0 Through HS0x Messages

HS06-01

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS06-02

INVALID SYSTEM ID

Reason:
The system ID contains an error.

Action:
Correct and rerun the job.

HS06-03

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

HS06-04

INVALID TIME ZONE OPTION

Reason:
The only valid entries for time zone are 7, E, and blank.

Action:
Correct or eliminate this operand and rerun the job.

1122 Message Reference Guide

 HLP0 Through HS0x Messages

HS07-01

INVALID STATION ID

Reason:
The workstation name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS07-02

INVALID NETWORK ID

Reason:
The network name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS07-03

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS07-04

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

Chapter 5: CDSI - RSCx Messages 1123

HLP0 Through HS0x Messages

HS09-01

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS09-02

INVALID CROSS PLATFORM JOB TYPE

Reason:
The Cross Platform job type contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS09-03

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

HS09-04

INVALID TIME ZONE OPTION

Reason:
The only valid entries for time zone are 7, E, and blank.

Action:
Correct or eliminate this operand and rerun the job.

1124 Message Reference Guide

 HLP0 Through HS0x Messages

HS10-01

INVALID REPORT TYPE

Reason:
The report type contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

HS11-01

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS11-02

INVALID PARAMETERS FLAG

Reason:
The PARMnn ID flag contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

HS11-03

INVALID RETURN CODE FLAG

Reason:
The preprocess or process return code flag contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

Chapter 5: CDSI - RSCx Messages 1125

HLP0 Through HS0x Messages

HS11-04

INVALID SORT SELECTION

Reason:
The sort parameters contain an invalid key value.

Action:
Correct the sort key in error and rerun the job.

HS13-01

INVALID JOB NAME

Reason:
The job name contains an error.

Action:
Correct or eliminate this operand and rerun the job.

HS13-02

INVALID TIME ZONE OPTION

Reason:
The only valid entries for time zone are 7, E, and blank.

Action:
Correct or eliminate this operand and rerun the job.

HS20-01

INVALID THRESHOLD.

Reason:
The threshold specified is not a three-digit numeric.

Action:
Correct the threshold and rerun the job.

1126 Message Reference Guide

 HLP0 Through HS0x Messages

HS21-01

INVALID THRESHOLD.

Reason:
The threshold specified is not a three-digit numeric.

Action:
Correct the threshold and rerun the job.

HS21-02

INVALID EXCEPTION.

Reason:
The only valid entry in the exception field is a blank or "E".

Action:
Correct the exception field and rerun the job.

HS21-03

EXCEPTION REQUIRES THRESHOLD.

Reason:
The exception field contains an E but the threshold field is blank.

Action:
Either add a threshold or blank the exception field and rerun the job.

HS22-01

INVALID JOB NAME

Reason:
The job name field must contain at least one character before the mask character.

Action:
Either fix the mask or blank the job name field and rerun the job.

Chapter 5: CDSI - RSCx Messages 1127

HLP0 Through HS0x Messages

HS22-02

INVALID EXCEPTION FLAG

Reason:
The only valid entry in the exception field is E or a blank.

Action:
Correct the exception field and rerun the job.

HS23-01

INVALID THRESHOLD.

Reason:
The threshold specified is not a three-digit numeric.

Action:
Correct the threshold and rerun the job.

HS24-01

INVALID THRESHOLD.

Reason:
The threshold specified is not a three-digit numeric.

Action:
Correct the threshold and rerun the job.

HS25-01

INVALID REPORT TYPE

Reason:
The report type contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

1128 Message Reference Guide

 HLP0 Through HS0x Messages

HS25-02

DATE RANGE EXCEEDS MAXIMUM ALLOWED

Reason:
The difference between the Thru date/time and From date/time exceeds 31 days.

Action:
Correct the From date/time values, the Thru date/time values, or both. Rerun the job.

HS25-03

LOAD FAILED FOR MODULE L2DATES

Reason:
A LOAD for module L2DATES has failed. The module is required.

Action:
Verify that the indicated module is in a library accessible by the SASSHIS8 JCL.

HS25-04

ERROR CONVERTING DATES WITH L2DATES

Reason:
An error occurred converting dates in program L2DATES. This message indicates an
internal error and should not occur.

Action:
For assistance, contact CA Support at ca.com/support.

HS25-05

INVALID CREATE COMPARE FILE FLAG

Reason:
The create compare file flag contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

Chapter 5: CDSI - RSCx Messages 1129

HLP0 Through HS0x Messages

HS25-06

INVALID CREATE CSV FILE FLAG

Reason:
The create CSV file flag contains a value that is not valid.

Action:
Correct or eliminate this operand and rerun the job.

HS25-07

INVALID REPORT TYPE FOR CSV CREATION

Reason:
The report type must be A (ALL) to create a CSV file.

Action:
Correct the report type or create CSV flag operand and rerun the job.

HS50-01

INVALID COMMAND TYPE

Reason:
The command type contains an error.

Action:
Correct and rerun the job.

HS50-02

INVALID TIME ZONE OPTION

Reason:
The only valid entries for time zone are 7, E, and blank.

Action:
Correct or eliminate this operand and rerun the job.

1130 Message Reference Guide

 INxx Messages

INxx Messages
INQB-01

FILE CONTROL RECORD IS NOT FIRST RECORD

Reason:
The control record created during the CA Workload Automation SE queue unload was
not found as the first record. This message is followed by CA-7.935.

Action:
Make sure the queues were successfully unloaded previously. Also be sure that the
correct file is being used as input.

INQB-02

FILE TO RELOAD QUEUES IS NOT COMPLETE

Reason:
The control record created during the CA Workload Automation SE queue unload was
not found to be the last record.

Action:
None, this is only a warning.

Chapter 5: CDSI - RSCx Messages 1131

INxx Messages

INQB-03

I/O ERROR ON QUEUE FILE...x Q=y

Reason:
An I/O error was detected while attempting to reload the CA Workload Automation SE
queue. x is a return code from a CA Workload Automation SE internal macro. y is the
queue number that was being accessed. This message is followed by CA-7.935.
1
Preprocess queue
2
Request queue
3
Ready queue
4
Active queue
5
Postprocess queue
6
Prior-run queue

Action:
Check system console log for I/O error. May require reallocating the queue and running
the MOVQ again. If still unsuccessful contact your installation specialist for assistance.

INQB-04

UNEXPECTED EOF ON QUEUE FILE

Reason:
The file space for reloading the CA Workload Automation SE queues has been
exhausted. This message is followed by message CA-7.935.

Action:
Increase the space allocation for the CA Workload Automation SE queue files and
RESTART CA Workload Automation SE.

1132 Message Reference Guide

 INxx Messages

INQB-05

CA-7 HIJOBNM EXCEEDED xxxxxx TIMES

Reason:
During a MOVQ operation, at least one job was found in the CA Workload Automation
SE queues whose CA Workload Automation SE job number was greater than the
HIJOBNM. xxxxxx is the number of jobs found with this condition.

Action:
The HIJOBNM value has apparently been changed to a lower value. Any jobs using the
larger numbers will run all right. The numbers are not reused.

INQB-05

VRM VSAM RESOURCE FILE DD (CA7RSRC) NOT FOUND

Reason:
The VRM database file specified using the CA7RSRC DD was not found during MOVQ
(Move queue) startup processing.

Action:
Include the VRM database component in the CA Workload Automation SE execution
procedure using the CA7RSRC DD statement and restart CA Workload Automation SE.

INQB-06

ERROR OPENING VRM RESOURCE FILE

Reason:
An error has occurred during MOVQ (Move queue) startup processing while attempting
to open the VRM VSAM database component.

Action:
Ensure that the correct file is specified under the CA7RSRC DD statement in the CA
Workload Automation SE execution JCL procedure and restart CA Workload Automation
SE.

Chapter 5: CDSI - RSCx Messages 1133

INxx Messages

INQB-07

ERROR OPENING VRM DUMP FILE DD (CA7VDMP)

Reason:
An error has occurred during MOVQ (Move queue) startup processing while attempting
to open the VRM Dump queue file ddname CA7VDMP.

Action:
Specify the VRM Dump queue file using the CA7VDMP DD statement in the CA Workload
Automation SE execution JCL procedure and restart CA Workload Automation SE.

INQB-08

INVALID CONTROL RECORD FOUND IN VRM DUMP FILE DD - CA7VDMP

Reason:
The VRM control record must be the first record found when processing the VRM Dump
queue file during reload.

Action:
Verify that the correct file was specified under the CA7VDMP DD statement in the CA
Workload Automation SE execution JCL procedure and restart CA Workload Automation
SE.

INQB-09

CA-7 QUEUE DUMP FILE AND VRM DUMP FILE OUT OF SYNCH

Reason:
The CA Workload Automation SE Dump queue file control record and the VRM Dump
queue control records have mismatching date and time stamps.

Action:
Verify that the correct file name was specified under the CA7VDMP DD statement in the
CA Workload Automation SE execution JCL procedure and restart CA Workload
Automation SE.

1134 Message Reference Guide

 INxx Messages

INQB-10

INVALID LRECL FOR VRM RESOURCE FILE

Reason:
An invalid record length was found for the VRM VSAM database component. Verify that
the data set was allocated using the correct IDCAMS control statements supplied in the
CA Workload Automation SE installation JCL library member name VRMDECK.

Action:
Verify that the correct file name was specified under the CA7RSRC DD statement in the
CA Workload Automation SE execution JCL procedure and restart CA Workload
Automation SE.

INQB-11

VSAM PROCESSING ERROR - FUNCTION = x RC = x FDBK = (xxxx)

Reason:
A VSAM I/O error has occurred during MOVQ (Move queue) startup processing.

Action:
Contact your installation specialist for assistance.

INQB-20

SASSXXQB USER EXIT CALLED

Reason:
Program SASSINQB called user exit SASSXXQB.

Action:
None.

INQB-25

ARF VSAM FILE DD (CA7ARFDB) NOT FOUND

Reason:
The ARF database DD statement could not be found.

Action:
You need to add the ARF database to the CA Workload Automation SE JCL.

Chapter 5: CDSI - RSCx Messages 1135

INxx Messages

INQB-26

ERROR OPENING ARF RESOURCE FILE

Reason:
A nonzero return code was found during OPEN to the ARF database.

Action:
Check for messages on the console for VSAM errors.

INQB-29

CA-7 QUEUE DUMP FILE AND ARF DUMP FILE OUT OF SYNCH

Reason:
The timestamps on the queue dump file and the ARF dump file are different.

Action:
Contact your installation specialist for assistance.

INQB-40

nnnnn VRM ACTIVE RECORDS DELETED

Reason:
At least one VRM active record (X record) was found and the job was not in the queue.
The nnnnn is the number of these records found. A log record is written for each job.

Action:
None.

INQD-01

CORE FOR WORKAREA UNAVAILABLE

Reason:
The module used to unload the CA Workload Automation SE queues (SASSINQD) could
not find enough space for its required work area. This message is followed by message
CA-7.934.

Action:
Retry with a larger region size for CA Workload Automation SE.

1136 Message Reference Guide

 INxx Messages

INQD-02

I/O ERROR ON QUEUE FILE...x Q=y

Reason:
An I/O error was detected while attempting to unload the CA Workload Automation SE
queue. x is a return code from a CA Workload Automation SE internal macro. y is the
queue number that was being accessed. This message is followed by message CA-7.934.
See INQB-03 for queue numbers and names.

Action:
Contact your installation specialist for assistance.

INQD-03

FILE SPACE FOR Q UNLOAD EXCEEDED

Reason:
The file space on UCC7QDMP had been exceeded. This message is followed by message
CA-7.934.

Action:
Increase the space allocation for CA Workload Automation SE QDMP. Bring CA
Workload Automation SE up with a WARM or ERST type start and retry the DMPQ
shutdown.

INQD-04

QDMP FILE OPEN FAILED

Reason:
An open failed on the file defined by the UCC7QDMP DD when dumping of queues was
requested during shutdown.

Action:
Check attributes and JCL for dump file, correct and retry.

Chapter 5: CDSI - RSCx Messages 1137

INxx Messages

INQD-05

QDMP (VRM) FILE OPEN FAILED

Reason:
While doing a CA Workload Automation SE shutdown processing that includes a DMPQ,
the OPEN to the VRM dump queue data set (ddname of CA7VDMP) has failed.

Action:
If the CA7VDMP DD statement is missing, change the CA Workload Automation SE JCL to
add it, and start CA Workload Automation SE (WARM or ERST). The CA Workload
Automation SE shutdown using DMPQ can now be done.

INQD-09

VSAM PROCESSING ERROR ON VRM FILE...x RC = x FDBK = xxxxxxxx

Reason:
A VSAM I/O error occurred during DMPQ (Dump queue) shutdown while processing
VRM active resource records.

Action:
Save the console messages associated with this message and contact your installation
specialist for assistance.

INQD-10

(oooo) ARFIO ERROR : xxxxxxxx/yyyyyyyy/zzzzzzzz

Reason:
One of several ARFIO commands in program SASSINQD got a non-zero return code. The
offset into SASSINQD is oooo, the first four bytes of the reason code are xxxxxxxx, the
second four bytes of the reason code are yyyyyyyy, and the third four bytes of the
reason code are zzzzzzzz.

Action:
Contact your installation specialist for assistance.

1138 Message Reference Guide

 JCKn Messages

INWC-01

SASSINQB (QUEUE RELOAD) MODULE NOT FOUND

Reason:
The module required for the MOVQ function was not found. This message is followed by
message CA-7.935.

Action:
Make sure SASSINQB exists on a load library referenced by the STEPLIB DD statement in
the CA Workload Automation SE online JCL.

JCKn Messages
JCK0-T1

LINK 1 COMPLETE

Reason:
First link of the interface is complete.

Action:
This is an informational message for testing purposes only.

JCK0-T2

LINK 2 COMPLETE

Reason:
Second link of the interface is complete.

Action:
This is an informational message for testing purposes only.

Chapter 5: CDSI - RSCx Messages 1139

JCKn Messages

JCK0-T3

LINK 3 COMPLETE

Reason:
Third link of the interface is complete.

Action:
This is an informational message for testing purposes only.

JCK0-T4

LINK 4 COMPLETE

Reason:
Fourth link of the interface is complete.

Action:
This is an informational message for testing purposes only.

JCK0-01

INPUT DATA SET OPEN FAILURE

Reason:
Unable to open DD=INPUT. A condition code of 8 is set.

Action:
Check that DD=INPUT is correctly specified.

JCK0-02

SYSIN DATA SET OPEN FAILURE

Reason:
Unable to open DD=SYSIN. A condition code of 8 is set.

Action:
Check that DD=SYSIN is correctly specified.

1140 Message Reference Guide

 JCKn Messages

JCK0-03

BAD RETURN FROM SASSBSTR, RC=xxxx

Reason:
Module SASSBSTR completed with a nonzero return code. The RC value gives the error
code. See WTO messages for a further explanation of the error code.

Action:
Diagnose the problem using the WTO messages and take appropriate action.

JCK0-04

ERROR LINKING TO SASSBSTR, ABEND CODE=xxx

Reason:
The link to module SASSBSTR failed. The ABEND CODE value gives the error code. See
the IBM MVS System Codes manual for a further explanation of the error code.

Action:
Diagnose the problem using the IBM MVS System Codes manual and take appropriate
action.

JCK0-05

ERROR LINKING TO SASSJCK1, ABEND CODE=xxx

Reason:
The link to module SASSJCK1 failed. The ABEND CODE value gives the error code. See
the IBM MVS System Codes manual for a further explanation of the error code.

Action:
Diagnose the problem using the IBM MVS System Codes manual and take appropriate
action.

Chapter 5: CDSI - RSCx Messages 1141

JCKn Messages

JCK0-06

ERROR LINKING TO SASSJCK2, ABEND CODE=xxx

Reason:
The link to module SASSJCK2 failed. The ABEND CODE value gives the error code. See
the IBM MVS System Codes manual for a further explanation of the error code.

Action:
Diagnose the problem using the IBM MVS System Codes manual and take appropriate
action.

JCK1-01

SYSIN DATA SET OPEN FAILURE

Reason:
Unable to open DD=SYSIN. A condition code of 8 is set.

Action:
Check that DD=SYSIN is correctly specified.

JCK1-02

SYSPRINT DATA SET OPEN FAILURE

Reason:
Unable to open DD=SYSPRINT. A condition code of 8 is set.

Action:
Check that DD=SYSPRINT is correctly specified.

JCK1-03

SYSIN DATA SET EMPTY

Reason:
DD=SYSIN is empty. No /LOGON record can be passed for the interface. A condition
code of 8 is set.

Action:
Specify a /LOGON statement as the first record in DD=INPUT.

1142 Message Reference Guide

 JCKn Messages

JCK1-04

NO FORECASTED JOB OUTPUT

Reason:
No forecasted job output was available for the interface. A condition code of 8 is set.
This could be caused by all jobs that were selected being NON-EXEC jobs.

Action:
Check that the FJOB commands in DD=INPUT are correctly specified.

JCK2-01

SYSIN DATA SET OPEN FAILURE

Reason:
Unable to open DD=SYSIN. A condition code of 8 is set.

Action:
Check that DD=SYSIN is correctly specified.

JCK2-02

SYSPRINT DATA SET OPEN FAILURE

Reason:
Unable to open DD=SYSPRINT. A condition code of 8 is set.

Action:
Check that DD=SYSPRINT is correctly specified.

JCK2-03

JCLCHECK DATA SET OPEN FAILURE

Reason:
Unable to open DD=JCLCHECK. A condition code of 8 is set.

Action:
Check that DD=JCLCHECK is correctly specified.

Chapter 5: CDSI - RSCx Messages 1143

L2xxx Messages

JCK2-04

ERROR LINKING TO SASSHDAT, ABEND CODE=xxx

Reason:
The link to module SASSHDAT failed. The ABEND CODE gives the error code. See the IBM
MVS System Codes manual for a further explanation of the error code.

Action:
Diagnose the problem using the IBM MVS System Codes manual and take appropriate
action.

L2xxx Messages
L2CCIIS

Task for xxxxxxxx ended, TCBADDR=nnnnnnnn, TCBCMP=cccccccc

Reason:
The CA Workload Automation SE subtask for the XPS ROUTER ended. The TCB address
as well as the completion code are reported.

Action:
If this message appears prior to CA Workload Automation SE shutdown, then it is an
error and should be reported to your installation specialist. This message is normally
produced at CA Workload Automation SE shutdown.

L2CCIIS

EOT issued DETACH for xxxxxxxx, TCBADDR=nnnnnnnn, RC=rrrrrrrr

Reason:
The end-of-task issued a DETACH for the task that is ending.

Action:
None.

1144 Message Reference Guide

 L2xxx Messages

L2CCIIT

Task for xxxxxxxx ended, TCBADDR=nnnnnnnn, TCBCMP=cccccccc

Reason:
The CA Workload Automation SE subtask for the XPS TRACKER ended. The TCB address
as well as the completion code are reported.

Action:
If this message appears prior to CA Workload Automation SE shutdown, then it is an
error and should be reported to your installation specialist. This message is normally
produced at CA Workload Automation SE shutdown.

L2CCIIT

EOT issued DETACH for xxxxxxxx, TCBADDR=nnnnnnnn, RC=rrrrrrrr

Reason:
The end-of-task issued a DETACH for the task that is ending.

Action:
None.

L2CCILET

CCI Listener for xxxxxxxx ended, TCBADDR=nnnnnnnn, TCBCMP=cccccccc

Reason:
The CA Workload Automation SE subtask for a CCI listener ended. The TCB address as
well as the completion code are reported.

Action:
If this message appears prior to CA Workload Automation SE shutdown, then it is an
error and should be reported to your installation specialist. This message is normally
produced at CA Workload Automation SE shutdown.

Chapter 5: CDSI - RSCx Messages 1145

L2xxx Messages

L2CCILET

EOT issued DETACH for xxxxxxxx, TCBADDR=nnnnnnnn, RC=rrrrrrrr

Reason:
The end-of-task issued a DETACH for the task that is ending.

Action:
None.

L2TROUTR

SDWA at nnnnnnnn

Reason:
The recovery routine for a CA Workload Automation SE subtask detected an error. The
message displays the SDWA address.

Action:
None.

L2TROUTR

PSW nnnnnnnn nnnnnnnn

Reason:
The recovery routine for a CA Workload Automation SE subtask detected an error. The
message displays the PSW.

Action:
None.

L2TROUTR

ABEND CODE nnnnnnnn

Reason:
The recovery routine for a CA Workload Automation SE subtask detected an error. The
message displays the abend code.

Action:
None.

1146 Message Reference Guide

 MLRF Through MNU0 Messages

L2TROUTR

ESTAE R15=nnnnnnnn R0=nnnnnnnn

Reason:
The recovery routine for a CA Workload Automation SE subtask detected an error. The
message displays the contents of the ESTAE exit's R15 and R0.

Action:
None.

MLRF Through MNU0 Messages

MLRF-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Awaiting your choice of APA graphing functions.

Action:
Display a graph by entering the values that you want and pressing Enter. To transfer to
another menu or formatted input panel, enter a FUNCTION value. Otherwise, position
the cursor to the top line and enter a command.

MLRF-01

NOT ENOUGH INFORMATION

Reason:
The fields completed do not fully define a valid APA function.

Action:
Review documentation and enter fields required for whatever function is wanted.

Chapter 5: CDSI - RSCx Messages 1147

MLRF Through MNU0 Messages

MLRF-02

AT LEAST 1 ID IS REQUIRED

Reason:
For function value G, at least one graph ID must be given.

Action:
Provide graph IDs that you want and press Enter.

MLRF-06

GLINE VALUE IS INVALID FOR PRIM GRAPHS

Reason:
At least one of the graph IDs given is for a PRIM type of graph but the value entered for
GLINE is for a comparison type graph.

Action:
Correct graph IDs or GLINE value and press Enter.

MLRF-07

AT LEAST 1 ID HAS NO CALCULATION DEFINED

Reason:
At least one of the graph IDs given has no calculation value predefined for it and no
GLINE value entered. The cursor is positioned at the GLINE field.

Action:
Correct graph IDs or GLINE value and press Enter.

MLRF-11

INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Reason:
An invalid value was entered. The cursor will also be positioned at the field in question.

Action:
Correct the value in the indicated field and press Enter.

1148 Message Reference Guide

 MLRF Through MNU0 Messages

MLRF-12

ID IS UNKNOWN

Reason:
An invalid graph ID was entered. The cursor will also be positioned at the ID in question.

Action:
Correct the indicated ID field and press Enter.

MLRF-13

INVALID DATE RANGE

Reason:
The specified FROM values, THRU values, or both are invalid. Any of the following will
cause this error:
■ FROM date older than two years prior to today's date
■ FROM date greater than today's date
■ THRU date less than FROM date

Action:
Correct the date values and press Enter.

MLR0-00

ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Awaiting your choice of APA graphing functions.

Action:
Select a category by entering the values that you want and pressing Enter. To transfer to
another menu or formatted input panel, enter a FUNCTION value. Otherwise, position
the cursor to the top line and enter a command.

Chapter 5: CDSI - RSCx Messages 1149

MLRF Through MNU0 Messages

MLR0-05

INVALID FUNCTION VALUE

Reason:
The value entered is unknown.

Action:
Correct and retry.

MLR0-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
Security controls prohibit you from using the function you requested.

Action:
Contact your installation's security administrator if you need to gain authorization for
that function.

MLRx-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
This is an information message indicating completion of request processing.

Action:
None.

MLRx-03

REQUIRED INPUT MISSING

Reason:
Minimum input required to process the request was not given. Minimum input is
GRAPHc,ID= or GRAPHc,LIST=.

Action:
Correct by adding required data and retry.

1150 Message Reference Guide

 MLRF Through MNU0 Messages

MLRx-04

INVALID COMBINATION OF INPUT PARAMETERS.

Reason:
Mutually exclusive input parameters were used, and the module is unable to determine
which type of request or option is to be processed.

Action:
Check input and delete one or more parameters that may conflict. (Check for LIST
specification; if used it must be the only parameter.)

MLRx-05

INVALID OR OMITTED yyyyyyyy DATA

Reason:
Field identified by yyyyyyyy is invalid or missing.

Action:
Correct or enter data for field yyyyyyyy

MLRx-08

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Reason:
Module xxxxxxxx could not be loaded; nn is the code returned.

Action:
Check that the module named is on the load library and that it was link edited correctly.
Also make sure the module is defined either by an APPLCTN macro in the module
SASSPROG or by an APPLCTN statement in the initialization file. If the problem persists,
contact your installation specialist for assistance.

MLRx-10

UNRECOGNIZABLE KEYWORD IN INPUT

Reason:
An undefined keyword was found in the input request.

Action:
Correct and retry.

Chapter 5: CDSI - RSCx Messages 1151

MLRF Through MNU0 Messages

MLRx-50

STAT RECORD DATE IN ERROR

Reason:
Internal error.

Action:
Contact your installation specialist for assistance.

MLRx-51

GRAPH ID xxx NOT DEFINED

Reason:
The ID value xxx is not defined in the graph definition table specified.

Action:
Enter GRAPHc,LIST=HELP for a list of all valid graph identification numbers.

MLRx-52

UNABLE TO OPEN STATISTICS FILE

Reason:
Statistics file is not available.

Action:
Check to be sure a DD statement for UCC7STAT is in the CA Workload Automation SE JCL
and that the file was initialized with the SASSCDSI program.

MLRx-53

UNRECOVERABLE I/O ERROR ON STATISTICS FILE, UNABLE TO CONTINUE

Reason:
Probable hardware error.

Action:
Retry. If problem persists, contact your installation specialist for assistance.

1152 Message Reference Guide

 MLRF Through MNU0 Messages

MLRx-99

UNABLE TO DETERMINE ERROR CONDITION

Reason:
Probable internal error which module cannot diagnose.

Action:
Retry. If problem persists, contact your installation specialist for assistance.

MNU0-00

SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE.

Reason:
Self-explanatory.

Action:
Select a menu option.

MNU0-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
The request function cannot be done because the current security setup does not allow
it.

Action:
Change the security definition and retry the function.

Chapter 5: CDSI - RSCx Messages 1153

PCAL Messages

PCAL Messages
PCAL-01

Invalid date: text

Reason:
A perpetual calendar criteria statement contains an invalid date. The first part of the
statement in error immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-02

Invalid date range: text

Reason:
An invalid date range was encountered while generating a base calendar from perpetual
calendar criteria statements. The first part of the statement in error immediately follows
the error message. A date range should be in the following format:

date-expression-1 TO date-expression-2

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

1154 Message Reference Guide

 PCAL Messages

PCAL-03

Invalid date sequence: text

Reason:
An invalid date sequence was encountered while generating a base calendar from
perpetual calendar criteria statements. The first part of the statement in error
immediately follows the error message. A date sequence should be in the following
format:

date-expression FOR nnn

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-04

Invalid syntax: text

Reason:
A perpetual calendar criteria statement contains invalid syntax. The first part of the
statement in error immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1155

PCAL Messages

PCAL-05

Invalid verb: text

Reason:
The perpetual calendar criteria statement does not contain a valid verb. The first part of
the statement in error immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-06

Invalid DEFINE, contains reserved word: word

Reason:
A perpetual calendar criteria DEFINE statement contains the indicated reserved word.
Reserved words are not permitted on DEFINE statements.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

1156 Message Reference Guide

 PCAL Messages

PCAL-07

Invalid DEFINE, no "AS" keyword: text

Reason:
A perpetual calendar criteria DEFINE statement does not contain the AS keyword. AS is a
required keyword on the DEFINE statement. The first part of the statement in error
immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-08

Invalid DEFINE, already defined: text

Reason:
A phrase being defined in a perpetual calendar criteria DEFINE statement has already
been defined. The first part of the statement in error immediately follows the error
message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1157

PCAL Messages

PCAL-09

Need schedule/nonschedule/holiday: text

Reason:
The perpetual calendar criteria SET statement does not contain a valid action. Valid
actions are schedule/nonscheduled/holiday. The first part of the statement in error
immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-10

HOLIDAY action not valid with ALL|WEEKENDS|WEEKDAYS|HOLIDAYS: text

Reason:
The HOLIDAY action is not valid on a perpetual calendar criteria SET statement that
refers to all days, all weekdays, all weekends, or all holidays. The first part of the
statement in error immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

1158 Message Reference Guide

 PCAL Messages

PCAL-11

Error occurred on write to CALENDAR DSN in SASSPCAL module

Reason:
A base calendar was generated from a perpetual calendar and a write error occurred
while saving the base calendar to the CALENDAR PDS. The base calendar is not saved.

Action:
Contact your installation's systems programmer or installation specialist for assistance.

PCAL-12

Include member not specified

Reason:
The perpetual calendar INCLUDE criteria statement is missing a member name following
the INCLUDE keyword.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1159

PCAL Messages

PCAL-13

Include member xxxxxxxx > 8 chars

Reason:
The perpetual calendar INCLUDE criteria statement contains a member name greater
than eight characters in length.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-14

Include member xxxxxxxx not valid, nesting error

Reason:
The perpetual calendar INCLUDE criteria statement references a member name that has
already been included, and processing this member include would result in a loop
condition.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

1160 Message Reference Guide

 PCAL Messages

PCAL-15

Include member xxxxxxxx not found

Reason:
The perpetual calendar INCLUDE criteria statement references a member name that is
not found in the perpetual calendar PDS.

Action:
Perform the following actions:
■ Correct the criteria statement.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
If the problem persists, contact your installation specialist for assistance.

PCAL-16

Beg/End days not in ascending order: text

Reason:
A perpetual calendar criteria MONTHBEGIN or MONTHEND statement contains a date
that is not greater than the previous date. The first part of the statement in error
immediately follows the error message.

Action:
Perform the following actions:
■ Correct the criteria statement so that the dates are in ascending sequence.
Note: For more information about perpetual calendars, see the Systems
Programming Guide.
■ Retry the command.
■ If the problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1161

QM Messages

QM Messages
QM00-00

JOB xxxxxxxx(nnnn) POSTED FOR NORMAL COMPLETION

Reason:
The indicated job's status has been changed to complete. Normal completion processing
will begin.

Action:
None.

QM00-01

zz INVALID MACRO RETURN CODE yyyynnnn

Reason:
An error occurred on a formatted panel.

Action:
Two major actions are possible.
■ If QMxx=QM10, zz=BA and nnnn=0000, this indicates that the Scratch Work file was
not large enough to handle the command response. Check the DAIO statement in
the initialization file and increase the SCRTRK (or SWFTRK) parameter.
■ If QMxx=QM20 and zz=K2, there could be an error in the VTAM definitions. Check
for CA-7.V001 message on the system console. The PSERVIC value in a MODENT
macro definition to VTAM may be incorrect.

QM00-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

1162 Message Reference Guide

 QM Messages

QM00-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
The authorization to do this function has not been set up by your installation's security
administrator.

Action:
If this function is necessary for you to perform your duties, contact your installation
specialist for assistance.

QM00-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
An unrecognizable keyword, value, or both was input.

Action:
Correct the command and reenter.

QM00-12

FUNCTION ONLY AVAILABLE ON-LINE

Reason:
The Queue Maintenance functions are not available in batch mode.

Action:
Use an online terminal for these functions.

QM00-13

NO RECORDS FOUND

Reason:
No queue records could be found meeting the criteria imposed by the input command.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1163

QM Messages

QM00-30

REF#=jjjjrrs JOB=xxxxxxxx NW=xxxxxxxx SUB=xxxxxxxx DESC=xxxxxxxx

STATION=xxxxxxxx HAS LOGGED IN

Reason:
This message is sent to the previous station whenever a station logs in work.

Action:
None.

QM00-31

REF#=jjjjrrs JOB=xxxxxxxx NW=xxxxxxxx SUB=xxxxxxxx DESC=xxxxxxxx

STATION=xxxxxxxx HAS LOGGED OUT

Reason:
This message is sent to the next station whenever a station logs out work.

Action:
None.

QM00-32

REQUIREMENTS SCAN INCOMPLETE

Reason:
Schedule Scan has not completed initial processing on this queue record.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command.
■ After the job is canceled, DEMAND the job.

If the problem persists, contact your installation specialist for assistance.

1164 Message Reference Guide

 QM Messages

QM00-33

JOB COMPLETE OR RESTART IN PROCESS

Reason:
The job is in purge or restart processing and cannot be updated.

Action:
None.

QM00-80

LIST=Q,HIS,ALL REQUIRES JOB=

Reason:
LIST=Q, LIST=HIS, or LIST=ALL was entered along with OBJECT=object-name.

Action:
Perform one of the following actions:
■ Change to LIST=NO.
■ Use JOB=jobname instead of OBJECT=object-name.

QM00-81

ERROR RETRIEVING qqqq Q HEADER SEGMENT

Reason:
An error was encountered while trying to read the header segment for queue qqqq
where qqqq is REQ or PRRN.

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1165

QM Messages

QM00-82

HEADER SEGMENT NOT FOUND IN REQQ OR PRRNQ

Reason:
No request queue or prior run queue header segment exists for the job specified on the
command.

Action:
Verify you have the correct job name in the command. If valid, contact your installation
specialist for assistance.

QM00-83

JOB= OR OBJECT= IS REQUIRED

Reason:
The command requires either JOB=jobname or OBJECT=object-name.

Action:
Reenter the command with either a valid job name or object-name.

QM00-84

JOB nnnnn NOT FOUND ON CA7AGNT VSAM FILE

Reason:
The job indicated by job number nnnnn was not found on the CA7AGNT VSAM file.

Action:
Contact your installation specialist for assistance.

QM00-85

ERROR READING CA7AGNT VSAM FILE

Reason:
An error was encountered while trying to read the CA7AGNT VSAM file for the
object-name specified in the command.

Action:
Contact your installation specialist for assistance.

1166 Message Reference Guide

 QM Messages

QM00-86

USER NOT AUTHORIZED FOR THIS JOB

Reason:
The job is protected by a UID value, and the current user is not authorized for the job's
UID value.

Action:
Contact your installation specialist for assistance.

QM00-87

ONLY LIST=NO VALID FOR BATCH EXECUTION

Reason:
The AGFILE command was executed from a batch job and contained LIST=Q|HIS|ALL.

Action:
Perform one of the following actions:
■ Change LIST value to LIST=NO.
■ Remove the LIST parameter and take the default of LIST=NO.

QM00-88

MASKING CHARACTERS NOT ALLOWED IN JOB NAME

Reason:
The job name contains an * or ? masking character. The AGFILE command requires a
specific job name.

Action:
Reenter a specific job name without any * or ? masking characters.

Chapter 5: CDSI - RSCx Messages 1167

QM Messages

QM00-89

CANNOT SPECIFY BOTH JOB AND OBJECT

Reason:
The command was entered with both JOB=jobname and OBJECT=object-name. These
keywords are mutually exclusive.

Action:
Reenter the command with either JOB=jobname or OBJECT=object-name, but not both.

QM00-90

AGENT JOB ENVIRONMENT NOT SUPPORTED

Reason:
CA Workload Automation SE has been started with the agent job feature disabled. The
XPDEF file initialization statement enables the agent environment.

Action:
Perform the following actions:
■ Restart CA Workload Automation SE with the AGENTJOB feature enabled.
■ Contact your installation specialist for assistance.

QM00-91

JOB IS NOT AN AGENT JOB

Action:
The job entered on the command is not one of the defined agent job types.

Reason:
Verify you have the correct job name in the command. If valid, contact your installation
specialist for assistance.

1168 Message Reference Guide

 QM Messages

QM00-92

JOB IS MISSING REQ Q AGENT SEGMENT

Reason:
The agent segment does not exist in the REQ queue for the specified job.

Action:
Verify that you have the correct job name in the command. If valid, contact your
installation specialist for assistance.

QM00-93

TYPE=FILELIST NOT ALLOWED IN BATCH

Reason:
The AGFILE command was executed from a batch job and contained TYPE=FILELIST.

Action:
Execute the command from an online session of CA Workload Automation SE.

QM10-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Describes the user options available.

Action:
Self-explanatory.

QM10-00

ENTER FUNCTION (C,F,H,I,O,P, OR R) IN 'F' FIELD OR ENTER A COMMAND ON THE TOP

LINE

Reason:
Describes the options available on the QM.6-X panel.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1169

QM Messages

QM10-01

SCRATCH QUEUE ACCESS ERROR, RC=xxxxxxxx

Reason:
An error was encountered accessing the CA Workload Automation SE scratch queue.

Action:
Contact your installation specialist for assistance.

QM10-00

nn TRANSACTIONS PROCESSED, nn ERRORS DETECTED

Reason:
This message describes the total number of line transactions processed and the number
of those transactions that encountered an error.

Action:
For any errors, see the specific error reason in the REMARKS field for the transactions in
error.

QM10-05

INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM10-09

LAST ? SHOWN WAS SECURITY AUTHORIZATION FAILURE

Reason:
The last exception line transaction processed (? in 'F' field) encountered a security
authorization error.

Action:
If this function is necessary for you to perform your duties, contact your installation
specialist for assistance.

1170 Message Reference Guide

 QM Messages

QM10-13

NO SUCH TASKS IN THE QUEUE

Reason:
No network tasks were found matching the selection criteria.

Action:
None.

QM2F-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Describes the user options available.

Action:
Self-explanatory.

QM2F-01

QUEUE ACCESS OR SORT ERROR: xxxxxxxx

Reason:
An error occurred while accessing the CA Workload Automation SE queues, or, while
sorting the selected queue data. The specific error code is described by xxxxxxxx.

Action:
Contact your installation specialist for assistance.

QM2F-05

INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

Chapter 5: CDSI - RSCx Messages 1171

QM Messages

QM2F-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

QM2F-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
The authorization to do this function has not been set up by your installation's security
administrator.

Action:
If this function is necessary for you to perform your duties, contact your installation
specialist for assistance.

QM2F-13

NO SUCH JOB(S) FOUND

Reason:
No queue records could be found meeting the criteria imposed by the input command.

Action:
None.

QM20-00

ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Select a function option or a command on the top line.

1172 Message Reference Guide

 QM Messages

QM20-01

ww INVALID MACRO RETURN CODE xxxxnnnn

Reason:
An unexpected error condition was detected in program SASSQM20. The location in the
program is specified by ww and the value of register 15 is shown by nnnn. The offset
from the top of the program is indicated by xxxx. If nnnn=0000, a CA Workload
Automation SE data set may be out of space.

Action:
If nnnn=0000, check the system console for error messages. If the out-of-space
condition is indicated, increase the size of the failing data set. Otherwise, contact your
installation specialist for assistance.

QM20-02

JOB NOT FOUND

Reason:
The job no longer exists in the queue with which you are working.

Action:
None.

QM20-05

INVALID xxxxxx DATA

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM20-06

ERROR IN SUB-PROCESSOR

Reason:
An error occurred in a called program.

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1173

QM Messages

QM20-07

UPDATE DENIED - SUBMIT CHECK FAILED

Reason:
An attempt was made to replace JCL for a Request queue job. The JCL contained a
USERID and the updater was not authorized to submit for that USERID.

Action:
If security access should be allowed for the updater, contact your installation security
administrator or log on with an authorized USERID and update the JCL.

QM20-08

QJCL FOR JOB xxxxxxxx(nnnn) BEING EDITED BY ANOTHER USER

Reason:
This message is returned whenever JCL editing is requested for a job in the request
queue, but another CA Workload Automation SE user already has the JCL for editing.
The job name is indicated by xxxxxxxx and the CA 7 WA job number is indicated by nnnn.

Action:
Perform the following actions:
■ Wait for a few minutes for the other user to release the JCL.
■ Retry your request.

QM20-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
The authorization to do this function has not been set up by your installation's security
administrator.

Action:
If this function is necessary for you to perform your duties, contact your installation
specialist for assistance.

1174 Message Reference Guide

 QM Messages

QM20-13

JOB NOT FOUND [text]

Reason:
The job no longer exists in the queue with which you are working. If any text is shown, it
identifies the queues where the job is not found.

Action:
None.

QM20-21

JOB ALREADY SUBMITTED TO HOST

Reason:
The requested function cannot be performed after the job has been submitted.

Action:
None.

QM20-22

FUNCTION INVALID FOR THIS QUEUE

Reason:
The requested function is not valid for the queue with which you are working.

Action:
None.

QM20-23

MUST USE 'CANCEL' COMMAND FOR LOG DUMP JOBS

Reason:
An attempt was made to cancel the job that dumps the CA Workload Automation SE Log
file. This is not allowed from this panel.

Action:
Use the CANCEL command for this job. If FORCE=YES is not specified, the job will
reappear in the request queue.

Chapter 5: CDSI - RSCx Messages 1175

QM Messages

QM20-24

USE 'CANCEL' COMMAND - JOB IN LOAD STATUS

Reason:
An attempt is made to cancel a job that is in the Request queue and is currently going
through LOAD processing. Also, see the explanation in message SPO6-11.

Action:
Wait a few minutes and try again. If the message persists and the job must be canceled
before LOAD completion processing finishes, use the top line CANCEL command with
the FORCE=YES option.

Note: This may cause invalid job data to be added to the database. It is best to wait for
the LOAD to complete before canceling the job.

QM20-25

CANNOT CANCEL - JOB IN COMPLETION STATUS

Reason:
An attempt to cancel a job was rejected. The job is in the request queue in successful
completion processing. The job is not canceled.

Action:
None.

QM20-30

ALL REQUIREMENTS SATISFIED FOR xxxxxxxx(nnnn)

Reason:
You cannot post requirements for the identified job because the master count is zero.

Action:
Hold the job if you want to unpost requirements and the job has not been submitted.
The request is then honored.

1176 Message Reference Guide

 QM Messages

QM20-31

SKELETON RECORD FOUND

Reason:
Schedule Scan has not completed initial processing on the queue record.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM20-32

REQUIREMENTS SCAN INCOMPLETE

Reason:
Schedule Scan has not completed initial processing on this queue record.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command.
■ After the job is canceled, DEMAND the job.

If the problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1177

QM Messages

QM20-33

JOB COMPLETE OR RESTART IN PROCESS

Reason:
The job is in purge or restart processing and cannot be updated.

Action:
None.

QM20-34

ALL REQUIREMENTS SATISFIED EXCEPT RESTART

Reason:
Requirement posting (option X) was requested from the XQ, XQJ, XQM, or XQN panel
but only restart is needed; all other requirements are satisfied.

Action:
Use option F to transfer from the XQ, XQJ, XQM, or XQN panel to the QM.4 (XRST) panel
and perform the restart. You could also use the top line RESTART command.

QM20-35

INVALID DATA FOUND IN EDIT DATA

Reason:
A non-zero return code was passed from QJCL edit indicating non-displayable
hexadecimal is found.

Action:
Perform the following actions:
■ If editing is required, edit the JCL member through a facility like TSO/ISPF.
■ Cancel the job in the queues.
■ Demand the job again.

1178 Message Reference Guide

 QM Messages

QM20-51

ERROR ACCESSING CA-11 CMT (xx)

Reason:
During the processing for a cancel function (C) from the XQ/XQJ/XQN panel, an error
occurred in the CA Workload Automation SE/CA WA Restart Option interface. The error
code (xx) has the following meanings:
■ 04 - Unexpected end-of-data on the CMT.
■ 08 - Exclusive control CMT member not available.
■ 0C - CMT member changed by another program during access.
■ 10 - Fatal error - CA WA Restart Option Database Address Space is down.

Action:
Verify status of job on CMT by using the ARTS monitor interface. If the job shows in
restart status, a PRE P command should be requested. For format of online CA WA
Restart Option (ARTS) commands and how to determine job status, see the CA WA
Restart Option manuals.

QM20-52

LOAD PROCESSING INCOMPLETE

Reason:
Job load processing is currently in process for this job.

Action:
Wait until load processing completes before attempting the requested function.

QM20-55

CAN NOT RESTART - NO JCL ATTACHED

Reason:
A restart is being attempted for a job that does not have any JCL. Because there is not
any JCL, a restart would be invalid. Usually the job is marked EXEC=NO in the database
so that it will not be submitted to execute.

Action:
If the job should have had JCL, it may be added using the QJCL facility. If the job is not
supposed to have JCL (that is, if EXEC=NO on the DB.1 panel) and has a restart
requirement, it must be CANCELed and brought back into the request queue without
the restart requirement.

Chapter 5: CDSI - RSCx Messages 1179

QM Messages

QM20-56

MUST REQUEUE OR USE TOP-LINE CANCEL

Reason:
Cancel was requested for a job in the ready or active queue, but the CA WA Restart
Option interface is installed. Since the interface could cause the CA WA Restart Option
database entry for this job to be reset, the job should be requeued before it is canceled.

Action:
If the job is active or submitted to a CPU, use OS or JES cancel commands to purge the
job from the host system. This prevents duplicate runs. If the job is in the Ready queue
with JCLERR status or the host CPU is (or has been) down, REQUEUE the job before
canceling. If you must cancel without requeuing, use the top line CANCEL command
with FORCE=YES.

QM20-57

LINE FUNCTION DISABLED BY SITE OPTION

Reason:
The line command character entered here has been disabled in the CA Workload
Automation SE initialization file.

Action:
Use the equivalent top line command or contact your installation specialist for
assistance.

QM20-58

WARNING - SOME RQMT INFO DISPLAYED MAY BE IN ERROR OR INCOMPLETE

Reason:
One or more requirements for the job may have errors due to the data contained within
the requirement.

Action:
Contact your installation specialist for assistance.

1180 Message Reference Guide

 QM Messages

QM20-60

CANNOT CANCEL - JOB HAS RESOURCES

Reason:
The job cannot be canceled because it still holds VRM resources.

Action:
Either use the PRSCF command to release the resources, or use the top line CANCEL
command with FORCE=YES.

QM20-61

CANNOT CANCEL - JOB HAS ACTIVE ARF

Reason:
This message is issued when a cancel is attempted while ARF is controlling recovery for a
job.

Action:
Wait until ARF recovery is complete for the job. The LARFQ command can be used to
track the progress of ARF recovery for the job.

If the cancel must be issued prior to the completion of ARF recovery, then the ARFP
command can be used to terminate ARF recovery processing for the job. After the ARFP
command processing is complete, the cancel may be issued.

QM20-62

XQ E NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT

Reason:
The XQ panel will not allow an E (edit) function for jobs that are set as 7UNI jobs unless
CA Workload Automation SE mixed case support has been enabled.

Action:
If the JCL must be modified, then the job could be canceled, the JCL changed outside of
CA Workload Automation SE, and use the DEMAND command to bring the job in again.

Chapter 5: CDSI - RSCx Messages 1181

QM Messages

QM20-63

CANNOT CANCEL - ERROR IN ARF PURGE

Reason:
An error occurred while trying to delete the ARF environment for a job.

Action:
Attempt an ARFP command. If this fails, contact your installation specialist for
assistance.

QM20-64

CANNOT RESTART - NO PARM DATA ATTACHED

Reason:
An attempt to restart an agent job in the request queue failed. A user probably used
QJCL to delete the parameter data associated with the job. Agent jobs cannot run
successfully without the agent-specific parameter data.

Action:
Cancel the job and resubmit. This action assumes the required parameter data is in the
PDS member identified in the job definition panel.

QM20-65

CANNOT PERFORM FUNCTION - JOB NOT AT AGENT

Reason:
An attempt to HOLD or RELEASE an agent job at the agent was unsuccessful because the
job had never reached the agent.

Action:
Consider the following actions:
■ Confirm that the job is in the active queue using the LQ command.
■ If so, confirm the agent is running because this message typically occurs if the agent
is stopped after the job enters the active queue.
■ If the agent is running, run some jobs to other agents to determine whether the
problem is just with this agent, or numerous agents.
Problems with numerous agents could be indicative of a CA Integrated Agent
Services (CA IAS) interface problem.
■ For assistance, contact CA Support at http://ca.com/support.

1182 Message Reference Guide

 QM Messages

QM20-66

CANNOT PERFORM FUNCTION - AGENT ENVIRONMENT NOT ACTIVE

Reason:
An attempt to HOLD or RELEASE an agent job at the agent was unsuccessful because the
agent environment is not active. This problem can occur if the CA Workload Automation
SE instance was recycled with the AGENTJOB keyword on the XPDEF file initialization
statement set to NO, after having been previously started with a value of YES.

Action:
Try to demand a job to any agent. If the agent environment is not active, you receive an
error message.

QM20-67

CANNOT PERFORM FUNCTION - AGENT PROCESSING ERROR OCCURRED

Reason:
An attempt to HOLD or RELEASE an agent job at the agent was unsuccessful.

Action:
Check the CA Workload Automation SE browse data set for addition error messages
relating to the particular job. These messages start with an XAGT-xx prefix where xx is
the message number.

QM25-01

ww INVALID MACRO RETURN CODE xxxxnnnn

Reason:
An unexpected error condition was detected in program SASSQM25. The location in the
program is specified by ww, and the value in register 15 is shown by nnnn. The offset
from the top of the program is indicated by xxxx. If ww=Q2, the JCL is probably too large
to be edited with QJCL.

Action:
If the JCL needs to be changed, cancel the job, edit the JCL PDS, and then DEMAND the
job back in.

Chapter 5: CDSI - RSCx Messages 1183

QM Messages

QM30-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Describes the user options available.

Action:
Self-explanatory.

QM30-00

SET 'F' = 'X' TO POST OR ENTER A COMMAND ON TOP LINE

Reason:
Describes the options available on the QM.2-X panel.

Action:
None.

QM30-01

QUEUE ACCESS ERROR, RC=nnnnnnnn

Reason:
When trying to access the job or its information (JCL, requirements), an I/O error
occurred.

Action:
Contact your installation specialist for assistance.

QM30-05

INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

1184 Message Reference Guide

 QM Messages

QM30-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

QM30-13

JOB NOT FOUND IN THE REQUEST QUEUE

Reason:
The requested function cannot be completed because the job is not found in the
request queue. The job may have been moved to another queue or may have been
canceled by another user.

Action:
Issue the LQ command to see where that job may be.

QM30-30

ALL REQUIREMENTS SATISFIED FOR xxxxxxxx(nnnn)

Reason:
You cannot post requirements for the identified job because the master count is zero.

Action:
Hold the job if you want to unpost requirements and the job has not been submitted.
The request is then honored.

Chapter 5: CDSI - RSCx Messages 1185

QM Messages

QM30-31

JOB IS IN 'SKELETON' STATUS

Reason:
Schedule Scan has not completed initial processing on the queue record, or the JCL may
not have been found for a job.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM30-32

REQUIREMENTS SCAN HAS NOT COMPLETED

Reason:
Schedule Scan has not completed initial processing on this queue record.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job and DEMAND the job to resolve the problem.

If the problem persists, contact your installation specialist for assistance.

1186 Message Reference Guide

 QM Messages

QM30-34

ALL REQUIREMENTS SATISFIED EXCEPT FOR RESTART

Reason:
Requirement posting (option X) was requested from the XQ, XQJ, XQM, or XQN panel,
but only restart is needed. All other requirements are satisfied.

Action:
Perform the following actions:
■ Use option F to transfer from the XQ, XQJ, XQM, or XQN panel to the QM.4 (XRST)
panel.
■ Perform the restart.

Note: You could also use the top line RESTART command.

QM30-35

QJCL IN PROGRESS

Reason:
This message is returned whenever JCL editing is requested for a job in the request
queue, but another CA Workload Automation SE user already has the JCL for editing.
The job name is indicated by xxxxxxxx and the CA 7 WA job number is indicated by nnnn.

Action:
Perform the following actions:
■ Wait for a few minutes for the other user to release the JCL.
■ Retry your request.

QM40-00

SPECIFY DESIRED JOB, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Specify a job, select a function option or enter a command on the top line.

Chapter 5: CDSI - RSCx Messages 1187

QM Messages

QM40-00

CHANGE DESIRED FIELDS OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Perform the following actions:
■ Change the desired fields on the update screen.
■ Enter a top line command.

QM40-02

JOB UPDATED TO REFLECT VALUES SHOWN

Reason:
The queue update of the job has been completed.

Action:
None.

QM40-05

INVALID xxxxxx DATA

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM40-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

1188 Message Reference Guide

 QM Messages

QM40-13

JOB NOT FOUND IN REQUEST, READY OR ACTIVE QUEUE

Reason:
The requested job was not found in any of the queues.

Action:
Verify the job name entered. If you are unsure of the job name, issue XQ against the
appropriate queue or an LQ to locate the job.

QM40-31

JOB FOUND BUT IN 'SKELETON' STATUS

Reason:
Schedule Scan has not completed initial processing on the queue record, or the JCL may
not have been found for a job.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM40-32

JOB FOUND BUT REQUIREMENTS SCAN IS INCOMPLETE

Reason:
An update was attempted on a job that has not completed the requirements scan
process.

Action:
Let the job complete the process.

Chapter 5: CDSI - RSCx Messages 1189

QM Messages

QM40-33

JOB HAS ALREADY COMPLETED

Reason:
An update has been requested against an already completed job.

Action:
None.

QM40-34

JOB RESTART IS IN PROCESS

Reason:
A request to update a job cannot be completed because the job is being restarted.

Action:
None.

QM40-40

PROMPT HAS NOT BEEN RECEIVED

Reason:
An attempt has been made to acknowledge a prompt but no prompt has been sent.

Action:
None.

QM40-41

DEADLINE TIME MUST PRECEDE DUE-OUT TIME

Reason:
The deadline time specified is later than the due-out time. This is an invalid condition.

Action:
Correct the deadline time, due-out time, or both and retry.

1190 Message Reference Guide

 QM Messages

QM40-58

CANNOT HOLD - JOB ALREADY SUBMITTED OR COMPLETE

Reason:
An attempt to place a job on Hold was rejected. The job was in the active queue, in the
ready queue and already submitted to the MVS host, or in the request queue in
successful completion processing.

Action:
None. The job is not placed on Hold.

QM40-59

STOP TIME MUST BE < ORIGINAL SUBMIT TIME REQUIREMENT + 1 DAY

Reason:
The repeat stop time must be before the submit time requirement of the first job in the
repeating cycle plus one day. For example, if the first job has a submit time requirement
of 10:00 a.m., then the repeat stop time must be before 10:00 a.m. the following day.

Action:
Correct the QM.3-X fields.

QM40-60

STOP TIME MUST BE > ORIGINAL SUBMIT TIME REQUIREMENT

Reason:
The repeat stop time must be greater than the submit time requirement of the first job
in the repeating cycle.

Action:
Correct the QM.3-X fields.

Chapter 5: CDSI - RSCx Messages 1191

QM Messages

QM41-00

Specify desired job, transfer or enter a command on the top line

Reason:
Self-explanatory.

Action:
Perform one of the following actions:
■ Specify a job.
■ Select a function option.
■ Enter a command on the top line.

QM41-00

Change desired fields or enter a command on the top line

Reason:
Self-explanatory.

Action:
Perform one of the following actions:
■ Change the desired fields on the update screen.
■ Enter a top line command.

QM41-02

Job updated to reflect values shown

Reason:
The queue update of the job has been completed.

Action:
None.

1192 Message Reference Guide

 QM Messages

QM41-05

Invalid xxxxxx data

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM41-08

You are not authorized to access that job

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

QM41-13

Job not found in Request, Ready or Active Queue

Reason:
The requested job was not found in any of the queues.

Action:
Verify the job name entered. If you are unsure of the job name, issue XQ against the
appropriate queue or an LQ to locate the job.

QM41-23

XPJOB Node/EXEC Information not found

Reason:
An attempt to read XPJOB node and file executable information failed.

Note: This error indicates a larger problem.

Action:
Check to see whether you can update information for other jobs using the QM.3 panel.
If you cannot, your installation's queue files could have a problem. Contact your
installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1193

QM Messages

QM41-24

XPJOB Node/EXEC Information not updated

Reason:
An attempt to update XPJOB node and/or file executable information failed.

Note: This error indicates a larger problem.

Action:
Check to see whether you can update information for other jobs using the QM.3 panel.
If you cannot, your installation's queue files could have a problem. Contact your
installation specialist for assistance.

QM41-25

No XPJOB environment exists, XPJOB updates disabled

Reason:
CA Workload Automation SE was previously started with the XPJOB feature enabled. CA
Workload Automation SE has been restarted with the XPJOB feature disabled. The
XPDEF file initialization statement enables the XPJOB environment.

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Restart CA Workload Automation SE with the XPJOB feature enabled. Contact your
installation specialist for assistance.

1194 Message Reference Guide

 QM Messages

QM41-31

Job found but in 'Skeleton' Status

Reason:
Schedule Scan has not completed initial processing on the queue record, or the JCL may
not have been found for a job.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM41-32

Job found but requirements scan is incomplete

Reason:
An update was attempted on a job that has not completed the requirements scan
process.

Action:
Let the job complete the process.

QM41-33

Job has already completed

Reason:
An update has been requested against an already completed job.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1195

QM Messages

QM41-34

Job restart is in progress

Reason:
A request to update a job cannot be completed because the job is being restarted.

Action:
None.

QM41-40

Prompt has not been received

Reason:
An attempt has been made to acknowledge a prompt but no prompt has been sent.

Action:
None.

QM41-41

Deadline Time must precede Due-Out Time

Reason:
The deadline time specified is later than the due-out time. This is an invalid condition.

Action:
Correct the deadline time, due-out time, or both and retry.

QM41-58

Cannot Hold - Job already submitted or complete

Reason:
An attempt to place a job on Hold was rejected. The job was in the active queue, in the
ready queue and already submitted to the MVS host, or in the request queue in
successful completion processing.

Action:
None. The job is not placed on Hold.

1196 Message Reference Guide

 QM Messages

QM41-59

Stop Time must be < original Submit Time requirement + 1 day

Reason:
The repeat stop time must be before the submit time requirement of the first job in the
repeating cycle plus one day. For example, if the first job has a submit time requirement
of 10:00 a.m., then the repeat stop time must be before 10:00 a.m. the following day.

Action:
Correct the QM.3-X fields.

QM41-60

Stop Time must be > original submit time requirement

Reason:
The repeat stop time must be greater than the submit time requirement of the first job
in the repeating cycle.

Action:
Correct the QM.3-X fields.

QM42-00

Specify desired job, transfer or enter a command on the top line

Reason:
Self-explanatory.

Action:
Specify a job, select a function option or enter a command on the top line.

QM42-00

Change desired fields or enter a command on the top line

Reason:
Self-explanatory.

Action:
Change the desired fields on the update screen or enter a top line command.

Chapter 5: CDSI - RSCx Messages 1197

QM Messages

QM42-02

Job updated to reflect values shown

Reason:
The queue update of the job has been completed.

Action:
None.

QM42-05

Invalid xxxxxx data

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM42-08

You are not authorized to access that job

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

QM42-13

Job not found in Request, Ready or Active Queue

Reason:
The requested job was not found in any of the queues.

Action:
Verify the job name entered. If you are unsure of the job name, issue XQ against the
appropriate queue or an LQ to locate the job.

1198 Message Reference Guide

 QM Messages

QM42-23

Agent/User ID Information not found

Reason:
An attempt to read agent/user ID information failed.

Note: This error indicates a larger problem.

Action:
Check to see whether you can update information for other jobs using the QM.3 panel.
If you cannot, your installation's queue files could have a problem. Contact your
installation specialist for assistance.

QM42-24

Agent/User ID Information not updated

Reason:
An attempt to update agent/user ID information failed.

Note: This error indicates a larger problem.

Action:
Check to see whether you can update information for other jobs using the QM.3 panel.
If you cannot, your installation's queue files could have a problem. Contact your
installation specialist for assistance.

QM42-25

No Agent environment exists, Agent updates disabled

Reason:
CA Workload Automation SE was previously started with the agent job feature. CA
Workload Automation SE has been restarted with the agent job feature disabled. The
XPDEF file initialization statement enables the agent environment.

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Restart CA Workload Automation SE with the agent job feature enabled. Contact your
installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1199

QM Messages

QM42-31

Job found but in 'Skeleton' Status

Reason:
Schedule Scan has not completed initial processing on the queue record, or the JCL may
not have been found for a job.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM42-32

Job found but requirements scan is incomplete

Reason:
An update was attempted on a job that has not completed the requirements scan
process.

Action:
Let the job complete the process.

QM42-33

Job has already completed

Reason:
An update has been requested against an already completed job.

Action:
None.

1200 Message Reference Guide

 QM Messages

QM42-34

Job restart is in progress

Reason:
A request to update a job cannot be completed because the job is being restarted.

Action:
None.

QM42-40

Prompt has not been received

Reason:
An attempt has been made to acknowledge a prompt but no prompt has been sent.

Action:
None.

QM42-41

Deadline Time must precede Due-Out Time

Reason:
The deadline time specified is later than the due-out time. This is an invalid condition.

Action:
Correct the deadline time, due-out time, or both and retry.

QM42-58

Cannot Hold - Job already submitted or complete

Reason:
An attempt to place a job on Hold was rejected. The job was in the active queue, in the
ready queue and already submitted to the MVS host, or in the request queue in
successful completion processing.

Action:
None. The job is not placed on Hold.

Chapter 5: CDSI - RSCx Messages 1201

QM Messages

QM42-59

Stop Time must be < original Submit Time requirement + 1 day

Reason:
The repeat stop time must be before the submit time requirement of the first job in the
repeating cycle plus one day. For example, if the first job has a submit time requirement
of 10:00 a.m., then the repeat stop time must be before 10:00 a.m. the following day.

Action:
Correct the QM.3-X fields.

QM42-60

Stop Time must be > original submit time requirement

Reason:
The repeat stop time must be greater than the submit time requirement of the first job
in the repeating cycle.

Action:
Correct the QM.3-X fields.

QM50-00

xxxxxxxx FUNCTION COMPLETED SUCCESSFULLY

text

Reason:
The requested function has been successfully performed. If the second line appears, it
gives additional information about the job.

Action:
None.

QM50-00

SPECIFY DESIRED JOB, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Specify a job, select a function option or enter a command on the top line.

1202 Message Reference Guide

 QM Messages

QM50-00

SPECIFY DESIRED JOB, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Specify a job, select a function option or enter a command on the top line.

QM50-01

INVALID MACRO RETURN CODE xxxxnnnn

Reason:
An unexpected error condition was detected in program SASSQM50. The value of
register 15 is shown by nnnn. The offset from the top of the program is indicated by
xxxx. If nnnn=0000, a CA Workload Automation SE data set may be out of space.

Action:
Check the system console for error messages if nnnn=0000. If the out-of-space condition
is indicated, increase the size of the failing data set. Otherwise, contact your installation
specialist for assistance.

QM50-04

CONFLICTING FUNCTIONS SELECTED

Reason:
Multiple function requests have been specified on the same panel. These functions have
implied conflicts.

Action:
Correct and retry.

QM50-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

Chapter 5: CDSI - RSCx Messages 1203

QM Messages

QM50-05

'X' IS THE ONLY VALID SELECTION CHARACTER

Reason:
To select a job, enter X; no other character is valid.

Action:
Reenter using the character X.

QM50-05

INVALID VALUE FOR JOB

Reason:
Invalid data was entered.

Action:
Correct and retry.

QM50-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
You do not have the proper security to access the target job.

Action:
Contact your installation specialist for assistance.

QM50-13

JOB NOT FOUND [text]

Reason:
The job no longer exists in the queue with which you are working. If any text is shown, it
identifies the queues where the job is not found.

Action:
None.

1204 Message Reference Guide

 QM Messages

QM50-31

JOB FOUND BUT IN 'SKELETON' STATUS

Reason:
Schedule Scan has not completed initial processing on the queue record, or the JCL may
not have been found for a job.

Action:
Perform the following actions:
■ Wait a few minutes and try again.
■ Look for error messages about this job on the terminal defined as
STANIDS=MASTER in the initialization file.
■ If necessary, cancel the job using the CANCEL command with the FORCE=YES
option.
■ After the job is canceled, DEMAND the job back into the request queue.

If the problem persists, contact your installation specialist for assistance.

QM50-32

JOB FOUND BUT REQUIREMENTS SCAN IS INCOMPLETE

Reason:
Job modification cannot be performed because the requirements scan process has not
completed.

Action:
Let the job complete the process.

QM50-33

JOB HAS ALREADY COMPLETED

Reason:
A modification has been requested against an already completed job.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1205

QM Messages

QM50-42

CA-11 RESTART KEYWORDS INVALID WITH SELECTED FUNCTION

Reason:
The RESUBMIT or FORCE COMPLETE function was selected but one or more of the CA
WA Restart Option RESTART/RERUN fields was supplied.

Action:
If a RESUBMIT or FORCE COMPLETE is to be done, clear the CA WA Restart Option
RESTART/RERUN fields on the panel. If a restart is to be done, select the CA WA Restart
Option RESTART/RERUN function.

QM50-50

//*UCC7RESTART CARD NOT FOUND IN JCL

Reason:
The execution JCL should contain a restart comment statement. For unexplained
reasons, the statement is no longer present.

Action:
The statement may be reinserted by using the QJCL panel to fetch the JCL, correct it,
and then save it. In any case, contact your installation specialist for assistance. Try to
write down the commands which resulted in this condition.

QM50-51

ERROR TRYING TO UPDATE THE CA-11 CMT FILE

Reason:
While CA Workload Automation SE was trying to write to the CA WA Restart Option
CMT, an error was encountered.

Action:
Check the system console for CA WA Restart Option error messages. If the error is
temporary, the update should be attempted later.

1206 Message Reference Guide

 QM Messages

QM50-51

CMT CHANGED SINCE DISPLAYED - TRY AGAIN

Reason:
Between initial display and update request, the CMT member for the job was updated
by another user.

Action:
Recheck the displayed fields, correct and reenter.

QM50-51

CMT MEMBER NOT AVAILABLE - RETRY LATER

Reason:
Another user in the system has the CMT member for the job under exclusive control.

Action:
Wait a few minutes, then retry the request again. If the problem persists, contact your
installation specialist for assistance.

QM50-51

END STEP NOT FOUND IN CMT - TRY ANOTHER

Reason:
The requested ending step name for restart was not found in the CMT.

Action:
Use a different step name and try again. You may want to check the CMT member for
the job using the CINQ command to CA WA Restart Option through the ARTS monitor.

QM50-51

FATAL ERROR -- CA-11 MAY BE DOWN

Reason:
The CA WA Restart Option Database Address Space appears to be down.

Action:
Check status of CA WA Restart Option and reinitialize if necessary, then try the request
again. If problem persists, contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1207

QM Messages

QM50-51

INVALID ERROR CODE - xx

Reason:
A CA WA Restart Option restart was attempted; however, an unknown return code was
received from CA WA Restart Option. This may be caused by a mismatch between the
release of CA WA Restart Option and the version of the CA Workload Automation SE/CA
WA Restart Option interface.

Action:
Check the CA Workload Automation SE address space for CA WA Restart Option
messages indicating invalid or outdated parameter lists (such as U11-300). If these
messages are present, upgrade your CA Workload Automation SE/CA WA Restart Option
interface to match the release of CA WA Restart Option you are executing.

QM50-51

JOB NOT RESTARTABLE - USE RESUBMIT

[RMS STEP DID NOT COMPLETE]
[NCF INVOLVED BUT RMS NOT INSERTED BY CA-7]

Reason:
The job being displayed on the QM.4 (XRST) panel is not restartable. Use the RESUBMIT
option instead of RESTART. This message appears for one of the following reasons:
■ A job is not restartable according to the CMT flag settings.
■ The RMS procedure was inserted by CA Workload Automation SE, but did not
complete.
■ The job executed at a remote site (NCF node), but RMS was not inserted by CA
Workload Automation SE.

Action:
If the job is to be rerun, use the RESUBMIT option. If NCF and CA WA Restart Option are
involved but CA Workload Automation SE is not inserting RMS, update the JCL to set the
RMS parameters.

1208 Message Reference Guide

 QM Messages

QM50-51

LRTCD STEP NOT FOUND IN CMT BEFORE START STEP

Reason:
A CA WA Restart Option restart was attempted, but the step name specified in the
LRTCD field is not before the step specified for the starting step.

Action:
Correct the step names and then press Enter.

QM50-51

START STEP NOT FOUND IN CMT - TRY ANOTHER

Reason:
The requested starting step name for restart was not found in the CMT.

Action:
Use a different step name and try again. You may want to check the CMT member for
the job using the CINQ command to CA WA Restart Option through the ARTS monitor.

QM50-51

START STEP NOT RESTARTABLE - TRY ANOTHER

Reason:
The requested starting step for restart is flagged as not restartable on the CMT.

Action:
Specify an earlier starting step and retry. You may want to check the CMT member for
the job using CINQ command to CA WA Restart Option through the ARTS monitor.

QM50-51

USAGE CODE MUST CHANGE - TRY AGAIN

Reason:
CA WA Restart Option options require the usage code to change between runs but the
QM.4 (XRST) panel field matches the CMT field.

Action:
Change the usage field on the QM.4 (XRST) panel and try again.

Chapter 5: CDSI - RSCx Messages 1209

QM Messages

QM50-52

JOB FOUND BUT LOAD PROCESSING INCOMPLETE

Reason:
A restart was attempted on a job that is in the LOAD process.

Action:
Let the job complete the LOAD process.

QM50-53

JOB DOES NOT HAVE ABNORMAL STATUS

Reason:
The requested function is only valid for jobs with abnormal status.

Action:
None.

QM50-57

CA-11 RMS PARM DATA IS TOO LONG FOR JCL

Reason:
An invalid parameter has been specifies for RMS.

Action:
Correct the parameter data.

QM50-58

LOAD ONLY JOB - CANNOT FORCE COMPLETE

Reason:
An attempt was made to force complete a LOAD only job.

Action:
Restart or cancel the job.

1210 Message Reference Guide

 QM Messages

QM50-59

USE RESUBMIT OR SET PARM - NO CMT MEMBER

Reason:
A CA WA Restart Option Restart was specified for a job that does not have a CMT
member which CA Workload Automation SE can access.

Action:
The 'RESUBMIT FOR PRODUCTION' or 'SET PARM DATA FOR RMS' may be used to
resubmit the job to the operating system. If the job is submitted to a remote site and
tracked using CA Workload Automation SE NCF, the 'SET PARM DATA FOR RMS' field
should be used to pass the correct CA WA Restart Option PARM in the JCL.

QM50-60

USING LRTCD REQUIRES A STARTING STEP NAME

Reason:
A step name was supplied in the LRTCD field, but the starting step name was left blank.

Action:
Supply the appropriate starting step name and press Enter.

QM50-61

UNABLE TO RESTART, ARF EVENTS PENDING

Reason:
This message is issued when a RESTART is attempted while ARF is controlling recovery
for a job.

Action:
Wait until ARF recovery is complete for the job. The LARFQ command can be used to
track the progress of ARF recovery for the job.

If the RESTART must be issued prior to the completion of ARF recovery, then the ARFP
command can be used to terminate ARF recovery processing for the job. After the ARFP
command processing is complete, the RESTART may be issued.

Chapter 5: CDSI - RSCx Messages 1211

QM Messages

QM60-01

FUNCTION SUCCESSFUL: RESOURCE MODULE TEMPORARILY CHANGED

Reason:
Using the XWLB panel, the workload balancing module has been updated in storage
(and checkpointed) with any changes that were made.

Action:
None.

QM60-05

INVALID xxxxxx DATA

Reason:
On the XWLB panel, an invalid data entry was made. For example, using a value greater
than 255 for a class barrier.

Action:
Enter the correct value.

QM60-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
The authorization to do this function has not been set up by your installation's security
administrator.

Action:
If this function is necessary for you to perform your duties, contact your installation
specialist for assistance.

QM70-10

*** ATTENTION *** JOB=xxxxxxxx(nnnn) HAS BEEN CANCELED

Reason:
Job xxxxxxxx, job number nnnn has been canceled by a user request.

Action:
None.

1212 Message Reference Guide

 QM Messages

QM70-61

CAN NOT CANCEL - JOB HAS ACTIVE ARF

Reason:
This message is issued when a request to cancel a job is received while ARF is controlling
recovery for a job.

Action:
Wait until ARF recovery is complete for the job. Use the LARFQ command to track the
progress of ARF recovery for the job. If the job must be canceled prior to the completion
of ARF recovery, use the ARFP command to terminate ARF recovery processing for the
job. After the ARFP command processing is complete, you can issue the cancel request.

QM70-62

CAN NOT CANCEL - JOB HAS RESOURCES

Reason:
The job cannot be canceled because it still holds VRM resources.

Action:
Either use the PRSCF command to release the resources, or use the top line CANCEL
command with FORCE=YES.

QM70-62

CANNOT CANCEL, ARF RECOVERY IN PROGRESS

Reason:
This message is issued when a request to cancel a job is received while ARF is controlling
recovery for a job.

Action:
Wait until ARF recovery is complete for the job. The LARFQ command can be used to
track the progress of ARF recovery for the job.

If the job must be canceled prior to the completion of ARF recovery, then the ARFP
command can be used to terminate ARF recovery processing for the job. After the ARFP
command processing is complete, the cancel request can be issued.

Chapter 5: CDSI - RSCx Messages 1213

QM Messages

QM70-63

JOB xxxxxxxx (nnnn) WAS SET FOR REPEAT

Reason:
The specified job was canceled (see previous QM70-10 message). The job was set to
repeat but is not repeated because it was canceled.

Action:
None.

QM81-00

Enter desired function for a line entry or a command on the top line

Reason:
Self-explanatory.

Action:
Select a function option or enter a command on the top line.

QM81-01

Invalid function, please enter a valid function

Reason:
An invalid character was entered as the function.

Action:
Reenter using one of the valid functions displayed.

QM81-02

Invalid Start Offset. Must be numeric

Reason:
A non-numeric value was entered in the starting offset field.

Action:
Enter a valid numeric starting offset.

1214 Message Reference Guide

 QM Messages

QM81-03

Error trying to read VSAM N record

Reason:
When trying to retrieve the data associated with the specified job name, an error
occurred reading the CA7AGNT VSAM file.

Action:
Contact your installation specialist for assistance.

QM81-04

No agent data available

Reason:
For the requested job, the agent returned no data. This may be because the job has yet
to execute at the agent.

Action:
None.

QM81-05

Error trying to read queues

Reason:
An error occurred while accessing the CA Workload Automation SE queues.

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1215

QM Messages

QM81-06

No jobs found

Reason:
For LIST=Q, the requested job was not found in the status queues. For LIST=HIS, the
requested job was not found in the CA7AGNT VSAM file. For LIST=ALL, the requested job
was not found in either place.

Action:
Perform the following actions:
■ Verify that you have entered the correct job name.
■ Correct the job name.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

QM81-07

Invalid Step number. Must be numeric

Reason:
A non-numeric value was entered in the step number field.

Action:
Enter a valid numeric step number.

QM82-00

Request Complete

Reason:
This message indicates the successful end of a batch AGFILE command. The message
applies only when AGFILE is executing in batch mode.

Action:
None.

1216 Message Reference Guide

 QM Messages

QM82-00

Enter Spool Offset or a command on the top line

Reason:
Self-explanatory.

Action:
Perform one of the following actions:
■ Enter a numeric spool offset to the file being browsed.
■ If Next Offset is not EOF, enter N in Spool Offset to retrieve the next chunk of data.
■ Enter a top line command to request another function.

QM82-01

text

Reason:
An error has occurred while sending a command to an agent. text is the error message
that was returned.

Action:
Perform one of the following actions depending on the message prefix:
■ CAIAS message prefix - For more information, see the CA Integrated Agent Services
Message Guide.
■ AFM2 message prefix - For more information, see the AFM2-nnn message in this
guide.
■ No message prefix - The message is a STATUS message returned by the agent itself.
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1217

QM Messages

QM82-02

*** IAS IS NOT ACTIVE OR NOT INITIALIZED

Reason:
When trying to retrieve the requested spool or log data, a request could not be passed
to CA Integrated Agent Services (CA IAS).

Action:
Perform the following actions:
■ Verify that the initialization file option specifies XPDEF,AGENTJOB=YES.
■ Check the JES job log for any messages indicating problems with CA IAS.
■ Contact your installation specialist for assistance.

QM82-03

*** LOAD FAILED FOR SASSAFM2

Reason:
To communicate with the agents requires this module to build the appropriate
messages, but the module could not be loaded.

Action:
Verify the STEPLIB has the CAL2LOAD library concatenated and that SASSAFM2 can be
found in the library. If it is present, contact your installation specialist for assistance.

QM82-04

*** IAS DIVR INTERNAL ERROR, RC=nnnn

Reason:
An internal error when processing a control block called DIVR occurred.

Action:
Check the JES job log for any messages indicating problems with CA Integrated Agent
Services (CA IAS). Report this information and messages located in the job log to CA
Support.

1218 Message Reference Guide

 QM Messages

QM82-05

Invalid xxxxxxxxx data

Reason:
The identified field contains invalid data or is a required field.

Action:
Correct and retry.

QM82-06

Invalid Spool Offset. Must be numeric or NEXT

Reason:
A non-numeric value or the word not equal to 'NEXT' was entered in the spool offset
field.

Action:
Enter a valid numeric spool offset or the word NEXT.

QM82-07

Spool Offset is beyond the end of the file

Reason:
The requested spool offset is beyond the end of the requested file.

Action:
To view the file, enter 0 to begin, or a lower number than what was entered.

QM82-08

Function type xxxxxxxx not supported for job type xxxx

Reason:
The requested function type is not supported for the job type of the job requested.

Action:
Perform the following actions:
■ Enter PF3 key to get back to the previous menu.
■ Select a valid option for the job type of the job requested.

Chapter 5: CDSI - RSCx Messages 1219

QM Messages

QM82-09

Invalid AGFILE flag in L2AGTBL

Reason:
An internal error has occurred with the agent job type table, which may expose other
agent job problems in addition to this one.

Action:
Perform the following actions:
■ Report this error and other agent job errors to CA Support.
■ Provide the job type of the job being requested.

Note: A restart of CA Workload Automation SE may be required to reset the job table.

QM82-10

Error retrieving xxxxxxxx VSAM records

Reason:
When trying to retrieve the data associated with the specified keyword, an error
occurred reading the CA7AGNT VSAM file.

Action:
Contact your installation specialist for assistance.

QM82-11

Invalid or missing name/number, use FILELIST to obtain name/number

Reason:
Requesting spool from an i5/OS job requires the specific spool file name and number. To
obtain this information use option 'F' to obtain the needed data.

Action:
Request the spool file list via selection 'F' from the job menu.

1220 Message Reference Guide

 QM Messages

QM82-12

xxxxxxxx record not found on VSAM file

Reason:
The VSAM record associated with the specified keyword is not found on the CA7AGNT
VSAM file.

Action:
Contact your installation specialist for assistance.

QM82-13

Data field for xxxxxxxx/yyyyyyyy is null on VSAM record

Reason:
The VSAM record associated with the specified xxxxxxx keyword is found on the
CA7AGNT VSAM file, but field yyyyyyyy is null.

Action:
Contact your installation specialist for assistance.

QM82-16

Delete sent, check status with IN function

Reason:
A delete command has been sent to the agent.

Action:
Perform the following actions:
■ Display job information from the CA7AGNT VSAM file using one of the following:
– The IN function from an AGFILE list of jobs panel.
– TYPE=INFO on a AGFILE direct request.
■ Look for delete status information in the displayed data.

Chapter 5: CDSI - RSCx Messages 1221

QM Messages

QM82-17

Spool retrieved. Contents are empty

Reason:
This file location has no data.

Action:
Perform the following actions:
■ Check whether the job that was run generates spool output data. Some files may be
empty.
■ Verify that a file location was specified in the original job definition (NONSTOP_JOB
only).
■ Contact your installation specialist for assistance.

QM82-18

Offset overflow. Display is terminated

Reason:
The offset value can be up to 99,999,999. After this value is exceeded, the display is
terminated (and the value itself is truncated). Offsets at or near this size generate over 2
million lines of output. The file that you are retrieving is too large to display using the
AGFILE command.

Action:
Perform the following actions:
■ Go to the agent where the job ran.
■ Find the file in the spool directory.
■ Select the desired file to view it.

QM83-00

Select a line entry with an 'S' or enter a command on the top line

Reason:
The spool file list has been displayed.

Action:
Once the spool file list for an i5/OS job has been displayed, request the actual spool file
via line command 'S' or enter a top line command for another display.

1222 Message Reference Guide

 QM Messages

QM83-01

Invalid function, please enter a valid function

Reason:
An invalid character was entered as the function.

Action:
Reenter using one of the valid functions displayed.

QM83-02

Invalid Start Offset. Must be numeric

Reason:
A non-numeric value was entered in the starting offset field.

Action:
Enter a valid numeric starting offset.

QM83-03

Error trying to read VSAM N record

Reason:
When trying to retrieve the data associated with the specified job name, an error
occurred reading the CA7AGNT VSAM file.

Action:
Contact your installation specialist for assistance.

QM83-04

No agent data available

Reason:
For the requested job, the agent returned no data. This may be because the job has yet
to execute at the agent.

Action:
None.

Chapter 5: CDSI - RSCx Messages 1223

RMS1 Messages

RMS1 Messages
RMS1-00

ARTS ONLINE MONITOR ENDED

SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Reason:
Normal completion of ARTS command occurred. xxxx is the system abend code and
nnnn is the user abend code. For normal completion, both xxxx and nnnn are zero.

Action:
If both xxxx and nnnn are zero, no action is required. See message RMS1-80. If nnnn is
0999, the interface to CA WA Restart Option is not initialized.

RMS1-70

FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Reason:
ARTS command was issued from a non-3270 terminal.

Action:
Use 3270 (online) terminal to issue ARTS commands.

RMS1-80

ARTS ONLINE MONITOR TERMINATED

SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Reason:
Abnormal completion of ARTS command occurred either due to a C request made by
operator or abend condition noted. xxxx is the system abend code and nnnn is the user
abend code.

Action:
Determine cause of error and correct.

1224 Message Reference Guide

 RMS1 Messages

RMS1-81

ATTACH UNSUCCESSFUL FOR xxxxxxxx

Reason:
ARTS command was attempting to attach the CA WA Restart Option control program
identified by xxxxxxxx, but the attach failed.

Action:
Perform the following actions:
■ Verify program xxxxxxxx exists in a STEPLIB data set in the CA Workload Automation
SE execution JCL.
■ Concatenate the CA WA Restart Option load library if it is missing.
■ Reinitialize CA Workload Automation SE.
■ Retry ARTS.

RMS1-82

BLDL FAILED FOR xxxxxxxx

Reason:
ARTS command was attempting to find the CA WA Restart Option interface module
identified by xxxxxxxx, but failed.

Action:
Perform the following actions:
■ Verify program xxxxxxxx exists in a STEPLIB data set in the CA Workload Automation
SE execution JCL.
■ Concatenate the CA WA Restart Option load library if it is missing.
■ Reinitialize CA Workload Automation SE.
■ Retry ARTS.

Chapter 5: CDSI - RSCx Messages 1225

RSCx Messages

RMS1-83

LINKEDIT OF SASSRMS1 DOES NOT INCLUDE UCC11OCR

Reason:
CA Workload Automation SE module SASSRMS1 has not been linked with CA WA Restart
Option module UCC11OCR.

Action:
Follow linkage instructions in the Systems Programming Guide under Interfaces.

RMS1-84

ARTS ONLINE MONITOR TERMINATED

SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Reason:
Unusual completion for ARTS command. If the ARTS command is attempted while CA
WA Restart Option is not active, this message is issued.

Action:
None.

RSCx Messages
RSC0-00

SPECIFY DESIRED OPTION OR ENTER A COMMAND ON THE TOP LINE

Reason:
Self-explanatory.

Action:
Enter the option that you want or a top line command.

1226 Message Reference Guide

 RSCx Messages

RSC0-01

VRM SUPPORT NOT ACTIVE

Reason:
VRM support has not been activated.

Action:
Verify that the product's initialization file, DBASE statement includes the RSRC=YES
parameter to activate full Virtual Resource Management support.

RSC0-02

VRM MAINTENANCE SUPPORT ACTIVE

Reason:
The VRM Maintenance Support facility has been activated by specifying the
RSRC=MAINT parameter on the DBASE statement in the product's initialization file.

Action:
None.

RSC1-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC1-01

ww INVALID MACRO RETURN CODE nnnnnnnnn

Reason:
An unexpected error condition was detected in program SASSRSC1. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnnn.

Action:
Contact your installation specialist for assistance.

Chapter 5: CDSI - RSCx Messages 1227

RSCx Messages

RSC1-02

xxxxxxxx NOT FOUND

Reason:
The requested job or resource was not found on the CA Workload Automation SE
database.

Action:
Verify that you have specified the correct name and reissue the request.

RSC1-04

NO RESOURCES DEFINED FOR JOB

Reason:
No virtual resources are connected to the specified job.

Action:
None.

RSC1-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC1-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

1228 Message Reference Guide

 RSCx Messages

RSC1-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

RSC1-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
The input data contained unrecognizable keywords and/or formats data for one or more
parameters.

Action:
Reissue the transaction with the correct parameters data.

RSC1-14

ZERO AND NON-ZERO SCHID NOT ALLOWED

Reason:
An attempt was made to update a job to resource connection and an existing resource
already exists with a schedule-ID of zero. A schedule-ID of 0 (zero) applies to all
schedule-IDs for a job.

Action:
If you want to add a job to resource connection which will only apply to a specific job
schedule-ID, use the add function to make the connection. You cannot update a job to
resource connection when the resource exists on the database with a schedule-ID of 0
(zero).

Chapter 5: CDSI - RSCx Messages 1229

RSCx Messages

RSC1-15

DUPLICATE RESOURCE CONNECTED TO JOB

Reason:
An attempt was made to update a job to a resource connection, and a matching
resource connection is already defined.

Action:
Check the spelling of the resource name and the type of resource. Correct and reissue
the command if needed.

RSC1-18

xxx...xxx

Reason:
The resource name does not conform to the rules governing naming resources of this
type. The message at xxx...xxx explains the specific reason for the error.

Action:
Correct the error and continue.

RSC2-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC2-01

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSRSC2. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn.

Action:
Contact your installation specialist for assistance.

1230 Message Reference Guide

 RSCx Messages

RSC2-02

xxxxxxxx NOT FOUND

Reason:
The requested resource was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct name and reissue the request.

RSC2-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC2-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

RSC2-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

Chapter 5: CDSI - RSCx Messages 1231

RSCx Messages

RSC3-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC3-01

ww INVALID MACRO RETURN CODE nnnnnnnnn

Reason:
An unexpected error condition was detected in program SASSRSC3. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnnn.

Action:
Contact your installation specialist for assistance.

RSC3-02

xxxxxxxx NOT FOUND

Reason:
The requested data was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct values and reissue the request.

RSC3-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

1232 Message Reference Guide

 RSCx Messages

RSC3-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

RSC3-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

RSC4-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC4-02

xxxxxxxx NOT FOUND

Reason:
The requested data was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct values and reissue the request.

Chapter 5: CDSI - RSCx Messages 1233

RSCx Messages

RSC4-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC4-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

RSC4-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

RSC5-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

1234 Message Reference Guide

 RSCx Messages

RSC5-02

xxxxxxxx NOT FOUND

Reason:
The requested data was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct values and reissue the request.

RSC5-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC5-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

RSC5-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

Chapter 5: CDSI - RSCx Messages 1235

RSCx Messages

RSC6-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC6-02

xxxxxxxx NOT FOUND

Reason:
The requested data was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct values and reissue the request.

RSC6-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC6-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

1236 Message Reference Guide

 RSCx Messages

RSC6-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

RSC7-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The specified function was completed without error.

Action:
None.

RSC7-01

INVALID MACRO RETURN CODE nn

Reason:
The SASSRSC7 module has detected an error on return from a macro. The register 15
value (in hex) is given by nn

Action:
Contact your installation specialist for assistance.

RSC7-02

RESOURCE NOT FOUND

Reason:
The requested resource was not found on the CA Workload Automation SE database.

Action:
Verify that you have specified the correct name and reissue the request.

Chapter 5: CDSI - RSCx Messages 1237

RSCx Messages

RSC7-04

TOTAL AND USE COUNTS MUST BE ZERO TO DELETE

Reason:
Cannot delete an RCT entry unless the counts are zero.

Action:
Set total to zero, and when the use count goes to zero, the entry can be deleted.

RSC7-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
xxxxxxxx is the parameter that is invalid or omitted.

Action:
Reissue the request with the correct data.

RSC7-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
A security violation occurred when a user attempted to access a job without proper
authorization (UID security).

Action:
Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.

RSC7-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A security violation occurred when a user attempted a function without proper
authorization.

Action:
Verify that the user requires access to the indicated function.

1238 Message Reference Guide

 RSCx Messages

RSC7-13

RESOURCE ALREADY EXISTS

Reason:
Cannot add an RCT entry that already exists.

Action:
Ensure that the name is specified correctly, and reissue the command.

Chapter 5: CDSI - RSCx Messages 1239

Chapter 6: SANx - SJR2 Messages
This chapter contains the SANx through SJR2 messages.

SANx
SANx-00

ANALYZE REQUEST COMPLETED AT hh:mm:ss yy.ddd

Reason:
This is an informational message indicating the ANALYZE command has been
successfully processed.

Action:
None.

SANx-01

xxxxxxxx IS AN INVALID FUNCTION

Reason:
An invalid ANALYZE function xxxxxxxx has been specified.

Action:
Check the possible ANALYZE functions in the Database Maintenance Guide and reenter
the command.

SANx-02

INVALID OR OMITTED PARAMETER

Reason:
An invalid parameter has been specified or a required parameter has been omitted from
the command.

Action:
Verify the function and parameter values in the Database Maintenance Guide and
reenter the command.

Chapter 6: SANx - SJR2 Messages 1241

SANx

SANx-03

xxxxxxxx IS INVALID

Reason:
Keyword xxxxxxxx has an invalid value.

Action:
Verify the keyword values in the Database Maintenance Guide and reenter the
command.

SANx-04

OUT OF SPACE ON DATA BASE

Reason:
An out-of-space condition occurred while processing the command.

Action:
Scan the system log for the WTO messages identifying which data set is out of space.
Use the SASSBK00 program to back up the database. Next, expand the allocation for the
affected data set and reload the data set using SASSBK00.

SANx-05

JOB xxxxxxxx NOT FOUND

Reason:
An attempt was made to analyze job xxxxxxxx. This job was not found in the CA
Workload Automation SE database.

Action:
Verify that the job name was specified correctly on the input command. If not, correct
and reenter the command.

1242 Message Reference Guide

 SANx

SANx-06

UNEXPECTED EOD WIP=xx

Reason:
An unexpected end-of-data occurred while processing the database. xx identifies where
the EOD was received.

Action:
Contact your installation specialist for assistance.

SANx-07

SCRATCH WORK FILE SPACE EXCEEDED

Reason:
Scratch work file space has been exhausted in processing the request.

Action:
Review the initialization file DAIO statement, SWFTRK parameter.

SANx-08

READ ERROR HAS OCCURRED WIP=xx RETURN CODE=nn

Reason:
A read error has occurred while accessing the CA Workload Automation SE database. xx
is where the macro call was issued in the program; nn is the return code from the call.

Action:
Contact your installation specialist for assistance.

SANx-09

WRITE ERROR HAS OCCURRED WIP=xx RETURN CODE=nn

Reason:
A write error has occurred while processing the CA Workload Automation SE database.
xx is where the macro call was issued in the program; nn is the return code from the call.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1243

SANx

SANx-10

NO MATCH FOUND FOR GENERIC REQUEST xxxxxxxx

Reason:
In attempting to process a generic request, no matching jobs or data sets were found.

Action:
Verify that the generic name was specified correctly. If not, correct and reenter the
command.

SANx-11

SPACE EXCEEDED IN DATASET DATA SET

Reason:
All data set space has been used in the CA Workload Automation SE Dataset data set.
The Dataset data set must be compressed before any new members can be added.

Action:
Shut down CA Workload Automation SE and compress the Dataset data set.

Note: The data set must not be compressed while CA Workload Automation SE is
active.

SANx-12

XREF TABLE SPACE EXCEEDED

Reason:
The incore table used to verify data set cross-reference entries has been exceeded.

Action:
The first 1000 entries will be processed and the command should be executed again if
more entries are to be "cleaned up."

1244 Message Reference Guide

 SANx

SANx-13

UNMATCHED xxxxxxxx FOR DSnnnnnn, DSN=yyyyyyyy

AND HAS zz USING JOBS
or
AND HAS BEEN DELETED ...TEST RUN

Reason:
This message appears whenever a data set record does not have a proper
corresponding IDS entry. The second line of the message indicates the record has jobs
using it. The third line indicates that it has been deleted. TEST RUN indicates no deletion
actually has been done because UPDATE=NO was specified. The xxxxxxxx in the first line
may indicate ORIGIN ERROR, INDEX ENTRY, or DATASET MEMBER to further clarify
where the discrepancy existed.

Action:
Using Database Maintenance functions, make the required corrections and delete the
data set record if necessary.

SANx-14

SCRATCH FILE SORT ERROR xx RETURN CODE= nn

Reason:
Error occurred while sorting information. A location code xx is followed by return code
nn from the sort.

Action:
Determine sort error and correct or contact your installation specialist for assistance.

SANx-15

NODE NOT FOUND... xxxxxxxx

Reason:
A node from a data set name was being searched for on the CA Workload Automation
SE IDS and was not found.

Action:
Determine whether the node is valid. If it is valid, establish the node on the IDS. If the
node is not valid, see that it is deleted.

Chapter 6: SANx - SJR2 Messages 1245

SANx

SANx-16

INDEX ERROR HAS OCCURRED WIP=xx RC=nn

Reason:
An error has occurred either in the attempt to TRIG process entries on the Index data
set (IDS) or to perform a TRIG command.

Action:
If xx=D4, the IDS can be full, or it sometimes requires a backup and a reload.

If xx=C4 and nn=01, check to ensure that the IDS contains at least one entry for each of
the following:
■ JDEP.
■ AUTO.
■ TRGD.

If one does not exist, add a dummy entry and reissue the command. For example, if you
have no data set trigger (AUTO.) entries, add a dummy entry and then try the TRIG
command.

SANx-19

NOT ENOUGH STORAGE

Reason:
An error occurred using the RESANL command. Not enough storage is available for
processing.

Action:
Allocate a larger REGION for CA Workload Automation SE.

1246 Message Reference Guide

 SANx

SANx-20

ERROR WHILE READ/WRITE OF JOB DATABASE, JOB=xxxxxxxx RC=nnnn WIP=w

Reason:
I/O or parameter error while accessing the CA Workload Automation SE database.
Where:
■ xxxxxxxx is the job name.
■ RC is the four-digit return code.
■ w is the code identifying where in the program the error occurred.

Action:
Contact your installation specialist for assistance. If the RC is 0 or 4, the job could have a
bad entry in the JOB data set. Do a DUMP,JOB=xxxxxxxx to get documentation of the
problem.

SANx-21

I/O ERROR OCCURRED WHILE PROCESSING JOB DATABASE, WIP= xx RETURN CODE=
nn

Reason:
An I/O error occurred while processing the Job database. xx is where the macro call was
issued in the program. nn is the return code from the call.

Action:
Contact your installation specialist for assistance.

SANx-22

MAXJOBS= EXCEEDS LIMIT VALUE

Reason:
A number greater than the limit value in the program was entered.

Action:
Enter a smaller value or contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1247

SANx

SANx-23

NUMBER OF JOBS IN QUEUES EXCEEDS MAXJOBS= nn

Reason:
Preliminary examination of the request, ready, and active queues found more jobs than
allowed by the MAXJOBS value.

Action:
Retry with a larger MAXJOBS entry. If the limit value of 4000 was used, wait for the
number of jobs in the queues to decrease.

SANx-25

SECURITY UID MUST BE 255 FOR THIS COMMAND

Reason:
One of the database analyze commands was issued, but the current USERID does not
have a UID level of 255 (allowing access to all jobs).

Action:
Log on to CA Workload Automation SE with a USERID that has a UID value of 255 and
then reissue the command.

SANx-29

OUTPUT TRUNCATED

Reason:
The RESANL command is generating more than 254 pages of output.

Action:
The command has to use a BTI or CAICCI terminal to get all the output.

1248 Message Reference Guide

 SANx

SANx-30

ERROR ON R/W OF DSDS, JOB=xxxxxxxx, DSN=PPnnnnnnnn, RC=rrrr, WIP=w

Reason:
I/O error accessing the Dataset data set. The job referenced by xxxxxxxx refers to the
data set PPnnnnnnnn, but the record was not found. rrrr is the four-digit return code; w
is the code identifying where in the program the error occurred.

Action:
Reload the job referenced in the message. If the LOAD is unsuccessful, run UCC7DBVR
for diagnostic information.

SANx-40

ERROR WHILE READ/WRITE OF SCRATCH FILE, RC=nnnn, WIP=w

Reason:
An I/O error occurred during access of the scratch queue. w is where the macro call was
issued in the program; nnnn is the return code from the call.

Action:
Verify that the scratch queue has sufficient space allocated. If the problem persists,
contact your installation specialist for assistance.

SANx-99

SORT I/O ERROR ON SCRATCH FILE, WIP= xx RETURN CODE= nn

Reason:
An I/O error occurred during a sort operation. xx is where the macro call was issued in
the program; nn is the return code from the call.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1249

SATO

SATO
SATO-01

xx INVALID MACRO RETURN CODE = nnnnnnnn

Reason:
The SASSSATO module has detected an error on return from a macro. The
where-in-program (WIP) value is specified by xx. The register 15 value (in hex) is
nnnnnnnn. Values xx=34, rc=4 indicate the trailer queue may be full.

Action:
For assistance, contact CA Support at ca.com/support.

SATO-15

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q'.

[AUTO|RPET] [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)]
DUE-OUT ON yy.ddd AT hhmm.

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that job xxxxxxxx entered the request queue because of the creation of an AUTO
(trigger) data set DSnnnnnnnn or a triggering job yyyyyyyy or the completion of input
network NWnnnnnnnn, or because the job is set to repeat.

Action:
None.

SATO-19

JOB xxxxxxxx(nnnn) ENTERED INTO REQUEST 'Q' TO DUMP LOG FILE

Reason:
Job xxxxxxxx has been automatically scheduled into the request queue because one of
the CA Workload Automation SE Log data sets is full.

Action:
None.

1250 Message Reference Guide

 SATO

SATO-20

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q'.

AUTO [(JOB=yyyyyyyy)|(DSN=bbbbbbbb)]
*** JCL RETRIEVED FROM SPECIAL OVERRIDE LIBRARY ***
DUE-OUT ON yy.ddd AT hhmm.

Reason:
See SATO-15. The JCL for job xxxxxxxx was retrieved from the special JCL Override library
(JCLID=254).

Action:
None.

SATO-35

JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. JOB LOCKED ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)]

Reason:
The indicated job was triggered by creation of a data set, network or completion of a
job, but could not be entered into the request queue because of a lock. (See message
SATO-15.)

Action:
Determine why the job is locked using LLOCK. Make corrections if the job should be
scheduled.

Chapter 6: SANx - SJR2 Messages 1251

SATO

SATO-36

JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'.

JOB NOT FOUND ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)] CODE=xxxxyyzz SCHID=sss

Reason:
The job was not entered into the request queue because it was not found in the CA
Workload Automation SE Job data set. Or the job may not have been added to the
request queue because the HIJBNUM (highest job number) has been reached. This
means that CA Workload Automation SE has no available job numbers to assign to this
job. (See also message SATO-15.)

CODE=xxxxyyzz will indicate the reason for the error. The xxxx is the WIP (Where In
Program) from SASSSCSR. The yy is the return code from a macro call. The zz is the
return code from SASSSCSR, generally this is 08.
0014
For yy=00, the request queue may have filled up. Use /DISPLAY,Q=ALL to check this.
For yy=05, the Trailer queue may have filled up.
0016
An error was returned attempting to issue a new CA Workload Automation SE job
number. Check the HIJBNUM to see if it has been reached.
0044
For yyzz=0108, check for database error messages (CA-7..Vnnn.
0055
An error was returned attempting to add JCL to the TRLQ. This could indicate a lack
of available space in the TRLQ.

Action:
If the job is to be run, use the Queue Maintenance DEMAND function to cause the job to
be scheduled and submitted for database entries to be built. If the HIJBNUM has been
reached, see SPO7-02 for the action.

1252 Message Reference Guide

 SATO

SATO-37

JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. CODE=cccccccc ***

AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)]

Reason:
The job was not entered into the request queue because of the indicated code. (See also
message SATO-15.)

Action:
Contact your installation specialist for assistance.

SATO-38

JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. llkkkkjj JCL ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)]

Reason:
The job was not entered into the request queue because an error was encountered
trying to process the JCL. The error may have been encountered while CA Workload
Automation SE was attempting to attach the job's JCL. The Trailer queue may not have
enough space. llkkkkjj is a return code describing the error. A jj value of 1C indicates that
JCL was not attached for the job. The kkkk value is the reason code for the attach failure.
See message SCNJ-18 for an explanation of this code. (See also message SATO-15 for a
description of the format of this message.)

Action:
See message SCNJ-18 for the corrective action.

SATO-39

JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. llkkkkjj JCL ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnnnn)]

Reason:
The job was not entered into the request queue because an error was encountered
trying to process the JCL retrieved from the special JCL Override library (JCLID=254).
llkkkkjj is a return code describing the error. A jj value of 1C indicates that JCL was not
attached for the job. The kkkk value is the reason code for the attach failure. See
message SCNJ-18 for an explanation of this code. (See also message SATO-15 for a
description of the format of this message.)

Action:
Review and correct the JCL from the special JCL Override library. Replace the JCL
member in the special library and then DEMAND the job.

Chapter 6: SANx - SJR2 Messages 1253

SATO

SATO-69

JOB jobname NOT TRIGGERED--DRCLASS class NOT ACTIVE

Reason:
The specified job is not being triggered because its disaster recovery class is not active.

Action:
None.

SATO-70

JOB xxxxxxxx (nnnn) IS BEING REPEATED: INTERVAL=hhmm TYPE=xxxxx

COUNT=nnnn STOP=ddd/hhmm LEADTM=hhmm DIFF=hhmm

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that the job will be re-added to the request queue (repeated). INTERVAL is the time that
will be added to the submit time requirement, start, or end time of this job (based on
the setting of TYPE) to determine the next iteration's submit time. TYPE can be CLOCK,
START, or END to indicate that the INTERVAL will be added to the submit time
requirement, start, or end time, respectively. COUNT (if non-zero) is the remaining
number of repetitions that can be made. STOP is the time after which the job will not be
repeated. LEADTM and DIFF are used in calculating the next iteration's due-out time and
deadline time. DIFF is added to the new job's submit time requirement to create the
due-out time. LEADTM is subtracted from the new due-out time to create the deadline
time.

Action:
None.

SATO-71

JOB xxxxxxxx (nnnn) *NOT* REPEATED--STOP TIME REACHED

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that the job is no longer being repeated because its stop time was reached.

Action:
None.

1254 Message Reference Guide

 SCMx Through SCM9

SCMx Through SCM9

SCMx-00

xxxxxxxx COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Command xxxxxxx was completed at the date and time noted.

Action:
None.

SCMx-02

xxxxxxxx=yyyyyyyy NOT FOUND

Reason:
Value yyyyyyyy for keyword xxxxxxxx is not known to CA Workload Automation SE.

Action:
Correct and resubmit the command.

SCMx-03

REQUIRED INPUT MISSING

Reason:
A required input keyword is missing from the command.

Action:
See command format in Command Reference Guide or HELP facility to determine
required keywords for the command issued. Enter required input and reissue the
command.

Chapter 6: SANx - SJR2 Messages 1255

SCMx Through SCM9

SCMx-04

CONFLICTING INPUT PARAMETERS

Reason:
Mutually exclusive keywords were input with the command.

Action:
See command format in Command Reference Guide or HELP facility to determine
required keywords for the command issued. Enter required input and reissue the
command.

SCMx-05

INVALID OR OMITTED xxxxxxxx=yyyyyyyy

Reason:
Value yyyyyyyy for keyword xxxxxxxx is invalid or is required but was not specified. For
SCM7-05, the yyyyyyyy is the first eight characters if the value is longer than eight
characters.

Action:
Correct and resubmit the command.

SCMx-06

DCB/ACB FAILED OPEN/CLOSE, RC=

Reason:
The /OPEN or /CLOSE command for a GROUP failed. The return code (RC=) is the
contents of register 15 from the CA Workload Automation SE subtask after the open or
close. (See also CA-7.V001.)

Action:
For VTAM groups, verify the APPL parameter of the UCC7VTAM initialization file
statement. Match the name of the APPL macro used to define CA Workload Automation
SE to VTAM. For other groups, verify that proper DD statements have been specified.

1256 Message Reference Guide

 SCMx Through SCM9

SCMx-10

FUNCTION NOT AVAILABLE -- RETRY LATER

Reason:
A /WLB,SET=OFF command was entered.

Action:
Enter a /WLB,SET=ON command to reactivate workload balancing.

SCMx-22

xxxxxxxx IS NOT LOGGED ON, MESSAGE NOT SENT

Reason:
Because the specified user is not logged on to CA Workload Automation SE, the message
was not queued to a logical terminal.

Action:
None.

SCMx-40

COMMAND xxxxxxxx IS NOT VALID FOR THIS TERMINAL.

Reason:
The command xxxxxxxx cannot be used from the current CA Workload Automation SE
terminal. Certain commands can only be entered from native VTAM access to CA
Workload Automation SE.

Action:
Use a terminal that supports that command to enter the command.

Chapter 6: SANx - SJR2 Messages 1257

SCMx Through SCM9

SCMx-45

TCP/IP TERMINAL INTERFACE IS ALREADY INITIALIZED

Reason:
The request to initialize the TCP/IP terminal interface failed because the interface is
already initialized.

Action:
If you want reinitialize TCP/IP, issue a /CLOSE command first.

Note: For the syntax for issuing the /CLOSE command for TCP/IP, see the Command
Reference Guide.

SCMx-46

ERROR TERMINATING TCP/IP TERMINAL INTERFACE

Reason:
An error occurred when terminating TCP/IP. TCP/IP is down after the command
completed and may have been down before the command was issued.

Action:
None.

SCMx-47

INITIALIZING TCP/IP TERMINAL INTERFACE

Reason:
The TCP/IP terminal interface is being initialized.

Action:
None.

1258 Message Reference Guide

 SCMx Through SCM9

SCMx-64

ERROR INITIALIZING TCP/IP TERMINAL INTERFACE

Reason:
An error occurred when initializing the TCP/IP terminal interface. Either TCP/IP could
not initialize or TCP/IP was already initialized.

Action:
Check the CA Workload Automation SE log for any CAL2Txxxx messages and take
appropriate action.

SCMx-65

ERROR: KEYWORD MISSING OR INVALID: xxxxxx

Reason:
Keyword xxxxxx was incorrectly specified or is not permitted on the command.

Action:
Correct the command and reenter.

SCMx-99

INVALID ERROR CODE

Reason:
Module SASSSCMx specified an error code, but that code has no error message defined.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

SCMJ-00

nnnn MESSAGES PURGED FROM LTERM=xxxxxxxx

Reason:
A request to purge pages of queued output was successfully completed.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1259

SCMx Through SCM9

SCMJ-01

xx INVALID MACRO RETURN CODE hhhhhhhh

Reason:
An unexpected error occurred while processing the purge page request. The xx
identifies the macro call, and the hhhhhhhh is the return value in register 15.

Action:
Contact your installation specialist for assistance.

SCMJ-15

NO PURGE -- TERM=xxxxxxxx CONNECTED TO LTERM=yyyyyyyy

Reason:
An attempt was made to purge messages queued to a logical terminal while its physical
terminal was being used by a different logical terminal.

Action:
Wait a few minutes and then reenter the command. If the response continues and you
can determine that the terminal is not in use, issue a /LOGOFF or a /STOP for the
terminal, and then retry the PURGPG.

SCMK-01

TCP/IP TERMINAL INTERFACE IS CLOSED

Reason:
The request to terminate the TCP/IP terminal interface completed successfully.

Action:
None.

SCMK-06

DDNAME FAILED OPEN/CLOSE RC=8

Reason:
The ddname indicated failed either an OPEN or CLOSE.

Action:
Try again. If the problem persists, contact your installation specialist for assistance.

1260 Message Reference Guide

 SCMx Through SCM9

SCMO-02

OPERATOR ID NOT SPECIFIED

Reason:
The operator ID (ID=) keyword is required.

Action:
Specify the id= keyword and reissue the command.

SCMO-12

INVALID id= KEYWORD; id={*|nnn}.

Reason:
When using the /COID,ID= command, an invalid value for the ID keyword was detected.
Valid values for the id= include only an asterisk (*) to list all information in the table or
one UID number (nnn) for a single entry.

Action:
Correct the id= specification. If no id= is coded, all UIDs are listed (as if id=* was coded).

SCMO-14

USERID TABLE NOT FOUND; NO COIDS EXIST.

Reason:
A USERID table was not found in the CA Workload Automation SE address space,
probably because the USERID= keyword was not coded on the SECURITY statement in
the initialization file. As a result, no correspondence IDs (COIDS) exist.

Action:
None.

SCMO-15

NO COIDS FOUND FOR SPECIFIED UID.

Reason:
A specific UID request was entered (/COID,ID=nnn), and the requested UID was found
not to have any correspondence IDs.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1261

SCMx Through SCM9

SCMO-16

INVALID UID; ENTER UID NUMBER FROM 1 TO 254.

Reason:
The specific UID entered in the id= parameter is not within the range of UID format.
UIDs for the /COID command range from 1 to 254, because 0 and 255 are reserved UIDs
for none or all privileges.

Action:
Reenter the command with the ID parameter specifying a number from 1 to 254.

SCMP-00

PROCESSING COMPLETE FOR .... /pa or /pf command string .....

Reason:
The /PAnn or /PFnn command has been processed successfully.

Action:
None. Issue /DISPLAY,ST=KEY to view your current session PA/PF key settings.

SCMP-48

PROFILE RECORD NOT FOUND - NO ACTION TAKEN

Reason:
The requested action cannot be performed because no CA Workload Automation SE
profile record was found in the database.

Action:
Use the /PROF command to define a CA Workload Automation SE profile record. If you
are using /PROFS command, check to ensure you entered the correct CA Workload
Automation SE userid on the id= keyword.

1262 Message Reference Guide

 SCMx Through SCM9

SCMP-49

NO PFKEYS DEFINED IN PROFILE - NO ACTION TAKEN.

Reason:
A /PROF(S),KEYS=PROFILE request cannot be satisfied because the CA Workload
Automation SE profile record has no PA/PF key definitions.

Action:
Use the /PROF command to display the contents of your CA Workload Automation SE
profile. If you want to clear the PA/PF key settings in your current terminal session, use
the /PF99 command.

SCMP-50

ID= KEYWORD ONLY VALID WITH /PROFS COMMAND.

Reason:
A /PROF command was entered with the id= keyword.

Action:
Use the /PROFS command if you want to display or update another user's CA Workload
Automation SE profile.

SCMP-51

CURRENT SESSION REFRESHED WITH PFKEYS FROM PROFILE.

Reason:
The PA/PF key definitions for your current terminal session have been replaced with the
definitions in your CA Workload Automation SE profile. If you are using the /PROFS,ID=
format your keys have been replaced by those in the id= user's CA Workload
Automation SE profile.

Action:
None. Use the /DISPLAY,ST=KEY command to view your current terminal session PA/PF
key settings.

Chapter 6: SANx - SJR2 Messages 1263

SCMx Through SCM9

SCMP-52

PROFILE RECORD UPDATED FOR xxxxxxxx

Reason:
The PA/PF key definitions, the UID resource name in the CA Workload Automation SE
profile for user xxxxxxx, or both have been successfully updated.

Action:
None. Use the /PROF or /PROFS,ID= command to display the contents of the CA
Workload Automation SE user profile.

SCMP-53

PROFILE RECORD DELETED FOR xxxxxxxx

Reason:
The CA Workload Automation SE profile record for user xxxxxxxx has been deleted from
the database. This is in response to a /PROF(S),ST=DELETE command.

Action:
None.

SCMP-54

KEYS= AND/OR R= KEYWORDS INVALID WITH STATUS=DELETE.

Reason:
A /PROF(S),ST=DELETE command was entered with the KEYS= keyword, R= keyword, or
both. These are conflicting options since, in effect, you are asking to both update and
delete the profile record.

Action:
To delete the profile record, use only the STATUS=DELETE operand. To update or access
the profile record, use the KEYS= or R= keywords.

1264 Message Reference Guide

 SCMx Through SCM9

SCMP-55

PROFILE I/O ERROR. USER=uuuuuuuu FUNC=ff RC=rr FDBK=kkkk

Reason:
A database error was encountered attempting to access or act on the CA Workload
Automation SE profile record for user uuuuuuuu. The IO function (ff) return code (rr)
and feedback code (kkkk) are listed.

Action:
Contact your installation specialist for assistance.

SCMP-57

INVALID PA/PF KEY SPECIFIED.

Reason:
A /PA or /PF command was entered for an undefined PA or PF key. Valid PA keys are
PA01 - PA03. Valid PF keys are PF01 - PF24. The special command /PF99 causes any
PA/PF keys defined for the current terminal session to be deleted.

Action:
Enter a valid key.

SCMP-58

MIS-MATCHED PARENTHESES ON MSG= OPERAND.

Reason:
A /PA or /PF command was entered with unbalanced parentheses in the text associated
with the MSG= or M= keyword. The maximum length of the MSG= parameter is 60
characters (including parentheses).

Action:
Ensure the parentheses on the MSG= parameter are balanced.

Chapter 6: SANx - SJR2 Messages 1265

SCMx Through SCM9

SCMP-59

MSG= VALUE INVALID. MAX LENGTH IS 60.

Reason:
A /PA or /PF command was entered with invalid data in the MSG= or M= parameter. The
maximum length of the MSG= parameter is 60 characters (including parentheses).

Action:
Reenter the value.

SCMP-60

NO PA/PFKEYS DEFINED FOR CURRENT TERMINAL SESSION.

USE KEYS=CLEAR TO DELETE.

Reason:
A /PROF(S) command was entered with the KEYS=SAVE parameter; however, no PA or
PF keys are defined for the current terminal session.

Action:
Use the /PROF,KEYS=CLEAR command if the intent is to clear the PA/PF key definitions
in the profile record. If you want to add PA/PF key definitions to the profile, you must
first define them to your current terminal session using the /PA commands, the /PF
commands, or both.

SCMP-61

MSG= KEYWORD REQUIRED WITH /PA OR /PF COMMAND.

Reason:
A /PA or /PF command was entered without any MSG= or M= keyword. The MSG= (or
M=) keyword is required.

Action:
Use the MSG= keyword with no command text if you want to get rid of a current
definition.

1266 Message Reference Guide

 SCMx Through SCM9

SCMP-62

KEYS= OPTION INVALID. VALID OPTIONS ARE: SAVE, PROFILE AND CLEAR.

Reason:
A /PROF(S) command was entered with the KEYS= (or K=) keyword, but the parameter is
invalid. The valid options for the KEYS= keyword are SAVE, PROFILE, and CLEAR.

Action:
Correct the command and reenter.

SCMP-63

PROGRAM LOGIC ERROR AT LABEL xxxxxxxx

Reason:
A program logic error occurred attempting to satisfy a /PF, /PA, or /PROF(S) command
at label xxxxxxxx.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

SCMQ-66

ERROR: ADD REQUESTED BUT INDEX ALREADY DEFINED

Reason:
An attempt was made to add a JCL library with an index which already exists.

Action:
Select a different index and reenter.

SCMQ-68

ERROR: UPD REQUESTED BUT INDEX NOT FOUND.

Reason:
An update or delete was attempted for a JCL library index does not exist.

Action:
Determine the correct JCL library index and reenter.

Chapter 6: SANx - SJR2 Messages 1267

SCMx Through SCM9

SCMQ-69

ERROR: VSAM I/O UNSUCCESSFUL. FUNC=xx RC=xxxx FDBK=xxxx

Reason:
An error occurred during I/O to the JCL library database.

Action:
Contact your installation specialist for assistance.

SCMQ-71

ERROR: UPD REQUESTED BUT ENTRY IN USE.

Reason:
An update was attempted for a JCL library index which is currently allocated.

Action:
Wait until the requested JCL library index is not in use and reenter.

SCMQ-72

ERROR: DEL REQUESTED BUT ENTRY IN USE.

Reason:
A delete was attempted for a JCL library index which is currently allocated.

Action:
Wait until the requested JCL library index is not in use and reenter.

SCMQ-73

ERROR: INVALID OPERATION ON HELP LIBRARY

Reason:
The requested action is not valid on the HELP library.

Action:
None.

1268 Message Reference Guide

 SCMx Through SCM9

SCMQ-74

WARNING! JCL INDEX DELETED IS REFERRED TO AS AN ALTERNATE.

Reason:
The /JCL command was used to delete a JCL library definition. Another JCL definition
referred to the index as an alternate.

Action:
Review the JCL library definitions using /DISPLAY,ST=JCLVAR. Use /JCL to remove ALT
references to the deleted index.

SCMQ-75

CANNOT USE /JCL WITHOUT DYNAMIC ALLOCATION OF JCL LIBRARIES.

Reason:
The /JCL command was attempted, but dynamic allocation of JCL libraries is not
supported.

Action:
Change the PERFORM values on the INIT statement in the product's initialization file so
that dynamic allocation will be used for JCL libraries. See the Systems Programming
Guide for details.

SCMR-01

EMAIL INTERFACE NOT INITIALIZED

Reason:
Either the /EMAIL or /EADMIN command was issued, but the EMAIL initialization file
statement was either not present at CA Workload Automation SE startup or it was not
successfully processed.

Action:
Provide or correct the EMAIL initialization file statement and restart CA Workload
Automation SE.

Chapter 6: SANx - SJR2 Messages 1269

SCMx Through SCM9

SCMR-02

TRC KEYWORD MUST BE Y OR N

Reason:
The /EADMIN command was issued with an invalid value for the TRC keyword.

Action:
Correct the command and reissue.

SCMR-03

ENABLE KEYWORD MUST BE Y OR N

Reason:
The /EADMIN command was issued with an invalid value for the ENABLE keyword.

Action:
Correct the command and reissue.

SCMR-04

ETIMEOUT MUST BE IN THE RANGE 5 TO 20 SECONDS

Reason:
The /EADMIN command was issued with an invalid value for the ETIMEOUT keyword.

Action:
Correct the command and reissue.

SCMR-05

INVALID OR OMITTED VALUE ON KEYWORD xxxxxxxx

Reason:
The /EADMIN command was issued with an invalid value on the specified keyword.

Action:
Correct the command and reissue.

SCMR-06

DEFAULT EMAIL REPLY ADDRESS UPDATED

1270 Message Reference Guide

 SCMx Through SCM9

SCMR-06

EMAIL "FROM:" NAME UPDATED

SCMR-06

EMAIL TIMEOUT VALUE UPDATED

SCMR-06

EMAIL GLOBAL TRACE TURNED ON|OFF

SCMR-06

EMAIL INTERFACE ENABLED|DISABLED

Reason:
The /EADMIN command was issued and has successfully updated the listed EMAIL
global options.

Action:
None.

SCMR-07

EMAIL INTERFACE IS NOT ENABLED

Reason:
The /EMAIL command has been issued, but the email interface has been disabled by a
/EADMIN,ENABLE=N command.

Action:
Enable the email interface by issuing /EADMIN,ENABLE=Y, and then reissue the /EMAIL
command.

SCMR-08

NO EMAIL UPDATES WERE MADE

Reason:
The /EADMIN command was issued without any keywords. No changes were made to
the email global options.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1271

SCMx Through SCM9

SCMR-09

MISSING OR INVALID TO=

Reason:
The /EMAIL command was issued either without the TO keyword or with an invalid
value.

Action:
Correct the command and reissue.

SCMR-10

MISSING OR INVALID TXT=

Reason:
The /EMAIL command was issued either without the TXT keyword or with an invalid
value.

Action:
Correct the command and reissue.

SCMR-11

INVALID JOB=

Reason:
The /EMAIL command was issued with the JOB keyword, but the value of the JOB
keyword is not a valid job name or job number.

Action:
Correct the command and reissue.

SCMR-12

INSUFFICIENT STORAGE FOR WORK AREA

Reason:
The /EMAIL command was unable to obtain enough storage to process the request.

Action:
Try the command later. If the problem persists, contact CA Support at ca.com/support
for assistance.

1272 Message Reference Guide

 SCMx Through SCM9

SCMR-13

JOB xxxxxxxx NOT FOUND

Reason:
The /EMAIL command was issued with the JOB keyword, but the job could not be found
in the REQ, RDY, or ACT queues.

Action:
Correct the command and reissue.

SCMR-14

UNABLE TO READ ADDRESS MEMBER xxxxxxxx

Reason:
The /EMAIL command could not locate the specified member in the EADDRLIB PDS.

Action:
Either add the member to the EADDRLIB PDS or correct the command.

SCMR-15

MORE THAN 100 EMAIL ADDRESSES WERE FOUND IN MEMBER xxxxxxxx

Reason:
The /EMAIL command found more than 100 email addresses in the specified member.
/EMAIL supports sending an email to a maximum of 100 recipients.

Action:
Correct the EADDRLIB member to have a maximum of 100 email addresses. If more than
100 recipients are needed, build additional EADDRLIB members and issue multiple
/EMAIL commands.

SCMR-16

ZERO EMAIL ADDRESSES WERE FOUND IN MEMBER xxxxxxxx

Reason:
The /EMAIL command did not find any email addresses in the specified EADDRLIB
member. At least one email address is required.

Action:
Correct the EADDRLIB member and reissue the command.

Chapter 6: SANx - SJR2 Messages 1273

SCMx Through SCM9

SCMR-17

UNABLE TO READ TEMPLATE MEMBER xxxxxxxx

Reason:
The /EMAIL command could not locate the specified member in the EMAILLIB PDS.

Action:
Either add the member to the EMAILLIB PDS or correct the command.

SCMR-18

MORE THAN 100 EMAIL TEMPLATE LINES WERE READ FROM MEMBER xxxxxxxx

Reason:
The /EMAIL command found more than 100 lines in the specified member. /EMAIL
supports a maximum of 100 lines of email template.

Action:
Correct the EMAILLIB member to have a maximum of 100 lines.

SCMR-19

ZERO EMAIL TEMPLATE LINES WERE FOUND IN MEMBER xxxxxxxx

Reason:
The /EMAIL command found an empty EMAILLIB PDS member.

Action:
Correct the EMAILLIB member and reissue the command.

SCMR-21

BAD RETURN FROM CAL2EML2 RC=xx

Reason:
The /EMAIL command had an internal error.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

1274 Message Reference Guide

 SCMx Through SCM9

SCMR-22

NO STORAGE AVAILABLE FOR EMAIL REQUEST

Reason:
The /EMAIL command could not obtain enough storage to process the request.

Action:
Try the command later. If the problem persists, contact CA Support at ca.com/support
for assistance.

SCMR-23

EMAIL REQUEST SUCCESSFULLY QUEUED

Reason:
The /EMAIL command has successfully completed. A request to send the email has been
queued to the email subtask and will be processed in the order received.

Action:
None.

SCMR-24

INVALID VALUE IN VAR=

Reason:
One or more of the values in the VAR= keyword are invalid. They can be more than 8
characters long or contain invalid characters.

Action:
Correct the command and reissue.

SCMR-25

INVALID INPUT

Reason:
The /EADMIN command was issued with invalid keywords.

Action:
Correct the command and reenter.

Chapter 6: SANx - SJR2 Messages 1275

SCMx Through SCM9

SCMR-26

INVALID INPUT

Reason:
The /EMAIL command was issued with invalid keywords.

Action:
Correct the command and reenter.

SCMS-01

MISSING OR INVALID MODE=

Reason:
The /DRMODE command was issued with the MODE= keyword. The value on the
MODE= keyword is invalid. Valid values are DR or NORM.

Action:
Correct the command and reissue.

SCMS-02

MISSING OR INVALID TRIGGERS=

Reason:
The /DRMODE command was issued with the TRIGGERS= keyword. The value on the
TRIGGERS= keyword is invalid. Valid values are DR, ALL, or NONEXEC.

Action:
Correct the command and reissue.

SCMS-03

MISSING OR INVALID RQMTS=

Reason:
The /DRMODE command was issued with the RQMTS= keyword. The value on the
RQMTS= keyword is invalid. Valid values are DR or ALL.

Action:
Correct the command and reissue.

1276 Message Reference Guide

 SCMx Through SCM9

SCMS-04

MISSING OR INVALID DEFCLASS=

Reason:
The /DRMODE command was issued with the DEFCLASS= keyword. The value on the
DEFCLASS= keyword is invalid. Valid values are one to eight characters long.

Action:
Correct the command and reissue.

SCMS-05

NO DRMODE UPDATES WERE MADE

Reason:
The /DRMODE command was issued without any keywords.

Action:
Correct the command and reissue.

SCMS-06

DISASTER RECOVERY MODE TURNED OFF|ON

SCMS-06

TRIGGERS OPTION UPDATED

SCMS-06

RQMTS OPTION UPDATED

SCMS-06

DEFAULT DRMODE CLASS UPDATED

Reason:
The /DRMODE command was issued and successfully updated the listed disaster
recovery options.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1277

SCMx Through SCM9

SCMS-07

MISSING OR INVALID CLASS=

Reason:
The /DRCLASS command was issued. The CLASS= keyword was either not specified or
entered with invalid data. The CLASS= keyword is required and should have one to eight
disaster recovery classes, each of which is one to eight alphanumeric characters.

Action:
Correct the command and reissue.

SCMS-08

INVALID ACT=

Reason:
The /DRCLASS command was issued with the ACT= keyword. The value on the ACT=
keyword is invalid. Valid values are ADD or DEL.

Action:
Correct the command and reissue.

SCMS-09

CLASS(ES) [ADDED TO| DELETED FROM] THE ACTIVE DISASTER RECOVERY CLASS TABLE

Reason:
The /DRCLASS has successfully updated the active disaster recovery class list.

Action:
None.

SCMS-10

**** DISASTER RECOVERY MODE TURNED OFF

Reason:
The /DRMODE,MODE=NORM command was issued to dynamically turn off disaster
recovery mode. This message is issued to the browse log.

Action:
None.

1278 Message Reference Guide

 SCMx Through SCM9

SCMS-11

**** DISASTER RECOVERY MODE TURNED **ON**

Reason:
The /DRMODE,MODE=DR command was issued to dynamically turn on disaster recovery
mode. This message is issued to the browse log and is followed by SCMS-12 listing the
active disaster recovery classes.

Action:
None.

SCMS-12

ACTIVE DISASTER RECOVERY CLASS: xxxxxxxx

Reason:
The /DRMODE,MODE=DR command was issued to dynamically turn on disaster recovery
mode, or the /DRCLASS command was issued to add or remove a disaster recovery class
to the active disaster recovery class list. This message is issued for each disaster
recovery class that is active.

Action:
None.

SCMS-13

INVALID INPUT

Reason:
The /DRMODE command was issued with invalid keywords.

Action:
Correct the command and reenter.

SCMS-14

INVALID INPUT

Reason:
The /DRCLASS command was issued with invalid keywords.

Action:
Correct the command and reenter.

Chapter 6: SANx - SJR2 Messages 1279

SCMx Through SCM9

SCMT-01

PRODUCT INTERFACE TASK IS NOT ACCEPTING WORK

Reason:
The CA Workload Automation SE product interface task was either never initialized or
has been disabled due to a error condition. The product interface task is initialized when
a supported product interface, such as SERVICEDESK, is specified in the initialization file.

Action:
Make sure that the SERVICEDESK initialization file statement is specified in the product's
initialization file, and then restart CA Workload Automation SE.

SCMT-02

SERVICE DESK INTERFACE NOT ACTIVE

Reason:
The CA Service Desk interface has not been initialized.

Action:
Add the SERVICEDESK initialization file statement to the product's initialization file, and
then restart CA Workload Automation SE.

SCMT-03

EVENT= IS MISSING OR INVALID

Reason:
EVENT= is required on the /SDESK command and must specify a six-character CAISDI/els
event name.

Action:
Correct the command and reenter.

1280 Message Reference Guide

 SCMx Through SCM9

SCMT-04

EVENT= MUST BE EXACTLY SIX CHARACTERS LONG

Reason:
EVENT= was entered on the /SDESK command, but it did not specify a six-character
value.

Action:
Correct the command and reenter.

SCMT-05

JOB= IS INVALID

Reason:
The value specified on the JOB keyword on the /SDESK command is not a job name or
CA 7 WA job number.

Action:
Correct the command and reenter.

SCMT-06

UNABLE TO FIND JOB xxxxxxxx

Reason:
CA Workload Automation SE was unable to find the specified job in the request, ready,
or active queues.

Action:
Correct the command and reenter.

SCMT-07

SERVICE DESK REQUEST QUEUED

Reason:
The /SDESK command has been successfully processed and has been queued to the
product interface task to open a request in CA Service Desk.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1281

SCMx Through SCM9

SCMT-08

SYNTAX ERROR IN COMMAND

Reason:
The /SDESK command was entered with an invalid syntax, such as an unexpected
keyword.

Action:
Correct the command and reenter.

SCMT-09

INVALID VALUE xxxxxx=y

Reason:
The value y specified on keyword xxxxxx is invalid.

Action:
Correct the command and reenter.

SCMT-11

ARM FUNCTION SUCCESSFUL

Reason:
The /STATEMGR command was successful for the ARM function requested.

Action:
None.

SCMT-12

ARM FUNCTION FAILED, CHECK JES MESSAGES

Reason:
An error occurred processing the /STATEMGR command for the ARM interface. Detailed
error codes are in the JES messages for the online task.

Action:
Perform the following actions:
■ Review the JES messages.
■ Take the action associated with those messages.

1282 Message Reference Guide

 SCMx Through SCM9

SCMT-13

OPS/MVS SSM FUNCTION SUCCESSFUL

Reason:
The /STATEMGR command was successful for the CA OPS/MVS EMA SSM function
requested.

Action:
None.

SCMT-14

OPS/MVS SSM FUNCTION FAILED, CHECK JES MESSAGES

Reason:
An error occurred processing the /STATEMGR command for the CA OPS/MVS EMA SSM
interface. The JES messages for the online task contain detailed error codes.

Action:
Perform the following actions:
■ Review the JES messages.
■ Take the action associated with those messages.

SCMV-81

ERROR: ADD REQUESTED BUT VARIABLE ALREADY DEFINED

Reason:
The user attempted to add a global variable, but the variable already exists.

Action:
Display the global variables to determine that the variable does, in fact, exist. If job,
system, and/or schid values were included on the add attempt, verify they exist for the
variable. If the variable name/job/system/schid combination exists, either update it or
delete it and add another. If it does not exist, attempt another add. If that attempt fails,
contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1283

SCMx Through SCM9

SCMV-82

ERROR: DEL REQUESTED BUT VARIABLE NOT FOUND

Reason:
The user attempted to delete a global variable, but the variable was not found.

Action:
Display the global variables to determine that the variable does not exist. If it does not,
no further action is necessary. If job, system, and/or schid values were included on the
delete attempt, and they do exist for the variable, attempt to update one of those
values. If the update works, attempt a delete with the new values. If the update fails or
the second delete fails, contact your installation specialist for assistance.

SCMV-83

ERROR: UPD REQUESTED BUT VARIABLE NOT FOUND

Reason:
The user attempted to update a global variable, but the variable was not found.

Action:
Display the global variables to determine that the variable exists. If the global variable
exists with the combination of job, system and schid values in your update request,
make a note of the values. Delete the global variable and add it back with the new,
updated values. Then contact your installation specialist.

SCMV-84

VARIABLE NAME IS RESERVED

Reason:
The user attempted to add a global variable whose name is reserved. The system does
not permit users to determine the values for reserved global variables.

Action:
Select a different name for the variable you are attempting to add. Ensure that the
name is not on the reserved list.

1284 Message Reference Guide

 SCMx Through SCM9

SCMV-85

nnnnn VARIABLES DELETED

Reason:
The user has deleted nnnnn global variables. This message is issued only if more than
one global variable is deleted.

Action:
None.

SCMV-91

COMMAND IS UNAVAILABLE

Reason:
The command cannot be issued. Both global variables and CA-Driver are unavailable.

Action:
If the command is necessary, set GVARSUB=YES on the OPTIONS statement in the
initialization file. Alternatively, insert a //CARPROC DD statement in the CA7ONL JCL.
Then bring down and restart CA7ONL.

SCMW-01

ERROR: SCRATCH FILE FOR PASS-THRU AFM NEVER CREATED

Reason:
An edit file did not exist for an AFM Pass-Thru request.

Action:
Use the JCL/EDIT function to create a scratch file.

SCMW-02

ERROR: NO PASS-THRU AFM DATA IN SCRATCH FILE

Reason:
The edit file for the AFM Pass-Thru request was empty.

Action:
Add the appropriate data to the JCL/EDIT session.

Chapter 6: SANx - SJR2 Messages 1285

SCMx Through SCM9

SCMW-03

ERROR: UNABLE TO READ LINES IN THE SCRATCH FILE

Reason:
An attempt to read the edit scratch file used during an AFM Pass-Thru session failed.
You may have a problem with your CA Workload Automation SE scratch file allocation.

Action:
Contact your installation specialist for assistance.

SCMW-04

ERROR: AFM INVALID, NO MFUSER SUPPLIED

Reason:
The AFM Pass-Thru was missing a required value.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

SCMW-05

ERROR: AFM INVALID, USER ID > 128 BYTES

Reason:
The AFM Pass-Thru USER value exceeded 128 bytes.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

SCMW-06

ERROR: AFM INVALID, NO PASSWORD SUPPLIED

Reason:
The AFM Pass-Thru syntax for PASSWORD is incorrect.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

1286 Message Reference Guide

 SCMx Through SCM9

SCMW-07

ERROR: NO AGENT ENVIRONMENT EXISTS, CANNOT EXECUTE /AFM COMMAND

Reason:
CA Workload Automation SE was started with the Agent feature disabled.

Action:
Perform the following actions:
■ Contact your installation specialist for assistance.
■ Set AGENTJOB=YES on the XPDEF statement in the initialization file.
■ Recycle CA Workload Automation SE.

SCMW-08

ERROR: COMMON MODULE SASSAFM2 NOT FOUND, COMMAND NOT ALLOWED

Reason:
A critical module needed to support Agent job submission was missing. Your installation
of CA Workload Automation SE has a problem.

Action:
Contact your installation specialist for assistance.

SCMW-09

ERROR: USER-ID NOT SUPPLIED ON /AFM COMMAND

Reason:
The AFM Pass-Thru syntax for USER is incorrect.

Action:
For assistance, contact CA Support at ca.com/support for assistance.

Chapter 6: SANx - SJR2 Messages 1287

SCMx Through SCM9

SCMW-10

description

Reason:
The AFM Pass-Thru request failed. The common command module returns the cause of
the error in the description field.

Action:
Perform the following actions:
■ Make a note of the descriptive text that accompanied this message.
■ For assistance, contact CA Support at http://ca.com/support.

SCMW-11

ERROR: DIVR NON-ZERO RETURN CODE xxxxxxxx

Reason:
The CA Integrated Agent Services (CA IAS) interface did not complete the AFM Pass-Thru
request successfully.

Action:
Perform the following actions:
■ Make a note of the return code that accompanied this message.
■ For assistance, contact CA Support at http://ca.com/support.

SCMW-12

ERROR: WRITE TO SCRATCH FILE NOT SUCCESSFUL, RC=xxxx

Reason:
An attempt to write to the edit scratch file used during an AFM Pass-Thru session failed.
You may have a problem with your CA Workload Automation SE scratch file allocation.

Action:
Perform the following actions:
■ Make a note of the RC value.
■ Contact your installation specialist for assistance.

1288 Message Reference Guide

 SCMx Through SCM9

SCMW-13

ERROR: CLOSE OF SCRATCH FILE NOT SUCCESSFUL, RC=xxxx

Reason:
An attempt to close to the edit scratch file used during an AFM Pass-Thru session failed.
You may have a problem with your CA Workload Automation SE scratch file allocation.

Action:
Perform the following actions:
■ Make a note of the RC value.
■ Contact your installation specialist for assistance.

SCMW-14

ERROR: CONVERT TO EDIT NOT SUCCESSFUL, RC=xxxx

Reason:
An attempt to convert the edit scratch file used during an AFM Pass-Thru session to
readable data failed.

Action:
Perform the following actions:
■ Make a note of the RC value.
■ For assistance, contact CA Support at http://ca.com/support.

SCMW-15

ERROR: SCRATCH FILE GET FOR UPDATE NOT SUCCESSFUL, RC=xxxx

Reason:
An attempt to get the edit scratch file used during an AFM Pass-Thru session for
updating failed. You may have a problem with your CA Workload Automation SE scratch
file allocation.

Action:
Perform the following actions:
■ Make a note of the RC value.
■ Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1289

SCMx Through SCM9

SCMW-16

ERROR: SCRATCH FILE UPDATE NOT SUCCESSFUL, RC=xxxx

Reason:
An attempt to update the edit scratch file used during an AFM Pass-Thru session failed.
You may have a problem with your CA Workload Automation SE scratch file allocation.

Action:
Perform the following actions:
■ Make a note of the RC value.
■ Contact your installation specialist for assistance.

SCMW-17

ERROR: USER-ID NOT DEFINED, NO PASSWORD FOUND

Reason:
The AFM Pass-Thru USER-ID did not have an associated password.

Action:
Create an Agent User-ID/Password association using the AGPSWD command.

Note: For more information about the AGPSWD command, see the Database
Maintenance Guide.

SCMW-65

ERROR: KEYWORD MISSING OR INVALID: AGENT

Reason:
The AFM Pass-Thru did not contain the AGENT keyword.

Action:
For assistance, contact CA Support at ca.com/support.

1290 Message Reference Guide

 SCMx Through SCM9

SCMY-00

/IAS COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The /IAS command entered completed successfully on the time and date shown.

Action:
None.

SCMY-02

CONFIGURE FAILED, SEE OTHER MESSAGES FOR REASON(S), RC=sxxxx

Reason:
The /IAS,FUNC=RECONFIG command failed. Other messages that accompany this
message identify the cause.

Action:
Perform the action indicated in the other messages that are issued with this message.

SCMY-03

CONFIGURE FAILED, IASMOBJR RC=sxxxx

Reason:
The /IAS,FUNC=RECONFIG command failed. The signed return code identifies the cause
of the failure.

Action:
Perform the following actions:
■ Make a note of the IASMOBJR return code.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 6: SANx - SJR2 Messages 1291

SCMx Through SCM9

SCMY-04

AGLOGON CA 7 AFM TRACE ALREADY ACTIVE

Reason:
The /IAS,FUNC=AGLOGON command was issued, but the CA Workload Automation SE
AFM tracing facility is already active.

Action:
None.

SCMY-05

START COMMUNICATIONS FAILED, SEE OTHER MESSAGES FOR REASON(S), RC=sxxxx

Reason:
The /IAS,FUNC=STARTCOM command failed. This can occur if the agent configuration
file has errors. Check the CA Workload Automation SE JES2 JOBLOG for other messages
relating to CA Integrated Agent Services (CA IAS) to identify the cause of the start
communications failure.

Action:
Perform the action indicated in the other messages that may cause the generation of
this message.

SCMY-06

START COMMUNICATIONS FAILED, IASMOBJR RC=sxxxx

Reason:
The /IAS,FUNC=STARTCOM command failed. The signed return code identifies the cause
of the failure.

Action:
Perform the following actions:
■ Make a note of the IASMOBJR return code.
■ For assistance, contact CA Support at http://ca.com/support.

1292 Message Reference Guide

 SCMx Through SCM9

SCMY-07

AGLOGOFF CA 7 AFM TRACE ALREADY INACTIVE

Reason:
The /IAS,FUNC=AGLOGOFF command was issued, but the CA Workload Automation SE
AFM tracing facility is already inactive.

Action:
None.

SCMY-08

SHUTDOWN COMMUNICATIONS FAILED, SEE OTHER MESSAGES FOR REASON(S),

RC=sxxxx

Reason:
The /IAS,FUNC=STOPCOM command failed. Other messages that accompany this
message identify the cause.

Action:
Perform the action indicated in the other messages that accompany this message.

SCMY-09

Reason:
The /IAS,FUNC=STOPCOM command failed. The signed return code identifies the cause
of the failure.

Action:
Perform the following actions:
■ Make a note of the IASMOBJR return code.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 6: SANx - SJR2 Messages 1293

SCMx Through SCM9

SCMY-11

CANNOT START COMMUNICATIONS UNLESS PREVIOUSLY SHUTDOWN

Reason:
The /IAS,FUNC=STARTCOM command was issued, but communications are already
started.

Note: If you want to use this command, you usually need to issue a
/IAS,FUNC=STOPCOM command first.

Action:
None.

SCMY-12

CANNOT STOP SHUTDOWN COMMUNICATIONS UNLESS PREVIOUSLY STARTED

Reason:
The /IAS,FUNC=STOPCOM command was issued but communications are already
stopped.

Note: If you want to start already stopped communications, issue a

/IAS,FUNC=STARTCOM command.

Action:
None.

1294 Message Reference Guide

 SCMx Through SCM9

SCMY-13

/IAS,FUNC=xxxxxxxx ISSUED BY userid COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The /IAS command entered completed successfully on the time and date shown.
xxxxxxxx can be either RECONFIG, STARTCOM, or STOPCOM. This message only appears
in the browse data set for the following /IAS functions: RECONFIG, STARTCOM, and
STOPCOM. The command provides an audit trail for who issued the command when.

Note: This message can appear in the browse data set without the SCMY-00 prefix. In
these instances, check the browse data set for SCMY-xx error message appearing
immediately before this message.

Action:
Consider the following actions:
■ No action is necessary if the prefix SCMY-00 is present.
■ See the other SCMY-xx messages for actions you might need to take if the SCMY-00
prefix is not present.

SCMY-65

ERROR: KEYWORD MISSING OR INVALID: xxxxxxxx

Reason:
Keyword xxxxxxxx was incorrectly specified or is not permitted on the command.

Action:
Correct the command and reenter.

SCMY-88

*** IAS IS NOT ACTIVE OR NOT INITIALIZED

Reason:
CA Integrated Agent Services (CA IAS) is not supported or did not initialize correctly.

Action:
Check CA Workload Automation SE startup messages for CA IAS related errors.

Chapter 6: SANx - SJR2 Messages 1295

SCMx Through SCM9

SCMY-90

*** IASMLOG INTERNAL ERROR, RC=xxxx

Reason:
CA Integrated Agent Services (CA IAS) encountered an internal error. The return code is
listed.

Action:
Contact your installation specialist for assistance.

SCMY-91

*** IAS LOGGER FILE ALLOCATION ERROR

Reason:
CA Integrated Agent Services (CA IAS) encountered an error trying to allocate a sysout
file for printing the CA IAS log.

Action:
Check the CA Workload Automation SE JES messages for related information. Contact
your installation specialist for assistance.

SCMY-92

*** IAS LOGGER FILE OPEN ERROR

Reason:
CA Integrated Agent Services (CA IAS) encountered an error trying to open a sysout file
for printing the CA IAS log.

Action:
Check the CA Workload Automation SE JES messages for related information. Contact
your installation specialist for assistance.

1296 Message Reference Guide

 SCMx Through SCM9

SCMY-94

*** NO AGENT JOB ENVIRONMENT EXISTS

Reason:
The current command requires agent job support, and it is not supported in the current
CA Workload Automation SE environment.

Action:
Ensure AGENTJOB=YES is coded on the XPDEF CA Workload Automation SE initialization
statement. If not, add it, and cycle CA Workload Automation SE.

SCM0-00

MSG FROM TERM - xxxxxxxx

text...

Reason:
This message precedes free-form message text sent from terminal xxxxxxxx.

Action:
None.

SCM0-11

[(TERM)|(LTERM)] = yyyyyyyy IS NOT AVAILABLE FOR OUTPUT

Reason:
Terminal yyyyyyyy is currently closed and cannot receive the message being sent or
copied.

Action:
To send output to the closed terminal, the terminal must be started using /START
command. Then reenter the original command.

Chapter 6: SANx - SJR2 Messages 1297

SCMx Through SCM9

SCM0-12

HARDCOPY DEVICE NOT FOUND.

Reason:
PF2 (Program Function key 2) or the /COPY command was used to copy a page of output
from a 3270 terminal to a hardcopy terminal. To use this facility, a hardcopy terminal
must be present on the same line as the terminal issuing the command.

Action:
If it is necessary to copy the page, the /COPY command must be used to indicate a
specific terminal where the page is to be sent.

SCM0-14

MESSAGE HAS BEEN QUEUED ON LTERM xxxxxxxx

Reason:
This message appears at the sending terminal to indicate successful transfer of the
output. The receiving terminal, however, is busy. The output has been queued for
review as soon as the receiving terminal is available.

Action:
None.

SCM0-17

PROCESSING COMPLETED FOR xxxxxxxx

Reason:
The xxxxxxxx command processing was completed. This message is issued for /RESET
and /SWAP.

Action:
None.

1298 Message Reference Guide

 SCMx Through SCM9

SCM0-22

xxxxxxxx IS NOT LOGGED ON, MESSAGE NOT SENT.

Reason:
The /MSG command was issued using id=xxxxxxxx, but the USERID is not currently
logged on.

Action:
None.

SCM0-65

ERROR: KEYWORD MISSING OR INVALID: xxxxxxxx

Reason:
Keyword xxxxxxxx was incorrectly specified or is not permitted on the command.

Action:
Correct the command and reenter.

SCM0-77

/FETCH SERVICE UNAVAILABLE

Reason:
Could not locate the SASSCMDM module.

Action:
Ensure that the SASSCMDM module resides in a load library accessible to CA Workload
Automation SE.

SCM0-78

NO COMMAND RING ESTABLISHED

Reason:
No command ring has been built for this terminal yet. This occurs if /FETCH is entered
immediately after a /LOGON. /FETCH is not stored in the command ring.

Action:
Enter a command other than /FETCH, /LOGON, /PAGE, or /ECHO to initialize the
command ring.

Chapter 6: SANx - SJR2 Messages 1299

SCMx Through SCM9

SCM0-79

/FETCH STORAGE LIMIT EXCEEDED

Reason:
/FETCH exceeded an internal limit on the amount of storage allowed for the service. This
should not occur in normal operation.

Action:
If the problem persists, contact your installation specialist for assistance.

SCM0-86

BAD SEND OF XCF MESSAGE

Reason:
CA Workload Automation SE uses XCF messaging to perform this function, but the
message send failed for some reason.

Action:
Retry the command. If the message persists, contact your installation specialist for
assistance.

SCM0-87

*** CA 7 IS NOT USING XCF ***

Reason:
The /XCF command was issued. CA Workload Automation SE uses XCF messaging to
perform this function and cannot do so because the use of XCF is turned off.

Action:
None.

SCM0-88

*** IAS IS NOT ACTIVE OR NOT INITIALIZED

Reason:
CA Integrated Agent Services (CA IAS) is not supported or did not initialize correctly.

Action:
Check CA Workload Automation SE startup messages for CA IAS related errors.

1300 Message Reference Guide

 SCMx Through SCM9

SCM0-89

*** LOAD FAILED FOR SASSAFM2

Reason:
The request to access the common agent command module failed.

Action:
Perform the following actions:
■ Make sure SASSAFM2 is in a library accessible from CA Workload Automation SE.
■ Issue the /DISPLAY,A=SASSAFM2 command to ensure that an entry is in the
application directory for the module.

SCM0-90

*** PERSIST MUST BE YES, Y, NO, OR N

Reason:
The /AGENT PERSIST keyword is not valid. Valid values are YES, Y, NO, or N.

Action:
Correct the keyword value.

SCM0-93

*** IAS DIVR INTERNAL ERROR, RC=

Reason:
CA Integrated Agent Services (CA IAS) encountered an internal error. The return code is
listed.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1301

SCMx Through SCM9

SCM0-94

*** NO AGENT JOB ENVIRONMENT EXISTS

Reason:
The current command requires agent job support, and it is not supported in the current
CA Workload Automation SE environment.

Action:
Ensure AGENTJOB=YES is coded on the XPDEF CA Workload Automation SE initialization
statement. If not, add it, and cycle CA Workload Automation SE.

SCM1-00

LINE=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Reason:
The request to start or stop a line has been successfully completed.

Action:
None.

SCM1-00

TERM=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Reason:
The request to start or stop a specific real (physical) terminal has been successfully
completed.

Action:
None.

SCM1-00

LTERM=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Reason:
The request to start or stop a specific logical terminal has been successfully completed.

Action:
None.

1302 Message Reference Guide

 SCMx Through SCM9

SCM1-00

LINE=xxxxxxxx TERM=yyyyyyyy HAS BEEN [(STOPPED)|(STARTED)]

Reason:
The request to start or stop a line and terminals on that line has been successfully
completed.

Action:
None.

SCM1-00

PROMPTS FOR LTERM=xxxxxxxx HAVE BEEN [(STOPPED)|(STARTED)]

Reason:
Prompting for the logical terminal indicated by LTERM has been either stopped or
restarted by a /START or /STOP command with MSG=PROMPTS specified.

Action:
None.

SCM1-06

SHUTDOWN IS IN PROGRESS CANNOT START

Reason:
Shutdown of CA Workload Automation SE is in progress; the request to start a line,
terminal, or logical terminal cannot be honored.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1303

SCMx Through SCM9

SCM1-10

STOP/START INVALID, CODE=y

Reason:
If y=A, an attempt was made to stop or start a terminal that was in the middle of
processing a command. Terminal may have been processing a CA Workload Automation
SE CA WA Restart Option interface command, such as ARTS. If y=B, a /START was issued
to a VTAM terminal not connected to CA Workload Automation SE.

Action:
If y=A, let the terminal complete its activity, reissue the command. If the problem
resulted from the CA Workload Automation SE CA WA Restart Option interface, the link
of the SASSRMS1 and SASSRMS2 modules may not have been done correctly. If y=B,
issue the /OPEN command first and then issue a /START. If terminal does not connect,
bring CA Workload Automation SE down and then bring it back up with a TYPE=ERST
initialization.

SCM2-10

/SHUTDOWN MAY BE ENTERED FROM CA-7 MASTER TERMINAL ONLY.

/SHUTDOWN IGNORED.

Reason:
The CA Workload Automation SE /SHUTDOWN command can be input at the CA
Workload Automation SE Master Terminal only.

Action:
Enter command from the Master Terminal.

SCM2-11

BATCH RUN IN PROGRESS

Reason:
CA Workload Automation SE cannot be shut down while a batch terminal is in process.

Action:
Wait for the batch terminal run to complete and then reenter the /SHUTDOWN
command. The /DISPLAY,T=ALL command will provide status about the batch terminal.
When it shows "stopped," reenter the /SHUTDOWN command. Batch terminals may be
ignored by using a different shutdown option.

1304 Message Reference Guide

 SCMx Through SCM9

SCM2-12

TERMINAL xxxxxxxx IS BUSY / STOPPED /LOGOFF IGNORED

Reason:
Terminal xxxxxxxx is busy and cannot be logged off.

Action:
Wait a few seconds, and retry the logoff.

SCM2-13

TERMINAL xxxxxxxx IS ALREADY LOGGED OFF /LOGOFF IGNORED

Reason:
Terminal xxxxxxxx is already logged off.

Action:
None.

SCM2-14

TERMINAL xxxxxxxx HAS BEEN LOGGED OFF

Reason:
The request to log off terminal xxxxxxxx has been processed.

Action:
None.

SCM2-15

TERMINAL xxxxxxxx REQUIRED INTERVENTION /LOGOFF IGNORED

Reason:
Intervention is required to process previous output to terminal xxxxxxxx. The forced
logoff was ignored.

Action:
Place the device in "Ready." If the device still requires intervention, issue a
/STOP,T=xxxxxxxx to stop the terminal. If the device was made ready and is not a
printer, the /LOGOFF,T=xxxxxxxx may be reissued.

Chapter 6: SANx - SJR2 Messages 1305

SCMx Through SCM9

SCM2-16

TERMINAL xxxxxxxx IS A BATCH TERMINAL. /LOGOFF IGNORED

Reason:
Terminal xxxxxxxx is a batch terminal and cannot be forced to log off.

Action:
None.

SCM2-17

TERMINAL xxxxxxxx IS A PRINTER. /LOGOFF IGNORED

Reason:
Printer terminals cannot be forced to log off.

Action:
Place the device in "Ready." If the device still requires intervention, issue a
/STOP,T=xxxxxxxx to stop the terminal. If the device was made ready and is not a
printer, the /LOGOFF,T=xxxxxxxx may be reissued.

SCM2-18

SHUTDOWN FORMAT INVALID /SHUTDOWN IGNORED

Reason:
An invalid shutdown option was entered. A /SHUTDOWN may be done with no options
or one of the following. DMPQ, Z1, Z2, Z3, Z4, or Z5.

Action:
Correct the /SHUTDOWN command and reenter.

SCM2-19

INVALID SHUTDOWN OPTION. /SHUTDOWN IGNORED

Reason:
An invalid option was entered from the /SHUTDOWN command. The command is
ignored.

Action:
Reenter the command correctly.

1306 Message Reference Guide

 SCMx Through SCM9

SCM2-20

INVALID COMMAND - MUST BE /SHUTDOWN

Reason:
After CA Workload Automation SE is in shutdown mode, the terminal that entered the
/SHUTDOWN cannot enter most of the other commands. This message can also be
produced if the /SHUTDOWN is entered when CA Workload Automation SE is already in
the process of shutting down.

Action:
Reenter the /SHUTDOWN command or one of the other valid commands that are
allowed during shutdown. If the shutdown process is in progress, do not reenter the
/SHUTDOWN.

SCM2-25

SHUTDOWN ALREADY IN PROGRESS

Reason:
Shutdown has already been entered from another terminal.

Action:
None - CA Workload Automation SE will shut down shortly.

SCM2-30

SHUTDOWN TO BE DONE WITH THE FOLLOWING OPTIONS.

xxxxxx,xxxxxx,xxxxxx,xxxxxx
PRESS ENTER TO VERIFY

Reason:
The xxxxxx's indicate the options for the shutdown command entered. CA Workload
Automation SE is put in shutdown mode.

Action:
If these are the shutdown options that you want, press Enter and CA Workload
Automation SE is shut down. If you want different options, reenter the command. You
receive this message until Enter is pressed or two consecutive shutdown commands are
entered with the same options. If done from a JES console, the command must be
reentered.

Chapter 6: SANx - SJR2 Messages 1307

SCMx Through SCM9

SCM2-32

/SHUTDOWN INVALID FROM APPLICATION VTAM TERMINAL

/SHUTDOWN IGNORED

Reason:
A /SHUTDOWN request from an ISPF session will not be honored.

Action:
None.

SCM2-33

/SHUTDOWN INVALID FROM TRAILER TERMINAL

/SHUTDOWN IGNORED

Reason:
A /SHUTDOWN request from U7SVC or SASSTRLR will not be honored.

Action:
None.

SCM4-00

BARRIER FOR CPU=xxxxxxxx CHANGED FROM yyyy TO zzzz.

Reason:
The /ASSIGN command has executed successfully.

Action:
None.

SCM4-00

LTERM=xxxxxxxx ASSIGNED TO TERM=yyyyyyyy FROM TERM=zzzzzzzz.

Reason:
The request to change the assignment of a logical terminal from one physical terminal
zzzzzzzz to another yyyyyyyy has completed successfully.

Action:
None.

1308 Message Reference Guide

 SCMx Through SCM9

SCM4-00

MAINID=xxx ASSIGNED TO CPU yyyyyyyy FROM CPU zzzzzzzz

Reason:
The request to change the assignment of a main ID from CPU zzzzzzzz to CPU yyyyyyyy
has completed successfully.

Action:
None.

SCM4-13

LTERM=xxxxxxxx NOT ASSIGNED, DEVICE TYPE CONFLICT.

Reason:
The request to assign a logical terminal from one physical device to another cannot be
completed because the "from" and "to" devices are different types.

Action:
Reissue the /ASSIGN command specifying a "to" terminal of the same device type as the
real terminal to which the logical terminal is currently assigned.

SCM4-14

LTERM=xxxxxxxx NOT ASSIGNED, CONNECTION FIXED

Reason:
The logical terminal (LTERM) and the "from" physical terminal have the same name. This
is defined in the initialization file and is done to ensure that every physical terminal has
at least one logical terminal with which CA Workload Automation SE can communicate.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1309

SCMx Through SCM9

SCM4-15

LTERM=xxxxxxxx NOT ASSIGNED, TERM=yyyyyyyy IS CONNECTED

Reason:
The terminal to be reassigned is currently busy.

Action:
Wait a few minutes and then retry the /ASSIGN. If the situation persists and the terminal
is not in use, it may be logged off and the /ASSIGN retried.

SCM4-65

ERROR: KEYWORD MISSING OR INVALID: xxxxxx

Reason:
Keyword xxxxxx was incorrectly specified or is not permitted on the command.

Action:
Correct the command and reenter.

SCM4-95

*** AGENTDAY MUST BE 1 TO 35

Reason:
Number of retention days for /DELAGNT is not in the accepted range.

Action:
Reenter the command with a valid number.

SCM4-96

*** /DELAGNT ALREADY IN PROGRESS

Reason:
Only one /DELAGNT command can execute at a time to prevent multiple attempts to
delete the same record.

Action:
Reenter the /DELAGNT command with UPDATE=NO after a short time to let the
previous command complete. If records to be deleted are still displayed, reenter with
UPDATE=YES.

1310 Message Reference Guide

 SCMx Through SCM9

SCM4-97

*** NO RECORDS FOUND

Reason:
No agent history VSAM records are older than the AGENTDAY number of days specified
for the /DELAGNT command.

Action:
None.

SCM4-98

*** UPDATE MUST BE YES, NO, Y OR N

Reason:
Invalid value for UPDATE was entered.

Action:
Reenter command with corrected parameter value.

SCM5-00

PRTY=nn FOR APPL=xxxxxxxx AT TERM=yyyyyyyy FOR OPERID=zzzzzzzz, CHANGED TO

PRTY=mm

Reason:
The request to change application function authority for the specified operator ID,
terminal and application has been successfully completed.

Action:
The operator must log on again for the change to become effective.

SCM5-00

USERID=nnn AT TERM=xxxxxxxx FOR OPERID=yyyyyyyy CHANGED TO USERID=mmm

Reason:
The request to change a UID for the specified operator ID and the terminal has been
successfully completed.

Action:
The operator must log on again for the change to become effective.

Chapter 6: SANx - SJR2 Messages 1311

SCMx Through SCM9

SCM5-12

OPERID-xxxxxxxx NOT AUTHORIZED FOR TERM=yyyyyyyyy

Reason:
A request to change application function authorization or user ID cannot be completed
because operator ID xxxxxxxx is not authorized for terminal yyyyyyyyy.

Action:
Verify that the operator ID and terminal name were specified correctly on the input
request. If not, correct and reenter the command. If the original command was correct,
the product's initialization file must be changed to authorize the operator ID for the
terminal.

SCM5-13

APPL=xxxxxxxx NOT AVAILABLE TO OPERID=yyyyyyyyy

Reason:
A request to change application function authorization cannot be completed because
operator ID yyyyyyyyy is not authorized for application xxxxxxxx.

Action:
Verify that the operator ID and application name were specified correctly on the input
request. If not, correct and resubmit the command. If the original command was
correct, the product's initialization file must be changed to authorize the operator ID for
the application.

SCM5-14

/CHANGE NOT VALID FOR OPID WITH TRMID=**ALL**

Reason:
A /CHANGE command has been entered for an OPID that had global security defined.

Action:
If you want to change security for OPID with a global security definition, use a TERM (or
T)=**ALL** on the /CHANGE command.

1312 Message Reference Guide

 SCMx Through SCM9

SCM6-00

/DISPLAY COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input request was successfully completed.

Action:
None.

SCM7-00

/LOG COMMAND COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input request was successfully completed.

Action:
None.

SCM8-00

xxxxxxxx=yyyyyyyy SET FOR RELINK, USE COUNT=nnnn, BLDL NAME=zzzzzzzz

Reason:
The CA Workload Automation SE application or format block (specified by yyyyyyyy) has
been flagged as ready for relinking. The new version will be loaded when the use count
(nnnn) is zero (that is, the old version of the module is not in use by any program
currently executing). The new version will be loaded with the name specified by
zzzzzzzz.

Note: If a user ID was specified on the /RELINK command, that value will be used as the
first 2 characters of the BLDL name.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1313

SCMx Through SCM9

SCM8-02

INVALID TRANSACTION

Reason:
An attempt was made to do an online /RELINK of a module.

Action:
This module cannot be relinked online. CA Workload Automation SE must be shut down
and brought back up with a TYPE=WARM to bring in a new copy of the requested
module. A /RELINK cannot be done for a module marked RESD, or PERM, nor a module
that is part of the CA Workload Automation SE nucleus.

SCM8-11

xxxxxxxx=yyyyyyyy IS PERMANENTLY RESIDENT

Reason:
The CA Workload Automation SE application or format block to be relinked is either part
of the CA Workload Automation SE nucleus or is marked as permanently resident on the
APPLCTN/FMTBLK statement in the product's initialization file.

Action:
If the module is part of the CA Workload Automation SE nucleus, CA Workload
Automation SE must be relinked and CA Workload Automation SE must be shut down
and reinitialized. If marked as permanently resident in the initialization file, CA
Workload Automation SE must be restarted before the new version can be used.

SCM9-13

COMMAND INVALID FOR INTERNAL SECURITY.

Reason:
This message is issued when the /UID command is entered and external security is not
controlling CA Workload Automation SE LOGON and COMMAND security.

Action:
Verify that your current external security environment is controlling CA Workload
Automation SE logons and command security. Check the SECURITY statement, keyword
EXTERNAL=, in the CA Workload Automation SE initialization file for your current
external security options.

1314 Message Reference Guide

 SCMx Through SCM9

SCM9-14

RESOURCE NAME IS REQUIRED

Reason:
The /UID command was issued without specifying a resource name.

Action:
Correct and resubmit the command.

SCM9-15

CA-7 RESOURCE TABLE NOT FOUND

Reason:
The /UID command was issued but a UID resource table was not specified or loaded
during CA Workload Automation SE initialization. A UID resource table is required when
using the /UID command.

Action:
Ensure that a resource table name was specified in the CA Workload Automation SE
initialization file on the SECURITY statement using the UID= parameter.

SCM9-16

INVALID FORMAT FOR CA-7 RESOURCE TABLE.

Reason:
An error was encountered when reading the CA Workload Automation SE UID resource
table.

Action:
A UID resource table is required when using the /UID command. Ensure that the UID
resource table specified in the initialization file was built using the CA7RTBL macro.

Chapter 6: SANx - SJR2 Messages 1315

SCMx Through SCM9

SCM9-17

RESOURCE (xxxxxxxx) NOT FOUND IN CA-7 RESOURCE TABLE

Reason:
The resource name specified on the /UID command was not found in the UID resource
table.

Action:
Reissue the command using a valid resource name that exists in the UID resource table.

SCM9-18

ACCESS TO RESOURCE (xxxxxxxx) DENIED BY EXTERNAL SECURITY

Reason:
The user is not authorized to access the resource specified on the /UID command.

Action:
Ensure that the resource is defined to external security and determine if the user should
have access to the indicated resource.

SCM9-21

UID VALUE UPDATED

Reason:
The /UID command was processed and the user's CA Workload Automation SE UID
security level was updated for this session in CA Workload Automation SE.

Action:
None.

SCM9-32

UID RESOURCE TABLE REFRESHED

Reason:
The UID resource table has been successfully refreshed in storage using the /REFRESH
command.

Action:
None.

1316 Message Reference Guide

 SCMx Through SCM9

SCM9-33

MODULE NAME REQUIRED FOR REFRESH.

Reason:
The /REFRESH command was issued without specifying a module name on the
command.

Action:
Reissue the command and specify a UID resource table module name. For example:
/REFRESH,MOD=xxxxxxxx.

SCM9-34

MODULE xxxxxxxx NOT FOUND FOR REFRESH

Reason:
The module name specified on the /REFRESH command could not be found.

Action:
Ensure that the module exists and resides in a library accessible to CA Workload
Automation SE.

SCM9-35

NO STORAGE AVAILABLE FOR RESOURCE TABLE

Reason:
An attempt was made to refresh the in-storage UID resource table; however, the
storage for the new copy could not be obtained.

Action:
Contact your installation specialist for assistance.

SCM9-36

UNABLE TO FREE STORAGE DURING REFRESH

Reason:
An error occurred while freeing storage for the old copy of the UID resource table.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1317

SCMx Through SCM9

SCM9-37

MASTER STATION MESSAGE ROUTING INACTIVE

Reason:
/REFRESH,MOD=MSGRCNTL was issued. However, CA Workload Automation SE MSMR
is not active.

Action:
None.

SCM9-38

REBUILD ALREADY IN PROGRESS

Reason:
/REFRESH,MOD=MSGRCNTL was issued. However, CA Workload Automation SE is
already processing a request to refresh the CA Workload Automation SE MSMR Control
File.

Action:
None.

SCM9-39

UNABLE TO LOCATE SASSINEM

Reason:
/REFRESH,MOD=MSGRCNTL was issued. However, CA Workload Automation SE was
unable to locate SASSINEM, a module necessary to process the command. The request
to refresh the message selection table failed.

Action:
Ensure that SASSINEM is in the CA Workload Automation SE STEPLIB concatenation or a
linklisted library and try the command again.

1318 Message Reference Guide

 SCMx Through SCM9

SCM9-41

TABLE REBUILD REQUESTED

Reason:
/REFRESH,MOD=MSGRCNTL was issued. CA Workload Automation SE accepted the
request and scheduled a rebuild of the message selection table for CA Workload
Automation SE MSMR.

Action:
None.

SCM9-42

SERVICE DESK RULES REFRESHED WITH ERRORS

Reason:
The /REFRESH,MOD=SERVDESK command has been entered, but a problem was
detected with the SERVDESK rules.

Action:
The specific error encountered by /REFRESH,MOD=SERVDESK was issued as a WTO in
the CA Workload Automation SE address space as a CAL2Ixxxx message. Consult the
error messages and correct the problems, and then reenter the
/REFRESH,MOD=SERVDESK command.

SCM9-43

SERVICE DESK RULES SUCCESSFULLY REFRESHED

Reason:
The /REFRESH,MOD=SERVDESK command has been entered and successfully
completed.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1319

SCMx Through SCM9

SCM9-44

***UNABLE TO LOAD SASSUSD4

Reason:
The /REFRESH,MOD=SERVDESK command has been entered but could not load the
interface module.

Action:
Confirm that CA Workload Automation SE has been successfully installed. If you are
unable to resolve the problem, contact CA Support at ca.com/support for assistance.

SCM#-00

SASSMTOS FAILED, R15=xxxx (HEX) yyyy (HEX)

Reason:
When gathering metrics data for the address space, program SASSMTOS failed with
return code xxxx and reason code yyyy. This message typically relates to date conversion
or SWAREQ functions.

Action:
Consult your installation specialist for assistance.

SCM#-01

PROGRAM aaaaaaaa LOAD FAILED

Reason:
During the loading of program aaaaaaaa, the /DISPLAY,PERF= command could not
locate the program in the application list or in the metric common area. This program is
part of the CA Workload Automation SE base function.

Action:
Verify that the program is available in the STEPLIB concatenation or a linklist library.
Consult your installation specialist for assistance.

1320 Message Reference Guide

 SCMx Through SCM9

SCM#-02

SASSMTJS FAILED, RC=nnn

Reason:
When gathering metrics data from JES, program SASSMTJS failed with return code xxxx.
This message typically relates to the Subsystem Request 82.

Action:
Consult your installation specialist for assistance.

SCM#-03

SASSMTSC FAILED, R15=xxxx (HEX)

Reason:
When gathering metrics data for the CA 7 SCTs, program SASSMTSC failed with return
code xxxx.

Action:
For assistance, contact CA Support at ca.com/support.

SCM#-04

SASSMTVR FAILED, R15=xxxx (HEX)

Reason:
When gathering metrics data for VRM information, program SASSMTVR failed with
return code xxxx.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 6: SANx - SJR2 Messages 1321

SCNI Through SCN0

SCMx-05

INVALID OR OMITTED xxxxxxxx=yyyyyyyy

Reason:
Value yyyyyyyy for the keyword xxxxxxxx is invalid or is required but was not specified.
For SCM7-05, the yyyyyyyy is the first eight characters if the value is longer than eight
characters.
Note: A generic message as opposed to a specific message; SCM#-05 is the same as
others except the first aaa is PERF=aaa.

Action:
Correct and resubmit the command.

SCNI Through SCN0

SCNI-01

xx INVALID SGET RETURN CODE=nn

Reason:
An error was encountered by SASSSCNI while issuing a CA Workload Automation SE
macro. The macro statement where the error occurred is indicated by xx; nn is the
return code from the call. This message will be issued if the preprocess queue is full. If
the PREQ is full, the XPRE command can be used to list and then cancel any unneeded
input network stations.

Action:
Contact your installation specialist for assistance.

1322 Message Reference Guide

 SCNI Through SCN0

SCNI-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Reason:
An attempt to load the module indicated by xxxxxxxx has failed. The return code from
the SLOAD macro is indicated by nn; nn=04 indicates module not found; nn=12 indicates
an I/O error occurred.

Action:
Verify that the module indicated has not been inadvertently deleted from a
CA-7.LOADLIB, and that the APPLCTN statement is present (and correct) in the CA
Workload Automation SE initialization file or in the SASSPROG module. If the problem
persists, contact your installation specialist for assistance.

SCNI-11

PRE-PROCESS SCHEDULE SCAN STARTED AT hh:mm:ss ON yy.ddd.

Reason:
Scanning of preprocess schedules has started for work to be performed during the time
interval being scanned.

Action:
None.

SCNI-12

nnnn RECORDS ADDED TO THE PRE-PROCESS QUEUE.

Reason:
This is an informational message indicating the number of workstation records added to
the Preprocess queue during this scan interval.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1323

SCNI Through SCN0

SCNI-13

PRE-PROCESS SCHEDULE SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
This is an informational message indicating that the scan of preprocess schedules is
complete.

Action:
None.

SCNI-14

NETWORK (nnnn) ENTERED INTO PRE-PROCESS 'Q' FOR mm STATIONS

Reason:
This is an informational message which will appear at the CA Workload Automation SE
Master Station for each record entered into the preprocess queue. nnnn is the CA
Workload Automation SE assigned job number for the preprocess activity; mm is the
number of stations for this network.

Action:
None.

SCNI-40

SCHEDULE EXPIRED FOR NETWORK SCHD SIxxxxxx

Reason:
This message appears at the CA Workload Automation SE Master Station for each
network schedule that is found to be expired. The messages are produced each time
schedule scan runs. The xxxxxx is the schedule number (DSNBR) of the network.

Action:
The network schedule should be resolved. The network name can be found by doing an
LSCHD,DSNBR=SIxxxxxx.

1324 Message Reference Guide

 SCNI Through SCN0

SCNI-41

TOTAL NETWORK SCHD EXPIRED = xxxx

Reason:
At least one SCNI-40 message has been produced, and this reflects the number of them
that were produced for this cycle of schedule scan. Only the first five expired schedules
will be shown with the SCNI-40 messages.

Action:
If xxxx is greater than five, do an LSCHD,DSNBR=SI*,ST=EXP to determine which
schedules need to be resolved.

SCNJ-01

xx INVALID SGET RETURN CODE=nn. JOB = yyyyyyyy SCHID = zzzz

Reason:
The major reason for this error is a problem was encountered in trying to get a member
from the database.
■ xx is the macro statement where the error occurred.
■ nn is the return code from the call.
■ yyyyyyyy is the job that was being processed by Schedule Scan.
■ zzzz is schedule ID.

If xx=22 and nn=04, the HIJBNUM parameter on the SCHEDULE statement may have
been reached.

Action:
Perform the following actions:
■ If xx=22 and nn=04, see SPO7-02 for more details.
■ If xx=48, a bad job member in the CA Workload Automation SE Job data set was
detected. The indicated job may have to be deleted and readded. It must be
reloaded before the job can be run by CA Workload Automation SE. Also, job prose,
schedules, and JOBCONN connections may have to be reentered.
■ If xx=85, the Trailer queue may be full.

Chapter 6: SANx - SJR2 Messages 1325

SCNI Through SCN0

SCNJ-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Reason:
An attempt to load module xxxxxxxx has failed. The return code from the SLOAD macro
is indicated by nn; nn=4 indicates module not found; nn=12 indicates an I/O error.

Action:
Verify that the module has not been inadvertently deleted from CA-7.LOADLIB and that
the APPLCTN statement is present (and correct) in the product's initialization file or in
the module SASSPROG. If the problem persists, contact your installation specialist.

SCNJ-11

JOB SCHEDULE SCAN STARTED AT hh:mm ON yy.ddd.

Reason:
This is an informational message indicating that a scan of jobs has been started.

Action:
None.

SCNJ-12

nnnn JOBS ADDED TO REQUEST QUEUE.

Reason:
This is an informational message indicating the number of job records (nnnn) which
were added to the request queue during this scan.

Action:
None.

SCNJ-13

JOB SCHEDULE SCAN COMPLETED AT hh:mm ON yy.ddd.

Reason:
Self-explanatory.

Action:
None.

1326 Message Reference Guide

 SCNI Through SCN0

SCNJ-14

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',

DUE-OUT ON yy.ddd AT hh:mm.

or

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',

*** JCL RETRIEVED FROM SPECIAL OVERRIDE LIBRARY ***
DUE-OUT ON yy.ddd AT hh:mm

Reason:
This is an informational message which will appear on the CA Workload Automation SE
Master Station for each job added to the request queue by schedule scan. The job name
is indicated by xxxxxxxx and the CA 7 WA job number is indicated by nnnn. If the JCL has
been retrieved from the special JCL Override library (JCLID 254), this will be indicated.
The due-out date and time specifies when CPU processing must be completed.

Action:
None.

SCNJ-15

JOB xxxxxxxx NOT ENTERED INTO REQUEST 'Q'

***JOB LOCKED*** DUE-OUT ON yy.ddd AT hh:mm

Reason:
According to the job schedule member, the job's processing cycle has arrived and it
should be added to the request queue. However, the job is in locked status and
therefore cannot be scheduled. The due-out time specifies when the job must be
completed.

Action:
The LLOCK command should be used to determine why the job is in a locked status. If
you want scheduling, the reasons for the lock must be corrected. Schedule Resolution
must be rerun if the schedule definition is altered. The job may have to be manually
demanded into the queue for the current cycle, depending on the reason it is locked.

Chapter 6: SANx - SJR2 Messages 1327

SCNI Through SCN0

SCNJ-16

JOB xxxxxxxx NOT ENTERED INTO REQUEST 'Q'

***NXTCYC=SKP*** DUE-OUT ON yy.ddd AT hh:mm:ss

Reason:
Job xxxxxxxx is scheduled to start during the time span just searched by Schedule Scan.
It was not entered into the request queue, however, because the next cycle flag
indicates skip one cycle.

Action:
None. The next cycle indicator will be reset automatically and the job will be scheduled
when its next processing cycle occurs.

SCNJ-17

JOB xxxxxxxx NOT ENTERED INTO REQUEST 'Q'

***NXTCYC=OFF*** DUE-OUT ON yy.ddd AT hh:mm:ss

Reason:
Job xxxxxxxx is scheduled to start during the time span just searched by Schedule Scan.
It was not entered into the request queue, however, because the next cycle flag
indicates normal scheduling is to be bypassed indefinitely.

Action:
None. The next cycle indicator must be manually reset before normal scheduling will be
resumed.

SCNJ-18

JOB xxxxxxxx NOT ENTERED INTO REQUEST 'Q'

***JCL (kkkk)*** DUE-OUT ON yy.ddd AT hh:mm:ss

Reason:
The job was not entered into the request queue because the JCL could not be attached.
kkkk indicates the reason, as follows:
0004
Empty member.
0008
Member not found on CA Workload Automation SE CA Librarian or CA Panvalet for
z/OS libraries; or JCL INDEX not specified. Also, if a CA Workload Automation SE CA
Librarian or CA Panvalet for z/OS data set, it has been unavailable for two minutes.
Also, a ++INCLUDE may be referring to an invalid name.

1328 Message Reference Guide

 SCNI Through SCN0

000C
JCL data set not found on DASD volume.
0010
JCL data set is not a PDS - invalid DSORG.
0014
JCL data set has invalid DCB attributes.
0018
JCL data set resides on a DASD volume not accessible to CA Workload Automation
SE.
001C
JCL member not found in data set.
0020
READ I/O error was encountered.
0024
JCL data set is READ password protected.
0028
JCL data set is USERID protected or CA Workload Automation SE does not have
access to the JCL data set when external security is used for data sets.
0054
Data set is busy.
005C
Dynamic allocation for JCL data set failed.
0060
Error occurred during OPEN. The DCBABCOD field is nonzero.

Chapter 6: SANx - SJR2 Messages 1329

SCNI Through SCN0

007C
JCLID is not in the product's initialization file.
0080
Problem with interface to CA Librarian or CA Panvalet for z/OS.
0084
EOF reached in SQADD. The job may have too many lines of JCL for CA Workload
Automation SE to put in the Trailer queue (31 track maximum).
0088
Error on TRLQ.
008C
Error loading module SASSPCEJ. Return code from SLOAD macro is in the first two
characters.
0090
Bad SLINK to SASSPCEJ. See also 0490 and 0890.
0094
SASSXX05 determined job should be canceled.
0098
Error in SASSXX05 - invalid return code.
009C
Invalid data on # statement.
00A0
JCL attach rejected by user exit SASSXX11 with a return code of 4. Job will be
flagged for retry if the RETRY interval option is specified on the SCHEDULE
statement in the initialization file. If the RETRY option is not specified, the job will
be left in SKELETON status.
00A4
JCL attach rejected by user exit SASSXX11 with a return code other than 4. Job will
be left in SKELETON status.
0490
Error return from SASSPCEJ indicating invalid conversion request.
0588
Out of space in TRLQ.
0890
Error return from SASSPCEJ indicating invalid conversion request.

1330 Message Reference Guide

 SCNI Through SCN0

Action:
Determine the reason for the problem and correct it, if possible. If the job must run this
cycle, it must be demanded unless the job's status is RETRY on an LQ display. The
following list shows corrective action for the messages keyed to the codes shown in the
previous list.
0008
Try LLIB command for a more detailed error message and try JCL panel (DB.7 - fill in
the panel for a more detailed error message).
000C
Verify that the data set in on the volume requested. Specify the correct volume if in
error.
0010
Data set organization must be PS or PO. If PDS, the member name must be
provided.
0014
Either BLKSIZE=0 or KEYLEN=0 or RECFM not = F or LRECL not = 80.
0018
No //U7volser DD statement exists for the volume where the data set resides.
Supply a //U7volser DD statement in the CA Workload Automation SE execution
JCL. The ALLOC command may be issued to make the volume available.
001C
Provide a valid member name.
0020
Try again. If the problem persists, contact your installation specialist for assistance.
0024
This update would require a WTOR reply from the system operator's console which
would put CA Workload Automation SE in a hard wait; that is, no terminal
processing, job scheduling, job submittal, and so forth, until the operator
responded. Updates to such a data set are not allowed from CA Workload
Automation SE. The update must be made from outside of CA Workload
Automation SE by using TSO, batch, and so forth, so as not to impede production
scheduling.
0028
1) This request has violated User Security as defined in the module referenced by
the USER keyword of the SECURITY statement in the CA Workload Automation SE
initialization file. Use a different operator ID at logon time or change the USER ID
Security module.
2) CA Workload Automation SE does not have access to the JCL data set.

Chapter 6: SANx - SJR2 Messages 1331

SCNI Through SCN0

0054
Wait and try again. If the problem persists, contact your installation specialist for
assistance.
005C
Try to edit the JCL using the DB.7 panel. Error messages should be returned with
codes indicating the specific problem.
0060
Check the MVS console log for errors at the time the job came into the request
queue.
0080
Use the LJOB command to check the JCLID defined for the job then use
/DISPLAY,ST=JCL to verify the IDs defined to CA Workload Automation SE. Correct
the job definition or add the JCL definition to the initialization file and restart CA
Workload Automation SE using WARM.
0084
Try to demand the job identified by using DEMANDH so that it will be in HOLD
status and can be canceled if necessary. You may want to specify the SCHID and
DOTM values if the job needs to run. If the error repeats, the DEMAND command
will produce messages to explain the error.
0088
Take the same action as in code 0084 above.
008C
Verify that module SASSPCEJ is in a library pointed to by STEPLIB. Take the same
action as in code 0084.
0090
Take same action as in code 008C above.
0094
If you want the job, use DEMAND command. You may want to check with your
installation specialist as to why the exit (SASSXX05) canceled the job.
0098
Take same action as in code 0094 above.

1332 Message Reference Guide

 SCNI Through SCN0

009C
Use QM.5 panel to examine and correct any errors on Special Override (#)
statements in the JCL.
00A0
Probably none. If the JCL retry option is specified, JCL attach will be attempted at
the next retry interval. This will continue until the exit accepts the JCL attach or the
job is canceled. If the job must be scheduled, check with your installation specialist
concerning the SASSXX11 exit and why it is preventing JCL for this job to be
attached.
00A4
Because the job is left in SKELETON status, it must be canceled to remove it from
the request queue. If it must be scheduled, try using the DEMAND command. If the
reason for JCL attach rejection is not clear, you should check with your installation
specialist concerning the SASSXX11 exit.
0490
Take same action as in code 0090 above.
0588
If the error occurred while attaching the JCL, issue a /DISPLAY,Q=TRL and check the
space availability. If the number of tracks is low, increase the size of the Trailer
queue, at a convenient time, using the DMPQ/MOVQ shutdown and startup facility.
0890
Take same action as in code 0090 above.

SCNJ-19

JOB xxxxxxxx NOT ENTERED IN REQUEST 'Q', *** JCL (kkkk) *** JCL RETRIEVED FROM
SPECIAL OVERRIDE LIBRARY *** DUE-OUT ON yy.ddd AT hhmm

Reason:
See SCNJ-18. An attempt was made to retrieve the JCL for the job from the special JCL
Override library of ID 254.

Action:
Determine the reason for the problem and correct it, if possible. Replace the JCL
member in the special library. (This is required to indicate to the Job data set that next
time JCL is to be retrieved from this special library.) If job must be run this cycle, it must
be demanded.

Chapter 6: SANx - SJR2 Messages 1333

SCNI Through SCN0

SCNJ-40

SCHEDULE EXPIRED FOR JOB xxxxxxxx

Reason:
This message appears at the CA Workload Automation SE Master station for each job
schedule that is found to be expired. The messages are produced each time schedule
scan runs. The xxxxxxxx is the job name.

Action:
The job schedule needs to be resolved.

SCNJ-41

TOTAL JOB SCHD EXPIRED = xxxx

Reason:
At least one SCNJ-40 message has been produced, and this reflects the number of them
that were produced for this cycle of schedule scan. Only the first five expired schedules
will be shown with the SCNJ-40 messages.

Action:
If xxxx is greater than five, do an LSCHD,DSNBR=SJ*,ST=EXP to determine which
schedules need to be resolved.

SCNJ-42

JOB xxxxxxxx SKIPPED BY SSCAN--DRCLASS xxxxxxxx NOT ACTIVE

Reason:
Schedule scan is running while disaster recovery mode is active. The specified job is not
being added to the request queue because its disaster recovery class is not active.

Action:
None.

1334 Message Reference Guide

 SCNI Through SCN0

SCNJ-43

CA-7 IS RUNNING IN DISASTER RECOVERY MODE

Reason:
Schedule scan is running while disaster recovery mode is active. This message, along
with SCNJ-44 and SCNJ-45, are written to the browse log.

Action:
None.

SCNJ-44

DISASTER RECOVERY CLASS xxxxxxxx IS ACTIVE

Reason:
Schedule scan is running while disaster recovery mode is active. This message, along
with SCNJ-43 and SCNJ-45, are written to the browse log. This message is issued once
for every active disaster recovery class.

Action:
None.

SCNJ-45

END OF ACTIVE DISASTER RECOVERY CLASS LIST

Reason:
Schedule scan is running while disaster recovery mode is active. This message is written
to the browse log after all of the active disaster recovery classes have been displayed.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1335

SCNI Through SCN0

SCNJ-80

JOB xxxxxxxx FAILURE GETTING yyyyyyyy INFO SASSJOBR RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyy (agent information for agent
jobs or node/executable information for cross-platform job xxxxxxxx. As a result,
cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCNJ-81

JOB xxxxxxxx FAILURE GETTING yyyyyyyy INFO SASJE RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyy (agent information for agent
jobs or node/executable information for cross-platform job xxxxxxxx. As a result,
cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCNJ-82

JOB xxxxxxxx FAILURE ADDING yyyyyyyy SEGMENT EOF REACHED

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxx could not be added to the queue
because it is full.

Action:
Perform one the following actions:
■ Enlarge the queue if the queue if full.
■ Post existing jobs before processing additional requests.

Contact your installation specialist for assistance.

1336 Message Reference Guide

 SCNI Through SCN0

SCNJ-83

JOB xxxxxxxx FAILURE ADDING yyyyyyyy SEGMENT SQADD RC=xx

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxx could not be added to the queue.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCNJ-84

JOB xxxxxxxx is an yyyyy JOB- NO yyyyy ENVIRONMENT EXISTS

Reason:
CA Workload Automation SE has been started with the cross-platform job feature
disabled where yyyyy denotes the cross-platform job type (agent or XPJOB).

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Enable the cross-platform job feature. Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1337

SCNI Through SCN0

SCNP-11

JOB xxxxxxxx (nnnn) SYS=xxxxxxxx *** IS LATE ***

REQUIRED BY yy.ddd AT hhmm, MUST START BY yy.ddd AT hhmm
SCHID=xxx PROSE#=nnnnnnnn ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn
MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that a job is behind schedule. The fields in the message are as follows:
■ ERQD is a count of total external requirements.
■ ENSAT is a count of external requirements not satisfied.
■ IRQD is a count of total internal requirements.
■ INSAT is a count of internal requirements not satisfied.
■ MCNT is a master count of unsatisfied requirements.
■ FLAGS are hexadecimal values matching the following fields from the JQREC macro
DSECT. The fields are listed in order of appearance in the message.
– JQFLG1
– JQFLG2
– JQJFLG1
– JQJFLG2
– JQJFLG3
– JQJFLG4
– JQJFLG5

Action:
Determine why the job is late and take appropriate steps to correct the situation. This
message will continue to appear at every reprompt interval. To suspend the message,
use the RSVP command.

1338 Message Reference Guide

 SCNI Through SCN0

SCNP-11

xxxxxxxx STATION WORK (nnn,mmmm) REF=jjjjrrs ***IS LATE***

FOR NETWORK=xxxxxxxx [,SUBID=yyyyyyyy][,JOB=zzzzzzzz]
REQUIRED BY yy.ddd AT hhmm,
MUST START BY yy.ddd AT hhmm
PROSE #nnnnnnnn

Reason:
This message is issued to a station's terminal to indicate work is behind schedule.

Action:
Determine why the task is late and take appropriate action. This message will continue
to appear at every reprompt interval until action is taken. Use the RSVP command to
suspend the prompt.

SCNP-12

PROMPT | REMIND COMPLETE AT hh:mm:ss ON yy.ddd.

Reason:
Indicates end of a prompt or reprompt interval.

Action:
None.

SCNP-15

SASSAILE MESSAGE : text

Reason:
An ARF condition was detected for a job, but an error occurred. This message indicates
that module SASSAILE returned with an error. text provides supplementary information
about the error.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 6: SANx - SJR2 Messages 1339

SCNI Through SCN0

SCNP-50

RETRY COMPLETE. xx JOBS RETRIED, yy JOBS ATTACHED.

Reason:
The RETRY cycle for JCL attach has completed. xx indicates the number of jobs that were
in the request queue with R-RETRY status. yy indicates the number of jobs for which
RETRY was able to attach JCL. The RETRY cycle may occur on a time basis or if manually
specified with the SSCAN,SCAN=RET command.

Action:
None.

SCNP-51

JOB xxxxxxxx (nnnn) FAILED IN RETRY. CODE = zzzzzzzz

Reason:
When a retry attempt was done for job xxxxxxxx, a failure occurred other than dynamic
allocation.

Action:
The job is left in SKELETON status and needs to be canceled and, if needed, demanded
back in. See message SCNJ-18 to help in resolving the zzzzzzzz code.

SCNP-52

XP RETRY COMPLETE nn JOBS RETRIED.

Action:
The XPJOB Retry cycle is complete for XPJOBs in a N-xxxx status, which represents nodes
OFFLine, STOP, or FAIL. The number of jobs resubmitted is represented by nn.

Reason:
None.

1340 Message Reference Guide

 SCNI Through SCN0

SCN0-11

SCHEDULE SCAN STARTED AT hh:mm:ss ON yy.ddd.[(FORCED)]

***SCAN PERIOD OF yy.ddd AT hh.mm THRU yy.ddd AT hh:mm***

Reason:
This is an informational message indicating that Schedule Scan has been initiated and is
scanning for jobs and preprocess work whose schedules fall within the designated
period of the scan. All work found during the time period being scanned will be placed
in the preprocess or request queues as appropriate. If Schedule Scan is forced using the
SSCAN,SCAN=SCH command, the (FORCED) parameter is included in the message.

Action:
None.

SCN0-12

NEXT SCHEDULE SCAN WAKE-UP TIME IS yy.ddd AT hhmm.

***** x...x *****

Reason:
This is an informational message notifying the user when Schedule Scan will next begin
(wake-up) to perform a time-dependent function. The function to be performed is
indicated by x...x. Current values for x...x are:
■ FOR A POST 'Q' PROMPT
■ FOR A REQ 'Q' PROMPT
■ FOR A SKELETON RETRY CYCLE
■ FOR XPJOB RETRY CYCLE
■ TO RE-PROMPT USER
■ TO SCAN NEXT INTERVAL
■ TO NEXT SCAN INTERVAL

Note: Due to dynamic activities within CA Workload Automation SE, Schedule Scan may
be activated sooner than the specified next wake up for a reason other than the
function indicated in this message.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1341

SCNI Through SCN0

SCN0-13

SCHEDULE SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
Self-explanatory.

Action:
None.

SCN0-14

*** ATTENTION: SCHEDULE SCAN ERROR ***

Reason:
The message indicates that errors have occurred causing Schedule Scan to end before all
jobs have been brought in.

Action:
Check error messages (possibly on the Browse data set) for error that occurred during
the Schedule Scan. When these errors are corrected, the next Schedule Scan will bring in
any jobs that were not brought in previously. Enter SSCAN,SCAN=SCH to force Schedule
Scan to run immediately rather than awaiting its next cycle.

SCN0-15

SCHEDULE SCAN NOT DONE: REASON -- DATE=0

Reason:
The message indicates that this cycle of schedule scan was not done because the scan
period start date was zero.

Action:
Use the SSCAN command to make the scan period start date a valid date.

1342 Message Reference Guide

 SCO0 Through SCRJ

SCO0 Through SCRJ

SCO0-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Successful completion of input request.

Action:
None.

SCO0-01

INVALID INPUT REQUEST

Reason:
Function code not DMP or ZAP.

Action:
Correct and resubmit command.

SCO0-02

INVALID INPUT REQUEST

Reason:
The DMP command should specify one of the following:
■ SVT
■ MOD
■ ADR
■ JOB
■ DSN
■ DSNBR

TYPE should be DIR or MBR when dump request is JOB, DSN, or DSNBR.

Action:
Retry and specify one of the keywords noted. Check all keywords for proper spelling or
address.

Chapter 6: SANx - SJR2 Messages 1343

SCO0 Through SCRJ

SCO0-03

INVALID INPUT REQUEST

Reason:
Error in OFFSET field.

Action:
Correct OFFSET value and resubmit command.

SCO0-04

INVALID INPUT REQUEST

Reason:
Error in LENG field.

Action:
Correct LENG value and resubmit command.

SCO0-05

INVALID INPUT REQUEST

Reason:
Module name in MOD=SASSxxxx does not begin with SASS.

Action:
Correct MOD parameter and resubmit command.

SCO0-06

INVALID INPUT REQUEST

Reason:
Module name in MOD=SASSxxxx cannot be found, has not been loaded, or is not
resident.

Action:
If MOD was specified incorrectly, correct and resubmit command.

1344 Message Reference Guide

 SCO0 Through SCRJ

SCO0-07

INVALID INPUT REQUEST

Reason:
Error on job request; job is probably not on database.

Action:
Check job name given; if incorrect, supply correct job name and resubmit command.

SCO0-08

INVALID INPUT REQUEST

Reason:
Error on DSN request; data set probably was not found.

Action:
Check data set name; if incorrect, supply correct data set name and resubmit command.

SCO0-10

INVALID INPUT REQUEST

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

SCO0-11

INVALID INPUT REQUEST

Reason:
VSAM control block was requested and was either not found or had an error.

Action:
Check console log for CA-7.Vxxxx messages and if found refer to that message for
explanation.

Chapter 6: SANx - SJR2 Messages 1345

SCO0 Through SCRJ

SCRJ-11

JOB xxxxxxxx (nnnn) FORCED COMPLETE. *** COMPLETED ***.

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
when a job has been forced complete with either the XRST panel or the top line
RESTART command.

Action:
None.

SCRJ-12

JOB xxxxxxxx (nnnn) COMPLETED NORMALLY. ***COMPLETED***.

HIGHEST CONDITION CODE=nnnn.

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
successful completion of the specified job.

Action:
None.

SCRJ-13

JOB xxxxxxxx (nnn) HAS JCL ERROR ***RESTART REQUIRED***

Reason:
Generally this message will not be issued for jobs that have been submitted and fail with
a JCLERR. For these jobs, the SMF0-18 message will be issued, and the possible SCRJ-13
messages will be suppressed. However, for a job that is demanded with TYPE=RES, the
SCRJ-13 message can be issued periodically until restart is begun. The NOPRMP
command may be used to suspend the message. The RSVP command may be used to
suspend the message.

Action:
See message SMF0-18. Analyze the JCL to determine the problem and then restart the
job.

1346 Message Reference Guide

 SCO0 Through SCRJ

SCRJ-14

JOB xxxxxxxx(nnnn) ABNORMALLY TERMINATED ***RESTART REQUIRED*** FAILING

CODE= [(S)|(U)] cccc. LAST STEP EXECUTED= yyyyyyyy.

Reason:
See message SMF0-19. This message will reappear periodically until restart is begun.
The RSVP command may be used to suspend the message.

Action:
See message SMF0-19. The abend must be analyzed to determine what corrective
action is necessary. Job Restart must be used to resubmit the job. This message will
reappear periodically until restart is begun. The RSVP command may be used to suspend
the message.

SCRJ-29

XPS JOB jjjjjjjj (nnnn) COMPLETED. (xxxxxxxx)

Reason:
A cross-platform job has completed. This job was scheduled with the XPSSCHD=RUNREF
option. One of the following status indicators will be provided at xxxxxxxx.
NORMAL
Indicates the XPS job completed normally.
FCOMP
Indicates the completion of the XPS job was forced.
CCFAIL
Indicates the XPS job did not complete successfully because of a condition code
exception.
JCLERR
Indicates a JCL error was detected for the XPS job.
ABEND
Indicates the XPS job abended.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1347

SCO0 Through SCRJ

SCRJ-30

ARFJOB jjjjjjjj (nnnn) FOR yyyy COMPLETED. (xxxxxxxx)

Reason:
An ARF recovery job has completed. This job was scheduled by ARF to run on behalf of
an ARF monitored job for which an abnormal completion was detected. The CA
Workload Automation SE number of the job that ARF monitored is yyyy. One of the
following status indicators will be provided:
NORMAL
Indicates the ARF recovery job completed normally.
FCOMP
Indicates the completion of the ARF recovery job was forced.
CCFAIL
Indicates the ARF recovery job did not complete successfully because of a condition
code exception.
JCLERR
Indicates a JCL error was described for the ARF recovery job.
ABEND
Indicates the ARF recovery job abended.

Action:
None.

SCRJ-48

JOB xxxxxxxx (nnnn) COND CODE CHECK FAILED ***RESTART REQUIRED***

FAILING CODE=cccc. LAST STEP EXECUTED=yyyyyyyy.

Reason:
See message SMF0-20. The specified job generated a condition code in one of its steps,
and the code failed the test defined in the CA Workload Automation SE database. This
message will reappear periodically until restart is begun. The NOPRMP command may
be used to suspend the message.

Action:
See message SMF0-20. The situation must be analyzed to determine the corrective
action. Job Restart must be used to resubmit the job.

1348 Message Reference Guide

 SCO0 Through SCRJ

SCRJ-55

JOB/DSN TABLE FULL (nnnnnnnn)

Reason:
An internal CA Workload Automation SE table has filled up. This is an informational
message.

Action:
None.

SCRJ-60

JOB xxxxxxxx(nnnn) TO LOAD NEW WORK-LOAD BAL PARAMETER DEFN FAILED:

LOAD MODULE DOES NOT EXIST, OLD DEFN RETAINED

Reason:
The specified job does not have a corresponding Workload Balancing parameter
definition in the CA Workload Automation SE load library.

Action:
Create an appropriate load module.

SCRJ-72

JOB xxxxxxxx (nnnn) *NOT* REPEATED--COUNT IS ZERO

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that the job is no longer being repeated because it has already been repeated the
maximum number of times.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1349

SCO0 Through SCRJ

SCRJ-80

JOB xxxxxxxx (jobno) FAILURE GETTING yyyyyyyy INFO SASSJOBR RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyyy (agent information for
agent jobs or node/executable information for XPJOBs) for cross-platform job xxxxxxxx.
As a result, cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCRJ-81

JOB xxxxxxxx (jobno) FAILURE GETTING yyyyyyyy INFO SASJE RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyyy (agent information for
agent jobs or node/executable information for XPJOBs) for cross-platform job xxxxxxxx.
As a result, cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCRJ-82

JOB xxxxxxxx (jobno) FAILURE ADDING yyyyyyyy SEGMENT EOF REACHED

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxx could not be added to the queue
because it is full.

Action:
Perform one the following actions:
■ Enlarge the queue if the queue if full.
■ Post existing jobs before processing additional requests.

Contact your installation specialist for assistance.

1350 Message Reference Guide

 SDxx

SCRJ-83

JOB xxxxxxxx (jobno) FAILURE ADDING yyyyyyyy SEGMENT SQADD RC=xx

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxxx could not be added to the
queue.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SCRJ-84

JOB xxxxxxxx (jobno) is an yyyyy JOB- NO yyyyy ENVIRONMENT EXISTS

Reason:
xxxxxxxx is the job name. CA Workload Automation SE has been started with the
cross-platform job feature disabled where yyyyyyyyy denotes the cross-platform job
type (Agent or XPJOB).

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Enable the cross-platform job feature. Contact your installation specialist for assistance.

SDxx
SDAV-01

xxx INVALID MACRO RETURN CODE = nnn...n

Reason:
The SASSSDAV module has detected an error on return from a macro. The
Where-In-Program (WIP) value is specified by xxx. The register 15 value (in hex) is given
by nnn...n.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1351

SDxx

SDMx-00

SPECIFY DESIRED OPTION OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used for online selection of a major category. If an error is made in
the selection, you are again requested to select a function.

Note: The following are the actual message ID prefixes:

■ SDBE
■ SDBH
■ SDBL
■ SDBM
■ SDMA
■ SDMB
■ SDMF
■ SDMI
■ SDMJ
■ SDMN
■ SDMO
■ SDM0

Action:
Self-explanatory.

1352 Message Reference Guide

 SDxx

SDMx-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
You must have certain privileges to use the CA Workload Automation SE DB.10 function.

Note: The following are the actual message ID prefixes:

■ SDBE
■ SDBH
■ SDBL
■ SDBM
■ SDMA
■ SDMB
■ SDMF
■ SDMI
■ SDMJ
■ SDMN
■ SDMO
■ SDM0

Action:
Contact your installation specialist for assistance if you need access to the XPSWD
function.

SDMx-11

NO AGENT ENVIRONMENT EXISTS, x DISABLED

Reason:
The user is trying to use the agent job command, and the agent environment has not
been initialized. x is the menu selection attempted or AGPSWD.

Note: The actual message prefix IDs are SDMA and SDM0.

Action:
Enable the cross-platform job feature. Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1353

SDxx

SDM0-00

ENTER CA-7 TRANSACTION

Reason:
This is the reply to a DBM statement in batch. DBM is used in batch to exit Database
Maintenance mode.

Action:
Enter any command (Database Maintenance, inquiry, and so forth) in the next
statement.

SDM0-10

NO XPJOB ENVIRONMENT EXISTS, xxxxxxx DISABLED

Reason:
The user is trying to use one of the following commands, and the XPJOB environment
has not been initialized:
■ CONVERT
■ RESTORE
■ XNODE
■ XPJOB
■ XPSWD

Action:
Enable the cross-platform job feature. Contact your installation specialist for assistance.

SDM0-12

FUNCTION IGNORED FOR NON-3270 TERMINALS

Reason:
The function entered is not available in batch mode.

Action:
Reissue this function from a 3270-type terminal.

1354 Message Reference Guide

 SFCx

SFCx
This subsection contains the CA Workload Automation SE messages beginning with SFC.
These messages relate to the forecast function.

SFCW-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Input request has been successfully completed.

Action:
None.

SFCW-01

I/O ERR DURING READ OF PROSE MEMBER FOR JOB xxxxxxxx RC=nn WIP=ww
MODULE=SFCW.

Reason:
Error occurred accessing prose for indicated job.

Action:
Use LPROS to verify that prose data exists for the job. If the prose exists, it may need to
be deleted and readded. Then retry the command that failed.

SFCW-02

I/O ERROR DURING READ OF REQUIREMENT ENTRY FOR JOB xxxxxxxx RC=nn WIP=ww
MODULE=SFCW

Reason:
Error occurred while reading requirement type records for job xxxxxxxx.

Action:
Try LJOB,LIST=RQMT for job xxxxxxxx. If LJOB produces an error, try to delete and add
the problem requirement entry. Job may have to be deleted and then added.

Chapter 6: SANx - SJR2 Messages 1355

SFCx

SFCW-03

SCRATCH FILE READ ERROR RC=nn WIP=ww MODULE=SFCW

Reason:
Error occurred processing temporary data file in scratch queue.

Action:
Contact your installation specialist for assistance.

SFCY-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Input request has been successfully completed.

Action:
None.

SFCY-02

I/O ERROR DURING READ OF SCRATCH-FILE-1, RC=nn, WIP=ww, MODULE=SFCY

Reason:
An I/O error occurred during the read operation of the Scratch file ID 1. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module SFCY where the I/O error occurred.

Action:
Contact your installation specialist for assistance.

1356 Message Reference Guide

 SFCx

SFCY-03

I/O ERROR DURING READ OF JOB DIRECTORY FOR JOB yyyyyyyy, RC=nn, WIP=ww,
MODULE=SFCY

Reason:
An I/O error occurred during the read operation of the Job data set. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module SFCY where the I/O error occurred.

Action:
If the problem persists, contact your installation specialist for assistance.

SFCY-04

I/O ERROR DURING READ OF JOB MEMBER FOR JOB yyyyyyyy, RC=nn, WIP=ww,
MODULE=SFCY

Reason:
An I/O error occurred during the read operation of the Job data set. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module SFCY where the I/O error occurred.

Action:
If the problem persists, contact your installation specialist for assistance.

SFCY-05

I/O ERROR DURING READ OF HEADER RECORDS FOR JOB yyyyyyyy, RC=nn, WIP=ww,
MODULE=SFCY

Reason:
An error has occurred while reading data from the CA Workload Automation SE queues.
Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module SFCY where the I/O error occurred.

Action:
If the problem persists, contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1357

SFCx

SFCY-06

PROCESSING TERMINATED BY SYSTEM ERROR.

RC=nn, WIP=ww, MODULE=SM5C

Reason:
Error occurred attempting to write the WLP data as requested. See message SM50-14
for explanation of return code represented by nn. These return codes are given in
decimal representation and must be converted to hexadecimal when referring to the
explanation under message SM50-14.

Action:
Correct the indicated error and retry. See message SM50-14 for corrective action based
on return code values. If the error persists, contact your installation specialist for
assistance.

SFCY-08

ERROR READING QUEUE REQUIREMENT SECTION FOR JOB=yyyyyyyy, RC=xx, WIP=ww,

MODULE=SFCY

Reason:
An error has occurred while reading data from the CA Workload Automation SE queues.
Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module SFCY where the I/O error occurred.

Action:
If the problem persists, contact your installation specialist for assistance.

SFCY-09

NOT ENOUGH SPACE AVAILABLE IN OUTPUT FILE

FILE CREATED BUT IS INCOMPLETE,
LAST JOB WRITTEN - yyyyyyyy DUE-OUT DATE yyddd/hhmm

Reason:
The data set specified by DDNAME has insufficient space available to contain all of the
WLP JOB and RES card information generated by the request.

Action:
Because the data produced is not in a predictable order, no assumptions can be made
about the contents of the file. Reallocate the file with a larger space allocation and retry
the command.

1358 Message Reference Guide

 SFCx

SFC0-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Input request has been successfully completed.

Action:
None.

SFC0-02

'xxxxxx' IS AN INVALID FUNCTION

Reason:
xxxxxx is an invalid function specified on the input command.

Action:
Correct and resubmit.

SFC0-03

LOAD ERROR FOR 'xxxxxxxx', RC=nn

Reason:
xxxxxxxx is the module to be loaded; nn is the return code from the SLOAD macro.

Action:
Verify the following:
■ Module xxxxxxxx exists in the CA Workload Automation SE load library; and
■ An APPLCTN statement exists for xxxxxxxx in SASSPROG or in the initialization file.

SFC0-04

INVALID INPUT.

Reason:
Input data has unrecognizable keywords, formats, or both for one or more parameters.
This can result when a value is too big or too many entries are input.

Action:
Resubmit the command with correct parameters and data.

Chapter 6: SANx - SJR2 Messages 1359

SFCx

SFC0-08

GENERIC JOBNAME NOT ALLOWED WITH FRJOB OR FRQJOB.

Reason:
Reverse job flow does not support generic job names.

Action:
Respecify the command with one or more specific job names.

SFC0-09

MAX LEVEL HIT. SOME JOBS NOT LISTED.

Reason:
While processing a forecast command, CA Workload Automation SE found that the
maximum level had been reached and has terminated the command.

Action:
Check the output of the command to see if a triggering loop may be defined in the
database. By default the maximum number of levels is 99. To change this, use the LVL
keyword on the command or the FCMAXLEV keyword on the OPTIONS statement in the
initialization file.

SFC0-10

INVALID OR OMITTED 'xxxxxxxx' DATA

Reason:
xxxxxxxx is the parameter that is invalid or has been omitted.

Action:
Resubmit the command with correct parameter and data.

SFC0-11

'xxxxxxxx' DATA NOT REQUIRED. ERROR.

Reason:
xxxxxxxx is the parameter that has been provided but is not required.

Action:
Resubmit the command with correct parameter and data.

1360 Message Reference Guide

 SFCx

SFC0-12

REQUIRED INPUT 'xxxxxxxx' MISSING. ERROR.

Reason:
xxxxxxxx is the parameter that is required but not provided.

Action:
Resubmit the command with correct parameter and data.

SFC0-13

CONFLICTING PARAMETERS

Reason:
Mutually exclusive parameters have been specified on the input command (for example,
TO and SPAN).

Action:
Correct the invalid parameters and resubmit the command.

SFC0-19

STORAGE SHORTAGE, TRY COMMAND LATER

Reason:
The specified forecast needed more CA Workload Automation SE storage to complete
its process, but not enough was available.

Action:
Verify that the command was properly entered, especially that the time interval is
correct.

May need to increase the CA Workload Automation SE region size.

If the problem persists, contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1361

SFCx

SCF0-20

SCHEDULE ID REQUIRED FOR JOB xxxxxxxx (WITH NO SCHEDULE)

Reason:
Forecast was requested for a job with no schedule defined. To produce a forecast, a
schedule ID is required.

Action:
Retry the command with an appropriate SCHID value.

SFC0-21

I/O ERROR DURING READ OF JOB DIRECTORY FOR JOB xxxxxxxx, RC=nn, WIP=ww,
MODULE=GFCJ

Reason:
Job xxxxxxxx could not be read from the database. Where:
■ nn is the return code.
■ ww is the point in module GFCJ where the I/O error occurred.

Action:
Try LJOB,JOB= command to verify that the job is in the database; or run the Database
Verification Utility. Correct any errors reported by the command or the utility. Then
reissue the forecast command that failed.

SFC0-22

I/O ERROR DURING SEQUENTIAL READ OF JOB DIRECTORY FOR THE FIRST RECORD,
RC=nn, WIP=A2, MODULE=GFCJ

Reason:
Some error has occurred while accessing the Job data set directory entries. Where:
■ nn is the return code.
■ A2 is the point in module GFCJ where the I/O error occurred.

Action:
Try LJOB command to verify that the job is in the database; or run the Database
Verification Utility. Correct any errors reported by the command or the utility. Then
reissue the forecast command that failed.

1362 Message Reference Guide

 SFCx

SFC0-23

I/O ERROR DURING SEQUENTIAL READ OF JOB DIRECTORY LAST RECORD READ WAS
FOR JOB xxxxxxxx, RC=nn, WIP=A3, MODULE=GFCJ

Reason:
Some error has occurred while accessing the Job data set directory entries. Where:
■ nn is the return code.
■ A3 is the point in module GFCJ where the I/O error occurred.

Action:
Try LJOB,JOB= command to verify that the job is in the database; or run the Database
Verification Utility. Correct any errors reported by the command or the utility. Then
reissue the forecast command that failed.

SFC0-24

I/O ERROR DURING READ OF JOB MEMBER FOR JOB xxxxxxxx, RC=nn, WIP=A4,
MODULE=yyyy.

Reason:
The indicated job could not be read from the database. The module suffix is indicated by
yyyy.

Action:
If nn=00, the job will probably have to be deleted and readded to the CA Workload
Automation SE database.

Run UCC7DBVR and look for 011 messages indicating no job entry record for a job
member. If found, delete and re-add those jobs.

SFC0-25

I/O ERROR DURING READ OF JOB SCHEDULE DIRECTORY FOR SJnnnnnn FOR JOB
xxxxxxxx, RC=nn, WIP=B1, MODULE=GFCJ

Reason:
The indicated schedule could not be read from the database. Where:
■ nn is the return code.
■ B1 is the point in module GFCJ where the I/O error occurred.

Action:
Delete the schedule and add it again. Then reissue the command.

Chapter 6: SANx - SJR2 Messages 1363

SFCx

SFC0-26

I/O ERROR DURING READ OF JOB SCHEDULE MEMBER FOR SJnnnnnn FOR JOB
xxxxxxxx, RC=nn, WIP=ww, MODULE=GFCJ

Reason:
The indicated schedule could not be read from the database. Where:
■ nn is the return code.
■ ww is the point in module GFCJ where the I/O error occurred.

Action:
Delete the schedule and add it again. Then reissue the command.

SFC0-27

I/O ERROR DURING READ OF CA-7 INDEX DATASET FOR TRGD.xxxxxxxx, RC=nn,
WIP=C1, MODULE=GFCJ

Reason:
An error occurred processing the IDS key starting with the characters TRGD. Where:
■ nn is the return code.
■ C1 is the point in module GFCJ where the I/O error occurred.

Action:
Issue the TRIG command to clean up possible IDS entry errors. Then reissue the forecast
command which failed. If the problem persists, contact your installation specialist.

1364 Message Reference Guide

 SFCx

SFC0-28

I/O ERROR DURING READ OF INDEX DATASET FOR INPUT NETWORK xxxxxxxx, RC=nn,
WIP=G0, MODULE=GFCN

Reason:
An error occurred accessing the IDS entry for NW.xxxxxxxx. Where:
■ xxxxxxxx is the network name.
■ nn is the return code.
■ G0 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify the network that is requested is a valid network. Two methods of verification
are available:
– Enter the LNTWK command, or
– Run the Database Verification Utility.
■ Correct any errors reported.
■ Reissue the forecast command which failed.

If the problem persists, contact your installation specialist.

SFC0-29

I/O ERROR DURING SEQUENTIAL READ OF CA-7 INDEX DATASET FOR THE FIRST NODE
NW., RC=nn, WIP=G1, MODULE=GFCN

Reason:
An error occurred trying to access the first NW. entry in the IDS. Where:
■ nn is the return code.
■ G1 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify that the database has network entries, or run the Database Verification
Utility.
■ Correct any errors reported.
■ Reissue the forecast command which failed.

If the problem persists, contact your installation specialist.

Chapter 6: SANx - SJR2 Messages 1365

SFCx

SFC0-30

I/O ERROR DURING SEQUENTIAL READ OF CA-7 INDEX DATASET LAST ENTRY READ
WAS NW.xxxxxxxx, RC=nn, WIP=G2, MODULE=GFCN

Reason:
The error occurred while accessing the IDS. Where:
■ xxxxxxxx is the network name.
■ nn is the return code.
■ G2 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Run the Database Verification Utility.
■ Correct any errors reported.
■ Reissue the forecast command which failed.

If the problem persists, contact your installation specialist.

SFC0-31

I/O ERROR DURING READ OF INPUT NETWORK DIRECTORY FOR NETWORK xxxxxxxx
(NWnnnnnn), RC=nn, WIP=H1, MODULE=GFCN

Reason:
The network specified probably has an entry in the IDS, but the Dataset data set has no
corresponding entry.

Action:
Try to delete the network to clear the IDS or contact your installation specialist.

1366 Message Reference Guide

 SFCx

SFC0-32

I/O ERROR DURING READ OF INPUT NETWORK MEMBER FOR NETWORK xxxxxxxx,
RC=nn, WIP=H2, MODULE=GFCN

Reason:
Error occurred while accessing member data for the network indicated. Where:
■ xxxxxxxx is the network name.
■ nn is the return code.
■ H2 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify the network exists.
■ Delete and add the network if necessary.
■ Retry the command.

If the problem persists, contact your installation specialist.

SFC0-33

I/O ERROR DURING READ OF INPUT NETWORK SCHEDULE DIRECTORY FOR SInnnnnn
FOR NETWORK xxxxxxxx, RC=nn, WIP=H7, MODULE=GFCN

Reason:
Error occurred while accessing schedule data for the network indicated. Where:
■ nnnnnn is the input network schedule data set number.
■ xxxxxxxx is the network name.
■ nn is the return code.
■ H7 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify the schedule exists.
■ Delete and add the schedule if necessary.
■ Retry the command.

If the problem persists, contact your installation specialist.

Chapter 6: SANx - SJR2 Messages 1367

SFCx

SFC0-34

I/O ERROR DURING READ OF INPUT NETWORK SCHEDULE MEMBER FOR SInnnnnn FOR
NETWORK xxxxxxxx, RC=nn, WIP=ww, MODULE=GFCN

Reason:
Error occurred while accessing schedule data for the network indicated. Where:
■ nnnnnn is the input network schedule data set number.
■ xxxxxxxx is the network name.
■ nn is the return code.
■ ww is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify the schedule exists.
■ Delete and add the schedule if necessary.
■ Retry the command.

If the problem persists, contact your installation specialist.

SFC0-35

I/O ERROR DURING READ OF OUTPUT NETWORK DIRECTORY FOR NETWORK xxxxxxxx
CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H1, MODULE=GFCN

Reason:
Job yyyyyyyy has network xxxxxxxx connected, but the network is not in the Dataset
data set or has caused an error. Where:
■ xxxxxxxx is the network name.
■ yyyyyyyy is the job name.
■ nn is the return code.
■ H1 is the point in module GFCN where the I/O error occurred.

Action:
Verify the connection using the DB.3 (JOBCONN) panel to delete or add the network.
Then retry the command.

1368 Message Reference Guide

 SFCx

SFC0-36

I/O ERROR DURING READ OF OUTPUT NETWORK MEMBER FOR NETWORK xxxxxxxx
CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H2, MODULE=GFCN

Reason:
The network had an error with member data. Where:
■ xxxxxxxx is the network name.
■ yyyyyyyy is the job name.
■ nn is the return code.
■ H2 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Delete and add the network.
■ Retry the command.

Note: The JOBCONN entries may need to be deleted and added as well.

SFC0-37

I/O ERROR DURING READ OF OUTPUT NETWORK SCHEDULE DIRECTORY FOR

SOnnnnnn FOR NETWORK xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H3,
MODULE=GFCN

Reason:
Schedule probably does not exist for network indicated. Where:
■ nnnnnn is the output network schedule data set number.
■ xxxxxxxx is the network name.
■ yyyyyyyy is the job name.
■ nn is the return code.
■ H3 is the point in module GFCN where the I/O error occurred.

Action:
Perform the following actions:
■ Verify that the schedule exists for the network named.
■ If the schedule is missing, add the schedule.
■ Retry the command.

Chapter 6: SANx - SJR2 Messages 1369

SFCx

SFC0-38

I/O ERROR DURING READ OF OUTPUT NETWORK SCHEDULE MEMBER FOR SOnnnnnn
FOR NETWORK xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=ww,
MODULE=GFCN

Reason:
Schedule member contained an error. Where:
■ nnnnnn is the output network schedule data set number.
■ xxxxxxxx is the network name.
■ yyyyyyyy is the job name.
■ nn is the return code.
■ ww is the point in module GFCN where the I/O error occurred.

Action:
Delete and add schedule for network named.

SFC0-39

NOT FOUND CONDITION OCCURRED DURING READ OF CA-7 INDEX DATASET FOR
INPUT NETWORK xxxxxxxx, RC=01, WIP=G0, MODULE=GFCN

Reason:
The requested network was not found.

Action:
Add the network and then retry the command.

1370 Message Reference Guide

 SFCx

SFC0-41

I/O ERROR DURING READ OF xxxxx FOR HEADER RECORDS FOR JOB# nnnnnnnn,
RC=nn, WIP=A2, MODULE=SFCQ

Reason:
Error occurred reading from queue for job nnnnnnnn. Where:
■ xxxxx is the queue name.
■ nnnnnnnn is the job number.
■ nn is the return code.
■ A2 is the point in module SFCQ where the I/O error occurred.

Action:
Perform the following actions:
■ Verify job is in queue xxxxx using LQ/LPRE/LPOST command.
■ Retry original command.

If the problem persists, contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1371

SFCx

SFC0-42

I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR HEADER RECORDS FOR THE FIRST
RECORD, RC=nn, WIP=A3, MODULE=SFCQ

Reason:
Error occurred accessing queue xxxxx. Where:
■ xxxxx is the queue name.
■ nn is the return code.
■ A3 is the point in module SFCQ where the I/O error occurred.

Action:
Perform the following actions:
■ Retry the command before going to the next step.
■ If xxxxx is REQQ, RDYQ, or ACTQ, try the LQ command to check the error condition.
■ If xxxxx is PREQ, try the LPRE command.
■ If xxxxx is POSTQ, try LPOST command.
■ If no error is reported by the previous steps, retry the forecast command.
■ If an error is detected, it may be necessary to perform a DMPQ/MOVQ operation or
format the queues.

If the error persists, contact your installation specialist for assistance.

1372 Message Reference Guide

 SFCx

SFC0-43

I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR HEADER RECORDS LAST RECORD
READ WAS FOR JOB yyyyyyyy, RC=nn, WIP=A4, MODULE=SFCQ

Reason:
Error occurred while accessing queue. Where:
■ xxxxx is the queue name.
■ nn is the return code.
■ A4 is the point in module SFCQ where the I/O error occurred.

Action:
Perform the following actions:
■ Retry the command before going to the next step.
■ If xxxxx is REQQ, RDYQ, or ACTQ, try the LQ command to check the error condition.
■ If xxxxx is PREQ, try the LPRE command.
■ If xxxxx is POSTQ, try LPOST command.
■ If no error is reported by the previous steps, retry the forecast command.
■ If an error is detected, it may be necessary to perform a DMPQ/MOVQ operation or
format the queues.

If the error persists, contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1373

SFCx

SFC0-44

I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR TRAILER RECORDS FOR JOB
yyyyyyyy, RC=nn, WIP=ww, MODULE=SFCQ

Reason:
Error occurred while reading requirement type records for the indicated job. Where:
■ xxxxx is the status queue name.
■ yyyyyyyy is the job name.
■ nn is the return code.
■ ww is the point in module SFCQ where the I/O error occurred.

The error condition could be temporary due to the job just entering the queues. An
entry error could have also occurred.

Action:
Use LQ command for indicated job to evaluate status. If status is SKELETON or RQMT
INC, the job may need to be canceled from the queue if the status does not clear up. If
status is not SKELETON or RQMT INC, reissue the forecast command. If the problem
persists, contact your installation specialist for assistance.

SFC0-51

I/O ERROR DURING READ/WRITE OF SCRATCH-FILE-1, RC=nn, WIP=ww, MODULE=xxxx

Reason:
Error occurred during the read or write operation of the Scratch file ID 1. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module xxxx where the I/O error occurred.
■ xxxx is the module name.

Action:
Contact your installation specialist for assistance.

1374 Message Reference Guide

 SFCx

SFC0-52

NOT ENOUGH SPACE ON SCRATCH-FILE-1, RC=nn, WIP=ww, MODULE=xxxx

Reason:
All Scratch file space for Scratch file ID 1 has been used while selecting job or station
data for the time interval and selection criteria given. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module xxxx where the I/O error occurred.
■ xxxx is the name of the module executing at the time.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the DAIO statement SCRTRK keyword in the
product's initialization file. CA Workload Automation SE must be reinitialized.

SFC0-61

I/O ERROR DURING READ/WRITE OF SCRATCH-FILE-2, RC=nn, WIP=ww, MODULE=xxxx

Reason:
Error occurred during the read or write operation of the Scratch file ID 2. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module xxxx where the I/O error occurred.
■ xxxx is the module name.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1375

SFCx

SFC0-62

NOT ENOUGH SPACE ON SCRATCH-FILE-2, RC=nn, WIP=ww, MODULE=xxxx

Reason:
All Scratch file space for Scratch file ID 2 has been used while selecting job or station
data for the time interval and selection criteria given. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module xxxx where the I/O error occurred.
■ xxxx is the module name.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the SCRTRK keyword in the product's
initialization file.

SFC0-71

I/O ERROR DURING READ/WRITE OF SCRATCH-FILE-8, RC=nn, WIP=ww, MODULE=xxxx

Reason:
Error occurred during the read or write operation of the Scratch file ID 8. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module xxxx where the I/O error occurred.
■ xxxx is the module name.

Action:
Contact your installation specialist for assistance.

1376 Message Reference Guide

 SFCx

SFC0-72

NOT ENOUGH SPACE ON SCRATCH-FILE-8, RC=nn, WIP=ww MODULE=xxxx

Reason:
All Scratch file space for Scratch file ID 8 has been used while selecting job or station
data for the time interval and selection criteria given. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point where the CA Workload Automation SE macro was issued.
■ xxxx is the module name.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the DAIO statement SCRTRK keyword in the
product's initialization file.

SFC0-81

I/O ERROR DURING READ/WRITE OF SCRATCH-FILE-7, RC=nn, WIP=ww, MODULE=GFCJ

Reason:
Error occurred during the read or write operation of the Scratch file ID 7. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in module GFCJ where the I/O error occurred.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1377

SFCx

SFC0-82

NOT ENOUGH SPACE ON SCRATCH-FILE-7, RC=nn, WIP=ww, MODULE=GFCJ

Reason:
All Scratch file space for Scratch file ID 7 has been used while selecting job or station
data for the time interval and selection criteria given. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point where the CA Workload Automation SE macro was issued.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the DAIO statement SCRTRK keyword in the
product's initialization file.

SFC0-86

NOT ENOUGH SPACE ON SCRATCH-FILE-6, RC=nn, WIP=ww, MODULE=GFCJ

Reason:
All Scratch file space for Scratch file ID 6 has been used while selecting job or station
data for the time interval and selection criteria given. Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point where the CA Workload Automation SE macro was issued.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the DAIO statement SCRTRK keyword in the
product's initialization file.

1378 Message Reference Guide

 SFCx

SFC0-91

ERROR DURING SORT OPERATION, RC=nn, WIP=ww, MODULE=xxxx

Reason:
ww is the point in the module (WIP) xxxx where the sort operation was being performed
on the Scratch file. nn is the return code from the SORT module. This is a CA Workload
Automation SE system problem.

Action:
Contact your installation specialist for assistance.

SFC0-96

SCHEDULE SCAN IS ACTIVE. TRY LATER.

Reason:
To prevent degradation on scheduling activity, queue related forecasts, such as FQJOB,
are not allowed while Schedule Scan is processing.

Action:
Wait a few minutes. Then try the forecast again. If the problem persists, contact CA
Support at ca.com/support for assistance.

SFC0-97

NOT ENOUGH SCRATCH SPACE AVAILABLE. PROCESSING TERMINATED

Reason:
No more tracks are available to allocate to the Scratch file, even though the number of
allocated tracks has not reached the maximum specified. This condition may have arisen
because of other activities in CA Workload Automation SE.

Action:
Try to run the command when CA Workload Automation SE has less activity. Alternately,
shut down CA Workload Automation SE with a DMPQ, increase the space in the scratch
queue, and reinitialize CA Workload Automation SE with a MOVQ startup.

Chapter 6: SANx - SJR2 Messages 1379

SFCx

SFC0-98

NOT ENOUGH SCRATCH SPACE SPECIFIED. PROCESSING TERMINATED

Reason:
All specified Scratch file space has been used and no more space is available for the
Scratch file operation.

Action:
Two options are available:
■ Change the time interval or vary the selection criteria to reduce the number of jobs
or stations selected.
■ Increase the Scratch file space using the SWFTRK keyword in the product's
initialization file DAIO statement.

SFC0-99

SYSTEM ERROR, RC=nn, WIP=ww, MODULE=xxxx

Reason:
If nn=00 and xx=AA, and the command is FJOB,JOB=*, no SJ members were found.
Where:
■ nn is the return code from the CA Workload Automation SE macro.
■ ww is the point in the module where the I/O error occurred.
■ xxxx is the module name.

Action:
Contact your installation specialist. Ensure that you have at least one SJ member.

SFC1-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Request complete.

Action:
None.

1380 Message Reference Guide

 SFEx

SFEx
SFEO-14

NETWORK (nnnn) ENTERED INTO POST-PROCESS 'Q' FOR nn STATION

Reason:
This message is issued to the CA Workload Automation SE Master Station to identify
work added to the postprocess queue as a result of a job being scheduled into the
preprocess queue.

Action:
None.

SFEP-11

xxxxxxxx STATION WORK (nnn,mmm) REF# jjjrrs

FOR NETWORK=xxxxxxxx, [SUB-ID=yyyyyyyy] , [JOB=zzzzzzzz],
DESC=dddddddd
REQUIRED BY yy.ddd AT hh:mm:ss, MUST START BY yy.ddd
AT hh:mm:ss
PROSE#=nnnnnnnn SYSTEM=ssssssss

****PROSE****

Reason:
This message is sent to the CA Workload Automation SE terminal associated with the
specified station to notify personnel at that station that work has been scheduled. If no
terminal is defined for the station, the message is sent to the CA Workload Automation
SE Master Station. The only prose that appears is that designated with #QDESC for
station xxxxxxxx.

Action:
None.

SFEP-12

xxxxxxxx STATION WORK (nnn,mmm) END.

Reason:
This signifies the end of the preceding SFEP-11 message.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1381

SFEx

SFEP-13

ERROR ENCOUNTERED WIP=xx

Reason:
An error has occurred in the program. The WIP value indicates the location in the
program where the error occurred.

Action:
Contact your installation specialist for assistance.

SFER-01

xx INVALID SGET RETURN CODE=nn

Reason:
An error has occurred in the processing of a CA Workload Automation SE data set.

Action:
If xx=JJ, KK, LL or CC, the CA Workload Automation SE Trailer queue might be full. Do a
/DISPLAY,Q=TRL to display status of the queue. If xx=EE, a data set member on the
database could not be read and the job must be reloaded. If xx=AA, the job's JCL may
contain hex data.

SFER-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

Reason:
An attempt to load the module indicated by xxxxxxxx has failed. The return code from
the SLOAD macro is indicated by nn (nn=04 indicates module not found; nn=12 indicates
an I/O error occurred).

Action:
Verify that the module indicated has not been inadvertently deleted from the
CA-7.LOADLIB and that the APPLCTN statement is present (and correct) in the CA
Workload Automation SE initialization file or in the SASSPROG module. If the problem
persists, contact your installation specialist for assistance.

1382 Message Reference Guide

 SFEx

SFER-08

JOB xxxxxxxx HAS MORE THAN 255 REQUIREMENTS

Reason:
A job has been brought into the REQ queue. The specified job has more than 255
requirements defined. Having more than 255 requirements defined for a job can lead to
errors when the job enters the request queue because the master requirement count
can only be a maximum of 256 before it resets.

Action:
This is an informational message unless RQMT255=YES is specified in the product's
initialization file OPTIONS statement. If specified, any job entering the REQQ with more
than 255 requirements has the first 254 requirements added and then a special user
requirement with text of SFER-08: JOB HAS MORE THAN 254 RQMTS. This user
requirement has to be posted manually. A WTO with prefix CA-7.SFER-08 is also
produced.

SFER-14

JOB#nnnn NW=xxxxxxxx id=yyyyyyyy NOT ADDED TO POST 'Q'. CODE=nn

Reason:
The specified network was not added to the Postprocess queue.

Action:
The output network must have a schedule and the SCHID must be the same as the job. If
the problem persists, contact your installation specialist for assistance.

SFER-15

ERROR OCCURRED, DEBUG DATA=xxxxxxxx

Reason:
An invalid requirement entry for a job was encountered. The display (xxxxxxxx) is in
hexadecimal.

Action:
Contact your installation specialist for assistance.

Chapter 6: SANx - SJR2 Messages 1383

SIRx

SIRx
SIRA-01

xx INVALID SGET RETURN CODE = nn

Reason:
An error was detected by SASSSIRA while issuing a CA Workload Automation SE macro
during job requirement checking. The macro statement where the error occurred is
indicated by xx and the return code is indicated by nn.

Action:
Contact your installation specialist for assistance.

SIRA-16

JOB RQMT jobname SATISFIED--DRCLASS drclass INACTIVE

Reason:
The specified job is a predecessor of another job entering the request queue. Because
the disaster recovery class of the job requirement is not active, the requirement is
satisfied (ignored).

Action:
None.

SIRD-01

xx INVALID SGET RETURN CODE=nn

Reason:
An error was detected by SASSSIRD while issuing a CA Workload Automation SE
application macro. The macro statement where the error occurred is indicated by xx; nn
is the return code from the call.

Action:
Contact your installation specialist for assistance.

1384 Message Reference Guide

 SIRx

SIRD-11

**** JOB=xxxxxxxx (nnnn) EXECUTION REQUIREMENTS **** JCLID=nnn

SYSTEM=ssssssss DESC=d...d
DUE-OUT yy.ddd/hhmm DEAD-LINE yy.ddd/hhmm
SUBMIT yy.ddd/hhmm MAINID=xxx
SCHID=nnn PROSE#=pppppppp ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx

*** REQUIREMENTS ***

*** JOB PROSE ***

Reason:
This message is issued to the CA Workload Automation SE Master Station or to an
alternate station (LTERM) defined in the database entry for the job xxxxxxxx. The
message is produced for each job when it enters the request queue due to calendar,
trigger, or DEMAND scheduling. Input requirements and their status will be described
immediately following the REQUIREMENTS heading. Job prose, if defined in a #QDESC
segment, is listed immediately following the JOB PROSE heading. The SYSTEM (sssssss)
and the DESC (d...d) value also come from the job prose definition.

The status fields in the message are as follows:

DUE-OUT
Indicates the date/time when the job must complete execution.
DEAD-LINE
Indicates the date/time calculated when the job must begin execution to finish by
DUE-OUT time. The value is determined by subtracting the average runtime for the
job from DUE-OUT.
SUBMIT
Indicates the date/time specified as a must-submit value in the schedule definition.
MAINID
Indicates the system identifier. If present, MAINID indicates where the job should
(or should not) be submitted.
ERQD
Indicates a count of total external requirements.
ENSAT
Indicates a count of external requirements not satisfied.
IRQD
Indicates a count of total internal requirements.
INSAT

Chapter 6: SANx - SJR2 Messages 1385

SIRx

Indicates a count of internal requirements not satisfied.

MCNT
Indicates a master count of unsatisfied requirements for the job.
FLAGS
Provides hexadecimal values matching the following fields from the JQREC macro
DSECT. The fields are listed in order of appearance in the message.
■ JQFLG1
■ JQFLG2
■ JQJFLG1
■ JQJFLG2
■ JQJFLG3
■ JQJFLG4
■ JQJFLG5

Note: If a satisfied job requirement is followed by the text "(DRMODE)," the

requirement was satisfied because CA Workload Automation SE is in disaster recovery
mode, and the predecessor job has an inactive disaster recovery class.

Action:
None.

SIRD-12

END OF REQUIREMENTS FOR JOB=xxxxxxxx(nnnn).

Reason:
This message terminates the initial requirements display that followed the SIRD-11
message for the specified job.

Action:
None.

1386 Message Reference Guide

 SIRx

SIR0-01

xx INVALID SGET RETURN CODE=nn

Reason:
An error was detected by SASSSIR0 while issuing a CA Workload Automation SE macro.
The macro statement where the error occurred is indicated by xx; nn is the return code
from the call.

Action:
Contact your installation specialist for assistance.

SIR0-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

Reason:
An attempt to load the module indicated by xxxxxxxx has failed. The return code from
the SLOAD macro is indicated by nn (nn=04 indicates module not found; nn=13 indicates
an I/O error occurred).

Action:
Verify that module xxxxxxxx has not been inadvertently deleted from the CA-7.LOADLIB
and that the APPLCTN statement is present (and correct) in the product's initialization
file or in the SASSPROG module. If the problem persists, contact your installation
specialist for assistance.

SIR0-11

INITIAL REQUIREMENTS SCAN STARTED AT hh:mm:ss ON yy.ddd.

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate
that initial requirements scanning has started for jobs placed in the request queue
during the Schedule Scan interval. Input requirements for all newly added jobs will be
scanned and those already satisfied will be posted.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1387

SIRx

SIR0-12

INITIAL REQUIREMENTS SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
This message is issued to the CA Workload Automation SE Master Station to indicate the
completion of the initial requirements scan activity.

Action:
None.

SIR0-13

REQUIREMENT LIST SUPPRESSED FOR JOB=xxxxxxxx (nnnn)

Reason:
User has indicated that the requirement list for the specified job is to be suppressed.
This may be set by job using the JOB panel. It may be globally set by using
SSCAN,SCAN=ABR.

Action:
None.

SIR0-14

jjjjjjjj(nnnn) detail-text

Reason:
An error occurred while trying to initiate ARF monitoring. jjjjjjjj is the name of the job
that had the error. nnnn is the CA 7 WA job number of the job. Descriptions of detail
texts follow.

Action:
See reason and action for detail message.

UNABLE TO LOCATE ARF TRAILER.

Detail Reason:
The ARF segment on the TRAILER queue could not be found.
Detail Action:
Cancel the job and resubmit. If the problem persists, contact CA Support at
ca.com/support for assistance.

1388 Message Reference Guide

 SIRx

ARF ENVIRONMENT ERROR.

Detail Reason:
One or more ARF control areas could not be located.
Detail Action:
Ensure that ARF=YES is coded on the RESTART statement for ARF monitoring.
Cancel the job and resubmit. If the problem persists, contact CA Support at
ca.com/support for assistance.

SQ ERROR AT nnnn ERR=xxxx

Detail Reason:
An error occurred trying to issue a CA Workload Automation SE queue access
macro. nnnn is the SASSARFA module offset and xxxx is the macro return code.
Detail Action:
Cancel the job and resubmit. If the problem persists, contact CA Support at
http://ca.com/support for assistance.

#ARJI ERROR FOR ssssssss ERR=aaaa bbbb cccc

Detail Reason:
An error occurred trying to issue a CA Workload Automation SE ARF macro. ssssssss
is the name of the ARFSET. aaaa is the return code. bbbb is the reason code and
cccc is an information code.
Detail Action:
Cancel the job and resubmit. If the problem persists, contact CA Support at
ca.com/support for assistance.

NO ARF TESTS FOR ssssssss

Detail Reason:
An ARFSET was specified for ARF monitoring, but no tests were applicable for this
run.
Detail Action:
None.

ARF ATTACH COMPLETE - ssssssss

Detail Reason:
ARF monitoring has begun for the job named. The ARFSET that will be used for ARF
monitoring is ssssssss.
Detail Action:
None.

Chapter 6: SANx - SJR2 Messages 1389

SJC0

SJC0
This subsection contains the CA Workload Automation SE SJC0 messages. These
messages relate to job submission.

SJC0-00

SUBMIT PROGRAM STARTED

Reason:
The job submission function of CA Workload Automation SE has started.

Action:
None.

SJC0-00

JCL SUBMIT COMPLETE nnn JOBS SUBMITTED AT hh:mm:ss ON yy.ddd

Reason:
All jobs in the ready queue that were to be submitted have been written to the submit
data set or internal reader. nnn identifies the number of jobs submitted during this job
submission cycle. If JSOP=2 or PSP=Y is used, the value of nnn is 000. You can check for
Messages SS00-45 and SS0-46 for other information.

Action:
None.

SJC0-03

REQQ SCAN COMPLETE AT hh:mm:ss ON yy.ddd; nnn JOBS MOVED TO READY QUEUE

Reason:
This is an informational message indicating that the request queue scan completed at
the time and date shown (hh:mm:ss and yy.ddd). The number of jobs with master count
= 0, reflected in nnn, are moved to the ready queue.

Action:
None.

1390 Message Reference Guide

 SJC0

SJC0-11

ERROR - MOVE FROM REQUEST TO READY QUEUE

Reason:
An error occurred while attempting to move header records from the request queue to
the ready queue. The ready queue may be full.

Action:
If the ready queue is full, the job will be moved later. If not, contact your installation
specialist for assistance.

SJC0-13

ERROR - READ OF REQUEST QUEUE

Reason:
An error occurred while scanning the request queue for jobs to move to the ready
queue.

Action:
Contact your installation specialist for assistance.

SJC0-14

ERROR - UPDATE OF REQUEST QUEUE

Reason:
A nonexecutable job was marked as processed, and an error occurred while attempting
to replace the entry in the request queue.

Action:
Contact your installation specialist for assistance.

SJC0-15

REQUEST QUEUE STOPPED

Reason:
The request queue was stopped by the STOP,Q=REQ command. No jobs will be moved
from the request queue to the ready queue.

Action:
If you want job submission, restart the request queue using START,Q=REQ.

Chapter 6: SANx - SJR2 Messages 1391

SJC0

SJC0-16

READY QUEUE STOPPED - NO SUBMIT

Reason:
An attempt was made to submit jobs, but the ready queue has been stopped by the
STOP,Q=RDY command.

Action:
If you want job submission, restart the ready queue using START,Q=RDY.

SJC0-21

ERROR - ON READ OF READY QUEUE

Reason:
An error occurred on the first GET reading the ready queue for jobs to submit. A
problem exists in the ready queue.

Action:
Contact your installation specialist for assistance.

SJC0-22

ERROR - READY QUEUE GET NEXT

Reason:
An error occurred on a GETNEXT reading the ready queue for jobs to submit. A problem
exists in the ready queue.

Action:
Contact your installation specialist for assistance.

1392 Message Reference Guide

 SJC0

SJC0-33

INVALID JOB CARD COLS 70-71 MUST BE BLANK

Reason:
Data was found in columns 70, 71, or both of the JOB statement. These columns are
used by CA Workload Automation SE. The columns must be blank. When using CA
Workload Automation SE NCF or external security, column 69 may also need to be
blank. See the chapter "Installation Requirements" in the Systems Programming Guide.

Action:
Use the text editor to correct the JOB statement.

SJC0-34

INVALID JOB CARD

Reason:
This error may be caused by one of the following situations:
■ The JOB statement format in the execution JCL is actually invalid.
■ Check the DBASE statement for LDJOBNM. If the LDJOBNM parameter is used, the
word JOB does not begin in column 12 or later.

Action:
Use the text editor to correct the JCL in the queue. You may also want to change the
execution JCL permanently.

SJC0-35

FIRST RECORD OF JCLMBR NOT A JOB CARD

Reason:
The first record in the JCL member containing the job's execution JCL is not a valid JOB
statement.

Action:
Use the text editor to correct the JCL in the queue. The execution JCL member should
also be permanently updated.

Chapter 6: SANx - SJR2 Messages 1393

SJLx

SJLx
This subsection contains the CA Workload Automation SE messages beginning with SJL.
These messages relate to job load processing.

SJL0-00

JOB xxxxxxxx (nnnn) LOAD SUCCESSFUL. ***JOB LOADED.***

***LOAD ONLY, PURGED FROM REQUEST "Q".***

Reason:
The job has been successfully loaded.

Action:
None.

SJL0-00

JOB xxxxxxxx (nnnn) RELOAD SUCCESSFUL. ***JOB RELOADED.***

Reason:
The job has been successfully reloaded.

Action:
None.

SJL0-01

WIP=xx INVALID MACRO RETURN CODE=xxxxxxxx.

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** ***LOAD FAILED***

Reason:
The LOAD program has detected an unexpected error.

Action:
Run the SASSBK00 backup. Examine for error conditions. If some errors are
encountered, contact your installation specialist for assistance.

1394 Message Reference Guide

 SJLx

SJL0-01

WIP=xx INVALID MACRO RETURN CODE=xxxxxxxx.

DSN=x...........x
*** LOAD UNSUCCESSFUL, JOB LOCKED. *** ***LOAD FAILED***

Reason:
An unexpected error relating to the data set indicated has been detected by the LOAD
program.

Action:
If WIP=CY, member exists on IDS but not on the Dataset data set. Check for conflicts
related to the data set and correct, or contact your installation specialist for assistance.
If the data set name is not a valid OS data set name, reload the job, commenting out the
DD for the data set.

If WIP=CU and return code is 0, the SCRTRK value on the DAIO statement in the
initialization file may be too small.

SJL0-03

OUT OF SPACE ON DATA BASE

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** *** LOAD FAILED ***

Reason:
Insufficient space encountered while attempting to add a database entry during LOAD
processing for a job. If a DSN is listed, the job loaded but indicated data sets were not
added to the database. If no DSN is listed, the job itself was not added.

Action:
Check system log for WTO identifying the database file having an out-of-space
condition. After shutting down CA-7:
1. Back up the database.
2. Reallocate the affected file.
3. Reload the database.
4. Reload all jobs for which this message appeared.

Chapter 6: SANx - SJR2 Messages 1395

SJLx

SJL0-11

DSN= x.....x RENAMED x.....x TO AVOID INDEX CONFLICT

Reason:
The DSNAME is already cataloged for a prose or network entry. For SVS users with a
VSAM master catalog, this message could result from the DSNAME having been
cataloged in the VSAM master.

Action:
If the data set is permanent, no action is necessary other than to mark it as PERM on the
DSN panel. All database references will be through the renamed value. The data set has
assumed a new name only in the CA Workload Automation SE database. Your JCL
remains unchanged. For nonpermanent data sets, it may be necessary to restructure
your entries to avoid this conflict.

SJL0-12

UNABLE TO ADD TO INDEX DS DSN=x.....x

(OUT OF SPACE ON DATA BASE)
*** LOAD UNSUCCESSFUL, JOB LOCKED. *** *** LOAD FAILED ***

Reason:
An error resulted from the attempt to enter the above DSN in the CA Workload
Automation SE IDS. You may have no space in the Dataset data set or in the Index data
set for adding the specified DSN. If an out-of-space problem occurs, a WTO is issued.

Action:
Resolve the error and reload the job in question. If an out-of-space condition exists,
steps should be taken to increase the size of the data set.

1396 Message Reference Guide

 SJRx

SJL0-13

HAS INVALID OR NO LOAD DATA.

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** *** LOAD FAILED ***

Reason:
An unexpected error has caused invalid or missing data for the job. The job may have
been canceled while CA Workload Automation SE LOAD processing was occurring.

Action:
Rerun the load and if the problem recurs, contact your installation specialist for
assistance. If running two copies of CA Workload Automation SE, be sure a test version
of the load procedure CA07LOAD is changed to execute from the test CA Workload
Automation SE load library and the test copy of CA Workload Automation SE specifies
the test load procedure in the initialization file.

SJL1-01

WIP=zz INVALID MACRO RETURN CODE=yyyyyyyy

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** *** LOAD FAILED ***

Reason:
An attempted load failed. If zz=38 and yyyyyyyy=00000005, the error was encountered
trying to load job information to the Job data set.

Action:
If the error persists, try doing a backup and reload. Check the CI and CA sizes of the Job
data set. The Job data set may require a larger allocation.

SJRx
SJR0-10

RESTART STEP LIST FOR JOB...xxxxxxxx (nnnn) yyyyyyyy aaaaaaaaa bbbbb

Reason:
This message is produced when a RESTART command is done for a job. xxxxxxxx is the
job name. yyyyyyyy is the job prose number (and is 0 when no prose exists). aaaaaaaaa
is the failure code information. bbbbb is the JES job number.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1397

SJRx

SJR0-12

JOB NOT FOUND ON REQUEST QUEUE

Reason:
The job specified on the input command could not be found in the request queue.

Action:
Verify the job name or CA 7 WA job number; correct and resubmit the command.

SJR0-14

*NOTE* - JOB RESTART NOT REQUIRED

Reason:
The job that is specified on the input command does not require a restart.

Action:
Verify the job name or CA 7 WA job number; correct and resubmit the command.

SJR0-15

xxxxxxxx RESULTED IN I/O ERROR...n

Reason:
The CA Workload Automation SE macro being used when the I/O error occurred is
indicated by xxxxxxxx as follows:
■ SGET-DIR - Read the Job data set directory.
■ SGET-JOB - Read a job entry on the Job data set.
■ SGET-STEP - Read a step entry on the Job data set.

The I/O error return code is indicated by n.

Action:
Contact your installation specialist for assistance.

1398 Message Reference Guide

 SJRx

SJR0-16

INVALID FUNCTION SPECIFIED

Reason:
The function specified on the input request was not LIST or RESTART.

Action:
Correct and resubmit the command.

SJR0-17

JOB= WAS NOT SPECIFIED OR INVALID

Reason:
The JOB parameter was either omitted from the input request or contained an invalid
CA 7 WA job number.

Action:
Correct and resubmit the command.

SJR0-18

JOB NOT FOUND ON JOB DATA SET

Reason:
The job name did not match a member in the user-defined job data set.

Action:
Correct and resubmit the command.

SJR0-19

FORCECOMP= IS INVALID

Reason:
The value given for the FORCECOMP parameter was not YES or NO.

Action:
Correct and resubmit the command.

Chapter 6: SANx - SJR2 Messages 1399

SJRx

SJR0-20

EXPRESS= IS INVALID

Reason:
The value given for the EXPRESS parameter was not YES.

Action:
Correct and resubmit the command.

SJR0-21

SUP11STP= IS INVALID

Reason:
The value given for the SUP11STP parameter was not YES or NO.

Action:
Correct and resubmit the command.

SJR0-22

AN INVALID KEYWORD WAS ENTERED

Reason:
A keyword specified in the input command was invalid for the requested function.

Action:
Correct and resubmit the command.

SJR0-23

PROCESS= IS INVALID

Reason:
The CA WA Restart Option processing code, given by the PROCESS keyword, is invalid.
Allowable values are R, F or N.

Action:
Correct and resubmit the command.

1400 Message Reference Guide

 SJRx

SJR0-24

STPSTRT= MUST BE USED WITH PROCSTRT=

Reason:
Whenever the PROCSTRT keyword is used to indicate a starting point within a specific
PROC, STPSTRT must also be used to supply the starting step within that PROC. This is
true even if the starting step is the first in the PROC.

Action:
Correct and resubmit the command.

SJR0-25

STPEND= MUST BE USED WITH PROCEND=

Reason:
Whenever the PROCEND keyword is used to indicate that processing is to end with a
specific PROC, STPEND must also be specified to supply the ending step within that
PROC. This is true even if the ending step is the last in the PROC.

Action:
Correct and resubmit the command.

SJR0-26

LSTP= MUST BE USED WITH LPSTP=

Reason:
A procedure step name was specified without a corresponding step name.

Action:
Supply a valid procedure step name and then press Enter.

SJR0-27

LCC= REQUIRED AND MUST BE LESS THAN 4096

Reason:
If a LSTP value is specified, LCC must be used to specify the condition code for the step.

Action:
Supply a valid condition code and then press Enter.

Chapter 6: SANx - SJR2 Messages 1401

SJRx

SJR0-28

USAGE= IS REQUIRED

Reason:
The CA WA Restart Option installation options require that a usage code be supplied for
restarts.

Action:
Supply a valid usage and then press Enter.

SJR0-29

STPSTRT= IS REQUIRED WITH LSTP=

Reason:
If a LSTP value is specified, the starting step name must also be supplied.

Action:
Add the step name that you want, and then press Enter.

SJR0-32

CONDCD= IS NOT VALID

Reason:
The value specified for the CONDCD keyword is invalid. Value must be numeric, 0 to
4095.

Action:
Correct and resubmit the command.

SJR0-33

FORCE= IS NOT VALID

Reason:
The value given for FORCE was not YES. This is the only valid value.

Action:
Correct and resubmit the command.

1402 Message Reference Guide

 SJRx

SJR0-34

PROSE= IS INVALID AS USED

Reason:
The value given for PROSE was not YES or NO.

Action:
Correct and resubmit the command.

SJR0-35

BYPGDG= IS NOT VALID

Reason:
The value given for BYPGDG was not YES, NO, VER, or CAT.

Action:
Correct and resubmit the command.

SJR0-36

REASON REQUIRED BUT MISSING

Reason:
A reason is required for restarts, as specified on the RESTART statement in the
initialization file, but one was not entered.

Action:
Reenter request and supply a REASON parameter.

SJR1-10

RESTART STEP LIST FOR JOB...xxxxxxxx (nnnn) yyyyyyyy aaaaaaaaa bbbbb

Reason:
This message is produced when LIST,JOB=nnnn is done. xxxxxxxx is the job name.
yyyyyyyy is the job prose number (and is 0 when no prose exists). aaaaaaaaa is the
failure code information. bbbbb is the JES job number.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1403

SJRx

SJR1-12

*NOTE* - JOB ALREADY CONTAINS CA-11 RESTART JCL

Reason:
This is an informational message indicating that the job to be restarted contains CA WA
Restart Option JCL, thus making a step restart possible.

Action:
None.

SJR1-13

*NOTE* - CA-11 IS NOT AVAILABLE IN CA-7 FOR RESTART

Reason:
The product's initialization file option indicating CA WA Restart Option (RMS) availability
is not present; therefore, CA Workload Automation SE cannot generate the RMS step
JCL. If RMS JCL is already present in the job, it may be used by supplying parameters
with the text editor.

Action:
If CA WA Restart Option is available, the product's initialization file should be changed.
The RESTART statement is required.

SJR1-14

*NOTE* - INSERTRMS=NO AND CA-11 IS AVAILABLE

Reason:
INSERTRMS=NO is indicated on the Job panel for the job being restarted.

Action:
None.

1404 Message Reference Guide

 SJRx

SJR1-15

*NOTE* - JOB RESTARTABLE BY CA-7 USING CA-11

Reason:
This is an informational message indicating the requested job is restartable and CA WA
Restart Option is available for the restart.

Action:
None.

SJR1-18

PROSE NOT FOUND

Reason:
The job did not have PROSE when it entered the request queue, or no #RESTART
segment is supplied in the PROSE.

Action:
Add appropriate PROSE data to the job if needed.

SJR2-00

FORCED COMP - JOB xxxxxxxx(nnnn) COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The job has been forced to a completed status successfully by a FORCECOMP=YES
parameter.

Action:
None.

SJR2-00

RESTART FOR JOB xxxxxxxx(nnnn) COMPLETED AT hh:mm:ss ON yy.ddd

RESTARTED FOR STEP yyyyyyyy (FIRST) THRU zzzzzzzz (LAST).

Reason:
Restart activity for the requested job has been completed. The step where the restart
began is indicated. The ending step (if other than the last step of the job) is also shown.

Action:
None.

Chapter 6: SANx - SJR2 Messages 1405

SJRx

SJR2-10

RESTART STEP LIST FOR JOB...xxxxxxxx (nnnn) yyyyyyyy aaaaaaaaa bbbbb

Reason:
This message is produced when a RESTART command is done for a job. xxxxxxxx is the
job name. yyyyyyyy is the job prose number (and is 0 when no prose exists). aaaaaaaaa
is the failure code information. bbbbb is the JES job number.

Action:
None.

SJR2-13

STPEND= PRECEDES STPSTRT= IN JOB

Reason:
The specified ending step of the restart occurs before the specified starting step.

Action:
Correct and resubmit the command.

SJR2-14

STPSTRT= OCCURS AFTER LAST SUCCESSFUL STEP COMPLETED (xxxxxxxx)

Reason:
The specified starting step for the restart occurs after the last successfully executed
step. This is not a valid restart point.

Action:
Correct and resubmit the command with a valid start step.

SJR2-15

STPSTRT=/STPEND= IGNORED, NO RESTARTABLE STEPS, *RERUN* ASSUMED

Reason:
STPSTRT, STPEND, or both were specified but are ignored because the job has no
restartable steps. A job rerun will be performed.

Action:
None.

1406 Message Reference Guide

 SJRx

SJR2-16

*RERUN* ASSUMED, CA-11 IS NOT AVAILABLE

Reason:
An attempt was made to do a CA WA Restart Option step restart without CA WA Restart
Option. This is not allowed.

Action:
A total job rerun must be done, or the OS Step Restart facility must be used through a
JCL override.

SJR2-17

xxxxxxxx RESULTED IN I/O ERROR ...n

Reason:
The CA Workload Automation SE macro being used when the I/O error occurred is
indicated by xxxxxxxx as follows:
SGET-DIR
Read the Job data set directory.
SGET-JOB
Read a job entry on the Job data set.
SGET-STEP
Read a step entry on the Job data set.
SQGET
Read a job on the request queue.

The I/O error return code is indicated by n.

Action:
Resubmit the command. If the error recurs, contact your installation specialist for
assistance.

Chapter 6: SANx - SJR2 Messages 1407

SJRx

SJR2-18

xxxxxxxx IS NOT A RESTARTABLE STEP!

Reason:
The step specified by STPSTRT is not a valid restart point.

Action:
Correct and reenter the command.

SJR2-20

//*UCC7RESTART CARD NOT FOUND IN JCL

Reason:
The JCL statement which CA Workload Automation SE uses to communicate restart
parameters to CA WA Restart Option is not available.

Action:
If INSERT RMS=Y is specified in the database definition for the job, a problem exists with
the CA Workload Automation SE system. Contact your installation specialist for
assistance.

SJR2-21

JOB HAS NO STEPS - CANNOT BE RESTARTED

Reason:
An attempt to restart a job failed because the job does not have any steps.

Action:
If the job is supposed to have steps in the JCL, they may be added using the QJCL facility.

SJR2-22

CMT MEMBER NOT FOUND - USE STPSTRT=*RERUN*

Reason:
An attempt was made to restart the job using STPSTRT=*CMT*, but CA Workload
Automation SE could not access a CMT member for the job.

Action:
The job should be restarted using the parameter STPSTRT=*RERUN* to rerun the entire
job.

1408 Message Reference Guide

 SJRx

SJR2-23

*CMT* NOT VALID, JOB NOT SET FOR CA-11 RESTART.

Reason:
A RESTART command was issued with STPSTRT=*CMT* but the job was not set for
restart in the CA WA Restart Option CMT.

Action:
If the job is to be restarted, use STPSTRT=*RERUN* or supply the specific starting and
ending step names.

SJR2-25

UNABLE TO RESTART, ARF RECOVERY IN PROGRESS

Reason:
CA Workload Automation SE issues this message when a RESTART command is
attempted while ARF is controlling recovery for a job.

Action:
Wait until ARF recovery is complete for the job. You can use the LARFQ command to
track the progress of ARF recovery for the job.

If you must issue the RESTART command prior to the completion of ARF recovery, you
can issue the ARFP command to terminate ARF recovery processing for the job. After
the ARFP command processing completes, you can issue the RESTART command.

SJR2-51

JOB IS NOT RESTARTABLE - USE *RESUBP*

Reason:
According to CA WA Restart Option, the job is not restartable.

Action:
Use the *RESUBP* option to resubmit the job for rerun.

Chapter 6: SANx - SJR2 Messages 1409

SJRx

SJR2-51

CMT MEMBER NOT AVAILABLE - RETRY LATER

Reason:
Another user in the system has the CMT member for the job under exclusive control.

Action:
Wait a few minutes, and retry the request again. If the problem persists, contact your
installation specialist for assistance.

SJR2-51

CMT CHANGED SINCE DISPLAYED - TRY AGAIN

Reason:
Between initial display and update request, another user updated the CMT member for
the job.

Action:
Recheck the displayed fields, correct and reenter.

SJR2-51

FATAL ERROR - CA-11 MAY BE DOWN

Reason:
The CA WA Restart Option Database Address Space appears to be down.

Action:
Perform the following actions:
■ Check status of CA WA Restart Option.
■ Reinitialize if necessary.
■ Try the request again.
If the problem persists, contact your installation specialist for assistance.

1410 Message Reference Guide

 SJRx

SJR2-51

START STEP NOT FOUND IN CMT - TRY ANOTHER

Reason:
The requested starting step name for restart was not found in the CMT.

Action:
Use a different step name and try again. You may want to check the CMT member for
the job using the CINQ command to CA WA Restart Option through the ARTS monitor.

SJR2-51

END STEP NOT FOUND IN CMT - TRY ANOTHER

Reason:
The requested ending step name for restart was not found in the CMT.

Action:
Use a different step name and try again. You may want to check the CMT member for
the job using the CINQ command to CA WA Restart Option through the ARTS monitor.

SJR2-51

USAGE CODE MUST CHANGE - TRY AGAIN

Reason:
CA WA Restart Option options require the usage code to change between runs but the
XRST panel field matches the CMT field.

Action:
Change the usage field on the XRST panel and try again.

SJR2-51

LRTCD STEP NOT FOUND IN CMT BEFORE START STEP

Reason:
A CA WA Restart Option restart was attempted, but the step name specified in the
LRTCD field is not prior to the step specified for the starting step.

Action:
Correct the step names and then press Enter.

Chapter 6: SANx - SJR2 Messages 1411

SJRx

SJR2-52

JOB FOUND BUT LOAD PROCESSING INCOMPLETE

Reason:
A restart (or force complete) was attempted on a job that is in the LOAD process.

Action:
Allow the job to complete the LOAD process, and then retry the command.

1412 Message Reference Guide

Chapter 7: SLFA - SPOR Messages
This chapter contains the SLFA through SPOR messages.

SLFA Through SLI7

This section contains the SLFA through SLI7 messages.

SLFA-00

ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
Awaiting your choice of functions.

Action:
Perform the following actions:
■ Display catalog entries by entering the values you want and pressing Enter.
■ Enter the FUNCTION value you want to transfer to another menu or formatted
input panel.
■ Position the cursor to the top line and enter a command.

SLFA-05

INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Reason:
An error was detected with the contents of the indicated field. The cursor is positioned
to that field.

Action:
Correct and retry.

Chapter 7: SLFA - SPOR Messages 1413

SLFA Through SLI7

SLIx-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the date and time shown.

Action:
None.

SLIx-01

aa INVALID SGET RETURN CODE=xx

Reason:
Where:
■ aa is the SGET macro statement where the error occurred.
■ xx is the return code from the macro.

If SLIxSLIA, aa=38 and xx=01, a pointer from the Job data set points to a DSNBR not in
the Dataset data set.

If SLIxSLIG, aa=B5, and xx=03, a schedule member cannot be read.

Action:
Perform the following actions:
■ Do another LOAD on the job if SLIxSLIA, aa=38 and xx=01.
■ Try the command again if SLIxSLIG, aa=B5, and xx=03.

If the problem persists, contact your installation specialist for assistance.

1414 Message Reference Guide

 SLFA Through SLI7

SLIx-02

JOB=xxxxxxxx NOT FOUND

[DSN= x....x)|(DSNBR= x...x)] NOT FOUND
NW=xxxxxxxx NOT FOUND

Reason:
In general, the job, data set name (or node), data set number (or generic), or network
cannot be found in the CA Workload Automation SE database.

The format for data sets (by function) is as follows:

■ LDSN - DSNBR= value must begin with DS.
■ LPROS - DSN=/DSNBR= value must begin with PP.

In all cases DSN must be the fully qualified name or level of nodes that you want.

Action:
Verify that the requested job, data set name, data set number, or network is correct and
in the correct format.

SLIx-03

REQUIRED INPUT MISSING

Reason:
Either DSN or DSNBR is required for LDSN or LPROS. For other commands, a required
element was not specified.

Action:
Correct and resubmit the command.

SLIx-04

CONFLICTING INPUT PARAMETERS

Reason:
Mutually exclusive parameters were specified on the input request.

Action:
Correct and resubmit the command.

Chapter 7: SLFA - SPOR Messages 1415

SLFA Through SLI7

SLIx-05

INVALID 'LIST=' OPTION

Reason:
The LIST option specified is not allowable for the type of request (that is, LIST=ALL may
not be used with node or generic requests).

Action:
Correct and resubmit the command.

SLIx-05

INVALID 'ST=' OPTION

Reason:
The ST option specified is not allowable for the type of request (that is, conflicts with
another option such as LIST=ALL).

Action:
Correct and retry the request.

SLIx-07

INVALID GENERIC NAME OR NODE

Reason:
The format of the DSN node or DSNBR generic name is incorrect as specified. The
database might have a bad job entry.

Action:
Correct and resubmit the command. For LPROS, the DSN value must be DSN=PP, at the
least. If using DSNBR the value must be at least DSNBR=xx*, where xx=DS for LDSN,
xx=PP for LPROS, xx=NW for LNTWK or xx=SI/SJ/SO for LSCHD. If a bad job entry exists,
delete the job. This will also delete job schedules, triggers, and prose.

1416 Message Reference Guide

 SLFA Through SLI7

SLIx-08

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Reason:
Module xxxxxxxx failed to load. The return code from the SLOAD macro is specified by
nn.

Action:
If the module name begins with UCC7R, verify that the user-defined Workload Balancing
module was not deleted from the CA Workload Automation SE load library. If the
module is not a WLB module, make sure it exists on the CA Workload Automation SE
load library and that there is an APPLCTN for the module in either the initialization file
or in the SASSPROG module. If it is present in the load library, contact your installation
specialist for assistance.

SLIx-09

SEGMENT/SUBSEGMENT NOT FOUND

Reason:
A prose segment, subsegment, or both were requested but could not be found within
the prose member specified.

Action:
Reenter with correct values. Listing the entire member allows the correct
segment/subsegment contents to be reviewed.

SLIx-11

YOU ARE NOT AUTHORIZED TO ....text....

Reason:
A command or data access has been denied due to security definition.

Action:
Contact your security administrator if the command or data access should be allowed.

Chapter 7: SLFA - SPOR Messages 1417

SLFA Through SLI7

SLIx-16

JOB xxxxxxxx FOUND BUT NOT WITH OTHER VALUES ENTERED

Reason:
A job was requested and other selection parameters were specified. The job was found
in the database, but the other parameters did not match the values for the job.

Action:
Perform one of the following actions:
■ Reenter with correct values.
■ Omit the other parameters.

SLIx-17

NO JOBS MATCH PARAMETERS ENTERED

Reason:
No jobs were found to match the combination of selection parameters requested.

Action:
Reenter with new values if you want.

SLIx-18

NO SCHEDULES MATCH PARAMETERS ENTERED

Reason:
No schedule records were found to match the LSCHD parameters requested.

Action:
Reenter with new values if you want.

SLIx-19

NO QUEUE RECORDS MATCH PARAMETERS ENTERED

Reason:
Either the queue was empty or none of the records in the queue matched the selection
parameters specified on the command.

Action:
Reenter with new values if you want.

1418 Message Reference Guide

 SLFA Through SLI7

SLIx-21

INSUFFICIENT STORAGE - FURTHER QUALIFY THE DSN

Reason:
A listing request was issued that required too much storage to process the request.

Action:
Reissue the command after further qualifying the data set name.

SLIA-nn

See the SLIx messages.

SLIA-07

INVALID GENERIC NAME OR NODE

Reason:
An error was detected in reading the job record from the Job data set on an LJOB
command.

Action:
Perform the following actions:
■ Delete the job from the DB.1 (JOB) panel.
■ Add the job back to CA Workload Automation SE, including schedules, triggers,
prose, and all related information.

SLIA-10

JOB= xxxxxxxx FOUND BUT NOT IN SYS= nnnnnnnn

Reason:
Job xxxxxxxx was found but not in system nnnnnnnn.

Action:
Determine if the job is in the system specified. If so, contact your installation specialist
for assistance.

Chapter 7: SLFA - SPOR Messages 1419

SLFA Through SLI7

SLIA-68

FOLLOWING FIELDS NOT ALLOWED FOR INTERNAL CROSS PLATFORM JOBS.

Reason:
This message is issued when fields that apply to a CPU job are requested for a specific
internal cross-platform job or a MAINID value was specified to list only internal
cross-platform jobs.

Action:
Perform one of the following actions:
■ Remove the fields listed to display information for the internal cross-platform jobs.
■ Change the job name to a CPU job name.
■ Remove the MAINID option.

SLIA-70

FOLLOWING FIELDS NOT ALLOWED FOR CPU JOB

Reason:
This message is issued when fields only valid for internal cross-platform jobs are
requested for a CPU job (for example, NODE, PARMLIB).

Action:
Perform one of the following actions:
■ Remove the fields listed to display information for the specific CPU job.
■ Change the job name to an internal cross-platform job name (XPJOB job).

SLIA-71

LIST=XPJOB NOT ALLOWED FOR CPU JOB

Reason:
This message is issued when option LIST=XPJOB is requested for a specific CPU job.
LIST=XPJOB requests to display internal cross-platform information and is valid only for
internal cross-platform jobs.

Action:
Perform one of the following actions:
■ Remove the LIST=XPJOB option to display information for the specific JCL-related
job.
■ Change the job name to an internal cross-platform job name (XPJOB job).

1420 Message Reference Guide

 SLFA Through SLI7

SLIA-71

LIST=STEPDD NOT ALLOWED FOR XPJOB JOB

Reason:
This message is issued when option LIST=STEPDD is requested for a specific internal
cross-platform job. LIST=STEPDD requests a display of STEP and DD information, and
internal cross-platform jobs do not have JCL associated with them.

Action:
Perform one of the following actions:
■ Remove the LIST=STEPDD option to display information for the specific internal
cross-platform job.
■ Change the job name to a CPU job name.

SLIA-72

FOLLOWING FIELDS NOT ALLOWED WITH NODE, AGENT, or PARMLIB

Reason:
This message is issued when internal cross-platform fields NODE, AGENT, or PARMLIB
are entered with fields related to CPU jobs.

Action:
Remove the fields listed or remove the NODE, AGENT, and/or PARMLIB fields to display
information for the jobs.

SLIA-73

CANNOT SPECIFY BOTH NODE= AND AGENT=

Reason:
This message is issued when both NODE and AGENT are specified on the same
command. These fields are mutually exclusive.

Action:
Remove either NODE or AGENT to display information for the jobs.

SLIB-nn

See the SLIx messages.

Chapter 7: SLFA - SPOR Messages 1421

SLFA Through SLI7

SLIC-nn

See the SLIx messages.

SLIC-nn

SYSTEM NAME xxxxxxxx NOT FOUND ****

Reason:
The application system ID specified by xxxxxxxx could not be found in the database.

Action:
Verify that the system ID requested is correct. If not, correct and resubmit the
command.

SLIC-16

****TP DATASET TABLE IS FULL****

Reason:
More than 500 temporary data sets exist within a job. LSYS can only handle up to 500
temporary data sets in a single job.

Action:
Contact your installation specialist for assistance.

SLIC-71

LIST=XPJOB NOT ALLOWED FOR CPU JOB

Reason:
This message is issued when option LIST=XPJOB is requested for a specific CPU job.
LIST=XPJOB requests to display internal cross-platform information and is valid only for
internal cross-platform jobs.

Action:
Perform one of the following actions:
■ Remove the LIST=XPJOB option to display information for the specific JCL-related
job.
■ Change the job name to an internal cross-platform job name (XPJOB job).

1422 Message Reference Guide

 SLFA Through SLI7

SLIC-71

LIST=DEP NOT ALLOWED FOR XPJOB JOB

Reason:
This message is issued when option LIST=DEP is requested for a specific internal
cross-platform job. LIST=DEP requests a display of STEP and data set dependencies and
internal cross-platform jobs do not have JCL associated with them.

Action:
Perform one of the following actions:
■ Remove the LIST=DEP option to display information for the specific internal
cross-platform job.
■ Change the job name to a CPU job name.

SLID-nn

See the SLIx messages.

SLIE-nn

See the SLIx messages.

SLIE-14

*** OUT OF PAGING SPACE, TRUNCATED ***

Reason:
The data to be listed creates more than 255 online pages of output. The online limit is
255 and this message indicates that the rest of the data is not listed.

Action:
Perform the following actions:
■ Use the Batch Terminal Interface if all of the data needs to be listed.
■ Modify the command to produce less output.

Chapter 7: SLFA - SPOR Messages 1423

SLFA Through SLI7

SLIE-15

SGETPDS ERROR - text

Reason:
An error occurred while processing the LJCL, LLIB, or LPDS command. The error is
detailed by text. See message SM50-14 for possible values for text.

Action:
Perform the following actions:
■ Correct the error indicated and try again.
■ See message SM50-14 for a specific text action match.

SLIE-16

EOD ON FIRST READ FOR PDS

Reason:
The JCL member entry in the database points to a null PDS.

Action:
Verify the JCL data set identification and correct if necessary.

SLIE-17

JCL DATASET NOT FOUND FOR JCLID nnn

Reason:
The JCL data set indicated in the job's database entry is not defined with a JCL statement
in the product's initialization file.

Action:
Change the JCLID in the database entry if it is incorrect. Otherwise, it is necessary to add
the appropriate JCL statement to the initialization file.

If the JCL for the job is contained in a CA Librarian or CA Panvalet for z/OS file, do the
following:
■ Try LLIB command for a more detailed error message.
■ Try a Fetch from the DB.7 (JCL) panel, for a more detailed error message.

1424 Message Reference Guide

 SLFA Through SLI7

SLIE-18

XPJOB jobname HAS NO PARMLIB DATA

Reason:
You did not specify the PDS library containing execution data to associate with the
XPJOB jobname.

Action:
None.

SLIF-nn

See the SLIx messages.

SLIF-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input request has completed successfully.

Action:
None.

SLIF-30

OUTPUT TRUNCATED

Reason:
The generated output contained more than 254 pages.

Action:
Use keyword selection criteria with the command to reduce the number of records
selected.

Chapter 7: SLFA - SPOR Messages 1425

SLFA Through SLI7

SLIF-33

ERROR OCCURRED IN JCL CONVERSION RTN - SASSPCEJ

Reason:
System error.

Action:
Contact your installation specialist for assistance.

The following SLIF-55 error messages are concerned with I/O and sort operations. In all
cases, the required action is to contact your installation specialist for assistance.

SLIF-55

SCRGET10 ERROR OCCURRED ON SCRATCH FILE READ.

Reason:
An I/O error.

Action:
Contact your installation specialist for assistance.

SLIF-55

SCRGET20 ERROR OCCURRED ON SCRATCH FILE READ.

Reason:
An I/O error.

Action:
Contact your installation specialist for assistance.

SLIF-55

SCRPUT25 ERROR OCCURRED ON SCRATCH FILE WRITE.

Reason:
An I/O error occurred.

Action:
Contact your installation specialist for assistance.

1426 Message Reference Guide

 SLFA Through SLI7

SLIF-55

SCRPUT30 ERROR OCCURRED ON SCRATCH FILE WRITE.

Reason:
An I/O error occurred.

Action:
Contact your installation specialist for assistance.

SLIF-55

SCRGET40 ERROR OCCURRED ON SCRATCH FILE READ.

Reason:
An I/O error occurred.

Action:
Contact your installation specialist for assistance.

SLIF-55

SCRGET50 ERROR OCCURRED ON SCRATCH FILE READ.

Reason:
An I/O error occurred.

Action:
Contact your installation specialist for assistance.

SLIF-55

SORT-55 ERROR OCCURRED DURING SORT.

Reason:
A sort error occurred.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1427

SLFA Through SLI7

SLIF-65

ERROR RETURN FROM SASSDWSP, RC=nn

Reason:
A problem has occurred calling the routine to translate a cross-platform AJB from
EBCIDC to ASCII. nn is the return code.

Action:
For assistance, contact CA Support at ca.com/support.

SLIG-nn

See the SLIx messages.

SLIG-16

SYS= INVALID WITH SPECIFIC JOB= REQUEST

Reason:
The SYS= parameter is not valid when the JOB= parameter does not refer to a generic
job name.

Action:
Remove the SYS= parameter and issue the command again.

SLIH-nn

See the SLIx messages.

SLIJ-nn

See the SLIx messages.

SLIL-48

CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE

Reason:
A FLOWL command was issued but the CPM feature is not active.

Action:
Code CPM=YES on the OPTIONS statement in the initialization file if you want to use the
CPM feature.

1428 Message Reference Guide

 SLFA Through SLI7

SLIL-49

NO FLOW RECORDS CHAINED

Reason:
A FLOWL command was issued but no active CPM flow records exist.

Action:
None.

SLIL-50

NO FLOW RECORDS SELECTED

Reason:
A FLOWL command was issued but no active CPM flow records matched the specified
selection criteria.

Action:
Perform the following actions:
■ Check the spelling of the flow name argument.
■ Reissue the command.

SLIL-53

INVALID VALUE FOR xxxxxxx

Reason:
An invalid value was specified for the keyword xxxxxxxx.

Action:
Perform the following actions:
■ Correct the value.
■ Reissue the command.

Chapter 7: SLFA - SPOR Messages 1429

SLFA Through SLI7

SLIL-54

FLOW RECORDS ARE NOT USED WITH OPTION CPM=JFM

Reason:
JFM=YES and CPM=JFM are specified on the initialization file OPTIONS statement. This
interface does not create FLOW records. FLOWL and FLOWD commands are not
supported.

Action:
Use the CPM ISPF interface or CPM DISPLAY command to view flow status.

Note: For more information, see the Interface Reference Guide and the CA Critical Path
Monitor User Guide.

SLIM-nn

See the SLIx messages.

SLIN-14

*** OUT OF PAGING SPACE, TRUNCATED ***

Reason:
See the explanation for SLIE-14.

Action:
See the action recommended for SLIE-14.

SLIN-15

SGETPDS ERROR - text

Reason:
See the explanation for SLIE-15.

Action:
See the action recommended for SLIE-15.

1430 Message Reference Guide

 SLFA Through SLI7

SLIN-16

EOD ON FIRST READ FOR PDS

Reason:
See the explanation for SLIE-16.

Action:
See the action recommended for SLIE-16.

SLIN-17

JCL DATA SET NOT FOUND FOR JCLID nnn

Reason:
See the explanation for SLIE-17.

Action:
See the action recommended for SLIE-17.

SLIN-21

SLOAD FAILED FOR SASSJCKI

Reason:
Unable to access the CA Workload Automation SE CA JCLCheck Workload Automation
interface module. The LIST=ONLY option will be used.

Action:
Perform the following actions:
■ Make sure SASSJCKI is in a library accessible from CA Workload Automation SE.
■ Issue the /DISPLAY,A=SASSJCKI command to ensure that an entry is in the
application directory for the module.

Chapter 7: SLFA - SPOR Messages 1431

SLFA Through SLI7

SLIN-22

INTERFACE INTERNAL ERROR

Reason:
A severe error occurred in LJCK processing. A subtask abend may have been produced.

Action:
Check for any prior messages indicating abnormal termination, collect all output from
the failing command including any dumps that may have been produced and contact
your installation specialist for assistance.

Note: If the display indicates a DRIVER ALLOC ERROR, ensure that all CA-Driver
procedure libraries associated with this JCL library are accessible to CA Workload
Automation SE.

SLIN-23

JJ01 DETECTED ERROR ON # CARD

Reason:
An attempt to evaluate scheduled overrides (for example, #JI/#JO statements) failed.
Probably a syntax error.

Action:
Perform the following actions:
■ Check the JCL for any invalid # statements.
■ Correct the JCL.
■ Try again.

SLIN-24

INVALID JCLLIB VALUE

Reason:
The value specified on the JCLLIB keyword is invalid. The value must conform to the
syntax described for the INDEX keyword on the JCL statement in the product's
initialization file. The parameter must either be 1-3 numeric characters specifying a
value between 0 and 255 or it must begin with an ampersand and be followed by from
1-15 alphanumeric characters.

Action:
None.

1432 Message Reference Guide

 SLFA Through SLI7

SLIN-25

CONFLICT IN JOB AND MEM

Reason:
Both JOB and MEM keywords were specified on the LJCK command. These keywords are
mutually exclusive.

Action:
Determine which keyword is appropriate for the command and reenter.

SLIN-26

STORAGE OBTAIN FAILED FOR WORKAREA

Reason:
A STORAGE OBTAIN for a work area for an internal cross-platform or agent job has
failed. The command terminates.

Action:
Retry the command. If the problem persists, contact your installation specialist for
assistance.

SLIN-27

VRM READ FAILED RC=nn, KEY=kkkkkkkkkk

Reason:
A read of the VRM file to obtain information related to processing an internal
cross-platform job (XPJOB job) has failed. nn is the return code. kkkkkkkkkk is the record
key value.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1433

SLFA Through SLI7

SLIN-28

AGENT INTERFACE NOT ACTIVE OR NOT INITIALIZED

Reason:
A job check has been requested for an agent job. Either the agent interface has not
been activated by the XPDEF,AGENTJOB=YES initialization statement or the initialization
has failed.

Action:
Add the AGENTJOB=YES keyword to the XPDEF initialization statement to activate the
agent interface. If already activated, check CA Workload Automation SE start up
messages for agent interface-related errors. If the problem persists, contact your
installation specialist for assistance.

SLIN-29

LIST=DEBUG IS ONLY VALID FOR AGENT JOBS

Reason:
Option LIST=DEBUG was specified for a job that is not an agent job.

Action:
Correct the command and reenter.

SLIN-30

OUTPUT TRUNCATED

Reason:
The LJCK command is generating more than 254 pages of output.

Action:
Use a BTI or CAICCI terminal with the LJCK command to get all the output.

1434 Message Reference Guide

 SLFA Through SLI7

SLIN-31

CONFLICT in JOB and JOBL

Reason:
The LJCK command was entered with both the JOB and JOBL parameters specified.

Action:
Reissue the command using either JOB or JOBL, not both.

SLIN-32

CONFLICT in JOBL and MEM

Reason:
The LJCK command was entered with both the JOBL and MEM parameters specified.

Action:
Reissue the command using either JOBL or MEM, not both.

SLIP-01

SQGET-DS QUE HDR. EC1=65 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code. If xxxxxxxx=00000001, a job
has probably changed queues during the processing of the LQ command being done.

Action:
Reenter the command. If the error persists contact your installation specialist for
assistance.

SLIP-02

SQGET-DS QUE HDR. EC1=66 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1435

SLFA Through SLI7

SLIP-04

xxxxxxxx PARAMETER IS NOT YET AVAILABLE

Reason:
Keyword xxxxxxxx is not valid for this command.

Action:
Perform the following actions:
■ Omit the keyword.
■ Resubmit the command.

SLIP-08

SQG-NHDR JOBNAME REQUIRED FOR Q=PRN/*

Reason:
A job name or a job name mask is required when Q=PRN or Q=* is specified.

Action:
Reenter with correct values.

SLIP-13

SQG-FRQM QUE RQMT. EC1=71 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-14

SQG-NRQM QUE RQMT. EC1=72 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

1436 Message Reference Guide

 SLFA Through SLI7

SLIP-21

SQG-NRQM QUE RQMT. EC=79 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-29

SQG-FJCL QUE JCL. EC1=81 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-30

SQG-NJCL QUE JCL. EC1=82 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-33

SQG-NJCL ERROR OCCURRED IN JCL CONVERSION RTN - SASSPCEJ

Reason:
A processing error occurred.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1437

SLFA Through SLI7

SLIP-34

SORT-xx ERROR OCCURRED DURING SORT.

Reason:
Sort error indicated by xx. Where xx can be one of the following:
■ 04 - I/O error
■ 08 - Segment length error
■ 12 - Work space error

Action:
Contact your installation specialist for assistance.

SLIP-66

LQ-REDRV QUEUE NUMBER MUST BE 2, 3, or 4

Reason:
An error was detected with the contents of the indicated field. This error has occurred
as a result of a CA 7 API call.

Action:
Perform the following actions:
■ Capture the SCHSRVR task output that is associated with this request.
■ For assistance, contact CA Support at http://ca.com/support.

SLIP-67

LQ-REDRV QUEUE DISPLACEMENT DID NOT PASS VALIDATION TESTS IN SASSSLIP

Reason:
The value passed in the Queue Displacement keyword was not a valid starting search
displacement. This error occurred as a result of a CA 7 API call.

Action:
Perform the following actions:
■ Capture the SCHSRVR task output that is associated with this request
■ For assistance, contact CA Support at http://ca.com/support.

1438 Message Reference Guide

 SLFA Through SLI7

SLIP-81

SCRGET-F SCR. EC1=51 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-82

SCRGET SCR. EC1=52 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIP-85

SCRPUT SCR. EC1=55 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Check the DAIO statement in the initialization file if xx=00. The SCRTRK/SWFTRK
parameter may need to be increased.

SLIP-97

SQG-FHDR QUE HDR. EC1=61 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1439

SLFA Through SLI7

SLIP-98

SQG-NHDR QUE HDR. EC1=62 EC2=xxxxxxxx

Reason:
A processing error occurred. xxxxxxxx is the return code.

Action:
Contact your installation specialist for assistance.

SLIR-02

xxxxxxxx FAILED FORMAT BLOCK EDIT.

Reason:
An error was found by the format routine for the keyword specified by xxxxxxxx.

Action:
Correct and resubmit the command.

SLIR-03

xxxxxxxx DATA SUBMITTED IS TOO LONG

Reason:
Keyword xxxxxxxx is not valid.

Action:
Correct and resubmit the command.

SLIR-04

xxxxxxxx PARAMETER IS NOT YET AVAILABLE

Reason:
Keyword xxxxxxxx is not valid.

Action:
Correct the value or omit the keyword and resubmit the command.

1440 Message Reference Guide

 SLFA Through SLI7

SLIR-05

xxxxxxxx DATA VALUE SHOULD NOT BE USED

Reason:
Keyword xxxxxxxx is not valid.

Action:
Correct the value or omit the keyword and resubmit the command.

SLIR-06

xxxxxxxx DATA VALUE IS NOT VALID

Reason:
Keyword xxxxxxxx is not valid.

Action:
Correct the value or omit the keyword and resubmit the command.

SLIR-07

xxxxxxxx IS A REQUIRED PARAMETER

Reason:
Keyword xxxxxxxx is required but was omitted from the input request.

Action:
Supply the missing keyword (with an appropriate value) and resubmit the command.

SLIR-32

xxxxxxxx SEGMENT STATUS CONTAINS AN INVALID VALUE

Reason:
A program change caused an invalid segment status to be detected by the SASSSLIR
module, xxxxxxxx is the keyword.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1441

SLFA Through SLI7

SLIR-49

xxxxxxxx INVALID WITH THIS FUNCTION

Reason:
Keyword xxxxxxxx is a valid keyword, but it cannot be used with the current command.

Action:
Perform the following actions:
■ Determine if the command or the keyword is in error.
■ Correct the error and resubmit the command.

SLIR-50

xxxxxxxx ERROR. OUTAGE= and SPAN= ARE MUTUALLY EXCLUSIVE.

Reason:
Keyword xxxxxxxx is a valid keyword, but the OUTAGE and SPAN keywords cannot both
be used in the same command.

Action:
Perform the following actions:
■ Specify either OUTAGE= or SPAN=.
■ Resubmit the command.

SLIR-51

xxxxxxxx START DATE OR DURATION IS REQUIRED.

Reason:
Keyword xxxxxxxx has a valid format, however, the first operand is omitted (start date,
or, duration). This parameter is required.

Action:
Specify either the start date, or a duration as the first parameter of the SPAN= or
OUTAGE= keyword and resubmit the command.

1442 Message Reference Guide

 SLFA Through SLI7

SLIR-52

xxxxxxxx ERROR. BAD ELEMENT IS yyyyyyyy

Reason:
Keyword xxxxxxxx has an error in the sublist. Parameter yyyyyyyy is the sublist element
in error.

Possible values for yyyyyyyy are:

■ START DATE
■ START TIME
■ END DATE
■ END TIME

Action:
Correct the keyword sublist to provide valid data for the command being used and
resubmit the command.

SLIR-53

xxxxxxxx ERROR. IF DURATION, MUST BE ONLY VALUE.

Reason:
Keyword xxxxxxxx is either OUTAGE= or SPAN= and the parameter is specified as a
sublist. The first operand is specified as an absolute number rather than a Julian or
Gregorian Start Date.

Action:
Specify either the start date as the first parameter, or specify duration as the only
parameter and resubmit the command.

SLIR-54

xxxxxxxx ERROR. END DATE/TIME MUST BE GT START DATE/TIME.

Reason:
Keyword xxxxxxxx is either OUTAGE= or SPAN= and the parameter is specified as a
sublist of starting date/time (first two parameters) and ending date and time (second
two parameters). The ending date and time is equal to or less than the starting date and
time, which is a logical error.

Action:
Correct the dates and times in the sublist and resubmit the command.

Chapter 7: SLFA - SPOR Messages 1443

SLFA Through SLI7

SLIR-55

xxxxxxxx ERROR. RANGE EXCEEDS MAXIMUM.

Reason:
Keyword xxxxxxxx is either OUTAGE= or SPAN=. The difference between the starting
date and time and the ending date and time cannot be greater than one year.

Action:
Correct the dates and times in the sublist and resubmit the command. the command.

SLIR-56

xxxxxxxx ERROR. START DATE/TIME GT CURRENT DATE/TIME.

Reason:
Keyword xxxxxxxx is either OUTAGE= or SPAN=. The starting date and time specified on
the keyword is greater than the current date and time, which is a logical error.

Action:
Correct the dates and times in the sublist and resubmit the command.

SLIT-nn

See the SLIx messages.

SLIT-02

INVALID DATE CONVERT FIELD

Reason:
An error occurred in the date conversion.

Action:
Contact your installation specialist for assistance.

1444 Message Reference Guide

 SLFA Through SLI7

SLIT-03

INVALID MODULE CODE

Reason:
An invalid internal module code has been detected during the use of the LWLB function.

Action:
Contact your installation specialist for assistance.

SLIT-09

INVALID MOD=VALUE

Reason:
The MOD= value on the LWLB command does not start with UCC7R.

Action:
Correct the MOD= value and retry.

SLIU-nn

See the SLIx messages.

SLIW-01

NO RECORDS MATCHED ARFSET=&ARFSET

Reason:
The entire ARF database was searched. Either the ARF database contains no ARF Sets or
no ARF Sets were found that met the search criteria. Note that UID level security is
checked for each ARF Set Record. The terminal user must have UID security access to a
given ARF Set before that record can be displayed. &ARFSET is the ARFSET= value that
was used for the search.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1445

SLFA Through SLI7

SLIW-02

ARF IS NOT ACTIVE, ARF DB CANNOT BE ACCESSED

Reason:
The LARF command depends on the internal ARF control block structure to complete
normally. ARF is not active in this execution of CA Workload Automation SE.

Action:
Ensure the CA Workload Automation SE startup parameter input contains a
'RESTART,ARF=YES' or a 'RESTART, ARF=MAINT' control statement. If one was included,
some error occurred during startup that caused ARF to be disabled. Search the console
log for CA Workload Automation SE startup messages relating to ARF.

SLIW-03

ARF DB INIT FAILED - RC=&RC RS=&RR

Reason:
The LARF command was attempting to access the ARF database, but an error was
detected before the database was accessed. &RC is the return code and &RR is the
reason code.

Action:
Retry the command to verify that a temporary shortage of system resources was not the
problem.

SLIW-04

ARF DB BEGIN SEQ FAILED - RC=&RC RS=&RR

Reason:
The LARF command was attempting to orient on the ARF Sets within the ARF database,
but an error was detected during the access. &RC is the return code and &RR is the
reason code.

Action:
Retry the command to verify that a temporary shortage of system resources was not the
problem. Review the console log for VSAM-related error messages that CA Workload
Automation SE itself produces.

1446 Message Reference Guide

 SLFA Through SLI7

SLIW-05

ARF DB GET NEXT FAILED - RC=&RC RS=&RR

Reason:
The LARF command was reading through the ARF Sets within the ARF database when an
unexpected error was detected. &RC is the return code and &RR is the reason code.

Action:
Retry the command to verify that a temporary shortage of system resources was not the
problem. Review the console log for VSAM-related error messages that CA Workload
Automation SE itself produces.

SLIW-xx

ERROR WIP=&WIP RC=&RC RS=&RR, ARFDATA1 IS: &TEXT

Reason:
An unexpected internal error occurred. &WIP is the two-byte internal WIP code. &RC is
the current internal return code. &RR is the current internal reason code. &TEXT is the
current text area being manipulated.

Action:
Present this information to CA Support. For assistance, contact CA Support at
ca.com/support.

SLIX-04

*** NO MATCHING GLOBAL JCL VARIABLES FOUND ***

Reason:
No global JCL variables matched the selection criteria.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1447

SLFA Through SLI7

SLIX-13

*** INVALID VALUE FOR NAME KEYWORD ***

Reason:
The value entered for the NAME keyword was invalid. It may have had a preceding or
embedded blank, which is not permitted.

Action:
Either delete the NAME keyword or correct the value, and then reenter the LGVAR
command.

SLIX-14

*** OUT OF PAGING SPACE, TRUNCATED ***

Reason:
The data to be listed creates more than 255 online pages of output. The online limit is
255, and this message indicates that the rest of the data is not listed.

Action:
Perform one of the following actions:
■ Use the Batch Terminal Interface if all of the data needs to be listed.
■ Modify the command to produce less output.

SLIX-15

*** INVALID VALUE FOR LIST KEYWORD ***

Reason:
The value entered for the LIST keyword was invalid.

Action:
Either delete the LIST keyword or correct the value, and then reenter the LGVAR
command.

1448 Message Reference Guide

 SLFA Through SLI7

SLIY-01

NO QUEUE ELEMENTS FOUND FOR JOB=&JOB

Reason:
The entire ARF queue was searched. Either the ARF queue is empty or no ARF queue
elements were found that met the search criteria. Note that UID level security is
checked for each ARF queue element based on the UID associated with the ARF Set
(rather than the job). The terminal user must have UID security access to a given ARF
queue element before that element can be displayed. &JOB is the JOB= value that was
used for the search.

Action:
None.

SLIY-02

ARF IS NOT ACTIVE, ARF DB CANNOT BE ACCESSED

Reason:
The LARFQ command depends upon the internal ARF control block structure to
complete normally. ARF is not active in this execution of CA Workload Automation SE.

Action:
Ensure the CA Workload Automation SE startup parameter input contains a
'RESTART,ARF=YES' or a 'RESTART, ARF=MAINT' control statement. If one was included,
some error occurred during startup that caused ARF to be disabled. Search the console
log for CA Workload Automation SE startup messages relating to ARF.

SLIY-03

INVALID LIST OPTION - &LIST

Reason:
The LIST= option was specified on the LARFQ command. &LIST reflects the value that
was given on the command. This is not a valid choice. See the command descriptions for
the valid choices.

Action:
Perform the following actions:
■ Correct the LIST= specification.
■ Retry the command.

Chapter 7: SLFA - SPOR Messages 1449

SLFA Through SLI7

SLIY-04

INVALID JOB NAME/NBR GIVEN - &JOB

Reason:
The JOB= parameter was specified on the LARFQ command. &JOB reflects the value that
was given on the command. Either a specific CA 7 WA job number may be given here or
a job name (full or generic). The value given is not valid. See the command descriptions
for details.

Action:
Perform the following actions:
■ Correct the JOB= specification.
■ Retry the command.

SLIY-06

ERROR WIP=xx RC=yy RS=zz,

ERROR - TRY COMMAND AGAIN.

Reason:
An unexpected error occurred while processing a chain of data using the LARFQ
command.

Action:
Reenter the LARFQ command.

SLIY-xx

ERROR WIP=&WIP RC=&RC RS=&RR, ARFDATA1 IS: &TEXT

Reason:
An unexpected internal error occurred. &WIP is the two-byte internal WIP code. &RC is
the current internal return code. &RR is the current internal reason code. &TEXT is the
current text area being manipulated.

Action:
Present this information to CA Support. For assistance, contact CA Support at
ca.com/support.

1450 Message Reference Guide

 SLFA Through SLI7

SLIZ-05

PDS READ ERROR RC=&RC WIP=&WIP, MSG IS: &TEXT

Reason:
The internal command LVAR was issued with incomplete data. The LVAR command is
used within CA Workload Automation SE and should not be entered from a terminal or
batch interface.

Action:
Reenter the command with the G as in LGVAR if you were trying to use the LGVAR to list
global variables. If you receive this message from another interface, contact your
installation specialist for assistance.

SLI0-nn

See the SLIx messages.

SLI0-12

*xxxxxxxx* IS AN INVALID FUNCTION

Reason:
The function specified by xxxxxxxx is invalid.

Action:
Perform the following actions:
■ Correct the function identifier.
■ Resubmit the command.

SLI0-13

INPUT DATA IS NULL

Reason:
No input command was available.

Action:
Resubmit the command with input.

Chapter 7: SLFA - SPOR Messages 1451

SLFA Through SLI7

SLI0-14

INPUT DATA IS TOO SHORT

Reason:
A partial input command was received. Not enough data available to process the
request.

Action:
Perform the following actions:
■ Supply sufficient data to process the request.
■ Resubmit the command.

SLI0-15

INPUT DATA IS TOO LONG

Reason:
Extraneous data was found on the input command.

Action:
Correct and resubmit the command.

SLI0-16

INVALID KEYWORD OR DATA IN INPUT

Reason:
An unknown keyword or other invalid input was detected.

Action:
Correct and resubmit the command.

1452 Message Reference Guide

 SLFA Through SLI7

SLI0-17

INVALID DATA FOUND FOR THE FOLLOWING FIELDS.

xxxxxxxx xxxxxxxx xxxxxxxx

Reason:
The keyword or name of the data found to be invalid is specified by xxxxxxxx. Invalid
data can be:
■ Non-numeric data specified for a numeric parameter.
■ Nonalphabetic data specified for an alphabetic parameter.
■ Too much or too little data given for a parameter.
■ Invalid decimal point or sign (+/-) given for a parameter.

Action:
Correct and resubmit the command.

SLI2-64

CROSS PLATFORM INTERNAL JOB SUPPORT NOT ACTIVE

Reason:
This informational message is issued when the XPDEF initialization statement has the
parameter XSUBMIT=NO, indicating that the XPJOB environment should not be
initialized.

Action:
None if this is what you intended. If you want an XPJOB environment to be set up,
change the XPDEF initialization statement to have XSUBMIT=YES and the appropriate
XPDEF parameters, and then recycle CA Workload Automation SE.

SLI2-65

XPJOB NODE TABLE NOT LOADED OR INVALID

Reason:
This message is issued when the XPJOB node table cannot be found in storage.

Action:
Verify that CA Workload Automation SE successfully initialized the XPDEF environment.
If the problem persists, contact CA Support at ca.com/support for assistance.

Chapter 7: SLFA - SPOR Messages 1453

SLFA Through SLI7

SLI2-66

NO {NODE|AGENT} RECORDS SELECTED

Reason:
This message is issued when no records are selected for display because they do not
match the parameters specified on the LNODE or the LAGENT command.

Action:
Reenter the LNODE or the LAGENT command with new parameters or values.

SLI2-67

INVALID MACRO RETURN CODE

Reason:
This message is issued when a CA Workload Automation SE macro returns an
unexpected error return code.

Action:
Reenter the request. If the problem persists, contact CA Support at ca.com/support for
assistance.

SLI2-69

INVALID VALUE FOR keyword=kkkkkkkk

Reason:
This message is issued when an invalid value is entered for one of the keywords on an
LNODE command. The keyword is identified in the message as kkkkkkkk.

Action:
Perform one of the following actions:
■ Remove the fields listed to display information for the specific non cross-platform
job.
■ Change the job name to a cross-platform job name.

1454 Message Reference Guide

 SLFA Through SLI7

SLI2-75

AGENT INTERFACE NOT ACTIVE

Reason:
The LAGENT command cannot display any agent information because the interface from
CA Workload Automation SE to CA Integrated Agent Services (CA IAS) is not active.

Action:
Contact your installation specialist for assistance.

SLI2-76

NO AGENTS ARE CONFIGURED

Reason:
In the CA Integrated Agent Services (CA IAS) agent definition file, no agents are defined.
As a result, no agents are available to list.

Action:
Contact your installation specialist to find out why no agents are defined.

SLI5-57

XPJOB/AGENT SEGMENT NOT FOUND FOR JOB=jjjjjjjj

Reason:
The indicated job is missing its XPJOB or agent segment in the queue file. The command
terminates.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1455

SLFA Through SLI7

SLI7-01

*** INVALID VALUE FOR LIST KEYWORD ***

Reason:
The value entered for the LIST keyword was invalid.

Action:
Perform one of the following actions:
■ Delete the LIST keyword and value, and then reenter the LXCF command.
■ Correct the value, and then reenter the LXCF command.

SLI7-02

*** COULD NOT READ XCFCKPT DATA SET ***

Reason:
The XCF checkpoint data set, ddname XCFCKPT, could not be read. The data set may
have been busy, or something else may have prevented the read action.

Action:
Retry the command. If the message persists, contact your installation specialist for
assistance.

SLI7-03

*** CONTROL BLOCK xxxxxxxx NOT AVAILABLE ***

Reason:
The LXCF command attempted to read the specified control block, but it was not
available.

Action:
Contact your installation specialist for assistance.

1456 Message Reference Guide

 SMF0

SLI7-04

*** CA 7 IS NOT USING XCF ***

Reason:
The LXCF,LIST=SMF command was issued, attempting to display data from the XCF
checkpoint data set. CA Workload Automation SE uses XCF messaging to retrieve this
information and cannot do so because the use of XCF is turned off.

Action:
None.

SMF0
This section contains the SMF0 messages.

SMF0-12

JOB xxxxxxxx (nnnn) ACTIVE ON MAIN.

Reason:
An SMF type-20 (job initiation) record has been received by CA Workload Automation
SE, which indicates that the job is now active on the CPU. If nnnn=0000, the job was
resubmitted while active on MAIN.

Action:
None.

SMF0-13

LOCATE FAILED FOR DSN=x...x

JOB=xxxxxxxx,STEP=yyyyyyyy,DD=zzzzzzzz

Reason:
An SMF type-14/15/99 (data set) record has been received by CA Workload Automation
SE, but the data set is not found in the CA Workload Automation SE IDS. The jobname,
stepname and ddname that referenced the data set are shown as indicated.

Action:
None. This usually occurs only when a job is being loaded for the first time.

Chapter 7: SLFA - SPOR Messages 1457

SMF0

SMF0-14

BAD RECORD=x....x

Reason:
An invalid record type was found while processing CA Workload Automation SE SMF
records.

Action:
Contact your installation specialist for assistance.

SMF0-15

JOB xxxxxxxx (nnnn) HAS BEEN PURGED FROM HOST SYSTEM.

**********
**********
**********
JOB xxxxxxxx (nnnn) IN RDY 'Q' MAY HAVE A JCL ERROR.
CHECK THE JOB'S SYSOUT AND REQUEUE THE JOB IF NECESSARY.
**********
**********
**********

Reason:
An SMF type-26 record was received by CA Workload Automation SE for a job submitted
by CA Workload Automation SE, and the job name xxxxxxxx was found in the ready
queue. If the type-26 record is for the current run of this job, the job either had a JCL
syntax error or was possibly canceled in JES.

Action:
Requeue the job back to the request queue if the job needs to be restarted. The type-26
record could be for a previous run of this job (for example, yesterday's run), and it has
just finished printing and is now going through JES purge. In this case this message can
be ignored and the condition will clear itself when the SMF Job Initiation record is
received for the job.

Many of these messages have been eliminated because CA Workload Automation SE

can check the JES job number. However, some cases exist where the JES job number is
not available while the job is in the CA Workload Automation SE RDYQ. (For example, if
a submit data set is used instead to the INTRDR.)

Note: A JES inquiry by job name shows if the current run of the job is still in the JES Q.

1458 Message Reference Guide

 SMF0

SMF0-16

JOB xxxxxxxx HAS BEEN PURGED FROM HOST SYSTEM

Reason:
An SMF type-26 record was received by CA Workload Automation SE for a job. This
informational message denotes that all printing is complete for a job.

Action:
None.

SMF0-17

TYPE 99 RECORD REJECTED FROM JOB = xxxxxxxx DSN=x...x

Reason:
A pseudo-SMF record (type-99) and an SMF type-15 record were received by CA
Workload Automation SE; the job creating them was a CA 7 WA job not marked as
maintenance. To avoid double posting, the record was dropped. The SCHID on the
type-99 record may have been different than the SCHID of the job creating the type-99.

Action:
Perform the following actions:
■ Check to ensure the correct jobs were triggered.
■ Update the CA Workload Automation SE database definition of the job to mark it as
maintenance.

SMF0-18

JOB xxxxxxxx (nnnn) HAS JCL ERROR ***RESTART REQUIRED***

Reason:
The specified job was terminated by a JCL error.

Action:
Analyze the JCL to determine the problem; JCL errors may occur because of an incorrect
override. To correct the JCL error, overrides must be corrected or added in the request
queue. Job Restart must then be used to resubmit the job.

Chapter 7: SLFA - SPOR Messages 1459

SMF0

SMF0-19

JOB xxxxxxxx(nnnn) ABNORMALLY TERMINATED,

***RESTART REQUIRED***
FAILING CODE=[Sccc|Ucccc]. LAST STEP EXECUTED= yyyyyyyy

Reason:
The specified job has abended. The last step executed was yyyyyyyy

Action:
Analyze the abend to determine what corrective action is necessary. Once the
appropriate steps have been taken, Job Restart must be used to resubmit the job.

SMF0-20

JOB xxxxxxxx (nnnn) COND CODE CHECK FAILED

***RESTART REQUIRED***
FAILING CODE=cccc. FAILING STEP=yyyyyyyy

Reason:
The specified job generated a condition code in one of its steps, and the code failed the
test defined in the CA Workload Automation SE database. The condition code that failed
the test is cccc. The last step that executed is yyyyyyyy.

Action:
Analyze the situation to determine corrective action. Once the appropriate steps have
been taken, Job Restart must be used to resubmit the job.

SMF0-21

JOB xxxxxxxx (nnnn) #SCC CHECK FAILED ***RESTART REQUIRED***

FAILING CODE=cccc. FAILING STEP={pppppppp.}yyyyyyyyy

Reason:
The specified job generated a condition code in one of its steps, and the code failed the
test defined by the #SCC statements in the job's JCL. The condition code that failed the
test is cccc. The step that failed is yyyyyyyy (and optional procstepname of pppppppp).

Action:
Analyze the situation to determine corrective action. Once the appropriate steps have
been taken, Job Restart must be used to resubmit the job.

1460 Message Reference Guide

 SMF0

SMF0-22

JOB xxxxxxxx (nnnn) #SCC CHECK FAILED ***RESTART REQUIRED***

STEP FLUSHED. STEPNAME={pppppppp.}yyyyyyyy.

Reason:
The specified job flushed one of its steps, and failed the test defined by the #SCC
statements in the job's JCL. The step that failed is yyyyyyyy (and optional procstepname
of pppppppp).

Action:
Analyze the situation to determine corrective action. Once the appropriate steps have
been taken, Job Restart must be used to resubmit the job.

SMF0-29

JOB aaaaaaaa (nnnn) NOT ADDED, BAD SASSEXTT MODULE.

Reason:
During the processing of an externally tracked job (aaaaaaaa), it was found that the
SASSEXTT module is not of a valid format.

Action:
Verify that the SASSEXTT module has been properly constructed using the $L2EXTT
macro.

SMF0-30

JOB jjjjjjjj (nnnn) NOT ADDED, DUPLICATE JOB IN RDY/ACT QUEUE

Reason:
The job indicated by jjjjjjjj is an externally submitted job and was not added to the active
queue because a job with the same name was already in the ready or active queue. CA
Workload Automation SE will not track this external job through job completion.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1461

SMF0

SMF0-31

JOB jjjjjjjj (nnnn) NOT ADDED TO ACTIVE QUEUE, SQADD ERROR

Reason:
The job indicated by jjjjjjjj is an externally submitted job and was not added to the active
queue because an error occurred while trying to add it.

Action:
Check the allocation of the active queue to make sure that adequate space is available.
The DMPQ/MOVQ process may be used to change queue allocations.

SMF0-32

JOB jjjjjjjj (nnnn) SECURITY SEGMENT NOT ADDED, SQADD ERROR

Reason:
An error occurred trying to build the security segment in the trailer queue for an
externally submitted job. A record was added to the active queue without a security
segment. The external job cannot propagate a security USERID to any triggered jobs.

Action:
Check the allocation of the trailer queue to make sure adequate space is available. The
DMPQ/MOVQ process may be used to change queue allocations.

SMF0-33

JOB jjjjjjjj (nnnn) REQUEUED (IPL) *** RESTART REQUIRED ***

Reason:
The specified job was active on a system that was IPLed, and the CA Workload
Automation SE AUTOREQ option is in effect. The job is automatically moved to the
REQUEST queue with a status of R-REQUE and must be manually restarted.

Action:
Analyze the situation to determine whether corrective corrective actions are necessary.
Once the appropriate steps have been taken, Job Restart must be used to resubmit the
job.

1462 Message Reference Guide

 SMXx

SMF0-34

AUTO-REQUEUE FEATURE INACTIVE - IPL RECORDS IGNORED.

Reason:
An IPL of the system within the CA Workload Automation SE complex was detected, and
the AUTOREQ option is not in effect. Any jobs active on systems at the point of an IPL
will be left in the active queue. Jobs left in the active queue following a system failure
such as this must be manually requeued to the request queue (see the REQUEUE
command). This message is displayed only once.

Action:
All jobs left stranded in the active queue following the system failure must be manually
requeued to the request queue (see the REQUEUE command).

To activate the Auto-Requeue feature, see the AUTOREQ keyword in the OPTIONS
initialization statement in the Systems Programming Guide.

SMXx
This section contains the SMXx messages.

SMX1-00

Enter function, transfer or enter a command on the top line

Reason:
This message is an XNODE command informational message.

Action:
Enter a function, a command, or a transfer panel ID.

SMX1-01

Successful function function

Reason:
This is an informational message indicating the success of function function.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1463

SMXx

SMX1-02

Invalid or omitted fieldname data

Reason:
The field indicated by fieldname is invalid (alphabetic instead of numeric or conversely)
or was omitted when it is required.

Action:
Correct the field and try the function again.

SMX1-03

Existing entry found; function not performed

Reason:
Because a matching node name was already defined, the function could not be
performed.

Action:
Try to list the requested node. If the node exists, you can update the definition instead
of adding it.

SMX1-04

Node entry not found

Reason:
An update or delete function was attempted, but the node does not currently exist.

Action:
Try the add function if an update was attempted. If the function was to delete a node,
no action is needed since the node does not exist.

SMX1-05

Invalid function

Reason:
An invalid function request made or not recognized by CA Workload Automation SE.

Action:
Ensure the correct spelling was entered, or that the command is truly a CA Workload
Automation SE command.

1464 Message Reference Guide

 SMXx

SMX1-06

Node table problems

Reason:
When trying to manipulate a node, the command detected problems with the
in-storage node table.

Note: This could indicate system problems.

Action:
Try the command again, or try the LNODE command. If the problem persists, contact
your installation specialist for assistance.

SMX1-07

No XPJOB environment exists; XNODE cmd disabled

Reason:
The XNODE command was entered, but this execution of CA Workload Automation SE
does not support the XPJOB environment, and thus the XNODE command.

Action:
Verify with your installation that the XPJOB environment should be set up. This requires
an initialization file change and a recycle of CA Workload Automation SE to activate.

SMX1-08

XPJOB Table not present; unable to process command

Reason:
The main control block that defines the XPJOB environment was not found in the CA
Workload Automation SE system.

Note: If the XPJOB environment has been established through specification of

initialization file options, this could indicate internal system problems.

Action:
Try another command such as LNODE. If the problem persists, contact your installation
specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1465

SMXx

SMX1-09

You are not authorized to perform function

Reason:
Security has denied access to the function you are entering. Depending on the security
settings for this execution of CA Workload Automation SE, you may not have the ability
to enter the XNODE command or the related function.

Action:
Verify with your installation if you should have access to the XNODE command and
related function. If so, modify the security rules to permit the function to be entered.

SMX1-10

Unrecognizable data in input

Reason:
CA Workload Automation SE does not recognize the data entered on the XNODE
command.

Action:
Retry the command ensuring that you specify valid fields. If the problem persists,
contact your installation specialist for assistance.

SMX1-11

Add of node entry failed (I/O)

Reason:
An I/O error occurred when trying to add this new node definition to the CA Workload
Automation SE database (the VRM file, specifically).

Action:
Ensure there is sufficient room on the VRM file, and that there are no errors for that file.
An IDCAMS PRINT operation (key begins with N) could be attempted to ensure the file
can be accessed through other means. If repeated errors occur, contact your installation
specialist for assistance.

1466 Message Reference Guide

 SMXx

SMX1-12

Reason:
A value was entered for alternate node #2 with no value detected for alternate node #1.

Note: You must specify the first alternate node before coding the second alternate
node.

Action:
Reenter the command, specifying an alternate node #1.

SMX1-14

Update of node entry failed (I/O)

Reason:
An I/O error occurred when trying to update the node definition to the CA Workload
Automation SE database (the VRM file, specifically).

Action:
Ensure there is sufficient room on the VRM file and that there are no errors for that file.
An IDCAMS PRINT operation (key begins with N) could be attempted to ensure the file
can be accessed through other means. If repeated errors occur, contact your installation
specialist for assistance.

SMX1-15

Invalid status for node detected

Reason:
When adding or updating a node definition, the status for the node is not valid. ONLINE,
OFFLINE, and STOP are the only valid statuses for a node.

Action:
Reenter the command supplying a valid status for the node.

Chapter 7: SLFA - SPOR Messages 1467

SMXx

SMX1-17

Node name field required for function

Reason:
With the XNODE command, the NODE is always a required field, but no data was
entered.

Action:
Ensure the NODE field is completed for the requested function.

SMX1-18

Time zone must be between -12 and +12

Reason:
When assigning a time zone for the node, the valid range for the time zone is from -12
to +12, relative to the Universal Coordinated Time (UCT).

Action:
Ensure the value specified for the time zone ranges from -12 to +12.

SMX1-20

Get for update failed for this node; aborted function

Reason:
The function specified by function was aborted because the node record could not be
retrieved from the CA Workload Automation SE database.

Action:
Retry the function. If the same message occurs, ensure that the CA Workload
Automation SE database, specifically the VRM file, is available to CA Workload
Automation SE. If the error occurs again, other problems with CA Workload Automation
SE could be occurring. If the problem persists, contact your installation specialist for
assistance.

1468 Message Reference Guide

 SMXx

SMX1-21

Delete of node record failed

Reason:
The delete function of a node was requested, but the node record could not be deleted
from the CA Workload Automation SE database (the VRM file).

Action:
Perform the following actions:
■ Ensure there are no CA Workload Automation SE database problems.
■ Try the function again.
■ Contact your installation specialist for assistance if the problem persists.

SMX1-22

Retrieved record key does not match node

Reason:
For the requested the node, the node record retrieved from the CA Workload
Automation SE database does not match what was entered.

Action:
Perform the following actions:
■ Ensure valid node name was coded.
■ Retry the function.
■ Contact your installation specialist for assistance if the problem persists.

SMX1-23

Table update lock failure; try request again

Reason:
When trying to perform a function that updates the node table, exclusive control could
not be granted at the time of the command.

Action:
Try the command again. If the same message comes out again, wait a few minutes and
then retry. The node table is locked when adds, deletes, or updates occur to ensure the
integrity of the table.

Chapter 7: SLFA - SPOR Messages 1469

SMXx

SMX1-24

This is a {Permanent/Temporary} Node

Reason:
This informational message indicates whether the node is permanent (exists on the CA
Workload Automation SE database and will be defined at each initialization of CA
Workload Automation SE) or temporary (added dynamically by CA Workload
Automation SE when it routed a job for execution to this node).

Action:
None. If the node should be permanent, enter the ADD or UPDATE function so that the
node is defined to the CA Workload Automation SE database.

SMX1-25

Invalid Data entered for Description

Reason:
Data entered for description must be alphanumeric, national characters (@,$,#)
underscore (_) or +-,=.()'/&.

Action:
Reenter description using allowable characters.

SMX2-00

Enter function, transfer or enter a command on the top line

Reason:
This is an informational message.

Action:
Self-explanatory.

SMX2-01

Add Successful

Reason:
This is an informational message.

Action:
None.

1470 Message Reference Guide

 SMXx

SMX2-02

Delete Successful

Reason:
This is an informational message.

Action:
None.

SMX2-03

List Successful

Reason:
This is an informational message.

Action:
None.

SMX2-04

Update Successful

Reason:
This is an informational message.

Action:
None.

SMX2-05

Invalid Owner Data

Reason:
Owner data contains embedded spaces.

Action:
Reenter owner information without embedded spaces.

Chapter 7: SLFA - SPOR Messages 1471

SMXx

SMX2-09

You are not authorized to perform function

Reason:
You must have certain privileges to use the CA Workload Automation SE XPSWD
function.

Action:
Contact your installation specialist for assistance if you need access to the XPSWD
function.

SMX2-16

No XPJOB environment exists, XPSWD disabled

Reason:
CA Workload Automation SE has been started with the cross-platform job feature
disabled. The XPSWD function is a subcomponent of the cross-platform job feature.

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Enable the cross-platform job feature at the site. Contact your installation specialist for
assistance.

SMX2-17

Unrecognizable data in input

Reason:
An unrecognizable keyword, value, or both was input.

Action:
Reissue the command with the correct parameter data.

1472 Message Reference Guide

 SMXx

SMX2-18

Invalid function data

Reason:
An invalid function was entered.

Action:
Enter a valid function.

SMX2-19

Missing User Id data

Reason:
The user ID field was left blank. User ID is required when adding XPSWD owner or node
records.

Action:
Supply the missing user ID.

SMX2-21

I/O error when attempting to add record

Reason:
An I/O error occurred while attempting to add an XPSWD record to the database.

Action:
Contact your installation specialist for assistance.

SMX2-22

Password and reconfirm password do not match

Reason:
Password and reconfirm password must match or be null when attempting to add or
update a cross-platform password record.

Action:
Ensure both passwords match.

Chapter 7: SLFA - SPOR Messages 1473

SMXx

SMX2-23

XPJOB password record already exists for node/owner yyyyyyyy

Reason:
An attempt was made to add a node or owner password record for yyyyyyyy. The record
yyyyyyyy already exists.

Action:
Self-explanatory.

SMX2-24

I/O error when attempting to delete record

Reason:
An I/O error occurred while attempting to delete an XPSWD record from the database.

Action:
Contact your installation specialist for assistance.

SMX2-25

XPJOB password record not found for node/owner yyyyyyyy

Reason:
An attempt was made to update, delete, or list a password record for owner/node
yyyyyyyy. The record could not be found.

Action:
Self-explanatory.

SMX2-32

I/O error when attempting to update record

Reason:
An I/O error occurred while attempting to update an XPSWD record in the database.

Action:
Contact your installation specialist for assistance.

1474 Message Reference Guide

 SMXx

SMX2-33

Owner or node is required

Reason:
An attempt was made to add, update, delete, or list a password record without
supplying an owner or a node.

Action:
Supply an owner or a node.

SMX2-34

Enter either owner or node, not both

Reason:
An attempt was made to add, update, delete, or list a password record supplying both
owner and node information.

Action:
Enter either the owner value or node value, not both.

SMX2-35

Root User Id not allowed at site

Reason:
An attempt was made to add or update a record while supplying a User Id of 'root'. The
site's installation options are set up to prevent this.

Note: For more information about using the 'root' User ID, see the XPDEF initialization
statement in Systems Programming Guide.

Action:
Contact your installation specialist for assistance if this option is necessary.

Chapter 7: SLFA - SPOR Messages 1475

SMXx

SMX2-36

Not authorized to add/update information for owner xxxxxxxx

Reason:
An attempt was made to add or update information for owner password record
xxxxxxxx. The user does not have authority to update this record.

Action:
Contact your installation specialist for assistance.

SMX2-37

XPJOB table not present; unable to process command

Reason:
An attempt was made to add or update a node password record. The table containing
the basic node information could not be found.

Action:
Contact your installation specialist for assistance.

SMX2-38

Node entry not found, use XNODE command to add permanent entry

Reason:
An attempt was made to add a node password record. A corresponding node record
could not be found. A node record must exist before a node password record can be
added.

Action:
Perform the following actions:
■ Use the XNODE command to add a node record to the database.
■ Use the XPSWD command to add a corresponding node password record.

1476 Message Reference Guide

 SMXx

SMX2-39

Temporary node found, permanent entry required

Reason:
An attempt was made to add a node password record. Node password records can only
be added if a permanent node record exists.

Action:
Perform the following actions:
■ Use the XNODE command to add a permanent node record to the database.
■ Use the XPSWD command to add a corresponding node password record.

SMX3-00

Enter function, transfer or enter a command on the top line

Reason:
This is an informational message.

Action:
Self-explanatory.

SMX3-01

Password added successfully

Reason:
This is an informational message.

Action:
None.

SMX3-02

Password deleted successfully

Reason:
This is an informational message.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1477

SMXx

SMX3-03

Password found

Reason:
This is an informational message.

Action:
None.

SMX3-04

Password updated successfully

Reason:
This is an informational message.

Action:
None.

SMX3-05

Invalid xxxxxxxx Data

Reason:
Field xxxxxxxx contains invalid data.

Action:
Reenter indicated field without invalid data.

SMX3-06

Wildcard characters not allowed for field xxxxxxxx

Reason:
Field xxxxxxxx contains * characters, ? characters, or both.

Action:
Reenter indicated field without wildcard charaters.

1478 Message Reference Guide

 SMXx

SMX3-07

IAS not active or not initialized

Reason:
CA Integrated Agent Services (CA IAS) is not supported or has not initialized correctly.

Action:
Check CA Workload Automation SE start-up messages for IAS-related errors.

SMX3-09

You are not authorized to perform function

Reason:
You must have certain privileges to use the CA Workload Automation SE AGPSWD
function.

Action:
Contact your installation specialist for assistance if you need access to the AGPSWD
function.

SMX3-16

No Agent Job environment exists, AGPSWD disabled

Reason:
CA Workload Automation SE has been started with the agent job feature disabled. The
AGPSWD function is a subcomponent of the agent job feature.

Action:
Enable the agent job feature at the site by coding AGENTJOB=YES on the XPDEF
initialization file statement. Contact your installation specialist for assistance.

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Chapter 7: SLFA - SPOR Messages 1479

SMXx

SMX3-17

Unrecognizable data in input

Reason:
An unrecognizable keyword, value, or both was input.

Action:
Reissue the command with the correct parameter data.

SMX3-18

Invalid function data

Reason:
An invalid function was entered.

Action:
Enter a valid function.

SMX3-19

Missing User Id data

Reason:
The user ID field was left blank. A user ID is required when adding AGPSWD password
records.

Action:
Supply the missing user ID.

SMX3-22

Password and verify password do not match

Reason:
The New Password and Verify Password fields must match when adding or updating
password records.

Action:
Renter both fields so that they match.

1480 Message Reference Guide

 SMXx

SMX3-32

Timeout occurred, contact your CA 7 specialist

Reason:
A timeout occurred waiting for CA Integrated Agent Services (CA IAS) to respond to a
password maintenance request.

Action:
Contact your installation specialist for assistance.

SMX3-35

Password already exists

Reason:
CA Integrated Agent Services (CA IAS) tried to add a password record to the database,
but the key already exists.

Action:
Change Add to Update or enter new key fields.

SMX3-36

DIV file is full

Reason:
CA Integrated Agent Services (CA IAS) tried to add a password record to the database,
but the database is full.

Action:
Contact your installation specialist for assistance.

SMX3-39

Password not found

Reason:
CA Integrated Agent Services (CA IAS) tried to update, delete, or list a password record,
but the record was not found.

Action:
Verify that you entered the key information correctly.

Chapter 7: SLFA - SPOR Messages 1481

SMxx

SMX3-40

Old password doesn't match

Reason:
CA Integrated Agent Services (CA IAS) tried to update a password record on the
database, but the old password provided does not match the current password on the
database.

Action:
Verify that you entered the old password correctly.

SMX3-43

Too many matches for answer area

Reason:
CA Integrated Agent Services (CA IAS) encountered an internal error processing a LIST
request.

Action:
Contact your installation specialist for assistance.

SMX3-47

IASMPW internal error, Return Code=xxxx, Reason Code=yyyy

Reason:
CA Integrated Agent Services (CA IAS) encountered an internal error. The message lists
the return and reason codes.

Action:
Contact your installation specialist for assistance.

SMxx
This section contains the SMxx messages.

1482 Message Reference Guide

 SMxx

SM10-00

SPECIFY OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used to request selection of a prose type. If an error is made in the
selection, this message will be reissued.

Action:
Self-explanatory.

SM11-00

ENTER INPUT DATA

Reason:
This prompt requests input data.

Action:
Self-explanatory.

SM11-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function was successful.

Action:
None.

SM11-00

xxxxxxxx FUNCTION SUCCESSFUL FOR PPnnnnnn

Reason:
The requested function was successful. The prose member affected is identified.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1483

SMxx

SM11-01

xx INVALID MACRO RETURN CODE nnnn.

Reason:
If xx=P1 and nnnn=0002, error can occur when saving a new member to the Dataset
data set. Indicates an existing DSNBR was assigned to the new member resulting in two
members with the same DSNBR. This can occur if the Dataset data set is reinitialized.
The data set should not be reinitialized once it is in use, even when moving,
compressing, or expanding it. If xx=05, the data set is out of space and it is necessary to
compress the data set.

Action:
Contact your installation specialist. If it is determined that the Dataset data set was
reinitialized and if a backup of the entire database (Job, Dataset and Index data sets) is
available, do a restore.

SM11-02

xxxxxxxx NOT FOUND

Reason:
The identified member was not found.

Action:
Check for correct input. If an error exists, correct and retry.

SM11-03

OUT OF SPACE ON DATA BASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up the database.
■ Reallocate the affected file.
■ Reload the database.

1484 Message Reference Guide

 SMxx

SM11-04

CONFLICT IN DSN AND DSNBR

Reason:
Both DSN and DSNBR were input, but these values are in conflict.

Action:
Correct or delete one specification (both are not required) and retry.

SM11-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
If the CA Workload Automation SE Index data set is an OS catalog, there are possible
restrictions on prose member names. If User Prose has been defined using the job name
as the User Prose name, then Job Prose cannot be defined. This restriction does not
apply when using a VSAM data set for the CA Workload Automation SE Index data set.

Action:
Correct the field in error and retry.

SM11-07

PROSE MEMBER ALREADY EXISTS

Reason:
A SAVE function was entered for an existing prose member.

Action:
If you want to change an existing prose member, use an REPL function.

SM11-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to alter or add prose for a job that is not accessible due to UID
security.

Action:
Contact your security administrator if you need to change an existing prose member or
to add a new one.

Chapter 7: SLFA - SPOR Messages 1485

SMxx

SM11-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM11-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

SM11-13

NO SAVE -- ACTIVE FILE EMPTY

Reason:
An attempt was made to SAVE or REPL a prose member, but the Active Area contains no
lines of text.

Action:
Perform the following actions:
■ Use the text editor to add lines of text to the Active Area.
■ Reissue the command.

1486 Message Reference Guide

 SMxx

SM2E-00

CHOOSE A FUNCTION OR ENTER A COMMAND ON THE TOP LINE

Reason:
Awaiting your choice of functions.

Action:
Perform the following actions:
■ Transfer to another menu or formatted input panel by entering the FUNCTION
value you want.
■ Position the cursor to the top line and enter a command.

SM2x-00

ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used to request input data online.

Action:
Self-explanatory.

SM2x-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data in batch.

Action:
Self-explanatory.

Chapter 7: SLFA - SPOR Messages 1487

SMxx

SM2x-00

xxxxxxxx SUCCESSFUL [nnn DATASET(S) DELETED]

[,DEFAULTJOB USED FOR DEFAULT VALUES]
[,RESIDUALS PURGED.]
[WARNING: SOME RESIDUAL ELEMENTS COULD NOT BE DELETED.]

Reason:
The requested function was successful. If the DD or PURGE function was entered, the
number of data sets deleted is denoted by nnn. DEFAULTJOB USED FOR DEFAULT
VALUES is appended, if an ADD function was performed and a job with the name
DEFAULTS was found in the database and was used to provide the default values for the
job being added.
If the PURGE function was entered, the text RESIDUALS PURGED is appended if all
elements connected to the job were successfully removed. If any of these residuals
could not be deleted, the warning SOME RESIDUALS COULD NOT BE DELETED is present
on the next line.

Action:
None.

SM2x-01

xx INVALID MACRO RETURN CODE nnnn

Reason:
An error has occurred in the processing of the Job data set. If xx=C2 and nnnn=0000, the
Job data set may be out of space. If xx=82 and nnnn=0000, the job member had an error
that may have left prose, data set, and index entries for this job even though the job and
any triggers have been deleted.

Action:
Delete the job from the CA Workload Automation SE database. When any of these
errors occur, it is recommended that commands TRIG, RQMT, and XREF be executed to
update the database and correct pointer errors; then run the Database Verification
program to check for stranded members. This may require backing up and reloading the
database with SASSBK00.

1488 Message Reference Guide

 SMxx

SM2x-02

JOB NOT FOUND

Reason:
The requested job was not found in the CA Workload Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

SM2x-03

OUT OF SPACE ON DATABASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up the database.
■ Reallocate the affected file.
■ Reload the database.

SM2x-05

INVALID OR OMITTED xxxxxxxx DATA [,REJECTED BY USER EXIT]

Reason:
The identified field contains invalid data or the SASSXX10 user exit has denied the
request. If the command is being done through a batch terminal, and the message reads
INVALID OR OMITTED FUNCTION DATA, it may be a security violation, rather than a
command error.

Action:
Check with your installation specialist to determine the security restrictions for the
batch terminal and operator. If the SASSXX10 user exit has rejected the request, check
with your installation specialist for information regarding why the rejection occurred.

Chapter 7: SLFA - SPOR Messages 1489

SMxx

SM2x-07

JOB ALREADY EXISTS

Reason:
An ADD function was entered, but the job already exists in the CA Workload Automation
SE database.

Action:
Use the UPD function to change existing job information if you want.

SM2x-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to access a job definition that is not accessible due to UID
security.

Action:
Contact your security administrator if you need to change an existing job or to add a
new one.

SM2x-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM2x-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

1490 Message Reference Guide

 SMxx

SM2x-12

USER NOT AUTHORIZED FOR OWNER ID

Reason:
An attempt was made to add or update the OWNER field for a job on the DB.1 (JOB)
panel. The operator was not authorized to submit for the USERID in the OWNER field.

Action:
If security access should be allowed, authorize the operator for the USERID being added
or updated in the Job Owner field.

SM2x-13

ERROR RETURN FROM USER EXIT (SASSXX10)

Reason:
The installation user exit SASSXX10 returned error condition to CA Workload
Automation SE for this job definition. The job definition is not saved or updated.

Action:
Contact your installation specialist to see why the user exit produces the error.

SM2x-14

CONFLICT IN JCLID AND JCLLIB FIELDS

Reason:
When defining a CPU job to the database, you cannot enter both JCLID and JCLLIB.

Action:
Enter either the JCLID (numeric value) or the JCLLIB (symbolic name) for the location of
the job's JCL.

Chapter 7: SLFA - SPOR Messages 1491

SMxx

SM2x-15

ARFSET NOT DEFINED

Reason:
An attempt was made to add or update the ARFSET field for a job on the DB.1 (JOB)
panel. The ARFSET specified is not defined to CA Workload Automation SE. Also, UID
security sometimes prevents you from displaying the ARFSET.

Action:
Perform one of the following actions:
■ Correct the ARFSET name.
■ Define the ARFSET before connecting a job to it.

SM2x-16

ARFIO ERROR R15=nn R0= R1=

Reason:
When trying to access the specified ARFSET in the ARF VSAM file, an I/O error occurred.

Action:
Verify the ARF VSAM file is not encountering other errors. If the file appears not to be
experiencing problems, note the message information, including the register values, and
contact CA Support at http://ca.com/support for assistance.

SM2x-17

ARFIO INIT FAILED

Reason:
Errors occurred when trying to initialize the environment to retrieve the specified
ARFSET in the ARF VSAM file.

Action:
Verify the ARF VSAM file is not encountering other errors. If the file appears not to be
experiencing problems, contact CA Support at http://ca.com/support for assistance.

1492 Message Reference Guide

 SMxx

SM2x-25

DEFAULT JOB DEFINITION NOT VALID FOR JOB TYPE

Reason:
Your have attempted to add a new job, and your site has defined a default job
definition. The default job definition does not match the type job you are defining. To
determine the exact cause of your problem:
■ Check the DBASE file initialization statement to identify your site's default job
definitions for regular jobs, XPJOBs, and AGJOBs.
■ List each job using the DB.1 panel. You should see the following results:
– List the regular default job definition, and you should remain on the DB.1
screen. If you do not, this job definition does not match the proper keyword on
the DBASE statement.
– List the XPJOB default job definition, and you should be redirected to the DB.10
screen. If you are not, this job definition does not match the proper keyword
on the DBASE statement.
– List the AGJOB default job definition, and you should be redirected to the
DB.11 screen. If you are not, this job definition does not match the proper
keyword on the DBASE statement.

Action:
Have your site CA Workload Automation SE administrator delete any incorrect default
job definitions and redefine them using the proper screen. You cannot add any jobs
having an incorrect default job until this is done.

SM20-20

UPDATE REQUESTED FOR yyyyy TYPE INVALID FROM THIS SCREEN

Reason:
This is an informational message indicating an update request for yyyyy (XPJOB or
Agent) job was attempted from the JOB (DB.1) panel.

Action:
Perform one of the following actions:
■ Enter the XPJOB (DB.10) panel to update the XPJOB definition.
■ Enter the AGJOB (DB.11) panel to update the agent job definition.

Chapter 7: SLFA - SPOR Messages 1493

SMxx

SM22-18

XP NODE FIELD IS REQUIRED

Reason:
When defining an XPJOB to the CA Workload Automation SE database, the XP NODE
field is always required.

Action:
Reenter the function specifying the destination node to which this job should be
directed.

SM22-20

Update requested for yyyy job type invalid from this panel

Reason:
This is an informational message indicating an update request for yyyyy (MVS or Agent)
job was attempted from the XPJOB (DB.10) panel.

Action:
Perform one of the following actions:
■ Enter the JOB or DB.1 panel to update the MVS job definition.
■ Enter the AGJOB (DB.11) panel to update the agent job definition.

SM22-21

First part of XP EXEC must be specified

Reason:
No data was specified in the first line of the XP EXEC section on the XPJOB/DB.10 panel,
but some value must be specified on the first line.

Note: If there are to be preceding blanks in the executable file name passed to the
destination node, enter the entire value in single quotes, which are removed by CA
Workload Automation SE when sending the data to the target destination.

Action:
Enter data on the first line of the XP EXEC section.

1494 Message Reference Guide

 SMxx

SM22-22

First part of XP EXEC must be specified before second part

Reason:
No data was specified in the first line of the XP EXEC section on the XPJOB/DB.10 panel,
but some value must be specified on the first line before coding data on the second line.

Note: If there are to be preceding blanks in the executable file name passed to the
destination node, enter the entire value in single quotes, which are removed by CA
Workload Automation SE when sending the data to the target destination.

Action:
Enter data on the first line of the XP EXEC section.

SM23-18

Agent Name field is required

Reason:
When defining an agent job to the CA Workload Automation SE database, the Agent
field is always required.

Reason:
Reenter the function specifying the agent to which this job should be directed.

SM23-20

Update requested for yyyyy job type invalid from this panel

Reason:
This is an informational message indicating an update request for yyyyy (MVS or XPJOB)
job was attempted from an Agent Job Definition panel.

Action:
Perform the following actions:
■ Enter the JOB (DB.1) panel to update the MVS job definition.
■ Enter the XPJOB (DB.10) panel to update the XPJOB job definition.

Chapter 7: SLFA - SPOR Messages 1495

SMxx

SM23-22

Agent Job Type is required

Reason:
When defining an agent job to the CA Workload Automation SE database, the Agent Job
Type field is always required.

Action:
Reenter the function specifying the agent job type to pass with the job to the agent.

Note: For more information about valid agent job types, see the Database Maintenance
Guide.

SM23-23

Agent Job Type is invalid

Reason:
When defining an agent job to the CA Workload Automation SE database, the agent job
type specified must be valid.

Action:
Reenter the function specifying a valid agent job type.

Note: For more information about valid agent job types, see the Interface Reference
Guide.

SM23-24

Cond-Code/RO must be zero for xxxxxxxx

Reason:
Certain agent job types (xxxxxxxx) do not use the Condition Code/Relational Operator
fields. In these situations, these fields should be set to 0.

Note: For more information about the agent job types that do not use the Condition
Code/Relational Operator fields, see the Database Maintenance Guide.

Action:
Reenter the function, setting the Cond-Code and RO fields to zero.

1496 Message Reference Guide

 SMxx

SM27-01

w JOB=xxxxxxxx yyyyyyy SUCCESSFULLY COMPLETED

Reason:
A CONVERT or RESTORE command has successfully completed. The where-in-program
code is indicated by w. The job is indicated by xxxxxxxx. The command (CONVERT or
RESTORE) is indicated by yyyyyyy. The command was successful.

Action:
None.

SM27-02

w JOB=xxxxxxxx YOU ARE NOT AUTHORIZED FOR THIS FUNCTION

Reason:
The user does not have the necessary security access to execute the CONVERT or
RESTORE command on the job specified. The where-in-program code is indicated by w.
The job is indicated by xxxxxxxx.

Action:
Contact your security administrator.

SM27-04

w JOB=xxxxxxxx ALREADY EXISTS RC = cc

Reason:
The backup job name that is requested on a CONVERT command exists in the CA
Workload Automation SE job database. The w indicates the where-in-program code. The
xxxxxxxx indicates the job. The cc indicates the return code. The command terminates.

Action:
Perform one of the following actions:
■ Remove the BACKUP option on the CONVERT command.
■ Specify a new job name for the backup job name.

If the problem persists, contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1497

SMxx

SM27-05

w JOB=xxxxxxxx NOT FOUND ON JOB DIR RC = cc

Reason:
A job is not found on the job database. The w indicates the where-in-program code. The
xxxxxxxx indicates the job. The cc indicates the return code. The command terminates.

Action:
Perform the following actions:
■ Verify that you have entered the correct job name.
■ Correct the job name.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

SM27-06

w JOB=xxxxxxxx INVALID JOBNAME RC = cc

Reason:
A job name entered on a CONVERT or RESTORE command is not valid. The
where-in-program code is indicated by w. The job is indicated by xxxxxxxx. The return
code is indicated by cc. The command terminates.

Action:
Perform the following actions:
■ Verify that you have entered the correct job name.
■ Correct the job name.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

1498 Message Reference Guide

 SMxx

SM27-07

w JOB=xxxxxxxx ERROR UPDATING JOB DIR RECORD RC = cc

Reason:
An error has occurred trying to update a record in the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. The command terminates. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

SM27-08

w JOB=xxxxxxxx NO SASJE RECORD FOUND RC = cc

Reason:
A job segment record is not found on the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

SM27-09

w JOB=xxxxxxxx INVALID SASJE RECORD TYPE FOUND RC = cc

Reason:
An invalid job segment record was found on the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. The command terminates.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1499

SMxx

SM27-10

w JOB=xxxxxxxx ERROR READING JOB DIR RECORD RC = cc

Reason:
An error has occurred trying to read a record in the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

SM27-11

w JOB=xxxxxxxx ERROR READING JOB MBR RECORD RC = cc

Reason:
An error has occurred trying to read a record in the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

SM27-12

w JOB=xxxxxxxx EOD ON FIRST READ OF SCRATCH FILE RC = cc

Reason:
An end-of-data condition was encountered on the first read of a temporary scratch file.
The where-in-program code is indicated by w. The job is indicated by xxxxxxxx. The
return code is indicated by cc. The command terminates. A timing problem may cause
this message.

Action:
Contact your installation specialist for assistance.

1500 Message Reference Guide

 SMxx

SM27-13

w JOB=xxxxxxxx ERROR READING SCRATCH FILE RC = cc

Reason:
An error has occurred trying to read a temporary scratch file. The where-in-program
code is indicated by w. The job is indicated by xxxxxxxx. The return code is indicated by
cc. The command terminates. A timing problem may cause this message.

Action:
Contact your installation specialist for assistance.

SM27-14

w JOB=xxxxxxxx ERROR WRITING TO SCRATCH FILE RC = cc

Reason:
An error has occurred trying to write to a temporary scratch file. The where-in-program
code is indicated by w. The job is indicated by xxxxxxxx. The return code is indicated by
cc. The command terminates. A timing problem may cause this message.

Action:
Contact your installation specialist for assistance.

SM27-15

w JOB=xxxxxxxx ERROR WRITING TO SASJOB, FILE IS FULL RC = cc

Reason:
A 'file full' condition was encountered trying to write to the job database. The w
indicates the where-in-program code. The xxxxxxxx indicates the job. The cc indicates
the return code. The command terminates.

Action:
Perform the following actions:
■ Correct the space problem.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance

Chapter 7: SLFA - SPOR Messages 1501

SMxx

SM27-16

w JOB=xxxxxxxx ERROR WRITING TO SASJOB RC = cc

Reason:
An error has occurred trying to write a record to the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

SM27-17

w JOB=xxxxxxxx JOB TO RESTORE IS NOT AN XPJOB JOB

Reason:
You have attempted to restore a converted XPJOB job back to a CA7TOUNI job and the
job name entered is not an XPJOB job. The where-in-program code is indicated by w.
The job is indicated by xxxxxxxx. The command terminates.

Action:
Perform the following actions:
■ Verify that you have entered the correct job name.
■ Correct the job name and retry.

If the problem persists, contact your installation specialist for assistance.

1502 Message Reference Guide

 SMxx

SM27-18

w JOB=xxxxxxxx JOB TO RESTORE NOT CONVERTED WITH BACKUP=

Reason:
You tried to restore a converted XPJOB job back to a CA7TOUNI job, and the BACKUP
option was not specified on the original CONVERT command. The where-in-program
code is indicated by w. The job is indicated by xxxxxxxx. The command terminates.

Action:
Perform the following actions:
■ Verify that you entered the correct job name.
If you entered the correct job name, a RESTORE is not possible.
■ Correct the job name if the correct job name was not entered.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

SM27-19

w JOB=xxxxxxxx ERROR DELETING JOB DIR RECORD RC = cc

Reason:
An error has occurred trying to delete a record from the job database. The w indicates
the where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. The command terminates. A timing problem can cause this message.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1503

SMxx

SM27-20

w JOB=xxxxxxxx FUNCTION NOT CONVERT/RESTORE

Reason:
The command entered is not CONVERT or RESTORE. The where-in-program code is
indicated by w. The job is indicated by xxxxxxxx. The command terminates.

Action:
Perform the following actions:
■ Correct the command.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

SM27-21

w JOB=xxxxxxxx JOB TO CONVERT ALREADY AN XPJOB JOB

Reason:
You have attempted to convert a CA7TOUNI job to an XPJOB job and the job name
entered is already an XPJOB job. The where-in-program code is indicated by w. The
indicated by xxxxxxxx. The command terminates.

Action:
Perform the following actions:
■ Verify that you have entered the correct job name.
■ Correct the job name.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

1504 Message Reference Guide

 SMxx

SM27-22

w JOB=xxxxxxxx MUST PROVIDE BACKUP JOBNAME ON RESTORE CMD

Reason:
You have attempted to restore an XPJOB job to a CA7TOUNI job but did not provide the
BACKUP= parameter on the RESTORE command. The where-in-program code is
indicated by w. The job is indicated by xxxxxxxx. The command terminates.

Action:
Perform the following actions:
■ Add the BACKUP parameter.
■ Retry the command.

If the problem persists, contact your installation specialist for assistance.

SM27-24

w JOB=xxxxxxxx ERROR UPDATING JOB MBR RECORD RC= cc

Reason:
An error has occurred trying to update a record in the job database. The w indicates the
where-in-program code. The xxxxxxxx indicates the job. The cc indicates the return
code. The command terminates.

Action:
Contact your installation specialist for assistance.

SM27-ee

w JOB=xxxxxxxx UNKNOWN ERROR CODE RC = cc

Reason:
An unknown error code has been encountered while processing a CONVERT or RESTORE
command. The error code is indicated by ee. The where-in-program code is indicated by
w. The job is indicated by xxxxxxxx. The command terminates.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1505

SMxx

SM30-00

ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used to request input data online.

Action:
Self-explanatory.

SM30-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data in batch.

Action:
Self-explanatory.

SM30-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function was successful.

Action:
None.

1506 Message Reference Guide

 SMxx

SM30-01

xx INVALID MACRO RETURN CODE nnnn

Reason:
If nnnn=0000, the Dataset data set may be out of space. If xx=33 and nnnn=04E6, the
error may have occurred while adding a DSN. The DS0 member of the Dataset data set
may have been lost. Check for this with the DUMP,DSNBR=DS0 command.

If xx=33 and nnnn=05E8, and the error persists, the DS0 member of the Dataset data set
may contain an invalid pointer. In this case, you should contact your installation
specialist for assistance.

Action:
Perform the following actions:
■ Verify that the CDSI program in installation Job N030 ran successfully if you are
installing CA Workload Automation SE.
■ Use SASSBK00 to back up and reload the CA Workload Automation SE database.

SM30-02

DSN NOT FOUND

Reason:
The requested data set was not found in the CA Workload Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1507

SMxx

SM30-03

OUT OF SPACE ON DATA BASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up the database using SASSBK00.
■ Change DBPARMS.
■ Reallocate the affected file.
■ Reload the database using SASSBK00.

SM30-04

CONFLICT IN DSN AND DSNBR

Reason:
Both DSN and DSNBR were input, but these values are in conflict.

Action:
Correct or delete one specification (both are not required), and retry.

SM30-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field error and retry.

1508 Message Reference Guide

 SMxx

SM30-08

DSN ALREADY EXISTS

Reason:
An attempt was made to add a data set definition that is already in the CA Workload
Automation SE database.

Action:
Use the UPD function if you need to change an existing data set definition.

SM30-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM30-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

SM30-13

DSN HAS USERS -- CANNOT DELETE

Reason:
An attempt was made to delete a data set that is still referenced by jobs in the
database. These references were created by loading a job or adding DSN requirements.

Action:
None. The data set name cannot be deleted from the database at this time.

Chapter 7: SLFA - SPOR Messages 1509

SMxx

SM30-14

CA-7 IDS FAILURE. RC=nnnnnnnn

Reason:
An unexpected error occurred while accessing or updating the CA Workload Automation
SE IDS. If the error occurred during a LOAD of a job, this message could indicate a DSN
that is not cataloged or had no VOLSER specified in the JCL. If RC=0, the IDS is full and
must be expanded.

Action:
If the error was a DSN not cataloged or no VOLSER specified, either catalog the DSN or
add a VOLSER parameter to the JCL, and reissue the LOAD command. If RC=0:
1. Shut down CA Workload Automation SE.
2. Back up the entire database.
3. Reallocate the IDS.
4. Reload the database while CA Workload Automation SE is down.
5. Bring up CA Workload Automation SE with TYPE=ERST.

SM40-00

ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This message is the prompt that is used to request input data online.

Action:
Self-explanatory.

SM40-00

ENTER INPUT DATA

Reason:
This message is the prompt that requests input data in batch.

Action:
Self-explanatory.

1510 Message Reference Guide

 SMxx

SM40-00

xxxxxxxx FUNCTION SUCCESSFUL FOR NW aaaaaa

Reason:
The requested function was successful. The network member that is affected is
identified.

Action:
None.

SM4x-01

ww INVALID MACRO RETURN CODE nnnn

Reason:
An error condition was detected by the program. If nnnn=0000, the Dataset data set or
Index data set may be out of space.

Action:
If nnnn=0000, check the system console for error messages and if the out-of-space
condition is indicated, increase the size of the failing data set. Otherwise, contact your
installation specialist for assistance.

SM4x-02

NETWORK NOT FOUND

Reason:
The requested network was not found in the CA Workload Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1511

SMxx

SM4x-03

OUT OF SPACE ON DATA BASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up the database using SASSBK00.
■ Reallocate the affected file.
■ Reload the database using SASSBK00.

SM4x-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

SM4x-06

COULD NOT ffffffff NETWORK CONTROL RECORD

Reason:
An error occurred trying to access the DS00000000 record from the database. If ffffffff is
FIND, the record was not found. If ffffffff is UPDATE, the error occurred while trying to
replace the record.

Action:
Contact your installation specialist for assistance.

1512 Message Reference Guide

 SMxx

SM4x-07

NETWORK ALREADY EXISTS

Reason:
An ADD function was entered, but the network already exists in the CA Workload
Automation SE database.

Action:
Use the UPD function to change existing network information if you want.

SM4x-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM4x-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

SM4x-12

NETWORK TYPE CANNOT BE CHANGED

Reason:
A UPD function was specified attempting to change the network type from INPUT to
OUTPUT or conversely. This cannot be done.

Action:
Correct or eliminate the network type data and retry.

Chapter 7: SLFA - SPOR Messages 1513

SMxx

SM4x-13

NUMBER OF STATIONS CANNOT BE CHANGED

Reason:
A UPD function indicated an increase or decrease in the number of stations. This cannot
be done if the network already has a schedule.

Action:
Perform the following actions:
■ Delete the schedule.
■ Do the update.
■ Add an appropriate schedule.

SM4x-14

NETWORK HAS JOB REFERENCES AND CANNOT BE DELETED

Reason:
An attempt was made to delete a network that is currently connected to at least one
job.

Action:
Perform the following actions:
■ Disconnect the network from all jobs.
■ Delete the network.

SM4x-15

BAD RETURN FROM IDS FOR xxxxxxxxyyyyyyyy

Reason:
An error occurred while accessing or updating the CA Workload Automation SE IDS.
xxxxxxxx denotes the element and yyyyyyyy denotes the return code.

Action:
Contact your installation specialist for assistance.

1514 Message Reference Guide

 SMxx

SM4x-16

NETWORK IN CONFLICT WITH EXISTING STATION

Reason:
An attempt was made to add a network. This network name conflicts with an existing
station name. This causes an index conflict.

Action:
Select another name for the network and retry.

SM4x-17

STATION xxxxxxxx IN CONFLICT WITH EXISTING NETWORK

Reason:
The specified station name was used with an ADD or UPD function. This station name
conflicts with an existing network and causes an index conflict.

Action:
Select another name for the station identified and retry.

SM50-00

ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used to request input data online.

Action:
Self-explanatory.

SM50-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data in batch.

Action:
Self-explanatory.

Chapter 7: SLFA - SPOR Messages 1515

SMxx

SM50-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

SM50-00

xxxxxxxx FUNCTION SUCCESSFUL [JOB SET FOR RELOAD]

Reason:
The requested function completed successfully. A replace has been done for a JCL
member, and the corresponding job has been set to be reloaded on the next run.

Action:
Set the RELOAD indicator to N by using the DB.1 (JOB) panel of Database Maintenance if
the changes are not to impact the database. Otherwise, no action is necessary.
Note: If RELOAD of x is used for this job on the JOB panel, the reload indication for the
next run is ignored.

SM50-00

xxxxxxxx FUNCTION SUCCESSFUL xxxxxxxx(nnnn) ADDED TO THE REQ 'Q'

Reason:
The RUN or RUNH function completed successfully. The job name and the CA Workload
Automation SE assigned number are identified in the second line of the message.

Action:
None.

1516 Message Reference Guide

 SMxx

SM50-00

xxxx FUNCTION SUCCESSFUL (JCL SET FOR RETRIEVAL FROM OVERRIDE LIB)

Reason:
The requested function completed successfully. A new JCL member has been added
(through SAVE function) or replaced (through REPL function) in the JCL Override library
of ID 254. The next time the job is executed (either by demand or through Schedule
Scan functions), JCL will come from this Override library.

Action:
None.

SM50-01

xx INVALID MACRO RETURN CODE xxxxxxxx

Reason:
The program detected an unusual condition. If xx=L5 and nn=00, an error probably
occurred in the attempt to edit a large member in the EWF.

Action:
Increase the SWFTRK allocation on the DAIO statement in the initialization file.

SM50-04

CONFLICT IN DSN, VOLSER, OR JCLID

Reason:
A combination of DSN, VOLSER, and JCLID were input, but their values were in conflict.

Action:
Delete or clear the unnecessary fields and retry.

SM50-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

Chapter 7: SLFA - SPOR Messages 1517

SMxx

SM50-06

NO AVAILABLE JOB NUMBER

Reason:
The job being submitted for CA Workload Automation SE processing from the JCL screen
cannot enter the queues because there are no available job numbers to assign.

Action:
Perform the following actions:
■ Determine why all available job numbers are in use.
■ Retry the command after some jobs have completed CA Workload Automation SE
processing.
■ Contact your installation specialist for assistance.

If the SCHEDULE initialization file statement, HIJBNUM, does not already specify the
maximum 9999, consider increasing that number after taking the appropriate planning
steps (a COLD type of start is required).

SM50-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM50-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input received was not recognized by the program.

Action:
Correct the input and retry.

1518 Message Reference Guide

 SMxx

SM50-10

JOB (xxxxxxxx) ENTERED INTO REQUEST Q.

Reason:
This message is sent to the Master Station. Indicates that a job entered the request
queue by a RUN or RUNH command from the DB.7 (JCL) panel.

Action:
None.

SM50-12

JCL FE NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT

Reason:
The JCL panel does not allow a FE function for members that have a #7UNI as the first
statement unless CA Workload Automation SE mixed case editor support is enabled.

Action:
Use an external editor if the JCL member must be modified (for example, TSO ISPF - not
under CA Workload Automation SE).

SM50-13

NO SAVE -- ACTIVE FILE EMPTY

Reason:
An attempt was made to SAVE or REPL a member, but the Active Area is empty.

Action:
Retry after the Active Area is set to contain the data you want.

Chapter 7: SLFA - SPOR Messages 1519

SMxx

SM50-14

text

Reason:
An error occurred while accessing or updating the data set. The message text should be
one shown on the following list. The list shows a return code in front of the message,
but the return code is not displayed. The following return codes are shown in their
hexadecimal representation:
08 -
DSN NOT FOUND IN CATALOG
0C -
DATASET NOT FOUND ON VOLUME (vvvvvv)
10 -
INVALID DSORG
14 -
INVALID DCB ATTRIBUTE
18 -
DASD VOLUME NOT AVAILABLE
1C -
MEMBER NOT FOUND
20 -
READ I/O ERROR
20 -
WRITE I/O ERROR
24 -
DATASET IS PASSWORD PROTECTED or
CA-7 DOES NOT HAVE THE REQUIRED DSN ACCESS
28 -
DATASET IS USERID PROTECTED
2C -
MEMBER ALREADY EXISTS
30 -
NEW NAME ALREADY EXISTS

1520 Message Reference Guide

 SMxx

34 -
STOW ERROR
38 -
DATASET OUT OF SPACE
3C -
DATASET IS DATE PROTECTED
40 -
INVALID PARM DATA
54 -
DATASET IS BUSY
58 -
INVALID DDNAME SPECIFIED
5C -
SVC99 ERROR, RF=xxxxxxxx, S99ERROR=yyyyyyyy
60 -
ABEND CONDITION DETECTED (xxx-yy)

For JCL on a CA Librarian or CA Panvalet for z/OS file, pseudo codes appear in front of
the message ONLY as a reference to action to be taken.
L1 - LIB**
CA-LIBRARIAN FAIR HAS NOT BEEN LINKED WITH SASSLIB3
L2 - LIB**
CA-LIBRARIAN INTERFACE BUSY FOR OVER 2 MINUTES
See message CA-7.601 for reason.
L3 - LIB**
INVALID FAIR RESULT AREA - R15=nnnnnnnn
L4 - LIB**
OPN - OPEN UNSUCCESSFUL - RES=bbbbbb
If bbbbbb=000011, check the CA Workload Automation SE JCL to see whether a
//JCLnnn DD statement is present.
L5 - LIB**
MOD - ERROR DURING MEMBER SEARCH - RES=bbbbbb
L6 - LIB**
MOD - MEMBER NOT FOUND - RES=bbbbbb

Chapter 7: SLFA - SPOR Messages 1521

SMxx

L7 - LIB**
REC - READ ERROR - RES=bbbbbb
L8 - LIB**
REC - IMBEDDED INCLUDE NOT FOUND - RES=bbbbbb
L9 - LIB**
CA-LIBRARIAN: DATE CONVERT ERROR - DATE=00yydddF
LA - LIB**
CA-LIBRARIAN: SASSDCON LOAD ERROR - R0=nnnnnnnn
LB - LIB**
CA-LIBRARIAN: MCD CODE ERROR - RES=bbbbbb-c
P1 - PAN**nnn
PAM HAS NOT BEEN LINKED WITH SASSPANV
P2 - PAN**nnn
CA-PANVALET INTERFACE BUSY FOR OVER 2 MINUTES
See message CA-7.601 for reason.
P3 - PAN**nnn
OPEN UNSUCCESSFUL FOR PAN LIBRARY
P4 - PAN**nnn
NAME NOT ALPHANUMERIC
P5 - PAN**nnn
IMBEDDED INCLUDE MEMBER NOT FOUND
P6 - PAN**nnn
MEMBER NOT FOUND IN PAN LIBRARY
P7 - PAN**nnn
CA-PANVALET FILE READ ERROR

Action:
See the following list of corrective actions for the messages keyed to the return code
shown in the previous list for non-CA Librarian or CA Panvalet for z/OS files. If the
problem persists, contact your installation specialist for assistance.
08
Supply a volume serial number for the request or catalog the data set.

1522 Message Reference Guide

 SMxx

0C
Verify that the data set is on the volume requested. Specify the correct volume if in
error.
10
Data set organization must be PS or PO. If PDS, the member name must be
provided.
14
Either BLKSIZE=0 or KEYLEN=0 or RECFM not = F or LRECL not = 80.
18
No //U7volser DD statement exists for the volume where the data set resides.
Supply a //U7volser DD statement in the CA Workload Automation SE execution
JCL. The ALLOC command may be issued to make the volume available.
1C
Provide a valid member name.
20
Try again. If problem persists, contact your installation specialist for assistance.
24
This update would require a WTOR reply from the system operator's console that
would put CA Workload Automation SE in a hard wait; that is, no terminal
processing, job scheduling, job submittal, and so forth, until the operator
responded. Updates to such a data set are not allowed from CA Workload
Automation SE. The update must be made from outside of CA Workload
Automation SE by using TSO, batch, and so forth, so as not to impede production
scheduling.
28
1) This request has violated User Security as defined in the module referenced by
the USER keyword of the SECURITY statement in the product's initialization file. Use
a different operator ID at logon time or change the USER ID Security module.
2) CA Workload Automation SE does not have access to the JCL data set. This can
occur using external security for data sets if CA Workload Automation SE does not
have authorized access to the data set.
2C
Use REPL function instead of SAVE. If returning from the Editor, use SR instead of
SS.

Chapter 7: SLFA - SPOR Messages 1523

SMxx

30
Either use a different NEWNAME for the RENAME function or delete the existing
NEWNAME member before doing the RENAME.
34
Check for sufficient directory space. Probably will require reallocating and copying
the data set.
38
Try compressing the data set. It may require a reallocation and copy. CA Workload
Automation SE will not write on the last track of any extent in the data set. If an
attempt is made by CA Workload Automation SE to do so, the SAVE/REPL is
terminated with this code.
3C
Similar to return code 24. This request is rejected to prevent CA Workload
Automation SE from going into a hard wait until an operator responds to the WTOR
for the date override. This update must be made outside of CA Workload
Automation SE through TSO, batch, and so forth, so as not to impede production
scheduling.
40
Contact your installation specialist for assistance.
44
The necessary programs to interface with CA Workload Automation SE are not
available. Verify that the following modules are in a CA Workload Automation SE
load library. If one or more modules are missing, contact your installation specialist
for assistance.
■ SASS6CPY
■ SASS6DEL
■ SASS6MOD
■ SASS6RNM
50
SASSSM5C detected an error. Values of x are:
■ 3 - SNOTE failure.
■ 4 - An attempt was made to write more data than the calculated allocation.
Contact your installation specialist for assistance.

1524 Message Reference Guide

 SMxx

54
Wait and try again. If problem persists, contact your installation specialist for
assistance.
58
Specify a ddname that exists in the execution JCL for CA Workload Automation SE.
Check spelling and try again.
5C
Dynamic allocation failed.
If xxxxxxxx=00000004, then:
yyyyyyyy=020C0000
Indicates a request for exclusive use of a shared data set failed. If this is a JCL
data set, try using the DYN=2 option on the appropriate JCL statement in the
product's initialization file.
yyyyyyyy=02100000
Indicates that the requested data set is unavailable to CA Workload
Automation SE because another job has exclusive use of the data set; for
instance, another job has the data set allocated DISP=OLD.
yyyyyyyy=02180000
Indicates that the specified volume could not be mounted.
yyyyyyyy=17080002
Indicates that the data set is not cataloged.
For other values of yyyyyyyy, see the IBM Manual z/OS MVS Programming:
Authorized Assembler Services Guide.
If xxxxxxxx=00000008,
Then CA Workload Automation SE is not running in an MVS environment and
dynamic allocation is unavailable.
If xxxxxxxx=0000000C,
Then a dynamic allocation internal error was detected. If the error persists,
contact CA Support at ca.com/support for assistance.
If xxxxxxxx=00000010,
Then a dynamic allocation internal error was detected. If the error persists,
contact CA Support at ca.com/support for assistance.
If xxxxxxxx=00000014,
Then a dynamic allocation internal error was detected. If the error persists,
contact CA Support at ca.com/support for assistance.

Chapter 7: SLFA - SPOR Messages 1525

SMxx

If xxxxxxxx=00000018,
Then a DD statement for the data set was detected in the CA Workload
Automation SE JCL. This DD statement should be removed.
If xxxxxxxx=00000020,
Then the member is currently in use. Wait a few minutes and attempt the
command again.
If xxxxxxxx=00000024,
Then the data set is currently in use. Wait a few minutes and attempt the
command again.
60
Abend condition detected. xxx indicates the abend code while yy is the reason
code. If xxx=213 and yy=30, another task is updating the file; try again. If xxx=913,
CA Workload Automation SE may not be authorized to access the data set; check
with your security administrator. For any other abend codes, see IBM manual
GC38-1008 for further details.

For CA Librarian or CA Panvalet for z/OS files, the following list shows the corrective
action for the messages keyed to the pseudo code shown in the list under Action.
L1
See the Interface Reference Guide for instructions on installing the CA Librarian
interface.
L2
See message CA-7.601 for action.
L3
If this message persists, contact your installation specialist for assistance.
L4
For explanations of bbbbbb, see the CA Librarian File Access Interface Routines
guide for the first six bytes of FAIROPN result area.
L5
For explanations of bbbbbb, see the CA Librarian File Access Interface Routines
guide for the first six bytes of FAIRMOD result area.
L6
The member could not be found on the CA Librarian file. Check the spelling of the
member and retry. If the error persists, contact your installation specialist for
assistance.

1526 Message Reference Guide

 SMxx

L7
For explanations of bbbbbb, see the CA Librarian File Access Interface Routines
guide for the first six bytes of FAIRREC result area.
L8
The member on the -INC statement could not be found. For explanations of
bbbbbb, see the CA Librarian File Access Interface Routines guide for the first six
bytes of FAIRREC result area.
L9
An invalid date was passed to the date conversion module. yy is the year, and ddd is
day of the year (this should be the current Julian date). If the date is not in the
format indicated or if the problem persists, contact your installation specialist for
assistance.
LA
nnnnnnnn is the return code from the SLOAD macro. Make sure the module exists
in the CA Workload Automation SE load library. If it does, verify that the module is
defined to CA Workload Automation SE by an APPLCTN statement in the
initialization file or in the SASSPROG module.
LB
For explanations of bbbbbb, see the CA Librarian File Access Interface Routines
guide for the first six bytes of FAIROPN result area. For an explanation of c, see the
CA Librarian Software Lock Facility for the FAIROPN result area that is for an MCD
code.
*LIBR* OPN UNSUCCESSFUL
Check for a U7VOLVER DD in the CA Workload Automation SE PROC. Use the UT.11
panel or the ALLOC command to allocate the volume if it is not in the CA Workload
Automation SE PROC.
P1
See the Interface Reference Guide for instructions on installing the CA Panvalet for
z/OS interface.
P2
See message CA-7.601 for action.
P3
nnn is the return code from the POPEN routine in PAM. See the CA Panvalet for
z/OS System Management Guide for further explanation.
P4
nnn is the return code from the PREAD routine in PAM. Check the spelling of the
member and retry. See the CA Panvalet for z/OS System Management Guide for
further explanation.

Chapter 7: SLFA - SPOR Messages 1527

SMxx

P5
nnn is the return code from the PREAD routine in PAM. The member on the
++INCLUDE statement could not be found. See the CA Panvalet for z/OS System
Management Guide for further explanation.
P6
nnn is the return code from the PREAD routine in PAM. Check the spelling of the
member and retry. See the CA Panvalet for z/OS System Management Guide for
further explanation.
P7
nnn is the return code from the POPEN routine in PAM. See the CA Panvalet for
z/OS System Management Guide for further explanation.

The preceding Px errors may also be produced if the security has not been correctly set
up to allow CA Workload Automation SE USERID access to the CA Panvalet for z/OS
library. See the appropriate security documentation for additional information about
security requirements for accessing CA Panvalet for z/OS libraries.

SM50-15

NO SUBMIT---EOD ON FIRST READ

Reason:
The member or sequential data set was empty.

Action:
Verify your input parameters. If in error, correct and retry.

SM50-16

INTERNAL READER BUSY--WAIT AND TRY AGAIN

Reason:
Someone at another terminal has also issued a SUBMIT command.

Action:
Wait ten seconds and try again. If problem persists, contact your installation specialist
for assistance.

1528 Message Reference Guide

 SMxx

SM50-17

INTERNAL READER NOT AVAILABLE

Reason:
A //UCC7IRDR DD statement does not exist in the CA Workload Automation SE
execution JCL.

Action:
Add the correct DD statement so that it is available the next time CA Workload
Automation SE is started.

SM50-18

I/O ERROR ON INTERNAL READER

Reason:
An I/O error was detected while writing to the internal reader.

Action:
Contact your installation specialist for assistance.

SM50-19

ERROR UPDATING JOB DATA SET FOR JOB xxxxxxxx

(JOB WAS RETRIEVED FROM JCL OVERRIDE LIBRARY)

Reason:
A delete function was done for a member from the override library, and a problem
occurred accessing the job information to turn off the USE-OVERRIDE field. Or, if
external security is used to insert USERIDs and a RUN function was entered, a problem
occurred accessing the job information to find a USERID for job submission.

Action:
Try listing the job (using the LJOB command or LIST function from the DB.1 panel). If the
problem persists, you may need to delete and readd the job.

Chapter 7: SLFA - SPOR Messages 1529

SMxx

SM50-22

SUBMIT DENIED BASED ON USERID IN JCL

Reason:
An attempt was made to RUN/RUNH a job for execution from the CA Workload
Automation SE JCL Library Maintenance panel with the JCL containing a USERID that the
requester is not authorized to submit.

Action:
Contact your security administrator to authorize the user to submit for the USERID
specified in the JCL if security access should be allowed.

SM50-23

REPLACE DENIED BASED ON USERID IN JCL

Reason:
An attempt was made to replace JCL for a job that contained a USERID that the user was
not authorized to access.

Action:
Contact your installation security administrator to authorize the user to access the
USERID that exists in the JCL if security access should be allowed.

SM50-24

CONFLICT IN JCLID AND JCLLIB FIELDS

Reason:
The JCL library for a job can only be specified by a JCLID or a JCLLIB, not both.

Action:
Specify either a JCLID or a JCLLIB and reenter.

1530 Message Reference Guide

 SMxx

SM50-25

XPJOB DEFINITION CONTAINS NO PARMLIB

Reason:
XPJOBs can be defined with or without an Optional PARMLIB and Member (on the DB.10
screen). If you try to use the JCL command to FETCH or FE (FETCH EDIT) an XPJOB that
does not have an Optional PARMLIB or Member, you receive this message.

Note: For more information about XPJOB definition, see the Database Maintenance
Guide.

Action:
Determine whether to update the XPJOB definition to include an Optional PARMLIB and
Member.

SM50-35

INVALID DATA FOUND IN EDIT DATA

Reason:
An attempt was made to edit data that contained invalid HEX code. The CA Workload
Automation SE edit process cannot use the data.

Action:
Edit the data outside of CA Workload Automation SE, if necessary, using TSO for
example.

SM60-00

SPECIFY OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This is the prompt used to request selection of a predecessor/successor type. If an error
is made in this selection, you will again be requested to select a type.

Action:
Self-explanatory.

Chapter 7: SLFA - SPOR Messages 1531

SMxx

SM60-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM61-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data.

Action:
Self-explanatory.

SM61-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

SM61-00

xxxxxxxx FUNCTION SUCCESSFUL FOR NWnnnnnn

Reason:
The requested function completed successfully. The network member is also indicated
in the message.

Action:
None.

1532 Message Reference Guide

 SMxx

SM61-01

xx INVALID MACRO RETURN CODE nnnn

Reason:
An error condition was detected by the program. If nnnn=0000, the Job data set may be
out of space, or the job that is being updated may have an invalid database entry.

Action:
If nnnn=0000, check the system console for error messages and if the out-of-space
condition is indicated, increase the size of the failing data set. You can run UCC7DBVR to
help determine the database entry in error. Otherwise, contact your installation
specialist for assistance.

SM61-02

xxxxxxxx NOT FOUND

Reason:
The field identified in the message was not found.

Action:
Correct the specification and retry.

Note: For a connected job or DSN, SCHIDs must match. For anetwork, SUBID and SCHID
must also match. These values may be determined by LJOB,JOB=jobname,LIST=RQMT. If
they are wrong, correct and retry.

SM61-03

OUT OF SPACE ON DATA BASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up database using SASSBK00.
■ Reallocate the affected file.
■ Reload the database using SASSBK00.

Chapter 7: SLFA - SPOR Messages 1533

SMxx

SM61-04

CONFLICT IN DSN AND DSNBR

Reason:
Both the DSN and DSNBR were input, but they did not agree. Both parameters are not
required.

Action:
Correct or delete one specification and retry.

SM61-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

SM61-06

BAD RETURN FROM MODULE xxxxxxxx, RC=hhhh

(FULL INDEX BLK, PRED NOT ADDED BUT UPD GOOD)

Reason:
An error was returned from module xxxxxxxx. The return code is identified by hhhh. If
the message in parentheses appears, either the Index data set is out of space or the 255
limit has been reached for a PRED entry. Since the index entry is only used for listing
references, the job requirement update is completed.

Action:
If the message in parentheses appears, try backing up and reloading the database. You
may want to increase the space for the Index data set. After reloading, try executing the
RQMT command to rebuild the index entries for job requirements.

If the message in parentheses did not appear, note the return code and check the
system console for error messages. Then contact your installation specialist for
assistance.

1534 Message Reference Guide

 SMxx

SM61-07

REQUIREMENT ALREADY EXISTS

Reason:
An A (add) option was entered, but the requirement already exists in the CA Workload
Automation SE database.

Action:
Use the U (update) option to change existing requirement information if applicable.

SM61-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to alter or add a requirement to a job that is not accessible due to
UID security.

Action:
Contact your security administrator if you need to change an existing job requirement or
add a new one.

SM61-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

Chapter 7: SLFA - SPOR Messages 1535

SMxx

SM61-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program. If a user requirement is
being added through an external communicator, be sure that the input does not contain
a parenthesis, comma, or an apostrophe.

Action:
Correct the input and retry.

SM61-13

NETWORK ALREADY USED BY JOB 255 TIMES

Reason:
The network is already connected to the job 255 times. This is the limit.

Action:
Consider adding a functionally identical network under another network name.

SM61-14

ZERO AND NON-ZERO SCHID NOT ALLOWED

Reason:
An attempt has been made to establish a connection for a particular SCHID, when it has
already been established for all SCHIDs (zero), or conversely. This is clearly a
contradiction.

Action:
Verify that the existing connection is correct. If not, disconnect existing requirement
then reenter the request that failed.

1536 Message Reference Guide

 SMxx

SM61-15

CONFLICT IN JOBNAME SPECIFICATION

Reason:
An attempt was made to delete a job requirement when the definition was for a
negative requirement (or conversely).

Action:
Correct the command and try it again.

SM70-00

ENTER OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Reason:
This prompt a selection of a schedule type online. If an error is made in the selection,
this message is reissued.

Action:
Self-explanatory.

SM70-00

ENTER SCHEDULE TYPE

Reason:
This is the prompt used to request the schedule type in batch mode.

Action:
Enter JOB, INWK, ONWK, or TRGR as the next command.

SM70-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The schedule type was incorrectly specified.

Action:
Correct the command and rerun batch input stream.

Chapter 7: SLFA - SPOR Messages 1537

SMxx

SM70-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM71-00

ENTER INPUT DATA

Reason:
This prompt requests input data.

Action:
Self-explanatory.

SM71-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

SM71-00

xxxxxxxx FUNCTION SUCCESSFUL FOR xxxxxxxx

Reason:
The requested function completed successfully. The schedule member is identified.

Action:
None.

1538 Message Reference Guide

 SMxx

SM71-01

xx INVALID MACRO RETURN CODE nnnn

Reason:
The following explains the various situations:
■ If xx=67, nnnn=0004, and the error occurs as a result of adding or saving schedules,
then the probable cause is the absence of the ZERO member in the Dataset data
set. This can occur if the Dataset data set was reinitialized after the original
installation of CA Workload Automation SE.
■ If xx=B7, nnnn=0001, and the error occurs as a result of fetching a schedule
member with a MEMBER NOT FOUND message, then this may relate to the absence
of the ZERO member as described above (xx=67, nnnn=0004).
■ If nnnn=0000, the Dataset data set may be out of space.
■ If xx=J7, nnnn=0A62, check that the Dataset data set has available space.

Action:
Perform the following actions:
■ Use SASSBK00 to back up and reload the database.
■ Check for the existence of the ZERO member in the dataset data set using
DUMP,DSNBR=SJ0 (SI0, SO0).
■ Do a restore of the database (job, dataset and index data set) to the most current,
correct copies if the dataset data set has recently been reinitialized in error.
■ Contact your installation specialist if no backup exists.

SM71-02

xxxxxxxx NOT FOUND

Reason:
The identified member was not found in the CA Workload Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1539

SMxx

SM71-03

OUT OF SPACE ON DATA BASE

Reason:
Part of the database is full. See WTO on the system log to determine which file had the
error.

Action:
Perform the following actions:
■ Shut down CA Workload Automation SE.
■ Back up the database using SASSBK00.
■ Reallocate the affected file.
■ Reload the database using SASSBK00.

SM71-04

CONFLICT IN STYPE AND NETWORK

Reason:
An attempt was made to reference an output network (SO type) while in INWK mode (SI
type) or conversely.

Action:
Check for correct network specification. If in error, correct and retry. Otherwise,
transfer to the correct mode by entering the SCHD function and making the appropriate
selection.

SM71-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

1540 Message Reference Guide

 SMxx

SM71-07

SCHDMBR ALREADY EXISTS

Reason:
A SAVE function was entered, but the schedule member already exists in the CA
Workload Automation SE database.

Action:
Use the REPL function to change an existing schedule member if you want.

SM71-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to alter or add schedule information for a job that is not
accessible due to UID security.

Action:
Contact your security administrator if you need to change an existing schedule or add a
new one.

SM71-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM71-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

Chapter 7: SLFA - SPOR Messages 1541

SMxx

SM71-13

NO SAVE -- SCHID COUNT ZERO

Reason:
An attempt was made to SAVE or REPL a schedule but no SCHID data is available.

Action:
Use FETCH or schedule edit (SCHD EDIT) to build SCHIDs before the SAVE or REPL is
attempted.

SM71-14

NO SAVE -- STATION COUNT CONFLICT

Reason:
The currently available schedule data contains schedules for either more or less stations
than the number defined for the specified network.

Action:
Verify that the station specification is correct. If in error, correct and retry. Otherwise,
schedule edit (SCHD EDIT) must be used (specifying the correct network) to construct a
correct schedule.

SM72-00

ENTER INPUT DATA

Reason:
This prompt requests input data.

Action:
Self-explanatory.

SM72-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

1542 Message Reference Guide

 SMxx

SM72-00

LIST FUNCTION SUCCESSFUL,

USE '/PAGE+1' COMMAND OR PFK EQUIVALENT FOR NEXT SCHID.

Reason:
The LIST function completed successfully. All SCHIDs may be reviewed by paging
through the output. Any SCHID may be updated by changing the function to REPL and
updating various fields on the appropriate panel.

Action:
None.

SM72-01

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSSM72. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn. If
nnnnnnnn=00000000, a CA Workload Automation SE data set may be out of space.

Action:
Perform the following actions:
■ Check the system console for error messages if nnnnnnnn=00000000.
■ Increase the size of the failing data set if the out-of-space condition is indicated.
■ Contact your installation specialist for assistance.

SM72-02

SCHID NOT FOUND

Reason:
The requested schedule ID was not found.

Action:
Check for correct input. If in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1543

SMxx

SM72-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Note: For correct syntax, see the Database Maintenance Guide

Action:
Correct the appropriate data fields and retry.

SM72-07

SCHID ALREADY EXISTS

Reason:
An ADD function was entered, but the SCHID already exists for this schedule member.

Action:
Perform one of the following actions:
■ Use the REPL function to change the existing SCHID information.
■ Use a different SCHID number.

SM72-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

1544 Message Reference Guide

 SMxx

SM72-13

ID-COUNT IS ZERO

Reason:
A LIST function was requested but there are currently no SCHIDs to list.

Action:
None.

SM72-14

DEAD-LINE TIME PRECEDES PREVIOUS STATION DOTM

Reason:
The deadline time (due-out minus lead-time) of station n occurs before the DOTM of
station n-1. This is an erroneous condition. It is necessary to specify DODY if processing
extends past midnight.

Action:
Change the input to correct this situation and reenter.

SM72-15

SCHID CONTAINS NO SCHEDULE ELEMENTS

Reason:
An attempt was made to ADD or REPL a SCHID but no processing days have been
specified.

Action:
Correct the input and reenter.

SM72-16

SCHEDULE TYPE INDICATOR MUST BE 'X' OR 'Y'

Reason:
A DAILY, WEEKLY, and so on, cycle was indicated with a character other than X or Y.

Action:
Correct the input and retry.

Chapter 7: SLFA - SPOR Messages 1545

SMxx

SM72-17

TOO MANY SCHEDULE ELEMENTS -- MAX IS nn

Reason:
A limited number of internal schedule elements (ISEs) may apply to a single schedule ID
(SCHID). This maximum number is indicated in the message (nn). The formulas for
calculating ISEs are as follows:
1. If DAILY=Y, add 1.
2. If WEEKLY=Y, add 1 for each day of the week selected.
3. If MONTHLY=Y, add 1 for each week and add 1 for each RDAY.
4. If ANNUAL=Y, add 1 for each day.
5. If SYMETRIC=Y, add 1.

The total obtained cannot be greater than the maximum indicated.

Action:
Determine if any ISEs may be eliminated by defining the schedule differently. It may be
necessary to split this specification into two different SCHIDs.

SM72-18

REPEAT LOOP LASTS MORE THAN 24 HOURS

Reason:
The INTERVAL times the COUNT specified totals 1440 or more minutes (24 hours).

Action:
Correct the values and reenter.

SM72-19

REPEATING JOBS REQUIRE A SUBMIT TIME

Reason:
An INTERVAL has been provided, but a submit time (SBTM) has not.

Action:
Correct the values and reenter.

1546 Message Reference Guide

 SMxx

SM75-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data.

Action:
Self-explanatory.

SM75-00

xxxxxxxx FUNCTION SUCCESSFUL

ENTER INPUT FOR NEXT REQUEST

Reason:
The requested function completed successfully.

Action:
None.

SM75-01

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSSM75. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn. If
nnnnnnnn=00000000, a CA Workload Automation SE data set may be out of space.

Action:
Perform the following actions:
■ Check the system console for error messages if nnnnnnnn=00000000.
■ Increase the size of the failing data set if the out-of-space condition is indicated.
■ Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1547

SMxx

SM75-02

xxxxxxxx NOT FOUND

Reason:
The job, DSN, or trigger definition specified was not found in the CA Workload
Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

SM75-03

OUT OF SPACE ON DATABASE

Reason:
Not enough room in the IDS to contain the trigger definitions.

Action:
Reorganize the IDS. Consider increasing the size also.

SM75-04

CONFLICT IN NAME AND DSNBR

Reason:
Both DSN and DSNBR or NWK and DSNBR were input but do not agree with IDS data.

Action:
Correct or delete one specification (both are not required) and retry.

SM75-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

1548 Message Reference Guide

 SMxx

SM75-06

ERROR FROM MODULE xxxxxxxx, RC=hhhh

(FULL INDEX BLK, DATA NOT ADDED FOR y...y)

Reason:
The module xxxxxxxx returned an error. The hhhh identifies the return code. The
message in parentheses appears when the Index data set is out of space or the 255
entry limit is reached for a y...y entry.

Action:
If the second line of the message in parentheses appears, try backing up and reloading
the database. Consider increasing the space for the Index data set. After reloading, try
the entry that failed. If the same failure recurs, you have reached the limit of entries
possible for the indicated entry y...y and cannot add any more.

If the message in parentheses did not appear, note the return code and y...y values.
Possibly, more than 255 different job/data set/network/SCHID combinations trigger the
job. In this case, no problem exists. The actual triggers are added, but the LJOB with
LIST=TRIG only reports the first 255.

SM75-07

TRIGGER ALREADY EXISTS

Reason:
An A (add) option was entered, but exactly the same trigger entry exists in the database.

Action:
Use the U (update) option to change an existing trigger if applicable.

SM75-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to alter or add a job trigger for a job that is not accessible due to
UID security.

Action:
Contact your security administrator if you need to change an existing job trigger or add
a new one.

Chapter 7: SLFA - SPOR Messages 1549

SMxx

SM75-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM75-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input received was not recognized by the program.

Action:
Correct the input and retry.

SM75-11

UPDATE FINISHED BUT WITH EXCEPTIONS AS SHOWN

Reason:
The updating of job triggers has occurred excluding those entries that have comments in
the EXCEPTIONS column. If the message indicates ERROR FROM: SASSSM6D, the job
probably already has 255 trigger definitions. See Trigger Scheduling Panels topic in the
chapter "Scheduling" in the Database Maintenance Guide for more information.

Action:
Review and correct the reasons for the EXCEPTIONS and reenter.

SM75-14

NO TRIGGERS DEFINED

Reason:
No triggers are defined for the requested element.

Action:
None.

1550 Message Reference Guide

 SMxx

SM75-14

NO TRIGGERED ENTRY FOUND FOR xxxxxxxx

Reason:
No trigger information currently exists for the indicated value.

Action:
Verify input. If in error, correct and retry.

SM75-15

TRGD-JOB AND SCHID COMBINATION NOT FOUND

Reason:
The TRGD-JOB and SCHID combination do not currently exist for the specified job or
DSN.

Action:
Verify input. If in error, correct and retry.

SM75-16

xxxxxxxx GREATER THAN MAXIMUM ALLOWED

Reason:
One of the time indicators in the input data is invalid.

Action:
Determine which field is in error. Correct and retry.

SM75-17

SCHID 0 ALREADY EXISTS

Reason:
An A (add) option was entered for a job that is already triggered by SCHID 0. You cannot
add a SCHID 0 and a specific SCHID for the same triggered job.

Action:
If the job should be triggered by only specific SCHIDs, delete the entry for SCHID of 0
and add the specific SCHIDs.

Chapter 7: SLFA - SPOR Messages 1551

SMxx

SM75-17

CANNOT TRIGGER JOB FOR SCHID OF ZERO AND NON-ZERO

Reason:
An attempt has been made to establish a job trigger based on a particular SCHID, when
it has already been established for all SCHIDs (zero), or conversely. This is clearly a
contradiction.

Action:
Verify that the existing relationship is correct. If not, delete it and reenter the command.

SM75-18

DUE-OUT TIME AND QUEUE TIME CONFLICT

Reason:
Either due-out time or queue time must be specified, but not both.

Action:
Delete one of the specifications and retry.

SM75-19

INPUT NETWORK MUST BE SPECIFIED

Reason:
An output network cannot trigger a job.

Action:
Specify an input network.

SM75-22

WARNING: TRIGGER LOOP DEFINED FOR JOB xxxxxxxx

Reason:
A job has been defined to trigger a job with the same name.

Action:
Verify that the existing relationship is correct. If not, delete it and reenter the command.

1552 Message Reference Guide

 SMxx

SM80-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

SM80-00

xxxxxxxx FUNCTION SUCCESSFUL FOR xxxxxxxx

Reason:
The requested function completed successfully. The schedule member is identified.

Action:
None.

SM80-01

xx INVALID MACRO RETURN CODE xxxxxxxx

Reason:
This indicates an unusual condition detected by the program.

Action:
Contact your installation specialist for assistance.

SM80-02

xxxxxxxx NOT FOUND

Reason:
The identified member was not found in the CA Workload Automation SE database.

Action:
Check for correct input. If in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1553

SMxx

SM80-04

SPECIFY EITHER JOB OR NETWORK -- NOT BOTH

Reason:
Either JOB or NETWORK may be specified, but not both.

Action:
Delete one specification and reenter.

SM80-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the value in error and retry.

SM80-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to alter a job's schedule that is not accessible due to UID security.

Action:
Contact your security administrator if you need to modify the job's schedule.

SM80-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

1554 Message Reference Guide

 SMxx

SM80-14

NETWORK NOT INPUT TYPE

Reason:
Output network schedules are based on the jobs to which the networks are connected.
Therefore, SCHDMOD does not apply.

Action:
None.

SM80-15

JOB/NETWORK HAS NO SCHEDULE

Reason:
The requested job or network does not have an associated schedule.

Action:
Add and resolve the schedule before modifying it.

SM80-16

SCHEDULE HAS NOT BEEN RESOLVED

Reason:
A schedule must be successfully resolved before it may be modified.

Action:
Resolve the schedule, and then make the modifications that you want.

SM80-17

ENTIRE DAY MASK MUST BE 0'S AND 1'S

Reason:
An attempt was made to update a schedule but unrecognizable data appeared in the
day mask.

Action:
Correct the input and retry.

Chapter 7: SLFA - SPOR Messages 1555

SMxx

SM85-00

cccccccc ffffffff SUCCESSFUL

Reason:
The requested function (ffffffff) for calendar cccccccc was completed successfully.

Action:
None.

SM85-00

cccccccc ffffffff SUCCESSFUL [RESOLVE MAY BE REQUIRED]

Reason:
The requested function (ffffffff) for calendar cccccccc completed successfully. Because
the function affected a standard CA Workload Automation SE base calendar, a RESOLVE
command is sometimes required to update schedules that use this calendar.

Note: If you add a leap year calendar and do not change the end of February to be 29,
you receive the following additional message alerting you of a possible problem:

NOTE: END OF FEB IS NOT 29

Verify that you have the correct month end date for February.

If you refresh a calendar, you receive one of these additional messages indicating the
refresh source:

NOTE: REFRESHED FROM LOADLIB

NOTE: REFRESHED FROM PCALYYxx

Action:
RESOLVE any affected schedules if needed.

1556 Message Reference Guide

 SMxx

SM85-01

LOAD FAILED FOR MODULE SASSDCON

Reason:
The product was unable to access the date conversion routine.

Action:
Perform the following actions:
■ Make sure that SASSDCON is in a library accessible from CA Workload Automation
SE.
■ Issue the /DISPLAY,A=SASSDCON command to ensure that an entry is in the
application directory for the module.

SM85-02

INTERNAL DATE CONVERSION ERROR

Reason:
An error occurred in the internal processing of the calendar data.

Action:
Check the data specified for the calendar. If it is correct and the problem persists,
contact your installation specialist for assistance.

SM85-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
An error occurred processing the data for field xxxxxxxx.

Action:
Correct the field specified on the message and retry the function.

Chapter 7: SLFA - SPOR Messages 1557

SMxx

SM85-06

INVALID DAY SPECIFIED IN CALENDAR DAYS: DAY xxx

Reason:
An error occurred processing the data for the days of the months. The day in error is
described as the relative day of the year (xxx). For example, DAY 032 represents
February 1st.

Note: The most common cause for this message is specifying too many or too few days
for a particular month. For example, specifying 31 days in September would cause this
error.

Action:
Correct the data and retry the function.

SM85-07

ACCESS TO CALENDAR xxxxxxxx DENIED BY EXTERNAL SECURITY

Reason:
The external security package denied an attempt to access CA Workload Automation SE
calendar xxxxxxxx. This message can only occur if external security for calendar access
has been enabled in the product's initialization file.

Action:
Check with your external security administrator to define the correct access level.

SM85-07

LOAD FAILED

Reason:
The base calendar with a standard CA Workload Automation SE calendar name that was
the subject of a LIST or REFRESH function was not found in either the CA Workload
Automation SE Calendar PDS or the load libraries available to the CA Workload
Automation SE address space.

Action:
Check the name of the calendar to ensure it is correct. If this is a batch calendar, check
to ensure it resides in a load library connected to the CA Workload Automation SE
address space and retry the function.

1558 Message Reference Guide

 SMxx

SM85-07

MEMBER NOT FOUND [ON CALENDAR LIBRARY]

Reason:
The calendar that was the subject of a UPD or DEL function was not found in the CA
Workload Automation SE Calendar PDS. The optional part of the message text displays
when the nonstandard calendar name that was the object of a LIST function was not
found.

Action:
None.

SM85-07

OPTION NOT VALID WITHOUT CALENDAR LIBRARY

Reason:
The product's initialization file has no CA Workload Automation SE Calendar PDS
definition.

Action:
See the Systems Programming Guide for instructions on allocating and identifying the
Calendar PDS if you want to use online calendars.

SM85-07

PREMATURE EOF REACHED ON SGETPDS

Reason:
An attempt was made to read a calendar from the CA Workload Automation SE
Calendar PDS, however, the end of data was reached before the full calendar was read.

Action:
Check the CA Workload Automation SE Calendar PDS to see if it has been corrupted.
Also, check the product's initialization file to ensure that the CALENDAR statement
specifies the correct data set name. Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1559

SMxx

SM85-07

REFRESH FAILED

Reason:
A REFRESH function was attempted on a member with a nonstandard calendar name.
Load module versions of calendars must have a standard name format (SCALyyxx).

Action:
Verify that the calendar name was entered correctly, and retry the command.

SM85-07

text

Reason:
Check the SM50-14 message for a comparison of the text value.

Action:
Take the action as indicated for the SM50-14 message.

SM85-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM85-10

INVALID DAY SPECIFIED FOR MONTH BEG/END : mm/dd

Reason:
An invalid date was entered for the beginning or ending date mm/dd.

Action:
Correct the field specified on the message and retry the function.

1560 Message Reference Guide

 SMxx

SM85-11

BEG/END DAYS NOT IN ASCENDING ORDER : mm/dd1 mm/dd2

Reason:
The beginning and ending dates are valid dates, however, mm/dd1 is a higher date than
mm/dd2.

Action:
Correct the fields specified on the message so that the beginning and ending dates are
in ascending sequence and retry the function.

SM85-12

SPECIFIED MEMBER IS NOT A VALID CA-7 CALENDAR

Reason:
A member was found in the calendar PDS matching the calendar name specified on the
panel. However, that member is not in the correct format for a CA Workload
Automation SE calendar.

Action:
Check to ensure that the name specified is correct. If it is correct and the problem
persists, contact your installation specialist for assistance.

SM90-00

ENTER INPUT DATA

Reason:
This is the prompt to request input data.

Action:
Self-explanatory.

SM90-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The requested function completed successfully.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1561

SMxx

SM90-00

xxxxxxxx FUNCTION SUCCESSFUL FOR JOB xxxxxxxx

Reason:
The requested function completed successfully. The associated job name is printed.

Action:
None.

SM90-01

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSSM90. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn. If
nnnnnnnn=00000000, a CA Workload Automation SE data set may be out of space.

Action:
Perform the following actions:
■ Check the system console for error messages if nnnnnnnn=00000000.
■ Increase the size of the failing data set if the out-of-space condition is indicated.
■ Contact your installation specialist for assistance.

SM90-02

JOB NOT FOUND

Reason:
The requested job was not found in the appropriate queues.

Action:
Check for correct input. If in error, correct and retry.

1562 Message Reference Guide

 SMxx

SM90-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
The identified field contains invalid data.

Action:
Correct the field in error and retry.

SM90-08

YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Reason:
An attempt was made to access a job's QJCL that is not accessible due to UID security.

Action:
Contact your security administrator if you need to edit the QJCL for this job. contact
your security administrator.

SM90-09

YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Reason:
A function was entered that the operator is not authorized to do.

Action:
Contact your security administrator if the operator should be allowed to enter the
function.

SM90-10

UNRECOGNIZABLE DATA IN INPUT

Reason:
Input was received that was not recognized by the program.

Action:
Correct the input and retry.

Chapter 7: SLFA - SPOR Messages 1563

SMxx

SM90-13

NO SAVE -- ACTIVE FILE EMPTY

Reason:
An attempt was made to replace the JCL for a request queue job but the Active Area
contains no data.

Action:
Verify that the Active Area contains the JCL that you want and retry.

SM90-15

SKELETON RECORD FOUND

Reason:
Schedule Scan has not completed initial job processing. This message also may be
produced for jobs whose status is RETRY on an LQ display.

Action:
Wait a few minutes before trying the JCL request again. If problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SM90-16

NO SAVE -- JOB COMPLETED NORMALLY

Reason:
The requested job already completed successfully.

Action:
None.

1564 Message Reference Guide

 SOxx

SM90-17

UPDATE DENIED - SUBMIT CHECK FAILED

Reason:
An attempt was made to replace JCL for a request queue job. The JCL contained a
USERID; however, the user trying to update is not authorized to submit for that USERID.

Action:
Perform one of the following actions:
■ Contact your security administrator if security access needs to be allowed.
■ Log on with an authorized USERID and update the JCL.

SM90-18

QJCL FE/FETCH NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT

Reason:
The QJCL panel will not allow a FE (or FETCH) function for jobs that are set as 7UNI jobs
unless CA Workload Automation SE mixed case editor support has been enabled.

Action:
If the JCL must be modified, then the job could be canceled, the JCL changed outside of
CA Workload Automation SE, and the DEMAND command used to bring the job in again.

SM90-19

RUN LOG DATA NOT AVAILABLE THROUGH EDIT

Reason:
The QJCL panel does not allow a FPE function for CA Workload Automation SE Run Log
records.

Action:
Use the LRLOG command to list information from the CA Workload Automation SE Run
Log.

SOxx
This section contains the SOxx messages.

Chapter 7: SLFA - SPOR Messages 1565

SPOx

SO00-4B

SASSSOnn CYCLE COMPLETED.

Reason:
This message is issued when a CA Workload Automation SE submit thread has
submitted at least 15 jobs. This is only an informational message. The nn denotes the
particular submit thread.

Action:
None.

SPOx
This section contains the SPOx messages.

SPOA-00

REQUEST COMPLETE.
JOB xxxxxxxx HAS BEEN POSTED FOR SUBMISSION (EXPRESS)
(xxx EXTERNAL INPUTS FORCED)
(xxx INTERNAL INPUTS FORCED)

Reason:
The input request was completed successfully. If JOB was specified, the last three
information lines will be printed.

Action:
Acknowledge the message. It may be necessary to cancel incomplete tasks still in the
Preprocess queue.

SPOA-01

xxxxxxxx - INVALID

Reason:
Keyword/value xxxxxxxx is invalid. If required, it may have been omitted from the input
request.

Action:
Correct and resubmit the command.

1566 Message Reference Guide

 SPOx

SPOA-02

SKELETON RECORD FOUND

Reason:
Schedule Scan is still in the process of building queue records for the requested job.

Action:
Wait a few minutes before trying the JCL request again. If problem persists for an
extended period, look for messages concerning this job on the Master Station. This
message also may be produced for jobs whose status is RETRY on an LQ display. If
unable to resolve the problem, contact your installation specialist for assistance.

SPOA-03

REQUIREMENTS SCAN INCOMPLETE

Reason:
Schedule Scan (Requirements Scan modules) is still in the process of determining the
job's requirements.

Action:
Wait a few minutes before trying the JCL request again. If problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SPOA-04

JOB HAS ALREADY BEEN SUBMITTED

Reason:
The requested job has already been submitted for execution.

Action:
Verify the job number specified on the input request. If correct, no action is required; if
not, correct and resubmit the command.

Chapter 7: SLFA - SPOR Messages 1567

SPOx

SPOA-05

JOB NOT FOUND IN REQ OR RDY QUEUE

Reason:
The job specified on input could not be found in the request or ready queue.

Action:
Verify the job name specified on the input request; correct and resubmit the command
if wrong.

SPOA-06

I/O ERROR RC=xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
Resubmit the command. If the error recurs, contact your installation specialist for
assistance.

SPOA-07

JCL SUBMISSION POSTED [(EXPRESS)]

Reason:
JCL submission has been posted as requested. If the EXPRESS=YES option was specified,
the EXPRESS notation is displayed.

Action:
None.

1568 Message Reference Guide

 SPOx

SPOA-08

EXPRESS=YES INVALID WITH WLB

Reason:
The SUBMIT command parameter EXPRESS=YES is not valid if Workload Balancing is
being used.

Action:
None. If you want, use the QM.3 (XUPD) panel to update the job's priority instead of
using EXPRESS=YES. To satisfy all requirements for the job, enter the SUBMIT command
for the job eliminating the EXPRESS=YES operand.

SPOB-00

JOB= xxxxxxxx (nnnn) SET FOR RESTART

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
Job xxxxxxxx has been moved from the ready or active queue back to the request queue
and flagged for restart.

Action:
Use restart to reactivate processing for the job.

SPOB-00

JOB= xxxxxxxx SCHD FLAG SET TO yyy

Reason:
A NXTCYC command has been successfully processed and normal scheduling will be
altered as requested with yyy.

Action:
None.

Chapter 7: SLFA - SPOR Messages 1569

SPOx

SPOB-00

JOB xxxxxxxx(nnnn) - MAINID CHANGED TO yyy

Reason:
A DIRECT command has been successfully processed. The main ID for the job specified
by xxxxxxxx(nnnn) has been changed to redirect submission to the CPU designated by
yyy.

Action:
None.

SPOB-01

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid (or omitted) for the specified command.

Action:
Correct and resubmit the command.

SPOB-02

JOB nnnn NOT FOUND IN READY OR ACTIVE QUEUE

Reason:
An attempt was made to requeue a job to the request queue. Job nnnn was not found in
the ready or active queue.

Action:
Verify that the correct CA 7 WA job number was specified. If necessary, correct and
resubmit the command.

1570 Message Reference Guide

 SPOx

SPOB-02

JOB nnnn NOT FOUND IN REQUEST OR READY QUEUE

Reason:
An attempt was made to direct a job to another CPU. Job nnnn was not found in the
request or ready queue.

Action:
Verify that the correct CA 7 WA job number was specified. If necessary, correct and
resubmit the command.

SPOB-02

JOB xxxxxxxx NOT FOUND IN JOB DATA SET

Reason:
The job name specified on a NXTCYC command was not found in the Job data set.

Action:
Verify the job name specified; correct and resubmit the command.

SPOB-03

JOB xxxxxxxx HAS ALREADY BEEN SUBMITTED

Reason:
An attempt was made to direct job xxx...x to another CPU. The job has already been
submitted and the request cannot be satisfied.

Action:
None.

SPOB-04

QUEUE I/O ERROR, RC=nnn

Reason:
An I/O error occurred while attempting to access the queue.

Action:
Resubmit the command. If the problem persists, contact your installation specialist for
assistance.

Chapter 7: SLFA - SPOR Messages 1571

SPOx

SPOB-05

JOB MEETING SELECTION CRITERIA NOT FOUND

Reason:
An attempt was made to locate a job using a combination of parameters that could not
be satisfied.

Action:
Correct any parameters that require correction and retry.

SPOB-06

UNABLE TO REQUEUE, ARF EVENTS PENDING

Reason:
This message is issued when a REQUEUE is attempted while ARF is controlling recovery
for a job.

Action:
Wait until ARF recovery is complete for the job. The LARFQ command can be used to
track the progress of ARF recovery for the job.

If the REQUEUE must be issued prior to the completion of ARF recovery, you can use the
ARFP command to terminate ARF recovery processing for the job. After the ARFP
command processing is complete, issue the REQUEUE command.

SPOB-07

CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE.

Reason:
A FLOWD command was issued but the CPM feature is not active.

Action:
None.

1572 Message Reference Guide

 SPOx

SPOB-08

NO FLOW RECORDS SELECTED FOR DELETION

Reason:
A FLOWD command was issued but no active flows matched the selection criteria
specified.

Action:
Check the spelling of the flow name argument and reissue the command.

SPOB-09

FLOW RECORD(S) DELETED : nnnn

Reason:
A FLOWD command was issued and one or more active CPM flow records were deleted.
The value nnnn indicates the number of flows deleted.

Action:
None.

SPOB-10

VSAM ERROR : FUNC=ff RC=rrrr CC=cccc KEY=kkkkkkkk

Reason:
A FLOWD command was issued and a VSAM error was encountered attempting to
delete an active CPU flow record. The return code (rrrr) condition code (cccc) and record
key (kkkk...) are displayed.

Action:
Contact your installation specialist for assistance.

SPOB-11

DIRECT COMMAND NOT ALLOWED FOR INTERNAL CROSS-PLATFORM JOBS.

Reason:
The DIRECT command is only valid for regular CPU jobs. The command is not valid for
internal cross-platform jobs (XPJOBs or agent jobs).

Action:
None.

Chapter 7: SLFA - SPOR Messages 1573

SPOx

SPOB-12

REQUEUE INVALID; KEYWORDS CANNOT BE USED TOGETHER.

Reason:
The REQUEUE command has NODE, MAINID, or CPU keywords specified together.

Action:
Correct and resubmit the command.

SPOB-13

REQUEUE INVALID; KEYWORD REQUIRED.

Reason:
The REQUEUE command has no JOB, NODE, MAINID, CPU, or Q keyword specified.

Action:
Correct and resubmit the command.

SPOB-14

FLOW RECORDS ARE NOT USED WITH OPTION CPM=JFM

Reason:
JFM=YES and CPM=JFM are specified on the initialization file OPTIONS statement. This
interface does not create FLOW records. FLOWL and FLOWD commands are not
supported. The CPM CANCEL command will delete a flow.

Action:
Use the CPM ISPF interface or CPM DISPLAY command to view flow status.

Note: For more information, see the Interface Reference Guide and the CA Critical Path
Monitor User Guide.

1574 Message Reference Guide

 SPOx

SPOB-20

JOB=xxxxxxxx HAS NO SCHEDULE, BUT SCHD FLAG SET TO yyy

Reason:
A NXTCYC command has been processed. Since the job has no schedule, normal
scheduling is not altered unless a schedule is added for the job.

Action:
None. If the job should have a schedule, you should add one.

SPOC-02

REF - INVALID.

Reason:
One of the following conditions exists:
■ The REF parameter was omitted.
■ A non-numeric reference number was entered.
■ More than ten reference numbers were specified on one command.
■ A job number of 0 was specified.
■ A station number of 0 was specified.

Action:
Correct the error and reenter the command.

SPOC-04

xx INVALID MACRO RETURN CODE= xxxxxxxx

Reason:
An unexpected error condition was detected in the SASSSPOC module. The location in
the program and the hex value of the return code are given.

Action:
Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1575

SPOx

SPOD-01

xx INVALID MACRO RETURN CODE=hhhhhhhh

Reason:
An unexpected error condition was returned from a macro call. The location in the
program where the error occurred is indicated by xx; the hex value of Register 15 is
indicated by hhhhhhhh.

Action:
Contact your installation specialist for assistance.

SPOD-02

NO QUEUE RECORDS FOUND

Reason:
No entries were found in the CA Workload Automation SE queue pertaining to a
request.

Action:
Verify that the input request was correct. If not, correct the error and reenter the
command.

SPOD-03

REQUIRED INPUT MISSING

Reason:
A required keyword was not found on the input command.

Action:
Correct and reenter the command.

SPOD-04

CONFLICTING INPUT PARAMETERS

Reason:
Mutually exclusive parameters were specified on the input command.

Action:
Correct and reenter the command.

1576 Message Reference Guide

 SPOx

SPOD-05

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx was specified incorrectly.

Action:
Correct and reenter the command.

SPOE-00

JOB xxxxxxxx (nnnn) ADDED TO THE [(PRE/Q)|(POST/Q)]

FOR NETWORK= yyyyyyyy, [SUBID= zzzzzzzz]
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The DMDNW function completed successfully for network yyyyyyyy. The network is
assigned job xxxxxxxx with CA 7 WA job number nnnn. SUBID zzzzzzzz further identifies
the network in the queues.

Action:
None.

SPOE-01

xxxxxxxx -- INVALID OR OMITTED

Reason:
Keyword xxxxxxxx is invalid or omitted. If the keyword is specified, it may contain invalid
data. If the keyword is required, it may have been omitted from the input request.

Action:
Correct and reenter the command.

SPOE-02

NETWORK xxxxxxxx NOT FOUND

Reason:
Network xxxxxxxx was not found in the CA Workload Automation SE database.

Action:
If input is in error, correct and retry.

Chapter 7: SLFA - SPOR Messages 1577

SPOx

SPOE-03

NETWORK xxxxxxxx HAS LOCKED SCHEDULE

Reason:
The network's schedule is locked and it cannot be demanded.

Action:
Resolve the schedule and reissue the request.

SPOE-04

NETWORK xxxxxxxx HAS NO SCHEDULE

Reason:
The specified network does not have a schedule.

Action:
A schedule must be added for the network before it can be demanded.

SPOE-05

ERR/EOF ADDING NETWORK=nnnnnnnn TO THE {PREQ|POSTQ} CODE=xx

Reason:
The network stations could not be added to the specified queue because of an error
condition indicated by xx. If xx=00, the queue is probably full. If xx is not 00, a queue
access error exists.

Action:
If the queue is full, it must be enlarged or stations must be posted before additional
network stations can be added. It may be necessary to delete some stations if only part
of the network was added.

1578 Message Reference Guide

 SPOx

SPOE-06

UNABLE TO ASSIGN CA-7 NUMBER

Reason:
No CA 7 WA job numbers are available to be assigned to the requested network
stations.

Action:
Perform the following actions:
■ Increase the HIJBNUM parameter on the SCHEDULE statement.
■ Demand the network after other stations have been posted or jobs have completed
and freed CA 7 WA job numbers.

SPOE-08

ww INVALID MACRO RETURN CODE nnnnnnnn

Reason:
An unexpected error condition was detected in program SASSSPOE. The location in the
program is specified by ww and the value of register 15 is shown by nnnnnnnn.

Action:
Contact your installation specialist for assistance.

SPOE-09

xx ACTIVE FILE EMPTY OR UNUSABLE. CODE= yyyyyyyy

Reason:
The Active file is probably empty. The active file data can be built using the text editor.

Action:
Make sure that the Active file contains the REMIND data.

Chapter 7: SLFA - SPOR Messages 1579

SPOx

SPOE-10

ERROR TRYING TO CONVERT REMIND DATA. CODE=xx

Reason:
The Active file could not be internally converted.

Action:
Contact your installation specialist for assistance.

SPOE-14

NETWORK (nnnn) ENTERED INTO [(PRE)|(POST)] - PROCESS 'Q' FOR nn STATION(S)

Reason:
This message is sent to the Master Station to indicate that a network has been added to
the queue.

Action:
None.

SPOE-20

REMIND DATA (RMD#xxxx) ENTERED INTO PRE/Q

Reason:
The REMIND command was successfully processed.

Action:
None.

SPOF-00

JOB nnnn ARF REQUIREMENT PURGED.

Reason:
The request to purge the ARF requirement completed successfully. The job number is
indicated by nnnn.

Action:
None.

1580 Message Reference Guide

 SPOx

SPOF-01

INVALID KEYWORD

Reason:
An invalid keyword was entered.

Action:
Correct and resubmit the command.

SPOF-02

JOB nnnn NOT FOUND.

Reason:
The specified job was not found in either the request, ready, or active queue. The nnnn
is the CA 7 WA job number.

Action:
Correct and resubmit the command.

SPOF-03

offset ARQM ERROR R15=return-code R1=reason-code R0=information-code

Reason:
An error occurred accessing the ARF queue record for this job.

Action:
Contact your installation specialist for assistance.

SPOF-04

QUEUE FILE I/O ERROR, RC=xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
Resubmit the command. If the error persists, contact your installation specialist for
assistance.

Chapter 7: SLFA - SPOR Messages 1581

SPOx

SPOF-05

NO STORAGE AVAILABLE FOR DUMMY JOB QUEUE RECORD.

Reason:
An error occurred while attempting to acquire storage for a CA 7 WA job queue record.

Action:
Resubmit the command. If the error persists, contact your installation specialist for
assistance.

SPOF-06

NO ARF QUEUE ELEMENTS FOUND FOR JOB nnnn.

Reason:
No ARF queue element was found for job number nnnn, which was the target of an
ARFP command.

Action:
Correct the job number and reissue the command.

SPOF-07

ARFP IS INVALID IN THIS MODE

Reason:
Someone attempted to issue the ARFP command, and the RESTART statement in the
initialization file does not have ARF=YES.

Action:
Use ARF=YES if you need to issue the ARFP command.

SPOG-00

Reply sent. Please verify job status thru the LQ command.

Reason:
A reply message has been sent to a system agent in response to an Intervention
Required condition for a job that is attempting to execute on the agent platform.

Action:
Monitor the job through the LQ or other queue inquiry commands to ensure the job's
status changes from W-REPLY.

1582 Message Reference Guide

 SPOx

SPOG-01

Invalid or missing data for field xxxxxxxx

Reason:
The indicated required field is either missing or contains invalid data.

Action:
Perform the following actions:
■ Correct the field.
■ Retry the command.

SPOG-02

No agent job environment exists

Reason:
CA Workload Automation SE has been started with the agent job feature disabled.

Action:
Perform the following actions:
■ Enable the agent job feature at the site by coding AGENTJOB=YES on the XPDEF
initialization file statement.
■ Cycle CA Workload Automation SE.
■ Contact your installation specialist for assistance.

SPOG-03

IAS not active or not initialized

Reason:
CA Integrated Agent Services (CA IAS) is not supported or has not been initialized
correctly.

Action:
Perform the following actions:
■ Check CA Workload Automation SE start-up messages for IAS-related errors.
■ Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1583

SPOx

SPOG-04

LOAD failed for module SASSAFM2

Reason:
Unable to access the common agent command module.

Action:
Perform the following actions:
■ Make sure SASSAFM2 is in a library accessible from CA Workload Automation SE.
■ Issue the /DISPLAY,A=SASSAFM2 command to ensure that an entry is in the
application directory for the module.

SPOG-05

text

Reason:
The common agent command module, SASSAFM2, returned an error. The message
contains the text of the error.

Action:
Take action depending on the text in the message.

SPOG-06

Error retrieving ACTQ xxxxxxxx Segment

Reason:
An error occurred while trying to retrieve the indicated segment from the ACT queue.
The segment type is either HEADER or AGENT.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

Verify that you have entered the correct CA 7 WA job number. If necessary, reenter the
correct job number or contact your installation specialist for assistance.

1584 Message Reference Guide

 SPOx

SPOG-07

ACTQ xxxxxxxx segment not found

Reason:
The indicated segment is not found on the ACT queue. The segment type is either
HEADER or AGENT.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

SPOG-08

CA7AGNT VSAM JNO record does not contain a JobId

Reason:
The CA 7 WA job number entered does not contain a JobId on the CA7AGNT VSAM file
JNO (job number) record.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1585

SPOx

SPOG-09

xxxxxxxx is not valid for the Agent Job Type

Reason:
The command (xxxxxxxx) entered is not valid for the Agent Job Type associated to the
job.

Action:
Perform one of the following actions:
■ Check the command in the Command Reference Guide to determine the applicable
Agent Job Types for this command.
■ Reenter a valid comand and job number combination.
■ Contact your installation specialist for assistance.

SPOG-10

This job is not waiting on a reply.

Reason:
The CA 7 WA job number entered is not waiting on a reply (that is, the status is not
W-REPLY).

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

SPOG-11

User uuuuuuuu replied to job jjjjjjjj(nnn) at agent aaaaaaaaaaaaaaaa

REPLY=text

Reason:
The CA Workload Automation SE user indicated in the message replied to an
'intervention required' message for the I5 agent job and agent name identified in the
message. The second line contains the reply data. This is an informational message.

Action:
None.

1586 Message Reference Guide

 SPOx

SPOG-12

CA7AGNT VSAM xxxxxxxx record not found

Reason:
The VSAM record key denoted by xxxxxxxx was not found on the CA7AGNT VSAM file.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

SPOG-13

Error retrieving CA7AGNT VSAM xxxxxxxx record

Reason:
An error occurred while trying to retrieve the VSAM record, denoted by xxxxxxxx, from
the CA7AGNT VSAM file.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1587

SPOx

SPOG-14

CA7AGNT VSAM JNO record does not contain an agent name

Reason:
The CA 7 WA job number entered does not contain an agent name on the CA7AGNT
VSAM file JNO (job number) record.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

SPOG-15

CA7AGNT VSAM JNO record does not contain a JobCount

Reason:
The CA 7 WA job number entered does not contain a JobCount on the CA7AGNT VSAM
file JNO (job number) record.

Action:
Verify that you have entered the correct CA 7 WA job number.

Perform one of the following actions:

■ Reenter the correct job number if necessary.
■ Contact your installation specialist for assistance.

SPOG-16

Invalid MODE Value, specify A or I

Reason:
When entering a JOBSTART command, the MODE= value was not A or I, which are the
only two valid values.

Action:
Reissue the JOBSTART command specifying the correct MODE= value (either A or I).

1588 Message Reference Guide

 SPOx

SPOG-20

xxxxxxx request sent to Agent

Reason:
A command (xxxxxxxx) was sent to an Agent to perform an action specified by the
command. For example, the JOBSTART command tells an SAP agent to begin running
the job specified in the request. This is an informational message only.

Action:
Issue the LQ command periodically to see whether the Agent has acted on the request.

SPOR-32

PRSCF UNSUCCESSFUL
RESOURCE : resource-name
NOT USED BY JOB xxxxxxxx

Reason:
This message indicates that the attempted PRSCF command failed because the resource
is not currently used by the job.

Action:
Use the RM.3 and RM.4 panels to confirm that the job is currently "using" the resource.

SPOR-34

PRSCF UNSUCCESSFUL
DELETE ERROR FOR RESOURCE : resource-name
FOR JOB xxxxxxxx

Reason:
An error has occurred attempting to access the VRM definitions for the indicated job.

Action:
If the error persists, contact your installation specialist for assistance.

Chapter 7: SLFA - SPOR Messages 1589

SPOx

SPOR-35

PRSCF SUCCESSFUL
RESOURCE : resource-name
FREED FOR JOB - xxxxxxxx

Reason:
The resource has been freed.

Action:
None.

SPOR-39

PRSQA SUCCESSFUL
CO-REQUISITE RESOURCE: resourcename
ACTIVATED

Reason:
The CRQ resource has been successfully activated.

Action:
None.

SPOR-40

PRSQD UNSUCCESSFUL
CO-REQUISITE RESOURCE: resourcename
NOT FOUND.

Reason:
This message indicates that the attempted PRSQD command failed because the
resource could not be found.

Action:
Make sure the correct resource name is used and retry the command.

1590 Message Reference Guide

 SPOx

SPOR-41

PRSQA SUCCESSFUL
CO-REQUISITE RESOURCE: resourcename
ALREADY ACTIVE

Reason:
This message indicates that the resource is already active.

Action:
None.

SPOR-42

CRQ SENT TO CA7n: PRSQx,RSRC=cccc...cccc

Reason:
An activation or deactivation command is successfully propagated to another instance,
CA7n. This message indicates the command is successfully queued to the trailer chain of
the target instance. The message does not mean that the target instance has received
and processed the command.

Action:
None.

SPOR-43

UNABLE TO FIND ICMDSECT FOR CA7n

Reason:
CA 7 attempted to propagate a PRSQA or PRSQD command to another instance (CA7n)
but cannot find the instance control block (ICMDSECT) for that instance.

Action:
Perform the following actions:
■ Confirm that the target instance is initialized by CAIRIM on the local LPAR.
■ Execute the AL2ENVR report.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 7: SLFA - SPOR Messages 1591

SPOx

SPOR-44

CRQ SEND FAILED; CA7n TRAILER NOT BLOCKED

Reason:
CA 7 attempted to propagate a PRSQA or PRSQD command to another instance, but the
receiving instance did not support trailer blocking.

Action:
Update this instance to use the TRLBLK(Y) option through the CAIRIM CA 7 system
configuration file on all LPARs that have this instance defined.

SPOR-45

CRQ SEND FAILED FOR CA7n; R15=xxxxxxxx

Reason:
CA 7 attempted to propagate a PRSQA or PRSQD command to another instance. An
error occurred while trying to add the command to the CSA trailer chain. The return
code from the SVC call is xxxxxxxx.

Action:
Perform the following actions:
■ Execute the AL2ENVR report.
■ For assistance, contact CA Support at http://ca.com/support.

SPOR-53

COREQUISITE PROPAGATION REQUEST SUCCESSFUL

Reason:
The activation/deactivation command has been successfully propagated to other CA 7
instances. A status message is written to the Browse data set for each instance that is
receiving propagated commands. This message indicates the command has been
successfully queued to the trailer chain of the target instance. The message does not
mean that the target instance has received and processed the command.

Action:
None.

1592 Message Reference Guide

 SPOx

SPOR-54

COREQUISITE PROPAGATION REQUEST FAILED

Reason:
The activation or deactivation propagation has failed for one or more instances. A status
message is written to the Browse data set for each instance receiving propagated
commands.

Action:
Perform the following actions:
■ Check the Browse log for failure messages.
■ Verify that the destination instance is initialized with CAIRIM on the local LPAR.
■ For assistance, contact CA Support at http://ca.com/support.

Chapter 7: SLFA - SPOR Messages 1593

Chapter 8: SPO0 - XTRK Messages
This chapter contains the SPO0 through XTRK messages.

SPO0 Through SPO9

This section contains the SPO0 through SPO9 messages.

SPO0-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The input request completed successfully.

Action:
None.

SPO0-01

UNRECOGNIZABLE KEYWORD FOUND

Reason:
Self-explanatory.

Action:
Perform the following actions:
■ Check for a misspelled keyword.
■ Correct and resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1595

SPO0 Through SPO9

SPO0-02

xxxxxxxx INVALID OR MISSING

Reason:
Keyword xxxxxxxx is incorrect or is required but was not supplied.

Action:
Correct and resubmit the command. If the keyword is DATE and the SSCAN command is
being used, check to see if you are trying to set the DATE forward without first setting it
to zero.

SPO0-03

REQUIRED KEYWORD MISSING

Reason:
A required keyword has been omitted.

Action:
Correct and resubmit the command.

SPO0-04

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid or does not pertain to the request.

Action:
Correct and resubmit the command.

SPO0-05

PROGRAM ERROR, WIP=xx

Reason:
A CA Workload Automation SE program error has occurred. The Where-In-Program
(WIP) location of the error is indicated by xx.

Action:
Contact your installation specialist for assistance.

1596 Message Reference Guide

 SPO0 Through SPO9

SPO0-06

JOB NOT FOUND IN REQ/Q

Reason:
The job number specified on input was not found in the request queue.

Action:
Verify that the proper job number was specified; if not, correct and resubmit the
command.

SPO0-07

REQUIREMENTS SCAN INCOMPLETE

Reason:
Requirements Scan is still in the process of determining the job's requirements.

Action:
Wait a few minutes, and then resubmit the command. If the message persists and no
other pertinent messages can be found on the Master Station, contact your installation
specialist for assistance.

SPO0-08

Q ANALYSIS INCOMPLETE

Reason:
Schedule Scan is still in the process of adding the job to the queue.

Action:
Wait a few minutes, and then resubmit the command. If the message persists and no
other pertinent messages can be found on the Master Station, contact your installation
specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1597

SPO0 Through SPO9

SPO0-12

INPUT RECEIVED FROM JOB=xxxxxxxx,STEP=xxxxxxxx ***TRAILER STEP***

Reason:
The message notifies the Master Station that CA Workload Automation SE has received
input from a Trailer Step.

Action:
None.

SPO1-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The HOLD or RELEASE function was completed without errors. The action field contains
one of the following:
■ HELD - The requested job is being held.
■ RELEASED - The requested job has been released.
■ NOT HELD - An attempt was made to release a job not being held.
■ ALREADY HELD - An attempt was made to hold a job that is already being held.
■ HELD BY JOB - The job was held on an individual basis. A RELEASE QUEUE does not
cause it to be released.
■ JOB ALREADY SUBMITTED - The HOLD is ignored for this job because it is already
submitted.
■ NO STATION IN PROCESS - All workstations in the network that logged in have also
logged out. The network can no longer be held.
■ RQMTS SCAN REQUIRED - Requirements Scan has not completed determination of
the job's requirements.
■ Q ANALYSIS INCOMPLETE - Schedule Scan is still in the process of adding entries to
the queue.

Action:
Only the last two messages above require action. In both cases, wait a few minutes, and
then resubmit the command. If the message persists, contact your installation specialist
for assistance.

1598 Message Reference Guide

 SPO0 Through SPO9

SPO1-03

xxxxxxxx INVALID

Reason:
Keyword xxxxxxxx is invalid or missing.

Action:
Correct and resubmit the command.

SPO1-04

REQUIRED KEYWORD MISSING

Reason:
A required keyword was not specified on input.

Action:
Correct and resubmit the command.

SPO1-05

I/O ERROR, RC = xxxx

Reason:
An I/O error occurred while accessing the queues.

Action:
Contact your installation specialist for assistance.

SPO1-06

JOB/STATION NOT FOUND

Reason:
The required job or workstation entry was not found in the queue.

Action:
Verify that the job or workstation number was specified correctly. If not, correct and
resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1599

SPO0 Through SPO9

SPO2-00

xxxxxxxx FUNCTION SUCCESSFUL REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input request has been completed successfully.

Action:
None.

SPO2-01

REQUIRED KEYWORD MISSING

Reason:
A keyword required for the function was omitted from the input.

Action:
Correct and resubmit the command.

SPO2-02

xxxxxxxx INVALID

Reason:
Keyword xxxxxxx is invalid or was omitted.

Action:
Correct and resubmit the command.

SPO2-03

STATION HAS BEEN PREVIOUSLY LOGGED IN

Reason:
An attempt was made to log in the status of a workstation that has already been logged
in.

Action:
Verify that input parameters were specified correctly. If correct, no action is required; if
not, correct and resubmit the command.

1600 Message Reference Guide

 SPO0 Through SPO9

SPO2-04

NOT LOGGED OUT OF PREVIOUS STATION

Reason:
An attempt was made to log in a workstation before the preceding workstation had
logged out.

Action:
Check to see why the preceding workstation has not logged out.

SPO2-05

ASSOCIATED JOB HAS NOT COMPLETED NORMALLY

Reason:
An attempt was made to log in a workstation in the Postprocess queue. The job that
produces the work for that workstation has not executed or it abended during
execution.

Action:
Verify that the input command was correct. If input is accurate, check the status of the
job. If the command is invalid, correct and resubmit. A log in can be forced by specifying
FORCE=YES.

SPO2-06

STATION HAS NOT BEEN LOGGED IN

Reason:
An attempt was made to log out a workstation before that workstation had logged in.

Action:
Verify that the input command was correct. If it was, the station must first be logged in
before it can be logged out. If not, correct and resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1601

SPO0 Through SPO9

SPO2-07

I/O ERROR, RC=xxx

Reason:
An I/O error was encountered while attempting to access the CA Workload Automation
SE queues.

Action:
Resubmit the command. If the error recurs, contact your installation specialist for
assistance.

SPO2-08

Q ANALYSIS INCOMPLETE

Reason:
Schedule Scan has not finished building the queue records for the requested job.

Action:
Wait a few minutes before trying the JCL request again. If the problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SPO2-09

JOB/STATION NOT FOUND

Reason:
The requested job or workstation was not found in the Preprocess or Postprocess
queue.

Action:
Verify that the input command was correct. If not, correct and resubmit. If it was, verify
the job/workstation schedules.

1602 Message Reference Guide

 SPO0 Through SPO9

SPO2-10

JOB HELD

Reason:
An attempt was made to log out a workstation. The job associated with the workstation
activity has been held in the CA Workload Automation SE queue. The job must be
released before the workstation can be logged out.

Action:
Determine why the job is being held. If the reason for the hold has been satisfied,
release the job and then log out the workstation.

SPO2-11

STATION ALREADY LOGGED OUT

Reason:
An attempt was made to log out a workstation that has already been logged out.

Action:
Verify that the input was correct. If it was, no action is required. If not, correct and
resubmit the command.

SPO3-00

RESPONSE TO PROMPT ACKNOWLEDGED REQUEST COMPLETED AT hh:mm:ss ON

yy.ddd

Reason:
Response to a prompt has been acknowledged. No further prompting occurs.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1603

SPO0 Through SPO9

SPO3-01

Q FILE I/O ERROR, RC=xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
Resubmit the command. If the error recurs, contact your installation specialist for
assistance.

SPO3-02

REQUIRED KEYWORD MISSING

Reason:
A required keyword was omitted from the input.

Action:
Correct and resubmit the command.

SPO3-03

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid or missing.

Action:
Correct and resubmit the command.

SPO3-04

JOB/STATION NOT FOUND

Reason:
The requested job or workstation was not found in the specified queue.

Action:
Verify that the input was correct. If not, correct and resubmit the command.

1604 Message Reference Guide

 SPO0 Through SPO9

SPO3-05

Q ANALYSIS INCOMPLETE

Reason:
Schedule Scan has not completed building the queue records for the requested job.

Action:
Wait a few minutes, and then resubmit the command. If the problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SPO3-06

REQUIREMENTS SCAN INCOMPLETE

Reason:
Schedule Scan (Requirements Scan modules) has not completed determination of the
requested job's requirements.

Action:
Wait a few minutes before trying the request again. If the problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SPO3-07

NO PROMPT HAS BEEN RECEIVED

Reason:
An attempt was made to acknowledge a prompt when no prompt was issued.

Action:
Verify that the input was correct. If it was, no action is required. If not, correct and
resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1605

SPO0 Through SPO9

SPO4-00

cccccccc SUCCESSFUL FOR JOB xxxxxxxx (nnnn)

(DSN= x...x)
(DEPJOB=yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input requirements have been satisfied or the job dependency has been added
successfully according to the command indicated by cccccccc.

Action:
None.

SPO4-01

xxxxxxxx INVALID OR MISSING

Reason:
Keyword xxxxxxxx is invalid or was not included in the input.

Action:
Correct and resubmit the command.

SPO4-02

xxxxxxxx INVALID

Reason:
Keyword xxxxxxxx is invalid.

Action:
Correct and resubmit the command.

1606 Message Reference Guide

 SPO0 Through SPO9

SPO4-03

CONFLICTING KEYWORDS SPECIFIED

Reason:
Mutually exclusive keywords were specified on the input request.

Action:
Correct and resubmit the command.

SPO4-04

JOB xxxxxxxx NOT FOUND IN REQ/Q

Reason:
The job name or job number specified on the input command was not found in the
request queue.

Action:
Perform the following actions:
■ Verify the job name or job number.
■ Correct and resubmit the command.

SPO4-05

POST UNSUCCESSFUL FOR JOB xxxxxxxx(nnnn)

(DSN= x...x)
(DEPJOB=yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUIREMENT NOT FOUND

Reason:
An attempt was made to post the availability of a data set or the completion of a job.
The data set or job dependency indicated is not a requirement for the job being posted.

Action:
Verify the input. Correct and resubmit the command if necessary. If it is a user
requirement that you are trying to post, check to be sure that the input does not
contain a parenthesis, comma, or an apostrophe. If it does, an online POST using the
QM.2 (XRQ) panel needs to be done.

Chapter 8: SPO0 - XTRK Messages 1607

SPO0 Through SPO9

SPO4-06

POST UNSUCCESSFUL FOR JOB xxxxxxxx(nnnn)

(DSN= x...x)
(DEPJOB=yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUIREMENT ALREADY POSTED

Reason:
The requirement being posted has already been satisfied.

Action:
Verify the input. If necessary, correct and resubmit the command.

SPO4-07

POST UNSUCCESSFUL FOR JOB xxxxxxxx (nnn)

(DSN= x...x)
(DSN IS NOT INTERNAL)

Reason:
INTERNAL=YES was specified when attempting to post the availability of a data set. The
data set specified is not internal.

Action:
Verify the data set name. If correct, resubmit the command omitting INTERNAL=YES.

SPO4-08

POST UNSUCCESSFUL FOR JOB xxxxxxxx (nnnn)

(DSN= x...x)
(DSN IS NOT EXTERNAL)

Reason:
INTERNAL=YES was not specified when attempting to post the availability of a data set.
The data set specified is internal.

Action:
Verify the data set name. If correct, resubmit the command with INTERNAL=YES
specified.

1608 Message Reference Guide

 SPO0 Through SPO9

SPO4-11

I/O ERROR, RC= xxx

Reason:
An I/O error occurred while trying to access the CA Workload Automation SE queues.

Action:
Resubmit the command. If the error persists, contact your installation specialist for
assistance.

SPO4-12

POST UNSUCCESSFUL
JOB=xxxxxxxx -- MULTIPLE ENTRIES FOUND IN REQ/Q

Reason:
An attempt was made to post a job in the request queue by job name. No post was
done because multiple entries were found for the job name specified.

Action:
Perform the following actions:
■ Determine the 4-digit CA Workload Automation SE job number of the entry to be
posted.
■ Resubmit the command using that number to identify the job.

Chapter 8: SPO0 - XTRK Messages 1609

SPO0 Through SPO9

SPO4-15

INVALID ADDRQ/POST - JOB IN xxxxxxxx STATUS

Reason:
An ADDRQ or POST command was issued before all requirements for the job were
attached. The ADDRQ or POST cannot be done until requirements for the job are
successfully attached; that is, the job is not in SKELETON or RQMT-INC status. Where:
■ xxxxxxxx = SKELETON or RQMT-INC

If xxxxxxxx equals SKELETON, the JCL has not been attached. When xxxxxxxx=SKELETON,
the status on an LQ display may be either SKELETON or RETRY. If xxxxxxxx equals
RQMT-INC, the initial job requirements have not been attached.

Action:
Wait a few minutes, and then try the ADDRQ or POST command again. If it still does not
work, check Master Station messages (Browse data set) to determine why the JCL or the
requirements are not attached. The job may have to be canceled and manually
demanded.

SPO5-00

xxxxxxxx FUNCTION SUCCESSFUL

Reason:
The input request completed successfully.

Action:
None.

SPO5-01

CA-7 IDS AND SYSTEM CATALOG IN AGREEMENT

Reason:
A consolidation of the system catalog and the CA Workload Automation SE IDS was
requested. The two catalogs match for the data set specified. No action is taken.

Action:
None.

1610 Message Reference Guide

 SPO0 Through SPO9

SPO5-02

ERROR IN INPUT DATA

Reason:
An error was detected in the parameter list passed to SASSSCTU.

Action:
Correct and resubmit the command.

SPO5-03

IDS INCONSISTENT WITH REQUEST

Reason:
An attempt was made to delete or replace an entry that does not exist in the CA
Workload Automation SE IDS.

Action:
Verify the input request. If necessary, correct and resubmit the command.

SPO5-04

ENTRY IS TOO LARGE FOR EXISTING STRUCTURE

Reason:
The CA Workload Automation SE IDS contains entries for the three most current
versions of a data set. The entry structure can control up to 251 volumes for the three
versions. This input request exceeded this number.

Action:
Verify that the input request is correct. If it is, the request cannot be honored due to the
large number of volumes. If not, correct and resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1611

SPO0 Through SPO9

SPO5-05

DSN NOT FOUND IN CA-7 IDS, RC=xxx

Reason:
The data set name that is specified on input could not be located in the CA Workload
Automation SE IDS. The return code from the LOCATE is xxx.

Action:
Verify that the data set name in the input request is correct. If it is, contact your
installation specialist for assistance. If not, correct and resubmit the command.

SPO5-06

DSN NOT FOUND IN SYSTEM CATALOG, RC=xxx

Reason:
The data set name specified on the input request could not be located in the system
catalog. The return code from the LOCATE is xxx.

Action:
Verify that the data set name specified in the input request is correct. If it is, it may be
necessary to catalog the data set on the system catalog.

SPO5-07

UPDATE ERROR, RC=xxx

Reason:
An error was encountered when attempting to update the IDS entry for the data set.
The return code from the IDS is xxx.

Action:
Check the return code. Enlarging the CA Workload Automation SE IDS is sometimes
necessary.

1612 Message Reference Guide

 SPO0 Through SPO9

SPO5-08

NOT ENOUGH AVAILABLE MEMORY

Reason:
Not enough core was available to process the input request.

Action:
Resubmit the command. If the error recurs, it may be necessary to increase the region
size for CA Workload Automation SE.

SPO5-09

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx was invalid or was required but omitted from the input request.

Action:
Correct and resubmit the command.

SPO6-00

JOB xxxxxxxx(nnnn) HAS BEEN CANCELED [AND CMT CLEARED]

[-*WARNING* CMT NOT CLEARED]
[REASON IGNORED] [,] [PLEASE VERIFY 'NEXT-RUN' PREDECESSOR VALUES]

Reason:
The request to cancel a CPU job was successful. If noted, the CA WA Restart Option CMT
was cleared to prevent erroneous restarts. If a job is canceled after being submitted, but
is still in the active or ready queue, the CMT is not cleared and this may need to be done
manually.

If REASON= is used for the cancel, and the initialization file CANCEL statement is used
with REASON=NO, then the REASON IGNORED shows.

If the cancel is done by number (nnnn), any network records (PREQ/PSTQ) are also
canceled. If there are NEXT-RUN values to check, this is indicated.

Action:
If the job being canceled was in the active queue, or had been submitted and was in the
ready queue, an OS cancel is also required to terminate execution.

Chapter 8: SPO0 - XTRK Messages 1613

SPO0 Through SPO9

SPO6-00

JOB CANCELED FROM PRE-PROCESS 'Q' JOB=xxxxxxxx, NW=yyyyyyyy

Reason:
The request to cancel preprocess work completed successfully.

Action:
None.

SP06-00

RECORDS DELETED FROM POST-PROCESS 'Q', FOR JOB= xxxxxxxx(nnnn) [,NW=

yyyyyyyy] [,SUBID= zzzzzzzz]

Reason:
The request to cancel postprocess work completed successfully.

Action:
None.

SPO6-02

INVALID OR OMITTED VALUE FOR: xxxxxxxx

Reason:
Keyword xxxxxxxx is invalid or is required but was omitted from the input request.

Action:
Correct and resubmit the command.

SPO6-03

NO QUEUE RECORDS FOUND

Reason:
No records were found in the CA Workload Automation SE queues for the job name
specified on the input request.

Action:
Verify that the job name was specified correctly. If it was, no action is required since the
job has already been canceled. If not, correct and resubmit the command.

1614 Message Reference Guide

 SPO0 Through SPO9

SPO6-04

JOB IS IN 'SKELETON' STATUS

Reason:
Either Schedule Scan is still in the process of adding the job to the CA Workload
Automation SE queue or the job had some type of error when it entered the queue.

Action:
Wait a few minutes before trying the request again if Schedule Scan is still active. If the
problem persists for an extended period, look for messages concerning this job on the
Master Station. If Schedule Scan is not still active, reenter with FORCE=YES. This
message also may be produced for jobs with a status of RETRY on an LQ display. If
unable to resolve the problem, contact your installation specialist for assistance.

SPO6-05

REQUIREMENTS SCAN INCOMPLETE

Reason:
Schedule Scan (Requirements Scan modules) is still in the process of determining the
job's requirements.

Action:
Wait a few minutes before trying the JCL request again. If the problem persists for an
extended period, look for messages concerning this job on the Master Station. If unable
to resolve the problem, contact your installation specialist for assistance.

SPO6-06

QUEUE FILE I/O ERROR, RC= xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
Resubmit the command. If the error persists, contact your installation specialist for
assistance.

Chapter 8: SPO0 - XTRK Messages 1615

SPO0 Through SPO9

SPO6-07

CANNOT CANCEL '*CRDLOAD'

Reason:
An attempt was made to cancel *CRDLOAD from the request queue. This is not allowed.

Action:
None.

SPO6-08

MUST REQUEUE OR USE FORCE=YES

Reason:
Cancel was requested for a job in the ready or active queue, but the CA WA Restart
Option interface is installed. Since the interface could cause the CA WA Restart Option
database entry for this job to be reset, the job should be requeued before canceling.

Action:
Consider the following actions:
■ If the job is active or submitted to a CPU, use OS or JES cancel commands to purge it
from the host system. This prevents duplicate runs.
■ If the job is not active or submitted, the host CPU is (or has been) down, or the job
does not use CA WA Restart Option, use the FORCE=YES option to issue the
CANCEL.

SPO6-09

RESOURCE CHANGE COMPLETE

Reason:
The request to free tape drives has been successfully completed. The RESCHNG
command may have been issued in a Trailer Step.

Action:
None.

1616 Message Reference Guide

 SPO0 Through SPO9

SPO6-10

***ATTENTION*** STATION= xxx...x (nn)

FURTHER PROCESSING HAS BEEN CANCELLED FOR: REF #nnn...n
JOB= xxxxxxxx,NW= yyyyyyyy [,SUBID= zzzzzzzz]

Reason:
This message is sent to all workstations that have not completed their processing for the
job being canceled.

Action:
None.

SPO6-10

*** ATTENTION *** JOB xxxxxxxx (nnnn) HAS BEEN CANCELED

Reason:
This message is sent to the appropriate logical terminal to notify personnel of the
canceled job.

Action:
None.

SPO6-11

CANNOT CANCEL - LOAD NOT COMPLETE

Reason:
An attempt was made to cancel a job that is in the request queue and is currently going
through LOAD processing.

Action:
Wait a few minutes and try again. If the message persists and the job must be canceled
before LOAD completion processing finishes, use the top line CANCEL command with
the FORCE=YES option.

Note: This may cause invalid job data to be added to the database. It is best to wait for
the LOAD to complete before canceling the job.

Chapter 8: SPO0 - XTRK Messages 1617

SPO0 Through SPO9

SPO6-12

CANNOT CANCEL JOB=xxxxxxxx - DUPLICATE JOBNAMES

Reason:
An attempt was made to cancel a job by job name, but more than one entry in the
request queue has that name. The job name entered is indicated by xxxxxxxx.

Action:
Reissue the CANCEL command using the CA 7 WA job number instead of the job name.

SPO6-13

REASON FOR CANCELING IS REQUIRED

Reason:
An attempt was made to cancel a job, but a reason was not supplied.

Action:
Issue the command again with the REASON parameter specifying the reason for the
cancel.

SPO6-14

CANNOT CANCEL - JOB IN COMPLETION STATUS

Reason:
An attempt was made to cancel a job that completed and is in CA Workload Automation
SE completion processing or waiting for CA Workload Automation SE completion
processing.

Action:
Wait a short time, and the job should finish completion processing (clearing the request
queue). If the job must be canceled, use the top line CANCEL command with the
FORCE=YES option.

1618 Message Reference Guide

 SPO0 Through SPO9

SPO6-15

CANNOT CANCEL - CONNECTED RESOURCES. USE FORCE=YES.

Reason:
The job cannot be canceled because it still holds VRM resources.

Action:
Perform one of the following actions:
■ Use the PRSCF command to release the resources.
■ Use the FORCE=YES option.

SPO6-16

UNABLE TO CANCEL, ARF RECOVERY IN PROGRESS

Reason:
This message is issued when a CANCEL is attempted while ARF is controlling recovery for
a job.

Action:
Wait until ARF recovery is complete for the job. The LARFQ command can be used to
track the progress of ARF recovery for the job.

If the CANCEL must be issued prior to the completion of ARF recovery, use the ARFP
command to terminate ARF recovery processing for the job. After the ARFP command
processing is complete, the CANCEL may be issued.

SPO6-17

JOB xxxxxxxx (nnnn) WAS SET TO REPEAT

Reason:
The specified job was canceled (see previous SPO6-10 message). The job was set to
repeat but is not repeated because it was canceled.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1619

SPO0 Through SPO9

SPO7-00

JOB xxxxxxxx (nnnn) ADDED TO THE REQ/Q BY yyyyyyy

[*** JOB TRIGGERING WILL BE BYPASSED ***]
[*** CA7 DATABASE UPDATES BYPASSED ***]
[*** NEXT SCHEDULED CYCLE WILL BE SKIPPED ***]
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The job specified by xxxxxxxx has been successfully added to the request queue. The job
number assigned by CA Workload Automation SE is indicated by (nnnn). The command
used to bring the job into the request queue is indicated by yyyyyyyy. If the SET=NTR
option was specified, the trigger bypass message is displayed. If the SET=NDB option
was specified, the database update bypass message is displayed. If the SET=SKP option
was specified, the next scheduled cycle message is displayed.

Action:
None.

SPO7-01

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid or is required but was omitted from the input request. If
xxxxxxxx=SET and SET=SKP is specified, the job may not have a schedule or may not be
defined in the database. If xxxxxxxx=DATE, the value entered is incorrect or DATE may
have been entered without TIME or DOTM that is invalid. If xxxxxxxx=JCLID, be sure that
the job is not defined to CA Workload Automation SE on the DB.1 panel. If the job is
defined on the DB.1 panel, you cannot use the JCLID keyword on the DEMAND
command.

Action:
Correct and resubmit the command.

1620 Message Reference Guide

 SPO0 Through SPO9

SPO7-02

JOB xxxxxxxx NOT FOUND IN JOB DATA SET

Reason:
The requested job (member) may not have been found in the CA Workload Automation
SE Job data set.

Action:
Several conditions could cause this message to be issued:
■ Verify the job name specified on the input request. If it is invalid, correct and
reenter the command.
■ The Schedule statement may be missing from the initialization file and therefore
jobs cannot be submitted.
■ If there is a Schedule statement, check the HIJBNUM parameter. The high job
number may have been reached. If this is the case, CA Workload Automation SE
cannot add jobs (or networks) to the queue until a number becomes available or
the HIJBNUM value is increased. To increase the value, bring CA Workload
Automation SE down with a DMPQ, change the value in the initialization file, and
bring CA Workload Automation SE back up with a TYPE=COLD or MOVQ.
■ An operator may not have the correct user ID authorization to access the job.
■ The request queue does not have enough space to add the job.

SPO7-03

JOB xxxxxxxx IS LOCKED

Reason:
The requested job is in locked status.

Action:
Use the LLOCK command to determine why the job is locked and then correct. If the
schedule is locked, do a RESOLV on it. If the job is locked in LOAD status, use the LOAD
command to reload the job. If the LOAD is not successful, error messages are produced
at the appropriate CA Workload Automation SE terminal describing the problem.

Chapter 8: SPO0 - XTRK Messages 1621

SPO0 Through SPO9

SPO7-04

CONFLICTING INPUT PARAMETERS: xxxxxxxx / yyyyyyyy

Reason:
The command specified parameters that are mutually exclusive. The xxxxxxxx and
yyyyyyyy indicate the parameters in error.

Action:
Correct and reissue the command.

SPO7-05

KEYWORD MAINID= IS NOT VALID FOR INTERNAL CROSS-PLATFORM JOBS

Reason:
The MAINID= keyword was specified on DEMAND or RUN command for an internal
cross-platform job. The MAINID keyword is only valid jobs executing in the local CA
Workload Automation SE mainframe environment.

Action:
Resubmit the command without the MAINID keyword.

SPO7-07

xxxxxxxx ERROR RETURN, R15=yyyyyyyy

Reason:
A bad return code was received from the called module specified by xxxxxxxx.

Action:
If xxxxxxxx=SASSSFER and yyyyyyyy=04, an output network that is connected to a job
may not have a schedule or the NWKSCHID from the JOBCONN panel is incorrect. Use
DB.2.3 (SCHD,ONWK) to set up a schedule for the output network or correct the
NWKSCHID. If R15=04 an out of space condition may have been encountered in the
trailer queue.

1622 Message Reference Guide

 SPO0 Through SPO9

SPO7-08

I/O ERROR, RC=xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
If xxx=001, check to see if the job being DEMANDed processes correctly. It is possible
that schedule scan may have processed the job; if so, nothing else is needed. If the error
persists, contact your installation specialist for assistance.

SPO7-09

SCHEDULE SCAN POSTED TO DUMP xxxxxxxx LOG FILE

Reason:
A DEMAND(H) or RUN(H) command was issued for the job that is used to dump the log
file indicated by xxxxxxxx.

Action:
None.

SPO7-10

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',

DUE-OUT ON yy.ddd AT hhmm.
[*** CA7 DATABASE UPDATES BYPASSED ***]
[,DEPJOB=jobname2]

or

Chapter 8: SPO0 - XTRK Messages 1623

SPO0 Through SPO9

SPO7-10

JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q', [*** LOAD ONLY ***]
*** JCL RETRIEVED FROM SPECIAL OVERRIDE LIBRARY ***
DUE-OUT ON yy.ddd AT hh:mm.
[*** CA7 DATABASE UPDATES BYPASSED ***]
[,DEPJOB=jobname2]

Reason:
This message is sent to the CA Workload Automation SE Master Station to indicate that
a new job has been added to the request queue. If the JCL is retrieved from the special
JCL Override library of ID 254, it is indicated as such. The due-out date and time specifies
when CPU processing must be complete. If the job was a no database job (NDB), CA
Workload Automation SE database updating is bypassed. The DEPJOB requirement is
noted if one was specified.

Action:
None.

SPO7-11

SCHEDULE SCAN POSTED TO DUMP [(PRIMARY)|(SECONDARY)] LOG FILE

Reason:
The job (specified in the product's initialization file) that dumps a CA Workload
Automation SE Log data set has been manually demanded. The data set for which the
dump was requested is available and the job has been scheduled into the request
queue.

Note: Dump jobs are normally scheduled automatically.

Action:
None.

SPO7-12

REQUEST INVALID -- LOG FILE IS ACTIVE

Reason:
This message is generated when a DEMAND is done of a log dump job and that log is
active. The DEMAND is ignored.

Action:
None.

1624 Message Reference Guide

 SPO0 Through SPO9

SPO7-13

UNABLE TO ATTACH JCL (kkkk) - JOB xxxxxxxx

Reason:
When trying to add a job to the request queue, the JCL or parameters could not be
retrieved from the specified JCL/PARM data set. For some of the reason codes, a
detailed explanation of the specific error is displayed within a highlighted box following
this message. (See also the SCNJ-18 message for reason codes identified by kkkk.)
xxxxxxxx is the job name.

Action:
See message SCNJ-18.

SPO7-14

UNABLE TO ATTACH JCL FROM OVERRIDE LIB (kkkk) - JOB xxxxxxxx

Reason:
When trying to add a job to the request queue, the JCL could not be retrieved from the
specified JCL data set. For some of the reason codes, a detailed explanation of the
specific error is displayed within a highlighted box following this message. (See also the
SCNJ-18 message for reason codes identified by kkkk.) xxxxxxxx is the job name.

Action:
Verify the input command is correct. If it is, verify that the member name you want
exists in the special Override library. After detecting the problem, either SAVE or REPL
the JCL member in the special library. This is required to indicate to the Job data set that
on subsequent executions, JCL is to be retrieved from this special library.

SPO7-15

xxxxxxxx IS NON EXECUTABLE -- NOT ADDED TO REQUEST 'Q'

Reason:
A nonexecutable job cannot go through the CA Workload Automation SE load process.
For nonexecutable jobs, the LOAD process serves no purpose and can be ignored.

Action:
Perform one of the following actions:
■ Ignore the message.
■ Make the job executable and try again.

Chapter 8: SPO0 - XTRK Messages 1625

SPO0 Through SPO9

SPO7-16

SUBMIT DENIED BASED ON USERID IN JCL

Reason:
An attempt was made to DEMAND(H) or LOAD(H) a job and the jobs JCL contained a
USERID that the requester was not authorized to submit.

Action:
If security access should be allowed, contact your installation security administrator to
authorize the user to submit for the USERID that exists in the JCL.

SPO7-17

SUBMIT DENIED BASED ON JOB OWNER ID

Reason:
An attempt was made to DEMAND(H) or LOAD(H) a job and the requestor was not
authorized to submit for the USERID in the Job Owner field associated with the job.

Action:
If security access should be allowed, contact your installation security administrator to
authorize the user to submit for the USERID in the Job Owner field on the DB.1 panel.

SPO7-18

SUBMIT DENIED BASED ON UPDATER ID

Reason:
Someone replaced the QJCL for the job, but did not have the authority to submit for the
USERID in the Job Owner field on the DB.1 panel.

Action:
If security access should be allowed, contact your installation security administrator to
authorize the user to submit for the USERID in the Job Owner field on the DB.1 panel.

1626 Message Reference Guide

 SPO0 Through SPO9

SPO7-19

SUBMIT DENIED BASED ON GLOBAL ID

Reason:
An attempt was made to DEMAND(H) or LOAD(H) a job and the requestor was not
authorized to submit for the USERID associated with CA Workload Automation SE (the
Global ID).

Action:
If security access should be allowed, contact your installation security administrator to
authorize the user to submit for the USERID associated with CA Workload Automation
SE.

SPO7-20

CONFLICT IN JCLID AND JCLLIB FIELDS

Reason:
The JCL library for a job can only be specified by a JCLID or a JCLLIB, not both.

Action:
Specify either a JCLID or a JCLLIB and reenter.

SPO7-21

JOB NOT DEFINED AND JCLID/JCLLIB NOT SPECIFIED

Reason:
An attempt was made to DEMAND(H) or LOAD(H) a job and the job is not defined in the
CA Workload Automation SE database and no JCLID= or JCLLIB= keyword was specified
to indicate where the JCL for the job resides.

Action:
Confirm that the job name was entered correctly. If so, specify a valid JCLID= or JCLLIB=
keyword to indicate where the JCL should be retrieved from.

Chapter 8: SPO0 - XTRK Messages 1627

SPO0 Through SPO9

SPO7-22

REPEATING JOBS REQUIRE A SUBMIT TIME

Reason:
The INTERVAL keyword was specified, but the TIME keyword was not.

Action:
Correct the command and resubmit.

SPO7-23

REPEAT LOOP LASTS MORE THAN 24 HOURS

Reason:
The INTERVAL value times the COUNT value totals 1440 or more minutes (24 hours).

Action:
Correct the command and resubmit.

SPO7-24

ARF REQUIREMENT OVERRIDDEN WITH ARFSET=xxxxxxxx

Reason:
The ARF requirement for this job has been overridden.

Action:
None.

SPO7-25

ARF REQUIREMENT OVERRIDDE ERROR. JOB WILL RUN WITHOUT ARF OVERRIDE.

Reason:
An error occurred while attempting to override the ARF requirement for this job. The
job will run with its original ARF requirement.

Action:
None.

1628 Message Reference Guide

 SPO0 Through SPO9

SPO7-26

NO ARF RECOVERY WILL BE IN EFFECT FOR THIS JOB.

Reason:
The job was scheduled with ARFSET=**NONE** on the DEMAND or RUN command. No
ARF processing is performed.

Action:
None.

SPO7-27

JOB xxxxxxxx(nnnn) error

Reason:
An error occurred during ARF attach processing for this job.

Action:
None.

SPO7-28

TYPE=CLOCK, START, OR END REQUIRED FOR REPEATING JOBS

Reason:
The INTERVAL keyword was specified, but the TYPE keyword is missing.

Action:
Correct the command and resubmit.

SPO7-29

COMMAND IGNORED - LOAD NOT VALID FOR INTERNAL CROSS-PLATFORM JOBS

Reason:
Because internal cross-platform jobs have no JCL, there is no need to try to load JCL.

Note: The LOAD command is not valid for internal cross-platform jobs.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1629

SPO0 Through SPO9

SPO7-30

xxxxxxxx is an yyyyy JOB- NO yyyyy ENVIRONMENT EXISTS

Reason:
xxxxxxxx is the job name. CA Workload Automation SE has been started with the
cross-platform job feature disabled where yyyyy denotes the cross-platform job type
(Agent or XPJOB).

Note: For more information about the XPDEF statement, see the Systems Programming
Guide.

Action:
Enable the cross-platform job feature. Contact your installation specialist for assistance.

SPO7-31

xxxxxxxx FAILURE GETTING yyyyyyyy INFO SASSJOBR RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyyy (agent information for
agent jobs or node/executable information for XPJOBs) for cross-platform job xxxxxxxx.
As a result, cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SPO7-32

xxxxxxxx FAILURE GETTING yyyyyyyy INFO SASJE RC=xx

Reason:
CA Workload Automation SE was unable to access yyyyyyyyy (agent information for
agent jobs or node/executable information for XPJOBs) for cross-platform job xxxxxxxx.
As a result, cross-platform job xxxxxxxx is not executed.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

1630 Message Reference Guide

 SPO0 Through SPO9

SPO7-33

xxxxxxxx FAILURE ADDING yyyyyyyy SEGMENT EOF REACHED

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxx could not be added to the queue
because it is full.

Action:
Perform one the following actions:
■ Enlarge the queue if the queue if full.
■ Post existing jobs before processing additional requests.

Contact your installation specialist for assistance.

SPO7-34

xxxxxxxx FAILURE ADDING yyyyyyyy SEGMENT SQADD RC=xx

Reason:
The yyyyyyyyy segment (agent information for agent jobs or node/executable
information for XPJOBs) for cross-platform job xxxxxxx could not be added to the queue.

Action:
Note the message and return code provided, and contact CA Support at ca.com/support
for assistance.

SPO7-35

KEYWORD RMS= IS NOT VALID FOR INTERNAL CROSS-PLATFORM JOBS

Reason:
The RMS keyword was specified on DEMAND or RUN command for an internal
cross-platform job (no JCL). The RMS keyword is only valid for jobs containing JCL.

Action:
Resubmit the command without RMS keyword.

Chapter 8: SPO0 - XTRK Messages 1631

SPO0 Through SPO9

SPO7-36

KEYWORDS CC=/RO= ARE NOT VALID FOR AGENT JOBS

Reason:
The CC/RO keywords were specified on DEMAND or RUN command for an agent job.
These keywords are only valid for CPU or XPJOBs.

Action:
Resubmit the command without the CC/RO keywords.

SPO7-37

ARFSET NAME INVALID

Reason:
The ARFSET override must be a valid ARFSET name.

Action:
Correct the name or use ARFSET=**NONE** to bypass ARF processing for the job.

SPO8-00

SUBMIT TIME UPDATED FOR JOB nnnn REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The submit time has been successfully updated as requested.

Action:
None.

SPO8-01

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid or is required but was omitted from the input command.

Action:
Correct and resubmit the command.

1632 Message Reference Guide

 SPO0 Through SPO9

SPO8-02

SKELETON RECORD FOUND

Reason:
Schedule Scan is still in the process of building queue records for the requested job.

Action:
Wait a few minutes before trying the JCL request again. If the problem persists for an
extended period, look for messages concerning this job on the Master Station. This
message also may be produced for jobs with a status of RETRY on an LQ display. If
unable to resolve the problem, contact your installation specialist for assistance.

SPO8-04

JOB HAS ALREADY RUN

Reason:
An attempt was made to update the submit time for a job that has already run.

Action:
Verify the job name specified on the input request. If correct, no action is required. If
not, correct and resubmit the command.

SPO8-05

SUBTM IS NOT A REQUIREMENT

Reason:
An attempt was made to remove the submit time requirement for a job that does not
have submit time as a requirement.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1633

SPO0 Through SPO9

SPO8-06

JOB NOT FOUND IN REQ/Q

Reason:
The job specified on input was not found in the request queue.

Action:
Perform the following actions:
■ Verify the job name on the input request.
■ Correct and resubmit command if wrong.

SPO8-07

QUEUE FILE I/O ERROR, RC=xxx

Reason:
An I/O error occurred while attempting to access the CA Workload Automation SE
queues.

Action:
Resubmit the command. If the error recurs, contact your installation specialist for
assistance.

SPO9-00

REQUEST COMPLETE AT hh:mm:ss ON yy.ddd.

Reason:
The input request completed successfully.

Action:
None.

SPO9-01

xxxxxxxx - INVALID

Reason:
Keyword xxxxxxxx is invalid or is required but was omitted from the input request.

Action:
Correct and resubmit the command.

1634 Message Reference Guide

 SPRG Through SRC2

SPO9-02

JOB NOT FOUND IN xxx QUEUE

Reason:
The requested job was not found in the xxx queue.

Action:
Perform the following actions:
■ Verify the job name in the input request.
■ Correct and resubmit the command if wrong.

SPO9-03

SASSSQM7 ERROR RETURN, R15=xxxxxxxx

Reason:
An error was encountered while attempting to process the input request.

Action:
Contact your installation specialist for assistance.

SPRG Through SRC2

This section contains the SPRG through SRC2 messages.

SPRG-01

xx INVALID MACRO RETURN CODE-nnnnnnnn

Reason:
The SASSSPRG module has detected an error on return from a macro. The
Where-In-Program (WIP) value is specified by xx. The register 15 value (in hex) is
specified by nnnnnnnn. For an explanation of the nnnnnnnn values, see message
SCNJ-18.

If xx=4R and nnnnnnnn=1C, the JCL was saved in the Override library and has not been
defined on the DB.1 (JOB) panel, and SASSSPRG is trying to scratch the member in the
Override (254) library.

Action:
Contact your installation specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1635

SPRG Through SRC2

SPRG-02

JOB xxxxxxxx (nnnn) NOT FOUND. MAY HAVE BEEN CANCELED

Reason:
During a CA 7 WA job completion cycle, a job that was going through one of the
completion phases is no longer in the request queue. Generally no action is required.
The job was probably canceled.

Action:
None.

SPRG-16

JOB xxxxxxxx (nnnn) PURGED FROM REQUEST 'Q'.

Reason:
This message is issued to the CA Workload Automation SE Master Station to show jobs
that have been purged from the request queue.

Action:
None.

SPRG-17

JOB xxxxxxxx (nnnn) PURGED FROM REQUEST 'Q'.

*** JCL MEMBER DELETED FROM OVERRIDE LIBRARY ***

Reason:
This message is issued to the CA Workload Automation SE Master Station to show a job
purged from the request queue after its successful completion. It also indicates that the
JCL member used for executing the job has been deleted from the special JCL Override
library.

Action:
None.

1636 Message Reference Guide

 SPRG Through SRC2

SRC0-04

CONFLICTING INPUT PARAMETERS

Reason:
Mutually exclusive parameters were specified on the input request. Parameter pairs
that cannot be specified together are:
■ NW=keyword/JOB=keyword
■ PRINT function/JOB=keyword
■ PRINT function/NW=keyword
■ PRINT function/TEST=keyword
■ PRINT function/OLDYR=keyword
■ PRINT function/PRINT=keyword

Action:
Correct and resubmit the command.

SRC0-05

INVALID OR OMITTED xxxxxxxx DATA

Reason:
Parameter xxxxxxxx has been omitted or is invalid.

Action:
Correct and resubmit the command.

SRC0-06

INVALID GENERIC NAME OR NODE

Reason:
Either an NW node or a JOB generic name has been specified incorrectly.

Action:
Correct and resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1637

SPRG Through SRC2

SRC0-11

SECURITY VIOLATION

Reason:
The operator ID used in the /LOGON is not authorized for the function specified.

Action:
Change the Security macro for that operator ID in the security module if the operator is
to be authorized access to the specified function.

SRC0-12

*xxxxxxxx* IS AN INVALID FUNCTION

Reason:
The function specified by xxxxxxxx is invalid.

Action:
Correct and resubmit the command.

SRC0-13

INPUT DATA IS NULL

Reason:
No input command was available for processing.

Action:
Perform the following actions:
■ Supply sufficient data to process the request.
■ Resubmit the command.

1638 Message Reference Guide

 SPRG Through SRC2

SRC0-14

INPUT DATA IS INCOMPLETE

Reason:
Not enough data was available on the input command to process the request.

Action:
Perform the following actions:
■ Supply sufficient data to process the request.
■ Resubmit the command.

SRC0-15

TOO MUCH INPUT DATA

Reason:
Extraneous data was found on the input request.

Action:
Correct and resubmit the command.

SRC0-16

INVALID KEYWORD OR DATA IN INPUT

Reason:
An unrecognizable keyword was found in the input request.

Action:
Correct and resubmit the command.

Chapter 8: SPO0 - XTRK Messages 1639

SPRG Through SRC2

SRC0-17

INVALID DATA FOUND FOR FOLLOWING FIELDS: xxxxxxxxxxxxxxxx xxxxxxxx

Reason:
The keyword or name of the data found to be invalid is specified by xxxxxxxx. Invalid
data is:
■ Non-numeric data specified for a numeric parameter.
■ Nonalphabetic data specified for an alphabetic parameter.
■ Too much or too little data given for a parameter.
■ Invalid decimal point or sign (+/-) given for a parameter.

Action:
Correct and resubmit the command.

SRC1-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Reason:
The input request has been successfully completed. If TEST=YES was in effect, the
schedule members were not updated. Any schedule member for which resolution was
not completed due to errors was not updated as well.

Action:
None.

1640 Message Reference Guide

 SPRG Through SRC2

SRC1-01

aa INVALID SGET RETURN CODE=xx

Reason:
aa is the SGET statement where an error occurred. xx is the return code. If aa=20 and
xx=01, it indicates that no job member was found to correspond to the schedule
member being resolved.

Action:
Perform the following actions:
■ Determine which schedule member is in error by doing a LSCHD,DSNBR=SJ*
(through the Batch Terminal, if available).
The listing should stop at the last good schedule member.
■ Run the Database Verification program using the JOBSCHD parameter to identify
schedule errors.
■ Contact your installation specialist for assistance.

SRC1-02

(JOB=xxxxxxxx NOT FOUND)

(NW=xxxxxxxx NOT FOUND)
(NO JOB OR NETWORK SCHEDULES FOUND)

Reason:
The job or network specified on the input request cannot be found in the database.

Action:
Perform the following actions:
■ Verify that the job or network name was specified correctly.
■ Verify that the database contains at least one network, job schedule, or both.
■ Correct any discrepancies and resubmit the command.

For a JOB NOT FOUND message, run DBVR (Database Verification) to check for schedule
members missing. If any are found, you can use the DB.2.1 panel and do a DELETE for
the JOB. This will "clean up" a bad schedule pointer. If the job should have a calendar
schedule, it will have to be re-added.

Chapter 8: SPO0 - XTRK Messages 1641

SPRG Through SRC2

SRC1-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

Reason:
The module specified by xxxxxxxx failed to load.

Action:
Perform the following actions:
■ Verify that the module has not been inadvertently deleted from the CA Workload
Automation SE load library.
■ Verify that an APPLCTN statement exists for the module in either the initialization
file or in the SASSPROG module.
If the module is present, contact your installation specialist for assistance.

SRC1-100

NO SCHEDULES TO RESOLVE FOR SCAL= AND OLDYR= GIVEN

Reason:
RESOLVE command parameters are incorrect.

Action:
Perform the following actions:
■ Correct the SCAL and OLDYR parameters.
■ Reenter the RESOLVE command.

SRC1-101

nnnn SCHEDULES SELECTED FOR RESOLUTION

Reason:
The number of schedules selected for resolution is specified by nnnn. More information
regarding resolution activity for each schedule will follow this message.

Action:
None.

1642 Message Reference Guide

 SPRG Through SRC2

SRC1-102

xx SCRATCH SPACE EXHAUSTED

Reason:
Scratch work file space is insufficient for the amount of data selected using the specified
criteria. The location of the statement in the program being processed when space ran
out is specified by xx.

Action:
Perform the following actions:
■ Narrow the scope of the selection criteria to reduce the number of schedules
selected.
■ Redefine the selection criteria.
■ Resubmit the command.

SRC1-103

OUTPUT SCHEDULE MEMBER FOR NW= xxxxxxxx, DSNBR= SOvnnnnnn WITH

EXTRANEOUS ID OF zzz

Reason:
An output schedule member (identified by SOnnnnnn) has a schedule ID (zzz) that does
not appear in the associated job's schedule definition. The output schedule member is
for network xxxxxxxx.

Note: This error means no updating is done to the schedule member involved.

Action:
Perform one of the following actions:
■ Omit the extraneous ID in the output schedule.
■ Update the job schedule to include that ID.
The schedule may need to be deleted and readded.

Chapter 8: SPO0 - XTRK Messages 1643

SPRG Through SRC2

SRC1-104

OMITTED OUTPUT SCHEDULE ID OF zzz for NW=xxxxxxxx, DSNBR=SOnnnnnn

Reason:
An output schedule member (SOnnnnnn) does not have the schedule ID (zzz) defined in
the connected job's schedule member. The output schedule member is for network
xxxxxxxx. Output schedule definitions must have IDs that match the creating job's
schedule IDs.

Note: This error means no updating is done to the schedule member involved.

Action:
Perform one of the following actions:
■ Update the output schedule to include the omitted ID.
■ Remove the extra ID from the job schedule.

SRC1-105

SCHEDULE RESOLUTION COMPLETE FOR xxnnnnnn, [SCAL=yyyy]

(JOB=xxxxxxxx)
(NW=xxxxxxxx)

Reason:
Indicates successful completion of schedule resolution for schedule member xxnnnnnn.
If TEST=NO was in effect, the member has been updated. The xx portion of the schedule
member name is SI, SJ or SO for input, job and output, respectively; the nnnnnn portion
is the schedule number (assigned by CA Workload Automation SE). For SI and SJ
schedules, the SCAL information is shown. For SO and SI schedules, the network name is
shown.

Action:
None.

1644 Message Reference Guide

 SPRG Through SRC2

SRC1-106

OUTPUT SCHEDULE RESOLUTION STARTED

Reason:
This is an information only message indicating that output schedule resolution has
started for the job identified in the SRC1-110 message immediately preceding this
SRC1-106.

Action:
None.

SRC1-107

UNABLE TO COMPLETE RESOLUTION FOR xxnnnnnn, JOB=yyyyyyyy [,NW=zzzzzzzz]

,BECAUSE OF ABOVE ERRORS

Reason:
This message indicates that schedule resolution for xxnnnnnn has been terminated due
to errors. The errors are listed in the SRC1-nnn messages preceding this SRC1-107.

Action:
Perform the following actions:
■ Correct all indicated errors using Database Maintenance.
■ Rerun schedule resolution.

SRC1-108

INVALID RDAY

Reason:
The relative day specified in the schedule data is invalid in relation to the base calendar.
RDAY must not overlap into the preceding or following years for months other than
January or December.

Note: This error means no updating is done to the schedule member involved.

Action:
Perform the following actions:
■ Correct the error using Database Maintenance.
■ Rerun schedule resolution.

Chapter 8: SPO0 - XTRK Messages 1645

SPRG Through SRC2

SRC1-109

NO SCHEDULE DAYS FOR SCHEDULE DATA GIVEN

Reason:
After applying all schedule information to the specified base calendar, no schedule days
were found to exist.

Note: This is a warning only; the schedule member involved is updated unless other
critical errors are detected.

Action:
Perform the following actions:
■ Check for a definition with only "not day" (/) specified or for "not day" (/)
specifications that result in no schedule days being defined.
■ Correct the schedule data using Database Maintenance.
■ Rerun schedule resolution (RESOLV).

SRC1-110

*****SCHEDULE RESOLUTION STARTED FOR xxnnnnnn JOB= yyyyyyyy [,NW=xxxxxxxx]

*****

Reason:
This is an information only message indicating that schedule resolution has started for
member xxnnnnnn associated with job yyyyyyyy. If the schedule member is for an input
network (SI), the network name to which the schedule applies will also be shown.

Action:
None.

SRC1-111

**SCHEDULE DATA:

Reason:
This message marks the beginning of the schedule data for the member being resolved
as defined in the database. Resolution messages will follow the listing of schedule data.

Action:
None.

1646 Message Reference Guide

 SPRG Through SRC2

SRC1-112

mmmdd (DAY # nnn) FALLS ON A NON-SCHEDULE DAY, SCHEDULE DAY RETAINED

Reason:
The schedule day indicated by month (mmm) and day (dd, nnn) falls on a base calendar
nonschedule (nonprocessing) day. The ROLL option defined in the database schedule
entry specified that scheduling should occur on base calendar nonprocessing days (that
is, do not reschedule forward or backward).

Action:
Verify each of these days to ensure that scheduling on base calendar nonprocessing
days will produce the results you want. If schedule days are to stand as shown, no action
is required. If scheduling is to be bypassed or rolled (forward or backward), the schedule
member must be changed and resolved again.

SRC1-113

mmmdd (DAY # nnn) ROLLED [(FORWARD)|(BACKWARD)] TO xxxyy (DAY # zzz)

Reason:
The schedule day indicated by month (mmm) and day (dd, nnn) falls on a base calendar
nonprocessing day and has been rolled, forward or backward, to the base calendar
processing day indicated by month (xxx) and day (yy, zzz). If the day that is rolled from
or to is outside of the year's span that is resolved, the nnn or zzz value is zero. The ROLL
option in the database schedule entry specified that scheduling should be rolled
backward (ROLL=B) or forward (ROLL=F) to the next base calendar processing day.

Action:
Verify that each rolled schedule day should be rolled. If not, the schedule member must
be changed and resolved again.

SRC1-114

OUTPUT SCHEDULE RESOLUTION COMPLETED

Reason:
This is an information only message indicating that the resolution of a job's output
schedules are complete.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1647

SPRG Through SRC2

SRC1-115

mmmdd (DAY # nnn) FALLS ON A NON-SCHEDULE DAY, SCHEDULE DAY OMITTED

Reason:
The schedule day indicated by month (mmm) and day (dd, nnn) has fallen on a base
calendar nonschedule (nonprocessing) day. The ROLL option defined in the database
schedule entry specified that scheduling should be omitted on base calendar
nonprocessing days.

Action:
Verify each of these days to ensure that bypassing normal scheduling produces the
results you want.

SRC1-116

mmmdd (DAY # nnn) UNABLE TO FIND A ROLL DAY

Reason:
The schedule day indicated by month (mmm) and day (dd, nnn) has fallen on a base
calendar nonprocessing day. The ROLL option specified in the database schedule entry
was taken but no base calendar processing day could be found.

Note: This error means no updating is done to the schedule member involved.

Action:
Perform the following actions:
■ Change the schedule data.
■ Resolve the schedule again.

1648 Message Reference Guide

 SPRG Through SRC2

SRC1-117

(W) ID MULTIPLE SCHEDULES AT LEAST ONE DAY

Reason:
At least one day scheduled by this ID is also scheduled by one or more other IDs within
the schedule definition. Also, this message can be caused by the ROLL option forcing
one day's schedule to be rolled forward or backward matching another day's schedule
within the same ID. If DUPDATE=YES is specified on the RESOLV command, message
SRC1-137 will also be produced indicating the duplicate days.

Note: This is a warning only; the schedule member involved is updated unless other
critical errors are detected.

Action:
Verify that multiple processing of the job (or workstation activity) in one day will
produce the results you want. If not, the schedule member should be changed and
resolved again. It is possible, due to the way different calendars can be built, that the
multiply scheduled day is not within the forecastable time frame. Also, having calendars
for the previous year and the next year can sometimes alleviate this message. If this
does not, check to see if the job is scheduled more than once for the same day. To do
this, issue command FJOB,JOB=jobname,SPAN=8742 through the Batch Terminal
Interface and check the output. If the job does not forecast twice for the same day, this
situation may clear itself up with the next time frame's RESOLV.

SRC1-118

mmmdd (DAY # nnn) ROLLED [(FORWARD)|(BACKWARD)] TO xxxyy (DAY # zzz)

DAY IS ALREADY SCHEDULED BY THIS ID

Reason:
The schedule day indicated by month (mmm) and day (dd, nnn) has fallen on a base
calendar nonprocessing day. The ROLL option was exercised and a new base calendar
processing day was found, as indicated by month (xxx) and day (yy, zzz). If the day that is
rolled from or to is outside of the year's span that is resolved, the nnn or zzz value is
zero. However, the day rolled to is already scheduled by this ID.

Note: This error means no updating is done to the schedule member involved.

Action:
Determine if the job should be scheduled twice for the noted days; if so, another SCHID
must be used. If the ROLL day is valid, an additional ID must be included in the schedule
definition to allow for scheduling multiple runs on the same day. A "not day" (/)
specification must also be added to remove the original schedule day. The schedule
must again be resolved after all necessary changes are made.

Chapter 8: SPO0 - XTRK Messages 1649

SPRG Through SRC2

SRC1-119

mmmdd (DAY # nnn) IS A DUE-OUT DAY, JOB STARTS ON A NON-SCHEDULE DAY

Reason:
The due-out day indicated by month (mmm) and day (dd, nnn) is a base calendar
processing day. However, the lead time specified requires that the job be scheduled on
a previous nonprocessing day.

Action:
Verify the scheduling of workstation activities on nonprocessing days for the base
calendar referenced by the associated job. Valid processing days for workstation
activities may vary from what are considered valid processing days for the job. If this is
the case, a separate base calendar should be defined for the workstations and the
schedules should again be resolved.

SRC1-120

mmmdd (DAY # nnn) IS SCHEDULE DAY FOR STATION #01,

STATION#ss FALLS ON NON-SCHEDULE DAY xxxyy (DAY #zzz)

Reason:
The schedule day for workstation number ss falls on the base calendar nonschedule
(nonprocessing) day indicated by month (xxx) and day (yy, zzz).

Note: This is a warning only. The schedule member involved is updated unless other
critical errors are detected.

Action:
Verify the scheduling of workstation activities on nonprocessing days for the base
calendar referenced by the associated job. Valid processing days for workstation
activities may vary from what are considered valid processing days for the job. If this is
the case, a separate base calendar should be defined for the workstations and the
schedules should again be resolved.

1650 Message Reference Guide

 SPRG Through SRC2

SRC1-121

mmmdd (DAY # nnn) IS A DUE-OUT DAY FOR STATION # ss, WORK STARTS ON A
NON-SCHEDULE DAY

Reason:
The due-out day indicated by month (mmm) and day (dd, nnn) for workstation number
ss is a valid processing day in the base calendar. However, the lead time specified in the
schedule definition requires the work to begin on a nonprocessing day.

Action:
Verify the scheduling of workstation activities on nonprocessing days for the base
calendar referenced by the associated job. Valid processing days for workstation
activities may vary from what are considered valid processing days for the job. If this is
the case, a separate base calendar should be defined for the workstations and the
schedules should again be resolved.

SRC1-122

** OUTPUT SCHEDULE RESOLUTION STARTED FOR xxnnnnnn, NW-xxxxxxxx**

Reason:
This is an information only message indicating that resolution has started on the output
schedule member specified.

Action:
None.

SRC1-123

mmmdd (DAY # nnn) IS SCHEDULE DAY FOR STATION # ss, STATION # ss SCHEDULE
DAY IS NEXT YEAR

Reason:
The schedule day for station number ss falls into next year. CA Workload Automation SE
only maintains a schedule mask for one year at a time.

Note: This is a warning only. The schedule member involved is updated unless other
critical errors are found.

Action:
Verify that this schedule will produce the processing results you want. If this situation
presents a problem, the schedule definition should be changed to eliminate the day that
falls in the next year. The schedule must then be resolved again.

Chapter 8: SPO0 - XTRK Messages 1651

SPRG Through SRC2

SRC1-124

(W) mmmdd (DAY# nnn) IS DUE-OUT DAY, SUBTM IS FOR A NON-SCHEDULE DAY

Reason:
The due-out day indicated by month (mmm) and day (dd, nnn) is a valid processing day
in the base calendar. However, the submit time specified in the schedule definition will
cause the work to be submitted on a nonschedule day.

Note: This is a warning only. The schedule member involved is updated unless other
critical errors are detected.

Action:
Verify the scheduling and submit time specified. If submittal should not occur on a
nonschedule day, the schedule should be corrected and resolved again.

SRC1-126

(E) mmmdd (DAY # nnn) UNABLE TO ADJUST FOR INDEX DAYS

Reason:
An error has been detected during the attempt to process the index days.

Action:
Contact your installation specialist for assistance.

SRC1-134

JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss NOT AVAILABLE

Reason:
The job or network nnnnnnnn was not processed by this RESOLV command because the
calendar SCALyyss was not available to CA Workload Automation SE to be used.

Action:
Perform the following actions:
■ Check the initialization file to ensure that a CALBLK statement defines the calendar.
■ Ensure that the calendar is available in the load library or calendar library
referenced by CA Workload Automation SE.
■ If SCALyyss was being generated from a perpetual calendar PCALYYss member, the
SCALyyss calendar is not available because there was an error during the generation
process. Use the PRINT command or the LIST function of the CALMOD command to
display the specific error.

1652 Message Reference Guide

 SPRG Through SRC2

SRC1-135

JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss NOT LOADED

Reason:
The job or network nnnnnnnn was not processed by this RESOLV command because the
calendar SCALyyss was not loaded when this job was selected for RESOLV. This can occur
when a schedule definition is modified while a RESOLV command is executing.

Action:
Reissue the RESOLV command for this job or network.

SRC1-136

JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss DENIED BY

EXTERNAL SECURITY

Reason:
The job or network nnnnnnnn was not processed by this RESOLV command. The
external security system did not allow access to the calendar SCALyyss.

Action:
If appropriate, update the external security system to allow your operator ID access to
the calendar listed.

SRC1-137W

SCHEDULE IDS xxx AND yyy ARE BOTH SCHEDULED ON mmm dd

Reason:
This message is produced after SRC1-117 if the extended RESOLV message option is
enabled, or DUPDATE=YES is specified. A message is produced for each pair of schedule
IDs (for example, 001 and 002) that have scheduled the job/network to run on the same
day (for example, JUL 10).

Action:
See message SRC1-117.

Chapter 8: SPO0 - XTRK Messages 1653

SPRG Through SRC2

SRC2-00

COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The input request completed successfully.

Action:
None.

SRC2-02

UNABLE TO FETCH xxxxxxxx CLIO_RC=nn

text

Reason:
An error occurred while trying to retrieve the calendar named at xxxxxxxx. nn is the
return code from the SASSCLIO service. The text is an additional line of information
about the error.

Action:
Use the nn return code to determine your response.
04
Parameter list error. Contact your installation specialist for assistance.
08
SGETPDS error. SGETPDS is a CA Workload Automation SE service routine used for
PDS access. Contact your installation specialist for assistance.
12
Unexpected EOF on calendar PDS. Contact your installation specialist for assistance.
16
Load failed. The indicated calendar could not be located on the calendar PDS or in a
library in the STEPLIB concatenation. If the calendar is on the calendar PDS or in the
STEPLIB concatenation, contact your installation specialist for assistance.
28
Load failed because of the CALENDAR security checking.

1654 Message Reference Guide

 SSM0 Through SYS0

SRC2-07

LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Reason:
The module specified by xxxxxxxx failed to load. The return code from the SLOAD macro
is specified by nn.

Action:
Verify that the module has not been inadvertently deleted from the CA Workload
Automation SE load library and that there is an APPLCTN statement for it in the
initialization file or in the SASSPROG module. If present, contact your installation
specialist for assistance.

SSM0 Through SYS0

This section contains the SSM0 through SYS0 messages.

SSM0-AB

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO yyyyyyyy -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to yyyyyyyy (either an
internal reader or submit data set). MULTIJOB=REQUEUE was coded on the SECURITY
initialization statement and the JCL for the job contained multiple JOB statements.

Action:
Edit the JCL so that it contains only one JOB statement and restart the job.

SSM0-A5

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO yyyyyyyy -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to yyyyyyyy (either an
internal reader, submit data set, or agent name) due to an internal error. Message
SSM0-90 follows this message. This condition is encountered when CA Workload
Automation SE cannot update the security segment in the queues.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1655

SSM0 Through SYS0

SSM0-CC

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to cross-platform node
nodename. Either CAICCI has encountered an unrecoverable error, is not active, or the
node is in stopped or offline state in CA Workload Automation SE. Message SSM0-90
follows this message, which further explains the error.

Action:
Verify that the CAICCI environment is not having problems in sending. Verify that the
CAICCI environment is receiving data. If the second byte of the SSM0-90 EC= is 0C or 10,
the CA Workload Automation SE node is stopped or offline with no alternate nodes
defined. If the second byte of the SSM0-90 EC= is 04, the node is not available or the
CAICCI environment has problems. If the second byte of the SSM0-90 EC= is 18, the
internal CA Workload Automation SE tracker task (XTRK) is not active. Contact your
installation specialist. If CAICCI appears not to have any problems and the node is
online, report both this message and the subsequent SSM0-90 message to CA Support.
For assistance, contact CA Support at ca.com/support.

SSM0-C0

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO yyyyyyyy OUTPUT SUBTASK ENDED

PREMATURELY; REASON=cccccccc

Reason:
The job jjjjjjjj, whose CA 7 WA job number is nnnn was not submitted to yyyyyyyy
(either an internal reader or submit data set) due to an abend in the submit subtask.
The subtask abended with the code cccccccc.

Action:
Determine the type of abend by looking at the CA Workload Automation SE Online JES
job log. If a system abend, gather the JES job log, any supporting information and
contact CA Support at ca.com/support for assistance.

1656 Message Reference Guide

 SSM0 Through SYS0

SSM0-C1

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO yyyyyyyy UNABLE TO ATTACH OUTPUT SUBTASK;

REASON=cccccccc

Reason:
The job jjjjjjjj, whose CA 7 WA job number is nnnn was not submitted to yyyyyyyy
(either an internal reader or submit data set) because the subtask did not get attached
correctly. The ATTACH error codes are reflected in cccccccc.

Action:
Determine the type of error by looking at the CA Workload Automation SE Online JES
job log. If unable to detect the problem, gather the JES job log, any supporting
information and contact CA Support at ca.com/support for assistance.

SSM0-C4

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename/agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to the indicated
internal cross-platform node nodename or agentname. Storage could not be obtained
to build the buffer that is to be sent to the destination node. This message is followed
by SSM0-90.

Action:
Verify CA Workload Automation SE is not encountering other storage related abends. If
so, increase the region for CA Workload Automation SE and recycle. If this does not
resolve the problem, report both this message and the subsequent SSM0-90 message to
CA Support.

SSM0-C8

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to cross-platform node
nodename. The CCI SEND function encountered an error. This message is followed by
SSM0-90.

Action:
Ensure the CCI environment is not having problems in sending and receiving data. If CCI
appears to not have any problems, then report both this message and the subsequent
SSM0-90 message to CA Support.

Chapter 8: SPO0 - XTRK Messages 1657

SSM0 Through SYS0

SSM0-D0

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename/agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to the indicated
internal cross-platform node nodename or agentname. A parameter data error, driver
proc error, or invalid keyword specified in the PARMLIB occurred. This message is
followed by SSM0-90 which further explains the error.

Action:
Validate the internal cross-platform parameters by issuing a CA JCLCheck Workload
Automation command (LJCK) against the job. This should show errors as to why the job
is not getting submitted. If the second byte of message SSM0-90 EC= is one of the
following, take appropriate actions:
0C
Indicates a Driver Proc error. Verify valid DPROC usage
04
Indicates no storage for PARM data. Contact local CA Workload Automation SE
support to ensure CA Workload Automation SE is not having storage problems.
08
Indicates internal data error when trying to retrieve the parameters from storage.
1C
Indicates PARMnn where nn is not numeric.
10
Indicates a keyword exceeded eight characters in length. Check for valid keywords.
14
Indicates PARMnn error where nn is not specified or exceeds two bytes in length.
18
Indicates PARMnn length exceeds 256 bytes in length.
20
Indicates PARMnn where nn exceeds 64.
24
Indicates a keyword error, an unrecognizable keyword.
28
Indicates that a C-LANG statement exceeded 4 KB in size.

1658 Message Reference Guide

 SSM0 Through SYS0

30
Indicates an internal error. An invalid function was passed to the program that
builds the AFM.

SSM0-D4

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to cross-platform node
nodename. Either the ROOT user ID is specified when the CA Workload Automation SE
installation options do not allow the use of ROOT, or an exit error occurred in SASSXX21.
This message is followed by SSM0-90, which further explains the error.

Action:
Verify that the ROOT user ID is not being used when it is not permitted by installation
setting if the second byte of the SSM0-90 EC= is 04 or 10. If the SSM0-90 EC= second
byte is 08 or 0C, contact your local CA Workload Automation SE support, since this is an
error produced from the exit SASSXX21.

SSM0-D8

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. Either AGENTJOB=YES is not coded
on the XPDEF initialization statement, CA Integrated Agent Services (CA IAS) has not
initialized correctly, or CA IAS has encountered severe errors because CA Workload
Automation SE initialization.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1659

SSM0 Through SYS0

SSM0-EC

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. This message is followed by SSM0-90. This message is encountered when a
security error is detected for the user ID and agent associated with this job. If using
external security, the user ID must have READ access to the following resource:

ca7-instance.AGENTUSR.userid.agent

Action:
Verify that the user ID is authorized to submit the job to this agent.

SSM0-E0

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. This message is encountered when
the AFM Builder program has determined there is an error in the input data.

Action:
Verify that the job has valid parmlib data. Report both this message and the subsequent
SSM0-90 message to CA Support. For assistance, contact CA Support at ca.com/support.

SSM0-E4

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. This message is encountered when
an invalid agent job type is found for job jjjjjjjj.

Action:
Verify that the job has a valid agent job type. Report both this message and the
subsequent SSM0-90 message to CA Support. For assistance, contact CA Support at
ca.com/support.

1660 Message Reference Guide

 SSM0 Through SYS0

SSM0-E8

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. This message is encountered when
CA Integrated Agent Services (CA IAS) determines that it cannot send the AFM to the
system agent.

Action:
Verify that the agent is active and working. Report both this message and the
subsequent SSM0-90 message to CA Support. For assistance, contact CA Support at
ca.com/support.

SSM0-F0

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. This message is followed by SSM0-90. This message is encountered when
the CONTINUOUS keyword is detected in the C-LANG statements. CONTINUOUS is not
currently supported.

Action:
Remove the CONTINUOUS keyword and resubmit the job.

SSM0-0C

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyy -DATA SET SPACE EXCEEDED

Reason:
The job was not submitted to the SUBMIT data set indicated. The size of the JCL is
greater than the size permitted to the Submit data set.

Action:
Perform one of the following actions:
■ Check for other CA Workload Automation SE messages giving explanations of why
the job was not submitted.
■ Enter the top line SUBMIT command with no parameters to activate submission
processing.

Chapter 8: SPO0 - XTRK Messages 1661

SSM0 Through SYS0

SSM0-00

JOB xxxxxxxx(nnnn) SUBMITTED TO { yyyyyyyy SYn (USERID=zzzzzzzz) | CCINODE

nnnnnnnnnn | AGENT aaaaaaaaaaaaaaaa }

Reason:
The job indicated by xxxxxxxx has been successfully submitted for execution. yyyyyyyy
represents the CA Workload Automation SE internal reader or the Submit data set to
which the job was submitted. The MAINID to which the job was directed is SYn. If you
are using external security, the user ID with which the job is submitted is zzzzzzzz. For an
XPJOB, the job is submitted to the CCI Node nnnnnnnn. For an agent job, the job is
submitted to the agent named aaaaaaaaaaaaaaaa.

Action:
None.

SSM0-01

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename/agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to the indicated
internal cross platform nodename or agentname due to an internal error. Message
SSM0-90 follows this message. This condition is encountered when CA Workload
Automation SE cannot locate the Job Queue Record (JQREC) in the queues.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

SSM0-02

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename/AGENTJOB -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to the indicated
internal cross platform nodename or if AGENTJOB, to a CA Workload Automation Agent,
due to an internal error. Message SSM0-90 follows this message. This condition is
encountered when CA Workload Automation SE is unable to retrieve the parameter
data from the queues. The agent name is part of the parameter data that could not be
retrieved and is not available for display in this message.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

1662 Message Reference Guide

 SSM0 Through SYS0

SSM0-03

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename/agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to the indicated
internal cross platform nodename or agentname due to an internal error. Message
SSM0-90 follows this message. This condition is encountered when CA Workload
Automation SE cannot write the parameter data to an internal buffer.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

SSM0-04

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - SUBMIT BARRIER REACHED

Reason:
The job indicated by xxxxxxxx was not submitted because the barrier limit for the
number of CA 7 WA jobs submitted to yyyyyyyy has been reached.

Action:
Perform one of the following actions:
■ Wait for the number of jobs submitted to drop below the barrier limit and let the
job be submitted automatically.
■ Raise the barrier value using the /ASSIGN command and then either force job
submission or allow automatic submission to occur.
■ Change the main ID for the job to a CPU that is not at the barrier limit and then
force job submission.

Chapter 8: SPO0 - XTRK Messages 1663

SSM0 Through SYS0

SSM0-08

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - DATA SET BUSY

Reason:
This message can be the result of a previous system crash or of particular failures by
ICOM or CA Workload Automation SE. It can also be caused by the normal processing of
CA Workload Automation SE when too many jobs are submitted at one time.

Action:
If the condition does not clear up in a few minutes, it was probably caused by failure. To
resolve the problem, a reply of SUB=R (or SUB=F) should be made to ICOM's
outstanding WTOR. This is only valid if submit data sets are being used. See the Systems
Programming Guide for valid ICOM WTOR replies. If the condition persists, contact your
installation specialist.

SSM0-1C

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy INVALID CONTROL INFORMATION

Reason:
An error condition exists within the CA Workload Automation SE submit function.

Action:
If no SASSXX02 exit is coded, check for other CA Workload Automation SE messages
giving explanations of why the job was not submitted. Otherwise, check the SASSXX02
user exit to ensure that it is not changing or destroying information passed to it by CA
Workload Automation SE.

SSM0-10

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - PERM I/O ERROR

Reason:
A permanent I/O error has been detected on the Submit data set specified by yyyyyyyy.

Action:
To regain use of the data set, it is necessary to scratch and reallocate it in a different
location. CA Workload Automation SE must be shut down and brought back up before
the data set is available. In a multi-CPU environment, jobs can be directed to another
CPU using the /ASSIGN and DIRECT commands until the problem can be corrected.

1664 Message Reference Guide

 SSM0 Through SYS0

SSM0-14

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - UNABLE TO OPEN DATA SET

Reason:
The Submit data set specified by yyyyyyyy could not be opened for submission of jobs.
This is an unlikely situation that will generally only occur after a WARM start
initialization of CA Workload Automation SE.

Action:
Verify that the Submit data set is defined by a DD statement in the CA Workload
Automation SE JCL and by a CPU statement in the initialization file. If the data set is
properly defined in both locations, contact your installation specialist for assistance. In a
multi-CPU environment, jobs may be directed to another CPU using the /ASSIGN and
DIRECT commands until the problem is resolved.

SSM0-16

READY QUEUE STOPPED - NO SUBMIT

Reason:
An attempt was made to submit jobs, but the ready queue has been stopped by the
STOP,Q=RDY command.

Action:
Restart the ready queue using START,Q=RDY if job submission is wanted.

SSM0-18

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - INVALID SEQ - NO 'M' CALL

Reason:
An error condition exists within the CA Workload Automation SE submit function.

Action:
Contact your installation specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1665

SSM0 Through SYS0

SSM0-20

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy INVALID CONTROL BIT SETTING

Reason:
The status of the Submit data set was not acceptable for submitting the job. The job is
automatically submitted when the Submit data set status indicates availability.

Action:
Contact your installation specialist for assistance when this error occurs.

SSM0-24

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - CPU TABLE NOT SET UP

Reason:
The internal table required to control job submission was not built because CPU
statements in the product's initialization file were omitted.

Action:
If CA Workload Automation SE was initialized for batch-only type processing and no jobs
are to be submitted, this message may be ignored. If automatic job submission is
required, then the appropriate CPU statements must be added to the initialization file
and CA Workload Automation SE must be shut down and reinitialized with an ERST start.

SSM0-28

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy - JOB IS TOO BIG FOR DATA SET

Reason:
The SUBMIT data set to which the job is to be submitted does not have enough space to
hold the JCL.

Action:
None. The job is not submitted. If this or the SSM0-0C message persists, the size of the
Submit data set indicated by yyyyyyyy may need to be increased.

1666 Message Reference Guide

 SSM0 Through SYS0

SSM0-33

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

INVALID JOB CARD COLS (69), 70, 71 MUST BE BLANK.
HAS BEEN MOVED BACK TO REQUEST 'Q'

Reason:
Columns 70 and 71 of the first JOB statement are not blank and therefore CA Workload
Automation SE cannot track the job. If CA Workload Automation SE NCF is being used,
column 69 of the JOB statement must also be blank for tracking purposes. The job is
moved back into the request queue and flagged with a JCL error.

Action:
Perform the following actions:
■ Correct the JOB statement.
■ Restart the job.

SSM0-34

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

INVALID JOB CARD HAS BEEN MOVED BACK TO THE REQUEST 'Q'

Reason:
The length of the job name is greater than the number of characters in the JOB
statement where the job name is placed, or the JCL jobname and the REQQ jobname do
not match and JCLJOBCK=Y is used. The job is moved back to the request queue.

Action:
Check the job name on the JOB statement in the request queue to be sure it is correct.

If the job is being loaded, check the DBASE statement LDJOBNM value. If it is being used,
the JOB statements must have room for an 8-character job name.

If the job has #J or #X statements, ensure that the # statements are not deleting all of
the JCL for that job. If this is the case, an SSM0-90 message is produced with this
message.

Chapter 8: SPO0 - XTRK Messages 1667

SSM0 Through SYS0

SSM0-35

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

FIRST RECORD OF JCLMBR NOT A JOB CARD.
HAS BEEN MOVED BACK TO THE REQUEST 'Q'

Reason:
The first record in the JCL member does not begin with //. The job is moved back into
the request queue.

Action:
Perform the following actions:
■ Verify that the first JCL statement begins with //.
■ Correct and restart the job.

SSM0-36

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

INVALID #J OR #X OVERRIDE CARD

Reason:
A syntax error has been detected in a #J or #X control statement.

Action:
Correct the error and resubmit.

1668 Message Reference Guide

 SSM0 Through SYS0

SSM0-37

JOB xxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

NO UID SELECTED OR UID INVALID - JCL UPDATE REQUIRED
HAS BEEN MOVED BACK TO THE REQUEST 'Q'

Reason:
An attempt was made to submit a job for execution, but the job's JCL did not contain a
valid USERID or a valid USERID was not available for JCL insertion. The job is moved back
to the request queue with a status of R-NOUID.

These are some of the circumstances that can cause this message:
■ The SUBUID was coded on the SECURITY statement of the initialization file
specifying a submission hierarchy, but there was not a valid USERID available for the
job. SUBNOID=NO would also have to be coded on the SECURITY statement.
■ JCLUID=NO is coded in the SECURITY statement of the initialization file and the job
has a USERID coded in the JCL.
■ The job has a USERID coded in the JCL but CA Workload Automation SE does not
have submit security access for the USERID.

Action:
Edit the request queue JCL. If there is an invalid USERID coded, correct the USERID. If
QJCL is specified on the SUBUID parameter, you may remove an invalid USERID (or leave
the JCL unchanged if there is not a USERID in the JCL) and then replace the request
queue JCL.

SSM0-38

SECURITY SEGMENT ERROR - CANCEL JOB AND RESUBMIT

Reason:
An internal error condition was detected while retrieving a security segment for a job
during submission. The job is moved back to the request queue with a status of
E-SEGERR.

Action:
Cancel and resubmit the job.

Chapter 8: SPO0 - XTRK Messages 1669

SSM0 Through SYS0

SSM0-39

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

JOB MOVED BACK TO REQUEST QUEUE BY ARF.

Reason:
An IS condition for the job was detected by ARF. The recovery actions defined for this
condition are executed.

Action:
None.

SSM0-40

JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

ARF ERROR - UNABLE TO REQUEUE JOB.

Reason:
An IS condition for the job was detected by ARF, but the job could not be requeued
because of an internal error.

Action:
Contact your installation specialist for assistance.

SSM0-41

JOB xxxxxxxx (nnnn) NOT SUBMITTEDTO qqqqqqqq CA-DRIVER ERROR - RC=xx HAS
BEEN MOVED BACK TO REQUEST 'Q'

Reason:
The job named in the message was not submitted because of an error in CA-Driver. The
CA-Driver procedure libraries may not have been accessible to CA Workload Automation
SE.

Action:
Ensure that the CA-Driver procedure libraries associated with this job are accessible to
CA Workload Automation SE and resubmit.

1670 Message Reference Guide

 SSM0 Through SYS0

SSM0-42

JOB jjjjjjjj (nnnn) NOT SUBMITTED

SCHENV VALIDATION FAILED FOR ssssssssssssssss
ttt...ttt

Reason:
WLMSEVAL=YES was specified on the OPTIONS statement in the product's initialization
file. The job named at jjjjjjjj with CA 7 WA job number nnnn was not submitted to
internal reader or submit data set. The job was not submitted because the specified
scheduling environment name is not valid. ssssssssssssssss is the name of the scheduling
environment that was defined for the job in CA Workload Automation SE. The reason
the scheduling environment name is considered invalid is given at ttt...ttt If the
scheduling environment is not defined in the current IBM WLM Policy, then the text will
read:

SCHED ENVIR DOES NOT EXIST

Action:
Correct the error and continue.
■ If the scheduling environment name is incorrect or misspelled, use the QJCL Edit
facility to manually add a SCHENV='xxx' keyword to the JOB statement and initiate a
restart for the job. CA Workload Automation SE will not override an existing
SCHENV= keyword in the JCL. Remember to correct the original VRM resource
definition or global setting.
■ If you want the job submitted without inserting any scheduling environment
keyword, use the :xph.JCLOVRD,SET=NOWLM,JOB=nnnn:exph. command. This will
suppress scheduling environment insertion for this execution of the job.
■ If the wrong IBM WLM policy is active then manually restart the job after the
correct WLM policy has been activated.

SSM0-45

JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - DPROC DSNAME INVALID

Reason:
The job named in the message was not submitted to the destination internal reader
because the DPROC library on the JCL entry did not match.

Action:
Ensure the correct DPROC data set name is associated with the JCL library where the JCL
library is defined (in either the initialization file or in the VRM JCL definitions).

Chapter 8: SPO0 - XTRK Messages 1671

SSM0 Through SYS0

SSM0-46

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to cross-platform node
nodename. The CA Workload Automation SE CCI environment has not been established
or has encountered severe errors since CA Workload Automation SE initialization. This
message is followed by SSM0-90. This condition is encountered when CA Workload
Automation SE cannot establish a communications path to the CAICCI environment. This
could indicate that either CA Workload Automation SE has never initialized the CCI
environment, or some error has occurred from which CA Workload Automation SE
cannot contact CAICCI.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support.

SSM0-47

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO nodename -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to cross-platform node
nodename. The specified node name is either in a stopped state, or there are problems
locating the node in the internal CA Workload Automation SE node table. This message
is followed by SSM0-90. This condition is encountered when the node is in a stopped
status, or if a temporary node, storage is unable to be obtained.

Action:
Perform the following actions:
■ Execute a LNODE command against the specified node name to see if it is stopped;
if so, use XNODE to put the node online or offline as needed. If the node is not
listed from the LNODE command, check the CA Workload Automation SE address
space to see if it is having any storage problems.
■ Report both this message and the subsequent SSM0-90 message to CA Support if
still unable to resolve the problem.

1672 Message Reference Guide

 SSM0 Through SYS0

SSM0-48

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. Either AGENTJOB=YES is not coded
on the XPDEF initialization statement, CA Integrated Agent Services (CA IAS) has not
initialized correctly, or CA IAS has encountered severe errors because CA Workload
Automation SE initialization.

Action:
Report both this message and the subsequent SSM0-90 message to CA Support. For
assistance, contact CA Support at ca.com/support.

SSM0-49

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. Message SSM0-90 follows this message. This message is encountered when
a request for storage has failed.

Action:
Verify CA Workload Automation SE is not encountering other storage-related abends. If
so, increase the region for CA Workload Automation SE and recycle. If this action does
not resolve the problem, report both this message and the subsequent SSM0-90
message to CA Support. For assistance, contact CA Support at ca.com/support.

SSM0-50

JOB jjjjjjjj(nnnn) NOT SUBMITTED TO agentname -

Reason:
The job jjjjjjjj with CA 7 WA job number nnnn was not submitted to system agent
agentname. This message is followed by SSM0-90. This message is encountered when a
security error is detected.

Action:
Verify that the user submitting this job has the necessary authorizations.

Chapter 8: SPO0 - XTRK Messages 1673

SSM0 Through SYS0

SSM0-90

SUBMIT ERROR FOR JOB xxxxxxxx(nnnn) EC=wwxxyyzz

Reason:
The CPU job is in ready queue with no JCL attached. For an XPJOB or agent job, this
describes the related information as accompanied by an SSM0-xx message, where xx is
non-zero.

Action:
Perform one of the following actions:
■ For a CPU job, cancel the job and re-DEMAND. Check for the SASSxx05 user exit. It
may have deleted the JCL. Also check SASSxx02 for the same reason.
The JCL may have been deleted due to #J or #X statements. If this is the case, the
job is requeued back to the request queue and the SSM0-34 message is produced.
■ For an XPJOB or agent job type, the EC= value indicates what specific error
occurred. The ww of EC= indicates the message suffix of the SSM0-, and xx indicates
the reason. Consult the SSM0-ww message for additional details. For an agent job, a
reason follows and is one of the following:
– CAIAS message prefix - For more information, see the CA Integrated Agent
Services Message Guide.
– External Security package message prefix - For more information, see the
appropriate external security package manual.
– text without a message prefix - For more information, see the reason under the
preceding SSM0-ww message for why the error occurred.

SSM0-91

JOB jjjjjjjj(nnnn) - POST RC(xxx) REAS(yyy)

Reason:
This message is issued when a problem occurs in CA 7 WA job submission
post-processing.

Action:
Collect all job information (including JCL or parameter data), the browse log, and other
relevant information, and contact CA Support at ca.com/support for assistance.

1674 Message Reference Guide

 SSM0 Through SYS0

SSM0-92

JOB jjjjjjjj(nnnn) - TRACE FAILED, NO STORAGE TO LOG AJB DATA

Reason:
Trace information is not written to the log for the job jjjjjjjj with CA 7 WA job number
nnnn.

Action:
Increase the region size specified for CA Workload Automation SE.

SSM3-25

JOB xxxxxxxx (nnnn) AND JOB yyyyyyyy (ALREADY SUBMITTED) ARE MUTUALLY
EXCLUSIVE
RQMT IGNORED BECAUSE OF MANUAL POSTING

Reason:
xxxxxxxx indicates the job in the ready queue is to be submitted. nnnn is the job
number. yyyyyyyy is the name of a mutually exclusive job that has already been
submitted. The mutually exclusive requirement of job yyyyyyyy was manually posted
and is no longer a requirement for job xxxxxxxx.

Action:
None. Job xxxxxxxx is submitted (the posting requirement will no longer be honored)
unless job xxxxxxxx has other mutually exclusive job requirements.

SSM3-26

JOB xxxxxxxx (nnnn) AND JOB yyyyyyyy (ALREADY SUBMITTED) ARE MUTUALLY
EXCLUSIVE
JOB xxxxxxxx (nnnn) HAS BEEN MOVED BACK TO REQ Q

Reason:
xxxxxxxx indicates the job in the ready queue is to be submitted. nnnn is the job
number. yyyyyyyy is the name of a mutually exclusive job that has already been
submitted. Job xxxxxxxx is moved back to the request queue, and the master count is
increased by one. Job xxxxxxxx is submitted when job yyyyyyyy successfully completes.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1675

SSM0 Through SYS0

SSYM-04

No delimiter found for variable

Reason:
No character (blank, period, comma, right parenthesis) was found that could delimit the
end of the variable. A JCL error occurs, and a message is written to the Browse data set.

Action:
Perform the following actions:
■ Correct the JCL or submission text.
■ Resubmit the job or reissue the command.

SSYM-08

Error calculating variable length

Reason:
Program SASSSSYM could not calculate the length of the global variable. A JCL error
occurs, and a message is written to the Browse data set.

Action:
Perform the following actions:
■ Correct the JCL or submission text.
■ Resubmit the job or reissue the command.

SSYM-12

Variable substitution exceeds recursion limit

Reason:
One or more global variables were recursive and exceeded the recursion limit specified
on the initialization file OPTIONS statement keyword GVARLVL. If GVARLVL is not
specified, the default recursion limit is four. A JCL error occurs, and a message is written
to the Browse data set.

Action:
Perform the following actions:
■ Correct the JCL, submission text, or global variables.
■ Resubmit the job or reissue the command.

1676 Message Reference Guide

 SSM0 Through SYS0

SSYM-16

Insufficient space to insert variable contents

Reason:
The length of the text being substituted for one or more global variables is longer than
the global variables, forcing the line of text to be shifted to the right. There is
insufficient space in the line to contain the existing text plus the new substitution text. A
JCL error occurs, and a message is written to the Browse data set.

Action:
Perform the following actions:
■ Correct the JCL or submission text.
■ Resubmit the job or reissue the command.

SSYM-28

Statement buffer address missing or invalid

Reason:
Program SASSSSYM cannot read the JCL or XPJOB submission text line. A JCL error
occurs, and a message is written to the Browse data set.

Action:
For assistance, contact CA Support at ca.com/support.

SS00-45

nnn JOBS SUBMITTED SINCE yy.ddd AT hh:mm:ss

Reason:
This status message is issued when CA Workload Automation SE begins scanning the
ready queue to select jobs for submission. The message reports the number of jobs
submitted since the date and time the message was last issued.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1677

SSM0 Through SYS0

SS00-46

xxxxxxxx(yyyyyyyy) JOBS EVALUATED; nnnnnnnn JOBS SELECTED

Reason:
This status message is issued when CA Workload Automation SE finishes scanning the
ready queue to select jobs for submission. The message contains the following items:
xxxxxxxx
Specifies the count of jobs in the ready queue during the scan.
yyyyyyyy
Specifies the number of times CA Workload Automation SE fetched a record from
the ready queue during the scan. If certain options (such as Workload Balancing,
JSOP=3) are indicated, yyyyyyyy may be considerably greater than xxxxxxxx.
nnnnnnnn
Specifies the number of jobs selected for submission during the scan.

Action:
None.

SVPR-01

xx INVALID MACRO RETURN CODE = nnnnnnnn

Reason:
The SASSSVPR module has detected an error on return from a macro. The
Where-In-Program (WIP) value is specified by xx. The register 15 value (in hex) is given
by nnnnnnnn. If xx=1G, issue the command /DISPLAY,Q=ALL to check the available space
in the Prior-run queue.

Action:
Contact your installation specialist for assistance.

1678 Message Reference Guide

 SSM0 Through SYS0

SVPR-18

OUTPUT DSN=x...x NOT FOUND IN INDEX DATA SET

Reason:
An output data set was not found in the CA Workload Automation SE IDS.

Action:
None. Usually occurs when a job is first loaded. If the data set was known to be in the
CA Workload Automation SE IDS, contact your installation specialist for assistance.

SVPR-49

FOLLOWING INPUT REQUIREMENT NOT USED BY JOB=xxxxxxxx DSN=y...y

Reason:
A data set requirement for job xxxxxxxx was not opened.

Action:
None. Message is for user information only. If the data set was supposed to be opened,
contact your installation specialist for assistance. This condition can be caused by using
a DISP=(OLD,DELETE). May also get this message if the data set was opened, but the
ddname changed. Use of PERFORM=1 on the INIT statement in the product's
initialization file suppresses this message.

SVPR-50

TABLE OVERFLOW -- OUTPUT DSN x.......x NOT CAPTURED

Reason:
The internal table for completion processing has overflowed and the information about
the named data set was lost. Only this creation of the data set and possibly requirement
posting were lost.

Action:
The job that created this data set may need to be marked as a maintenance job using
the MAINT field on the DB.1 (JOB) panel. If requirement posting was lost, may require
manual posting. Contact your installation specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1679

SSM0 Through SYS0

SVPR-51

INDEX DATA SET ERROR (aaaabbbb) -- OUTPUT DSN x............x NOT CAPTURED

Reason:
An error occurred while updating the CA Workload Automation SE IDS with data about
the data set whose name appears in the message. The type of error is indicated by
aaaabbbb.

Action:
Check for conflicting data set names in the IDS and correct if necessary. Also, check
system console for possible messages related to space or I/O errors on the IDS. If
aaaa=0000 and bbbb=0007, the CA Workload Automation SE IDS is probably full. For the
VSAM data set, all the control areas are used and a RE-ORG should be sufficient.

SVPR-52

DSN=x.........x SUCCESSFULLY CREATED

Reason:
CA Workload Automation SE received a type 99 record from the Batch Card Load
Program (BCLP) or from U7SVC for the data set noted. The CA Workload Automation SE
IDS has been updated, and any jobs in the request queue containing this data set as an
input requirement are appropriately posted.

Action:
None.

1680 Message Reference Guide

 SSM0 Through SYS0

SVPR-65

JOB jjjjjjjj (nnnn) JOB MEMBER ACCESS ERROR, R15=xxxxxxxx

UNABLE TO RESET TEMPORARY REQUIREMENTS

Reason:
The indicated job has at least 1 requirement with a NEXT-RUN value of SKIP or ONLY,
but an error occurred while trying to read the database member record for the
indicated job. The return code is shown as the value for R15=. Job completion
processing was not completed successfully. The job was not added to the Prior-run
queue. Input and output trailer processing was not done. The SKIP or ONLY
requirements were not reset.

Action:
If the error was not transient, the database will have to be corrected, probably by your
installation specialist. The SKIP or ONLY requirement must be reset manually with the
appropriate DB.3 function. Dependent tasks with this job as a predecessor requirement
will have to have that requirement posted manually. Triggered tasks must be demanded
manually. This job will have to be canceled from the request queue.

SVPR-66

JOB jjjjjjjj (nnnn) REQUIREMENT ENTRY ACCESS ERROR, R15=xxxxxxxx

UNABLE TO RESET TEMPORARY REQUIREMENTS

Reason:
This is the same condition as explained in message SVPR-65 except the error occurred
while reading a requirement record.

Action:
Same as in message SVPR-65 except some NEXT-RUN requirements may have already
been reset before the error occurred.

SVPR-67

JOB jjjjjjj (nnnn) REQUIREMENT ENTRY UPDATE ERROR, R15=xxxxxxxx

UNABLE TO RESET TEMPORARY REQUIREMENTS

Reason:
This is the same condition as in message SVPR-65 except the error occurred while
rewriting a requirement record.

Action:
Same as in message SVPR-65 except some NEXT-RUN requirements may have already
been reset before the error occurred.

Chapter 8: SPO0 - XTRK Messages 1681

SSM0 Through SYS0

SYN1-00

SYNTAX COMPLETED. PRESS PA1/ENTER TO CONTINUE mmm ERRORS FOUND

Reason:
The JCL syntax check has completed. The number of errors detected is listed.

Action:
Press the PA1 key or the Enter key to return to the edit mode.

SYN1-01

JCL SYNTAX CHECKING SERVICES UNAVAILABLE

Reason:
CA Workload Automation SE could not locate the JCLCheck Common Component or the
full CA JCLCheck Workload Automation product to perform JCL syntax checking
functions.

Action:
Perform one of the following actions:
■ Include a JCLCHECK statement in the product's initialization file if you have the CA
JCLCheck Workload Automation product.
■ Install the JCLCheck Common Component to perform JCL syntax checking if you do
not have the CA JCLCheck Workload Automation product.

For information about the CA JCLCheck Workload Automation interface, see the
Interface Reference Guide.

SYN1-20

UNDEFINED OR MISSING OPERATION FIELD

Reason:
In the statement displayed, the operation field could not be located or was not defined
in SASSSYT1 or SASSSYT2. The syntax check continues with the next statement.

Action:
Correct and try again.

1682 Message Reference Guide

 SSM0 Through SYS0

SYN1-21

EXPECTED CONTINUATION NOT RECEIVED

Reason:
In the statement displayed, the last statement ended in a comma but the next
statement was not a continuation. The statement is checked for other errors and the
syntax check continues.

Action:
Correct and try again.

SYN1-22

OPERAND FIELD DOES NOT TERMINATE IN A COMMA OR BLANK

Reason:
A comma or blank was not encountered before reaching column 72. The statement is
checked for other errors and the syntax check continues.

Action:
Correct and try again.

SYN1-28

EXCESSIVE NUMBER OF DD STATEMENTS

Reason:
More than 1625 DDs were encountered in one job step. This message appears for each
DD encountered beyond 1625. The syntax check continues.

Action:
Correct and try again.

SYN1-29

JOB HAS NO STEPS

Reason:
There were no valid EXEC statements after the JOB statement.

Action:
Correct and try again.

Chapter 8: SPO0 - XTRK Messages 1683

SSM0 Through SYS0

SYN1-35

MISPLACED DD

Reason:
A DD statement, other than JOBLIB, JOBCAT or SYSCHK, was found between the JOB
statement and the first EXEC statement. The remainder of the statements are checked
for syntax errors.

Action:
Correct and try again.

SYN1-36

NO NAME ON THE FIRST DD CARD AFTER EXEC

Reason:
The first DD statement after an EXEC does not have a name. The remainder of the
statements are checked for syntax errors.

Action:
Correct and try again.

SYN1-37

OVERRIDE NAME NOT ALLOWED WITH KEY WORD - keyword

Reason:
An override name is not allowed with the keyword displayed.

Action:
Correct and try again.

SYN1-41

UNBALANCED PARENTHESES IN FIELD-field

Reason:
An unbalanced parentheses condition was encountered. The last major keyword
processed is displayed. Processing continues with the next major keyword.

Action:
Correct and try again.

1684 Message Reference Guide

 SSM0 Through SYS0

SYN1-42

SOURCE TEXT CONTAINS ILLEGAL CHARACTER IN FIELD-field

Reason:
The statement displayed contains illegal characters in the field indicated. JCL statements
may contain only alphabetic, numeric, national or certain special characters. Processing
continues.

Action:
Correct and try again.

SYN1-43

INCORRECT USE OF APOSTROPHE IN FIELD-field

Reason:
The statement displayed contains an incorrect use of an apostrophe. Special characters
are enclosed by apostrophes. If a field contains an apostrophe as part of the character
string, the apostrophe must be expressed as a double apostrophe. The last major
keyword processed is displayed in the message text. This message is also displayed if an
apostrophe is missing. The syntax check continues with the next statement.

Action:
Correct and try again.

SYN1-44

UNDEFINED KEYWORD-keyword

Reason:
The statement displayed contains a keyword not defined in SASSSYT1 or SASSSYT2. The
keyword may also be present in an undefined combination, such as SPACE with an EXEC
statement. The keyword in question is displayed with the error message. Processing
continues with the next keyword.

Action:
Correct and try again.

Chapter 8: SPO0 - XTRK Messages 1685

SSM0 Through SYS0

SYN1-45

INVALID KEYWORD-keyword

Reason:
The statement displayed contains an invalid keyword. For example, a PROC statement
contains a symbolic keyword that is invalid with an EXEC statement. The invalid keyword
is displayed in the message text. Processing continues with the next keyword.

Action:
Correct and try again.

SYN1-50

INVALID OR MISSING NAME IN FIELD-field

Reason:
The statement displayed contains an invalid name or (if a name is required) is missing a
name. The name may be invalid due to length or it may violate the rules for a name. The
last major keyword processed is displayed in the message text. The remainder of the
statement is checked for syntax errors.

Action:
Correct and try again.

SYN1-51

SUBLIST NOT ALLOWED IN FIELD-field

Reason:
The statement displayed contains a sublist with a field that does not allow a sublist. The
last major keyword processed is displayed in the message text.

Action:
Correct and try again.

1686 Message Reference Guide

 SSM0 Through SYS0

SYN1-52

INCORRECT USE OF A PERIOD IN FIELD-field

Reason:
The statement displayed contains a period in a field that does not allow a period. For
example, a period is immediately preceded by a close parenthesis or is followed by a
comma. The last major keyword processed is displayed in the message text. Processing
continues with the next major keyword.

Action:
Correct and try again.

SYN1-53

INCORRECT USE OF LEFT PAREN IN FIELD-field

Reason:
The statement displayed contains a left parenthesis that is used incorrectly. For
example, a left parenthesis is immediately preceded by a quote or a right parenthesis.
The last major keyword processed is displayed in the message text. Processing continues
with the next major keyword.

Action:
Correct and try again.

SYN1-59

FORMAT ERROR IN FIELD-field

Reason:
The statement displayed contains one of the following format errors:
■ Zero length keyword (for example, =).
■ Positional parameter out of place.
■ Close parenthesis not followed by a blank, comma or another close parenthesis.
■ Symbolic outside the range of a procedure.

The last major keyword processed is displayed in the message text. Processing continues
with the next major keyword.

Action:
Correct and try again.

Chapter 8: SPO0 - XTRK Messages 1687

SSM0 Through SYS0

SYN1-60

FIELD EXCEEDS ALLOWABLE LENGTH IN FIELD-field

Reason:
The statement displayed contains a field that is too long. The last keyword processed is
also displayed. Processing continues with the next field.

Action:
Correct and try again.

SYN1-61

INVALID NUMERIC IN FIELD-field

Reason:
The statement displayed contains a non-numeric character in a field that must be
numeric. The last keyword processed is also displayed. Processing continues with the
next field.

Action:
Correct and try again.

SYN1-62

NUMERIC EXCEEDS MAX ALLOWED VALUE IN FIELD-field

Reason:
The statement displayed contains a numeric field that is larger than the maximum
allowed for that field. The last keyword processed is also displayed. Processing
continues with the next field.

Action:
Correct and try again.

1688 Message Reference Guide

 SSM0 Through SYS0

SYN1-63

INVALID VALUE IN FIELD-field

Reason:
The statement displayed contains an invalid value for a field. The last keyword
processed is also displayed. Processing continues with the next field.

Action:
Check for misspelled values. Correct and try again.

SYN1-64

REQUIRED POSITIONAL PARAMETER MISSING IN FIELD-field

Reason:
A required positional parameter is not present. The last keyword processed is displayed.
Processing continues with the next field.

Action:
Correct and try again.

SYN1-65

EXCESSIVE NUMBER OF POSITIONALS IN FIELD-field

Reason:
The operand field of the keyword displayed contains too many positional parameters.
Processing continues with the next keyword.

Action:
Correct and try again.

SYN1-66

MUTUALLY EXCLUSIVE FIELDS-fields

Reason:
The two keywords or values displayed are mutually exclusive. Processing continues with
the next field.

Action:
Correct and try again.

Chapter 8: SPO0 - XTRK Messages 1689

SSM0 Through SYS0

SYN1-67

INVALID CHARACTER IN FIELD-field

Reason:
The operand of the keyword displayed contains a character that is invalid for that
operand. Processing continues with the next field.

Action:
Correct and try again.

SYN1-68

INVALID PGM=/PROC=

Reason:
The EXEC statement displayed does not contain PGM, PROC or a valid procedure name.
The remainder of the statement is checked for errors.

Action:
Correct and try again.

SYN1-69

NUMBER OF NESTED IF STATEMENTS EXCEEDS ALLOWABLE MAXIMUM

Reason:
JCL IF statements can only be nested 15 levels. The JCL syntax checker found more than
15 levels of IF statements.

Action:
Correct the JCL.

SYN1-70

EXCESSIVE NUMBER OF ENDIF STATEMENTS

Reason:
The number of ENDIF statements should match the number of IF statements. This
message indicates too many ENDIF statements were found.

Action:
Correct the JCL.

1690 Message Reference Guide

 SSM0 Through SYS0

SYN1-71

INSUFFICIENT NUMBER OF ENDIF STATEMENTS SPECIFIED

Reason:
The number of ENDIF statements should match the number of IF statements. This
message indicates not enough ENDIF statements were found.

Action:
Correct the JCL.

SYN1-72

UNABLE TO LOAD JCLCHECK INTERFACE

Reason:
An error occurred trying to load the interface module for CA JCLCheck Workload
Automation. The interface is terminated and is not usable until the problem is
corrected.

Action:
Perform the following actions:
■ Check the console messages from CA Workload Automation SE startup for possible
error conditions.
■ Verify that module SASSJCKI exists in the CA Workload Automation SE load library
concatenation.

SYN1-79

JCLCHECK INTERFACE INTERNAL ERROR

Reason:
An invalid return code was received from the interface module.

Action:
Perform the following actions:
■ Check the console for other messages from CA Workload Automation SE or CA
JCLCheck Workload Automation.
■ Perform any corrective actions indicated.
■ Try the interface again.
If the problem continues, contact your installation specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1691

SSM0 Through SYS0

SYN1-80

SYSIN STATEMENT WILL BE GENERATED

Reason:
The non-JCL statement was not preceded by a DD *. The message indicates that a SYSIN
DD * statement is generated if the job is submitted. Processing continues.

Action:
Check for a missing DD * or an incorrect statement.

SYN1-81

ERROR DETECTED BY USER EXIT

Reason:
User exit SASSXX06 detected an error in the statement listed. Processing continues.

Action:
Perform the following actions:
■ Check message from exit.
■ Correct error.
■ Try again.

SYN1-89

PARSE AREA TOO SMALL

Reason:
The statement displayed was too large to complete syntax checking on it. Processing
continues with the next statement.

Action:
Perform the following actions:
■ Remove non-essential parameters from the statement.
■ Try again.
■ Contact your installation specialist for assistance.

1692 Message Reference Guide

 SSM0 Through SYS0

SYN1-90

INVALID INPUT FILE ID

Reason:
The input file ID posted from the editor was not a 6 or 7. The syntax check is aborted.

Action:
Contact your installation specialist for assistance.

SYN1-91

INPUT FILE EMPTY

Reason:
The input file passed did not contain any statements. The syntax check is aborted.

Action:
Ensure that the Edit Work file is not empty before requesting a syntax check.

SYN1-92

OUT OF SPACE ON FILE 1

Reason:
There was insufficient room in Scratch File 1 to contain JCL images and error messages.
The syntax check is aborted.

Action:
If LIST was specified, retry the syntax check without the LIST option. If the problem
persists, increase the SCRTRK/SWFTRK value on the DAIO statement in the initialization
file, and then reinitialize CA Workload Automation SE.

Chapter 8: SPO0 - XTRK Messages 1693

SSM0 Through SYS0

SYN1-93

STATEMENT TOO BIG

Reason:
A statement that contained more than 2000 characters was encountered. The syntax
check is aborted.

Action:
Perform the following actions:
■ Remove non-essential parameters from the statement.
■ Try again.
■ Contact your installation specialist for assistance.

SYN1-94

ERROR ON FILE 1 - field

Reason:
An error was returned while attempting to write a statement image or an error
message. The syntax check is aborted.

Action:
Contact your installation specialist for assistance.

SYN1-95

ERROR ON INPUT FILE

Reason:
An error was returned while attempting to read the statements to be checked. The
syntax check is aborted.

Action:
Contact your installation specialist for assistance.

1694 Message Reference Guide

 SSM0 Through SYS0

SYN1-96

SASSPCEJ ERROR - return code

Reason:
The return code displayed was returned from SASSPCEJ. The syntax check is aborted.

Action:
Contact your installation specialist for assistance.

SYN1-97

# STATEMENT ERROR FOUND BY SASSJJ01 - return code

Reason:
Module SASSJJ01 detected an error in the syntax of a #X or #J statement. The statement
preceding the one in error is displayed ahead of this message. The return code displayed
was returned from SASSJJ01. The syntax check is aborted.

Action:
Contact your installation specialist for assistance.

SYN1-98

JCL TABLE NOT FOUND - table

Reason:
The JCL table displayed was not found by LOAD. The syntax check is aborted.

Action:
Perform the following actions:
■ Check CA Workload Automation SE installation for errors.
■ Ensure that SASSPROG has an entry for the program.
■ Contact your installation specialist for further assistance.

Chapter 8: SPO0 - XTRK Messages 1695

TIQ1 Through Tnnn

SYN1-99

INTERNAL ERROR

Reason:
A programming error was detected in the syntax checker. The syntax check is aborted.

Action:
Contact your installation specialist for assistance.

SYS0

INVALID INPUT - ERROR

Reason:
The input command contained invalid data.

Action:
Correct and resubmit the command.

TIQ1 Through Tnnn

This section contains the TIQ1 through Tnnn messages.

TIQ1-00

TMS ONLINE MONITOR ENDED SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Reason:
Normal completion of TIQ command occurred. Where:
■ xxxx is the system abend code.
■ nnnn is user abend code.

Action:
None if both xxxx and nnnn are zero.

1696 Message Reference Guide

 TIQ1 Through Tnnn

TIQ1-70

FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Reason:
TIQ/TIQU command was issued from a non-3270 terminal.

Action:
Use 3270 (online) terminal to issue the command.

TIQ1-91

ATTACH UNSUCCESSFUL FOR UCC1OCTL

Reason:
During the initialization of the CA Workload Automation SE TIQ interface, a failure
occurred while attaching module UCC1OCTL.

Action:
Determine the reason for the failure by checking module UCC1OCTL in the CA 1 load
library, and then try again. It may be necessary to assemble and link UCC1OCTL to
correct the error.

TIQ1-92

BLDL FAILED FOR xxxxxxxx

Reason:
During the initialization of the CA Workload Automation SE TIQ interface, the module
xxxxxxxx could not be found.

Action:
Perform the following actions:
■ Verify that the CA 1 library is concatenated to STEPLIB in the CA Workload
Automation SE JCL and that the indicated module exists.
■ Retry the interface.

Chapter 8: SPO0 - XTRK Messages 1697

TIQ1 Through Tnnn

TIQ1-93

CA-7 TIQ CANNOT INITIALIZE - PLEASE RETRY

Reason:
A problem was encountered when executing multiple TIQ commands through CA
Workload Automation SE.

Action:
Try the TIQ command again. If the problem persists, try using the LIST=RST option.

TIQ5-00

TMS ONLINE MONITOR ENDED SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Reason:
Normal completion of TIQ command occurred. Where:
■ xxxx is the system abend code.
■ nnnn is user abend code.

Action:
None if both xxxx and nnnn are zero.

TIQ5-70

FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Reason:
TIQ/TIQU command was issued from a non-3270 terminal.

Action:
Use 3270 (online) terminal to issue the command.

1698 Message Reference Guide

 TIQ1 Through Tnnn

TIQ5-91

ATTACH UNSUCCESSFUL FOR TMSTOCTL

Reason:
During the initialization of the CA Workload Automation SE TIQ interface, a failure
occurred while attaching module TMSTOCTL.

Action:
Determine the reason for the failure by checking module TMSTOCTL in the CA 1 Load
library, and then try again. It may be necessary to assemble and link TMSTOCTL TO
correct the error.

TIQ5-92

BLDL FAILED FOR xxxxxxxx

Reason:
During the initialization of the CA Workload Automation SE TIQ interface, the module
xxxxxxxx could not be found.

Action:
Perform the following actions:
■ Verify that the CA 1 library is concatenated to STEPLIB in the CA Workload
Automation SE JCL and that the indicated module exists.
■ Retry the interface.

TIQ5-93

CA-7 TIQ CANNOT INITIALIZE - PLEASE RETRY

Reason:
A problem was encountered when executing multiple TIQ commands through CA
Workload Automation SE.

Action:
Try the TIQ command again. If the problem persists, try using the LIST=RST option.

Chapter 8: SPO0 - XTRK Messages 1699

UTLx

T351-35

BAD KEYWORD FOR JOB: xxxxxxxx

Reason:
While interrogating LJOB output for job xxxxxxxx, module SASST351 encountered an
unknown keyword. The record being interrogated is displayed below the message for
debugging purposes. A user 0035 abend is also issued. This message indicates an error
in CA Workload Automation SE.

Action:
Contact your installation specialist for assistance.

UTLx
This section contains the UTLx messages.

UTL0-05

UNRECOGNIZABLE KEYWORD IN INPUT

Reason:
The input contains unrecognizable data.

Action:
Correct and reenter.

UTL0-05

INVALID OR OMITTED FUNCTION DATA

Reason:
The identified keyword data is either invalid or was required and not entered.

Action:
Correct and reenter.

1700 Message Reference Guide

 UTLx

UTL0-11

DATASET IS USERID PROTECTED

Reason:
You are not authorized to use this function.

Action:
Verify that the data set name and userid protection are in the USERID security module.

UTL0-67

CA-1 NOT ACTIVE ON THE SYSTEM

Reason:
CA 1 has not been initialized on the system.

Action:
If you want, initialize CA 1. Then repeat the command that resulted in this message.

UTL0-68

UNKNOWN CA-1 VERSION DETECTED ON THE SYSTEM

Reason:
The "eyecatcher" of a supposed CA 1 system does not match any of the CA 1 releases
that CA Workload Automation SE supports.

Action:
For assistance, contact CA Support at ca.com/support.

UTL0-69

INTERNAL ERROR PROCESSING TIQ(U) REQUEST

Reason:
The proper CA Workload Automation SE interface module for CA 1 could not be
determined for your release of CA 1.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1701

UTLx

UTL1-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the time and date shown.

Action:
None.

UTL1-02

func(rc) DATA SET NOT FOUND

Reason:
The requested data set was not found. The OS macro issued and its return code are
displayed.

Action:
Correct and reenter.

UTL1-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL1-12

func(rc) REQUIRED DASD VOLUME NOT AVAILABLE

Reason:
Either the required DASD is not online or a DD statement is not available to CA
Workload Automation SE to access that volume. The OS macro issued and the return
code are printed.

Action:
If you want, insert a DD statement in the CA Workload Automation SE execution JCL to
access that volume the next time CA Workload Automation SE is initialized: or use the
ALLOC command to dynamically allocate the volume.

1702 Message Reference Guide

 UTLx

UTL1-13

LOC(rc) DATA SET NOT DASD OR MULTI-VOLUME

Reason:
Support is provided for single volume DASD data sets only.

Action:
None.

UTL1-14

FIND(rc) MEMBER NOT FOUND

Reason:
The requested member was not found in the PDS.

Action:
None.

UTL1-15

UNABLE TO OPEN DATA SET DUE TO reason

Reason:
The data set could not be opened because of the specified reason.

Action:
None.

UTL1-16

END OF DATA REACHED

Reason:
An end-of-data condition was detected before the specified record was read.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1703

UTLx

UTL1-17

SYNAD EXIT ENTERED

Reason:
An I/O error occurred while reading the data set.

Action:
Determine cause and correct.

UTL1-33

LOAD ERROR FOR SASSDCON

Reason:
Failure occurred trying to load module SASSDCON.

Action:
Check that the module is in your CA Workload Automation SE load library. If missing or
error continues, reassemble and link the module.

UTL1-34

DATE CONVERT ERROR; DATE ARG IS xxxxxxxx, MBR=yyyyyyyy

Reason:
Error occurred while converting what should be a date value indicated by xxxxxxxx that
is hexadecimal and should have format 0yymmdds. The member being processed when
the error occurred is noted by yyyyyyyy.

Action:
Determine why the data is in error and correct.

Note: It is assumed that directory entries have been formatted by TSO/ISPF or

equivalent.

1704 Message Reference Guide

 UTLx

UTL1-35

ONLINE CALENDAR FEATURE NOT ENABLED.

Reason:
A request was made to list the base calendars in the CA Workload Automation SE
Calendar PDS. However, the Calendar PDS is identified to CA Workload Automation SE in
the initialization file CALENDAR statement.

Action:
None. If you want to enable the online calendar maintenance feature, see the
CALENDAR initialization file statement in the Systems Programming Guide.

UTL1-36

PERPETUAL CALENDAR FEATURE NOT ENABLED.

Reason:
A request was made to list the perpetual calendars in the CA Workload Automation SE
perpetual calendar PDS. However, the perpetual calendar PDS is not identified to CA
Workload Automation SE on the initialization file CALENDAR statement with the
PCALDSN keyword.

Action:
None. If you want to enable the perpetual calendar feature, see the CALENDAR
initialization file statement in the Systems Programming Guide.

UTL1-99

function FAILED -- R15=rc FLAGS=xxxx

Reason:
The indicated command has failed.
■ function is either DMPDSN or LISTDIR
■ rc is return code value in register 15
■ xxxx is reason code

Action:
Look up the error codes for dynamic allocation in the IBM manual z/OS MVS
Programming: Authorized Assembler Services Guide.

Chapter 8: SPO0 - XTRK Messages 1705

UTLx

UTL2-02

func(rc) DATA SET NOT FOUND

Reason:
The requested data set was not found. The OS macro issued and its return code are
displayed.

Action:
Correct and reenter.

UTL2-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL2-12

RDJF(rc) REQUIRED DASD VOLUME NOT AVAILABLE

Reason:
Either the required DASD is not online or a DD statement is not available to CA
Workload Automation SE to access that volume. The OS macro issued and the return
code are printed.

Action:
If you want, insert a DD statement in the CA Workload Automation SE execution JCL to
access that volume the next time CA Workload Automation SE is initialized; or use the
ALLOC command to dynamically allocate the volume.

1706 Message Reference Guide

 UTLx

UTL2-15

UNABLE TO OPEN DATA SET DUE TO IO-ERROR

Reason:
An I/O error occurred on data set open.

Action:
Copy the data set to another volume. If that does not solve the problem, contact your
installation specialist for assistance.

UTL2-16

END OF DATA REACHED

Reason:
An end-of-data condition was detected before the specified record was read.

Action:
None.

UTL2-17

SYNAD EXIT ENTERED

Reason:
An I/O error occurred while reading the data set.

Action:
Determine cause and correct.

UTL3-00

dsname SUCCESSFULLY CATALOGED [ON cvol]

Reason:
The data set specified is successfully cataloged.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1707

UTLx

UTL3-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the time and date shown.

Action:
None.

UTL3-01

NO VOLUME ID IN TIOT

Reason:
The volume is not allocated to CA Workload Automation SE.

Action:
Allocate the volume by putting a //U7volser DD in the CA Workload Automation SE
PROC, by using the UT.11 panel or the ALLOC command.

UTL3-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL3-11

dsname NOT FOUND

Reason:
The requested data set was not found.

Action:
None.

1708 Message Reference Guide

 UTLx

UTL3-12

CVOL NOT ONLINE OR CONTAINS NO CATALOG

DSNAME INCONSISTENT WITH REQUEST
OUT OF SPACE IN CATALOG
I/O ERROR IN CATALOG
UNABLE TO COMPLETE REQUEST (rc)

Reason:
Your request could not be serviced because of one of the listed conditions. The last
message indicates an unexpected return (rc) from the CATALOG macro. The return code
is printed. The following is the correspondence between return code and message:
■ 4 - CVOL NOT ONLINE OR CONTAINS NO CATALOG
■ 8 - DSNAME INCONSISTENT WITH REQUEST
■ 14 - OUT OF SPACE IN CATALOG
■ 1C - I/O ERROR IN CATALOG
■ rc - UNABLE TO COMPLETE REQUEST (rc)

Action:
Perform the following actions:
■ Correct the condition that caused the problem.
■ Abandon the request.

UTL3-32

COMMAND REJECTED BY USER EXIT

Reason:
User exit SASSXX03 rejected your request.

Action:
Contact your installation specialist for assistance in determining why the request was
rejected.

Chapter 8: SPO0 - XTRK Messages 1709

UTLx

UTL4-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the time and date shown.

Action:
None.

UTL4-00

dsname SCRATCHED FROM volume [AND UNCATALOGED]

Reason:
The data set name indicated was scratched from the specified volume. If indicated, the
data set was uncataloged as well.

Action:
None.

UTL4-00

dsname SCRATCHED FROM volume BUT NOT UNCATALOGED (rc)

Reason:
The data set was scratched from the identified volume but could not be uncataloged as
indicated by the return code (rc).

Action:
Contact your installation specialist for assistance.

UTL4-00

dsname ON volume RENAMED newname

Reason:
The data set has been renamed but not necessarily cataloged.

Action:
None.

1710 Message Reference Guide

 UTLx

UTL4-00

dsname ON volume RENAMED newname AND UNCTLGD, BUT NOT RECTLGD (rc)

Reason:
The data set has been renamed. The old name has been deleted from the OS catalog,
but the new name could not be cataloged as indicated by the return code (rc).

Action:
Contact your installation specialist for assistance.

UTL4-00

dsname ON volume RENAMED newname AND RECATALOGED

Reason:
The data set has been renamed. The old name has been deleted from the OS catalog,
and the new name has been added.

Action:
None.

UTL4-00

dsname ON volume RENAMED volume BUT NOT UNCATALOGED (rc)

Reason:
The data set was renamed successfully, but the old name could not be uncataloged as
indicated by the return code (rc).

Action:
Contact your installation specialist for assistance.

UTL4-00

dsname UNCATALOGED [FROM cvol]

Reason:
The data set is uncataloged.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1711

UTLx

UTL4-02

LOC(08) DATA SET NOT FOUND

Reason:
The requested data set was not found.

Action:
Correct and reenter.

UTL4-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL4-12

SCR(01) DATASET NOT FOUND ON volume

SCR(03) DATASET IS DATE PROTECTED
SCR(04) VTOC I/O ERROR
SCR(rc) INVALID RETURN CODE

Reason:
An invalid return code was passed from the OS SCRATCH macro.

Action:
Consider the following actions:
■ For (03), use the SCRATCHP command if you want.
■ For (rc), contact your installation specialist for assistance.

1712 Message Reference Guide

 UTLx

UTL4-13

REN(01) DATASET NOT FOUND ON volume

REN(03) NEWNAME ALREADY EXISTS ON volume
REN(04) VTOC I/O ERROR
REN(rc) INVALID RETURN CODE

Reason:
An invalid return code was passed from the OS RENAME macro.

Action:
For (rc), contact your installation specialist for assistance.

UTL4-14

VOLUME volume NOT AVAILABLE TO CA-7

Reason:
The CA Workload Automation SE execution JCL has no DD statement to allow access to
the volume identified.

Action:
Before your request can be processed, a DD statement for the requested volume must
be added to the execution JCL and CA Workload Automation SE must be reinitialized, or
the ALLOC command must be entered to dynamically allocate the volume.

UTL4-15

UNCATALOG ERROR (rc)

Reason:
The uncatalog request could not be completed. The return code from the OS macro is
displayed.

Action:
If in error, correct the data set name and retry.

Chapter 8: SPO0 - XTRK Messages 1713

UTLx

UTL4-32

COMMAND REJECTED BY USER EXIT

Reason:
User exit SASSXX03 rejected your request.

Action:
Contact your installation specialist for assistance in determining why the request was
rejected.

UTL5-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the time and date shown.

Action:
None.

UTL5-00

INDEXES SUCCESSFULLY DELETED FOR nn LEVELS

Reason:
Information only message.

Action:
None.

UTL5-00

GDG INDEX BUILT FOR nnn ENTRIES (FULL=action)

Reason:
This message is informational.

Action:
None.

1714 Message Reference Guide

 UTLx

UTL5-00

DCONN FUNCTION SUCCESSFUL

Reason:
This message is informational.

Action:
None.

UTL5-00

index CONNECTED TO volume

Reason:
This message is informational.

Action:
None.

UTL5-00

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL5-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

Chapter 8: SPO0 - XTRK Messages 1715

UTLx

UTL5-12

(08) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

(20) OUT OF SPACE IN CATALOG
(28) I/O ERROR IN CATALOG
(rc) CATALOG MANAGEMENT ERROR

Reason:
Problem can occur while building and cataloging a dummy index.

Action:
CA Workload Automation SE utilities cannot be used with VSAM or ICF catalogs. Use
IDCAMS.

UTL5-13

(rc) CATALOG MANAGEMENT ERROR

Reason:
Problem can occur when uncataloging an index.

Action:
Be sure you are using the correct utility for database access method.

1716 Message Reference Guide

 UTLx

UTL5-14

(rc) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

Reason:
Problem can occur when issuing the BLDG command on a VSAM catalog. Probable
causes are:
■ CA Workload Automation SE is using the IBM CAMLIST Structure, which is limited to
use with CVOL catalogs.
■ The necessary index structure is not built.

Action:
Several actions are possible:
■ If the catalog is a VSAM catalog, use some other means outside of CA Workload
Automation SE to build the index, for example, IDCAMS.
■ If attempting to do a BLDG for A.B.C, then do the following CA Workload
Automation SE commands:
– CAT,DSN=A.B.X,VOL=A,DVC=00000000
– BLDG,INDX=A.B.C, plus any other needed parameters
– UNC,DSN=A.B.X

UTL5-15

(08) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

Reason:
Error occurred while processing a DCONN command.

Action:
Several actions are possible:
■ If the catalog is a VSAM catalog, use some other means outside of CA Workload
Automation SE to build the index, for example, IDCAMS.
■ If attempting to do a BLDG for A.B.C, then do the following CA Workload
Automation SE commands:
– CAT,DSN=A.B.X,VOL=A,DVC=00000000
– BLDG,INDX=A.B.C, plus any other needed parameters
– UNC,DSN=A.B.X

Chapter 8: SPO0 - XTRK Messages 1717

UTLx

UTL5-16

(08) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

Reason:
Error occurred while processing a CONN command.

Action:
Several actions are possible:
■ If the catalog is a VSAM catalog, use some other means outside of CA Workload
Automation SE to build the index, for example, IDCAMS.
■ If attempting to do a BLDG for A.B.C, then do the following CA Workload
Automation SE commands:
– CAT,DSN=A.B.X,VOL=A,DVC=00000000
– BLDG,INDX=A.B.C, plus any other needed parameters
– UNC,DSN=A.B.X

UTL5-17

(04) REQD VOLUME NOT AVAILABLE OR HAS NO CATALOG

(rc) CATALOG STRUCTURE INCONSISTENT WITH REQUEST
(12) INDEX IS ACTIVE AND CANNOT BE DELETED
(20) OUT OF SPACE IN CATALOG
(28) I/O ERROR IN CATALOG
(rc) CATALOG MANAGEMENT ERROR

Reason:
Your request could not be completed because of the listed condition. The OS macro
return code is printed in parentheses. These messages usually occur during a DLTX.

Action:
Correct the condition that caused the problem or abandon the request.

UTL5-18

VOL= MAY NOT BE SYSRES VOLUME

Reason:
A request was made to CONNect the SYSRES volume to itself. This is clearly in error.

Action:
Correct the VOL parameter and reenter.

1718 Message Reference Guide

 UTLx

UTL5-19

INDEX NOT CONNECTED

Reason:
A request was made to list the connected volume for an index, but the index is not
connected.

Action:
None.

UTL5-32

COMMAND REJECTED BY USER EXIT

Reason:
User exit SASSXX03 rejected your request.

Action:
Contact your installation specialist for assistance in determining why the request was
rejected.

UTL6-00

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Reason:
The request completed at the time and date shown.

Action:
None.

UTL6-00

dsname ALLOCATED ON volume AND SUCCESSFULLY CATALOGED | BUT UNABLE TO

CATALOG[(RC=rc)]

Reason:
The data set has been successfully allocated. Either the data was cataloged correctly or
could not be cataloged.

Action:
Determine why the data set could not be cataloged and take necessary action.

Chapter 8: SPO0 - XTRK Messages 1719

UTLx

UTL6-05

INVALID OR OMITTED keyword DATA

Reason:
The keyword specified was omitted or incorrectly entered.

Action:
Correct and retry.

UTL6-12

RDJF(04) REQUIRED DASD VOLUME NOT AVAILABLE

Reason:
Either the required DASD is not online or a DD statement is not available to CA
Workload Automation SE to access that volume. The OS macro issued and the return
code are printed.

Action:
If you want, insert a DD statement in the CA Workload Automation SE execution JCL to
access that volume the next time CA Workload Automation SE is initialized, or use the
ALLOC command to dynamically allocate the volume.

UTL6-13

DYNAMIC ALLOCATION ONLY AVAILABLE FOR MVS

Reason:
ALLOC command was issued but the operating system is not MVS.

Action:
None.

1720 Message Reference Guide

 UTLx

UTL6-14

DATASET ALREADY EXISTS ON VOLUME

OUT OF SPACE IN VTOC
I/O ERROR IN VTOC
INSUFFICIENT SPACE ON VOLUME
ALLOCATION ERROR (RC=rc)

Reason:
Only one message is printed depending on the situation. For the last message, the
allocation return code is displayed. (See the Direct-Access Data Storage Management
document.)

Action:
If possible, try to allocate the data set to another volume.

UTL6-32

COMMAND REJECTED BY USER EXIT

Reason:
User exit SASSXX03 rejected your request.

Action:
Contact your installation specialist for assistance in determining why the request was
rejected.

UTL6-99

[(ALLOC)|(DEALLOC)] FAILED -- R15=rc FLAGS=xxxxxxxxx

Reason:
An attempt was made to do an online allocation or a deallocation for a volume that is
already allocated/deallocated by a //U7volser DD statement in the CA Workload
Automation SE execution JCL.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1721

WPxx

UTL6-99

[(ALLOC)|(DEALLOC)] SUCCESSFUL FOR DDNAME=//U7volume

Reason:
The indicated command completed successfully for the volume requested.

Action:
None.

WPxx
This section contains the WPxx messages.

WP00-10

ERROR ENCOUNTERED IN EDITOR.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
See WP20-xx or WP21-xx messages.

WP00-20

ERROR ENCOUNTERED IN SIMULATOR.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
See WP50-xx or WP51-xx messages.

1722 Message Reference Guide

 WPxx

WP00-30

ERROR ENCOUNTERED IN LOG SPLITTER.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
Check sort output messages for possible JCL error on job file SIMLOG or UCC7LOG DD.

WP00-40

ERROR ENCOUNTERED IN REPORT GENERATOR.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
See WP80-xx message.

WP20-01

EXPECTED CONTINUATION NOT FOUND.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
Correct listed input record and resubmit.

WP20-02

MISSING REQUIRED PARAMETER.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
Check documentation for omitted parameter, correct and resubmit.

Chapter 8: SPO0 - XTRK Messages 1723

WPxx

WP20-03

INVALID OPERATION FIELD.

Reason:
SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.

Action:
Correct control statement and resubmit.

WP20-04

MISSING CONTROL CARD INFORMATION.

Reason:
Neither WLP1 nor WLP2 was specified as a PARM or in the WLPCC data set.

Action:
Insert either control statement, but not both, and resubmit.

WP20-05

MISSING RES OR JOB CARD.

Reason:
The editor completed processing the UCC7WLP DD data set without encountering at
least one RES and one JOB data statement. If a RES statement is not encountered,
UCC7RDFL cannot act as the default because a time factor must be indicated.

Action:
Resubmit with input containing at least one RES statement and one JOB statement.

WP20-06

WLPCC FILE NOT OPENED.

Reason:
No PARM value was specified on the EXEC statement of the JCL and no WLPCC DD was
included in the JCL.

Action:
Make sure that PARM information is supplied in the JCL on the EXEC statement, or that
a WLPCC DD points to an 80-character, card-image control statement.

1724 Message Reference Guide

 WPxx

WP20-07

UCC7WLP FILE NOT OPENED.

Reason:
The WLP1 command was specified and no UCC7WLP DD was included in the JCL.

Action:
Make sure that a UCC7WLP DD statement is included to point to resource and job input
information in 80-character, card-image format.

WP20-08

RESFILE FILE NOT OPENED.

Reason:
The work file necessary for WLP1 processing was not specified properly in the JCL.

Action:
Make sure RESFILE DD statement is included. It may refer to a temporary data set.

WP20-09

JOBFILE FILE NOT OPENED.

Reason:
The work file necessary for WLP1 processing was not specified properly in the JCL.

Action:
Make sure JOBFILE DD statement is included for both WLP1 and WLP2. It may refer to a
temporary data set.

WP20-10

RES WORK FILE NOT SUCCESSFULLY SORTED.

Reason:
Invalid return code passed from SORT involved in WLP20.

Action:
Check SORT generated SYSOUT messages for errors.

Chapter 8: SPO0 - XTRK Messages 1725

WPxx

WP20-11

JOB WORK FILE NOT SUCCESSFULLY SORTED.

Reason:
Invalid return code passed from SORT involved in WLP20.

Action:
Check SORT generated SYSOUT messages for errors.

WP20-12

INVALID VALUE FOR SPAN

Reason:
The acceptable values for SPAN on the WLP2 statement are 01 to 99. See the Report
Reference Guide.

Action:
Correct the entry and try again.

WP20-13

INVALID DATE/TIME SPECIFIED

Reason:
DATE/TIME value for FROM or TO on the WLP2 statement is in error. FROM must be
less than TO. Values entered must be in the format of yyddd/hhmm. See the Report
Reference Guide.

Action:
Correct the entry and try again.

WP21-01

EXPECTED CONTINUATION NOT FOUND.

Reason:
Editor detected continuation error in data statement record.

Action:
Correct indicated input statement and resubmit.

1726 Message Reference Guide

 WPxx

WP21-02

INVALID JOB NAME.

Reason:
Editor detected job name error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-03

INVALID BLANK CARD.

Reason:
Editor detected blank statement error in data statement record.

Action:
Delete blank input statement and resubmit.

WP21-04

INVALID CARD.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-05

INVALID OPERATION FIELD.

Reason:
Editor detected field error in data statement record.

Action:
Correct indicated input statement and resubmit.

Chapter 8: SPO0 - XTRK Messages 1727

WPxx

WP21-06

INVALID DATE.

Reason:
Editor detected date error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-07

INVALID KEYWORD xxxxxxxx.

Reason:
Editor detected keyword error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-08

INVALID VALUE FOR KEYWORD xxxxxxxx.

Reason:
Editor detected parameter error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-09

MISSING VALUE FOR KEYWORD xxxxxxxx.

Reason:
Editor detected keyword error in data statement record.

Action:
Correct indicated input statement and resubmit.

1728 Message Reference Guide

 WPxx

WP21-10

INCOMPLETE OPERAND FIELD.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-11

INVALID VALUE FOR SCHEDULE-ID.

Reason:
Editor detected schedule ID error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-12

MISSING REQUIRED PARAMETER.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-13

INVALID SUBPARAMETER.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

Chapter 8: SPO0 - XTRK Messages 1729

WPxx

WP21-14

INVALID COMMA.

Reason:
Editor detected comma error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-15

BOTH OF MUTUAL EXCLUSIVE KEYWORDS "TO" AND "SPAN" SPECIFIED.

Reason:
Editor detected error on data statement record.

Action:
Correct indicated input statement and resubmit. Valid combinations are FROM,
FROM/TO, or FROM/SPAN.

WP21-16

DUPLICATE KEYWORD.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-17

KEYWORD "T" IS NOT THE 1ST PARAMETER FOLLOWING POSITIONAL PARAMETERS.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

1730 Message Reference Guide

 WPxx

WP21-18

MISSING KEYWORD.

Reason:
Editor detected error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-19

UNBALANCED PARENTHESIS FOR THE SUBPARAMETERS OF THE KEYWORD xxxxxxxx.

Reason:
Editor detected parenthesis error in data statement record.

Action:
Correct indicated input statement and resubmit.

WP21-20

INVALID RESOURCE DEFINITION LOAD MODULE NAME.

Reason:
Editor detected error in data statement record.

Action:
Resource definition modules must begin with UCC7R. Correct indicated RES statement
and resubmit.

WP21-21

RESOURCE LOAD MODULE NOT FOUND

Reason:
The module requested was not found.

Action:
Verify module is on library referenced as STEPLIB. If the module is not there:
■ Create a copy of the module on the STEPLIB library; or,
■ Move a copy of the module to the STEPLIB library; or,
■ Concatenate the library containing the module to the STEPLIB library.

Chapter 8: SPO0 - XTRK Messages 1731

WPxx

WP21-25

MORE THAN 999 DEPENDENCIES FOR A JOB

Reason:
A job was found that had more than 999 dependencies defined.

Action:
The program halts execution at the point where the problem is found. Decrease the
number of dependencies and resubmit the job.

WP50-10

ERROR ENCOUNTERED IN SASSWP51.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is a system
error.

Action:
Contact your installation specialist for assistance.

WP50-20

ERROR ENCOUNTERED IN SASSWP52.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is a system
error.

Action:
Contact your installation specialist for assistance.

WP50-30

INVALID PRIORITY ALGORITHM SPECIFIED.

Reason:
Simulator driver module detected error in indicated SASSWP5x module.

Action:
Correct ALG value on control statement and resubmit.

1732 Message Reference Guide

 WPxx

WP50-40

ERROR ENCOUNTERED IN SASSWP57.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is a system
error.

Action:
Contact your installation specialist for assistance.

WP50-50

ERROR ENCOUNTERED IN SASSWP53.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is a system
error.

Action:
Contact your installation specialist for assistance.

WP50-60

ERROR ENCOUNTERED IN SASSWP56.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is a system
error.

Action:
Contact your installation specialist for assistance.

Chapter 8: SPO0 - XTRK Messages 1733

WPxx

WP50-70

jobname - JOB WAS NOT SUBMITTED.

Reason:
All jobs that fit into the resources specified at the appropriate time would have been
submitted and the last RES statement is currently in effect. Each job that was not ready
to be submitted when sufficient resources were available generates this message. This is
not an error condition.

Action:
No action is necessary for WLP. Jobs could be rescheduled, however, to allow resources
to be available, or a different RES statement definition could be in effect at the
appropriate time.

WP51-10

INVALID JOB INDICATOR.

Reason:
Simulator driver module detected error in indicated SASSWP5x module. This is an
internal system error.

Action:
Contact your installation specialist for assistance.

WP51-20

INVALID D/M JOB RECORD GENERATION.

Reason:
The temporary data set produced by WP20 is incorrectly formatted. This is a system
error.

Action:
Contact your installation specialist for assistance.

1734 Message Reference Guide

 XAGT

WP80-01

NO JOB WAS FOUND DURING THE 8-HR PERIOD FROM yy.ddd/hh:mm TO

yy.ddd/hh:mm

Reason:
No jobs were found for processing during either of the following time spans:
■ For WLP1, the period between the lowest T value on the RES statements and the
end of processing.
■ For WLP2, the period between the FROM and TO (or SPAN) values.

Action:
Not usually an error condition.

XAGT
This section contains the XAGT messages.

XAGT-01

Job xxxxxxxx(yyyyy) zzzzzzzz: Function Not Defined to SASSXAGT

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. The function should be permitted but is not.

Action:
For assistance, contact CA Support at ca.com/support.

XAGT-02

Job xxxxxxxx(yyyyy) zzzzzzzz: Agent Job Type Not Defined in L2AGTBL

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. The agent job type is not known.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1735

XAGT

XAGT-03

Job xxxxxxxx(yyyyy) zzzzzzzz: Error Reading JCLOSEG for Agent Job

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. An I/O error occurred when reading the queue record. This
error typically indicates a larger problem.

Action:
Determine whether you can run other agent jobs successfully.
■ If not, contact CA Support at ca.com/support for assistance.
■ If other jobs are submitted successfully, CANCEL this job (FORCE option may be
required) and try again.

XAGT-04

Job xxxxxxxx(yyyyy) zzzzzzzz: No IAS Address or IAS Inactive

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. The CA Integrated Agent Services (CA IAS) interface is not
available.

Action:
Check to ensure that the XPDEF file initialization AGENTJOB keyword is set to YES. Also
ensure that CA IAS has not been shut down.

XAGT-05

Job xxxxxxxx(yyyyy) zzzzzzzz: SASSAFM2 Module Not Found

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. A required module is missing.

Action:
Check with your site's systems programmer to verify that SASSAFM2 is in the STEPLIB or
LINKLST concatenation. If it is not, contact CA Support at ca.com/support for assistance.

1736 Message Reference Guide

 XAGT

XAGT-06

Job xxxxxxxx(yyyyy) zzzzzzzz: Agent Communication Failure, DIVR RC=aaaa

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. Failure aaaa occurred when attempting to contact the agent.

Action:
Examine the CIAS-10 error message for return code details. For assistance, contact CA
Support at ca.com/support.

XAGT-07

Job xxxxxxxx(yyyyy) zzzzzzzz: No Status/LStatus Supplied

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. The agent did not return an Status or LStatus response to the
request.

Action:
For assistance, contact CA Support at ca.com/support. Be prepared to supply the job
you were running, the agent you were using, and the function you were requesting.

XAGT-08

Job xxxxxxxx(yyyyy) zzzzzzzz:

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. After the XAGT-08 message, either a CAIAS* or AFM2-nnn
message is issued. This message describes the actual cause of the error.

Action:
Check the documentation associated with the second line of this message. For
assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1737

XCAN

XAGT-09

Job xxxxxxxx(yyyyy) zzzzzzzz: "status"

"long status"

Reason:
An attempt was made to issue a function (zzzzzzzz) against an agent job (with a job
name of xxxxxxxx and job number of yyyyy) from the CA-7 Queue Maintenance - CPU
Jobs Status (QM20) panel. The agent returns a status in the first message line and Long
Status (LStatus) response in the second message line.

Action:
Base any action required on the Status and LStatus response. For assistance, contact CA
Support at ca.com/support.

XCAN
This section contains the XCAN messages.

XCAN-10

XPJ jobname(jobno) XCancel Send Failed; ASCII Translate failure

Reason:
An attempt to send a cancel request for an XPJOB with jobname/jobno named failed. A
problem exists with the data translation from EBCDIC to ASCII. The job is canceled from
the CA Workload Automation SE queues. The job may not be canceled ("killed") at the
platform where the CA Workload Automation SE-submitted job is executing.

Action:
Sign in to that platform to kill the process if it is not to continue executing.

1738 Message Reference Guide

 XCAN

XCAN-20

XPJ jobname(jobno) XCancel Send Failed; Node information unavailable

Reason:
An attempt to send a cancel request for an XPJOB with jobname/jobno named failed.
The node information (where the XCancel request should be sent) was not available.
The job is canceled from the CA Workload Automation SE queues. A job cannot be
canceled ("killed") at the node where it is running.

Action:
Sign in to that platform to kill the process if it is not to continue executing.

XCAN-30

XPJ jobname(jobno) XCancel Send Failed; FDBK= xxx Node yyyyyyyy

Reason:
An attempt to send a cancel request for an XPJOB with jobname/jobno named failed.
The CAICCI Send attempt failed for the code given at xxx. The Node name may or may
not display. The job is removed from the CA Workload Automation SE queues.

Action:
Perform the following actions:
■ Check to see if the node is still connected.
■ Issue the /XTASK,M=(CMD,TRACKER,NODEX) command under CA Workload
Automation SE and view the results in the CA 7 WA job log or XPRINT DD data set.
■ Sign in to that platform to kill the process if it is not to continue executing.

XCAN-40

AGENT JOB jobname(jobno) XCancel Failed; Agent Job Type does not exist

Reason:
Attempts to cancel a job running at a CA Workload Automation SE system agent failed
because the agent job type was not defined.

Action:
For assistance, contact CA Support at ca.com/support.

Chapter 8: SPO0 - XTRK Messages 1739

XCAN

XCAN-41

AGENT JOB jobname(jobno) XCancel Failed; Cannot cancel

Reason:
Attempts to cancel a job running at a CA Workload Automation SE system agent failed.
This agent job type does not support cancelling at the agent.

Action:
Log on to the machine running the CA Workload Automation SE system agent to cancel
the executing job.

XCAN-42

AGENT JOB jobname(jobno) XCancel Failed; Agent Job segment not found

Reason:
Attempts to cancel a job running at a CA Workload Automation SE system agent failed.
The agent job segment could not be retrieved. This message usually indicates a larger
problem.

Action:
Contact your site system administrator to see whether there are problems submitting
jobs and issuing commands against the queue (LQ, XQ, and so on). If further assistance
is needed, contact CA Support at ca.com/support for assistance.

XCAN-43

description

Reason:
Attempts to cancel a job running at a CA Workload Automation SE system agent failed.
The common command module returns the cause of the error in the description field.

Action:
For assistance, contact CA Support at ca.com/support. Be prepared to provide the
descriptive text that accompanied this message.

1740 Message Reference Guide

 XCAN

XCAN-44

AGENT JOB jobname(jobno) XCancel Failed; IAS Not Active or Initialized

Reason:
Attempts to cancel a job running at a CA Workload Automation SE system agent failed.
CA Integrated Agent Services (CA IAS) was either never started (XPDEF file initialization
statement AGENTJOB parameter set to NO) or a /IAS,FUNC=STOPCOM command was
issued.

Action:
Contact your site system administrator to determine whether your site permits the
definition and submission of agent jobs, or if your site has temporarily stopped
communications with agents.

XCAN-45

AGENT JOB jobname(jobno) XCancel Failed; Load Failed for SASSAFM2

Reason:
When attempting to cancel an executing CA Workload Automation SE system agent job,
module SASSAFM2 is invoked. Attempts to load this module failed.

Action:
Contact your site's systems programmer to determine whether this module is in the
STEPLIB/LINKLIST concatenation. For assistance, contact CA Support at ca.com/support.

XCAN-47

AGENT JOB jobname(jobno) XCancel Failed; IAS PURGEMSG Failure, RC=yyyy

Reason:
Attempts to cancel a CA Workload Automation SE system agent job failed. This job was
not actually executing at the CA Workload Automation SE system agent. The job was
awaiting transfer to the agent by CA Integrated Agent Services (CA IAS).

Action:
For assistance, contact CA Support at ca.com/support. Have the return code specified in
yyyy available.

Chapter 8: SPO0 - XTRK Messages 1741

XCAN

XCAN-48

AGENT JOB jobname(jobno) XCancel Failed; Cannot find xxxxxxxxxx

Reason:
Depending on the job type being canceled, information from different key records
(denoted by xxxxxxxxxx) is extracted from the Agent VSAM file. The necessary VSAM key
record could not be found. CA Workload Automation SE considers the job canceled.

Action:
If you want to prevent the job from running (or stop the job as it is running), perform
the following actions:
■ Log on to the agent.
■ Cancel the job manually.

For assistance, contact CA Support at ca.com/support.

XCAN-49

AGENT JOB jobname(jobno) XCancel Failed; Error Reading Agent VSAM File

Reason:
Attempts to read the Agent VSAM file to extract information needed to build an agent
cancel request failed. This message indicates a problem with your Agent VSAM file that
can impact other agent job activities. CA Workload Automation SE considers the job
canceled.

Action:
If you want to prevent the job from running (or stop the job as it is running), perform
the following actions:
■ Log on to the agent.
■ Cancel the job manually.

Contact your installation specialist for assistance with the Agent VSAM file problem.

1742 Message Reference Guide

 XDSI

XCAN-50

AGENT JOB jobname(jobno) XCancel Failed; Agent Cancel request not sent

Reason:
Information needed to send a cancel request to the Agent where the job was submitted
is missing. This situation typically occurs when the job is in the RDY queue. This message
indicates that CA Workload Automation SE sent the job to the agent but never received
any feedback from the agent concerning the job's status. CA Workload Automation SE
considers the job canceled.

Action:
If you want to prevent the job from running (or stop the job as it is running), perform
the following actions:
■ Log on to the agent.
■ Cancel the job manually.

XDSI
This section contains the XDSI messages.

XDSI-00

Initialization complete

Reason:
The XCF data set has been successfully initialized.

Note: These are 1024-byte blocks, and each block may contain multiple logical records.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1743

XKPI

XDSI-01

XCF DD statement is missing

Reason:
The DD statement defining the XCF data set was omitted from the initialization JCL.

Action:
Perform the following actions:
■ Add the required DD statement.
■ Resubmit the job.

XDSI-02

XCF data set must be a single extent

Reason:
The XCF data set was not allocated as a single, contiguous extent.

Action:
Scratch and reallocate the data set with CONTIG specified in the JCL.

XDSI-03

XCF data set is too small

Reason:
Not enough space was allocated for the XCF data set.

Action:
Perform the following actions:
■ Increase the space allocation.
■ Resubmit the job.

XKPI
This section contains the XKPI messages.

1744 Message Reference Guide

 XREF

XKPI-00

Initialization complete

Reason:
The XCF checkpoint data set has been successfully initialized.

Action:
None.

XKPI-01

XCFCKPT DD statement is missing

Reason:
The DD statement defining the XCF checkpoint data set was omitted from the
initialization JCL.

Action:
Perform the following actions:
■ Add the required DD statement.
■ Resubmit the job.

XKPI-02

XCFCKPT failed to open

Reason:
The XCF checkpoint data set did not open.

Action:
Ensure the XCFCKPT DD statement is pointing to a valid data set.

XREF
This section contains the XREF messages.

Chapter 8: SPO0 - XTRK Messages 1745

XREF

XREF.001

INVALID RECORD TYPE CODE

Reason:
An invalid database record type code was passed to SASSXREF reporting module. A
database record may be in error.

Action:
Perform the following actions:
■ Save console listings, logs, and dumps.
■ Contact your installation specialist for assistance.

XREF.002

JOB DIR/MEM OUT OF SEQUENCE

Reason:
The directory records, which were written to a work file, were found to be out of
sequence with their corresponding member records on the database backup file.

Action:
Perform the following actions:
■ Save console listings, logs, and dumps.
■ Contact your installation specialist for assistance.

XREF.003

SORT COMPLETION INVALID

Reason:
The sort returned a bad code.

Action:
Perform the following actions:
■ Check for sort error messages.
■ Make corrections.
■ Rerun the job.

1746 Message Reference Guide

 XTRE

XREF.004

LOAD FAILED FOR MODULE SASSHDAT

Reason:
Module SASSHDAT could not be loaded.

Action:
Perform the following actions:
■ Ensure module SASSHDAT is in the STEPLIB load library.
■ Rerun the job.

XREF.005

OPEN FAILED FOR DDN=xxxxxxxx

Reason:
Output file xxxxxxxx could not be opened.

Action:
Perform the following actions:
■ Examine the JCL and job output.
■ Determine why the data set could not be opened.
■ Make corrections.
■ Rerun the job.

XTRE
This section contains the XTRE messages.

XTRE-00

NO CONTROL CARD ERRORS FOUND

Reason:
This is an informational message indicating that the control statement entered was
validated successfully.

Action:
None.

Chapter 8: SPO0 - XTRK Messages 1747

XTRE

XTRE-01

A JOBNAME IS REQUIRED

Reason:
A job name was not entered. It is required by the SASSXTRK program. A return code of
13 is produced with this error message.

Action:
Enter a job name. It can be 1-8 characters in length. An asterisk (*) can be used to
provide a generic job specification. An asterisk (*) cannot be used as the first character.

XTRE-02

THE FROM DATE IS GREATER THAN THE TO DATE

Reason:
The FROM DATE entered is greater than the TO DATE entered. A return code of 23 is
produced with this error message.

Action:
Correct the input and resubmit.

XTRE-03

THE FROM DATE IS GREATER THAN yy366

Reason:
The FROM DATE was specified in the yyddd format. The ddd is greater than 366. A
return code of 33 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-04

THE TO DATE IS GREATER THAN yy366

Reason:
The TO DATE was specified in the yyddd format. The ddd is greater than 366. A return
code of 43 is produced with this error message.

Action:
Correct the input and resubmit.

1748 Message Reference Guide

 XTRE

XTRE-05

THE FROM TIME IS GREATER THAN 2400

Reason:
The FROM TIME that was entered is greater than 2400. The largest value that can be
used is 2400. A return code of 53 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-06

THE TO TIME IS GREATER THAN 2400

Reason:
The TO TIME that was entered is greater than 2400. 2400 is the largest value that can be
used. A return code of 63 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-07

THE FROM TIME IS GREATER THAN TO TIME

Reason:
This message is generated if the FROM and TO dates are the same and if the FROM
TIME is greater than the TO TIME specified. A return code of 73 is produced with this
error message.

Action:
Correct the input and resubmit.

XTRE-08

INVALID FORMAT FOR FROM/TO DATE

Reason:
This message is generated if the specified FROM date, TO date, or both did not have all
numeric input specified. A return code of 83 is produced with this error message.

Action:
Correct the input and resubmit.

Chapter 8: SPO0 - XTRK Messages 1749

XTRE

XTRE-09

CONTROL CARD COLUMNS INCORRECT

Reason:
This message is generated if the control has nonblank characters in columns that should
be blank. See the Report Reference Guide for the required format of the input
statement. A return code of 93 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-10

INVALID FORMAT FOR FROM/TO TIME

Reason:
This message is generated if the specified FROM time, TO time, or both did not have all
numeric input specified. A return code of 103 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-11

FROM DATE REQUIRED FOR JOB=*

Reason:
An "*" was specified for the job name but the FROM DATE field was not supplied. A
return code of 113 is produced with this error message.

Action:
Correct the input and resubmit.

XTRE-12

TO DATE REQUIRED FOR JOB=*

Reason:
An "*" was specified for the job name but the TO DATE field was not supplied. A return
code of 123 is produced with this error message.

Action:
Correct the input and resubmit.

1750 Message Reference Guide

 XTRK

XTRK
This section contains the XTRK messages.

XTRK-01

xxxxxxxx DD NOT OPENED SUCCESSFULLY

Reason:
This message indicates that the open for the indicated DD statement failed (SYSIN or
LOGIN). Both of these ddnames are required for execution. This message is a WTO. A
return code of 01 is produced with this error message.

Action:
Ensure that both DD statements are present and resubmit the job.

XTRK-02

INVALID LRECL FOUND FOR LOGIN

Reason:
The LRECL for the LOGIN data set is not valid. A return code of 02 is produced with this
error message.

Action:
Check the JCL and resubmit the job.

XTRK-03

LOAD FAILED FOR SASSXTRE

Reason:
A LOAD was done for the module SASSXTRE and it was not found. A return code of 03 is
produced with this error message.

Action:
Ensure that the SASSXTRE module is in the STEPLIB for this job and resubmit the job.

Chapter 8: SPO0 - XTRK Messages 1751

XTRK

XTRK-04

JOBNAME LENGTH IS ZERO

Reason:
The job name that was entered on the control statement has an invalid length. A return
code of 04 is produced with this error message.

Action:
Correct the control statement and resubmit the job.

XTRK-05

NO RECORDS SELECTED

Reason:
No records were found meeting the selection criteria. A return code of 05 is produced
with this error message.

Action:
None.

XTRK-06

NO CONTROL CARD SPECIFIED

Reason:
No control card was used for SYSIN.

Action:
Add the control card and rerun the job.

1752 Message Reference Guide

Appendix A: Database Verification
(DBVR)
This chapter contains the database verification (DBVR) messages.

000 Through 255 Messages

This section contains the 000 through 255 messages.

000

INVALID MSG REQUEST.

Reason:
Indicates a program error.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.

001

INVALID PARM OPTION.

Reason:
Indicates a parameter error.

Action:
Check the PARM and/or DBVPARM DD input in the execution JCL for valid keywords.

002

NO PARM INFORMATION GIVEN.

Reason:
Indicates a parameter error.

Action:
Add PARM or DBVPARM DD statement.

Appendix A: Database Verification (DBVR) 1753

000 Through 255 Messages

003

JOBDS DD STATEMENT MISSING.

Reason:
Indicates a misspelled or omitted DD statement.

Action:
Add the JOBDS DD statement.

004

DSDS DD STATEMENT MISSING.

Reason:
Indicates a misspelled or omitted DD statement.

Action:
Add the DSDS DD statement.

005

DSDS MEMBER OPEN PROBLEM.

Reason:
Could not open the Dataset data set for processing members.

Action:
Check to see if you have the correct data set name.

006

JOB MEMBER OPEN PROBLEM.

Reason:
Could not open the Job data set for processing members.

Action:
Check to see if you have the correct data set name.

1754 Message Reference Guide

 000 Through 255 Messages

007

TOO MANY INPUTS WERE SPECIFIED IN PARM OR DBVPARM.

Reason:
Only one input IDS type can be specified.

Action:
Submit with one input type of
INCTLG/INVSAM/PDSCVOL/PDSVSAM/ALLVSAM.

008

NO INPUTS WERE SPECIFIED BUT ONE WAS NEEDED.

Reason:
An IDS input is required if IDSVERFY is specified.

Action:
Resubmit with an input type of INCTLG, INVSAM, or ALLVSAM.

009

TOO MANY OUTPUTS WERE SPECIFIED IN PARM OR DBVPARM.

Reason:
Only one IDS output type can be specified when converting the Index data set.

Action:
Resubmit with only one IDS output type of OUTCTLG or OUTVSAM for conversion only.

010

DSDS DIRECTORY ENTRY HAS NO MEMBER DATA DIR xxnnnnnn.

Reason:
Indicates a bad Dataset data set entry.

Action:
If nnnnnn is zero, this message is informational and no real error exists. Otherwise,
contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: DUMP,DSNBR=xxnnnnnn, and an
LCTLG,DSN=AUTO.xxnnnnnn. Also, run SASSBK00 with the XREF parameter.

Appendix A: Database Verification (DBVR) 1755

000 Through 255 Messages

011

JOB MEMBER HAS NO JOB ENTRY RECORD TYPE JOB xxxxxxxx.

Reason:
Indicates a bad job entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: DUMP,JOB=xxxxxxxx,LIST=BYENT

012

INVALID RECORD TYPE IN JOB MEMBER JOB xxxxxxxx.

Reason:
Indicates a bad job entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: DUMP,JOB=xxxxxxxx,LIST=BYENT

013

INVALID 1ST CHARACTER OF THE MEMBER NAME ON THE DATA SET DATASET.
MEMBER -- nnnnnnnnnnnnnnnn.

Reason:
Invalid Dataset data set entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, run SASSBK00 with the XREF parameter and have the
output available.

1756 Message Reference Guide

 000 Through 255 Messages

014

INVALID 1ST CHARACTER OF THE MEMBER NAME ON THE JOB DATASET. MEMBER --
nnnnnnnnnnnnnnnn.

Reason:
Invalid job entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, run SASSBK00 with the XREF parameter and have the
output available.

015

PARAMETER CONFLICT FOR ALLVSAM DATA BASE.

Reason:
ALLVSAM cannot be specified in combination with any prior IDS type.

Action:
One of the following was specified with ALLVSAM; INCTLG, INVSAM, OUTCTLG,
OUTVSAM, PDSCVOL, PDSVSAM. Remove the conflicting parameter and resubmit.

016

ALLVSAM ERROR ATTEMPTING INIT/CONN/DISCON/FINISH, RC=xxxx.

Reason:
Errors occurred while attempting to initialize, connect, disconnect, or finish with an
ALLVSAM database. RC value gives error code which is further explained by WTO
messages.

Action:
Diagnose problem from WTO messages and take appropriate action.

Appendix A: Database Verification (DBVR) 1757

000 Through 255 Messages

017

ERROR ON JOB DIR, RC=xxxx.

Reason:
Logic or I/O error occurred while accessing job directory type entries. RC value gives
error code and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

018

ERROR ON JOB MEM, RC=xxxx.

Reason:
Logic or I/O error occurred while accessing job member type entries. RC value gives
error code and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

019

ERROR ON DSDS DIR, RC=xxxx.

Reason:
Logic or I/O error occurred while accessing data set directory type entries. RC value
gives error code and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

020

ERROR ON DSDS MEM, RC=xxxx.

Reason:
Logic or I/O error occurred while accessing data set member type entries. RC value gives
error code and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

1758 Message Reference Guide

 000 Through 255 Messages

021

ERROR ON IDS, RC=xxxx.

Reason:
Logic or I/O error occurred while accessing index type entries. RC value gives error code
and WTO message gives specifics on error.

Action:
Diagnose problem from WTO messages and take appropriate action.

050

DATA SET DS- NETWORK DIR. HAS NO ASSOCIATED IDS ENTRY -

NW-DIR-NWnnnnnn,IDS-KEY-NW.network name.

Reason:
Invalid network entry in Dataset data set.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an
LCTLG,DSN=NW.network name.

051

DATA SET DS-NETWORK DIR. INDICATES AN INPUT SCHEDULE - NONE WAS FOUND. -
NW-DIR-NWnnnnnn,SCH-DIR-SInnnnnn.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an
LCTLG,DSN=NW.network name.

Appendix A: Database Verification (DBVR) 1759

000 Through 255 Messages

052

DATA SET DS-NETWORK DIR. INDICATES AN OUTPUT SCHEDULE - NONE WAS FOUND. -
NW-DIR-NWnnnnnn,SCH-DIR-SOnnnnnn.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an
LSCHD,DSNBR=SOnnnnnn.

053

DATA SET DS- JOB SCH.DIR. HAS NO ASSOCIATED JOB DIR. MEMBER - SJ-DIR
SJnnnnnn,JOB-DIR-xxxxxxxx.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LJOB,JOB=xxxxxxxx and an
LSCHD,DSNBR=SJnnnnnn.

054

DATA SET DS- JOB SCH.DIR. POINTS TO A JOB DIR. BUT DOESN'T POINT BACK
SJ-DIR-SJnnnnnn,JOB-DIR-xxxxxxxx.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LJOB,JOB=xxxxxxxx and an
LSCHD,DSNBR=SJnnnnnn.

1760 Message Reference Guide

 000 Through 255 Messages

055

DATA SET DS- PROSE DIR. HAS NO ASSOCIATED IDS ENTRY - PP-DIR-PPnnnnnn
IDS-KEY-PP.dsname.

Reason:
Invalid prose pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LPROS,DSNBR=PPnnnnnn and an
LCTLG,DSN=PP.dsname.

056

JOB DS- JOB DIR. INDICATES IT TRIGGERS OTHER JOBS. - NO IDS ENTRY WAS FOUND -
JOB-DIR-xxxxxxxx,IDS-KEY-JDEP.dsname.

Reason:
Invalid schedule pointer.

Action:
If there should be triggers, rebuild them on the DB.2.4 (SCHD,JTRG) panel. If there
should not be any triggers, add a dummy trigger on the DB.2.4 (SCHD,JTRG) panel and
then delete the dummy trigger.

057

JOB DS- JOB DIR. INDICATES IT HAS A JOB SCHEDULE. - NONE WAS FOUND
-JOB-DIR-xxxxxxxx,SJ-DIR-SJnnnnnn.

Reason:
Invalid job pointer.

Action:
Delete the schedule on the DB.2.1 (SCHD,JOB) panel.

Appendix A: Database Verification (DBVR) 1761

000 Through 255 Messages

058

JOB DS- JOB DIR. POINTS TO A JOB SCHEDULE BUT IT DOESN'T POINT BACK -
JOB-DIR-xxxxxxxx,SJ-DIR-SJnnnnnn.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LJOB,JOB=xxxxxxxx and an
LSCHD,DSNBR=SJnnnnnn.

059

DATA SET DS- DATA SET MBR. INDICATES -AUTO- IDS ENTRY NOT FOUND
-DS-MBR-DSnnnnnnnn.

Reason:
Invalid data set pointer.

Action:
If there should be triggers, rebuild them on the DB.2.6 (SCHD,DTRG) panel. If there
should not be any triggers, add a dummy trigger on the DB.2.6 (SCHD,DTRG) panel and
then delete the dummy trigger.

060

DATA SET DS- DATA SET MBR. HAS NO ASSOCIATED IDS ENTRY - DS-MBR-DSnnnnnnnn
- IDS-KEY-dsname.

Reason:
Invalid data set pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: DUMP,DSNBR=DSnnnnnnnn and an
LCTLG,DSN=dsname.

1762 Message Reference Guide

 000 Through 255 Messages

062

DATA SET DS- DATA SET MBR. MEMBER NAME DOESNT MATCH DIRECTORY MEMBER
NAME - DS-MBR-DSnnnnnnnn, DS-DIR-DSmmmmmmmm.

Reason:
Invalid data set entry.

Action:
If nnnnnnnn is zero, then the message is only informational and no real error exists.
Otherwise, contact your installation specialist, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available:

DUMP,DSNBR=DSnnnnnnnn,
DUMP,DSNBR=DSmmmmmmmm,
LDSN,DSNBR=DSnnnnnnnn,LIST=ALL,
LDSN,DSNBR=DSmmmmmmmm,LIST=ALL and run SASSBK00 with the XREF parameter.

063

DATA SET DS- NETWORK MBR. INDICATES -AUTO- IDS ENTRY NOT FOUND -
NW-MBR-NWnnnnnn,IDS-KEY-AUTO.network name.

Reason:
Invalid network pointer.

Action:
If there should be triggers, rebuild them on the DB.2.5 (SCHD,NTRG) panel. If there
should not be any triggers, add a dummy trigger on the DB.2.5 (SCHD,NTRG) panel and
then delete the dummy trigger.

Appendix A: Database Verification (DBVR) 1763

000 Through 255 Messages

064

DATA SET DS- NETWORK MBR. HAS NO ASSOCIATED IDS ENTRY -

NW-MBR-NWnnnnnn, IDS-KEY-NW.network name.

Reason:
Invalid network entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LCTLG,DSN=NW.network name,
LNTWK,DSNBR=NWnnnnnn,LIST=ALL, and
LCTLG,DSN=NW.station name(from the LNTWK command).network name for all
stations.

065

DATA SET DS- INPUT NW. SCHED. MBR. HAS NO ASSOCIATED IDS ENTRY
SI-MBR-SInnnnnn,IDS-KEY-NW.network name.

Reason:
Invalid network entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LCTLG,DSN=NW.network name,
LNTWK,NW=network name, and LSCHD,DSNBR=SInnnnnn.

066

DATA SET DS- INPUT NW. SCHED.MBR. POINTS TO AN IDS ENTRY. NO NETWORK WAS
FOUND - SI-MBR-SInnnnnn,IDS-KEY NW.network name.

Reason:
Invalid network entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LCTLG,DSN=NW.network name,
LNTWK,NW=network name, and LSCHD,DSNBR=SInnnnnn.

1764 Message Reference Guide

 000 Through 255 Messages

067

DATA SET DS- INPUT NW. SCHED. MBR. POINTS TO A NETWORK BUT DOES NOT POINT
BACK - SI-MBR-SInnnnnn,MEMBER-NWmmmmmm.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,DSNBR=NWmmmmmm, and
LSCHD,DSNBR=SInnnnnn.

068

DATA SET DS- OUTPUT NW. SCHED. MBR. HAS NO ASSOCIATED IDS ENTRY -
SO-MBR-SOnnnnnn,IDS-KEY-NW.network name.

Reason:
Invalid network entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,NW=network name and
LSCHD,DSNBR=SOnnnnnn.

069

DATA SET DS- OUTPUT NW. SCHED. MBR. POINTS TO AN IDS ENTRY. NO NETWORK
WAS FOUND - SO-MBR-SOnnnnnn, IDS-KEY NW.network name.

Reason:
Invalid network entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,NW=network name and
LSCHD,DSNBR=SOnnnnnn.

Appendix A: Database Verification (DBVR) 1765

000 Through 255 Messages

070

DATA SET DS- OUTPUT NW. SCHED. MBR. POINTS TO A NETWORK BUT DOES NOT
POINT BACK - SO-MBR-SOnnnnnn,MEMBER-NWmmmmmm.

Reason:
Invalid schedule pointer.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LNTWK,DSNBR=NWnnnnnn and
LSCHD,DSNBR=SOnnnnnn.

071

DATA SET DS- PROSE MBR. HAS NO ASSOCIATED IDS ENTRY - PP.xxxxxxxx
PP-MBR-PPnnnnnn.

Reason:
Invalid prose entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LPROS,DSNBR=PPnnnnnn and
LPROS,DSN=PP.xxxxxxxx.

073

DATA SET DS- PROSE MBR. POINTS TO A DS. MBR. NONE WAS FOUND - PP-MBR-
PPnnnnnn,DS-MBR-DSmmmmmmmm.

Reason:
Invalid prose entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available: LPROS,DSNBR=PPnnnnnn and
LDSN,DSNBR=DSmmmmmmmm.

1766 Message Reference Guide

 000 Through 255 Messages

074

DATA SET DS- PROSE MBR. POINTS TO A DS. MBR. NO IDS ENTRY WAS FOUND -
PP-MBR-PPnnnnnn - IDS-KEY-PP.dsname.

Reason:
Invalid prose entry.

Action:
Contact your installation specialist for assistance, who may want to contact CA Support.
Before contacting CA Support, enter these commands using the Batch Terminal
Interface and have the output available:

LPROS,DSNBR=PPnnnnnn,
LPROS,DSN=PP.dsname and
LCTLG,DSN=PP.dsname.

101

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
For assistance, contact CA Support at ca.com/support.

102

TOTAL NUMBER OF EDITS PERFORMED ON THE NETWORK DIRECTORIES - nnnn TOTAL

ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

Appendix A: Database Verification (DBVR) 1767

000 Through 255 Messages

103

TOTAL NUMBER OF EDITS PERFORMED ON THE PROSE DIRECTORIES - nnnn TOTAL

ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

104

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

105

TOTAL NUMBER OF EDITS PERFORMED ON THE JOB SCHEDULE DIRECTORIES - nnnn

TOTAL ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

106

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

1768 Message Reference Guide

 000 Through 255 Messages

107

TOTAL NUMBER OF EDITS PERFORMED ON THE JOB DIRECTORIES - nnnn TOTAL

ERRORS xxxx.

Reason:
Totals, not an error.

Action:
None.

108

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

109

TOTAL NUMBER OF EDITS PERFORMED ON THE DATA SET MEMBERS - nnnn TOTAL
ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

110

TOTAL NUMBER OF EDITS PERFORMED ON THE NETWORK MEMBERS - nnnn TOTAL

ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

Appendix A: Database Verification (DBVR) 1769

000 Through 255 Messages

111

TOTAL NUMBER OF EDITS PERFORMED ON THE PROSE MEMBERS - nnnn TOTAL

ERRORS xxxx.

Reason:
Totals, not an error.

Action:
None.

112

TOTAL NUMBER OF EDITS PERFORMED ON THE INPUT NETWORK SCHEDULE

MEMBERS - nnnn TOTAL ERRORS xxxx.

Reason:
Totals, not an error.

Action:
None.

113

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

114

TOTAL NUMBER OF EDITS PERFORMED ON THE OUTPUT NETWORK SCHEDULE

MEMBERS - nnnn TOTAL ERRORS xxxx.

Reason:
Totals, not an error.

Action:
None.

1770 Message Reference Guide

 000 Through 255 Messages

115

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

116

RESERVED - AN INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

117

TOTAL NUMBER OF EDITS PERFORMED ON THE JOB ENTRY MEMBERS - nnnn TOTAL
ERRORS - xxxx.

Reason:
Totals, not an error.

Action:
None.

118-132

RESERVED - AN INTERNAL ERROR

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

Appendix A: Database Verification (DBVR) 1771

000 Through 255 Messages

200

IDS ENTRY SUCCESSFULLY BUILT ON VSAM/CVOL RECORD KEY -- dsname.

Reason:
Tracking message, not an error.

Action:
None.

201

A BAD RETURN FROM VSAM - GENCB BLK-ACB.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
GENCB macros for a description of the problem.

202

A BAD RETURN FROM VSAM - GENCB BLK-RPL - OPT-DIR.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
GENCB macros for a description of the problem.

203

CAN NOT OPEN VSAM FILE --- ERROR CODE - nnn.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
OPEN macros for a description of the problem.

1772 Message Reference Guide

 000 Through 255 Messages

204

A BAD RETURN FROM GET VSAM -- RETURN-nnn, FUNCTION-mmm, FDBK-xxx.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
REQUEST macros for a description of the problem.

205

A BAD OPEN ON DDNAME - DBVTRACE.

Reason:
JCL error.

Action:
Add the DBVTRACE DD to the JCL.

206

A BAD OPEN FOR VSAM FILE ON DDNAME - IDSOUT.

Reason:
JCL error.

Action:
Add the IDSOUT DD to the JCL.

207

A BAD OPEN ON DDNAME - DSDS.

Reason:
JCL error.

Action:
Add the DSDS DD to the JCL.

Appendix A: Database Verification (DBVR) 1773

000 Through 255 Messages

208

A BAD OPEN ON DDNAME - JOBDS.

Reason:
JCL error.

Action:
Add the JOBDS DD to the JCL.

209

WARNING MESSAGE FROM OPEN VSAM -- REG. 15-n ---ERROR CODE - xxx.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
OPEN macros for a description of the problem. If error code=116 and REG 15=4, run an
IDCAMSS VERIFY against the data set.

210

COULD NOT DO LOCATE ON OS CVOL BECAUSE OUTPUT RETURN AREA WAS TOO
SMALL -- YOU MUST INCREASE AREA SIZE.

Reason:
Area size problems.

Action:
Contact your installation specialist for assistance.

211

A BAD JFCB READ ON OUTPUT OS CVOL DDNAME - IDSOUT.

Reason:
JCL problem.

Action:
Add the IDSOUT DD to the JCL.

1774 Message Reference Guide

 000 Through 255 Messages

212

A BAD JFCB READ ON INPUT OS CVOL DDNAME - IDSIN.

Reason:
JCL problem.

Action:
Add the IDSIN DD to the JCL.

213

A BAD RETURN FROM VSAM - GENCB BLK-EXLST.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
GENCB macros for a description of the problem.

214

A BAD RETURN FROM VSAM - GENCB BLK-RPL - OPT-SEQ.

Reason:
VSAM problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets for return codes from
GENCB macros for a description of the problem.

215

A BAD OPEN ON DDNAME - SYSPRINT.

Reason:
JCL problem.

Action:
Add the ddname SYSPRINT to the JCL.

Appendix A: Database Verification (DBVR) 1775

000 Through 255 Messages

216

A BAD RETURN FROM A LINK TO IEHLIST.

Reason:
The IBM IEHLIST must be in one of your system load libraries.

Action:
If not, concatenate the library under STEPLIB.

217

A BAD RETURN FROM A OS CVOL BY CAMLIST REG. 15-nnn.

Reason:
CAMLIST problem.

Action:
Check the IBM manual DFSMS Macro Instructions for Data Sets on exceptional return
codes for a description of the problem.

218

IDS OUT OF SEQUENCE. IDS RECORD DELETED. DSN- DSNAME.

Reason:
The input IDS was out of sequence. All records are deleted until it is back in sequence.

Action:
Check the messages in DBVTRACE to see what causes it to go out of sequence.

219

TOTAL IDS RECORDS WRITTEN - nnnnnn.

Reason:
Totals, not an error.

Action:
None.

1776 Message Reference Guide

 000 Through 255 Messages

220

TOTAL IDS RECORDS WITH ONE VCB. ENTRY - nnnnnn.

Reason:
Totals, not an error.

Action:
None.

221

TOTAL IDS RECORDS WITH SEVEN VCB. ENTRIES - nnnnnn.

Reason:
Totals, not an error.

Action:
None.

222

AVERAGE IDS LRECL - nnnnnn.

Reason:
Totals, not an error.

Action:
None.

223

MAX. IDS LRECL - nnnn.

Reason:
Totals, not an error.

Action:
None.

Appendix A: Database Verification (DBVR) 1777

000 Through 255 Messages

255

INTERNAL ERROR.

Reason:
Program problem.

Action:
Contact your installation specialist for assistance.

1778 Message Reference Guide

Appendix B: Abend Codes
This section contains the abend codes.

S806 for NCF

Reason:
The node table was not found. Message CA-7.NC107 usually indicates the name of the
table not found. The level of this error is catastrophic.

Action:
Verify that the node table was assembled and linked correctly and that the library that
contains the table is accessible.

S80A for NCF

Reason:
Not enough storage is available for initialization. The VTAM application creates a
number of control blocks for each node in the table, and not enough storage is available
to accommodate the amount of storage required. The level of this error is catastrophic.

Action:
To calculate the storage requirements based on the number of nodes in the network,
see the system requirements in chapter "NCF" in the Interface Reference Guide. Increase
the region size and resubmit. Also verify that the CA71 tracking instance is active and
that a valid node table was accessible to CAIRIM at the time the instance was added.

SB0A for NCF

Reason:
Not enough storage is available for initialization. The VTAM application creates a
number of control blocks for each node in the table and not enough storage was
available to accommodate the amount of storage required. The level of this error is
catastrophic.

Action:
To calculate the storage requirements based on the number of nodes in the network,
see the system requirements in the chapter "NCF" in the Interface Reference Guide.
Increase the region size and resubmit. Also verify that the CA71 tracking instance is
active and that a valid node table was accessible to CAIRIM at the time the instance was
added.

Appendix B: Abend Codes 1779

000 Through 255 Messages

U0001 for ICOM

Reason:
The PARM contains invalid data.

Action:
Correct the PARM and start ICOM.

U0414 for CA 7

Reason:
A security module is not found. Check for the WTO CA-7.906.

Action:
Verify that the security module indicated by the CA-7.906 WTO is available.

U0503 for ICOM

Reason:
ICOM cannot find the specified ddname in the command data set.

Action:
If ICOM is to submit jobs, verify that the command data set is formatted with
appropriate ddnames.

U3313 for NCF

Reason:
The node table was not found. See also error message CA-7.NC107. The level of this
error is catastrophic.

Action:
Verify that the node table was assembled and linked correctly and that the library that
contains the table is accessible.

1780 Message Reference Guide

 000 Through 255 Messages

U3314 for NCF

Reason:
The node table contains more nodes than the installation is authorized to operate. The
level of this error is catastrophic.

Action:
Decrease the nodes in the table to the authorized number. To increase the nodes
authorized, contact CA Support at http://ca.com/support for assistance.

U3315 for NCF

Reason:
Not enough storage is available for initialization. The VTAM application creates a
number of control blocks for each node in the table and not enough storage is available
to accommodate the amount of storage required. The level of this error is catastrophic.

Action:
See the chapter "NCF" in the Interface Reference Guide to calculate the storage
requirements based on the number of nodes in the network. Increase the region size
and resubmit.

U3316 for NCF

Reason:
Unsuccessful VTAM ACB open. See message CA-7.NC202 for specific information
regarding the type of error. The level of this error is catastrophic.

Action:
Review the reason for the error in message CA-7.NC202 and try to resolve the problem.
If it continues, contact CA Support at http://ca.com/support for assistance.

U3317 for NCF

Reason:
Data set I/O error. The message preceding the abend indicates which data set had the
problem. The level of this error is catastrophic.

Action:
Verify that the data set exists and is specified correctly in the JCL. Determine if the data
set has been corrupted. Correct the problem and resubmit. If assistance is required,
contact CA Support at http://ca.com/support for assistance.

Appendix B: Abend Codes 1781

000 Through 255 Messages

U3318 for NCF

Reason:
An internal logic error has been detected. The level of this error is catastrophic.

Action:
Review any error messages that were issued before the abend, save all listings and the
dump and contact CA Support at http://ca.com/support for assistance.

U3319 for NCF

Reason:
An NCF system initialization error has occurred. Message CA-7.NC113 or CA-7.NC114
accompanies this abend.

Action:
See the appropriate message for further action.

1782 Message Reference Guide

Appendix C: Master Station Message
Routing
The following list shows messages that can appear as single segments if selected by
Master Station Message Routing (MSMR).

Note: For more information about MSMR and interleaved messages, see the Systems
Programming Guide.

CA-7.023

SATO-15

SATO-20

SATO-35

SATO-36

SATO-37

SATO-38

SATO-39

SCM0-00

SCNJ-14

SCNJ-15

SCNJ-16

SCNJ-17

SCNJ-18

SCNJ-19

Appendix C: Master Station Message Routing 1783

000 Through 255 Messages

SCNP-11

SCRJ-12

SCRJ-14

SCRJ-48

SCRJ-60

SJL0-00

SJL0-01

SJL0-03

SJL0-11

SJL0-12

SJL0-13

SJL1-01

SMF0-13

SMF0-15

SMF0-17

SMF0-19

SMF0-20

SMF0-21

SPO7-00

SSM0-C0

SSM0-C1

SSM0-00

1784 Message Reference Guide

 000 Through 255 Messages

SSM0-1C

SSM0-28

SSM0-33

SSM0-34

SSM0-35

SSM0-36

SSM0-37

SSM0-39

SSM0-40

SSM0-41

SSM0-42

SVPR-50

SVPR-51

SVPR-65

SVPR-66

SVPR-67

Appendix C: Master Station Message Routing 1785