SESCHA - define session characteristics for distributed processing based on LU6.1

The SESCHA control statement allows you to define session characteristics between the local application and the partner application. The set of session characteristics defined here is stored under a name, which can then be assigned to an LPAP partner using the SESCHA= operand of the LPAP statement (see "LPAP - define an LPAP partner for distributed processing based on LU6.1").

When generating LU6.1 connections, you must bear in mind the information in section "Distributed processing via the LU6.1 protocol".

SESCHA

sescha_name [ ,CONNECT={ YES | NO} ] [ ,CONTWIN={ YES | NO } ] [ ,DPN=destination_process_name ] [ ,IDLETIME=pacing_count_time ] [ ,PACCNT=pacing_count_number ]   ,PLU={ YES | NO }    additional operand on Unix, Linux and Windows systems [ ,MAP={ USER | SYSTEM | SYS1 | SYS2 | SYS3 | SYS4 } ]

sescha_name	Name under which the session characteristics are combined. This is specified for the SESCHA= operand of the LPAP statement in order to assign these session characteristics to a particular LPAP partner.
CONNECT=	This defines whether the local application is to establish the connection to the partner application during startup.
NO	The connection to the partner application must be established using an administration command. Default: NO
YES	The connection to the partner application is established when the local application is started. If unsuccessful, openUTM repeats its attempt to establish the connection at intervals defined in MAX ...,CONRTIME=. CONNECT=YES can be specified both in the local application and in the partner application. This means that the connection is established automatically as soon as both applications are available.
CONTWIN=	(contention winner) This defines whether the local application is the contention winner or the contention loser. The contention winner application is responsible for managing the session and controlling the reservation of sessions by jobs. You must specify CONTWIN=Y in one of the two participating applications and CONTWIN=N in the other.
YES	The partner application is the contention winner.
NO	The local application is the contention winner. In both cases, jobs can be started by either application. If both applications simultaneously attempt to initiate a job, the session is reserved by the job issued by the contention winner. The correct selection of this parameter is important for performance in communication between two applications: CONTWIN=Y must be specified in one of the applications, and CONTWIN=N in the other. Default: If PLU=N, the local application is the contention loser; otherwise, it acts as the contention winner.
DPN=	destination_process_name Entity that processes asynchronous messages. This operand is significant only for links to IBM systems. Default: 8 blanks
IDLETIME=	idle_time Number of seconds for which the idle state of a session is monitored. If the session is not reserved by a job within the period specified in IDLETIME=, openUTM shuts down the connection. IDLETIME = 0 means that the idle state of the connection is not monitored. Default value: 0 Minimum value: 60 Maximum value: 32767 If you specify a value that is greater than zero and smaller than the minimum value, KDCDEF replaces the value with the minimum value.
MAP=	This operand is only supported 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). openUTM does not generally execute any message handling for formatted messages (KCMF contains a format identifier).
USER	openUTM does not convert the user messages, i.e. the data in the KDCS message area is transferred to the partner application 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 parameter values 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.
PACCNT=	pacing_count_number Maximum number of message segments of a long message which can be received by the local application without issuing a response. If this value is too high, this may result in network congestion or loss of messages. If PACCNT=0, pacing does not take place. Default: 3 Minimum value: 0 Maximum value: 63 CAUTION! If only short messages are to be exchanged with the partner application (less than 4000 byte) then pacing should be deactivated (PACCNT=0); this saves on overhead in communication with the partner. If data flow problems still occur, then either the default must be reset or the generation of the transport system must be modified accordingly.
PLU=	Application that opens the session, i.e. the primary logical unit (PLU).
YES	The partner application is the primary logical unit.
NO	The local application is the primary logical unit. PLU=Y must be specified for one of the applications, and PLU=N for the other.