KDCPTERM - Change properties of clients and printers

KDCPTERM allows you to change the properties of clients and printers.

You can perform the following actions:

• Disable or re-enable clients and printers.

• Establish and shut down logical connections to clients and printers. In particular, you can establish or shut down connections to individual printers in a printer pool.

• Initiate or prevent the automatic establishment of connections to clients and printers when the application starts.

• Only on BS2000 systems: If terminals are connected to the application via a multiplex connection, you can release sessions that are in DISCONNECT-PENDING mode.

Things to note when establishing and shutting down connections

With KDCPTERM you can initiate immediate connections or the automatic establishment of a connection for each subsequent application start for the following objects (ACTION=CON or ACON):

• On BS2000 systems: Printers, terminals and transport system applications of the type APPLI or SOCKET.
  Calls from connections to UTM clients with the UPIC carrier system (PTYPE=UPIC-R) are rejected.
  The initiative for establishing a connection always lies with the UTM client.

• On Unix, Linux and Windows systems: Printers (PTYPE=PRINTER) and transport system applications of the type PTYPE=APPLI or SOCKET.
  Calls from connections to UPIC clients (PTYPE=UPIC-R/-L) and to terminals (PTYPE=TTY) are rejected. The establishment of connections to these clients can only be initiated by the clients themselves.

No connections can be established with KDCPTERM to clients which connect to the application by means of an LTERM pool.

If there is a request for connection to be established with a client for which the actions CON and ACON are not permitted, the KDCPTERM call is rejected.

In response to a successful call from KDCPTERM with the action CON, UTM initiates the establishment of a connection to the specified clients and printers. Successful execution of this command does not mean that the connections have actually been established or even, indeed, that they can be established. To find out whether the connections are actually possible, you must enter a specific query (e.g. with KDCINF).

Termination of a connection with ACTION=DIS causes the connection to a client or printer to be shut down immediately. Neither can open services be terminated.

Things to note when disabling clients or printers

A lock operates as follows:

• Every connection request from a client is rejected.

• Existing connections are retained.
  The lock only comes into effect when a client next attempts to establish a logical connection.

• Calls from a connection to a disabled client or printer are rejected.

Asynchronous messages to disabled clients or printers are stored in the buffer memory or the KDCFILE and can give rise to a shortage or resources!

Effect in UTM cluster applications

The effect in UTM cluster applications is described in the sections devoted to the individual operands since some of the changes made with KDCPTERM apply locally to the node whereas others take effect globally in the cluster.

Period of validity of changes

The period during which the changes remain effective is dependent on the type of change and is therefore specified in the operand descriptions.

---

KDCPTERM    PTERM={ ptermname | (ptermname_1,ptermname_2,...,ptermname_10) }

[ ,BCAMAPPL=applname ]

[ ,STATUS={ ON| OFF } ]

BS2000 systems:

  ,PRONAM=proname

[ ,ACTION={ CON| DIS | REL | ACON | NACON } ]

Unix, Linux and Windows systems:

[ ,PRONAM=proname ]

[ ,ACTION={ CON| DIS | ACON | NACON } ]

---

For administration using message queuing you must enter the KDCPTRMA administration command.

PTERM=(ptermname_1,...,ptermname_10)
		Name of the clients and printers to be administered. You can enter a maximum of 10 names for each KDCPTERM call.  If only one name is entered you do not need to key in the parentheses. All names on the list must belong to clients and printers located on the same computer.
BCAMAPPL=applname
		Only applicable to client applications of the PTYPE=APPLI/SOCKET or PTYPE=UPIC-R/L type. For applname, enter the name of the local UTM application with which the connections between the UTM application and client applications are established. Default: The application name specified in MAX APPLINAME for KDCDEF generation is accepted.
STATUS=
		Disables a client or printer or allows disabled clients and printers to be used again (i.e. to be re-enabled). In UTM cluster applications, the operand applies globally in the cluster.
	ON	The clients/printers ptermname_1,...,ptermname_10 are released for use again.
	OFF	The clients/printers ptermname_1,...,ptermname_10 are to be disabled. Enabling and disabling in this manner extend beyond the end of the current application.
