IBM Support

PM11431: U073 ABEND WHEN USING RESOLVE STARTED UOW AND JOB ENDS BEFORE CURRENT LOG.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An U=73 ABEND occurs when a begin span log record is found
    without an end span log record. This should not happen in a
    normal situation; however, do to the processing for Resolve
    started UOW some circumstances have been found to cause this
    issue. Resolve started UOW will cause Log Analysis processing to
    either end on a log boundary or at the current time. It is when
    the Resolve started UOW ends on a log boundary this can become
    an issue. This fix will modify the processing to ignore the
    begin span records that are not needed for the reporting
    process.
    

Local fix

  • Turn off Resolve stared UOW and expand the end reporting time.
    If this happens when using a RBA range, modify the end RBA range
    to not be on the log boundary. If this happens during other
    processing - it may be resolved by just restarting the job as
    the end span would be written by then.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An U=73 ABEND occurs when a begin span  *
    *                      log record is found without an end      *
    *                      span log record. This should not happen *
    *                      in a normal situation; however, do to   *
    *                      the processing for Resolve started UOW  *
    *                      some circumstances have been found to   *
    *                      cause this issue. Resolve started UOW   *
    *                      will cause Log Analysis processing to   *
    *                      either end on a log boundary or at      *
    *                      the current time. It is when the        *
    *                      Resolve started UOW ends on a log       *
    *                      boundary this can become an issue.      *
    *                      This fix will modify the processing to  *
    *                      ignore the begin span records that are  *
    *                      not needed for the reporting process.   *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM11431

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-04-01

  • Closed date

    2010-05-04

  • Last modified date

    2010-06-03

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

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

Modules/Macros

  •    ALAA07
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK56716

       UP10/05/12 P F005

  • R320 PSY UK56717

       UP10/05/12 P F005

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

Document Information

Modified date:
31 March 2021