7. PARAMETERS › 7.3 Unit-level Parameters › 7.3.1 Processing Options (SNTOPS)

7.3.1 Processing Options (SNTOPS)

This section shows you how to specify the operational
statements that control CA MICS Network Analyzer processing.

Operational statements are stored in the prefix.MICS.PARMS
cccOPS member, where ccc is the component identifier, and are
incorporated into the CA MICS system by running the
prefix.MICS.CNTL(cccPGEN) job.

*************************************************************
*                                                           *
*  NOTE:  CHANGES to prefix.MICS.PARMS(cccOPS) members      *
*         REQUIRE EXECUTION of prefix.MICS.CNTL(cccPGEN)    *
*         to take effect.                                   *
*                                                           *
*         In addition, any change to parameters that        *
*         impact the DAILY operational job JCL such as,     *
*                                                           *
*         o  changing RESTART NO to RESTART YES,            *
*                                                           *
*         o  WORK parameter changes when RESTART NO is in   *
*            effect,                                        *
*                                                           *
*         o  Specifying TAPEfff (if this product supports   *
*            a DETAIL level TAPE option),                   *
*                                                           *
*         o  or changes to prefix.MICS.PARMS(INPUTccc),     *
*                                                           *
*         will require regeneration of the DAILY job by     *
*         executing prefix.MICS.CNTL(JCLGEND) or by         *
*         specifying DAILY in prefix.MICS.PARMS(JCLGENU)    *
*         and executing prefix.MICS.CNTL(JCLGENU).          *
*                                                           *
*         Refer to the checklist (if provided) for updating *
*         cccOPS parameters and running required generation *
*         jobs.                                             *
*************************************************************


The SNTOPS member contains the following statements,
described in detail below.  A worksheet for recording the
statement values for SNTOPS is shown in Figure 7-4.

Required Statements
-------------------

  NETWORK ID
  ORGSYSID
  TIME OFFSET or DEFAULT TIME OFFSET
  DATA SOURCES or DEFAULT DATA SOURCES

Optional Statements
-------------------

  SNTNAC SUSPEND
  NVSNSC SUSPEND
  TCP    SUSPEND
  IBMTCP SMF or DEFAULT IBMTCP SMF
  NETSPY SMF or DEFAULT NETSPY SMF
  NETTCP SMF or DEFAULT NETTCP SMF
  DELETEMS or DEFAULT DELETEMS
  WORK
  MULTWORK/NOMULT
  RESTART
  INCRUPDATE

Unless otherwise specified, the following are general rules
for coding all statements above:

o  Blank statements are permitted.  Code comments by
   beginning the statement with an asterisk (*).

o  The SNTNAC, NVSNSC, TCP suspend keywords are global and
   may be specified anywhere within the SNTOPS member.  Since
   the keywords are global, they should be specified only
   once.  If they are specified more than once, the last
   specification will be used as the suspend limit.  If they
   are not specified at all, the default is 30.

o  The WORK, MULTWORK/NOMULT, RESTART, and INCRUPDATE
   keywords are also global, may be specified anywhere within
   the SNTOPS member, and should be specified only once.  If
   they are specified more than once, the last specification
   will be used.

o  The NETWORK ID parameter must be the first parameter
   defined in the ORGSYSID group.

o  Only one NETWORK ID parameter is required (even for
   multiple ORGSYSID parameters).

o  You must code the options in the order indicated on the
   worksheet shown in Figure 7-4.

o  Required statements associated with each ORGSYSID are:

   - TIME OFFSET
   - DATA SOURCES

o  The DEFAULT IBMTCP SMF, DEFAULT NETSPY SMF, and DEFAULT
   NETTCP SMF statements are coded after the first NETWORK ID
   statement and before the first ORGSYSID statement.

o  The IBMTCP SMF, NETSPY SMF, or NETTCP SMF statement is
   required when, respectively, NSPY, NTCP, or TCP is coded
   with a DATA SOURCES statement, and one of the following is
   true:

   - The DEFAULT IBMTCP SMF, DEFAULT NETSPY SMF, and DEFAULT
     NETTCP SMF statement is not defined.

   - The DEFAULT IBMTCP SMF, DEFAULT NETSPY SMF, and DEFAULT
     NETTCP SMF statement is defined but you need to
     override the default for a particular ORGSYSID.

A sample SNTOPS member describing input from a multiple
domain network with three host processors in different time
zones is shown below.  The three network monitor hosts are
Q033, P168, and XTRA.  Note that CA NetSpy data is being
processed from XTRA and that the session records between
terminals and the multiple session manager are to be dropped.

*  SAMPLE CA MICS NETWORK ANALYZER OPTIONS

     SNTNAC SUSPEND 15
     NVSNSC SUSPEND 15
     NETWORK ID NETWORK1
       DEFAULT NETSPY SMF = 132
       DEFAULT NETTCP SMF = 132
       DEFAULT IBMTCP SMF = 118
       ORGSYSID Q033
         TIME OFFSET 0
         DATA SOURCES NLDM NPDA NPMN NPMS NPMV NTRI TCP
         IBMTCP SMF = 119
       ORGSYSID P168
         TIME OFFSET 2
         DATA SOURCES NPDA NPMN NPMS NPMV NTRI X25 NTCP
         NETTCP SMF = 144
       ORGSYSID XTRA
         TIME OFFSET -1
         DATA SOURCES NLDM NPDA NSPY TIC3 X25 TCP
         NETSPY SMF = 183
         DELETEMS YES