Re: Journals and Triggers

[DAsmussen@xxxxxxx]

Bob,

In a message dated 97-05-23 16:09:03 EDT, you write:

> Is there a way to perform any of the following using either API calls or
SQL:
>  1) Determine if a file is journaled.  If so, what is the name of the
Journal 
> and current Receiver.
>  2) Start journaling on a physical file or access path.
>  3) End journaling on a physical file or access path.
>  4) Determine the trigger programs associated with a file.
>  5) Add a trigger program to a file.
>  6) Remove a trigger program from a file.
>  7) Determine the RI constraints for a file.
>  8) Add a RI constraint for a file.
>  9) Remove a RI constraint from a file.

I'm not near a CD, so I can't confirm or deny the ability of an API to do
this.  I know that you CAN do it (but not sure about the RI stuff) using CL
and DSPFD to an outfile.  Manually perform the DSPFD to an outfile, then
write your CL with a DCLF statement for your outfile (the variables will
automatically be imported to your CL just like any externally defined file in
RPG or other 3GL).  There will be variables in your outfile (use DSPFFD on
it) that contain the values you seek.  Use RCVF (don't forget to monitor for
EOF!) to receive the data one file at a time.  You can then perform the
desired function based upon the data read.

We've used the above to periodically perform a CHGJRN command to detach and
save journal receivers automatically...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"You don't get ulcers from what you eat, you get them from what's eating
you." -- Vicki Baum
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *