If you initiate RIP through a WFL to run a Report, the value of Glb.Task is returned to RIP as TASKVALUE at the end-of-task (EOT) of the Report. This provides a run result accessible to your WFL, which you might use to control subsequent WFL execution.

The mix number of the initiated report is returned through the MAXCARDS task attribute of RIP. Using a PROCESS RUN of RIP within the WFL, and waiting a few seconds for the report to start, allows the WFL to determine the active report mix number. For example, REPORTMIX:= RIPTASK(MAXCARDS).

A task, EPILOG_TIDYUP, runs at the completion of every report and at the closure of every update (comstp) for an online application. It is a part of internal runtime infrastructure and ensures a clean exit of the task (report/update) with respect to its linkage to the dynamic DBinterface library.

This task might impact if you run a report from WFL jobs that include defined task limit in queue.

Refer to the appropriate WFL manual for the correct form of initiation and file equation.