One thing you may not be considering when you set up journaling is whether or not the user who is creating the journal is authorized to allocate enough space to hold the journal receivers.
In our shop, we decided to journal our BPCS database files (a very large database) and everything went along fine until we received the following CPF message on a file update:
CPA7090: Entry not journaled to journal BPCSJRN in library BPCS-JRNLIB because of reason code 1.
The system message then provided an explanation of reason code 1.
1: The attached journal receiver does not have enough space for the entry because either the system, object, user profile, or group user profile storage limit has been exceeded.
What reason code 1 meant was that the user who created the journal did not have enough auxiliary storage assigned to him to store all the journal entries that were being written to the journal receiver. The amount of auxiliary storage is defined by the MAXSTG parameter in the user profile. When the MAXSTG parameter is exceeded (as it was when we were trying to write entries to a very large journal), an error message is displayed or sent to the job log, and the object is not created or updated.
We looked at the MAXSTG parameter for the user and found it was set to 6156KB. We used the Change User Profile (CHGUSRPRF) command to change it to *NOMAX and found we were able to write journal entries again.
The key here is that the MAXSTG of the user who creates the journal receiver must be changed to *NOMAX. It does not matter who is creating the journal entries-it's the person who creates the journal receiver that must have the space available. -Joe Hertvik
Editor's Note: If you find you cannot give MAXSTG(*NOMAX) to the owner of the journal receiver, you can also change the receiver's owner with the Change Object Owner (CHGOBJ-OWN) command, assigning ownership to a user profile that already has *NOMAX or to one that can be given *NOMAX without trouble.