Previous Topic: General PrinciplesNext Topic: Work Management Objects in QGPL


Shipped Work Management Objects

OS/400 is shipped with a default set of Work Management objects (for example, QBATCH, QPRINT, QINTER). If you are a new user, use these to start and then modify them over time. The commands to make the modifications should be stored in a CL program or a spool reader so that they can be reapplied at any time. This is necessary in particular for the changes that are ‘undone’ by reinstalling new releases of the operating system; for instance, overrides to print files in QSYS.

Such a program should includes changes to OS/400 system values made with the OS/400 Change System value (CHGSYSVAL) command, although such changes are preserved when a new release of the operating system is installed. These include:

All files in the system library QSYS and other utility libraries should be given the default forms size for your installation. For example:

CHGPRTF FILE(QSYS/*ALL) PAGESIZE(88 132) LPI(8) +

CPI(15) OVRFLW(80) RPLUNPRT(*YES)

The files used for compilation listings should be held (set to HOLD(*YES)), so that listings can be examined online, using the browse scan facility of the OS/400 Start SEU (STRSEU) command. They should not normally need printing:

CHGPRTF FILE(QPDDSSRC) SCHEDULE(*FILEEND) HOLD(*YES)

CHGPRTF FILE(QSYSPRT) SCHEDULE(*FILEEND) HOLD(*YES)

Job logs and program dumps should be directed to a separate queue. They can then be found easily, but will not normally be printed.

For example:

CRTOUTQ OUTQ(QGPL/YQJOBLOG) DSPDTA(*YES) +

TEXT(‘Job logs & dump output’)

CHGPRTF FILE(QSYS/QPJOBLOG) OUTQ(YQJOBLOG) HOLD(*YES)

CHGPRTF FILE(QSYS/QPPGMDMP) OUTQ(YQJOBLOG) HOLD(*YES)

CHGPRTF FILE(QSYS/QPSRVDMP) OUTQ(YQJOBLOG) HOLD(*YES)

CHGPRTF FILE(QSYS/QPDSPJOB) OUTQ(YQJOBLOG) HOLD(*YES)