Change Job Queue Entry (CHGJOBQE)

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 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:

Submit Job (SBMJOB)
Submit Data Base Jobs (SBMDBJOB)
Submit Diskette Jobs (SBMDKTJOB)
Transfer Job (TFRJOB)
Transfer Batch Job (TFRBCHJOB)

In a subsystem, job queues with lower sequence numbers are processed first.

Notes:

The job associated with an active subsystem can only find objects that exist in the system auxiliary storage pool (ASP) or in a basic user ASP. Therefore, objects that are referenced by this command should exist in the system ASP or in a basic user ASP.

Restrictions:

To use this command, you must have:
- object operational (*OBJOPR), object management (*OBJMGT), and read (*READ) authority to the specified subsystem description and execute (*EXECUTE) authority to the library containing that subsystem description.

Parameters

Keyword	Description	Choices	Notes
SBSD	Subsystem description	Qualified object name	Required, Positional 1
	Qualifier 1: Subsystem description	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
JOBQ	Job queue	Qualified object name	Required, Positional 2
	Qualifier 1: Job queue	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
MAXACT	Maximum active jobs	0-1000, SAME, NOMAX	Optional, Positional 3
SEQNBR	Sequence number	1-9999, *SAME	Optional
MAXPTY1	Max active priority 1	0-99, SAME, NOMAX	Optional
MAXPTY2	Max active priority 2	0-99, SAME, NOMAX	Optional
MAXPTY3	Max active priority 3	0-99, SAME, NOMAX	Optional
MAXPTY4	Max active priority 4	0-99, SAME, NOMAX	Optional
MAXPTY5	Max active priority 5	0-99, SAME, NOMAX	Optional
MAXPTY6	Max active priority 6	0-99, SAME, NOMAX	Optional
MAXPTY7	Max active priority 7	0-99, SAME, NOMAX	Optional
MAXPTY8	Max active priority 8	0-99, SAME, NOMAX	Optional
MAXPTY9	Max active priority 9	0-99, SAME, NOMAX	Optional

Top

Subsystem description (SBSD)

Specifies the name and library of the subsystem description that contains the job queue entry being changed.

This is a required parameter.

Qualifier 1: Subsystem description

name

Specify the name of the subsystem description where the job queue entry is being changed.

Note: The following IBM-supplied objects are not valid on this parameter:

QSYSSBSD

Qualifier 2: Library

*LIBL: All libraries in the thread's library list are searched until a match is found.
*CURLIB: The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.

name: Specify the library where the subsystem description is located.

Job queue (JOBQ)

Specifies the name and library of the job queue that is a source of batch jobs that are started by the subsystem. If the job queue does not exist when the entry is added or changed, a library qualifier other than *LIBL must be specified because the job queue name is kept in the subsystem description.

This is a required parameter.

Qualifier 1: Job queue

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

Qualifier 2: Library

*LIBL: All libraries in the thread's library list are searched until a match is found.
*CURLIB: The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.

name: Specify the library where the job queue is located.

Maximum active jobs (MAXACT)

Specifies the maximum number of jobs that can be active at the same time from this job queue.

*SAME: The maximum number of jobs that can be active at the same time does not change.

*NOMAX: There is no maximum for the number of jobs that can be started at the same time through this job queue entry. However, the maximum activity level of the routing entries, the subsystem, or the specific job priority level might prevent jobs from being started. If *NOMAX is specified, all the jobs on the job queue are started, even though the activity level of the storage pool being used might prohibit them from running at the same time.
0-1000: Specify the maximum number of jobs that can be active at the same time from this job queue.

Sequence number (SEQNBR)

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

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 Maximum active jobs (MAXACT) parameter has been reached, the subsystem processes jobs on the queue with the next higher sequence number. This sequence continues until all job queue entries have been processed, or until the subsystem has reached its limit for overall maximum jobs. In some cases, the sequence is interrupted and the subsystem processes a job 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 job queue.
A new job queue is allocated.
A job ends.

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

1-9999: Specify the sequence number assigned to this job queue. The sequence number must be unique in the subsystem description.