IBM Support

Steps to migrate library and IFS data from an IASP to the System ASP

How To


Summary

These are the steps to migrate data that is currently being stored in an IASP (Independent auxiliary storage pool) into the system ASP. This may be done when eliminating an IASP during a system migration or moving any existing data from IASP to SYSTEM ASP.

Objective

These are the steps to migrate data that is being stored in an IASP (Independent auxiliary storage pool) into the system ASP.  This can be done when eliminating an IASP during a system migration or moving any existing data from IASP to SYSTEM ASP.  The steps outlined in this document are for moving ALL data from the IASP.  A modified list of steps can be used to move just a portion of the data.

Steps

The following are the recommended steps to move data from the IASP to the SYSTEM ASP
  1.   Perform a GO SAVE 21 on the source system specifying the parm: Unmount file systems Y (yes)
  2.   DSPTAP to find the two sequence numbers for the QFILE objects on the tape
    • The second QFILE is needed for the RSTLIB of the IASP libraries to the system ASP
  3.  DSPTAP to find the two sequence numbers for the SAVyyyymmdd of the IFS objects on the tape
    • The second SAVyyyymmdd is for the save of the QDEFAULT.UDFS object for the IASP
  4. Build or recover the target system LIC, base i OS, GO RESTORE 21
    • The GO RESTORE 21 process will only restore the *SYSBASE objects (not any IASP objects saved)
  5. Create a directory on the target system to restore the IFS data into
    • In most cases ... it is recommended to create a directory of the same name as the IASP was using
    • This will keep the IFS path to these objects the same
  6. Restore the IASP libraries to the system asp using the QFILE object for these libraries
    • RSTLIB SAVLIB(*ALLUSR) DEV(TAPXX) SEQNBR(xxxxxx) MBROPT(*ALL) RSTASP(1)
    • Put in the SEQNBR of the QFILE object that represents the IASP libraries on the save media
    • There is a SMALL chance that there is a library in the IASP with the same name of a library in the system ASP... check the DSPTAP report to verify if this is the case and OMIT that library for now as unpredictable results can occur
  7. Restore the UDFS object from the IASP to the new system ASP directory of the chosen name
    • RST DEV('/qsys.lib/tapxxx.devd') OBJ(('/dev/iaspname/qdefault.udfs/*' *INCLUDE '/new_dir')) SEQNBR(xxxxx) ALWOBJDIF(*ALL)
    • Put in the SEQNBR of the SAVyyymmdd associated with the IASP portion of save.. this is usually at the end of the GO SAVE 21 tape volume
  8. If there are ANY private authorities on objects in the old IASP libraries or IASP directories... you must run RSTUSRPRF again and run RSTAUT again for these private authorities to be processed.
    • RSTUSRPRF DEV(TAPXX) USRPRF(*ALL) SECDTA(*PVTAUT)
    • RSTAUT SAVASPDEV(iaspname) RSTASPDEV(*SYSBAS) 
  9. Check  the libraries
  10. Check the directory with WRKLNK '/new_dir'  
Note:
If IFS data are restored to a different IASP then private authorities will not get linked by design. The recommended method to ensure all private authorities get linked when they are restored to a different IASP from which they were saved is to save the private authorities with the objects by specifying PVTAUT(*YES) on the save and then specify the PVTAUT(*YES) on the restore.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cwp6AAA","label":"Save Restore"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Document Information

Modified date:
31 July 2024

UID

ibm16602043

Page Feedback