|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] I thought about a trigger over QADBXREF but was concerned about putting a trigger on a system file - especially one as crucial as that one. Dave -----Original Message----- From: Metz, Zak [mailto:Zak_Metz@G1.com] Sent: Friday, October 11, 2002 10:20 AM To: 'midrange-l@midrange.com' Subject: RE: Library trigger This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Going back to the original question, since David has a working solution now, I'm curious if this could also have been done by adding a trigger to QSYS/QADBXREF (which the SQL collection's SYSTABLES is a view of). It is a journalled file, so I don't see why it wouldn't work, although determining which updates are relevant may be a tad tricky based on the complexity of SYSTABLES's SQL. -----Original Message----- From: Leland, David [mailto:dleland@Harter.com] Sent: Wednesday, October 09, 2002 4:14 PM To: 'midrange-l@midrange.com'; 'mi400@midrange.com' Subject: Library trigger This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Anyone know of a way (outside of having a constantly running monitor program) to automatically trigger an event when an object is placed in a library? I would like to create a library that, when a user creates a file in it (typically using Query), a trigger program of some type would automatically FTP that file somewhere. Dave _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.