Command files on system startup
After system initialization the operator usually has to make preparations for processing in interactive mode. This includes startup of the data communication system and initiation of the inquiry and transaction applications, among other things.
The commands required for preparing for interactive operation may be stored in a command file.
If the name of this command file was already defined in the startup parameter service (system parameter CMDFILE), the system automatically processes this file immediately after system startup.
The operator can either have a different command file executed by modifying the system parameter CMDFILE by means of the parameter service or during dialog startup or enter commands manually (see also the system parameter NBRUNUID).
Command files for recurrent command sequences
Command sequences which the operator has to enter repeatedly on different occasions – for example in the case of frequently recurring jobs – can be stored in command files.
The operator uses a RUN command to start execution of a command file. The RUN command may be issued either from the physical console or by an authorized user program. In either case it is necessary that those functional areas referenced by the commands in the command file be assigned to the calling physica operatorl terminal or to the authorized user program. In addition to the command files, systems support may create ENTER jobs that are started by the operator from the console. As command sequences in ENTER jobs contain user commands and do not require any special operator action following startup, these command sequences are skipped in the description below.
The provision of operator functionality in any user tasks with the OPERATING privilege means that any procedures (with and without SDF-P) can be provided for the operator. These command files can contain a random mixture of operator and user commands. Starting the procedures with CALL-PROCEDURE and ENTER-PROCEDURE, however, is only possible from user tasks and not from physical consoles or authorized applications. The functions are the same as the procedures in user tasks and are therefore not described here.
The following thus refers exclusively to operator command sequences.
Command | Meaning |
AGOGO | Continue a command file |
ASTOP | Stop processing the command file and define the continuation condition |
CANCEL-RUN-PROCESS | Aborting a command file |
ENTER-JOB | Start an ENTER job |
RUN | Start a command file |
SHOW-PENDING-MSG | Repeat the display of system messages |
Table 48: Overview of commands for command files