The syntax for this command is as follows:
SCHEDULING
A queued generate request for a system or report(s) might wait on a start time and/or an event. By default, the queued entry waits on whichever occurs first, the start time being reached or the start event being set. By setting a start time of at least two months in advance (based on the month number) then the queue entry becomes event triggered exclusively.
The event trigger is set via utility NGENnn/ABTALKER.
This utility has a single array parameter of the following format:
"U=<usercode> S=<system> P=<dict.pack> A=<action>"
Where, <action> is either SYSTEM or REPORTS.
When many report generates are scheduled for a system, then all are marked as generate as soon as possible. The running of this utility might be used within WFLs etc, to control the generate based on user determined events, for example, database backup completed ok.
This utility returns a taskvalue indicating the result of the call, as shown in the following table:
| Task Value | Result of the Call |
|---|---|
| 1 | Entry found in queue, generate starts as soon as possible |
| 2 | Entry found in queue, generate starts as soon as there is an available generate worker (all are currently busy) |
| -1 | Could not locate entry in queue |
| -2 | Badly formatted parameter |
Individual generate queue entries might be altered using the FORCEQ, CHANGEQ, SETQSEQ, and CLEARQ commands.