LINC Programming Reference Manual - Public Support Login - Unisys

SLEEP (SLP)
SLEEP (SLP)
The SLEEP; command suspends execution of a Report. When reactivated, execution
resumes from the next command in the Report logic.
The SLEEP; command has the following variants:
$ SLEEP n
Any current database transaction is committed, and the Report is suspended for a
number of seconds (in the range 0 through 9999). The Report is reactivated after this
time, or if a WAKE.UP; command is received.
For OS 2200 base LINC Systems, a SLEEP; 0 forces a database commit. A SLEEP; n
(where n is greater than zero) initiates an end thread, followed by a wait of n seconds,
followed by a begin thread.
$ SLEEP; UNTIL WAKE.UP
Any current database transaction is committed, and the Report is suspended until it is
explicitly reactivated by a WAKE.UP; command, or termination of the Report.
$ SLEEP; UNTIL WAKE.UP END.AFTER; n
Any current database transaction is committed, and the Report is suspended until it is
explicitly reactivated by a WAKE.UP; command, Report termination, or until after the
specified number of seconds. In the latter case, GLB.CLOSE is set to CLOSE.
Note: In a LINC Report generated as a Coroutine, the SLEEP; UNTIL WOKEN
command performs an end transaction only. See the CALL; command for
details of Coroutines.
About the SLEEP; Command
If GLB.CLOSE equals CLOSE when a SLEEP; command is executed, the Report goes to
end-of-job.
Following the SLEEP; command, a new database transaction (thread) will be started. On
MCP based LINC Systems, this will occur on the first database update following the
SLEEP; command.
On OS 2200 based LINC Systems, if your Report is executed with the no restart option on
the @XQT (@XQT,X), then the SLEEP; will not be actioned.
On UNIX ORACLE Systems, updates are not available to other processes until a database
commit occurs, normally at the end of Pre-Screen logic. If a WAKE.UP; command occurs in
Main logic, and the update has not been committed in the Ispec, it is possible that the
sleeping Report might not find any outstanding request in the parameter file when it is
reactivated. This could result in some outstanding requests remaining in the parameter file.
In LDA Run Time, if a SLEEP; command is executed within a block of logic introduced by a
loop or a condition, it does not perform a database commit or close command, and
therefore does not release any database locks that have been set.
1-234 v