MXG Update 2012 Dr Barry Merrill Southwest Computer

MXG Update 2012 Dr. Barry Merrill Southwest Computer Measurement Group Mon Sep 24 th IBM Innovation Center Dallas, TX

Agenda • • • Installing MXG Software UTILBLDP BLDSMPDB ANALID ANALGRID VMXGPRNT VMXGFIND VMXGSRCH READDB 2 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 - z. OS //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. 234 USERID PASSWORD LOCSITE LRECL=1024 RECFM=FB BLKSIZE=6144 LOCSITe UNIT=SYSDA PRIMARY=5000 SECONDARY=300 BINARY GET TER 3006. TER 'MXG. TER 3006. TER' (REPLACE CLOSE QUIT FTP Tersed

Installing MXG - z. OS • UNTERSE //SYSPRINT //INFILE //OUTFILE // // EXEC PGM=TRSMAIN, PARM='UNPACK' DD SYSOUT=* DD DSN=MXG. TER 3006. TER, DISP=SHR DD DSN=MXG. V 3006. 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 //STEP 2 //USERID // // //CHANGES // // EXEC PGM=IEFBR 14 DD DSN=MXG. USERID. SOURCLIB, UNIT=SYSDA, DISP=(NEW, CATLG), RECFM=FB, LRECL=80, BLKSIZE=0, SPACE=(CYL, (15, 99)) DD DSN=MXG. CHANGES. SOURCLIB, UNIT=SYSDA, DISP=(NEW, CATLG), RECFM=FB, LRECL=80, BLKSIZE=0, SPACE=(CYL, (15, 99))

Installing MXG - z/OS • Run FORMATS // //SASLOG //SASLIST //SOURCLIB // // //LIBRARY // //SYSIN %INCLUDE //* EXEC SAS, ENTRY=SAS, CONFIG='MXG. V 3006. MXG. SOURCLIB(CONFIGV 9)' DD SYSOUT=* DD DSN=MXG. USERID. SOURCLIB, DISP=SHR DD DSN=MXG. CHANGES. SOURCLIB, DISP=SHR DD DSN=MXG. V 3006. MXG. FORMATS, UNIT=SYSDA, DISP=(NEW, CATLG), SPACE=(CYL, (12, 2)) DD * 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 %LET MXGSOURC=MXG. V 3006. SOURCLIB; MXGFORMT=MXG. FORMATS; MXGUSER 1=MXG. CHANGES. SOURCLIB; MXGUSER 2=MXG. USERID. SOURCLIB; MXGUSER 3=;

Installing MXG – z/OS • Now you can use the base SAS PROC which keeps SAS changes out of the way. //STEP 1 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(TYPE 30); • And to read two types you might code: • %INCLUDE SOURCLIB(TYPE 30); • %INCLUDE SOURCLIB(TYPE 1415); • 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 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 Read ASUM 70 LP 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 %ANALGRID(INCODE=IF LPARNAME=SYSG; );

VMXGPRNT Print PDB. DB 2 ACCT VMXGPRNT(SP_DSET=PDB. DB 2 ACCT, SP_NOBS=3);

VMXGFIND 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’ If PRINT=YES or xxx then VMXGPRNT is used to do the printing %VMXGFIND(FIND=QWHSSSID=DBTB, PRINT=3);

VMXGSRCH Utility 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=D 2 DD, LIBNAME=PDB);

