RE: Adopted Authority problem

Jerry,
I made a CL for compiling. I added the 'crtbndrpg', 'chgobjown & chgpgm commands.
The user was able to run the program after I compiled it using this CL.
Thanks,

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Thursday, January 14, 2010 1:08 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Adopted Authority problem

Jerry,
Thanks for the information. Will try to get a copy of Alan's 'make' program.
Thanks,

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, January 14, 2010 12:42 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Adopted Authority problem

A change management system (CMS) is a package (such as MKS) that is used to checkout an object for maintenance. It has all of the facilities needed to promote the changed object back to production with all of the attributes intact. At least, that's the short version (over to you, David).

A 'make' program is something as simple as a CLP that is used to compile the program and apply, if needed/desired, attributes such as ownership. Someone on the list (Alan Campin, I think) has a Make utility.

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


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Thursday, January 14, 2010 1:55 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Adopted Authority problem

Thanks Rob,
Not sure by what you mean by 'make' program or change management system?
I never used the 'make' program and do not believe we have a 'change management system'.
Could you give me some information on these.
Thanks,

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 14, 2010 10:51 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Adopted Authority problem

Are you running this:
CHGOBJOWN OBJ(MMLIB/SCPTAGSEL) OBJTYPE(*PGM) +
NEWOWN(WJM) CUROWNAUT(*SAME) in your production program?

That should NOT be in your production program. That should either be:
1 - Stored in your change management system.
2 - Stored in a "make" program that compiles SCPTAGSEL.
3 - Stored as a comment in SCPTAGSEL so that if someone recompiles SCPTAGSEL outside of the change management or make program, and it now fails to work, that they know how to fix it.

The user cannot execute the command CHGOBJOWN to a user profile other than they're own.


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





From: "Willie J. Moore" <WJMoore@xxxxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date: 01/14/2010 01:22 PM
Subject: Adopted Authority problem
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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.


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

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