Re: Can't inhibit message logging.

   A copy of quick ideas. First, put a break message handling program on 
the submitting job, and simply remove the comp messages as they arrive. 
Second, why is this thing designed this way, it sounds like it would be
much more efficent to have the submitted job wait on an event, dataq, 
msgq, or dlyjob rather than supporting the 8640 +/- jobs in the system 
created if this thing runs 24 * 7. 

        JMS 

On Fri, 5 Jun 1998, Erick wrote:

> I have a client who runs a CL program that submits a job to a user
> defined subsystem. The job then runs every 10 seconds. Even though the
> job is submitted qualified as MSGQ(*NONE) and job logging is set for
> *NONE, a message complete is still being generated. Since this job runs
> continuously, the message job queue fills up and ends the job. He also
> has a specific class and job description for the SBMJOB. Is there an
> presidence here that I don't understand?
> 
> I had suggested ti the client that changing the system value QJOBMSGQFL
> to *WRAP would alleviate the problem. He does not want to do this.
> 
> Thank you in advance for any advice in this matter?
> 
> Erick
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@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 is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---