II08976: * IMPORTANT INFORMATION FOR ADSM VERSION 2 RELEASE 1 HSM CLIENT CUSTOMERS *

APAR status

• Closed as canceled.

Error description

• 565511901 R210 ADSM MVS V2 server
  576556401 R210 ADSM AIX V2 server
  Prior to General Availability for the ADSM Version 2 Release 1
  AIX HSM product, IBM ADSM development discovered and corrected a
  problem in the management of files migrated to the version 2
  ADSM Server from the AIX client.
  If you are planning to use the AIX client hierarchical storage
  management (HSM) function, you should ensure that your version 2
  server level is the same as that provided at the time of HSM
  client general availability.
  The proper server level is Version 2 Release 1 Level 0.2/0.2.
  Your server level is displayed when the server starts or in
  response QUERY STATUS command.
  Since the Version 2 ADSM product (without client HSM functions)
  was generally available on August 25th, 1995, it is possible
  that you have a version 2 server installed with a level below
  the one described above.
  Before using ADSM Version 2 AIX client HSM functions, please
  ensure that your server is at Level 0.2/0.2 or higher. This is
  the proper server level for HSM client general availability.
  Problem Description:
  IBM ADSM Development discovered and corrected an error in the
  server code that automatically copies HSM client migrated files
  when they are backed up or migrated from the client.
  When a AIX client file has been HSM migrated to the ADSM server,
  and a subsequent request is made to backup or archive the file,
  the server automatically copies the migrated file data to the
  appropriate backup or archive storage pool without requiring
  that the file data be recalled to the client. In the rare
  instance that the migrated file spans disk or tape volumes on
  the ADSM server, the coding error causes data to be lost during
  the backup or archive operation.
  This error only affects files that are backed up or archived
  after HSM migration. If the management class for the file has
  MIGREQUIRESBKUP set to YES, and the file has not been backed up
  or archived since migration, the backup copy will not be
  affected by the error.
  

Local fix

Problem summary

Problem conclusion

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

Applicable component levels