Usage

Compiler-Directive Statements › DISPLAY/PUNCH ALL Statement › Usage

Usage

Limiting the Number of Records Read

You can limit the number of entity occurrences CA IDMS/DB reads for a DISPLAY ALL request by setting two options in the SET OPTIONS statement:

DISPLAY ALL LIMIT IS ON activates interrupt processing.
INTERRUPT COUNT IS interrupt-count terminates the DISPLAY ALL request when the number of occurrences read exceeds the interrupt limit, whether or not the occurrences meet the criteria of an associated WHERE clause. If you set the interrupt count to NULL, CA IDMS/DB will reject DISPLAY ALL requests.

Type of Display Depends on Compiler and Entity

The compilers display the entity occurrences as syntax or as comments depending on the entity type requested and the compiler in which the DISPLAY/PUNCH ALL statement is issued, as shown in the following table

Note: C means display as comments; S means display as syntax, if requested.

Entity type	Compiler Schema	Compiler Subschema
ATTRIBUTES	C	C
CLASSES	C	C
ELEMENTS	C
ELEMENT SYNONYMS	C
LOAD MODULES		S
RECORDS	C
RECORD SYNONYMS	C
SCHEMAS	S	C
SUBSCHEMAS	C	S
USERS	C	C

Output Contains Only Enough Information to Display/Punch Entity

Output produced by DISPLAY or PUNCH ALL consists only of the information necessary to execute a DISPLAY/PUNCH request for each entity occurrence. For example, RECORD occurrences are displayed with their name and version, and ATTRIBUTE occurrences with their name and class. In an online session, the user can execute the displayed statements by pressing [Enter]. This two-step process allows the user to scan the names of entity occurrences related to the compiler in which the statement is issued.

Valid Entity Option Keywords for Conditional Expressions

The following table lists entity type options that you can specify in a conditional expression.

Entity type	Option	Entity type	Option
ATTribute User-defined entity	Entity-type name PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated CLAss name	CLAss	Entity-type name PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated
ELement RECord USEr	Entity-type name Version PREpared by REVised by DATe last UPDated DATe CREated DEScription FULl name (users only)	ELement SYNonym	ELement SYNonyn name ELement NAMe Version PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated DEScription
RECord SYNonym	SYNonym NAMe RECord NAMe Version PREfix SUFfix VIEw id PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated DEScription	SUBschema	Entity-type name PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated DEScription SCHema NAMe SCHema Version
SCHema	Entity-type name PREpared by REVised by DATe last UPDated MONth last UPDated DAY last UPDated YEAr last UPDated DATe CREated MONth CREated DAY CREated YEAr CREated DATe COMpiled MONth COMpiled DAY COMpiled YEAr COMpiled DEScription	LOAd module	Entity-type name Version DATe COMpiled MONth COMpiled DAY COMpiled YEAr COMpiled

Default Order of Precedence Applied to Logical Operators

Conditional expressions can contain a single condition, or two or more conditions combined with the logical operators AND or OR. The logical operator NOT specifies the opposite of the condition. The compiler evaluates operators in a conditional expression 1 at a time, from left to right, in order of precedence. The default order of precedence is as follows:

MATCHES or CONTAINS keywords
EQ, NE, GT, LT, GE, LE operators
NOT
AND
OR

If parentheses are used to override the default order of precedence, the compiler evaluates the expression within the innermost parentheses first.