Automatic MICF Inquiry Generation
Exclusive to the User Reporting Jobstream facility is the ability to generate automatically MICF inquiries from your own independent SAS source code or Q&R developed queries, and include them in your user reporting job stream.
micsrm140
Exclusive to the User Reporting Jobstream facility is the ability to generate automatically MICF inquiries from your own independent SAS source code or Q&R developed queries, and include them in your user reporting job stream.
These automatically generated MICF inquiries are always written to your private inquiry catalog.
Automatic inquiry generation can also be performed outside a user reporting job stream, by selecting MICF Option 6. MICF Option 6 generates a MICF inquiry to your private inquiry catalog, without adding it to a reporting job stream.
Prerequisites
The Automatic MICF Inquiry Generation feature has the following requirements:
- The independent SAS code (program) or Q&R developed query must reside in a PDS accessible to MICF.
- The SAS code must be self-contained. That is, it must provide its own file allocations, such as a LIBNAME statement to allocate anyMICSdatabases that may be required by the program.
- These inquiries cannot use execution-time parameters.
These requirements are in effect regardless of where the feature is invoked, in a user reporting job stream, or if MICF Option 6 is selected.
Using Automatic MICF Inquiry Generation
Sample Define Source Data Sets
---------------- Inquiry Generation - Define Source Data Sets ------------- Command ===> Scroll ===> CSR Press END to process the query data sets. Enter CANCEL to terminate. Default Catalog Group: Name: ===> DATACOM Title: ===> CA-DATACOM/DB Extracts Input Data Sets: sharedprefix.MQR.PUTPDS: ===> 'MDI.PROD.MQR.PUTPDS' User defined data set: ===> 'MDI.MQR.QUERYS' Line Cmds: S Select Catalog Cmd Group Catalog Group Title - -------- --------------------------------------- _ ALERT IS Management Alert _ AVAIL Availability Analysis _ BATCH Batch Catalog _ DATACOM CA-DATACOM/DB Extracts _ EXCEPT Exception Analysis - -------- -------------------------------------------
To use the Automatic MICF Inquiry Generation feature of User Reporting Job Stream, follow these steps:
- Select your User Reporting Job Stream from the User Reporting Administration Panel, or Insert a new one.
- Enter a Y in the "Specify Inquiries for Reporting Jobstream" and press ENTER.
- From the Inquiry Selection Options menu, select Option 3: "Select Source for Automatic Inquiry Generation" and press ENTER.The "Inquiry Generation - Define Source Data Sets" panel s displayed. Here you specify the name of your source data set as input to the Inquiry Generation feature.Note:The Automatic Inquiry Generation Option is also available directly from MICF as option 6 (MWF 2;6.) MWF Option 2.6 functions the same, however the generated MICF inquiries are not added to a User Reporting Job Stream. MWF Option 2.6 is useful when you intend to promote the inquiries to the Shared Inquiry Catalog to include in a Production Reporting Job Stream.
- On the "Inquiry Generation - Define Source Data Sets" panel, the data set name of Q&R query data set included with theMICS Complexshould already be defined. An extra line is included for a user-defined data set. This data set defaults to the last value entered, or blank, if this panel has not been visited previously.If the data set names are not enclosed in quotes, and your TSO profile includes a PREFIX, the prefix is added to the data set name.
- Select or enter the Default Catalog Group Name under which the inquiry is saved.This field is a 1-8 character name and is required. This field defaults to the last value specified for this parameter.
- The Catalog Group title is a 1-40 character name that describes the catalog group, and is required. This title defaults to the last value specified for this parameter.When the Catalog Group is selected from the table display at the bottom of the panel, the Default Catalog Group title is automatically populated based on the Catalog Group selected. This title can also be entered manually.After you have completed this panel, press END. MICF dynamically allocates and processes these data sets. The results are presented in a tabular form to allow you to select members, rename inquiries, and define the inquiry generation method that you want to use for each inquiry.
MICF Inquiry Generation Member Selection
Once you have completed the "Inquiry Generation - Define Source Library" panel and pressed ENTER, the results are displayed in a subsequent table display of your partitioned data set (PDS or PDSE). Sample Source Member Selection panel is an example.
Sample Source Member Selection
Command ===> Scroll ===> CSR Catalog Group: BATCH Catalog Group Title: Batch Catalog Replace Existing Inquiry ===> NO (YES/NO) Line Cmds: B Browse S Select U Unselect Member Query Execute Cmd Name Name From PDS? Query Title - ------- ------ --------- ---------------------------------------- _ #TSTEMP1 +EMPTYS NO zOS Daily Top 10 Service Classes _ #TSTEMP2 +EMPTYS YES Empty File Report _ #IBDAILY2+IBDAIS NO User Reporting Generated Query _ #MQRHOST +MQRHOS YES User Reporting Generated Query _ #NEWQRM4 +RMFQRS NO zOS Daily Service Classes _ #RMFCPU +RMFCPS NO RMF CPU Busy _ #RMFCSV +RMFCSS NO User Reporting Generated Query
The columns of this table display are described as follows:
Member Name
The name of the member as it exists in your PDS library. This name cannot be modified.
Query Name
If the member processed contains a Q&R developed query, the query name was derived from the MQR header included when the query was saved. Otherwise, the query name defaults to the first six characters of the member name.
Query Name can be modified to avoid conflicts with other members within this same PDS and MICF inquiries that may already exist in your private inquiry catalog. Query name must be unique.
Execute from PDS?
Defaults to NO. This field allows you to control the way the MICF inquiry is generated. There are two methods:
- When generating the inquiry, insert an independent SAS step in the inquiry that contains an %INCLUDE statement to the library and member that contains the code or Q&R query. Specify a Y in this column if you prefer to use this method.The use of the SAS %INCLUDE statement allows flexibility for those users inexperienced in MICF. Using this method eliminates the need to revisit MICF to modify the inquiry (source code), as it is read at execution time directly from the external PDS.
- Embed the code within MICF. The embedded code is the default. Each line of the source code is written to an ISPF table stored within MICF as an Independent Source step.
To modify the inquiry, once it has been generated requires a subsequent visit to MICF. Select MICF Database Inquiries (MWF;2;2) and select the inquiry (S or M line commands) to see the individual steps. Select the Independent Source Statements step to modify the SAS code. Your modifications are saved when you use the END key (or command) to exit.
Alternatively, you can revisit the Automatic Inquiry Generation Option of MWF (2;6) to replace the existing inquiry using the contents of the corresponding PDS member.
Query Title
If the member processed contains a Q&R developed query, the Query Title is derived from the query title in the MQR header included when the query was saved.
Otherwise, if the Automatic Inquiry Generation Option was executed from MICF (MWF;2;6), the query title defaults to "MICF Generated Query". If the Automatic Inquiry Generation was executed from within a User Reporting Job Stream, (MWF;2;5), the query title defaults to "User Reporting Generated Query." A query Title can be modified from this panel and does not need to be unique.
From this panel, you can select, the S line command, for those members that you want to generate MICF inquiries, and include them in your user reporting job stream.
Note:
Generated MICF inquiries are always written to your private inquiry catalog. If you are executing this option from MICF (MWF;2;6), the inquiries are generated and written to your private inquiry catalog, but they are not added to any User Reporting Job Stream.After selecting members and modifying any of the columns you want to change, press ENTER. For example, query name or query title. MICF validates your selections using the following criteria:
- The selected members are compared to ensure that no duplicate query names are selected. If duplication occurs, a message to that effect is issued and the cursor is placed at the offending row, and the row is marked with an E.To resolve this error condition, use one of the following methods:
- Use the U line command to clear one of the duplicate members.or
- Change the name of one of the selected members by overtyping the name in the Query Name column, and use the S line command to select the member again.
- More checking is performed to ensure that a MICF inquiry does not already exist with the same name as the name in the Query Name column. When a duplicate name is found, the selected members are identified by an "E" in the CMD column.To resolve this error condition, use one of the following methods:
- Set the Replace Existing Inquiry option to Y (YES) to replace the existing MICF inquiry.or
- Change the name of one of the selected members by overtyping the name in the Query Name column, and use the S line command to select the member again.
If you are executing this option directly from MICF (MWF;2;6) the inquiries are generated into your private MICF inquiry catalog. If you are executing this option from within User Reporting Job Stream Administration (MWF;2;5), the inquiries are generated into your private MICF inquiry catalog and added to your User Reporting Job Stream.Upon successful completion, you receive the message, "Inquiry Generation Complete."