OC Open Connection

[OC] n [appl] [, trm] [, host] [, opt] [ /cmd]    or equally:

n [appl] [, trm] [, host] [, opt] [ /cmd]

The entry OC is optional and can be ommitted.

appl Application name.

e.g. $DIALOG, $CONSOLE or the name of a UTM/DCAM application.

Standard: $DIALOG (BS2000-Dialog task).

Notes:

UTM application:

Additional PTERM and LTERM statements need to be added to the KDCDEF during UTM generation to enable connection via CFS.

PTERM/LTERM statement format in UTM:

PTERM trm, PTYPE=pt, PROTOCOL=N, PRONAM=host, LTERM=trm

LTERM trm

trm freely selectable virtual terminal name that the user will enter in the OC command to access the UTM application (see below). Example: CFS1

host BCAM name of the host computer from which CFS will be called. The name of the host computer is displayed in the CFS mask header as HOST= ... .

The host name may not be replaced by the front-end processor (see status command).

pt Terminal type. For example, T9750 .

Unsolicited output from UTM should be acknowledged with the DUE2 transmission key. The DUE2 key may not be used for processing purposes by the UTM application. If this is nevertheless required, the transmission key for unsolicited output must be redefined by the CFS command M L'1307',X'nn'. X'nn' is the ASCII code for the remapped transmission key. M L'1307',X'3A' for example, remaps the DUE2 key to the K14. Further information about the transmission key codes can be found in the manual "TRANSDATA, Data Terminal 9750, Programmers Interface".

If the user wishes to open the connection to a UTM application with the option ES (OCn appl,trm,[host],ES), i.e. the connection should be handled like a physical screen, the PTERM/LTERM statements should be defined as follows:

PTERM trm,PTYPE=pt,PROTOCOL=STATION,PRONAM=host,LTERM=trm

LTERM trm

It is important that the PTYPE entry pt should correspond to the terminal type defined in the PDN generation for the terminal from which CFS will be executed. Further information on the ES option can be found in the description of the opt parameters (Additional information when establishing a connection).

Unsolicited output in ES mode should not be acknowledged with DUE2.

Terminal Pools: UTM allows multiple PTERMs to be defined on the same processor by means of the TPOOL statement. During the connection setup UTM allocates the next free PTERM/LTERM name to the current connection, so long as the generated maximum number of connections has not been exceeded. The standard CFS name can be used for the terminal name in the OC command when opening a connection (OCn appl,,[host] [,ES] ). Example of a TPOOL statement:

TPOOL LTERM=trm,PROTOCOL=N|STATION,PTYPE=pt,PRONAM=host, NUMBER=num

trm Constant prefix for the LTERM names, e.g. LTERM=CFS. The real LTERM names are assembled by attaching an increment to the prefix. No explicit LTERM statements are required when using TPOOL statements.

num maximum number of connections that can be processed by this Terminal Pool.

The transaction codes LOG../NLOG../HC../NHC../RES../O [ON|OFF] are processed internally by CFS, and are not passed to the application. Refer to the commands NECn (No Exit for Connection) Page 9-, and CRD (Connection Command Redefine) Page 9- for further information about this.

DCAM Applications:

The generation of the virtual CFS terminal is to be taken from the internal conventions of the DCAM application, assuming it is actually required.

When opening a connection to an application that is expecting the CCB property EDIT=SYSTEM, the option ES must be given at the OC command.

When opening a connection to an application that is expecting the RBP property OPTCD=(CS,SPEC), the option S must be given at the OC command.

For DCAM applications that expect a connection message, the option C must be given at the OC command.

A complete description of the OC command options is given below.

SAP Applications:

The SAP option must be given for SAP applications. In the case of UTM-SAP applications the SAP option should not be used.

$CONSOLE application:

When opening a connection to $CONSOLE, the name of an authorised user process (user-id without $ and full stop) and a password (if required) will be requested via a connection message: "Please enter connection message". The input should be in the form: user-id, C'passw'. To define an authorised user process, the UCC statement must be assigned in the BS2000 system generation. For further information, refer to the manual "BS2000 System Generation". An example of how procedure-controlled commands can be directed to the console can be found on page 19-.

trm Name of a virtual terminal under which the connection will be opened.

With UTM, and most DCAM applications, the virtual terminal name trm must be known to the application (Generation).

Standard: CFSntttt (n: Connection number, tttt: TSN of the task from which CFS was loaded).

The System Administrator can change the method by which standard terminal names are created. The alternative algorithm results in the physical terminal name being used with minor modifications for the terminal name for the connections.

This feature, important for LOGON-Systemexits, is activated via the USERMOD of CFS. See Appendix A2 "Interfaces for the System Adminstrator".

host Name of the host computer on which the application is running.

The user will be prompted for the host name if '?' is entered instead of the host name. An application example of this could be for a menu system for Connections providing similar Connections to different hosts.

Standard: own host.

opt Optional parameters for setting up the connection.

R Return switch. After successfully opening a connection, a branch is immediately made back to the basic level of CFS. This option is particularly important when opening a connection to $CONSOLE under control of a procedure.

C Connection message. Prior to the YOPNCON, a Connection message is requested from the user. The blanked entry can be given in the form xxx (unformatted input) or X'...' (hexadecimal format).

If this C option is not specified, CFS generates a Standard Connection Message. In cases where the connection message should actively be suppressed at the YOPNCON call (e.g. DCAM application ROUTE), the NC parameter should be used (see below).

