KDCSWTCH allows you to redefine the assignment of clients and printers (PTERM) to LTERM partners.
KDCSWTCH is only permitted in standalone UTM applications.
KDCSWTCH has the following effect:
the existing assignment of a client/printer to an LTERM partner is cancelled and
the client/printer is assigned to the specified LTERM partner.
This function can only be performed when no logical connection exists between the client/printer and the UTM application.
With KDCSWTCH you can, for example, assign another printer to a printer pool. In a printer pool, several physical printers are assigned to one LTERM partner.
If on the other hand you wish to assign an LTERM partner to a printer to which, in turn, a printer control LTERM is assigned (CTERM), then the control identification (CID) of that printer must be unique within the printer control LTERM range.
openUTM on Windows systems does not support any printers.
Restriction
Reassignment of the LTERM partner is possible only for terminals and printers. The assignment to an LTERM partner specified on configuration cannot be changed
for UPIC clients
for TS applications (APPLI/SOCKET) generated as interactive partners
for clients that connect to the application via an LTERM pool
for LTERMs that belong to an LTERM bundle or an LTERM group
If you assign a new LTERM partner to a terminal or printer, the LTERM partner may not be assigned to a terminal/printer of another protocol type (either currently or in the past). Distinctions are drawn here between the following 4 protocol types: terminals, TS applications, printers and RSO printers.
KDCSWTCH is therefore rejected if:
the client specified in ptermname is a UPIC client or a TS dialog application (PTYPE=UPIC-R/L or PTYPE=APPLI/SOCKET) or
the LTERM partner specified in ltermname was previously assigned to a UPIC client or a TS dialog application or if
the LTERM partner specified in ltermname is assigned to an LTERM pool or if.
the printer specified in ptermname is an RSO printer (PTYPE=RSO) and the LTERM partner specified in ltermname was previously assigned to a normal printer.
the LTERM partner specified in ltermname belongs to an LTERM group or an LTERM bundle.
Period of validity of the change
These changes remain in force after the end of the application.
BS2000 systems:
KDCSWTCH ltermname,ptermname,proname [ ,applname ]
Unix, Linux and Windows systems:
KDCSWTCH ltermname,ptermname [,proname [ ,applname ] ]
For administration using message queuing you must enter KDCSWCHA.
ltermname | ||
Name of the LTERM partner to which the client or printer should be assigned. The LTERM partner must exist in the configuration of the UTM application. | ||
ptermname, proname, applname | ||
Uniquely identifies the client/printer. | ||
ptermname | ||
Name of the client or printer (PTERM name) | ||
proname | ||
Name of the processor on which the client is running or to which the client or printer is connected. The proname entry is mandatory in UTM applications on BS2000 systems. In UTM applications on Unix, Linux or Windows systems, proname only has to be entered if the client or printer is not connected locally. Default value in openUTM on Unix, Linux or Windows systems: | ||
applname | ||
This entry is only meaningful for UPIC clients and TS applications. For applname, please enter the name of the UTM application which was assigned to the client when it was entered in the configuration. The applname entry is mandatory if the BCAMAPPL name assigned to the client does not match the name of the UTM application defined for KDCDEF generation in MAX APPLINAME. If applname is not entered, the command is rejected with this message:
Default: | ||
Output from KDCSWTCH
The new and old assignments between client/printer and LTERM 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.
The following section shows you the outputs for the calls with a short and with a long host name.
KDCSWTCH ltermname1,ptermname1,proname1,applname1
Here the LTERM partner lterm1 is assigned to the client pterm1.
KDCSWTCH lterm2,pterm1,proname1,app11 PTERM | PRONAM | BCAMAPPL | NEW LTERM || OLD LTERM ---------+----------+----------+-----------++---------- pterm1 | proname1 | appl1 | lterm2 || lterm1 ---------+----------+----------+-----------++---------- pterm2 | proname2 | appl2 | || lterm2
KDCSWTCH lterm2,pterm1,long.processor.name1,appl1
PTERM | PRONAM | BCAMAPPL | NEW LTERM || OLD LTERM
---------+----------+----------+-----------++----------
pterm1 | long.processor.name1
| appl1 | lterm2 || lterm1
---------+----------+----------+-----------++----------
pterm2 | proname2 | appl2 | || lterm2
Explanation of the output
openUTM outputs the old and new assignment for the client ptermname entered in the KDCSWTCH call (here pterm1), and for the client assigned to the LTERM partner lterm2 before the KDCSWTCH call (here pterm2).
Before the KDCSWTCH call, LTERM partner lterm1 was assigned to client pterm1 and client pterm2 was assigned to LTERM partner lterm2 (see column headed OLD LTERM). Both assignments are cancelled by the KDCSWTCH call.
If pterm1 and pterm2 are clients (i.e. not printers), then the old assignments linking LTERM partners to PTERMs are cancelled.
If pterm1 and pterm2 are printers, the old assignment of lterm2 to pterm2 is not cancelled. A printer pool is then always created at this point, i.e. both printers are assigned to the LTERM partner lterm2.
PTERM | Name of the client or printer | |
PRONAM | Name of the processor on which the client/printer is located | |
BCAMAPPL | Name of the local UTM application through which connection to the client/printer is established | |
NEW LTERM | Name of the LTERM partner to which the client/printer was assigned by the KDCSWTCH call | |
ltermname1 | ||
Name of the LTERM partner which was assigned to the client/printer with the KDCSWTCH call | ||
ltermname2 | ||
Name of the LTERM partner which was assigned to the client/printer before the KDCSWTCH call. | ||
OLD LTERM | Name of the LTERM partner to which the client/printer was previously assigned. | |
Example: Combining printers to form printer pools
Printers pterm1 and pterm2 are to be combined to form a printer pool. The LTERM partner of the printer pools is to be lt-bundle.
Assignment before the KDCSWTCH call:
Printer pterm2 is already assigned to the LTERM partner lt-bundle. The printer pterm1 is assigned to the LTERM partner lt-print.
Call:
KDCSWTCH lt-bundle,pterm1,proname1,appl1
Output:
PTERM | PRONAM | BCAMAPPL | NEW LTERM || OLD LTERM ---------+----------+----------+-----------++---------- pterm1 | proname1 | appl1 | lt-bundle || lt-print ---------+----------+----------+-----------++---------- pterm2 | proname2 | appl2 | lt-bundle || lt-bundle