LINC Programming Reference Manual - Public Support Login - Unisys

BEGIN.EDIT and END.EDIT
BEGIN.EDIT and END.EDIT
Syntax
Examples
The BEGIN.EDIT; and END.EDIT; commands delimit sequences of main logic that perform
editing and validation of input data in a Copy.From Ispec. Although there may be multiple
pairs, the logic contained in the various pairs is treated as a single unit called the
Copy.From Edit Logic, which is executed in the validation phase of the Copy.From cycle.
Any logic that may cause rejection of data must be coded as Copy.From Edit logic. AUTO;
FLAG; or RECALL; commands cannot be included.
In Copy.From Ispecs, MESSAGE; commands can be coded only within Pre-LINC and Edit
logic. The MESSAGE; command sets GLB.ERROR to ***** (and so inhibits updating the
database) only in the validation phase of the Copy.From cycle. MESSAGE; commands are
not actioned in the update phase of the Copy.From cycle.
The BEGIN.EDIT; and END.EDIT; commands are not implemented in LDA Run Time. Use
Copy.From Edit logic instead.
For details about Copy.From Ispecs in the LINC Cycle, see your LINC Generate
Operations Guide.
DDDD DDDD DDDD DDD4
An Event named SALE is specified with MAX.COPIES of 5, starting from line 5. The Data
items on line 5 are PRODUCT, QUANTITY, and AMOUNT. A CUSTOMER Data item is on
line 3.
This Copy.From edit loop will be cycled through 5 times. Any executed MESSAGE; or
RECALL; command means that the edit loop fails, and the LINC database will not be
updated. If the edit loop is successful, Pre-LINC and Main Logic (including the Copy.From
edit loop) are processed MAX.COPIES times, and the database is updated (provided
PRODUCT has a value).
1-44 v