Reason:
Module IN25COLD of CA SymDump for CICS was assembled at the indicated date and time. This message is displayed when IN25COLD is made resident during initialization. x.x.x is your CA SymDump for CICS release number.
Action:
None.
Reason:
CA SymDump for CICS has finished processing the abend, and is returning control to CICS and directing it to record the dump in its own dump data set.
Action:
None.
Reason:
A VSAM error occurred for the function xxx while accessing the CA SymDump for CICS file.
Action:
Check the VSAM manual for an explanation of the return code and FDBK code for the function specified.
Reason:
An I/O error occurred while accessing the CA SymDump for CICS file. See message CASD6051.
Action:
Determine the cause of the error from the VSAM return codes.
Reason:
There is not enough free DSA storage in CICS to fill a storage request.
Action:
Check why CICS is short on storage and reenter the transaction.
Reason:
There is not enough free space on the CA SymDump for CICS file to accommodate more dumps.
Action:
Delete unnecessary dumps or release dumps currently being held.
Reason:
Too many freespace fragments exist on the CA SymDump for CICS file.
Action:
Delete unnecessary dumps to reduce the number of freespace fragments.
Reason:
The maximum number of dumps has been exceeded.
Action:
Delete unnecessary dumps.
Reason:
Freespan area overflow or index area overflow has occurred. See messages CASD6055 and CASD6056.
Action:
Delete unnecessary dumps.
Reason:
An invalid storage address was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
An invalid pointer to the next LLA was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
An invalid pointer to the next user storage block was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
An invalid pointer to the next TIOA storage block was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
An invalid pointer to the next anchor block was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
An invalid pointer to the next PCB block was found while dumping storage areas for a given task.
Action:
Analyze the dump to determine the cause of the transaction abend.
Reason:
The abending program was not a CICS loaded program.
Action:
Use the storage area dump around the PSW to help determine the cause of the transaction abend.
Reason:
The storage area around the PSW was not dumped separately because the abend occurred within the current program that appears in the dump.
Action:
Use the storage area dump around the PSW to help determine the cause of the transaction abend.
Reason:
The PROTDMP file has been damaged. No more dumps can be written to this file.
Action:
Stop CA SymDump for CICS, print the dumps, and obtain a hex printout of the first five records in the PROTDMP file. Reinitialize the file and restart CA SymDump for CICS. Contact CA technical support for help in resolving the problem.
Reason:
CA SymDump for CICS has intercepted a CICS transaction dump for transaction code aaaa. The abend code for the dump is bbbb.
Action:
None.
Reason:
CA SymDump for CICS was unable to obtain the storage required to capture this transaction dump. Processing is terminated. CICS takes a normal transaction dump.
Action:
Review other messages accompanying this message to determine the cause.
Reason:
CA SymDump for CICS has intercepted an AP0001 system dump or an EXEC CICS dump request on behalf of transaction aaaa. The dump type is shown as bbbbbbbb.
Action:
None.
Reason:
CA SymDump for CICS will not record this dump to the PROTDMP file. This is due to one of the following reasons:
Action:
Review the CA SymDump for CICS initialization parameters through the SYMI transaction. You can update the parameters to specify how you want CA SymDump for CICS to handle specific dumps.
Reason:
CA SymDump for CICS has captured the dump. x.x.x represents your CA SymDump for CICS release number.
Action:
None.
Reason:
CA SymDump for CICS does not record this dump to the PROTDMP file because this abend code has been excluded from CA SymDump for CICS processing. The exclusion is specified on the Initialization screen.
Action:
If you want to capture this abend, enter the transaction SYMI to update the initialization parameters. Remove the appropriate abend code from the list of abend codes to be "EXCLUDED."
Reason:
IN25COLD failed on a getmain request.
Action:
Review your CICS messages for any indications as to why this failure occurred. If none exists, contact CA SymDump for CICS technical support.
Reason:
IN25COLD failed on a getmain request.
Action:
Review your CICS messages for any indications as to why this failure occurred. If none exists, contact CA SymDump for CICS technical support.
Reason:
IN25COLD failed on a getmain request.
Action:
Review your CICS messages for any indications as to why this failure occurred. If none exists, contact CA SymDump for CICS technical support.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|