IBM Support

PK84767: BYPASS CERTAIN ERROR CONDITION CHECKS WHEN UNDERLYING VSAM DATASETS DO NOT EXIST FOR INDEXES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Currently during the job build process all objects must have an
    existing underlying VSAM dataset.  If the dataset does not exist
    message HAAB074E, 'Underlying VSAM file not found' is generated.
    
    This APAR will bypass the VSAM existence check for INDEXES if
    both the following conditions are true:
    
    1) The index is not eligible for an IMAGE COPY utility
       because COPY YES is not specified for the INDEX
    
    2) Only the IMAGE COPY utility was selected for that
       INDEX in the job build
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently during the job build process  *
    *                      all objects must have an existing       *
    *                      underlying VSAM dataset.  If the        *
    *                      dataset does not exist message          *
    *                      HAAB074E, 'Underlying VSAM file not     *
    *                      found' is generated.                    *
    *                      This APAR will bypass the VSAM          *
    *                      existence check for INDEXES if both     *
    *                      the following conditions are true:      *
    *                      1. The index is not eligible for an     *
    *                      IMAGE COPY utility because COPY YES is  *
    *                      not specified for the INDEX             *
    *                      2. Only the IMAGE COPY utility was      *
    *                      selected for that INDEX in the job      *
    *                      build                                   *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF.
    

APAR Information

  • APAR number

    PK84767

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-15

  • Closed date

    2009-07-07

  • Last modified date

    2009-08-03

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

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

    UK48166

Modules/Macros

  • HAA$SV26 HAAALA   HAAM076E
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R310 PSY UK48166

       UP09/07/14 P F907

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUWB","label":"IBM Db2 Automation Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 February 2021