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.

FLAG (FL, FG)<br />

FLAG (FL, FG)<br />

The FLAG; command is used to directly modify data in the <strong>LINC</strong> database.<br />

Note: A FLAG command causes a database update, regardless of the setting of<br />

GLB.ERROR (unlike an AUTO.WRITE; command, or Ispec automatic update at<br />

the end of Main logic).<br />

For flagging a Setup Data item array to an alphanumeric data item, use the FLAG.ARRAY;<br />

command.<br />

What You Cannot Use a FLAG; Command For<br />

You cannot use the FLAG; command to:<br />

$ Change the value of the Ordinate of a Component.<br />

$ Store an alphanumeric value in a numeric data item.<br />

$ Move the value of a Data item to another Data item in the same Ispec. If this is<br />

required, use a Setup Data item as intermediate storage. (See "Before Executing a<br />

FLAG; Command".)<br />

Before Executing a FLAG; Command<br />

Before executing a FLAG; command, the record to be changed should be retrieved. When<br />

the FLAG; command is executed, the record is again retrieved from the <strong>LINC</strong> database, to<br />

reduce the chance of data corruption. Since the record in memory is overwritten, it is<br />

advisable to hold required values in Setup Data items until after the execution of any<br />

FLAG; commands. (This is why you cannot use the FLAG; command to move the value of a<br />

Data item to another Data item in the same Ispec. Use a Setup Data item as intermediate<br />

storage.)<br />

Grouping FLAG; Commands<br />

Consecutive FLAG; commands are grouped together, with the combined database record<br />

changes being written to the database in one operation. When the FLAG; commands are<br />

separated by other commands, multiple database update operations will occur, possibly<br />

causing unexpected performance degradation.<br />

Record Locking<br />

The first FLAG; command locks the record being flagged, prior to storing it. The record is<br />

not freed until End of Transaction.<br />

1-130 v

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

Saved successfully!

Ooh no, something went wrong!