Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Production Environment Product Conversion Facility

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

Publishing Venue

IBM

Related People

Calvert, N: AUTHOR [+2]

Abstract

Described is a mechanism for packaging software such that the boundaries of the software are not limited to the product containers.

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

Production Environment Product Conversion Facility

      Described is a mechanism for packaging software such that the
boundaries of the software are not limited to the product containers.

      On most systems today, application software is loosely
packaged.  In most instances, this software resides in system
containers and the containers, therefore, define the boundary
(content) of the software.  The AS/400* has developed a mechanism for
packaging software such that the boundaries of the software are not
limited to the containers (libraries for Licensed Programs (LPs),
segment groups for Licensed Internal Code (LIC)).  Most software
today is not packaged using the packaging structure defined in the
Figure, therefore, the software is not enabled to use generalized
system software LP and LIC management functions
  o  install LP
  o  display LP
  o  distribute LP
  o  service LP electronically
  This uses problem identifications based on symptom string
   support and electronic fix distribution using AS/400 Program
   Temporary Fixes (PTF).

      It is desirable to enable any application for AS/400 LP
management.  Converting non-packaged applications into LPs enables
the converted LP to use the system's software management facilities
which exist for AS/400 'packaged' LPs.

Note:  A software LP is software which performs a well defined set of
functions.  The AS/400 provides a mechanism for managing software LPs
if they are properly packaged.

      This disclosure concentrates on the support required to convert
application software in a production environment to a 'packaged' LP
and, thereby, enabling it to be managed via IBM's AS/400 system
management functions.

      This disclosure defines how the LP implemented on the AS/400
may be imbedded within any software application installed on the
system.  This disclosure is aimed at applications on the AS/400, but
the concept is consistent across any system which provides
Application Program Interfaces (APIs) for managing LPs that are
packaged according to the Figure.

Implied within the Figure is a set of relationships (ownership and
shareability relationships):
  1.  Ownership relationship - Identifies how each lower level
belongs
       to its parents.  An LP may have multiple options which in turn
       may have multiple loads which in turn may have multiple
objects.
       Each lower level entity in the hierarchy may only have a
single
       owner within the hierarchy.  In essence an object can only be
       owned by a single LP load, a LP load can only be owned by a
       single LP option.
  2.  Shareability relationship - Shareability is defined as
functional
       dependencies (hardware or software) required by an LP to
properly
       function.  For example, a secondary option of an LP is usually
       dependant upon the primary option of the LP.  The primary
option
       is...