PRONAM=proname
		Name of the processor on which the clients/printers  (ptermname_1,...,ptermname_10) are located. At this point, enter the name of the processor that was specified when the clients/printers were specified in the configuration. For clients and printer in a UTM application on BS2000 systems, entering proname is mandatory. In a UTM application running on a Unix, Linux or Windows system you do not enter proname if the specified clients and printers are connected locally.
ACTION=		Defines which action openUTM is to perform.
	CON	openUTM should establish logical connections to the clients and printers ptermname_1,...,ptermname_10. In UTM cluster applications, the operand applies locally in the node. ACTION=CON is not permitted for: UPIC clients clients connected to the application by an LTERM pool terminals connected to the openUTM application on BS2000 systems by a multiplex connection terminals in a UTM application on a Unix, Linux or Windows system (PTYPE=TTY)
	DIS	openUTM is to shut down logical connections to the clients and printers ptermname_1,...,ptermname_10. In UTM cluster applications, the operand applies locally in the node. In openUTM on BS2000 systems, ACTION=DIS is rejected if a terminal connection is to be shut down which is connected to the UTM application by a multiplex connection and which exists for a session in DISCONNECT-PENDING mode. The KDCPTERM call is rejected. The logical connection must be shut down with ACTION=REL.  You can check whether or not a session is in DISCONNECT-PENDING mode with KDCINF PTERM.
	REL (only on BS2000 systems)
		ACTION=REL is only permitted if the clients specified in ptermname_1,...,ptermname_10 are connected to the application by a multiplex connection. A session is released with ACTION=REL. The logical connection to the client is shut down.  Entry of ACTION=REL is only permitted if the session is in DISCONNECT-PENDING mode and if its timer has run out (approx. 10 minutes).
	ACON	(automatic connection)  During subsequent application starts, UTM should automatically establish logical connections to ptermname_1,...,ptermname_10. In UTM cluster applications, the operand applies globally in the cluster. ACTION=ACON is not permitted for: UPIC clients clients connected to the application via an LTERM pool terminals on a UTM application on a Unix, Linux or Windows system with PTYPE=TTY.
	NACON	(no automatic connection)  Renders the ACON entry ineffective, i.e. openUTM does not establish any logical connections to ptermname_1,...,ptermname_10 during subsequent application starts. In UTM cluster applications, the operand applies globally in the cluster.

Output from KDCPTERM

The new and old properties of specified physical clients and printers (NEW, OLD) are displayed on the administrator terminal.

The output depends on whether a short or a long host name is assigned to a PTERM. In the case of a long host name, the information on a PTERM is output in two screen lines.

PTERM    PRONAM   BCAMAPPL  STATUS         CONNECTION
                            NEW    OLD     NEW         OLD 
pterm1   proname  applname  ON|OFF ON|OFF  C|D|W A M   C|D|W A M    [POOL PTERM] 
                                           T|E         T|E 
pterm1   long.processor.name 
                  applname  ON|OFF ON|OFF  C|D|W A M   C|D|W A M    [POOL PTERM] 
                                           T|E         T|E 

Explanation of the output

PTERM

Name of the client/printer

PRONAM

Name of the processor on which the client/printer is located

BCAMAPPL

Name of the local UTM application through which connections are established to the client/printer

STATUS

The client/printer is disabled (OFF) or not disabled (ON) 

CONNECTION

1st column:

C/D/W	Client/printer is currently connected to the application (C) or is not connected (D), or openUTM is trying to establish a connection (W = waiting for a connection)
T/E	Is only output for terminals which use a multiplex connection to connect with a UTM application on a BS2000 system. T: (timer) The session is in DISCONNECT-PENDING mode; the timer isrunning, waiting on confirmation that a connection has beenestablished E: (expired) The session is in DISCONNECT-PENDING mode and has timedout waiting for confirmation.

2nd column:
A: Connection established automatically when the application starts

3rd column (only for UTM applications on BS2000 systems):
The client is connected (M) or not (no entry) to the application via a multiplex connection.

POOL PTERM

This is output if the client is connected via LTERM pool.