|MVS Appendix 5: The Transition from MXG Software to IT Service Vision Software with MXG|
You can make the transition from MXG alone to IT Service Vision with MXG without throwing away any existing data or report programs (report definitions). This appendix will walk you through the steps.
When you process data into an IT Service Vision PDB, as an early step in the processing, the IT Service Vision server invokes MXG software. More specifically, for each kept table in the IT Service Vision PDB or for each table in your supplied list (in the %CMPROCES macro), the IT Service Vision server invokes the MXG macro that builds the corresponding MXG data in a temporary (staging) data set. The data are then further processed into the IT Service Vision PDB.
You will probably want to continue to run both processes in parallel while you are getting acquainted with IT Service Vision. After a period of running in parallel, you can discontinue running BUILDPDB (the job that loads the MXG PDB).
With maintenance level TS45501, a new macro called %CMEXTDET became available. It is designed to support the reduction of data that is currently held in a MXG PDB into an IT Service Vision PDB without having to re-process it. This also allows you to "import" MXG history (but not trend) data that may be held on tape. For more details, please see the Macro Reference documentation for IT Service Vision.
If you generate MXG views in the IT Service Vision PDB, you can run existing MXG report programs against the data in the IT Service Vision PDB without modifying the programs.
Your IT Service Vision PDB has MXG views by default. To check that the setting has not changed, follow this path from the IT Service Vision server's main menu:
PDB Admin -> Set Active PDB Options
Provide PDB MXG
Views selection should be set to Yes.
If not, set it to Yes.
Once the MXG views have been built, you can run
existing MXG report programs against your IT Service Vision PDB.
An example of running the MXG
against the demonstration PDB follows:
//$PDBGRAF JOB /*JOBPARM FETCH //LOAD EXEC SAS,REGION=32M,WORK='2000,500', // OPTIONS='SOURCE MEMSIZE=32M DMSBATCH BATCH TERMINAL' //PDB DD DSN=your.pdb.name.DETAIL,DISP=SHR //SOURCLIB DD DSN=mxg.userid.sourclib,DISP=SHR // DD DSN=mxg.mxg.sourclib,DISP=SHR //SYSIN DD * options sasautos=(sourcelib sasautos) mautosource noimplmac errorabend dquote ; options pagesize=60 linesize=132 ; %grafrmfi(pdb=PDB,device=IBM3179,company=Your Company, display=n,mxgraphs=DEMO,goutnew=yes);
The sasautos option concatenates your library of modified MXG macros and the library of unmodified MXG macros. The %GRAFRMFI macro produces graphs from the IT Service Vision table XRMFINT, which it sees by means of the IT Service Vision view RMFINTRV. These graphs will be put into a SAS catalog named DEMO in the library with libname PDB.
You can put an icon in the IT Service Vision server's main menu to make it easy to view the graphs generated by your MXG report programs. See Section 1, Task 3: Create a Test PDB and Process, Reduce and Report on Your Data for an example of adding an icon to the IT Service Vision server's main menu for graphs generated by your IT Service Vision report definitions.
For data without a variable named DATETIME, you will need to define DATETIME. For example, the following program creates a data step view, which effectively copies the TYPE70 data set and creates the DATETIME variable. Minimal space is needed for this view because the view only copies the data when the view is invoked by, for example, a report.
libname mxgpdb 'your.mxg.pdb' disp=shr; data sasuser.type70/view=sasuser.type70; format datetime datetime16.; set mxgpdb.type70; datetime = startime; drop startime; run;
Use the PF8 key (or whichever key is associated
with the NEXT command) to cycle through the active SAS windows
until the PROGRAM EDITOR window displays. Type in and submit this
program. Check in the SAS log that there are no errors. Return to
the CPE window by continuing to press PF8 or by typing
on the command line and pressing ENTER or RETURN.
To continue the above example and produce a One Y-Axis Plot based on the view in the SASUSER library,
Reports -> DesignGraphRpt -> One Y-Axis Plot -> select level Other -> select library SASUSER
Select the table icon (the icon in the upper left corner) and then select TYPE70. Select Y Variable and then PCTCPUBY. If you have more than one system, select By Variable and then SYSTEM. Select DateTime Range, Reset from PDB, and OK. On the main report definition window, select Actions and then Run Report.
Note: You use level "Other," above, instead of levels like detail, day, week, month, and year.