You can start WFL jobs at an ODT in either of two ways:

A complete job that is entered at the ODT should begin with a BEGIN JOB statement. It is not necessary to end the job with an END JOB statement, because WFL adds this statement automatically. Alternatively, you can specify that a WFL job is to be passed to the WFL compiler by preceding the statement with either the letters CC or a question mark (?). Examples of these formats are ?MOVE and CC  RESTORE.

Jobs entered at an ODT must not contain data specifications. Any WFL compiler options must be followed by a semicolon (;) to separate them from the rest of the job.

A number of WFL statements are recognized by the CONTROLLER and are passed to the WFL compiler automatically, even if they are not preceded by the CC, ?, or BEGIN JOB constructs. The following list shows the valid WFL statements:

A WFL job started at an ODT runs without a usercode unless the job contains a USERCODE job attribute specification. A job without a usercode (and any tasks it initiates) cannot access files residing under usercodes unless their security attribute is PUBLIC. If the job has no usercode or FAMILY specification, the FAMILY of the job queue is used, if present. Otherwise, the FAMILY attribute defaults to a null string, which has the same effect as

DISK = DISK ONLY

The statements ALTER, CHANGE, MKDIR, REMOVE, RERUN, SECURITY, and START are executed interpretively if entered individually at an ODT rather than as part of a job. In these cases, the WFL compiler produces no code file; instead, it executes the statements directly. These statements, if entered at an ODT, are treated as privileged and can access files residing under usercodes.