Basic Mapping Support (BMS)

Basic mapping support
BMS support levels
Minimum BMS
Standard BMS
Full BMS
A BMS output example
Creating the map
Defining map fields: DFHMDF
Defining the map: DFHMDI
Defining the map set: DFHMSD
Writing BMS macros
Assembling the map
Physical and symbolic map sets
The SDF II alternative
Grouping maps into map sets
The Application Data Structure (ADS)
Using complex fields
Composite fields: the GRPNAME option
Repeated fields: the OCCURS option
Block data
Support for non-3270 terminals
Output considerations for non-3270 devices
Differences on input
Special options for non-3270 terminals
Device-dependent maps
Device dependent support: DDS
Finding out about your terminal
Sending BMS mapped output
Acquiring and defining storage for the maps
BASE and STORAGE options
Initializing the output map
Moving the variable data to the map
Setting the display characteristics
Changing the attributes
Attribute value definitions: DFHBMSCA
Using the SEND MAP command
SEND MAP control options
Other BMS SEND options: WAIT and LAST
Merging the symbolic and physical maps
MAPONLY option
DATAONLY option
The SEND CONTROL command
Building the output screen
What you start with
What is sent
Where the values come from
Outside the map
Using GDDM and BMS
Positioning the cursor
Sending invalid data and other errors
Output disposition options: TERMINAL, SET, and PAGING
Using SET
Receiving mapped data
An input-output example
The symbolic input map
Programming mapped input
Using the RECEIVE MAP command
Getting storage for mapped input
Formatted screen input
Modified data
Upper case translation
Using the attention identifier
Using the HANDLE AID command
Finding the cursor
Processing the mapped input
Handling input errors
Flagging errors
Saving the good input
Rechecking
Sending mapped output after mapped input
MAPFAIL and other exceptional conditions
EOC condition
Formatting other input
BMS logical messages
Building logical messages
The SEND PAGE command
RETAIN and RELEASE
The AUTOPAGE option
Terminal operator paging: the CSPG transaction
Logical message recovery
Cumulative output -- the ACCUM option
Floating maps: how BMS places maps using ACCUM
Page breaks: BMS overflow processing
Map placement rules
ASSIGN options for cumulative processing
Input from a composite screen
Performance considerations
Minimizing path length
Reducing message lengths
Text output
The SEND TEXT command
Text logical messages
Text pages
Text lines
Header and trailer format
SEND TEXT MAPPED and SEND TEXT NOEDIT
Message routing
Message destinations
Eligible terminals
Destinations specified with OPCLASS only
OPCLASS and LIST omitted
Route list provided
Route list format
Message delivery
Undeliverable messages
Recoverable messages
Message identification
Programming considerations with routing
Routing and page overflow
Routing with SET
Interleaving a conversation with message routing
The MAPPINGDEV facility
SEND MAP with the MAPPINGDEV option
RECEIVE MAP with the MAPPINGDEV option
Sample assembler MAPPINGDEV application
Partition support
Uses for partitioned screens
Scrolling
Data entry
Lookaside
Data comparison
Error messages
Partition definition
3290 character size
Establishing partitioning
Partition options for BMS SEND commands
Determining the active partition
Partition options for BMS RECEIVE commands
ASSIGN options for partitions
Partitions and logical messages
Partitions and routing
Attention identifiers and exception conditions
Terminal sharing
Support for special hardware
Logical device components
Defining logical device components
Sending data to a logical device component
LDCs and logical messages
LDCs and routing
10/63 magnetic slot reader
Field selection features
Trigger field support
Cursor and pen-detectable fields
Selection fields
Attention fields
BMS input from detectable fields
Outboard formatting
[[ Contents Previous Page | Next Page Index ]]