IBM Support

PM63672: INCORRECT JOBNAME WHEN USING CONTROL CARD DATASET

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using a Control Card Dataset on an Automation Tool build,
    the jobname used in the members of the dataset may be incorrect.
    Specifically, the last jobname is used for all members in the
    dataset.  This can affect the mapping table database name when
    the &JOBNAME variable is used to create an online reorg mapping
    table. It can also affect the generated utility id when jobname
    is being used to generate the utility id. The jobnames are
    generated correctly if no Control Card Dataset is specified and
    the control cards are built inline in
    the JCL.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using a Control Card Dataset on    *
    *                      an Automation Tool build, the jobname   *
    *                      used in the members of the dataset may  *
    *                      be incorrect. Specifically, the last    *
    *                      jobname is used for all members in the  *
    *                      dataset.  This can affect the mapping   *
    *                      table database name when the &JOBNAME   *
    *                      variable is used to create an online    *
    *                      reorg mapping table. It can also affect *
    *                      the generated utility id when jobname   *
    *                      is being used to generate the utility   *
    *                      id. The jobnames are generated          *
    *                      correctly if no Control Card Dataset    *
    *                      is specified and the control cards are  *
    *                      built inline in the JCL.                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63672

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-01

  • Closed date

    2012-06-13

  • Last modified date

    2012-07-02

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

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

Modules/Macros

  • HAA#UOPC
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R310 PSY UK79554

       UP12/06/19 P F206

  • R410 PSY UK79555

       UP12/06/19 P F206

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