× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



When a CRT* does a replace, it keep certain parameters, like owner.
Makes sense - usually when you recreate a program you're changing what
the program does, not what the program is.

On Fri, Oct 3, 2008 at 12:37 PM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:
Hi, everyone,

Can anyone explain why a program, created by CRTBNDRPG, which currently has
the User Profile attribute set to *USER, will NOT change that attribute to
*OWNER when the compile command clearly instructs it to do so?

For example, Display Program appears as follows:

Program . . . . . . . : I276200441 Library . . . . . . . :
UserLibrary
Owner . . . . . . . . : QSECOFR

Program attribute . . : RPGLE

Detail . . . . . . . . : *BASIC





Program creation information:

Program creation date/time . . . . . . . . . . : 10/03/08 11:16:08

Type of program . . . . . . . . . . . . . . . : ILE

Program entry procedure module . . . . . . . . : I276200441

Library . . . . . . . . . . . . . . . . . . : QTEMP

Activation group attribute . . . . . . . . . . : *DFTACTGRP

Shared activation group . . . . . . . . . . . : *NO

User profile . . . . . . . . . . . . . . . . . : *USER

Use adopted authority . . . . . . . . . . . . : *YES

Coded character set identifier . . . . . . . . : 65535

Number of modules . . . . . . . . . . . . . . : 1


Now, a recompile, as follows, occurs...
CRTBNDRPG UserLibrary/I276200441 srcfile(UserLibrary/qrpglesrc)
srcmbr(I276200441)
replace(*yes) dftactgrp(*no) actgrp(*caller) usrprf(*owner)
aut(*exclude) dbgview(*source)

Note the usrprf attribbute and the replace parameter.

Why would the new, replaced object RETAIN the *USER setting, after the
compile has successfully completed? (QSECOFR is doing the compile).

This can't be some security approach IBM is using because if I have the
authority to replace the object, and change the logic altogether through the
compile, surely I have the authority to indicate it should be run as *OWNER,
not *USER.

Furthermore, if I delete the program before the compile, the attribute is
set properly.

Any ideas?


Best Regards,

Thomas Garvey



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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.