This modification relates to an LTERM partner.
You must pass the name of the LTERM partner to UTM in the identification area (kc_name8 in the union kc_id_area).
In the data area you must pass the data structure kc_lterm_str with the new values of the properties.
Possible modifications
Disable the LTERM partner or release the disabled LTERM partner. LTERM partners in an LTERM pool cannot be disabled or released with obj_type=KC_LTERM (see in this connection obj_type= KC_TPOOL; "obj_type=KC_TPOOL").
To disable or release an LTERM partner, specify the following in kc_lterm_str:
Field name
Meaning
state='N'
Disables the LTERM partner.
Disabling a dialog partner (usage_type='D') has the following effect:
A client connection request is performed. The connection is disabled and UTM message K027 is output. With the exception of KDCOFF, no client/user jobs are performed.
Any existing connection is maintained. Any input with the exception of KDCOFF is acknowledged with UTM message K027.
The lock does not take effect until a synchronization point (end of transaction) is reached on this connection.
If the LTERM partner is disabled, KDCOFF BUT has the same effect as KDCOFF.
If the LTERM partner of a printer is disabled, the print jobs are retained in the message queue. Print jobs initiated after a disable operation are not rejected; they are entered in the message queue.
state='Y'
Releases the LTERM partner, i.e. cancels a lock.
Period of validity / transaction management: Type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Set up or shut down the connection to the client or printer assigned to this LTERM partner.
Field name
Meaning
connect_mode='Y'
The connection to the client/printer is to be set up.
connect_mode='Y' is not permitted if the LTERM partner you have specified in the identification area belongs to an LTERM pool or is assigned to a UPIC client.connect_mode='N'
The connection to the client/printer is to be shut down immediately.
A connection shutdown initiated with connect_mode = 'N' takes immediate effect, with the result that services may be terminated abnormally (PEND ER).
Using connect_mode='N', you can also shut down the connection to a client that is connected to the application via an LTERM pool, i.e. you can also specify in the identification area the name of an LTERM partner that belongs to an LTERM pool.Period of validity / transaction management: type A ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Only on BS2000 systems:
Assign a new start format to the LTERM partner or delete the start format of the LTERM partners.You can assign a start format to each LTERM partner that has been configured for connecting terminals. In order to modify the start format, you must always specify the format name and the format attribute of the new start format.
A precondition for allocation of a start format is that a formatting system must have been generated (KDCDEF statement FORMSYS). If the start format is a #format, then a signon service must also have been generated.
Field name
Meaning
format_attr
Format identifier for the new start format:
'A'
for the format attribute ATTR. The format name at the KDCS program interface is +format_name.
'N'
for the format attribute NOATTR. The format name at the KDCS program interface is *format_name.
'E'
for the format attribute EXTEND. The format name at the KDCS program interface is #format_name.
The meanings of the format attributes are described in section "format_attr, format_name (only on BS2000 systems)" in chapter "kc_lterm_str - LTERM partners".
format_name[7]
Name of the start format. The name may be up to 7 characters long and may contain only alphanumeric characters.
To delete the start format, enter blanks in format_attr and format_name.
Period of validity / transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Activate the BCAM trace for the connections for this LTERM partner.
The BCAM trace function monitors all connection-related activity.
The precondition for LTERM-specific activation is:
The BCAM trace is not generally activated for all LTERM and LPAP partners, i.e. the trace is either completely deactivated or explicitly activated only for selected LTERM/LPAP partners and USERs.
The precondition for LTERM-specific deactivation is:
The BCAM trace can only be deactivated for specific LTERM partners if the BCAM trace is not generally activated.
You will find information about general activation and deactivation of the BCAM trace in the description of the data structure kc_diag_and_account_par_str starting from "kc_diag_and_account_par_str - Diagnostic and accounting parameters".
Field name
Meaning
bcam_trace='Y'
The BCAM trace is explicitly activated for this LTERM partner. All events on the connection to the client/printer assigned to this LTERM partner are logged.
When the trace function is activated, each application process creates its own trace file.bcam_trace='N'
The BCAM trace is explicitly deactivated for this LTERM partner.
The trace files are closed only when the trace function is deactivated generally (object type KC_DIAG_AND_ACCOUNT_PAR; "obj_type=KC_DIAG_AND_ACCOUNT_PAR").Period of validity / transaction management: type IR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Exchange the master LTERMs of two LTERM bundles or add a group LTERM to a different LTERM group.
This function is only permitted in standalone UTM applications.
If the LTERM is the master LTERM of the LTERM bundle, you can replace all the slave LTERMs and the associated PTERMs with a different master LTERM. In this event, a master LTERM of an LTERM bundle must be specified in the master parameter.
If the LTERM is a group LTERM of an LTERM group, you can assign it to a different LTERM group. The primary LTERM that you specify in the master parameter must either be a normal LTERM, a primary LTERM of an LTERM group or a master LTERM of an LTERM bundle. A normal LTERM must fulfill the following conditions:
A PTERM with the PTYPE APPLI or SOCKET must be assigned to the LTERM.
The LTERM must not be a slave LTERM of an LTERM bundle.
The LTERM must have been generated with USAGE=D.
Specify the following in the data structure kc_lterm_str:
Field name
Meaning
master[8]
The name of a master LTERM in an LTERM bundle, the name of a primary LTERM in an LTERM group or the name of the normal LTERM. The name can be up to 8 characters in length and may only contain alphanumeric characters.
Period of applicability / transaction management: type PD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Some of the modifications can also be performed with KDCLTERM ("KDCLTERM - Change the properties of LTERM partners") or KDCDIAG ("KDCDIAG - Switch diagnostic aids on and off"). |