A typical mapping cycle

GDDM V3R2 Base Application Programming Guide

A typical mapping cycle

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

The diagram in Figure 85 in topic 15.3.2 shows some of the major steps that a typical mapping program goes through.

Figure 85. Typical cycle of mapping operations

First, the application executes an MSPCRT call to create a mapped page. The page is given the identifier 4, and is associated with a mapgroup called MAPGRPD6. The mapgroup has three maps in it, called MAP99, MAP100, and MAP101.

An MSDFLD call puts the map called MAP99 onto the page. MAP99 contains two constant data fields, the values of which are NAME: and SALARY:, and two variable data fields. The program puts the variable data "J SMITH" and "12345" into this map's ADS, called ADS99, and then executes an MSPUT call to copy the data into the variable fields on the page. A second MSDFLD call puts a second map, MAP101, onto the page. This contains just the constant data "XXXXXXXX". The third map in the mapgroup, MAP100, is not used in this execution of the program.

An ASREAD call sends the page to the terminal, and waits for operator input. When this arrives, GDDM updates the page. The application accesses the input by executing an MSGET call to copy the variable data from the page into the ADS.

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