IBM Support

PI59819: IF A CUSTOMER STORES THEIR OPTIONS MODULES IN RESLIB, AN IRT278EAND U4000 ABEND CAN RESULT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a customer decides to place their PRF options override
    modules in RESLIB, or in any dataset already allocated to the
    job, if the DDNAME allocated to the dataset is less than 8
    characters in length, the following messages are generated,
    followed by a U4000 abend:
    IEC130I xxx.. DD STATEMENT MISSING
    +IRT278E OPEN FAILED FOR IRTOPT DATA SET RC=08
    
    In the IEC130I message above, 'xxx' is the DDNAME the dataset is
    allocated to. If you do a hex display on the IEC130I message,
    you will see that the DDNAME is suffixed by x'00' bytes.
    

Local fix

  • Store your options override modules in a library not otherwise
    allocated to the job. PRF finds the IRT#OPT module through a
    standard LOAD macro, and reads the module to find the options
    override module data set. PRF then dynamically allocates that
    dataset, so it does not have to be directly allocated to the
    job.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Users of Program Restart Facility        *
    *                 V2R2 who place their inclusion options       *
    *                 modulesin RESLIB or in another dataset       *
    *                 directly allocated to the job.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a user places inclusion options      *
    *                      modules in a dataset directly allocated *
    *                      to the job, and the DDNAME associated   *
    *                      with the allocation contains less than  *
    *                      8 characters, the PRF allocation logic  *
    *                      will fail to format the DDNAME          *
    *                      correctly when opening the dataset. For *
    *                      instance, if the user places inclusion  *
    *                      options in RESLIB, and allocates RESLIB *
    *                      in a //DFSESL DD statement, and that    *
    *                      statement comes after any //DFSRESLB DD *
    *                      allocation, the customer will encounter *
    *                      this problem.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When PRF attempts to allocate the inclusion options modules, it
    looks for the dataset name of the options module, found in the
    IRTUSRL user library created at installation, and dynamically
    allocates the file. PRF then takes the DDNAME returned from the
    allocation request and uses it to open the dataset. If the
    dataset isn't otherwise allocated to the job, dynamic allocation
    creates an allocation with an 8-byte DDNAME. If the dataset *is*
    allocated to the job, dynamic allocation will return one of the
    DD names to which the dataset is allocated. If this DDNAME is
    less than 8 characters long, dynamic allocation does not pad the
    returned DDNAME. PRF mistakenly copies all 8 characters of the
    returned DDNAME into the DCB used to open the dataset. If the
    DDNAME is less than 8 characters, this results in invalid pad
    bytes for the DDNAME, leading to the error.
    

Problem conclusion

  • The Program Restart Facility will blank-pad DDNAMEs returned
    from dynamic allocation prior to attempting to using the DDNAME
    to open the associated dataset.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI59819

  • Reported component name

    IMS PGM RESTART

  • Reported component ID

    5655E1400

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-29

  • Closed date

    2016-05-19

  • Last modified date

    2016-06-02

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

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

    UI38027

Modules/Macros

  • IRTA63P0 IRTDDA10
    

Fix information

  • Fixed component name

    IMS PGM RESTART

  • Fixed component ID

    5655E1400

Applicable component levels

  • R220 PSY UI38027

       UP16/05/24 P F605

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":"220","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVHR","label":"IMS Program Restart Facility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
24 January 2022