RE: Dumb adopted authority question

[rob@xxxxxxxxx]

A lot of that crud hangs around forever.  We had a subsystem description 
(QBATCH) that would never upgrade right because it was built prior to 
V2R1.  We wrote a program to rebuild it and now it works fine.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/22/2005 03:34 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Dumb adopted authority question






Prior to V2R1 no one had access to their own profile.  We have several
profiles that were created at V1R2 and V1R3 that did not allow the user to
modify or use their own profile.  Jobs start with the user profile of QSYS
so you can get logged on and work via 5250.  I had to add the profile it's
self to *USE authority for it self.   Does not make sense to me.  About 
the
Qsecofr thing, I do not know for sure it this is the problem.  Sure would
like to know what the solution is.

Chris Bipes

-----Original Message-----

> David I have run into this.  Make sure Qsecofr has *use authority to
> Qsecofr profile.  You must have *use authority to your own profile to
> use the api.

Hmm. I didn't think it was possible to even sign on if one doesn't have
*USE authority to one's own user profile. Nor did I think it was possible
for QSECOFR to lack authority to anything.

Fascinating.
-- 
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.