Instrumentation facilities messages (CSQW...)

CSQW001I: ASYNCHRONOUSLY GATHERED DATA IS BEING FORMATTED
Explanation: The dump formatting exit is not using summary dump records for formatting. The formatted control blocks might not contain the same values as they did at the time of the error.
System action: Dump formatting continues.
System programmer response: If we want summary dump records to be used, do not specify the 'SUMDUMP=NO' operand on the MQ DUMP DISPLAY MAIN MENU (if we are using the dump display panels), or in the CSQWDMP verbexit (if we are using line mode IPCS).

CSQW002I: SUMMARY DUMP RECORDS ARE BEING FORMATTED
Explanation: The dump formatting exit is using MQ summary dump record information to format its control blocks.
System action: Dump formatting continues.
System programmer response: If we do not want IBM MQ summary dump records to be used in formatting, specify the 'SUMDUMP=NO' and 'SUBSYS=subsystem name' on the MQ DUMP DISPLAY MAIN MENU (if we are using the dump display panels), or in the CSQWDMP verbexit (if we are using line mode IPCS). Both operands are required.

CSQW004E: ONE OR MORE OPERANDS ARE NOT VALID. FORMATTING TERMINATED
Explanation: An invalid operand was specified on the MQ DUMP DISPLAY MAIN MENU (if we are using the dump display panels), or in the CSQWDMP verbexit (if we are using line mode IPCS).
System action: The dump formatting exit terminates.
System programmer response: Correct the operand specified by message CSQW007E.

CSQW006E: THE ERLY BLOCK CANNOT BE ACCESSED OR IT IS INVALID
Explanation: The dump formatting exit could not locate its anchor block.
System action: The dump formatting exit terminates.
System programmer response: Specify 'SUBSYS=subsystem name', and 'SUMDUMP=NO' on the MQ DUMP DISPLAY MAIN MENU (if we are using the dump display panels), or in the CSQWDMP verbexit if we are using line mode IPCS.

CSQW007E: OPERAND IS NOT VALID: xxxx
Explanation: The specified operand was not a valid dump formatting operand.
System action: The dump formatting exit terminates.
System programmer response: Check the dump formatting operands.

CSQW008E: THE SCOM CANNOT BE ACCESSED OR IT IS INVALID
Explanation: An error was encountered while trying to retrieve the SCOM.
System action: The dump formatting exit terminates.
System programmer response: If 'SUMDUMP=NO' was specified on the MQ DUMP DISPLAY MAIN MENU (if we are using the dump display panels), or in the CSQWDMP verbexit (if we are using line mode IPCS) omit it and resubmit the request. Otherwise, specify this operand, and resubmit the request.

CSQW009E: THE ADDRESS SPACE REQUESTED IS NOT AVAILABLE
Explanation: The MQ control blocks for the address space specified could not be located.
System action: Formatting continues of any other requested dump segment.
System programmer response: Check the ASID specified. The ASID must be specified in hexadecimal.

CSQW010E

THE TRACE RMFT CANNOT BE ACCESSED OR IT IS INVALID

Explanation

The MQ trace table could not be located.

System action

Formatting of the MQ trace table is bypassed, and formatting continues of any other requested dump segment.

System programmer response

If 'SUMDUMP=NO' was specified try formatting the dump again using the summary dump because it could contain the information required to access this data.

If 'SUMDUMP=NO' was not specified, and the summary dump was used, try formatting the dump again specifying this option because the summary dump data could have been corrupted.

CSQW011I: A LARGER REGION SIZE IS REQUIRED FOR THIS JOB
Explanation: The dump formatting exit could not obtain a large enough work buffer to process the summary dump records.
System action: The dump formatting exit terminates.
System programmer response: Rerun the job, specifying a larger TSO region size (or a larger region size if running in batch).

CSQW013I: DMPW NOT FOUND IN SUMMARY DUMP
Explanation: The dump formatting exit was unable to locate the DMPW control block in the summary record portion of the dump data set. Because the DMPW provides the main anchor block for the dump formatter, processing is terminated.
System action: The dump formatting exit terminates.
System programmer response: Specify 'SUBSYS=xxxx' to identify which address space to format information for.

