RE: Programmer DFU access

["Nelson, Jim (RCIS)" <Jim.Nelson@xxxxxxxxxxxx>]

We removed all developer authority to update production files, but created a
'PGPROD' userid.  Access to this userid is at the team lead level or their
discretion.

First step when signing on is to enter the developers 'true' userid and the
reason they are signing on with this password - goes into an audit file for
review as needed.

This received a 'just barely' pass from our auditors (banking folks, pretty
anal)

JN

> -----Original Message-----
> From: Johnny Helms [SMTP:Johnny.Helms@rhtelco.com]
> Sent: Friday, June 16, 2000 6:31 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Programmer DFU access
> 
> I realize this. I guess I need to re-phrase my question. How do other
> shops 
> change actual data in physical files without using DFU on the production 
> system?
> 
> Johnny Helms
> 
> At 06:47 PM 6/15/00 -0400, you wrote:
> >Um, change the DFU commands authority to exclude *public on the
> production
> >box?
> >
> >Fire the programmers for insubordination?  What part of "no" don't they
> >understand?
> >
> >- Dan Bale
> >
> > > -----Original Message-----
> > > From: Johnny Helms [SMTP:Johnny.Helms@RHTelCo.Com]
> > > Sent: Thursday, June 15, 2000 2:32 PM
> > > To:   MIDRANGE-L@midrange.com
> > > Subject:      Programmer DFU access
> > >
> > > I am looking for suggestions on how to secure a current production
> AS/400
> > > that has programmer's using DFU to change data in files. We do have a
> > > development system and I thought change management would allow this
> > > practice to be ended. However, after talking with Aldon, they have no
> > > suggestions.  The reason I am trying to end this practice is due to an
> > > Audit we recently had that we failed miserably.
> > >
> > > TIA,
> > >
> > > Johnny Helms
> > > Mid-Range Sytems Engineer
> >+---
> >| This is the Midrange System Mailing List!
> >| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> >| To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> >| Questions should be directed to the list owner/operator:
> david@midrange.com
> >+---
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---