Listing printer drivers

[OFC_EDM]

A DBA at my company wants to know if the following printer drivers are installed, identically, on 2 of our servers.

All I can tell him is that the generic HP Laserjet model script is on both systems.

How can I report on the more detailed level stuff such as LANDSCAPEHPLJ4. (See table below)


Printer
Type: HPLJ
Description: Generic HP Laser Printer 4 or greater

Style Driver Name
=============== =====================
A4 PORTRAITHPLJ4
DYNAMIC PORTRAITHPLJ4
DYNAMICPORTRAIT DYNAMICPORTRAITHPLJ4
LANDSCAPE LANDSCAPEHPLJ4
LANDWIDE LANDWIDEHPLJ4
PORTRAIT PORTRAITHPLJ4
PORTRAITLASERCHECK PORTRAITHPLJ4LASCHECK

[Raj D.]

Hi Kevin ,
Generic driver will work for that, Try using the printer through Jetadmin,

check :

/opt/hpnpl/bin/addqueue -l for the printer driver.

1003) LaserJet 4L net_lj4x , hope this will work ..

Cheers,
Raj.

[Bill Hassell]

The chart shown is from the database and meaningless to HP-UX. Like any SysV version of Unix, there are no printer drivers at all, just simple printer scripts that can prepend escape codes to the print job.

The generic laserjet script found in the choices for adding a local (parallel or serial port) printer is for long-obsolete printers such as the LaserJet classic, and I, II and III. While it will work just fine for more recent printers, you do not match unrelated info from the database with the printer's script. Instead, you add the printer according to it's interface (local, remote - on another computer, and network - HP JetDirect only).

Then you send the DBA back to the database vendor to find out how to specify the right options for the lp command. The LaserJet series 4 has been obsolete for many years and you probably don't have one on your system. What is more important is the printer language (PCL or Postscript) and how to specify options in the database config file.

[TwoProc · Accepted solution]

Those the drivers from Oracle Apps.

Your answer about telling him about the generic HP Laserject model script is on both systems is correct. You could just do diff on the two to be absolutely sure.

You could lastly diff each individual printer driver(script) on each server.

The individual script (which is copied from the model original) is in /var/spool/lp/interface/[printer_name]

You could get a copy of the two scripts together on the same machine and diff them.

The rest of the differences would lay in the definitions inside of each Oracle database.

He/she should be also examining the contents of "SRW Driver" field in the "Print Styles" form(for each of the above Style Driver Names above), that points to a file in the APPL_TOP that could be checked to see if they are the same in each APPL_TOP.

He/she should be also examining the "Arguments", "Initialization", and "Reset" fields of the "Printer Drivers" form for each of the above "Style Driver Names" above on each database to make sure that they are exactly the same also.

[OFC_EDM]

Thanks everyone for the replies.

I used the addqueue -l command to list all printers, their model and model script.

But it lists them my Printer ID and not the logical name.

If I have a printer called "cheque" how would I find it's numeric printer ID? I couldn't see anything in SAM either.

[TwoProc]

That ID number doesn't appear to be a number that corresponds to *A* printer (I know - that header is awfully misleading). That looks to me to be just a unique id for the /opt/hpnpl/admin/PrinterList file that matches a script in /opt/hpnpl/admin/printers/ directory. It looks to me that those scripts tie the peripheral types to the model scripts.

[OFC_EDM]

Thanks.

This was easier than expected to resolve I simply compared the following scripts on the two servers using diff.

/etc/lp/interface/cheque
/etc/lp/cinterface/cheque
/etc/lp/interface/cheque
/etc/lp/member/cheque
/etc/lp/sinterface/cheque

There were 0 differences. So I told the DBA the issue must be in the Oracle printer definition. They seemed happy. So my issue is over.

Thanks for the help.

Hopefully there isn't anything else I should have checked to ensure it isn't a UNIX OS printer setup issue. :)

[OFC_EDM]

.