IBM Support

PM38730: POSSIBLE SKIPPED RECORDS OR ABENDU088 FOR SOME COMBINATION OF SPANNED RECORDS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a middle spanned or end spanned record has certain values at
    the same offsets as the record types of the begin spanned
    record then the record could be bypassed if needed.  Under
    certain conditions if the begin span record had a particular
    record length, this could result in U=88 abend.  This would only
    occur if PM25628 has been applied.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a middle spanned or end spanned      *
    *                      record has certain values at the same   *
    *                      offsets as the record types of the      *
    *                      begin spanned record then the record    *
    *                      could be bypassed if needed.  Under     *
    *                      certain conditions if the begin span    *
    *                      record had a particular record length,  *
    *                      this could result in U=88 abend.        *
    *                      This would only occur if PM25628        *
    *                      has been applied.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM38730

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-05-09

  • Closed date

    2011-05-24

  • Last modified date

    2011-06-02

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

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

    UK68088

Modules/Macros

  •    ALAGIC   ALALOGR
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R320 PSY UK68088

       UP11/06/01 P F105

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

Document Information

Modified date:
17 March 2021