|
*JOBCTL (usually) or *SPLCTL (always) will do the trick, but give it to the program, not to the user. Compile the program as a user with *SPLCTL special authority, and choose the USRPRF(*OWNER) option on the compile (Also known as adopting authority). Then give the user you want to be able to do this just *USE authority to the program. The benefit of this is that the user only has *SPLCTL within the confines of your tightly scripted program, and doesn't wield that powerful authority all of the time. jte -- John Earl | Chief Technology Officer The PowerTech Group 19426 68th Ave. S Seattle, WA 98032 (253) 872-7788 ext. 302 john.earl@xxxxxxxxxxxxx www.powertech.com This email message and any attachments are intended only for the use of the intended recipients and may contain information that is privileged and confidential. If you are not the intended recipient, any dissemination, distribution, or copying is strictly prohibited. If you received this email message in error, please immediately notify the sender by replying to this email message, or by telephone, and delete the message from your email system. -- > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l- > bounces@xxxxxxxxxxxx] On Behalf Of > michael@xxxxxxxxxxxxxxxxxx > Sent: Thursday, September 23, 2004 10:55 AM > To: Midrange Systems Technical Discussion > Subject: RE: Not authorized to spooled file - CPF3492 > > You could give *JOBCTL or *SPLCTL special authority to the > users or you > could set the effective UID to a user with authority to > the spooled > file. > > > -------- Original Message -------- > > Subject: Not authorized to spooled file - CPF3492 > > From: fkany@xxxxxxxxxxxxxxxxxx > > Date: Thu, September 23, 2004 1:40 pm > > To: MIDRANGE-L@xxxxxxxxxxxx > > > > Hello, > > > > I'm receiving the CPF3492(Not authorized to spooled > file) error in a CLP > > program when I'm trying to use CPYSPLF on a spool file > generated by another > > job and user. Is there anyway to get around this road > block? > > > > Thanks, > > > > Frank > > > > > > > > -- > > 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.