Instrumentation facilities messages (CSQW...)
CSQW001IASYNCHRONOUSLY GATHERED DATA IS BEING FORMATTEDExplanation: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 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).
CSQW002ISUMMARY DUMP RECORDS ARE BEING FORMATTEDExplanation: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 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.
CSQW004EONE OR MORE OPERANDS ARE NOT VALID. FORMATTING TERMINATEDExplanation: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).
System Action:The dump formatting exit terminates.
System Programmer Response:Correct the operand specified by message CSQW007E.
CSQW006ETHE ERLY BLOCK CANNOT BE ACCESSED OR IT IS INVALIDExplanation: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 you are using the dump display panels), or in the CSQWDMP verbexit if you are using line mode IPCS.
CSQW007EOPERAND IS NOT VALID: xxxxExplanation: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.
CSQW008ETHE SCOM CANNOT BE ACCESSED OR IT IS INVALIDExplanation: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 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.
CSQW009ETHE ADDRESS SPACE REQUESTED IS NOT AVAILABLEExplanation: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.
CSQW010ETHE TRACE RMFT CANNOT BE ACCESSED OR IT IS INVALIDExplanation: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.
CSQW011IA LARGER REGION SIZE IS REQUIRED FOR THIS JOBExplanation: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).
CSQW013IDMPW NOT FOUND IN SUMMARY DUMPExplanation: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.
CSQW014IREQUIRED SUMMARY DUMP RECORDS ARE NOT IN THIS DUMP. WILL ATTEMPT TO FORMAT FROM NON-SUMMARY DUMPExplanation: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.
CSQW015ISSCVT NOT LOCATED, CHECK THE SUBSYSTEM NAME SPECIFIEDExplanation: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.
CSQW016ITHE RMVT CANNOT BE ACCESSED OR IT IS INVALIDExplanation: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.
CSQW017EMAXIMUM STACK LEVEL EXCEEDEDExplanation: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 your IBM support center.
CSQW018ISUBSYS= SPECIFIED INCORRECTLY OR MISSING. REQUIRED IF SUMDUMP=NO SPECIFIEDExplanation: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.
CSQW020IUNSUCCESSFUL SEARCH FOR THE ERLY CONTROL BLOCKExplanation: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.
CSQW022ITHE RESIDENT TRACE WAS NOT ACTIVE AT THE TIME OF DUMPExplanation: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.
CSQW023ITHE TRACE TABLE ENTRY IS OUT OF SEQUENCE OR OVERLAIDExplanation: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.
CSQW024ITRACE TABLEExplanation:This identifies the start of the formatted trace table.
System Action:Trace table formatting follows.
CSQW025IERROR ACCESSING THE TRACE TABLEExplanation:A nonzero return code was returned from the storage access routine when accessing the trace table.
System Action:Trace table formatting is bypassed.
CSQW026ICONTROL BLOCK SUMMARY (ALL ADDRESS SPACES)Explanation:This messages provides descriptive information about the type of formatting being produced.
System Action:Dump formatting continues.
CSQW027ICONTROL BLOCK SUMMARY (SINGLE ADDRESS SPACE)Explanation:This messages provides descriptive information about the type of formatting being produced.
System Action:Dump formatting continues.
CSQW028ICONTROL BLOCK SUMMARY (LONG FORM GLOBAL)Explanation:This messages provides descriptive information about the type of formatting being produced.
System Action:Dump formatting continues.
CSQW029ICONTROL BLOCK SUMMARY (SHORT FORM GLOBAL)Explanation:This messages provides descriptive information about the type of formatting being produced.
System Action:Dump formatting continues.
CSQW030EDUMP ACCESS ERROR ACCESSING THE CONTROL BLOCK STRUCTURE TABLE IN THE DUMPExplanation: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 MQ, see the WebSphere MQ for z/OS Problem Determination Guide for information about reporting the problem.
CSQW032EERROR ACCESSING ANCHOR CONTROL BLOCKExplanation: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 MQ, see the WebSphere MQ for z/OS Problem Determination Guide for information about reporting the problem.
CSQW033IBEGINNING FORMATTINGExplanation:Formatting of MQ control blocks is beginning.
CSQW034ITRACE TABLE AND GLOBAL BLOCKS ALREADY FORMATTEDExplanation: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.
CSQW035IWARNING - NO TASK RELATED CONTROL BLOCKS FOR THIS TASKExplanation: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.
CSQW036ICONTROL BLOCKS FOR TASKS ASSOCIATED WITH THE ABOVE RECOVERY COORDINATOR TASKExplanation: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.
CSQW037ITASK RELATED CONTROL BLOCKS FOR THIS TASKExplanation: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.
CSQW038IEND OF FORMATTINGExplanation:Formatting of MQ control blocks is completed.
CSQW039IFORMATTING COMPLETE FOR THIS DUMPExplanation:The dump formatting exit has completed its processing for this dump data set.
CSQW041ETHE TAB CANNOT BE ACCESSED OR IT IS INVALIDExplanation: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 MQ, see the WebSphere MQ for z/OS Problem Determination Guide for information about reporting the problem.
Problem Determination:You might find the following items useful in resolving the problem:
- Console output
- Dynamic dump
- Printout of SYS1.LOGREC
CSQW042EREQUIRED SUMMARY DUMP RECORDS ARE NOT IN THIS DUMP. RERUN SPECIFYING SUBSYS= PARAMETERExplanation: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=').
CSQW049IOLDEST SLOT ADDRESS INVALID, FORMATTING TRACE TABLE FROM FIRST ENTRYExplanation: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.
Problem Determination:This error occurs when the trace control block has been overwritten, and could be a symptom of a larger problem.
CSQW050Issnm NO SDWA/LOGREC, ABN=comp-reason, U=userid, M=module, C=compid.vrm.comp-functionExplanation: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).
Problem Determination:In a recovery environment, functional recovery routines (FRRs) are guaranteed an SDWA by Recovery Termination Manager (RTM). Therefore, the recovery routine is most likely an ESTAE recovery routine. The primary reason for an SDWA not being provided to an ESTAE routine is due to insufficient storage available during recovery processing. The region sizes allocated to the function in error should be examined to ensure sufficient storage is available.
In a non-recovery environment, where there is no RTM, no SDWA is produced.
CSQW051EERROR DURING DUMP PROCESSINGExplanation: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.
CSQW053IVRA DIAGNOSTIC INFORMATION REPORTExplanation: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 the WebSphere MQ for z/OS Problem Determination Guide.
System Action:Dump formatting continues.
CSQW054INO VRA DATA RECORDED IN SDWAExplanation: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.
CSQW055IUNABLE TO LOCATE SDWAExplanation: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.
CSQW056IVRA DIAGNOSTIC REPORT COMPLETEExplanation:The dump formatter has completed processing of the VRA diagnostic report.
System Action:Dump formatting continues.
CSQW059ISUMMARY OF CONNECTED JOBSExplanation:A summary of information about connected jobs follows.
System Action:Job summary information follows.
CSQW060IBEGIN SAVE AREA TRACEExplanation: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.
CSQW061ISAVE AREA TRACE COMPLETEExplanation:This message indicates that the MQ formatted save area trace report (CSQW060I) is complete.
System Action:Dump formatting continues.
CSQW062IR6 (R6-contents) DOES NOT CONTAIN A VALID EB ADDRESSExplanation: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.
Problem Determination:Register 6 does not contain the current EB address or a prior EB address.
Refer to the abend reason and completion codes associated with the original error to determine the use of register 6 prior to the error.
CSQW063Ename (address) ASID (asid) NOT FOUND IN DUMPExplanation: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 utilizes 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.
Problem Determination:During z/OS RTM recovery processing, MQ attempts to include all control blocks (both MQ and z/OS), and the pertinent MQ save areas in the dump data set, regardless of the type of error. Control blocks and save areas associated with the MQ address space at time of error will be included in the dump data set.
CSQW064I*ERROR* BLOCK NOT FOUND IN DUMPExplanation:The dump formatter was unable to format a control block because the storage could not be found.
System Action:Dump formatting continues.
Problem Determination:This problem can occur for the following reasons: