The field list header row

GDDM V3R2 Base Application Programming Reference

The field list header row

GDDM V3R2 Base Application Programming Reference
SC33-0868-02

1 - List Status

The status of the field list.

Values that can be assigned to list status are the same as field status; in fact, list status must always be equal to the value obtained by ORing together the values of all the field statuses in the field list. For example, if any field has the indicator set to indicate that the field is to be "output" because the character data has been changed by the application, the corresponding indicator in list status must also be set. This means that whenever the application changes a field status indicator, it must ensure that the list status indicator is correct. Whenever GDDM changes a field status indicator it will also do this.

2 - Used depth

The number of rows in the field list used by GDDM.

This value must be in the range 1 through list depth. It may be changed by the application to add new fields or to remove deleted fields from the list.

Note: If this number is increased to add new fields to the list, the create indicator must be set in the new field-definition status elements. Also, if deleted fields are removed from the list, the deletions must first have been processed by GDDM, which sets the status element in the field definitions to zero.

3 - Used width

The number of elements in the header and each field definition used by GDDM.

This value must be less than or equal to the list width, and must be in the range 6 through 10. If the value is less than the list width, any extra elements in the header and each field definition are ignored by GDDM, and may be used by the application to record its own data. It may be changed by the application to extend or reduce the field definitions. An example of this might be increasing the used width to 9 to specify character color. If the used width is changed, the output indicator must be set in the field definition status elements of all the field definitions altered by this change.

If this value is less than 10, then the omitted parts of the field definition are described as being "not present," and assume default values.

Note: Even though GDDM may not use as many elements in the header as in the field definitions, only those elements beyond the used width may be used for application data. The rest must be zero.

4 - Cursor row

This is the row position of the alphanumeric cursor on the GDDM page.

When used, it must be in the range 1 through page depth, otherwise it must be zero. If the field list is designated as the one used for cursor positioning, then the cursor row and cursor column are used to position the alphanumeric cursor on output, and also to return its position on input. This designation is made by setting the mode parameter of the APDEF or APMOD call.

This cursor position overrides any cursor position specified by calling ASFCUR. During I/O, if the cursor position specified lies outside the page window, then the cursor is placed at the closest position within the page window.

5 - Cursor column

This is the column position of the alphanumeric cursor on the GDDM page.

When used it must be in the range 1 through page width, otherwise it must be zero.

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