Protecting fields from the end user

GDDM V3R2 Base Application Programming Guide

Protecting fields from the end user

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

The 3270 display unit enables you to protect fields from change by the operator. It does so by either locking the keyboard if the operator tries to type into it, or by making the cursor skip over it if the operator tries to move the cursor into it. The first type of field is called protected, and the second type autoskip. Fields that the operator is allowed to type into are called unprotected.

It might seem that variable data fields should always be unprotected. This is not the case, however, because "variable" means capable of being changed by the operator or by the program. If your application uses fields that may be changed by the program but need to be protected from change by the end user, you would make them variable but give them the protected or autoskip attribute.

You can specify which of the three protection attributes a field is to have on the Field Attribute Definition frame of GDDM-IMD's map editor. At execution time, you can override the map-defined attribute by using a base attribute adjunct. As with selector adjuncts, you specify which fields are to have base attribute adjuncts on the Field Naming or Application Data Structure Review frame of the GDDM-IMD map editor. Like selector adjuncts, they appear to the application as extra elements in the ADS.

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