Release Job (RLSJOB)

The Release Job (RLSJOB) command makes a job eligible for processing either after that job is held from processing by the Hold Job (HLDJOB) command, or if the job was submitted to the system as a held job by the Batch Job (BCHJOB) command or Submit Job (SBMJOB) command. The job being released can be on the job queue, on an output queue, or active in a subsystem (competing for system resources) when it is held. Releasing a job causes all threads within the job to be released. Spooled output files being held because *YES is specified for the Hold spooled files (SPLFILE) parameter in the Hold Job (HLDJOB) command are also released. Only those spooled output files which are on output queues in the library name space of the thread issuing this command (RLSJOB) will be released. If the Spooled file action (SPLFACN) job attribute is *DETACH and the job is ended while the spooled files are held, the spooled files cannot be released using the RLSJOB command. To release spooled files after the job has been removed from the system, use the Release Spooled File (RLSSPLF) command.

Restrictions: The issuer of the command must be running under a user profile which is the same as the job user identity of the job being released, or the issuer of the command must be running under a user profile which has job control (*JOBCTL) special authority.

The job user identity is the name of the user profile by which a job is known to other jobs. It is described in more detail in the Work Management book.


Keyword Description Choices Notes
JOB Job name Qualified job name Required, Positional 1
Qualifier 1: Job name Name
Qualifier 2: User Name
Qualifier 3: Number 000000-999999
DUPJOBOPT Duplicate job option *SELECT, *MSG Optional

Job name (JOB)

Specifies the name of the job being released.

This is a required parameter.

Qualifier 1: Job name

Specify the name of the job being released.

Qualifier 2: User

Specify the user name that identifies the user profile under which the job is started.

Qualifier 3: Number

Specify the system-assigned job number.

Note: If no user name or job number is specified, all jobs currently in the system are searched for the job name. If more than one occurrence of the specified name is found, a qualified job name must be provided either explicitly or through the selection display. Refer to the Duplicate job option (DUPJOBOPT) parameter for more information.

Duplicate job option (DUPJOBOPT)

Specifies the action taken when duplicate jobs are found by this command.

The selection display is shown when duplicate jobs are found during an interactive session. Otherwise, a message is issued.
A message is issued when duplicate jobs are found.


Example 1: Releasing a Job for Processing


This command releases the job PAYROLL for processing. If the corresponding HLDJOB command had specified SPLFILE(*YES), any spooled files for job PAYROLL are also released.

Example 2: Releasing a Job for Processing


This command releases job name PAYROLL that was submitted by a user through the user profile DEPTXYZ and later held. The qualified form of the job name is used when jobs with duplicate names exist in the system.

Error messages

*ESCAPE Messages

No response from subsystem for job &3/&2/&1.
Job &1 user &2 job number &3 not found.
End of duplicate job names.
Job control function not performed.
Reader or writer &3/&2/&1 not allowed as job name.
Job &3/&2/&1 not valid job type for function.
Not authorized to control job &3/&2/&1.
Job &3/&2/&1 not released, the job is not held.
Job &3/&2/&1 not released, CPUTIME limit exceeded.
Job &3/&2/&1 not released, MAXTMPSTG limit exceeded.
Function check occurred in subsystem for job &3/&2/&1.
Function not done. &3/&2/&1 in transition condition.