• Subject: RE: Bug w/ Ping command?
  • From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
  • Date: Fri, 26 Dec 1997 22:01:50 -0600 (CST)

If your monitor job is a "NEP" (Never Ending Program) that just does
continuous monitoring, you -could- make your program count the number of
times it does its thing, and re-submit itself to the jobq, then quit.

It's not a fix, but a usable workaround.  (We've done similar things to keep
job logs from growing too large).

--Paul E Musselman


At 02:49 PM 12/22/97 -0500, you wrote:
>After finally finding the QGY* APIs in the QGY library (thanks Bruce) I can
>confirm your problem of QGYRPRTA leaking memory. In my case I'm loosing 16K
>per call, not 20. However, I'm running V4R1, you? Have you contacted IBM? If
>so, what did they say?
>-----Original Message-----
>From: mcsnet!midrange.com!midrange-l-owner@Mcs.Net
>[mailto:mcsnet!midrange.com!midrange-l-owner@Mcs.Net]On Behalf Of
>Leland, David
>Sent: Friday, December 12, 1997 3:05 PM
>To: 'MIDRANGE-L@midrange.com'
>Subject: RE: Bug w/ Ping command?
>Well, I discovered that there is not a bug w/ the PING command. It's
>just fine.  However, I did discover what was eating up my "Temporary
>storage".  It is the API QGYRPRTA in library QGY which I use to retrieve
>the status of a printer.  Everytime I call this API it adds 20 to my
>"Temporary storage used" for my job.
>Attachment Converted: c:\eudora\attach\winmail.dat

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].