ITEM: DF1672L

Cannot print postscript and pcl to one queue at 4.1.5

ENV:
        AIX 4.1.5.0
        Model F40 and 59H
        HP LaserJet 5Si attached via JetDirect card

PROBLEM: A queue on 59H can print ps and pcl with the same queue. queue
on f40 cannot do ps, only pcl. both systems are 4.1.5 and using hplj-5si
colon file. 

*ACTION TAKEN:

\#lslpp -l printers.* | grep hplj-5
  printers.hplj-5si.rte      4.1.5.0  COMMITTED  Hewlett-Packard LaserJet 5si 
same output on both

On 59H:
\#lslpp -l bos.rte.printers
  Fileset                      Level  State      Description         
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.rte.printers           4.1.5.0  COMMITTED  Front End Printer Support

Path: /etc/objrepos
  bos.rte.printers           4.1.3.0  COMMITTED  Front End Printer Support

On f40:
\#lslpp -l bos.rte.printers
  Fileset                      Level  State      Description         
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.rte.printers           4.1.5.0  COMMITTED  Front End Printer Support

Path: /etc/objrepos
  bos.rte.printers           4.1.5.0  COMMITTED  Front End Printer Support

\#lslpp -l printers.rte
  Fileset                      Level  State      Description         
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  printers.rte               4.2.1.0  COMMITTED  Printer Backend 

Path: /etc/objrepos
  printers.rte               4.2.1.0  COMMITTED  Printer Backend 
same output on both machines.

tried copying qconfig entry and virtual printer file from 59H to f40.
touched device file for the queue in /var/spool/lpd/pio/@local/dev

\#cd /var/spool/lpd/pio/@local/custom
\#chvirprt -q \ -d \
get an error here. AIX will not let us do it.

Tried to make a change to the queue in smit and it failed too.
replaced old qconfig file since we had made a backup copy.
remove device file and virtual printer file.

remove and readd queue through smit on f40.
did not work.

Changed on the f40 virtual printer attributes (with lsvirprt):
mi=a,s
mp=,%%!

the postscript file printed as the postscript source and not translated.
checked ia, is, sD, and d attributes. Same on both systems.

\#lslpp -l bos.txt.tfs
4.1.5.0 on both systems
\#lslpp -l bos.txt.ts
4.1.5.0 on both systems

no full filesystems on the f40.

If Jessie prints /usr/lib/lpd/pio/burst/H.ps to the queue on the f40 it
will not work. It will work from the 59H.
If Jessie enscripts a text file it will work on the 59H but not on 
the f40.

setup a queue that prints to a file on the f40.
\#touch /dev/jessietst
make a queue that prints to this file.
turn auto-sensing on.

the beginning of the file begins with: \^[%-12345
The printer does not know it is a postscript file because it does not
begin with %!.

tried printing the /usr/lib/lpd/pio/burst/H.ps file to queue that prints
to a file and it began the same way.

setup a remote queue using standard processing from the f40 to the 59H.
enscripting a text file to the remote queue on the f40 and it printed in
postscript.

*ACTION TAKEN:
        smit mkpq
                Created a PostScript JetDirect queue

        smit chpq
                Set auto-detect to yes

        Sent a PostScript and an ASCII file and both printed.

        You created a PostScript queue and could print both PCL 
        and PostScript to it - but you didn't have some of the
        abilities you needed for PCL (such as changing _w width
        attribute).

        You removed the PostScript queue and created a PCL queue.
        Then set it to "post script option installed = yes" in
        SMIT.  Sending PCL jobs to this queue worked, but when  
        a PostScript job was sent to the queue, you received a
        message on the console "No PostScript queue."

        We added a new PostScript queue and send a job to the PCL
        queue and it printed fine.  This is what appears to be
        going on:

        CREATE A POSTSCRIPT QUEUE
          1. Send a PostScript job - just prints it
          2. Send a PCL job - enscripts the job

        CREATE A PCL QUEUE
          1. Send a PCL job - just prints it
          2. Send a PostScript job - looks for ANOTHER PostScript 
             queue to the same device and routes the job there.

        So, even though you are going to send both PCL and PostScript
        jobs to a single (PCL) queue - a second PostScript queue MUST
        EXIST!



Support Line: Cannot print postscript and pcl to one queue at 4.1.5 ITEM: DF1672L

Dated: July 1997 Category: N/A

This HTML file was generated 99/06/24~13:30:16

Comments or suggestions?
Contact us