CSQW014I: REQUIRED SUMMARY DUMP RECORDS ARE NOT IN THIS DUMP. WILL ATTEMPT TO FORMAT FROM NON-SUMMARY DUMP
Explanation: Expected data could not be found in the summary dump. This message is issued for information only. Dump formatting continues.
System action: Formatting is attempted using information found from the full dump instead of the summary dump.

CSQW015I: SSCVT NOT LOCATED, CHECK THE SUBSYSTEM NAME SPECIFIED
Explanation: In a search through the SSCVT chain, a match of the subsystem name in the SSCVTs and the subsystem name specified was not found.
System action: Formatting for the named subsystem is not done.
System programmer response: Specify the subsystem name correctly.

CSQW016I

THE RMVT CANNOT BE ACCESSED OR IT IS INVALID

Explanation

The dump formatting exit could not locate the RMVT. The RMVT is required for formatting the MQ trace table and a number of other MQ control blocks.

System action

Formatting of the MQ trace table is bypassed, and formatting of other requested dump segments continues.

System programmer response

If 'SUMDUMP=NO' was specified try formatting the dump again using the summary dump because it could contain the information required to access this data.

If 'SUMDUMP=NO' was not specified, and the summary dump was used, try formatting the dump again specifying this option because the summary dump data could have been corrupted.

CSQW017E: MAXIMUM STACK LEVEL EXCEEDED
Explanation: This condition is usually caused by the MQ control block formatter looping. The stack array is depleted and can no longer accommodate control blocks.
System action: Dump formatting is terminated.
System programmer response: Contact the IBM support center.

CSQW018I: SUBSYS= SPECIFIED INCORRECTLY OR MISSING. REQUIRED IF SUMDUMP=NO SPECIFIED
Explanation: The 'SUMDUMP=NO' option was specified, but either the 'SUBSYS=' operand is missing, or it was incorrectly specified.
System action: Dump formatting is terminated.
System programmer response: Specify the name of the subsystem in the 'SUBSYS=' operand, and resubmit the request.

CSQW020I: UNSUCCESSFUL SEARCH FOR THE ERLY CONTROL BLOCK
Explanation: A key control block could not be located in the dump.
System action: Dump formatting is terminated.
System programmer response: Check that the 'SUBSYS=' operand was correctly specified, and resubmit the request.

CSQW022I: THE RESIDENT TRACE WAS NOT ACTIVE AT THE TIME OF DUMP
Explanation: Trace table formatting has been attempted, but no trace table existed at the time of the dump.
System action: Dump formatting continues with any other control blocks that were to be formatted.

CSQW023I: THE TRACE TABLE ENTRY IS OUT OF SEQUENCE OR OVERLAID
Explanation: A trace entry is overlaid by another trace entry of a different time stamp. This message is issued to flag an unrecognized trace entry. This error can occur if the dump is initiated by operator command, because the MQ address space continues to run while the dump is being taken.
System action: Formatting of the trace table continues.

CSQW024I: TRACE TABLE
Explanation: This identifies the start of the formatted trace table.
System action: Trace table formatting follows.

CSQW025I: ERROR ACCESSING THE TRACE TABLE
Explanation: A nonzero return code was returned from the storage access routine when accessing the trace table.
System action: Trace table formatting is bypassed.

CSQW026I: CONTROL BLOCK SUMMARY (ALL ADDRESS SPACES)
Explanation: This messages provides descriptive information about the type of formatting being produced.
System action: Dump formatting continues.

CSQW027I: CONTROL BLOCK SUMMARY (SINGLE ADDRESS SPACE)
Explanation: This messages provides descriptive information about the type of formatting being produced.
System action: Dump formatting continues.

CSQW028I: CONTROL BLOCK SUMMARY (LONG FORM GLOBAL)
Explanation: This messages provides descriptive information about the type of formatting being produced.
System action: Dump formatting continues.

CSQW029I: CONTROL BLOCK SUMMARY (SHORT FORM GLOBAL)
Explanation: This messages provides descriptive information about the type of formatting being produced.
System action: Dump formatting continues.

