7. Writing Field-developed Applications › 7.3 Writing the Code › 7.3.1 Define the Application (fdaGENIN) › 7.3.1.2 Define the Application (ZTMGENIN)
7.3.1.2 Define the Application (ZTMGENIN)
The statements listed below define an MSI field-developed
application for VTAM Tuning Statistics (ZTM), derived from
the MXG file TYPE50, with one file VTAM Tuning Stats (ZTS).
These statements are presented here to illustrate
field-developed application definitions.
Please refer to Section 4.2.4.3 within this guide for
information on the required order of these statements.
* MICS6
* READ DATA FROM MXG FILES created from the SMF Type 50 00001000
* 00003000
*********************************************************
* E X A M P L E Z T M P R O D U C T *
*********************************************************
Hypothetical contents of sharedprefix.MICS.GENLIB(ZTMGENIN):
*
* ZTM component generator statements
*
* The following GEN statement causes the MCG to generate
* documentation shells and file description members.
*
GEN GENSHELL 00004000
*
* If an OPTION statement existed, it would be placed here.
*
* The COMP statement identifies the ZTM product. This
* product is step 198 of the CA MICS operational jobs, so the
* UNP update step of the CA MICS DAILY job, for example,
* would be step DAY198. The input source for reading ZTM
* data is a VBS data set of default blocksize. The
* accounting component will not be active for ZTM (because
* there is no user-related identifier on any VTAM Tuning
* data).
*
COMP ZTM 198 . . NOACCT VTAM Tuning STATS 00005000
COMPOPT DEFAULT DEFAULT 00006000
* 00007000
* In order to use MSI features, you must specify MSI as the
* input source.
*
INPUTSOURCE MSI 00009000
COMPJOB DWMY EDWM AWM 00010000
DBMDATA1 15 100 50 30000 0 0 00011000
OPTION 00012000
* 00013000
* Special options for MSI are set here. Note that options
* specified here are global and will apply to all files,
* and that MSIOPTS can be used after the INPUTSAS statement
* to specify or override options.
*
* In this example, the following options are used:
* SPLITCHAR translates '*' to a space (the * is used in MXG
* as a new line character when printing labels).
*
* FILTER will automatically ignore variables that conflict
* with existing CA MICS variables for specific data sources
*
MSIOPTS SPLITCHAR *
MSIOPTS FILTER MXG
* 00013000
* ZTM's information area is also called ZTM.
*
AREA ZTM VTAM Tuning STATS INFO AREA 00014000
* 00015000
FILE ZTS 00 1 Y Y Y Y Y N Y Y Tuning STATS 00016000
FOPT DEFAULT DEFAULT STD 00017000
CYCLES 07 33 09 06 01 00 053 024 00018000
COMPRESS Y Y Y Y Y 00019000
*
00020000
* The INPUTSAS statement is used to specify the SAS data
* set that will be used as input in the DAYxxx step.
*
INPUTSAS PDB.TYPE50 00021000
* 00020000
* Each file that uses INPUTSAS or INPUTMODEL is designated
* as an MSI file and MUST define ENDTS, STARTTS, and
* ORGSYSID. Failing to specify these data elements will
* result in an error.
*
ENDTS SMFTIME 00030000
STARTTS SMFTIME 00031000
ORGSYSID SYSTEM
00032000
*
* The following statements change a data element's type.
* Here BSIZE is changed to RETAIN, and MXTRSIZE is
* changed to MAXIMUM.
*
RETAIN BSIZE
MAXIMUM MXTRSIZE
*
* The KEEP/DROP statements allow for elements to be removed
* from the file.
*
DROP VERSN50
*
* The SEQUENCE statement (below) sets the user sort sequence
* for the ZTS file. This sequence will apply to all
* timespans. Note that it is unnecessary to specify things
* like MONTH, DAY, YEAR, etc.
*
SEQUENCE SYSID CONTROLR CTCANAME MPCNAME
*
* MSI allows modifications of the sort sequences to specific
* timespans. Here the APPENDSEQUENCE statement adds the
* data element DEV to the sort sequence after MPCNAME, only
* for the detail timespan.
*
DETAIL
APPENDSEQUENCE DEV
End of example for ZTMGENIN
