× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Trigger programs.
  • From: DAsmussen@xxxxxxx
  • Date: Tue, 20 May 1997 17:54:06 -0400 (EDT)

Charlie,

In a message dated 97-05-20 11:28:44 EDT, you write:

> >Well done!  I might also note that triggers CANNOT be removed if the file
is
>  >open by anybody, and that *LIBL is NOT supported as a location for said
>  >trigger program...
>  >
>  If *LIBL were supported, which library list would you want used to locate
>  the trigger program? 

I would hope the LIBL of the job invoking the trigger (since the trigger
becomes part of that job anyhow).  I work in a large system environment, and
we test the STEW out of everything before it goes to production -- with the
exception of triggers.  We have been burned more than once by trigger
programs that either filled the triggering program's job log with SEQONLY
messages or just plain didn't work right against production data.  For
obvious security reasons, developers don't have authorization to add or
remove triggers.

Actually, our testing is much better now that we have moved to a separate
development box and can add/remove triggers on it with abandon.
 Unfortunately, most shops cannot afford the near-terabyte of DASD we have on
our development box (let alone the processor and OS/400 licenses) that allows
us to have test, prototype, and a duplicate of the production environment.  I
just wish that this ability was available to those that don't have the same
resources...

Regards!

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

"The two hardest things to handle in life are failure and success." --
Anonymous
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.