IBM Support

PH10518: VARIOUS ISSUES ENCOUNTERED WHEN IMPROPERLY POSITIONING INTO A LOG DATASET.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When attempting to position inside a log dataset for more
    efficient access, Db2 Log Analysis Tool was not properly
    considering which log dataset was being processed when
    calculating the relative RBA. This can result in an ALAA447E,
    ALAA440E, S0C7 during decompression, or data not being reported
    accurately. Each of these issues is due to missing a needed log
    record during the Detail Report processing.
    .
    This is most likely to occur during non Hi-Speed processing in a
    non DATASHARING environment when SYSLGRNX processing has
    eliminated the first log dataset in the list of log datasets
    that match the log ranges needed to be processed.
    

Local fix

  • Turn off SYSLGRNX processing using Misc flags=X until the APAR
    can be applied.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 Log Analysis Tool for z/OS      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When attempting to position inside a    *
    *                      log dataset for more efficient access,  *
    *                      Db2 Log Analysis Tool was not properly  *
    *                      considering which log dataset was being *
    *                      processed when calculating the relative *
    *                      RBA. This can result in an ALAA447E,    *
    *                      ALAA440E, S0C7 during decompression, or *
    *                      data not being reported                 *
    *                      accurately. Each of these issues is due *
    *                      to missing a needed log record during   *
    *                      the Detail Report processing.           *
    *                                                              *
    *                      This is most likely to occur during non *
    *                      Hi-Speed processing in a non            *
    *                      DATASHARING environment when SYSLGRNX   *
    *                      processing has                          *
    *                      eliminated the first log dataset in the *
    *                      list of log datasets that match the log *
    *                      ranges needed to be processed.          *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    Code has been changed to fix this problem.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH10518

  • 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-04-02

  • Closed date

    2019-05-16

  • Last modified date

    2019-06-03

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

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

    UI63084

Modules/Macros

  • ALADSPG  ALAIN4X  ALAIN4XR ALAIN5X  ALAIN9X  ALAIN9XR ALAINBX
    ALAINBXR ALALF1A  ALAREC
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI63084

       UP19/05/21 P F905

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.5.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 June 2019