The unit-level prefix.MICS.PARM(DBMODEL) data retention specifications tell the CA MICS database how many cycles of each file, in each active timespan, to save both online and in archive mode for each database unit. Figure 7-7 is a worksheet for collecting this information for the CA MICS Analyzer for CA-IDMS. Use the worksheet to define your retention specifications, which in turn will allow you to determine the appropriate values for the modeling process. Each file in the IDMS information area is listed by name. For each file, you can modify the default number of cycles of data to be maintained in the six online database files and the two archive database files. o The values you enter for the online database files define the number of cycles of data to be maintained in the DETAIL, DAYS, WEEKS, MONTHS, and YEARS timespans and the TABLES data area. o The values you enter for the archive database files define the number of cycles of data to be retained in the WEEKS and MONTHS archive history files. Note: The archive definitions have no impact on the size of the database and can be specified whether or not the weekly and/or monthly archive history files have been activated in the component's generation definition member (sharedprefix.MICS.GENLIB(cccGENIN)). The worksheet provides underscored areas for your definitions. The underscored areas are followed by the default retention values that initially appear in the prefix.MICS.PARMS(DBMODEL) FILE statements. In the DETAIL timespan, a value of '00' in the underscored area indicates that the file is not normally supported in the DETAIL timespan. To activate the file in the DETAIL timespan, refer to the standard database tailoring techniques described in Chapter 6 of the CA MICS System Modification Guide (SMG). In the YEARS timespan, a value of '0' indicates that to activate the file in the YEARS timespan you must set parameters in prefix.MICS.PARMS(SITE), as described in Section 2.3.2.4 of the PIOM, in addition to the standard database tailoring techniques. In the Archive database, a value of '000' indicates that activating the WEEKS or MONTHS archive timespans is meaningless. If a file has been activated in a timespan, you must specify a cycle retention limit greater than zero. If a file is inactive in a timespan, you must specify a cycle retention limit of 0. A typical set of IDMS FILE statements follows: FILE IDM IDMSAC 00 07 00 13 01 00 000 024 FILE IDM IDMSAU 00 02 00 06 01 00 000 024 FILE IDM IDMSCL 00 01 00 06 00 00 000 000 FILE IDM IDMSIN 07 00 00 00 00 00 000 000 FILE IDM IDMSSY 07 31 13 13 01 00 053 024 FILE IDM IDMSUA 00 02 00 06 01 00 000 024
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: Database Data Retention Definitions | | | | PARMS Library Member is DBMODEL | | | | Reference Sections: 7.3.4.1 CA MICS Analyzer for CA-IDMS Guide | +------+-----------------------------------------------+-------------------+ | | Online Database Retention | Archive Cut-Off | | File |DETAIL DAYS WEEKS MONTHS YEARS TABLES | WEEKS MONTHS | | Name | | | +------+-----------------------------------------------+-------------------+ |IDMSAC| 00(00) __(07) __(00) __(13) 0(1) __(00) | ___(000) ___(024) | |IDMSAU| 00(00) __(02) __(00) __(06) _(1) __(00) | ___(000) ___(024) | |IDMSCL| 00(00) __(01) __(00) __(06) 0(0) __(00) | 000(000) 000(000) | |IDMSIN| __(07) __(00) __(00) __(00) 0(0) __(00) | 000(000) 000(000) | |IDMSSY| __(07) __(31) __(13) __(13) 0(1) __(00) | ___(053) ___(024) | |IDMSUA| 00(00) __(02) __(00) __(06) 0(1) __(00) | ___(000) ___(024) | +------+-----------------------------------------------+-------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 7-7. Database Data Retention Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |