RE: Journaling and contention -- MIDRANGE-L


Look at the priority of a system job, which manages receiver. Make sure
that it's higher than priority of your writer jobs.
I am not sure if you can change priority of this particular job, but
CHGSYSJOB command can change some of them.
In general, try to understand what makes system job run slow - it should do
it's job pretty fast.
Do you have enough memory in a machine pool ? Look at disk unit utilization
- it may be overloaded.

    Alexei Pytel

"The better is the worst enemy of the good"




                                                                                
                   
                    Jim Damato                                                  
                   
                    <jdamato@dollargene       To:     
"'MIDRANGE-L@midrange.com'"                  
                    ral.com>                   <MIDRANGE-L@midrange.com>        
                   
                    Sent by:                  cc:                               
                   
                    owner-midrange-l@mi       Subject:     RE: Journaling and 
contention           
                    drange.com                                                  
                   
                                                                                
                   
                                                                                
                   
                    06/29/2001 05:54 PM                                         
                   
                    Please respond to                                           
                   
                    MIDRANGE-L                                                  
                   
                                                                                
                   
                                                                                
                   



Much thanks to Buck and Alexei for helpful replies.

We've dug into this one deeper and discovered that on two occasions we've
received the "CPA7090  Entry not journaled to journal IPBLK in MRCARC. (C
R)
" message WITHOUT the preceding "CPI70E5  Journal or journal receiver not
available" message.

It seems like this means that the jobs are filling up the journal receiver
so fast that system cannot create a new receiver quickly enough.  The new
receiver is created after one or two jobs bomb because the current/old
receiver has run out of space.

Now my course of action seems to be:  1)  Try Buck's suggestion of giving
the history table its own journal.  2)  Put the journals and receivers in
their own pool -- contention between the journals and the data could be
preventing the receivers from being created quickly enough.  3)  Reduce the
number of concurrent batch streams writing to the history file.

I continue to dig into this.  I wonder if I've misinterpreted the
situation.
It seems weird that my journaled batch jobs could get ahead of the system
managed journal receivers.  Any opinions?

-Jim

James Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.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
+---