MXG Update 2012

Dr. Barry Merrill

Southwest Computer Measurement Group

Mon Sep 24th

IBM Innovation CenterDallas, TX

Agenda • Installing MXG Software• UTILBLDP• BLDSMPDB• ANALID• ANALGRID• VMXGPRNT• VMXGFIND• VMXGSRCH• READDB2• ANALCAPD• MXG SOFTWARE UPDATES

Installing MXG • z/OS:• Download the TERvvnn.TER file which is a tersed copy of the MXG

SOURCLIB PDS and when untersed automagically creates the PDS containing all of the SOURCE.

• .ASCII:• Download the DIRVVNN.ZIP file which is a zipped copy of the MXG

Source Directory.

Installing MXG - zOS

//FTPMXG EXEC PGM=FTP,PARM='(EXIT=4'//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133//SYSABEND DD SYSOUT=*//SYSOUT DD SYSOUT=*//FTPOUT DD SYSOUT=*//SYSIN DD *70.86.188.234USERIDPASSWORDLOCSITE LRECL=1024 RECFM=FB BLKSIZE=6144LOCSITe UNIT=SYSDA PRIMARY=5000 SECONDARY=300BINARYGET TER3006.TER 'MXG.TER3006.TER' (REPLACECLOSEQUIT

FTP Tersed

Installing MXG - zOS• UNTERSE

//UNTERSE EXEC PGM=TRSMAIN,PARM='UNPACK'//SYSPRINT DD SYSOUT=*//INFILE DD DSN=MXG.TER3006.TER,DISP=SHR//OUTFILE DD DSN=MXG.V3006.MXG.SOURCLIB,UNIT=SYSDA,// DISP=(NEW,CATLG),RECFM=FB,LRECL=80,BLKSIZE=0,// AVGREC=M,SPACE=(80,(3,1,1199))

PDS: 3 Million 80 BYTE Records

Installing MXG• Building one or more USERID.SOURCLIBs.• Why more than one??• Sometimes putting in an entire new release is not necessary but it can result

in mounds of paperwork (which we all love.)• Putting in a single member can reduce the paperwork since it then becomes a

‘fix’ and not a new release• Putting those ‘fixes’ into a CHANGES.SOURCLIB between new releases and

then emptying CHANGES when you put in the new release can be simpler

Installing MXG - z/OS• Building USER SOURCLIBs

//STEP2 EXEC PGM=IEFBR14//USERID DD DSN=MXG.USERID.SOURCLIB,UNIT=SYSDA,// DISP=(NEW,CATLG),RECFM=FB,LRECL=80,BLKSIZE=0,// SPACE=(CYL,(15,15,99))//CHANGES DD DSN=MXG.CHANGES.SOURCLIB,UNIT=SYSDA,// DISP=(NEW,CATLG),RECFM=FB,LRECL=80,BLKSIZE=0,// SPACE=(CYL,(15,15,99))

Installing MXG - z/OS• Run FORMATS

//FORMATS EXEC SAS,ENTRY=SAS,// CONFIG='MXG.V3006.MXG.SOURCLIB(CONFIGV9)'//SASLOG DD SYSOUT=*//SASLIST DD SYSOUT=*//SOURCLIB DD DSN=MXG.USERID.SOURCLIB,DISP=SHR// DD DSN=MXG.CHANGES.SOURCLIB,DISP=SHR// DD DSN=MXG.V3006.MXG.SOURCLIB,DISP=SHR//LIBRARY DD DSN=MXG.V3006.MXG.FORMATS,// UNIT=SYSDA,DISP=(NEW,CATLG),SPACE=(CYL,(12,2))//SYSIN DD * %INCLUDE SOURCLIB(FORMATS);//*

Installing MXG – z/OS• A separate MXGSASnn JCL PROCEDURE is no longer required.• In your USERID.SOURCLIB create a member MXGNAMES with• These statements to define your DSNAMEs:

%LET MXGSOURC=MXG.V3006.SOURCLIB; %LET MXGFORMT=MXG.FORMATS; %LET MXGUSER1=MXG.CHANGES.SOURCLIB; %LET MXGUSER2=MXG.USERID.SOURCLIB; %LET MXGUSER3=;

