Execution-Time Data Selection

Some MICF inquiries are made more general by allowing you to specify information such as the range of
MICS
file cycles or the system identifier (SYSID) to be reported on at execution time.
micsrm140
When you select such an inquiry, MICF automatically takes you to the Execution-Time Parameters panel.
Sample Execution-Time Parameter Panel is an example of such a panel after the database ID,
MICS
File Cycle, and the IMS region parameters have been entered.
Sample Execution-Time Parameter Panel
------------------------- Execution-Time Parameters ------------------------- Command ===> end Scroll ===> CSR Press END to execute the inquiry. Enter CANCEL to cancel inquiry execution. Executing
MICS
Inquiry: IMSCD2 - Daily IMS Service Reports icfe130b ------------------------------------------------------------------------------ Enter one or more Database IDs for the Database(s) you want to process. I - _____________________________________ Enter range of
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 ********************************
Note:
The analyst wants MICF to report on all systems, and so has left the SYSID parameter blank. The analyst has also entered PROD for the IMS region parameter to limit the report to production IMS regions starting with PROD.
Since END has been entered in the command line, the inquiry executes when ENTER is pressed. The END PF key would have the same effect.
If you have chosen to execute the inquiry in foreground, MICF first gives you a series of messages stating that SAS is being invoked in foreground and that it is generating the source code. When the inquiry is complete, you see the report if there is one or you are shown the Inquiry Output Replay panel. The Inquiry Output Replay panel works in the same way as the Cataloged Inquiry Output Replay panel. The only difference is that the Inquiry Output Replay panel has an additional option, Option 6, Catalog Inquiry Output, which lets you save the inquiry report, log, and color graphics in your private inquiry output catalog.
Tip:
When MICF displays the
MICS
file cycles execution-time option (like in Execution-Time Parameter Panel), you can process the online
MICS database
or the
MICS
archive database:
  • If you specify a cycle range (for example, 01 or 01 - 07), MICF executes the inquiry against the specified online file cycles.
  • If you specify ARCHIVE (A), MICF executes the inquiry against the corresponding
    MICS
    archive (tape) file. Remember that the archive option is valid only for batch execution. MICF does not support dynamic foreground tape drive allocation.
MICF allocates the most recent (that is, 0) archive generation unless you specifically request another generation. For example, you could specify ARCHIVE-2 for the -2 generation. MICF uses the archive audit tape for DETAIL or DAYS timespan
MICS
files, the weekly archive history tape for WEEKS files, and the monthly archive history tape for MONTHS files. Archive is not available for application database files (for example, the Financial Recap file, ACTRCP) or YEARS timespan files.
Note:
You cannot access archive files if any
MICS
File Selection inquiry steps that allow execution-time cycle override reference files that are not archived. An error message explains why archive access is not available.
In the
MICS database
ID execution-time option, you can enter a single
MICS
Unit database (DB) ID or a list of DB IDs separated with blanks. This technique lets you execute the inquiry against a single
MICS database
or concatenate data from multiple databases.