Browse Prior Art Database

Provide Local Access to Global Initial Program Load Data Set Specifications

IP.com Disclosure Number: IPCOM000118323D
Original Publication Date: 1996-Dec-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Duval, ME: AUTHOR [+4]

Abstract

Disclosed is a method to provide local access to global Initial Program Load (IPL) data set specifications while protecting the user from the need to be aware of the specific data sets or files that make up that information.

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

Provide Local Access to Global Initial Program Load Data Set Specifications

      Disclosed is a method to provide local access to global Initial
Program Load (IPL) data set specifications while protecting the user
from the need to be aware of the specific data sets or files that
make up that information.

      In Today's MVS/ESA* environment installations are required to
use SYS1.PARMLIB to house the system initialization parameters used
during IPL and by various system/vendor programs during the life of
that IPL.  Originally, when only the operating system required
initialization parameters, this one data set situation was
acceptable.  However, as systems have evolved and become more and
more complex, more and more system functions and now vendor and/or
installation programs require initialization parameters.  The system
initialization parameter data set has provided a good consolidation
point for this information but is now pushing the limits of its
usefulness.

      The growth in the number of initialization parameters and the
growing diversity of the programs requiring these parameters has led
to service and integrity concerns.

      The solution to these problems was to allow the data set which
contains the system initialization parameters to be a logical data
set rather than a physical data set.  The logical data set can be
made up of  various data sets with no naming conventions.

      This solves the service and integrity problems.  However, it
creates another problem.  Today there is no ambiguity about where
initialization parameters reside.  They will always be in
SYS1.PARMLIB.  With the new logical data set, it's anyone's guess
where the initialization parameters reside.  Visibility and access to
these initialization parameters is very difficult.

      The solution to this new problem is to provide local visibility
and access (e.g., in another address space) to the system parameter
specifications that were previously available only from a Master
source.  This is done by providing the ability to obtain the data
(e.g., IPL parameters, etc.) without needing to know which physical
data set within the logical data set contains the required data.  In
MVS this is accomplished by:
  o  During IPL/NIP processing the system determines which data
      sets have been specified by the installation for in...