* copyright (C) 1984-2019 merrill consultants dallas texas usa

VMACEDGS in informat (i.e., they should be "&PIB.2. " instead of

Oct 12, 1993 "&PIB.2 "). Invalid data results without this change!

Change 11.208 The example AUTOEXEC.SAS for OS/2, Windows, and Unix did

AUTOEXEC not invoke %VMXGINIT, but only included it! Change to:

Oct 11, 1993 %INCLUDE SOURCLIB(VMXGINIT); %VMXGINIT;

(Why did I %INCLUDE the macro first, when only its

invocation is required, since MXG uses MAUTOSOURCE?

Because I frequently SAS GO under TSO, and changes to

VMXGINIT did not take effect with the "GO" option!)
Change 11.207 Support for TOP-SECRET type 80 records written to a log

TYPE80 instead of to SMF is accomplished by changing " _SMF "

TYPE80A reference in TYPE80/TYPE80A to " _NETVLOG ". These log

Oct 11, 1993 records are written with only one 4-byte RDW field, so

the MVS RECFM=VBS or RECFM=VB or RECFM=V won't work (all

MVS variable records have both a 4-byte BDW and a 4-byte

RDW). The _NETVLOG macro defined in VMACSMF, used in

place of the _SMF macro, handles this "DOS RECFM=V" data.

Note: MXG members TYPE80/TYPE80A were not changed by this

change; this is an optional change that you must make if

you must process these records from a log instead of SMF.

Thanks to Jan-Ake Christoffersson, GotaData, SWEDEN.

Change 11.206 WEEKBLD/MONTHBLD error "DATA SET TAPEMNTS IS NOT SORTED"

MONTHBLD occurs IF you install Change 11.040, as it was incorrect.

WEEKBLD The correct order for TAPEMNTS (and TYPETMNT) in both

Oct 11, 1993 WEEKBLD and MONTHBLD is:

BY SYSTEM SHIFT DEVICE TMNTMTYP TMNTTIME;

Thanks to Bill Stoneberg, National-Oilwell, USA.

Change 11.205 This change to ANALVVDS and VMACVVDS are needed ONLY if

ANALVVDS you want ANALVVDS to correctly report VSAM statistics.

VMACVVDS Except for adding variable VVRTYPE to TYPEVVDS for that

Oct 11, 1993 report, this change does not alter data set TYPEVVDS:

Variable VVRTYPE was added to the KEEP= list in VMACVVDS,

so that ANALVVDS can test VVRTYPE to prevent the MXG

generated "***NUMEXT" error messages printed because

that report program did not anticipate the existence of

NVR (non-VSAM records) in a VVDS! For the VSAM space

analysis, NVR records must be deleted by inserting

IF VVRTYPE='N' THEN DELETE; after SET MXGVVDS.TYPEVVVDS;

Unfortunately, I discovered that I had reused variable

VVRTYPE, and the value kept was from its second use! To

correct, rename all VVRTYPE to VVRSTYPE in VMACVVDS,

except for its KEEP, LABEL, and the first INPUT statement

and for all tests of '00'x, 'D8'x, 'E9'X, and 'D5'x,

which must still use VVRTYPE).

Thanks to Billy Westland, Hitachi, USA.

Change 11.204 Dataset TYPEVVDS variable VVRBSENM can be blank because

VMACVVDS this test in VMACVVDS:

IF VVRCATNL THEN INPUT VVRBSENM $VARYING. VVRBSENL @;

Oct 11, 1993 must be changed to:

IF VVRBSENL THEN INPUT VVRBSENM $VARYING. VVRBSENL @;

Thanks to Billy Westland, Hitachi, USA.

==Changes thru 11.203 were included in MXG PreRelease 11.07 dtd 4Oct93=
Change 11.203 TYPE60 observations for NVR records have missing SMS

VMAC60 Storage, Data, Management Classes; alignment was off by

Oct 4, 1993 one byte. Change @OFFNVR+04 to @OFFNVR+03, and in the

following line change @OFFNVR+05 to @OFFNVR+04.

Thanks to BIll Cassidy, IST, CANADA.
Change 11.202 Support for NETVIEW APAR OY66237 SMF Type 37 (Hardware

VMAC37 Monitor Log Record) coded for the ETHERNET LAN section,

Oct 4, 1993 but without actually seeing at a dump of a record with

the new data segment. Furthermore, it's not clear which

