PH31606: IBM DEVELOPER FOR Z (IDZ) GETS LZOSDATASETMEMBER ERROR MESSAGE DUE TO MIGRATED LIBRARY

APAR status

• Closed as program error.

Error description

• All users of IDz v14.2 get two different symptoms related to
  migrated datasets -
  1- migrating a physical library causes LZOSDataSetMember message
  2- recalling a migrated library causes source member to vanish
  from the project view
  
  1-
  In the IDz client, make sure a z/OS Project is open and members
  exist.  In the Remote Systems view, right-click on source
  library and select "Migrate".  The icons change to a red square
  indicating "migrated".  Receive the following message in the
  Error Log -
  .
  ***
  com.ibm.ftt.i.actions.editorutils.LogicalResourceEditorUtils#get
  DefaultEditor(Object): could not handle file of type class
  com.ibm.ftt.projects.zos.zoslogical.impl.LZOSDataSetMember
  .
  
  2-
  Next, right-click on the source library in Remote Systems and
  select "HRECALL".  See the following message in the Error Log -
  .
  LZOSDataSetMemberOnlineState::internalSelfRemove - Physical file
  not found for XMEM.  The corresponding logical resource will be
  removed from parent Xproj
  .
  and the member disappears from the project.  The project is now
  empty (all members gone) even though the physical members still
  exist in the library.
  

Local fix

• manually add the members back to the z/OS project
  

Problem summary

• After migrating, then recalling, then expanding, then migrating
  and then expanding a PDS, members appear to go missing
  

Problem conclusion

• The underlying client model cache becomes corrupted after these
  migrate/recall operations resulting in the client incorrectly
  returning no members
  

Temporary fix

Comments

APAR Information

• 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

  EXP FOR Z/OS CL

• Fixed component ID

  5655EXP00

Applicable component levels