Dynamic Symbolic Support Messages

Messages › Dynamic Symbolic Support Messages

Dynamic Symbolic Support Messages

CAIN5900I

mm/dd/yyyy hh:mm:ss IN25NDVR STARTED FOR PRGNNAME – pppppppp.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This is an informational message indicating that the Listing Server is retrieving the symbolic for program named pppppppp. This message is used to serve as a beginning bookmark for message extraction. All messages issued after this message are extracted by message extraction service.

Action:

None.

CAIN5903E

mm/dd/yyyy hh:mm:ss IN25NSRV CCI SPNPARM FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI SPNPARM request. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5903E

mm/dd/yyyy hh:mm:ss IN25NSRV CCI INIT FAILED.

Reason:

This message is issued by IN25NSRV. where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. CCI INIT action has failed. This error occurred when IN25NSRV issued a CCI INIT request. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5904I

mm/dd/yyyy hh:mm:ss IN25NSRV WAITING FOR WORK.

Reason:

Action:

None.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, INVALID DATA.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received are invalid. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, RECEIVED NULLS.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received contained all null values. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to inspect the block received. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, INVALID LENGTH.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and length of the data block received was incorrect. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to inspect the length of data block received. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5907E

mm/dd/yyyy hh:mm:ss IN25NSRV SENDSPEC FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Send action. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the reasons for the failure. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5908W

mm/dd/yyyy hh:mm:ss IN25NSRV GETMAIN FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. The message indicated that GETMAIN for 32K of main storage has failed.

Action:

Make sure that you have specified a sufficiently large region size to meet the many main storage requirements of the Listing service.

CAIN5909I

mm/dd/yyyy hh:mm:ss IN25NSRV REQUEST RECEIVED FOR eeeeeeee.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This is an informational message indicating that a listing request for element named eeeeeeee has been received.

Action:

None.

CAIN5913I

mm/dd/yyyy hh:mm:ss IN25NSRV SENDING RESPONSE

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This is an informational message indicating that the request by message CAIN5909 has been serviced and response is being sent back to the remote host.

Action:

None.

CAIN5930I

mm/dd/yyyy hh:mm:ss IN25NSRV CCI FEEDBACK: feedback info.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This is the message that is usually issued in conjunction with CCI-related error conditions. Feedback is a 256 bytes area containing CCI return codes, reason codes, and brief description associated with the error encountered.

Action:

Use the information provided in this message in conjunction with the failure message to diagnose the error.

CAIN5950I

mm/dd/yyyy hh:mm:ss IN25NSRV SHUTDOWN.

Reason:

Action:

None.

CAIN5970W

LINK TO IN25SPOL FAILED.

Reason:

This message is issued by IN25NSRV indicating that LINK to IN25SPOL has failed. Message extraction will not be performed.

Action:

Determine that the data set containing IN25SPOL is either defined in the LINKLIST or is properly defined in the STEPLIB concatenations.

CAIN5980E

CA SCM CRITICAL ERROR. ERROR CODE: eeee. REQUEST FOR pppppppp NOT SERVICED.

Reason:

This message is issued by IN25NSRV and is used as an end bookmark for message extraction. All messages issued before this message are extracted by the message extraction service.

Action:

None.

CAIN5990I

ALLOCATION OF LOG FILE FAILED. LOGGING DISABLED.

Reason:

This message is issued by IN25FSYM, indicating that dynamic allocation for SRVPRINT DD has failed. Logging activities is disabled. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed.

Action:

Determine and correct the cause for failure then retry the action.

CAIN5990I

LINK TO IN25SPOL FAILED.

Reason:

This message is issued by IN25NSRV. LINK SVC for IN25SPOL has failed. Message extraction will not be performed.

Action:

Make sure that the data set containing IN25SPOL is either defined in the LINKLIST or properly defined in the STEPLIB DD.

CAIN5991W

HHMM DOES NOT MATCH.

Reason:

This message is issued by IN25FSYM. The hour and minute of the timestamp found in the symbolic does not match the timestamp provided by the caller for the same symbolic. Requested action is not performed.

Action:

Provide the correct timestamp value and try the action again.

CAIN5995E

NO PROTSYM SEARCH LIST PROVIDED.

Reason:

This message is issued by IN25FSYM. User did not provide one or more PROTSYM data set names to perform symbolic search. Requested action is not performed.

Action:

Provide at least one or up to a maximum of eight PROTSYM fully qualified data set names to be used for symbolic search.

CAIN6000E

DYNAMIC UNALLOCATION FAILED FOR nnnnnnnn. RC= rr. RSN= ssssssss.

Reason:

This message is issued by IN25FSYM. Dynamic unallocation of data set with nnnnnnnn DD name has failed. Return code from Dynamic Allocation is rr and the reason code is ssssssss.

Action:

Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action.

CAIN6010W

LOAD OF pppppppp FAILED. RC= rr.

Reason:

This message is issued by IN25FSYM. Loading of program named pppppppp has failed. The return code is rr.

Action:

Make sure that the data set containing the pppppppp program is in the LINKLIST or defined in the STEPLIB concatenation.

CAIN6020W

FAILED IN ROUTINE: rrrrrrrrrr RC= rr.

Reason:

This message is issued by IN25FSYM. Routine named rrrrrrrr has failed with a return code of rr. This message is usually associated with IN25SAPI and rrrrrrrr is the failed SAPI function.

Action:

Determine the error and retry the request.

CAIN6070E

CRITICAL ERROR LD@DSSDSN INVALID VALUE.

Reason:

This message is issued by IN25FSYM. The data set name provided in LD@DSSDSN is invalid.

Action:

LD@DSSDSN should contain a valid DD name to be used for DSS logging. It is usually specified as DSSLOG. Correct the DD name and retry the action.

CAIN7000W

IN25NDVR MAJOR ERROR, LOG FILE NOT OPENED

Reason:

SRVPRINT log file not opened. Endevor activity log disabled.

Action:

We recommend that //SRVPRINT DD SYSOUT=* be defined in the job’s JCL so that relevant error can be captured to assist in problem analysis. This would avoid the need to recreate the error.

CAIN7010I

IN25NDVR ALLOCATION OF LOG FILE FAILED.

Reason:

Dynamic allocation of activity log has failed. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed.

Action:

Determine and correct the cause of the error and retry the request.

CAIN7020W

LOAD OF IN25DALC FAILED.

Reason:

IN25NDVR encountered an error trying to LOAD IN25DALC. Endevor List request will not be performed.

Action:

Make sure that the data set containing IN25DALC load module is either defined in the LINKLIST or is defined in the STEPLIB concatenation.

CAIN7030W

LOAD OF ENA$NDVR FAILED.

Reason:

IN25NDVR cannot LOAD the Endevor API. Endevor List request will not be performed.

Action:

Make sure that Endevor AUTHLIB and CONLIB data sets are either defined in the LINKLIST or defined in the job’s JCL.

CAIN8000W

JESMSGLG JCT MTTR FOUND.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicates that MTTR of JESMSGLG JCT was found.

Action:

None.

CAIN8010I

JESYSMSG JCT MTTR FOUND.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicates that MTTR of JESMSGLG JCT was found.

Action:

None.

CAIN8020I

ACQUIRED MSGLOG AND SYSMSG JCT

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This message indicates that the JCT for JESMSGLG and JESYSMSG have been acquired.

Action:

None.

CAIN8030W

UNABLE TO ACQUIRE JCT OF EITHER JESMSGLG OR JESYSMSG.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicated that IN25SPOL was unable to acquire the JCT of either JESMSGLG or JESYSMSG. Message extraction will not be performed.

Action:

Call CA Technical Support with the information.

CAIN8040I

STIMER WAIT FOR JQE UPDATE.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicated that IN25SPOL has issued a STIMER SVC to wait for JQE update to complete.

Action:

None.

CAIN8050I

THERE ARE NO SJQES RETURNED.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ did not return SJQES information. Message extraction will not be performed.

Action:

None.

CAIN8060I

THERE ARE NO SOUTS RETURNED.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ did not return SOUTS information. Message extraction will not be performed.

Action:

None.

CAIN8070I

UNABLE TO ACCESS JOB QUEUE.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ was unable to access JES job queue.

Action:

None.

CAIN8080I

IN25SS71 LOAD FAILED.

Reason:

This message is issued by IN25SPOL indicating that loading of IN25SS71 has failed.

Action:

Make sure that the data set containing IN25SS71 is either in the LINKLIST or the STEPLIB concatenation is properly defined.

CAIN8090I

IN25SDSB LOAD FAILED.

Reason:

This message is issued by IN25SPOL indicating that loading of IN25SDSB has failed.

Action:

Make sure that the data set containing IN25SDSB is either in the LINKLIST or the STEPLIB concatenation is properly defined

CAIN8091I

jjjj IS THE PRIMARY JOB ENTRY SUBSYSTEM. SYSTEM ID FROM JQRYSSID ===> iiii.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating that jjjj is the primary job entry subsystem whose id is iiii.

Action:

None.

CAIN8092I

dddddddd IS THE DDN OF jjjjjjjj RETURNED.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating dddddddd is the DD name of jjjjjjjj returned. jjjjjjjj can either be JESMSGLG or JESYSMSG.

Action:

None.

CAIN8093I

ASSOCIATED DSN: datasetname.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating that the fully qualified data set name for the DD name cited in message CAIN8092 is datasetname.

Action:

None.

CAIN8094I

JOBNAME: jobname JOBID: iiiiiiii

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating that the active job name is jobname whose jobid is iiiiiiii.

