CHGJOBQE (Change Job Queue Entry)

CHGJOBQE Command syntax diagram

 

Purpose

The Change Job Queue Entry (CHGJOBQE) command changes an existing job queue entry in the specified subsystem description. This command can be issued while a subsystem is either active or inactive. A job queue entry identifies the job queue from which jobs are selected to run in the subsystem. Jobs can be placed on a job queue by spooling readers or by using the following commands:

In a subsystem, job queues with lower sequence numbers are processed first. For more information, refer to the SEQNBR parameter description.

Restriction: To use this command, the user must have object operational and object management authorities for the subsystem description being changed.

 

Required Parameters

SBSD
Specifies the qualified name of the subsystem description that contains the job queue entry being changed.

The name of the subsystem description can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library to be searched.

subsystem-description-name: Specify the name of the subsystem description that contains the job queue entry.

JOBQ
Specifies the qualified name of the job queue that is a source of batch jobs started by the subsystem.

The name of the job queue can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

library-name: Specify the name of the library to be searched.

If the job queue does not exist when the entry is changed, a library qualifier must be specified because the job queue name is retained in the subsystem description.

job-queue-name: Specify the name of the job queue.

 

Optional Parameters

MAXACT
Specifies the maximum number of jobs that can be started at the same time from this job queue. More information on this parameter is in Commonly used parameters.

*SAME: The value does not change. However, the maximum activity level of the routing entries might prevent routing steps from being started. If *NOMAX is specified, all the jobs on the job queue are started (within the limit specified by the MAXJOBS parameter in the subsystem description), even though the activity level of the storage pool being used might prohibit them from running at the same time.

*NOMAX: There is no maximum number of jobs that can be active at the same time.

maximum-active-jobs: Specify a value for the new maximum for the number of jobs that can be active at the same time from this job queue.

MAXPTYn
Specifies the number of jobs that can be started for a specified job priority level.

*SAME: The value does not change.

*NOMAX: There is no disconnect limit.

maximum-active-jobs: Specify the number of jobs started in a specific priority level. Valid values range from 0 through 99. If zero (0) is specified, no jobs are started from a specific priority level.

SEQNBR
Specifies a sequence number for this job queue that is used by the subsystem to determine the order in which the job queues are processed.

*SAME: The sequence number assigned to this job queue does not change.

sequence-number: Specify the sequence number assigned to the job queue. The sequence number must be unique in the subsystem description. Valid values range from 1 through 9999.

The subsystem first selects jobs from the job queue with the lowest sequence number. When all jobs on that queue have been processed or the number of jobs specified on the MAXACT parameter has been reached, the subsystem processes jobs on the queue with the next higher sequence number. This process continues until all job queue entries have been processed or until the subsystem has reached its limit for overall maximum jobs (as specified on the MAXJOBS parameter in the subsystem description). In some cases, the sequence is interrupted and the subsystem processes a queue with a lower sequence number. This occurs for this subsystem when one of the following conditions occurs:

  • A held job or job queue is released.

  • A job is placed on or transferred to a queue.

  • A new queue is allocated.

  • A job ends.

Example for CHGJOBQE 

CHGJOBQE  SBSD(QGPL/QBATCH)  JOBQ(QGPL/QBATCH)
  MAXACT(4)  MAXPTY1(1)  MAXPTY2(*NOMAX)

This command changes the maximum number of jobs submitted from the job queue QBATCH via the job queue entry to the QBATCH subsystem for processing at the same time. Up to four jobs from the QBATCH job queue can be active at the same time. The sequence number of the job queue entry does not change. Up to one job can be active from priority level 1. There is no maximum for the number of jobs that can be active at the same time from priority level 2. Priority levels 3 through 9 do not change.

Error messages for CHGJOBQE

*ESCAPE Messages

CPF1619
Subsystem description &1 in library &2 damaged.
CPF1691
Active subsystem description may or may not have changed.
CPF1697
Subsystem description &1 not changed.