Format of messages
The information that is displayed in the text of each message has a standard set of fields, although not all of the fields are populated with data for certain messages. The messages are also grouped into types, and each type of message includes some additional information to help diagnose the cause of the error.
The standard set of fields appear in each message in the following format:
Processed: Date: ddmmyy Processed: Time: hhmmss PutApplid: applid PutTranid: transaction
Error: message number Processing type
Userid: username Applid: applid Tranid: tranid Eibtaskn: number AbsTime: time
Request: request name Mode: mode Program: program name Type: program type
Activity: activity name Node name: node name
Event: event Event type: event type Step: program step
Proctype: process type Process: process
Failed Processtype: failed process Failed process: failed process
ReplyToQ: WebSphere MQ reply queue ReplyToQMgr: WebSphere MQ reply queue mgr
MQ MsgId: WebSphere MQ message identifier MQ CorrelId: WebSphere MQ correlation identifier
Error detail: error text
- Processed: Date
- The date that the record was written to the CMAC transient data queue.
- Processed: Time
- The time that the record was written to the CMAC transient data queue.
- PutApplid
- The APPLID retrieved from the origin context in the WebSphere® MQ Message Descriptor structure (MQMD), after a successful MQGET command. See the WebSphere MQ Application Programming Reference for more information.
- PutTranid
- The transaction ID retrieved from the original context in the WebSphere MQ Message Descriptor structure (MQMD), after a successful MQGET command.
- Error
- The error message that indicates the error that occurred. See Messages and codes for a description of the error messages that can display in this field.
- Processing type
- The mode of request processing. The value is derived from a field
in the request message header. See Request message headers for
information on the DFHMAH-UOWCONTROL field. Valid values are as follows:
- Normal processing
- Compensation processing
- Cancel processing
- Userid
- The user ID under which the error was reported, and for which the request processing was occurring.
- Applid
- The APPLID indicating the CICS® region and transaction, under
which the failed application program was running, where the error
occurred.
This value can be different from the PutApplid if an error occurred in a program link or queue server adapter that was not running in the same region as the controlling flow navigator; for example, because of workload balancing. The program link and queue server adapters return control to the flow navigator indicating the error. The flow navigator subsequently writes to the CMAC TDQ.
- Tranid
- The transaction ID indicating the CICS region and transaction, under which the failed application program was running, where the error occurred.
- Eibtaskn
- The task number of the failed transaction assigned by CICS. See the CICS Application Programming Reference for more information.
- AbsTime
- The time as reported by CICS when the error occurred. This time is retrieved with an EXEC CICS ASKTIME command. See the CICS Application Programming Reference for more information
- Request
- The name of the service flow request that was being processed when the failure occurred.
- Mode
- The mode of request processing that was in effect when the failure
occurred. The type of request processing is saved in the service flow
repository file, DFHMAASF, and is retrieved based on the request name.
Valid values are as follows:
- Async
- Link
- Sync
- Sync RB
- Program
- The program name that reported the error or where the failure occurred. In the case of a program link server adapter, it could be the target program name. This is true when the error is an abend in the target program.
- Type
- The type of program indicated by the program name. Valid values
are as follows:
- Navigator
- DPL
- MQPUT
- FEPI
- MQGET
- LINK3270
- System
- Activity
- The activity name that reported the error or where the failure occurred. The activity name is the program name being run as an activation. If the error was reported in the CICS SFR interface program, DFHMADPL, this field is blank. For information on activity names, see the CICS Business Transaction Services manual.
- Node Name
- The node name that reported the error or where the failure occurred. The node name is the program name being run as an activation. Node names are server adapters.
- Event
- The last reattach event retrieved at the time of failure. For information regarding BTS events, see the CICS Business Transaction Services manual
- Event type
- The event type of the last reattach event retrieved at the time
of failure. For information regarding BTS events and event types,
see the CICS Business Transaction Services manual.
Valid values are as follows:
- Input
- Activity
- Composite
- Timer
- System
- None
- Unknown
- Step
- Indicates the internal program step at the time of failure.
- Proctype
- The process type of the request or process that reported the error or failure.
- Process
- The process name of the request processing instance that reported the error or failure.
- Failed Processtype
- The failed process type of a previously run instance of the request processing that resulted in error or failure. This field is populated when an error or failure occurs in a service flow process that was run as the result of an earlier processing failure.
- Failed Process
- The failed process name of a previously run instance of the request processing that resulted in error or failure. This field is populated when an error or failure occurs in a service flow process that was run as the result of an earlier processing failure.
- ReplyToQ
- The WebSphere MQ reply queue name where CICS Service Flow Runtime writes the
error reply. This field is populated when an error or failure occurs
in asynchronous request processing.
For information regarding WebSphere MQ programming, see WebSphere MQ Application Programming Reference and the WebSphere MQ Application Programming Guide.
- ReplyToQMgr
- The WebSphere MQ reply queue manager name where CICS Service Flow Runtime writes the error reply. This field is populated when an error or failure occurs in asynchronous request processing.
- For information regarding WebSphere MQ programming, see WebSphere MQ Application Programming Reference and the WebSphere MQ Application Programming Guide.
- MQ MsgId
- The WebSphere MQ message identifier set by the service requester for use on all MQPUT commands in the queue server adapter and reply messages. This field is populated when an error or failure occurs in asynchronous request processing. For information regarding WebSphere MQ programming, see WebSphere MQ Application Programming Reference and the WebSphere MQ Application Programming Guide.
- MQ CorrelId
- The WebSphere MQ correlation identifier set by the service requester. This field is populated when an error or failure occurs during asynchronous request processing.
- For information regarding WebSphere MQ programming, see WebSphere MQ Application Programming Reference and the WebSphere MQ Application Programming Guide.
- Error detail
- Brief description of the error that has occurred. This description is followed by specific error details that apply to the particular type of message that has been issued.