APAR added the data segment, as OY66237 is documentation

only.
Change 11.201 TYPE90 variables OLDDSN/NEWDSN were renamed OLDDSNSM and

VMAC90 NEWDSNSM (they are the old/new SMF dataset names) to

Oct 4, 1993 avoid conflict with TYPE80A variables OLDDSN/NEWDSN.

Change 11.200 PROC GPLOT can 0C4 ABEND, or CPU loop, unless you have

GRAFLPAR these options in effect on a GOPTIONS statement:

GRAFRMFI NOPCLIP NOPOLYGONFILL NOPOLYGONCLIP

GRAFTMNT This is a known SAS bug with no ZAP yet, but it can be

GRAFTRND circumvented by

GRAFTRND a) removing all GOPTIONS statements in members GRAFLPAR,

GRAFWORK GRAFTRND and GRAFWORK (the only ones with exposure),

VMXGGOPT b) changing the GOPTIONS in member VMXGGOPT by inserting

Oct 2, 1993 NOPCLIP NOPOLYGONFILL NOPOLYGONCLIP

after the existing line:

NOCHARACTERS NOCELL GOUTTYPE=INDEPENDENT

The bug only occurs when area fill is used with GPLOT.

Unrelatedly, TMNTMTYP is now labeled in GRAFTMNT,

V=NONE is added to three SYMBOL statements in GRAFTMNT,

and TRIVRESP is now FORMAT 6.2 in GRAFRMFI.

Thanks to Chuck Hopf, Primerica, USA.

Change 11.199 TYPE30_V and PDB.SMFINTRV variables INTBTIME/INTETIME can

VMAC30 be 100 seconds earlier that actual because my fuzzy logic

VMAC7072 to convert the GMT values to local time was too fuzzy!

Oct 2, 1993 The algorithm

GMTOFF30=100*FLOOR((SMF30IST-INTBTIME)/100);

must be replaced with

IF (SMF30IST-INTBTIME) GT 0 THEN

GMTOFF30=100*FLOOR((SMF30IST-INTBTIME)/100);

ELSE IF (SMF30IST-INTBTIME) GT . THEN

GMTOFF30=100*CEIL((SMF30IST-INTBTIME)/100);

because SMF30IST has 10 millisecond resolution, while the

INTBTIME has 1 microsecond resolution, and IST=30:19.70,

INTB=30:19.7064 created a GMTOFF30=-1:40.00 (-100 secs)

instead of zero, due to the FLOOR of a negative number!

TYPE70 variable SYNCTIME can also be incorrect. VMAC7072

GMTOFF70=100*FLOOR((STARTIME+DURATM-SYNCTIME)/100);

must be similarly replaced with:

IF (STARTIME+DURATM-SYNCTIME) GT 0 THEN

GMTOFF70=100*FLOOR((STARTIME+DURATM-SYNCTIME)/100);

ELSE IF (STARTIME+DURATM-SYNCTIME) GT . THEN

GMTOFF70=100*CEIL((STARTIME+DURATM-SYNCTIME)/100);

and the GMTOFF72 logic must be similarly replaced.

Note: This change revised by Change 11.229.

Thanks to Diane Eppestine, Southwestern Bell, USA.

Change 11.198 Type 42 subtype 4 records testing caused STOPOVER abend.

VMAC42 After the @; after the INPUT of TYPETEST, insert these

Sep 30, 1993 two statements: M1=-1; INPUT +M1 @;

Also, labels for variables JESNR and TYPETASK were wrong.

Thanks to John Maher, Home Savings of America, USA.
Change 11.197 TYPEQAPM causes SAS 6.07 to 0C4 ABEND IN FUNCTION DSRFMT

SAS 6.07 AT OFFSET 000200. Problem has just been discovered. Does

Sep 30, 1993 NOT fail with SAS 6.08.

Thanks to Freddie Arie, Lone Star Gas, TEXAS.

Change 11.196 New Partition Channel busy was incorrectly printed.

ANALRMFR Change ... PUT @20 PNCHANBY 6.2 @;

to read: ... PUT #LIN @COL+20 PCHANBY 6.2 @;

Sep 30, 1993 Change ... @13 CHANSHAR

to read: ... @COL+13 CHANSHAR
Change 11.195 Variable PNCHANBY was propagated into observations with

VMAC73 no activity. After the line that calculates PNCHANBY,

