Work Flow Language: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 07:07, 2 September 2007 edit Lycurgus (talk \| contribs) Extended confirmed users 11,231 edits No edit summary ← Previous edit		Latest revision as of 22:39, 13 February 2025 edit undo Ourobosch (talk \| contribs) 89 edits Disagree with the suggestion to delete. Merging with the Burroughs Large Systems article is the better option in my opinion as WFL is a distinct enough language from JCL and was integral to a product line sold by a company of notable influence in the history of computing. This makes WFL, in my opinion, notable enough to at least include as a subsection in the aforementioned article. Tag: Manual revert
(36 intermediate revisions by 25 users not shown)
Line 1: '''Work Flow Language''', or '''WFL''' (~~pronounced~~ "''wiffle''") is the ~~operations~~[[process control]] language for the [[Burroughs large systems]], including the [[Unisys]] [[Burroughs MCP\|ClearPath/MCP]] series, and their [[operating system]] [[~~MCP (~~Burroughs ~~Large Systems)~~MCP\|Master Control Program]]. Developed soon after the B5000 in 1961, WFL is the ClearPath equivalent of the [[Job Control Language~~\|JCL~~]] (JCL) on ~~other~~[[IBM]] ~~machines~~mainframes and the [[shell script]]s of [[Unix-like]]~~-style~~ operating systems. Unlike JCL ~~and shell scripts though~~, WFL is a high-level structured language complete with ~~routines~~[[subroutine]]s (procedures and functions) with [[Parameter (computer science)\|arguments]] and high-level program [[control flow]] instructions. WFL programs are [[compiler\|compiled]] soto ~~that~~binary ~~they~~executables ~~don't~~like ~~fail~~any onother ~~statements during the run of a WFL~~MCP ~~job~~subject. 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. == See Also ==▼ ▲== See ~~Also~~ also== * [[Burroughs large systems]] ==Sources== <references/> [[Category:ALGOL 60 dialect]] [[Category:Burroughs mainframe computers]] [[Category:Scripting languages]] [[Category:~~Domain-specific~~Mainframe ~~programming~~computer ~~languages~~software]]