When and how should an SVCDUMP of the TPX region be taken?

Products

• TPX - Session Management

Issue/Introduction

An SVCDUMP is required to debug TPX error conditions that do not provide any information nor display any symptoms in the TPX LOG.
There may also be instances when TPX support / engineering may ask to generate one under various conditions of error.

Environment

Release: TPX 5.4
Component : TPX for Z/OS

Resolution

In general, an SVCDUMP is important for diagnosing, when TPX is in a hung state / using an excessive amount of CPU time or storage related problems.

1. Issue the following z/OS command at the system console:   
              DUMP COMM=(user comment)

        2. MVS will respond:
                       xx IEE094d SPECIFY OPERANDS(S) FOR DUMP COMMAND 
where, xx is the reply number

       
        3. Reply to the console message with:
                     xxJOBNAME=(proc_name,),SDATA=(RGN,SQA,CSA,TRT,LSQA,SWA,SUM,PSA,XESDATA),
                    STRLIST=(STRNAME=sname,ACCESSTIME=NOLIMIT,LOCKENTRIES,(LISTNUM=ALL,      <------> Abbreviated syntax: STL=(STRNM=sname,ACC=NOLIM,LOCKE,(LNUM=ALL,ADJ=CAP,EDATA=SER)),END
                    ADJUNCT=CAPTURE,ENTRYDATA=SERIALIZE)),END

                   where, xx is the reply number   
                   proc_name, is the CA TPX procedure name

Note:         If TPX is not running as a VTAM generic resource,
            -- Omit the STRLIST parameter.
            -- Remove XESDATA from SDATA parms.

Additional Information

Refer to the IBM z/OS MVS System Commands manual for the appropriate z/OS release for additional detail on the commands above.