IBM Support

OA55724: A MOVE OR COPY FROM OPTION 3.3 OR 3.4 USING A TO DATA SET THAT IS A GDG WITH A POSITIVE GENERATION (+n) FAILS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • From ISPF Option 3.3, if you use the C (copy) or M (move)
    option, and then enter a GDG with a positive generation as the
    To data set on the To Data Set Panel like this:
    
    To Other Partitioned or Sequential Data Set:
       Name  . . . . . . . private.gdg(+1)
    
    the move/copy fails with message ISRD024 (Request failed -
    Allocation/deallocation failed. Press Help for more
    information.).
    
    From ISPF Option 3.4, if you use the CO (copy) or the MO (move)
    line command on a line in the data set list, and then enter a
    GDG with a positive generation as the To data set on the
    MOVE/COPY Entry Panel like this:
    
    To Other Data Set Name
       Name  . . . . . . . private.gdg(+1)
    
    the new generation is created, but the move/copy to the new
    generation fails with message ISRD024 (Request failed -
    Allocation/deallocation failed. Press Help for more
    information.).
    
    Message ISRD014 can also occur.
    

Local fix

  • Use the GxxxxVyy syntax instead of the (+1) syntax to specify
    the generation.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All ISPF Users.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a user enters the C or M option in the Move/Copy        *
    * Utility and specifies a To Data Set Name that is a           *
    * generation data set with a positive generation number, the   *
    * new generation is not created and error message ISRD024 is   *
    * issued.                                                      *
    *                                                              *
    * When a user enters the CO or MO line command in a data set   *
    * list and specifies a To Data Set Name that is a generation   *
    * data set with a positive generation number, the new          *
    * generation is created, but the data is not copied/moved to   *
    * the new generation and error message ISRD024 is issued.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the provided PTF.                                      *
    ****************************************************************
    In the option 3.3 processing, ISRUMC is incorrectly terminating
    the move/copy when the GDG generation to be created is not
    located.
    
    In the option 3.4 processing, after allocating the data set with
    the positive generation number, ISRUDMS is issuing an LMINIT for
    the data set using the same positive generation number.  This
    LMINIT is failing.
    

Problem conclusion

  • After the data set  with the positive generation is allocated,
    it becomes the most recently allocated generation and it needs
    to be referenced as generation zero.  Therefore:
    
    In the option 3.3 processing, ISRUMC is modified to continue
    with the move/copy when the GDG generation to be created is not
    located because this is to be expected.  In addition, ISRTALLO
    is modified so that the new generation is referenced using a
    generation number of zero after it is allocated.
    
    In the option 3.4 processing, ISRUDMS is modified to issue the
    LMINIT for the newly allocated generation using a generation
    number of zero.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA55724

  • Reported component name

    ISPF Z/OS PDF&S

  • Reported component ID

    565504202

  • Reported release

    P02

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-14

  • Closed date

    2018-07-31

  • Last modified date

    2018-09-04

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

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

    UA96973 UA96978

Modules/Macros

  • ISRUDMS  ISRUMC   ISRTALLO
    

Fix information

  • Fixed component name

    ISPF Z/OS PDF&S

  • Fixed component ID

    565504202

Applicable component levels

  • RR02 PSY UA96978

       UP18/08/17 P F808

  • RP02 PSY UA96973

       UP18/08/17 P F808

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":"P02","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCDKBQ","label":"Program Development Facility (PDF)"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"P02","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 September 2018