RE: Adopted Authority problem

Mark,
Yes it does show owner = WJM, but user profile = *user.

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: Thursday, January 14, 2010 11:57 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Adopted Authority problem

Hello, Willie:

Issue:
DSPPGM MMLIB/SCPTAGSEL

and look at the first page of information displayed. What does it show for the "Owner . . ." (near the upper left of the screen)? (According to your e-mail, it should show "WJM" as the owner.)

And, what does it show for "User profile . . . " (about half-way down the first screen of information)? It should show "*OWNER".

HTH,

Mark S. Waterbury

Willie J. Moore wrote:
When running CL program SCPTAGSLCL, the user gets the following message:
User not authorized to operation on file ITMMRI1 in MMLIBD, member,
device, or program device *N.
The RPGLE program called is SCPTAGSEL, it only reads this file.

I have tried to adopt authority from a user profile that can run this job in the CL.
CHGOBJOWN OBJ(MMLIB/SCPTAGSEL) OBJTYPE(*PGM) +
NEWOWN(WJM) CUROWNAUT(*SAME)
CHGPGM PGM(MMLIB/SCPTAGSEL) USRPRF(*OWNER) +
USEADPAUT(*YES)

Now I get the following message when I call the CL:
CALL PGM(MMLIB/SCPTAGSLCL)
Not authorized to user profile WJM.
CPF2217 received by SCPTAGSLCL at 2200.

I have even tried to change the owner of the CL program. But this has not worked either.

The only other way I know is wait until this weekend when the file is not active and run GRTOBJAUT on this file.
But I would much prefer to do the object authority inside a CL statement.

Any ideals or examples would be greatly appreciated.

William Moore
California Fine Wire
805-489-5144

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