|
Format of the Menu File
The menu file is a sequential file containing all the parameters necessary to realise the users predefined Connections from within CFS.
For a full description of the menu file, see Chapter 10 of the User Manual.
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.