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 active jobs using the WRKACTJOB command

The WRKACTJOB command shows all active jobs. All server jobs are displayed, as well as the listener job.

The following figures show a sample status using the WRKACTJOB command. Only jobs related to the server are shown in these figures. You must press F14 to see the available prestart jobs.

The following types of jobs are shown in the figures.

1 - Listener job
2 - Prestarted server jobs

 
                         Work with Active Jobs                AS400597
                                                    04/25/97  10:25:40
CPU %:   3.1   Elapsed time:  21:38:40  Active jobs:  77
 
Type options, press Enter.
  2=Change   3=Hold   4=End   5=Work with   6=Release   7=Display message
  8=Work with spooled files   13=Disconnect ...
 
Opt  Subsystem/Job  User     Type  CPU %  Function          Status
           .
___   QUSRWRK        QSYS        SBS      .0                   DEQW
           .
___ 1
        QRWTLSTN     QUSER       BCH      .0                   SELW
           .
           .
___ 2
        QRWTSRVR     QUSER       PJ       .0                   TIMW
___     QRWTSRVR     QUSER       PJ       .0                   TIMW
___     QRWTSRVR     QUSER       PJ       .0                   TIMW
___     QRWTSRVR     QUSER       PJ       .0                   TIMW
___     QRWTSRVR     QUSER       PJ       .0                   TIMW
           .                                                            More...

The following types of jobs are shown:

PJ: The prestarted server jobs.
SBS: The subsystem monitor jobs.
BCH: The listener job.

Display active user jobs using the WRKUSRJOB command

The command WRKUSRJOB USER(QUSER) STATUS(*ACTIVE) will display all active server jobs running under QUSER. This includes the DDM listener and all DDM server jobs. This command might be preferable, in that it will list fewer jobs for you to look through to find the DDM-related ones.