ACCESS-POINT - create an OSI TP access point

The ACCESS-POINT control statement is required only for communication based on the OSI TP protocol. It defines a local access point to the services of OSI TP.

If you issue more than one ACCESS-POINT statement per application, then KDCDEF outputs warning K492.

If more than one ACCESS-POINT statement is generated for an application then the applcation program have to make sure that all partner applications involved in a single transaction are connected to the UTM appilcation via the same service access point. OSI TP does not support tansactions spreading over more than one service access point.

Using the information specified in the ACCESS-POINT statement, a partner application can address the local application.

You specify the following parameters for a service access point in the ACCESS-POINT statement:

• Address of the access point within the local system
  The address of the access points consists of the presentation selector, session selector and transport selector components.

  The address specifications must be coordinated with the communication partners. The TRANSPORT-SELECTOR specification is mandatory in all cases.

  Unix, Linux and Windows systems:
  On Unix, Linux and Windows systems the address of the access point also comes from the LISTENER-PORT, T-PROT, and TSEL-FORMAT components.
  See "Providing address information for the CMX transport system (Unix, Linux and Windows systems)" for more information.

  Only a maximum of 1000 connections can be established per access point at a time. If you require more concurrent connections in your application, you must define more than one access point. But in this case note the above info box.

• Application Entity Qualifier
  You can define an application entity qualifier (AEQ) as additional address information. The application entity qualifier (AEQ) is combined with the application process title (APT) defined in the UTMD statement to form the application entity title (AET). The AET is a globally unique name for an application entity within the OSI TP environment. During transaction-oriented processing, the partner application requires the AET of the local UTM application in order to establish a connection. Similarly, the local application requires the AET of the partner application. It must be specified in the OSI-LPAP control statement that defines the partner application.
  The transport selector for the access point is still a mandatory entry.

• Listener ID (Unix, Linux and Windows systems)
  On Unix, Linux and Windows systems the access point is assigned a listener ID.

Each ACCESS-POINT is signed on to the transport system when the application is started (provided this is possible), and is not signed off until the application is terminated.

ACCESS-POINT

access_point_name [ ,APPLICATION-ENTITY-QUALIFIER=aequalifier ]   ,PRESENTATION-SELECTOR={ *NONE |                          (C'c' [,STD | EBCDIC | ASCII ]) |                           X'x' }   ,SESSION-SELECTOR={ *NONE |                       (C'c' [, STD | EBCDIC | ASCII ]) |                       X'x' }   ,TRANSPORT-SELECTOR=C'c' further operands for Unix, Linux and Windows systems [ ,LISTENER-ID=number ] [ ,LISTENER-PORT=number ] [ ,T-PROT=( RFC1006 ) ] [ ,TSEL-FORMAT={ T | E | A } ]

access_point_name
	Name of the OSI TP access point, which is then used to identify the access point in the local UTM application. access_point_name can be up to eight characters in length. access_point_name must be unique within the local UTM application.
APPLICATION-ENTITY-QUALIFIER=aequalifier
	Address component of the application entity title (AET). The AET is required if you are working with transaction management (commit functional unit), or if a heterogeneous partner requires an AET in order to establish a connection. An application entity qualifier (AEQ) can be specified only if an application process title (APT) is also defined for the application in the UTMD statement. However, an APT need not necessarily be assigned an AEQ. If AEQ is not defined , the access point has no application entity title (AET), i.e. it cannot be used for transaction management (commit functional unit). If the application context of an OSI-LPAP partner that operates via this access point (OSI-CON statement) contains the CCR syntax, you must enter an application entity qualifier here. For aequalifier, specify a positive integer. aequalifier must be unique within the application, i.e. aequalifier=integer1 must not be specified as the AEQ in any other ACCESS-POINT statement. Minimum value: 1 Maximum value: 67 108 863 (226-1)
LISTENER-ID=	number This operand is supported only on Unix, Linux and Windows systems. This assigns a listener ID to the access point as administrative information. Listener IDs can be specified for access points and application names. See also the BCAMAPPL statement in section "BCAMAPPL - define additional application names". You can use the listener IDs to distribute the network connections of the access points to different network processes. All connections of an access point are managed by the same network process. If you do not explicitly specify a listener ID, openUTM assigns the value 0 and combines all connections without a listener ID into a single network process. Default value: 0 Minimum value: 0 Maximum value: 65535 BCAMAPPL names that were created for communication via the socket interface (native TCP/IP) use separate network processes. Their listener IDs comprise a separate number space. i.e. they are administered in a different network process even if they have the same listener ID as this access point.
LISTENER-PORT=	number   This operand is supported only on Unix, Linux and Windows systems. Port number of the access point. All port numbers between 1 and 65535 are allowed. Default: 0 (i.e. no port number) If OPTION CHECK-RFC1006=YES, then a port number must be entered for LISTENER-PORT.
PRESENTATION-SELECTOR=
	Presentation selector for the address of the OSI TP access point.
*NONE	The address of the OSI TP access point does not contain a presentation selector.
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 to 16 bytes) in length. You must enter an even number of hexadecimal digits.
SESSION-SELECTOR=
	Session selector for the address of the OSI TP access point.
*NONE	The address of the OSI TP access point does not contain a session selector.
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’
	Transport component for the address of the OSI TP access point. The specification of T-SEL=C’c’ is mandatory. 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 of the name must be an uppercase letter. The name defined in T-SEL must be unique in the local UTM application. It must not be the same name as the primary application name specified in MAX APPLINAME, a BCAMAPPL name or the name specified with a Tselector in an ACCESS-POINT control statement. BS2000 systems: T-SEL= specifies the local BCAM application name.The transport selector must be unique in the local system for each host. Unix, Linux and Windows systems: You must match T-SEL to the transport selector of the OSI TP partner. If, for example, the partner is a UTM application, the specification in T-SEL must match the transport selector of the OSI-CON statement on the partner.
T-PROT=	Address formats of the T-selectors of the access point This operand is supported only on Unix, Linux and Windows systems. Further Information, see "PCMX documentation" (openUTM documentation).
RFC1006	Address format RFC1006, ISO transport protocol based on TCP/IP and RFC1006 convergence protocol. Default: RFC1006
TSEL-FORMAT=	Format indicator of the T-selectors of the access point (operand TRANSPORT-SELECTOR) This operand is supported only on Unix, Linux and Windows systems. The format indicator specifies the encoding of the T-selectors in the transport protocol. You will find more information in the "PCMX documentation" (openUTM documentation).
T	TRANSDATA format (encoded in EBCDIC)
E	EBCDIC character format
A	ASCII character format Default:     T   if the character set of the T-selector corresponds to the TRANSDATA format     E   in all other cases It is recommended to specify a value explicitly for TSEL-FORMAT.