Note:
Causing data to be sent back is not necessarily an efficient way to pass data from program to program. v
Insert-cursor indicator
The insert-cursor indicator is not a field attribute. Instead, it places the cursor under the first data character of the field whenever the map is sent with the
ERASE option. If the insert-cursor indicator is specified for more than one field, the cursor is placed under the first data character of the last field specified. If no insert-cursor indicator is specified, the cursor is placed at position zero (row one, column one) on the display screen.
Note:
If symbolic cursor is explicitly specified, this overrides the insert-cursor indicator option. v
Background transparency
Background transparency determines whether the background of an alphanumeric field is transparent or opaque; that is, whether an underlying
(graphic) presentation space is visible between the characters.
This feature is not supported by the 5250 architecture. However, you may define this feature in maps because BMS will prevent the attribute being placed in output data streams to a 5250 device. v
Field outlining
Field outlining allows lines to be included above, below, to the left, and to the right of a field. You can use these lines in any combination to construct boxes around fields or groups of fields. v
SO/SI creation
SO/SI creation indicates that the field may contain a mixture of single-byte and double-byte character set (DBCS) data. The DBCS subfields within an EBCDIC field are delimited by SO (shift out) and SI (shift in) characters. SO and SI both occupy a single screen position (normally displayed as a blank). They can be included in any non-DBCS field on output if they are correctly paired. The terminal user can transmit them inbound if they are already present in the field, but may only add them to an EBCDIC field if the field has the SOSI attribute.
Not all devices support all the attributes. BMS ensures that attributes not supported by the device (as specified in the terminal definition) are ignored when building the data stream.
Screen layout design
The features of the 3270 system allow screen layouts to be designed for operator convenience and efficiency. The success of an online system depends on its ease of use, screen clarity, and terminal operator acceptance.
Refer to the following manual for information about screen layout design and user dialog flows: v
SAA CUA Basic Interface Design Guide
, SC26–4583
The following features of some 3270 and 5250 displays make it easier for the layout designer to meet the requirement of ease of use: v
Color v
Field highlighting v
Ease of correction v
Numeric shift for numeric data
146
CICS for iSeries Application Programming Guide V5
