1 / 34

SWCMG

SWCMG . MXG “Vendor” Session August 11, 2011 Dallas, TEXAS, USA. MXG Version 29.04 dated May 17, 2011. UPDATES TO MXG Z/OS 1.12 Support CICS/TS 4.2 Support Z196 Support DB2 V10 Support EXITCICS COMPRESSED CICS AND DB2 TYPE113 Support VMXGSRCH VMXGFIND SAS 9.2 Install

enoch
Download Presentation

SWCMG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SWCMG MXG “Vendor” Session August 11, 2011 Dallas, TEXAS, USA

  2. MXG Version 29.04 dated May 17, 2011. UPDATES TO MXG Z/OS 1.12 Support CICS/TS 4.2 Support Z196 Support DB2 V10 Support EXITCICS COMPRESSED CICS AND DB2 TYPE113 Support VMXGSRCH VMXGFIND SAS 9.2 Install WINDOWS SEVEN AND MSE JCLSIMPL/JCLSPSMx/BLDSIMPL/BLDSPSMx COMPARISON OF Z/VM MONWRITE AND Z/OS RMF

  3. 1. New stuff in MXG 28.01, Mar 9, 2010: VMXGFIND 28.012 Kewl tool, find all obs in all datasets meeting, a test (all obs with JOB=‘CICS’ in all PDB. TYPESTC 28.005 Support for Sun StorageTek VSM Version 6.2/7.0 TYPE89 28.015 Support for z/TPM SMF 89 record, subtype wrong. TYPENTSM 28.042 New Sentry VM 3.1.4.3 adds VMWARE objects/metrics. TYPE30 28.031 z/OS 1.11 GA added variables to SMF 30 and SMF 71. TYPEZTPF 28.043* zTPF has major revisions in Performance Data TYPETMS 28.040* CA-1 Retention and VMRECORD extensions. Changes: TYPE74 28.039 R7451RID now one byte, R7451FLG/TYPE74CA overlays. BUILDPDB 28.037 PDB.SMFINTRV have EXCP/IOTM counts for FLUSHED. TYPE103 28.036 TYPE1032 deaccum needed PORTNR, label changed. VGETOBS 28.034 %TRIM() references here removed, still in VMXGSUM. IMACICMR 28.032 Protect 200-byte CMRDATA on CICS/TS 3.2 (s/b 256). VGETDDS 28.014 Colon in DDNAMES= worked only with DDNAMES=PDB:) TYPEDB2 28.010 Variable SHIFT (from QWHSSTCK, END) kept.

  4. 2. Major enhancements added in MXG 28.02, dated Apr 14, 2010 VMXGINIT 28.081 VARLENCHK=NOWARN eliminates SAS V9.2 WARNINGS VMXGINIT 28.057 ERROR MACRO %ABORT IS NOT IN SAS 8.2, ONLY. TYPE84 28.077 Support for all JES3 JMF TYPE84 subtypes. ASMIMSL6 28.066 Support for IMS Version 11 (INCOMPATIBLE). TYPEIMS7 28.066 Support for IMS Version 11 (INCOMPATIBLE). TYPEMVCI 28.065 Support for BMC CICS CMRDETL C660 for CICS/TS 4.1 TYPEDB2 28.051 Support for DB2 APAR PK62161 new SQL Counters. TYPETMNT 28.079 TOTAL LENGTH OF VARIABLES MUST BE LT 32760. TYPEDB2 28.073 DB2STATS had missing values for QW0225 variables. TYPE42 28.072 TYPE42X4 Above the BAR LRU variables wrong. BUILDPDB 28.071 PDB.STEPS/PDB.JOBS duplicates if FLUSHED steps. MXGSAS92 28.070 SAS 9.2 TS2M2 DSNAMES may have changed TYPERMVV 28.048 RMFV CPUG3 was misaligned in z/OS 1.1122.

  5. 3. BLDSMPDB 28.125 Support for Week/Month if 1st-day-of-week NOT MON. CONFIGVx28.128 ERROR APPARENT MACRO TRIM NOT RESOVED: MORE DOC. VMXGSRCH 28.147 Kewl Tool. Find all instances of VARIABLE='VALUE'. BUILDPDB 28.139 Recently added SMF30xxx varskept in PDB.STEPS. Major enhancements added in MXG 28.03, dated May 25, 2010 TYPEWPMO 28.086 Support for Windows Performance Monitor PERFMON. TYPECTCP 28.108 Support for CleverView for TCP/IP TN3270 SMF. TYPE80A 28.107 TOKDANAM BINDDN,BINDPW,APPLNAM,UTYPE,JPNUM. VMXGSUM 28.105 Optional KEEPWEEK/MNTH/YEAR/DAYS/ keeps TRENDs. TYPE7072 28.099 Variable CPULHKTM, CPU TIME Lock Promoted, 72GO. VMXGSET 28.098 DSETOPT= optional argument for data set options. SMFRECNT 28.089 BUILDPDBs PDB.SMFRECNT now has bytes and counts. TYPE110 28.087 Internal Decompression Algorithm use now ERROR:'d. TYPECIMS 28.084 BMC IMF INPUTCLS and LASTCLAS variables restored.

  6. 4. Many 28.175 Support for z/OS 1.12 (REQUIRES MXG 28.05). DO NOT USE MXG 28.04 WITH z/OS 1.12 DATA INCOMPAT. TYPE70 28.175 Support z196: REQUIRED ONLY WITH GT 64 ENGINES. (Lots of new data added compatibly.) TYPE113 28.166 Major revision - TYPE113 - John Burg's SHARE 2010. Calculation of RNI, new z196 fields, new metrics. TYPE119 28.175 Support for SMF 119 new subtypes 32-37 and 48-52. TYPEITRF 28.162 Support for ITRF V420 IF2 (COMPATIBLE). TYPECTCP 28.160 Support for CleverView GMT offset, CTCPIPAD fixed. TYPE42 28.158 Support for APAR OA31648 TYPE42D1/D3 buff gets TYPEVM 28.157 Support for VM ACCOUNT ID='09' ISFC record. TYPE102 28.156 Support for IFCID=27 specific variables. TYPENMON 28.176 Support for SARMON - Solaris SAR in NMON format. IMACCADI 28.172 Support for CA-Dispatch V11 SMF 6 INCOMPATIBLE. TYPETPFC 28.152 Support for zTPFC TPF Continuous Monitoring . TYPEZCOS 28.151 Support for zCost AutoSoftcapping V 1.5.00 SMF. UTILPDSL 28.179 Utility to read PDS/PDSE directories of a concat. IMACZDAT 28.174 Example to set ZDATE when you rebuild a past PDB.

  7. 5. Major enhancements added in MXG 28.05, dated Aug 18, 2010 The z196 processor with more than 64 engines REQUIRES MXG 28.05. A z196 with LESS THAN 64 engines DOES NOT require MXG 28.05, as long as the operating system is z/OS 1.11 or earlier. IBM Maintenance APARs OA30563,OA33976 REQUIRES MXG 28.05. Major enhancements added in MXG 28.06, dated Oct 7, 2010 TYPEWSMQ 28.233 Support for WebSphere MQ Version 7 Accounting TYPEDB2 28.222 ITRM only, DB2STAT4 NOT SORTED ERROR. ASUMDB2- 28.220 DB2 Summary ASUMDBxx and Trending TRNDDBxx. EXITCICS 28.223 Support for DB2 V10 Compressed SMF records. DFH$MOLS 28.223 JCL example to use IBM CICS decomp utility. TYPEITRF 28.227 INPUT STATEMENT EXCEEDED RECORD LENGTH type=17x. TYPEIMFS 28.193 Full support for IMF records in SMF format. TYPE113 28.226 Variable LPBUSY,LPARBUSY replaced LPARCPU. m TYPE74 28.212 TYPE74ID (small) created, saves pass TYPE74CA.

  8. 6. MXG Version 28.07 dated Nov 5, 2010. Major enhancements added in MXG 28.07, dated Nov 5, 2010 TYPEDB2 28.264 Support for DB2 Version 10. COMPLETELY INCOMPAT: MXG 28.06 was required to process the V10 data, now, MXG 28.07 has full support. TYPEOMMQ 28.263 Support for IBM/OMEGAMON XW MQ file (INCOMPAT) TYPEMIM 28.262 Support for CA MIM RESOURCE SHARE R11.7 (COMPAT) GRAFCEC 28.261 SAS/GRAPH example charts CEC Util by engine TYPETPX 28.260 IP address and Port Number now decoded in TPX UTILEXCL 28.259 Spurious "WRONG LENGTH OF 200 FOR CMRDATA" TYPE120 28.258 Support for WebSphere ID=120 SUBTYPE=20 records ANALID 28.257 ERROR: VARIABLE IDANDSUM ... with PDB,DISP=OLD READDB2 28.250 COPYONLY logic now works. VMXGSUM 28.249 VMXGSUM enhanced with MODE and MEDIAN statistics TYPE110 28.247 Example using _Kdddddd to create new datasets TYPE30 28.246 New CPITCxTM/CPISRxTM wrong in MXG 28.06. TYPESTC 28.244 STC/STK/Oracle VSM user SMF records support

  9. 7. MXG Version 28.08 dated Dec 13, 2010, thru Change 28.288. TYPE113 28.279 "Near duplicate" ASUM113 intervals corrected. TYPE89 28,282 Support for APAR OA31615, zIIP/zAAP CPU times. TYPENMON 28.275 Support for NMON FCREAD/FCWRITE/XFERIN/XFEROUT TYPETNG 28.273 Support for more than 9999 instances in CA NSM. TYPETMVT 28.287 Support for ASG-TMON for VTAM subtype 'SX'. TYPE110 28.285 CICS Statistics Subtype 2 STID=143 corrected. ASUMUOWT 28.284 ASUMUOWT (for ASG-TMON MRO) uses VMXGUOW. ASUMCICR 28.281 Count/avg response time by DATE for each APPLID. DB2ACCT 28.277 NETSNAME/UOWTIME only created QWHCATYP=4 (CICS). TYPE89 28.272 SMF89HOF/SMF89DTO SCRT don't use last 3 nybbles. WEEKBLD 28.269 TYPE72DL NOT SORTED after Clock Set Back. UTILNPRT 28.268 Identify non-print chars, SAS Enterprise Guide

  10. 8. MXG Version 28.28 dated Jan 18, 2011, thru Change 28.331. TYPE89 28.331 INVALID DATA FOR SMF89CZT if APAR OA31615 on. TYPE111 28.329 CTG records had zero obs in TY111CXI "IPIC". JCLINSTT 28.328 JCL example to ftp/unterse/install on z/OS. TYPENDM 28.327 Connect Direct/NDM 'RT' record INCOMPAT change. TYPE102 28.325 DB2 SQL-text vars only 100 bytes COMPRESS=NO. TYPEIMSA 28.311 Support for IMS/DBCTL transactions in IMSTRAN. TYPEIMS7 28.310 Support for IMS/DBCTL transactions in IMS0708. TYPE0 28.313 Variable CVTTZ in TYPE0 could be one sec wrong. BUILDPDB 28.305 PDB.NJEPURGE did not contain all NJE-variables. ANALDUPE 28.308 Removal of Duplicate SMF (or any) records. TYPEVMXA 28.315 PFXCPUAD in VXSYTCUM is the LCPUADDR, no CPUID. TYPEVMXA 28.307 Short LINUXKRNL MONWRITE record caused errors. UTILGETM 28.312 No Reporting Class data in SMFSMALL NRECORD=10. TYPE89 28.304 SMF 89 with no usage segment INPUT EXCEEDED. TYPE30 28.302 TYPE30MU duplicate records exist, non-dupes.

  11. 9. MXG Version 29.01 dated Feb 4, 2011, thru Change 29.022. These two impacted MONTHLY build: MONTHBLD 29.017 SERIOUS ERROR CORRECTED: last day's PDB skipped. BLDSMPDB 29.017 LIBNAME WEEK1 not found corrected. These two eliminate possibility of NOTSORTED errors: BLDSMPDB 29.008 SORTEDBY=NO default to eliminate NOTSORTED. WEEKBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. MONTHBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. TYPEENDV 29.012 Support for Endeavor Version 14 (INCOMPATIBLE). TYPE111 29.001 Support for IPIC creates obs in TY111CXI. TYPE115 29.015 Support for MQ Version 7 compression statistics. TYPE89 29.002 Support for APAR OA31615, zIIP/zAAP times added, and false error messages are eliminated..

  12. 10. MXG Version 29.02 dated Mar 1, 2011, thru Change 29.050. VSETMNTH 29.041 POSSIBLE LOSS OF MON DATA IN FEB MONTHLY PDB. (Unfortunately, EVEN with the newest MXG 29.01). ONLY IF USING NEW VSETMTH LOGIC IN MONTHBLD. Future MONTHly'scan also be missing one or more day's PDBs in your MONTH PDB. Complete details are in Change 28.041, below. TYPENDM 29.042 Support for NDM-CDI Version 5 records (COMPAT). VMACDB2H 29.037 DB2 V9.1 false "INVALID DISTRIBUTED HEADER" msg. TYPE30 29.034 Invalid data for SMF30RGT is true, circumvented. TYPECIMS 29.033 Support for IMF Version 4.5 is in place. TYPE0 29.032 PDB.IPLS, now, DOES always report a SYSTEM IPL. TYPEDB2 29.031 DB2 V9.2 only, QBGxxx variables DB2GBPST wrong. TYPEVMXA 29.026 Support for zVM APAR VM64794 (COMPATIBLE). TYPE30 29.025 Small negative CPUUNITS now set to zero. TYPE26J2 29.024 Cosmetic: INREASON NOT DECODED msgscorrected.

  13. 11. MXG Version 29.03 dated Apr 19, 2011, thru Change 29.094. TYPE110 29.094 1st MXG 29.03 ONLY. CICSTRAN CPUTM fields WRONG. TYPE116 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPE115 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPEBBMQ 29.056 Support for MainView MQ (MVMQ) Version 4.4. TYPEQACS 29.078 Support for OS/400, AS/400 Version 7.1 (INCOMPAT) TYPE110 29.076 CICS CPUTM exceeds ELAPSTM, zAAP/zIIP Equivalent TYPE120 29.081 Support for User Field in SMF 120 Subtype 9. TYPETPMX 29.071 Support for Throughput Manager subtype 10 and 16. TYPENTSM 29.075 Support for 62 new objects and 1425 new metrics. UTILVREF 29.075 MXG creates DATASET names up to 32 characters. BUILDPDB 29.068 28.28-29.02. ABEND=JCL obs missing in PDB.JOBS. TYPERACF 29.067 RACF UNLOAD dataset RACF0270 UID limit variables. TYPEBETA 29.059 Support for Beta 93 Version 4.2 subtypes 25/50. TYPE30 29.058 Variable CPUCEPTM always a missing value. MONTHxxx 29.052 SAS 9.1.3 Only. %QCMPRES needed versus %CMPRES. TYPE85 29.093 INPUT STATEMENT EXCEEDED st 79, z/OS 1.12. ASUM70PR 29.092 ZIPCPUS/IFACPUS included parked time. TYPEVMXA 29.092 z/VM new PDB.VXINTUSR sums all engines each VM.

  14. 12. MXG Version 29.04 dated May 17, 2011, thru Change 29.115. TYPE105 29.100 Support for GDPS Global Mirror V3R8 SMF 105. DB2ACCT 29.111 DB2 CICS TRAN name wrong, now from QWHCCV. TYPEIMSA 29.110 the exit _IMSTRN was accidentally removed. BUIL3005 29.106 JES3 PDB.JOBS variable JOBCLAS8 after change. VMXGSRCH 29.103 RESULTS=FINDVAR finds all datasets with a var. TYPE70PR 29.098 Counts ICFCPUS/IFLCPUS/IFACPUS/ZIPCPUS too high. TYPE110 29.097 INPUT EXCEEDED 110-2 MNSEGLC=5 with DPL segment

  15. 13. MXG Version 29.05 dated Jul 11, 2011, thru Change 29.151. TYPE110 29.135 Support for CICS/TS 4.2. CICSTRAN supported in 29.03. TYPE110 29.149 Support for CICS/TS 4.2. MNSEGCL=5 requires 29.05. TYPE120 29.136 Support for WebSphere WAS 8.0 (COMPATIBLE). TYPE70 29.127 Support for z/OS 1.12 VMGUEST option, CPU Time in 70. TYPEIMST 29.144 IMS Transactions in IMS56FA, replaces JCLIMSL6!!! TYPETIMS 29.123 Support for TMON/IMS Version 3.0 (INCOMPATIBLE). TYPEPOEX 29.134 Support for Informatica's POWER EXCHANGE SMF record. TYPEDB2 29.140 New LUUVTIME instead of QWACBSC for start time. TYPEVMXA 29.133 z/VM LPARNAME, LPNUMBER kept in PDB.VMXAINTV. UTILARCH 29.137 New UTILARCH archives data (like Outlook archive). TYPEXAM 29.126 XAM variables in VXSYTEP2 were not all input/kept. TYPE111 29.124 Variables CTGIAREQ/CTGLALRQ revised keeps.

  16. 14. MXG Version 29.06 dated Aug ??, 2011, thru Change 29.???. SAS V9.3 29.159 Support for SAS Version 9.3 - SAS Hot Fix SN43828. With Hot Fix SN43828 (in %MACRO compiler portable SAS code) the full MXG QA test stream executed with no errors nor any new warnings, on z/OS (where the error was found and the hot fix tested), and on both the 32-bit and 64-bit SAS Version 9.3 with Windows Seven. MANY 29.169 MXG ODS HTML ASCII examples failed if no PATH=. Seen first with SAS V9.3; complete revision of MXG ODS HTML examples with new %macros with consistent arguments, etc, for all platforms. TYPEVMXA 29.172 Support for APAR VM64961, SMF 113 in z/VM MONWRITE!! TYPE113 29.176 Support for APAR OA36816, SMF 113 HIS DATALOSS parm. IBM now recommends SMF 113 always be created. TYPEIMST 29.162 Validation of TYPEIMST, many changes for IMS56FA. Finally: IMS Transaction CPU/Response from ONE IBM IMS LOG RECORD. TYPE23 29.177 Support for APAR OA35175, logstream stats in SMF 23. TYPE30 29.175 Support for APAR OA35617, SMF30CRM VELOCITY MNGED? TYPE30 29.174 Support for APAR OA34895, EXCP/IOTM Missed, SMF Lock. TYPEIDMS 29.156 Support for IDMS/R Performance Monitor Version 18.

  17. 15. VMXGFIND EXAMPLES: 1. FIND ALL OBSERVATIONS FOR A JOB NAME: %VMXGFIND(PDB=PDB SPIN, PDBOUT=WORK, KEEPIN=JOB, FIND= IF JOB=:'CICS'; , PRINT=99); 2. FIND ALL OBSERVATIONS FROM/FOR A SPECIFIC USER FROM PDB1-PDBN AND SPIN LIBRARIES: %VMXGFIND(PDB=PDB: SPIN, PDBOUT=WORK, KEEPIN=FSRUID JOB RACFUSER QWHCAID, FIND=IF RACFUSER='XYZ12345' OR QWHCAID ='XYZ12345' OR FSRUID ='XYZ12345' OR JOB ='XYZ12345';, PRINT=YES);

  18. 16. VMXGSRCH EXAMPLES: TO FIND ALL OBSERVATIONS IN ALL SAS DATASETS IN THE PDB LIBRARY THAT HAVE ANY VARIABLE THAT CONTAINS "SYSD", AND PRINT THE FIRST TEN OBSERVATIONS OF EVERY FOUND DATASET: %VMXGSRCH(LIBNAME=PDB,RESULTS=PRINT,VALUE=SYSD,NOBS=10); TO FIND ALL VARIABLES IN ALL ALLOCATED DATA LIBRARIES WITH THE TEXT "CPU" IN THE LABEL %VMXGSRCH(VALUE=CPU,RESULTS=LABEL); WILL REPORT EVERY SAS DATASET AND VARIABLE IN THOSE "PDBS" THAT HAVE CPU IN THEIR LABEL. TO FIND ALL VARIABLES WITH TIME IN THE FORMAT (WILL ALSO FIND DATETIME) %VMXGSRCH(VALUE=TIME,RESULTS=FORMAT); WILL REPORT EVERY SAS DATASETS/VARIABLES WITH TIME IN THE FORMAT

  19. 17. CICS Record Size Growth

  20. 18. Assemble and Install the EXITCICS THIS ASM PROGRAM IS ASSEMBLED AND LINK-EDITED INTO A LOAD MODULE THAT IS NAMED CICSIFUE THAT IS STORED IN A LOAD LIBRARY DATASET THAT IS CONCATENATED TO THE //STEPLIB DD STATEMENT IN YOUR MXGSASVN JCL PROCEDURE. THE LOAD MODULE IS A SAS INFILE EXIT. 1) %LET SMFEXIT=CICS; 2) FILENAME SMF 'dsname of dataset' ENGINE=CICS; DATA X; INFILE SMF; INPUT ... 3) DATA X; INFILE SMF CICS; INPUT .... THAT FIRST %LET STATMENT CAN BE PLACED IN THE "IMACKEEP" MEMBER IN YOUR USERID.SOURCLIB TAILORING LIBRARY, OR IT CAN BE PLACED IN THE //SYSIN DD STREAM AS THE FIRST STATEMENT.. EXITCICS decompresses CICS 110, 112, and DB2 100, 101, and 102 records.

  21. 19. The INTERNAL SAS algorithm on z/OS is VERY CPU intensive (and it takes a long time, too!). DFH$MOLS and read UNCOMP only slightly slower than reading COMPRESSED+EXIT, BUT uncompressed file needs nearly 5 times the disk space. I/O activity with DFH$MOLS (read comp, write uncomp, read took six times the EXCPs and four times the IOTM (Connect Time) Reading of the compressed file with the EXITCICS exit is best. On Windows/ascii platforms, SAS Infile Exits do not exist. Only two ways to process compressed CICS data on ASCII: a. Use DFH$MOLS first to uncomp file and read UNCOMP. c. Use MXG's internal algorithm to read COMP NO EXIT. Elapsed User SYS Size a. DFH$MOLS .4 .07 .00 212/970 ftp download 2.0 .04 .00 970 MB UNCOMPRESSED .4 .23 .05 970 MB total 2.8 .34 .05 c. ftp download 0.5 .01 .00 212 MB INTERNAL SAS 3.8 2.71 .05 212 MB total 4.3 2.72 .05

  22. 20. SAS Version Requirementsinformation: MXG 26.03 thru MXG 29.06 will execute under SAS Version 9.3, on all supported platforms, but SAS Hot Fix SN43828 is REQUIRED. MXG 26.03 thru MXG 29.06 will execute under SAS V9.2, or with SAS V9.1.3 with Service Pack 4, on all supported SAS platform. SAS Hot Fix for SAS Note 37166 is required to use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2 Decompression Infile Exit. And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG, the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe). Old MXG code may continue to execute with SAS V8.2, but V8 is now "Level B" support from SAS Institute, and there are known errors in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2; While many MXG programs (accidentally) will still execute under V8.2, I can not guarantee that all of MXG executes error free.

  23. 21. Install of SAS V9.2 for z/OS is rumored to be difficult, BUT BY following the SAS Install Instructions at: http://preview.tinyurl.com/443mlpd upload and install of the (7.5 GB) z/OS SAS/BASE took 2 hours BUT ONLY if everything needed is already in place!). Size of the depot between 5GB and 17GB depending on products SAS Depot will be uploaded to a ZFS filesystem z/OS restriction of 4GB for size of normal zFS mount point Need authority to define a larger zFS mount point Either must be created with the SMS Data Class EXTENDED attribute. Need two zFS directories of 5GB to 17GB because 2nd SASHOME But, one last note, do NOT use that EXTENDED attribute for the Data Class of your SAS Data Libraries on z/OS; it is not supported due to SAS's use of the EXCP access method.

  24. 22. Using MicroSoft Security Essential, MSE, causes various errors     the MXG QA job is run, never at the same place in the job:    ERROR: File Deletion Failed For MXGSUM1  (after 293 succeeded) ERROR: An I/O error occurred on file WORK._tf6737.UTILITY ERROR: Rename of temporary member WORK.OPTVAR.DATA failed.    BUT BY disabling MSE Settings to:      -exclude the SAS.EXE process, and      -exclude files *.sas7bdat and     -exclude the c:\qa directory, where all output is written, &       -exclude the c:\sastemp "WORK" directory. were both errors were eliminated, with WINDOWS 7 64 bit. “SAS NOTE: Do not run your antivirus software in real-time mode. OR be sure to exclude the following file types from your virus scan: SAS* LCK* UTL* “

  25. 23. Issue open with SAS Institute and Microsoft since Feb, 2010; In October, a new MicroSoft "Senior Escalation Engineer" attempted resolution, providing instructions to install several MicroSoft diagnostics tools that either failed to initialize or failed to capture the event data, including runs with TTTracer that generated over 85 GigaBytes of trace (how do you send a file that big??) that still did not capture anything of use to MS. Nov 2010: 14 MicroSoft updates auto installed, error went away. MS engineer was unable to identify why the error disappeared. Moral: Disable MSE for SAS. MAY 2011: WINDOWS 7 ULTIMATE AUTOINSTALL SP1 REINSTATED ERRORS. DISABLING MSE REAL TIME SCAN WAS REQUIRED TO RUN QA. USING MSE SETTINGS (process/dir/file) DID NOT CIRCUMVENT. ADDITIONALLY: RUN SAS AS ASMINISTRATOR MAY BE REQUIRED WITH SP1. ERROR: User does not have appropriate authorization level for      library C:\PROGRAM FILES\SAS\SASFOUNDATION\9.2 (to write qasas.log and qasas.lst files).

  26. 24. JCLSIMPL and JCLSPxxx examples use UTILBLDP/BLDSMPDB and are THE now-recommended z/OS jobs for a "SIMPLE" BUILDPDB or the "SPLIT SMF" family of "BUILDPDB" jobs. JCLSIMPL creates a "simple", PDB library, with one job that reads the SMF file, showing how to add an SMF record and invoking all of the default ASUMxxxx members to build a "single", default PDB data library from raw SMF data. You could do the same with BUILDPDB and the EXPDBxxx exit members, but these more recent utility macros are now the recommended way to build/tailor a simple BUILDPDB: UTILBLDP - defines what data is to be created in a PDB you can add, subtract, or change what's kept by each of these jobs using UTILBLDP to create a specific suit of MXG datasets in a PDB built from SMF data records. BLDSMPDB - flexible job manager creates day/week/etc PDBs using the UTILBLDP execution preceding its invocation to define the PDB contents. Will process non-SMF data records.

  27. 25. JCLSPxxx is a family of jobs to read "split" subsets of SMF and other data records to parallelize the BUILDPDB, using the above+ UTILBLDP and BLDSMPDB members: JCLSPGDG - run once to create GDGs, and then never again unless there is a need to alter a GDG base or to change dataset names.. JCLSPLIT - first job in daily stream - standalone - splits the daily SMF into pieces for subsequent processing SMF.ALL - All SMF for archive SMF.CICS - SMF 110.1 SMF.DB2 - SMF 101/102 SMF.IO - SMF 14/15/42/61/65/66/74/240/241 SMF.MQ - SMF 115/116 SMF.SPLITPDB - All other SMF records JCLSPSMA/JCLSPSMB/JCLSPSMC/JCLSPSMD/JCLSPSME can be run concurrently to process the split SMF files:

  28. 26. Family of jobs to read the SPLIT SMF files: JCLSPSMA - Read only CICS SMF 110.1, create: JCLSPSMB - Read only DB2 SMF 101/102, create: JCLSPSMC - Read only I/O records, create: JCLSPSMD - Read only MQ records, create: JCLSPSME - Read all remaining SMF, create: JCLSPOTH - DCOLLECT, TMC. JCLSPUOW - after JCLSPLTA and JCLSPLTB have run, build PDB.ASUMUOW from CICSTRAN and DB2ACCT, build PDB.CICS from PDB.ASUMUOW. JCLSPCPY - Copies these datasets into PDB library: ASUMCACH CICS ASUMUOW ASUMDB:

  29. 27. SAS Paper Configuration and Tuning Guidelines for SAS®9 in the Microsoft Windows Server 2008 Operating Environment The monitoring tool that SAS recommends is the Performance Monitor (PerfMon) tool from Microsoft that comes with the Windows operating system. Hundreds of performance counters are associated with this tool, but from a SAS perspective, only the following subset of PerfMon objects and their associated counters is of primary interest: Cache • o Data Flush Pages/sec • o Dirty Pages • o Fast Read Not Possible/sec • o Fast Read Resource Misses/sec • o Lazy Write Pages/sec • o Read Aheads/sec Client-Side Caching • o Application Bytes Read from Cache • o Application Bytes Read from Server (Not Cached) And Many more in the paper at: http://support.sas.com/resources/papers/ WindowsServer2008ConfigurationandTuning.pdf

  30. 28. COMPARISON OF z/VM MONWRITE AND z/OS RMF CPU TIMINGS MONWRITE DATA FROM 2 Z/VM LPARS AND RMF 70 LPAR DATA FOR THE 4 IFLS (SMF70CIN=IFL data for both the "IFL LPAR" and "IFL PHYSICAL") was compared for 23 hours of matching data. The RMF "IFL BUSY" time was 87.31 hours (so the IFLs were busy 94.7% of those 23 hours). Those 87.31 hours of IFL BUSY time is 5239 minutes, and MONWRITE captured 5182 minutes (98.9%) of that hardware busy time. And of the 57 minutes not captured in MONWRITE, 49 minutes were the z/OS IFL Management Time. Or, MONWRITE captured all but 7 minutes of the 5189 minutes of the "Effective Dispatch Time" recorded by z/OS. COMPARISON OF RMF 70 IFL CPU TIME AND MONWRITE CPU TIME VMCPU = MONWRITE CPU (PFXUTIME+PFXSYSTM) IFLACTTM = RMF Partition CPU Dispatch Time, SMF70CIN='IFL' (both LPAR and PHYSICAL for IFL) DIFF = IFLACTTM minus VMCPU LCPUMGTM = LCPUPDTM minus LCPUEDTM LCPUPDTM = Logical/Physical LPAR Partition Dispatch CPU Time LCPUEDTM = Logical/Physical LPAR Effective Dispatch CPU Time

  31. (hours 0-8 removed to fit, totals are for 23 hours) HR VMCPU IFLACTTM DIFF LCPUMGTM LCPUPDTM LCPUEDTM hh:mm:ss hh:mm:ss hh:mm:ss hh:mm:ss hh:mm:ss hh:mm:ss 9 3:45:52 3:48:14 0:02:21 0:02:02 3:48:14 3:46:11 10 3:52:52 3:54:56 0:02:04 0:01:48 3:54:56 3:53:08 11 3:54:01 3:56:04 0:02:03 0:01:47 3:56:04 3:54:17 12 3:48:54 3:51:14 0:02:20 0:02:02 3:51:14 3:49:12 13 3:41:47 3:44:20 0:02:32 0:02:13 3:44:20 3:42:07 14 3:43:33 3:46:12 0:02:40 0:02:20 3:46:12 3:43:53 15 3:33:38 3:36:26 0:02:48 0:02:27 3:36:26 3:33:59 16 3:34:50 3:37:50 0:03:00 0:02:37 3:37:50 3:35:13 17 3:47:36 3:49:56 0:02:20 0:02:02 3:49:56 3:47:54 18 3:48:37 3:50:55 0:02:18 0:02:01 3:50:55 3:48:55 19 3:28:17 3:31:28 0:03:11 0:02:48 3:31:28 3:28:40 20 3:44:45 3:47:22 0:02:37 0:02:18 3:47:22 3:45:05 21 3:47:22 3:50:02 0:02:40 0:02:19 3:50:02 3:47:43 22 3:56:37 3:58:38 0:02:02 0:01:46 3:58:38 3:56:53 ======== ======== ========= ======== ======== ======== 86:22:20 87:19:09 0:56:49 0:49:33 87:19:09 86:29:36

  32. 29. MONWRITE DOES NOT PROVIDE SYNCHRONIZED INTERVAL RECORDS (YET???). The below procedure is only run a IPL time or any situation the requires a recycle. This procedure holds the Monitor START command until the next hour boundary, wih the hour padded with a zero if had only one digit, as the WAKEUP command doesn't support a single digit hour. /* Make the monitor intervals start on the hour */ 'CP MONITOR STOP' Parse value time('N') with hh ':' mm ':' ss . hh=hh+1 /*Wait for the next hour*/ If ss=59 then mm=mm+1 /*May need a bit more time*/ If mm>60 then do /*Overflow to the hour*/ mm=mm-60 hh=hh+1 end If hh<10 then hh = '0'hh 'WAKEUP' hh':00:00' /*Wait*/ 'CP MONITOR START' /*Start the monitor*/

  33. 30. Daily BUILDPDB on INTEL using SAS ftp access to read SMF: 1. Daily BUILDPDB on 8GB 64-bit Intel Duocore E7500 2.93 Ghz, Windows Seven Professional 64-bit, SAS V9.2 64-bit. SMF read: 19,803,835,294 Bytes @7345KByte/Sec 9,819,991 records MXG BUILDPDB "Big data" step: 1:08:00 elapsed 13:50 total CPU (12:42 User, 1:08 System) Total daily run including some reports 1:27:00 elapsed 22:08 total CPU (20:21 User, 1:47 System) Output PDBs: CICSTRAN CICSTRAN 4,677,295 obs 3.00 Gigabytes PDB 3.35 Gigabytes DB2ACCT 867,135 1.30 Gigabytes DB2ACCTP 1,267,153 0.60 Gigabytes TYPE42DS 2,057,402 0.50 Gigabytes SMFINTRV 275,725 0.20 Gigabytes STEPS 260,484 0.20 Gigabytes Rest of PDB 0.55 Gigabytes

  34. Questions • Contact Info • www.mxg.com • support@mxg.com • Listserv MXG-L • 214-351-1966 x7

More Related