Setup for IT Service Vision Server

Section 1, Task 3: Create a Test PDB and Process, Reduce, and Report on Data Action 3: Generate one or more reports on the date in your test PDB

Review the model job's partial job step:

    *--------------------------------------------------------------*
    * The following are some sample reports you might want to run. *
    *--------------------------------------------------------------*;

    /*---------------------------------------------------------------*
    |                     IT Service Vision Report
    | Report Name: PAGRD
    | Dataset:     XTY71
    |
    *---------------------------------------------------------------*/


   GOPTIONS reset=title reset=footnote DEVICE=IBM3179   #1
            COLORS=(WHITE RED BLUE);
   TITLE1 "Demand paging rate during day";
   %CPPLOT1(XTY71,DPR,Demand paging                     #2
            ,STAT=MEAN
            ,PERIOD=24HOUR
            ,BY=MACHINE
            ,WEIGHT=DURATION
            ,XVAR=DATETIME
            ,XLAB=Date
            ,TYPE=STACK
            ,REDLVL=DETAIL
            ,OUTMODE=GRAPHCAT                           
            ,OUTLOC=ADMIN.CPEGRAFS                      #3
            ,OUTDESC=PAGING REPORT                      
            ,OUTNAME=PAGING);                           
		.
		.                                       #4
		.

Notes:

You may need to change the value of the DEVICE= parameter on the GOPTIONS statement. This parameter specifies the SAS device driver for the device on which the reports will be viewed.
For more on SAS device drivers, see the prerequisites in MVS Appendix 3: Printing Graphs. (In that appendix, you select a driver for your printer/plotter type.) Here, you select a driver for your monitor type.
The %CPPLOT1 macro is one of the IT Service Vision reporting macros. IT Service Vision has one macro for each type of report that it can create. For more information on the reporting macros, see the Macro Reference documentation for IT Service Vision.
The OUTLOC= parameter specifies where to store the resulting graph. This job stores it in the CPEGRAFS catalog in the test PDB's ADMIN library.
For the sake of brevity, the remaining report definitions are not shown. However, they require the same OUTLOC= parameter as the first report definition.

Review the output from the model job's partial job step:

129730      /*- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -*
129731      |                     IT Service Vision Design Report                 #1
129732      | Report Name: PAGRD
129733      | Dataset:     XTY71
129734      |
129735      *- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -*/
129736
129737
129738     GOPTIONS reset=title reset=footnote DEVICE=IBM3179
129739              COLORS=(WHITE RED BLUE);
129740     TITLE1 "Demand paging rate during day";
129741     %CPPLOT1(XTY71,DPR,Demand paging
129742              ,STAT=MEAN
129743              ,PERIOD=24HOUR
129744              ,BY=MACHINE
129745              ,WEIGHT=DURATION
129746              ,XVAR=DATETIME
129747              ,XLAB=Date
129748              ,TYPE=STACK
129749              ,REDLVL=DETAIL
129750              ,OUTMODE=GRAPHCAT
129751              ,OUTLOC=ADMIN.CPEGRAFS                                        #2
129752              ,OUTDESC=PAGING REPORT
129753              ,OUTNAME=PAGING);
***************************************************************
NOTE: OUTMODE=CATALOG  gout = ADMIN.CPEGRAFS  name = "PAGING"
***************************************************************
              .
              .                                                                   #3
              .

Notes:

After reduction completes, this report runs against the data in the detail level of the PDB.
The parameters OUTMODE=, OUTLOC=, OUTDESC=, and OUTNAME= control the destination of the report that is generated. In this case, the destination is ADMIN.CPEGRAFS.PAGING.GRSEG, where ADMIN is the ADMIN library in the active PDB, REPORTS is a catalog (new or existing) in that library, and PAGING is an entry of type GRSEG in that catalog.
For the sake of brevity, the remaining reports in the CMQSTART job are not shown.

Tailor the partial job step to your collector's data.

Display the list of supplied report definitions.
From the main menu of the IT Service Vision server interface, follow this path:

Explore CPE -> All Supplied Reports -> Edit -> Sort -> Report Name

Select (click on) the report definitions that you want to save as a file.

For example,

Collector	Reports	Description
DB2	M2GBLM01	DB2 Overview
	M2CPUM01	DB2 Task CPU time and Thread Creation
	M2MEMQ01	DB2 Free Pages
	M2INOE01	DB2 Physical DB Page Requests
