kc_mux_str - Multiplex connections (BS2000 systems)

The data structure kc_mux_str is defined for the object type KC_MUX. In the case of KC_GET_OBJECT, UTM returns the names and properties of a multiplex connection via which a message router can connect to the application in kc_mux_str.

Several terminal clients can be connected simultaneously to the UTM application via a multiplex connection.

mod 1	Data structure kc_mux_str
-	char mx_name[8];
-	char pronam[8];
-	char bcamappl[8];
x(GPD)	char auto_connect;
x(GPR)	char maxses[5];
x(GPD)	char state;
-	char netprio;
x(A)	char connect_mode;
-	char actcon[5];
-	char maxcon[5];
-	char letters[10];
-	char incnt[5];
-	char wait_go[5];
-	char shortage[5];
-	char rtryo[5];
-	char rtryi[5];
x(IR)	char bcam_trace;

¹  The contents of the field can be modified with KC_MODIFY_OBJECT; see "obj_type=KC_MUX (BS2000 systems)"

The fields in the data structure have the following meanings:

mx_name
	Contains the name of the multiplex connection.
pronam
	The name of the computer containing the message router. The name in pronam is identical to the name of the computer specified for the BCAM generation for this computer.
bcamappl
	The name of the local UTM application (BCAMAPPL name) via which the connection to the message router will be established, i.e. the message router must specify this application name as the partner name when the connection to the UTM application is established. If several multiplex connections (the same computer name is always in pronam) with different BCAMAPPL names exist in the local application for a message router, then several parallel connections can be established to the message router.
auto_connect
	Specifies if the local application automatically establishes a transport connection to the message router during the application start.
	'N'	The connection is not automatically established, it must be established by the administrator (see connect_mode).
	'Y'	UTM attempts to establish the connection to the message router at the start of the local application. If no connection can be made, for example because the message router is not available, then UTM will repeat the attempt to establish the connection at the intervals specified in the conrtime_min timer. The timer can be changed (see the data structure kc_timer_par_str, conrtime_min field "kc_timer_par_str - Timer settings").
maxses
	Specifies the maximum number of simultaneously open sessions that can exist between the message router and the application, i.e. maxses contains the maximum number of clients that can be simultaneously connected to the application via the message router. Minimum value: '1' Maximum value: '65000' (theoretical value)
state	Specifies whether the multiplex connection is currently disabled.
	'Y'	The multiplex connection is not disabled.
	'N'	The multiplex connection is disabled. No connection between the message router and the application can be established at the present time.
netprio
	Specifies the transport priority used on the transport connection between the application and the message router.
	'M'	"Medium" transport priority
	'L'	"Low" transport priority
connect_mode
	Specifies whether the message router is currently connected to the application.
	'Y'	The message router is currently connected to the application.
	'W'	UTM is attempting to establish a connection to the message router.
	'N'	The message router is not currently connected to the application.
actcon
	Contains the number of clients currently connected to the application via this multiplex connection.
maxcon
	Contains the maximum value that actcon has reached during the current application run. maxcon also specifies the maximum number of clients that were simultaneously connected to the application via this multiplex connection during the previous application run.  The counter is reset to 0 at the start of the application.
letters	Contains the number of messages replaced between the message router and the application since the start of the application (input and output messages).
incnt	Contains the number of input messages received from the application via this multiplex connection.  The counter is reset to 0 at the start of the application.
wait_go
	Specifies how often BCAM needed to request the multiplex connection to resend a message because BCAM was not able to accept this message before due to a BCAM bottleneck (WAIT FOR GO). The counter is reset to 0 at the start of the application.
shortage
	Contains the number of BCAM bottlenecks (shortages) for this multiplex connection since the start of the application.
rtryo ( retry out)
	Specifies how often the application needed to retry sending an output message to the message router since the application start.
rtryi ( retry in)
	Specifies how often the application needed to retry reading a message from the message router since the application start.  If a message from the message router is received by BCAM, then BCAM informs UTM that a message is available. UTM then tries to read the message from BCAM.  rtryi contains the number of failed attempts to read the message from BCAM before UTM was finally able to read the message.
bcam_trace
	Specifies whether the BCAM trace for this multiplex connection is explicitly activated or deactivated.
	'Y'	The BCAM is explicitly activated.
	'N'	The BCAM trace is not explicitly activated.
	There is only any point evaluating this field if the BCAM trace is activated explicitly for a number of LTERM partners, LPAP partners or multiplex connections. If the BCAM trace is activated or deactivated generally (kc_diag_and_account_par_str), 'N' is returned for bcam_trace. If the value of bcam_trace is to be modified, the following prerequisites apply to explicit activation: The BCAM trace must be deactivated for everything (kc_diag_and_account_par). The BCAM trace must be deactivated explicitly for this multiplex connection. The prerequisite for explicit deactivation is that the BCAM trace is activated explicitly for a number of LTERM partners, LPAP partners or multiplex connections.