Installing MXG – z/OS• Now you can use the base SAS PROC which keeps SAS changes out of

the way.

//STEP1 EXEC SAS,CONFIG=‘MXG.SOURCLIB(CONFIMXG)’//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR//whatever other DDs are needed for the job//SYSIN DD *your SAS program

UTILBLDP• Normally the code to read an SMF record is:

• %INCLUDE SOURCLIB(TYPE30);• And to read two types you might code:

• %INCLUDE SOURCLIB(TYPE30);• %INCLUDE SOURCLIB(TYPE1415);

• But that would cause two passes of the SMF dataset which can be very large and make this an expensive and time consuming process.• With UTILBLDP this becomes:

• %UTILBLDP(USERADD=30 1415, BUILDPDB=NO,SORTOUT=NO,OUTFILE=INSTREAM);• %INCLUDE INSTREAM;

BLDSMPDB• There are numerous parameters – too many to

mention here but all are documented in the member of SOURCLIB

• Allows for reruns• User code• Run daily/weekly/monthly• Run WTD MTD• Run TRENDing daily/weekly• Read DCOLLECT and Tape management data• And much much more…

Combine UTILBLDP and BLDSMPDB to tailor your PDB

Use UTILBLDP to add/subtract record types and specify things to run after BUILDPDB

Use BLDSMPDB to control the execution of BUILDPDB

ANALID • New MACRO to create

an SMF Audit dataset and report• READSMF=NO• PRINT=YES• PDBOUT=PDB• PERCENTS=YES• ODS parameters

ANALID - Sample

ANALID - Sample

ANALID – Sample

ANALGRID• Creates a dense

color coded grid of values using PROC REPORT• Does not

require SAS/GRAPH• Works on all

SAS versions 9.1.3 and above

%ANALGRID(INCODE=IF LPARNAME=SYSG;);

Read ASUM70LP and for the specified system create a grid of CPU busy for a day.

This is the default with addition of an INCODE to select a specific LPAR

VMXGPRNT

VMXGPRNT(SP_DSET=PDB.DB2ACCT,SP_NOBS=3);

Print PDB.DB2ACCT

VMXGFIND

%VMXGFIND(FIND=QWHSSSID=DBTB,PRINT=3);

If PRINT=YES or xxx then VMXGPRNT is used to do the printing

Utility that will find every OBS in every dataset where some condition is satisfied and make a copy/print the observations.

For example:Find all obs where JOB=:’CICS’

VMXGSRCHUtility that will find every observation in every dataset in every allocated SAS data library where the value of the observation contains some string.

%VMXGSRCH(LOG=NO,RESULTS=COUNT, VALUE=D2DD,LIBNAME=PDB);

READDB2 - Parameters

• SYSTEM – list of systems• PLAN – list of plan names• AUTHID – list of authorization IDs• CORRID – list of correlation IDs• CONNID – list of connection IDs• DB2 – list of DB2 subsystems• CONNTYPE – list of connect types

MXG supplied macro that generates the code to read all of the different types of DB2 SMF data (all IFCIDs). It has been ‘enhanced’ to make a copy of the SMF data and allow for selection based on reading the record headers only which makes it very fast.

ANALCAPD• Can you save money by capping the MSU’s consumed?• Billing is based on the peak of the rolling 4 hour MSU average• Rolling average will (almost) always lag behind actual usage• So, you can set a cap lower than the actual peak and possibly reduce software billing• ANALCAPD will let you ‘play’ with values to find a happy MSU value that allows work to run while

reducing the peak MSU value

Uses the ASUMCEC dataset in the PDB as input

Best granularity is when you match CECINTRV to INTERVAL in ASUM70PR

ANALCAPD - Results

Black line is current capacity Cyan line is current cap (in this case there is not one)

Blue line is actual usage

Green line is rolling 4 hour average

Red * are the intervals where the CEC would have been capped

MXG Software Support Updates• Major enhancements/corrections added in MXG 30.06, dated Sep 1, 2012:

