You could setup a user (example CDAUSR) and then code USER=CDAUSR on the jobcard.
If you have RACF as an ESM (assume same concept for other ISV ESMs), then define a profile in the SURROGAT Class called CDAUSR.SUBMIT with a UACC(NONE). Then PERMIT either your ID or a suitable RACF Group READ access to the CDAUSR.SUBMIT profile in the SURROGAT Class which will then allow you to submit on behalf of that userid. You will then still have to create a /u/CDAUSR home directory with the ~/gdk files but only just for the CDAUSER id Obviously, CDAUSR will also need the required access to whatever resource(s) you are restoring to/from ...... Roger On Tue, 12 May 2026 17:54:44 -0500, Wendell Lovewell <[email protected]> wrote: >The job below will restore a file backed up logically by ADRDSSU, if it is >submitted with the requisite files in the submitting user's home directory: > >~/gdk/config.json >~/gdk/gdkkeyf.json >~/gdk/providers/AZURE.json > >//CDARESTF JOB CLASS=B,MSGCLASS=L >//******************************************************************** >//* RESTORE A DATASET FROM AZURE LOGICAL DUMP OF A SPECIFIC VOLUME >//******************************************************************** >//RESTFL EXEC PGM=ADRDSSU,REGION=0M >//SYSPRINT DD SYSOUT=L >//SYSIN DD * > RESTORE SPHERE - > DATASET(INCLUDE(MY.TEST.DATA)) - > LOG(DEBUG) - > CLOUD(AZURE) - > CONTAINER('dssdump') - > OBJECTPREFIX('TEST/M04.LOGICAL.VOL001') - > CDAPROVIDERFILE - > REPLACE >// > >However, I don't want to set up those files into everyone's home folder. > >Is there a way to use a common/production set of files instead of requiring >the files in ~/gdk? > >I'd prefer to store them under /usr/lpp/dfsms/gdk and let them be shared. > >Also, there is a userid in the Credentials section of the gdkkeyf.json file. >Are there an consequences of other users sharing a file with a different >userid there? > >Thanks for your help. > >~ Wendell > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
