For clients and printers in an openUTM application, you can perform the actions described in the following section.
Printers are not supported by openUTM on Windows systems.
Transferring logical properties from one terminal to another
If a terminal is defective, or if the user previously connected to the terminal wishes in future to work from a different terminal, you can transfer the logical properties of one terminal to another one in stand-alone UTM applications. You do this by assigning the LTERM partner of one terminal to another terminal (of the same type). In so doing, you can for example transfer the following properties to the new terminal:
restart information
access rights (key set)
access protection (access list or lock code)
message queue with asynchronous messages
user ID for the automatic KDCSIGN, where defined
language environment, where defined
start format, where defined
control value qlev for the message queue, where defined
 | KDCSWTCH |
| KC_MODIFY_OBJECT with obj_type=KC_PTERM |
Assigning the message queue of one printer to another printer
In standalone UTM applications, if one printer malfunctions, the printer queue can be assigned to another printer (of the same type). This printer then processes the print jobs in that queue. To do this, you must disable the defective printer and assign the LTERM partner of the printer to a different one.
In addition to the printer queue, defined logical properties are also transferred to the new printer. This includes the control value qlev for the printer queue and the value plev. As soon as plev print jobs are waiting in the printer queue, openUTM automatically sets up a connection to the printer.
 | KDCPTERM: Disable a printer |
 | KC_MODIFY_OBJECT with obj_type=KC_PTERM |
Generating printer pools
In standalone UTM applications, at runtime you can group printers in the application together into printer pools. Printer pools are created when you assign additional printers to the LTERM partner of one printer. The printer queue belonging to the LTERM partner is then processed jointly by all printers assigned to that LTERM partner. Good reasons for generating a printer pool can include:
The message queue of a printer may become too large. It may prove necessary to wait too long for requested print outputs and the page pool in which jobs are kept in buffer storage can be placed under excessive strain. To process print jobs in the queue, several printers should be implemented.
When a printer is entered, if the maximum specified number of print jobs which can be stored in a printer queue at one time (plev) is too small, print jobs sent to this printer will be rejected frequently.
Additional printers have recently become available in a branch office. These printers are to process all print jobs from this branch office on a joint basis, i.e. when a print job is issued, it is sent for processing to a printer which is free at the time. You can load these new printers in the configuration dynamically and group them in printer pools with the existing printers.
 | KDCSWTCH |
| KC_MODIFY_OBJECT with obj_type=KC_PTERM |
Disabling printers/clients and their LTERM partners
You can disable clients and printers and their LTERM printers. It is not possible to establish a connection to disabled clients or via disabled LTERM partners. You can still send asynchronous jobs to disabled LTERM partners. These are then stored in the message queue until the control value for that message queue is reached. However, the jobs are not processed until the LTERM partners are re-enabled.
 | KDCLTERM, KDCPTERM |
| KC_MODIFY_OBJECT with obj_type=KC_PTERM or KC_LTERM |
Connections to clients and printers
If necessary you can establish and terminate connections to TS applications, terminals and printers.
In the case of terminals, TS applications and printers that are always connected to the application, you can arrange for connections to be established automatically each time the application starts.
 | KDCLTERM, KDCPTERM |
| KC_MODIFY_OBJECT with obj_type=KC_PTERM or KC_LTERM |
Reading information about the availability of clients and printers
Using the information functions of openUTM you can query information about the availability of clients and printers. The following information is provided:
Current status of client/printer (is it disabled at present or not?)
Does a connection exist at present, or is an attempt currently being made to establish a connection?
Period of time where the printer or client has already been connected to the application
Number of messages replaced on the connection
Number of failures in the connection to client/printer
Control value of message queue (qlev)
Number of jobs in the message queue of a printer/printer pool for which a connection to the printer (pool) is established automatically.
 | KDCINF LTERM or PTERM |
| KC_GET_OBJECT with obj_type=KC_PTERM or KC_LTERM |