Action:

None.

CAIN8095I

IEFSSREQ TYPE=QUERY FAILED. RETURN CODE= cccc REASON CODE= ssss

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ type of query has failed with a return code of cccc and reason code of ssss.

Action:

Determine the cause of failure based on the return code and reason code.

CAIN8096I

IEFSSI SUBFUNCTION 80 FAILED. SSOBRETN= rrrr STATREAS= ssss.

Reason:

This message is issued by IN25SPOL indicating that IEFSSI subfunction 80 has failed. The subsystem return code is rrrr and reason code is ssss. Message extraction will not be performed.

Action:

Call CA Technical Support.

CAIN8097I

JESMSGLG dddddddd NOT FOUND.

Reason:

This message is issued by IN25SPOL indicating that dddddddd token for JESMSGLG is not found.

Action:

None.

CAIN8098W

POSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.

Reason:

This message is issued by IN25SPOL indicating that IN252POL was unable to locate SSVE control blocks via chaining through various JES control blocks. Message extraction will not be performed. General Purpose Register 8 points to the chain.

Action:

Call CA Technical Support.

CAIN8100I

SPOOL READ FUNCTION CURRENTLY DOES NOT SUPPORT JES3 AT BELOW ZOS 01.11.01 LEVEL.

Reason:

This message is issued by IN25SPOL indicating that spool read function does not support JES3 at a level below ZOS 01.11.01 level. Message extraction will not be performed.

Action:

None.

CAIN8100I

STARTING MSGLOG00 PROCESS.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that message extraction of JESMSGLG is being started.

Action:

None.

CAIN8110I

STARTING SYSMSG00 PROCESS.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that message extraction of JESYSMSG is being started.

Action:

None.

CAIN8120I

OBTAINED JCT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71. It is an informational message indicating that JCT information was obtained from in-storage buffer.

Action:

None.

CAIN8120I

OBTAINED IOT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71. This is an informational message indicating that IOT information was obtained from in-storage buffer.

Action:

None.

CAIN8130E

INVALID REQUEST.

Reason:

This message is issued by IN25SS71. This is a should not occur error.

Action:

Call CA Technical Support.

CAIN8140W

FAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.

Reason:

This message is issued by IN25SS71 indicating that it cannot locate the PDDBs for JESMSGLG and JESYSMSG.

Action:

Call CA Technical Support.

CAIN8150I

JESMSGLG BUFR IS EMPTY

Reason:

This message is issued by IN25SS71 indicating that the JESMSGLG buffer is empty. Message extraction cannot be performed.

Action:

None.

CAIN8160I

MSGLOG OBTAINED FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESMSGLG messages were extracted from in-storage buffer.

Action:

None.

CAIN8170I

MSGLOG READ FROM LAST TRACK.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESMSGLG messages were extracted from the last track specified in MTTR.

Action:

None.

CAIN8180I

MSGLOG RECORD COUNT EXHAUSTED.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESMSGLG messages extraction has exhausted its record count.

Action:

None.

CAIN8190I

SYSMSG RECORD COUNT IS ZERO.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESYSMSG record count is zero.

Action:

None.

CAIN8200I

SYSMSG OBTAINED FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESYSMSG information was extracted from in-storage buffer.

Action:

None.

CAIN8210I

SYSMSG RECORD COUNT EXHAUSTED.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESYSMSG messages extraction has exhausted its record count.

Action:

None.

CAIN8230I

SYSMSG READ FROM LAST TRACK.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that JESYSMSG messages were extracted from the last track specified in MTTR.

Action:

None.

CAIN8240E

SUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= cccc SSJIRETN= ssss.

Reason:

This message is issued by IN25SS71 indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return code is rrrr, subsystem reason code is cccc, subsystem return code is ssss. Message extraction is not performed.

Action:

Call CA Technical Support with the error message.

CAIN8260W

OUTPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SS71 indicating that open attempt of output DCB for JOBLOG DD statement has failed. Message extraction will not be performed.

Action:

Determine the reason for open failure. DD statement: //JOBLOG DD SYSOUT=* may be missing.

CAIN8270I

NO MORE SYSOUT FROM JES.

Reason:

This message is issued by IN25SS71 indicating end of file condition has reached.

Action:

None.

CAIN8300I

JCT RETREIVAL ERROR.

Reason:

This message is issued by IN25SDSB indicating there was an error retrieving job’s JCT. Message extraction will not be performed.

Action:

None.

CAIN8310I

IOT RETRIEVAL ERROR.

Reason:

This message is issued by IN25SDSB indicating there was an error retrieving job’s IOT. Message extraction will not be performed.

Action:

None.

CAIN8320I

OBTAINED IOT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SDSB when CA Technical Support requests for diagnostic messages. The message indicated that job’s IOT information was obtained from in-storage buffer.

Action:

None.

CAIN8330E

JESMSGLG ALLOCATION FAILED. MSGLOG NOT COLLECTED.

Reason:

This message is issued by IN25SDSB indicating that dynamic allocation of JESMSGLG data set name has failed. Message extraction will not be performed.

Action:

None.

CAIN8340E

JESYSMSG ALLOCATION FAILED. SYSMSG NOT COLLECTED.

Reason:

This message is issued by IN25SDSB indicating dynamic allocation of JESYSMSG data set name has failed. Message extraction will not be performed.

Action:

None.

CAIN8350W

FAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.

Reason:

This message is issued by IN25SDSB indicating that attempts to locate the PDDBs for JESMSGLG and JESYSMSG has failed. Message extraction will not be performed.

Action:

None.

CAIN8360I

SUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= ssss SSJIRETN=nnnn

Reason:

This message is issued by IN25SDSB indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return code is rrrr, subsystem reason code is ssss, subsystem return code is nnnn. Message extraction is not performed.

Action:

Call CA Technical Support with this message.

CAIN8380I

JESMSGLG ALLOCATED. DDNAME: dddddddd

Reason:

This message is issued by IN25SDSB when CA Technical Support requests for diagnostic messages. The message provides the dynamic allocation returned DDNAME as dddddddd.

Action:

None.

CAIN8390I

JESMSGLG DYNAMIC ALLOCATION FAILED. RC/RSN: rrrr/ssss

Reason:

This message is issued by IN25SDSB indicating that dynamic allocation of SYSOUT for JESMSGLG has failed. The dynamic allocation return code is rrrr, its reason code is ssss. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed. Message extraction will not be performed.

Action:

Determine and correct the cause for the failure, than retry the request.

CAIN8400W

INPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SDSB indicating that open of input DCB has failed. The two input data sets involved are JESMSGLG and JESYSMSG. When these data sets were allocated successfully, open should not fail. Message extraction will not be performed.

Action:

Determine and correct the cause of the failure, and retry the request.

CAIN8410I

INPUT DDNAME: sys E N D O F F I L E

Reason:

This message is issued by IN25SDSB indicating the end of file condition for DD named sys has reached.

Action:

None.

CAIN8410W

OUTPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SDSB indicating that open of JOBLOG SYSOUT has failed.

Action:

Verify that //JOBLOG DD SYSOUT=* is defined in the job’s JCL.

SYM Messages

SYM002

LISTER= OPTION INVALID, NO LISTING SAVED

Reason:

The LISTER option was invalid.

Action:

Correct the LISTER option and resubmit your job stream.

SYM003

CUTPRINT= OPTION INVALID, LISTING WILL BE PRINTED

Reason:

The CUTPRINT option was invalid.

Action:

Correct the CUTPRINT option and resubmit your job stream.

SYM004

SYMBOLIC INFORMATION HAS BEEN SET AS NON-PURGABLE

Reason:

The NOPURGE option was specified on the parameter statement.

Action:

None.

SYM005

PARAMETER OPTIONS INVALID, SYMBOLIC STEP NOT RUN

Reason:

An invalid option was specified on the parameter statement.

Action:

Correct the parameter statement and resubmit your job stream.

SYM006

LISTER=XXX REQUESTED

Reason:

This identifies the LISTER option specified.

Action:

None.

SYM007

CUTPRINT=XXX REQUESTED

Reason:

This identifies the CUTPRINT option specified.

Action:

None.

SYM008

CONTROL STATEMENT IS MISSING - JOB TERMINATED

Reason:

No parameter statement was found.

Action:

Correct the parameter statement and resubmit your job stream.

SYM009

PROTSYM HAS REACHED MAXIMUM NUMBER OF PROGRAMS

Reason:

The symbolic file has exceeded the maximum number of program entries.

Action:

Delete some programs for your file and resubmit your job stream, or define a new PROTSYM file and then resubmit your job stream using the new file.

SYM010

PROCESSING HAS BEGUN FOR PROGRAM NAME - XXXXXXXX

Reason:

Program xxxxxxxx will be processed and its output will reside on the symbolic file.

Action:

None.

SYM011

SEQUENCE NUMBERS ARE NOT IN ASCENDING SEQUENCE. JOB WILL BE TERMINATED - CONTACT CA

Reason:

This is an internal verification check error.

Action:

Contact Technical Support.

SYM012

RECORD COUNT ERROR AT XXXXXXX

Reason:

This is an internal verification check error.

Action:

Contact Technical Support.

SYM013

QQQQ ERROR R15 = X'YY' ERROR CODE = X'ZZ'

Reason:

A VSAM request, qqqq, has resulted in an error. The maximum number of program entries has been reached. This usually indicates a corrupted symbolic file.

Action:

Contact Technical Support.

SYM014

PROTSYM OUT OF SPACE

