Re: print subsystem errors



Could this be a PATH or LIBPATH problem? Is this printer PCL or
PostScript?



If it is PostScript, the "-z 1" flag will be translated to an option for
the "enscript" program. Maybe there is a different version of (or
wrapper for) enscript installed that is incompatible with the AIX print
spooler.



The other problem I had was when Microsoft Word changed a hyphen to a
dash and some one cut and pasted a command from mail note into a script
file. Try retyping the command in the script.



Some commands that might be useful for trouble shooting are:



$ lsque -q'print_que'

PRINT_QUE:

device = @print_quedev

host = print_server.domain

rq = remote_print_que

s_statfilter = /usr/lib/lpd/bsdshort

l_statfilter = /usr/lib/lpd/bsdlong

$ lsquedev -q'print_que -d'@print_quedev'

@print_quedev:

header = never

trailer = never

access = both

backend = /usr/lib/lpd/pio/etc/piorlfb -f ! -T60

$ lsvirprt

An interactive menu...



Or

$ lsvirprt -q'print_que -d'@print_quedev' | more

.... A whole bunch of stuff that is normally just confusing. ....



$ type enscript

enscript is hashed (/usr/bin/enscript)

$ lslpp -w /usr/bin/enscript

File Fileset Type


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

/usr/bin/enscript bos.txt.ts File

$ lslpp -l bos.txt.ts

Fileset Level State Description


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

Path: /usr/lib/objrepos

bos.txt.ts 5.3.0.40 COMMITTED TranScript Tools

$ rpm -q enscript

...(not sure of the exact output since I don't have GNU enscript
installed from the IBM Linux Toolbox).



Edward Davignon <mailto:Edward.Davignon@xxxxxxxxxxxxxx>
Lead Analyst - Distributed Systems
Utility Shared Services - IT
Energy East Corporation



________________________________

From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Christina Lewis
Sent: Thursday, December 07, 2006 11:12 AM
To: aix-l@xxxxxxxxxxxxx
Subject: print subsystem errors




I am looking for ideas on where a problem might be...
I have an application that executes a shell script to print jobs.

Periodically (not every time) the print subsystem throws out this
message

Message from queueing system:
=====> MESSAGE FROM PRINT JOB 187870 (report-name)
0782-006 -z flag not supported for the print file type, printer
language,
and printer type selected for the print job. Check the flags.
<EOT>


I can take the same command issued in the shell script; and issue it on
command line - using the exact same report and printer
that previoulsy got the above error.. and it prints everytime with no
message.

The command:

qprt -c -w 132 -p 12 -P print_que -z 1 print_file_name


Any ideas on why this message randomly occurs when the shell script is
used, but not when command line is used?



-------------------------------------------------------------------
Christina (Tina) Lewis
Navy Exchange Service Command (NEXCOM)
UNIX System's Administrator
Desk: 757-631-3331
Email: Christina_Lewis@xxxxxxxxxx
--------------------------------------------------------------------

************************************************************************
******

ATTENTION ATTENTION ATTENTION ATTENTION ATTENTION

Our domain name is changing. Please take note of the sender's

e-Mail address and make changes to your personal address list,

if needed. Both domains will continue to work, only for a limited

time.

************************************************************************
******

This email and any files transmitted with it are intended solely for

the use of the individual or agency to whom they are addressed.

If you have received this email in error please notify the Navy

Exchange Service Command e-mail administrator. This footnote

also confirms that this email message has been scanned for the

presence of computer viruses.



Thank You!

************************************************************************
******





Relevant Pages

  • print subsystem errors
    ... I have an application that executes a shell script to print jobs. ... I can take the same command issued in the shell script; ... ATTENTION ATTENTION ATTENTION ATTENTION ATTENTION ...
    (AIX-L)
  • Re: despair
    ... I once tried to write a cd program in Unix. ... Just putting a cd command in a script and then ... hell are you supposed to write shell script macros to run a frequently ... make "$ FOO BAR" a meaningful DCL command. ...
    (comp.os.vms)
  • [Full-Disclosure] MDKSA-2005:033 - Updated enscript packages fix multiple vulnerabilities
    ... A vulnerability in the enscript program's handling of the epsf command ... executing enscript with carefully crafted command-line arguments. ... the GPG public key of the Mandrakelinux Security Team by executing: ...
    (Full-Disclosure)
  • Re: cron and command quote
    ... if you are going to be using a shell script you have to make sure that it exits properly. ... So, '||' is just as legal as '&&' and would do just as it does on the command line, assuming of course there is nothing found by the grep. ... with && we have execute command1 if it returns true execute command2 ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: Oracle dbi ?
    ... Can you execute a command line ... > shell script using OCI? ... Not using OCI, but Perl can run SQL*Plus very nicely. ...
    (perl.dbi.users)