CHANGING A LIBRARY’S OWNER and ALL of its OBJECTS

Many times libraries have been created and later realized it has the wrong owner, or you decide to use a new authority scheme in your company and want to change the owner and authority.  It takes a long time to change all the effected objects and the library owner. I created a simple utility command to do the work for you. It only requires 1 CL PGM, 1 CMD and 1 file. In short the CL command will build a file of all the objects in a library and then change the owner of all the objects to the new owner you want them to be. You even have an option to save or revoke the authority of the old owner too.

Just compile the CL Program, Command, and create the File below all in your favorite Utility library, or personal library and give it a try

CL PROGRAM

PGM        PARM(&LIB &NEWOWNER &CURAUT) 
DCLF       FILE(YOURLIB/OBJOWN)
DCL        VAR(&LIB) TYPE(*CHAR) LEN(10)
DCL        VAR(&CURAUT) TYPE(*CHAR) LEN(10)
DCL        VAR(&NEWOWNER) TYPE(*CHAR) LEN(10)
DSPOBJD    OBJ(&LIB/*ALL) OBJTYPE(*ALL) +
         OUTPUT(*OUTFILE) OUTFILE(YOURLIB/OBJOWN)
RCVF:       RCVF       DEV(*FILE)
MONMSG     MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
CHGOBJOWN  OBJ(&ODLBNM/&ODOBNM) OBJTYPE(&ODOBTP) +
      NEWOWN(&NEWOWNER) CUROWNAUT(&CURAUT)
MONMSG     MSGID(CPF0000)
GOTO       CMDLBL(RCVF)                               
END:        ENDPGM

COMMAND

CMD        PROMPT(‘Change Library Owner’)
PARM       KWD(LIB) TYPE(*CHAR) LEN(10) MIN(1) +
     PROMPT(‘Library’) 
PARM       KWD(NEWOWN) TYPE(*CHAR) LEN(10) MIN(1) +
     PROMPT(‘New Owner’)
PARM       KWD(CURAUT) TYPE(*CHAR) LEN(10) RSTD(*YES) +
     VALUES(‘*SAME’ ‘*REVOKE’) MIN(1)  PROMPT(‘Current Owner Authority’)

FILE

DSPOBJD    OBJ(YOURLIB/*ALL) OBJTYPE(*ALL) +
         OUTPUT(*OUTFILE) OUTFILE(YOURLIB/OBJOWN)

Just run this command manually one time and you will have your file created.

Share this:

• Click to share on Facebook (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• More

• Click to share on Pinterest (Opens in new window)
• Click to share on Pocket (Opens in new window)

‹ Finding Local Ports in use in an IBM i environment

Release levels and PTFs (January 2019) ›

6 comments on “CHANGING A LIBRARY’S OWNER and ALL of its OBJECTS”

1. Rohit Sharma says:

   January 30, 2019 at 5:01 pm

   You could also use IFS naming to make these change with a single command.
   For example, to change the owner of all *PGM objects under library MYLIB, use command:
   CHGOWN OBJ(‘/QSYS.LIB/MYLIB.LIB/*.PGM’) NEWOWN(someuser).

   Similarly, to change all files use “/QSYS.LIB/MYLIB.LIB/*.FILE”, and for all objects use “/QSYS.LIB/MYLIB.LIB/*”

   Reply
2. Mark S. Waterbury says:

   January 30, 2019 at 5:02 pm

   This is stupid. Just use the built-in OS/400 command CHGOWN as follows:

   CHGOWN ‘/QSYS,LIB/libname.LIB’ NEWOWN(newowner)

   to change the owner of the *LIB and then issue:

   CHGOWN ‘/QSYS,LIB/libname.LIB/*’ NEWOWN(newowner)

   to change the owner of all of the objects in that library.

   Done!

   Reply
3. Rohit Sharma says:

   January 30, 2019 at 5:06 pm

   You could also use IFS naming to make changes with a single command.
   For example, to change all program objects under library MYLIB:
   CHGOWN OBJ(‘/QSYS.LIB/MYLIB.LIB/*.PGM’) NEWOWN(someuser)
   Similarly, you can use “*.FILE” for all file objects, “*” for all objects, etc.

   Reply
4. Rohit Sharma says:

   January 30, 2019 at 5:07 pm

   You could also use IFS naming to make changes with a single command.

   For example, to change all program objects under library MYLIB:
   CHGOWN OBJ(‘/QSYS.LIB/MYLIB.LIB/*.PGM’) NEWOWN(someuser)

   Similarly, you can use “*.FILE” for all file objects, “*” for all objects, etc.

   Reply
5. John R. Bromm says:

   January 30, 2019 at 5:29 pm

   I probably would have just created a user defined option in PDM to do this.

   Reply
6. DB says:

   January 30, 2019 at 6:51 pm

   One small but useful tip is to use IBM’s own model files for things like this. DSPOBJD uses QADSPOBJ. This way you can compile your programs without having to manually create outfiles first.

   Just add the following line right after your existing line 1 (the one that start with “PGM”):
   DCLF FILE(QSYS/QADSPOBJ)

   Then add the following line right before the line that begins with “RCVF”:
   OVRDBF FILE(QADSPOBJ) TOFILE(YOURLIB/OBJOWN)

   Reply