CSQCABNT |
Abnormal termination |
Before issuing END_THREAD ABNORMAL to WebSphere MQ. This
is due to the end of the task and therefore an implicit backout could be performed
by the application. A ROLLBACK request is included in the END_THREAD call
in this case. |
Unit of work information. You can use this information
when finding out about the status of work. (For example, it can be verified
against the output produced by the DISPLAY THREAD command, or the log print
utility.) |
CSQCAUID |
Bridge security |
Before validating bridge user password or PassTicket. |
User ID. |
CSQCBACK |
Syncpoint backout |
Before issuing BACKOUT to WebSphere MQ. This is due to an explicit
backout request from the application. |
Unit of work information. |
CSQCCONX |
MQCONNX |
Before issuing MQCONNX to WebSphere MQ. |
Connection tag. |
CSQCCCRC |
Completion code and reason code |
After unsuccessful return from API call. |
Completion code and reason code. |
CSQCCOMM |
Syncpoint commit |
Before issuing COMMIT to WebSphere MQ. This can be due to a
single-phase commit request or the second phase of a two-phase commit request.
The request is due to a explicit syncpoint request from the application. |
Unit of work information. |
CSQCDCFF |
IBM(R) use only |
CSQCDCIN |
IBM use only |
CSQCDCOT |
IBM use only |
CSQCEXER |
Execute resolve |
Before issuing EXECUTE_RESOLVE to WebSphere MQ. |
The unit of work information of the unit of work issuing
the EXECUTE_RESOLVE. This is the last in-doubt unit of work in the resynchronization
process. |
CSQCGETW |
GET wait |
Before issuing CICS wait. |
Address of the ECB to be waited on. |
CSQCGMGD |
GET message data |
After successful return from MQGET. |
Up to 40 bytes of the message data. |
CSQCGMGH |
GET message handle |
Before issuing MQGET to WebSphere MQ. |
Object handle. |
CSQCGMGI |
Get message ID |
After successful return from MQGET. |
Message ID and correlation ID of the message. |
CSQCHCER |
Hconn error |
Before issuing any MQ verb. |
Connection handle. |
CSQCINDL |
In-doubt list |
After successful return from the second INQUIRE_INDOUBT. |
The in-doubt units of work list. |
CSQCINDO |
IBM use only |
CSQCINDS |
In-doubt list size |
After successful return from the first INQUIRE_INDOUBT
and the in-doubt list is not empty. |
Length of the list; divided by 64 gives the number
of in-doubt units of work. |
CSQCINDW |
Syncpoint in doubt |
During syncpoint processing, CICS is in doubt as to the disposition of
the unit of work. |
Unit of work information. |
CSQCINQH |
INQ handle |
Before issuing MQINQ to WebSphere MQ. |
Object handle. |
CSQCLOSH |
CLOSE handle |
Before issuing MQCLOSE to WebSphere MQ. |
Object handle. |
CSQCLOST |
Disposition lost |
During the resynchronization process, CICS informs the
adapter that it has been cold started so no disposition information regarding
the unit of work being resynchronized is available. |
Unit of work ID known to CICS for the unit of work being resynchronized. |
CSQCNIND |
Disposition not in doubt |
During the resynchronization process, CICS informs the
adapter that the unit of work being resynchronized should not have been in
doubt (that is, perhaps it is still running). |
Unit of work ID known to CICS for the unit of work being resynchronized. |
CSQCNORT |
Normal termination |
Before issuing END_THREAD NORMAL to WebSphere MQ. This
is due to the end of the task and therefore an implicit syncpoint commit might
be performed by the application. A COMMIT request is included in the END_THREAD
call in this case. |
Unit of work information. |
CSQCOPNH |
OPEN handle |
After successful return from MQOPEN. |
Object handle. |
CSQCOPNO |
OPEN object |
Before issuing MQOPEN to WebSphere MQ. |
Object name. |
CSQCPMGD |
PUT message data |
Before issuing MQPUT to WebSphere MQ. |
Up to 40 bytes of the message data. |
CSQCPMGH |
PUT message handle |
Before issuing MQPUT to WebSphere MQ. |
Object handle. |
CSQCPMGI |
PUT message ID |
After successful MQPUT from WebSphere MQ. |
Message ID and correlation ID of the message. |
CSQCPREP |
Syncpoint prepare |
Before issuing PREPARE to WebSphere MQ in the first phase of
two-phase commit processing. This call can also be issued from the distributed
queuing component as an API call. |
Unit of work information. |
CSQCP1MD |
PUTONE message data |
Before issuing MQPUT1 to WebSphere MQ. |
Up to 40 bytes of data of the message. |
CSQCP1MI |
PUTONE message ID |
After successful return from MQPUT1. |
Message ID and correlation ID of the message. |
CSQCP1ON |
PUTONE object name |
Before issuing MQPUT1 to WebSphere MQ. |
Object name. |
CSQCRBAK |
Resolved backout |
Before issuing RESOLVE_ROLLBACK to WebSphere MQ. |
Unit of work information. |
CSQCRCMT |
Resolved commit |
Before issuing RESOLVE_COMMIT to WebSphere MQ. |
Unit of work information. |
CSQCRMIR |
RMI response |
Before returning to the CICS RMI (resource manager interface) from
a specific invocation. |
Architected RMI response value. Its meaning depends
of the type of the invocation. To determine the type of invocation, look at
previous trace entries produced by the CICS RMI component. |
CSQCRSYN |
Resync |
Before the resynchronization process starts for the
task. |
Unit of work ID known to CICS for the unit of work being resynchronized. |
CSQCSETH |
SET handle |
Before issuing MQSET to WebSphere MQ. |
Object handle. |
CSQCTASE |
IBM use only |
CSQCTEST |
Trace test |
Used in EXEC CICS ENTER TRACE call to verify the trace
number supplied by the user or the trace status of the connection. |
No data. |