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

[barsa@xxxxxxxxxxxxxxxxxxx]

I don't all of the prior notes in this thread, but somewhere it does say to
'change the owner to QSYS'  (loose quote - not precise).

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






                    "Steve Richter"
                    <srichter@AutoCoder       To:     <midrange-l@midrange.com>
                    .com>                     cc:
                    Sent by:                  Subject:     Re: Does QSYS have 
to own QINSTAPP programs created for
                    midrange-l-admin@mi        LODRUN
                    drange.com


                    12/12/01 10:45 AM
                    Please respond to
                    midrange-l







----- Original Message -----
From: <barsa@barsaconsulting.com>
> 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.
>

What follows is an excerpt from the online documention of the LODRUN cmd (
at a cmd line, type LODRUN, press F4, press F1, press F2 ).  The online
documentation of LODRUN is very extensive, is accurate and clearly states
that "the program QINSTAPP must be owned by a user user profile that
resises
on the target system".

What does IBM have to change ?

Steve Richter


The except from LODRUN online documentation (V4R4) :

   When the LODRUN command is run:

     1.  The media is searched for the user-written program, which must
         be named QINSTAPP and saved from library QTEMP.

             Note:  The program QINSTAPP must be owned by a user
             profile that resides on the target system.  If QINSTAPP is
             restored to a system that does not have the owning user
             profile, control is not transferred and the program is not
             run.



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