Sounds like, via SOX compliance, you need a hands-on record of someone
reviewing the change, so you may not be able to avoid the manual process
you are trying to circumvent?
Dave
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----

To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Paul Jackson <paulgjackson@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 03/17/2009 02:53PM
Subject: 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
>
>
>
>

NOTICE - This e-mail message is intended only for use by the addressee(s)
named herein and may contain legally privileged and/or confidential
information. If you are not the intended recipient of this message, you
are hereby notified that any dissemination, distribution or copying of
this message is strictly prohibited. If you have received this message in
error, please notify the sender by e-mail or telephone and delete the
original and all copies of this message immediately.
www.ephratanationalbank.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.