Server work management

Server jobs are started with a job description that matches the name of the instance.

The instance library is checked first. If a job description that matches the name of the instance is not found in the instance library, then library QUSRRDARS is checked. If a job description by that name is still not found, then job description QOND400 in library QRDARS is used (and can be changed if necessary).

The job description controls the following attributes of the server job:
  • JOBQ
  • JOBPTY
  • OUTPTY
  • PRTDEV
  • OUTQ
  • INLLIBL
  • LOG
  • LOGCLPGM
  • INQMSGRPY
  • HOLD
  • DATE
  • SWS
  • JOBMSGQMX
  • JOBMSGQFL

For example, if you want to change the job queue that instance TEST uses, you create a job description named TEST in the TEST library that specifies the job queue you want to use.

To change the run priority of the server jobs, you must add a routing entry to the subsystem. The server job is always submitted with routing data QRLMSERVER. To change the run priority of all server jobs for all instances to 40, you could add the following routing entry to subsystem QSYSWRK. (You must choose a sequence number (SEQNBR) that is not already in use.)

ADDRTGE SBSD(QSYSWRK) SEQNBR(1841) CMPVAL(QRLMSERVER) PGM(QSYS/QCMD) 
   CLS(QSYS/QSYSCLS40)

After making this change, you must stop and restart all your servers.