The STATUS statement allows you to alter the flow of processing by invoking an APPX status process from within an ILF routine.
••••• STATUS •••
•••••••••••••••••••••••••••••• •••••••••• END? • FAIL •
(1) (2) (3) (4) (5) (6)
(2) Application ID
(3) Status process name
(4) Invocation type (SUBPROCESS, RELATED, DETACHED)
(5) End current process first? (Y/N)
(6) Fail action (0=nothing, 1=warning, 2=error, 3=cancel)
The next status indicator is set to T if the process is invoked successfully, and to F, otherwise. If the process cannot be invoked successfully, the FAIL parameter determines what additional action to take.
In addition to the application ID and status process name to be invoked, you specify the invocation type (subprocess, related, or detached). As with all other child invocations, this parameter controls the level of data sharing between the parent and the status process that is invoked.
If END? is set to Y, the current process will end before invoking the status process. The status process will return to the parent of the current process when it is finished. If END? is set to N, the status process returns to the current process (beginning with the first statement after the STATUS statement).
If the application ID is blank, the value in the predefined field NEXT APPLICATION is used. If the process name is blank, the value in the predefined field NEXT PROCESS NAME is used.
The STATUS statement passes the current PASS list, if any. Refer to the PASS Lists section for details.
NEXT APPLICATION, NEXT PROCESS NAME
INPUT, INQUIRY, JOB, MENU, OUTPUT, PASS, QUERY, SUBR, UPDATE
The following example checks to see if it is the last processing day in the month. If so, the STATUS statement is executed, invoking an end-of-month file status operation.
WORK END OF MONTH EQ
T STATUS TAR END OF MONTH STATUS SUBPROCESS END? Y FAIL 3