|
|
|
---------------------------- Database Inquiries -----------------------------
Command ===> Scroll ===> CSR
Reporting Job Stream: IMSDAILY - Daily IMS Reports
Catalog Group ===> * Inquiry Name ===> _____ Line Cmds: I Insert D Delete S Select M Move E Exec-Time R Reset Parms Cmd Name Title Exec-Time Catalog - -------- ---------------------------------------- ----------- -------- _ IMSCDT 8am 5 pm IMS Service By Type *Specified* SHARED _ IMSCD1 Daily IMS Workload Report SHARED _ IMSCD2 Daily IMS Service Reports *Specified* SHARED
_ IMSCD2 Daily IMS Service Reports *Specified* SHARED _ IMSCD3 Daily IMS Availability Report SHARED ****************************** BOTTOM OF DATA ********************************
Scrolling RIGHT on an inquiry display shows the following:
Reporting Job Stream: IMSDAILY - Daily IMS Reports Catalog Group ===> * Inquiry Name ===> ______ SCROLL LEFT TO RETURN TO INQUIRY INFO Line Cmds: I Insert D Delete S Select M Move E Exec-Time R Reset Parms Inquiry Cmd Name Typ Prim 2nd STORCLAS DATACLAS MGMTCLAS - -------- --- ----- ----- -------- -------- -------- _ IMSCDT CYL 15 5 _ IMSCD1 _ IMSCD2 CYL 25 5 _ IMSCD2 CYL 25 5 _ IMSCD3 TRK 10 5 ******************************* Bottom of data ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-7. Sample MICF Inquiries for Reporting Jobstream Use this option to specify the MICF inquiries to be executed with the production reporting job stream. You can select any inquiry from the MICF shared inquiry catalog. Figure 5-7 (above) shows an example of shared MICF inquiries selected for daily IMS production reporting. You can execute an inquiry using default execution-time parameter values. If the inquiry does not specify a default value for Database (DB) ID or CA MICS File Cycle(s), then the values you specify on the Reports and Graphics Jobstream panel will be used to execute the inquiry. The inquiries you select MUST have valid default values for all other execution-time parameters. Alternatively, you can specify execution-time parameter overrides. Enter the E (Exec-Time) line command to display the associated execution-time parameters panel for an inquiry (see sample on next page). The execution-time parameter values you specify are saved with the production reporting job stream definition and are applied to the inquiry when the reporting job stream executes. MICF marks the inquiries that have execution-time parameter overrides by showing *Specified* in the Exec-Time column of the Database Inquiries panel. As you can see on the sample above, execution-time parameter overrides have been defined for the IMSCDT inquiry and for both copies of IMSCD2.
------------------------- Execution-Time Parameters -------------------------
Command ===> Scroll ===> CSR
Selecting CA MICS Inquiry: IMSCD2 - Daily IMS Service Reports
------------------------------------------------------------------------------ Enter one or more Database IDs for the Database(s) you want to process. I - _____________________________________ Enter range of CA MICS online file cycles or enter ARCHIVE for archive files.
01 - _____________________________________ Enter the SYSID(s) to be reported or leave blank to report all systems. _____________________________________ - _____________________________________ Enter the IMSID(s) to be reported or leave blank to report all regions. PROD - _____________________________________ ****************************** BOTTOM OF DATA ********************************
. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-8. Execution-Time Parameters If you want, you can execute a single inquiry against different DB IDs, file cycles, or other execution-time parameter values. Simply select the inquiry multiple times and specify different execution-time parameter overrides. The sample in figure 5-7 shows that the IMSCD2 inquiry is executed twice. The sample Execution-Time Parameters panel above shows the execution-time parameter overrides that might have been specified for one of the executions of the IMSCD2 inquiry. o The inquiry will execute against the I (IMS) unit database and will select the 01 cycle. o The inquiry will report on the production IMS regions. That is, the inquiry will subset the available IMS data to observations with IMSID values that begin with the characters PROD (this inquiry is defined to subset based on leading characters). o We can assume that the second execution of the IMSCD2 inquiry might be limited to development (or test) IMS regions, or to some other subset of the IMS workload. You can use this technique of multiple inquiry executions under different execution-time parameters to create unique, tailored reports for different readers. Once an inquiry has been added to the job stream, you can enter space parameters for individual inquiries. If omitted, they will default to the SAS work data set allocation for the job stream. If the SAS work data set has not yet been defined for the job stream, the SAS work data set space allocation will default to the definition provided by the CA MICS administrator in MWF;5;0;4. You should also note that the archive (tape) option of the CA MICS file cycle(s) parameter is not valid for production reporting. MICF production reporting uses dynamic allocation to access CA MICS files, and CA MICS does not support dynamic tape drive allocation.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |