obj_type=KC_LTERM

To create a new LTERM partner you must place the data structure kc_lterm_str in the data area. You cannot create LTERMs for bundles and groups.

The following table shows how the fields in the data structure are to be supplied with data.

	Field name 1	Meaning
m	lt_name[8]	Name of the LTERM partner. The name may be up to 8 characters long. The name may be entered in upper or lowercase letters. The name must be unique within its name class. See section "Format and uniqueness of object names" for information on the format and uniqueness of the name. Names of LTERM partners and transaction codes that have been deleted may not be used.
o	kset[8]	Only relevant for dialog partners (usage_type='D'): Key set of the application to which the LTERM partner is to be assigned. The key set must have been created dynamically first or defined at generation. A client or client program can only start a service secured with a lock code or access list if the corresponding key or access code for the lock code or access list is contained both in the key set of the user ID under which the client or client program signs on and in the key set of the associated LTERM partner.
		Note If you do not want to define any access protection for LTERM partners in an application generated with user IDs (USER), then assign key sets to the LTERM partners containing all of the key codes of the application (MASTER).
o	locale_lang_id[2] locale_terr_id[2] locale_ccsname[8]	Only on BS2000 systems: Specifies the language environment (locale) of the LTERM partner.
		In locale_lang_id you specify the language code of the language to be used when sending UTM messages to the LTERM partner. It is a maximum of 2 bytes long.
		In locale_terr_id you specify the territory code. This parameter specifies territorial particularities of the main language. It is a maximum of 2 bytes long.
		In locale_ccsname you specify the CCS name of the expanded coded character set. The CCS name can be up to 8 bytes long .It must belong to one of the EBCDIC character sets defined on the BS2000 system, see XHCS User Giude.
o	lock_code[4]	Only relevant for dialog partners (usage_type='D'): Lock code to be assigned to the LTERM partner (access security). The lock code must lie within the range defined in the KEYVALUE operand of the MAX KDCDEF command.
o	state	Specifies whether the LTERM partner is to be disabled or not after generation.
		'Y'	The LTERM partner is not to be disabled. (ON)
		'N'	The LTERM partner is to be disabled. (OFF)
o	usage_type	Specifies whether the LTERM partner is to be configured for connecting dialog partners or for connecting printers:
		'D'	LTERM partner for connecting dialog partners.
		'O'	LTERM partner for connecting output media such as printers.
o	user_gen[8]	Only relevant for dialog partners (usage_type='D'): For LTERM partners of terminals: User ID for which UTM will execute an automatic KDCSIGN when establishing the logical connection. This user ID must have been entered in the configuration dynamically or statically before the LTERM partner. For LTERM partners of UPIC clients and TS applications: The connection user ID must be created in the same transaction in which the LTERM partner was created. See chapter "Changing the configuration dynamically" for more information.
		Default for LTERM partners of terminals: No automatic KDCSIGN Default for LTERM partners of UPIC clients (ptype='UPIC-R') or TS applications (ptype='APPLI' or 'SOCKET'): Connection user ID with the name of the LTERM partner. If this user ID is not created explicitly in the same transaction as the LTERM partner, then UTM creates this user ID implicitly. This user ID must not already exist, however.
		Note: The use of the automatic KDCSIGN on terminals restricts access protection.
o	cterm[8]	Only on BS2000, Unix and Linux systems: Only relevant for LTERM partners used to connect printers (usage_type='O'). Name of the printer control LTERM that is to administer the printer. The printer control LTERM must have been dynamically or statically added to the configuration before the LTERM partner (see chapter "Changing the configuration dynamically").
		Every printer assigned to this LTERM partner (KC_PTERM) must be assigned a printer ID (cid) that is unique to this printer control LTERM.
