CHGSYSLIBL

[Caroline Koh]

Hi,

I have a question on system library list.

Apparently, I have an application library place on top of my system library
list (i.e. defined in the system value, QSYSLIBL). This library contains
commands such as CHGJOB, CHGOUTQ, which are modified from the original QSYS
library. All jobs in the system is supposed to use the commands in this
particular library.

However, I have a particular application which needs to use the commands
specifically from the QSYS (i.e. the original commands). I understand that I
can make use of the command CHGSYSLIBL to remove the library on top. Alas, I
do not have the program source code to hard code this command in the program
for these jobs. Can I control the system library list at the job description
or subsystem level? How can routing data benefit in this case?

Appreciate your expert inputs. Thank you.

Carol

[Kirk Goins]

How about moving it out of SYSLIBL to USRLIBL. Depending on how your users JOBDs
are setup (*SYSVAL or each lib listed) you could assign a custom JOBD to the job
that needs the original cmds.

[Mark Ford]

Yes, you can change the routing entries on the required subsystem(s) to call
a customised routing program which can do a CHGSYSLIBL xxxx *REMOVE. IIRC
the program should finish with a TFRCTL xxx/xxx to transfer control the
whatever the program was that should have been called for the routing step
in the first place.

The CHGSYSLIBL command normally has restricted authority, so you will need
to make sure the user profiles involved have the required authority, or run
the custom routing program with adopted authority of a suitable profile.

Mark.

"Caroline Koh" <hwe...@hotmail.com> wrote in message
news:a8gp43$nh6$1...@dahlia.singnet.com.sg...

[AlexS]

Caroline,

I would try following:
- rename your program object
- create CL wrapper program (same name and parameter list as original
program) which will replace libl with what you need and which is calling
renamed program
- put wrapper program into same lib (try to keep structure intact)

In case something goes wrong you always can revert back (by deleting wrapper
and renaming old program to original name)

It won't work if you have to deal with service program, but for standard
situation it should be Ok.

HTH
Alex

"Caroline Koh" <hwe...@hotmail.com> wrote in message
news:a8gp43$nh6$1...@dahlia.singnet.com.sg...