I heard from IBM this morning, and the changing the ownership was
necessitated by the fact that the user must exist on the target system, and
that's why QSYS was picked.  They agreed to change the documentation.


Al Barsa, Jr.
Barsa Consulting Group, LLC


914-251-9406 fax


                    Sent by:                  To:     midrange-l@midrange.com
                    midrange-l-admin@mi       cc:
                    drange.com                Subject:     Re: Does QSYS have 
to own QINSTAPP programs created for

                    12/11/01 10:29 PM
                    Please respond to

On Tue, 11 December 2001, Chuck Morehead wrote:

> I read the documentation that I cited on a previous thread more closely.
> was basically giving step-by-step instructions for creating a CD.  It
> to change the owner of QINSTAPP to QSYS, but does not say why.  That is,
> never actually states that it is a requirement.

There are two examples there, one for "objects" and one for "licensed
programs". The one for objects states "Change the owner to QSYS." The other
states "Change the owner to QSYS. QSYS MUST be the owner of the QINSTAPP

However, I don't consider these pages to be documentation any more than I
would Redbooks. Stuff on those pages is just examples.

AFAIK, the general requirement is that the owning profile should exist on
the system that executes LODRUN. I'm not totally certain that that's an
absolute requirement depending on (1) what profile executes LODRUN, (2)
what system values, etc., are set and (3) what the USRPRF() attribute of
QINSTAPP is, i.e., *OWNER or *USER.

Tom Liotta

Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904

The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
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 On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.