Validation adjunct

GDDM V3R2 Base Application Programming Reference

Validation adjunct

GDDM V3R2 Base Application Programming Reference
SC33-0868-02

The validation attribute is supported only by the IBM 8775 Display Terminal (with the appropriate feature). On all other devices it is ignored.

Possible settings in the attribute adjunct value byte are as shown in Table 42 in topic 16.1.5. The IBM 8775 handles operator input according to the validation attribute, as follows:

1

Mandatory Enter Attribute
If the operator tries to transmit data (for example, by pressing the ENTER key) while there is a mandatory enter field that has not had data entered into it, the transmission fails and input is inhibited. The cursor is repositioned to the start of the first empty mandatory enter field. The operator can proceed by pressing the RESET key. Then, the operator can either enter data in the mandatory enter field, or use the ERASE EOF or Error Override key to set the MDT. For the Error Override key, an error value (X'3F') is returned to the application program in the mandatory enter field.

2

Mandatory Fill Attribute
If data is entered into a mandatory fill field, the field must be completely filled before the cursor can be moved out of it. If an attempt is made to move the cursor out of the field before it has been filled, further input is inhibited.

The operator can proceed by pressing the RESET key, and completing the entry of data into the mandatory fill field. Or, the Error Override key can be used to fill the field with error values (X'3F') before continuing.

3

Trigger Fill Attribute
The trigger field attribute enables the application program to receive data entered into a particular field as soon as the data entry for that field is complete and the cursor leaves the field. The operator can continue keying data while the trigger field is being checked, but the data entered is placed on a queue in the device (and is not displayed).

Cursor exit from a modified trigger field causes the inbound transmission of this single field with a "trigger" AID. The application can access the trigger field data in the usual way using MSGET.

The application program must then decide whether to accept the trigger field (and hence the operator's queued keystrokes) by issuing a positive acknowledgment, or to reject the field (and lose the operator's queued keystrokes) by issuing a negative acknowledgment.

A positive acknowledgment is generated by issuing an MSPUT call specifying that the keyboard is to be unlocked. By default, this is true of options 0 (WRITE) and 1 (REWRITE).

A negative acknowledgment is generated by issuing an MSPUT call specifying that the keyboard is to remain locked. By default, this is true of option 2 (REJECT).

Note: The relationship between the MSPUT option and locking the keyboard is defined in GDDM-IMD's Map Characteristics step.

Notices | Terms of use | Support | Contact z/OS