4. Operation › 4.3 Operations Reference › 4.3.12 Special Processing Considerations › 4.3.12.4 CA MICS Year-End Processing Considerations
4.3.12.4 CA MICS Year-End Processing Considerations
This section highlights the CA MICS complex-level and
unit-level specifications that should be checked prior to the
start of the new calendar year. It also discusses how the
execution of CA MICS operational jobs at the end of the year
can affect the content of CA MICS database files.
CA MICS COMPLEX-LEVEL CONSIDERATIONS
1. Validate the holiday specifications in the CPLXZONE member
of the sharedprefix.MICS.PARMS library. If any changes
are made, execute sharedprefix.MICS.CNTL(CPLXGEN) to make
them effective. See Section 2.3.1.10 for more
information.
2. Review any user calculations in the $DWMYxxx and #DWMYxxx
members of sharedprefix.MICS.SOURCE, where xxx is 12, 13,
WK1, or a user-defined value. These members contain the
macros that determine the values of the DAY, WEEK, MONTH,
and YEAR elements. Hard-coded dates may need to be
changed, but be careful; if your site has the CA MICS
Capacity Planner management application installed, do not
delete the start date of any year that could be used in
long term capacity trend or forecast studies. See Section
4.7 in the System Modification Guide for information about
coding these members.
3. If the YEARS TIMESPAN ACTIVE statement is coded in
sharedprefix.MICS.PARMS(CPLXDEF) or if the YEARS TIMESPAN
parameter is NOT specified in this member, then the YEARS
timespan will be active by default in each unit database.
Verify that enough space is available in each unit
database YEARS timespan for additional data.
If YEARS TIMESPAN INACTIVE statement is coded in
sharedprefix.MICS.PARMS(CPLXDEF), then the YEARS timespan
will be inactive by default in each unit database.
Sites that operate on a non-standard (that is, greater
than twelve months) calendar should also ensure that the
sharedprefix.MICS.PARMS(CPLXDEF) 13MONTHYEAR parameter
contains the start date of both the new year and the
previous year. Leave enough specifications in the member
to support the Capacity Planner management application if
it is installed. See Section 2.3.1.8 for more information
about the CPLXDEF member.
4. Review MICF inquiries, production inquiry jobstreams and
user-written batch reports for hard coded selections that
are based upon date, timespan, or file cycle values and
adjust accordingly.
5. If the CA MICS Accounting and Chargeback management
application is installed:
o If your site utilizes a special accounting calendar that
is different from the CA MICS calendar, review Sections
1.3.6 and 4.6 in the Accounting and Chargeback User
Guide and ensure that monthly cutoff dates for the
upcoming year have been specified.
o Determine if any of the following files need to be
updated for the coming year:
ACTBGT00 - Budget File
ACTCCA01 - Cost Center Attribute File
ACTRCT00 - Recurring Credit File
ACTRDT00 - Recurring Debit File
ACTSEQ01 - Invoice Sequence Number File
See Chapter 7 and Appendix A in the Accounting and
Chargeback User Guide for more information about these
files.
o Examine complex-level utility jobs, prorating
specifications and external file logic for any required
changes. See Sections 4.15 and 1.3.8, and Chapter 4 in
the CA MICS Accounting and Chargeback User Guide,
respectively, for information about changing these
specifications.
CA MICS UNIT-LEVEL CONSIDERATIONS
Review the following items for each unit in the complex.
1. For units that override the complex-level ZONE definition,
validate the holiday specifications in the ZONE member of
prefix.MICS.PARMS. If any changes are made, execute
prefix.MICS.CNTL(BASPGEN) to make them effective. See
Section 2.3.2.3 for further information.
2. We recommend that you do a year-end review of all other
prefix.MICS.PARMS members to ensure that they contain
adequate information for the new year. Review step 8 in
Section 3.8.2.2 for a list of standard parameter members
to check.
3. If the years timespan is active, ensure that enough space
is available in the YEARS timespan for additional data.
The years timespan will be active if YEARS TIMESPAN ACTIVE
is coded in prefix.MICS.PARMS(SITE), or if the YEARS
TIMESPAN parameter is NOT specified in this member and
defaults to active due to sharedprefix.MICS.PARMS(CPLXDEF)
specifications,
If the YEARS timespan is inactive, do not execute the
YEARLY job.
If the 13MONTHYEAR parameter is specified at the
unit-level in prefix.MICS.PARMS(SITE), ensure that this
parameter contains the start date of both the new year and
the previous year. Leave enough specifications in the
parameter to support the Capacity Planner management
application if it is installed. See Section 2.3.2.4 for
more information about the SITE member.
4. If the CA MICS Accounting and Chargeback management
application is installed in this unit:
o Determine if the rate specifications for any journal
file or external file need to be changed for the coming
year. The effective date facility allows you to enter
these rates in advance. See Sections 1.3.3 in the
CA MICS Accounting and Chargeback User Guide for more
information.
o Determine if any changes are required to unit-level
prorating specifications. See Section 1.3.8 in the
CA MICS Accounting and Chargeback User Guide for more
information.
o Review Section 5.3 in the CA MICS Accounting and
Chargeback User Guide for yearly processing steps.
SCHEDULING CA MICS UPDATE JOBS FOR YEAR-END PROCESSING
The end of the calendar year can necessitate a change in the
normal execution of CA MICS operational jobs. The CA MICS
DAILY job should be submitted in each unit as usual. The
submission of the WEEKLY job, however, can be affected by the
day of the week on which the new year begins or by the way
weekend job scheduling is handled at your site. User reports
and inquiries that select data based upon the WEEK variable
or the cycle number can be affected as a consequence.
It may be necessary for your site to submit an additional
WEEKLY job at the beginning of the new year to ensure that
data for the last week of the previous year and data for the
first week of the new year reside in different cycles.
Two CA MICS facilities can be used to predict the requirement
for an additional WEEKLY job.
Use the SCHEDULE command in the MWF Operational Status and
Tracking facility or manually submit the SCHEDULE job in each
unit to find out how the end of the calendar year will affect
CA MICS processing. Section 4.3 discusses each of these
facilities in detail.
Issue the SCHEDULE command in the Operational Status and
Tracking facility for each unit to produce a report of jobs
that will be submitted over the next seven day period. (Note
that this command will consolidate all CA MICS jobs for the
day into one JCL jobstream and write the data to
prefix.MICS.RESTART.CNTL.)
Submit the prefix.MICS.CNTL(SCHEDULE) job in "simulation" or
"test" mode in order to print a list of CA MICS update jobs
that will execute over a specified time period. You can
submit this job even if your site does not use the CA MICS
scheduling facilities. To execute the SCHEDULE job in test
mode, modify the SYSPARM parameter on the //SCHEDULE EXEC
card to read as follows:
SYSPARM='BKFQ=DAILY TEST(TODAY=ddmmmyy TESTEND=ddmmmyy)'
where TODAY equals the starting date to be analyzed by the
SCHEDULE job in day-month-year format, and TESTEND equals the
ending date.
When TEST is specified, the SCHEDULE job will receive a
return code. No jobs will be scheduled or submitted. You
will find the simulated schedule report in the SASLOG DD.
Look at a sample report produced at a site that has the
following operational configuration:
o The CA MICS year is defined as a normal calendar year.
o The CA MICS week begins on Sunday.
o The BACKUP job is executed on a daily basis.
o The CA MICS SCHEDULE facility is used to submit jobs.
o The YEARS timespan is active.
o SCHEDULE WEEKEND NO is specified in the EXECDEF member
of prefix.MICS.PARMS to prevent submission of the
WEEKLY, MONTHLY, or YEARLY jobs on a weekend. This
parameter has a direct impact on the amount of data
transferred to the weekly file cycles at year-end.
The last column of the sample report lists the jobs that will
be submitted on a given date, where DWMYB is equal to the
DAILY, WEEKLY, MONTHLY, YEARLY, or BACKUP job, respectively.
The YEARLY job will not be listed if the YEARS timespan is
specified as INACTIVE in prefix.MICS.PARMS(SITE).
SUN 27DEC06 DAY=27 MONTH=12 YEAR=06 WEEK=53 DWMYB=D B
MON 28DEC06 DAY=28 MONTH=12 YEAR=06 WEEK=53 DWMYB=DW B
TUE 29DEC06 DAY=29 MONTH=12 YEAR=06 WEEK=53 DWMYB=D B
WED 30DEC06 DAY=30 MONTH=12 YEAR=06 WEEK=53 DWMYB=D B
THU 31DEC06 DAY=31 MONTH=12 YEAR=06 WEEK=53 DWMYB=D B
FRI 01JAN07 DAY=01 MONTH=01 YEAR=07 WEEK=01 DWMYB=D B
SAT 02JAN07 DAY=02 MONTH=01 YEAR=07 WEEK=01 DWMYB=D- B
SUN 03JAN07 DAY=03 MONTH=01 YEAR=07 WEEK=02 DWMYB=D- B
MON 04JAN07 DAY=04 MONTH=01 YEAR=07 WEEK=02 DWMYB=DW- B
TUE 05JAN07 DAY=05 MONTH=01 YEAR=07 WEEK=02 DWMYB=D M B
WED 06JAN07 DAY=06 MONTH=01 YEAR=07 WEEK=02 DWMYB=D YB
THU 07JAN07 DAY=07 MONTH=01 YEAR=07 WEEK=02 DWMYB=D B
FRI 08JAN07 DAY=08 MONTH=01 YEAR=07 WEEK=02 DWMYB=D B
SAT 09JAN07 DAY=09 MONTH=01 YEAR=07 WEEK=02 DWMYB=D B
SUN 10JAN07 DAY=10 MONTH=01 YEAR=07 WEEK=03 DWMYB=D B
The CA MICS scheduling facility has a built-in submission
delay of one day for the WEEKLY job, three days for the
MONTHLY job, and five days for the YEARLY job to allow time
for adjustments to the database or recovery from abend
situations. By default the CA MICS scheduling facility will
not submit a WEEKLY and MONTHLY job or a MONTHLY and YEARLY
job on the same day. A dash in the DWMYB column represents a
CA MICS job that has a scheduling conflict. Note that the
WEEKLY job is in conflict and will not run until Monday,
January 4th. How does this affect the content of CA MICS
database files?
CA MICS translates the system date at the time the WEEKLY job
is executed to the current WEEK value. CA MICS cycles data
from each database file's week-to-date 00 cycle to the 01
cycle based upon the value in the WEEK variable of each
observation. All observations with a WEEK value that is less
than the current week's value moves to the 01 cycle;
observations with a WEEK value that is equal to the current
week's value remains in the 00 cycle. How does this affect
CA MICS reporting?
In the sample report above, a WEEKLY job will be submitted on
Monday, December 28th, as usual. Note that the MONTH, YEAR
and WEEK values change on Friday, January 1st, because of the
change in the calendar year. (See how WEEK is determined in
the System Modification Guide Section 4.7.2.4.) Another
WEEKLY job would normally be scheduled for Saturday, January
2nd, but no weekend job submission is allowed in this unit.
Therefore, the next WEEKLY job is scheduled for Monday,
January 4th, which is CA MICS WEEK 2.
As a result of this delay in the normal execution of the
WEEKLY job, the 01 cycle of all weekly files in this unit
will contain data from WEEK 53 and WEEK 01. The source code
for reports, inquiries, and graphs that use the WEEKS
timespan at this site would have to filter out data for WEEK
01. The site would also have to change source code to
include an additional cycle of weekly data in order to
construct weekly and monthly reports for January's data.
Based on this simulation report, the system administrator
should schedule an additional WEEKLY job to execute on
Saturday, January 2nd to avoid making these code changes.
The MONTHLY and YEARLY jobs at this site are scheduled for
January 5th and 6th in the simulation report. The system
administrator has the option of submitting the MONTHLY job on
Sunday, or allowing it to execute as scheduled on Monday.
The monthly files will be cycled based on the value in the
MONTH variable and the yearly files will be cycled based on
the value in the YEAR variable. No adjustment to report code
is necessary.
CA MICS sites that use either one of the CA MICS scheduling
facilities and have SCHEDULE WEEKEND YES specified in the
prefix.MICS.PARMS(EXECDEF) each unit do not have to make
these scheduling adjustments; a WEEKLY job will be scheduled
automatically for Saturday, January 2nd. Thus, CA MICS will
schedule two WEEKLY jobs in a seven-day period; the cycles
created by each WEEKLY job will have less than seven day's
worth of data in them.
Sites that do not use the CA MICS scheduling or Operational
Status and Tracking facilities can create a schedule report
that is based upon their own year-end date and submit their
year-end processing jobs in a similar manner or adjust
automated scheduling packages to adhere to a slightly
modified year-end process.
If your site normally specifies SCHEDULE WEEKEND NO in
prefix.MICS.PARMS(EXECDEF) or does not use the CA MICS
Scheduling facility, then you may want to manually schedule
an additional WEEKLY job at the end of the year so that data
from the last week of the year will be separated from data in
the first week of the new year.
