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

4.3.3.3.2 WEEKLY Job Steps

 
 The actions being performed within each step of the WEEKLY
 job are discussed below.
 
 Step WEEKnnn:  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 WEEKLY job, then
       a.  If ARCHIVE AUDIT YES JOB is specified in JCLDEF
           (stand-alone Archive Audit processing is enabled),
           then verify that the AUDIT job for the previous
           week completed successfully.
       b.  If ARCHIVE HISTW YES JOB is specified in JCLDEF
           (stand-alone Archive Weekly History processing is
           enabled), then verify that the HISTW job for the
           previous week completed successfully.
   3.  Delete each file's highest defined cycle.
   4.  Split week-to-date cycles (00) into current week (W0)
       and prior weeks (W1) cycles.
   5.  Perform weekly file aging for each file.
       a.  Rename cycles 01-nn to cycles 02-(nn+1).
       b.  Replace cycle 00 with cycle W0 (new week-to-date).
       c.  Rename cycle W1 to 01.
   6.  Update cycles and date/time ranges in the DAYS.ADMCYC01
       file.
   7.  Update the Checkpoint File -- WEEKnnn completed.
 
 Step WEEK199:  Accounting and Chargeback -- see the
                 Accounting and Chargeback User Guide for
                 information on monthly accounting processing.
 
 Step WEEK300:  Update the CA MICS archive Database.
 
   1.  Verify that prerequisite step completed successfully.
   2.  If you specified ARCHIVE AUDIT YES in
       prefix.MICS.PARMS(JCLDEF),
       a.  If you specified the STEP option (or took the
           default), then create the new generation of the
           archive audit files.
       b.  Or, if you specified ARCHIVE AUDIT YES JOB, then
           1)  Mark checkpoint to indicate that Audit Archive
               processing is required (AUDIT job).
           2)  If ARCHIVE AUDIT YES JOB AUTOSUBMIT is
               specified, write the AUDIT operational job to
               the OS/390 internal reader.
   3.  If you specified ARCHIVE HISTW YES in
       prefix.MICS.PARMS(JCLDEF),
       a.  If you specified the STEP option (or took the
           default), then update weekly archive history files.
           Combine the current (0) generation weekly archive
           history files with the new 01 cycle WEEKS timespan
           files to create the new (+1) generation weekly
           archive history files.  See weekly 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 HISTW YES JOB, then
           1)  Mark checkpoint to indicate that Audit Weekly
               History processing is required (HISTW job).
           2)  If ARCHIVE HISTW YES JOB AUTOSUBMIT is
               specified, write the HISTW operational job to
               the OS/390 internal reader.
   4.  Update the Checkpoint File -- WEEK300 completed.
 
 
 Step WEEK400:  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 WEEKRPT job; copy
       prefix.MICS.CNTL(WEEKRPT) 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 -- WEEK400 completed.
 
 
 Step WEEK500:  User-written reports (non-MICF).
 
   1.  Verify that prerequisite step completed successfully.
   2.  Perform user-defined processing -- see
       prefix.MICS.USER.SOURCE(WKUSER).
   3.  Update the Checkpoint File -- WEEK500 completed.
 
 
 Step WEEK900:  Database update termination.
 
   1.  Verify that prerequisite step completed successfully.
   2.  Update the Checkpoint File -- WEEK900 completed.
 Step WEEKRSR:  Run Status Report.
 
   1.  Generate CA MICS Run Status Report.
   2.  Update Operational Status and Tracking control tables.
       a.  Store WEEKLY 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.