Reason:

The symbolic file has exceeded the maximum number of records.

Action:

Delete some programs for your file or increase the size of your symbolic file. Then resubmit your job stream. Or, define a new PROTSYM file and then resubmit your job stream using the new file.

SYM015

DD STATEMENT MISSING FOR PROTSYM

Reason:

The DD statement for the symbolic file could not be found.

Action:

Correct the JCL and resubmit the job stream.

SYM016

ENQ ERROR - CODE = X'YY'

Reason:

In VSE, an error occurred when an SVC 63 (ENQ) was issued. This is normally caused by a NOT FOUND condition for the symbolic file.

Action:

Check the JCL and correct. If you still cannot determine the cause of this error, Contact Technical Support.

SYM017

UTILITY IN PROGRESS ON PROTSYM FILE - JOB TERMINATED

Reason:

The CA InterTest batch utility program was processing the symbolic file at the same time that the postprocessor step was running.

Action:

First ensure that the last UTILITY run was successful. To turn off this indicator, run a UTILITY job with a REPORT function.

SYM018

MAIN STORAGE NOT AVAILABLE - INCREASE REGION SIZE

Reason:

A GETMAIN (MVS) or GETVIS (VSE) request has failed due to insufficient storage.

Action:

Resubmit the job stream with a larger region size.

SYM019

PROGRAM ABENDED 111 AT DISPLACEMENT XXXXX

Reason:

A condition has occurred that required a termination with a dump.

Action:

Contact Technical Support.

SYM020

SYMBOLIC FILE UPDATED SUCCESSFULLY

Reason:

The postprocessor has ended successfully and the program has been added to the symbolic file.

Action:

None.

SYM021

XXXXXX SOURCE STATEMENTS SAVED

Reason:

On a successful completion, the number of source statements, xxxxxxx, displays.

Action:

None.

SYM022

YYYY TOTAL RECORDS INSERTED INTO SYMBOLIC FILE

Reason:

On a successful completion, the total number of records added to the symbolic file, yyyy, displays.

Action:

None.

SYM023

POST-PROCESSOR TERMINATED

Reason:

The CA InterTest postprocessor program has ended.

Action:

None.

SYM024

NPUT FILE PROCESSED

Reason:

The CA InterTest postprocessor program has read all of the data passed to it in the INPUT data set.

Action:

None.

SYM025

PROCEDURE NAMES CROSS-REFERENCE NOT FOUND

Reason:

The procedure names cross-reference output area was not found.

Action:

Without this area, CA InterTest is unable to process any requests using a PARAGRAPH NAME. If PARAGRAPH NAMES are needed, correct the COBOL options and resubmit the job stream.

SYM026

INPUT FILE IS EMPTY

Reason:

The data set specified by the INPUT JCL statement was empty.

Action:

Correct and resubmit the job stream.

SYM027

CAPEX OPTION ERROR - MLIST MUST BE SPECIFIED

Reason:

The required CA Optimizer (CAPEX) option MLIST was not specified.

Action:

Correct and resubmit the job stream.

SYM028

COBOL COMPILER OPTIONS ARE INCORRECT - XXXX - NOT FOUND

Reason:

Area xxxxx could not be found in the COBOL listing. For working storage, at least one data item must be declared.

Action:

Correct COBOL compiler options or add a working storage data item to produce the required area and resubmit the job stream.

SYM029

XXXXX NOT REQUESTED - PROCESSING TERMINATED

Reason:

The required COBOL II option, xxxxx, was not specified.

Action:

Correct and resubmit the job stream.

SYM030

NO CSECT FOUND - PLEASE REMOVE ANY PRINT NOGEN STATEMENTS THAT MIGHT PREVENT THE CSECT STATEMENT FROM BEING PRINTED

Reason:

After examining the entire Assembler listing, no labeled CSECT could be found.

Action:

Correct and resubmit the job stream.

SYM031

INPUT IS FROM COMMAND TRANSLATOR

Reason:

The input passed to the CA InterTest postprocessor program was generated by the CICS command translator and not by the compiler or Assembler.

Action:

Correct the procedure so that the passed output is from the compiler/Assembler.

SYM032

OPEN FOR INPUT FAILED

Reason:

The INPUT file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.

Action:

Correct the JCL and resubmit the job stream.

SYM033

OPEN FOR OUTPUT FAILED

Reason:

The OUTPUT file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.

Action:

Correct the JCL and resubmit the job stream.

SYM034

OPEN FOR CARDS FAILED

Reason:

The CARDS file could not be opened. Check the printed output for additional error messages that may have been produced by the operating system.

Action:

Correct the JCL and resubmit the job stream.

SYM035

NO CROSS-REFERENCE FOUND - SYMBOLIC NAMES CANNOT BE USED

Reason:

The Cross-Reference area could not be found in the Assembler listing. Without this area, symbolic names cannot be resolved.

Action:

Resubmit the job stream with the XREF (SHORT) or XREF (FULL) Assembler parameter.

SYM036

PASSED PARAMETER STATEMENTS

Reason:

The next group of printed lines will be an echo of all the parameter statements read by the postprocessor.

Action:

None.

SYM038

XXX LINK-EDITOR MAP RECORD(S) HAVE BEEN ADDED TO ENTRY

Reason:

The IN25LINK program has added xxx linkage editor records to an existing symbolic entry.

Action:

None.

SYM039

NO LINK-EDITOR ENTRY FOUND FOR XXXXXXXX

Reason:

The link-name, xxxxxxxx, specified on an IN25LINK postprocessor control card could not be found in the output produced by the linkage editor.

Action:

You can do one of the following:

Ignore the error.
Correct the parameter card and resubmit the job stream.
Use the CNTL Composite Support menu to add the information online. If the LISTER parameter is omitted, no listing is saved in the symbolic file.

SYM040

THE FOLLOWING OPTIONS WERE NOT SPECIFIED

Reason:

The list of options following this message was not specified. Without these options, some CA InterTest facilities may not function.

Action:

Correct the JCL and resubmit the job stream.

SYM042

NO STATEMENT INFORMATION WAS FOUND IN THE PASSED LISTING

Reason:

The postprocessor program could not find the data needed to process the statement information.

For a COBOL program, this data is produced by the CLIST or PMAP compiler option.
For a COBOL II program, this data is produced by the OFFSET or LIST compiler option.
For a CA Optimizer program, this data is produced by the MLIST option.
For a CA Optimizer/II program, this data is produced by the MOFFSET option.

The following are some of the conditions that may cause this error:

Errors in the compile which cause the suppression of the data.
Incorrect compiler options.
Compiler control statements that suppress the needed data.

Action:

Determine why the required area was suppressed. Correct and resubmit the job stream.

SYM043

THE CSECT NAMED XXXXXXX WAS NOT FOUND IN THE EXTERNAL SYMBOL DICTIONARY

Reason:

In a VSE Assembler, a CSECT statement named xxxxxxx was found, but that name could not be found in the ESD list.

Action:

Correct the JCL and resubmit the job stream.

SYM044

INPUT DATA WAS NOT PRODUCED BY THE LINKAGE-EDITOR

Reason:

The data passed to the IN25LINK postprocessor using the INPUT JCL statement did not contain the output produced by the linkage editor step, or the linkage editor PARM=MAP is not in effect.

Action:

Correct the JCL and resubmit the job stream.

SYM045

INVALID POWER PARAMETER FORMAT

Reason:

The POWER parameter was specified incorrectly.

Action:

Correct the parameter card and resubmit the job stream.

SYM046

INVALID POWER CLASS SPECIFIED (NOT A - Z)

Reason:

The POWER LST class specified on the parameter card was not an alphabetic character.

Action:

Correct the parameter card and resubmit the job stream.

SYM047

INVALID POWER JOB NAME

Reason:

The name specified in the POWER parameter is invalid.

Action:

Correct the parameter card and resubmit the job stream.

SYM048

IN25PWRI, POWER INTERFACE MODULE, WAS NOT FOUND

Reason:

The CA InterTest module, IN25PWRI, was not found in the load library specified in the JCL. This module is required when using the VSE/POWER LST queue.

Action:

You can do one of the following:

Change the JCL to point to a load library that contains the IN25PWRI module.
Change the JCL to use SYSLST instead of POWER.

SYM049

IN25OPTS MODULE NOT FOUND - DEFAULTS ARE USED

Reason:

Module IN25OPTS was not found in the load library specified in the JCL.

Action:

If the default POWER options can be used, no action is required. However, we recommend that the correct IN25OPTS module be added to the load library.

SYM050

POWER INTERFACE IS NOT ACTIVE

Reason:

The POWER parameter was specified incorrectly.

Action:

Correct the parameter card and resubmit the job stream.

SYM051

SYNTAX ERROR IN WH= OPTION

Reason:

A syntax error was found in the CA Realia/II Workbench Host Option parameter.

Action:

Correct the parameter card and resubmit the job stream.

SYM052

WH= SOURCE FILE OPTION IS INCORRECT

Reason:

An error was found in the CA Realia/II Workbench Host Option parameter.

Action:

Correct the parameter card and resubmit the job stream.

SYM053

WH= MEMBER NAME IS MISSING OR INCORRECT

Reason:

An error was found in the CA Realia/II Workbench Host Option parameter.

Action:

Correct the parameter and resubmit the job stream.

SYM054

REALIA WORKBENCH HOST OPTION WAS REQUESTED WITHOUT HAVING A LISTER OPTION SPECIFIED

Reason:

The LISTER option was not specified in the CA Realia/II Workbench Host Option parameter.

