|
|
|
The MICF Production Reporting Administration option (MWF;2;4;3) allows you to define and maintain your MICF inquiry production reporting. o You can add, modify, execute, and delete MICF production reporting job streams. o You can generate and catalog color graphics and printed reports either with regularly scheduled CA MICS production processing or through your data center's own scheduling facilities. o You can optionally generate hardcopy printed reports, color graphics, and MICSLOG and SAS log while still saving reports, graphics, and logs for later online review. You can even use your data center's report management facility (for example, CA Bundl) to route, archive, and manage MICF production reporting hardcopy outputs. o You can specify execution-time parameter overrides for production execution of MICF inquiries or execute inquiries with predefined default parameter values. o You can access the Reports and Graphics option (MWF;2;1) for online review and printing of production reporting color graphics and printed reports, as well as any CSV file output. You will also use MICF Production Reporting Administration to define and maintain production job streams to create your CSV files. You can add CSV file capability to any standard MICF production reporting job stream. The Q&R Workstation guides document the use of the MICF Production Reporting Administration facilities for CSV file creation. You will use MICF Production Reporting Administration to define and maintain production job streams for updating your CA MICS Capacity Planner Option shared capacity planning database files. Capacity Planner Option file update job streams are a special type of MICF production reporting job stream. The Capacity Planner Option Guide documents use of MICF Production Reporting Administration facilities for shared Capacity Planner Option file definitions. Unless specifically noted otherwise, all references to MICF production reporting job streams in the documentation that follows also apply to the Capacity Planner Option file updates. However, you should see the Capacity Planner Option Guide for specific issues relating to Capacity Planner Option files. Each production reporting job stream allocates unique, user-defined printed report and color graphics catalog data sets. Thus you can use your data center's security facilities to limit access to sensitive reports. For example, your accounting staff may want to share a series of daily financial graphics. You can create a separate job stream to generate and save financial graphics, and protect them using RACF or another security facility. You also have the option to define "hardcopy only" MICF production reporting. MICF will write printed reports, color graphics, and MICSLOG and SAS log to the JES SYSOUT data set and hardcopy color graphics device you define. After execution completes, MICF will delete the staging data sets used to hold printed reports, color graphics, and MICSLOG and SAS log during execution processing. Each production reporting job stream defines a list of MICF inquiries to be executed. You can execute with the predefined default execution-time parameter values specified in the inquiry, or you can specify execution-time parameter overrides for production execution. You can create multiple versions of a production report with a single production reporting job stream by executing an inquiry multiple times and specifying different execution-time parameter overrides for each execution. The Production Reporting Administration panel (Figure 5-4) displays your MICF inquiry production reporting job streams. The display lists job stream name and title, along with the CA MICS production job association you define. A CA MICS job name of DAILY, WEEKLY, or MONTHLY plus a DB ID identifies the specific CA MICS database unit update job associated with the job stream. CA MICS Job is the name of the production CA MICS job that may schedule the production reporting. DB ID is the CA MICS database unit ID where the job runs, as well as the default unit ID for MICF inquiry execution. Note: MICF production reporting does not actually execute within the production CA MICS DAILY, WEEKLY, or MONTHLY database update jobs. Execution actually occurs in the DAILYRPT, WEEKRPT, and MONTHRPT jobs. These jobs may be submitted by the DAILY, WEEKLY, and MONTHLY database update jobs, or you may schedule the MICF production reporting process through your data center's own scheduling facilities. For more information about production interface and scheduling, see section 5.1.6.4.
-------------------- Production Reporting Administration --------------------
Command ===> Scroll ===> CSR
Line Cmds: I Insert D Delete S Select G Generate -- Associated -- Cmd Name Reports and Graphics Jobstream Title CA MICS Job DB ID - -------- ---------------------------------------- -------- -
_ ACTDAILY Daily Accounting Reports ________ _ _ ACTMONTH Monthly Accounting Reports ________ _ _ DAILY Daily Reports DAILY P _ DAILYEXC Daily Exception Reports DAILY P _ DAILYMBO Daily Mgmt. by Objective Reports (MBO) DAILY P _ IMSDAILY IMS Daily Reports DAILY I _ MONTHLY Monthly Reports MONTHLY P _ MONTHMBO Monthly Mgmt. by Objective Reports (MBO) MONTHLY P _ NETSMRY Daily Network Analysis Reports DAILY N _ WEEKLY Weekly Reports WEEKLY P _ WEEKMBO Weekly Mgmt. by Objective Reports (MBO) WEEKLY P _ VMCDAILY VM/CMS Daily Reports DAILY V _ VMCWEEK VM/CMS Weekly Reports WEEKLY V ****************************** BOTTOM OF DATA ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-4. Production Reporting Administration
Line commands available on the Production Reporting
Administration panel, Figure 5-4, include:
o I (Insert) defines a new production reporting job stream.
o D (Delete) deletes individual reports and graphics outputs
from the production output catalog, or delete an entire
production reporting job stream and ALL saved reports and
graphics outputs.
o S (Select) reviews and modifies an existing job stream.
o G (Generate) is on demand job stream execution, or
generates and saves execution JCL for submission through
your data center's batch job scheduling facilities.
MICF Production Reporting Administration is discussed in the
following sections:
1 - Controlling Access to Reports and Graphics
2 - Defining a Production Reporting Job Stream
3 - Executing a Production Reporting Job Stream
4 - MICF Inquiry Production Interface
5 - Deleting Reports and Graphics Outputs
6 - CA MICS Standard MBO and Exception Reports
In addition, the remainder of this section is a step-by-step
checklist for implementing MICF production reporting. The
checklist refers to specific actions described in sections
5.1.6.1 through 5.1.6.6, so you may want to review these
sections before trying to use the checklist.
Implementing MICF Production Reporting
__ 1. Review your data center's production reporting
environment and the specific requirements relative
to the production reporting you plan to implement.
Consider the following issues (you will apply your
answers later in the checklist).
o Who are the reports for? Who will need access
to the reports? Who should not be allowed to
see the reports? Do you need hardcopy reports
and graphics? Will you be routing reports and
logs to a report management facility (for
example, CA Bundl)?
o What color graphics devices are used for online
graphics review? What color graphics devices
are used for hardcopy graphics output? Do you
use black and white or grey scale graphics, for
example on a laser printer?
o Which shared MICF inquiries do you want to
regularly execute so that reports are generated
and saved? What execution-time parameter
overrides are needed to generate the reports?
o How do you schedule production CA MICS
reporting? Do you have a production batch job
scheduling facility/procedure? Do you let CA
MICS jobs submit other jobs (that is, do you
use the CA MICS AUTOSUBMIT facility)?
o When do you want the reports to execute:
daily, weekly, monthly?
o What dependencies do the reports have?
Do they depend on a single database unit update
or do they extract information from multiple CA
MICS database units?
o How do you plan to monitor production reporting
execution? Do you want a hardcopy log of
execution errors?
__ 2. Use the MICF Production Reporting Administration
option to define a MICF production reporting
job stream that will generate and save the reports.
Reference: Section 5.1.6.2
__ a. Select option 4, MICF Administration, from
the MICF Primary Options menu.
__ b. Select option 3, Production Reporting
Administration, from the MICF Administration
menu.
__ c. Use the insert (I) line command to insert a
new MICF production reporting job stream.
__ d. Specify the job stream name, title, and
catalog table data set name on the Insert
Reporting Jobstream panel.
Select the catalog table data set name
carefully. You control access to the reports
and the reporting job stream definition by
using your data center's security facilities
(for example, RACF or other security product)
to control access to the catalog table data
set and the reports and graphics data sets
associated with each job stream.
o The job that executes the production
reporting job stream must have authority
to UPDATE the catalog table data set AND
must be able to CREATE (that is,
allocate new), UPDATE, and DELETE the
associated color graphics and printed
report output data sets.
o For CA MICS job streams that generate
CSV files, the job that executes the
reporting job stream must also have
authority to UPDATE the
sharedprefix.MICS.DTF.INDEX data set.
o For Capacity Planner Option file update
job streams, the job that executes the
reporting job stream must also have
authority to UPDATE the
sharedprefix.MICS.CAPACITY data set.
o You or any other user authorized to
maintain the production reporting
definition must have authority to UPDATE
the catalog table data set and be able
to DELETE associated color graphics and
printed report output data sets.
o A user ID must have READ access to the
catalog table data set and the
associated color graphics and printed
report output data sets in order to
review reports.
__ e. Press END to allocate the catalog table data
set, insert the production reporting
job stream definition, and display the
Reports and Graphics Jobstream panel.
o Specify a maximum report retention
limit.
- Specify a nonzero value to retain
reports, graphics, and logs for
later online review.
- If you plan to generate hardcopy
reports and color graphics, you
have the option to specify 0.
- Even if you want hardcopy output,
MICF's online retention of reports
and graphics provides a valuable
reporting "archive" so reports and
graphics are available online long
after hardcopy outputs have been
discarded.
o Specify DAILY, WEEKLY, or MONTHLY for
Associated CA MICS Job depending on
whether you want the reports run daily,
weekly, or monthly.
o Specify Database ID for the CA MICS
database update that will schedule the
MICF inquiry production reporting if the
reports depend on information from a
single CA MICS database unit.
Otherwise, leave the DB ID field blank.
o Specify default file cycles parameters.
o Review the generated printed reports,
color graphics, temporary report, and
temporary MICSLOG data set names and
make any changes you require. Remember
that the data set names MUST be unique
and CANNOT overlap data set names used
by any other production reporting job
stream definition.
__ f. Select MICF Inquiries for Reporting Jobstream
(enter a Y following the prompt and press
Enter), and select the shared MICF inquiries
you want to execute in this MICF production
reporting job stream.
Reference: Section 5.1.6.2.1
o You can change the catalog group
specification when you select an
inquiry. Inquiry outputs are organized
in the production catalog according to
the catalog group assignments you make
when you select inquiries for the
reporting job stream.
o You can specify execution-time parameter
overrides. For example, if you are
defining a complex-level reporting job
stream, there is no default for the unit
Database (DB) ID. You can use the
execution-time parameter overrides to
specify the P (primary) unit for one
inquiry and the I (IMS) unit for another
inquiry. You can also execute a single
inquiry multiple times. For example,
run the IMSCD2 inquiry once for all
production IMS regions and a second time
for development (or test) regions.
__ g. Select Data Set Allocation Parameters (enter
a Y following the prompt and press Enter) if
you want to change defaults for allocating
the production report output data sets.
Reference: Section 5.1.6.2.2
__ h. Select Execution and Hardcopy Output Options
(enter a Y following the prompt and press
Enter) if you want to change default color
graphics device parameters or other execution
options, generate hardcopy printed reports,
generate hardcopy color graphics, or activate
the hardcopy error log.
Reference: Section 5.1.6.2.3
__ i. Press END on the Reports and Graphics
Jobstream panel after you complete the
definition.
__ 3. We suggest that you test the job stream using the G
(generate) line command on the Production Reporting
Administration panel to generate and submit a batch
job to execute your production reporting job stream
definition. Examine the MICSLOG output for any
error conditions and correct any problems before
proceeding with this checklist.
__ a. If you run the suggested test, then use the
MICF Reports and Graphics option to review
the production reports online. Note and
correct any problems in catalog groups, color
graphics device parameters, execution-time
parameter overrides, and SAS execution
parameters. Make sure that ALL inquiries
execute successfully and generate the desired
outputs.
__ b. If you are generating hardcopy reports and
logs, verify that the outputs are written to
the proper SYSOUT class and form. Correct
any problems in hardcopy report and log
SYSOUT allocation parameters. Make sure your
report management facility (for example,
CA Bundl) will be able to capture the
hardcopy outputs.
__ c. If you are generating hardcopy graphics,
verify that the outputs are generated on the
proper graphics device. Correct any problems
in hardcopy color graphics device parameters.
Verify that online and hardcopy color
graphics device specifications are compatible
and that MICF graphics are usable both online
and in hardcopy format. This is especially
important when routing hardcopy graphics to a
laser printer. Ensure that the MICF
execution parameters select a color graphics
format set using hashed patterns so that the
graphics are usable both in color (online)
and in black and white (hardcopy).
__ 4. Add the MICF production reporting job stream to your
regularly scheduled production processing.
__ a. If you specify YES for the AUTOSUBMIT
parameter in prefix.MICS.PARMS(JCLDEF), the
next daily, weekly, or monthly production
reporting process will include your MICF
production reporting job stream.
__ b. If you specify NO for the AUTOSUBMIT
parameter in prefix.MICS.PARMS(JCLDEF), use
your data center's standard production batch
job scheduling facility to schedule the
CA MICS report job steps for execution after
the corresponding daily, weekly, and monthly
production database update jobs complete.
Reference: Sections 5.1.6.3 and 5.1.6.4
o Construct a batch JCL stream according to
your data center standards to execute the
production reporting job stream.
o Include the ICFDY400, ICFWK400, and
ICFMN400 job steps as generated in the
DAILYRPT, WEEKRPT, and MONTHRPT reports
jobs.
o Add the MICF production reporting job
stream to your production processing
schedule.
__ c. If you are using a report management facility
(for example, CA Bundl) to capture hardcopy
reports and logs, set up the report manager's
control definitions for the job name, SYSOUT
class, and SYSOUT form to which you directed
MICF outputs.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |