IBM Support

II11016: HOW TO FIND PSW AND REGS AT TIME OF ERROR WITH LE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • In most cases LE condition handling will trap original
    program checks (like ABEND0C4) and turn them into corresponding
    LE conditions (like CEE3204S). After storing information about
    the original program check, LE will terminate with an
    ABENDU40xx. When examining a dump of a U40xx, the PSW and
    Registers can be found in a control block called the ZMCH. This
    will assist in identifying the failing module, offset within
    that module, and the register contents at the time of the error.
    
    
    *********** NON - CICS *****************************************
    -
       First you will need to obtain a SYSMDUMP.  Instructions on
    how to get a SYSMDUMP with LE can be found in Info APAR II10573.
    After loading the SYSMDUMP into IPCS, issue one of the following
    commands to format the ZMCH:
        IP VERBX LEDATA 'CM'
               or
        IP VERBX CEEERRIP 'CM'
    
    (For more information on the syntax, refer to the z/OS LE
    Debugging Guide, z/OS LE Run-Time Messages, or the IPCS Command
    in z/OS MVS System Commands.)
    
       The LEDATA verb searches for an error TCB and formats the
    control blocks for that TCB. If there is no error TCB (such as
    in a console dump) the TCB or CAA keywords will need to be
    specified.  They can be tried as follows:
    
    -
    To use the TCB Address:
    
    1.  Load the SYSMDUMP into IPCS.
    2.  Issue command:  IP SUMM FORMAT
    3.  Issue command:  BOTTOM
    4.  Find the TCB with a non-zero completion code (heading=CMP).
    5.  Try the command: IP VERBX LEDATA 'CM TCB(xxxxxxxx)'
    -
    
       If this fails to format the control blocks, try using the
    CAA:
    
    -
    To use the CAA Address (AMODE 31 only):
    
    Find the TCB in question by completing steps 1-4 above and
    continue:
    
    6.  Issue command:  F 'TCB: xxxxxxxx' PREV  where the x's
        represent the address of the failing TCB.
    7.  Issue command:  F RTM2WA
    8.  Hit PF5 to search again (to find "RTM2WA SUMMARY").
    9.  Cut/Copy the address in Register 12 (this is the CAA@).
    10. Issue command:  =1   to go into Browse mode.
    11. Hit enter to accept the defaults.
    12. Type an "s" in the PTR field for the address space of
        interest and hit enter.
    13. Issue the command:  L yyyyyyyy    where the y's represent
        the address obtained from Reg 12 (the CAA@).
    14. Now verify whether this is a valid CAA with the following:
        a. At the Reg 12 address verify that the value is
           "xxxx0800"
        b. Issue command:  L X-18   and the eyecatcher should be
           CEECAA
    15. This indicates we have found a valid CAA and we can now
        issue the command:  IP VERBX LEDATA 'CM CAA(yyyyyyyy)'
    -
    
       Now that the control blocks are formatted, you can find the
    ZMCH with command:
       F ZMCH
    so you can locate the PSW and Register contents to help find
    the failing module, offset, and Register contents at the time
    of error.
    
    
    -
    Note that the above does NOT pertain to an ABENDU4036.
    Information for the particular reason code associated with
    the U4036 ABEND is in the z/OS LE Debugging Guide and the
    z/OS LE Run-Time Messages manuals.  Follow the instructions
    there to find the information about the original error.
    -
    
    ***************** CICS *****************************************
    -
       When running under CICS an alternate method of retrieving the
    CAA and DSA may be necessary.  The following steps outline a
    procedure to obtain these addresses under CICS.  NOTE: Some of
    the sample outputs have been modified to fit within the bounds
    to avoid wrapping, so the output may not exactly match yours, be
    sure you match the desired field names!
    
    
    Step 1:
    -
    Obtain the CICS TCA address: issue the following command
    replacing the xxx with the appropriate CICS Release
    (610,620,630,640,650):
    
       ip verbx DFHPDxxx 'KE=3'
    
    Look for the running task (which may be in an error state):
    
    KE_NUM KE_TASK  STATUS       TCA_ADDR TRAN_# TRANSID DS_TASK
    00E3   14469880 ***Running** 00056680 55614  PM30    1CA89200
                                 ^^^^^^^^
    Then grab the TCA address for this task.
    -
    
    Step 2:
    -
    Obtain the EIUS address and Transaction Number for this task
    by issuing:
    
       ip verbx DFHPDxxx 'AP=3'
    
    Look for the following output and get the EIUS address
    corresponding to the TCA address from step 1:
    
    Tran  Tran   TCA       EIB       SEIB     EIUS
     No    Id    Addr      Addr      Addr     Addr
    55614 PM30   00056680  001450D0  00056A94 00145008
    ^^^^^        ^^^^^^^^                     ^^^^^^^^
    -
    
    Step 3:
    -
    Locate in the same output the SYSTCA.  Easiest way is to issue:
       F SYS_TCA.zzzzz
    where zzzzz is the Transaction Number from Step 2.  Looking at
    the SYSTCA the CAA address is at offset +x'94'.  Save this
    address.
    -
    
    Step 4:
    -
    Locate in the same output the EIUS.  Issue:
       F EIUS.zzzzz
    Looking at this output the DSA is at EIUS+x'50'.
    -
    
    Step 5:
    -
    Now that you have the CAA and DSA address you can issue the
    LEDATA command:
        ip verbx ledata 'caa(caa@) dsa(dsa@) all'
    -
    
       Now that the control blocks are formatted, you can find the
    ZMCH with command:
       F ZMCH
    so you can locate the PSW and Register contents to help find
    the failing module, offset, and Register contents at the time
    of error.
    
    
    ----
    KEYWORDS:
    MSGCEE3201 MSGCEE3202 MSGCEE3203 MSGCEE3204 MSGCEE3205
    MSGCEE3206 MSGCEE3207 MSGCEE3208 MSGCEE3209 MSGCEE3210
    MSGCEE3211 MSGCEE3212 MSGCEE3213 MSGCEE3214 MSGCEE3215
    MSGCEE3201S MSGCEE3202S MSGCEE3203S MSGCEE3204S MSGCEE3205S
    MSGCEE3206S MSGCEE3207S MSGCEE3208S MSGCEE3209S MSGCEE3210S
    MSGCEE3211S MSGCEE3212S MSGCEE3213S MSGCEE3214S MSGCEE3215S
    CEE3201S CEE3202S CEE3203S CEE3204S CEE3205S CEE3206S
    CEE3207S CEE3208S CEE3209S CEE3210S CEE3211S CEE3212S
    CEE3213S CEE3214S CEE3215S
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II11016

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1998-01-22

  • Closed date

  • Last modified date

    2009-05-18

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
18 May 2009