ICL 1900 Series George 3 Operating System Commands

RUNJOB (RJ)

Function

Initiates a background job defined by a filed job description.

Format

1. NO USER context:
   
   RUNJOB user name,job name,file name,PARAM(a₁,a₂,...a_n)
   The first three parameters are mandatory although user name and job name are interchangeable
   
   
2. USER context:
   
   RUNJOB job name,file name,PARAM(a₁,a₂,...a_n)
   The first two parameters are mandatory

In both formats the job name must not coincide with the name of any of the user's files or with the name of any other job which the user currently has in the system. In particular it must not coincide with the local name given in the third parameter of format 1 or the second parameter of format 2.

However, if the local name is part of a file name with the user name specified as being other than the proper user, then the job name may coincide with the local name

The file name is the name of the job description file. If the file name is not a local name then only this file is opened. There is the usual trap checking when the file is opened.

If only a local name is specified then the file specified must be directly below either the current directory, a directory superior to the current directory, or :SYSTEM.MACROS.

Note that if the command is issued in USER context, although the search for the job description file is made relative to the current directory, the files set up by the command to executethis job are set up below the proper user's proper directory. Thus, any budgetting and accounting applies to the proper user and not to the user associated with the current directory. If the command is issued in NO USER context, the current directory is the proper user's proper directory.

The parameters a₁,a₂,...a_n if present, are the job parameters which must conform to the rules that govern the formats of all parameters. They will be substituted in the job description where parameter substitution is required (denoted by %A, %B etc.).

Forbidden contexts

USER (Format 1)
NO USER (Format 2)

Execution

1. NO USER context
   A check is made that the named user is in the Dictionary and is permitted to start background jobs. HIGH and NORMAL security users, when starting a job in NO USER context on-line, must type in their password: HIGH security users are not permitted to start background jobs from a reader in NO USER context.
   
   The job name is then checked to see that it is acceptable, and the file name is checked to see that the file is entered in either the current directory, :SYSTEM.MACROS or a directory superior to the current directory (they are searched in that order). Provided that an entry is found, the user traps are checked to ensure that the user is allowed to access the file.
   
   If any of the above requirements is not satisfied, the command is abandoned. Otherwise, a monitoring file is opened with the name given in the first parameter, and the specified file name is issued as a macro with the a₁,a₂,...a_n , if any, as parameters. Once the job has started, commands are read and obeyed from the job description file until either an ENDJOB command is encountered or the end of the file is reached at which point the job is terminated. If no ENDJOB command is encountered, the job is suspended for a length of time determined by the WAITTIME installation parameter.
   
   
2. USER context
   Action is the same as that described for format 1 except that no check is made on the user.

Examples

RUNJOB OLDJOBNO1,:FRED,JOBFILE
RUNJOB J3,JDF3,PARAM(*CR0,*LP0,11,01)

Note

Background jobs with full security may be started from a MOP console by means of format 1. The passwrd will be called for and checked.

Error Messages

FILE NAME PARAMETER MISSING
JOB NAME PARAMETER MISSING
JOB NAME z NOT UNIQUE
THE LIMIT ON THE NUMBER OF JOBS HAS BEEN REACHED
USER NAME PARAMETER MISSING
z HAS OVERDRAWN HIS MONEY BUDGET
z IS NOT A CORRECTLY FORMED NAME (job name or user name)
z IS NOT A REAL USER
USER NAME/PASSWORD INVALID
THE SECURITY OF USER z DOES NOT ALLOW THIS COMMAND TO BE OBEYED IN THIS CONTEXT
YOU CANNOT SPECIFY A WORKFILE NAME