|
Certain conventions have been used in this manual to explain the concepts involved. This meta syntax is described in the table below:
Representation Description Example
UPPER CASE Upper case letters indicate SO AGE
constants that have to be
entered exactly as shown. Enter as:
SO AGE
italics italic lower case letters ONXADD library
indicate variables for which
the user must substitute his/ Enter as:
her current value, i.e the ONXADD LMS.PROC
contents will vary from ONXADD $TSOS.MACROLIB
case to case. etc.
[ ..... ] square brackets indicate LOG [lib](elem)
optional entries. These
may be included or omitted Enter as:
as required. If a comma is LOG XYZ.LIB(TEST)
present within the brackets, LOG (TEST)
it will only be expected if
this option is used.
Brackets (..) must always
be entered as shown
| The pipe symbol (vertical slash) LOG [file | lib(elem)]
separates two alternative entries.
It is important to distinguish Enter as:
whether the pipe symbol is LOG CFS.LOG
enclosed within square or LOG CFS.LIB(TEST)
curly brackets. LOG
{ ..... } Curly brackets indicate LOG {file | lib(elem) }
alternative entries, i.e.
one of the enclosed Enter as:
values must be specified. LOG CFS.LOG
LOG CFS.USERLIB(TEST)
AAAAAA Underlining indicates the SO [AGE | NAME | SIZE]
standard value. This is the
value substituted by CFS if Enter as:
the user does not specify SO AGE
any value explicitly. SO NAME
SO SIZE
SO SO will have the
SO same effect as SO NAME
Representation Description Example
_ This symbol depicts a DO_
blank character (X'40').
Enter as:
DO + a blank.
< This symbol depicts the --<
End marker on the keyboard.
On some keyboards, this key Enter as:
will be marked as EM . -- + End marker.
DUE1 This symbol depicts the DUE1 --< DUE1
key on the 9750 terminals.
This key is labeled ENTER Enter as:
on newer terminals. -- + End marker + DUE1
or ENTER.
DUE2 This symbol depicts the DUE2 -- DUE2
key on the 9750 terminals.
This key does not appear on Enter as:
newer terminals. The DUE2 -- + DUE2 or
function is achieved by SHIFT + ENTER.
pressing SHIFT and ENTER
simultaneously.
LSP This symbol depicts the LSP
(Clear Screen) key on the
9750 terminals. This key
does not appear on newer
terminals. The LSP function
is achieved by pressing
SHIFT and RESET simultaneously.
K1 These symbols depict the
K2 special data transfer
K3 message keys K1, K2, K3, etc.
F1 Theses symbols depict the
F2 respective data transfer
F3 function keys.
Action Code
An Action Code is a one to five digit alphanumeric string that can be entered in the Action column of every entry in a file list. Action Codes represent simple commands, and have no parameters. If small numbers of files/library elements/Job variables in a list are to be processed, these Action Codes simplify the operation considerably.
Connection
A Connection is an independent dialog session with $DIALOG or a DCAM/UTM application that may be started and terminated at any time by the user. Each time CFS is loaded, up to 10 Connections may be opened. Switching between the individual connections is achieved by pressing the K2 key, and then entering the required Connection number.
File list
After entering the relevant selection criteria, the data objects (files/library elements/Job variables) meeting those criteria are displayed in a concise, informative mask.
In addition to all the normal BS2000 commands, a large number of CFS commands may be entered in the command field of the file list. These commands provide file processing and additional services. In addition, each entry in the file list will have an Action column into which different Codes can be entered and executed.
Hardcopy
The contents of a screen can be accurately captured by CFS to a printable file. The hardcopy mode can be activated in all CFS screens, as well as in each Connection opened by CFS.
Help System
The Help System is a facility of CFS that provides the detailed presentation of the CFS Reference Manual on screen in a simple, structured manner. This information is available for all commands and input fields, and is context-sensitive.
Job Report
The Job Report System provides the facility for running DO procedures as Enter jobs. All parameters required by the DO procedure are scanned by CFS, and prompted for in a special mask. Following termination of the job, the user is automatically informed, with the SYSOUT listing being displayed on screen.
Command memory
CFS provides the user with the facility to redisplay keystrokes previously entered. These may be retransmitted unchanged, or modified and then retransmitted. This facility is available for the FILENAME-SELECT field of the selection mask, the file list command field, as well as any line mode entry in a Connection (e.g. an ARCHIVE command). In CFS screens, the Command memory is activated by pressing the DUE2 key, while in Connections, it is activated by entering '-' and DUE1.
Logging
Logging is an additional CFS facility provided in Connections. When the logging mode is set, all input under this Connection will be saved in physical format (i.e. with message header and all field attributes) to an ISAM file. If required, all screen output can also be saved. See also "Restore", below.
Restore
Restore is an additional CFS facility provided in Connections. When the restore mode is set, the input source for this Connection is changed from the keyboard to a file created under the Logging mode (see above). This allows dialog sesions captured once to be repeated as often as required, and can also be achieved without user intervention. Different variants of the restore mode are:
a) automatic replay of a dialog session without user intervention (Batch Mode).
b) replay of the dialog session, whereby the user must acknowledge each step by pressing the DUE/ENTER key (Step Mode).
c) automatic replay of a dialog session, with the current output compared to the historic output. The user will be notified if differences occur (Compare Mode).
d) Simulation of the recorded dialog session on the screen. All input and output will be displayed on the screen only, with no communication between the terminal and the session partner taking place.
Selection
After loading the program, the user will be presented with an empty selection mask. The user can now choose which data objects are to be processed. The selection can be based on a number of criteria, e.g. files with particular characteristics (particular name strings, particular creation date, file type etc.), or perhaps some elements from a library, or Job variables.
If no selection of data objects is required, e.g. the user wants to work only in Connections, then "NO" can be entered in the first field of the selection mask.
Startup
A sequence of commands executed automatically each time CFS is started. The commands to be executed are stored in a file in the userid from which CFS is called. The Startup file name must be prefixed with CFS.STARTUP. ....
Variable Action
A Variable Action is a complex instruction that can be performed on a group of files/library elements/Job variables. The instructions indicated in the Variable Action may be enhanced by parameters. With Variable Actions it is therefore possible to process multiple files/library elements/ Job variables simultaneously, with just one command.