Re: CPF4328 Member CACUB3CUP not journaled to journal *N.

Hi, Glenn:

Perhaps you inadvertently have a "COMMIT" keyword on the F-spec in the RPGLE source?

Or, perhaps you compiled with CRTSQLRPGI and forgot to specify COMMIT(*NONE) on that command? This is a good reason to use Alan Campin's COMPILE command to embed such compile parameters in the source, so they are never forgotten. See: http://www.think400.dk/downloads.htm for that tool.

HTH,

Mark

> Glenn Gundermann wrote:

Hi everyone,

This is crazy. I've had this error before and I fixed it at the time. Now I can't remember what I did. I've searched the archives and found
nothing relevant. Same for Google. So I'm hoping someone here can help.

This is in regards to an RPGLE program and I do not have any imbedded SQL.

I have two tables, created using RUNSQLSTM ...etc.
CACUB3CUP - customers
CACUB3EMP - employees of the customers

They are not journalled, nor will they be in the future.

EMP has a foreign key constraint to the parent file CUP, based on the
customer code. Do I have to remove this constraint?

I have an RPGLE program that maintains these two files, hence it opens
them for update. Or at least it tries. I get the following error
message:

CPF4328

Message . . . . : Member CACUB3CUP not journaled to journal *N.

Cause . . . . . : Member CACUB3CUP file CACUB3CUP in library CAGLENN is
not journaled to journal *N in library *N for commitment definition
QDBCMTDFN. The journal specified is used by commitment definition
QDBCMTDFN. If *N is specified for the journal, the file is not journaled.
If the file is a logical file, all based-on physical files may not be
journaled to the same journal as required by commitment control.

Recovery . . . : Ensure the file being opened is journaled. For logical
files, make sure that the based-on physical files are journaled to the
same journal.

Technical description . . . . . . . . : The commitment definition
identifier is X'1001010000000005B505'.