IBM Support

PM74179: ENABLE ALLOCATION OF AN IIUDUMP DATA SET DYNAMICALLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Enable allocation of an IIUDUMP data set dynamically as SYSOUT
    to print a SNAP dump at an I/O error while scanning a database
    or loading an index.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS Index Builder for z/OS,     *
    *                 Version 3 Release 1 (FMID=H22O310)           *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR enables to produce an snap    *
    *                      dump in the IIUDUMP data set when an    *
    *                      I/O error occurs during the DB scan     *
    *                      process or the index load process.      *
    *                      The snap dump file is used for          *
    *                      analysis.                               *
    *                                                              *
    *                      And the following problems are fixed:   *
    *                      1. When the scan process fails with     *
    *                      REASON=749 or REASON=756, the other     *
    *                      active common sorts (IIUSRTxx) and      *
    *                      the buffered index sorts should be      *
    *                      terminated without sorting records.     *
    *                                                              *
    *                       IIUB052E ERROR IN IIUSCAxx             *
    *                           - REASON=749                       *
    *                           COMMON SORT FAILURE ABEND          *
    *                                                              *
    *                       IIUB052E ERROR IN IIUSCBxx             *
    *                           - REASON=756                       *
    *                           SEQUENTIAL BUFFER SCAN FAILURE     *
    *                                                              *
    *                      In this case, MSGIIUB050E should not    *
    *                      be printed.                             *
    *                       IIUB050E index IIUSRPRC SUBORDINATE    *
    *                          PROCESS FAILURE - REASON=A26        *
    *                          SORT PROCESSING FAILURE             *
    *                                                              *
    *                      2. The access registers 14-1 should     *
    *                      be restored after calling MVS macros    *
    *                      in the AR mode.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR fixes the problems listed in the Problem Description
    field.
    

Problem conclusion

Temporary fix

Comments

  • This APAR enables to produce a snap dump in the IIUDUMP data
    set when an I/O error occurs during the DB scan process or
    the index load process.
    
    In this case, a new IIUB090I message is printed in the joblog
    and the IIUPRINT data set.
     IIUB090I SNAP DUMP IS GENERATED IN IIUDUMP DATA SET.
              JOBID=jobid
    
    If the IIUDUMP DD statement is not coded the JCL or
    the subordinate address space procedure IIUBSRT, the data set
    is allocated dynamically.
    
    ========================
    = Documentation Change =
    ========================
    IBM IMS Index Builder for z/OS, V3R1, User's Guide
    (SC18-9101-04) should be changed as follows:
    ================================================================
    2.2.1 IMS Index Builder JCL
    2.2.1.2 DD statements
    
     IIUDUMP DD statement
      This DD statement contains a dump that is generated as the
      result of an error. You can use this dump to diagnose the
      error.
    | If not specified, this file is allocated dynamically as:
    | //IIUDUMP DD SYSOUT=*.
      This statement is optional.
    
    ----------------------------------------------------------------
    3.3 IMS Index Builder reason codes
    3.3.3 IMS Index Builder initialization phase secondary reason
          codes
    
     756    SEQUENTIAL BUFFER SCAN FAILURE
    
      Explanation: The database might be corrupted.
      User Response:  Check database integrity. If the problem
      persists, contact the installation DBA.
    | If the cause is an IMS Index Builder internal error,
    | an snap dump produced in the IIUDUMP data set is needed for
    | analysis.
      The general-purpose registers at taking the snap dump contain
      the following information:
       R2 RBA of the database block or CI
       R3 Storage address of the database block or CI
       R4 Storage address of the segment currently processed
    ----------------------------------------------------------------
    3.4 IMS Index Builder messages
    
     IIUB048E ddname xxxxxxxx VSAM ERROR WHILE LOADING INDEX
              -- REASON=reason
    
      Explanation: A VSAM error occurred while loading INDEX.
      System Action: Processing stops.
      User Response: See "IMS Index Builder processing phase
      failure reason codes" in topic 3.3.5 for information about
      the reason code issued by this message and the appropriate
      action to take.
      xxxxxxxx shows the VSAM macro return code and reason code in
      the RPL feedback area or in the ACB error field. For the
      meaning of the codes, see DFSMS Macro Instructions for Data
      Sets.
    | If the cause is an IMS Index Builder internal error,
    | an snap dump produced in the IIUDUMP data set is needed for
    | analysis.
    ----------------------------------------------------------------
    | IIUB090I SNAP DUMP IS GENERATED IN IIUDUMP DATA SET.
    |          JOBID=jobid
    |
    | Explanation: An snap dump is produced in the IIUDUMP data set
    | in the indicated job, which is the main address scape or a
    | subordinate address space, for analysis.
    | System Action: Processing stops.
    | User Response: None
    ----------------------------------------------------------------
    ================= End of Documentation Change ==================
    

APAR Information

  • APAR number

    PM74179

  • Reported component name

    IMS INDEX BUILD

  • Reported component ID

    5655E2400

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2012-10-02

  • Closed date

    2012-11-01

  • Last modified date

    2012-12-04

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

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

    UK83147

Modules/Macros

  • IIUBDE10 IIUBDE20 IIUBEN20 IIUBMSGS IIUBSCTL
    IIUDRVRX IIUDSRTD IIUDYN10 IIUMMGR1 IIUNDXRC IIUSCA01 IIUSCA11
    IIUSCA12 IIUSCB01 IIUSCB11 IIUSCB12 IIUSE15  IIUSIN00 IIUSIN10
    IIUSIN12 IIUSIN20 IIUSRPRC IIUSTART
    

Publications Referenced
SC18910104    

Fix information

  • Fixed component name

    IMS INDEX BUILD

  • Fixed component ID

    5655E2400

Applicable component levels

  • R310 PSY UK83147

       UP12/11/02 P F211

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":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89M","label":"IMS Index Builder"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 December 2012