Action:

The LISTER=ALL option is set by default.

SYM055

REALIA WORKBENCH HOST OPTION INTERFACE MODULE WAS NOT LINKED WITH THIS MODULE

Reason:

The CA Realia/II Workbench Host Option Interface Module was not linked.

Action:

Correct and resubmit the job.

SYM056

A CA LMP RIMSTAT ERROR HAS BEEN DETECTED

Reason:

The CA License Management Program is not properly installed.

Action:

Ensure that you have the proper level of CA Common Services for z/OS installed.

SYM057

CSECT NAME 'XXXXXXXX' IS GT 8 BYTES. CSECT IGNORED

Reason:

CSECT name is greater than 8 bytes.

Action:

Correct and resubmit the job.

SYM058

HLASM OPTION "LIST(133|MAX)" IS NOT SUPPORTED. USE OPTION "LIST(121)".

Reason:

HLASM option LIST(133|MAX) is not supported.

Action:

Correct the option by using LIST(121).

SYM059

HLASM OPTION "NOTHREAD" IS NOT SUPPORTED. USE OPTION "THREAD".

Reason:

The NOTHREAD option is not supported.

Action:

Correct the option by using the THREAD option (IBM default).

SYM090

ATTEMPT TO UPDATE SAM RECORD VIA DATA RPL

SYM091

ATTEMPT TO UPDATE DATA RECORD VIA SAM RPL

SYM092

ATTEMPT TO UPDATE DIRECTORY RECORD VIA DATA RPL

SYM093

ATTEMPT TO UPDATE DATA RECORD VIA DIRECTORY RPL

SYM094

NO ENQ IS SET FOR A XXXXXX

SYM095

DIRECTORY RECORD IS CORRUPTED

SYM097

MISMATCH ON AVAILABLE FREE RECORDS IN ONE SAM

SYM Messages 2-11

Symbolic Post-Processor Program Messages

SYM960

MAX SAM RECS EXCEEDED. PROTSYM FILE MAY BE CORRUPTED

SYM961

MAX DIR RECS EXCEEDED. PROTSYM FILE MAY BE CORRUPTED

Reason:

Error messages SYM090 to SYM097, and SYM960 to SYM961 are produced by a special checkout procedure.

This procedure looks for conditions that corrupt the symbolic file. If any of the conditions are found, one of the above messages is issued, and the batch processor program abends.

Action:

For assistance in handling these errors, contact Technical Support.

SYMP001I

**** INTERTEST VERSION ID: x.x COMPILED: dd mm yy hh:mm:ss

Reason:

This reason is informative. It identifies the version and compile date and time for the PL/I postprocessor program, IN25SYMP.

Action:

None.

SYMP002I

INTERTEST - PL/I POSTCOMPILER RUN FOR PROGRAM: progname

Reason:

This reason is informative during initialization of IN25SYMP. Processing for the requested program has begun.

Action:

None.

SYMP003I

LISTER RECORDS ADDED TO PROTSYM FILE: nn

Reason:

This reason is informative during termination of IN25SYMP. The number of records used on the PROTSYM file for listing information displays.

Action:

None.

SYMP004I

SYMBOLIC RECORDS ADDED TO PROTSYM FILE: nn

Reason:

This reason is informative during termination of IN25SYMP. The number of records used on the PROTSYM file for symbolic information displays.

Action:

None.

SYMP005I

IN25ASMP RETURN CODE ON FINAL PROCESSING: nn

Reason:

This reason is informative. The final return code from routine IN25ASMP displays.

Action:

None.

SYMP006I

IN25SYMP RETURN CODE ON FINAL PROCESSING: nn

Reason:

This reason is informative. The final return code from routine IN25SYMP displays.

Action:

None.

SYMP101W

BLOCK NAME CANNOT BE RESOLVED. VARIABLE AND PARAMETER RESOLUTION MAY BE AFFECTED. DRC=n BLOCK NAME= blockname

Reason:

A variable was found in the variable storage map section of the compiler output whose associated block cannot be identified.

Action:

Contact Technical Support with program listings.

SYMP102W

VARIABLE DISPLACEMENT CANNOT BE DETERMINED. DRC=n, VARIABLE NAME= variable name

Reason:

A variable was found in the variable storage map section of the compiler output whose associated attributes could not be identified.

Action:

Make sure all data names are unique within each block.

SYMP103W

PARAMETER DISPLACEMENT CANNOT BE DETERMINED. DRC=n, PARAMETER NAME= parameter name

Reason:

A parameter passed to a procedure could not be resolved and will not be available to the CORE transaction, or an associated block could not be determined.

Action:

Make sure all data names are unique within each block and that no procedure or entry statements are suppressed by %NOPRINT. Check for other error messages.

SYMP104W

BASED/DEFINED VAR PTR/BASE CANNOT BE FOUND. DRC=n, VARIABLE NAME= variable name POINTER NAME = pointer name

Reason:

The pointer associated with a BASED variable or the base variable of a redefined variable (see message SYMP115W) could not be resolved. The pointer name can be the name of the associated pointer or the base area for the redefinition.

Action:

Try simplifying the expression of the base area. For example, use the following syntax to declare a redefined variable:

...BASED( ADDR( variable) )

...DEFINED base_variable...

Also, make sure the variable does not refer to a subscripted array element or qualified name.

SYMP105W

ADDRESSES OF THE FOLLOWING BASED VARIABLES CANNOT BE DETERMINED FROM THE PL/I CROSS REFERENCE. IN ORDER TO ACCESS THESE VARIABLES ON-LINE, YOU MUST SPECIFY A QUALIFIED NAME IN THE INTERTEST CORE COMMAND.

Reason:

One or more BASED (*) variables were found in the PL/I cross reference. IN25SYMP was unable to determine the pointer to the variables specified.

Action:

This reason is informative only. When attempting to view the variable online with CA InterTest for CICS, you must use the POINTER option in the CORE command.

SYMP106W

ADDRESSES OF THE BASED STRUCTURES CONTAINING THE FOLLOWING VARIABLES COULD NOT BE DETERMINED. IN ORDER TO ACCESS THESE VARIABLES ON-LINE, YOU MUST SPECIFY A QUALIFIED NAME IN THE INTERTEST CORE COMMAND.

Reason:

A SYMP105W message was issued for the major structure containing the variable names.

Action:

This reason is informative only. When attempting to view the variable online with CA InterTest for CICS, you must use the POINTER option in the CORE command.

SYMP107W

THE FOLLOWING PL/1 COMPILER OPTION IS REQUIRED IN ORDER FOR IN25SYMP TO PROCESS CORRECTLY compiler option.

Reason:

The listed PL/I compiler option was not specified.

Action:

Be sure that the following options were specified to the PL/I compiler:

AGGREGATE
ATTRIBUTES(FULL)
MAP
NEST
OFFSET

OPTIONS
SOURCE
STMT or GOSTMT
STORAGE
XREF(FULL)

If all of the previous options were not specified, code the appropriate options and rerun the job.

If all of the previous options were specified, ensure that the options section is included in the PL/I compiler listing and that the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return code of 8 or less.

SYMP108W

*** WARNING: "%NOPRINT" OPTION SPECIFIED. ***

Reason:

The NOPRINT option was specified on the control card. This option suppresses checking for the occurrence of the preprocessor control statement %NOPRINT. If the use of this facility suppresses the listing of PROCEDURE or ENTRY statements that contain parameter lists, or suppresses the listing of the final END statement of the program, the results may be unpredictable. Possible effects include the inability to resolve parameter variables properly, as well as possible abnormal termination of SYMP.

Action:

Remove the NOPRINT option or ensure required information is not suppressed.

Note: Indiscriminate use of this option could cause program failure or incorrect results.

SYMP110W

STRUCTURE NAME "IN" ENCOUNTERED WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LIST VARIABLE: variable name STATEMENT NO: statement number

Reason:

While resolving structure nesting information, the identified variable in the specified statement number was found in a major or minor structure named IN. If this is not true, the variable may not be properly resolved.

Action:

None, if the previous condition described is correct. Otherwise, Contact Technical Support.

SYMP111W

UNABLE TO DETERMINE LENGTH OF DATA ITEM. "REFER" OPTION NOT SUPPORTED FOR BASED VARIABLES. VARIABLE: variable name STATEMENT NO: statement number

Reason:

Dynamically sized items are not supported. Examples include string parameters that inherit their size from the calling block, automatic strings whose length is an expression, and based strings whose length is specified by the REFER option. Such variables may not be available to the CORE transaction when debugging.

Action:

None.

SYMP112W

UNEXPECTED CONVERSION ERROR WHILE PROCESSING THE CROSS REFERENCE/ATTRIBUTE LIST FOR: VARIABLE: variable name STATEMENT NO: statement number

Reason:

An unanticipated error occurred during processing of the attribute list.

Action:

Contact Technical Support.

SYMP113W

LABEL DISPLACEMENT CANNOT BE DETERMINED FOR: xxxxxxxx

Reason:

The indicated label could not be associated with its block.

Action:

Make sure label names are unique. Check the statement/offset table for missing or out-of-order entries. Do not use END block-name statements to close multiple blocks.

SYMP114W

NO STORAGE WILL BE ALLOCATED FOR THE FOLLOWING VARIABLES. THE VARIABLES CANNOT BE ACCESSED.

List of variables

Reason

The PL/I compiler has not allocated storage for these variables. This is normally the result of the variables not being referenced or their values never being used.

Action

Informational only. No action is necessary.

SYMP115W

