1 1 19 Boolean

You are here:

1.1.19 Boolean

Boolean fields have only two possible values: either False (0) or True (1).

Please review the general 1.1.1 Field Type Considerations.

Field Definition Rules

Rules for defining a Boolean field in the repository are:

Length	Length cannot be specified. No decimals.
Valid Keyboard Shift	Blanks
Allowed Attributes	ASQN
Edit Mask	Not allowed.
Default	*NULL (False)

Field Definition Notes

None.

Usage Rules

Partition Type	RDMLX Enabled Partitions
Files	Booleans may only be used in RDMLX Files. Booleans can be used as key fields if the ASQN attribute is removed.
Logical Views	Booleans may be used as keys to logical views if the ASQN attribute is removed. Booleans may be used in Select/Omit criteria with COMP() EQ/NE 'True' or 'False'
Virtual Fields	Booleans may be used as virtual field; they may only be assigned a value using Code Fragments.
Predetermined Join Fields	Booleans may be used for lookup predetermined joined fields.
RDML Commands	Booleans are classified as their own type and are not valid for numeric or alpha command parameters in RDML commands.
Built-In Functions	Booleans are classified as their own type and are not valid for numeric or alpha command parameters in RDML commands.
Special Values	NULL, NAVAIL, HIVAL, LOVAL, *REMEMBERED_VALUE
Conversion	Booleans may be converted to alpha, integer, signed, packed, string or char. In numeric conversions, False becomes 0, and True becomes 1. In Character/String conversions, the target is populated with the word "False" or "True". Refer to Field Type Conversions.

Usage Notes

Working fields may be defined as TYPE(*BOOLEAN).

In a SELECT_SQL Where clause, you must use 0 and 1, the keywords True and False are not supported.

In Select/Omit criteria, Boolean literals must be specified in capitals and surrounded by quotes. I.e. 'TRUE' or 'FALSE'.

Platform Considerations

Refer to Platform Considerations in 1.1.1 Field Type Considerations.

Also See