HPUX - LSO Printer Management

HPUX - LSO Printer Management

LSO uses the standard HPUX print spooler on raw queues only
Except for creating VDS2 - print PDF

Important commands
Three commands for printer checks

Icon

Note: there must not be a space between option < -p > and < spooler_name >.
Otherwise the command relates to all printers!!

Printer status from the perspective of the spooler

lpstat -p<spooler_name> ... is idle. enabled since ...

DNS name/IP address of the printer (server or printer box) saved

for this spooler
lpstat -v<spooler_name>
remote to: LP1 on p00605996.degsp.corpintra.net

Printer status from the perspective of the printer. Shows print jobs
or list is empty. Also when out of paper
lpstat -o<spooler_name>
printer queue for ... No entries

Delete print job (HP UX)

# cancel job p0060517-1382 (printer name-job

number)

To check the functionality of a printer:

# lpstat -tp0060517

disable printer - Deactivating printer

enable printer - Activating printer

Start/stop spooler

The scheduler must be restarted when creating a new printer in versions up to HPUX 11.23.
This is no longer required from 11.31 ! Note: risk of malfunction. The printeradmin script
(see below) proceeds as per the OS level. HPUX version < 11.31 is no longer available at Germersheim.
# lpshut

# lpsched

Creating printers

Icon

In cluster systems the printer must be created on both systems.

Printers can be conveniently created using the /usr/local/sbin/printeradmin script.

Available on every HP-UX system.

Operating principle

Determines the OS version and (if necessary) stops the local scheduler
(lpshut, OS < HPUX 11.31)
If necessary, it determines the spooler name from the DNS name

Creates spooler

Script code

/usr/sbin/lpadmin \

-p$spooler_name \

-v/dev/null \

-mrmodel \

-ocmrcmodel \

-osmrsmodel \

-orm$printer_adress \

-orp$printer_port

echo

/usr/sbin/accept $spooler_name

echo

/usr/bin/enable $spooler_name

Starts the scheduler if it has been stopped previously (lpsched, HPUX < 11.31 only)
Creating VDS2 printers

Icon

In cluster systems the printer must be created on both nodes

Determine for which location the printer must be created. Must be visible from the ticket

Germersheim vds2g pvds2g degsp.corpintra.net

Woerth vds2w pvds2w1 dewoe.corpintra.net
Sindelfingen vds2s pvds2s de050.corpintra.net
Zwickau vds2z pvds2z ??
Integration vds2i pvds2i degsp.corpintra.net (integration in Germersheim)
LCs vds2? pvds2? degsp.corpintra.net ( LCs share the domain with Germersheim )

Connecting to the corresponding systems

For example: printer p50a0085 for VDS2 Sindelfingen

Ping and check name resolution
Create the printer even if both processes fail. New printers are only enabled upon installation
Note the IP domain for different locations.

# ssh pvds2s

# nslookup p50a0085.de050.corpintra.net

Last name: p50a0085.de050.corpintra.net

Address: 53.188.70.249

# ping p50a0085.de050.corpintra.net

64 bytes from 53.188.70.249: icmp_seq=0. time=17. ms

Creating printers

Parameter <FQDN> [ spoolername ]

spoolername is optional. Must be included if it differs from the DNS name

# printeradmin p50a0085.de050.corpintra.net

Last name: p50a0085.de050.corpintra.net

Address: 53.188.70.249

Create: p50a0085.de050.corpintra.net p50a0085 on LP1

destination "p50a0085" now accepting requests

printer "p50a0085" now enabled

If it has been created incorrectly (e.g. printer should have been created in pvds2g, but it is located
in Wörth [Ticket#99040964/0028223722 ]) the following solution is available:

/usr/local/sbin/chg_printer.sh p0060989 p0060989.dewoe.corpintra.net p0060989

Server creates an E-mail with information:
· From: root@obelix.degsp.corpintra.net [root@obelix.degsp.corpintra.net]
Sent: Friday, March 27th, 2015, 11:52
To: root@obelix.degsp.corpintra.net
Subject: Printer installation: p0060989 obelix

Install print queue: p0060989@p0060989.dewoe.corpintra.net

Delete print queue : p0060989
scheduler stopped
Delete old print queue: p0060989
Adding printer: p0060989 p0060989.dewoe.corpintra.net
Enable printer: p0060989
destination "p0060989" now accepting requests
printer "p0060989" now enabled
Start scheduler
scheduler is running

Printing via the print server

Print server Woerth swoep013
Spooler on this print server PWOE14074
Local spooler pwoe14074

# printeradmin swoep013.dewoe.corpintra.net pwoe14074 PWOE14074

=> Results in lpadmin -ppwoe14074 ...... -ormswoep013.dewoe.corpintra.net -orpPWOE14074

# lpstat -vpwoe14074

device for pwoe14074: /dev/null

remote to: PWOE14074 on swoep013.dewoe.corpintra.net

# lpstat -opwoe14074

printer queue for pwoe14074

Windows LPD server

Printer \\53.8.148.239\PWOE14074

Owner Status Job name Job ID Size Pages Priority

----------------------------------------------------------------------------

no entries

Creating printers using cron job

The spooler must be created at night on productive systems running HPUX < 11.31 to prevent malfunctions. There is a dedicated script for this
purpose which can also be used to delete a printer.
It is theoretically also possible to use the above script. The /usr/local/sbin/chg_printer.sh script is
also available on all systems and it is distributed there from SVN using remdist

Parameter
chg_printer.sh <spooler_name> <dns_name> [ <del_spooler> ]

cron entry (example)

For instance, spooler p261e091 is assigned a new address (by previously deleting it and creating
a new one)

Providing data on a spooler to be deleted is optional

03 04 * * * /usr/local/sbin/chg_printer.sh p261e091 p261e091.degsp.corpintra.net p261e091

Listing or deleting print jobs

Listing

# /usr/local/sbin/list_printjobs.pl p00640037

# /usr/local/sbin/list_printjobs.pl p00640037 -d <== delete

Available from HP-UX 11.23 without having to stop the spooler. However, the print queue
must be empty
Deleting (do not leave a space behind the parameter! )

# lpadmin -x<printer_name>