You can perform tasking functions through any of the following interactive interfaces:
-
A command-driven environment that provides file handling and tasking capabilities
-
Menu-Assisted Resource Control (MARC)
A menu-driven interface to system operations functions
-
A Windows-based application that provides a graphical user interface (GUI) to system operations
-
Operator display terminals (ODTs)
Terminals that support an interface called system command mode
Each of these products provides the following general types of tasking capabilities:
-
A command or menu selection that allows you to initiate any object code file by name. Examples are the RUN command in CANDE and MARC.
-
Syntax for specifying task equations, which are task attribute assignments applied to a process when it is first initiated.
-
Task attribute inheritance, which causes a process to receive task attributes associated with the initiating source.
-
Various commands or selections for monitoring process status and resource use, or for intervening in process execution.
The tasking capabilities of CANDE, MARC, Operations Center, and the ODT are described in Tasking from Interactive Sources.
Note that many commands entered by users can indirectly cause a process to be initiated. For example, the Transaction Server initiates instances of direct window programs in response to variations in the message traffic from users. Similarly, the system initiates processes to execute some specialized system commands, such as LOG.
This guide does not attempt to describe all such cases of indirect tasking. CANDE, MARC, and the ODT are all introduced in this guide because they provide direct, generalized tasking interfaces. With these products, you can initiate any object code file, as well as monitor and control any process (to the extent allowed by system security).