CSQW030E: DUMP ACCESS ERROR ACCESSING THE CONTROL BLOCK STRUCTURE TABLE IN THE DUMP
Explanation: A control block identifying the structure of MQ control blocks could not be found.
System action: Control block formatting is terminated.
System programmer response: Check the z/OS console to see if any messages were produced to indicate that there was a problem when the dump was taken. If you suspect an error in IBM MQ, see Troubleshooting and support for information about reporting the problem.

CSQW032E: ERROR ACCESSING ANCHOR CONTROL BLOCK
Explanation: A control block cannot be accessed from the dump.
System action: Control block formatting is terminated.
System programmer response: Check the z/OS console to see if any messages were produced to indicate that there was a problem when the dump was taken. If you suspect an error in IBM MQ, see Troubleshooting and support for information about reporting the problem.

CSQW033I: BEGINNING FORMATTING
Explanation: Formatting of MQ control blocks is beginning.

CSQW034I: TRACE TABLE AND GLOBAL BLOCKS ALREADY FORMATTED
Explanation: An indicative dump is being requested. The MQ trace table and the global blocks have already been formatted with first dump (full dump) for this abend dump (SNAP) invocation. These are, therefore, not formatted for this task.

CSQW035I: WARNING - NO TASK RELATED CONTROL BLOCKS FOR THIS TASK
Explanation: The task for which the dump is being requested is not identified to MQ. Task-related control blocks are not dumped. The MQ trace table and global blocks are dumped only if the SYSABEND DD statement is present and only if this is the first of the dumps (full dump) for this abend dump (SNAP) invocation.
System action: No MQ formatting is done for the specified task.

CSQW036I: CONTROL BLOCKS FOR TASKS ASSOCIATED WITH THE ABOVE RECOVERY COORDINATOR TASK
Explanation: The formatted blocks following this message are associated with tasks that have been identified to MQ with the 'recovery coordinator = no' option. These tasks might not have invoked SNAP, but they are associated with the task that did.
System action: The appropriate control blocks are formatted.
System programmer response: Examine the control blocks for relevant information.

CSQW037I: TASK RELATED CONTROL BLOCKS FOR THIS TASK
Explanation: The formatted blocks following this message are associated with the current task.
System action: The appropriate control blocks are formatted.
System programmer response: Examine the control blocks for relevant information.

CSQW038I: END OF FORMATTING
Explanation: Formatting of MQ control blocks is completed.

CSQW039I: FORMATTING COMPLETE FOR THIS DUMP
Explanation: The dump formatting exit has completed its processing for this dump data set.

CSQW041E

THE TAB CANNOT BE ACCESSED OR IT IS INVALID

Explanation

The MQ trace table anchor block could not be located.

System action

Formatting of the MQ trace table is bypassed, and formatting of any other requested dump segment continues.

System programmer response

If 'SUMDUMP=NO' was specified try formatting the dump again using the summary dump because it could contain the information required to access this data.

If 'SUMDUMP=NO' was not specified, and the summary dump was used, try formatting the dump again specifying this option because the summary dump data could have been corrupted.

Check the z/OS console to see if any messages were produced to indicate that there was a problem when the dump was taken. If you suspect an error in IBM MQ, see Troubleshooting and support for information about reporting the problem.

CSQW042E: REQUIRED SUMMARY DUMP RECORDS ARE NOT IN THIS DUMP. RERUN SPECIFYING SUBSYS= PARAMETER
Explanation: The summary dump records were not found in the dump. When this occurs the dump formatter needs the subsystem name to be able to identify which address space is to be formatted.
System action: Dump formatting is terminated.
System programmer response: Rerun the formatting specifying the parameter the subsystem name (using 'SUBSYS=').

CSQW049I: OLDEST SLOT ADDRESS INVALID, FORMATTING TRACE TABLE FROM FIRST ENTRY
Explanation: There are several pointers in the control block that defines the trace. One points to the start of the storage that contains the trace data, one to the end, and one to the next free record. The formatter has detected that the pointer to the next free record is outside the range indicated by the pointers to the start and end of the storage.
System action: Dump formatting continues, but from the physical start of the trace table, not the oldest record.
System programmer response: If the time of day values are meaningful, and in sequence, scan down the formatted trace to find the latest trace record written.

