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

Not only does QSYS not have to own QINSTAPP, it would be
unnatural for it to do so.

QINSTAPP can be owned by any profile that you like with two
caveats in mind:
1) The profile must already be known to the system (which makes
QUSER and QPGMR good candidates).
2) The profile must have enough authority to execute the
instructions in the program.

The second point may have a lot to do with why QSYS owns the
QINSTAPP in question here.

Just for fun, (temporarily) turn on User Profile auditing for
QSYS and then restore the object and see what they are up to.
You'll likely find that they are either being devious (changing
stuff they shouldn't), or just plain stupid (assuming way more
authority than they really need).

I'd love to hear the outcome of this Al,

jte






--
John Earl
johnearl@powertechgroup.com
The Powertech Group          www.powertechgroup.com
Kent, Washington, USA       +1 253-872-7788


----- Original Message -----
From: <barsa@barsaconsulting.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, December 11, 2001 08:02 AM
Subject: Does QSYS have to own QINSTAPP programs created for
LODRUN


>
> Hi,
>
> I have been doing some research, and I see no reason that QSYS
has to own a
> QINSTAPP program to be used in the LODRUN command.
>
> The design of LODRUN is that a program called QINSTAPP which
was saved from
> QTEMP, must be the first file on the tape, it is restored and
executed.
>
> I can find no evidence of ownership restrictions.  For TAATOOL,
it is NOT
> owned by QSYS, and people run it successfully every day.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
> _______________________________________________
> 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.
>