(a) In a multi-thread environment

PROCEDURE DIVISION

 
CALL 'CBLDCCLS' USING identifier-1
 

DATA DIVISION

 
01 identifier-1.
   02 data-name-A PIC X(8)  VALUE 'CONNECT '.
   02 data-name-B PIC X(5).
   02 FILLER     PIC X(3).
   02 data-name-C PIC S9(9) COMP VALUE ZERO.
   02 data-name-D PIC S9(9) COMP.
 

(b) In a single-thread environment

PROCEDURE DIVISION

 
CALL 'CBLDCCLT' USING identifier-1
 

DATA DIVISION

 
01 identifier-1.
   02 data-name-A PIC X(8)  VALUE 'CONNECT '.
   02 data-name-B PIC X(5).
   02 FILLER     PIC X(3).
   02 data-name-C PIC S9(9) COMP VALUE ZERO.
 

Establishes permanent connection with a CUP execution process, a RAP-processing server or the DCCM3 logical terminal.

The CUP execution process for establishing the permanent connection is running on the OpenTP1 node specified in the data-name-D in the CBLDCCLS('CLTIN '), or specified in DCCLTRAPHOST or DCHOST in the client environment definition.

To establish the permanent connection with the DCCM3 logical terminal, define DCCLTDCCMHOST and DCCLTDCCMPORT in the client environment definition. Also specify 32 for data-name-C in CBLDCCLS('CONNECT ').

To establish permanent connection with the DCCM3 logical terminal using the remote API facility, provide DCCLTRAPHOST with the host name and the port number for the DCCM3 logical terminal. Also specify 0 for data-name-C in CBLDCCLS('CONNECT ').

• data-name-A
  Set VALUE 'CONNECT' as the request code for indicating establishment of permanent connection.
  
• data-name-C
  Specify the node with which you want to establish permanent connection.
  

  0: Permanent connection is established with TP1/Server, a RAP-processing server or the DCCM3 logical terminal.

  32: Permanent connection is established with the DCCM3 logical terminal.

• data-name-D
  Specify the client ID received with CBLDCCLS('CLTIN ') or CBLDCCLS('EXCLTIN ').
  

• data-name-B
  5-digit status code.
  

Status code	Meaning
00000	Normal termination. Or, permanent connection has already been established.
02501	Invalid value for the data name. The request code (data-name-A) may be invalid.
02502	CBLDCCLS('CONNECT ') is issued in the transaction, or CBLDCRPS ('OPEN ') is not issued. The establishment request to OpenTP1 is issued while permanent connection with DCCM3 has already been established. Alternatively, the establishment request to DCCM3 is issued while permanent connection with OpenTP1 has already been established.
02504	A necessary amount of buffer could not be allocated.
02506	Communication error
02507	A timeout error occurred during establishment of permanent connection.
02515	One of the following causes is likely: The OpenTP1 server or the DCCM3 logical terminal has not started. The client extended service has not started. Check whether clt_conf is specified correctly in the system service configuration definition. The CUP executing process has not started. Check whether clt_cup_conf is specified correctly in the client service definition.
02518	System error
02539	The establishment request to the DCCM3 logical terminal is issued with an invalid host name.
02544	The client ID specified in data-name-D differs from the one received with CBLDCCLS('CLTIN ') or CBLDCCLS('EXCLTIN ').
02547	The specified port number is in use, or port numbers that can be assigned automatically by the operating system are insufficient.

• No permanent connection is established when CBLDCCLS('CONNECT ') returns error. Permanent connection may be established only on the CUP execution process if the error is returned with the status code 02506, 02507, or 02518.
  In this case, the CUP execution process or DCCM3 logical terminal may keep on waiting for a response from the CUP. To prevent an infinite wait, specify an appropriate value for the maximum time interval for the permanent connection. For a DCCM3 logical terminal, specify an appropriate value for the time during which the system is unable to determine whether a connection with the terminal is valid.
  
• CBLDCCLS('CONNECT ') cannot be issued in a transaction.
• You can establish permanent connection with only one of the following two categories.
• CUP execution process, RAP-processing server, or a DCCM3 logical terminal that is specified for DCCLTRAPHOST in the client environment definition
• DCCM3 logical terminal that is specified for DCCLTDCCMHOST in the client environment definition
  If you establish permanent connection with one category, you cannot communicate with the other until you issue CBLDCCLS('DISCNCT ').
  
• The data compression is unavailable when you establish permanent connection with DCCM3 logical terminals. You need to omit DCCLTDATACOMP or specify N for it in the client environment definition.