Re: Small changes are better RE: Daylight savings time

Theres an upside to SOX, other than it has me on a contract for the
forseeable future?

On 3/1/06, Keith Carpenter <carpcon@xxxxxxx> wrote:
>
>
> More than reasonable if your company is trying to meet SOX requirements.
>
> Where I'm working currently, many things that had been performed by IT
> have been pushed back to the users.  In some cases, this meant new
> developing new programs to eliminate the routine use of DBU/SQL for
> changing production data.
>
> For the remaining exceptional changes, we require the user (often the
> appropriate department head) to make a non-verbal request (email or
> helpdesk ticket)  and then verify the change we make in a test
> environment.  Once approved (email or signed CRF (change request form)),
> IT then changes the production environment.  May seem excessive, but
> it's part of our written SOP developed with the auditors.
>
> One of the few upsides of SOX has been to get users to take more
> responsibility for their data.
>
>
>
>
> Tom Jedrzejewicz wrote:
> > My position is ...
> >
> > The fact of the matter is that mistakes happen; that is why there are
> > methods in any system to reverse transactions or make adjustments.
> > When an error happens, those means should be employed if at all
> > possible.  DBU or SQL or fix programs should only be employed when the
> > system cannot be used.
> >
> > Question for the list ... is my position unreasonable?  How are these
> > situations handled in your companies?
> --
> 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.
>
>