4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.3 Job Steps › 4.3.3.3.3 MONTHLY Job Steps

4.3.3.3.3 MONTHLY Job Steps

 
 The actions being performed within each step of the MONTHLY
 job are discussed below.
 
 Step MONTHnnn:  Update information areas in the database for
                 products installed in this unit database.
                 There is one step (001-190) for each product.
 
   1.  Verify that prerequisite step completed successfully.
   2.  If this is the first step of the MONTHLY job and
       ARCHIVE HISTM YES JOB is specified in JCLDEF
       (stand-alone Archive Monthly History processing is
       enabled), then verify that the HISTM job for the
       previous month completed successfully.
   3.  Delete each file's highest defined cycle.
   4.  Split month-to-date cycles (00) into current month (M0)
       and prior months (M1) cycles.
   5.  If YEARS timespan is active, build year-to-date
       temporary files (cycle Y0) for files maintained in the
       YEARS timespan from the new MONTHS M1 cycle and
       existing YEARS timespan 00 cycle files.  See
       sharedprefix.MICS.PARMS(CPLXDEF),
       prefix.MICS.PARMS(SITE), and
       prefix.MICS.PARMS(DBMODEL).
   6.  Perform monthly cycle aging for each file.
       a.  Rename cycles 01-nn to cycles 02-(nn+1).
       b.  Replace cycle 00 with cycle M0 (new month-to-date).
       c.  Rename cycle M1 to 01.
       d.  Rename YEARS cycle Y0 to 00.
   7.  Update cycles and date/time ranges in the DAYS.ADMCYC01
       file.
   8.  Update the Checkpoint File -- MONTHnnn completed.
 
 
 Step MONTH199:  Accounting and Chargeback -- see the
                 Accounting and Chargeback User Guide for
                 information on monthly accounting processing.
 
 Step MONTH200:  Update CA MICS exception files.
 
   1.  Verify that prerequisite step completed successfully.
   2.  Delete the highest defined cycle.
   3.  Split month-to-date cycle (00) into current month (M0)
       and prior months (M1) cycles.
   4.  Perform monthly cycle aging.
       a.  Rename cycles 01-nn to cycles 02-(nn+1).
       b.  Replace cycle 00 with cycle M0 (new month-to-date).
       c.  Rename cycle M1 to 01.
   5.  Update the Checkpoint File -- MONTH200 completed.
 
 Step MONTH300:  Update the CA MICS archive database.
 
   1.  Verify that prerequisite step completed successfully.
   2.  If you specified ARCHIVE HISTM YES in
       prefix.MICS.PARMS(JCLDEF),
       a.  If you specified the STEP option (or took the
           default), then update monthly archive
           history files.  Combine the current (0) generation
           monthly archive history files with the new 01 cycle
           MONTHS timespan files to create the new (+1)
           generation monthly archive history files.  See
           monthly archive history eligibility and retention
           parameters in prefix.MICS.PARMS(DBMODEL) and the
           specifications in
           sharedprefix.MICS.GENLIB(cccGENIN).
       b.  Or, if you specified ARCHIVE HISTM YES JOB, then
           1) Mark checkpoint to indicate that Audit Monthly
               History processing is required (HISTM job).
           2)  If ARCHIVE HISTM YES JOB AUTOSUBMIT is
               specified, write the HISTM operational job to
               the OS/390 internal reader.
   3.  Update the Checkpoint File -- MONTH300 completed.
 
 
 Step MONTH400:  Standard reports and MICF inquiry production
                reporting.
 
   1.  Verify that prerequisite step completed successfully.
   2.  If you specified AUTOSUBMIT YES in
       prefix.MICS.PARMS(JCLDEF), submit the MONTHRPT job;
       copy prefix.MICS.CNTL(MONTHRPT) to the JES internal
       reader.
   3.  If you specified AUTOSUBMIT NO in
       prefix.MICS.PARMS(JCLDEF), produce management objective
       reports -- see report control parameters in
       prefix.MICS.PARMS(EXECDEF).
   4.  Update the Checkpoint File -- MONTH400 completed.
 
 
 Step MONTH500:  User-written reports (non-MICF).
 
   1.  Verify that prerequisite step completed successfully.
   2.  Perform user-defined processing -- see
       prefix.MICS.USER.SOURCE(MNUSER).
   3.  Update the Checkpoint File -- MONTH500 completed.
 Step MONTH900:  Database update termination.
 
   1.  Verify that prerequisite step completed successfully.
   2.  Update the Checkpoint File -- MONTH900 completed.
 
 
 Step MONTHRSR:  Run Status Report.
 
   1.  Generate CA MICS Run Status Report.
   2.  Update Operational Status and Tracking control tables.
       a.  Store MONTHLY job status.
       b.  Copy ADMCYC01 file to the cycle inventory table.
       c.  Update the processing schedule for the next 7 days.
       d.  Update the operational job log.
 
 
 Step BACKUP:  Produce CA MICS Monthly backup.
 
   1.  Execute or submit the Monthly backup job.
 
 
 The monthly backup steps are described below:
 
 Step BKUP900M:  Database backup.
 
   1.  Backup the Checkpoint File.
   2.  Copy online Database files to timespan monthly backup
       data sets.
   3.  Update Operational Status and Tracking control tables.
       a.  Store monthly backup (MBACKUP) job status.
       b.  Update the operational job log.
 
 
 Step BKTLIB:  Backup sharedprefix.MICS.ISPTLIB (PRIMARY unit
               database only).
 
   1.  Copy sharedprefix.MICS.ISPTLIB to the monthly ISPTLIB
       backup file.
 
 
 Step IDCAMS:  Produce CA MICS Catalog List.
 
   1.  Generate Catalog List for all 'prefix.MICS' entries.