Re: V5R1 question - CPF4238 & SQL7008

Dennis

I thinks there is a change in commitment control settings - something
called autocommit, IIRC. This is a PTF that references the same message

SI02901 2134 02/15/02 OSP-DB-MSGSQL0428 RUNNING WITH AUTOCOMMIT SI04944 DQ

This seems to apply to ODBC in the main, but it affects other things too -
I don't know all the implications.

Vern

At 11:00 AM 9/30/02 -0500, you wrote:

AS/400 720 running V5R1 since Labor Day weekend & current with "all" ptf's
at that time.

Ran a "test" of the month-end process on the machine & I got a
escape/diagnostic message that does not make sense.  First CPF4238 (Sev
50/Escape) "Member ILI not journaled to journal *N" which was followed by
SQL7008 (Sev 30/Diagnostic) "ILI in BPCSF not valid for operation" with
reason code 3 "ILI not journaled, or no authority to the journal.  Files
with an RI constraint action of CASCADE, SET NULL, or SET DEFAULT must be
journaled to the same journal."

Did a DSPFD on the file & it shows number of constraints as zero (-0-) & the
file is not being journaled.  So what is causing these messages to occur?
The program seemed to run correctly & the report generated was what I was
expecting.  There are eight files referenced by this program & all eight got
the same two messages & all eight have no constraints & they are not
journaled.

Thanks - Dennis.

Dennis Munro