KC_ONLINE_IMPORT - Import application data online

In a UTM cluster application (Unix, Linux and Windows systems), following the normal termination of a node application, another running node application can import messages to LTERMs, (OSI) LPAPs, asynchronous TACs, TAC queues and open asynchronous services from the terminated node application provided that its KDCFILE comes from the same generation run. The imported data is deleted in the terminated node application. Prior to import, a check is performed to determine whether an online import is running. If it is, the new import is rejected. Online import is only possible in UTM-S applications. Open asynchronous services are not imported if the service contains database transactions with SESAM/SQL.

Execution / period of validity / transaction management / clusters

KC_ONLINE_IMPORT initiates the online import of the application data, i.e. an online import job is generated. When control returns to the program unit, the online import has not yet been performed. Online imports are not subject to transaction management. It cannot be rolled back by a subsequent RSET call in the same transaction. Online import is performed by a process in the application.

When the job has been processed, UTM issues a message informing you of the success or failure of the online import. If the import was successful but it was not possible to import all the data due to a temporary resource bottleneck, another online import can be run to import the outstanding data into another node application or, once the bottleneck has been cleared, into the same node application.

This function is only permitted in cluster operation. The online import operation is performed in the node application in which the call is made.

Parameter settings
Parameter area
Field name	Contents
version	KC_ADMI_VERSION_1
retcode	KC_RC_NIL
version_data	KC_VERSION_DATA_11
opcode	KC_ONLINE_IMPORT
subopcode1	KC_ALL
id_lth	0
select_lth	0
data_lth	Length of the data structure
Identification area
—
Selection area
—
Data area
Data structure

Data returned by UTM
Parameter area
Field name	Content
retcode	Return codes

subopcode1

With subopcode1=KC_ALL, you specify that all messages, i.e. messages to (OSI) LPAPs, asynchronous TACs, TAC queues and open asynchronous services are to be imported.

data_lth

In data_lth, you enter the length of the data structure in the data area.

Data area

Specify the data structure kc_online_import_str in the data area.

In kc_online_import_str, specify the number of the node from which the application data is to be imported.

The data structure kc_online_import_str is defined as follows.

struct kc_online_import_str

char import_node[4];

The field in the data structure has the following meaning:

import_node

Number of the node from which the application data is to be imported.

retcode

openUTM indicates the return code from the call in the retcode field. Alongside the return codes listed in section "Return codes", the following return codes may also occur:

Maincode = KC_MC_REJECTED

The call was rejected by openUTM.

Subcode:

KC_ONLINE_IMPORT_RUNNING

An attempt has been made to start an online import while an online import is already running.

KC_SC_CCFG_INVALID_NODE_INDEX

The number of the node application from which the application data is to be imported is invalid. The number is either the number of the local node application or a number that does not belong to the UTM cluster application.

KC_SC_CCFG_INVALID_NODE_STATE

The node application from which the application data is to be imported has a status that is not valid for online imports. An invalid status means that the node application

• has either never been started, or

• has been terminated abnormally, or

• is not running

Maincode = KC_MC_NOT_EXISTENT

The number of the node application from which the import is to be performed lies outside of the valid range of values from 1 to 32.

Subcode:

KC_SC_NO_INFO