7. Writing Field-developed Applications › 7.3 Writing the Code › 7.3.1 Define the Application (fdaGENIN) › 7.3.1.1 Define the Application (UNPGENIN)

7.3.1.1 Define the Application (UNPGENIN)

The statements listed below define a field-developed Network
Performance application (UNP) with one file, the Network
Control Program File (UNA).

These statements are presented here to illustrate
field-developed application definition.  This description of
the UNP product does not look like the definition shown in
Section 4.2.6 of this guide because the names of the product,
information area, files, and data elements were changed to
simulate the coding techniques you would use in coding your
own network performance field-developed application.


*********************************************************
*        E X A M P L E   U N P   P R O D U C T          *
*********************************************************

Hypothetical contents of sharedprefix.MICS.GENLIB(UNPGENIN):

*
* UNP component generator statements
*
* The following GEN statement causes the MCG to generate
* documentation shells and file description members.
*
GEN GENSHELL

*
* If an OPTION statement existed, it would be placed here.
*
*  The COMP statement identifies the UNP product.  This
*  product is step 150 of the CA MICS operational jobs, so
*  the UNP update step of the CA MICS DAILY job, for example,
*  would be step DAY150.  The input source for reading UNP
*  data is a VBS data set of default blocksize.  The
*  accounting component will not be active for UNP (because
*  there is no user-related identifier on any NPA data).
*
COMP UNP 150 32000 VBS NOACCT User NPA Component
COMPOPT DEFAULT DEFAULT
COMPJOB DWMY EDWM AWM
INPUTSOURCE SMF 37
DBMDATA1
*
* The following elements are common to UNP files.
*
TYPE XR  3 . 3 . 3 .
NAME UNPNRRLS  Receiving Line Speed (line/link)
NAME UNPNRSLS  Sending Line Speed (line/link)
TYPE XA  5  TIME11.2  6  TIME15.2  6  TIME15.2
NAME UNPTMAOT  Actual Observation Time
TYPE XR  4  TIME8.  4  TIME8.  4  TIME8.
NAME UNPTSEIS  Expected Interval Time
NAME UNPTSFRU  Foreward RU Send Time
NAME UNPTSLOG  Time Record Logged To SMF
*
* UNP's information area is also called UNP.

*
AREA UNP User NPA Activity Information Area
*
*  This FILE statement describes the  UNP area's User NCP
*  Activity File (UNA).  It is a standard CA MICS file (the
*  type 00 after UNA), is not considered for introduction to
*  the YEARS time-span, and has no archive audit application.
*
FILE UNA 00 1 Y Y Y Y N N Y Y User NCP Activity File
FOPT DEFAULT DEFAULT STD
CYCLES 10 33 26 06 00 00 054 024
COMPRESS Y Y Y Y N

*
*  Include common elements.
*
NAME UNPNRRLS     99  0 N N N N
NAME UNPNRSLS     99  0 N N N N
*
*  The next four data elements are retained numeric, saved on
*  the CA MICS database in the UNPUNA files with a length of
*  3 bytes.
*

TYPE R 3 . 3 . 3 .
NAME UNANRFBQ     00  0 0 0 0 0 Free Buffer Queue Length
NAME UNANRHQL     00  0 0 0 0 0 NCP Channel Hold Queue Length
NAME UNANRIQL     00  0 0 0 0 0 NCP Channel Intrmd Queue Len.
NAME UNANRSFB     00  0 0 0 0 0 Free Buffer Count At Slowdown
*
*  The next data elements are accumulated numeric elements,
*  and will be summed in the generated summarization process.
*  Elements kept in time-spans higher than DETAIL should have
*  a slightly larger saved  data element length to ensure
*  that they contain all the precision  pertinent to the data
*  element.

*
*  Note that a numeric time data element of length 6 can
*  contain enough precision to carry a year of elapsed time.
*  The format length also changes with the increased length.
*
TYPE A 5 TIME11.2 6 TIME15.2 6 TIME15.2
NAME UNATMFCT     00  0 0 0 0 0 Free Cycle Time
NAME UNATMTIS     00  0 0 0 0 0 Time In Slowdown
TYPE M 3 . 3 . 3 .
NAME UNAMXANP     00  0 0 0 0 0 Max Available NCP Buffers
NAME UNAMXFBH     00  0 0 0 0 0 Free Buffer High Water Mark
TYPE N 3 . 3 . 3 .
NAME UNAMNFBL     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 time-spans of the UNPUNA
*  file.  DAY, below, appears in the DETAIL and DAYS
*  time-spans, but is dropped from the file in WEEKS and
*  MONTHS.  If this file were active in the YEARS time-span
*  (which it is not), DAY would have been dropped there, too.
*  Further, DAY is a part of the key structure for the UNPUNA
*  file.  In the DETAIL and DAYS time-spans, 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 .
*

  End of example for UNPGENIN