Re: HPPJLDRV vs IBMSNMPDRV

Group PTF, Gee, just might be .....

I downloaded it. Looked at the symptom strings. SI40835 was the only PTF that had something in the symptom string that >might< be involved. Couldn't tell for sure. If I bring it up to my boss (boss of sa as well), he will ask, and also send me to the sa, I am sorely tempted to apply that PTF. I didn't get any grief when I applied PTFs suggested by Scott Klement for QSH error handling. Just don't know if there is a magic point beyond which I get the sa "ticked off". All too easy to do without trying. Unbelievable that he still works there.

John McKee


-----Original message-----
From: DrFranken midrange@xxxxxxxxxxxx
Date: Fri, 29 Jul 2011 19:22:00 -0500
To: midrange-l@xxxxxxxxxxxx
Subject: Re: HPPJLDRV vs IBMSNMPDRV

SF99347 is likely to be helpful though I can't say specifically why. :-)

- Larry "DrFranken" Bolhuis

On 7/29/2011 8:03 PM, John McKee wrote:

I had been converting the driver program used for Lexmark printers from HPPJLDRV to IBMSNMPDRV. Seemed a lot better and a lot more tolerant of printer issues.

Until a few days ago with one printer.

The writer for this printer just ends abnormally. When it does, all the spool files in the queue get put on HOLD status.

I was told to change the driver back to PJL.

Questions:

Anybody have any idea why this one writer/printer combination is unstable?

Thoughts about why the joblog has nothing useful in it? Time I see this happening, the job has already ended. If I had had time, I would have changed the message logging level.

Any idea why spool files get forced to HOLD, and how to stop that?

We are marooned at v5r4, woefully behind on PTFs (sa can't be "bothered").

I have limited access to IBM. Any PTFs that might address this issue?

John McKee

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.