RLSJOB (Release Job)
Purpose
The Release Job (RLSJOB) command makes a job eligible for processing after that job has been held from processing by the HLDJOB (Hold Job) command or if the job was submitted to the system as a held job by the JOB or SBMJOB (Submit Job) commands. The job being released could have been on the job queue, output queue, or active in a subsystem (competing for system resources) when it was held. Spooled files that are held because SPLFILE(*YES) is specified in the HLDJOB command are also 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 Release Job (RLSJOB) command. To release spooled files after the job has been removed from the system, use the Release Spooled File (RLSSPLF) command>.
Restriction: 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.
Required Parameters
- JOB
- Specifies the qualified name of the job being released. If no job qualifier is given, all of the jobs currently in the system are searched for the job name. If more than one of the specified names are found, a qualified job name must be specified.
A job identifier is a qualified name with up to three elements. For example:
job-name user-name/job-name job-number/user-name/job-nameMore information on this parameter is in commonly used parameters.
job-name: Specify the name of the job being released.
user-name: Specify the name of the user of the job being released.
job-number: Specify the number of the job being released.
- DUPJOBOPT
- Specifies the action taken when duplicate jobs are found by this command.
*SELECT: The selection display is shown when duplicate jobs are found during an interactive session. Otherwise, a message is issued.
*MSG: A message is issued when duplicate jobs are found.
Examples for RLSJOB
Example 1: Releasing a Job for Processing
RLSJOB JOB(123456)This command releases the job 123456 for processing. If the corresponding HLDJOB command had specified SPLFILE(*YES), any spooled files for job 123456 are also released.
Example 2: Releasing a Job for Processing
RLSJOB JOB(DEPTXYZ/987654)This command releases job name 987654 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 for RLSJOB
*ESCAPE Messages
- CPF1317
- No response from subsystem for job &3/&2/&1.
- CPF1321
- Job &1 user &2 job number &3 not found.
- CPF1332
- End of duplicate job names.
- CPF1340
- Job control function not performed.
- CPF1341
- Reader or writer &3/&2/&1 not allowed as job name.
- CPF1343
- Job &3/&2/&1 not valid job type for function.
- CPF1344
- Not authorized to control job &3/&2/&1.
- CPF1349
- Job &3/&2/&1 not released, the job is not held.
- CPF1351
- Function check occurred in subsystem for job &3/&2/&1.
- CPF1352
- Function not done. &3/&2/&1 in transition condition.