obj_type=KC_LTAC

In order to create a new transaction code by means of which service programs can be started in partner applications, you must place the data structure kc_ltac_str in the data area. The following table shows how the fields in the data structure are to be supplied with data.

	Field name 1	Meaning
m	lc_name[8]	Name of a local transaction code for the remote service program.
o	lpap[8]	Specifies the partner application to which the service program belongs. lpap contains the name of the LPAP or OSI-LPAP partner assigned to the partner application, or the name of a master LPAP partner. If lpap is not specified, the name of the partner application must be specified in the APRO function call (in the KCPA field).
o	rtac[64]	The name of the associated transaction code in the remote application (recipient_TPSU_title).
o	rtac_lth[2]	Specifies the length of the name rtac. The number of relevant bytes is specified in rtac. Minimum value: '1', maximum value: '64'
o	code_type	Specifies which code type is used by UTM internally for the rtac name:
		'I'	INTEGER The TAC name in rtac is a positive integer between 0 and 67108863. rtac names of the code type INTEGER are only permitted for partner applications that are not UTM applications and that communicate via the OSI TP protocol.
		'P'	PRINTABLE-STRING The TAC name in rtac is specified as a string with a maximum length of 64 characters. A distinction is drawn between uppercase and lowercase. A TAC name with the code type PRINTABLE-STRING can contain the following characters: A, B, C, . . . , Z a, b, c, . . . , z 0, 1, 2, . . . , 9 the special characters ' - : ? = , + . ( ) / (blank)
		'T'	T61-STRING rtac contains a T61 string. For the code type T61-STRING, UTM supports all the characters of the code type PRINTABLE-STRING as well as the following special characters: $ > < & @ # % ; * _
o	state	Specifies whether or not lc_name is disabled for the remote service program after the startup of the local application.
		'Y'	lc_name is not disabled. Jobs are accepted for the associated remote service.
		'N'	lc_name is disabled. Jobs are not accepted for the associated remote service.
o	accesswait_sec[5]	Maximum time waited in seconds for a session to be occupied (possibly including connection establishment) or for an association to be established after the remote service is requested (the LTAC is called).
		In the case of asynchronous jobs (LTAC with ltac_type='A'), a wait time != 0 means the job is always entered in the local message queue for the partner application. Dialog jobs are accepted.
		A wait time accesswait_sec=0 means that dialog jobs are rejected if no session/association for which the local application is the contention winner has been generated. In the case of asynchronous jobs, the FPUT call is rejected with a return code if there is no logical connection to the partner application. If there is a logical connection to the partner application, the message is entered in the local message queue.
		Dialog jobs are rejected regardless of the value in accesswait_sec if there is no logical connection to the partner application. The establishment of a connection is initiated at the same time.
		Minimum value: '0' (jobs are rejected) Maximum value: '32767'
o	replywait_sec[5]	Maximum time in seconds waited by UTM for a reply from the remote service. By limiting the wait time you can ensure that clients or users on the terminal do not have to wait too long.
		replywait_sec='0' means the wait time is not limited.
		Minimum value: '0' Maximum value: '32767'
o	lock_code[4]	Contains the lock code assigned to the remote service in the local application (data access control). lock_code can contain a number between '0' and the maximum value defined by means of the KEYVALUE operand of the KDCDEF statement MAX. '0' means that the LTAC is not protected by a lock code.
		If lock_code is specified, access_list cannot be specified.
o	ltac_type	Specifies whether the local application processes jobs in a dialog with the remote service or whether asynchronous jobs are transferred to the partner service.
		'D'	Jobs to the partner service are processed in a dialog.
		'A'	The partner service is started asynchronously (by means of message queuing).
o	ltacunit[4]	Contains the number of accounting units calculated in the UTM accounting phase for each ltac call. The accounting units are added to the accounting unit counter of the user ID that called the ltac.
		Minimum value: '0', maximum value: '4095'
o	access_list[8]	Describes a key set that specifies the access rights that a user of the local UTM application must have in order to send a job to the remote service program. Whether the job is executed in the remote application depends on the access rights defined there. The key set must be created first or already have been defined at generation.
		If access_list is specified, lock_code cannot be specified.
		A user can only access the LTAC if the key set of the user, the key set of the LTERM partner via which the user is signed on and the specified key set have at least one key code in common.

1	All fields of the kc_ltac_str data structure that are not listed and all the fields that are not relevant to the operating system used are to be set to binary zero. The data structure is described in full in chapter "kc_ltac_str - Transaction codes of remote services (LTAC)".