IBM Support

PK84749: RAS: IMS FORMATTING FOR A SYSMDUMP GETS ERRORS WHEN TRYING TO FORMAT FIELDS FROM THE SDWA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer prefers to use SYSMDUMPs to diagnose their IMS
    abends.  They set FMTO=T in order to get this type of dump.
      When using the IMS panels to get diagnostic information, they
    get MSGDFS3937I UNABLE TO ACCESS STORAGE WHILE FORMATTING THE
    DIAGNOSTIC AREA REQUESTED STORAGE: ADDR=007A6808, ASID=0039,
    LENGTH=00000020 (when using the SUMMARY option) and DFS3937I
    UNABLE TO ACCESS STORAGE WHILE FORMATTING THE AUTO OPTION PROC
    REQUESTED STORAGE: ADDR=00F8C000, ASID=0039, LENGTH=00000048
    (when using the AUTO option).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V10 users using the SYSMDUMP DD      *
    *                 and option FMTO=T to produce a SYSMDUMP      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Various IMS termination problems result *
    *                      in incomplete dumps when using SYSMDUMP *
    *                      which causes IMS Dump Formatter errors. *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Customer experienced multiple MSGDFS3937I while processing IMS
    dump produced by SYSMDUMP. The DFS3937I message is issued when
    there is a dump storage access error. Some dump storage access
    errors are the result of an incomplete dump. Others are caused
    by the method that is used to identify and locate the SDWA for
    a dump produced by SYSMDUMP.
    
    Several IMS abnormal termination problems have been identified
    which result in an incomplete dump when using SYSMDUMP.  These
    are:
    
    DFSSDL20 - The common TCB ETXR exit routine in DFSSDL20, the
               DLI-SAS Region Attach/ETXR Processor, was changed
               by PTM KWS0009 in IMS 7.1 as a result of FIN APAR
               PN92111 to address a DLI region abend termination
               error.  The change introduced code which used the
               high-order bit of the stored DLI TCB addresses as
               a flag bit.
    
               These addresses are passed unchanged to the MVS
               DETACH service to terminate the non-abending DLI
               TCBs when the DLI address space is abending.
    
               Passing a TCB address with the h/o bit set causes
               the DETACH service to abend.  In this case, since
               DLI is already in an RTM process, the DETACH abend
               is silent.  No messages or other indicators can be
               seen except that the abend interrupts the SYSMDUMP
               in-progress resulting in a partial dump.
    
               This will happen when the original abend is in the
               control region or in the DBRC region.
    
    DFSFSTM0 - Module DFSFSTM0, the control region STM Processor
               (E)STAE Exit Routine, has no facility to wait for
               the DBRC address space to complete termination as
               it does for the DLI address space. If the control
               region ends prior to SYSMDUMP capturing essential
               data, the Dump Formatter can not process the dump.
    
               This will happen when the original abend is in the
               control region or in the DLI region.
    
    DFSXRID0 - The DBRC ESTAE exit in DFSXRID0, the DBRC region
               initialization module, bypasses a call to DFSFDMP0
               for all abnormal sign-off requests - a U0150 abend.
               In the case of SYSMDUMP, where there is a separate
               dump created for each IMS address space, bypassing
               DFSFDMP0 results in missing SDWA SETRP data.
    
    There are also several problems in the IMS Dump Formatter that
    result in errors and incorrect output when processing any dump
    produced by SYSMDUMP.  These are:
    
    DFSAACI0 - DFSAACI0, the IMS Dump Formatter Init Panel Driver
               initialization CLIST, attempts to use the SCDDSDWA
               and SCDDASID fields from the SCD for the dump SDWA
               address and ASID value, respectively.
    
               This methodology works for an SVC dump, when there
               is a single, consolidated dump for all IMS address
               spaces, but does not work when there are multiple
               dumps, from multiple address spaces, which is the
               case for SYSMDUMP.
    
    DFSOFMD0 - DFSOFMD0, the IMS Dump Formatter Offline Formatted
               Dump Initialization module, also uses the SCDDSDWA
               and SCDDASID fields from the SCD for the dump SDWA
               address and ASID value, respectively.
    
               This methodology works for an SVC dump, when there
               is a single, consolidated dump for all IMS address
               spaces, but does not work when there are multiple
               dumps, from multiple address spaces, which is the
               case for SYSMDUMP.
    
    DFSABLF0 - DFSABLF0, the IMS Dump Formatter Symptom String
               Format Routine, does not check for control region
               storage being present in the dump.  The storage
               this module formats is only present in the control
               region.  When a separate SYSMDUMP is processed for
               either the DLI or DBR regions an extraneous and
               confusing DFS3937I message is generated because
               the required control region storage area is not
               available.
    
    DFSAUTO0 - DFSAUTO0, the Auto Option Processor, produces an
               extraneous MSGDFS3937I when attempting to access
               the SAP because the CTL region ASID is hard-coded
               on the call to the access service.  The CTL ASID
               is not necessary for SVC dumps and incorrect for
               SYSMDUMP.
    
    ADDITIONAL PROBLEMS:
    
    DFSABND0, IMS Dump Formatter Online Dump Format Initialization
    module, inserts an incorrect region mnemonic value in the dump
    report title because it checks the wrong flag for the presence
    of CTL, DLI, or DBR region storage in the dump.
    
    DFSFDMP0, the IMS Offline Dump Assist Module, copies the abend
    SDWA into an internal area in the case of SYSMDUMP which is no
    longer needed.
    

