Re: Write Joblog to a different OUTQ

Having read the other responses to this thread I thought I would offer one perspective.

Having a user library (meaning non-IBM) at the top of the system library list is a time honored way to override default behaviors such as the one you are suggesting here:

1) Create the library and secure it so not just anyone can drop objects into it. Lacking a different naming convention I call this one OVRSYS. Make sure all users can use all the objects in it.

2) Change the system value QSYSLIBL to have this library at the top of your system library list, above all the IBM delivered libraries.

3) Create your duplicate of file QPJOBLOG print file into this library and make the change as indicated by Scott. I suggest you create a source file in this library and create a CL program in it. Put a line in the program with the exact command you use to make the change. Now you have recorded any/all changes you make to IBM (or your own) delivered objects. Include changes to subsystems, outqs, other print files, system values and the like. Auditors love this since it provides a way to put it all back after an OS upgrade or disaster, but also clearly shows what was done to the system.

4) When you are done with year end processing reverse the change to the print file, and you are now back to normal. I would put a comment in your new program to indicate why the change was done and reversed for your own sanity and those that might follow you.

Now you have a completely documented approach, one that can be repeated, and is clear to anyone that takes the time to look. I always put all the custom work management objects such as subsystem descriptions (even if I modify the IBM version, copy it into this library and make the change there), classes, routing programs and the like. I especially make sure to put changes to memory/shared pools in there. Now when an OS upgrade comes along your changes will survive the upgrade and be fully documented for the bargain.

Others may argue with this approach but it has passed many a SOX/IT audit and provides clear concise documentation on any/all changes that were made to the system, and you won't have to figure out how you did it last year, when the new year rolls around again in 356 days (2012 is a leap year)

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 12/21/2011 4:57 PM, Sam_L wrote:

I have a bunch of year end jobs where I'd like to route the joblog to
somewhere other than QEZJOBLOG. Preferably without changing the jobs.

From my research, job logs go to the OUTQ specified in the the QPJOBLOG
printer file. The spooling system finds the first QPJOBLOG in the
library list and uses that, and the first QPJOBLOG is in QSYS, which is
at the top of the library list. Thus it seems very hard to reroute job
logs.

If I create a temporary library, copy QPJOBLOG there, change it, and put
that library at the top of the library list, I can make it work. Code
like this:
PGM
CHGSYSLIBL LIB(SAM_TEMP)
dsplibl
ENDPGM

But that means I would have to change every job.

I suppose I could permanently move QPJOBLOG to somewhere in the user
portion of the library list and control it by manipulating the library
list through JOBDs.

Has anyone else come up with a solution? How have you done it?

Thanks, Sam
--