Sep 30, 1993 insert: ELSE PNCHANBY=.; to reset the value.

Thanks to Bruce Widlund, Merrill Consultants, USA.

Change 11.194 VMXGHSM did not output all observations in dataset DSR.

VMXGHSM The line IF DSNRTRKR = 0 AND DSNRTRKW = 0 THEN DELETE;

Sep 30, 1993 must itself be deleted, and in the OUT_DSR macro, replace

OUTPUT DSR; with

IF DSNRTRKR GT 0 AND DSNRTRKW GT 0 THEN OUTPUT DSR;

Thanks to Mr. Ertingshausen, RWG GmbH, GERMANY

Thanks to Chris Weston, SAS Institute Europe, GERMANY.
Change 11.193 Preliminary NDM support in 11.07 has now been tested with

EXNDMAE SMF records, uncovering these errors for early recipients

EXNDMCH a. Change all "PK2" to "PK1".

EXNDMDP b. Change the one "PIB.2 " to "PIB.2." (add a period).

EXNDMDT c. Add variables NDMRVOLS NDMSVOLS NDMRVOL1 NDMSVOL1

EXNDMFP to the KEEP list for NDMCT.

EXNDMGF d. Change occurrences of "+19+OFFSMF" to "+15+OFFSMF".

EXNDMMC e. Change the INPUT @15+OFFSMF statement to look like:

EXNDMRJ INPUT @15+OFFSMF

EXNDMRT NDMRECLN &PIB.2. /*NDM RECORD LENGTH*/

EXNDMSI NDMRTYPE $EBCDIC2. /*RECORD*SUBTYPE*/

EXNDMST @;

TYPENDML IF NDMRTYPE NE 'CT' AND NDMRTYPE NE 'PS' AND

VMACNDM NDMRTYPE NE 'PT' AND

VMACSMF NDMRTYPE NE 'WO' THEN DELETE;

Sep 30, 1993 INPUT HH &PK.1. /*HOUR*/

Oct 3, 1993 MM &PK.1.

This change also added support for all 22 subtypes, now

creating fifteen NDM datasets:

Dsname Description NDMRTYPEs

NDMAE Authorization Event AE

NDMCH Change Process Termination CH

NDMCT Copy Termination Record CT

NDMDP Delete Process Termination DP

NDMDT Display Termination DT,FT,SP,SN,SS

NDMMC PDS Member Copy Record MC

NDMFP Flush Process Termination FP,FS,TS

NDMGF General Function Termination GF

NDMPS Start Process PS

NDMPT Process Termination Record PT

NDMRJ Run Job Termination Record RJ

NDMRT Run Task Termination Record RT

NDMSI Signon File Record SI,SO

NDMST Stop NDM Event ST

NDMWO Authorization Event WO
Member TYPENDM processes the NDM Statistics from SMF.

The NDM Sample Library member ???????? provides the exit

code to write that data in an SMF record.
Member TYPENDML, added by this change, will process the

NDM Statistic File directly, for sites that did not write

their NDM data to SMF.

Thanks to Chuck Hopf, Primerica, USA.

==Changes thru 11.192 were in the Early MXG PreRelease 11.07 dtd 1Oct93=
Change 11.192 Additional cleanup and enhancement of RMF-like reports

ANALRMFR from MXG data sets continues.

Sep 28, 1993
Change 11.191 The ADOC documentation for data sets built from VM/ESA

ADOCVMXA (and VM/XA) MONWRITE records is now 150 pages, although

Sep 28, 1993 this documentation member is still in progress.
Change 11.190 Support for IBM's DFSMSrmm Removable Media Manager's

EXEDGRD Extract file created by IBM utility EDGHSKP creates six

EXEDGRO new MXG data sets (equivalent of EDGRPTD reports):

EXEDGRP EDGRDEXT - DFSMSrmm Extract Data Set Name Record

EXEDGRR EDGROEXT - DFSMSrmm Extract Data Set Owner Record

EXEDGRS EDGRPEXT - DFSMSrmm Extract Data Set Software Product

EXEDGRV EDGRREXT - DFSMSrmm Extract Data Set Rack Record

IMACEDGR EDGRSEXT - DFSMSrmm Extract Data Set Storage Location

TYPEEDGR EDGRVEXT - DFSMSrmm Extract Data Set Volume Record

VMACEDGR These extract data sets are good for quick reports, but

