Report held up

[SeanAIX430]

I've got a report that won't print because it tells me I have to wait for another user to finish printing the same report. Only problem is that user isn't logged in when I run a ps -u user it comes up with nothing, so I don't know how to cancel the report. She was running the report when I used shutdown to restart the server. Any ideas?

 

[KenCunningham]

If you know the name of the file, fuser <filename> might help identify the process, which you can then kill. HTH.

 

[KenCunningham]

Another thought - does the job show up in lpstat -o? If so, can it be cancelled?

 

[SeanAIX430]

I don't know the name of the report, and is there any difference adding -o to the end of lpstat? Either way I cannot find the print job or the report.

 

[sectorseveng]

If you rebooted the server whilst the print job was running there may be files left over in /var/spool/lpd/qdir that should be cleaned out. Check this and see if there are any files with a timestamp that matches the reboot time.

The other possibility is that these reports are handled by some application and there may be state files left lying around within the application that are preventing you from printing.

 

[SeanAIX430]

Thanks for the advice, but there wasn't a thing in the /var/spool/lpd/qdir directory. I have no idea what state files are or how to access and fix them to print the report. Please keep the advice coming. Thanks!

 

[sectorseveng]

Sean,

How are these reports created & printed?
Where are you seeing the error message saying that you cannot print this report (and what is the exact text of the message)?
Is the message from the AIX spooler or from an application?

If the reports are generated by an application then could well be state files (or flags set in a database) that tell the application that a print is already in progress. This could be what is preventing you from performing a print.