CSQW050I

ssnm NO SDWA/LOGREC, ABN=comp-reason, U=userid, M=module, C=compid.vrm.comp-function

Explanation

This message provides the default SVC dump title (SDUMP) associated with the SYS1.DUMP data set, when an SDWA was unavailable during recovery processing. The individual variable fields contain:

Field: Contents
ssnm: MQ subsystem name
ABN: The abend completion code, followed by the abend reason code
U: The user ID for the individual subsystem user
M: The function recovery routine responsible for the dump
C: The component-ID
vrm: The MQ version, release number, and modification level
comp-function: The component-ID function

System action

Dump processing continues.

System programmer response

Since the SDWA provides important diagnostic information to assist in problem determination, the recovery environment at time of error should be examined to determine why an SDWA was not provided for this ABEND.

In a non-recovery environment, there might be valid reasons for the lack of an SDWA (for example, the operator could have initiated the dump).

CSQW051E: ERROR DURING DUMP PROCESSING
Explanation: This message is generated by the recovery routine of the SDUMP dump data gathering service when an error is encountered during dump processing.
System action: Processing of the SUMLSTA user storage areas is terminated, an SVC dump is requested, and control is returned to RTM.
System programmer response: This error is documented in a SYS1.LOGREC record. This message can be issued because of an error in the invocation of SDUMP, or because of an error in SDUMP itself, or during control block examination and access.

CSQW053I

VRA DIAGNOSTIC INFORMATION REPORT

Explanation

The variable recording area (VRA) is part of the system diagnostic work area (SDWA) and contains MQ diagnostic information. The VRA is extracted and displayed in this report.

For information about this report, see Troubleshooting and support .

System action

Dump formatting continues.

CSQW054I: NO VRA DATA RECORDED IN SDWA
Explanation: The SDWA obtained from the SYS1.DUMP data set contained no diagnostic information in the VRA.
System action: VRA report generation is bypassed, dump format processing continues.

CSQW055I: UNABLE TO LOCATE SDWA
Explanation: The z/OS summary dump data access service routine (IEAVTFRD) was unable to locate the SDWA in the summary data portion of the SYS1.DUMP data set. SVC dumps only contain an SDWA if they are initiated by MQ. If the dump was initiated by any other means (such as the operator) the SDWA will not be present.
System action: No VRA is produced, and dump formatting continues.

CSQW056I: VRA DIAGNOSTIC REPORT COMPLETE
Explanation: The dump formatter has completed processing of the VRA diagnostic report.
System action: Dump formatting continues.

CSQW059I: SUMMARY OF CONNECTED JOBS
Explanation: A summary of information about connected jobs follows.
System action: Job summary information follows.

CSQW060I: BEGIN SAVE AREA TRACE
Explanation: This message identifies the start of the MQ register save area trace report which appears in the formatted section of an MQ SVC dump. This report is useful for problem determination because it contains the save areas for the agent execution block (EB) in error, and all associated agent EBs, traced from the point of error and displayed in order of invocation.
System action: Save area trace format processing continues for the agent EB in error, and all associated agent EBs.

CSQW061I: SAVE AREA TRACE COMPLETE
Explanation: This message indicates that the MQ formatted save area trace report (CSQW060I) is complete.
System action: Dump formatting continues.

CSQW062I: R6 (R6-contents) DOES NOT CONTAIN A VALID EB ADDRESS
Explanation: During dump format processing of the MQ formatted save area trace report (CSQW060I), register 6 (R6) did not contain the address of a valid agent execution block (EB).
System action: Save area trace format processing is terminated for the current agent EB, and all prior EBs.

CSQW063E

name (address) ASID (asid) NOT FOUND IN DUMP

Explanation

During processing of the save area trace report (CSQW060I), a control block or save area was not found in the dump data set.

Because the dump formatter uses the MQ and z/OS control blocks defined under the name field of this message to locate individual register save areas, subsequent save areas located using the named control block or save area will not be displayed in the report.

name

Identifies the name of the control block or save area that was not found in the dump data set:

