RE: QSTRUP Issue

Thanks, Chris. What I was missing was that I had to DLTPGM my application program before re-compiling it. Once I did that, it worked. (I like having a test box that I can IPL to my heart;s content during the middle of the day!)

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

He's an intellectual from Yale, but he's very intelligent. -Pete Rose on Bart Giamatti, Baseball Commissioner


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Friday, May 21, 2010 2:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: QSTRUP Issue

Is the authority issue perhaps the fact that the startup list in the
system value does not have authority to your program object or
containing library? I have my startup program owned by QSECOFR with
public *EXCLUDE. It runs under *OWNER adopted authority. It calls
additional programs that have the SAME authority.

Your program may have the correct authority but the startup one does not
and does not have access to your program.

Also check to make sure no one added a user profile as *EXCLUDE as that
profile will not be able to access the object no matter what the *PUBLIC
authority is set to. (Private authorities are checked first.)

Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, May 21, 2010 11:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: QSTRUP Issue

Jerry,

If the CL program that was blowing up has USRPRF(*OWNER), and the
owner is your profile with *ALLOBJ that should be enough.

However, if the file has *PUBLIC *ALL, as you say, then there's almost
no way for you to be seeing an authority issue.

The only way would be if the file or it's authorization list has an
explicit *EXCLUDE for the user running the program or the user's
group.

So please look at the file and the authorization list (if any)
attached to the file. Are there any *EXCLUDEs?

If not, then my guess is it's a library list issue, the file you think
is being opened...isn't. And the file actually being opened has
*EXCLUDEs or maybe isn't actually a PRTF.