User`s guide

Create a file that maps long names to short names. Use the messages produced in the preceeding step and the
table and variable name definitions in !SASROOT/misc/cpe/cssnmnam as a guide (note that the message
produced by %CSSNMSCH in the SAS log are of a form that they can be cut and pasted directly into the file that
maps long names to short names. Just type over UNKNOWN with a correct name. There are rules regarding table
and variable names for IT Service Vision. They are:
User defined table names for IT Service Vision should begin with "U" and have exactly four more
alphanumeric characters.
Both table and variable names should consist of letters and numbers only (no underscores!).
User-defined variables should be 7 or fewer characters long.
Loop through these steps until all table and variable names have been defined properly.
3. Resolve error messages produced by %CSSNMSCH
A number of things can go wrong with converting a schema file to IT Service Vision dictionary definitions even after the
names and rpc ids are resolved. These problems are principally caused by the schema file not being totally syntactically
correct. To get around these problems, do the following:
Run the %CSSNMSCH macro against your schema file again.
If you get no error messages, continue with step 4.
If you get error messages, edit the schema file as indicated in the messages. The kinds of error messages to expect
are:
Malformed BY list. The BY list is called the key in the schema file -- it is used to set the order of
observations in the DETAIL data (useful when reporting on the data) and to recognize duplicate
observations. Since SunNet Manager does not depend on the BY list being correct (or even present) for
tables, it many times is not. Edit the schema file to supply the correct BY list after the "characteristics-k"
statement.
Too many variables defined in a table. If you get a message about too many variables, change the
declaration for the vnam, long, and sort arrays in the %CSSNMSCH macro to something larger and try
again.
Schema format errors. %CSSNMSCH is more sensitive to some deviations from schema format rules than
SNM is. If errors of this type occur, %CSSNMSCH issues messages on the SAS log that are usually self-
explanatory if you examine the schema file carefully.
Unknown BY-group variable. Until all variable long names are mapped to short names (see step 2 above),
this message will appear for the variables in the BY list. Once all long-to-short names have been mapped,
this message probably means that the BY-list variable is misspelled in the schema file. A common
misspelling involves case mismatch: "-k ifIndex" sometimes is in the BY list definition when "IfIndex" is
in the variable definition. Correct the BY list spelling and rerun %CSSNMSCH.
Sometimes variations from standard syntax (such as unbalanced parentheses or quotes, or certain special
characters) will confound %CSSNMSCH and error messages will be confusing. The easiest way to solve
these problems is to examine the schema file for anomalies around the point the error messages occur.
Loop through these steps until messages have been resolved.
When all messages are resolved, %CSSNMSCH will create, in the specified OUTFILE, the %CPDDUTL statements to
define the tables and variables for the schema file.