KDCMUX - Change properties of multiplex connections (BS2000 systems)

KDCMUX allows you to change the properties of multiplex connections. You can:

• disable or re-enable multiplex connections

• activate or deactivate multiplex connections

• make specifications regarding the establishment of a connection when the application starts.

Things to note when establishing a connection

KDCMUX...,ACTION=CON merely initiates the establishment of a connection. Successful execution of this command does not therefore mean that the connections are actually established or even that they can, in fact, be established successfully (e.g. a connection attempt may fail due to a fault in the transport system). You should therefore use KDCINF to check whether openUTM has actually been able to establish a connection. For example:

KDCINF MUX,LIST=(muxname_1,muxname_2,...,muxname_10)

If a connection is to be established for a disabled multiplex connection (STATUS=OFF), you must make two calls with KDCMUX.

1. KDCMUX to re-enable the multiplex connection, e.g.:

   KDCMUX MUX=muxname,STATUS=ON

2. KDCMUX call to arrange for a connection to be established, e.g.:

   KDCMUX MUX=muxname,ACTION=CON

Period of validity of the change

The period for which these changes remain valid depends on the type of change and is therefore specified in the description of each operand.

---

KDCMUX      MUX={ muxname | (muxname_1,muxname_2,...,muxname_10) }

           [ ,ACTION={ CON| DIS | ACON | NACON } ]

           [ ,BCAMAPPL=applname ]

           [ ,MAXSES=number_sessions ]

             ,PRONAM=proname

           [ ,STATUS={ ON| OFF } ]

---

For administration using message queuing you must enter KDCMUXA.

MUX=(muxname_1,muxname_2,...,muxname_10)
		Name of the multiplex connection to be administered.  For muxname_1,...,muxname_10 , names must be entered that have been defined with MUX statements during KDCDEF generation.  For each KDCMUX call you can enter a maximum of 10 names. If you only enter one name you do not need to key in the parentheses.
ACTION=		ACTION allows you to initiate the establishment and shutdown of connections to the specified multiplex connections. You can specify whether or not openUTM is to establish connections to the specified multiplex connections automatically in subsequent application starts.
	CON	(connection)  openUTM initiates the establishment of connections to the specified multiplex connections. KDCINF allows you to check whether or not the connection was established successfully.
	DIS	(disconnection)  Connections to the specified multiplex connections are shut down. The connection is shut down with immediate effect: this means that not even open services can be completed.
	ACON	(automatic connection)  At subsequent application starts, openUTM is to activate the multiplex connections automatically, i.e. it is to establish the connections automatically. ACTION=ACON takes effect until automatic connection establishment is explicitly reset by means of system administration functions (NACON action).
	NACON	(no automatic connection)  If the ACON property is entered for the specified multiplex connections during generation by the administration function, it is to be deleted. In other words connections to the specified multiplex connections should no longer be established automatically during subsequent application starts.
BCAMAPPL=applname
		Name of the local application through which connections are established to the multiplex connections. For applname, the application name assigned to the multiplex connections in the MUX statements during KDCDEF generation should be specified, i.e. the name which the message router must pass to UTM in order for a connection to be established.  Default value:  If you do not enter BCAMAPPL, the name generated in the APPLINAME operand in the KDCDEF control statement MAX is assumed.
MAXSES=number_sessions
		number_sessions defines the maximum number of terminals through which each of these multiplex connections can be connected at the same time. This change only applies to the current application run. Minimum value: 1  Maximum value: 65000
PRONAM=proname
		Name of the processor running the message router to which the multiplex connection is assigned.
STATUS=		The specified multiplex connections are disabled or released again.
	ON	Releases (enables) the multiplex connections (with immediate effect).
	OFF	Releases (enables) the multiplex connections (with immediate effect). Disables multiplex connections. No connection to any of the specified multiplex connections should exist at the point in time when they are disabled.  If such a connection does exist, openUTM will not disable it. The value ON is issued in the output from KDCMUX (see chapter "Output from KDCMUX") for STATUS NEW and STATUS OLD.

Output from KDCMUX

The new and old properties of the multiplex connections (NEW, OLD) currently being administered are displayed on the administrator terminal.

MUX     PRONAM   BCAMAPPL  STATUS         CONNECTION     MAXSES
                           NEW    OLD     NEW    OLD     NEW    OLD
muxname proname  applname  ON|OFF ON|OFF  AC|D|W AC|D|W  number number

Explanation of the output

MUX	Name of the multiplex connection
PRONAM	Name of the processor on which the message router is running
BCAMAPPL	Name of the UTM application which was assigned to the multiplex connection for KDCDEF generation.
STATUS	The multiplex connection is disabled (OFF) or not disabled (ON).
CONNECTION
	1st column: The multiplex connection is connected to the application (C) or not (D), or openUTM is currently trying to establish a connection to the multiplex connection (W = waiting for a connection). 2nd column: Every time the application starts, openUTM will try to establish a connection automatically (A) or not (no entry).
MAXSES	Maximum number of terminals that can be connected to the application via this multiplex connection at the same time.