Browse Prior Art Database

Flexible DDR Installation Process

IP.com Disclosure Number: IPCOM000110980D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 4 page(s) / 128K

Publishing Venue

IBM

Related People

Blake, K: AUTHOR [+6]

Abstract

VM/ESA features a new, automated installation process. You now use a new INSTALL exec with a panel interface that reduces complexity and time required to install VM/ESA. This new process provides flexibility both in what components you load and where you can load them. This installation method minimizes contiguous DASD requirements and DASD device-type restrictions.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 45% of the total text.

Flexible DDR Installation Process

      VM/ESA features a new, automated installation process.  You now
use a new INSTALL exec with a panel interface that reduces complexity
and time required to install VM/ESA.  This new process provides
flexibility both in what components you load and where you can load
them.  This installation method minimizes contiguous DASD
requirements and DASD device-type restrictions.

The following are installation steps using the DDR:

1.  Format all system DASD.

2.  DDR restore the IIS.

    Note:  IIS stands for Initial Installation System.  The IIS is a

    Note:

    Note:

    Note:

    VM subset with enough function to run the INSTALL exec and load
    down the entire system.

3.  Logon to the MAINT userid.

4.  Choose the proper directory for your given system.

5.  Put the directory online.

6.  Invoke the INSTALL EXEC.

7.  Complete post install steps.  (i.e., customize CMS, segments etc)

Special Features of the Flexible DDR Install:

o   Feature:  Flexibility of What Components to Load

    The user is presented with a panel when they invoke the INSTALL
    exec.  This panel allows the user to choose which
    component/components they desire to load by typing an 'S' in the
    field next to the component.  This panel also reflects if any of
    the componets were previously loaded upon a past invocation of
    the INSTALL exec by displaying an 'L' in front of the component.
    If the user wishes to reload a component, they would hit PF4
    (Unload Reload) and type an 'S' over the 'L'.  Fig. 1 is an
    example of the panel.

o   Implementation:  Flexibility of What Components to Load

    Each component on the panel corresponds to a set of minidisks
    which are required to load the given component.  When the user
    chooses one of the components, the INSTALL exec checks the
    virtual machine to ensure that all the required minidisks exist,
    are read/write, are of the correct device type, and are the right
    size.  Once the checks are complete, the next menu is presented.
    (LOAD DEVICE MENU).

o   Feature:  Ability to use Multiple Tape Drives to Load the Tapes.

    Prior to this new procedure, there was no method to utilize more
    than one tape drive when installing.  This would force the
    installer to have to wait for a prompt to mount the subsequent
    tapes.  This in itself made the old install method a manual task.
    The new procedure presents a panel (LOAD DEVICE MENU) that tells
    the installer which volumes to mount and accepts as input what
    address he wishes to load the tapes from.  The panel will still
    accept one address for each volume, should there only be one tape
    drive.  This allows for a totally automated install since once
    the input is given, the exec knows where to load each tape from
    and will do so until all components have been...