Add File to Monthly History Archive Tape
MICS includes a facility to copy a file's data to offline storage (a tape generation data group) every month.
micsrm140
Required roles: systems programmer, security administrator, database administrator |
|---|
Such data may be useful for maintaining long periods of data for large volume historical analyses without using undue amounts of online storage. A file eligible for monthly history archiving must exist in the MONTHS time-span.
To add a file to the monthly history archive tape, which is generated by the
MICS
MONTHLY or the standalone HISTM operational job, follow these steps:- Edit the FILE statement in sharedprefix.MICS.GENLIB(cccGENIN). Change the "N" in the file's monthly history archive position to "Y".For more information about the GENIN FILES statement, see Tailoring Archive Files.
- Submit the sharedprefix.MICS.CNTL(cccCGEN) job to regenerate the component.
- Edit prefix.MICS.PARMS(DBMODEL) for all database units in which the component is installed.To add the file, the FILE statement for that file must have a cutoff limit greater than zero in the monthly history archive position. Define a zero cutoff limit in units where you don't want to create this file.For more information about the FILE statement in DBMODEL, see Data Retention Specifications (FILE Statement).
- Submit the prefix.MICS.CNTL(CYCLEGEN) job for all database units in which the component is installed.This job changes the component's executable code in the prefix.MICS.USER.SOURCE libraries and affects only the database units in which the component is installed.
- Verify that your current specification for NULLSER is valid.If your existing history archive tapes for a unit in which the file's component is installed are in an automatic tape loader (ATL) or a virtual tape subsystem (VTS), you might need to change the NULLSER value to a volume serial number that is valid for the ATL or VTS.For JES2 customersIf left unchanged, you may see a tape mount for a volume serial number such as NULSER; however, the WEEKLY job should complete typically, regardless of the unsatisfied tape mount request.For JES3 customersIf left unchanged, the MONTHLY job does not continue because the tape mount cannot be satisfied. The job waits.To determine that the NULLSER and NULLUNIT values already specified are still acceptable to z/OS do the following steps:
- For each unit in which the file's component is installed, in the JCLDEF member locates the NULLSER value that is specified for the history archive tapes. If NULLSER is not specified on the HISTWPARM or HISTMPARM statements, review the TAPEPARM statement. If not found there, find it in sharedprefix.MICS.PARMS(JCLDEFC).
- Also locate the NULLUNIT value. If necessary, review the TAPEPARM statement or in sharedprefix.MICS.PARMS(JCLDEFC).
- Modify this JCL with these two values and submit the job.//jobname JOB //ALLOC EXEC PGM=IEFBR14 //NULSER DD DSN=anyname, // DISP=(NEW,DELETE), // UNIT=nullunit, // VOL=SER=nulser //
- If this job runs clean, the null specifications are good. If not, select new NULLSER and NULLUNIT values. Rerun this job with the new specified values to prove that the new values are still good. If not, new NULLSER and NULLUNIT values must be chosen. Rerun this job with the new values specified to prove that the new values are acceptable.A technique for obtaining and retaining validNULLSER and NULLUNIT values is described in Database Complex Tape Specifications.
- Ensure that each unit has the same NULLSER and NULLUNIT values specified.For more information about the use of the NULLSER and NULLUNIT keyword, see Database Unit Tape Specifications.To determine the volume serial number of an existing history archive tape, under TSO option 6, issue the command:LISTC EN('tapeprefix.HISTM.iiifff') ALLFor a file which is active for history archive. Refer to the MONTHLY job MONTH300 step (or the standalone HISTM job if you activated the standalone archive monthly history job option) and may select any one of the HIiiifff DDs. Repeat this step for every unit which has this component that is installed.
- Edit prefix.MICS.PARMS(JCLGENU) for all database units in which the component is installed. Specify:MONTHLY HISTMIf you edit the NULLSER value as stated in the previous step, specify:MONTHLY HISTM GDGSGEN
- Submit the prefix.MICS.CNTL(JCLGENU) jobs.This generates the MONTHLY or HISTM job JCL, or both. This JCL contains DD statements for the new monthly history tape files, and recreates the GDGSGEN job with the volume serial number that the first generation of the new file is cataloged to (with the NULLSER value you select).
- Submit prefix.MICS.CNTL(GDGSGEN) for all database units in which the component is installed.This creates monthly history tape generation data groups for the new archive files, if necessary. For example, assume that the NPANCP file appears in the following archives:For example, assume that the NPANCP file appears in the following archives:WEEKLY WEEKLY MONTHLY AUDIT HISTORY HISTORY -------- -------- -------- NO YES NO Assume the desired configuration is: WEEKLY WEEKLY MONTHLY AUDIT HISTORY HISTORY -------- -------- -------- NO YES YESThe initial definition of the NPANCP file statement in sharedprefix.MICS.GENLIB(NPAGENIN) would have been:FILE NCP 00 1 Y Y Y Y N N Y N NCP Activity File | | | no WEEKLY audit ----+ | | WEEKLY history ------+ | no MONTHLY history--------+ Change this statement to: FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File | +- MONTHLY history producedThe number of cycles of the file thatMICSuses as input to the monthly history archive is fixed at 1. This means the last cycle of MONTHS time-span data is copied to the new generation of the monthly history archive tape when the monthly history is generated in theMICSMONTHLY or standalone HISTM operational job. The data from the database is added to data on the previous generation of the file's monthly history tape.The test of what observations to put on the archive file is: any observation from a date later than the specified cutoff date is copied to the archive file. No observations from the current month are included in the input.The cutoff date is determined by the user specification of the monthly history retention limit in the DBMODEL member of the prefix.MICS.PARMS library.For example, assume that the retention limit was 010. The previous ten months of monthly history would be available on any generation of the monthly history tape. Also, assume the month that is only processed by the currentMICSMONTHLY or HISTM run (now cycle NPANCP01) is for month 11 of the year.Contents Last Month's Contents of Last Activity of New Monthly From Online Monthly History Database History ---------- ---------- ---------- month 01-(dropped, too old) month 02----------------->month 02 month 03----------------->month 03 month 04----------------->month 04 month 05----------------->month 05 month 06----------------->month 06 month 07----------------->month 07 month 08----------------->month 08 month 09----------------->month 09 month 10----------------->month 10 month 11---->month 11