Instrumentation facilities messages (CSQW...)

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.

Dump formatting continues.

If you want summary dump records to be used, do not specify the 'SUMDUMP=NO' operand on the MQ DUMP DISPLAY MAIN MENU (if you are using the dump display panels), or in the CSQWDMP verbexit (if you are using line mode IPCS).

The dump formatting exit is using MQ summary dump record information to format its control blocks.

Dump formatting continues.

If you do not want 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 you are using the dump display panels), or in the CSQWDMP verbexit (if you are using line mode IPCS). Both operands are required.

An invalid operand was specified on the MQ DUMP DISPLAY MAIN MENU (if you are using the dump display panels), or in the CSQWDMP verbexit (if you are using line mode IPCS).

The dump formatting exit terminates.

Correct the operand specified by message CSQW007E.

The dump formatting exit could not locate its anchor block.

The dump formatting exit terminates.

Specify 'SUBSYS=subsystem name', and 'SUMDUMP=NO' on the MQ DUMP DISPLAY MAIN MENU (if you are using the dump display panels), or in the CSQWDMP verbexit if you are using line mode IPCS.

The specified operand was not a valid dump formatting operand.

The dump formatting exit terminates.

Check the dump formatting operands.

An error was encountered while trying to retrieve the SCOM.

The dump formatting exit terminates.

If 'SUMDUMP=NO' was specified on the MQ DUMP DISPLAY MAIN MENU (if you are using the dump display panels), or in the CSQWDMP verbexit (if you are using line mode IPCS) omit it and resubmit the request. Otherwise, specify this operand, and resubmit the request.

The MQ control blocks for the address space specified could not be located.

Formatting continues of any other requested dump segment.

Check the ASID specified. The ASID must be specified in hexadecimal.

The MQ trace table could not be located.

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

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.

The dump formatting exit could not obtain a large enough work buffer to process the summary dump records.

The dump formatting exit terminates.

Rerun the job, specifying a larger TSO region size (or a larger region size if running in batch).

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.

The dump formatting exit terminates.

Specify 'SUBSYS=xxxx' to identify which address space to format information for.

Expected data could not be found in the summary dump. This message is issued for information only. Dump formatting continues.

Formatting is attempted using information found from the full dump instead of the summary dump.

In a search through the SSCVT chain, a match of the subsystem name in the SSCVTs and the subsystem name specified was not found.

Formatting for the named subsystem is not done.

Specify the subsystem name correctly.

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.

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

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.

This condition is usually caused by the MQ control block formatter looping. The stack array is depleted and can no longer accommodate control blocks.

Dump formatting is terminated.

Contact your IBM® support center.

The 'SUMDUMP=NO' option was specified, but either the 'SUBSYS=' operand is missing, or it was incorrectly specified.

Dump formatting is terminated.

Specify the name of the subsystem in the 'SUBSYS=' operand, and resubmit the request.

A key control block could not be located in the dump.

Dump formatting is terminated.

Check that the 'SUBSYS=' operand was correctly specified, and resubmit the request.

Trace table formatting has been attempted, but no trace table existed at the time of the dump.

Dump formatting continues with any other control blocks that were to be formatted.

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.

Formatting of the trace table continues.

This identifies the start of the formatted trace table.

Trace table formatting follows.

A nonzero return code was returned from the storage access routine when accessing the trace table.

Trace table formatting is bypassed.

This messages provides descriptive information about the type of formatting being produced.

Dump formatting continues.

This messages provides descriptive information about the type of formatting being produced.

Dump formatting continues.

This messages provides descriptive information about the type of formatting being produced.

Dump formatting continues.

This messages provides descriptive information about the type of formatting being produced.

Dump formatting continues.

A control block identifying the structure of MQ control blocks could not be found.

Control block formatting is terminated.

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 MQ, see Troubleshooting and support for information about reporting the problem.

A control block cannot be accessed from the dump.

Control block formatting is terminated.

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 MQ, see Troubleshooting and support for information about reporting the problem.

Formatting of MQ control blocks is beginning.

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.

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.

No MQ formatting is done for the specified task.

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.

The appropriate control blocks are formatted.

Examine the control blocks for relevant information.

The formatted blocks following this message are associated with the current task.

The appropriate control blocks are formatted.

Examine the control blocks for relevant information.

Formatting of MQ control blocks is completed.

The dump formatting exit has completed its processing for this dump data set.

The MQ trace table anchor block could not be located.

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

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 MQ, see Troubleshooting and support for information about reporting the problem.

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.

Dump formatting is terminated.

Rerun the formatting specifying the parameter the subsystem name (using 'SUBSYS=').

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.

Dump formatting continues, but from the physical start of the trace table, not the oldest record.

If the time of day values are meaningful, and in sequence, scan down the formatted trace to find the latest trace record written.

Dump processing continues.

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).

This message is generated by the recovery routine of the SDUMP dump data gathering service when an error is encountered during dump processing.

Processing of the SUMLSTA user storage areas is terminated, an SVC dump is requested, and control is returned to RTM.

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.

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 .

Dump formatting continues.

The SDWA obtained from the SYS1.DUMP data set contained no diagnostic information in the VRA.

VRA report generation is bypassed, dump format processing continues.

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.

No VRA is produced, and dump formatting continues.

The dump formatter has completed processing of the VRA diagnostic report.

Dump formatting continues.

A summary of information about connected jobs follows.

