RE: Journaling and contention

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

Jim D wrote:
>Part of my difficulty is that I can't figure out what's causing 
>the "CPI70E5 Journal or journal receiver not available" 
>message that starts this whole problem.  At the point in 
>time where the system is supposed to add a receiver 
>it is unable to access the journal to determine if 
>receivers are system generated.

I have never seen this error, but reading the text indicates a second
possible reason:
"...be managed by the system, or from  attaching new journal receivers to
the journal at this time..."  I'm presuming that you've done WRKOBJLCK on
the *JRN and the *JRNRCV objects.  Which one is locked?  Is it a QDBSRVx job
that's locking the object?  Does a manual CHGJRN work?  

Your history file must have a huge record size to burn up a 2Gb *JRNRCV
every 1-2 minutes - I don't envy you there.  One idea sprang to mind: are
other files being journaled to this *JRN?  I'm thinking of anything that
would reduce the traffic to this *JRN and associated receivers.  Is this a
strange case of the batch jobs having too high a RUNPTY compared to the
QDBSRVx jobs?  

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