THE FOLLOWING LINE CONTAINS "%NOPRINT" WHICH COULD PREVENT PROPER RESOLUTION OF SOME VARIABLES.

input compiler record

Reason:

Use of the compiler option %NOPRINT may cause the suppression of information needed to resolve variables properly.

Action:

Make sure %NOPRINT does not suppress the printing of:

PROCEDURE or ENTRY statements containing parameter lists.
Declarations of redefined variables using expressions, such as:
```
...BASED( ADDR( variable ) )
...DEFINED base_variable...
```

SYMP116W

THE FOLLOWING "DEFINED" STRUCTURE IS NESTED TOO DEEPLY TO PROPERLY RESOLVE ITS LENGTH: structure

Reason:

This error occurs only with a structure nesting depth that exceeds 16, which is not currently allowed by any version of the PL/I compiler.

Action:

None.

SYMP117W

LENGTH OF DEFINED STRUCTURE "structure" CANNOT BE RESOLVED DUE TO CONTAINED ARRAY "array"

Reason:

When a CORE command displays the specified DEFINED structure containing an array or a substructure that contains an array, the area displayed is correct, but it is limited to the correct length. This error occurs only with a structure nesting depth that exceeds 16, which is not currently allowed by any version of the PL/I compiler.

Action:

None.

SYMP118W

VARIABLE "element name" IS A DUPLICATE NAME WITHIN A STRUCTURE. STRUCTURE, "structure name", IS DECLARED IN STATEMENT statement number DRC = n.

Reason:

A duplicate name was found in a structure. All names must be unique within a major structure. If not, the following problems can occur:

Selection of an incorrect variable
Incorrect attributes for a variable
Incorrect resolution of parameters
System errors not apparently related to these variables

Action:

Assign unique names.

SYMP119W

NO AUTOMATIC VARIABLES FOUND FOR PROCEDURE procname PARAMETER parameter CANNOT BE RESOLVED DRC = n.

Reason:

No AUTOMATIC variables were declared for the specified procedure. Parameters cannot be resolved for any PL/I procedure unless AUTOMATIC variables are declared in it.

Action:

You can circumvent this restriction by declaring an AUTOMATIC variable. This variable does not have to be referenced.

SYMP120W

STRUCTURE INFORMATION FOR: variable-name IS INVALID. SPECIFY CONNECT ATTRIBUTE, OTHERWISE ONLINE STRUCTURE REQUEST WILL SHOW INVALID INFORMATION. STATEMENT #: nnn

Reason:

The CONNECT attribute is missing from the named variable, found in the specified statement number. When the CONNECT attribute is missing, CA InterTest and CA SymDump cannot properly format the variable.

Action:

Redefine the variable with the CONNECT attribute.

SYMP121W

COMPILER EXTERNAL SYMBOL DICTIONARY NOT AVAILABLE. ADDRESSES OF THE FOLLOWING CONTROLLED VARIABLES CANNOT BE DETERMINED.

List of variable names

Reason:

The External Symbol Dictionary is not in the compiler listings. As a result it is not possible to determine the address of controlled variables. Therefore they cannot be displayed.

Action:

Informational only. If you desire to display controlled variables, recompile with the ESD option.

SYMP122W

THE FOLLOWING VARIABLES CAN ONLY BE ACCESSED THROUGH CA INTERTEST BATCH.

List of variables

Reason:

The information required to locate these variables is not available in a CICS environment.

Action:

Informational only. These variables cannot be displayed by CA InterTest.

SYMP123W

THE FOLLOWING EXTERNAL VARIABLES CANNOT BE ACCESSED THROUGH CA INTERTEST BATCH DUE TO THE RENT OPTION.

Reason:

The information necessary to locate external variables for reentrant compiled programs is not available and therefore cannot be displayed.

Action:

Informational only. No action is necessary.

SYMP124W

THE POINTER FOR A BASED ADDR VARIABLE CAN NOT HAVE MORE THAN 3 SUBSCRIPTS

VARIABLE NAME = variable_name

Reason:

CA InterTest for CICS and CA InterTest Batch do not support variables with more than three subscripts.

Action:

Informational only. These variables cannot be displayed.

SYMP125W

CURRENTLY, THE FOLLOWING VARIABLES CAN NOT BE PROPERLY DISPLAYED BY INTERTEST/CICS and INTERTEST BATCH.

List of variables

Reason:

CA InterTest for CICS and CA InterTest Batch cannot support variables with BASED ADDRESS variables with subscripts.

Action:

Informational only. These variables cannot be displayed.

SYMP126W

THE FOLLOWING VARIABLES RESIDE WITHIN AN UNNAMED STRUCTURE AND MAY NOT BE QUALIFIED

List of variables

Reason:

The indicated variables are defined within a structure that was defined with a name of '*'. Since the variable name '*' cannot be referenced, the structure name cannot be used as qualifier.

Action:

Informational only. If the variable names indicated are not unique, the variables may not be displayable by the CA Application Quality and Testing Tools.

SYMP182W

UNABLE TO OBTAIN TIMESTAMP INFORMATION FROM LISTING, CURRENT DATE/TIME WILL BE USED. PARAMETER parameter CANNOT BE RESOLVED DRC = n.

Reason:

The compiler generated timestamp cannot be found in the SYSPRINT listing used as input. The date and time of the postprocessor's execution is used in place of the compiler timestamp.

Action:

Contact Technical Support.

Note: For messages SYMP500 to SYMP599, you are advised to Contact Technical Support. Provide the message number, text, and DRC code (if available). Also provide the IN25SYMP version ID and compile date and time (see message SYMP001I) and the release number of the PL/I compiler you are using.

SYMP500E

ERROR SCANNING SOURCE FOR COMMENTS/LITERALS STATEMENT NUMBER: statement number COMMENT/LITERAL SCAN FLAGS: xxxxxxxx

Reason:

An error occurred while scanning for comments and literals. If comments or literals contain text that resembles a PROCEDURE or ENTRY statement with parameters, some parameter variables may not be properly resolved.

Action:

Make sure comments and literals do not contain text as previously described. Check message SYMP103W. Contact Technical Support if this error occurs.

SYMP501E

UNABLE TO DETERMINE BEGINNING STATEMENT NUMBER FOR BLOCK. ANY VARIABLES DECLARED IN THIS BLOCK PRIOR TO THE INDICATED STATEMENT NUMBER WILL NOT BE RESOLVED. xxxxxxxx AT STATEMENT:statement number

Reason:

An error occurred while identifying the beginning statement number for a block. Variables declared between the beginning of the block and the statement number may not be properly resolved.

Action:

Place an executable statement before the first variable declaration in this block. Contact Technical Support if this error occurs.

SYMP502E

EXPECTED "IN..." NOT FOUND WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LIST VARIABLE variable STATEMENT NO: statement number

Reason:

An error occurred while resolving structure nesting. Structure elements may not be properly resolved.

Action:

Contact Technical Support.

SYMP503E

WARNING - THE FOLLOWING LINE ASSUMED TO BE PART OF COMPILER INFORMATORY MESSAGE AND IGNORED:

input compiler record DRC = n

Reason:

The specified compiler input record was ignored.

Action:

Contact Technical Support.

SYMP503E

WARNING - THE FOLLOWING LINE ASSUMED TO BE A REPETITION OF VARIABLE MAP COLUMN HEADINGS:

input compiler record DRC = n

Reason:

The specified compiler input record was assumed to repeat variable map column headings.

Action:

Contact Technical Support.

SYMP503E

WARNING - THE FOLLOWING LINE ASSUMED TO IDENTIFY COMPILER DIAGNOSTIC MESSAGES SECTION:

input compiler record DRC = n

Reason:

The specified compiler input record was assumed to identify the compiler's diagnostic messages section.

Action:

Contact Technical Support.

SYMP503E

WARNING - THE FOLLOWING LINE CONTAINS TITLE IN UNEXPECTED POSITION - ASSUMED TO LIST STATEMENT OFFSETS:

input compiler record DRC = n

Reason:

The specified compiler input record contains a title in an unexpected position. This line is assumed to list statement offsets.

Action:

Contact Technical Support.

SYMP503E

WARNING - THE FOLLOWING LINE CONTAINS UNEXPECTED DECIMAL OFFSET - HEX VALUE WILL BE USED:

input compiler record DRC = n

Reason:

The specified compiler input record contains a decimal offset. The hexadecimal value will be used instead.

Action:

Contact Technical Support.

SYMP504E

UNEXPECTED STRUCTURE NESTING DEPTH OF n EXCEEDS PREVIOUS COMPILER LIMIT IN STATEMENT statement number

Reason:

The nesting depth exceeds the limit in the specified compiler statement.

Action:

Contact Technical Support.

SYMP505E

BLOCK NOT FOUND FOR VARIABLE variable, DECLARED IN STATEMENT NO. nn

Reason:

The block for the specified variable could not be found.

Action:

Contact Technical Support.

SYMP507E

STATEMENT OUT OF EXPECTED RANGE FOR BLOCK block name

Reason:

The statement was out of the expected range for the specified block.

Action:

Contact Technical Support.

SYMP508E

SEARCH FAILED FOR: variable DRC = n

Reason:

The specified variable could not be found.

Action:

Contact Technical Support.

SYMP509E

INCLUDE OF USER FILES THROUGH INTEGRATED PREPROCESSOR NOT SUPPORTED. USE SEPARATE PREPROCESSOR STEP

Reason:

