Browse Prior Art Database

Stand-Alone VSE Driver

IP.com Disclosure Number: IPCOM000114271D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 4 page(s) / 85K

Publishing Venue

IBM

Related People

Barthold, H: AUTHOR [+3]

Abstract

It is a complex and time consuming task to get an inoperative VSE/ESA* system ready to run. During this work multiple VSE/ESA specific actions have to be initiated on the system console. Detailed skill about VSE/ESA internals and VSE/ESA specific system commands is needed. This task may be performed as part of: o system software network distribution o partial operating system software replacement o initial installation of the operating system (see Automated VSE/ESA System Installation) o disaster error recovery actions o offline data loading onto DASDs o operating system independent preparation of direct access storage devices (hardware)

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

Stand-Alone VSE Driver

      It is a complex and time consuming task to get an inoperative
VSE/ESA* system ready to run.  During this work multiple VSE/ESA
specific actions have to be initiated on the system console.
Detailed skill about VSE/ESA internals and VSE/ESA specific system
commands is needed.
  This task may be performed as part of:
  o  system software network distribution
  o  partial operating system software replacement
  o  initial installation of the operating system (see Automated
      VSE/ESA System Installation)
  o  disaster error recovery actions
  o  offline data loading onto DASDs
  o  operating system independent preparation of direct access
     storage devices (hardware)

      Any combination and sequence of following actions must be
performed without an up-and-running operating system available:
  o  initialization of direct access storage devices
  o  analysing, scanning and testing of direct access storage devices
  o  IBM system code loading onto devices
  o  user data and/or code loading onto devices

      The Stand Alone VSE Driver (SAVD) is a mechanism to define a
sequence of those actions and execute it later with almost no human
intervention.

      The definition of those actions with accompanying user defined
messages is done in batch mode on a running VSE/ESA system.

      The result is an IPL tape suitable to execute the predefined
sequence of actions without a running operating system available.

      The amount of manual intervention after the tape has been
IPL'ed may be minimized up to zero.

      SAVD is a feature to run a sequence of actions, the sequence is
unlimited, the set of actions is limited.  The run is in a kind of
'unattended mode', as there is no need of interactively requesting
any information from the person monitoring the process.
  SAVD is composed of two parts:
  1.  a driver routine, initiating and controlling all actions after
       IPL from the driver tape
  2.  a customization table containing all information used to execute
       the predefined sequence of actions.

      Driver routine - The driver is composed of 3 parts running on a
minimal subset of the VSE/ESA operating system:
  o  a set of utility programs to perform the tasks
  o  a control program to initiate and monitor the utilities.
 ...