4. CA MICS Facilities › 4.2 CA MICS Component Generator (MCG) › 4.2.6 MCG Illustrations

4.2.6 MCG Illustrations

The statements listed below define the Network Performance
Analyzer (NPA) with one file, the NCP Activity File (NCP).

The examples in this chapter are based on a network
performance analysis (NPA) component that was superseded
entirely by the CA MICS SNA Network Analyzer. The references
to the NPA Component in this chapter provide an illustration
of how such tailoring operations would apply to any
hypothetical CA MICS component.

*
* The following GEN statement causes the MCG to generate file
* description members only.
*
GEN GENFILES
*
* The COMP statement identifies the NPA component.  This
* component is step 050 of the CA MICS operational jobs, so
* the NPA update step of the CA MICS DAILY job, for example,
* would step DAY050.  The input source for reading NPA data
* is a VBS data set of default blocksize.  The accounting
* component will not be active for NPA (because there is no
* user-related identifier on any NPA data).
*
COMP NPA 050 32000 VBS NOACCT NPA Component
*
* If COMPOPT, COMPJOB, INPUTSOURCE, or DBMDATA statements
* existed, they would be placed here.
*
* If an OPTION statement existed, it would be placed here.
*
* The following elements are common to NPA files.
*
TYPE XR  3 . 3 . 3 .
NAME NPANRRLS  Receiving Line Speed (line/link)
NAME NPANRSLS  Sending Line Speed (line/link)
TYPE XA  5  TIME11.2  6  TIME15.2  6  TIME15.2
NAME NPATMAOT  Actual Observation Time
TYPE XR  4  TIME8.  4  TIME8.  4  TIME8.
NAME NPATSEIS  Expected Interval Time
NAME NPATSFRU  Foreward RU Send Time
NAME NPATSLOG  Time Record Logged To SMF
*
* NPA's information area is also called NPA.
*
AREA NPA NPA Activity Information Area
*
* The following FILE statement describes the NCP Activity
* File.  It is a standard CA MICS file (the 00 after NCP),
* is not considered for introduction to the YEARS timespan,
* and has no archive audit application.
*
FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File
*
* If FOPT, CYCLES, or COMPRESS statements were needed, they
* would be placed here.
*
* The next 4 data elements are retained numeric and are saved
* on the CA MICS database in the NPANCP files with a length
* of 3 bytes.
*
TYPE R 3 . 3 . 3 .
NAME NCPNRFBQ     00  0 0 0 0 0 Free Buffer Queue Length
NAME NCPNRHQL     00  0 0 0 0 0 NCP Channel Hold Queue Length
NAME NCPNRIQL     00  0 0 0 0 0 NCP Channel Intrmd Queue Len.
NAME NCPNRSFB     00  0 0 0 0 0 Free Buffer Count At Slowdown
*
* The next data elements are accumulated numeric elements.
* They will be summed in the generated summarization process.
* The saved data element length in timespans higher than
* DETAIL should be slightly larger to ensure that precision
* is not lost.  The format length also changes with the
* increased length.
*
TYPE A 5 TIME11.2 6 TIME15.2 6 TIME15.2
NAME NCPTMFCT     00  0 0 0 0 0 Free Cycle Time
NAME NCPTMTIS     00  0 0 0 0 0 Time In Slowdown
TYPE M 3 . 3 . 3 .
NAME NCPMXANP     00  0 0 0 0 0 Max Available NCP Buffers
NAME NCPMXFBH     00  0 0 0 0 0 Free Buffer High Water Mark
TYPE N 3 . 3 . 3 .
NAME NCPMNFBL     00  0 0 0 0 0 Free Buffer Low Water Mark
*
* The following data elements are common to files in more
* than one CA MICS product. The type and label descriptions
* for those data elements are contained on
* sharedprefix.MICS.GENLIB($DEGENIN).  Common data elements
* are generically named, according to their purpose or
* content, such as DURATION.  It is not necessary to code
* labels for common data elements.  A period (.) is coded to
* note the absence of a label.
*
NAME RESNAME      99  0 0 0 0 0 .
NAME MICSVER      99  0 0 0 0 0 .
*
* MICSVER, above, appears in all timespans of the NPANCP
* file.  DAY, below, appears in the DETAIL and DAYS
* timespans, but is dropped from the file in WEEKS and
* MONTHS.  If this file were active in the YEARS timespan
* (which it is not), DAY would have been dropped there too.
* Furthermore, DAY is a part of the key structure for the
* NPANCP file.  In the DETAIL and DAYS timespans, DAY is the
* 5th data element in the key.

NAME DAY          99  5 5 N N N .
NAME HOUR         99  6 6 6 N N .
NAME WEEK         99  0 0 4 N N .
NAME YEAR         99  3 3 3 3 3 .
NAME MONTH        99  4 4 N 4 N .
NAME INTERVLS     99  0 0 0 0 0 .
NAME DURATION     99  0 0 0 0 0 .
NAME STARTTS      99  0 0 0 0 0 .
NAME ENDTS        99  7 0 0 0 0 .
NAME ZONE         99  0 0 5 5 4 .
NAME DAYNAME      99  0 0 N N N .
NAME SYSID        99  1 1 1 1 1 .
NAME NCPNAME      99  2 2 2 2 2 .
NAME NETNAME      99  0 0 0 0 0 .
*
* If any of the elements were documented under an alias name,
* the ALIAS statement would precede the NAME or NAMX
* statements.
*
* If any of the elements were computed, the EXP and DEPEND
* statements would follow the NAME or NAMX statements.
*
End of example