Structure of command files

A command file started by the operator from the console is a SAM or ISAM file or a library element (of type J) on public volumes. The data records may contain any operator commands and, with certain restrictions, privileged and user commands. The RUN command sequence must not contain a SET-LOGON-PARAMETERS or EXIT-JOB command. The command file records are of either fixed or variable length, the maximum record length being 201 bytes. Continuation lines are not supported.
Systems support can protect the command file against unauthorized execution by the operator by assigning an execution password. The command file is then processed by the system only if the operator enters the correct password in the RUN command. The password is not logged in the CONSLOG file.

RUN command sequences may consist of any number of commands. At the latest after 30 commands, however, systems support should insert the ASTOP command in order to ensure structured execution of the commands. It is also a good idea to interrupt the sequence whenever the execution of a command necessitates the complete processing of the previous one or the invocation of dependent functions.
For example, if 10 commands are contained in the RUN command file, these commands are read and processed in succession. If a SHOW-PENDING-MSG command occurs in the command sequence, the procedure after this command should be interrupted by means of an ASTOP command. The operator may then answer any outstanding queries. Processing of the command sequence is resumed after the waiting time has expired or an AGOGO.

One advantage of splitting up a RUN file with ASTOP commands is that the command sequence does not occupy class 4 memory unnecessarily during execution.
An extensive command file created in this way is read by the system into class 4 memory section by section, i.e. from one ASTOP command to the next; each file section read in is executed before a new one is read.

If DSSM commands are part of the command file, systems support should note the following:
DSSM commands are processed by a separate task. Commands which cannot be issued until the relevant subsystem is loaded must wait for the DSSM commands to be processed first. The ASTOP command must therefore be inserted in the command file at this point.

The CMDFILE command file (library members are not permissible) may contain a sequence of operator commands that execute invariably on every system startup. For example, this file contains calls for the following command sequence:

DCSOF

Command file (Start Option File) for startup of the data communication system (DCS)

Example of a CMDFILE

/MODIFY-JOB-CLASS CLASS-NAME=JCDIALOG,C-L=0                              1.
/MODIFY-JOB-CLASS CLASS-NAME=TSOSDIA,C-L=0                               2.
/MODIFY-JOB-CLASS CLASS-NAME=JCBATCH,C-L=40                              3.
/SET-MSG-SUPPRESSION MSG-ID=(BLS0980,JMS0154),CONSOLE=C0                 4.
/DCSTART DCSOF=SOF.ACT.DCM8                                              5.
/ASTOP                                                                   6.
/MOD-TASK-CAT CATEG-NAME=DIALOG,WEIGHT-CODE=400,MIN-ACT=35,MAX-ACT=50    7.
/MOD-TASK-CAT CATEG-NAME=BATCH,WEIGHT-CODE=10,MIN-ACT=5,MAX-ACT=20       8.
/MOD-TASK-CAT CATEG-NAME=TP,WEIGHT-CODE=500,MIN-ACT=20,MAX-ACT=40        9.
/IMPORT-PUBSET PUBSET=L                                                 10.
/ATTACH-DEVICE (X3,X4,X5,S1,S3,K7,X0,Y3)                                11.
/SET-DISK-P V=(PRI009,PRI010,PRI037,PRI038,SESAMA),USER=SHARE,ASS=OPER  12.
/SET-DISK-P V=(WORK11,SLED),USER=SHARE,ASS=OPER                         13.
/START-SUBSYS SUBSYS-NAME=MSCF,SUBSYS-PARAM='FILE=$TSOS.RFA.MSCFSTART'  14.
/START-SUBSYS SUBSYS-NAME=SPOOL,SUBSYS-PARAM='RSO=STD'                  15.
/ASTOP                                                                  16.
/MODIFY-JOB-CLASS CLASS-NAME=JCDIALOG,CLASS-LIMIT=20                    17.
/MODIFY-JOB-CLASS CLASS-NAME=TSOSDIA,CLASS-LIMIT=4                      18.

1. Do not permit any jobs for job class JCDIALOG.

2. Do not permit any jobs for job class TSOSDIA.

3. Do not permit more than 40 jobs for job class JCBATCH.

4. Messages BLS0980 and JMS0154 will be suppressed at console C0.

5. Load the Data Communication System.

6. Interrupt the command file until the Data Communication System has been loaded.

7. Define the number and weight of tasks for task category DIALOG.

8. Define the number and weight of tasks for task category BATCH.

9. Define the number and weight of tasks for task category TP.

10. Import pubset L.

11. Attach devices to the system.

12. Set values for disk monitoring.

13. Set values for disk monitoring.

14. Activate MSCF communication.

15. Load the subsystem SPOOL with automatic loading of RSO.

16. Interrupt the command file until SPOOL has been loaded.

17. Do not permit more than 20 jobs for job class JCDIALOG.

18. Do not permit more than 4 jobs for job class TSOSDIA.

The system parameter NBCONOPI=Y can be used to request a system in which a logon is also necessary for physical consoles. In such systems therefore, entry of, say, a RUN command at a physical console is only possible after a successful SET-LOGON-PARAMETERS and a corresponding REQUEST-OPERATOR-ROLE.

If, when the system parameter NBCONOPI=Y is used, the file name of the RUN file is specified without a user ID, the file is sought first under the ID of the operator, then under the ID specified in the system parameter NBRUNUID, and finally under the TSOS user ID. Because the OPERATING privilege no longer requires the TSOS ID, the RUN file may have to be made “shareable”.

When the system parameter NBCONOPI=Y is used, it is not the case that every operator can enter the AGOGO or CANCEL-RUN-PROCESS command for every RUN sequence, even if he/she has the necessary authorization code.
Both commands are only permissible when at least one of the following conditions is fulfilled:

• the user ID of the caller matches the ID under which the RUN command was issued

• the user ID of the caller is TSOS

• the RUN command was entered by an authorized user program with a generated authorization name

• the caller of the RUN command has logged off from the system.

At system startup, the CMDFILE is processed, being treated like a RUN command issued on this file from the main console. It is not necessary to enter the SET-LOGON-PARAMETERS or REQUEST-OPERATOR-ROLE command beforehand, because, for this CMDFILE and only at startup, the authorization check is performed using authorization codes as though the main console had been assigned all authorization codes. All RUN commands called from the CMDFILE also enjoy this privilege.

The RUN command and the commands that are logically linked to it (e.g. AGOGO and CANCEL-RUN-PROCESS) are not allowed for a user task, even with the OPERATING privilege. Here, SDF-P procedures can be used, in which commands of the OPERATING privilege can also be used.