• A Collection of Tips
• Tips for Subsetting Data
  • Subsetting via DATETIME
  • Subsetting by a Simple Local Where Expression
  • Subsetting by a Simple Global Where Expression

A Collection of Tips

Here are some tips that may be useful to you as you generate reports with IT Service Vision.

• Test report definitions on a small subset of your data so that the testing proceeds quickly.

  For details, see Tips for Subsetting Data in this appendix.

• If running your report does not seem to produce any results, be sure that you are looking for the report in the correct window. The default window for graph reports is the SAS GRAPH window. The default window for text reports is the SAS OUTPUT window. (For more about accessing windows, see Shared Appendix 2: Navigating SAS Windows.)

  You can override those defaults from the report's main definition window by selecting Output Options, Graphics Window or Output Window, and OK.

• If running your report definition produces unexpected results, examine the SAS log for messages.
• Some IT Service Vision supplied report definitions require setup to run properly.

  Follow this path from the server's main menu:

     Reports -> Supplied Rpts ->
     select the report definition ->
     ItemActions -> Explanation
  

  to be certain that you have met all the setup requirements for a report definition.

• If you get the No observations were selected message, check the following:
  • Does the SAS log display the report definition that you ran? Check to see that you are running at the PDB level (REDLVL) at which you have data. For more information about the SAS log, see Shared Appendix 2: Navigating SAS Windows.
  • Check to see that you are running with the date range (BEGIN and END) in which you have data.

    For more about date range subsetting, see Subsetting via DATETIME in this appendix.

  • Check to see that you are running with a subsetting WHERE expression (Local Where or Global Where) for which you have data. If not, and you are running a supplied report definition that requires setup, the lack of a subsetting WHERE expression could easily be the cause. Check the Explanation for the report definition.

    For more about a subsetting WHERE expression, see Subsetting by a Simple Local Where Expression in this appendix and Subsetting by a Simple Global Where Expression in this appendix.

  • Check to see that there really are data in the table at the level in that date range for the variables in the report definition. From the IT Service Vision server's main menu, follow this path:

       PDB Data -> Examine PDB Data ->
       select the table -> ItemActions ->
       Browse Data or View Data
    

    Then, if you are looking for specific information, you may want to subset the data by using a WHERE expression. For instance, if you are looking for observations on machine 41TS because a graph shows an outlier value for that machine, you could follow this path from the FSBROWSE window:

       Search -> Where ->
       type machine='41TS' -> OK
    

    Note: You can also use other methods to browse your data. For more information, see MVS Appendix 4: Alternate Data Browsing Method.

  • If the data that you see in your table using Browse Data or View Data are unexpected, check the table's definition. From the IT Service Vision main menu, follow this path:

       PDB Admin -> Config Active PDB Dictionary ->
       select the table -> ItemActions ->
       Browse Definition
    

    Check that the Kept status of the appropriate table is set to Yes and the appropriate levels are set to non-zero durations.

    On the table definition window, select Variables to check the variables' definitions. Check that the Kept status of the appropriate variables is set to Yes. For the non-detail levels, check that the appropriate statistics are selected. (For a formula variable, check that the variable is defined at the appropriate level and that the table and variables on which it is based are defined appropriately. To check the levels for which it is defined, select the formula variable and then ItemActions and Edit Definition.)

    Note: A formula variable does not have selectable statistics. If you want statistics on a formula variable, you must define the statistics as formula variables at the desired non-detail levels.

  • Check that the collector was configured correctly to provide the metrics.
  • If you do not get the "No observations" window but you get no report, perhaps all data values are missing. That is, the observation may exist but the value on the observation may be set to a SAS missing-value code.

    At detail level, this can occur if you have not set up data logging properly. At all levels, this can occur for a formula variable if it is not defined properly or if the statistics on which it is based are not selected at the levels specified for the formula variable or if the base variables for the statistics have a Kept status of No.

    Note: A formula variable does not have selectable statistics. If you want statistics on a formula variable, you must define the statistics as formula variables at the desired non-detail levels.

• For the type of report definition that you are running, select the report type from the pull-down menu under DesignGraphRpt or DesignTextRpt. Then read the Help file. (Help files contain tips on generating reports.)
• The most probable cause of this message

     ERROR: The left vertical axis labeled <varlabel> could not be fit
     as specified.
  

  in a graph report is that you have more classes than will fit in the legend on the graph.

  A solution to this problem is to increase the height of the GRAPH window. From the report's main definition screen, select Output Options. Edit the GOptions field from

     DEVICE=value
  

  to

     DEVICE=value  VPOS=100
  

  where VPOS=100 means a vertical height of 100 rows. Then re-run the report definition.

• Add formula variables (variables that are calculated only when accessed) to simplify reporting.

  For details, see Section 2, Task 6: Wrap Up.

Tips for Subsetting Data

Subsetting via DATETIME

If your report displays no observations (you get an empty report) or if your report displays observations in only one part of the date range of the processed or reduced data, you may need to reset the report definition's datetime range.

Follow this path from the report's main report definition window:

   DateTime Range -> Reset from PDB -> OK

IT Service Vision looks in the PDB's data dictionary to find the earliest and latest DATETIME values at the level that is specified on the main report definition window.

If you want to use less of that range, you can type over the values in the Begin and End fields.

Note: The need to reset may occur when you are designing or modifying report definitions and switch from one table to another or one level to another. The begin and end points of the range are global variables that retain their values until you change them or switch the active PDB.

Subsetting by a Simple Local Where Expression

A Local Where expression applies to a single report definition.

If your report definition generates a report that includes observations in which you are not interested, you can use the Local Where to restrict the observations to the ones in which you are interested. For instance, suppose you have a report definition with a BY variables list that includes MACHINE, and you have many machines but you are only interested in a few of them for this report definition. Rather than get dozens of graphs and ignore all but a few, you can generate just the ones you want to see.

From the report's main definition screen, select Local Where. Under Local subsetting follow this path:

   Varname -> MACHINE -> Operator ->
   IN -> Value(s) ->
   select the machines on which you want to report ->
   OK -> OK

This method is not restricted to subsetting by MACHINE. You can subset by any variable that is in the specified level of the specified table. For instance, you can report on only first shift data by using this WHERE expression:

   SHIFT = '1'

If you want to subset by more than a few values, you may want to create a user format.

Note: By default, if there is an expression in the Local Where, it overrides the expression, if any, in the Global Where. If you want the report definition to use both the Local Where and the Global Where, insert the words SAME AND in front of the WHERE expression in the Local Where.

Subsetting by a Simple Global Where Expression

A Global Where expression applies to all report definitions.

You may want to generate a number of reports with the same subsetting; for this, use a Global Where expression. For instance, you may be having trouble with a few machines and want to run a number of reports for just those machines. In this case, rather than changing the Local Where for each report, you can set the Global Where (on any report definition) and it will apply to all report definitions until you reset it to blank.

From the report's main definition screen, select Global Where. Under Global subsetting follow this path:

   Varname -> MACHINE -> Operator ->
   IN -> Value(s) ->
   select the machines on which you want to report ->
   OK -> OK

This method is not restricted to subsetting by MACHINE. You can subset by any variable that is in the specified level of the specified table. For instance, you can report on only first shift data by using this WHERE expression:

   SHIFT = '1'

If you want to subset by more than a few values, you may want to create a user format.

Note: By default, if there is an expression in the Local Where, the Global Where is ignored (unless the Local Where starts with the words SAME AND).