Re: SNDDST to IFS?

The change is already being recorded in a DB2 file, the email is for
instant notification to concerned parties as part of our SOX
compliance procedures. I agree that it seems like overkill, but that
is what our users want to do (if possible), I just wanted to get an
idea of the feasibility at this point.

On Tue, Mar 17, 2009 at 11:18 AM, <rob@xxxxxxxxx> wrote:

Why not just have the program that determines that a change occurred
record the change (be it into a stream file, a DB2 file or whatever)?  Why
complicate it by sending it out as an email, receiving an email and then
storing it into a stream file?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Paul Jackson <paulgjackson@xxxxxxxxx>
To:
MIDRANGE-L@xxxxxxxxxxxx
Date:
03/17/2009 02:01 PM
Subject:
SNDDST to IFS?
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Greetings,

I have a process that monitors for system value changes and sends out
an email via the SNDDST command whenever a change is detected.  One of
our admins saves each of the emails from Outlook into a network drive
mapped in the IFS where they appear as .msg type files.

We are wondering if this process can be automated somehow so that the
monitor program can automatically put a copy of the email into the IFS
location?

Any suggestions would be appreciated.

Thanks!
-Paul
--
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.