Re: Object owner differences on compiles.

Brad,

Stone, Brad V (TC) wrote:

> Make all owners QPGMR.  Works well for us.

I know that lots of people do this, but I discourage my customers from using any
IBM profiles as application owners.... QPGMR most of all. Using an IBM profile 
as
your application profile essentially gives that IBM profile *ALLOBJ authority
within your application.  Unfortunately the history of QPGMR is a little more
promiscuos than you would like, the most glaring example being the QBATCH job
description.  If you're running at security level 30, then anyone who has access
to your system (read: *PUBLIC) can have that *ALLOBJ-like authority to your
application.

IMHO, it's best to keep IBM profile's an arms lengthfrom your application.

jte


>
>
> Bradley V. Stone
> bvstone@taylorcorp.com
> http://prairie.lakes.com/~bvstone/
> "Robble Robble" - The Hamburgler
>
>         ----Original Message-----
>         From:   John Bussert [SMTP:jbussert@stecnet.com]
>         Sent:   Saturday, April 04, 1998 12:12 AM
>         To:     Midrange-L (E-mail)
>         Subject:        Object owner differences on compiles.
>
>         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).  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?
>          Now we have to delete the silly thing by hand and then compile
> it.
>
>         If you respond, please shoot a direct mail so I can filter it
> out.
>
>         Thanks
>
>         John Bussert
>         jbussert@stecnet.com
>         Swift Technologies, Inc.
>         847-289-8339
>
>         +---
>         | 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
>         +---
> +---
> | 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
> +---



--
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
+---