Determining in which pool a single job is running

 

If you have a job that is not performing as you expect you might want to check the memory pool in which the job is running. To determine in which pool a single job is running, use iSeries™ Navigator or the character based interface. After you have identified the pool in which the job is running, you can view memory pool information and determine if changes need to be made. For example, if too much paging occurs, possibly the memory pool needs to be larger. Another possibility for poor performance is that maybe too many other jobs are in the pool and you need to route this job to another pool.

 

Parent topic:

Managing memory pools

Related concepts
Memory pool allocation Memory pool activity level

Related information
Manage iSeries performance Basic performance tuning Applications for performance management Experience report: The Performance Adjuster (QPFRADJ)

 

iSeries Navigator

To use iSeries Navigator, follow the following instructions:

  1. In iSeries Navigator, expand My Connections > connection > Work Management > Active Jobs or Server Jobs, depending on the type of job you want to work with.

  2. Find the job whose memory pool you want to view.

  3. Right-click the Job Name and click Properties.

  4. Click the Resources tab. The Job Properties - Resources window displays specific information about the job's memory pool.

 

Character-based interface

Command: Work with job (WRKJOB)

Option 1: Display Job Status Attributes

The Subsystem pool ID field contains the name of the pool defined for the subsystem in which the job is running. This field is blank for jobs that are not active at the time the display is requested. It is also blank for system jobs (type SYS), subsystem monitor jobs (type SBS) that do not run within a subsystem and batch immediate jobs (BCI) that are running in the Base memory pool.

Command: Work with active job (WRKACTJOB)

You can use the WRKACTJOB command to see the system pool ID for an active job.