Use JobAlter to alter the attributes of a JES job, a JES data set group, or a POWER job.
JobAlter may also be entered as JobAlt[er], AlterJ[ob], AltJ[ob], AlterP, AltP, or AP.
Optional Operands
JOB is the JES job or POWER job to alter or the JES job containing the JES data set group to alter.
GROUP [JES jobs only]. is the JES data set group to alter. To alter a JES job (as opposed to JES data set group), do not specify GROUP.
CLASS specifies a new JES or POWER class. JES and POWER use classes to select the resources to use to process a job or data sets. Values are site-specific.
DISP [POWER jobs only.] specifies a new POWER disposition. POWER uses disposition to determine the circumstances of processing an entry. Values are D = dispatchable, K = keep, L = leave, H = hold.
PRI specifies a new JES or POWER priority. JES and POWER use priority to determine the order of processing entries.
COPY [POWER jobs only.] specifies a new POWER copy count. POWER uses the copy count to determine how many copies of an entry to process.
DEST [POWER jobs only.] specifies a new POWER destination. POWER uses destination to route output in a networked environment.
SYSID [POWER jobs only.] specifies a new POWER system ID. POWER uses system ID to route output in a multi-CPU environment.
USER [POWER jobs only.] specifies a new POWER user ID. POWER records user IDs in job accounting.
FNO [POWER jobs only.] specifies a new POWER forms ID. POWER uses forms ID to manage output devices.
JES Notes
If neither JOB nor GROUP is specified, the last referenced job (and data sets) sets are altered. (If last referenced data sets was specified with a DSET operand, JobAlter will be rejected because JES provides no facility to alter by data set.)
To alter a JES job (as opposed to a JES data set group), specify the JOB operand but do not specify the GROUP operand. To usefully alter a JES job, the job must not have started processing.
If GROUP is specified, JobAlter operates on all data sets within the JES data set group.
The relationship between the output queue and the hold queue is a little confusing. For a data set to be in the hold queue, HOLD=YES must have been specified or implied by the CLASS on the DD statement that created it and it must never have been JobRelease(d) or altered to a CLASS that implies Hold=NO. When a JobHold command is issued for a data set that is in the output queue, the data set is placed on hold status but remains in the output queue, and must therefore be accessed by out group rather than by class.
JobAlter sets the last referenced job (and data sets).
POWER Notes
If JOB is not specified, the last referenced job is altered.
JobAlter sets the last referenced job.
When Valid
Check with your System Administrator to determine the restrictions on access to jobs and data sets at your site. The exit routine distributed with host BIM-EDIT provides several restriction schemes your System Administrator can select from.
Return Codes
OK Successful.
NF Job or data sets not found.
PW Rejected by JES or POWER.
-- Other codes as set by BIXPWQA exit routine.
JES Examples
Change the class of JES job 1234 to I:
=> ap 1934,class=i
Change the class A hold queue output for the last referenced job to class B:
=> ap group=a,class=b
Change JES job U782PRT output queue out group 2.1 data sets to class A:
=> ap u782prt,2.1,class=a
POWER Examples
Alter a POWER job in the LST queue, identifying it with queue and job name:
=> ap lst.asm100,class=a,disp=d
Alter a POWER job in the RDR queue, identifying it with queue and job number:
=> ap rdr.1278,pri=4
Alter a POWER job in the LST queue, identifying it with just the job number:
=> ap 3426,pri=4
Alter the last referenced job:
=> ap disp=d