The integrated INCLUDE and MACRO preprocessors of PL/I for z/OS are not supported. If you are using the integrated SQL preprocessor, programs that contain EXEC SQL INCLUDE statements for user-defined members still require a separate preprocessor step. (EXEC SQL INCLUDE statements for SQLCA and SQLDA are supported when using the integrated SQL preprocessor.)

Action:

Use a separate preprocessor step to incorporate external files into your program.

SYMP599E

UNEXPECTED CHAR IN MARGIN DELIMITER POSITION M, L, MACRO, MRGCHR: aaa, bbb, ccc, ddd DRC = n.

Reason:

An unexpected character was found in the margin delimiter position.

Action:

Contact Technical Support.

SYMP599E

"aaaa" POSITIONED AT BLANK STRING: "portion of listing line" DRC = n.

Reason:

aaaa was positioned at a blank.

Action:

Contact Technical Support.

SYMP599E

"IN" FOUND AT INVALID LOCATION STRING: "portion of listing line" DRC = n.

Reason:

An IN structure was found at an invalid location.

Action:

Contact Technical Support.

SYMP599E

VARIABLE "variable", DECLARED IN STATEMENT statement number, IS ALREADY RESOLVED DRC = n.

Reason:

The specified variable is already resolved.

Action:

Contact Technical Support.

SYMP599E

AGGREGATE NAME NOT MATCHED aggregate name DRC = n.

Reason:

The specified aggregate name was not found.

Action:

Contact Technical Support.

SYMP599E

FORWARD SCAN FAILED TO RESOLVE BLOCK OUTERMOST BLOCK ASSUMED DRC = n.

Reason:

The block could not be resolved. The outermost block is assumed.

Action:

Contact Technical Support.

SYMP599E

STRUCTURE PROCESSING ERROR variable name

Reason:

An error has occurred in recording a variables structure position while processing the aggregate table.

Action:

This can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these conditions and if they occur, correct them and rerun the job. If neither has occurred, Contact Technical Support with the complete job output.

SYMP599E

STORAGE DESCRIPTOR NAME NOT MATCHED variable name

Reason:

A variable name in the storage offset table could not be matched.

Action:

SYMP801E

nn STATEMENTS ENCOUNTERED; PROGRAMS WITH MORE THAN 10,000 STATEMENTS NOT SUPPORTED. RESULTS WILL BE UNPREDICTABLE, WITH SEVERE ERRORS LIKELY.

Reason:

Because of a bug in the PL/I compiler that truncates high order digits from statement numbers in the statement/offset table, programs with over 9,999 statements cannot be supported completely. This message is usually accompanied by other error messages. Online debugging will be affected significantly.

Action:

None.

SYMP901S

THE PL/1 COMPILER OPTIONS LISTED PREVIOUSLY WERE NOT SPECIFIED AND HAVE CAUSED IN25SYMP TO TERMINATE

Reason:

One or more SYMP107W messages were issued.

Action:

Ensure that the following options were specified to the PL/I compiler:

AGGREGATE
ATTRIBUTES(FULL)
MAP
NEST
OFFSET

OPTIONS
SOURCE
STMT or GOSTMT
STORAGE
XREF(FULL)

See the SYMP107W messages for the specific options missing.

If all options were not specified, code the appropriate options and rerun the job.

If all of the previous options have been specified, ensure that the options section is included in the PL/I compiler listing and that the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return code of 8 or less.

SYMP902S

UNEXPECTED TERMINATION OF COMPILER OUTPUT HAS OCCURRED DRC = n.

Reason:

While scanning the PL/I compiler output, an end-of-file condition was raised for the INPUTT DD statement.

Action:

Check that all the PL/I options required by IN25SYMP were set, or that the compiler terminated with a return code of 8 or less. Correct the problem and rerun the compile and IN25SYMP.

SYMP903S

UNEXPECTED ERROR DETECTED. ERROR CORE=nnnn DRC = n.

Reason:

A PL/I error condition occurred that IN25SYMP was not designed to handle.

Action:

Check the PL/I ONCODEs and take the appropriate suggested action. If unsuccessful, contact Technical Support with the dump.

SYMP904S

IN25ASMP FUNCTION FAILED. FUNCTION CODE= n DRC = n.

Reason:

The routine that does I/O to the PROTSYM file returned with a non-zero return code.

Action:

Check the error messages from IN25ASMP and take appropriate action, and then rerun the job. This error usually indicates a problem with the PROTSYM file. If this is the first use of the PROTSYM file, check the job that initialized the file for normal completion. If this is not the first use of the file, check for a physical or logical error on the file. The MESSAGE DD statement contains more information.

Note: Function code 8 usually means the file is full.

SYMP905S

ERROR ENCOUNTERED ON FILE INPUTT, ERROR CODE = nnnn DRC = n.

Reason:

An error has occurred trying to open the INPUTT file.

Action:

Ensure that the ddname DLBL INPUTT points to a file that contains the output listing of the PL/I compiler.

SYMP906S

ERROR ENCOUNTERED ON FILE SYSPRINT, ERROR CODE = nnnn DRC = n.

Reason:

An error has occurred attempting to open the SYSPRINT file.

Action:

Ensure that the ddname DLBL SYSPRINT is coded in your JCL.

SYMP908S

SUBSCRIPT OVERFLOW IN TABLE T4 DRC = n.

Reason:

The internal table used to keep track of variable information has exceeded its limits. This error is usually caused when the Attribute and Cross Reference section of the compile output could not be found by IN25SYMP.

Action:

This can occur if the compiler options ATTRIBUTE(FULL) and XREF(FULL) were not specified, or if the PL/I compile abnormally terminates or terminates with a return code greater than 8. Check for these conditions and if they occur, correct and rerun the job. If neither has occurred, contact Technical Support with the dump.

SYMP909S

SUBSCRIPT OVERFLOW IN TABLE T5 DRC = n.

Reason:

The internal table used to keep track of PROC BLOCKS has exceeded its limits.

This error is usually caused when the Storage Requirements section of the compile output could not be found by IN25SYMP. This can occur if the compiler option STORAGE was not specified, or if the PL/I compile has abnormally terminated or terminated with a return code greater than 8.

Action:

Check for these conditions and if they occur, correct and rerun the job. If neither has occurred, contact Technical Support with the dump.

SYMP910S

SUBSCRIPT OVERFLOW IN TABLE T6 DRC = n.

Reason:

An internal table used to keep track of information about statements has overflowed.

Action:

This occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option.

This can also occur if many source statement lines contain multiple PL/I statements (for example, A=B; C=D; E=F;). In this case, separate the PL/I statements into multiple source lines.

This can also occur if the PL/I preprocessor command %NOPRINT was specified. In this case, remove the %NOPRINT command.

SYMP911S

SUBSCRIPT OVERFLOW IN TABLE T6A DRC = n.

Reason:

An internal table used to keep track of information about statements has overflowed.

Action:

This occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option.

This can also occur if a large number of source statement lines contain multiple PL/I statements (for example, A=B; C=D; E=F;). In this case, separate the PL/I statements into multiple source lines.

This can also occur if the PL/I preprocessor command %NOPRINT was specified. In this case, remove the %NOPRINT command.

SYMP912S

INPUT FROM THE PL/I COMPILER CONTAINS AN INVALID STATEMENT NUMBER IN COLUMNS 1-8 OF THE RECORD.

Reason:

An error was detected while attempting to find the largest PL/I statement number.

Action:

Check compiler output and the line listed. Correct the problem and rerun the job.

SYMP916S

UNEXPECTED ERROR ENCOUNTERED DURING PHASE 1 DRC = n.

Reason:

An error has occurred during phase 1 of IN25SYMP processing.

Action:

Check the job log for operating system or PL/I error indicators. Correct and rerun the job.

SYMP917S

DOS INITIALIZATION FAILED IN "ASMP"; POST-PROCESSOR SYMP WILL BE TERMINATED DRC = n.

Reason:

For VSE only. Usually, a control card is missing or invalid. Or, there may be a problem with the symbolic file or with the JCL for the MESSAGE file.

Action:

Correct the control card, symbolic file, or JCL.

SYMP919S

END OF FILE ENCOUNTERED FOR "INPUTT" DURING PHASE 1 OF PRE-PROCESSOR DRC = n.

Reason:

An end-of-file condition occurred during the phase 1 scan of the PL/I compiler output.

IN25SYMP prints the compiler output and terminates processing. This condition can occur when the PL/I compiler detects program errors that would prohibit successful compilation.

Action:

Refer to the PL/I compiler output for error messages.

SYMP920S

"CDLOAD" FAILED FOR "IN25ASMP". RETURN CODE = nnnn

Reason:

VSE only. The VSAM I/O routine, IN25ASMP, could not be dynamically loaded. Possible causes include incorrect installation or partition JCL that does not allow sufficient storage for loading this phase.

Action:

Check that the specified phase is in the execution phase library and that there is adequate storage.

SYMP921S

POWER SPOOL RETRIEVAL FAILURE: ATTEMPT NUMBER: request

Reason:

For VSE/POWER only. A POWER spool retrieval failed. This message identifies the request. If only one job gets this error, the JCL for the job is probably incorrect. If all jobs get this error, the product may not have been properly installed and customized.

Action:

Check the JCL and, if necessary, the installation and customization.

SYMP922S

INCOMPLETE COMPILER OUTPUT DUE TO ERRORS HAS CAUSED TERMINATION OF IN25SYMP OPTION CAUSING PL/1 COMPILER TERMINATION WAS: option

Reason:

