Midrange News for the IBM i Community


Posted by: Bob Cozzi
Rogue Programmer
Cozzi Productions, Inc.
Chicagoland
What USRPRF Owners your Production Programs?
has no ratings.
Published: 18 Feb 2013
Revised: 19 Feb 2013 - 1620 days ago
Last viewed on: 28 Jul 2017 (3132 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

What USRPRF Owners your Production Programs? Published by: Bob Cozzi on 18 Feb 2013 view comments(2)

I'm wondering if people have a unique/custom user profile for objects placed into product or if they use a developer user profile or QPGMR or QDFTOWN or something like that.

Also, when you, as a developer compiler/create objects, is the owner of those object your user profile or a Group Profile?

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS

(Sign in to Post a Comment)
Posted by: DaleB
Premium member *
Reading, PA
Comment on: What USRPRF Owners your Production Programs?
Posted: 4 years 5 months 8 days 23 hours 34 minutes ago

We've used both QPGMR and application specific object owner group profiles. We tend to use separate profiles for data objects and for everything else, since most things that aren't data usually only need *USE.

Developers are not members of production group profiles. Programmers have their own group profile, which usually has *USE in production authorization list(s). There are single-object exceptions, of course; often *OBJMGT to allow CRTDUPOBJ.

Posted by: Paulster
Premium member *
Sweden and The Netherlands
Comment on: What USRPRF Owners your Production Programs?
Posted: 4 years 5 months 8 days 10 hours 13 minutes ago

As we share our box with other companies in the same group, authority is well taken care of. All objects have the same group owner profile as owner and also have *GROUP *ALL and *PUBLIC *EXCLUDE. Every end-user profile is then tied to this group profile is order to make it work.

You could drill it down even more to allow certain users access to certain modules but we found this overkill. Worth mentioning is that no users have access to a command line.If commands are needed, they are supplied for by the menu system.

Profiles with *ALLOBJ or similar are scarce and are validated on a regular basis for SOX reasons.

The other companies on the same box have the exact same setup. So far no conflicts have emerged.