processing a dump, formatting a dump, format, selecting, selecting a dump, using the CSQWDMP statement, CSQWDMP statement, SUBSYS= parameter, resource manager formatting keywords, SUMDUMP= parameter, VERBEXITs, IPCS subcommands, formatting, channel initiator dump, IPCS VERBEXIT CSQXDPRD keywords, Coupling Facility structure dump" /> Use line mode IPCS

 

Using line mode IPCS

To format the dump using line mode IPCS commands, select the dump required by issuing the command: 

SETDEF DSN('SYS1.DUMPxx')

(where

SYS1.DUMPxx is the name of the data set containing the dump). We can then use IPCS subcommands to display data from the dump.

 

Formatting a WebSphere MQ for z/OS dump

The IPCS VERBEXIT CSQWDMP invokes the WebSphere MQ for z/OS dump formatting program (CSQWDPRD), and enables you to format an SVC dump to display WebSphere MQ data. We can restrict the amount of data that is displayed by specifying parameters.

See page Formatting a Coupling Facility structure dump for details on formatting a Coupling Facility list structure.

Note:
This section describes the parameters required to extract the necessary data. Separate operands by commas, not blanks. A blank that follows any operand in the control statement terminates the operand list, and any subsequent operands are ignored. Table 6 explains each keyword that we can specify in the control statement for formatting dumps.
Table 6. Keywords for the WebSphere MQ for z/OS dump formatting control statement
Keyword Description
SUBSYS=aaaa Use this keyword if the summary dump portion is not available, or not to be used, to give the name of the subsystem to format information for. aaaa is a 1 through 4-character subsystem name.
ALL (default) All control blocks and the trace table.
AA Data is displayed for all WebSphere MQ for z/OS control blocks in all address spaces.
DIAG=Y Print diagnostic information. Use only under guidance from IBM service personnel. DIAG=N (suppresses the formatting of diagnostic information) is the default.
EB=nnnnnnnn Only the trace points associated with this EB thread are displayed (the format of this keyword is EB=nnnnnnnn where nnnnnnnn is the 8-digit address of an EB thread that is contained in the trace). You must use this in conjunction with the TT keyword.
LG All control blocks.
PTF=Y, LOAD=load module name A list of PTFs at the front of the report (from MEPL). PTF=N (suppresses the formatting of such a list) is the default.

The optional load subparameter allows you to specify the name of a load module, up to a maximum of 8 characters, for which to format a PTF report.

SA=hhhh The control blocks for a specified address space. Use either of the following formats:

  • SA=hh or

  • SA=hhhh

where h represents a hexadecimal digit.

SG A subset of system-wide control blocks.
TT The trace table only.

Table 7 details the dump formatting keywords that we can use to format the data relating to individual resource managers. We cannot use these keywords in conjunction with any of the keywords in Table 6.

Table 7. Resource manager dump formatting keywords
Keyword What is formatted
BMC=1

BMC=2(buffer pool number)

Buffer manager data. BMC=1 formats control blocks of all buffers. BMC=2 formats data relating to the buffer identified in the 2-digit buffer pool number.
CFS=1 Coupling Facility manager report.
DB2=1 DB2 manager report.
DMC=1,

ONAM=object name

Data manager data.

The optional ONAM subparameter allows you to specify the object name, up to a maximum of 20 characters, to limit data printed to objects starting with characters in ONAM.

DMC=2,

ONAM=object name

Formats scavenger information.

The optional ONAM subparameter allows you to limit the objects printed to those with names beginning with the characters specified in ONAM (up to a maximum of 20 characters).

IMS=1 IMS bridge data.
LMC=1 Log manager data.
MMC=1,
OBJ=object type,
ONAM=object name 		Message manager data. The optional OBJ subparameter allows you to select the message manager data for a specific object type. Permitted object type values are:

  • MAUT (for authentication information)

  • MQLO (for local queues that are not shared)

  • MQSH (for local queues that are shared)

  • MQRO (for remote queues)

  • MQAO (for alias queues)

  • MQMO (for model queues)

  • MCHL (for channels)

  • MNLS (for namelists)

  • MSTC (for storage classes)

  • MPRC (for processes)

The optional ONAM subparameter allows you to limit the objects printed to those with names beginning with the characters specified in ONAM (up to a maximum of 20 characters).

MMC=2,
ONAM=object name 		MMC=2 formats trigger information for local queues.

The optional ONAM subparameter allows you to limit the objects printed to those with names beginning with the characters specified in ONAM (up to a maximum of 20 characters).

THR=* A list of all threads with connections.
THR=EB_address Thread-related data for the specified EB thread.

If the dump is initiated by the operator, there is no information in the summary portion of the dump. Table 8 shows additional keywords that we can use in the CSQWDMP control statement.

Table 8. Summary dump keywords for the WebSphere MQ for z/OS dump formatting control statement
Keyword Description
SUBSYS=aaaa Use this keyword if the summary dump portion is not available, or not to be used, to give the name of the subsystem to format information for. aaaa is a 1 through 4-character subsystem name.
SUMDUMP=NO Use this keyword if the dump has a summary portion, but you do not want to use it. (You would usually only do this if so directed by your IBM support center.)

The following list shows some examples of how to use these keywords:

  • For default formatting of all address spaces, using information from the summary portion of the dump, use: 

    VERBX CSQWDMP

  • To display the trace table from a dump of subsystem named MQMT, which was initiated by an operator (and so does not have a summary portion) use: 

    VERBX CSQWDMP 'TT,SUBSYS=MQMT'

  • To display all the control blocks and the trace table from a dump produced by a subsystem abend, for an address space with ASID (address space identifier) 1F, use: 

    VERBX CSQWDMP 'TT,LG,SA=1F'

  • To display the portion of the trace table from a dump associated with a particular EB thread, use: 

    VERBX CSQWDMP 'TT,EB=nnnnnnnn'

  • To display message manager 1 report for local non-shared queue objects whose name begins with 'ABC' use: 

    VERBX CSQWDMP 'MMC=1,ONAM=ABC,Obj=MQLO'

Table 9 shows some other commands that are used frequently for analyzing dumps. For more information about these subcommands, see the MVS IPCS Commands manual.

Table 9. IPCS subcommands used for dump analysis
Subcommand Description
STATUS To display data usually examined during the initial part of the problem determination process.
STRDATA LISTNUM(ALL) ENTRYPOS(ALL) DETAIL To format Coupling Facility structure data.
VERBEXIT LOGDATA To format the in-storage LOGREC buffer records present before the dump was taken. LOGDATA locates the LOGREC entries that are contained in the LOGREC recording buffer and invokes the EREP program to format and print the LOGREC entries. These entries are formatted in the style of the normal detail edit report.
VERBEXIT TRACE To format the system trace entries for all address spaces.
VERBEXIT SYMPTOM To format the symptom strings contained in the header record of a system dump such as stand-alone dump, SVC dump, or an abend dump requested with a SYSUDUMP DD statement.
VERBEXIT GRSTRACE To format diagnostic data from the major control blocks for global resource serialization.
VERBEXIT SUMDUMP To locate and display the summary dump data that an SVC dump provides.
VERBEXIT DAEDATA To format the dump analysis and elimination (DAE) data for the dumped system.

 

Formatting a dump from the channel initiator

The IPCS VERBEXIT CSQXDPRD enables you to format a channel initiator dump. We can select the data that is formatted by specifying keywords.

This section describes the keywords that we can specify.

Table 10 describes the keywords that we can specify with CSQXDPRD.

Table 10. Keywords for the IPCS VERBEXIT CSQXDPRD
Keyword What is formatted
SUBSYS=aaaa The control blocks of the channel initiator associated with the named subsystem. It is required for all new formatted dumps.
CHST=1,
CNAM=channel name,
DUMP=S|F|C

All channel information.

The optional CNAM subparameter allows you to specify the name of a channel, up to a maximum of 20 characters, for which to format details.

The optional DUMP subparameter allows you to control the extent of formatting, as follows:

  • Specify DUMP=S (for "short") to format the first line of the hexadecimal dump of the channel data.

  • Specify DUMP=F (for "full") to format all lines of the data.

  • Specify DUMP=C (for "compressed") to suppress the formatting of all duplicate lines in the data containing only X'00'. This is the default option

CHST=2,
CNAM=channel name,
A summary of all channels, or of the channel specified by the CNAM keyword.

See CHST=1 for details of the CNAM subparameter.

CHST=3,
CNAM=channel name,
Data provided by CHST=2 and a program trace, line trace and formatted semaphore table print of all channels in the dump.

See CHST=1 for details of the CNAM subparameter.

CLUS=1 Cluster report including the cluster repository known on the queue manager.
CLUS=2 Cluster report showing cluster registrations.
CTRACE=S|F,


DPRO=nnnnnnnn,


TCB=nnnnnnn

Select either a short (CTRACE=S) or full (CTRACE=F) CTRACE.

The optional DPRO subparameter allows you to specify a CTRACE for the DPRO specified.

The optional TCB subparameter allows you to specify a CTRACE for the job specified.

DISP=1,
DUMP=S|F|C 		Dispatcher report

See CHST=1 for details of the DUMP subparameter.

 

Formatting a Coupling Facility structure dump

The Coupling Facility administration structure and application structures for your queue-sharing group, in conjunction with dumps of queue managers in the queue-sharing group might be required by IBM Service Personnel to aid problem diagnosis.

For information on formatting a Coupling Facility list structure, and the STRDATA subcommand, see the MVS IPCS Commands book.