Reason:
In response to the FUNC=GET, FUNC=NEXT, or FUNC=PREV that you entered, a record has been received and its data has been placed in the WORK AREA that is currently displayed.
Action:
None.
Reason:
A WORK AREA has been obtained in response to the FUNC=ADDN or FUNC=ADDU that you entered.
Action:
None.
Reason:
A browse operation began in response to your command.
Action:
None.
Reason:
A browse operation has ended in response to the FUNC=ENDB that you entered.
Action:
None.
Reason:
The current WORK AREA has been saved, in response to the FUNC=SAVE that you entered.
Action:
None.
Reason:
An existing saved WORK AREA has been replaced by a new saved WORK AREA, in response to the FUNC=SAVE that you entered.
Action:
None.
Reason:
The saved WORK AREA is displayed on your screen, in response to the FUNC=DISS that you entered.
Action:
None.
Reason:
The WORK AREA is displayed on your screen, in response to the FUNC=DISW that you entered.
Action:
None.
Reason:
A VSAM record has been retrieved by an alternate index, in response to the FUNC=GET that you entered. However, there are other records in the data set that have the same alternate key. The VSAM record's data was placed in the WORK AREA, which is now displayed on the screen.
Action:
A browse retrieves the duplicate records.
Reason:
The record specified in the RCID= field has been retrieved for update, in response to the FUNC=GETU that you entered. The record's data was placed in the WORK AREA, which is now displayed on your screen.
Action:
None.
Reason:
(1) For MODE=UPDATE, the record specified in the RCID= field, which had previously been retrieved for update, has been released. (2) For MODE=ADD or MODE=ADDM, this indicates that you have specified that no more records will be added.
Action:
None.
Reason:
The record specified in the RCID= field has been deleted from the file specified in the FILEID= field, in response to the FUNC=DEL or FUNC=PUT/SUBFUNC=DEL that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
The record specified in the RCID= field has been added to the file specified in the FILEID= field, in response to the FUNC=PUT that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
The record specified in the RCID= field has been replaced in the file specified in the FILEID= field, in response to the FUNC=PUT that you entered. The record's data is still displayed in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
The data specified in the DATA= field has been found, in response to the FUNC=SRCH that you entered. The record was retrieved and its data placed in the WORK AREA, which is displayed on your screen, beginning with the byte where the data was found.
Action:
None.
Reason:
An end‑of‑file condition has been encountered during a FUNC=NEXT or a beginning‑of‑file condition was found during a FUNC=PREV. The browse operation has been terminated.
Action:
None.
Reason:
Your request has been processed successfully.
Action:
None.
Reason:
A record has been retrieved from the temporary storage area specified in the RCID= field, in response to the FUNC=GET that you entered. The record's data was placed in the WORK AREA, which is now displayed on your screen.
Action:
None.
Reason:
A record has been retrieved and released from the temporary storage area specified in the RCID= field, in response to the FUNC=REL or FUNC=GET/SUBFUNC=REL that you entered.
Action:
None.
Reason:
The temporary storage queue record specified in the RCID=and ENTRY= fields has been retrieved, in response to the FUNC=GETQ that you entered. The record's data was placed in the WORK AREA, which is now displayed on your screen.
Action:
None.
Reason:
The temporary storage queue specified in the RCID= field has been purged, in response to the FUNC=PURG that you entered.
Action:
None.
Reason:
A record has been written to the temporary storage area specified in the RCID= field, in response to the FUNC=PUT that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
A record has been replaced in the temporary storage area specified in the RCID= field, in response to the FUNC=PUT/SUBFUNC=REPL that you entered. The record's data is still active in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
A record has been written to the temporary storage queue specified in the RCID= field, in response to the FUNC=PUTQ that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
A record has been placed in the temporary storage queue specified in the RCID= and ENTRY= fields, in response to the FUNC=PUTQ/SUBFUNC=REPL that you entered.
Action:
None.
Reason:
A transient data record has been retrieved from the transient data destination specified in the DESTID= field, in response to the FUNC=GET that you entered. The record's data was moved to the WORK AREA, which is displayed, on your screen.
Action:
None.
Reason:
The specified record was written to the transient data destination specified in the DESTID= field, in response to the FUNC=PUT that you entered. The record's data is still available in the WORK AREA, which is displayed on your screen.
Action:
None.
Reason:
The transient data destination specified in the DESTID= field was purged, in response to the FUNC=PURG that you entered.
Action:
None.
Reason:
Self‑explanatory.
Action:
Correct the error, and resubmit your request.
Reason:
Self‑explanatory.
Action:
Correct the error, and resubmit your request.
Reason:
The LOC= field does not contain one of the following values: all numerics, ?, FWD, BWD, or ANY.
Action:
Correct the error and resubmit the request.
Reason:
The record identification must be entered exactly as required in the CICS/VS Application Programmer's Reference Manual. This includes all the necessary bytes; the FILE transaction provides no padding. If character and hexadecimal values have to be mixed in the record identification, use C' ' and X' ' strings.
Action:
Correct the error, and resubmit the request.
Reason:
The DATATYPE= field was not an FC, TS, TD, or DL (if DL/I support is generated).
Action:
Correct the error, and resubmit the request.
Reason:
The function you selected is not known to the FILE transaction or is not supported for the specified file.
Action:
Correct the error, and resubmit the request.
Reason:
Self‑explanatory.
Action:
Correct the error and resubmit the request.
Reason:
The RETMETH= field does not contain 'KEY' or 'RELREC'.
Action:
Correct the error and resubmit the request.
Reason:
The SRCHTYP= field does not contain one of the following: 'FKEQ', 'FKGE', 'GKEQ', or 'GKGE'.
Action:
Correct the error and resubmit the request.
Reason:
Self‑explanatory. Note that if both hexadecimal and character bytes are to be entered, a concatenation of C' ' and X' ' strings is most practical.
Action:
Correct the error and resubmit the request.
Reason:
The TODEST= field is either not filled in or is filled in with an invalid transient data destination. You can check the CICS Destination Control Table by issuing the CORE=DCT or CORE=DEST=destid command.
Action:
Correct the error and resubmit the command.
Reason:
The ARGTYP= field does not contain 'KEY', 'RBA' or 'XRBA'.
Action:
Correct and resubmit.
Reason:
Instructional message.
Action:
Enter the program.structure name in the USE= field.
Reason:
The number specified in the ENTRY= field is not within the limits of the existing queue.
Action:
Correct and resubmit.
Reason:
There is no space available in auxiliary storage.
Action:
None.
Reason:
The temporary storage record to be replaced cannot be found.
Action:
None.
Reason:
The symbolic temporary storage identification in the RCID= field could not be found. This is usually the same as a 'record not found' condition.
Action:
Correct the RCID= and resubmit.
Reason:
Access to remote temporary storage queues is not supported.
Action:
None.
Reason:
The transient data queue could not be accessed due to a busy condition.
Action:
Try the request later.
Reason:
There are no records in the Transient Data Queue.
Action:
None.
Reason:
The Transient Data Queue name is not defined to CICS.
Action:
Correct the queue name and resubmit.
Reason:
The destination entered in the DESTID= field is not opened.
Action:
Determine why the destination is not open. If possible, use the CEMT or CSMT service transactions to open the destination.
Reason:
The intrapartition data set specified in the DESTID= field is out of space.
Action:
None.
Reason:
The extrapartition data set specified in the DESTID= field is out of space.
Action:
None.
Reason:
Informational message.
Action:
None.
Reason:
The file named in the FILEID= was not found in the CICS File Control Table (FCT).
Action:
Correct the file name in the FILEID= field and resubmit the request.
Reason:
You attempted to add a record whose record key already exists.
Action:
None.
Reason:
You attempted to read a record that does not exist.
Action:
Correct the record ID and resubmit the request.
Reason:
A duplicate record occurred while you were executing a file request.
Action:
Correct the record ID, and resubmit the request.
Reason:
An invalid request occurred while executing a file request.
Action:
Check the FCT entry for the FILEID to ensure that it allows the type of processing that you requested.
Reason:
An Input/Output error occurred during the CICS requests and processing did not complete correctly.
Action:
Retry the request. If the error still occurs, contact your CICS Systems Programmer.
Reason:
EXEC CICS names a disabled or non‑existing program.
Action:
Check that the program is in the correct CICS Load Library. Check the program definition for the program you requested.
Reason:
There is no space available on the direct access device for adding records to a data set. Your program did not have a HANDLE CONDITION for this error.
Action:
Expand the data set or cancel your transaction by pressing PF9, ENTER and PF3.
Reason:
The error occurred because the file you are trying to access is not open to CICS. Your program did not have a HANDLE CONDITION for this error.
Action:
Disconnect your terminal from CA InterTest for CICS and use the CEMT transID to open the file. Then reconnect you terminal to CA InterTest for CICS and use the resume task menu to execute the CICS request again.
Reason:
You cannot modify the key of a record.
Action:
None.
Reason:
The file you are accessing is a DL/I database and DL/I cannot be accessed from DATATYPE=FC.
Action:
Specify DATATYPE=DL.
Reason:
Informational message.
Action:
Correct and resubmit.
Reason:
The file specified in the FILEID= field is defined as RECFORM= Undefined.
Action:
None.
Reason:
Informational message.
Action:
Determine why the file could not be opened. Correct the problem and resubmit your request.
Reason:
You attempted to update or insert a record that is too long (RECFM=V) or not equal (RECFM=F) to the file's record definition.
Action:
Specify the correct length and resubmit the request.
Reason:
Abend xxxx occurred while processing a remote request.
Action:
Probable MRO/ISC setup error. Check that the MRO/ISC connections are properly established and that CA InterTest for CICS release 4.2 or above is installed in each region.
Reason:
The file to be processed is not local to the region.
Action:
Use CA InterTest for CICS in the region that owns the file.
Reason:
An error occurred while establishing the session to the remote region. Probable MRO/ISC setup error.
Action:
Check the MRO/ISC connections. Ensure that CA InterTest for CICS release 4.2 or above is installed in each region. You can use CEDF to debug this problem and stop at ALLOCATE commands.
Reason:
Informational message.
Action:
None.
Reason:
The database is not defined to CICS, or it has not been started.
Action:
Ensure that the database exists and resubmit the request.
Reason:
The file to be processed is not local to the region.
Action:
Use CA InterTest for CICS in the region that owns the file.
Reason:
The PSB is not defined in the IN25FLF program's entry in the DL/I Application Control Table. The IN25FLF must be in the ACT because that programs issues the DL/I calls for the FILE transaction.
Action:
Add the PSB to the IN25FLF entry in the ACT.
Reason:
The PSB has already been scheduled.
Action:
Continue with the request.
Reason:
The specified PSB was generated as PL/I.
Action:
Change the PSB language specification and regenerate, or generate a duplicate PSB that specifies the languages as ASM.
Reason:
The PSB could not be scheduled.
Action:
Determine the reason for this failure.
Reason:
The PSB is not defined in the IN25FLF program's entry in the DL/1 Application Control Table. The IN25FLF must be in the ACT because that program issues the DL/1 calls for the FILE transaction.
Action:
Add the PSB to the IN25FLF entry in the ACT.
Reason:
Informational message.
Action:
Determine why the DL/1 interface has been terminated.
Reason:
A proper PSB must be scheduled to complete your DLI call.
Action:
Specify the correct PSB, and resubmit the request.
Reason:
Informational message.
Action:
Enter the appropriate value.
Reason:
The proper PSB must be scheduled to complete your DLI call.
Action:
Check the PSB specified, and resubmit the request.
Reason:
The DBD specified in the DBD= field was not found in the PSB that was entered in the PSB= field.
Action:
Enter the correct PSB or DBD and resubmit.
Reason:
The PCB number in the NO= field for this DBD is invalid.
Action:
Specify the correct PCB number and resubmit.
Reason:
Informational message.
Action:
Specify the correct SSA and resubmit.
Reason:
You attempted to access a DL/I database, but your attempt has failed, because the DL/I is not defined to the region.
Action:
Check the SIT parameter, DL1=.
Reason:
No WORK AREA was found for a FUNC= DISW request.
Action:
Enter the appropriate value.
Reason:
The transient data copy function may not be used while the logging or audit functions are active.
Action:
Deactivate these functions, and resubmit the request.
Reason:
The system installation defined automatic logging through AUDIT=YES, and the no logging (NLOG) parameter was specified by the user.
Action:
Logging is performed.
Reason:
BDAM files cannot be read in reverse.
Action:
None.
Reason:
The value in the LOC= field points beyond the WORK AREA.
Action:
Enter the correct value and resubmit.
Reason:
There was no work area available for the specified function.
Action:
Issue a save command, and resubmit the request.
Reason:
Informational message.
Action:
Correct and resubmit.
Reason:
The file or DBD you are working with is password‑protected. The password is missing from the PASSWORD= field or PS= field. The person who generated CA InterTest for CICS at your installation should be able to answer any questions about FILE passwords.
Action:
Enter the correct password.
Reason:
The password that you entered was incorrect.
Action:
Obtain the appropriate password and resubmit.
Reason:
Informational message.
Action:
Refer to the CA InterTest for CICS User Guide for the proper sequence.
Reason:
The data specified in the DATA= field has been not been found after searching the number of records specified in the SIZE= field, in response to the FUNC= SRCH command that you entered.
Action:
Enter a different data string.
Reason:
The file name, or identification, is missing from the FILEID= field.
Action:
Enter the appropriate value.
Reason:
The transient data destination name, or identification, is missing from the DESTID= field.
Action:
Enter the appropriate value.
Reason:
The FILE transaction is not authorized to access the file.
Action:
If the file or TS queue is remote, check the CICS mirror transaction authority. You can use CEDF to debug this problem.
Reason:
Informational message.
Action:
None.
Reason:
You attempted to access a disabled transient data queue.
Action:
Enable the queue, and resubmit your request.
Reason:
A logic error occurred in the file transaction.
Action:
Contact CA technical support.
Reason:
The FILE transaction goes to the CA InterTest for CICS program IN25SEC2 to check to see if a password is valid. However, the transaction was unable to find IN25SEC2.
Action:
Report the problem to the person who installed CA InterTest for CICS.
Reason:
An unexpected error has occurred.
Action:
Resubmit your request. If you still get an error, contact CA technical support.
Reason:
The command you entered is not supported in this release of CA InterTest for CICS.
Action:
None.
Reason:
This error occurs after all other error conditions have been checked.
Action:
Check the VSAM error code in the VSAM Messages and Codes manual and proceed accordingly. The value in VSWARTNC is the same as the value in register 15 on return from the VSAM macro. The value in VSWAERRC is the error code from the RPL block in the VSWA area. Both values are expressed in hexadecimal format.
Reason:
A logic error occurred in the file transaction.
Action:
Contact CA technical support.
Reason:
The global logging Transient Data Destination ID is not defined to CICS or it cannot be written to.
Action:
Ensure that the Destination ID exists and can be written to.
Reason:
A 'FIND' request for an undefined data name was issued.
Action:
Specify a valid data name, and resubmit the request.
Reason:
This item is the first item in a structured request.
Action:
None.
Reason:
This item is the last item displayed for a structured request.
Action:
None.
Reason:
You were displaying a structured work area before setting a breakpoint or UBP option.
Action:
Start CA InterTest for CICS at the first area in the procedure division or at #1 before looking at the item.
Reason:
The structured file is longer than the area that you are trying to access.
Action:
Specify the actual length of the structured file and insert that information into the program. Recompile the program and run the NEW COPY function.
Reason:
This item is the last field of the structure. It has been redefined.
Action:
None.
Reason:
The length of the item you are trying to view is longer than the length of the work area.
Action:
Increase the length of the work area. Recompile the program and run the NEW COPY option.
Reason:
The specified location is not part of your record.
Action:
Check the listing to find out where the field is located and correct the LOC= entry.
Reason:
The transaction was abended or the transaction ended correctly
Action:
Press PF1 to display the abend, or specify the next transaction.
Reason:
You pressed Clear and terminated the FILE facility.
Action:
None.
Reason:
Errors are present in your listing.
Action:
Check your listing to determine where the errors occurred.
Reason:
This message indicates that (*) bytes changed. It gives the address of the first byte (YYYYYYY).
Action:
None.
Reason:
The program was not loaded in the proper CICS load LIB. The PPT entry was disabled and cannot be loaded.
Action:
Modify or correct the PPT name. Ensure that the program is loaded into the correct load LIB.
Reason:
A remote file cannot be accessed, or it is not defined properly.
Action:
Check the file definitions and the CICS connection to the remote system.
Reason:
The specified abend occurred while you were trying to access the DBCTL.
Action:
For more information, see the DB2 Messages and Codes manual. Correct the problem and retry.
Reason:
You requested that specified records be deleted using the FILE facility of CA InterTest for CICS.
Action:
None.
Reason:
The file you were searching for was not found.
Action:
Check the FCT entries to see where the file is located. Correct the FCT entry if necessary.
Reason:
There is a logic error. The EIB return code (N), EIB error code (X) follows.
Action:
Examine your program and correct the logic.
Reason:
An internal logic problem exists in the FILE transaction.
Action:
Contact CA technical support.
Reason:
You attempted to modify lowercase data to upper‑case data because you are in Caps On mode. The lower case data was not modified.
Action:
Press PF9 to switch to Caps Off mode, and reenter the modified data, or switch to Format H and modify the data.
Reason:
You entered the wrong search type. To delete records, enter FKEQ or GKEQ.
Action:
Specify FKEQ or GKEQ as your search type.
Reason:
A partial dump occurred. It contains registers and the last instruction that was executed.
Action:
Enable ITTrace to obtain a valid dump: CNTL=ITTRACE,ON. Or, fix the error that caused the dump to occur.
Reason:
The DL/I CALL that you specified executed successfully.
Action:
None.
Reason:
The DL/I CALL that you specified did not execute successfully. Refer to the IBM IMS/VS Application Programming Guide for CICS Users for a detailed explanation of the DL/I status code, which appears on the FILE menu.
Action:
Contact CA technical support.
Reason:
This database call requires that the SSAs be properly specified.
Action:
Correct the SSAs and resubmit, or contact CA technical support.
Reason:
The database you are trying to open could not be accessed.
Action:
Check the parameters you set and resubmit, or contact CA technical support.
Reason:
Informational message.
Action:
Check the parameters you set and resubmit, or contact CA technical support.
Reason:
Informational message.
Action:
Correct the SSA field name and try again, or contact CA technical support.
Reason:
Your request is illogical.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
An I/O error occurred during the CICS request, and processing was not successfully completed.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
There is no such command in CA InterTest for CICS.
Action:
Refer to the CA InterTest for CICS User Guide for a list of valid commands.
Reason:
The command you entered in your program executed successfully.
Action:
None.
Reason:
The command you entered violates security.
Action:
Check the command you entered. See your facility's systems people to find out what caused the security violation.
Reason:
While completing a FILE transaction, you attempted to change a non‑replaceable or segment key field.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
The command you entered requires that a previous GHX had been successfully executed.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
You did not enter the FUNC=DEL command properly.
Action:
Refer to the CA InterTest for CICS User Guide for a list of valid commands, correct your request and try again, or contact CA technical support.
Reason:
A DL/1 request was issued, which caused a hierarchy boundary change.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
An End of Dataset was encountered while processing the DL/I request.
Action:
None.
Reason:
The segment that you requested is not on the file.
Action:
None.
Reason:
Your data includes 2 or more field names at this level.
Action:
Correct your request and try again, or contact CA technical support.
Reason:
A DL/I GNP or GHNP call was executed, but no parentage was established.
Action:
None.
Reason:
You are trying to add a record that already exists.
Action:
Delete the older record before you add this record, or clear out this record.
Reason:
Your attempt to insert or add a record or record segment was invalid.
Action:
Refer to the CA InterTest for CICS User Guide for a list of rules on how to use the File Request option. Correct your request and try again, or contact CA technical support.
Reason:
The segment that you are trying to add is already on the database.
Action:
Contact CA technical support.
KEY FIELD OF SEGMENT OUT OF SEQUENCE
Reason:
The key field of the segment being loaded is out of sequence.
Action:
Check the segment and determine where it should be loaded.
NO PARENT FOR THIS SEGMENT HAS BEEN LOADED
Reason:
An illogical DL/1 request has been made.
Action:
Respecify the command, or contact Support.
OUT OF SEQUENCE FOR SIBLING SEGMENT
Reason:
An illogical DL/1 request has been made.
Action:
Respecify the command.
VIOLATED REPLACE RULE
Reason:
You did not enter the correct information to replace a record or field.
Action:
Refer to the CA InterTest for CICS User Guide for a list of rules on how to replace a record or field.
NO Message FOR THIS STATUS CODE
Reason:
There is no message available for this status.
Action:
None.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|