Re: Create Table Security

Traditionally when I see a Group profile assigned I also see Owner changed 
from *USRPRF to *GRPPRF.

When a user is a member of a group profile you can do a WRKOBJ on the 
group profile and see that user, for example
DSPOBJAUT OBJ(SYSGENPGMR) OBJTYPE(*USRPRF)
                         Object 
User        Group       Authority
*PUBLIC                 *EXCLUDE 
ACCTG                   USER DEF 

DSPUSRPRF ACCTG
Group profile  . . . . . . . . . . . . . . :   SYSGENPGMR
Owner  . . . . . . . . . . . . . . . . . . :   *GRPPRF 
Group authority  . . . . . . . . . . . . . :   *NONE 
Group authority type . . . . . . . . . . . :   *PRIVATE 

However I understand what you are doing - just never seen it done that 
way.

Using your technique.  On an existing library I got
MCH1001-Attempt to use permanent system object ROB without authority.
The library was owned by user ROB.  And if I do a DSPOBJAUT ROB *USRPRF I 
will not see this new user in there.

On a whole new library or collection, no problem:
create collection acctgx 
Schema ACCTGX created. 
CREATE TABLE acctgx/YA (MYCHAR CHAR (5 ) NOT NULL WITH DEFAULT,
PRIMARY KEY (MYCHAR)) 
Table YA created in ACCTGX. 
LABEL ON TABLE ACCTGX/YA IS 'duh' 
LABEL ON for YA in ACCTGX completed. 

Does it create your table and is it only the label on that is failing?


Rob Berendt