5. FILES › 5.16 SRL Communications Controller Rel. (SRLNTC) File › 5.16.3 SRLNTC Usage Considerations

5.16.3 SRLNTC Usage Considerations

This section identifies any special considerations or
techniques related to using the SRLNTC file.  Additionally,
a sample retrieval example is provided to facilitate
the use of this file.

The SRLNTC file is made up of information from seven types of
records.  The field RECMODE will indicate the source of each
observation.

RECMODE can take on the following values depending on the
type of record encountered:

'80'X - Record Maintenance Statistics (RECMS) RU Format for
        Permanent BSC/SS or Line Errors.

'81'X - Record Maintenance Statistics (RECMS) RU Format for
        BSC/SS Station Statistics.

'82'X - Record Maintenance Statistics (RECMS) RU Format for
        SNA Link Permanent Errors.

'83'X - Record Maintenance Statistics (RECMS) RU Format for
        SNA Station Permanent Errors.

'84'X - Record Maintenance Statistics (RECMS) RU Format for
        BSC 3270 Status/Sense.

'86'X - Record Maintenance Statistics (RECMS) RU Format for
        SNA Statistics.

'A3'X - Record Maintenance Statistics (RECMS) RU Format for
        Intensive-Mode Record for SNA Recoverable Errors.

Whenever you find missing values for the observations, it
means that field is not valid for that type.  For
example, the field NTCTCNT is valid for an observation when
RECMODE = X'80', but will be missing when RECMODE is X'82' as
that field is not present in the data.  When writing reports
using the SRLNTC file, this information may be important.

A number of fields consist of bit patterns represented
as hexadecimal values.  The following method is normally used
to test bit patterns in SAS.

Example:

Let us assume that the variable NTCDFEAT that contains the
Device Features has a value of X'4080' and we want to report
on whether a Critical situation notification has
occurred.

From the Data Dictionary description for NTCDFEAT we know
that this field is valid only when RECMODE is X'80' or
X'81'.  We also know the bit pattern for Critical situation
notification is that byte 2 should have the following
pattern '1.......'.  So our code would look as follows:

DATA CRITICAL;
SET DETAIL.SRLNTC01;
IF RECMODE EQ 80 OR RECMODE EQ 81;
IF NTCDFEAT EQ '........1.......';
RUN;


In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan.  For the examples, a database
identifier of P is used.  The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.