Map-defined input editing

GDDM V3R2 Base Application Programming Reference

Map-defined input editing

GDDM V3R2 Base Application Programming Reference
SC33-0868-02

Using GDDM-IMD's Field Naming or Application Data Structure Review steps, you can specify that the following transformations are to be performed automatically by GDDM on input data passed to the application program. The transformations are specified for individual fields.

Folding: translation to uppercase of all alphabetic input entered into the field.
Justification and padding: right- or left-alignment and padding of data entered into the field.
Attention identifier translation: translation of the AID associated with the input transmission into a predetermined character string.

For information on how to specify these transformations on a map, see the Application Data Structure Review step of GDDM-IMD in the GDDM Interactive Map Definition book. The information given in the remainder of this section relates to the application program's view of the transformed fields returned in response to a receive request.

Notes:

1. The transformations take place on input from the operator, for receipt by the application on an MSGET. Data that is placed into the application data area by the application's MSPUT and map-defined default data is not transformed, even though it may be read back using MSGET.

The effect of the transformations is not immediately visible to the operator. However, if the application does not modify the field, delete the mapped field, or delete the page, the transformed data is displayed to the operator on the next ASREAD, FSFRCE, or GSREAD call.

2. If more than one of these transformations have been specified for a given field, processing is done in this order:

AID translation
Folding
Justification and padding.

Subtopics:

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