MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2012

RE: Set authority on SQL CREATE TABLE



fixed

Drop table mylib.mytable;

Won't work?


-Tom Stieger
IT Manager
California Fine Wire



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Thursday, September 27, 2012 6:49 AM
To: Midrange Systems Technical Discussion
Subject: Re: Set authority on SQL CREATE TABLE

Well... this mostly worked. The only problem is they can't delete this temp file when it is done being processed. Guess I'll go back to the CL route.

--
Mike Wills
http://mikewills.me


On Wed, Sep 26, 2012 at 9:26 AM, Tom E Stieger <testieger@xxxxxxxxxxxx> wrote:
Try running the GRANT SQL command after the create statement.

Create table mylib.mytable as (balh, blah, blah);

Grant all on mylib.mytable to user;


-Tom Stieger
IT Manager
California Fine Wire



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Wednesday, September 26, 2012 7:19 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Set authority on SQL CREATE TABLE

I am having a problem where I have a program do an SQL CREATE TABLE and the authorization for *PUBLIC is *EXCLUDE. Now leaving out the security implications of setting that to *ALL, how can I either add a user with *ALL or change *PUBLIC to *ALL? A third option would be to use an authorization list.

No matter the approach, is this possible at the time of creation? Or do I have the run the CL command (which for the life of me I can't remember which) and change it that way? This is all ran through an automated process. I have tried to set CRTAUT on the library to *ALL and to my authorization list with no effect.

--
Mike Wills
http://mikewills.me
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact