As I understand it, in Unix to cancel a print request there is a command "cancel <request-id>" where reqeuet id is the id returned from lpstat -t.
e.g. lpstat -t o/p is :

prt_zeb1 accepting requests since Mar 14 15:28

printer prt_zeb1 now printing prt_zeb1-82. enabled since Apr 13 14:50 fence priority : 0
prt_zeb1-82 mfor priority 0 Apr 14 13:15 on prt_zebra1 fileout 25953 bytes



When I am trying to cancel a queue and I get the message :
request "prt_zebra1-108" non-existent

Also, when I am trying to print through SAM, I am getting the same message.


Any suggestions of how do i remove such a queue?

a. From your inputs, your cancel command should have been:

cancel prt_zeb1-82

[There is no such request ID such as 'prt_zebra1-108' in the queue.]

b. If there was indeed a report 'prt_zeb1-108' being printed, the situation can been explained as follows:
i.: You are typing in a wrong request ID.
or
ii.:
- The size of the report is too small.
- Between the time you run the lpstat -t command to get the request ID and actually issue the cancel command, the whole thing is out of control of the UNIX system and is sitting in the Zebra Printers own buffer.
- Therefore, you get the message that there is no such request.

Thanks BS.

i noted the request-ids wrongly.

lpstat -t gives me:

prt_zebra1-82 mfor priority 0 Apr 21 15:49 on prt_zebra1 fileout 25953 bytes

to cancel the queue I am giving the command :
cancel prt_zebra1-82

Here I am getting the message:
cancel: request "prt_zebra1-82" non-existent.

I get the same message if I am using SAM to cancel the queue.

Also, I have switched "OFF" my zebra printer so that anything in the zebra printer buffer is clear.

Any suggestions ??

I am not a UNIX 'guru' and this definitely is heading that way.

This may be stupid, but I do suppose you are running SAM as root login and not doing an 'su'. The last time I was dabbling in 'lp' and 'cancel' and their 'relatives', they were bit fussy about 'ownership' of the print requests, except when you were logged in as 'root' (I mean, really logged in as 'root').


Other than that, I think you may need help from someone more qualified than me right now. :(

Hi,

The command i'm using on UNIX as root is:

For all jobs for a printer:
qcan -P<printername>

or

for a specific job for a printer:
qcan -P<printername> -x<jobnr. in the queue>

p.e. qcan -PP120001 -x150

If you do on UNIX the command qcan -?, you will see some info.

Rgrds,

GN

forsms, what kind of printer is your zebra printer? Is it set up as a remote or network printer? Check the /var/spool/lp/request subdirectory for your zebra printers and see if there any data and/or control files left. You could try by deleting any of these. Also try to stop and restart the lpsched process. Worst case would be to do a lp spooler kick.

Thanks for ur inputs !!!

The zebra printer is a normal(but ver old :) ) label printer.and is set up as a network printer and networked through UNIX.

I have removed all the files in /var/spool/lp/request/prt_zebra1 directory; but still when I have given a fresh set of labels to be printed, it is still printing the leftover stuff of last queue.


lpshut can be used to shutdown the printer; but how to restart?

what is "lp spooler kick "????

i know there is a lot of question and appreciate the contributions being made..

Thanks.

1) Try deleting/recreating the queue but that will probably fail due to pending requests in the spooler

2) Restarting the LP scheduler: lpsched -v

3) LP spooler kick: I have to lookup the correct procedure but it's something you should try as a LAST RESORT. If it goes wrong, you will be at the mercy of HP Support :)

Did you check all LP log files?:
/var/adm/lp/log
/var/adm/lp/lpd.log
/opt/hpnp/tmp/*