The job control language of the Cray Operating System (COS) allows the user to present a job to the Cray Computer System, define and control execution of programs, and manipulate datasets.
The job control language is composed of oontrol statements with each control statement containing information for a job step. COS initially creates a oontrol statement dataset, $CS, to hold job control
4
statements. Additional control statement datasets can be created through procedure definition or the CALL control statement (see section 6).
The syntax of a control statement is:
verb sePl paraml seP2 param2
...
sePn paramn term oomrnentsAll control statements must adhere to a set of general syntax rules.
Every control statement consists of a verb and a terminator (term) as a minimum, except for the comment control statement (*) which does not require a terminator. Additionally, most control statements require parameters (parami) and separators (sePi) between the verb and the terminator. The maximum number of parameters (zero, one, or more) depends on the verb.
The continuation separator (the caret symbol) allows a control statement to consist of more than one line image (80 characters). The JOB,
ACCOUNT, DUMPJOB, EXIT, and comment control statements cannot be continued. All other control statements can have any number of
continuation card images, subject to restriction by the verb. A caret occurring within a literal string has no special significance.
A oomment is an optional annotation to a control statement and can be a string of any ASCII graphic characters. The comment follows the line image terminator. The control statement interpreter ignores comments.
All comments appear in the logfile unless suppressed by the ECHO control statement.
Blanks are ignored unless they are embedded in a literal string. Blanks cannot precede the verb on the JOB control statement.
SYNTAX VIOLATIONS
COS notes syntax violations in the system and user logfiles. If the JOB control statement is in error, processing of the job terminates
immediately. If accounting is mandatory, ACCOUNT statement errors also cause job termination. All other syntax errors cause a job step abopt condition, which causes the system to search for an EXIT control
statement. A successful search resumes contro+ statement processing with the job step following EXIT. If no such job step exists or if an EXIT statement is not found, the job is terminated. Job step abort can also direct control to a user-specified routine (see exit processing and reprieve processing in section 3).
VERBS
A eontpol statement vepb is the first nonblank field of a control statement specifying the action to be taken by COS during control statement processing. COS recognizes three types of control statement verbs: system verbs, dataset name vepbs (loeal and system), and
libpapy-defined vepbs. A control statement verb cannot be continued across a card boundary.
When COS encounters a verb in a control statement file, it searches for a match to that verb in the following order:
1. System verbs
2. Local dataset name verbs 3. Library-defined verbs 4. System dataset name verbs
COS first searches the list of system verbs for a match. If the verb is not a system verb, COS searches for a local dataset name that might match the verb. If the verb is not the name of a local dataset, COS searches each library in the library searchlist for a match. If it does not find a library entry that matches the verb, it searches the System Directory Table (SDR) for a matching system dataset name. If a match for the verb
is not found under any of these categories, COS issues a control statement error and aborts the job step.
SYSTEM VERBS
A system verb consists of an alphabetic character which can be followed one through seven alphanumeric characters.t The verb requests that COS perform the indicated function. The system verbs are:
*
DISPOSE EXIT LIBRARY PERMIT ROLLJOBACCESS ECHO EXITIF LOOP PRINT SAVE
ACQUIRE ELSE EXITLOOP MEMORY PROC SET ADJUST ELSEIF FETCH MODE RELEASE SIMABORT
ASSIGN ENDIF IF MODIFY RERUN SUBMIT
CALL ENDLOOP IOAREA NORERUN RETURN SWITCH
DELETE ENDPROC JOB OPTION REWIND
The SIMABORT control statement is described in the COS Simulator (CSIM) Reference Manual, publication SR-0073.
LOCAL DATASET NAME VERBS
A verb that is the name of a local dataset consists of an alphabetic character followed by one through six alphanumeric characters.t This verb requests that COS load and execute an absolute binary program from
the first record of the named dataset. If the user job has a dataset with the indicated name, COS loads and executes the program from that dataset.
LIBRARY-DEFINED VERBS
A library-defined verb consists of one through eight characters. The library-defined verb is either a program or procedure definition (see section 16 of this manual) residing in a library that is a part of the current tibpapy seapchtist. (The library searchlist defines the
library and the order in which the libraries are searched by COS. This order can be specified with the LIBRARY statement described in section
7.) A program in a library is an absolute binary program to be loaded and executed. A procedure definition is a group of control statements and/or data to be processed (see section 16).
t Alphabetic characters include $, %, @, and the letters A through Z.
Alphanumeric characters include all the alphabetic characters and the digits 0 through 9.
by
SYSTEM DATASET NAME VERBS
COS searches for a verb that is the name of a system-defined dataset in the System Directory Table (SDR). A system-defined dataset name verb consists of an alphabetic character which can be followed by one through six alphanumeric characters.t The System Directory Table is a list of common language processors and utilities known to the system and made available to users at startup. The name of the program (for example, CAL, CFT, or DUMP) is also the name of the dataset containing the absolute binary of the program. The exact list of system dataset name verbs is site-dependent.
SEPARATORS
A sepapatop is a character used as a delimiter in a control statement.
It separates the verb from the first parameter, separates parameters from one another, delimits subparameters, terminates verbs and parameters, and separates a keyword from its value in parameters having keyword form.
The control statement separators allowed by COS are given in table 4-1.
PARAMETERS
A pa~ametep is a control statement argument, whose exact requirements are defined by the control statement verb. Parameters are used in
control statements to specify information to be used by the verb-defined process. Parameters that can be used with COS control statements are either positional or keyword. For certain verbs, a parameter value can be an expression. Detailed information on the use of expressions is presented later in this section. Parameters are separated by commas.
POSITIONAL PARAMETERS
A positional parameter has a precise position relative to the separators in the control statement. Even a null positional parameter must be delimited from the control statement verb or other parameters by a separator.
t Alphabetic characters include $, i, @, and the 26 uppercase letters A through Z. Alphanumeric characters include all the alphabetic
Table 4-1. Control statement separators Function
Initial separator (comma or open parenthesis) t - Separates the verb from the first parameter Statement terminator (period if
initial separator is comma; close parenthesis if initial separator
is open parenthesis)t - Signifies end of control statement
Parameter separator (comma) -Indicates the end of one parameter and the beginning of the next
VERB(parameter,paramete~
Equivalence separator (equal sign) -Delimits a parameter keyword from the first parameter value for that key-word. Adjacent equivalence separa-tors are illegal.
Concatenation separator (colon) -Separates multiple parameter values from each other
Continuation character (caret) -Indicates that the control statement consists of more than one SO-character initial and terminator separators for all control statements except or the JCL block control statements (procedure definition, iterative, and conditional) where paired parentheses are conventional.
tt See section 16 for additional information on strings and string delimiters.
The formats for a positional parameter follow:
value
Each
valuei
is a string of alphanumeric characters, a literal string, or a null string. All positional parameters are required to berepresented by at least one
value,
although the value can be null.Rules for strings are given in section 16.
Examples of positional parameters:
• • • ,ABCDE, •••
... , , ...
Parameter value is ABCDE •
The adjacent parameter separators indicate a null positional parameter.
••• ,Pl:P2:P3, ••• The parameter consists of multiple values • VERB () or VERB,. Positional parameter 1 is null
KEYWORD PARAMETERS
A keyword parameter is identified by its form rather than by in the control statement. The keyword is a string of one to alphanumeric characters uniquely identifying the parameter.
of this type can occur in any order but must be placed after positional parameters for the control statement, or they can
The formats of keyworq parameters are: