This chapter presents the commands used in the Uproc CL.
The term "Command Language or CL" designates a command file associated with the Uproc (CL_INT or CL_EXT type). In the rest of this chapter, all operations procedures written in command language (i.e. belonging to the operating system) are called "procedures".
The command language provides the indispensable access to communications between the procedures and Dollar Universe. The latter therefore supplies a set of commands aimed at acquiring information from or transmitting information to the 'procedure'.
It is worth noting that the preliminary processing performed by Dollar Universe before actually submitting the job ("condition check") requires no specific intervention in the procedure itself.
To facilitate manipulation and maintenance, it is recommended to keep procedures short and homogeneous from the functional viewpoint (simplified Launch Formulas, simpler conditions).
Dollar Universe commands contribute to making procedures portable, independent of the configuration and ensure coherent operations management, while permitting applications to benefit fully from the logic inherent in the Dollar Universe concepts (companies, areas, Management units and inter-MU dependencies, etc.).
The following specific commands are available:
|
Command |
Function |
|---|---|
|
Protects the execution from interruption from the job monitor |
|
|
Passes parameters to other Uprocs within a session |
|
|
Displays additional information in the job monitor |
|
|
Sends messages to the Uproc's history trace |
|
|
Writes a step in a Uproc |
|
|
Carry-over of a variable’s values within a session |
|
|
Transfers variables from one Uproc to another within a session |
|
|
uxexechidden |
Commands that can be implemented to manage hidden variables Execute a command using the value of one or more hidden variables |
These commands leave a trace of their execution in the execution history (History Trace). If recording in the history has been turned off for the Task, or generally by setting the node setting U_HISTORIC to “No” (Advanced Settings category), the command will run normally. The execution traces will be visible in the History Trace only for the duration of the Uproc execution.
In each of these commands the default values of the Management unit and applications parameters are systematically those of the operating environment.
Normalization
The CL procedure can be written either in Dollar Universe or independently, using a text editor of the user's choice.
The procedure can make use of the commands described below, or the local environment variables generated by Dollar Universe.
Return Code
While Dollar Universe can recognize the technical quality of a job’s completion, the procedure may, from an applications perspective, be deemed incorrectly completed.
Therefore, to cover all possible cases, Dollar Universe requires that procedures set a variable indicating the desired return code.
Two procedures may issue a return code: The pre-processing routine and the CL of the Uproc.
The pre-processing routine delivers its return code in the variable unix_status. The Uproc exit is restored in the variable RESEXE or S_RESEXE on OpenVMS. The first may be of use to the Uproc procedure and both may be used in the batch envelope's post processing routine.
On OpenVMS only, the variable S_RESEXE can also be used in the CL to ensure a job will complete or abort regardless of the return code:
If the variable S_RESEXE is set with any other value, the return code is taken into account.
On OpenVMS if the S_RESEXE variable is set to “V” or “I” and there is no specified exit code, Uproc status management rules based on the return code value are not available.