Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

obj_type=KC_MUX (BS2000 systems)

This operation relates to a multiplex connection.

You must identify the multiplex connection unambiguously in the identification area. To do this, in the data structure kc_triple_str of the union kc_id_area, pass the name of the multiplex connection, the name of the computer on which the associated message router is located, and the name of the UTM application through which the multiplex connection is to be established.

In the data area you must pass the data structure kc_mux_str with the new values of the properties.


Possible modifications

  • Disable a multiplex connection or release a disabled multiplex connection.

    No connection between the message router and the UTM application can be set up via a disabled multiplex connection. Specify the following in the data structure kc_mux_str:

    Field name       

    Meaning

    state='N'

    Disables a multiplex connection
    There must be no current connection to the multiplex connection. You must shut down any existing connections with connect_mode='N'.
    It is not possible to shut down the connection and disable a multiplex connection in a single KC_MODIFY_OBJECT call as shutting down the connection can take some time.

    state='Y'

    Releases a multiplex connection, i.e. cancels a lock.

    Period of validity / transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

  • Increase or reduce the maximum number of clients that can be connected concurrently via this multiplex connection.

    Field name        

    Meaning

    maxses[5]

    Specify in maxses the maximum number of sessions that can exist between the message router and the application.

    Minimum value:'1';
    Maximum value:'65000' (theoretical value)

    Period of validity / transaction management: type GPR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

  • Activate or deactivate automatic connection setup to the multiplex connection.

    In automatic connection setup, UTM attempts to establish a connection to the multiplex connection automatically whenever the application starts.

    Specify the following in the data structure kc_mux_str.

     

    Field name                 

    Meaning

    auto_connect='Y'

    As of the next application start, UTM is to attempt to establish the connection to the multiplex connection automatically.

    auto_connect='N'

    As of the next application start, UTM is no longer to establish the connection the multiplex connection automatically. It must then be established explicitly by the administrator.

    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 message router for the multiplex connection.

    Specify the following in the data structure kc_mux_str:

    Field name                 

    Meaning

    connect_mode='Y'

    UTM is to establish the connection to the message router.
    If a connection is to be established for a disabled multiplex connection, the multiplex connection must be released before connection setup with its own KC_MODIFY_OBJECT call (state='Y'). connect_mode = 'Y' cannot be set at the same time as state ='N' (disable multiplex connection).

    connect_mode='N'

    The connection to the message router is to be shut down immediately. A connection shutdown initiated with connect_mode = 'N' takes immediate effect, so it is possible for sessions to be terminated abnormally.

    Period of validity / transaction management: Type A ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

  • Activate or deactivate the BCAM trace for this multiplex connection. Specify the following in the kc_mux_str data structure:

    Field name               

    Meaning

    bcam_trace='Y'

    The BCAM trace is activated explicitly for this multiplex connection. All the events on the connection to the message router assigned to this multiplex connection are recorded.
    When the trace function is created, every process of the application generates its own trace file.

    bcam_trace='N'

    The BCAM trace is deactivated explicitly for this multiplex connection.
    The trace files are not closed until the trace is deactivated with general validity (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")