× 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.


  • Subject: RE: Can't inhibit message logging.
  • From: Bob Crothers <bcrothers@xxxxxxxxxxxxx>
  • Date: Sun, 7 Jun 1998 09:20:34 -0500

I agree, a redesign is called for.

However, if that can not or will not be done, then change the 
JOBMSGQFL on the Jobd to *WRAP.  This will do the same thing as 
changing the system value, but will only be for that job.  This 
is parm is availible on the JOBD as of V3R1.

Bob

-----Original Message-----
From:   Jeffrey M. Silberberg [SMTP:silbrbrg@netcom.com]
Sent:   Saturday, June 06, 1998 3:57 PM
To:     Erick
Cc:     Midrange List
Subject:        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
+---

+---
| 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
+---


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.