Re: Object owner differences on compiles.

John,

John Bussert wrote:

> On release 4.1, we are experiencing problems compiling programs where the
> owner of the program is not the same as the person compiling and it fails.
>  We are not using group profiles (because it won't let us).

This is a curious statement.  Group profiles are really your best defense 
against
this type of problem.  I wonder what kind of trouble you're running into with
them?

> Is there a
> system value of option somewhere that will let compiles go through and
> replace the object (if the person compiling has rights) with the new one?

Other than the "Replace object" paramter behinf the F18 key on PDM?  (That's
probably not your problem, but I like to get the easy ones out of the way early
:).Another questions... are you sure that the USERID doing the compiling has
proper authority to the existing object?  You need object existance (or *ALL)
authority to delete an object.  If the person doing the compiling doesn't have
those rights, they won't be able to replace the existing object.

The best way to get around this problem is to use a good change management 
system
(I like Turnover... no affiliation) that will set all of your production (or
test) objects to be owned by an application owner ID.  Then object ownership is
consistant across your system.

Barring that, create an application owner ID yourself and then build a shell
'create' process that compiles objects as that ID using adopted authority.  Then
anyone who is authorized to run the shell 'create' process will be authorized to
replace objects.

Hope this helps.

jte

--
John Earl Lighthouse Software Inc.
8514 71st NW Gig Harbor, WA 98335
253-858-7388 johnearl@lns400.com

Without Lighthouse Network Security/400, your AS/400 is wide open.
--




+---
| 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---