Problem conclusion

  • GEN:
    KEYWORDS:
     IMSSERV
    
    *** END IMS KEYWORDS ***
    The following changes have been made to address problems when
    processing a SYSMDUMP:
    
    DFSAACI0 - Updated to use the SDWA address and ASID value
               from the dump header when processing a SYSMDUMP
    
    DFSABLF0 - Updated to check for the presence of the control
               region in the dump and to bypass processing, and
               avoid error messages, if not present
    
    DFSABND0 - Updated to use the correct flags when checking
               for an IMS region's storage being included in a
               dump, so that the correct mnemonic is inserted
               into the dump report title when processing a
               SYSMDUMP:
    
                 CTL for control region
                 DLI for DLI-SAS region
                 DBR for DBRC region
                 UNK for UNKNOWN region
    
    DFSAUTO0 - Updated to remove hard-coded CTL ASID on access
               call for SAP
    
    DFSFDMP0 - Updated to remove SCDDSDWA update and SDWA (R10)
               reset when processing SYSMDUMP SDWA copy. Copied
               SDWA is no longer referenced or used.
    
    DFSFSTM0 - Conditional wait added after DBRC sign-off call
               to allow SYSMDUMP to take place.  Only used
               when SYSMDUMP and abend is not in DBRC itself.
    
    DFSOFMD0 - Updated to use the SDWA address and ASID value
               from the dump header when processing a SYSMDUMP
               and to set CAFMSYSM flag for same
    
    DFSSDL20 - Updated to reset the TCB address passed to the
               DETACH service so as not to have the h/o bit on
    
    DFSXRID0 - Updated to call DFSFDMP0 for SETRP's if U0150
               and SYSMDUMP
    
    ICADSECT - Updated to add CAFMSYSM flag, processing SYSMDUMP,
               for IMS Dump Formatter use
    
    ADDITIONAL KEYWORDS:
    U150 U0150 ABENDU150 ABENDU0150
    DFS1193I MSGDFS1193I
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK84749

  • Reported component name

    IMS V10

  • Reported component ID

    5635A0100

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-04-15

  • Closed date

    2010-04-23

  • Last modified date

    2010-05-04

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

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

    PK98651 UK56353

Modules/Macros

  • DFSAACI0 DFSABLF0 DFSABND0 DFSAUTO0 DFSFDMP0
    DFSFSTM0 DFSOFMD0 DFSSDL20 DFSXRID0 ICADSECT
    

Fix information

  • Fixed component name

    IMS V10

  • Fixed component ID

    5635A0100

Applicable component levels

  • R010 PSY UK56353

       UP10/04/29 P F004

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"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":"10.1","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 May 2010