Identify server jobs
If you look at the server jobs started on the system, you might find it difficult to relate a server job to a certain application requester job or to a particular PC client. Being able to identify a particular job is a prerequisite to investigating problems and gathering performance data. iSeries™ Navigator provides support for these tasks that make the job much easier.
- iSeries job names
The job name used on the iSeries consists of three parts: the simple job name, user ID, and job number (ascending order).
- Display server jobs
There are several methods that can be used to aid in identifying server jobs. One method is to use the WRKACTJOB command. Another method is to use the WRKUSRJOB command. A third method is to display the history log to determine which job is being used by which client user.
- Display the history log
Each time a client user establishes a successful connection with a server job, that job is swapped to run under the profile of that client user. To determine which job is associated with a particular client user, you can display the history log using the DSPLOG command.
Parent topic:
Manage the TCP/IP server