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



AFAIK, virtual CD support on V5R1 is only for installing V5R2. It cannot be used for anything else at V5R1. STRVRTINS is specific to a V5R1-V5R2 upgrade and has no purpose beyond that, at least "as designed"

In future releases, one simply uses the existing commands, naming the virtual optical drive (OPTVRT01, e.g.) instead of the physical optical drive.

You'll find a lot of what you suggest covered via *IMGCLG keywords on commands, etc., or the actual name of the virtual device.

Some of the steps suggested probably involve an IPL - this complicates things - the scope of a command does not cross IPLs - would need persistent storage of the various settings as well as automated PTF processing - not sure that is possible, or at least easy.

I've not even been able to create more than one virtual optical device - in order to mount more than one image catalog. Anyone tried that successfully?

Regards

Vern

At 08:06 AM 4/28/2003 -0500, you wrote:
I used the STRVRTINS command and image catalogs to install V5R2. It was great. Saved me having to be here a couple of hours loading CDs.

Here is what I think would be the nuts for future release installs:

STRVRTINS SAVBFR(*NONE|device name)
          INSIMGCLG(*NONE|install image catalog name)
          PTFIMGCLG(*NONE|c-u-m PTF image catalog name)
          GRPIMGCLG(*NONE|group PTF(s) image catalog name)
          SAVAFT(*NONE|device name)


Here is what the above would do: ================================

1) The SAVBFR parm indicates whether to do an "option 21" save before starting any of the following, and, if so, what device to use.

2) The INSIMGCLG parm indicates whether to do a release upgrade, and, if so, the image catalog to use. The system would then IPL to do the install (this is the part it does already)

3) If an install was done, wait for the INZSYS to complete.

4) The PTFIMGCLG parm indicates whether to do a c-u-m PTF install and apply, and, if so, the image catalog to use. The system would then IPL to do the PTF apply.

5) If a PTF c-u-m install was done, wait for the IPL to complete.

6) The GRPIMGCLG parm indicates whether there are any group PTFs to install and apply, and, if so, the image catalog to use. The system would then IPL to do the PTF apply.

7) The SAVAFT parm indicates whether to do an "option 21" save after everything else is done, and, if so, what device to use.

8) A final IPL is done and the system is ready to use.


Using the above, couldn't a release upgrade be _entirely_ unattended? What have I missed?


You know, I just decided to look at the STRVRTINS command at V5R2 to see what parms there are, and the command does not exist at V5R2! I guess I'll do some reading when I get the chance. Maybe IBM has something up their sleeve for this.

--
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.