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.

profile keys<br />

Conventions for Syntax Diagrams<br />

Data items whose values are to match those of Ordinates named in the Profile declaration,<br />

or the System Data items GLB.SPACES or GLB.ZEROS.<br />

There must be the same number of data items as Ordinates declared for the Profile. As the<br />

keys determine which records are retrieved from the <strong>LINC</strong> Database, they must be<br />

specified in the same order as declared in the Profile specification. The same name need<br />

not be used in both places, but a numeric data item may not be used as a key for an<br />

alphanumeric Profile Ordinate, or vice versa.<br />

A data item brought into memory may not be specified as a key over its own structure. For<br />

example, if the Profile is over a Component CUST, you may not specify CUST.data name<br />

as a key. If you need to do this, move the value to a Setup Data item, and specify that Setup<br />

Data item as the key.<br />

shadow report<br />

A Shadow Report, identified by the one-character Shadow Report designator (A to Z).<br />

v 1-5

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

Saved successfully!

Ooh no, something went wrong!