SA: Indicates a save area
ASCE: MQ address space control element
EB: MQ execution block
TCB: z/OS task control block
RB: z/OS request block
XSB: z/OS extended status block
PSA: z/OS prefix save area
SDWA: z/OS system diagnostic work area
STSV: z/OS SRB status save area
STKE: z/OS cross memory stack element

address

The address of the named control block or save area.

asid

The address space identifier associated with the control block or save area.

Due to the execution structures and environmental restrictions of selected MQ and z/OS control structures, some control blocks and save areas associated with these execution environments will not be included in the dump data set.

System action

Register save area trace format processing for the current save area chains is terminated. Subsequent save area processing will vary depending on the specific control block or save area that was available, and the MQ agent execution environments at the time of the error.

CSQW064I: *ERROR* BLOCK NOT FOUND IN DUMP
Explanation: The dump formatter was unable to format a control block because the storage could not be found.
System action: Dump formatting continues.

CSQW065I: *ERROR* BLOCK LENGTH INCORRECT
Explanation: During the formatting of a control block, a mismatch was found between the expected length and the value determined from the dump.
System programmer response: We might find this message helpful when solving a more serious problem because it might indicate that a control block has been corrupted.

CSQW066I: *ERROR* BLOCK ID INCORRECT
Explanation: Each control block type has a unique identifier for verification. During the formatting of the control block, a mismatch occurred between the value expected and the value found in the control block in the dump.
System programmer response: This message could indicate that storage has been overlaid, and you might find it helpful when solving a more serious problem because it might indicate that a control block has been corrupted.

CSQW067I: *ERROR* BLOCK CHAINED FROM THIS BLOCK NOT FOUND IN DUMP
Explanation: Control blocks can contain pointers to other control blocks. A control block pointed to by the current control block could not be found in the dump.
System programmer response: This message could indicate that storage has been overlaid, and you might find it helpful when solving a more serious problem. The control block pointed to will have error message CSQW064I associated with it.

CSQW068I: *ERROR* BLOCK CHAINED FROM THIS BLOCK HAS INCORRECT ID
Explanation: Each control block type has a unique identifier for verification. During the formatting of a control block pointed to by the current control block, a mismatch occurred between the value expected and the value found in the control block in the dump.
System programmer response: This message could indicate that storage has been overlaid, and you might find it helpful when solving a more serious problem because it might indicate that a control block has been corrupted. The control block in error has error message CSQW066I associated with it.

CSQW069I: *ERROR* BLOCK EYECATCHER INCORRECT
Explanation: Each control block type has a unique eyecatcher for verification. During the formatting of the control block, a mismatch occurred between the value expected and the value found in the control block in the dump.
System programmer response: This message could indicate that storage has been overlaid, and you might find it helpful when solving a more serious problem because it might indicate that a control block has been corrupted.

CSQW070I: DUMP TITLE dump-title
Explanation: This shows the title of the dump.

CSQW072I: ENTRY: MQ user parameter trace
Explanation: This message is inserted into the formatted MQ trace to indicate that the control block was traced on entry to MQ.

CSQW073I: EXIT: MQ user parameter trace
Explanation: This message is inserted into the formatted MQ trace to indicate that the control block was traced on exit from MQ.

CSQW074I: ERROR: MQ user parameter trace
Explanation: This message is inserted into the formatted MQ trace to indicate that the control block was traced because it was determined to be in error.

CSQW075I: WARNING - data was truncated at 256 bytes
Explanation: This message is inserted into the formatted MQ trace when a control block has exceeded a 256 byte length limit.

CSQW076I: Return code was mqrc
Explanation: This message is inserted into the formatted MQ trace when an error has been detected. mqrc is the return code. Refer to API completion and reason codes for information about this code.

CSQW105E: ERROR DURING LOAD OR VALIDATION OF A CONTROL BLOCK STRUCTURE TABLE MODULE
Explanation: The MQ dump formatting facility cannot be used to format control blocks. An error occurred during the startup process while attempting to LOAD one of the Control Block Structures Table modules (CSQWDST1, CSQWDST2, CSQWDST3, and CSQWDST4) from the MQ program library.
System action: Queue manager startup processing continues.
System programmer response: If you expect to experience problems, stop your queue manager, resolve the problem, and restart. If we do not anticipate that this error will cause problems, we can stop and restart the queue manager at a convenient time.

