× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello everyone,

This came to my attention last Friday, as I was debugging a job via service
entry point. The job is a batch job. Once I got past the debug stage I
ended the debug session, and deleted my SEP in RDi (V9.1.1). This was at
approximately 9:30 am, but I let the job in batch continue to run. Later in
the day I was informed that there were numerous entries in QSYSOPR with
this same message:

Job message queue for 203562/QUSER/QZRCSRVS has been wrapped.

Looking at the job log I determined these were related to the debug job I
was running earlier that morning.

So since it was around 4:00 pm I didn't want this activity to continue
throughout the weekend I simply ended the QUSER job and the logging stopped.

However I also went to debug another job and saw a similar message on
QSYSOPR for the new debug job, and out of curiosity I shut down my RDi
client and the QUSER job ended.

So I guess my questions are 1) why did the QUSER job continue to write to
the job message queue after I stopped debugging the initial program? and;
2) is there anyway to control that logging?

I often leave RDi open but minimized when I go home for the eventing but
now I'm wondering if I need to shut it down when I'm not actively using it,
just as insurance against all this logging to a message queue?

Thought, comments anyone?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.