Work Flow Language: Difference between revisions

Revision as of 20:59, 11 May 2014

Revision as of 21:04, 11 May 2014

Line 2:

WFL<ref>Work Flow Language (WFL) Programming Reference Manual. ClearPath MCP Release 10.0 or Later. 8600 1047-507 Unisys Corporation. 2005</ref> is used for high-level system operations, such as running tasks, moving and copying files, providing high-level recoverability. Thus it is not a general purpose language in that you would not use it to do general computations. You can open and close files to check their attributes for example; however, you cannot read or change their contents in WFL – that you do in a general purpose language, and invoke it as a task from WFL.

WFL has a high-level [[ALGOL]]-like readable syntax. It has none of the low-level assembler-like commands of JCL like <code>//SYSIN DD</code>, etc. in order to connect hardware devices and open files for programs. All WFL constructs deal with the high-level abstractions of tasks and files. Parameters are also real HLL parameters, not the $1, $2... style position parameters of shell scripts.

WFL also has an instruction block command which is used to give operators instructions needed to run the current job. These instructions are displayed using the 'IB' operator command.

WFL was a compiled language on the medium systems. Because some OS interfaces may change from release to release, Medium Systems WFL code included a copy of the source in the object file. Upon executing a WFL job it would check to determine if the object was compatible with the OS version. If not it would trigger a recompile of the object using the source embedded in the object code.

Line 11 ⟶ 7:

==See also==

*[[Burroughs large systems]]

*[[UML -IBM ]]

==Sources==