5. MICF Administration › 5.1 Tasks Performed During Installation › 5.1.6 Production Reporting › 5.1.6.8 Q&R Integration › 5.1.6.8.3 Directory Structure

5.1.6.8.3 Directory Structure

Q&R Integration stores all its information in an HFS/zFS
directory and should not be used by other applications.  This
interface builds a specific directory structure required by
the Q&R distributed server.

Note: The inquiry name must NOT include the '#' character.
The '#' character is interpreted by the UNIX environment
as a command, which causes an error.

   /Q&R root/+
        |
     "Server"/+
        |
       MF server name/+
             |
          long catalog name/+
                   |
               jobstream_name/+
                           |
                        query name - query title/+
                                   |
                               run date/+ (yyy-mm-dd)
                                     |
                                 run time/+ (hh-mm)
                                   MICSLOG.TXT
                                   SASLIST.TXT
                                   SASLOG.TXT
                                   csv title.CSV


Figure 2-75.  HFS/zFS Q&R Integration Directory Structure

Q&R root is the name of a directory where the Q&R Integration
feature stores MICF inquiry output for access by the Q&R
Workstation.  The Q&R root can be the same as the MICF Web
Publishing root directory as they write different directory
structures.  Typically you would not activate both MWP and
Q&R Integration unless you are migrating from the use of MWP
to Q&R to take advantage of the Q&R charting capabilities.

The Q&R root directory must be created before activating this
feature and executing your reporting job stream.

Each "query name - query title" directory contains a
subdirectory of run date and run time, using the format
yyyy-dd-mm/hh-mm.

Each time directory (hh-mm) contains the inquiry output
generated during execution.  HH-MM is the time of the job
stream execution and may not represent the actual time the
inquiry itself executed.

.  MICSLOG.txt
.  SASLIST.txt (if no report was generated, it will be empty)
.  SASLOG.txt
.  csv title.CSV

Multiple CSVs can be created in the same MICF inquiry, but
must have different titles.

Note: If a job stream contains multiple instances of the same
inquiry, for example an inquiry executed multiple times for
different units, the nth execution is stored under the hh-mm
time with the execution order appended to the directory name.
This allows you to differentiate one inquiry output from
another by the order in which they executed.  For example:


. . . ./RMFED1 - MVS CPU and ASID Activity (.csv)
        /2011-09-01
         /10-19
           MICSLOG.txt
           SASLIST.txt
           SASLOG.txt
           Daily - MVS ASID Activty by System.csv
           Daily Percent CPU busy by System.csv
         /10-19 (4)
           MICSLOG.txt
           SASLIST.txt
           SASLOG.txt
           Daily - MVS ASID Activty by System.csv
           Daily - Percent CPU busy by System.csv