MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

RE: Trigger question



fixed

This is a _very_ bad idea.

Besides the fact that a trigger program could be fire within a batch job, the real problem is that the
trigger program in invoked by the DB code deep in the OS. I doubt that you'd even be able to call a
program that uses a display file even when the trigger is fired in an interactive job.

Even if you could...I'd strongly advise against it. That's just not the way triggers are designed to
work.

How did you plan to handle the need for additional info when the job is batch?



Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jones Simon
Sent: Thursday, June 12, 2008 10:47 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Trigger question

Hello all,

I have a trigger program which calls after an update to a database file,
that works fine.

A requirement has come up where some of the processing which is done by
the trigger program will need some user input by way of an interactive
screen. Instead of adding this screen to the trigger program I was
looking at adding a call to a new program from the trigger program. I'm
trying to work out if this will cause any problems - the trigger program
will be active for the duration of the time that the screen is displayed
and processed.

The obvious problem I've though of is the danger of trying to open the
display file in a batch job, but we can cater for this. But what I cant
work out is if this call to an intractive program will cause any issues
within the trigger program.

My initial thoughts are that this is likely to be a bad idea, but I'm
not really sure why!

Hopefully I've made that clear

Simon

Volvo Information Technology is a Division of Volvo Group UK Limited,
Registered in England No: 2190944, Registered office: Wedgnock Lane,
Warwick, CV34 5YA
The information in this email and in any attachments is confidential and
may be privileged. If you are not the intended recipient, please destroy
this message, delete any copies held on your systems and notify the
sender immediately. You should not retain, copy or use this email for
any purpose, nor disclose all or any part of its contents to any other
person.


--
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 e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact