Printers cannot be generated in UTM applications on Windows systems.
Printers that are to be used by a UTM application are connected via LTERM partners that are configured with the logical properties for printers. LTERM partners for printers are defined in the LTERM statement. Printers cannot be connected via LTERM pools. Physical printers are defined with the PTERM statement, which is also where the assignment is made to the LTERM partner.
The connection setup by openUTM can be defined either with PTERM...,CONNECT=YES or with LTERM...,PLEV=. The connection can also be established using administration functions. See also the openUTM manual “Administering Applications”.
| LTERM statement in section "LTERM - define an LTERM partner for a client or printer" |
ltermname
Name of the LTERM via which the printer is connected to the UTM application.
CTERM=
Defines the printer control LTERM so that the user can administer printers, print jobs, and the print jobs in the message queue of the LTERM partner.
PLEV=
Number of printer messages for which openUTM attempts to establish a connection to the printer assigned to this LTERM partner.
If PLEV=1, a connection is established for each print job.
If PLEV=n, the connection is established for the nth print job (n=1 to 32767).
If PLEV=0, the connection setup is not initiated by pending print jobs, rather is initiated explicitly by the administrator using the command KDCLTERM...ACT=CON or KDCPTERM.
The connection is shut down again as soon as there are no further messages for this printer.
PLEV= makes it easier for the user to use printers from various UTM applications (printer sharing). In this case, the connection between a UTM application and the printer is only kept open while the print job is being transmitted, in order to allow other applications to establish a connection. If there are unprocessed print messages for a printer in the message queue of the LTERM partner when the UTM application terminates, these print messages are retained until the next application start. Before terminating the application, the administrator can initiate the processing of the outstanding print messages using the command KDCAPPL SPOOLOUT=ON.
QAMSG=
Messages to printers can be buffered in the message queue of the LTERM partner, even if the printer is not connected to the application.
USAGE=O
USAGE=O defines a printer as a communication partner which can connect to an application via the LTERM partner. Messages can only be sent from the application to the printer.
Each printer must be described in the configuration, i.e. for each printer, a PTERM statement is written with the physical properties of the printer and the assignment is made to an LTERM partner. The assignment between the printer and LTERM partner is static, i.e. the assignment applies until it is canceled using administration commands. You can assign another printer (of the same type) to an LTERM partner during operation, e.g. in the event of a printer fault.
 | PTERM statement in section "PTERM - define the properties of a client/printer and assign an LTERM partner" |
ptermname
Name of the printer
BS2000 systems:
The BCAM name or the RSO name of the printer must be specified.Unix and Linux systems:
The name of a printer group of the spool system must be specified. A printer group used by UTM applications should comprise only one printer. This is the only way to ensure that all parts of a message are output to the same printer if a message comprises message segments (see also the information on printer pools).CID=
The printer is assigned a printer ID printer_id via which the printer can be identified by a printer control LTERM. The printer control LTERM attaches to the LTERM partner to which the printer is assigned.
CONNECT=
Specifies whether or not openUTM automatically establishes a connection to the printer when the application starts. The printer is then explicitly occupied by the application until the next time the connection is cleared down, even if there are no print jobs.
LTERM=
Name of the LTERM partner assigned to the printer ptermname and via which the printer is connected to the UTM application.
PTYPE=
BS2000 systems:
Printer type or *RSO.Unix and Linux systems:
Printer type.
To output the data, the printer process (utmprint) calls the utmlp script. The call also passes parameters to utmlp in addition to the data to be printed. By default, utmlp then passes the data to the lp command (see PTYPE=PRINTER on "PTERM - define the properties of a client/printer and assign an LTERM partner").USAGE=O (only BS2000 systems)
The communication partner is a printer.
The maximum values and limits that are to apply throughout the application for printers are defined with the MAX statement.
| MAX statement in section "MAX - define UTM application parameters" |
CONRTIME=
Time in minutes after which openUTM makes cyclical attempts to reestablish a logical connection. openUTM attempts this for:
Printers to which openUTM establishes a connection as soon as the number of print jobs for this printer exceeds the generated threshold value (LTERM...,PLEV>0). When the connection is aborted, the number of print jobs must be greater than or equal to the threshold value if openUTM is to attempt to re-establish the connection.
Printers to which openUTM automatically establishes a connection (PTERM...,CONNECT=YES), provided that the connection was not terminated by the administration.
If no connection is established when the application starts or if the connection is interrupted during operation, openUTM attempts to reestablish the connection at intervals of CONRTIME=.
PGPOOL=
A sufficiently large value must be specified for the PGPOOL operand so that the page pool can accommodate all print messages in the event of a high print volume.
LOGACKWAIT=
Maximum time in seconds that openUTM is to wait for an acknowledgment from the output devices. This acknowledgment is
for a printer, the logical print acknowledgment from the printer,
for an RSO printer, the acknowledgment from RSO,
with an FPUT call to another application, a transport acknowledgment.