Initiate WFL jobs from an ODT using one of the following methods:
-
Use the START statement to initiate a job stored in a disk file.
-
Type the complete job at the ODT and transmit the job.
When a complete job is entered at the ODT, it should begin with the BEGIN JOB construct. It is not necessary to append the END JOB construct to the job, since WFL will add this automatically.
| Note: | A complete job entered at an ODT cannot include data specifications. Any WFL control option must be followed by a semicolon (;) to separate it from the rest of the job. |
A number of WFL statements are recognized by the CONTROLLER and are passed to WFL automatically, even if they are not preceded by a BEGIN JOB heading. These statements include the following:
|
|
|
A WFL job initiated at an ODT runs without a usercode unless the job that includes a USERCODE job attribute specification is run from an ODT with TERM USER specified, or the HU system command has an associated usercode. The HU system command designates a usercode for certain distributed systems services Host Services requests if they come from an ODT that has no terminal usercode assigned to it. The TERM USER system command controls the format of all displays on the ODT, and associates the usercode with certain requests initiated at the ODT where the command is entered. See the System Commands Reference for more details on these commands.
The statements ADD, ARCHIVE, CATALOG, COPY, MODIFY, MOVE, REPLACE, RESTORE, RESTOREADD, RESTOREREPLACE, UNWRAP, VOLUME and WRAP, when run without a usercode, are privileged and can access any file, volume family, catalog entry or archive entry.
| Note: | The job, and any tasks initiated by the job, will therefore be unable to access files residing under usercodes unless their security is PUBLIC. In addition, if the job is running without a usercode, and no FAMILY specification is included in the job, the FAMILY will default to DISK = DISK ONLY. |
The statements ALTER, CHANGE, REMOVE, RERUN, SECURITY, and START are executed interpretively if entered individually at an ODT (rather than as part of a job). When this occurs, no object code file is produced by the WFL compiler; the statements are executed directly by the WFL compiler and do not enter a job queue. Thus, no queue attributes, such as FAMILY, are inherited by the job or the statement. These particular statements are treated as privileged if entered in this way, and can be used to affect files residing under usercodes.
