Re: Does QSYS have to own QINSTAPP programs created for LODRUN

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.


===>Thinking about it now Tom, I rememeber that if the profile
that owns QINSTAPP does not exist, a CPF error message is
generated to the job stating that the proile is not known to the
current system and ownership of program QINSTAPP has been
assigned to QDFTOWN.

I suppose that if you could monitor that CPF message, you could
recoever from it, but the monitor would have to be outside of the
QINSTAPP program because the program has yet to be called when
the CPF message is generated.

But this is all pretty esoteric isn't it?   Best to assign
ownership and use the tool as it was intended.  :)

jte


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/




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