IBM Support

PI94552: ISSUE WITH TRANSACTION REPORT IN DETAIL REPORT WHEN SKIP FORMATTING = Y

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If Skip Formatting (When Possible) parameter is set to Y and the
    Transaction Report is later requested to be created in the
    Detail Report step, it is possible that it will not be created
    or be created with incorrect data. When the Transaction Report
    is requested, the format step has to run. If there is no other
    need to perform the format step when the Transaction Report is
    requested, then the problem will occur. If there are other items
    already being used or also being added to the job that require
    formatting, then there will not be a problem.
    

Local fix

  • Set "Skip formatting (when possible)" to 'N'.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of ALA 350                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: If Skip Formatting (When Possible)      *
    *                      parameter is set to Y and the           *
    *                      Transaction Report is later             *
    *                      requested to be created in the          *
    *                      Detail Report step, it is possible      *
    *                      that it will not be created             *
    *                      or be created with incorrect data.      *
    *                      When the Transaction Report             *
    *                      is requested, the format step has       *
    *                      to run. If there is no other            *
    *                      need to perform the format step         *
    *                      when the Transaction Report is          *
    *                      requested, then the problem will        *
    *                      occur. If there are other items         *
    *                      already being used or also being        *
    *                      added to the job that require           *
    *                      formatting, then there will not         *
    *                      be a problem.                           *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94552

  • 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

    2018-03-01

  • Closed date

    2018-04-02

  • Last modified date

    2018-05-01

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

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

Modules/Macros

  •    ALAGL4
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI54922

       UP18/04/07 P F804

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:
31 March 2021