OSI-CON - define a logical connection to an OSI TP partner

The OSI-CON control statement allows you to assign a real partner application to an OSI-LPAP partner for communication based on the OSI TP protocol. It is used to define logical connections between the local UTM application and a partner application. For this purpose, you must specify:

• the name of the OSI TP access point in the local application, via which the connection is to be established. This is defined using the ACCESS-POINT statement.

• the address of the OSI TP access point of the partner application. This address consists of P-selector, S-selector, T-selector and N-selector and optionally the port nummer (parameter LISTENER-PORT).

  On Unix, Linux and Windows systems the following operands are used to describe the T-selector:

  • TRANSPORT-SELECTOR (=address of the partner application on the partner computer)

  • T-PROT (the transport protocol used)

  • TSEL-FORMAT (format identifier of the T-selector)

  • LISTENER-PORT (port number for RFC1006)

  See "Providing address information for the CMX transport system (Unix, Linux and Windows systems)" for more information.

The partner application sets up the connection to the local application via an OSI-LPAP partner, which is defined in the OSI-LPAP statement. Here you generate the number of connections, the names of the individual connections, and so on. The communication parameters of the OSI-LPAP partner are assigned to the OSI-CON statement using the operand OSI-LPAP=osi_lpap_name. The logical connection is thus generated in a single OSI-CON statement, even if there are several parallel connections to the partner application.

If a partner application can be accessed in various remote systems at different times, you must define several addresses and thus replacement connections for the OSI-LPAP partner assigned to this application. For generation purposes, this involves assigning several OSI-CON statements (OSI-CON statements with the same osi_lpap_name and LOCAL-ACCESS-POINT) to a single OSI-LPAP statement (see "OSI-LPAP - define an OSI-LPAP partner for distributed processing based on OSI TP"). However, only one OSI-CON statement can be active at any one time. You can switch to a replacement connection by means of administration.

When you use OSI-LPAP bundles, then the following also applies to the OSI-CONs of the slave LPAPs in a LPAP bundle:
All OSI-CONs of all slave LPAPs in a LPAP bundle must be assigned the same access point (see also section "MASTER-OSI-LPAP - Defining the master LPAP of an OSI-LPAP bundle").

OSI-CON

connection_name [ ,ACTIVE={ YES | NO } ]   ,LOCAL-ACCESS-POINT=access_point_name   ,NETWORK-SELECTOR=C'c'   ,OSI-LPAP=osi_lpap_name   ,PRESENTATION-SELECTOR={ *NONE |                            (C'c' [, STD | EBCDIC | ASCII ]) |                             X'xx' }    ,SESSION-SELECTOR={ *NONE |                        (C'c' [, STD | EBCDIC | ASCII ]) |                        X'xx' }    ,TRANSPORT-SELECTOR=C'c' [ ,LISTENER-PORT=number ]                              additional operands on Unix, Linux and Windows systems [ ,MAP={ USER | SYSTEM | SYS1 | SYS2 | SYS3 | SYS4 } ] [ ,T-PROT= RFC1006 ] [ ,TSEL-FORMAT={ T | E | A } ]

connection_name	Name of the logical connection between the local UTM application and the partner application for communication based on the OSI TP protocol. connection_name identifies the connection in the local application. It can be up to eight characters in length and must be unique in the local application.
ACTIVE=	Status (active or inactive) of the logical connection to the partner application. In the case of replacement connections to the partner application, several OSI-CON control statements are issued with the same  osi_lpap_name of an OSI-LPAP partner. However, only one OSI-CON statement can be generated with ACTIVE=YES. All others must be defined with ACTIVE=NO. You can then switch to the replacement connections by means of administration.
YES	The connection defined in this OSI-CON statement is active. Default: YES
NO	The connection defined in this OSI-CON statement is inactive.
LISTENER-PORT=	number Port number of the partner application. All port numbers between 1 and 65535 are allowed. Default: 0 (no port number) On BS2000 systems, the transport system uses the standard port 102 in this case. On Unix/Linux and Windows systems, a port number must be specified.
LOCAL-ACCESS-POINT=access_point_name
	Name of the local OSI TP access point used for communication with the partner application. This is defined using the ACCESS-POINT control statement. If replacement connections (several OSI-CON statements with the same  osi_lpap_name) have been defined for the OSI-LPAP partner to which the partner application is assigned, the same local access point must be specified for all replacement connections. If the application context of the OSI-LPAP partner uses the CCR syntax, the following address components must also be defined for the local access point: APPLICATION-ENTITY-QUALIFIER (see the description of the ACCESS-POINT statement in section "ACCESS-POINT - create an OSI TP access point") APPLICATION-PROCESS-TITLE (see the description of the UTMD statement in section "UTMD - application parameters for distributed processing")