DCOL	MDAPPU01	Allocated Space by usage Group
	MDAPPU03	DASD Application Volumes Free Extents
	MDAPPU04	DASD Volumes Averages by Use Group for Month
RMF	MMMEMT03	Paging Rate During Day
	MUAPPRU1	TSO Trivial Response vs. Number of TSO Users
	MWMIXM01	Workload Analysis
	MWMEMOWS	Storage Avg. Working Set Size in KB.
	MDDSKR02	DASD Response Time and Analysis
	MDDSKRX1	Top Ten Average DASD Response Times
	MMAPPTSW	Paging - Swaps by Preformance Groups

Save the report definitions to a file by following this path:

ItemActions -> Preview Source -> File -> Save As -> Write to a file... -> type the name (without quotes) of a file -> Replace -> OK

Note: In this section, you use specified report definitions. Later, in Section 2, you will customize the report definitions to a file.

Note: For other collectors other than the ones in the table above, select report definitions based on Shared Appendix 7: Supplied Report Naming Convention.

If there are no supplied reports for your collector/data source, make at least one report definition and save it in a file. For information on creating report definitions and for examples, see the Reporting Macros in the Macro Reference documentation for IT Service Vision. For convenience use the %CPPLOT1 macro. You may find helpful (as a model) the following sample report definition that is based on fax data (ignore the text "To save follow..."):

GOPTIONS reset=title reset=footnote DEVICE=IBM3179
         COLORS=(WHITE RED BLUE);
TITLE1 "Pages sent or received";
%CPPLOT1(UFAXES, PAGES, Pages sent/rec
         ,STAT=MEAN
         ,PERIOD=24HOUR
         ,BY=MACHINE
         ,XVAR=DATETIME
         ,XLAB=Date
         ,TYPE=STACK
         ,REDLVL=DETAIL
         ,OUTMODE=GRAPHCAT
         ,OUTLOC=ADMIN.CPEGRAFS            #1
         ,OUTDESC=FAX PAGING REPORT
         ,OUTNAME=FXPAGES);

Notes:

The parameters OUTMODE=, OUTLOC=, OUTDESC=, and OUTNAME= control the destination of the report that is generated. In this case, the destination is ADMIN.CPEGRAFS.FXPAGES.GRSEG, where ADMIN is the ADMIN library in the active PDB, REPORTS is a catalog (new or existing) in that library, and FXPAGES is an entry of type GRSEG in that catalog.
To save follow this path for the SAS window:

File -> Save as

You may want to save this report macro before submitting it, or you will have to recall the text from the PROGRAM EDITOR window.

Return to the main menu.
Follow this path

File -> End -> File -> End
Edit the file of report definitions to specify the destinations for the reports that they generate.
1. For each report that is generated by %CPPLOT, %CPPLOT2, %CPSPEC, %CPCHART, %CPCCHRT, or %CPG3D, add OUTMODE=, OUTLOC=, OUTNAME=, and OUTDESC= parameters. Use a comma to separate each parameter from the previous parameter.
  Use:
  
  ,OUTMODE=CATALOG
  ,OUTLOC=ADMIN.CPEGRAFS
  ,OUTNAME=report_name
  ,OUTDESC=report_description
  
  where report_name is the name of the supplied report definition and the name must start with a letter or underscore and contain a total of one to eight characters (letters, numbers, and/or underscores), and report_description is a shortened version (as many as 40 characters) of the report title.
  
  Note: These reports will be formatted as graphics and saved to the CPEGRAFS catalog
2. For each report that is generated by %CPTABRPT or %CPXTAB,
  Add the OUTMODE= parameter as follows:
  
  ,OUTMODE=LP
  
  Note: These reports will be formatted in ASCII and printed.
  
  Note: The OUTMODE parameter can also be set to LPCAT. If the value is LP, the output is formatted in ASCII and printed. If the value is LPCAT, the output is formatted in ASCII and stored in a catlog using the same OUTLOC=, OUTNAME=, and OUTDESC= paramters as above.
Add the edited report definitions to the end of the job step that processed or reduced the data.
Submit your batch job.
When your job completes, check the SAS log for ERROR messages. If you find any, locate and fix the problem and re-submit the job.