Job log server
Typically the job log server writes a job's job log to a spooled file. You can route the job log to a printer or to an outfile, (if specified to do so by using the QMHCTLJL, Control job log API), however this is not the recommended method for producing job logs.
You can view information about the job log server via iSeries™ Navigator from the Work Management > Server Jobs display, or the Work Management > Active Jobs display. (To make it easier to identify the jobs running on the job log server, make sure that you include the Server column in your display.)
The maximum number of job log servers that can be active at one time is 30. You start additional job log servers and manage them in the same way as other servers in your system. This is done by using the character-based interface command STRLOGSVR.
How the job log server starts
By default, the job log server will start automatically when the QSYSWRK subsystem starts. The server ends whenever the QSYSWRK subsystem is ended.
The Start Job Log Server (STRLOGSVR) command starts the job log server. The job log server writes job logs for jobs that are in a job log pending state and that do not have the attribute of *PND. The job log server writes a job's job log either to a spooled file, to a printer, or to an outfile, (if specified to do so by using the QMHCTLJL, Control job log API).
Parent topic:
Job logsRelated concepts
How job logs are created Job log pending Job log characteristics Interactive job logs QHST History Log Spooled filesRelated tasks
Reconfiguring the job log server Starting the job log server Ending the job log serverRelated information
Control Job Log Output (QMHCTLJL) API