You can include task equations after a WFL task initiation statement submitted from the ODT. Also, if you type in a complete WFL job at the ODT, you can include task attribute assignments in the job attribute list. However, you cannot include task equations after the ??RUN or the PRIMITIVE RUN command.
When you initiate a process from the ODT, the process typically does not inherit any of the task attributes that it would if you initiated the process from a MARC or CANDE session. For example, the USERCODE, ACCESSCODE, CHARGE, and FAMILY values of the process are usually null, unless explicitly assigned.
However, task attributes are inherited in the following cases:
-
If you submit a WFL job that includes a USERCODE assignment in the job attribute list, then the following task attributes of the WFL job inherit values from the corresponding usercode attributes: CHARGE, CLASS, CONVENTION, FAMILY, LANGUAGE, PRINTDEFAULTS, and PRIORITY. This inheritance can be overridden by assignments to these attributes in the job attribute list.
-
If you use the TERM (Terminal) system command to assign a terminal usercode to an ODT. This usercode is inherited by WFL jobs submitted from the ODT, unless overridden by a USERCODE assignment in the job attribute list. The job also inherits values for the same set of task attributes listed in the previous item in this list.
-
If you submit a WFL job, the job can inherit attributes from a job queue. Refer to “Deciding on the Queue for a Job” in Tasking from Programming Languages.
Note that programs initiated by a ??RUN command or a PRIMITIVE RUN command do not inherit the terminal usercode or any other usercode attributes.
Special types of security status apply to nonusercoded processes and certain WFL statements when they are entered at the ODT. These privileges are discussed in Establishing Process Identity and Privileges.
