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



On Tue, 11 December 2001, Chuck Morehead wrote:

> I read the documentation that I cited on a previous thread more closely.  It
> was basically giving step-by-step instructions for creating a CD.  It says
> to change the owner of QINSTAPP to QSYS, but does not say why.  That is, it
> 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 
program".

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
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.