When opening a connection to $CONSOLE, the name of an authorised user process (user-id and LOGON password) will be requested via a connection message: "Please enter connection message". The input should be in the form: xxx,C'...'. To define an authorised user process, the UCC statement must be assigned at BS2000 system generation time. For further information, refer to the manual "BS2000 System Generation".

NC On establishing a connection with YOPNCON, no connection message is generated.

UC Console-type connection. Asynchronous output is in line mode, input only possible by pressing the K2 key.

UCH like UC, but with Input Subsystem Header.

HC Only for console-type connections. Asynchronous output in Line mode is logged to a locally-connected hardcopy printer.

U UTM-type connection (rigid dialog in Format/Physical Mode).

S CFS makes the connection to the application with the attributes OPTCD=(CS,SPEC). Some DCAM applications, e.g. SAP only accept partners with OPTCD=(CS,SPEC). Standard: OPTCD=(CA,ANY).

A3 A3NOP-compatible mode. The user can perform data input from the first screen to be displayed (WRTRD call). The output following this initial screen is treated as asynchronous data (WROUT call). A Connection opened in A3 mode can only be closed from the main CFS screen by means of a DC command. The A3 mode is aimed at providing Connections to the A3NOP and VIDEO DCAM applications.

ES | ES1 | ES2 | ESO

EDIT=DSSIM: This option ensures that the connection is seen by the operating system as a real physical screen. It enables, for example, a connection to be established to the application VIDEO, as well as other "difficult" applications. See also page 9- "Troubleshooting failed connection setup". In ES mode, asynchronous output must not be acknowled with DUE2.

ES1 | ES2 ES1 and ES2 are particular variations of the ES mode for DCAM applications such as RDDIA/FTDIA. ES1 and ES2 differ only slightly in the handling of transmitted K2 messages.

ESO Edit System with Original Terminal name: This option can only be used for a Connection. It will cause the original physical terminal name from which CFS was started to be used instead of the virtual terminal name.

DCAM8 The Connection is opened in ACB (DCAM Application Control Block) mode, with DCAMVER=8.0. Standard: DCAM 7.0. This parameter is necessary if the primary process uses DCAMVER=8.0.

NES The configuration module of CFS can be used to open all Connections to $DIALOG automatically in ES mode.

In this case, the option NES will enable a non-ES mode Connection to be opened.

LC Lower Case. Only relevant for Connections to $VMCONS: Lower case letters will be passed to the application. Normally, console-oriented Connections will result in any lower case letters being converted to upper case.

Note: This option can only be used in VMCONS Connections for the administration of a Linux VM.

SAP [ [TTYPE=...] [/NP] ]

The specified application is a SAP application. The standard SAP connection message 'TTYPE=T9750___/NC' is prepared. The system administrator can amend the standard terminal type T9750 specified in the CFSMAIN module. SAP implies the U and S options, additionally with a standard Connection message being generated. The SAP option may not be specified if the SAP application is running under UTM. The following can be specified after the SAP option:

TTYPE= Terminal type that SAP should emulate, e.g. SAPTTYPE=T9756. By default, the T9750 will be emulated.

/NP Appending /NP will result in SAP not loading any P-keys, or only the keys P1 to P4. When using /NP, note that the terminal type Txxxx specification is 8 bytes long, and hence three blanks must be enetered before /NP.

Example: SAPTTYPE=T9756___/NP.

Multiple options can be given, each seperated by a comma.

Standard: None of the optional parameters are used.

/cmd A $DIALOG BS2000 task will be started, and the given BS2000 command will be executed. There are two different cases to consider:

a) /cmd = /LOGON user-id,acct,C'...' 

The dialog task is started under the specified user id.

b) /cmd = any BS2000 command with the exception of LOGON.

A dialog task is started under the same user id (i.e. the user id from which CFS was started). The specified BS2000 command is then executed under this opened connection. If the user id contains a LOGON password, it will be requested by BS2000 while establishing the connection.

Examples:

OC1

Open Connection 1. Open a BS2000 dialog task on own host computer. On executing the OC1 command, the normal BS2000 logon message "....PLEASE LOGON ..." will appear. The user can log on to any user id as normal.

OC1,,host/LOGON user-id,acct,C'passw'

Establish a dialog task on specified host computer as Connection 1. The LOGON command in this example is specified in the OC command.

OC9/EXEC $EDT

Open dialog task (Connection 9) on own host and under own user id. Following successful LOGON, and after acknowledging the bulletin, the BS2000 command /EXEC $EDT is automatically executed.

OC2 TESTUTM,CFS1

Open Connection 2 to the application TESTUTM. The virtual terminal name for this connection is CFS1. There must be PTERM and LTERM statements for the name CFS1 in the KDCROOT. After establishing the connection, the UTM request to enter a KDCSIGN command will appear.

OC3 SAP,,VAR3,SAP

A connection will be made as number 3 to the DCAM SAP application SAP. The application runs on the host VAR3, and is not under UTM control. The optional parameter SAP flags CFS that this connection is to an SAP application.

OC4 UDSDB,,,UC

A connection is established under number 4 to the DCAM application for UDS administration. The administration password, if required, should be given in plain text when CFS prompts with the connection message. For example, a password in the format C'ABC' should be entered simply as ABC. When a successful connection has been established, commands can be passed to the administration program by pressing the K2 key.