![]() |
Escape symbol in Connections
If CFS is loaded from a connection, and then another connection is opened from here, (Connection Level 2), there is an overlap if the same escape symbol is used between Level 1 and Level 2. If CFS is loaded from a connection, the alternative escape symbol ` (X'4A') is automatically used. If the user is in a connection in Level 2, the escape symbol ^ will return him to the CFS level that was first loaded i.e. Level 0. Entering the symbol ` will return him to the level from which this CFS was loaded i.e. Level 1. It makes sense, therefore, to leave nested connections by using the alternative escape symbol.
With regard to nested connections, it should be noted that pressing the K2 key in Level 2, and then entering R (Return) will return you to that level of CFS which was originally loaded (Level 0), and not to the level immediately below you (Level 1). Later, a command CCn will not enable CFS in Level 1, rather in the Level 2 that you left with K2. Pressing the K2 key and entering B (Break) in a connection in Level 2 will result in CFS in Level 1 returning its connection request "Return / Continue in Conn. n / Break ...".
Transmitting a HC-, LOG-, RES command in a nested connection will always result in the basic CFS task (Level 0) processing the command. LOG and hardcopy files are also always created in the userid from which CFS was called for the first time.
The symbol to activate the command memory (see next section) can be redefined for each connection level seperately by means of the CRD (Connection Command Redefine) command. The CRD command to change the symbol for all connections within a level should be entered in the command line of the CFS task that is directly controlling the affected connections, i.e. those in the level immediately below.
The processing of all CFS connection-specific commands such as HC, LOG, RES can also be prevented for a specified Connection x at Level n. To achieve this, enter the CFS command NEC x (No Exit for Connection x) at Level n-1.