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



Fiona, Al, Bryan,

Thanks for your replies, I've made a few changes that you sugested and now
things are running much better.

thanks again 
Neil


-----Original Message-----
From: fiona.fitzgerald@notes.royalsun.com
[mailto:fiona.fitzgerald@notes.royalsun.com]
Sent: 15 August 2001 18:00
To: midrange-l@midrange.com
Subject: Re: suppress qsysopr message




We had the same issue some time ago, when there was a lot of activity on
the system.

I'd recommend increasing the size at which the receiver is changed,
considered full,
as this will reduce the frequency of messages.

wrkjrna  qrecovery/qdbjrn

Note the name of the current receiver - QDBJRN5068 for example.
Take option 8 against the attached receiver.

Look at the Threshold - probably 5000, or smaller.

Now
CRTJRNRCV JRNRCV(QRECOVERY/QDBJRN5069)
          THRESHOLD(10000)

If it's already gone up, repeat the command with QDBJRN5070, 71, etc until
you create one.

Then change the journal to use the bigger receiver;

CHGJRN JRN(QRECOVERY/QDBJRN)
       JRNRCV(QRECOVERY/QDBJRN5069)  <- or 70, 71, whatever worked.
       MNGRCV(*SYSTEM)

Fiona

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@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.