Troubleshooting
Problem
This document explains how authorities to objects are handled when saving and restoring libraries and objects between *SYSBAS and IASPs.
Resolving The Problem
When a library residing in *SYSBAS is saved using SAVLIB, only *PUBLIC and the owner of the object will have their authorities saved. After that library is restored to an IASP, the objects will restore just fine; however, not all of the authorities will be restored. If the library has the same name between *SYSBAS and the IASP, RSTUSRPRF USRPRF(*ALL) and RSTAUT SAVASPDEV(*SYSBAS) RSTASPDEV(iasp-name) can be run and that should pick up the missing authorities.
If the restore of the library onto the IASP has a different library name, GRTOBJAUT must be used to get the authorities back.
Note: In R610 and above, there is an option to have the private authorities saved with the object.
Message CPF2208 followed by message CPF3736 can be posted for all objects not present on IASP. If this message is logged, only authorities to object present on IASP are restored and a RSTAUT RSTASPDEV(*SYSBAS) is required.
Historical Number
460924048
Was this topic helpful?
Document Information
Modified date:
11 November 2019
UID
nas8N1014175