The base attribute adjunct

GDDM V3R2 Base Application Programming Guide

The base attribute adjunct

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

The base attribute adjunct consists of two elements, each one byte long. There is an example in "Defining the base attributes that are to apply to mapped fields" in topic 16.7.1. The second byte indicates what the program-defined field attributes are to be. The first contains a code that indicates whether GDDM should use these attributes, use the ones in the map, or leave the field's attributes unchanged.

You may notice that this discussion refers to attributes in the plural. This is because the second byte can be used to define several types of attribute, not just the one concerned with protecting the field from end-user input. The other types are listed in "The base attribute adjunct."

The effect of an MSPUT call on the base attributes is analogous to its effect on the data. It depends on the type of operation and the code in the first byte of the base attribute adjunct. A write operation first resets all base attributes in the mapped field to the values specified in the map, or, where none were specified, to GDDM-IMD defined defaults. The GDDM-IMD defaults are listed in "The base attribute adjunct."

The write-type MSPUT call sets each field's base attributes according to the contents of first byte of the adjunct, as follows:

A blank character

Leave the base attributes unchanged.

A 1 character

Set the attributes to those specified in the second byte of the adjunct.

A 2 character

Apply the map-defined (or GDDM-IMD default) attributes.

A 3 character

The same as a 1 character.

For rewrite and reject operations, MSPUT sets the base attributes according to the code in the first byte of the adjunct, without first resetting them to the map-defined (or GDDM-IMD default) values.

Subtopics:

16.7.1 Defining the base attributes that are to apply to mapped fields

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