You can change the parameter settings in the workspace/window configuration menu programmatically by using escape sequences. Normally the escape sequences are issued from a program executing in a host computer but they may also be entered through the keyboard.
The "'=&W sequence altetls the particular parameter in the menu, and the new setting takes effect immediately, but it does NOT alter the content of non-volatile memory. If
an
"'='w
sequence is received while a configuration menu isbeing displayed on the terminal's screen, the menu is first removed from the screen and the escape sequence is then executed.
The"'='q sequence, on the other hand, alters the particular parameter in non-volatile memory. The new configura-tion values become active immediately. Note that the "'='q sequence is ignored if received while any configuration menu is being displayed on the terminal's screen.
Lock/Unlock Configuration
Using an escape sequence you can "lock" the current workspace/window configuration menu so that the menu cannot be accessed from the keyboard. Any attempt to access a locked menu from the keyboard will result in the
"FUHCT I 01'1 LOCKED" error message; the terminal operator clears the message by pressing _ . An "'='q sequence will alter the content of non-volatile memory even when the configuration is locked.
Note: When ANY workspace has its keyboard locked the configuration menus are locked for ALL workspaces.
To lock the menu, use either of the following escape se-quences:
To programmatically alter the workspace/window configuration parameters in non-volatile memory, use an
"'='q sequence. The new configuration values become ac-tive immediately. You will notice that you may also in-clude a configuration lock/unlock command (described earlier) in the escape sequence.
2-12
Note that an "'='q sequence is ignored by the terminal if received while any configuration menu is being displayed on the screen.
When you issue an "'='q sequence the terminal normally takes the current menu values from non-volatile memory and then alters only those fields (parameters) that you specifically include in the escape sequence. If you include the command parameter "d" at the start of the escape se-quence, however, the terminal will first set all of the fields in the menu to their default values and then alter those fields (parameters) that you specifically include in the es-cape sequence.
The general format of the workspace/window"'='q se-quence is as follows:
"'='q 3t
[<lock/unlock>l]
[d] (initially sets all menu fields to default values) [e] (signals start of individual field definitions) o <Kybd Wk!!!p>a
The "e" command parameter specifies that the remainder of the sequence defines one or more workspace/window configuration parameters. The parameters in the "0"
subgroup are those of a more general nature (that is, they do not specify the physical structure of a particular workspace and/or window). The parameters in "1", "2",
"3", or "4" subgroups define the physical structure of workspaces one through four,respectively, and their asso-ciated windows (if any). With the following exceptions, the parameter value supplied is the same as that which you would enter into the particular field in the menu:
<Start Row>u
For the <Start Row> and <Stop Row> parameters the rows are numbered 0-23 (instead of 1-24 as in the menu).
For the other parameters the supplied value is a zero or a one which has the following meanings:
Horiz
--~---Side 0
=
RIGHT (Default=
0) 1=
LEFTLock/Unlock 0 = unlock menu (Default = 0) 1 = lock menu
Open/Close 0
=
close (delete) specified window 1=
open (create) specified window The final parameter identifier character in the escape se-quence must be an uppercase letter; all preceding ones must be lowercase.
Example: Define workspaces 1, 2, and 3 with a single win-dow initially attached to workspace 1. The line length in display memory will be 100 and each workspace will contain 30 lines. Workspace 1 will initially be attached to data comm port 2.
The window will encompass the entire screen (rows 0-23). All three workspaces will be asso-ciated with the Term #1 configuration menu.
The workspace/window configuration will be locked.
(the equivalent of setting the menu field to a blank) because the default value for that field is "1" and we wish to define the port #2 workspace as "1". The two ports CANNOT be attached to the same workspace. If we had omitted the "op" parameter the sequence would have been rejected when the" 1 q"
parameter was encountered.
You can use either a single escape sequence (as illustrated above) or you can use a series of escape sequences. If you specify an invalid parameter within an Ii:&q sequence the sequence is rejected. In such a case both the active and non-volatile versions of the Workspace/Window Configu-ration menu remain as they were before the erroneous es-cape sequence was issued.
When issuing a series of Ii:&q sequences there are a few things that you must be particularly careful with, as fol-lows:
1. If you are specifying a left/right orientation for a dis-play window the vertical border must already be de-fined (either earlier within the same escape sequence or in a preceding one).
2. You should specify the page width before defining any workspaces. As with a single escape sequence you must also make sure that the overall configured size of dis-play memory (sum of all <Rows> X <Page Width»
does not exceed 9520.
Workspaces and Windows 3. When defining multiple windows on the same side of the vertical border, the upper and lower bounds of one display window must not overlap those of another.
After each Ii:&q sequence you can verify that the particular parameter(s) were accepted by issuing one ofthe window status escape sequences described in Section VIII of this manual.
Temporary Reconfiguration
To programmatically reconfigure display memory and the screen WITHOUT altering non-volatile memory, use an Ii:&w sequence as follows:
1. CREATE A WORKSPACE:
Ii:&w Of <rows)n <workspace')!
where rows
workspace'
is an integer specifying the num·
ber of rows to be allocated to the workspace.
is the workspace's number (1·4).
2. DELETE A WORKSPACE:
where workspace'
Ii:&w lf <workspace')I
is the workspace's number (1·4).
3. DEFINE A WINDOW:
Ii:&w 2f <workspace')i
where workspace'
<starting data row)d
<starting screen row)u
<ending screen row)l (side)S
is the number (1·4) of the asso-ciated workspace.
starting data row is an integer specifying which line of data within the workspace is to be displayed initially in the
side is an integer specifying on which
side of the vertical border the window is to reside (O=right;
1 = left).
2-13
Workspaces and Windows
~&w 3f <workspace#)1
is the number (1-4) of the asso-ciated workspace.
MOVE THE CURSOR TO A SPECIFIED WIN-DOW:
~&w 4f <workspace#)1 where
workspace#
SET LINE LENGTH:
is the number (1-4) of the workspace associated with the desired window. Note that there must be a window defined for the specified workspace (Display field = YES) or else the escape sequence has no effect.
~&w Sf <line length)W where
line length is an integer specifying the de-sired line length for all workspaces. This parameter must be a multiple of four within the range 80-160 .. If it is not a multiple of four, the terminal ig-nores the escape sequence.
Note that whenever you change the line length using this escape sequence the terminal's screen and display memory are both reconfigured immediately using the new line length (all data in display memory is cleared).
7. DEFINE VERTICAL BORDER:
8.
where column#
~&w Sf <column#)C
is an integer specifying the screen relative column (0-80) at which you want the vertical bor-der to occur.
ATTACH A DATA COMM PORT TO A WORKSPACE:
~&w 7f <port#>p <workspace#)1 where
is an integer (1-4) specifying the particular workspace to which you wish to attach the specified data comm port.
2-14
- - - _ . __ ._._._. _ . . __ . __ . _
-9. ATTACH DATA COMM CONFIGURATION TO A DATA COMM PORT:
~&w Sf <port#)p <configuration#)G where
<port#)
<configuration#)
is a 1 or 2 specifying the data comm port to which you wish to attach the specified menu.
is a 1 or 2 specifying the cur-rently defined "datacom 1" or
"datacom2" configuration menu, respectively.
10. ATTACH A TERMINAL CONFIGURATION TO A WORKSPACE:
~&w Sf <term config#)t <workspace#)!
where
is an integer (1-4) specifying the particular workspace to which you wish to attach the specified menu.
11. MOVE CURSOR TO NEXT WINDOW:
~&w 10F
Note that this escape sequence has exactly the same effect as pressing the "NEXT WINDOW" function key
Note that this escape sequence has exactly the same effect as pressing the "NEXT WORKSPCE" function key
< . . in the "window control" set of system func-tion keys).
If you use any of the above escape sequences in a manner that is inconsistent with the current terminal configura-tion then the escape sequence is ignored. For example, if you attempt to move the cursor to a non-existent workspace (#5, above) the escape sequence is ignored.
Similarly, if you attempt to move the vertical border to column 0 (#7, above) and there are one or more existing windows to the left of the border the escape sequence is . ignored.
If you attempt to redefine an existing display window using escape sequence #3, above, and the escape sequence contains an erroneous parameter the window is removed from the screen (the "Display" parameter is changed from "YES" to "NO") but the rest of its definition remains unchanged.
(
(
W orkspaces and Windows When issuing a series of £':&w sequences there are a few
things that you must be particularly careful with, as fol-lows:
THE