Using the DUMP command on z/OS

Follow the steps in this task to use the DUMP command on z/OS®.

About this task

z/OS platformYou might be asked to dump any or several of the following address spaces for IBM® to resolve the problem:
  • Control address space
  • DataFlowEngine address space
  • OMVS kernel address space

The following procedure demonstrates how to dump the DataFlowEngine address space. This procedure is the same for any of the address spaces.

Procedure

  1. Find the address space ID of the address space that you want to dump using the display command on the z/OS syslog:
    D OMVS,U=your started task user ID
    This command displays the address spaces of all the processes that are running from your started task user ID, for example:
    D OMVS,U=IB01NODE                                                      
    BPXO040I 16.14.30 DISPLAY OMVS 237                                    
    OMVS     000D ACTIVE          OMVS=(14)                               
    USER     JOBNAME  ASID        PID       PPID STATE   START     CT_SECS
    
    IB01NODE  IB01NODE  009D   67306064   84083282 HRI--- 15.41.55     48.37
      LATCHWAITPID=         0 CMD=bipservice IB01NODE AUTO                 
    IB01NODE  IB01NODE  009D   84083282          1 1WI--- 15.41.55     48.37
      LATCHWAITPID=         0 CMD=/argoinst/S000_L30307_P/usr/lpp/mqsi/bin
    IB01NODE  IB01NODE  009D   16974444   67306064 HRI--- 15.42.01     48.37
      LATCHWAITPID=         0 CMD=bipbroker IB01NODE                       
    IB01NODE  IB01NODE  009F   16974445          1 1W---- 15.42.05   2914.22
      LATCHWAITPID=         0 CMD=/argoinst/S000_L30307_P/usr/lpp/mqsi/bin
    IB01NODE  IB01NODE  009F   33751662   16974445 HR---- 15.42.05   2914.22
      LATCHWAITPID=         0 CMD=DataFlowEngine IB01NODE ca614eec-f300-000
    
    
    The infrastructure main program bipimain is the first process in every address space. For a control address space, bipimain starts the bipservice process, which starts the bipbroker process, which might also start the biphttplistener process, depending on the configuration. For a DataFlowEngine address space, bipimain starts the DataFlowEngine process. For each integration server, an additional DataFlowEngine address space is started. In this example, only one integration server is deployed.
  2. Use the z/OS DUMP command to dump the DataFlowEngine address space, which is shown in the above example as 9F.
    1. Enter the following command:
        DUMP TITLE=(DFE)                                                   
      
      The console returns:
       *`15 IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND                     
      
    2. Enter:
       R 15,ASID=9F,CONT                                                  
      
      The console returns:
       *16 IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND                     
      
    3. Enter:
        R 16,SDATA=(CSA,RGN,PSA,SQA,LSQA,LPA,TRT,GRSQ,SUM),END             
      
      The console returns:
        IEE600I REPLY TO 16 IS;SDATA=(CSA,RGN,PSA,SQA,LSQA,LPA,TRT,GRSQ,SUM),END
        IEA794I SVC DUMP HAS CAPTURED: 356                                 
        DUMPID=014 REQUESTED BY JOB (*MASTER*)                             
        DUMP TITLE=DFE                                                     
        IEF196I IGD101I SMS ALLOCATED TO DDNAME (SYS00018)                 
        IEF196I         DSN (SYS3.DUMP.ARG5.#MASTER#.T142958.S00014      ) 
        IEF196I         STORCLAS (SMS) MGMTCLAS (DUMP) DATACLAS (        ) 
        IEF196I         VOL SER NOS= ARGSMR
      The dump is stored in either a pre-allocated dump data set called SYS1.DUMPxx, or an automatically allocated dump data set named according to an installation-specified pattern.
  3. In some scenarios, all address spaces for a given integration node, that is, all those listed in the example above, plus the OMVS address space and dataspaces, are needed by IBM to resolve the problem. Use the z/OS DUMP command to dump all IB01NODE address spaces.
    1. Enter the command:
      DUMP TITLE=(ALL)                                                   
      
      The console returns:
          `15 IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND                     
      
    2. Enter:
          R 15,JOBNAME=(OMVS,IB01NODE),DSPNAME=('OMVS'.*),SDATA=(PSA,SQA,LSQA,RGN,TRT,
            LPA,CSA,GRSQ,SUM,NUC)      
      The console returns:
           IEE600I REPLY TO 15 IS;JOBNAME=(OMVS,IB01NODE),DSPNAME=('OMVS'.*),S         
           IEA794I SVC DUMP HAS CAPTURED: 303    
           DUMPID=040 REQUESTED BY JOB (*MASTER*)
           DUMP TITLE=ALL                   
           IEE853I 13.40.40 SYS1.DUMP TITLES 306                                
           SYS1.DUMP DATA SETS AVAILABLE=000 AND FULL=000                          
           CAPTURED DUMPS=0001, SPACE USED=00000447M, SPACE FREE=00001053M      
               DUMP.MVK4.#MASTER#.D030415.T134007.S00039 DATA UNAVAILABLE WHILE
                   BEING DUMPED TO                                          
           IEA611I COMPLETE DUMP ON DUMP.MVK4.#MASTER#.D030415.T134007.S00039 309
           DUMPID=040 REQUESTED BY JOB (*MASTER*)                                
           FOR ASIDS(000D,009D,009F)

Results

You can also find information on the individual thread by issuing the DISPLAY z/OS console command, as in the example:
D OMVS,PID=83886535