• TYPE120 30.155 Support WebSphere Asynchronous Section 120 Subtype 9.• TYPETAPR 30.164 Support for Tandem Prognosis data files.• TYPEZVPS 30.154 Support XAM/ZVPS VCPU Virtual CPU segment XMUSVCPU• TYPE102 30.175 Support for IFCID=271 DB2 AUDIT PERMISSIONS trace.• TYPENTSM 30.159 Support MicroSoft Exchange 2010 incompat changes.• TYPENMON 30.137 Updates to NMON/TOPAS Monitor for AIX and LINUX.• VGETOBS 30.177 SAS 9.2 z/OS ONLY VGETOBS didn't recognize tape dset.• EXITCICS 30.130 DB2 V10 compressed records "enhanced": NOW WORKS!• ANALDB2R 30.147 DB2 AUDIT reports updated for DB2PM Version 4.2• TYPE102 30.140 Support for IFCID 269,270 Audit, decodes uniques.• TYPEDB2 30.133 Support for (optional) DB2 Netezza Accelerator data.• TYPE30 30.119 Support for APAR OA39629 HICPUPCT/HICPUPGM TYPE30.• TYPEMVCI 30.109 Support for Mainview CICS v64 CICS/TS 4.2 (COMPAT).

MXG Software Support Updates TYPETMD2 30.107 Support for ASG/Landmark TMON DB2 PTFs TE03699/03718. ASMRMFV 30.105 Support for RMF III ASIG3 segments '13'x and '14'x. TYPE119 30.099 Support for CO:Z SMF 119 Subtypes 192 and 193. TYPE1415 30.103 Support for z/OS 1.13-added RAS segment (COMPATIBLE). TYPERACF 30.120 Support for RACF database Record 02G1. TYPEDB2 30.113 Support for DB2 V10 restructured QIST statistics. TYPEZPRO 30.116 Support for Voltage SecureData for z/OS z/Protect. TYPEDB2 30.089 Support for DB2 V10 APAR PM24723 adds data IFCID=225. TYPE105 30.080 Support for GDPS SMF 105 now validated with SMF data. TYPESAMS 30.073 Support for CA Vantage Stor Resc MGR 12.6.00 INCOMAT. TYPE74 30.072 Support for RMF 74 APAR OA36831 (COMPAT) SMF74NSS. TYPECMA 30.070 Support for CA-Spool Subtype 12 (partial). TYPEFERT 30.066 Support for new subtype 1 and 4 FERRET SMF records. TYPE115 30.064 Support for MQ QJST 7.01B Statistics Block. TYPE117 30.063 SMF 117 IMFL subtype SM17ACCT kept in WS 7.0.0.3 SMF.

MXG Software Support Updates TYPE102 30.037 Support for BMC APPTUNE V6R3 SMF 102 records INCOMPAT TYPE102 30.038 Support for DB2 IFCIDs 357 and 358. TYPE102 30.055 Support for DB2 APAR PM37956 to SMF 102 IFCID 25 TYPE119 30.009 Support for SMF 119 ST 6 z/OS 1.13 (INCOMPAT). TYPE21 30.014 Support for APAR OA33947 for TS1140 Tape Drive TYPE85 30.050 Support for SMF 85 records from z/OS 1.13 (INCOMPAT, TYPEBBMQ 30.047 Support for BMC Mainview for MQ Version 5.1 (INCOMPAT TYPEBVIR 30.057 Support for TS7700 Version 2.0a (INCOMPATIBLE) TYPEEZSM 30.041 Support for EMC EzSM z/OS Storage Manager SMF record TYPEHSM 30.006 Support for HSM SMF z/OS 1.12 changes (COMPATIBLE) TYPESVIE 30.051 Support for SYSVIEW PTF Test APAR TSD0145, for IMS. TYPETMD2 30.060 Support for TMON/DB2 V5, INCOMPATIBLE, for DB2 V10. TYPETMMQ 30.025 Support for TMON for MQ Version 2.2/2.3/2.4 INCOMPAT TYPE119 30.009 Support for SMF 119 ST 6 z/OS 1.13 (INCOMPAT). TYPE21 30.014 Support for APAR OA33947 for TS1140 Tape Drive