Work With Active Prestart Jobs
This blog will review features of Work with Active Jobs (WRKACTJOB) that make finding prestart jobs easier.
By Dawn May09/05/2018
The subsystem parameter allows you to display the jobs in a specific subsystem. This is useful if you separate your jobs into different subsystems, and in fact, this support is a good reason why you may want to separate your prestart jobs into different subsystems. It can make finding the jobs related to specific users or applications easier.
The sequence parameter allows you to specify an ordering when you display the active jobs. *SBS is the default and orders the jobs by subsystem. Using *JOB orders the jobs by job name - this is the only way you can get the list of jobs in alphabetical order. *CURUSR orders the jobs by the current user profile, which is the same as using F16 on that column. There are various other SEQ parameter options you can use, allowing you to sort on that particular column for the starting display.
The job name parameter allows you to specify the name of the jobs to display and it also supports generic job names. Thus, you could display only the jobs who’s name starts with QZDASO*.
- Entered system
- Subsystem and subsystem library
- Server name
- Job user identity
- Database CPU time and percentage
- Disk I/O rate and count
- Synchronous disk I/O rate
- Total disk I/O count
- Total CPU and database CPU time
- Page fault rate
Dawn May is an IBM i consultant. She owns Dawn May Consulting, LLC in the Greater Boston area. Dawn is a former IBM senior technical staff member.