Transferring objects between auxiliary storage pools
You can move entire libraries or folders from one auxiliary storage pools (ASPs) to another. Special procedures are used to move a library that contains journals because a journal and the journaled objects must be in the same basic user ASP or the same independent ASP group.
The Working with nonlibrary user auxiliary storage pools topic discusses the procedures for working with nonlibrary user ASPs.
You cannot directly move objects between ASPs because the Move Object (MOVOBJ) command and the Move Document (MOVDOC) command move only the pointer to the object. They do not physically copy data from one location to another. In general, follow these steps to move an object to a different ASP:
- Sign as QSECOFR.
- Save the object and its private authorities by specifying the PVTAUT(*YES) parameter.
- Delete the object from the system. If you are transferring the object from one independent ASP to another independent ASP, this step is not required.
- Restore the object to the target ASP by using the RSTASP parameter on the RSTxxx command. If you are restoring objects to an independent ASP, use the RSTASPDEV parameter. If you need to restore the private authorities of the object, use the PVTAUT(*YES) parameter.
These restrictions apply when specifying the RSTASP parameter for a basic user ASP:
- When you attempt to restore an object to a different basic ASP from its library, the ASP must be a nonlibrary user ASP and the object must be a journal, a journal receiver, or a save file.
- For journals, journal receivers, and save files, if a library exists on the ASP, you receive an error message and the object is not restored.
- For other object types, the object is restored to the ASP that contains the library.
- If you try to restore an object to a basic user ASP by explicitly specifying the user ASP that you want for the RSTASP parameter and the designated user ASP does not exist, you receive a message. The object is not restored.
- If you restore an object and specify RSTASP(*SAVASP), and if the basic ASP from which the object was saved no longer exists, the object is restored to the system ASP. You receive an informational message.
If you try to restore an object to an independent ASP by explicitly specifying the independent ASP that you want for the RSTASPDEV parameter and the designated independent ASP does not exist, you receive a message. The object is not restored.