WFL jobs can be initiated from user programs written in any of several different programming languages through the use of certain statements. The following table lists the different programming languages and the statements of each that initiate WFL jobs from user programs.
|
Language |
Language Statement |
Reference Document |
|
ALGOL |
ZIP statement |
ALGOL Programming Reference Manual, Volume 1: Basic Implementation |
|
COBOL74 |
CALL SYSTEM WFL statement |
COBOL ANSI-74 Programming Reference Manual, Volume 1: Basic Implementation |
|
COBOL85 |
CALL SYSTEM WFL statement |
COBOL ANSI-85 Programming Reference Manual, Volume 1: Basic Implementation |
|
DCALGOL |
CONTROLCARD function |
DCALGOL Programming Reference Manual |
|
RPG |
ZIP operation code |
Report Program Generator (RPG) Programming Reference Manual, Volume 1: Basic Implementation |
Input submitted from such programs can be in array form or in file form.
| Note: | If the job submitted is from a data array contained in the program, the job cannot contain any data specifications, and any WFL control options included in the job must be followed by a semicolon (;). |
If the job is stored in a file external to the program, it can include any WFL construct defined in this manual. However, if the job contains a job parameter list, it can only be initiated by a START statement, which can be submitted in array form.
Jobs initiated from user programs inherit the usercode and associated privileges of the initiating program.
Jobs originating from a user program by way of an array, and that consist of a single CHANGE, PRINT, REMOVE, RERUN, SECURITY, or START statement, are executed interpretively. That is, an object code file is not generated, and the statement is executed directly by the WFL compiler. These statements are not considered privileged unless the user program is privileged.
