When specifying a location within a presentation space, Screen object methods use column and row coordinates to specify the cursor position. Standard presentation space sizes for supported terminal types are shown in the table below.
Note, however, that the actual presentation space size is based on the Display Properties, as specified in the terminal configuration.
| Terminal Type |
Rows |
Columns |
Total Size |
|---|---|---|---|
| 3270 | 24 | 80 | 1,920 |
| 32 | 80 | 2,560 | |
| 43 | 80 | 3,440 | |
| 27 | 132 | 3,564 | |
| 5250 | 24 | 80 | 1,920 |
| 27 | 132 | 3,564 | |
| T27 | 24 | 80 | 1,920 |
| UTS | 24 | 80 | 1,920 |
| 24 | 132 | 3,168 | |
| VT | 24, 25, 36, 48, 72, or 144 |
80 or 132 | 1,920 to 19,008 |
| ALC | 14 | 64 | 960 |
| 23 | 64 | 1,472 | |
| 23 | 80 | 1,840 | |
| 30 | 64 | 1,920 | |
| 24 | 80 | 1,920 |
 |
The row totals shown in the table above do not include the operator information area (OIA). The OIA, also known as the status line, appears at the bottom of each screen and contains information about the session status (such as which mode the screen is in) and other information (the location of the cursor, for example).
A T27 session can also display a line of information between the presentation space and the OIA; this is known as the user message. You can obtain this information using the SDK getOIAText method (Javadoc and .NET). |
The sizes shown in the table above are configured sizes, and represent the largest possible presentation-space sizes for each terminal. Host applications can specify a subset of the presentation space to use; when this happens, the result is the current size. The current size is always less than or equal to the configured size. The Attachmate Verastream SDK for Unisys and Airlines objects can work with either configured sizes or current sizes.
 |
|
 |
The Presentation Space |
 |
Fields and Attributes |
 |