qcan, qchk, lpr and qprt are all front-ends to enq.  enscript also calls
enq, but only after it prepares a flat file to postscript.

-----------------------------------------------------------------------------
To print a flat ascii file on Tom's printer, (P)4019tee, which Tom has set up 
as a postscript printer (i.e. no ascii queue), use enscript like so.
       enscript -d 4019tee file_name

Or to get fancier,
       enscript -r -fCourier-Bold8 -B -n5 /afs/d/u/jasper/aixnotes/servers
-r = Rotate (i.e. Landscape mode)
-f = Font,
-B = Don't print headers,
-n = Number of copies

-----------------------------------------------------------------------------
To print a postscript file, qprt -c -P printer_name file_name.
For example, when I printed off the latest NIM guide, I typed
           qprt -c -P psua /afs/austin/u1/jkennedy/23262703.ps

-----------------------------------------------------------------------------
Rick's printer is a 4019, defined on my machine as queue 4019ech.

On Rick's machine, it's queue ps, attached to device lp0.
To query it, enq -q since he's got the ps queue set up as the system default.
or lpq -P4029c1a for example.

To start, qadm -U ps (the U says to bring it up).

-----------------------------------------------------------------------------
To print from Mosiac, From the File pull-down, select Print... and if you want
to print to the UA printer instead of ech, add <-P psua> to the lpr command.
Also change the "Format for printed document:" to PostScript.

-----------------------------------------------------------------------------
Print queue definitions are kept in /etc/qconfig, with the first stanza being
the system default.  With the new (9/95) customize, there's now a cron job
calling /afs/alm/ais/printers/bin/Remoteprinters to keep the /etc/qconfig
file current.

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

For locally-attached printers, host systems need to have the lpd daemon up
and running (src-controlled) and remote hosts defined in /etc/hosts.lpd file.
For ALMVMA, by the way, you need to define almvma1.sanjose.ibm.com
                                       and almvma2.sanjose.ibm.com
                  as well as (I think)         vma.almaden.ibm.com.
You can just edit /etc/host.lpd or find it in smitty buried under
  Communications Applications and Services
  TCP/IP
  Further Configuration
  Remote Printer Subsystem
  Server Services
  Host Access for Printing
  Add a Remote Host         
which by the way, uses the ruser -a -p 'hostname-you're-adding' command,
but the easiest way, is to simply ruser -a -p+ to authorize everybody.
The ruser command updates/changes the /etc/hosts.lpd file.
-----------------------------------------------------------------------------

What I had to do to get my printer (P4029RAJ) defined.

  - Physically connect it to the parallel port (duh!).

  - Add the device support to AIX with the following 2 commands,
        nimclient -o allocate -a lpp_source=lpp-414
    and nimclient -o cust -a filesets=printers.ibm4029.rte

  - smitty mkvirprt (aka mkpq - mkvirprt is the AIX 3.2 fast path name)
    Selected "local                Printer Attached to Local Host"
             "IBM"
             "ibm4029      IBM 4029 LaserPrinter"
             "parallel"
             "ppa0 Available 00-00-0P Standard I/O Parallel Port Adapter"
    Specified the four print queue names, ascii, gl, pcl, & ps.  Just took
    the defaults for the other stuff.  This did a /usr/lib/lpd/pio/etc/piomkpq
    command (whatever the heck that is).
             
  - Fill out the web form at http://w3/ais/forms, under "Printer definition request".
    Once Rosa puts that in the Almaden common printer definition tables, it'll appear
    on the VM list of printers available, as well as the AIX common qconfig, which is
    /afs/.almaden.ibm.com/ais/printers/qconfig.all.  You can manually run the program
    that cron runs to update your own /etc/qconfig.  You may have to use the -force
    option if the dates are such that the program doesn't think it needs updating.
         /afs/alm/ais/printers/bin/Remoteprinters -force
    
  - Added a few hosts that I wanted to be able to print from to /etc/hosts.lpd,
    including vma-red.almaden.ibm.com.

  - Get the lpd up and running.  You can edit /etc/rc.tcpip and uncommented the 
    starting up of the lpd daemon yourself, or use the undocumented command
         chrctcp -a lpd
    to do it.  I also started lpd up myself manually for the first time.
         lpd
    You can do the same thing through smitty, but it looks like smitty wants to 
    start lpd via /etc/inittab, 'cause I see the /usr/sbin/piomisc_base program 
    that smitty calls, does a /usr/sbin/mkitab 'lpd:2:once:/usr/bin/startsrc -s lpd'.
    So, I guess there's more than one way to skin a cat.

========================================================================================

Here's the clauses I removed from my AIX machine's /etc/qconfig file after disconnecting
my 4029 printer from jasper,

ps:
        device = lp0
lp0:
        file = /dev/lp0
        header = never
        trailer = never
        access = both
        backend = /usr/lib/lpd/piobe
ascii:
        device = lp0
lp0:
        file = /dev/lp0
        header = never
        trailer = never
        access = both
        backend = /usr/lib/lpd/piobe
gl:
        device = lp0
lp0:
        file = /dev/lp0
        header = never
        trailer = never
        access = both
        backend = /usr/lib/lpd/piobe
pcl:
        device = lp0
lp0:
        file = /dev/lp0
        header = never
        trailer = never
        access = both
        backend = /usr/lib/lpd/piobe