User's Manual

5250 Connect User’s Guide
34
 The new screen is displayed in the Native Environment pane.
 A Map Screen action appears in the Action Model. The Map Screen action is
where you will add, change, and delete actions for this particular screen.
Each time a new screen block is received as you build the component, a new
Map Screen action is created.
 The Map Screen action calculates and records how many TDS fields were
received for this particular screen. This information is used for validation
purposes the next time the component is run.
 The ScreenDoc DOM is refreshed with a new DOM that reflects the screen
just received. Block mode terminals send their data as a stream of fields.
These fields are defined using screen creation utilities in the host
environment (such as BMS in CICS).
The fields are represented in the ScreenDoc DOM in the order they appear on the
screen starting from the upper left corner of the screen, moving across to the right,
then down a row starting again at the left and so on until the entire 80x24 or
132x27 screen area is covered. Depending on how the original screen layout was
defined, there can be many fields. Some FIELDs are text labels on the screen and
usually have display attributes of protected (prot) and bright (brt). Some FIELDs
are for data entry and have an attribute of unprotected (unprot). Other FIELDs
contain data but are hidden from display with an attribute of dark (drk). Finally
there are special screen fields for implementing tabbing features on the screen,
which are protected from entering data and called bypass fields with an attribute
of bypass.
The end result of listing all the TDS fields is that the ScreenDoc DOM can be quite
large. Its use is primarily intended for finding hidden fields, verifying fields and
their locations by their attributes, and in cases where it is convenient, mapping
from the ScreenDoc DOM to the Output DOM using Composer’s drag and drop
features.
NOTE: Normally it is much quicker and more efficient to map directly to and from
the Native Environment pane using drag and drop instead of mapping to the
ScreenDoc DOM.
Each field in the TDS is represented in the ScreenDoc DOM as an element titled
FIELD. The ScreenDoc DOM contains as many FIELD elements as there are
fields in the TDS. The element displays any data defined for the field. Note that
screen fields are used for both field labels and data-entry fields.