GDDM V3R2 Base Application Programming Reference
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF | BOOK


MSDFLD

GDDM V3R2 Base Application Programming Reference
SC33-0868-02



Function


To create or delete a mapped field.


   MSDFLD      (id, row, column, map-name)

APL code 1108 GDDM RCP code X'0C280500' (203949312)


Parameters


id (specified by user) (fullword integer)
The identifier of the mapped field. It must be a positive integer greater than zero.


If there is an existing mapped field with the same identifier, the existing mapped field is deleted (see the section below about row or column with zero value).

row (specified by user) (fullword integer)

column (specified by user) (fullword integer)
The position on the page of the rectangle covered by the mapped field. Usually, the position of the mapped field is taken from the map definition by specifying row and column as -1. The size of the mapped field is taken from the map definition.


If the value of row or column is zero, any existing field with the same identifier is deleted.

The field must not overlap any existing mapped field.

map-name (specified by user) (8-byte character string)
The name of the map that defines the properties of the field. The maps of all the mapped fields within a page are taken from the same mapgroup; see MSPCRT.

Description


Creates a mapped field and positions it on the current page. The map's constant fields are put onto the page. If the cursor has not previously been positioned and the map has defined a static cursor-position, the cursor is placed at that static cursor-position. The application data area associated with the mapped field is set to its default value.

   Notes:

1. The current page must have been created with the MSPCRT call but it can also contain simple alphanumeric fields.

2. The size of the mapped field is found from the map definition. It cannot overlap any other mapped field.

3. A mapped field must not overlap a simple alphanumeric field. Also, care must be taken when placing mapped and alphanumeric fields next to each other, because of the attribute bytes that enclose alphanumeric fields. Undesirable results can occur if the attributes intrude into a mapped field.

4. The area occupied by a mapped field can overlap a graphics or image field. Where such overlaps occur, the mapped data takes precedence, but the results are device-dependent. For devices that support background transparency, the mapped field is transparent, that is, the underlying graphics or image are always visible. For devices that do not support background transparency, the mapped field is opaque, that is, no graphics or image appears in the cells that are occupied by the mapped field. However, the map definition can contain a graphic area definition, for which a GSFLD call is issued automatically for the appropriate area, and in which the graphics is always visible.

5. The specification of the map position in the map definition can be overridden by the MSDFLD call.

6. Parts of the map that lie outside the page will not be visible to the operator. A warning message is issued if all the map is outside the page. An information message is issued if part of the map is outside the page.

7. If the map is defined as a floating map and is not explicitly positioned, the call is rejected if the floating area is full.

8. Any map can be explicitly positioned within the floating area of the current page. Any attempt to float another map into the same position is rejected.

9. If the page size was defaulted when the MSPCRT call was issued and if the mapgroup associated with the page does not match the current screen or partition, the floating area of the map may extend outside the current page. This can lead to a warning message being issued by MSDFLD.

Principal errors


ADM0966 E
PAGE n IS NOT MAPPED
ADM0968 E
ALPHANUMERIC FIELD a1 AND MAPPED FIELD a2 OVERLAP
ADM0970 E
MAP 'a1' IS NOT IN MAPGROUP 'a2'
ADM0971 E
ROW OR COLUMN IS LESS THAN -1 OR TOO LARGE
ADM0972 E
MAPPED FIELD a1 OVERLAPS MAPPED FIELD a2
ADM0973 E
INSUFFICIENT SPACE LEFT IN FLOATING AREA FOR MAPPED FIELD a
ADM0974 E
MAP 'a' FLOATS HORIZONTALLY BUT VERTICALLY FLOATING MAPS USED
ADM0975 E
MAP 'a' FLOATS VERTICALLY BUT HORIZONTALLY FLOATING MAPS USED
ADM0978 E
MAPPED FIELD ID n IS NOT GREATER THAN ZERO
ADM0990 W
MAP-DEFINED GRAPHIC FIELD IS OUTSIDE PAGE
ADM0991 W
MAPPED FIELD a IS POSITIONED OUTSIDE THE PAGE
ADM0992 I
MAPPED FIELD a IS PARTIALLY OUTSIDE THE PAGE

Go to the previous page Go to the next page



Copyright IBM Corporation 1990, 2012