Re: Primitive editor's stupid security requirements

Rob,

wasn't aware of the execute requirement.  good to know, in case I run
into it again.

Rick

On 8/15/05, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> Thank you.  I looked at their existing authority and a new person created
> with *USE.  The missing details (shown by beating the F11 key) was
> 'Execute'.  Apparently they need 'Execute' authority on a source physical
> file to view a member of that file with SEU.  And a blanket "let's change
> everyone to *USE" will then allow them to execute any *PGM objects, like
> custom compile commands.  Got lucky on this library and there are no
> command or program files.
> 
> I wonder why they require Execute?  I hazard to guess that they check for
> the generic *USE or higher.
> 
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
> 
> 
> rick baird <rick.baird@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 08/15/2005 04:27 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> 
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> Re: Primitive editor's stupid security requirements
> 
> 
> 
> 
> 
> 
> Rob,
> 
> your users should have *use authority to the souce files, allowing
> copy,browse but not add or edit.
> 
> this has worked for me in the past - in fact, with this authority, SEU
> will actually allow you to open the file for edit (option 2), but once
> inside it will give you a message (not authorized to edit) and not
> allow you to save it back to the same sourcefile - it will allow you
> to save to a sourcefile you have authority to.
> 
> hth,
> 
> Rick
> 
> On 8/15/05, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> > Tried to use SEU by using the command:
> > STRSEU SRCFILE(BPCS405CDS/QCLSRC) SRCMBR(ACP100C) OPTION(5)
> > Option 5 is view.  Not change.  I get EDT0215.  But a simple
> > DSPPFM FILE(BPCS405CDS/QCLSRC) MBR(ACP100C)
> > command works fine.
> >
> > Situation:  I have a vendor supplied source library.  If my developers
> > truly need to modify one of their programs they can view it.  Maybe even
> > copy it to our modification library and modify it there.  I really don't
> > want them modifying source in this source library.
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>