CKPT scheduling failed
Reason:
Checkpoint processing was unable to schedule the next checkpoint.
Action:
Check your CICS console for temporary storage errors. Correct any errors or if there are none, contact CA technical support.
CKPT function abnormally terminated
Reason:
An abend occurred during checkpoint processing.
Action:
Collect the transaction dump and contact CA technical support.
(*) not in FCT
Reason:
The file is not defined to CICS or has not been installed.
Action:
Define and install the file.
invalid processing options in FCT for (*)
Reason:
The file (*) has the wrong service options specified for the file.
Action:
Correct the file's options, and resubmit the request.
VSAM err code=(*) return code=(*) file=(*)
Reason:
An error occurred while accessing the checkpoint file.
Action:
Ensure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's Guide.
dynamic open failure code = (*) file = (*)
Reason:
CA InterTest for CICS was unable to open the file.
Action:
Ensure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's Guide.
CICS error = (*) detected in file (*)
Reason:
An error occurred while accessing the checkpoint file.
Action:
Ensure that the file is accessible. For more information on the error and return codes, see the VSAM Programmer's Guide.
CKPT function abnormally terminated
Reason:
An abend occurred during checkpoint processing.
Action:
Collect the transaction dump and contact CA technical support.
(*) file space exhausted
Reason:
The checkpoint file has insufficient space to hold all the requests.
Action:
Increase the size of the checkpoint file.
scheduling for CA InterTest CKPT has failed
Reason:
Checkpoint processing was unable to schedule the next checkpoint.
Action:
Check your CICS console for temporary storage errors. Correct any errors or, if there are none, contact CA technical support.
CKPT function completed at (*)
Reason:
Checkpoint completed successfully.
Action:
None.
RECEIVING FIELD HAS BEEN CHANGED AS SHOWN
Reason:
The MOVE= command was performed and the result is displayed on the screen.
Action:
None.
PROGRAM IS ASSEMBLER - REQUESTS DISREGARDED
Reason:
The MOVE= command was entered for an Assembler program that is supported for COBOL and PL/I only.
Action:
None.
XXXXXXXX USAGE-TYPE NOT SUPPORTED
Reason:
The USAGE-TYPE, for the data-item xxxxxxxx, was not valid. The MOVE= command can only handle data-items that are defined as COMP, COMP-3, GROUP, DISPAY-NUMERIC, or DISPLAY.
Action:
None.
FIGURATIVE CONSTANT ALL FORMAT ERROR
Reason:
A MOVE ALL xx...' command was found to be in error. The 'ALL' option may only be a FIGURATIVE CONSTANT, like ZERO or SPACES, or a non-numeric literal.
The format is the same as is described in your COBOL APPLICATION PROGRAMMING LANGUAGE REFERENCE manual.
Action:
Correct command and resubmit.
LITERAL FOR ALL KEYWORD IS MISSING FROM COMMAND
Reason:
A MOVE ALL xx...' command was found to be in error. The 'ALL' option may only be a FIGURATIVE CONSTANT, like ZERO or SPACES, or a non-numeric literal.
The format is the same as is described in your COBOL APPLICATION PROGRAMMING LANGUAGE REFERENCE manual.
Action:
Correct command and resubmit.
SENDING FIELD DOES NOT CONTAIN A VALID NUMERIC VALUE
Reason:
When using a 'MOVE data1 TO data2' command format, the 'data2' field was defined as numeric but the'data1' was not.
Action:
Correct command and resubmit.
NUMERIC LITERAL IS NON-NUMERIC
Reason:
A numeric literal was found to contain non-numeric characters.
Action:
Correct command and resubmit.
SENDING FIELD CONTAINS MORE THAN 18 DIGITS
Reason:
The sending field, a data item or numeric literal, was found to be longer than 18 numeric characters. This is a COBOL restriction.
Action:
Correct command and resubmit.
UNPAIRED QUOTES AROUND LITERAL
Reason:
A literal was entered that did not contain an even number of quotation marks.
Action:
Correct command and resubmit.
LITERAL IS GREATER THAN 120 CHARACTERS
Reason:
A literal was entered that contains more than 120 characters. This is a COBOL restriction.
Action:
Correct command and resubmit.
A NULL LITERAL HAS BEEN ENTERED
Reason:
A literal was entered that contains only two (2) quotation marks.
Action:
Correct command and resubmit.
INDEXING FORMAT IS INCORRECT
Reason:
The SUBSCRIPT or INDEX format that was entered for a data item was found to be invalid.
Action:
Correct command and resubmit.
KEYWORD TO IS MISSING FROM COMMAND
Reason:
The MOVE= command requires the keyword TO. The format of the MOVE= command is the same as described in your COBOL APPLICATION PROGRAMMING LANGUAGE MANUAL.
Action:
Correct command and resubmit.
COMMAND IS INCOMPLETE
Reason:
The MOVE= command was found to be incomplete. This may occur if the following command was entered: MOVE SPACES TO
Action:
Correct command and resubmit.
RECEIVING FIELD NOT CONTAINED WITHIN YOUR STORAGE
Reason:
The receiving data item did not reside in an area of storage that was owned by the task.
Action:
None.
xxxxxx CANNOT BE MOVED TO A FIELD DEFINED AS NUMERIC
Reason:
The figurative literal, xxxxxx, cannot be moved to a data item that is described as numeric.
Action:
Correct command and resubmit.
HIGH-ORDER TRUNCATION MIGHT HAVE OCCURRED
Reason:
A numeric receiving data item was smaller than the sending data item. This condition may cause a loss of high-order data.
Action:
None.
LOW-ORDER TRUNCATION MIGHT HAVE OCCURRED
Reason:
A non-numeric receiving data item was smaller than the sending data item. This condition may cause a loss of low-order data.
Action:
None.
MOVE PERFORMED WITHOUT DATA CONVERSION
Reason:
One of the data items was found to be a GROUP item. When a GROUP item is found, the data is moved without any conversion.
Action:
None.
SYMBOLIC RETRIEVAL PROGRAM ACCESS FAILURE
Reason:
The CA InterTest for CICS program, IN25SGET, was either not found in the PPT or was diagnosed disabled.
Action:
Correct condition.
NOTAUTH CONDITION - RESOURCE LEVEL SECURITY FAILED FOR "(*)"_
Reason:
This transaction is not authorized to use the resource specified.
Action:
Adjust your security definitions, and resubmit the request.
COMMAND TEXT EXCEEDS MAXIMUM LENGTH
Reason:
The input command exceeded a maximum of 72 characters. This normally occurs when a CORE command is entered by overtyping an existing display.
Action:
If the error is caused by overtyping an existing display then simply place the cursor at the first character that follows the CORE command, then use the ERASE EOF key and resubmit the command.
AN AICA HAS OCCURRED
Reason:
While processing the CORE request an AICA occurred and was recovered.
Action:
None.
AREA TO BE CHANGED RESIDES OUTSIDE OF CICS
Reason:
The area that is being changed does not reside within the CICS address space.
Action:
Check your previous CORE commands to see how this address was generated and, if possible, correct and retry the change operation.
INVALID ADDRESS/OFFSET
Reason:
An ADDRESS or OFFSET was requested that was greater than 8 characters long, or the Address Offset contained a non-hexadecimal character.
Action:
Correct and resubmit command.
INVALID KEYWORD
Reason:
The argument that followed an '=' sign was not found in the list of allowable keywords.
Action:
Correct and resubmit command.
REQUESTED IDENTIFICATION NOT FOUND
Reason:
The item requested could not be found in the area specified.
Action:
Correct and resubmit command.
LOAD MACRO FAILED, PPT ENTRY IS DISPLAYED
Reason:
A =LOAD=program request, in an XA environment, resulted in a failure. The CORE program displays the program's PPT entry.
Action:
None.
SYNTAX ERROR
Reason:
While editing a CORE request, an error in the syntax was found.
Action:
Correct and resubmit request.
INVALID OPERATION
Reason:
The request could not be performed.
Action:
Correct and resubmit request.
SPECIFIED DATA AREA IS EITHER STORE OR FETCH PROTECTED
Reason:
While trying to display or change a data area, a PROTECTION EXCEPTION occurred.
Action:
Correct and resubmit request.
CURRENT USE COUNT IS 0 FOR PROGRAM
Reason:
When trying to do a =DLTE=program request, the program's use count was found to be 0.
Action:
None.
PROGRAM NOT IN MAIN STORAGE
Reason:
The program that was specified in an =PGM=program request was not loaded into CICS.
Action:
Change the request to =LOAD=program and resubmit.
REQUESTED AREA WAS NOT FOUND
Reason:
The area, that was requested, was not found.
Action:
None.
INIT= IS INVALID
Reason:
The INIT= field, for a =GETM request, was not within the range of X'00' through X'FF'.
Action:
Correct and resubmit.
INVALID COMPARATOR CODE
Reason:
The comparator code, found in a =IF request, was not valid.
Action:
Correct and resubmit.
INVALID IF STATEMENT
Reason:
The =IF request was found to be invalid.
Action:
Correct and resubmit.
TASK NOT AT BREAKPOINT
Reason:
A CORE request was made that requires a task at a breakpoint and one was not found.
Action:
None.
STORAGE NOT AVAILABLE, DL1=NO SPECIFIED IN SIT
Reason:
No DL/1 is available in the CICS region and an attempt was made to display a DL/1 storage area.
Action:
None.
TASK NUMBER UNKNOWN
Reason:
The task number, which is being used, was not found in CICS.
Action:
Verify task number using a CSMT TAS or CEMT I TAS command.
HEX=xxxxxxxx DEC=yyyyyyyyyy
Reason:
As a result of a CALC command, both the HEXadecimal value (xxxxxxxx) and a DECimal value (yyyyyyyyyy) are displayed for the function.
Action:
None.
STORAGE NOT AVAILABLE
Reason:
The storage, requested by a =GETM request, could not be obtained.
Action:
None.
PASSWORD REJECTED
Reason:
The password entered, in response to the CORE000 message' was incorrect.
Action:
Enter the correct password.
xxxxx BYTES CHANGED AS SHOWN AT yyyyyyy
Reason:
After a =CHG request has been processed, the number of bytes changed (xxxxx) and the address of the first byte changed (yyyyyyy) is shown.
Action:
None.
ILLEGAL USAGE OF SYMBOLIC NAME
Reason:
A symbolic name has been used in a CORE request that cannot support a symbolic name.
Action:
Correct and resubmit.
NOT VERIFIED
Reason:
A verification request, =VER, has resulted in a non-match condition.
Action:
Correct and resubmit.
DATA VERIFIED
Reason:
A verification request, =VER, has resulted in a match condition.
Action:
None.
DUMP WRITTEN TO CICS DUMP DATA SET
Reason:
A =DUMP request has been completed with the dump being written to the CICS dump data set.
Action:
None.
PGM RELOAD=YES, NOT LOADED WHEN MONITORED
Reason:
The program to be loaded, by a LOAD=program request, was found to be at a breakpoint and the program was defined with a RELOAD=YES option.
Action:
None.
A COPY OF PGM, RELOAD=YES, USED IN ADDRESSING
Reason:
A =DUMP request has been completed with the dump being written to the CICS dump data set.
Action:
None.
RESULT IS TRUE
Reason:
A true condition was found in response to an =IF request.
Action:
None.
RESULT IS NOT TRUE
Reason:
A false condition was found in response to an =IF request.
Action:
None.
PROGRAM IS DISABLED
Reason:
The program, specified in a =LOAD=program request was found to be disabled.
Action:
Use CSMT or CEMT to enable the program and then resubmit the request.
INCOMPATIBLE SCREEN SIZE
Reason:
During the processing of a =SSCR request, the terminal being used for the CORE transaction is not in the same mode as the terminal used for the breakpoint. For example - the user's program displayed a screen on a MODEL 5 terminal and is now trying to display it on a MODEL 2 terminal.
Action:
None.
TASK POSTED FOR ASRA
Reason:
In response to a =PURGE request, the task has been terminated with an ASRA condition.
Action:
None.
COMPARISON LENGTHs MISSING
Reason:
During the processing of a =IF request, it was found that either one or both length fields were missing.
Action:
Correct request and resubmit.
COMPARISON LENGTHS NOT EQUAL
Reason:
During the processing of a =IF request, it was found that the length fields were not the same length.
Action:
Correct request and resubmit.
MON/NOM OPTIONS ARE SET FOR PROG - DELETE DENIED.
Reason:
The program to be deleted contains MON or NOM monitoring options.
Action:
Remove the MON and/or NOM options and retry the request.
COMPARE LENGTHs ARE GREATER THAN MAX FOR DATA TYPE
Reason:
During the processing of a =IF request, it was found that either one or both length fields were greater than the maximum for the data type. For example - a maximum of 16 bytes is permitted for packed (comp-3) data.
Action:
Correct request and resubmit.
INVALID KEYWORD FOUND IN "KEEP" REQUEST
Reason:
The keyword specified is not valid for a KEEP request.
Action:
The keyword cannot be used.
LITERAL IS TOO LONG
Reason:
A literal was entered that was greater than 50 characters long, which is the maximum for one request.
Action:
Correct request and resubmit.
PL/I PROCEDURE NAME NOT FOUND.
Reason:
The PL/I procedure name could not be found.
Action:
Correct the procedure name and retry the request.
OFFSET IN PL/I MAIN CSECT IS (*)
Reason:
Informational.
Action:
None.
INVALID HEXADECIMAL LITERAL
Reason:
A literal, specified in an X'....' format, was found to contain non-hexadecimal characters or there were an odd number of characters specified.
Action:
Correct request and resubmit.
INVALID CHARACTER LITERAL
Reason:
A literal, specified in a C'....' format, was found to contain characters that were less than a blank, X'40'.
Action:
Correct request and resubmit.
INVALID PACKED DECIMAL LITERAL
Reason:
A literal, specified in a P'....' format, was found to contain non-numeric characters and/or the first character was no a '+' or '-'.
Action:
Correct request and resubmit.
INVALID HALFWORD LITERAL
Reason:
A literal, specified in a H'....' format, was found to contain non-numeric characters and/or the first character was not a '+' or '-'.
Action:
Correct request and resubmit.
INVALID FULLWORD LITERAL
Reason:
A literal, specified in a F'....' format, was found to contain non-numeric characters and/or the first character was not a '+' or '-'.
Action:
Correct request and resubmit.
Command invalid when viewing past data values.
Reason:
The specified command is not valid while navigating the statement trace table with the DATAMON option in effect.
Action:
Specify a valid command.
INDIRECT ADDRESSING IS INVALID FOR THIS KEYWORD
Reason:
The keyword, specified by a keyword or %keyword request, may not be used for indirect addressing.
Action:
Correct request and resubmit.
MODEL TCT ENTRY FOUND FOR REMOTE TERMINAL ID
Reason:
The terminal specified by a TERM=termid request was found to a model TCT entry.
Action:
None.
FIELD DOES NOT CONTAIN A VALID PACKED DECIMAL (COMP-3) VALUE
Reason:
The displayed COBOL data item, which was defined as a COMP-3 field, was found to contain an invalid value.
Action:
None.
ttttttttt - VALUE OF FIELD = xxxxxxxxx
Reason:
The decimal value, xxxxxxxxx, is displayed for a PL1 data item which was defined as ttttttttt.
Action:
None.
=MOVEIN COMMAND MISSING LENGTH (L=) PARAMETER
Reason:
The length parameter, L=, was not found while processing a =MOVEIN request.
Action:
Correct request and resubmit.
=MOVEIN COMMAND MISSING FROM= PARAMETER
Reason:
The from parameter, FROM=, was not found while processing a =MOVEIN request.
Action:
Correct request and resubmit.
LENGTH FIELD (L=) IS ZERO
Reason:
The length parameter, L=, was found to contain a zero value.
Action:
Correct request and resubmit.
LENGTH FIELD (L=) IS GREATER THAN MAXIMUM ALLOWED
Reason:
The length parameter, L=, was found to contain a value, which was greater than the maximum permitted.
Action:
Correct request and resubmit.
xxxxxxxx NOT FOUND IN PPT OR IS DISABLED
Reason:
The program, xxxxxxxx, specified in the CORE request was either not found in the PPT or diagnosed disabled.
Action:
Use CSMT or CEMT to locate the program, if found, enable the program and resubmit request.
UNABLE TO START ISER TASK - TRANSACTION NOT DEFINED
Reason:
No CORE commands can be processed.
Action:
Ensure that the ISER transaction is properly installed.
UNABLE TO START ISER TASK - TRANSACTION IS NOT ENABLED_
Reason:
No CORE commands can be entered.
Action:
Enable the ISER transaction.
TO MANY INDEX NAMES (MAX = 3)
Reason:
Too many subscripts or indexes were found when processing a ='data-name(x1,..,xn)' request. A maximum of 3 levels may be specified. This is a COBOL restriction.
Action:
Correct request and resubmit.
FIRST SYMBOLIC REFERENCE IS NOT A EQUATED TO A REGISTER
Reason:
The first symbolic reference, in a symbolic request for an assembled data item, was not a register.
Action:
Correct request and resubmit.
INVALID NUMERIC VALUE FOR DATA TYPE
Reason:
When changing data, by over-typing, in the Structure Display Format area, an invalid numeric value was entered for the data type. This can occur by entering a numeric value that is too large for the data type. For example, the maximum value an S9(4) COMP field can hold is +32767. The screen is restored to its original condition.
Action:
Retype your change.
INVALID USE= SYNTAX - FORMAT NOT = MODULE.NAME OR *.NAME
Reason:
A =USE request was not specified correctly.
Action:
Correct and resubmit.
INVALID CHARACTER ENTERED OR A FIELD WAS ERASED
Reason:
When changing data, by over-typing, in the hexadecimal area, a non-hexadecimal character was entered or an ERASE EOF key was hit. The screen is restored to its original condition.
Action:
Retype your change.
AT FIRST ENTRY IN STRUCTURE
Reason:
The first data item, displayed for a structure request, is the first item in that structure.
Action:
None
AT LAST ENTRY IN STRUCTURE
Reason:
The last data item displayed, for a structure request, is the last item in that structure.
Action:
None
STRUCTURE DISPLAY FORMAT (SDF) UNAVAILABLE
Reason:
Prior to InterTest 6.2, Assembler modules did not carry the data type on the symbolic file. Because of this, the format of the data cannot be determined. The data displays in the hexadecimal / character format.
Action:
Reassemble the program using the InterTest 6.2 version of IN25SYMA.
PROGRAM CANNOT BE DELETED
Reason:
The program is being used by some task.
Action:
Terminate the task holding the resource and retry this request.
CANNOT DIVIDE BY 0
Reason:
A division by zero request was made in a CALC function.
Action:
Correct request and resubmit.
PRESS CLEAR TO SEE NEXT ITEM OR PF3 TO CANCEL DISPLAYS
Reason:
This message appears only when multiple display requests are made from the source code viewing screen.
Action:
If you wish to see the data item requested, then press the Clear key. If you wish to cancel the remaining display requests, press PF3.
INVALID DFHAID ENTERED
Reason:
The AID byte entered is unrecognizable. This is a logic error in program IN25CORE.
Action:
Collect the dump and contact CA technical support.
GETM, CLASS=TERM, IS INVALID FOR THIS TASK
Reason:
The task does not have an associated terminal.
Action:
None.
LOWER CASE CHARS FOUND - PRESS PF9 AND RE-ENTER CHANGES_
Reason:
Lower case characters were found in the line being modified, but the terminal is in upper case mode.
Action:
Press PF9 and re-enter the changes.
NO STRUCTURE INFORMATION FOR A FIND= REQUEST
Reason:
The name specified does not exist in the structure.
Action:
Correct the name and retry the request.
FIND= REQUEST HAS WRAPPED
Reason:
The name requested occurs before the first name currently displayed.
Action:
None.
(*) FIELD CONTAINS INVALID PACKED DATA
Reason:
A field defined as PACKED contains non-PACKED data.
Action:
Correct the field.
KEYWORD NOT SUPPORTED IN THIS RELEASE OF CICS
Reason:
The keyword is not supported by the CICS release you are using.
Action:
None.
ABEND OCCURRED IN PROGRAM (*) AT OFFSET (*)
Reason:
The ABEND occurrence in the Kernel Error Data Block points to the program at the stated offset.
Action:
Use this information and the register contents to debug the abend.
NO PROGRAM NAME FOUND MATCHING STORAGE ADDRESS
Reason:
The address does not occur in any program in the CICS region.
Action:
None.
ADDRESS POINTS TO PROGRAM (*) AT OFFSET (*)
Reason:
The address specified in the WHERE request points to the program at the offset specified.
Action:
None.
INVALID OPERATION FOR SymDump
Reason:
The keyword requested is invalid under CA SymDump for CICS.
Action:
None.
CORE/KEEP WINDOW REFERENCED PROTECTED CSA ABEND SUPPRESSED_
Reason:
The KEEP window was requested to display a fetch-protected area. This area cannot be displayed.
Action:
Correct the KEEP window request.
InterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)_
Reason:
The wrong CA InterTest for CICS release is installed in your CICS region.
Action:
Install the proper CA InterTest for CICS release.
CORE FACILITY TERMINATED
Reason:
The CORE facility was terminated.
Action:
None.
NOTAUTH CONDITION - RESOURCE LEVEL SECURITY FAILED FOR "(*)"_
Reason:
The transaction is not authorized to use the resource.
Action:
Adjust your security definitions, and resubmit the request.
SECURITY PASSWORD ====>
Reason:
An attempt is being made to change storage which does not belong to a break-pointed task and CA InterTest for CICS has been generated with CORESEC=YES.
Action:
Do one of the following:
OPERATION VALID FOR SymDump ONLY
Reason:
The keyword requested is only valid when using CA SymDump for CICS.
Action:
Review your request and select another keyword.
VALUE OF FIELD = (*)
Reason:
The decimal value, xxxxxxxxx, is displayed for a COBOL data item that was defined as numeric. The sign, a '+' or '-', appears as the first character 's'.
Action:
None.
SQLCODE CODE (*) HAS OCCURRED
Reason:
A serious SQL return code xxxxx has occurred. This could be caused possibly by an incomplete/incorrect installation of the CA InterTest for CICS DB2 interface.
Action:
Contact your site CA InterTest for CICS or CA SymDump for CICS installer and report this error.
(*)
Reason:
Miscellaneous informational CORE messages.
Action:
See message text.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|