CSQW108E: UNABLE TO AUTOMATICALLY START 'type' TRACE
Explanation: System parameters indicated that an MQ trace should be started automatically during queue manager initialization, but the queue manager was unable to start the trace.
System action: Queue manager initialization continues.
System programmer response: Start the trace with the START TRACE command after queue manager initialization is complete.

CSQW109E: TRACE INITIALIZATION PARAMETERS UNAVAILABLE, DEFAULTS USED FOR 'type' TRACE
Explanation: The trace function was unable to access the trace initialization parameters defined by the CSQ6SYSP macro. Default values as defined by that macro are assumed for trace parameters.
System action: Queue manager initialization continues.
System programmer response: Determine if the system parameter load module (the default version is called CSQZPARM) is missing or inaccessible. Trace can be started with the START TRACE command.

CSQW120E: DEST VALUE IS INVALID FOR 'type' TRACE
Explanation: A trace command has been entered, but the specified destination value is not valid for the trace type requested.
System action: Processing for the TRACE command is terminated.
System programmer response: If a START TRACE command was entered, specify a valid destination for the trace. Otherwise, a DISPLAY TRACE command can be issued to determine what traces are currently active. See MQSC commands for information about valid destinations.

CSQW121E: CLASS VALUE IS INVALID FOR 'type' TRACE
Explanation: A trace command has been entered, but the specified class value is not valid for the trace type requested.
System action: Processing for the TRACE command is terminated.
System programmer response: If a START TRACE command was entered, specify a valid class for the trace. Otherwise, a DISPLAY TRACE command can be issued to determine what options are currently active. See MQSC commands for information about valid classes.

CSQW122E: 'keyword' IS NOT VALID FOR 'type' TRACE
Explanation: A trace command has been entered, but keyword is not valid for the trace type specified.
System action: Processing for the TRACE command is terminated.
System programmer response: Either the named keyword must be omitted from the command, or a different type of trace must be specified. See MQSC commands for information about valid combinations of keywords and trace types.

CSQW123I: csect-name TRACE RECORDING HAS BEEN RESUMED ON dest
Explanation: dest destination has resumed acceptance of trace data after an error.
System action: Data recording is resumed.

CSQW124E

csect-name 'type' TRACE TERMINATED RC=code RMID=nn

Explanation

During processing type trace, processing ended due to an error. A trace type of blank indicates all tracing has stopped. RMID, displayed in decimal, identifies the resource manager. For information on IBM MQ RMIDs, see the TRACE commands in MQSC commands.

code, displayed in hexadecimal, specifies the return, reason, or abend code associated with the action. Refer to IBM MQ for z/OS codes for information about these codes.

Further collection of the named trace is stopped. If it is necessary to resume collection of the trace, a START TRACE command can be issued. However if another error is experienced, the problem should be resolved before starting the trace collection again.

System action

Processing for the named trace type is stopped. The message is not externalized by the functional recovery routine, but is output whenever an IFC event is driven at a later time. A trace type of blank indicates all tracing has stopped.

System programmer response

Investigate the reasons for the error. If necessary to collect the named trace, issue a START TRACE command to resume processing.

CSQW125E: MULTIPLE VALUES NOT ALLOWED FOR keyword AND keyword
Explanation: Multiple values were specified for both of the named keywords. At most one of these keywords is allowed multiple values on a single command.
System action: Processing for the command is terminated.
System programmer response: Reenter a valid command. See MQSC commands for additional information.

CSQW126E: 'type' TRACE NOT ALLOWED, ACTIVE TRACE TABLE FULL
Explanation: The type trace cannot be started because the active trace table has reached the maximum number of active traces allowed.
System action: Processing for the command is terminated.
System programmer response: Use the DISPLAY TRACE command to see if an active trace could be stopped. An active trace must be stopped before any other start trace command will be processed.

CSQW127I

CURRENT TRACE ACTIVITY IS -

