Maximum size of a journal receiver is 1TB. I think that's what *NONE really
means in your case. Hopefully you didn't hit this limit :)
If you did, you might think about changing the journal to *SYSTEM managed.
HTH, Elvis
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzamp/rzampjourn
al.htm#rzampjournal
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: RE: CPF7091 - space for entry cannot be allocated on journal
receiver
Sharon,
We have lots of disk and the journal receiver threshold is *NONE so, in my
mind
at least, the system shouldn't bother the operator with picayune details
like
this error message. That's why I'm wondering if there is something about
*NONE
that I don't understand. Is there some other system default that overrides
the
*NONE? The CHGJRN occurs at least once each day during the dayend and
sometimes
more frequestly.
Thanks for the reply. JK
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.