|
10. Menu System for Connections
In the previous chapter (Chapter 9, Connections), the commands for administering Connections were presented: OC to open a Connection, CC to resume a previously opened Connection, DC to terminate a Connection, and CD to display all open Connections.
The MENUE command of CFS provides a means of accessing Connections through predefined, formatted screens. The user does not have to be familiar with the individual CFS Connection administration commands. Marking an option in a predefined mask will cause CFS to open or to resume the required Connection automatically; i.e. CFS will substitute and execute the required command.
With a mouseclick you get a describtion of the screen item.
The Menu System for Connections offers the user the following facilities:
1) User-specific list of predefined Connections.
The parameters for Connections with which the user might wish to work can be stored in a so-called menu file. The Connection parameters include partner name, host system, virtual terminal name, LOGON/KDCSIGN command, and startup sequences.
In the standard Menu System mask, up to ten predefined Connections can be established. A background mask provides another ten Connections, which, if necessary, can be transfered to the main mask.
2) Marking a predefined option in the menu will open that Connection automatically, according to the parameters stored in the menu file. An automatic sequence of commands can also be executed (startup sequence), if specified. Should the marked Connection already have been opened by the user, a branch will be made to it.
3) Automatic maintenance of the Connection number. When opening a new process, the next free number will automatically be used.
4) Overview of all the Connections, whether open or not, and their status (ON/OFF). Pressing the K2 key in a Connection will automatically switch control back to the main menu mask. If the DKC (Direct K2 for Connection) mode is set, see page 9-), the user can only return to the main menu by using the escape symbol.
5) A set of P-key assignments for each process in the main menu mask can be created. Switching between the Connections will cause the respective P-key set to be reloaded.
6) The Connections predefined in the main menu mask can be changed, enhanced or reorganised by the user at any time by means of a Menu Editor. This edit facility may be restricted to privileged users.
For users unfamiliar with BS2000 and with CFS, e.g. non-technical users, the Menu System provides a unified tool for accessing the multiple Connection services offered by CFS. After the necessary preparatory work has been done, the user need only LOGON. The main menu will then be displayed, and the user can then begin processing from any relevant tasks, in parallel if desired.
The necessary preparatory work mentioned above, normally performed by the system administrator, includes the following:
a) Creating user-specific menu files, with startup sequences if required, for the various Connections.
b) Creating a LOGON-DO procedure called SYS.SDF.LOGON.USERPROC under the userid from which CFS will be called automatically when the user logs on. The prerequisite for this is SDF Version 1.4 or greater. The LOGON-DO procedure must contain the BS2000 commands to load CFS, as well as the CFS-internal command sequence up to and including the MENUE command. See Chapter 19 "Procedure Language" and Chapter 20 "CFS Startup" for further information.
The menu mask is called with the command MENUE or MENUE file.
The basis for displaying a menu mask is an existing menu file, unless a new file was specified explicitly in the command. This menu file will contain all the parameters for the Connections that will be needed by the user.
The command MENU file,N will create a menu file if one does not already exist under that name.
Marking a process displayed in the menu will transfer the user directly to that predefined Connection. Returning to the menu mask is achieved by pressing the K2 key. If the DKC (Direct K2 for Connection) mode is set, the K2 key function will be passed directly to the Connection. In this case, the only way to return to the menu is by means of the escape symbol, ^.
Switching directly between open Connections using the escape symbol (^n) is also possible when under control of the Menu System.
The user can exit the Menu System to CFS if that option has specifically been included in the menu file. Entering the abbreviated command 'C' in the first column of the menu, or pressing the K1 key will return the user to the CFS mask. The user could still access all the predefined Connections from here.
The CFS access described above will also allow the user to call the Menu Editor (by entering 'M' in the input field of a process, or in the global input field). The parameters associated with each process can be amended using this Menu Editor. New entries can also be added, and existing entries deleted. When leaving the Menu System, the user is asked if the changes made should be saved to the menu file.
Naming Hierarchy of the Menu File
The menu file to be used by the Menu System will be determined according to the following principles:
1) Was a file specified in the MENUE command?
2) Does a file command exist with a LINK=MENUE association (/FILE ...,LINK=MENUE) ?
3) If no TFT entry exists with the link name MENUE, then the Job name specified in the LOGON command (/.name LOGON ...) will be suffixed to 'CFS.MENUE.' If such a file name, CFS.MENUE.name exists, then it will be used as the menu file.
4) If no Job name was specified during the LOGON command, or if the file CFS.MENUE. name does not exist, the file CFS.MENUE under the current userid will be used.
5) If none of the above files exist, CFS will look for a file $user-id. CFS.MENUE , where $user-id is the userid under which CFS is stored.
The menu file is a sequential file containing all the parameters necessary to realise the users predefined Connections from within CFS.
A task description record from the menu file has the following format:
<1____8>__<11_________________________67>__<70_________________________104><105_12>
vvvvvvvvknccccccccc...................cccbbxxxxxx...................xxxxxxxpppppppp
| || | | |
| || | | {____________________________}
| || | |
optional: Name of a PLUS module
| || | |
for a specific set of P-key
| || | |
assignments for this process.
| || | |
The PLUS module must be contained
| || | |
in PLUS.MAPLIB, or in a library
| || | |
assigned with /FILE file,LINK=MAPLIB.
| || | | | || |
Text for a task description.
| || | | ||
Parameters needed by CFS to open the Connection. A valid OC command
| ||
should appear in this column range. The first three characters of the
| ||
OC command, OCn, should not be specified.
| || | ||
Examples: /LOGON user-id, acct-#, &(jv-name)
| || | | ||
see page 19-
| || | ||
$DIALOG,,HOST2/.&LOGNAM LOGON ......
| || | | ||
CFS-specific procedure variable. Contains the Job name
| ||
of the task under which CFS was loaded.
| ||
For further information, see page 19-.
| || | ||
OASE,CFS1
| ||
$CONSOLE,,HOST3,R R: Automatic return to the menu
| ||
mask after opening the Connection.
| || | || | |
0 - 9: Fixed Connection number, under which the Connection should be opened.
| || | |
_: When opening the Connection, the Menu System assigns the next free number
| |
to this Connection. The number used will be displayed in the #-column of
| |
the menu mask.
| | | | |
K2-Column B: Entering 'B' for a Connection passes the K2 key function to
|
the respective Connection.
| |
_: Entering 'B' for a Connection will be ignored, and the K2 key function
|
will not be passed to the respective Connection (necessary for UTM applications).
| |
Abbreviated name for the task. No duplicates are allowed. See the notes below for more information regarding the CFS task.
The menu file may contain up to 20 records with this format. The first 10 will be displayed in the main menu. Entering 'M' in the first selection column will switch control to the Menu Editor, from where all 20 tasks will be displayed in an overview. The sequence of the tasks 1 to 20 can be changed, so that for example, a task number 9 which is not needed at the moment can be replaced with task number 17, which was hidden in the background, and can then be displayed and activated.
Notes:
Switching from the Menu mask to CFS is only possible if an additional record appears in the menu file. This record must have CFS as the process name, and must contain blanks except in columns 105-112, where an optional P-key assignment set may be stored for working in CFS. If no such record exists in the menu file, the menu option 'C' (CFS) will not appear, and the user will not be permitted to break out to CFS. In this case, the Menu System, as well as CFS, can only be terminated by marking the last option in the menu mask, 'E' (ENDE).
The user can also branch to CFS by means of the Menu Editor, used to amend, add and delete task entries (Menu options).
With the exception of the 'CFS' entry, records may be inserted into the menu file either with EDT, or with the CFS Menu Editor (by entering 'M' Modify, see below). Creating or amending menu file entries with the Menu Editor presupposes that the user has the right to branch to CFS. The menu file must therefore already exist, and contain at least a record for the 'CFS' task.
A LOGON command can be given together with the OC command when connecting to $DIALOG, and also in the following descriptive record section. Two examples of this have been given above. If no LOGON password was specified in the LOGON command contained within the descriptive section, and a password is necessary to open the Connection, then it must be entered in the 'Password' field of the menu mask, when required. For a description of the menu mask, see below.
One or more records can be added to the menu file following the description of a Connection which would be interpreted as an automatic Startup sequence, and will be passed to the partner after the Connection has been successfully opened.
The Startup records in the menu file must have the following format:
<1_____9><10___________________________________________78>
bbbbbbbbbiiiiiiii...............................iiiiiiiiii
| |
| |
|
empty
|
|
Startup statements for Connection
e.g. KDCSIGN .... UTM task
/DO procedure,(...) $DIALOG
userid,C'passw' $CONSOLE: Connection message
RES file Replay a captured dialog sequence
Any number of Startup records for each task may be specified.
Any of the CFS procedure language statements (* statements) can also be used as Startup records. CFS-specific procedure variables can also be used. For a full description, see Chapter 19 "CFS Procedure Language".
With a mouseclick you get a describtion of the screen item.
Description of the mask fields:
The name of the menu file being used is displayed in the 'Menue : xxxxxxxxxxxxx' field. The terminal name from which CFS was called is displayed in the 'Station : ssssssss' field. These fields, xxxxxxxx and ssssssss, could be useful, for example, in assisting the system administrator when answering queries from non-technical users.
A line in the menu is displayed for each predefined Connection. This consists of a single digit input field, a Connection number (# column) that was either predefined, or allocated when the Connection was opened. It is followed by the name of the host system on which the Connection was opened, an abbreviated name of the task or Connection, as well as a full description. The Status column is controlled by CFS, and will show a value of ON or OFF, depending on whether or not that Connection has been opened.
In the global input field in the title line, a Connection number can be entered directly. Either control will be passed to the Connection already opened, or a new Connection to the required process will be opened using the specified number. In addition to a Connection number, the codes C (return to CFS), E (terminate all tasks, including CFS), M (jump to the Modify Menu), or S (Save) can be entered in the global input field. A full description of the individual codes is given later.
If an X is entered in the line "CFS Program CFS", the user will switch from the Menu system to the command line of CFS. The user can switch to any Connection already opened with a CC (Continue in Connection) command.
Permission for the user to switch from the Menu system to CFS (CFS permission) must have been explicitly granted by means of an entry in the menu file (see page 10-). Those users with CFS permission may additionally invoke the Menu Editor, and can modify, copy and delete menu items. These changes are temporary, and will be lost when CFS is terminated, unless the user chooses to save them to the menu file.
Marking the "ENDE Terminate all Connections" line with an X will close the Menu system and terminate CFS. The ENDE function will close all open Connections with a DC (Disable Connection) command, and then terminate CFS.
If CFS had been loaded with a Startup sequence containing an '*ON %END CONTINUE' statement, the open Connections will not be terminated with the DC command. In this case, the Startup sequence will be continued at the point at which it had been interrupted. The following Startup sequence commands could then, for example, also contain commands to close any opened Connections in a controlled manner (Shutdown sequence). A detailed example of a Startup file containing a Shutdown command sequence can be found in Chapter 20 "Startup File".
The dark 'Password' field in the last line of the menu mask is used to enter a LOGON password. This field must be empty if the password has already been specified in the LOGON command in the menu file.
The dark 'Lock' field in the last line of the menu mask allows the user to lock the screen against unauthorised access, for example if the terminal is to left unattended. If a password is specified, nothing can be entered or displayed until the user re-enters that password.
Global Input Field in the title line:
n A number displayed in the # column of a task can be entered here. The effect is the same as if the respective menu item had been marked with an X, i.e. the Connection is opened (if Status = OFF), and control will switch to this Connection.
C Return to the CFS program. The K1 key has the same effect of quitting the Menu system and returning to the command line of CFS. The menu mask can be reactivated at any time by entering a MENUE command.
A particular entry in the menu file will permit or prohibit the user from accessing the CFS "task", i.e. from using the "File Services".
E Terminate the Menu system and CFS. The ENDE function terminates all opened Connections with a DC (Disable Connection) command, and then terminates the CFS program.
If a Startup file containing a Shutdown command sequence was used to load CFS (see Chapter 20), then entering 'E' will cause the Shutdown command sequence defined in the Startup file to be executed. In this case, the open Connections will not be terminated by the Menu system with a DC command.
M Modify. The Modify menu will be invoked. The Modify menu has space for up to 20 entries, and allows the individual menu items to be modified, copied, deleted, or their sequence to be changed. Changing the sequence of the menu items can shift menu items from the background to the main mask, in which only Connections numbered 0 through 9 are displayed.
S Save. 'S' will overwrite the menu file with the current values in operation. Normally, the user will only be asked if the menu file should be updated after exiting the system with 'C' (CFS) or 'E' (ENDE).
If the user does not have permission to invoke CFS (no 'CFS' entry in the menu file), the 'M', 'C', and 'S' entries in the global input field will be ignored.
The Input Field for each menu item will accept one of the following entries:
A Abort. A DC (Disable Connection) command will be generated for this Connection. This function is equivalent to switching off the terminal, and should really only be used for Connections to $CONSOLE.
As far as possible, the task should be terminated normally (e.g. by entering a LOGOFF command to a $DIALOG task, or a KDCOFF command to a UTM task).
B This entry is only relevant to $DIALOG Connections. It simulates pressing the K2 key in the respective Connection.
C Copy. The menu item is marked in preparation to be copied. The target of the Copy operation is marked with 'T' (To). The result of the Copy operation will be displayed in the menu mask immediately. Upon exiting the Menu system with 'E' (ENDE), or with 'C' (CFS), the user will be asked if these amendments should be saved by overwriting the menu file.
If the user does not have permission to invoke CFS (no 'CFS' entry in the menu file), the 'C' and 'T' entries in the input field will be ignored.
D Delete. The respective menu item will be deleted. The result of the Delete operation will be displayed in the menu mask immediately. Upon exiting the Menu system with 'E' (ENDE), or with 'C' (CFS), the user will be asked if these amendments should be saved by overwriting the menu file.
If the user does not have permission to invoke CFS (no 'CFS' entry in the menu file), the 'D' entry in the input field will be ignored.
M Modify. The Menu Editor will be invoked. All the parameters relating to the marked menu item will be displayed in a special mask, from where the user may make the required changes. The user returns to the Menu mask by pressing the K1 key. The modifications to the menu item are effective immediately. Upon exiting the Menu system with 'E' (ENDE), or with 'C' (CFS), the user will be asked if these amendments should be saved by overwriting the menu file.
If the user does not have permission to invoke CFS (no 'CFS' entry in the menu file), the 'M' entry in the input field will be ignored.
X Open the Connection automatically, if Status = OFF.
Branch to the Connection, if Status = ON.
More than one task can be marked with X simultaneously. In this case, those Connections are opened, their Status set to ON, and the menu mask displayed again.
n 0 <= n <= 9: Replace the marked item with the item numbered n. In this way, the sequence of the menu items in the mask can be changed.
With a mouseclick you get a describtion of the screen item.
Possible entries in the Command field of the Modify Menu mask:
/cmd Any BS2000 command.
END | K1 Return to the Menu mask.
HC | NHC Set/reset Hardcopy mode.
MENU file A new menu file is read into memory. This file is made current when returning to the menu mask.
F3 Capture the current screen to the CFS hardcopy file.
Possible entries for each item in the marker column (M):
C Copy. This item is marked for copying. The target of the copy operation should be marked with 'T' (To).
D Delete. The marked item is deleted.
M Modify. The Menu Edotor is invoked. All of the parameters relating to this item will be displayed in a special mask, and can be modified as required.
n 0 <= n <= 9: Replace the marked item with the item numbered n. In this way, any of the hidden items numbered 10 to 19 can be transfered to occupy any of the positions 0 through 9, and can so be displayed in the menu mask.
With a mouseclick you get a describtion of the screen item.
Possible entries in the Command field of the Modify Menu Item mask:
/cmd Any BS2000 command.
HC | NHC Set/reset Hardcopy mode.
MENU file A new menu file is read into memory. This file can then be processed in this same mask.
K1 Return to the Menu mask.
F3 Capture the current screen to the CFS hardcopy file.
"OC-Command" Field
Statements needed by CFS to open a Connection. A valid OC command should be entered in this field. The first three characters of the OC command (OCn) must not be specified. If nothing is specified in this field, a connection to $DIALOG on the users own host will be opened. The LOGON command must be executed manually by the user when the Connection is opened, or it can be specified in the "Commands after Open-Connection" field.
Examples:
$DIALOG,,HOST2/.&LOGNAM LOGON ......
&LOGNAM: CFS-specific procedure variable. It contains the Job name of the task from which CFS was loaded.
/LOGON userid,acct-#,&(jv-name)
The LOGON password is stored in the Job variable 'jv-name'.
OASE,CFS1
$CONSOLE,,HOST3,R
R: Automatic return to the Menu mask after opening the Connection.
"Comment" Field
The description of the process that will be displayed in the description column of the Menu mask can be entered here. Lower case letters will not be converted to upper case.
If nothing is specified in this field, the following parameters will appear in the description field after the Connection has been opened: partner name (e.g. $DIALOG), virtual terminal name, host name, and userid if the Connection is to $DIALOG.
"Program" Field
Abbreviated name for the Connection. This abbreviation will appear in the "Task" column of the Menu mask. No duplicate abbreviations are allowed in the same Menu mask. If lower case letters are used, they will be converted to upper case.
"Connection-number or space" Field
n 0 <= n <= 9 Fixed Connection number under which the Connection should be opened.
_ Blank: The Menu System will assign the next free number when attempting to open the Connection. Numbers that have been specified as fixed (see above), will have been reserved. The number allocated will be displayed in the # column of the Menu mask, following the Connection being successfully opened.
"Break (B) allowed (Y/N)" Field
B Entering 'B' for a Connection will allow the K2 key function to be transmitted in that Connection.
_ Blank: 'B' will be ignored, and the K2 function will not be transmitted for that Connection (necessary for UTM tasks).
"Plus-Module for P-keys" Field
Optional name of a PLUS module for a specific P-key assignment. The module must reside in PLUS.MAPLIB or in an LMS library previously assigned with /FILE file,LINK= MAPLIB.
"Commands after Open-Connection" Field
This area can contain up to 12 statements which will be sent to the Connection as a Startup sequence, following it being successfully opened. Lower case letters will be converted to upper case.
Any CFS procedure language statements ('*' statements) can be specified as Startup records. CFS-specific procedure variables can also be used. For a full description, see Chapter 19 "CFS Procedure Language".
Examples:
KDCSIGN ....
Connect to a UTM task
/DO procedure,(...)
Call a DO procedure after connecting to $DIALOG.
userid,C'passw'
Pass the message header when connecting to $CONSOLE.
RES file
Replay a captured dialog session.
Editing multiple lines in the "Commands after Open-Connection" field
Various editing facilities are available to delete, insert and copy existing lines. These commands should always appear at the beginning of the line to be edited.
,c Copy. The marked line is to be used as the source for a Copy operation. The line contents overwritten by the ,'c' operator will be copied as well.
,m Move. The marked line will be moved. The location to which it should be moved is defined by ',a', ',b' or ',o'. The line contents overwritten by the ',m' operator will remain unaltered.
,a After. The line marked with ',c' or ',m' will be inserted after this line. The line contents overwritten by the ',a' operator will remain unaltered.
,b Before. The line marked with ',c' or ',m' will be inserted before this line. The line contents overwritten by the ',b' operator will remain unaltered.
,o Over. This line will be overwritten with the contents of the line marked with ',c' or ',m'.
,d Delete. The marked line will be deleted.
,i Insert. A blank line will be inserted in front of the marked line.
User-specific Layout of the Menu Mask
Normally, the Menu mask will appear as laid out on page 10-. If required, the system administrator or even each user can design their own specific Menu mask layout. This design will be stored in a format file, which must be a SAM file. CFS follows the following sequence in trying to find a format file:
1) Has a file command been issued with LINK=MENUFOR ?
2) CFS will look for a file under the current userid called CFS.MENU.FORMAT.name, where name is the Job name specified in the LOGON command (/.name LOGON ...).
3) If a Job name was not specified in the LOGON command, or if the file CFS.MENU. FORMAT.name does not exist, CFS will look for a file called CFS.FORMAT under the current userid.
4) If none of the above files exist, CFS will look for a file called $userid.CFS.MENU.FORMAT, where $userid is the userid under which CFS is stored.
The contents of the format file below define the standard layout of the Menu mask.
*------------------------------------------------------------------------------* ! $H CFS - Dialog control $R Host: %HOST TSN: %TSN %DATG %TIME ! *------------------------------------------------------------------------------* ! Menu : %MENU Station: %TERM ! ! Select task (X = Select, A = Abort, B = K2 key, M = Modify) ! ! or enter task number from # column ! *------------------------------------------------------------------------------* ! %Z! $U#$R $UHost$R ! $UTask$R ! $UDescription$R ! $UStatus$R ! *------------------------------------------------------------------------------* ! %a! $H%A$R%RA ! %VA ! %TA ! %SA ! ! %b! $H%B$R%RB ! %VB ! %TB ! %SB ! ! %c! $H%C$R%RC ! %VC ! %TC ! %SC ! ! %d! $H%D$R%RD ! %VD ! %TD ! %SD ! ! %e! $H%E$R%RE ! %VE ! %TE ! %SE ! ! %f! $H%F$R%RF ! %VF ! %TF ! %SF ! ! %g! $H%G$R%RG ! %VG ! %TG ! %SG ! ! %h! $H%H$R%RH ! %VH ! %TH ! %SH ! ! %i! $H%I$R%RI ! %VI ! %TI ! %SI ! ! %j! $H%J$R%RJ ! %VJ ! %TJ ! %SJ ! ! %k! $H%K$R ! CFS ! CFS Programm ! ! ! %l! $H%L$R ! ENDE ! Terminate all Connections ! ! *------------------------------------------------------------------------------* ! Password: >%PASS < Lock: >%LOCK < ! * %MESS *
In addition to constant values, the format file also contains variables designating particular mask fields, as well as control sequences for display characteristics.
Variables designating Mask Fields
Variables always begin with a % character, and can be placed anywhere within the mask. In the mask, variables need as many positions as specified in their length (see below). All the variables available for format files are listed below.
Variables for input fields. These will be double intensity fields in the mask.
%Z Global input field of the Menu mask. Length = 1 + 1 protected blank character.
%a Input field for Task 0. Length = 1 + 1 protected blank character.
%b Input field for Task 1. Length = 1 + 1 protected blank character.
...
%j Input field for Task 9. Length = 1 + 1 protected blank character.
%k Input field for CFS task (return to CFS). Length = 1 + 1 protected blank character.
%l Input field for ENDE transaction (terminate all tasks). Length = 1 + 1 protected blank character.
%PASS Input field for the LOGON password. Length = 11.
%LOCK Input field for the LOCK function for temporarily barring access to the terminal. Length = 8.
Variables for output fields. These fields will normally appear in the mask at half brightness, unless displayed otherwise by a specific parameter.
%A Connection number for Task 0. Length = 2.
%RA Host for Task 0. Length = 8.
%VA Abbreviated name for Task 0. Length = 8.
%TA Description for Task 0. Length = 35.
%SA Status information for Task 0. Length = 3.
...
%J Connection number for Task 9. Length = 2.
%RJ Host for Task 9. Length = 8.
%VJ Abbreviated name for Task 9. Length = 8.
%TJ Description for Task 9. Length = 35.
%SJ Status information for Task 9. Length = 3.
%K 'C ' for CFS task (return to CFS). Length = 2.
%L 'E ' for ENDE transaction (terminate all tasks). Length = 2.
%TSN TSN of the task from which CFS was called. Length = 4.
%DATG Current date in dd.mm.yy format. Length = 8.
%DATE Current date in mm.dd.yy format. Length = 8.
%TIME Current time in hh:mm:ss format. Length = 8.
%HOST Name of the host system from which CFS was called. Length = 8.
%USER Userid from which CFS was called. Length = 8.
%MENU Name of the menu file. Length = 40.
%TERM Name of the terminal from which CFS was called. Length = 40.
%MESS Message text (Note about the Help function, reason for loss of Connection, etc.). Length = 70.
Control characters for changing the display characteristics of the output fields. Normally, output fields are displayed at half brightness. The following control sequences are two bytes long and begin with a $ character, but do not take up any space in the mask. The mask definition will thus be lengthened by two bytes for each control sequence.
$B Double brightness and underlined
$H Double brightness
$U Underlined
$R Reset. Half brightness, not underlined
Error messages for mask definition:
000001 invalid name for a % variable
000002 input variable (%a, ..., %l, %PASS, %LOCK) multiply defined
000003 input variable (%a, ..., %l, %PASS, %LOCK) is missing
000011 invalid control sequence ($B, $H, $U, $R)
Note: The standard format definition, as well as an alternative layout are supplied in the CFS.S.LMSLIB library under the element name X/CFS. MENU.FORMAT.1 and 2. The mask defined under the name CFS.MENU.FORMAT.2 will look as follows:
}dd.mm.yy hh:mm:ss Host: ........ TSN: .... Station: ssssssss {
} {
} Application Menu {
} {
} # Host Application Text Status {
}---------------------------------------------------------------------------------{
} HOST1 UTMTEST UTM application Stock (TEST) OFF {
} 0 HOST2 CONS-2 UCON Connection to Host 2 ON {
} HOST1 ODR1 $DIALOG with UseriD $ODR1 OFF {
} 1 HOST3 SAP-P SAP Connection (Live) ON {
} 4 HOST1 SAP-T1 SAP Connection (Test 1) OFF {
} 5 HOST2 SAP-T2 SAP Connection (Test 2) OFF {
} {
} {
} {
} {
} C CFS Return to CFS {
} E END Terminate all applications {
}---------------------------------------------------------------------------------{
} Password : >...........< Lock: >........< {
} {
}Menu-File used : xxxxxxxxxxxxxxxxxxxxxxxxxx {
}select application : X = activate, A = abort, B = break (K2), M = modify {
}for Help type "?" at any Input-Field {