Visara LINCS Features - Manual (Page 122)

112
LINCS Features
707021-001
• 400 series events will be logged in the Event Logs, indicating the status of Change
Management functions. These events are documented in the LINCS Problem Determination
manual.
• SNA sense codes may appear on an SNA negative response, in a function management
header type 7 (FMH-7), in an inbound unbind request, or in a Sense Data MS common
subvector. The SNA sense codes are documented in the LINCS Problem Determination
manual.
Preparing for CSCM Function
Before using CSCM to distribute LINCS Gen-C microcode and customization data, all LINCS
nodes which will be receiving the data should be running LINCS C1.0 or greater. LINCS
nodes running Gen-B are not capable of receiving Gen-C data objects electronically.
The CSCM functions are implemented using NetView DM commands on an LU type 6.2
session. NetView DM Version 1, Release 2 or higher, may be installed on any IBM processor
capable of operating with MVS, ACF/VTAM, or ACF/TCAM.
LU address 01 on the CSCM host in a LINCS node will support the LU6.2 protocol. This LU
will have to be defined to ACF/VTAM for each LINCS node that will support CSCM. The
LUNAMES defined to ACF/VTAM should match the LUNAMES defined at the LINCS nodes.
Refer to the NetView DM Installation Manual for details on how to define the Logical Unit
and the Logon mode.
Data Objects and Canonical Names
The various types of microcode and customization data distributed by CSCM are referred to
as data objects. There are two types of data objects, Microcode data objects and Customization
data objects. The following sections further describe each type of data object.
Each data object is uniquely identified by a structured name which is known as the data object’s
canonical name. This is the name which must be supplied to NetView DM in order to distribute
the data objects.
A canonical name consists of several tokens (or fields) separated by a period. The content of a
token varies depending on the data object. The sections which follow give the canonical name
format for the LINCS microcode and customization data objects.
Microcode Data Objects
Microcode data objects contain the microcode which controls the operation of the LINCS
nodes and its attached devices. These data objects are provided on diskettes. The canonical
names are built as follows:
• Token 1 must always be MCODE for Microcode data objects.
• Token 2 is used to identify the product such as 9300 or 1174.
• Token 3 is not used and must always be NA.
• Token 4 identifies the type of release as follows:
• FUNCTEC identifies a new functional release of LINCS microcode. A whole number
release such as C3.0 contains major new functions and features while a decimal number
release such as C3.1 contains smaller features.