QUERY
The QUERY statement allows you to alter the flow of processing by invoking an APPX query process from within an ILF routine.
••••• QUERY •••
•••••••••••••••••••••••••••••• •••••••••• END? • FAIL •
(1)
(2) (3) (4) (5) (6)
(2) Application ID |
(3) Query 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 query 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 query process that is invoked.
If END? is set to Y, the current process will end before invoking the query process. The query process will return to the parent of the current process when it is finished. If END? is set to N, the query process returns to the current process (beginning with the first statement after the QUERY 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 QUERY 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, STATUS, SUBR, UPDATE
The following example checks to see if it is the last processing day in the month. If so, the QUERY statement is executed, invoking an end-of-month query process.
IF TAR
WORK END OF MONTH EQ
Y
T QUERY TAR
END OF MONTH QUERY SUBPROCESS END?
Y FAIL 3