NTSMF Appendix 1: NTSMF Support Description
The following description of the NTSMF processing assumes that you are running IT Service Vision Release 2.2 with Maintenance Pack 1 installed or higher.
This document walks through the process of recording Demand Technology's NTSMF data into IT Service vision. The following stages will be covered along with working examples.
NTSMF data requirements :-
There are three approaches you can use when starting out with NTSMF data.
For MVS use the following %cpstart.
Once the tables have been added, dictionary characteristics (age limits, variables kept status) can be modified either using the interactive interface or the %CPDDUTL macro.
The NTSMF data can be processed on any platform, MVS, UNIX or Windows NT Server, irrespective of which platform it originated. Once that data is moved to the appropriate platform the processing is identical.
Enhanced NTSMF support is different from the original support that was provided in IT Service Vision Release 2.1 in that it dynamically builds the necessary code to process NTSMF smf files. It uses the NTSMF Discovery records at the head of each file to provide the information on the layout of the NTSMF data records. Different versions of the same software can produce different format NTSMF records, counters are inserted, deleted and appended and the only way to ensure the data is processed correctly is to use the Discovery record. Worse case, each machine on which NTSMF is logging could have different NTSMF record layouts due to different versions of the same software.
If multiple NTSMF smf files are to be passed to IT Service Vision and they all have different layouts, then staging code is built for each separate file. This ensures data integrity, however it also increases the processing time of the data. Fortunately, this is not typically the case, normally organizations have some control over the software and software versions that are installed on the monitored machines and as a result it is possible to group the NTSMF smf files according to common Discovery records. If several NTSMF smf files have the same Discovery record layouts then these can be processed using the same staging code.
To improve processing performance by reducing the number of times the staging code is built IT Service Vision performs an initial scan of all the NTSMF smf files and groups them according to common Discovery record layouts. Once completed each group of files is processed as a single file and the staging code is built only once per group (See note below for information on large volumes of data)..
The following should be considered when processing NTSMF smf files :-
Transferring the Data
For the Enhanced NTSMF support that is provided in IT Service Vision Release 2.2 or higher it is recommended that each NTSMF smf file is maintained as a separate smf file, that is, we do not recommend that they are concatenated together.
Transfer the file to the appropriate platform so that it retains it's text format.
Unix and PC
Place all the NTSMF smf files in a single directory which will be pointed to by the %cpproces macro. No other files or sub-directories should be in this directory.
Place each smf file in its own PDS member with the following DCB attributes DSORG=PO,RECFM=VB,LRECL=32756,BLKSIZE=32760. By specifying the PDS name in the %cpproces macro, each member will be picked up and processed.
If you decide to use Input Filtering, we recommend that you do the following before running your first %CPPROCES :-
If you do not do the above, the first run of %cpproces with Input Filtering active will copy the default %CPDUPCHK invocation into the admin library automatically, and you will receive the following warning message recommending that you review the %CPDUPCHK parameter values.
WARNING: *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ***
If you require more information on Input Filtering please refer to the How To/Macro section from the online help for IT Service Vision.
Processing and Reducing the Data
The following process example should be run a %CPSTART. For the purpose of this example I have included input filtering in this process run. The rawdata parameter on the %CPPROCES macro should point to a directory (on Unix and PC) which contains the NTSMF logs to be processed and a PDS (on MVS).
%put 'CPPROCES return code is ' &cpprc;
%put 'CPREDUCE return code is ' &cprrc;
In the SAS log you can expect to see the following :-
The above message will only appear when Input Filtering is active. The message shown will depend on whether the input data is considered duplicate.
This report is always produced when processing NTSMF data. It reports the objects that were found in the rawdata that were not processed. If an object appears in this report for which you want to collect the data for, then you should add the appropriate table to the PDB. If you do not want to keep the data for an object, you can update your collection process to no longer keep the history data. If an object appears for which there is no supplied table, then one can be constructed using the GENERATE SOURCE function of the %CPDDUTL macro and an INTYPE= parameter of NTSMF.
Occasionally, you may see messages appear in the SAS log similar to the ones below. These messages are produced when new NTSMF counters appear in an NTSMF object that are not defined in the IT Service Vision data dictionary.
WARNING: Process discovery record contains unrecognized metric label: ID Logon . WARNING: Process discovery record contains unrecognized metric label: ID User .
To stop these warning messages appearing you need to add these metrics to the table definition. Cut and paste the NTSMF discovery record for the object in question into a text file and then pass that to Generate Source using the INTYPE=NTSMF to generate a table and variable definitions. You can then use the definitions of the new counters as a starting point for adding them to your PDB.
Messages similar to the following may appear in the SAS log during a %CPPROCES and are caused by variables (in this case ACTVSSN and INCTSSN) being marked as KEPT=YES in the table being processed, however, data for that variable not existing in the raw NTSMF data. In this example, the reason that there is no data for these varaibles in the NTSMF data was becaused the NT machine that was recording this information had an older service pack applied that did not produce values for these counters. This is not a problem and to stop these warnings from appearing just mark the appropriate variables as KEPT=NO.
WARNING: Variable name Active Session in
table NTSSTM is not in data set COLLECT