compiling cl program, ownership issues

15 pts.
Tags:
CL Program
compling
i series
i added a commment line to a current CL program. when i went to compile it thefollowing error message appeared Owner of object COPPK1 and object being replaced not the same. any ideas?

Software/Hardware used:
custom program, i series
ASKED: December 20, 2012  8:58 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Change the owner of the existing program object to be the same as the user who compiles the new program, compile the new program, then assign ownership back to the owner of the original program. Or delete the original, compile the new version, and then change the owner. Or run the compile under the user profile that owns the original program.   Note that first deleting the program will mean that you must log all of the existing authorities and then reassign them after creating the new version. The best method is to recreate the program under the profile that is the current owner, e.g., sign on as that user and run the compile. If that isn't reasonable, then change the owner first. Either of those ways should retain existing authorizations (but you might want to log them anyway).   The original *PGM is compiled with the USRPRF(*OWNER) attribute. That allows the program to 'adopt' any authority of its owner if elevated authority is needed. By doing that, a user who is authorized to run the program does not need private authority to do what the program can do. The user can't do the same actions outside of the program.   The system won't let you replace the *PGM object with a different one that has a different owner. A programmer might attempt to put malicious code into the new program and at the same time provide an owner with slightly different authorities. Users who run the program could then unknowingly enable hidden actions.   So the system forces you to follow a series of steps that ensures that you have authority for every individual piece of authority. For example, you have to have authority to change objects authorized by the original owning profile. You have to be able to add and remove objects owned by the owning profile. You have to have authority to create programs with the USRPRF(*OWNER) attribute. You have to have authority to manipulate the private authorities of all users who are authorized to the program.   A program that adopts authority is a potentially powerful object. Replacing it can have wide ranging effects far into the future. The steps needed to replace it are important.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following