Behalf Of johnking@xxxxxxxxxxx: Thursday, September 04, 2008 2:37 PM
You may have reached the limit as to the size of the journal receiver.
If you issue the CHGJRN command and allow it to generate a new receiver
you should be okay.
You should schedule the receivers to be changed on some timetable you
From: midrange-l-bounces@xxxxxxxxxxxx[firstname.lastname@example.org] On
nge-l@xxxxxxxxxxxxxxxxxxx: CPF7091 - space for entry cannot be allocated on journal
A program that has run flawlessly for years blew up today with a
not journaled to journal ORDJRN. Reason code 1. -- Space for entry
allocated on journal receiver."
This *JRN is used as an audit journal from which we harvest 'from-to'
made to our customer's standing merchandise orders. Yesterday I added
anadditional PF to the journal, so I certainly believe that there are
in the receiver - lots more entries. What I can't figure out is _why_
is complaining about them.
I've investigated the suggestions on the CPF7091 and the accompanying
and they show the following:
1) The journal receiver threshold = *NONE
2) The journal's owner max storage = *NOMAX
3) Disk utilization is 48%.
Perhaps there is something I don't understand about *NONE and *NOMAX?
has been here before I'd sure appreciate a suggestion!
Many thanks, JK