× 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: Changing triggers
  • From: "Nelson C. Smith" <ncsmith@xxxxxxxx>
  • Date: Mon, 27 Mar 2000 21:51:50 -0500

Some folks use CLP's as the trigger program and have it call an RPG program.
I prefer to stay with RPG all the way.

I use a generic program (same program in all 6 time slots) that does nothing
but call a generic trigger procedure and if the procedure returns any kind
of error, the generic trigger program returns an escape message to kill the
trigger update. The generic trigger procedure then calls a file-specific
procedure in a service program in which I maintain all procedures having
anything to do with that particular file.  All changes are then made in this
file-specific trigger procedure.

This eliminates the problem of changing trigger programs but I have
occasionally run into problems when making changes to the service program of
currently active triggers "losing their way" to the pointer to the service
program.  Apparently, once the pointer to the service program is resolved,
it doesn't check it again in the same job.


----- Original Message -----
From: "Nelson, Jim (RCIS)" <Jim.Nelson@RCIS-NET.COM>
To: <MIDRANGE-L@midrange.com>
Sent: Monday, March 27, 2000 10:20 AM
Subject: Changing triggers


> In our development environment, we are changing SOME trigger on SOME file
> almost daily.  To make such a change, the file that trigger is based on
must
> not have any locks.  This has become unworkable with the number of
> developers and functional test people involved.
>
> We are talking about creating completely generic triggers to call a stored
> procedure which will either run the activity intended or call one or more
> other stored procedures.  When a change was needed it would be made to
that
> front-end stored procedure.
>
> Before we get too deep into this, it would be nice to know if there are
any
> 'gotchas'.
>
> Has anybody else gone down this road?  Has it worked?  Anything we should
> keep in mind?
>
> Thanks,
> JN
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.