CBLDCMCF('TDCTCN ') - Release connection

Format

PROCEDURE DIVISION specification

CALL 'CBLDCMCF' USING unique-name-1 unique-name-2

DATA DIVISION specification

01 unique-name-1.
02 data-name-A PIC X(8) VALUE 'TDCTCN '.
02 data-name-B PIC X(5).
02 FILLER PIC X(3).
02 data-name-C PIC X(4).
02 data-name-D1 PIC X(1).
02 data-name-D2 PIC X(1).
02 data-name-D3 PIC X(26) VALUE SPACE.
02 data-name-E PIC 9(9) COMP.
02 data-name-F1 PIC X(8).
02 data-name-F2 PIC X(56) VALUE SPACE.
02 data-name-G PIC X(8) VALUE SPACE.
02 data-name-H PIC X(8) VALUE SPACE.
02 data-name-I PIC X(144) VALUE SPACE.
02 data-name-J PIC X(184) VALUE SPACE.
02 data-name-K1 PIC 9(9) COMP.
02 data-name-K2 PIC X(n).
01 unique-name-2.
02 data-name-L PIC 9(9) COMP VALUE ZERO.

Description

CBLDCMCF('TDCTCN ') releases connection.

Normal termination of CBLDCMCF('TDCTCN ') indicates that the connection release request was accepted successfully by the protocol product. However, this does not necessarily mean that connection with the remote system has been released.

If you intend to perform any connection-related operation after calling CBLDCMCF('TDCTCN '), first use CBLDCMCF('TLSCN ') to check the status of the connection.

Data areas whose values are set in the UAP

data-name-A

Specify VALUE 'TDCTCN[Figure]' for the request code indicating connection release.

data-name-C

Specify how to specify the connection that is to be released.

'LE[Figure]'
Specifies that a logical terminal name is specified for the connection that is to be released. This argument is not supported by TP1/NET/NCSB or TP1/NET/X25-Extended.
'CN[Figure]'
Specifies that a connection ID is specified for the connection that is to be released.
Space
'LE[Figure]' (specification of a logical terminal name) is assumed.

data-name-D1

Specify whether the connection is to be released forcibly.

'1'
Release connection forcibly.
'0'
Release connection normally.
Space
'0' (normal release) is assumed.

data-name-D2

Specifies whether functionality that depends on the communication protocol is being used.

'1'
Specifies that functionality that depends on the communication protocol is being used.
'0'
Specifies that functionality that depends on the communication protocol is not being used.
Space
'0' (functionality that depends on the communication protocol is not being used) is assumed.

data-name-D3

Specify a space.

data-name-E

Specify the MCF communication process identifier of the MCF communication service for the connection that is to be processed. The permitted value range is from 0 to 239.

This argument is ignored when a logical terminal name is used to request connection release.

If you specify 0, the system searches for the MCF communication service to which the specified connection ID belongs. In a configuration where many MCF communication services are running or when you issue this function many times from a UAP, we recommend that you specify the MCF communication process identifier.

data-name-F1

Specify the logical terminal name or connection ID of the connection that is to be released. Express the logical terminal name or connection ID as a maximum of 8 bytes. If the specified name is shorter than 8 bytes, pad the name with trailing spaces.

data-name-F2, data-name-G, data-name-H, data-name-I, data-name-J

Specify a space.

data-name-K1

Specify the length of a protocol-specific area. You can specify a maximum of 1024 bytes.

If you do not use functionality that depends on the communication protocol, specify 0.

data-name-K2

Specify contents for the protocol-specific area.

The permitted value depends on the communication protocol being used. For details, see the applicable OpenTP1 Protocol manual.

data-name-L

Specify 0.

Data area to which a value is returned from OpenTP1

data-name-B

A status code of 5 digits is returned.

Status codes

Status codeExplanation
00000Normal termination.
71001CBLDCMCF('TDCTCN ') cannot be accepted because MCF is under start processing.
71002CBLDCMCF('TDCTCN ') cannot be accepted because MCF is under termination processing.
71004A memory shortage occurred during CBLDCMCF('TDCTCN ') processing.
71005A communication error occurred. For the cause, see the message log file.
71006An internal error occurred. For the cause, see the message log file.
71007The specified connection name has not been registered.
71008The specified logical terminal name has not been registered.
71009CBLDCMCF('TDCTCN ') is not supported by the applicable communication process.
71010Although the request to release the connection was issued to the MCF communication process, the request was not accepted. For the cause, see the message log file.
71011CBLDCMCF('TDCTCN ') cannot be accepted because the connection has been deleted.
71014The specified logical terminal name belongs to TP1/NET/NCSB or TP1/NET/X25-Extended; or, the specified connection group name belongs to TP1/NET/OSI-TP or TP1/NET/TCP/IP.
72028The value specified for data-name-A is invalid.
72052<If '0' or a space is specified for data-name-D2>
A nonzero value is specified for data-name-K1.
<If '1' is specified for data-name-D2>
A value smaller than 0 or greater than 1024 is specified for data-name-K1.
72053A nonzero value is specified for data-name-L.
72058The value specified for data-name-C is not 'LE[Figure]', [Figure]'CN[Figure]', or a space.
72059The value specified for data-name-D2 is not 1, 0, or a space.
The value specified for data-name-D3 is not a space.
72061A value smaller than 0 or greater than 239 is specified for data-name-E.
72063data-name-F1 begins with a space.
72065The value specified for data-name-F2 is not a space.
72066The value specified for data-name-G is not a space.
72068The value specified for data-name-H is not a space.
72070The value specified for data-name-I is not a space.
72072The value specified for data-name-J is not a space.
72074The character string specified for data-name-F1 contains an invalid character.
72075The value specified for data-name-D1 is not 1, 0, or a space.