In WFL, the RUN statement can be used to initiate an object code file as a synchronous dependent process. The TYPE task attribute of the resulting process shows a value of CALL. The initiated program can be written in any language except WFL.

The PROCESS keyword is used as a modifier in front of other initiation statements to cause the process to run asynchronously. Thus, a PROCESS RUN statement initiates an asynchronous task. The TYPE task attribute of the task has a value of PROCESS.

WFL cannot initiate a program as an independent process. In addition, a WFL job is never considered to be a coroutine; that is, a WFL job and its offspring cannot use CONTINUE statements to pass control back and forth.

There are some noteworthy differences between task initiation in WFL and task initiation in ALGOL or COBOL. In the latter two languages, RUN initiates an independent process and PROCESS initiates an asynchronous dependent process. Another difference is that WFL does not use external procedure declarations. In addition, there is no need to include a NAME task attribute assignment in WFL; the name of the object code file to be executed is specified in the RUN statement.

WFL jobs can also initiate internal procedures. An internal procedure in WFL is referred to as a subroutine. If the PROCESS keyword precedes a subroutine invocation statement, the system initiates the subroutine as an internal, asynchronous, fully dependent process. (If you do not use the PROCESS keyword, the subroutine invocation statement enters, rather than initiates, the subroutine.)