I got a note from IBM merely stating that the owner has to exist on the
target system.

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






                    Chuck Morehead
                    <cbmorehead@nokuse.       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/11/01 01:39 PM
                    Please respond to
                    midrange-l






Al,

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.  When I originally read
this
I took it as such, but I suspect that it is actually just the writers
providing their method as an example.  I can't find anything that actually
states that ownership is a requirement, and your experience _proves_
otherwise.

Chuck

----- Original Message -----
From: <barsa@barsaconsulting.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, December 11, 2001 10: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.







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.