Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Modifying clients/printers and LTERM partners

In order to modify the properties of a client or printer, you have to call KC_MODIFY_OBJECT with the object type KC_PTERM. To modify the properties of an LTERM partner, you must specify the object type KC_LTERM.

LTERM partners that belong to an LTERM pool or clients/printers that are connected via an LTERM pool cannot be modified.

In the case of clients/printers and LTERM partners, you can change the status and the current state of the connection to the client/printer. A change of status (enabled/disabled) continues to apply after transaction processing beyond the end of the application run. A change to the current state (connection in existence, not in existence, currently being set up) applies when permitted by the utilization level of the application, but not after the end of the application run.

If you want to change the assignment of a client/printer to an LTERM partner, the partner must be in existence (it must not have been deleted). The LTERM partner must not be configured for connection to a client of the type UPIC. In addition, the LTERM partner must not be the master slave of an LTERM bundle or an alias or primary LTERM of an LTERM group. A change to the assignment continues to apply after transaction processing beyond the end of the application run.

In the case of clients/printers, only the LTERM partner, if assigned, or only one mode may be modified for automatic connection setup at the startup of the application. It is only possible to request automatic connection setup at startup of the application if the client/printer is not disabled. A change to connection setup at application startup continues to apply after transaction processing beyond the end of the application run.


Note on BS2000 Systems:

If the LTERM partner is assigned to a terminal, you can change the format attributes. However, a specific start format can only be used for applications without user IDs or when a separate sign-on service is defined. A change to the format attributes continues to apply after transaction processing beyond the end of the application run.