![]() |
CP Connection Prompt for BS2000 Commands
CP 'param' The system prompt for BS2000 commands in CFS Connections can be set to any string. These can even be variables, such as the date, time, userid or name of host system. Standard: '/'
param String for the BS2000 prompt in Connections. param may not exceed 60 characters. Lower case letters will not be converted to upper case. Variables can also be used in param as well as constants. At the time the prompt is displayed, the current value of the variable will be substituted. The name of a variable must be terminated with a special character, such as a blank or a comma. If a letter or numeral is to appear after the variable as a constant, the name of the variable should be terminated with a full stop. The full stop will not appear in the text. The following variables can be used:
&CON Connection number under which the user is currently working.
&USER-ID Userid under which the user is currently working in this Connection.
&LOGNAM Job name specified in the LOGON command for this Connection.
&HOST Name of the host system on which the dialog task is running.
&DATE Current date in the form dd.mm.yy
&TIME Current time in the form hh:mm
&(jvname) Contents of the specified Job variable
Notes:
The Connection Prompt will operate in all Connections to $DIALOG, so long as the SDF Option GUIDANCE= MIN | MED | MAX is not being used.
If the CP command is contained in a Startup file, and if variables are used, the following command sequence should be used to prevent conflicts with CFS procedure variables:
*SET PAR=#
CP ' ... '
*SET PAR=&
If the CP command is contained in a Startup file, then the hexadecimal mode of EDT can be used to enter Line Mode control characters to offset text strings in the CP command. For further information, see the "Executive Macro Calls" manual, VTCSET macro.
Example: CP 'x&CON:y &HOST $&USER-ID &TIME x->'
In the above example, x represents the Line Mode control character X'14' (EM4), and y represents the code X'1F' (EM2). Entering this CP command will display the following prompt:
1: VAR2 $TSOS 10:22 ->
When operating nested Connections (see page 9-), the Connection prompt of the latest copy of CFS to have been loaded will always be valid.
Examples:
CP 'Please enter next command >'
CP 'Conn. &CON &USER-ID &TIME /'
For example, if the user logs on to the userid TEST, the following prompt will be displayed:
Conn. 1 TEST 13:22 /