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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For 2200 Series<br />

System Data Item Descriptions<br />

The value of GLB.TASK is stored in T3 of the Run Condition Word and can be tested later<br />

in the same runstream by a succeeding task.<br />

Note: <strong>LINC</strong> Reports generated as <strong>LINC</strong> Subroutines cannot use this System Data<br />

item.<br />

If you use a MOVE; command to move a value to GLB.TASK, T3 of the Run Condition Word<br />

is set immediately. If you use any other command that has GLB.TASK as a receiving field,<br />

GLB.TASK is set only at the end of the Report.<br />

If the <strong>LINC</strong> Report terminates normally, the error status of the current task is cleared and<br />

the value in GLB.TASK is stored in T3 of the Run Condition Word. If the <strong>LINC</strong> Report<br />

terminates abnormally, the error status of the current task remains as it was set in T3 of<br />

the Run Condition Word.<br />

GLB.TASK is zero unless it is explicitly given a value.<br />

For more information on Run Condition Words, see your OS 2200 Based <strong>LINC</strong><br />

Administration and Operations Guide.<br />

LENGTH = 2 EDIT = N<br />

For UNIX<br />

For Reports initiated using the runrep shell script, you can determine the value of<br />

GLB.TASK from the return code of a <strong>LINC</strong> Report, and use that information to control<br />

dependent actions. The Report will return a value of zero through 99 to indicate the Report<br />

has successfully completed, or 100 through 199 to indicate that it has failed.<br />

You should set the value of GLB.TASK to a number in the range 60 through 99. This is<br />

because UNIX returns values in the ranges 1 through 31 and 129 through 159 if a Report is<br />

terminated by using a UNIX kill or a :TER <strong>LINC</strong> System command.<br />

For a description of the use of GLB.TASK for UNIX <strong>LINC</strong> System Reports, see your UNIX<br />

<strong>LINC</strong> Administration and Operations Guide.<br />

GLB.TASK defaults to zero.<br />

LENGTH = 2 EDIT = N<br />

For LDA<br />

Moving a value to GLB.TASK causes the task value to be set. This value can then be tested<br />

by the program initiator. This value is written to ERRLOG.TXT at the completion of a<br />

report or at the end of an online session. This value is also written to the log file if logging<br />

is enabled.<br />

The initial value of GLB.TASK is zero.<br />

v 2-63

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

Saved successfully!

Ooh no, something went wrong!