IBM Support

PI17226: FILE MANAGER DSG BATCH JOB DOES NOT DETECT IF A DATASET ALREADY EXISTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A user has the VOLSEROUT=xxxxxx in the DSG batch job. With the
    VOLSEROUT=xxxxxx value, FM does not find the dataset with that
    name on that volume, and so attempts to DEFINE it, getting the
    duplicate dataset messages. However, as per FM's design, the
    dataset was created prior to the creation of the batch job, and
    it is on a different volume.
    

Local fix

  • Remove the VOLSEROUT parm.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: File Manager Users of the DSC and DSG        *
    *                 functions in batch.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the Data Set Create function *
    *                      (Option 3.1) and batch is specified for *
    *                      a VSAM dataset, File Manager            *
    *                      incorrectly includes the VOLSEROUT=     *
    *                      parameter in the DSG batch control      *
    *                      statements.                             *
    *                      A similar problem exists for Data Set   *
    *                      Copy (DSC).                             *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    File Manager propagates any volume serial number from the
    DSG (3.1) entry panel and generates a VOLSEROUT= parameter,
    even if the dataset is VSAM.
    It should only be used for a non-VSAM uncatalogued data
    set.
    For DSC (3.3) the volume serial number from the 'To' data set
    entry panel is incorrectly propagated.
    

Problem conclusion

  • File Manager has been updated to correct the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI17226

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-05-02

  • Closed date

    2014-08-14

  • Last modified date

    2015-03-12

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

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

    PI36858

Modules/Macros

  • FMN0LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC10 PSY UI20501

       UP14/08/19 P F408

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
12 March 2015