Browse Prior Art Database

Naming Approach for Multi-release and Cross System Products

IP.com Disclosure Number: IPCOM000110350D
Original Publication Date: 1992-Nov-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 3 page(s) / 114K

Publishing Venue

IBM

Related People

McGraw, JK: AUTHOR [+2]

Abstract

Unlike some IBM products dealing with mainly one component which is consistent across releases, there are complex program products that have multiple components in it, each component having dependent functions i.e., various languages, fonts, etc. These complex products may also have multiple releases, where more components are being added each release, which increases the complexity exponentially. With a new naming approach for the function sysmod IDs (FMIDs) Release number, which is a part of the FMID, complex program products can eliminate much confusion to the installation and servicing of the program products, and reduce costs in time and resources to the customer and to IBM.

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

Naming Approach for Multi-release and Cross System Products

       Unlike some IBM products dealing with mainly one
component which is consistent across releases, there are complex
program products that have multiple components in it, each component
having dependent functions i.e., various languages, fonts, etc.
These complex products may also have multiple releases, where more
components are being added each release, which increases the
complexity exponentially.  With a new naming approach for the
function sysmod IDs (FMIDs) Release number, which is a part of the
FMID, complex program products can eliminate much confusion to the
installation and servicing of the program products, and reduce costs
in time and resources to the customer and to IBM.

      This disclosure consists of the use of the release number or
REL #, which is the last three digits of the FMID (described below as
rrr).
FMID format is:  TVVVrrr
                 T is the type of function
                 (e.g., licensed base or dependent function)
                 VVV is the unique alpha component ID (e.g., BDG)
                 rrr is the Release number or REL (e.g., 100)

      This new naming approach has two parts.  The first part is the
use of the first digit to specify the release of the program product.
For example:
           Release 1.0    1rr
           Release 2.0    2rr
           Release 3.0    3rr

      The second part of the new naming approach uses the second and
third number to denote a part of the program product component.  This
new naming approach then would be used consistently across each of
the dependent function components.  The base function code would be
00.  The dependent functions that are product specific would be n1,
where n can range from 0-9 and B-Z (no vowels).

      An example of a product-specific type of dependant function is
code that was developed by another group.  Since the REL      is also
used in the RETAIN tracking system change, team members can look at
RETAIN and quickly assess how many of a particular type of REL
have service activity against it.  This naming approach would allow
you to automate reports on the maintenance activity of a program
product.  Language support would be n2, again the range is 0-9 and
B-Z (no vowels), which would allow for 31 different languages that a
component could specify.  Font support would be n3, with the same
range values, etc.
Note: This naming approach assumes that you have used unique
component ID's (VVV in the FMID) and that the third digit (rrr) is
0-9 indicating the use of the MVS system, which is the case in these
examples.

      For a complex program product that has multiple releases, the
REL #s would look like this:
      Release Number      1.0  2.0  3.0  4.0  5.0  6.0
      Component #1 base     100  200  300  400 ...