CA InterTest for CICS Messages › IN25TRCF Messages: CAIN5980 to CAIN5999

IN25TRCF Messages: CAIN5980 to CAIN5999

CAIN5980

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX STARTED, NNNNNNNN TRACE BLOCKS TO BE PROCESSED.

Reason:

The CA SymDump for CICS Trace Format Region has established a CCI communications session with a CICS task. SUBXXXX uniquely identifies the subtask that is being started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. The number of trace blocks being sent is also listed.

Action:

None. This is an informational message indicating that the Trace Format Region started a format subtask.

CAIN5981

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CCI INIT FAILURE

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI initialization call has failed. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. A dump may be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5982

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CCI CONVERSE FAILURE

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI converse call has failed. SUBXXXX uniquely identifies the subtask that is being started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. A dump may be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5984

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX API CCI CALL FAILURE FOR PROGRAM: IN25TRCF

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call issued by IN25TRCF has failed. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. A dump may be taken and there are diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5990

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FDBVDESC:

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has received a non zero return code. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. FDBVDESC will be followed by diagnostic information that must be provided to CA technical support, in the event of a product malfunction. A dump may have been taken and there may be additional diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

In the event of a RECEIVE TIMEOUT in the TRACE FORMAT REGION, this message is purely informational and no action is required, although you may want to review your IN25OPTS definitions to increase your format timeout threshold (TRCFTOUT). If you suspect a product malfunction, then record this message number, the time/date of the occurrence, and then contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5992

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FREEMAIN OF LIST HAS FAILED

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error while trying to freemain storage previously acquired. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5993

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX GETMAIN FAILURE

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error while trying to getmain storage. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5994

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX API CALL FAILURE:

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request. API CALL FAILURE is followed by diagnostic information that must be provided to CA technical support.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5995

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX UNABLE TO DISPATCH IN25TRCM

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5996

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX CONVERSE ILLOGIC

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5997

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX

Reason:

While formatting your CICS trace entries CA SymDump for CICS has encountered an internal error. SUBXXXX uniquely identifies the subtask that has been started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CAIN5999

MM/DD/YYYY HH:MM:SS SUBXXXXX CICSXXXX FINISHED

Reason:

The CA SymDump for CICS Trace Format Region has completed a CCI communications session with a CICS task. SUBXXXX uniquely identifies the subtask that is being started to format a CICS trace, the number corresponds to the CICS task number in the CICS job that is sending the format request. CICSXXXX is the CICS job that is sending the format request.

Action:

None. This is an informational message indicating that the Trace Format Region completed a format request.