Explanation

This message is issued in response to the DISPLAY TRACE command. For each trace that is active, the message indicates the trace number, the type of trace, the class(es) within type, the destination(s) for the trace entries, the user ID, and the RMID(s), as follows:

  TNO TYPE CLASS DEST USERID RMID  tno type class dest userid rmid ⋮  END OF TRACE REPORT

The trace number tno can be:

01-03: A trace started automatically when the queue manager started, or a trace started by a START TRACE command.
04-32: A trace started by a START TRACE command.
00: The global trace started automatically when the channel initiator started.

Notes:

For TRACE(S) CLASS(4) (channel initiator statistics), the traces will only be gathered when the channel initiator is active and message CSQX128I has been output.
For TRACE(A) CLASS(4) (channel accounting), the traces will only be gathered when the channel initiator is active and message CSQX126I has been output.

CSQW130I: 'type' TRACE STARTED, ASSIGNED TRACE NUMBER tno
Explanation: In response to a command, or automatically during queue manager initialization, a type trace has been started and assigned the trace number tno. Multiple messages are possible when the start command specifies multiple user identifiers.
System action: Processing for the request continues. If the specified trace applies to the channel initiator, a request will be queued: see message CSQW152I.

CSQW131I: STOP TRACE SUCCESSFUL FOR TRACE NUMBER(S) tno,...
Explanation: In response to a command, the trace number(s), tno,..., have been stopped. Up to five trace numbers can be listed. If more than five traces have been stopped, another CSQW131I message is sent.
System action: Processing for the request continues. If the specified trace applies to the channel initiator, a request will be queued: see message CSQW152I.

CSQW132I: ALTER TRACE SUCCESSFUL FOR TRACE NUMBER tno
Explanation: The trace number tno has been altered.
System action: Processing for the request continues.

CSQW133E

csect-name TRACE DATA LOST, dest NOT ACCESSIBLE RC=code

Explanation

The destination specified stopped accepting trace data during a trace. Some external condition caused the data rejection. The reason for the error is defined by the return code (RC). The value of code can be:

The hexadecimal return code from SMF. See the MVS™ System Management Facilities (SMF) manual for the specific value.
The hexadecimal return code from the GTF request
The hexadecimal return code from the SRV request

System action

Trace processing continues, although data is lost.

System programmer response

Investigate the GTF or SMF facility to determine why data is not being accepted. We can issue a START TRACE command to record the data at another destination. The DISPLAY TRACE command shows what types of data were recorded at the specified destination.

See the MVS System Management Facilities (SMF) manual for an explanation of the return code value.

CSQW135I: 'type' TRACE ALREADY ACTIVE, TRACE NUMBER tno
Explanation: type trace was already active with trace number tno.
System action: Processing for the trace already in progress will continue.

CSQW137I

SPECIFIED TRACE NOT ACTIVE

Explanation

Either:

A command requested action for a specific trace, but that trace could not be found in the active trace table.
A command requested action for all traces, but there are no traces active.

System action

Processing for the command continues.

System programmer response

Issue an unqualified DISPLAY TRACE command (that is, DISPLAY TRACE(*) without any other keywords) to determine all the active trace entries.

CSQW138E: IFCID ifcid-number IS INVALID
Explanation: The specified IFCID number is outside the range of valid IFCID numbers or is an IFCID number which is not allowed on a trace command.
System action: Processing of the trace command is terminated before any trace functions are performed.
System programmer response: See the TRACE commands in MQSC commands and Line trace for more information.

CSQW144E: CHANNEL INITIATOR NOT ACTIVE
Explanation: TRACE(CHINIT) was specified, but the channel initiator is not active.
System action: The command is not actioned.
System programmer response: Issue the START CHINIT command to start the channel initiator, and reissue the command.

CSQW149E: RMID 231 IS OBSOLETE - USE TRACE(CHINIT)
Explanation: The command specifies RMID 231, which was formerly used for channel initiator traces, but is now obsolete. For channel initiator traces, specify TRACE(CHINIT).
System action: The command is not actioned.
System programmer response: Issue the command correctly. If both queue manager and channel initiator tracing is required, issue two separate commands.

