Browse Prior Art Database

Use of Alias Names to Reference Objects

IP.com Disclosure Number: IPCOM000116444D
Original Publication Date: 1995-Sep-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 6 page(s) / 260K

Publishing Venue

IBM

Related People

DiMarco, TT: AUTHOR [+2]

Abstract

A method for retrieving multiple related objects related by their "familiar" name is disclosed. The objects represent SNA LUs in some form or fashion. That is, the "familiar" name may be an alias for the real LU name or may represent a number of LUs.

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

Use of Alias Names to Reference Objects

      A method for retrieving multiple related objects related by
their "familiar" name is disclosed.  The objects represent SNA LUs in
some form or fashion.  That is, the "familiar" name may be an alias
for the real LU name or may represent a number of LUs.

      OSI Systems Management standards call for the use of objects
such that each object instance is referenced by a single
Distinguished Name (DN).  While this may be perfectly natural in
CMIP's native protocol, it can cause problems in other protocols.
For example, Logical Unit (LU) resources in SNA can be naturally
referenced by a number of "familiar" names:
  o  An LU representing a host application program can be referenced
      by its ACBNAME.
  o  A USERVAR or Generic Resource may be created to represent one or
      more LUs.
  o  An LUALIAS may be defined to represent a Cross-Domain Resource
      (CDRSC).

      Likewise, a single familiar name may apply to more than one
object.  The Systems Manager, needing to reference the object by this
"familiar" name, therefore requires that an agent translate the
familiar name and return the pertinent objects.  In cases where an
alias name represents more than one object, all applicable objects
must be returned.  This cannot be done with the base CMIP GET
operation.

      A special CMIP Action, called Snapshot, was used for this
invention.  The Snapshot Action is defined for use with collections
of objects.  Generally, such a collection is assumed to be related in
some way.  The objects in question here, may not be related at all
except that they happen to share the same name.  There could be, for
example, a CDRSC and an application with the same name.  This is used
for backup purposes and the backup resource is pushed to shadow until
needed.  This invention creates a new form of snapshot, called
luIndex, which finds all objects that share the same name as that
requested in the operation and returns all objects that contain that
name directly or that use that name as an alias.

      The logicalUnitIndex object aids the user in bridging the gap
from traditional SNA management to CMIP as well as adding additional
search capabilities to better manage dynamic networks.  CMIP requires
that the user understand the object types before he can issue any
effective requests, that is, he has to know how to build the DN for
the particular object.  Unfortunately, SNA does not always provide
the user with an easy way to determine the correct DN.  The DN for a
CDRSC, LU, and Generic Resource/Uservar are all different.  The SNA
user only knows that he is dealing with some sort of LU and only
knows the 8 character LU name and possibly the NETID.  The
logicalUnitIndex  object provides a mechanism for mapping a generic
LU NETID (Network Indentifier) and LU NAME to the appropriate objects
as known at the host processing the request.

      The logicalUni...