Test environment – stop iSeries journaling – how to get past hard errors?

Tags:
iSeries
SQL
We have stopped journaling on our test system (library driven). How can we get around the CPF4328 error - "Member (FILE) not journaled to journal *N'?
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheRealRaven
    There are two general ways to stop the error from happening.
    1. Start journaling.
    2. Stop performing actions that require journalling, e.g., don't attempt to use commitment control.
    There is no way to "get around" it.
    34,465 pointsBadges:
    report
  • ItsHerAgain
    Even with the program compiled commitment control (*None). I get the same CPF4328 - the table causing the issue has a DLTRule of *Cascade with a UdpRule of *Restrict. Thanks for your help!
    30 pointsBadges:
    report
  • TheRealRaven
    Commitment control was just one "e.g." There are others, e.g., delete/cascade/restrict rules. I don't know how many requirements exist. Essentially, anything that causes CPF4328 (and possibly others) is another example.

    If any problem arises down a delete/cascade chain, all I/O up to the point of error is automatically rolled back. And that characteristic relies on journalling.
    34,465 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: