LINC Programming Reference Manual - Public Support Login - Unisys

SECURE
SECURE
SECURE; is not a full logic command. It is a command option that can be specified with a
DETERMINE; or LOOK.UP; command only, to facilitate record locking of the LINC
database in a non-Integrity LINC System.
The SECURE; command option is applicable to No.Integrity Ispecs and Reports; that is,
those that do not have the Integrity field set (to Y) on either their Ispec or Report Options
screen and on the Primary Specification Options screen. Where the Integrity field is set,
those Ispecs and Reports will automatically secure all required resources.
The type of locking on each host type at runtime is described in the following subsections.
For an MCP based LINC System
The SECURE; command option facilitates record-level locking of the LINC database in a
non-Integrity MCP based LINC System. The SECURE; command option locks the record
that is read into memory by the associated LOOK.UP; or DETERMINE; command. The
record remains locked until one of the following situations occur:
$ The Ispec or Report logic is complete.
$ A SLEEP; or CRITICAL.POINT; command is executed in Report logic.
For an OS 2200 based LINC System
The SECURE; command allows page-level locking of a non-Integrity OS 2200 based LINC
database. The SECURE; command option locks the page containing the record read into
memory by the associated LOOK.UP; or DETERMINE; command. The page remains locked
until:
$ The Ispec or Report logic is complete.
$ A SLEEP; command or CRITICAL.POINT; command is executed in Report logic.
Note: If you use the SECURE; command option when reading a database record that
has already been updated by logic earlier in your Ispec, then an RDMS error
6002 (semantic error) and an RDMS ERROR 23030 (Table nnnn cannot be
explicitly locked because it is currently locked explicitly or implicitly for
update) will occur.
Always append your SECURE; command option to a LOOK.UP; or
DETERMINE; of the database record before the logic that updates the record. If
an exclusive lock has already been placed on the table using the
EXCLUSIVE.USE; command, the SECURE; command option will have no affect.
v 1-211