Job summary information follows.

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.

Save area trace format processing continues for the agent EB in error, and all associated agent EBs.

This message indicates that the MQ formatted save area trace report (CSQW060I) is complete.

Dump formatting continues.

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).

Save area trace format processing is terminated for the current agent EB, and all prior EBs.

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

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.

The dump formatter was unable to format a control block because the storage could not be found.

Dump formatting continues.

During the formatting of a control block, a mismatch was found between the expected length and the value determined from the dump.

You might find this message helpful when solving a more serious problem because it might indicate that a control block has been corrupted.

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.

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.

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.

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.

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.

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.

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.

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.

This shows the title of the dump.

This message is inserted into the formatted MQ trace to indicate that the control block was traced on entry to MQ.

This message is inserted into the formatted MQ trace to indicate that the control block was traced on exit from MQ.

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.

This message is inserted into the formatted MQ trace when a control block has exceeded a 256 byte length limit.

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.

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.

Queue manager startup processing continues.

If you expect to experience problems, stop your queue manager, resolve the problem, and restart. If you do not anticipate that this error will cause problems, you can stop and restart the queue manager at a convenient time.

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.

Queue manager initialization continues.

Start the trace with the START TRACE command after queue manager initialization is complete.

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.

Queue manager initialization continues.

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.

A trace command has been entered, but the specified destination value is not valid for the trace type requested.

Processing for the TRACE command is terminated.

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.

A trace command has been entered, but the specified class value is not valid for the trace type requested.

Processing for the TRACE command is terminated.

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.

A trace command has been entered, but keyword is not valid for the trace type specified.

Processing for the TRACE command is terminated.

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.

dest destination has resumed acceptance of trace data after an error.

Data recording is resumed.

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.

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.

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

Multiple values were specified for both of the named keywords. At most one of these keywords is allowed multiple values on a single command.

Processing for the command is terminated.

Reenter a valid command. See MQSC commands for additional information.

The type trace cannot be started because the active trace table has reached the maximum number of active traces allowed.

Processing for the command is terminated.

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.

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.

Processing for the request continues. If the specified trace applies to the channel initiator, a request will be queued: see message CSQW152I.

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.

Processing for the request continues. If the specified trace applies to the channel initiator, a request will be queued: see message CSQW152I.

The trace number tno has been altered.

Processing for the request continues.

Trace processing continues, although data is lost.

Investigate the GTF or SMF facility to determine why data is not being accepted. You 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.

type trace was already active with trace number tno.

Processing for the trace already in progress will continue.

Processing for the command continues.

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

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.

Processing of the trace command is terminated before any trace functions are performed.

See the TRACE commands in MQSC commands and Line trace for more information.

TRACE(CHINIT) was specified, but the channel initiator is not active.

The command is not actioned.

Issue the START CHINIT command to start the channel initiator, and reissue the command.

The command specifies RMID 231, which was formerly used for channel initiator traces, but is now obsolete. For channel initiator traces, specify TRACE(CHINIT).

The command is not actioned.

Issue the command correctly. If both queue manager and channel initiator tracing is required, issue two separate commands.

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.

A request has been queued for the channel initiator. Further messages will be produced when the command has been completed.

There is insufficient storage in ECSA for a new global trace table as requested by a previous SET SYSTEM TRACTBL command.

Processing continues using the existing global trace table.

Investigate how ECSA storage is being used. Issue a further SET SYSTEM TRACTBL command to set the trace table size to an acceptable value.

The z/OS STORAGE macro was issued to obtain storage for the trace formatter. The request failed with return code rc.

Formatting of control blocks stops, and a hexadecimal dump of the record is produced. (This might be only part of the logical record.)

See the MVS Assembler Services Reference manual for information about rc. You can usually resolve this problem by increasing the size of your TSO or batch region. When the problem has been solved, retry the operation.

The z/OS STORAGE macro was issued to release some storage. The request failed with return code rc.

Formatting of control blocks stops, and a hexadecimal dump of the record is produced. (This might be only part of the logical record.)

Try processing the dump again. If the problem persists, note the value of rc, and contact your IBM support center.

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.

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.)

Select a slightly earlier start time for your 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.

An internal error has occurred.

A hexadecimal dump of the record is produced, and formatting continues with the next record. This message might be followed by message CSQW202E.

Try processing the dump again. If the problem persists, contact your IBM support center.

An internal error has occurred.

This, and all subsequent records are displayed in hexadecimal. IBM MQ trace formatting is suppressed.

Try processing the dump again. If the problem persists, contact your IBM support center.

This message identifies this record as an accounting record.

A hexadecimal dump of the record is produced, and formatting continues with the next record.

The MQ trace formatter has detected a self-defining section of zero length.

Formatting continues with the next self-defining section.

The MQ trace formatter has been passed an invalid address. The address is in low storage.

Formatting of the record is suppressed. Formatting continues with the next record.

The MQ trace formatter detected a data item of zero length.

Formatting continues with the next data item.

The format of a record was different from the format expected by the IBM MQ trace formatter.

A hexadecimal dump is produced, and formatting continues with the next record.

Try processing the dump again. If the problem persists, contact your IBM support center.

A z/OS ENFREQ request failed. rc is the return code (in hexadecimal) from the request.

Processing continues.

See the z/OS MVS Authorized Assembler Services Reference manual for information about the return codes from the ENFREQ LISTEN and ENFREQ DELETE requests.