|
midrange.com
We suck.
We develop for a group of applications: Software Plus, BPCS, homegrown,
etc. And we run multiple companies BPCS on our production machine. Each
company has their own group profile. About the only people who think that
this is a PITA are developers. Our implementation requires that they have
multiple user id's. Because, yes, some wear many hats. No one except for
me and the security person (you don't want to F&*% with Peggy), have
*ALLOBJ and *SECADM on the production box. But, on the production box,
each developer whines, stomps their feet, sucks their thumb and complains
until at least one of their user profiles has *ALLOBJ. From then on that
seems to be about the only user profile they use. This helps them to avoid
that pesky adequate testing and getting the object authority right before
they slap it onto the production box.
We are currently implementing Turnover, but heaven help you if you run into
any glitch or anything. It immediately gets labeled as a problem with the
package in it's entirety.
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
"Chris Beck"
<CBeck@good-sam.com To:
<MIDRANGE-L@midrange.com>
> cc:
Sent by: Subject: Re: Developer
Access.
owner-midrange-l@mi
drange.com
06/04/01 08:41 AM
Please respond to
MIDRANGE-L
Sorry for being so vague, I didn't think before I typed.
As far as Security Access.
>>> rob@dekko.com 06/01/01 02:21PM >>>
Might just be me but I find this question quite vague.
Do you mean security access, like giving all developers *ALLOBJ?
Do you mean do you use CODE/400 or SEU?
Do you mean Token Ring, Ethernet, VPN, twinax?
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
"Chris Beck"
<CBeck@good-sam.com To:
<MIDRANGE-L@midrange.com>
> cc:
Sent by: Subject: Developer
Access.
owner-midrange-l@mi
drange.com
06/01/01 11:24 AM
Please respond to
MIDRANGE-L
What does everyone else use for access when setting up developers on a
separate Dev box.
+---
| 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
+---
+---
| 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
+---
As an Amazon Associate we earn from qualifying purchases.
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.
