Reason:
The batch utility has started.
Action:
None.
Reason:
The batch utility has ended.
Action:
None.
Reason:
The batch utility was terminated due to a previous error. See previous message.
Action:
Correct the error and rerun the batch utility.
Reason:
An invalid name specifying the data set name was used in the DSN command.
Action:
Correct the data set name and rerun the batch utility.
Reason:
An invalid name specifying the data set name was used in the ODSN command.
Action:
Correct the data set name and rerun the batch utility.
Reason:
The date was entered in the wrong format or the value is not valid.
Action:
Correct the date using format MM/DD/YYYY and rerun the batch utility.
Reason:
The batch utility did not recognize the command. Either the wrong command was used or positional parameters (or values) were wrong.
Action:
Check the syntax of the command, correct it, and rerun the batch utility.
Reason:
The PROTDMP size does not match the size specified in the PROTDMP header.
Action:
Check the VSAM data set size and value in the PROTDMP header. Manually correct the value in the PROTDMP header.
Reason:
The data set used in the DSN or ODSN commands does not exist or the batch utility cannot access it.
Action:
Check the system messages in the joblog. Check the data set name and its status, and rerun the batch utility. If the problem persists, contact the system programmer.
Reason:
The data set name is valid. However, the batch utility cannot work with it.
Action:
Check the system messages in the joblog, correct the situation, and rerun the batch utility. If the problem persists, contact the system programmer.
Reason:
An unpredictable error occurred while reading the data set. The batch utility is not able to read it.
Action:
Check the system messages in the joblog, correct the situation, and rerun the batch utility. If the problem persists, contact the system programmer.
Reason:
While processing the requested action, another job has modified the dump.
Action:
Check the PROTDMP content. If still required, repeat the action.
Reason:
The PROTDMP source and destination are the same. This is not allowed for the COPY command.
Action:
None.
Reason:
The dump code of the copied dump is suppressed in the PROTDMP destination.
Action:
To copy the dump, use the OPT command, change the suppressing option in the destination PROTDMP, and rerun the batch utility.
Reason:
The dump code of the copied dump is excluded in the PROTDMP destination.
Action:
To copy the dump, use the OPT command, change the excluding option in the PROTDMP destination, and rerun the batch utility.
Reason:
There is no space in the PROTDMP destination for storing another dump.
Action:
Delete unneeded dumps in the PROTDMP destination, and repeat the action. Space depends on the deleted dump's size.
Reason:
The maximum number of possible stored dumps in the PROTDMP destination was reached. No other dump could be stored.
Action:
Delete unneeded dumps in the PROTDMP destination, and repeat the action. Space depends on the deleted dump's count.
Reason:
The LOCK function was requested for a dump that is already locked.
Action:
None.
Reason:
The UNLOCK function was requested for a dump that is not locked.
Action:
None.
Reason:
While processing the DELETE command, another job has already performed the same action.
Action:
None.
Reason:
There are no dumps to delete.
Action:
None.
Reason:
The selected dump for a delete action is locked.
Action:
Unlock the dump using the UNLOCK command, and use the DELETE command again.
Reason:
A value used in a parameter of the command is not valid.
Action:
Correct the value and rerun the batch utility.
Reason:
The requested command is not valid.
Action:
Correct the command and rerun the batch utility.
Reason:
During dump capture, CA SymDump attempts to read the last screen image from the terminal. If the terminal does not respond within 16 seconds, the last screen capture times out and this informational message displays on the console log. The last screen image will not have been captured for the dump.
Action:
Determine the reason the terminal was not responding, and resolve the problem so that future dumps can be captured completely.
Reason:
Delete, Hold, and Release functions are not valid for a remote file.
Action:
Dump the PROTDMP file as local or enter the commands in another region.
Reason:
During dump capture, program IN25SYMZ attempted to capture the File Information Block, but failed.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ attempted to capture the Transaction Information Block, but failed.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ attempted to capture Last SQL information, but failed.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ attempted to capture the Terminal Information Block, but failed.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ failed because of unknown reason. IN25SYMZ resumes processing.
Action:
Action: Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ failed because of unknown reason. IN25SYMZ terminates.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ failed because of missing COMMAREA. IN25SYMZ terminates.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
During dump capture, program IN25SYMZ failed because of missing EXCAAREA. IN25SYMZ terminates.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA Support.
Reason:
CA SymDump for CICS program IN25SYMZ has detected a problem and has requested an SDUMP of the region.
Action:
Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|