|
Uuhhh. I didn't know you can actually do create table as. That will work. Thanks. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Thursday, January 12, 2006 11:23 AM To: Midrange Systems Technical Discussion Subject: RE: Cpy file command copy the authority The program that copies it could adopt authority. Or, (You voiced a preference for no sql but), this works quite well create table qtemp/lim as (select * from lim) with data Now, if it is imbedded sql that gives you shivers, then you could stick that into a source member and use RUNSQLSTM. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/12/2006 12:02 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Cpy file command copy the authority Below is the problem that I'm encountering: 1) I have a file FILEA in production lib LIBA that user only have *use auth. 2) A program is suppose to use cpyf command to dup it to qtemp and adding data the this qtemp file. It failed because the auth setting got copied over. Other than using sql or save and restore, is there any other easier way to go around this problem? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Thursday, January 12, 2006 10:27 AM To: Midrange Systems Technical Discussion Subject: RE: Cpy file command copy the authority Yes. Before copying I did a WRKOBJ and added a different profile at the bottom. After the CPYF the new person was in the new file. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.