Sep 28, 1993 have only a subset of the data available in the SMF Audit

data records described in Change 11.189. Let me know

which you find more useful. This code has only been

syntax checked and bench checked with a dump of three

of the Extract records.

Thanks to Leatha Harlow, Sperry Marine Inc, USA

Change 11.189 Support for IBM's DFSMSrmm Removable Media Manager's two

EXEDGSA user SMF records provides extensive measurement of the

EXEDGSD new IBM tape management product. These datasets allow

EXEDGSK you to:

EXEDGSO - List the contents of the system-managed libraries,

EXEDGSP non-system managed shelf space, and storage locations.

EXEDGSR - List volumes that should be moved from the library to

EXEDGSS storage locations.

EXEDGSU - Identify secure volumes that have been created or

EXEDGSV referenced.

EXEDGS0 - Audit library activites.

EXEDGS1 The Security record (EDGSMASR) creates one MXG dataset:

IMACEDGS EDGSSECU - DFSMSrmm Security Record.

TYPEEDGS The Audit Record (EDGSMFAR) creates ten new datasets:

VMACEDGS EDGSAREC - DFSMSrmm Action Record

Sep 28, 1993 EDGSDREC - DFSMSrmm Data Set Information Record

EDGSKREC - DFSMSrmm Vital Record Specification

EDGSOREC - DFSMSrmm Owner Information

EDGSOVOL - DFSMSrmm Owner Information Volume List

EDGSPREC - DFSMSrmm Software Product Record

EDGSPVOL - DFSMSrmm Software Product Volume List

EDGSRREC - DFSMSrmm Library Shelf Location Record

EDGSSREC - DFSMSrmm Storage Location Shelf Location

EDGSVREC - DFSMSrmm Volume Information

These datasets are described in Appendix B, DFSMSrmm

Mapping Macros of DFSMS/MVS 1.1 Customization Guide.

This code has been syntax checked. Only the Audit record

was hand checked with a hex dump, and only subtype 'V'.

I am unsure of the time inputs in the Security record!

See Change 11.190 for DFSMSRMM Extract Record Support.

Thanks to Mike Skopec, Platinum Technology, USA
Change 11.188 %READDB2; %INCLUDE SOURCLIB(ASUMDB2A); will fail because

READDB2 READDB2 modifies the macros defined in IMACDB2, but did

Sep 28, 1993 not restore the original values for ASUMDB2A! Insert

%INCLUDE SOURCLIB(IMACDB2);

after the last %END and before the %MEND in READDB2 and

this class of problems are resolved.

Thanks to Bernard Harrison, VISA International, USA.
Change 11.187 Execution of MXG 11.06 or later under archaic SAS 6.06

CONFIG06 is no longer formally supported. However, if you are

VMXGINIT still stuck on SAS 6.06, using member CONFIG06 as your

Sep 28, 1993 CONFIG= parameter will invoke VMXGINI6 to initialize the

MXG system as best as possible. However, there appear

to be significant errors in the $EBCDIC format under SAS

6.06. If you encounter unexpected/strange characters in

the SMF DUMP HEADER message for SYSTEM=, you will need to

change all occurrences of $EBCDIC to $CHAR to be able to

execute under SAS 6.06. The real message is that MXG now

requires SAS 6.08 or later for safe and easy execution.

Note: See MXG Technical Notes in Newsletter TWENTY-FIVE.

Change 11.186 Timestamps RPTTIME,ODITIME, and ODIELAPS were missing in

VMACODS datasets ODSREPOR & ODSUSER because informat TIME6. does

Sep 27, 1993 not work with a value of 135859. However, Change 11.150

replaced all use of TIMEn with separate input of HH MM SS

and that redesign accidentally corrected this error. A

division by zero was also protected.

Thanks to Cindy Ng, Charles Schwab, USA.
Change 11.185 Invalid MDF value for BDNSKIP in Type 72 record STOPOVER.

VMAC7072 There were only 4 segments to skip, but BNDSKIP was 8.

Sep 27, 1993 Insert this trap after LOCPRDS is calculated:

IF LOCPRDS+LPARCPUS*LENPRDS GT LENGTH+1 THEN DO;

NBDPRDS+1; IF NBDPRDS LE 2 THEN

PUT '***ERROR.VMAC7072.INVALID PRDS LOCATION '

LOCPRDS= OFFPRDS= LENPRDS= BDNSKIP= LOCPRCS= I=

LENGTH= /+5 ' RECORD WAS DELETED. ' SYSTEM= SMFTIME=;

DELETE; END;

Note: The variable BNDSKIP was misspelled BDNSKIP in the

text of this change in 11.07, and in the PUT= statement,

which caused UNINITIALIZED variable BDNSKIP. Those were

corrected Sep 30, but not included in MXG 11.07.

Thanks to Tony Gennari, Harcourt Brace & Company, USA.

Change 11.184 SPIN library can fill if Change 11.060 is not installed!

VMAC30 The incorrect value of JINITIME causes the SPIN logic in

Sep 26, 1993 BUILDPDB to hold records in the SPIN library until the

SPINCNT limit in IMACSPIN is exceeded.

Thanks to Andrea Mulcahey, United Jersey Bank, USA.
Change 11.183 The LABEL for VIOREADS should have been spelled as

VMAC71 *FROM ESTORE instead of *ROM ESTORE.

Sep 26, 1993

Thanks to Helmut Kirrmaier, Comparex, GERMANY.

Change 11.182 A user's technical note about problems accounting for

ADOCWSF printed output for users of RSD's WSF product was added

Sep 26, 1993 to the ADOC for WSF. (Unfortunately, that's all there

is in that particular ADOC right now!)

Thanks to Jonathan Caldwell, Department of Veterans Affairs, USA.
Change 11.181 Support for SAP's IMS log record type 'AE'x accounts SAP

ASMIMSLG transactions under IMS. Three new data sets are created:

EXSAPIBA SAPIMSBA - Batch SAP jobs.

EXSAPION SAPIMSON - Online SAP transactions.

EXSAPISP SAPIMSSP - SAP Spool Task activity.

IMACIMS Whether you use the old TYPEIMS or new ASMIMSLG members,

VMACIMS these three SAP datasets will be created (their default

VMACIMSA destination is WORK, but you set that in member IMACIMS

Sep 25, 1993 in the _LSAPIxx macro definition). Note that since the

IMACIMS was changed, if you have tailored IMACIMS into

your USERID.SOURCLIB, you will need to compare and update

your changes starting with the new IMACIMS in this MXG.

This code has been syntax and hand checked with a dump.

Thanks to J. Cary Jones, Philip Morris, USA.

Change 11.180 Support for AICorp Central Server SMF record creates one

EXAICSCS new dataset:

IMACAICS AICSCS - AICorp Central Server resources.

TYPEAICS This code has been syntax and hand checked with a dump.

VMACAICS

Sep 25, 1993

Thanks to Bob Mattingly, ARCO, USA.
Change 11.179 Support for Concurrent Copy and Extended Sequential Data

EXTY42CC set activity in SMF type 42 subtype 4 records creates

EXTY42CV three new datasets:

EXTY42EX TYPE42CC - Concurrent Copy Job resources per controller

IMAC42 TYPE42CV - Concurrent Copy Job, detail per VOLSER.

VMAC42 TYPE42EX - Extended Sequential Dataset activity.

Sep 25, 1993

Thanks to John Maher, Home Savings of America, USA.

Change 11.178 References to Duquesne Systems was changed to LEGENT in

Several members IMACTPX,IMACSTX,IMACNSPY,IMACDMON,ANALNSPY,

Sep 25, 1993 VMACSTX, and VMACDMON. Morino Associates merged with

Duquesne Systems to create LEGENT.

Thanks to Herbert G. Strozinsky, Burlington Northern Railroad, USA.
Change 11.177 Variable SERVICE is used to determine if a TYPE72 obs

EXTY72 will be created, but IBM Information APAR II07261 says

Sep 25, 1993 SERVICE is zeroed if it overflows! So MXG now uses

IF SUM(CPUUNITS,SRBUNITS,IOUNITS,MSOUNITS) GT 0 ...

to test any of the components of service for non-zero.

Thanks to Randy Shumate, Mead Data Central, USA.

Change 11.176 Character variable STATFLG in TYPEXCOM conflicted with

VMACXCOM numeric variable STATFLG in TYPE5568. The TYPEXCOM

Sep 25, 1993 variable STATFLG is now spelled STATFLGX.

Thanks to Dan Squillace, SAS Institute Cary, USA.

Change 11.175 Support for Sterling's NDM, Network Data Mover user SMF

EXNDMCT record creates four new datasets for their Release 1.4.0:

EXNDMPS NDMCT - NDM Copy Termination

EXNDMPT NDMPS - NDM Process Start Event

EXNDMWO NDMPT - NDM Process Termination Event

IMACNDM NDMWO - NDM WTO Statistics

TYPENDM This code has been syntax checked and hand checked with a

VMACNDM hex dump of all four records.

Sep 25, 1993

Thanks to Joseph L. Schwartz, CIGNA, USA.

Change 11.174 Support for Release 3.0.0 of 4th Dimension's CONTROL-D

VMACCTLD SMF record added (compatibly) CTLDJBID, the JOB ID field.

Sep 24, 1993

Thanks to Gary Cooper, 4th Dimension Software, USA.

Change 11.173 Significant enhancements of GRAFxxxx members and a change

GRAFLPAR in the basic structure of the graphics catalog that will

GRAFRMFI NOT work on releases of SAS earlier than 6.06. (The old

GRAFTMNT GRAFxxxx members that run on 6.06 and 5.18 were renamed

GRAFTRND to ZRAFxxxx and kept in the MXG Source Library).

GRAFWORK

VMXGGOPT All graphics routines now have common parameter that will

ZRAFLPAR control the construction of the graphics catalog and the

ZRAFRMFI appearance of the graphs. Each GRAFxxxx member defines a

ZRAFTMNT %MACRO of the same name as the member, and uses these

ZRAFTRND standard parameters:

ZRAFWORK

Sep 25, 1993 PDB= The DDname/LIBNAME for the source of the input

data library, and the destination library of

the output graphics catalog containing the

graphs produced. This can be a PDB or a TREND.

COMPANY= The first title line on all graphs. Defaults to

'Merrills Expanded Guide - Graphics Output', but

this parameter lets you change the title to your

company's name.

MXGRAPHS=The name of the output graphics catalog written

to the library specified by PDB=. The default

catalog name is the member=macro name, but could

be changed with this parameter.

GOUTNEW= A new parameter to re-initialize the graphics

catalog. SAS graphic procedures normally MOD

new graphs at the end of the graphics catalog.

If you reuse a PDB/TREND library, that catalog

could quickly consume the available DASD space.

MXG's default is GOUTNEW=YES, overriding SAS's

normal action and causing the catalog to be

erased before building the new graphs. Any other

value for GOUTNEW will cause the old graphs to

remain and the new to be added at the end.

The changes to the individual members are:
GRAFLPAR - New parameters added and old parameters PDBOUT

and SASGRAPH are no longer applicable (although they are

still recognized for compatibility). PDBOUT= was the old

catalog destination, now specified by PDB= parameter. The

SASGRAPH parameter was needed before it was possible to

detect if you have SAS/GRAPH (now, using the new SYSPROD

function, you no longer have to tell us what you have!).

Additionally, where bar charts are produced, plots with

area fills are used now to reduce the clutter on the

horizontal axis. This was always desired, but prior

versions of SAS did not support LEGEND processing to get

the patterns of the fill into the legend.

GRAFRMFI - New parameters added. All output is now to a

single catalog and (if only a single system is detected)

the graphs of the form VARIABLE*DATE=SYSTEM are not

produced. CLIST examples CLGRAF and CLSTRPLY are now

obsolete; using the SAS Display Manager is a much more

effective means of getting to the graphs now.

GRAFTMNT - New parameters added.
GRAFTRND - New parameters added. Parameters SASGRAPH

and SASSTAT are now obsolete. A new parameter GRAFFROM=

was added; this is the date that will be used as the

starting point of the graphs produced. Where bar charts

were produced, they have been converted to plots with

area fills. This will allow you to view more data (only

about 65 bars are possible but many years can now be

viewed on a single plot) and this reduces the clutter on

the HAXIS. The capacity lines have been smoothed by using

your IMACSHFT specification to calculate the capacity

based on the length of your shifts (previously, actual

duration of found data was used). This will eliminate

the annoying peaks and valleys caused by missing data,

outages, and incomplete weeks.

GRAFWORK - New parameters added. Parameter SASGRAPH is

obsolete. Bar charts were converted to plots with area

fills. In addition, plots of IO connect time and EXCP

counts by WORKLOAD were added. Only workloads that were

actually used (i.e., got service) are used.
VMXGGOPT - Specifies graphics options.

You should use: