RE: Journaling and contention

["Gary Monnier" <garymon@xxxxxxxxxxxxxxxxxx>]

A couple of things come to mind.  First, do any jobs do an exclusive object
allocation to the journal receiver, journal, or the library(ies) containing
them?  Are the journal and its receivers being backed up at the same time
your error occurred?

Second one that comes to mind is is some job changing the journal or its
receiver?  Is it possible a receiver reached its max and tried to generate
another at the same time some job was trying to gen another receiver also?

--
Gary Monnier               garymon@powertechgroup.com
The PowerTech Group        253.872.7788
PowerLock Network Security www.400security.com


-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Jim Damato
Sent: Friday, June 29, 2001 3:16 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: Journaling and contention


Unfortunately this job runs for about 14-18 hours and the critical lock
happens within a 2-3 minute period.

-----Original Message-----
From: Alexei Pytel [mailto:pytel@us.ibm.com]
Sent: Friday, June 29, 2001 11:49 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Journaling and contention



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

Try to catch the time when it happens and do a WRKOBJLCK on journal object
and on attached receiver object. This make give a clue, what's going on.


    Alexei Pytel






                    Jim Damato

                    <jdamato@dollargene       To:
MIDRANGE-L@midrange.com
                    ral.com>                  cc:

                    Sent by:                  Subject:     RE: Journaling
and contention
                    owner-midrange-l@mi

                    drange.com





                    06/29/2001 09:43 AM

                    Please respond to

                    MIDRANGE-L








> I would try making the receivers bigger.

Hmmm...
Right now the receiver's threshold is at 1919999 K, which is the maximum.
If I change the journal's receiver size option to *MAXOPT1 I can enlarge
the
receivers.  That option scares me though.  Each of the receiver size
options
(*MINFIXLEN, *RMVINTENT, *MAXOPT1) seems like it could help.  I just don't
know if they would require more processing and increase contention.

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 can't figure out which functions (deleting receivers,
adding receivers, hammering the journal with writes) might cause the lock,
and IBM has been no help.

Any thoughts on receiver size options or contention?

Much thanks...

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