OW56979: ALIAS COPY FROM OPTION 3.4 LOSES ALIAS DESIGNATION.

APAR status

• Closed as fixed if next.

Error description

• When you use option 3.4 to copy members from one load module pds
  into another, the alias loses its alias designation and the
  ttr is not the same.  To reproduce this problem:
  1. Select a PDS load module from a data set list with an M
  for member list.
  2. From the member list panel, a member, and its aliases, and
  press enter.
  When you look at the member list of the data set you just copied
  to, you will notice that the alias file is blank, and ttrs ¬=.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of opt 3.4                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Copying alias entries via opt3.4 does   *
  *                      not preserve alias information.         *
  ****************************************************************
  * RECOMMENDATION: Use Opt3.3                                   *
  ****************************************************************
  The member copy facilities accessed via opt3.4 do not
  maintain alias information when copying load modules.
  This is documented in ISPF User's Guide Vol II.
  

Problem conclusion

Temporary fix

Comments

• The ISPF User's Guide Volume 2 outlines the conditions
  under which alias information is maintained during move
  or copy operations for load modules. This support is
  currently only available under the Move/Copy Utility - opt3.3
  The next release of ISPF expands this support to opt3.4,
  ISPF Workplace and the LMCOPY service.
  

APAR Information

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

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

Fix information

Applicable component levels

• RA02 PSN

     UP

• RC02 PSN

     UP