5. DATABASE FILES › 5.4 TCP Information Area › 5.4.2 Telnet Client File (TCPCTN) › 5.4.2.3 Usage Considerations

5.4.2.3 Usage Considerations

This section identifies special considerations or techniques
related to using the TCPCTN file, as well as a retrieval
example to facilitate the use of this file.

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.


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.

Special Considerations/Techniques

1. The Telnet Client (TCPCTN) File is built by selecting data
   from SMF record type 118 and/or SMF record type 119. The
   data of type LGON and LGOF from SMF type 118 records.
   Care must be exercised when combining observations from
   other TCP files to avoid duplication.
 
   The data from SMF record type 119 subtype 23 (TSO Telnet
   client connection termination record) is also used to
   populate this file. This record provides several new
   metrics that are not available in SMF 118 records.
 
   Consult your z/OS CS system programmer to turn off SMF
   record type 118 and to activate SMF record type 119.  This
   will improve your DAY056 job performance.

1. This file is really designed for use only at the DETAIL
   timespan.  The following data elements lose significance
   once summarization has been performed, reducing the
   usability of this file.

   o CTNNODE  - NJE Node Name
   o TCPIPTYP - TCP/IP Type
   o TCPLADDR - Local IP Address
   o TCPLPORT - Local Port Number
   o TCPRADDR - Remote IP Address
   o TCPRPORT - Remote Port Number

2. The following data elements are user-defined.  The value
   in each depends on user-selected options or user-supplied
   SAS code:

   o NETWRKID - Network Identifier.  A one to eight-character
     descriptive name for each network represented
     in the data.  NETWRKID is set in the Network Identifier
     Exit Routine, SNTNIDRT, discussed in Chapter 7.

   o TMOFFSET - TIME OFFSET applied to the data in the file.
     The user can associate a TIME OFFSET with each unique
     NETWRKID/SYSID combination.  This offset is used to
     adjust data times when data from multiple time zones is
     brought together in the CA MICS database. To determine
     the original time at which the data was recorded,
     subtract TMOFFSET from the value.  TIME OFFSET is
     assigned in the SNTOPS member of prefix.MICS.PARMS,
     discussed in Chapter 7.


Retrieval Example

Report on the frequency of TCP/IP Telnet Client remote access
for yesterday.  This will report the type of activity which
occurred, by Remote IP Address.

   PROC FREQ DATA=&PTCPX.TCPCTN01 ;
        TABLES TCPRADDR * TCPIPTYP / LIST;
   TITLE1 'TCP/IP Activity By Remote Address';
   RUN;

Report on the frequency of TCP/IP Telnet Client local access
for yesterday.  This will report the type of activity which
occurred, by Local IP Address.

   PROC FREQ DATA=&PTCPX.TCPCTN01 ;
        TABLES TCPLADDR * TCPIPTYP / LIST;
   TITLE1 'TCP/IP Activity By Local Address';
   RUN;