CSQW152I: TRACE REQUEST FOR CHANNEL INITIATOR QUEUED
Explanation: Initial processing for a trace command has completed successfully. The command requires further action by the channel initiator, for which a request has been queued.
System action: A request has been queued for the channel initiator. Further messages will be produced when the command has been completed.

CSQW153E: csect-name STORAGE NOT AVAILABLE FOR NEW TRACE TABLE
Explanation: There is insufficient storage in ECSA for a new global trace table as requested by a previous SET SYSTEM TRACTBL command.
System action: Processing continues using the existing global trace table.
System programmer response: Investigate how ECSA storage is being used. Issue a further SET SYSTEM TRACTBL command to set the trace table size to an acceptable value.

CSQW200E: Error during STORAGE OBTAIN macro. Return code= rc
Explanation: The z/OS STORAGE macro was issued to obtain storage for the trace formatter. The request failed with return code rc.
System action: Formatting of control blocks stops, and a hexadecimal dump of the record is produced. (This might be only part of the logical record.)
System programmer response: See the MVS Assembler Services Reference manual for information about rc. We can usually resolve this problem by increasing the size of our TSO or batch region. When the problem has been solved, retry the operation.

CSQW201E: Error during STORAGE RELEASE macro. Return code= rc
Explanation: The z/OS STORAGE macro was issued to release some storage. The request failed with return code rc.
System action: Formatting of control blocks stops, and a hexadecimal dump of the record is produced. (This might be only part of the logical record.)
System programmer response: Try processing the dump again. If the problem persists, note the value of rc, and contact the IBM support center.

CSQW202E

Incomplete trace record detected

Explanation

A long trace record has been segmented, and the start record for the record currently being processed has not been processed.

This usually occurs when records within a time range have been selected for processing. The record with the start of segment flag is probably before the start of the selected time interval. This can also occur if the Generalized Trace Facility (GTF) is unable to write all records to the GTF data set.

System action

A hexadecimal dump of the record is produced, and formatting continues with the next record. (You will receive this message for each subsequent part of this logical record.)

System programmer response

Select a slightly earlier start time for the time interval (one tenth of a second for example) and retry the operation. If this is not successful, it is possible that your trace table has wrapped, and the start record has been overwritten.

CSQW204E: Internal error
Explanation: An internal error has occurred.
System action: A hexadecimal dump of the record is produced, and formatting continues with the next record. This message might be followed by message CSQW202E.
System programmer response: Try processing the dump again. If the problem persists, contact the IBM support center.

CSQW205E: Internal error
Explanation: An internal error has occurred.
System action: This, and all subsequent records are displayed in hexadecimal. IBM MQ trace formatting is suppressed.
System programmer response: Try processing the dump again. If the problem persists, contact the IBM support center.

CSQW206I: Accounting record
Explanation: This message identifies this record as an accounting record.
System action: A hexadecimal dump of the record is produced, and formatting continues with the next record.

CSQW207I: A Null Self Defining section was detected
Explanation: The MQ trace formatter has detected a self-defining section of zero length.
System action: Formatting continues with the next self-defining section.

CSQW208E: Invalid address detected
Explanation: The MQ trace formatter has been passed an invalid address. The address is in low storage.
System action: Formatting of the record is suppressed. Formatting continues with the next record.

CSQW209I: A null length data item was detected
Explanation: The MQ trace formatter detected a data item of zero length.
System action: Formatting continues with the next data item.

CSQW210E: Invalid record detected
Explanation: The format of a record was different from the format expected by the IBM MQ trace formatter.
System action: A hexadecimal dump is produced, and formatting continues with the next record.
System programmer response: Try processing the dump again. If the problem persists, contact your z/OS support center.

CSQW701E: csect-name ENFREQ request failed, RC=rc
Explanation: A z/OS ENFREQ request failed. rc is the return code (in hexadecimal) from the request.
System action: Processing continues.
System programmer response: See the MVS Authorized Assembler Services Reference manual for information about the return codes from the ENFREQ LISTEN and ENFREQ DELETE requests.

Parent topic: Messages for IBM MQ for z/OS