II10573: Instructions on how to request a SYSMDUMP when running under Language Environment

APAR status

• Closed as canceled.

Error description

• Here are directions on how to request a SYSMdump in the various
  environments:
  *****
  Batch (IMS, Webserver, etc.):
  *****
         1. Specify the following Runtime options:
            ABTERMENC(ABEND)  TERMTHDACT(UADUMP) TRAP(ON,SPIE)
            For information about how to specify Runtime options
            please refer to the section "Specifying run-time
            options under z/OS batch" in the " XL C/C++ User's
            Guide.
         2. Include a SYSMDUMP DD card in the JCL specifying
            SPACE=(CYL,(100,100),RLSE),DISP=(NEW,CATLG,DELETE),
            DSN=dump_dataset_name,LRECL=4160,RECFM=FBS
               (Info apar II11016 explains how to find the
                PSW and Registers at the time of failure.)
      Note: Ensure that your IEADMR00 Parmlib member reflects
            the following SDATA defaults:
        SDATA=(CSA,LPA,LSQA,RGN,SQA,SUM,SWA,TRT,ALLNUC,GRSQ)
  ****
  CICS:
  ****
            A transaction dump should be produced for all LE
            ABENDU40xx series abends, except ABENDU4038.
            If a transaction dump is not enough, request a
            CICS system dump:
            1. Use the CICS supplied CEMT transaction:
               CEMT SET TRD(40xx) SYS ADD
               This will produce a CICS system dump.
               (Refer to the CICS-Supplied Transactions Manual)
      Note: A CICS system dump of an ABENDU4038 is not
            helpful because it is taken at the time of
            of the last termination, not at the point of
            detection. Instead, specify the following:
            TERMTHDACT(UADUMP) ABTERMENC(ABEND) TRAP(ON,SPIE)
            This will produce a CICS transaction dump with
            for an ABENDU4039
            (Ref. OS/390 Language Environment for OS/390
             Customization)
      Note: SLIP commands on C=U40xx will not work
            in CICS. SLIP commands on C=0Cx will
            work in a CICS environment but not in batch.
            TERMTHDACT(UADUMP) ABTERMENC(ABEND) TRAP(ON)
            produces a CICS transaction dump. It will
            never produce a SYSUDUMP/SYSABEND/SYSMDUMP
            since LE's ESTAE routine does not get
            driven.
            (Info apar II13228 explains how to find the
             PSW and Registers at the time of failure.)
  -
    Additional procedure to get a SVCdump for 40xx abends
     under CICS:
    Here are the steps to get a SDUMP for a specific
    40xx transaction ABEND under CICS:
      1) Make sure the CICS region is started with the
         DUMP=YES sysin input (SIP) parameter.
      2) Make sure the SYS1.DUMP- datasets are available.
         Most customers should have all this already setup.
         As an alternative, dynamic allocation facility may be
         used as shown in example below.
         -
             DUMPDS ALLOC ADD,VOL=xxxxxx
             DUMPDS ALLOC=ACTIVE
         After these commands, MVS will dynamically
         allocate datasets on the xxxxxx volume containing
         the dump with the following type of name:
                  SYS1.DUMP.D970910.T191701.SY1.S00001
      3) Once the CICS region is up, signon and issue the
         following:
             'CEMT SET TRD(40xx) ADD SYS'
         Substituting the real dump code eg: 4088 for 40xx
         Below is a sample of what CICS sends back for this:
         SET TRD(4088) ADD SYS
          STATUS:  RESULTS - OVERTYPE TO MODIFY
           Trd(4088) Tra Sys     Loc Max( 999 ) Cur(0000)
      4) Now run the transaction that creates the U40xx ABEND.
         A system, or SVC dump, should be produced at the point
         of the abend. This procedure will work for any
         transaction dump under CICS, not just U40xx ABENDs.
  ********************
  UNIX System Services (OE / Shell environment):
  ********************
    Prior to OS/390 2.7, go to the following URL:
          http://www.s390.ibm.com/le/assist/support/ii10573.html
    At OS/390 2.7 or later:
    1. Specify where to write the system dump:
      To write the system dump to a dataset, issue the command:
          export _BPXK_MDUMP=filename
      where filename is a fully qualified dataset name with
          LRECL=4160 and RECFM=FBS
    2. Specify Language Environment run-time options:
          export _CEE_RUNOPTS="TERMTHDACT(suboption)"
      where suboption is UADUMP (preferred), UAONLY, UATRACE,
      UAIMM.  If UAIMM is set, TRAP(ON,NOSPIE) must also be
      set. Once documentation has been gathered, please revert
      back to TRAP(ON,SPIE) and the previous TERMTHDACT setting.
    3. Rerun the program and the dump will be written to
      the specified dataset.
  ***
  DB2:
  ***
  To override LE Run-Time Options under DB2, see II13232.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing for publication
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels