Re: Trigger Information

["Mark Allen" <scprideandms@xxxxxxxxx>]

Just an FYI for all:

I finally found the PRTSQLINF cmd and running it on the ILE C objects shows
me the SQL statements that were used to create it.  Thats a start....



On 7/18/06, Hauser, Birgitta <Birgitta.Hauser@xxxxxxxxxxx> wrote:
> Hi,
>
> double quotes are used to make a name case sensitive.
> CLE means ILE-C (not CL).
> SQL triggers are first converted into ILE C-Code with embedded SQL and
> after
> compiled with the normal C-language compiler. The result are CLE-objects
> (programs)
>
> Birgitta
>
> -----Ursprüngliche Nachricht-----
> Von: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark Allen
> Gesendet: Dienstag, 18. Juli 2006 01:55
> An: Midrange Systems Technical Discussion
> Betreff: Re: Trigger Information
>
> at home not at work, i did a q&D select on the table and see a lot I
> recognize but there are some where the program name is surrounded by "
> i.e.
> "Namechg"  in my notmal pgm library and IIRC I looked at the attribute and
> it was CLE, I have no clue right now where the source for this might be or
> even what type it is (C?  CL-ILE?) let alone what they are
> doing..............
>
>
> On 7/17/06, Dave Odom <Dave.Odom@xxxxxxxxxxxx> wrote:
> >
> > Dave Smith, et al,
> >
> > Yes, there is a TABLE... "QSYS2"/"SYSTRIGGER".   Therefore, is there
> > any reason why you couldn't do things the SQL/DB2 way... use a SELECT
> > statement and then an UPDATE or just an UPDATE?    I think you are
> > looking for columns:  A.OPERATIVE, A.ENABLED.
> >
> > BTW, the query for the full table looks like (some columns have been
> > cut off):
> >
> > SELECT
> > -- Columns
> >       A.TRIGGER_SCHEMA, A.TRIGGER_NAME, A.EVENT_MANIPULATION,
> >       A.EVENT_OBJECT_SCHEMA, A.EVENT_OBJECT_TABLE, A.ACTION_ORDER,
> >       A.ACTION_CONDITION, A.ACTION_STATEMENT, A.ACTION_ORIENTATION,
> >       A.ACTION_TIMING, A.TRIGGER_MODE, A.ACTION_REFERENCE_OLD_ROW,
> >       A.ACTION_REFERENCE_NEW_ROW, A.ACTION_REFERENCE_OLD_TABLE,
> >       A.ACTION_REFERENCE_NEW_TABLE, A.SQL_PATH, A.CREATED,
> >       A.TRIGGER_PROGRAM_NAME, A.TRIGGER_PROGRAM_LIBRARY, A.OPERATIVE,
> >      , A.THREADSAFE, A.MULTITHREADED_JOB_ACTION, A.ALLOW_REPEATED_CHAN
> >       A.TRIGGER_UPDATE_CONDITION, A.LONG_COMMENT
> > -- Tables
> >       FROM "QSYS2"/"SYSTRIGGER" A
> >
> > Dave
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.