Formatting an IBM MQ for z/OS dump

Use this topic to understand how to format a queue manager dump using line mode IPCS commands.

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

IBM Service Personnel might require dumps of your coupling facility administration structure and application structures for your queue-sharing group, with dumps of queue managers in the queue-sharing group, to aid problem diagnosis. For information on formatting a coupling facility list structure, and the STRDATA subcommand, see the MVS IPCS Commands book.
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 1 explains each keyword that you can specify in the control statement for formatting dumps.
Table 1. Keywords for the IBM 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 IBM 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

,HANDLES=x

,LOCKS=x

,INSYNCS=x

,URINFO=ALL/LONG

Format trace table

Indicate threads with greater than x handles

Indicate threads with greater than x locks

Indicate threads with greater than x insync operations

Show UR info for ALL threads or for long-running threads

Table 2details the dump formatting keywords that you can use to format the data relating to individual resource managers.

You cannot use these keywords in conjunction with any of the keywords inTable 1.
Table 2. Resource manager dump formatting keywords
Keyword What is formatted
BMC=1

BMC=2( buffer pool number )

BMC=3(xx/yyyyyy)

BMC=4(xx/yyyyyy)

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.

BMC=3 and BMC=4 display a page from a pageset, if the page is present in a buffer. (The difference between BMC=3 and BMC=4 is the route taken to the page.)
BUFL= <nnnnnnnnnnn> Storage access buffer allocation sz.
CALLD=Y

=W

Show arrow for call depth in TT.

and indent trace entry.

CALLTIME=Y Print call time on exit trace.
CB= (<addr>/[<strmodel>]) Format address as IBM MQ block.
CBF=1 CBF report level 1.
CCB=S Show the Composite Capability Block (CCB) for system EBs in TT.
CFS=1 CFS report level 1.
CFS=2 CFS report level 2.
CHLAUTH=1/2

ONAM=<20 chars>

CHLAUTH report level.

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.

CLUS=1 Cluster report including the cluster repository known on the queue manager.
CLUS=2 Cluster report showing cluster registrations.
CLXQ=1 Cluster XMITQ report level 1.
CLXQ=2

ONAM=<20 chars>

Cluster XMITQ report level 2.

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.

CMD=0/1/2 Command trace table display level.
D=1/2/3 Detail level for some reports.
Db2®=1 Db2 report level 1.
DMC=1,

ONAM=<48 chars>

DMC report level 1.

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

DMC=2,

ONAM=<48 chars>

DMC report level 2.

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

DMC=3,

ONAM=<48 chars>

DMC report level 3.

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

GR=1 Group indoubt report level 1.
IMS=1 IMS report level 1
Table 3. Resource manager dump formatting keywords (J -P)
Keyword What is formatted
JOBNAME= xxxxxxxx Job name
LKM=1 LKM report level 1.
LKM=2/3,

,NAME=<up to 48 chars>

,NAMEX= xxxxxxxxxxxxxxxx

,NAMESP=1/2/3/4/5/6/7/8

,TYPE=DMCP/QUALNM/TOPIC/

STGCLASS

,QUAL=GET/PUT/CRE/DFXQ/

PGSYNC/CHGCNT/

DELETE/EXPIRE

LKM=3

LKM=4

,JOBNAME= xxxxxxxx

,ASID= xxxx

LKM report level 2/3.

Name (character)

Name (Hex)

Namespace

Lock type

Lock qualification

LKM report level 3

LKM report level 4

LMC=1 LMC report level 1.
MAXTR= nnnnnnnnn Max trace entries to format
MHASID= xxxx Message handle ASID for properties
MMC=1

OBJ=MQLO/MQSH/MQRO/

MQAO/MQMO/MCHL/

MNLS/MSTC/MPRC/ : '

MAUT

ONAM

MMC report level 1

Object type

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

MMC=2

ONAM=<48 chars>

MMC report level 2

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

MSG=nnnnnnnnnnnnnnnn

MASID=xxxx

LEN=xxxxxxxx

MSGD=S/D

Format the message at pointer.

MASID allows storage in other address spaces.

LEN limits amount of storage to format.

MSGD controls level of detail.

MSGD=S/D Message details in DMC=3, BMC=3/4, PSID reports.

The parameter controls level of details, S is summary and D is detailed.

MSGH = nnnnnnnnnnnnnnnn Message handle
MT Message properties trace
MQVCX MQCHARVs in hexadecimal format
PROPS= nnnnnnnnnnnnnnnn Message properties pointer
PSID= nnnnnnnn Pageset to format page
PSTRX Properties strings in hex format
Table 4. Resource manager dump formatting keywords (R -Z)
Keyword What is formatted
RPR= nnnnnnnn Page or record to format
SHOWDEL Show deleted records for DMC=3
SMC=1/2/3 Storage manager
TC=

*

A

E

0

TT data char format, concatenated

print all in suitable character set

always print ASCII

always print EBCDIC

never print either

TFMT=H/M Time format - human or STCK
THR= nnnnnnnn Thread address
THR=*/2/3 Set thread report level
TOP=1 TOP report level 1
TOP=2 TOP report level 2
TOP= nnnnnnnnnnnnnnnn

/TSTR=<48 chars>

/TSTRX=<hex 1208 str>

Tnode 64bit address or

Topic string (wildcard with % at start or end)'

This will be converted EBCDIC to ASCII, but only invariant characters

Hexadecimal of topic string in 1208 always wildcard character at start.

TOP=3 TOP report level 3
TOP=4 TOP report level 4
TSEG=M(RU)/Q(P64)

I(NTERPOLATE)

F(WD)

D(EBUG)

Search process for 64-bit trace

Guess missing TSEG address or addresses

Force forward sort

Debug search process

TSEG=(M,Q,I,F,D) Specify multiple TSEG options
W=0/1/2/3 TT width format
XA=1 XA report level 1
ZMH = nnnnnnnnnnnnnnnn ZST message handle

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

Table 5. Summary dump keywords for the IBM 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 with a name begins with 'ABC' use:
    
    VERBX CSQWDMP 'MMC=1,ONAM=ABC,Obj=MQLO'
    
Table 6shows some other commands that are used frequently for analyzing dumps. For more information about these subcommands, see the MVS IPCS Commands manual.
Table 6. 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.