Re: Create Table Security

Mark - it'd be helpful to see the 2nd-level text - there is only msg-level 
here, and 2nd-level always has useful information in these kinds of messages. 
E.g., where it says an operation was not performed, the 2nd-level will probably 
tell you what operation it was trying to do. These messages are almost too 
general, and I wax too long - sorry!!

Let us know, please!

Vern

-------------- Original message -------------- 
From: Mark Adkins <adkinsm@xxxxxxxxxx> 

I need some help in the way security works with the "Create Table " 
command. 

I have a library "OTPTEST1" and a user profile "OTPTEST1". The user 
profile "OTPTEST1" has primary group "AMPGMR" and my user profile's 
primary group is "AMPGMR". 

OTPTEST1 

Group profile . . . . . . . . . . . . . . : AMPGMR 
Owner . . . . . . . . . . . . . . . . . . : *USRPRF 
Group authority . . . . . . . . . . . . . : *ALL 
Group authority type . . . . . . . . . . . : *PGP 

When I try a RUNSQLSTM on a script that creates a table with a primary key 
and label statements, it fails with the following. 

Ownership of object CHAINTEST in OTPTEST1 type *FILE changed. 
Not authorized to perform operation on file CHAINTEST. 
Function not done for user profile AMPGMR. 
One or more errors occurred during processing of command. 
Constraint was removed. 
1 constraint(s) removed from file CHAINTEST. 
Not authorized to object OTPTEST1 in *N type *USRPRF. 
RUNSQLSTM command failed. 

I should have the authority...what am I missing? 

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