READDB 2 - Parameters MXG supplied macro that generates the code to read all of the different types of DB 2 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. • • SYSTEM – list of systems PLAN – list of plan names AUTHID – list of authorization IDs CORRID – list of correlation IDs CONNID – list of connection IDs DB 2 – list of DB 2 subsystems CONNTYPE – list of connect types

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 ASUM 70 PR

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 TYPE 120 TYPETAPR TYPEZVPS TYPE 102 TYPENTSM TYPENMON VGETOBS EXITCICS ANALDB 2 R TYPE 102 TYPEDB 2 TYPE 30 TYPEMVCI 30. 155 30. 164 30. 154 30. 175 30. 159 30. 137 30. 177 30. 130 30. 147 30. 140 30. 133 30. 119 30. 109 1, 2012: Support Web. Sphere Asynchronous Section 120 Subtype 9. Support for Tandem Prognosis data files. Support XAM/ZVPS VCPU Virtual CPU segment XMUSVCPU Support for IFCID=271 DB 2 AUDIT PERMISSIONS trace. Support Micro. Soft Exchange 2010 incompat changes. Updates to NMON/TOPAS Monitor for AIX and LINUX. SAS 9. 2 z/OS ONLY VGETOBS didn't recognize tape dset. DB 2 V 10 compressed records "enhanced": NOW WORKS! DB 2 AUDIT reports updated for DB 2 PM Version 4. 2 Support for IFCID 269, 270 Audit, decodes uniques. Support for (optional) DB 2 Netezza Accelerator data. Support for APAR OA 39629 HICPUPCT/HICPUPGM TYPE 30. Support for Mainview CICS v 64 CICS/TS 4. 2 (COMPAT).

MXG Software Support Updates TYPETMD 2 ASMRMFV TYPE 119 TYPE 1415 TYPERACF TYPEDB 2 TYPEZPRO TYPEDB 2 TYPE 105 TYPESAMS TYPE 74 TYPECMA TYPEFERT TYPE 115 TYPE 117 30. 105 30. 099 30. 103 30. 120 30. 113 30. 116 30. 089 30. 080 30. 073 30. 072 30. 070 30. 066 30. 064 30. 063 Support Support Support Support SMF 117 for ASG/Landmark TMON DB 2 PTFs TE 03699/03718. for RMF III ASIG 3 segments '13'x and '14'x. for CO: Z SMF 119 Subtypes 192 and 193. for z/OS 1. 13 -added RAS segment (COMPATIBLE). for RACF database Record 02 G 1. for DB 2 V 10 restructured QIST statistics. for Voltage Secure. Data for z/OS z/Protect. for DB 2 V 10 APAR PM 24723 adds data IFCID=225. for GDPS SMF 105 now validated with SMF data. for CA Vantage Stor Resc MGR 12. 6. 00 INCOMAT. for RMF 74 APAR OA 36831 (COMPAT) SMF 74 NSS. for CA-Spool Subtype 12 (partial). for new subtype 1 and 4 FERRET SMF records. for MQ QJST 7. 01 B Statistics Block. IMFL subtype SM 17 ACCT kept in WS 7. 0. 0. 3 SMF.

MXG Software Support Updates TYPE 102 TYPE 119 TYPE 21 TYPE 85 TYPEBBMQ TYPEBVIR TYPEEZSM TYPEHSM TYPESVIE TYPETMD 2 TYPETMMQ TYPE 119 TYPE 21 30. 037 30. 038 30. 055 30. 009 30. 014 30. 050 30. 047 30. 057 30. 041 30. 006 30. 051 30. 060 30. 025 30. 009 30. 014 Support Support Support Support for for for for BMC APPTUNE V 6 R 3 SMF 102 records INCOMPAT DB 2 IFCIDs 357 and 358. DB 2 APAR PM 37956 to SMF 102 IFCID 25 SMF 119 ST 6 z/OS 1. 13 (INCOMPAT). APAR OA 33947 for TS 1140 Tape Drive SMF 85 records from z/OS 1. 13 (INCOMPAT, BMC Mainview for MQ Version 5. 1 (INCOMPAT TS 7700 Version 2. 0 a (INCOMPATIBLE) EMC Ez. SM z/OS Storage Manager SMF record HSM SMF z/OS 1. 12 changes (COMPATIBLE) SYSVIEW PTF Test APAR TSD 0145, for IMS. TMON/DB 2 V 5, INCOMPATIBLE, for DB 2 V 10. TMON for MQ Version 2. 2/2. 3/2. 4 INCOMPAT SMF 119 ST 6 z/OS 1. 13 (INCOMPAT). APAR OA 33947 for TS 1140 Tape Drive