IBM Support

PM80632: Member lost from z/OS project in RDz when using copy/paste/replace

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Rational Developers for System z z/OS projects gets changed w/o
    notifying the developer, thus causing confusion and loss of work
    
    This problem shows when the copy is done from outside (e.g. from
    
    ?hlq?.PROJECTX.COBOL) to ?hlq?.PROJECTY.COBOL)
    
    Recreation Steps:
    1)  Use/create the PDS datasets/members:
       ?hlq?.PROJECTX.COBOL(HELLO)
       ?hlq?.PROJECTX.COPYLIB(HELLOCP1)
       ?hlq?.PROJECTX.COPYLIB(HELLOCP2)
       ?hlq?.PROJECTY.COPYLIB(HELLOCP1)
    2) Create a remote z/OS Project 'myProject'
    3) Create a subproject 'mySubProject'
    4) Add the member ?hlq?.PROJECTX.COBOL(HELLO) to mySubProject
       and the 2 members ?hlq?.PROJECTX.COPYLIB(HELLOCP*)
    5) Observe that the source and the copy members are present in
       the 'z/OS Projects' view for mySubProject
    6) Now in the 'Remote Explorer' view use RDz drag and drop to
       copy and replace from PDS ?hlq?.PROJECTY.COPYLIB(HELLOCP1)
       to PDS ?HLQ?.PROJECTX.COPYLIB(HELLOCP1)
    7) Observe that the member ?hlq?.PROJECTX.COPYLIB(HELLOCP1)
       disappears from mySubProject in the 'z/OS Projects' view
    
    Note:
    In all cases below the member does ?not? disappear from the
    project
    - the PDS ?hlq?.PROJECTX.COBOL  is attached to the project
    - the member is copy / replaced from ISPF
    - when USERA has the project in his RDz and another USERB
      performs the drag/drop replace
    

Local fix

Problem summary

  • Currently, when you add a member (say MEM1) to a subproject and
    then later from Remote Systems view overwrite MEM1 with another
    file called MEM1, the overwrite is treated as  1) a deletion of
    the original MEM1 and then 2) the creation of a new member
    called MEM1.  The old MEM1 is deleted and therefore removed from
    the subproject but when the new MEM1 is created, we do not add
    the new MEM1 to the subproject.
    

Problem conclusion

  • The fix for this APAR is to add the new MEM1 to the subproject
    as expected.
    
     The problem listed in this APAR has been resolved with
    IBM Rational Developer for System z V8.5.1.1 Fix Pack which
    is available from the Recommended Fixes support download page:
    http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM80632

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-15

  • Closed date

    2013-03-21

  • Last modified date

    2013-03-21

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

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

Fix information

  • Fixed component name

    RATL DEV FOR SY

  • Fixed component ID

    5724T0700

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 8.0.1

Reference #: PM80632

Modified date: 21 March 2013