Attributes

Conflicts

The runtime mapping system does not allow conflicting attributes to be associated with a single map field. If an attribute specified in a map modification command conflicts with a previously established attribute, the new attribute overrides the existing attribute. For example, specification of BRIGHT overrides a previously established DARK attribute; specification of UNDERSCORE overrides a previous REVERSE-VIDEO specification.

How Attributes are Determined

The attributes used for fields are determined as follows:

Attributes specified for individual fields are used for the particular fields when a map is mapped out.
Attributes specified for error-handling override the attributes specified for data fields on a map when the map is redisplayed with error-handling attributes:
- Correct field attributes are used for all data fields that contain correct input and for fields that were not edited on mapin.
- Incorrect field attributes are used for all data fields that contain input errors.

The actual attributes for individual fields and for error-handling are determined at runtime:

Temporary modifications specified for the given field by CA ADS or DML statements take priority over any contradicting attributes previously specified for the field.
Permanent modifications made by CA ADS or DML statements override any contradicting attributes previously defined for the field.
Attributes defined for the field by the online mapping compiler or the batch compiler are used when neither temporary nor permanent modifications override them.

Neither temporary nor permanent modifications alter the map definition or the map load module.