Re: Not authorized to spooled file - CPF3492

My first reaction was to blow you grief for using QDLS, but you're using 
options of SNDDST that rather require that.

wrklnk '/qdl*'
put a 9 in front of /QDLS.  Look good?  Then use option 5
put a 9 in front of SPOOL.  Look good?  Then use option 5
put a 9 in front of SPLF.DOC
Find any authority issues?
Not only should you have access but I believe that QMSF will also need 
access.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





fkany@xxxxxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/24/2004 02:49 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: Not authorized to spooled file - CPF3492








Paul,

That worked.  It is strange that I had to delete the CL program before
recompiling it with USRPRF(*OWNER), it got a little bit farther and that's
all that matters.  The program was able to adopt authority of QPGMR and
execute the CPYSPLF command.

Now the program is getting the "Not authorized to object.  Object is
/QDLS/SPOOL/SPLF.DOC." error message when trying to use the CPYTOIMPF
command.  I edited the authority for folder SPOOL and that didn't work. Is
SPLF.DOC the object the error message is referring to?  How can I change
the document authority?

TIA,

Frank





pnelson@xxxxxxxxxx@midrange.com on 09/24/2004 03:11:00 PM

Please respond to Midrange Systems Technical Discussion
       <midrange-l@xxxxxxxxxxxx>

Sent by:    midrange-l-bounces+fkany=averittexpress.com@xxxxxxxxxxxx


To:    Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc:

Subject:    Re: Not authorized to spooled file - CPF3492


Also, make sure that you delete CLPGM2 before you compile, and to specify
REPLACE(*NO). It sounds weird, but read the help text carefully for the
reasons.


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx



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