Setup for IT Service Vision Server

Cabletron SPECTRUM Appendix 6: Mapping SPECTRUM Data Types to an IT Service Vision PDB

To read SPECTRUM data into an IT Service Vision PDB, it is necessary to tell SPECTRUM to write out the same data that you tell the IT Service Vision server to read in. If what is written does not correspond to what is read, the result is generally that %CSPROCES reads no data (or a smaller amount of data than you expected) into your PDB.

In the information that the %CSPROCES macro writes to the SAS log, there are messages indicating the number of observations read at various stages by the %CSPROCES macro and, at the end, a report on the number of observations kept and the date range of the data.

The following is a list of problems that may be indicated in the log, with an explanation of what they mean (and what to do about them):

The message "NOTE: CSIIPDI not initialized" appears.
This message means that some variables that are defined in the IT Service Vision table are not being logged and exported (as attributes) by SPECTRUM.

You will need to edit the SPECTRUM model type to enable logging of these attributes and re-export the data. To edit the SPECTRUM model type, see Cabletron SPECTRUM Appendix 5: Editing Model Types for SPECTRUM.
The message "ERROR: Negative value for counter CSIIPFD=-873173447 is invalid" appears.
Messages like this refer to data in the form of counters (that is, monotonically increasing values). Certain releases of SPECTRUM log negative numbers when the values in the counters become very large. See !sasroot/misc/cpe/cscsivew for a workaround until Cabletron fixes this problem.
The date range of the data that were read is not correct.
At the end of the messages that %CSPROCES writes to the SAS log, there is a report on the number of observations read in this %CSPROCES run and the date range of the data that %CSPROCES kept. If the date range is not what you expect, you may have exported the wrong range.

You can check the date range in the input (specgway.stat) data set by typing this command on the PROGRAM EDITOR window's command line after %CSPROCES completes:
```
fsview specgway.stat
```
and pressing ENTER or RETURN. Then, at the FSVIEW window's command line, type (do not forget the dot "." after datetime):
```
format ts "datetime."
```
and press ENTER or RETURN.