The PL/I compiler options NOSYNTAX and NOCOMPILE can prevent the normal completion of the compilation process, either conditionally, depending on the severity of the errors, or unconditionally. IN25SYMP terminates immediately when it recognizes an aborted compilation.

Action:

Usually, correction of compilation errors resolves this problem.

SYMP923S

TABLE SIZE EXCEEDS HALFWORD LIMIT FOR: name

Reason:

An internal table has exceeded the limit of the halfword index. The postprocessor program terminated to prevent subsequent errors. This situation should not occur for programs with significantly less than 32,767 statements. Because support is limited to programs with less than 10,000 statements, this situation is unlikely to occur.

Action:

Contact Technical Support.

SYMP924S

SUBSCRIPT OVERFLOW IN TABLE T7

Reason:

The internal table used to keep track of variable displacements has exceeded its limits.

Action:

This can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these conditions and if they occur, correct them and rerun the job. If neither has occurred, contact Technical Support with the complete job output.

SYMP925S

SUBSCRIPT OVERFLOW IN TABLE T10

Reason:

The internal table used to keep track of the pseudo register information for controlled variables has exceeded its limits.

Action:

This error is usually caused when the Attribute and Cross Reference section of the compile output could not be found by IN25SYMP.

This can occur if the compiler options ATTRIBUTE(FULL) and XREF(FULL) were not specified, or the if PL/I compile abnormally terminated or terminates with a return code greater than eight. Check these conditions and if they occur, correct and rerun the job. If neither has occurred, contact Technical Support with the complete job output.

SYMP926S

SUBSCRIPT OVERFLOW IN TABLE T11

Reason:

The internal table used to keep track of external symbol dictionary entries has exceeded its limits.

Action:

This can occur if the compiler option ESD was not specified, or the PL/I compiler abnormally terminated or terminates with a return code greater than eight. Check these conditions and if they occur, correct and rerun. If neither has occurred, contact Technical Support with the complete job output.

SYMP999S

UNEXPECTED ERROR CODE. nnn PROCESSING TERMINATED

Reason:

An undocumented error code has forced termination of IN25SYMP.

Action:

Contact Technical Support.

CAIN5990I

ALLOCATION OF LOG FILE FAILED. LOGGING DISABLED.

Reason:

Action:

Determine and correct the cause for failure then retry the action.

CAIN5991W

HHMM DOES NOT MATCH.

Reason:

Action:

Provide the correct timestamp value and try the action again.

CAIN5995E

NO PROTSYM SEARCH LIST PROVIDED.

Reason:

This message is issued by IN25FSYM. User did not provide one or more PROTSYM data set names to perform symbolic search. Requested action is not performed.

Action:

Provide at least one or up to a maximum of eight PROTSYM fully qualified data set names to be used for symbolic search.

CAIN6000E

DYNAMIC UNALLOCATION FAILED FOR nnnnnnnn. RC= rr. RSN= ssssssss.

Reason:

This message is issued by IN25FSYM. Dynamic allocation of data set with nnnnnnnn DD name has failed. Return code from Dynamic Allocation is rr and the reason code is ssssssss.

Action:

Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action.

CAIN6000W

DYNAMIC UNALLOCATION FAILED FOR dddddddd RC=rr. RSN=ssssssss.

Reason:

This message is issued by IN25FSYM. Dynamic unallocation of dddddddd DD name has failed. The Dynamic Unallocation return code is rr and reason code is ssssssss.

Action:

Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action. If the error persists call CA Technical Support.

CAIN6010W

LOAD OF pppppppp FAILED. RC= rr.

Reason:

This message is issued by IN25FSYM. Loading of program named pppppppp has failed. The return code is rr.

Action:

Make sure that the data set containing the pppppppp program is in the LINKLIST or defined in the STEPLIB DD.

CAIN6020W

FAILED IN ROUTINE: rrrrrrrrrr RC= rr.

Reason:

This message is issued by IN25FSYM. Routine named rrrrrrrr has failed with a return code of rr. This message is usually associated with IN25SAPI and rrrrrrrr is the failed SAPI function.

Action:

Determine the error and retry the request.

CAIN6070E

CRITICAL ERROR LD@DSSDSN INVALID VALUE.

Reason:

This message is issued by IN25FSYM. The data set name provided in LD@DSSDSN is invalid.

Action:

LD@DSSDSN should contain a valid DD name to be used for DSS logging. It is usually specified as DSSLOG. Correct the DD name and retry the action.

CAIN5990I

LINK TO IN25SPOL FAILED.

Reason:

This message is issued by IN25NSRV. LINK SVC for IN25SPOL has failed. Message extraction will not be performed.

Action:

Make sure that the data set containing IN25SPOL is either defined in the LINKLIST or properly defined in the STEPLIB DD.

CAIN5980E

CA SCM CRITICAL ERROR. ERROR CODE: rrrr. REQUEST FOR mmmmmmmm NOT SERVICED.

Reason:

This message is issued by IN25NSRV. This indicated that CA SCM Endevor for mainframe encountered a critical error. The error code is rrrr. Symbolic request for element named mmmmmmmm is not serviced.

Action:

Use the rrrr error code in conjunction with the SRVPRINT log and DSSLOG to determine the cause, correct the error and redo the request.

CAIN5900I

mm/dd/yyyy hh:mm:ss IN25NDVR STARTED FOR PRGNNAME – pppppppp.

Reason:

Action:

None.

CAIN5903E

mm/dd/yyyy hh:mm:ss IN25NSRV CCI SPNPARM FAILED.

Reason:

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5903E

mm/dd/yyyy hh:mm:ss IN25NSRV CCI INIT FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. CCI INIT action has failed. This error occurred when IN25NSRV issued a CCI INIT request. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5904I

mm/dd/yyyy hh:mm:ss IN25NSRV WAITING FOR WORK.

Reason:

Action:

None.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED.

Reason:

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, INVALID DATA.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received are invalid. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the request again.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, RECEIVED NULLS.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and data received contained all null values. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to inspect the block received. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5905E

mm/dd/yyyy hh:mm:ss IN25NSRV RECVANY FAILED, INVALID LENGTH.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and length of the data block received was incorrect. Message CAIN5930 is usually issued in conjunction with this message.

Action:

Examine feedback area provided in message CAIN5930 to inspect the length of data block received. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5907E

mm/dd/yyyy hh:mm:ss IN25NSRV SENDSPEC FAILED.

Reason:

Action:

Examine feedback area provided in message CAIN5930 to determine the reasons for the failure. This could be the result of transmission error. If the problem persists call CA Technical Support.

CAIN5908W

mm/dd/yyyy hh:mm:ss IN25NSRV GETMAIN FAILED.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. The message indicated that GETMAIN for 32K of main storage has failed.

Action:

Make sure that you have specified a sufficiently large region size to meet the many main storage requirements of the Listing service.

CAIN5909I

mm/dd/yyyy hh:mm:ss IN25NSRV REQUEST RECEIVED FOR eeeeeeee.

Reason:

Action:

None.

CAIN5913I

mm/dd/yyyy hh:mm:ss IN25NSRV SENDING RESPONSE

Reason:

Action:

None.

CAIN5930I

mm/dd/yyyy hh:mm:ss IN25NSRV CCI FEEDBACK: feedback info.

Reason:

This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was issued. This is the message that is usually issued in conjunction with CCI related error conditions. Feedback is a 256 bytes area containing CCI return codes, reason codes, and brief description associated with the error encountered.

Action:

Use the information provided in this message in conjunction with the failure message to diagnose the error.

CAIN5950I

mm/dd/yyyy hh:mm:ss IN25NSRV SHUTDOWN.

Reason:

Action:

None.

CAIN5970W

LINK TO IN25SPOL FAILED.

Reason:

This message is issued by IN25NSRV indicating that LINK to IN25SPOL has failed. Message extraction will not be performed.

Action:

Determine that the data set containing IN25SPOL is either defined in the LINKLIST or is properly defined in the STEPLIB concatenations.

CAIN5980E

==>CA SCM CRITICAL ERROR. ERROR CODE: eeee. REQUEST FOR pppppppp NOT SERVICED.

Reason:

This message is issued by IN25NSRV and is used as an end bookmark for message extraction. All messages issued before this message are extracted by the message extraction service.

Action:

None.

CAIN8000W

JESMSGLG JCT MTTR FOUND.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicates that MTTR of JESMSGLG JCT was found.

Action:

None.

CAIN8010I

JESYSMSG JCT MTTR FOUND.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicates that MTTR of JESMSGLG JCT was found.

Action:

None.

CAIN8020I

ACQUIRED MSGLOG AND SYSMSG JCT

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This message indicates that the JCT for JESMSGLG and JESYSMSG have been acquired.

Action:

None.

CAIN8030W

UNABLE TO ACQUIRE JCT OF EITHER JESMSGLG OR JESYSMSG.

Reason:

Action:

Call CA Technical Support with the information.

CAIN8040I

STIMER WAIT FOR JQE UPDATE.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. The message indicated that IN25SPOL has issued a STIMER SVC to wait for JQE update to complete.

Action:

None.

CAIN8091I

jjjj IS THE PRIMARY JOB ENTRY SUBSYSTEM. SYSTEM ID FROM JQRYSSID ===> iiii.

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating that jjjj is the primary job entry subsystem whose id is iiii.

Action:

None.

CAIN8092I

dddddddd IS THE DDN OF jjjjjjjj RETURNED.

Reason:

Action:

None.

CAIN8093I

ASSOCIATED DSN: datasetname.

Reason:

Action:

None.

CAIN8094I

JOBNAME: jobname JOBID: iiiiiiii

