18.08.2013 Views

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SLEEP (SLP)<br />

Use of this command with OLTP is described in your <strong>LINC</strong> Generate Operations Guide.<br />

Report Output Control (ROC) Standard Reports<br />

Syntax<br />

Examples<br />

It is recommended that the CRITICAL.POINT; command be used instead of the SLEEP;<br />

command in Standard ROC Reports, because although a SLEEP; command causes a<br />

database commit, all ROC Standard Report output may not have been written to the<br />

appropriate <strong>LINC</strong> structures (as it is with a CRITICAL.POINT; command). Recovery of the<br />

output cannot therefore be fully guaranteed. In addition, the values of System Data items<br />

are not recovered.<br />

DD DBDD DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBDD4<br />

3 3<br />

CDD DBDDBDDDDDDDDDDDDDDDDDDDDDDDDD4<br />

3 3 3 3<br />

@DD DDDY @D DD DY<br />

sleep time<br />

A numeric data item or constant giving the number of seconds (in the range 0 through<br />

9999) for which the Report is to be suspended. The Report is reactivated after this time, or<br />

if a WAKE.UP; command is received.<br />

timeout<br />

A numeric data item giving the number of seconds (in the range 0 through 9999) for which<br />

the Report is to be suspended. The Report is reactivated after this time (and the System<br />

Data item GLB.CLOSE is set to CLOSE), or if a WAKE.UP; command is received<br />

In the following example, the Report is suspended for 30 seconds every time Frame 03 is<br />

printed.<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

v 1-235

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!