The variable named TS contains the date/time stamp of each observation. These date/time stamps should correspond to the date range that you specified when you exported the data. See Section 1, Task 1: Start the IT Service Vision Server Software, Action 2.b.viii in this chapter to check the Export Range on the Export Definition Description that you used to export the data.
The data were read but no observations were kept.
If the SAS log shows that observations were read by %CSPROCES, for example:
```
NOTE: Processing RECNUM=1000 MACHINE=Rtr1 DATETIME=15JUN96:01:09:02
```
but the report at the end of the log shows that no observations were kept, for example:
```
NOTE:  +---------------------------------------------------------------
NOTE:  | Table   AgeLim  ObsIn  ObsKept   RBDF   LastIn  First-LastKept
NOTE:  |
NOTE:  | CCIRTR    10        0        0   N/A      N/A      N/A
NOTE:  +---------------------------------------------------------------
```
then
- the model types that you exported do not match the IT Service Vision tables that you named on the %CSPROCES macro (or selected, if you defined the process step through the server's interactive interface), or
- the attributes that you exported do not match the variables defined in the IT Service Vision tables that you named on the %CSPROCES macro (or selected, if you defined the process step through the server's interactive interface).
Each of these scenarios is described in some detail below.

Note: Earlier in this appendix we dealt with the case of not exporting variables for the tables that you named on the %CSPROCES macro. This case is the reverse of that: not defining the correct variable for an exported attribute.
- Investigate whether the IT Service Vision table that you are using is the correct one for the SPECTRUM model type that you are using.
  A SPECTRUM model type is mapped to an IT Service Vision table by matching the SPECTRUM model type handle and the IT Service Vision Table ID Number (TABIDNUM). The following steps walk you through checking these values and making the required corrections if they do not match:
  1. Creating a few SAS formats that map model handles and model type handles to each other and to their names will help you make sense of the specgway.stat data set.
    In the SAS PROGRAM EDITOR window, type the following starting at the first line in the body of the window:
```
/* This assumes that you have exported the model type, model, and
   statistics data sets and that they are in the directory that the
   specgway libref points to, and that they are named
   specgway.modtyp, specgway.model, and specgway.stat .  */

libname specgway '/usr/spectrum/export.output' ;

filename temp temp;

/* Map SPECTRUM model type handle to model type name */
data _null_;
   set specgway.modtyp end=lastrec;
   file temp; if _n_=1 then put 'proc format;
   value mth2mtn';
   put mth '="' mtname '"';
   if lastrec then put '; run;';
run;
%include temp;

/* Map SPECTRUM model handle to model type name */
data _null_;
   set specgway.model end=lastrec;
   file temp;
   if _n_=1 then put 'proc format; value mh2mtn';
   put mh '="' mth mth2mtn. '"' ;
   if lastrec then put '; run;';
run;
%include temp;

/* Map SPECTRUM model handle to model type handle */
data _null_;
   set specgway.model end=lastrec;
   file temp;
   if _n_=1 then put 'proc format; value mh2mth';
   put mh '=' mth;
   if lastrec then put '; run;';
run;
%include temp;
```
    and submit the program (by typing SUBMIT on the command line and pressing ENTER or RETURN) after the %CSPROCES macro completes.
    1. When the program completes (as indicated in the SAS log), issue this command
      fsview specgway.stat
    2. Type bye.
    To include the file in the PROGRAM EDITOR window, issue this command:
```
spectrum.gs
```
  2. If the FSVIEW window has pull-down menus, select Globals, Options, and Command line to get a command line. To see the model names that are in the data, at the FSVIEW window's command line prompt type this:
```
format mh 'cscmo2x.'
```
    and press ENTER or RETURN. The variable named MH contains the model handle. These values are now displayed as a names rather than numbers. Scroll down through the data observing the names now show in the model handle field. These should be the models you exported. If they are not, check your Export Definition Description and your model definition in SPECTRUM.
  3. To display the names of the model types to which these models belong, at the FSVIEW window's command line prompt type this:
```
format mh 'mh2mtn.'
```
    and press ENTER or RETURN. Model type names now display for the values of MH.
    
    These should match exactly the external names of the tables in your PDB. To check the external names, follow this path from the IT Service Vision main window:
    
    Administration -> Manage Tables -> select the table -> click right mouse button -> Properties -> Advanced
    
    The IT Service Vision table's external name is in the External Name field. These table names should be the ones specified in the %CSPROCES macro or in the GUI when selecting Administration -> Process Data - Wizard.
  4. If the model type name matches the table's external name exactly (case sensitive), but data did not read into the table during the %CSPROCES run, you need to compare the model type handle of the models in the specgway.stat data set to the IT Service Vision table IDs.
    To see the model type handles (instead of the model type names) of the data in the specgway.stat data set, at the FSVIEW window's command line prompt type this:
```
format mh 'mh2mth.'
```
    and press ENTER or RETURN. The values for MH now display as model type handles.
    
    Compare this number to the ID number of the corresponding IT Service Vision table. To check table ID numbers, follow this path from the IT Service Vision main window:
    
    Administration -> Manage Tables -> select a table -> click right mouse button -> Properties
    
    and look in the ID Number field, which is approximately in the middle of the window.
    
    The table's ID Number needs to match the model type handle in the specgway.stat data set.If it does not match, you need to replace this IT Service Vision table with the table that does have a matching table ID number. To search all IT Service Vision supplied tables for a table with this table ID Number (model type handle), follow this path from the IT Service Vision main window:
    
    Administration -> Explore Tables/Variables
    
    In the Search field, type TABIDNUM=n, where n is the model type handle. Then select OK. For example, this expression
```
TABIDNUM = 124556
```
    lists the table with TABIDNUM=124556.
    
    To add this table to your PDB, follow this path:
    
    Administration -> Manage Tables -> File -> Add Table Definition -> Collector: Specified -> SPECTRUM -> OK -> scroll to the table name and select it -> click right mouse button -> Add Table to Active PDB
    
    When the Migration in Progress window closes, select Close. The Manage Tables window displays. Notice that the new table is now added to the list of tables in the active PDB.
    
    If you found no supplied table for a given table ID number (model type handle), you need to create a user-defined table. See Cabletron SPECTRUM Appendix 4: Defining IT Service Vision Tables for SPECTRUM Data in this chapter for information on using the %CSATR2DD macro to generate the appropriate CPDDUTL control statements for you from the information in the specgway.stat data set.
- Investigate whether the IT Service Vision variables that you are using are the correct ones for the SPECTRUM attributes that you are using.
  If the IT Service Vision tables that you listed on your %CSPROCES macro match the SPECTRUM model type handles of the models that you exported, but still no observations are kept at the end of the %CSPROCES run, in your IT Service Vision table you may not have variables defined for the attributes you exported.
  
  A SPECTRUM attribute is mapped to an IT Service Vision variable by matching the SPECTRUM attribute ID number and the IT Service Vision Variable ID Number (VARIDNUM). The following steps walk you through checking these values and making the required corrections if they do not match:
  1. You should check the attribute ID numbers that you are exporting in two different places within SPECTRUM: first in the SPECTRUM internal list of attributes to be exported, and then again in the actual exported statistics data set.
  2. To display the SPECTRUM list of attributes to be exported for a particular model, from the Topology View window follow this path
    
    select the model -> View -> Icon Subviews -> Model Information
    
    The list of attributes under "LOGGED" shows the attribute name and attribute ID number of the attributes that are to be exported; for example:
```
TCP_Retrans_Min_Val 1007f
```
    These attribute ID numbers should match the attribute ID numbers in the actual exported statistics data set and in your PDB's data dictionary. Keep this window up so that you can compare attribute ID numbers from these other sources in the next steps.
  3. To display the attribute ID numbers that are in the exported statistics data set, allocate the statistics data set library as you did in Section 1, Task 3: Create a Test PDB and Process, Reduce and Report on Your Data. Then, make the PROGRAM EDITOR window the active window and issue the FSVIEW SPECGWAY.STAT command.
    The window displayed shows the data in the statistics data set. The column labeled TS is TimeStamp; the column labeled MH is ModelHandle. The other columns contain the values of the model's attributes at the indicated time. The hexadecimal representation of the attribute ID number (with the first hex digit translated to a letter or underscore) is used as the label (variable name) for the column. The first character of the variable name is translated as follows:
```
0->_   4->D   8->H   C->L
1->A   5->E   9->I   D->M
2->B   6->F   A->J   E->N
3->C   7->G   B->K   F->O
```
    Thus, values for attribute ID number 65,663 (which is 0x1007f in hex) would appear in a column labeled _001007F.
    
    These attribute ID numbers should match the attribute ID numbers in in your PDB's data dictionary. Keep this window up and go on to the next step to display the variable ID numbers (the IT Service Vision version of the attribute ID numbers) in your PDB's data dictionary.
  4. To display the variable ID numbers for the corresponding IT Service Vision table, follow this path from the IT Service Vision main window:
    
    Administration -> Manage Tables -> select the table -> click right mouse button -> Properties -> select a variable -> click right mouse button -> Properties -> Advanced
  5. The IT Service Vision variable's ID Number (which is in decimal in the Varidnum field) needs to match the SPECTRUM attribute ID number (which is in hex). If it does not, you need to add the correct variable definition to the IT Service Vision table. If this attribute has already been defined in another IT Service Vision table, you can copy the variable definition.
    To search all IT Service Vision supplied variables for one with this attribute ID number, follow this path from the IT Service Vision main menu
    
    Administration -> Explore Tables/Variables -> Collector: All -> Variables
    
    Edit the Search field Clause" expression to select the variable ID number in which you are interested and then select OK. For example, this expression:
```
tablenm=:"C" and varidnum = 01007fx
```
    lists all variables with VARIDNUM (attribute ID number) of 0x01007f in all tables whose names start with "C" (which all supplied SPECTRUM tables do).
    - If there is already at least one variable already defined in IT Service Vision for the attribute of interest, you can copy the variable by following this path from the IT Service Vision main menu
      
      Administration -> Manage Tables -> select the table to which you want to add the variable -> click right mouse button -> List Variables -> Tools -> Copy Variable -> Collector: Selected -> SPECTRUM -> OK -> OK -> scroll to the variable and select it -> click right mouse button -> Copy Variable to Current Table -> Close
      
      IT Service Vision re-displays the list of variables in the table, and the new variable is now in the list. Select Close -> Close -> OK to return to the main window.
      
      Alternatively, you can add the variable to the table by using %CPDDUTL control statements. For more information on running the %CPDDUTL macro, see the Macro Reference documentation for IT Service Vision. Use the form of the CREATE VARIABLE control statement that includes the LIKE= parameter.
    - If you found no supplied variable for a given variable ID number (attribute ID number), you need to create a user-defined variable. See Cabletron SPECTRUM Appendix 4: Defining IT Service Vision Tables for SPECTRUM Data for information on using the %CSATR2DD macro to generate the appropriate CPDDUTL control statements for you.