IBM Support

PQ69369: DB2 OBJECT RESTORE INTERFACE JCL ERRORS: IMPROPER SUMMARY REPORTFORMATTING: LOAD UTILITY ERROR: ABENDS0C4 IN ALAREC3 OR ALALF3

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ERROR DESCRIPTION
    This APAR will correct the following errors that occur when ALA
    is invoked
     from DB2 Object Restore Tool:
     - Error during JCL creation possible, such as 'unknown text:
       MLIST'
     - JCL allocation changed to MOD from SHR to allow for
       appending JCL so
       that JCL does not get overwritten
    .
    Correction of summary report formatting in the General report.
    Prior to this APAR, misplaced underlines were possible, and
    garbage (unreadable) data was possible
    .
    Correction of LOAD utility failure when processing 'Load
    details into DB2' when different tables reside in different
    tablespaces. This APAR allows use of different tablespaces to
    be processed in a single run.
    .
    Correction of possible ABENDS0C4 in ALAREC3 or ALALF3 when
    LOB column exists and it is not the  last sequential column of
    table
    .
    Correction of possible S0C4 in ALAREC (log-backward detail
    report only) when two different tables in same tablespace are
    updated and a REORG occurs after the updates.
    .
    ******
    KEyWORDS
    ABEND0C4 S0C4 ALAREC
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL DB2 Object Restore Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR will correct the following    *
    *                      errors that occur when ALA is invoked   *
    *                      from DB2 Object Restore Tool:           *
    *                                                              *
    *                      - Error during JCL creation possible,   *
    *                        such as 'unknown text: MLIST'         *
    *                                                              *
    *                      - JCL allocation changed to MOD from    *
    *                        SHR to allow for appending JCL so     *
    *                        that JCL does not get overwritten     *
    *                      .                                       *
    *                      Correction of                           *
    *                      summary report formatting in the        *
    *                      General report.Prior to this APAR,      *
    *                      misplaced underlines were possible, and *
    *                      garbage (unreadable) data was           *
    *                      possible                                *
    *                                                              *
    *                      Correction of LOAD utility failure when *
    *                      processing 'Load details into DB2' when *
    *                      different tables reside in different    *
    *                      tablespaces. This APAR allows use of    *
    *                      different tablespaces to be processed   *
    *                      in a single run.                        *
    *                                                              *
    *                      Correction of possible ABEND0C4 in      *
    *                      ALAREC3 or ALALF3 when LOB column       *
    *                      exists and it is not the  last          *
    *                      sequential column oftable               *
    *                                                              *
    *                      Correction of possible S0C4 in ALAREC   *
    *                      (log-backward detail report only)       *
    *                      when two different tables in same       *
    *                      tablespace are updated and a REORG      *
    *                      occurs after the updates. report only)  *
    *                      when two different tables in same       *
    *                      tablespace are updated and a REORG      *
    *                      occurs after the updates.               *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A code change has been made to address these issues.
    

Problem conclusion

  • APPLY PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ69369

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2002-12-20

  • Closed date

    2003-01-16

  • Last modified date

    2003-02-05

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

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

    UQ73300

Modules/Macros

  •    ALAAA2   ALAA06   ALAA09   ALABIND  ALACNTL
    ALAFRMTR ALAFRONT ALAFR1C  ALAGLOAD ALAINTC  ALALF1   ALAMAIN
    ALAREC   ALASREP  ALAZ0004
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R130 PSY UQ73300

       UP03/01/23 P F301

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130"}]

Document Information

Modified date:
17 March 2021