Clients/printers and LTERM partners can only be removed from the configuration with a delayed delete.
To delete a client or printer from the configuration you must call KC_DELETE_OBJECT (with subopcode1=KC_DELAY) for the object type KC_PTERM. To delete an LTERM partner, you have to indicate the object type KC_LTERM.
You are only allowed to delete a client/printer and its related LTERM partners if the client/printer is not connected to the application. For this reason, you should disable the client/printer before deletion to prevent errors from occurring. Such disabling operations must take place in a separate transaction. To disable the client/printer, see KDCPTERM in "KDCPTERM - Change properties of clients and printers" or KC_MODIFY_OBJECT with "obj_type=KC_PTERM".
Clients/printers and their associated LTERM partners have a logical relationship to one another. For this reason, you must pay attention to the sequence when deleting clients, printers and their LTERM partners. In general terms, the following rule applies:
An LTERM partner cannot be deleted while a.client/printer is assigned to it. |
If the client/printer and the related LTERM partner are to be deleted from the configuration, the following rule applies:
Client/printer (KC_PTERM) before LTERM partner (KC_LTERM). |
Both objects can only be deleted from the configuration one after the other in different transactions.
When deleting LTERM partners, please note:
With UPIC clients (type UPIC-R and UPIC-L) and TS applications (type APPLI or SOCKET), you must delete the client from the configuration before deleting the LTERM partner.
With terminals and printers, you can delete the LTERM partner without removing the terminal or printer from the configuration. In this event, before deleting the LTERM partner, you must assign the client or printer to another LTERM partner in a separate transaction (KDCSWTCH in "KDCSWTCH - Change the assignment of clients and printers to LTERM partners" or KC_MODIFY_OBJECT with "obj_type=KC_PTERM").
You cannot delete the following LTERM and PTERM partners:
LTERM partners belonging to an LTERM pool
LTERMs, belonging to LTERM bundles or LTERM groups,
printer control LTERMs
the LTERM partner KDCMSGLT which openUTM creates internally for the MSGTAC service
LTERM partners belonging to a multiplex connection (only on BS2000 systems)
LTERM and PTERM partners that are used for cluster-internal communication in UTM cluster applications (Unix, Linux and Windows systems).
You can delete all other LTERM partners and clients/printers from the configuration if you comply with the above rules, regardless of whether they were added to the configuration statically (with KDCDEF) or dynamically.
You can delete the LTERM partner defined as recipient (destadm) for the results of asynchronous administration commands. However, in this case, you should define a new recipient, as otherwise the results of asynchronously processed administration commands are lost. To do this, you have the KC_MODIFY_OBJECT call with parameter type KC_MAX_PAR and the administration command KDCAPPL.
Deleting clients, printers and LTERM partners has the following effects:
It is no longer possible to set up a connection to a deleted client/printer. This means that no more messages can be sent to a client or printer once it has been deleted.
No more asynchronous messages can be created for a deleted LTERM partner. In other words, no more asynchronous jobs can be added to the message queue of the LTERM partner.
Asynchronous jobs in the message queue of the LTERM partner at the time of deletion, i.e. jobs created before the deletion process, can no longer be read from the queue by the client/printer. In other words, the asynchronous jobs in the queue can no longer be processed. However, they can still be accessed by administration functions: they can be deleted from the queue. To do this, you can use the KDCS call DADM (see openUTM manual „Programming Applications with KDCS”).
Asynchronous jobs created by an LTERM partner which has already been deleted are still able to run and can be administered. However, when processing jobs, it is no longer possible to create any further asynchronous jobs (follow-up jobs).
TLS areas (TLS = terminal-specific long-term storage area) belonging to a deleted LTERM partner are still available for read and write accesses.