IBM Support

PH13766: POSSIBLE S0C4 IN ALADTL3

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Possible S0C4 in ALADTL3 when the catalog audit report is
    requested.
    

Local fix

  • The user can exclude the catalog audit report from the run.
    Also, the following ZAP can be applied on maintenance equal
    PI89909 / UI52404 or higher.
     //ZAP EXEC PGM=AMASPZAP
     //SYSPRINT DD SYSOUT=*
     //SYSLIB DD DISP=SHR,DSN=customer.LOADLIB
     //SYSIN DD *
     NAME ALADTL3 ALACTAU
     VER 0140 E370,C1A0,0004
     VER 40F8 C088,C08A,C08C,C08E
     REP 0140 A7F4,1FDC
     REP 40F8 B982,0077
     REP 40FC B982,0066
     REP 4100 A7F4,E023
     REP 4104 C094,C096,C098,C09A
     /*
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Possible S0C4 in ALADTL3 when the       *
    *                      catalog audit report is requested.      *
    ****************************************************************
    1. If we reach end of file during LBM file scan in ALALB3, SOC4
       is generated, because this situation is unhandled.
    
    2. In case MODE35 file contains SSID that is absent from control
       file and its LOG ANALYSIS TOOL job is run on other SSID that
       is available in control file, in one-phase mode, LOG ANALYSIS
       TOOL can fall with ALAA067E.
    
    3. The ALABINDC was changed to remove NFM parameter as we don't
       have it anymore. It was used for Db2 v8.
    
    4. The error message ALAA707E should be issued when the user
       combined 1PH mode with step of 2PH mode.
    
    5. Possible S0C4 in ALADTL3 when the catalog audit report is
       requested.
    
    6. Wrong partition number/IDs in header column in ALAGLOAD and
       ALACLDEL modules.
    
    7. Corrections in ISPF panels.
    
    8. Erroneous ALAA328E for ALAAA5D corrected.
    
    9. When using share level change image copies after converting
       the TABLESPACE to use 10 byte LOGPOINTS, it is possible that
       an ALAA440E, ALAA447E, or U=55 ABEND can occur.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH13766

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-24

  • Closed date

    2019-08-15

  • Last modified date

    2019-09-01

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

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

    UI64771

Modules/Macros

  • ALA#ERRM ALA#LCLF ALA#LDSN ALA#STOR ALA$$CCQ ALAAA5G  ALABIND
    ALABIND1 ALABINDA ALABINDC ALABINDP ALACC    ALACLDEL ALACTAU
    ALADTL1  ALADTL2  ALADTL3  ALADTL4  ALAFR6TC ALAGEN1  ALAGIC
    ALAGL2   ALAGL3   ALAGL4   ALAGLOAD ALAGLOAT ALAGLSUM ALALAUD
    ALALB3   ALALF1   ALAPNL1  ALAPNL2  ALASETUP ALAUTIL  ALAVBIO
    ALAZH030 ALAZH941 WTO
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI64771

       UP19/08/17 P F908

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":"3.5.0"}]

Document Information

Modified date:
30 March 2021