MAP=	This operand is only valid on Unix, Linux and Windows systems. Controls the code conversion (EBCDIC <-> ASCII) for user messages exchanged between partner applications (OSI-LPAP) in the abstract syntax UDT. User messages are passed in the message area on the KDCS interface in the message handling calls (MPUT/FPUT/DPUT). For user messages with a different abstract syntax than UDT - i.e. if KCMF does not contain any blanks - UTM does not perform a conversion regardless of the value generated here.
USER	openUTM does not convert user messages, i.e. the data in the KDCS message area is transferred between the partner applications unchanged. Default: USER
SYSTEM | SYS1 | SYS2 | SYS3 | SYS4
	UTM converts the user messages based on the conversion tables provided for the code conversion (see section "Code conversion"), i.e.: Prior to sending, the code is converted from ASCII to EBCDIC. After receipt, the code is converted from EBCDIC to ASCII. The specifications SYSTEM and SYS1 are synonymous. The prerequisite is that the message has been created using the abstract syntax of UDT (KCMF = blanks). UTM assumes that the messages contain only printable characters.
NETWORK-SELECTOR=C’c’
	Name of the partner computer. The complete name (FQDN) by which the computer is known in the DNS must be specified. The name can be up to 64 characters long. N-SEL is a mandatory operand. No distinction is made between uppercase and lowercase notation; KDCDEF always converts the name of the partner computer into uppercase. Please note that the name pair (TRANSPORT-SELECTOR, NETWORK-SELECTOR) specified here must not be identical to the name pair (remote_appliname, PRONAM) defined in a CON statement ("CON - define a connection for distributed processing based on LU6.1") , or to the name pair (ptermname, PRONAM) defined in a PTERM statement ("PTERM - define the properties of a client/printer and assign an LTERM partner").
OSI-LPAP=	osi-lpap_name Name of the OSI-LPAP partner defined as the logical access point for the partner application in the local application. osi_lpap_name must be defined in a OSI-LPAP statement. osi_lpap_name can be up to eight characters in length.
PRESENTATION-SELECTOR=
	Presentation selector of the partner application. This is the address component of the OSI TP access point in the remote partner’s system. The specified value must match the presentation selector defined for this access point in the partner application.
*NONE	A symbolic presentation selector is not defined.
C’c’	The presentation selector is entered in the form of a character string (c). The value specified for c can be up to 16 characters in length. The presentation selector is case-sensitive. In the case of a character string, you can chose the code in which the characters are interpreted:
STD	The characters are interpreted as a machine-specific code (BS2000 = EBCDIC; Unix, Linux and Windows systems = ASCII). Default: STD
EBCDIC	The characters are interpreted as EBCDIC code.
ASCII	The characters are interpreted as ASCII code.
X’x’	The presentation selector is entered in the form of a hexadecimal number (x). The value specified for x can be up to 32 hexadecimal digits (corresponds to16 bytes) in length. You must enter an even number of hexadecimal digits.
SESSION-SELECTOR=
	Session selector of the partner application. This is the address component of the OSI TP access point in the remote partner’s system. The specified value must match the session selector defined for this access point in the partner application.
*NONE	A session selector is not defined.
C’c’	The session selector is entered in the form of a character string (c). The value specified for c can be up to 16 characters in length. The session selector is case-sensitive. In the case of a character string, you can chose the code in which the characters are interpreted:
STD	The characters are interpreted as a machine-specific code (BS2000 = EBCDIC; Unix, Linux and Windows systems = ASCII). Default: STD
EBCDIC	The characters are interpreted as EBCDIC code.
ASCII	The characters are interpreted as ASCII code.
X’x’	The session selector is entered in the form of a hexadecimal number (x). The value specified for x can be up to 32 hexadecimal digits (corresponds to 16 bytes) in length. You must enter an even number of hexadecimal digits.
TRANSPORT-SELECTOR=C’c’
	You can enter up to eight printable characters. Permitted characters include uppercase letters, numbers, and the special characters $, # and @. Hyphens are not permitted. The first character must be an uppercase letter. T-SEL= is a mandatory operand. In T-SEL= you must specify the following: BS2000 systems: The BCAM application name of the remote partner. Unix, Linux and Windows systems: T-selector of the partner application. You must specify the T-selector in T-SEL that is assigned to the partner application in the remote system for CHECK-RFC1006=YES. Please note that the name pair (TRANSPORT-SELECTOR, NETWORK-SELECTOR) specified here must not be identical to the name pair (remote_appliname, PRONAM) defined in a CON statement (in section "CON - define a connection for distributed processing based on LU6.1"), or to the name pair (ptermname, PRONAM) defined in a PTERM statement (in section "PTERM - define the properties of a client/printer and assign an LTERM partner").
T-PROT=	The address format with which the OSI TP partner signs on to the transport system. Information on the following address formats can be found in section "PCMX documentation" (openUTM documentation).
RFC1006	Address format RFC1006 ISO transport protocol based on TCP/IP and RFC1006 convergence protocol. Default: RFC1006
TSEL-FORMAT=	The format identifier of the T-selector The format identifier specifies the coding of the T-selector in the transport protocol. You will find more information in section "PCMX documentation" (openUTM documentation).
T	TRANSDATA format
E	EBCDIC format
A	ASCII format Default:     T   If the character set of the value of T-SEL corresponds to the TRANSDATA format     E   Otherwise It is recommended to explicitly specify a value for TSEL-FORMAT operation via TCP/IP with RFC1006.