Re: Foreign key causing Error:55019 Message:SQLSTATE=55019 SQLCODE=-7008

Justin

There are documents that fully explain all this stuff - if you look only at the command parameters, you can get lots of information, but it's not going to give you a full picture.

So I recommend, if you haven't done so, that you find the journaling manuals on KnowledgeCenter.

As to QCMDEXC -- it is already something that can be called as a stored procedure - no need to register it - this is true about every program on the system.

Declared stored procedures usually are created with additional parameters and return values that provide more than just calling existing programs.

Just some thoughts - you've come to this platform from another area, and there's a lot of context you might not have yet - definitely good for those of us long on this platform to hear your perspective, of course.

Regards
Vern

On 10/23/2015 3:21 PM, Justin Dearing wrote:

On Fri, Oct 23, 2015, 13:51 Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

When one creates the journal (CRTJRN) one can specify that the system
manage cleaning up the receivers via the MNGRCV(*SYSTEM) DLTRCV(*YES)
parameters.

So, does this automatic clean up happen on transaction commitment, when
the table is backed up, when reclaim storage is run, or at some other
point?

On another note, if I wanted to make the journal in sql, are my two best
options QCMDEXEC and registering CRTJRN as a stored procedure? If
Journaling is a feature of tables that's been around since at least v5, why
can't I control it with CREATE/ALTER TABLE? Seems like a silly thing to
expect me to use CL for, if I'm supposed to use SQL DDL to make the
Physical File.