o	format_attr format_name[7]	Only on BS2000 systems: Only relevant if a terminal is to be assigned to the LTERM partner. With the help of these fields you can assign an LTERM-specific start format to the LTERM partner. One requirement for assigning a start format is that a formatting system has been generated (KDCDEF command FORMSYS). If the start format is a #Format, then a sign-on service must also have been generated.
		You must always specify a format_name and a format_attr when defining a start format.
		In format_attr you specify the format code of the start format:
		'A' for the format attribute ATTR (+Format). 'N' for the format attribute NOATTR (*Format). 'E' for the format attribute EXTEND (#Format).
		See section "format_attr, format_name (only on BS2000 systems)" in chapter "kc_lterm_str - LTERM partners" for descriptions of the format attributes.
		In format_name you specify the name of the start format. The name can be up to 7 characters long and may only contain alphanumeric characters.
o	plev[5]	Only on BS2000, Unix and Linux systems: Only relevant for LTERM partners of output media (usage_type ='O'). In plev you specify the control value for the message queue of the LTERM partner. As soon as the number of output jobs in the queue equals the value specified in plev, UTM attempts automatically to establish a connection to the printer. If a printer pool is assigned to the LTERM partner, then UTM establishes connections to all printers. UTM automatically shuts the connection down as soon as the message queue is empty.
		You may only specify plev in conjunction with qamsg='Y'. plev='0' means that no control value is defined.
		Minimum value: '0'     Maximum value: '32767'
o	qamsg	Specifies whether asynchronous jobs (FPUT and DPUT jobs) sent to the client/printer assigned to this LTERM partner are to be temporarily stored in the message queue of the LTERM partner, even if the client/printer is not connected to the application.
		'Y'	An asynchronous job is added to the message queue. qamsg='Y' is not possible for restart='N'.
		'N'	An asynchronous job is rejected if the corresponding client/printer is not connected to the application.
o	qlev[5]	Specifies the maximum number of asynchronous messages that may be temporarily stored in the message queue of the LTERM partner at any one time. If the control value in qlev is exceeded, then UTM rejects any further asynchronous jobs sent to this LTERM partner or to the client/printer assigned to it. Minimum value:'0'   Maximum value:'32767'
o	restart	Is only relevant for dialog partners (LTERM partners with usage_type='D'). In restart you specify how UTM will deal with asynchronous messages in the message queue of the LTERM partner at the time when the connection is being established.
		'Y'	Asynchronous messages to the client remain queued. In an application without user IDs, UTM executes an automatic service restart for this LTERM partner. In a UTM cluster application without user IDs, 'Y' is only permitted if it was generated with CLUSTER USER-RESTART=YES.
		'N'	UTM deletes all asynchronous messages from the queue when the connection is established. If the job is a job complex, then a negative confirmation job is activated. UTM does not execute an automatic restart for the LTERM partner in an application without user IDs.
		if qamsg='Y' then restart='Y' must be set.
o	annoamsg	Only on BS2000 systems: Only relevant for the LTERM partner of a terminal. In annoamsg you specify if UTM is to announce an asynchronous message to the terminal before outputting:
		'Y'	Asynchronous messages are announced by a message appearing in the system line.
		'N'	Asynchronous messages are output immediately (without announcement).
o	netprio	Only on BS2000 systems: Specifies the transport priority used for the transport connection between the application and the client/printer.
		'M'	"Medium" transport priority
		'L'	"Low" transport priority
		For native TCP/IP connections (t_prot = SOCKET) this field has no significance.
o	kerberos_dialog	Only on BS2000 systems: Specifies whether a Kerberos dialog is performed on the establishment of a connection for clients that support Kerberos and are connected with the application directly via via this LTERM partner (not via OMNIS).
		'Y'	A Kerberos dialog is performed.
		'N'	No Kerberos dialog is performed.

1	All fields in the data structure kc_lterm_str that are not listed and all fields that are not relevant to the operating system you are using are to be set to binary zero. The data structure is described in chapter "kc_lterm_str - LTERM partners".

Clients/printers are assigned to LTERM partners (LTERM - PTERM) when clients/printers are being added to the configuration, or with the aid of KC_MODIFY_OBJECT.