Add File to Weekly History Archive Tape
MICS includes a facility to copy a file's data to offline storage (a tape generation data group) every week.
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 weekly history archiving must exist in the WEEKS time-span.
To add a file to the weekly history archive tape, which is generated by the
MICS
WEEKLY or the standalone HISTW operational job, do the following:- Edit the FILE statement in sharedprefix.MICS.GENLIB(cccGENIN). Change the "N" in the the file's weekly history archive position to "Y".For more information on 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 weekly history archive position. Define a zero cutoff limit in units where you don't want to create this file.For more information on 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 still 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 normally, regardless of the unsatisfied tape mount request.For JES3 customersIf left unchanged, the WEEKLY job will 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:
- For each unit in which the file's component is installed, in the JCLDEF member locate the NULLSER value that is specified for the history archive tapes. If NULLSER is not specified on the HISTWPARM or HISTMPARM statements, look at 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 2 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 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 valid NULLSER and NULLUNIT values is described in in Database Complex Tape Specifications.
- Ensure that each unit has the same NULLSER and NULLUNIT values specified.For more information on the use of the NULLSER and NULLUNIT keywords, see Database Unit Tape Specifications.
- Edit prefix.MICS.PARMS(JCLGENU) for all database units in which the component is installed. Specify:WEEKLY HISTWIf you made a change to the NULLSER value as stated in the previous step, specify:WEEKLY HISTW GDGSGEN
- Submit the prefix.MICS.CNTL(JCLGENU) job(s).This generates the WEEKLY and/or HISTW job JCL that contains DD statements for the new weekly history tape files, as well as 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 chose).
- Submit prefix.MICS.CNTL(GDGSGEN) for all database units in which the component is installed.This creates weekly history tape generation data groups for the new archive files, if necessary. For example, assume the NPANCP file appeared in the following archives:WEEKLY WEEKLY MONTHLY AUDIT HISTORY HISTORY -------- -------- -------- NO NO YESAssume 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 be:FILE NCP 00 1 Y Y Y Y N N N Y NCP Activity File | | | no WEEKLY audit -----+ | | no WEEKLY history-------+ | MONTHLY history ---------+Change this statement to:FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File | +- WEEKLY history producedThe number of cycles of the file thatMICSwill use as input to the weekly history archive is fixed at 1. This means the last cycle of WEEKS time-span data will be copied to the new generation of the weekly history archive tape when the weekly history is generated in theMICSWEEKLY or standalone HISTW operational job. The data from the database is added to the previous generation of the file's weekly 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 will be copied to the archive file. No observations from the current week will be included in the input.The cutoff date is determined by the user specification of the weekly history retention limit in the DBMODEL member of the prefix.MICS.PARMS library.For example, assume the retention limit was 010. The previous ten weeks of weekly history would be available on any generation of the weekly history tape. Also, assume the week just processed by the currentMICSWEEKLY or HISTW run (now cycle NPANCP01) is for week 26 of the year.Contents Last Week's Contents of Last Activity of New Weekly From Online Weekly History Database History ---------- ---------- ---------- week 16-(dropped, too old) week 17------------------>week 17 week 18------------------>week 18 week 19------------------>week 19 week 20------------------>week 20 week 21------------------>week 21 week 22------------------>week 22 week 23------------------>week 23 week 24------------------>week 24 week 25------------------>week 25 week 26----->week 26