Reason:

This message is issued by IN25SPOL when CA Technical Support requested diagnostic messages. This is an informational message indicating that the active job name is jobname whose jobid is iiiiiiii.

Action:

None.

CAIN8098W

POSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.

Reason:

Action:

Call CA Technical Support.

CAIN8050I

THERE ARE NO SJQES RETURNED.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ did not return SJQES information. Message extraction will not be performed.

Action:

None.

CAIN8060I

THERE ARE NO SOUTS RETURNED.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ did not return SOUTS information. Message extraction will not be performed.

Action:

None.

CAIN8070I

UNABLE TO ACCESS JOB QUEUE.

Reason:

This message is issued by IN25SPOL indicating that IEFSSREQ was unable to access JES job queue.

Action:

None.

CAIN8080I

IN25SS71 LOAD FAILED.

Reason:

This message is issued by IN25SPOL indicating that loading of IN25SS71 has failed.

Action:

Make sure that the data set containing IN25SS71 is either in the LINKLIST or the STEPLIB concatenation is properly defined.

CAIN8090I

IN25SDSB LOAD FAILED.

Reason:

This message is issued by IN25SPOL indicating that loading of IN25SDSB has failed.

Action:

Make sure that the data set containing IN25SDSB is either in the LINKLIST or the STEPLIB concatenation is properly defined.

CAIN8095I

IEFSSREQ TYPE=QUERY FAILED. RETURN CODE= cccc REASON CODE= ssss

Reason:

This message is issued by IN25SPOL indicating that IEFSSRQ type of query has failed with a return code of cccc and reason code of ssss.

Action:

Determine the cause of failure based on the return code and reason code.

CAIN8096I

IEFSSI SUBFUNCTION 80 FAILED. SSOBRETN= rrrr STATREAS= ssss.

Reason:

This message is issued by IN25SPOL indicating that IEFSSI subfunction 80 has failed. The subsystem return code is rrrr and reason code is ssss. Message extraction will not be performed.

Action:

Call CA Technical Support.

CAIN8097I

JESMSGLG dddddddd NOT FOUND.

Reason:

This message is issued by IN25SPOL indicating that dddddddd token for JESMSGLG.

Action:

None.

CAIN8100I

SPOOL READ FUNCTION CURRENTLY DOES NOT SUPPORT JES3 AT BELOW ZOS 01.11.01 LEVEL.

Reason:

This message is issued by IN25SPOL indicating that spool read function does not support JES3 at a level below ZOS 01.11.01 level. Message extraction will not be performed.

Action:

None.

CAIN8100I

STARTING MSGLOG00 PROCESS.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that message extraction of JESMSGLG is being started.

Action:

None.

CAIN8110I

STARTING SYSMSG00 PROCESS.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating that message extraction of JESYSMSG is being started.

Action:

None.

CAIN8120I

OBTAINED JCT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71. It is an informational message indicating that JCT information was obtained from in-storage buffer.

Action:

None.

CAIN8120I

OBTAINED IOT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71. This is an informational message indicating that IOT information was obtained from in-storage buffer.

Action:

None.

CAIN8160I

MSGLOG OBTAINED FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESMSGLG messages were extracted from in-storage buffer.

Action:

None.

CAIN8170I

MSGLOG READ FROM LAST TRACK.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESMSGLG messages were extracted from the last track specified in MTTR.

Action:

None.

CAIN8180I

MSGLOG RECORD COUNT EXHAUSTED.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESMSGLG messages extraction has exhausted its record count.

Action:

None.

CAIN8190I

SYSMSG RECORD COUNT IS ZERO.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESYSMSG record count is zero.

Action:

None.

CAIN8200I

SYSMSG OBTAINED FROM INSTOR BUFFER

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESYSMSG information was extracted from in-storage buffer.

Action:

None.

CAIN8210I

SYSMSG RECORD COUNT EXHAUSTED.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESYSMSG messages extraction has exhausted its record count.

Action:

None.

CAIN8230I

SYSMSG READ FROM LAST TRACK.

Reason:

This message is issued by IN25SS71 when CA Technical Support requests diagnostic messages. This is an informational message indicating the JESYSMSG messages were extracted from the last track specified in MTTR.

Action:

None.

CAIN8130E

INVALID REQUEST.

Reason:

This message is issued by IN25SS71. This is a should not occur error.

Action:

Call CA Technical Support.

CAIN8140W

FAILED TO LOCATE PDDBS FOR BOTH JESMSLG AND JESYSMSG.

Reason:

This message is issued by IN25SS71 indicating that it cannot locate the PDDBs for JESMSGLG and JESYSMSG.

Action:

Call CA Technical Support.

CAIN8150I

JESMSGLG BUFR IS EMPTY

Reason:

This message is issued by IN25SS71 indicating that the JESMSGLG buffer is empty. Message extraction cannot be performed.

Action:

None.

CAIN8240E

SUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= cccc SSJIRETN= ssss.

Reason:

Action:

Call CA Technical Support with the error message.

CAIN8260W

OUTPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SS71 indicating that open attempt of output dcb for JOBLOG DD statement has failed. Message extraction will not be performed.

Action:

Determine the reason for open failure. DD statement: //JOBLOG DD SYSOUT=*

CAIN8270I

NO MORE SYSOUT FROM JES.

Reason:

This message is issued by IN25SS71 indicating end of file condition has reached.

Action:

None.

CAIN8320I

OBTAINED IOT FROM INSTOR BUFFER

Reason:

This message is issued by IN25SDSB when CA Technical Support requests for diagnostic messages. The message indicated that job’s IOT information was obtained from in-storage buffer.

Action:

None.

CAIN8380I

JESMSGLG ALLOCATED. DDNAME: dddddddd

Reason:

This message is issued by IN25SDSB when CA Technical Support requests for diagnostic messages. The message provides the dynamic allocation returned DDNAME as dddddddd.

Action:

None.

CAIN8300I

JCT RETREIVAL ERROR.

Reason:

This message is issued by IN25SDSB indicating there was an error retrieving job’s JCT. Message extraction will not be performed.

Action:

None.

CAIN8310I

IOT RETRIEVAL ERROR.

Reason:

This message is issued by IN25SDSB indicating there was an error retrieving job’s IOT. Message extraction will not be performed.

Action:

None.

CAIN8330E

JESMSGLG ALLOCATION FAILED. MSGLOG NOT COLLECTED.

Reason:

This message is issued by IN25SDSB indicating that dynamic allocation of JESMSGLG data set name has failed. Message extraction will not be performed.

Action:

None.

CAIN8340E

JESYSMSG ALLOCATION FAILED. SYSMSG NOT COLLECTED.

Reason:

This message is issued by IN25SDSB indicating dynamic allocation of JESYSMSG data set name has failed. Message extraction will not be performed.

Action:

None.

CAIN8350W

FAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.

Reason:

This message is issued by IN25SDSB indicating that attempts to locate the PDDBs for JESMSGLG and JESYSMSG has failed. Message extraction will not be performed.

Action:

None.

CAIN8360I

SUBSYSTEM FUNCTION 71 SPOOL READ FOR jct FAILED. RC= rrrr SSOBRETN= ssss SSJIRETN=nnnn

Reason:

This message is issued by IN25SDSB indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return code is rrrr, subsystem reason code is cccc, subsystem return code is ssss. Message extraction is not performed.

Action:

Call CA Technical Support with this message.

CAIN8390I

JESMSGLG DYNAMIC ALLOCATION FAILED. RC/RSN: rrrr/ssss

Reason:

Action:

Determine and correct the cause for the failure, than retry the request.

CAIN8400W

INPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SDSB indicating that open of input dcb has failed. The two input data sets involved are JESMSGLG and JESYSMSG. When these data sets were allocated successfully, open should not fail. Message extraction will not be performed.

Action:

Determine and correct the cause of the failure, and retry the request.

CAIN8410W

OUTPUT DCB OPEN FAILED.

Reason:

This message is issued by IN25SDSB indicating that open of JOBLOG SYSOUT has failed.

Action:

Verify that //JOBLOG DD SYSOUT=* is defined in the job’s JCL.

CAIN8410I

INPUT DDNAME: sys E N D O F F I L E

Reason:

This message is issued by IN25SDSB indicating the end of file condition for DD named sys has reached.

Action:

None.

CAIN7000W

IN25NDVR MAJOR ERROR, LOG FILE NOT OPENED

Reason:

SRVPRINT log file not opened. Endevor activity log disabled.

Action:

We recommend that //SRVPRINT DD SYSOUT=* be defined in the job’s JCL so that relevant error can be captured to assist in problem analysis. This would avoid the need to recreate the error.

CAIN7010I

IN25NDVR ALLOCATION OF LOG FILE FAILED.

Reason:

Dynamic allocation of activity log has failed. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed.

Action:

Determine and correct the cause of the error and retry the request.

CAIN7020W

LOAD OF IN25DALC FAILED.

Reason:

IN25NDVR encountered an error trying to LOAD IN25DALC. Endevor List request will not be performed.

Action:

Make sure that the data set containing IN25DALC load module is either defined in the LINKLIST or is defined in the STEPLIB concatenation.

CAIN7030W

LOAD OF ENA$NDVR FAILED.

Reason:

IN25NDVR cannot LOAD the Endevor API. Endevor List request will not be performed.

Action:

Make sure that Endevor AUTHLIB and CONLIB data sets are either defined in the LINKLIST or defined in the job’s JCL.

Tell Technical Publications how we can improve this information