Re: Programmer Authorities

["Rina A.Wiese" <rina@xxxxxxxxx>]

> Hi!
> 
> How do other sites restrict their programming staff? Do you allow them
> *JOBCTL or (shock horror) *ALLOBJ authority? Do they have access to live
> programs and data or is there some form of change control? etc...
Tim,
Programmers should work in an environment  separated from your business
environment. To create good applications they do not need any special
authorities at all, just a good workable environment e.g. own libraries ,
libs with test data, etc.
Make them part of a group w/ the necessary authorities to work, preferably
under a group profile that is NOT QPGMR but rather a copy of it. (aside of
some objects it is a good idea to use objects whose names begin with the
lettre Q as little as possible.

If U have only one system and U have programmers working on it (for
applications, not system programs for save/restore etc.) then use three (3)
separate environments; one for development purposes, one for the acceptance
tests and one production environment (=the largest).
If your programmers do not setup programs and objects authorities properly
then it is very difficult and probably cumbersome to put things right
afterwards (and that s then probably your job to do so!)
Another good advise on authorities is to have separate usrprofiles just to
OWN objects; if the owner and the group profile are the same then all group
members have *ALL authorities on the objects owned by the group and that s
not what U want.

Rina,

rina@xs4all.nl

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---