Technical data

IF PART_USES EMPTY . . .
IF EMPTY . . .
If NOT is used, the result of the test is reversed.
A database exception condition occurs if either:
The currency indicator for the run unit is null (DB-CONDITION is set to
DBM$_CRUN_NULL).
The currency indicator for the run unit specifies a position (DB-CONDITION
is set to DBM$_CRUN_POS).
The current record of run unit is not the owner of set-name (DB-CONDITION
is set to DBM$_NOTOTYP).
See Section 4.8.3, Exception Conditions and the USE Statement for information
on USE FOR DB-EXCEPTION.
4.5.3 Database Key Condition
The database key condition determines whether: ( 1 ) two database key values
identify the same database record, ( 2 ) a database key value is null, or ( 3 ) a
database key value is identical to any database key value in a keeplist.
General Format
database-key IS
NOT
ALSO database-key
NULL
WITHIN keeplist-name
database-key
references a currency indicator (see section on Database Key Identifiers) or a
keeplist entry in the Subschema Section.
The result of the test is true if:
When using the ALSO phrase, both database-keys reference identical
database key values. This example compares a set currency indicator for
ALL_PARTS to the currency indicator of the current record.
IF CURRENT WITHIN ALL_PARTS IS ALSO CURRENT . . .
When using the NULL phrase, the currency indicator referenced by database-
key is null. This example checks the currency indicator for the current record
before storing its key in a keeplist:
IF CURRENT IS NULL NEXT SENTENCE
ELSE
KEEP USING KEEP-LIST-A.
When using the WITHIN phrase, any database key value in keeplist-name is
identical to database-key. For example:
IF CURRENT IS WITHIN KEEP-LIST-A
PERFORM 200-ITS-IN-THE-LIST.
Otherwise, the result of the test is false.
If NOT is used, the result of the test is reversed.
A database exception condition occurs if:
The program identifies an invalid database key identifier. (See the Database
Key Identifiers section for more information.)
4–8 Procedure Division