COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA

MXG CHANGES 35.36

=========================member=CHANGE35================================
 /* COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
Annual  MXG Version 35.36 was dated Jan  8, 2018, thru Change 35.309    
        MXG Version 35.35 was dated Jan  3, 2018, thru Change 35.303    
        MXG Version 35.12 was dated Dec 26, 2017, thru Change 35.298    
EA test MXG Version 35.12 was dated Dec 20, 2017, thru Change 35.294    
        MXG Version 35.11 was dated Dec  1, 2017, thru Change 35.279    
        MXG Version 35.10 was dated Nov  6, 2017, thru Change 35.255    
First   MXG Version 35.10 was dated Nov  6, 2017, thru Change 35.254    
        MXG Version 35.09 was dated Oct  2, 2017, thru Change 35.217    
First   MXG Version 35.09 was dated Oct  2, 2017, thru Change 35.215    
        MXG Version 35.08 was dated Aug 24, 2017, thru Change 35.186    
        MXG Version 35.07 was dated Aug  2, 2017, thru Change 35.171    
        MXG Version 35.06 was dated Jun 30, 2017, thru Change 35.151    
        MXG Version 35.05 was dated May 15, 2017, thru Change 35.121    
        MXG Version 35.04 was dated May  1, 2017, thru Change 35.104    
        \XG Version 35.03 is  dated Mar 27, 2017, thru Change 35.072    
First   MXG Version 35.03 was dated Mar 22, 2017, thru Change 35.069    
        MXG Version 35.02 was dated Feb 10, 2017, thru Change 35.035    
        MXG Version 35.01 was dated Jan 20, 2017, thru Change 35.014    
ANNUAL  MXG Version 34.34 was dated Jan  3, 2017, thru Change 34.284    
ANNUAL  MXG Version 34.34 was dated Jan  3, 2017, thru Change 34.284    
        MXG Newsletter SIXTY-NINE was dated Jan  3, 2018.               
                                                                        
Instructions for ftp download can be requested by using this form:      
  http://www.mxg.com/Software_Download_Request                          
Your download instructions will be sent via return email.               
                                                                        
Contents of member CHANGES:                                             
                                                                        
I.    Current MXG Software Version 35.36 is available upon request.     
II.   SAS Version requirement information.                              
III.  WPS Version requirement information.                              
IV.   MXG Version Required for Hardware, Operating System Release, etc. 
V.    Incompatibilities and Installation of MXG 35.36.                  
VI.   Online Documentation of MXG Software.                             
VII.  Changes Log                                                       
                                                                        
  Member NEWSLTRS contains Technical Notes, especially APARs of interest
  and is updated with new notes frequently.  All Newsletters are online 
  at http://www.mxg.com in the "Newsletters" frame.                     
                                                                        
  Member CHANGES contains the changes made in the current MXG version.  
  Member CHANGESS contains all changes that have ever been made to MXG. 
  All MXG changes are also online at http://www.mxg.com, in "Changes".  
                                                                        
========================================================================
                                                                        
I.  MXG Version 35.36 dated Jan  8, 2018, thru Change 35.309.           
                                                                        
==Major CHANGES added in MXG 35.36, dated Jan  8, 2018 thru 35.309.     
                                                                        
ERROR Protection:                                                       
  Many     35.308  SAS Defect 9.4 M5 z/OS PROC SQL NOERRORSTOP protect. 
                   SAS Note 61672 will address, this circumvents need.  
ERROR Correction:                                                       
  TYPE42   35.305  Third incorrect SRLEN STOPOVER correction.           
  ANALDB2R 35.307  Broken DO Syntax, 35.11-35.35, if PDBOUT=PDB is used.
  UTILBLDP 35.306  SUPPRESS=74 variable DEVN NOT FOUND ERROR.           
  VGETxxxx 35.309  Protection for DATASET=PDB.dataset syntax.           
                                                                        
==Major CHANGES added in MXG 35.35, dated Jan  3, 2018 thru 35.303.     
                                                                        
New Products Support                                                    
  MDIJCL   35.299  Support for Luminex MDI box to run MXG on Linux.     
Error Corrections                                                       
  TYPE42   35.302  Incorrect SRLEN in SMF 42 Subtype 5 APAR STOPOVER.   
  TYPERMFV 35.300  CPUPHYAD format could fail causing ABEND.            
                                                                        
==Major CHANGES added in MXG 35.12, dated Dec 26, 2017 thru 35.298.     
                                                                        
New Products Support                                                    
  TYPE7072 35.285  Support for Container Pricing, new TYPE72TR dataset. 
  TYPEBETA 35.297  Support for BETA 93 Version 610 (update) 620 (added).
  TYPE0203 35.283  Support for APAR OA52828, SMF Temporary Buffer size. 
  TYPEQACS 35.288  Support for QAPMDISK with LENGTH=695.                
  TYPE42   35.289  TYPE42 APARs OA52132, OA52133, OA61734 now tested.   
Error Corrections                                                       
  TYPERMFV 35.287  MXG 35.10/35.11 RMF III ZRBASI ASICPUTA was WRONG.   
Enhancements                                                            
  TYPEDB2  35.280  Exit Members EXDB2STS and _EDB2STS are now valid.    
  RMFINTRV 35.282  New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.  
  TYPE70   35.282  New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.  
  UTILEXCL 35.293  &MXGCIEXC "exit" to correct USER CMODHEAD typos.     
  UTILCMPR 35.292  Utility compares numeric variables in OLD/NEW dataset
                                                                        
==Major CHANGES added in MXG 35.11, dated Dec  1, 2017 thru 35.279.     
                                                                        
New Products Support                                                    
  TYPE42   35.274  Support for APAR OA53110 new TYPE42 variables.       
  TYPE74   35.273  Support for APAR OA50761 Virtual Flash memory.       
  TYPE89   35.271  Support for Container Pricing in SMF 89.             
  TYPE70   35.270  Support for Container Pricing in SMF 70.             
  TYPE113  35.279  Support for Dec 2017 z14 CPU MF formula update.      
Error Corrections                                                       
  TYPERMFV 35.259  35.10: ZRBASI deaccumulation was not correct.        
  TYPEDB2  35.267  DB2 Netezza IDAA variables Q8STxxxx corrected.       
  TYPEDB2  35.277  New IFCID=225 QWA225PRISTG_PAGE variable added.      
  VMACSMF  35.266  SMF ID=2 SYSTEM=DUMY 14 byte records protected.      
  CICINTRV 35.264  CICDS Dispatch dataset DISP+WAIT GE Interval DURATM. 
  TYPEBVIR 35.260  BVIR History updated for 3.3 media codes and BVIR302.
  TYPEPOEX 35.257  Protection for truncated Power Exchange SMF record.  
  TYPETMS5 35.278  Correction for TMS Stacked Tape Files wrong values.  
Enhancements                                                            
  TYPE102  35.262  New DB2 zPARMS variables created in T102S106 dataset.
  TYPETPMX 35.261  Execution time for TYPETPMX halved by restructure.   
  TYPERMFV 35.259  New ZRBLCPLPAR dataset with per-LPAR totals.         
  TYPERMFV 35.259  IBM 4HR MSU (CPUAVB4H) in ZRBCPU per) interval.      
  VMXGSET  35.256  Example to read "concatenated" PDBs with PROC SQL.   
                                                                        
==Major CHANGES added in MXG 35.10, dated Nov  6, 2017 thru 35.255.     
                                                                        
New Products Support                                                    
  TYPERMFV 35.249  Support for z/OS 2.3 RMF III CPUG3 ZRBCPU changes.   
  TYPE113  35.246  SMF113/HIS formula for z14 L3P/RNI/SM1132SP changed. 
  TYPEPOEX 35.242  Support for Power Exchange Version 10.1.1.           
  TYPE42   35.240  Support for APARS OA52132/OA52133/OA61734 UNTESTED.  
Error Corrections                                                       
  TYPE119  35.220  Zero observations in TYP11920 dataset.               
  TYPE119  35.245  SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED.         
  TYPEDB2  35.229  PDB.DB2STATB/STSBP protection for large gaps in data.
  TYPEDB2  35.248  Four QWA225 and QWB225 variables now kept/input.     
  FORMATS  35.243  MOBILE WORK CSV files for CICS/TS 5.3 missing prod.  
  ANAL118  35.241  Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.         
  TYPEXAM  35.218  XAMSYPUP dataset variables are now correctly aligned.
  TYPEXAM  35.223  zVPS/XAM extra SYTCUP with totals is now decoded.    
  TYPEVMXA 35.221  zVM MONWRITE VXPRCPUP dataset corrected.             
Enhancements                                                            
  GRAFCEC  35.230  Replaces GRAFLPR, CPU/zIIP/4HR MSU graphs.           
  UTILBLDP 35.225  New EXPDBVAR/EXPDBCDE/EXPDBOUT to create subset.     
  BUILDPDB 35.234  New EXPDBKEP lets you KEEP=/DROP= vars in JOBS/STEPS+
  TYPE80A  35.231  RACFDIRECTED allows DELETE of RACF records DTP=44.   
  DEDUP701 35.236  Duplicate 70 Subtype 1 records can cause bad results.
  TYPERMFV 35.235  RMF III ZRBCPU enhanced with decodes of CPC_HOMEFLAG.
  TYPE116  35.219  MQMACCT variable NETSNAME new format decoded.        
  UTILEXCL 35.228  Support for 20 user character fields in CICSTRAN.    
                                                                        
==Major CHANGES added in MXG 35.09, dated Oct  2, 2017 thru 35.225.     
                                                                        
 MXG 35.09+ is required for:                                            
   z14 processor, ONLY the SMF 113 records were incompatibly changed.   
   z/OS 2.3  SMF 2 and 90 records incompatibly changed.                 
   z/VM 6.1.17.1 MONWRITE records incompatibly changed.                 
                                                                        
Error Corrections                                                       
  TYPE0203 35.190  SMF type 2 subtype 2 (SMF Signature enabled) STOPOVER
  TYPEVMXA 35.203  z/VM 6.4.17.1 INCOMPATIBLE fields.                   
  TYPENMON 35.208  Nigel's Monitor changed HH:MM to N MINS, INCOMPAT.   
  TYPE90A  35.199  z/OS 2.3 type 90 subtype 38 INPUT STATEMENT EXCEEDED 
New Products Support                                                    
  TYPE113  35.310  Support for z14 SMF type 113 (INCOMPATIBLE).         
  TYPEBETA 35.209  Support for BETA 93 Version 610 (INCOMPATIBLE).      
  TYPEBE97 35.196  Support for BETA 97 Extended 610 Header (INCOMPATIBL)
  TYPE102  35.204  Support for new IFCID 376 variables in T102S376.     
  TYPERMFV 35.191  Support for z/OS 2.3 ZRBASI and ZRBUWD new fields.   
  TYPEXAM  35.195  Support for zVPS XAM XAMPUP segment.                 
  TYPE6156 35.207  TYPE6156 enhancement adds FIRSTGEN and LASTGEN.      
  BUILD005 35.206  New %LET SPINSTC=365 keeps STC Account fields longer.
  TYPE30   35.205  Documentation of what is counted in SMF 30 EXCPs.    
  TYPECIMS 35.197  IMF variables STRTTIME/ENDTIME now in microseconds.  
  Many     35.194  Unrequested log messages  MXGDEBUG: VMXGOPTR         
  BLDSMPDB 35.200  New daily/weekly/monthly optional paths.             
  TYPE74   35.193  Alignment for sync I/O variables.                    
  TYPE116  35.192  MQMQUEUE INTS/STRT populated in subtype 2 records.   
                                                                        
==Major CHANGES added in MXG 35.08, dated Aug 24, 2017 thru 35.186.     
                                                                        
Error Corrections                                                       
  TYPE74   35.182  MXG 34.07 INPUT STATEMENT EXCEEDED RMF 74 SUBTYPE 8. 
  TYPE92   35.180  SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED RECORD.   
  TYPEVMXA 35.174A MONWRITE VXBYUSR _MT1 and _PRO (SMT times) corrected.
  TYPEROSC 35.177  PDB.ROSCOE, ROSIGNON Logon Time, CONNECTM, corrected.
New Products Support                                                    
  TYPE119  35.173  Support for SMF 119 Subtype 11 Zert record.          
  TYPE102  35.183  IFCIDs 389,404,413,414,477 support.                  
  TYPEBBMQ 35.176  Support for BBMQ QSDSTYPE='DISTRIBUTED SYSTEM TYPE'. 
  BUILDPDB 35.174  CPITCITM/CPISRITM Init, CPITCTTM/CPISRTTM added.     
                                                                        
==Major CHANGES added in MXG 35.07, dated Aug  2, 2017 thru 35.171.     
                                                                        
New Products Support                                                    
  TYPEmany 35.166  Support for z/OS 2.3, many additions.                
  TYPEVMXA 35.165  New variables added to VXMTRMEM dataset.             
  TYPEXAM  35.164  New variables added to XAMSYS dataset.               
  TYPEZDP  35.162  Support for Dell/EMC Mainframe Enabler zDP           
  TYPEMVCI 35.161  Support for BMC Mainview/CICS Version 7.1.           
  TYPEAXWY 35.150  Support for AXWAY Version 3.1.3, incomplete.         
  IMACICWU 35.158  Support for Mainview/CICS 7.1 SMF 110 BMCMVCIC.      
  TYPEBE97 35.152  Support for Beta 97 Subtype 22 for version 430/610.  
Error Corrections                                                       
  ASUMUOW  35.157  Variable DB2TCBTM removed from CPUUOWTM.             
  TYPETPX  35.155  STOPOVER when IP Port was changed from 4 to 5 digit. 
  ASMRMFV  35.154  STOPOVER using TYPERMFV if UWD records are created.  
  TYPE7002 35.153  IBM RMF CRYPTO report TOTAL EXEC is AVERAGE EXEC.    
                                                                        
                                                                        
==Major CHANGES added in MXG 35.06, dated Jun 30, 2017 thru 35.151.     
                                                                        
Error Corrections                                                       
  ASMRMFV  35.148  Must specify both SVP and RCD for RMF III CPUTM      
  TYPERMFV 35.148  RMF III CPUTM wrong if RCD without SVP selected.     
  TYPEVMXA 35.145  zVM SMT INTERVAL vars were incorrectly DIF()'d.      
  TYPE74   35.146  TYPE749 Corrections, vars R749FPGBYTx, and R749Dxxx. 
  TYPE103  35.134  Dataset TYPE103D vars T103DBYT/T103DREQ corrected.   
  TYPEVMXA 35.131  Variable CALENMT incorrect, new CALSHARE variable.   
  TYPE30_6 35.127  Negative values for Early Address Spaces corrected.  
  TYPE30_6 35.127  Negative values for Early Address Spaces corrected.  
  VMAC38   35.136  NETVIEW ID=38 unexpected S38CCALR length corrected.  
New Products Support                                                    
  TYPE42   35.137  APAR OA44319 improves accuracy for I/O durations.    
  TYPE991  35.123  New z/OS 2.2 variables added to TYPE991 dataset.     
  TYPEVMXA 35.132  Support for zVM 6.4 APAR VM66026 new variables.      
  TYPEBETA 35.139  BETA93 and BETA97 Subtype 25 restructure support.    
  TYPEXAM  35.147  Support for XAM new VSIDSK and XAMPRC segments.      
Enhancements                                                            
  UTILBLDX 35.149  New BUILDJCL=YES creates IFASMFDP code to select SMF.
                   SIGNIFICANT CPU SAVINGS for Ad Hoc SMF read when only
                   a few SMF records are wanted from a large file.      
                   See Change Text.  Will replace UTILBLDP next version.
  ASUM70PR 35.150  Option %LET CECONLY=YES creates ASUMCEC/ASUMCELP only
  ASUM70PR 35.144  MXGERROR:MISSING TYPE 70 RECORDS message.            
  TYPE113  35.141  SMF 113 Formula for RNI updated for z13.             
  IMACINIT 35.128  Note: OPTIONS NOCAPSOUT recommended for ODS users.   
  ASMRMFV  35.135  RMF III Enhancements, Filtering.                     
  UTILBLDP 35.143  Options SUPPRESS enhanced, NEVER corrected.          
                                                                        
==Major CHANGES added in MXG 35.05, dated May 15, 2017 thru 35.121.     
                                                                        
Error Corrections                                                       
  TYPEDB2  35.111  DB2 12.1 INVALID QLAC, CONTINUOUS DELIVERY CAUSED.   
                    THIS IS IMPORTANT: LOOK FOR INVALID QLAC ERROR ON   
                    YOUR SAS LOG - OBSERVATIONS ARE NOT OUTPUT.         
                    THE FIELDS WERE INSERTED BY APAR PI74456.           
  TYPE7072 35.113  35.04 only. TYPE79 SHARE weights wrong, ASUMCELP ok. 
  VMXGPRNT 35.120  WPS only, MXG 35.04 Only, Blank Label ERROR.         
  VMXGFIND 35.117  Multiple input PDBs were read, only one was output.  
  JCLTEST9 35.116  35.04 only. //MVJEIN DD in wrong step.               
  VGETSORT 35.112  35.04 only. ERROR Truncated SORTBY (name GT 32).     
  TYPE129  35.109  Variables SM1209EX/EY/EZ/FA were dropped.            
  ANALID   35.108  ANALID report TITLE for BUILDPDB can be tailored.    
New Products Support                                                    
  TYPEIAM  35.107  Support for IAM Version 9.0.                         
Enhancements                                                            
  TYPE110  35.105  CICS duration fields are now formatted TIME16.6.     
                                                                        
==Major CHANGES added in MXG 35.04, dated May  1, 2017 thru 35.104.     
Error Corrections                                                       
  TYPE7072 35.093  MXG 35.03 only. PLATBUSY/PCTOF HDW TYPE70/RMFINTRV.  
  TYPEVMXA 35.079  z/VM 6.3 SMT in VXSYTPRP, VXAPLSO0 corrections.      
  TYPEXAM  35.074  Velocity XAM SYTCPU invalid errors at vendor.        
  TYPEDB2  35.081  DB2ACCTP, truncated QPACLOCN/COLN/PKID/ASCH/AANM     
New Products Support                                                    
  TYPEMVJE 35.094  Support for BMC Mainview for Java Environment.       
  TYPEVMXA 35.092  Updated support for z/VM 6.4 (INCOMPAT, SYTLCK).     
Enhancements                                                            
  ANALFTP  35.087  New ANALFTP analysis provided five new reports.      
  ANALCNCR 35.091  New example count/plot concurrent TELNET sessions.   
  IHDRNDM  35.089  New NDM-CDI IHDRNDM exit for NDMRTYPE selection.     
  BUILDPDB 35.088  Running MXG on ASCII, free SMF alloc at read end.    
  TYPEOPSS 35.090  Support for CA's OPSS Product User SMF Record.       
                                                                        
==Major CHANGES added in MXG 35.03, dated Mar 27, 2017 thru 35.072.     
                                                                        
  VMAC1415 35.072  First MXG 35.03. Debug HEX DUMPS on log, no ERROR.   
                   Not serious, but easily corrected with this update.  
                                                                        
==Major CHANGES added in MXG 35.03, dated Mar 22, 2017 thru 35.069.     
                                                                        
Significant Correction/Documentation                                    
  TYPE7072 35.064  SMT Mode corrections, "Inflated" CPUZIPTM in MT=2    
                   ONLY IMPACTS 72 and 30 -  TYPE 70 DATA JUST FINE!    
New Products Support                                                    
  TYPE110  35.069  Support for CICS/TS 5.4 BETA 11 CICSTRAN new vars.   
  TYPESVIE 35.059  Support for CA SYSVIEW for IMS 14, missing values.   
  TYPEIMS  35.058  Support for IMS LOG 67D0 DIAGNOSTIC DC Log Record.   
  TYPEMVIP 35.055  Support for Mainview for IP PTF BPN2331 adds flag.   
  TYPE120  35.051  Support for Liberty 17.0.0.1 SMF 120 ST 12 new data. 
  TYPEOPC  35.048  Support for IWS/TWS/OPC Version 9.3 ST 66 was ST 23. 
  TYPE102  35.047  Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.
  TYPE102  35.046  Support for IFCID 125 Truncated fields.              
  TYPEVMXA 35.040  Support for Velocity ZWRITE z/VM MONWRITE records.   
  TYPEXAM  35.063  Support for XAMSYS wrong length, XMTCPSYS NAMENODE.  
  TYPEMVCI 35.062  Support for Mainview CICS CMRDETL file VER 6700.     
  TYPE30   35.066  APAR OA59593 adds INELIGHONOR flag to SMF 30s.       
Enhancements                                                            
  TYPEDCOL 35.064A Multi-Volume DCOLDSET fields retained & populated.   
  ASUMCELP 35.061  Variable SMT_NUM added to PDB.ASUMCELP with MT mode. 
  TYPE120  35.060  SMF 120 ST 11 TYP120BL CP and zIIP variables added.  
  GRAFCAPS 35.042  Example report of Resource Group CPU use and CAPPING.
  ASUM70PR 35.061  Enhancement adds SMT_NUM to PDB.ASUMCELP dataset.    
  TYPE120  35.060  Enhancement adds TOTAL/CP ONLY/ZIP CPU to TYP120BL.  
  ASMRMFV  35.054  RMF Monitor III Enhancement for OPD data filtering.  
  ASUM70PR 35.050  Error message if PDB.ASUMCELP does not have all 70s. 
Corrections                                                             
  VMXGSUM  35.056  Correction for KEEPMNTH= (very rarely used) option.  
  TYPERMFV 35.044  ZRBCP SMT vars missing, new CPC_CECNAME variable.    
  TYPE1415 35.040A IBM APAR OA51325 corrects missing UCB segment.       
  CICINTRV 35.038  MXG correction for ITRM to NOT delete CICINTRV       
                                                                        
                                                                        
==Major CHANGES added in MXG 35.02, dated Feb 10, 2017 thru 35.035.     
                                                                        
Execution Errors Corrected:                                             
  VMXGSUM  35.022  COMPBL too few arg, VARIABLE QWACBSC ALREADY...      
                   Rare and obscure, only three reports, but nasty      
                   if encountered deep in your daily run, so please     
                   "drop in" 35.02, which is a very good LEVEL SET.     
  VMXGSUM  35.020  MXG 35.01. Ignore MXGWARN VMXGSUM BACKLEVEL msg.     
  UTILEXCL 35.023  MXG 35.01.Old Dictionary Records were not used.      
  TYPEVMXA 35.025  Using _VMINPUT. z/VM variable VMDUSER was 1 byte.    
Variables corrected:                                                    
  TYPEDB2  35.027  DB2STATS QISTxxxx Storage multiplied by 4K vs 1K.    
  TYPE78   35.021  TYPE78PA variables R782LSMO/GMFO/GFRR are wrong.     
  GRAFWRKX 35.018  WARNING but ZIPTM, IFATM, and ZIETM were not plotted.
  TYPE120  35.024  Subtype 9 variables SMF1209EV,FI,EW no longer kept.  
  VMXGALOC 35.033  Month begin/logic revised, MNTHKEEP zero protected   
  TYPE42   35.031  Variable S42DSIOS added to TYPE42DS.                 
  TYPEDB2  35.030  DB2STAT4 _REAL variables way too large.              
New Products Support                                                    
  TYPE102  35.017  New DB2 ZPARMS added to T102S106 dataset.            
  TYPE117  35.015  Support for SMF 117 GTZ record.                      
  TYPE125  35.015  Support for SMF 125 GTZ record, untested.            
  TYPE80A  35.029  RACFTYPE=6 seg increased in length, message, no fail.
  TYPERMFV 35.028  New RMF III ZRBENC "long names" now input and kept.  
  IMACDBNZ 35.027  Support for DB2ACCT NETEZZA Q8AC "Accumu" variables. 
  TYPEBBMQ 35.034  Support for BBMQ BMC Utility BBM9MD73 restructure.   
Enhancements                                                            
  UTILRMFI 35.026  Enhanced reporting if SRVCVLASS=SYSOTHER detected.   
  TYPETPX  35.035  Protection for invalid TPX subtype 7 record.         
                                                                        
==Major CHANGES added in MXG 35.01, dated Jan 20, 2017 thru 35.015.     
                                                                        
POTENTIALLY SERIOUS Error Corrected:                                    
                                                                        
  RMFINTRV 35.006  Duplicate RMFINTRV if Multiple Capacity Groups exist.
                                                                        
         Culprit was MXG's addition of variable SMF70GNM to PDB.RMFINTRV
         back in MXG 34.01 in Feb, 2016, but only reported now by only  
         two sites.  THERE IS NO ERROR MESSAGE ON THE LOG.              
            PROC FREQ DATA=PDB.RMFINTRV; TABLES SMF70GNM;               
         will show if you are exposed. %INCLUDE SOURCLIB(RMFINTRV);     
         with //PDB DD DISP=OLD with this Change will rebuild           
         PDB.RMFINTRV correctly for each mis-built PDB data library.    
                                                                        
Errors Corrected:                                                       
  UTILEXCL 35.004  ERROR PDB.CICSDICT not FOUND - USE THIS UTILEXCL.    
  TYPE115  35.011  For local time zones with +GMT, GMT115TM wrong.      
  TYPE120  35.007  Liberty SMF 120 st 12 SM120CCC/CCD Year 2027.        
  TYPEPOEX 35.002  INVALID SMF Records caused STOPOVER ABEND.           
  TYPEOSEM 35.010  OSEM User SMF INPUT EXCEEDED, invalid, circumvented. 
New Products Support                                                    
  TYPE71   35.009  Support for APAR OA48913 with 2GB Memory Frames      
Enhancements                                                            
  TYPERMFV 35.005  Dataset ZRBLCP obs created for ONLINE LCPUADDRs.     
                                                                        
                                                                        
    Please read CHANGESS for the complete list of major enhancements.   
                                                                        
  See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
  current MXG Technical Notes.                                          
                                                                        
                                                                        
  All of these enhancements are described in the Change Log, below.     
                                                                        
II.   SAS Version requirement information:                              
                                                                        
   SAS Versions                                                         
     The current version nomenclature is SAS 9.4 TS1M5 (9.4M5), "M5",   
     or "SAS 9.4 (TS04.01M5P09132017)" if the OPTION VERSIONLONG is     
     enabled.                                                           
                                                                        
     Only on z/OS, SAS 9.4 "M5" requires MXG 35.36 because it adds the  
     NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect 
     that will be corrected in SAS Note 61672 defect.  See Change 35.309
     for more details on using NOERRORSTOP for your own PROC SQLs.      
                                                                        
     SAS V9.4 M5 Is RECOMMENDED, but MXG executes without error         
     using SAS Version 9.4 M0-M4 or SAS Version 9.3 M0-M2.              
                                                                        
     SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.      
                                                                        
     SAS V9.3   SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.  
                But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
                see CHANGE 29.169, IS REQUIRED:                         
                  The %MACRO compiler error is in processing %LET       
                  statements. While only two MXG members failed         
                  repeatedly in MXG QA tests on z/OS, there were random 
                  %LET errors in ASCII QA tests, so ANY use of %LET     
                  statement on ANY platform are vulnerable to this      
                  error, as the %MACRO compiler is SAS portable code,   
                  used on all platforms.  So this is NOT just an MXG    
                  error, but impacts ALL SAS programs.                  
                SAS9.3 is LEVEL A support from SAS.                     
     SAS V9.2   Was recommended, prior to 9.3, and was error-free with  
                MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to 
                use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2      
                Decompression Infile Exit.  but SAS V9.2 does execute on
                that platform.                                          
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
                Support level C by SAS Institute, Sep 30, 2013.         
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
     SAS V8.2   SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS! 
                with SAS 8.2.                                           
                SAS 8.2 is Level C Support from SAS as of Dec 31, 2011. 
                                                                        
      JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used  
                                                                        
      ***************************************************************   
      As documented in Change 27.356, for SAS V9.2 or later):           
      The standard SAS JCL Procedure can be used for MXG with SAS V9.2+ 
           // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                  
           //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR     
      or you can continue to use the MXGSAS94 JCL Procedure example.    
      ***************************************************************   
                                                                        
      MXG 26.03 thru MXG 35.36 will execute under the previously listed 
      SAS Versions on all supported platforms                           
                                                                        
      Unrelated to the above SAS Note/Hot Fix, ODS users will want to   
      use MXG 29.06+, because SAS V9.3 did expose incompatibilities in  
      MXG code for ODS reporting, that were fixed in MXG Version 29.06. 
      See Changes 29.159 and 29.169.                                    
                                                                        
                                                                        
      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). 
        Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors  
        can occur even though //XXXXXXXX DD is a valid SAS Data Library.
        This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does   
        NOT occur with SAS V9.2, nor with z/OS 1.9.  It can be          
        circumvented by adding a LIBNAME statement that specifies the   
        ENGINE name. See the Technical Note in Newsletters for SN-35332.
        Note that SAS V9.1.3 is now at "Level B" Support from SAS.      
                                                                        
      Old MXG code may continue to execute with SAS V8.2, but V8 is now 
      "Level C" 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 cannot guarantee that all of MXG executes error free.     
      PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!           
         If you are absolutely stuck on V8, you need to copy MXG member 
         V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.           
                                                                        
      MXG Software has not executed under SAS V6 in many years.         
                                                                        
      The "PDB" libraries (i.e., SAS data libraries) must be created by 
      SAS V8 or later, but any of those data libraries can be read or   
      updated by the SAS Versions that MXG Supports, above.             
                                                                        
                                                                        
      For SAS Version V9.3:                                             
        SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note 
        SN43828 is REQUIRED.  See text of Change 29.159.                
        With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions    
        26.03 or later execute under SAS V9.3 on all platforms.         
                                                                        
        SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and  
        SAS V9.4 are interchangeable and can be read/written by any of  
        those versions, provided they are on the same platform.         
          BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the 
          same "platform" and attempting to read/use the FORMAT catalog 
          created on one of those "platforms" on the other "platform"   
          will error out to remind you of that difference!              
        SAS V9.4 did change some V9.3 ODS processing defaults and syntax
        that might cause errors with MXG 29.05 or earlier; MXG 29.06,   
        Change 29.160 documents the major revisions made in MXG to fully
        support ODS, and MXG 29.06 is STRONGLY recommended for ODS with 
        SAS V9.3 or SAS V9.4.                                           
                                                                        
      For (Archaic) SAS Version V9.2 (TS1M0):                           
                                                                        
        Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.  
                                                                        
        On z/OS, SAS changed the DSNAMES for some of the SAS libraries, 
        so you do need to use the new MXGSAS92 JCL Procedure for MXG,   
        but it still uses the CONFIGV9 configuration file.              
                                                                        
        ****************************************************************
        However, NEW, and documented in Change 27.356, with SAS V9.2+:  
          The standard SAS JCL Procedure can be used for MXG:           
             // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                
             //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR   
          instead of using the MXGSAS92 JCL Procedure example.          
        ****************************************************************
                                                                        
        SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3, 
        and V9.4. "PDBs" can be read/written interchangeably between    
        these SAS versions.                                             
                                                                        
        MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS   
        and with NO ERRORS reported.                                    
          Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a  
          new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
          code). That warning is harmless (to MXG code) and all MXG     
          created SAS datasets were correct, even with that warning.    
          The ONLY exposure was ONLY on z/OS, and ONLY if condition code
          tests are used in your MXG jobstreams.                        
                                                                        
        SAS Version 9.2 requires z/OS 1.7 or later, both officially as  
        documented by SAS Institute, and actually as V9.2 fails with 0C4
        under z/OS 1.4.                                                 
                                                                        
      For SAS V9.1.3 on z/OS with Service Pack 4:                       
                                                                        
        On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.                     
                                                                        
        CONFIGV9 now specifies V9SEQ instead of V6SEQ.  As V6SEQ does   
        not support long length character variables, it can't be used.  
                                                                        
       SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.  
                                                                        
       For (back-level!) SAS V9.1 or V9.1.2 on z/OS:                    
        SN-013514 is REQUIRED to be able to read datasets that were     
          created by V6SEQ (tape) engine.                               
        SN-012437 is REQUIRED to prevent creation of corrupt/unreadable 
          datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.            
        Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT 
          SAFE without those two hot fixes, and if you do NOT have those
          two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.    
                                                                        
        With MXG 23.02 or later, V9SEQ is the default sequential engine 
        specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
        you MUST install the two hot fixes listed above.                
                                                                        
       For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
         as an absolute minimum level when that SAS Version was last    
         supported by MXG Software.  PLEASE INSTALL SAS V9.x ASAP.      
                                                                        
       Sequential Engine Status:                                        
          V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.   
          V8SEQ was always safe under SAS V8.2, but it wasted CPU time  
            by always compressing when writing in tape format.          
          V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ    
                 should no longer be used, as it does not support long  
                 length variables.                                      
                                                                        
      GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:              
                                                                        
      MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and
      Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,   
      but MXG users execute MXG on MANY (ALL??) SAS platforms, including
      AIX, Linux, and other 'nix' variants, on many different hardware  
      platforms, and since they all work we don't need to list them.  If
      SAS executes so does MXG.                                         
                                                                        
      Prior QA tests have been run with all SAS releases available at   
      that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880, 
      and on HP-UX v11.11 model rp5470, confirming full compatibility.  
                                                                        
      MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS  
      platform without errors! Each new MXG version is also tested with 
      the SAS ITSV/ITRM product by the ITRM developers.                 
                                                                        
                                                                        
III.  WPS Version requirement information:                              
                                                                        
      WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.  
         and other errors with 3.00 or 3.01 have been corrected in the  
         current WPS version.                                           
      WPS Version 3.01.1 maintenance level 731 required for PDB to tape 
      WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.     
      WPS Version 3.01  is required for MOBILWRK, PICTURE fails in 2.5. 
      WPS Version 3.01  executed MXG 32.03 BUILDPDB with no errors.     
      WPS Version 3.0   requires MXG 31.09 (see Change 31.251).         
      WPS Version 2.4   required MXG 27.09 (see Change 27.239).         
      WPS Version 2.3.5 required MXG 27.05.                             
                                                                        
      See NEWSLETTERS for WPS Support Statement.                        
                                                                        
      WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID" 
      when the LIBNAME PDB does not exist; there would also have been a 
      prior log message  NOTE: Library PDB does not exist   as the clue.
                                                                        
                                                                        
IV.   MXG Version Required for Hardware, Operating System Release, etc. 
                                                                        
   MXG is usually NOT sensitive to z/OS Hardware changes, but:          
                                                                        
     The z/EC12 with 85+ engines required MXG 30.07.                    
     Support for 255 engines was added in MXG 31.04.                    
     The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.        
                                                                        
   However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was  
   INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to
   read the SMT-format RMF records (which are written if you have zIIP  
   engines AND have enabled the new PROCVIEW CORE option for            
   Multi-Threading, even if only one thread is enabled).                
                                                                        
   The new zEDC compression hardware requires MXG 33.07 to support the  
   new metrics.                                                         
                                                                        
   For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.        
                                                                        
                                                                        
    Availability dates for the IBM products and MXG version required for
    error-free processing of that product's data records:               
                                                                        
                                       Product's                        
                                       Availability     MXG Version     
      Product Name                     Date              Required       
                                                                        
      MVS/ESA 4.1                      Oct 26, 1990         8.8         
      MVS/ESA 4.2                      Mar 29, 1991         9.9         
      MVS/ESA 4.2.2                    Aug 15, 1991         9.9         
      MVS/ESA 4.3                      Mar 23, 1993        10.10        
      MVS/ESA 5.1.0 - compatibility    Jun 24, 1994        12.02        
      MVS/ESA 5.1.0 - Goal Mode        May  3, 1995        13.01        
      MVS/ESA 5.2.0                    Jun 15, 1995        13.05        
      MVS/ESA 5.2.2                    Oct 19, 1995        13.09        
      OS/390  1.1.0                    Feb 22, 1996        14.01        
      OS/390  1.2.0                    Sep 30, 1996        14.05        
      OS/390  1.3.0 Compatibility Mode Mar 28, 1997        14.14        
      OS/390  1.3.0 WLM Goal Mode      Mar 28, 1997        15.02        
      OS/390  2.4.0                    Sep 28, 1997        15.06        
      OS/390  2.5.0                    Feb 24, 1998        15.06        
      OS/390  2.6.0                    Sep 24, 1998        16.04        
      OS/390  2.7.0                    Mar 26, 1999        16.09        
      OS/390  2.7.0 APAR OW41318       Mar 31, 2000        18.03        
      OS/390  2.8.0                    Aug 24, 1999        16.09        
      OS/390  2.8.0 FICON/SHARK        Aug 24, 1999        17.08        
      OS/390  2.8.0 APAR OW41317       Mar 31, 2000        18.03        
      OS/390  2.9.0                    Mar 31, 2000        18.03        
      OS/390 2.10.0                    Sep 15, 2000        18.06        
      OS/390  PAV                      Oct 24, 2000        18.09        
      z/OS 1.1                         Mar 30, 2001        18.11        
      z/OS 1.1 on 2064s                Mar 30, 2001        19.01        
      z/OS 1.1 with correct MSU        Mar 30, 2001        19.02        
      z/OS 1.2                         Oct 31, 2001        19.04        
      z/OS 1.1,1.2 APARs to 78         Oct 31, 2001        19.05        
      z/OS 1.2+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.3+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.2 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.3 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.4 Tolerate                Sep 27, 2002        20.03        
      z/OS 1.4 Support                 Sep 27, 2002        20.06        
      z/OS 1.4 Over 16 CPUs/LPARs      May 29, 2003        21.02        
      z/OS 1.4 DFSMS/rmm, RACF         Aug 29, 2003        21.04        
      z/OS 1.5                         Mar 31, 2004        21.21        
      z/OS IRD ASUM70PR/ASUMCEC        Sep 22, 2003       *24.10        
      z/OS IRD TYPE70PR                Mar 11, 2004       *24.10        
      z/OS IRD TYPE70,RMFINTRV         Mar 22, 2002       *24.10        
      z/OS 1.6 - No IFAs               Sep 30, 2004       *22.09        
      z/OS 1.6 - With IFAs             Sep 30, 2004       *22.11        
      z/OS 1.7 (COMPATIBLE CHANGES)    Sep 30, 2005       *24.10        
      z/OS 1.7 (SPLIT70 CORRECTION)    Sep 30, 2005       *24.10        
      z/OS IFA data in RMF 79s         Sep 30, 2005        23.10        
      z/OS 1.8 - ASMTAPEE assembly     Sep 30, 2005       *25.03        
      z/OS 1.8 - SMF 119 INCOMPAT      Sep 30, 2005       *25.06        
      z/OS More than 32 LPARs          Jan 30, 2006       *24.24        
      z/OS SPLIT RMF 70 records        Jan 30, 2006       *24.24        
      z/OS Dupe SYSTEMs in a SYSPLEX   Jan 30, 2006       *24.02        
      z/OS IRD errors corrected        May 15, 2006        24.03        
      z/OS ASUMCEC errors corrected    May 15, 2006       *24.24        
      z/OS ASUM70LP errors corrected   Jun 13, 2006       *24.24        
      z/OS zIIP Processor Support      Jun 22, 2006       *24.24        
      z/OS Dedicated zIIP Support      Mar  8, 2008       *26.01        
      z/OS Dedicated zAAP Support      Mar  8, 2008        26.01        
      z/OS 1.8 (COMPATIBLE CHANGES)    Sep 20, 2006       *24.24        
      z/OS 1.9 (INCOMPAT, 54 CPs)      Sep 27, 2007        25.10        
      z/OS 1.9 MXGTMNT at ML-39 reASM  Sep 27, 2007        25.10        
      z/OS new z10 variables           Mar  5, 2008        26.01        
      z/OS 1.8 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.9 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.10 (INCOMPAT, MXG code)   Sep 15, 2008        26.07        
      z/OS 1.10 With HiperDispatch     Sep 15, 2008       *26.10        
      z/OS 1.10 RMF III, SMF 119       Jul 20, 2009        27.05        
      z/OS 1.11                        Sep  2, 2009        27.08        
      z/OS 1.11 New 30 variables       Apr 14, 2010       *28.02        
      z/OS 1.12                        Aug 17, 2010       *28.05        
      z/OS 1.12 SMF 85 Subtype 79      Aug 17, 2010       *29.03        
      z/OS 1.12 VMGUEST option         Aug 17, 2010       *29.06        
      z/OS 1.13                        Sep 30, 2011        29.03        
      z/OS 1.13 - MXGTMNT only         Dec 15, 2011        29.08        
      z/OS 1.13 SMF 119 ST 6 INCOMPAT  Feb  7, 2012        30.01        
      z/OS 2.1  - Most Records support Jul 23, 2013        30.05        
      z/OS 2.1  - ID=0 ERROR MESSAGE   Jul 23, 2013        31.07        
      z/OS 2.1  - ID=85 INCOMPAT       Jul 23, 2013        32.03        
      z/OS 2.1  - ID=70 SMF70CPA       Jul 23, 2013        32.03        
      z/OS 2.1  - INPUT STATEMENT EXCEEDED ERROR SMF 74    33.10        
      z/OS 2.2  COMPATIBLE CH 33.189   Aug 19, 2015        33.08        
      z/OS 2.2 MXGTMNT ABEND S0E0-28   Sep 15, 2015        33.09        
               REQUIRES ASMTAPE ML-55  Sep 15, 2015        33.09        
      z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr  5, 2016        34.02        
      z/OS 2.2 SPLIT 73, ABEND 33.068  Apr  5, 2016        34.02        
      z/OS 2.2 JES2 8-char JOBCLASS    Oct  7, 2016        34.07        
      z/OS 2.2 NEW SMF 124 IOS Spvr    Oct  7, 2016        34.07        
      z/OS 2.3 Many new variables      Sep 24, 2017 35.166 35.09*       
      z/OS 2.3 RMF III Support         Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 2 st 2 STOPOVER    Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 90 st 38 STOPOVER  Sep 24, 2017 35.199 35.09*       
      z990 CPUs - CPUTYPE '2084'x      Aug 25, 2003        21.04        
      z890 CPUs - CPUTYPE '2086'x      Jun 24, 2004        22.07        
      z9   CPUs - CPUTYPE '2094'x      Jul 20, 2005       *24.24        
      z9EC CPUs - CPUTYPE '2094'x:                                      
             with 64-bit z/OS - no change required        *24.24        
             with 32-bit z/OS only:    Aug 26, 2006        24.06        
      z9BC CPUs - CPUTYPE '2096'x:                                      
             with 64-bit z/OS - no change required         24.01        
             with 32-bit z/OS only:    Jul 27, 2006       *24.24        
      z10  CPUs - CPUTYPE '2097'x      Dec  7, 2008        25.11        
      z10  HiperDispatch/Parked Time   Mar  3, 2008       *26.10        
      z196 (INCOMPAT IF GT 64 ENG)     Aug 17, 2010        28.05        
      zEC12                            Nov 14, 2012        30.07        
      z13   non-SMT Mode               May 27, 2014        32.05        
      z13   SMT Mode Change 33.217     Sep 15, 2015       *33.09        
      z13   SMT Mode NRZIPCPU 34.106   May 10, 2016        34.03        
      z13   SMT MT=2 CPUZIPTM TYPE70   Mar 21, 2016        35.03        
      z14   SMF 113 Records INCOMPAT   Oct  2, 2017        35.09        
      CICS/CTG V9 Transaction Gateway  ??  ??  2013        31.31        
      CICS/ESA 3.2                     Jun 28, 1991         9.9         
      CICS/ESA 3.3                     Mar 28, 1992        10.01        
      CICS/ESA 4.1                     Oct 27, 1994        13.09        
      CICS/ESA 5.1 aka CICS/TS V1R1    Sep 10, 1996        14.07        
      CICS-Transaction Server V1R1     Sep 10, 1996        14.07        
      CICS-TS V1R1 with APAR UN98309   Sep 15, 1997        15.06        
      CICS-TS V1R2  CICS/TS 1.2        Oct 27, 1997        15.06        
      CICS-TS V1R3  CICS/TS 1.3        Mar 15, 1999        17.04        
      CICS-TS V2R1  CICS/TS 2.1        Mar 15, 2001        18.11        
      CICS-TS V2R2  CICS/TS 2.2        Feb  9, 2002        19.19        
       CICSTRAN subtype 1 support only                    *19.19        
       CICSTRAN subtype 2 completed                       *19.08        
      CICS-TS V2R3  CICS?TS 2.3        Dec 19, 2003                     
       Using UTILEXCL to create IMACEXCL:                  21.04        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04        
      CICS-TS V2R3  CICS/TS 2.3        Aug 13, 2004        22.04        
      CICS-TS V3R1  CICS/TS 3.1        Jan 18, 2005        22.22        
      CICS-TS for Z/OS Version 3.1     Mar 15, 2005                     
       Using UTILEXCL to create IMACEXCL:                  22.13        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22        
      CICS-TS V3R2  CICS/TS 3.2        Dec  6, 2007        25.11        
      CICS-TS for Z/OS Version 3.2     Jun 29, 2007        25.03        
      CICS-TS/3.2 Compressed Records   Nov  3, 2007        25.11        
      CICS-TS/4.1 (CICSTRAN INCOMPAT)  Mar 13, 2009        27.01        
      CICS-TS/4.1 (STATISTICS ST=2)    Sep 18, 2009        27.08        
      CICS-TS/4.2 CICSTRAN/STATISTICS  Jun 24, 2011        29.03        
      CICS-TS/4.2 CICSRDS MNSEGCL=5    Jun 24, 2011       *29.05        
      CICS-TS/4.2 INVALID STID=116     Jan 31, 2012       *30.01        
      CICS-TS/5.1 (INCOMPATIBLE)       Dec 14, 2012       *30.08        
      CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013       *30.30        
      CICS-TS/5.1 MNSEGCL=5 INCOMPAT   Jun 17, 2013       *31.03        
      CICS-TS/5.2 COMPATIBLE CICSTRAN  Jun 13, 2014       *31.03        
      CICS-TS/5.2 INCOMPAT Statistics  Jun 13, 2014       *32.03        
      CICS-TS/5.3 INCOMPAT CICSTRAN    Apr 29, 2015        33.04        
      CICS-TS/5.3 RESOURCE SEGCL=5     Sep 31, 2015        33.09        
      CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015        33.11        
      CICS-TS/5.3 GA date              Dec 11, 2015        33.33        
      CICS-TS/5.3 MNSEGCL=5 INPUT ERR  Mar 21, 2016        34.02        
      CICS-TS/5.4 OPEN BETA  Aug       Aug 11, 2016        34.06        
      CICS-TS/5.4 OPEN BETA  Nov       Nov 11, 2016        34.09        
      CICS-TS/5.4 GA                   Jun 17, 2017        35.03        
      DB2 2.3.0                        Oct 28, 1991        10.01        
      DB2 3.1.0                        Dec 17, 1993        13.02        
      DB2 4.1.0 Tolerate               Nov  7, 1995        13.07        
      DB2 4.1.0 Full support           Sep 11, 1996        14.07        
      DB2 5.1.0 Tolerate               Jun 27, 1997        14.14        
      DB2 5.1.0 Full support           Jun 27, 1997        15.02        
      DB2 6.1.0 initial support        Mar 15, 1999        16.09        
      DB2 6.1.0 all buffer pools       Mar 15, 1999        18.01        
      DB2 6.1.0 parallel DB2           Mar 15, 1999        19.19        
      DB2 7.1.0 parallel DB2           Mar 31, 2001        19.19        
      DB2 7.1.0 corrections            Mar 31, 2001        20.06        
      DB2 8.1 Tolerate, no packages    Mar 31, 2004        20.20        
      DB2 8.1 New Data Packages wrong  Mar 31, 2004        21.08        
      DB2 8.1 Support with Packages    Mar 31, 2004       *23.09        
      DB2 8.1 with all zIIP Variables  Sep 30, 2006        24.08        
      DB2 8.1 +PK47659                 Sep 12, 2008        26.08        
      DB2 9.1 See Change 25.265.       Dec  7, 2007        25.11        
      DB2 9.1 Full Support +PK/56356   Sep 12, 2008        26.08        
      DB2 10.1 Tolerate                Oct  1, 2010        28.06        
      DB2 10.1 New vars + Compressed   Nov  1, 2010       *28.07        
      DB2 10.1 Invalid Header pre APAR Jan 12, 2011       *28.28        
      DB2 10.1 IFCID=225 INCOMPAT      Sep 23, 2011       *29.07        
      DB2 10.1 QWHCCV for QWHCATYP=8   Oct  3, 2011       *30.07        
      DB2 10.1 DBID/OBID decode        Jan 21, 2013       *30.30        
      DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013       *31.04        
               (ONLY IMPACTS DB2STATS)                                  
      DB2 11.1 TOLERATE DB2 V11.1      Jun 21, 2013        30.30        
      DB2 11.1 DB2STATS QLST CORRECT   Jun 21, 2013        31.04        
      DB2 11.1 SUPPORT NEW VARIABLES   Jun 21, 2013        31.08        
      DB2 11.1 IRLM NEW SEGMENT        Jun 21, 2013        32.10        
      DB2 12.1 COMPATIBLE              Oct  5, 2016        34.08        
      DB2 12.1 NETEZZA CORRECTIONS     Oct  5, 2016        34.08        
      DB2 12.1 QLAC INSERTS DB2ACCT    May 15, 2017        35.05*       
      DFSMS/MVS 1.1                    Mar 13, 1993        11.11        
      DFSMS/MVS 1.2                    Jun 24, 1994        12.02        
      DFSMS/MVS 1.3                    Dec 29, 1995        13.09        
      DFSMS/MVS 1.4                    Sep 28, 1997        15.04        
      DFSMS/MVS 1.4 HSM                Sep 23, 1998        16.04        
      DFSMS/MVS 1.5                    ??? ??, 1999        16.04        
      DFSORT SMF V1R5                  Mar  1, 2006        24.02        
      MQM 1.1.2, 1.1.3, 1.1.4          Apr 25, 1996        14.02        
      MQ Series 1.2.0                  May 26, 1998        16.02        
      MQ Series 2.1.0                  Oct  2, 1999        17.07        
      MQ Series 5.2                    Dec 16, 2000        18.10        
      MQ Series 5.3                    Dec 16, 2002        21.05        
      MQ Series 6.0                    Feb 14, 2006        23.23        
      Websphere MQ Series 7.0          ??? ??, 2009       *28.06        
      Websphere MQ Series 7.1          MAR 12, 2011        29.03        
      Websphere MQ Series 8.0          Jun 24, 2011        29.05        
      Websphere MQ Series 9.1          Mar 20, 2017        35.03        
      NETVIEW 3.1 type 37              ??? ??, 1996        14.03        
      NPM 2.0                          Dec 17, 1993        12.03        
      NPM 2.2                          Aug 29, 1994        12.05        
      NPM 2.3                          ??? ??, 1996        15.08        
      NPM 2.4                          Nov 18, 1998        17.01        
      NPM 2.5                          Feb ??, 2000        18.02        
      NPM 2.6                          Nov ??, 2001        19.06        
      RMDS 2.1, 2.2                    Dec 12, 1995        12.12        
      RMDS 2.3                         Jan 31, 2002        19.11        
      TCP/IP 3.1                       Jun 12, 1995        12.12        
      TCP/IP 3.4                       Sep 22, 1998        16.04        
      WebSphere 5.0 APAR PQ7463        Aug 19, 2003        21.04        
      WebSphere 6.0                    Feb 18, 2006        23.23        
      WebSphere 7.0                    Oct  7, 2010        28.06        
      WebSphere 8.0                    Jul 17, 2011        29.05        
      DOS/VSE POWER V6.3.0             Dec 19, 1998        16.08        
      VM/ESA  2.0                      Dec 23, 1992        10.04        
      VM/ESA  2.1                      Jun 27, 1993        12.02        
      VM/ESA  2.2                      Nov 22, 1994        12.06        
      VM/ESA  2.3                      Jun  1, 1998        16.08        
      VM/ESA  2.4                      Mar  1, 2001        19.03        
      z/VM    3.1                      Mar  1, 2001        19.03        
      z/VM    3.1 DATABYTE=0           May  2, 2002        20.02        
      z/VM    4.2 ??                   May  2, 2002        20.02        
      z/VM    4.4                      Jan 22, 2005        22.22        
      z/VM    5.1                      Jan 22, 2005        22.22        
      z/VM    5.2                      Jan 22, 2006        24.01        
      z/VM    5.3 TOLERATE             Jun  7, 2007        25.05        
      z/VM    5.3 NEW VARIABLES        Sep 12, 2008        26.08        
      z/VM    5.4 (COMPATIBLE)         Sep 12, 2008       *27.01        
      z/VM    6.1 (NO CHANGES)         Jul  7, 2008        27.01        
      z/VM    6.2                      Dec  2, 2011        29.04        
      z/VM    6.3 INCOMPATIBLE         Jul 23, 2013        31.05        
      z/VM    6.3 z/13                 Jan 23, 2016        33.33        
      z/VM    6.4 SYTLCK Incompat      Apr 26, 2016        34.04        
      IMS log 4.1                      Jul  4, 1994        12.02        
      IMS log 5.1                      Jun  9, 1996        14.05        
      IMS log 6.1                      ???  ?, 199?        20.03        
      IMS log 7.1                      ???  ?, 200?        20.03        
      IMS log 8.1                      May 21, 2003        21.02        
      IMS log 9.1                      Mar 96, 2004       *26.01        
      IMS log 10.1                     Mar 06, 2007       *26.01        
      IMS log 11.1                     Apr  1, 2010       *28.02        
      IMS log 12.1                     Jan 23, 2012       *29.29        
      IMS log 13.1 (NOT 56FA)          May 25, 2013        31.03        
      IMS log 13.1 (56FA RECORD)       May 27, 2014        32.05        
      IMS log 14.1 COMPATIBLE          Dec 19, 2015        33.13        
      AS400 3.7.0                      Nov  1, 1996        15.01        
      AS400 4.1.0                      Dec 30, 1996        15.08        
      AS400 4.2.0                      Apr 27, 1998        16.02        
      AS400 4.4.0                      Sep 27, 1999        17.07        
      AS400 4.5.0                      Jul 27, 2000        18.07        
      AS400 5.2.0 - Most records       Jul 23, 2003        21.03        
      AS400 5.2.0 - QAPMMIOP           Jul 23, 2003        22.04        
      AS400 5.3.0                      Jan 22, 2005        22.22        
      AS400 5.4.0                      Aug 26, 2006        24.06        
      AS400 6.1.0                      Jun 29, 2008        26.05        
                                                                        
    Note: Asterisk by the version number means the Version number       
          was changed (to the MXG version required), after an earlier   
          MXG version was listed as supporting this product release,    
          usually because an APAR modified the product's data records.  
          Or a coding error in MXG could be the reason for the change!  
                                                                        
    Availability dates for non-IBM products and MXG version required:   
                                                                        
                                                        MXG Version     
      Product Name                                       Required       
                                                                        
      Demand Technology                                                 
       NTSMF Version 1 Beta                                14.11        
       NTSMF Version 2.0                                   15.05        
       NTSMF Version 2.1                                   15.06        
       NTSMF Version 2.2                                   16.04        
       NTSMF Version 2.3                                   17.10        
       NTSMF 2.4.4                     Aug  9, 2002        20.04        
       NTSMF 2.4.5   INCOMPAT          Apr  1, 2003        21.02        
       NTSMF 2.4.7                     Sep 30, 2004        22.08        
       NTSMF 3.1.4                     Mar 15, 2009        27.01        
       NTSMF 4.0                       Mar 15, 2011        29.03        
      Landmark                                                          
       The Monitor for DB2 Version 2                       13.06        
       The Monitor for DB2 Version 3.0                     16.02        
       The Monitor for DB2 Version 3.1                     20.04        
       The Monitor for DB2 Version 4.0                     22.10        
       The Monitor for DB2 Version 5.0                     30.02        
       The Monitor for CICS/ESA 1.2 -                      12.12        
       The Monitor for CICS/ESA 1.3 -                      15.01        
       The Monitor for CICS/ESA 2.0 -                      15.06        
       The Monitor for CICS TCE 2.1 -                      20.04        
       The Monitor for CICS TCE 2.2 - 20.335, 21.134       21.04        
       The Monitor for CICS TCE 2.3 including CICS/TS 3.1  22.08        
       The Monitor for CICS TCE 3.2 (almost all)           25.11        
       The Monitor for CICS TCE 3.2 (almost all)           27.01        
       The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2)  29.07        
       TMON/CICS 3.4 (for CICS/TS 5.1)               30.30-32.12        
        (Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)              
       TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099)     33.04        
       TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195)    *33.09        
       TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257      34.08        
       The Monitor for MVS/ESA 1.3  -                      12.05        
       The Monitor for MVS/ESA 1.5  -                      12.05        
       The Monitor for MVS/ESA 2.0  -                      15.09        
       The Monitor for MVS/ESA 3.0  -                      19.19        
       TMON/MVS Version 4.4                                32.04        
                                                                        
      Candle                                                            
       Omegamon for CICS V200 User SMF                     12.05        
       Omegamon for CICS V300 User SMF                     13.06        
       Omegamon for CICS V400 User SMF                     16.02        
       Omegamon for CICS V400 type 110 segments            16.02        
       Omegamon for CICS V500 User SMF                     18.01        
       Omegamon for IMS V110 (ITRF)                        12.12        
       Omegamon for IMS V300 (ITRF)                        14.04        
       Omegamon for IMS V550/V560 (ITRF)                   25.05        
       Omegamon for MVS V300                               13.05        
       Omegamon for MVS V400                               13.06        
       Omegamon for DB2 Version 2.1/2.2                    13.05        
       Omegamon for VTAM V160                              12.04A       
       Omegamon for VTAM V400                              15.15        
       Omegamon for VTAM V500                              18.08        
       Omegamon for SMS V100/V110                          12.03        
      CA                                                                
       ACF2 6.2                                            16.04        
       ASTEX 2.1                                           14.04        
       IDMS 18                                             32.05        
       IDMS 19 (INCOMPAT after PTF R084146 Change 34.164)  33.05        
       NETSPY 4.7                                          14.03        
       NETSPY 5.0                                          14.03        
       NETSPY 5.2                                          16.05        
       NETSPY 5.3                                          18.03        
       NETSPY 6.0                                          20.10 20.305 
       NETSPY 7.0                                          20.10 20.305 
       SAR/VIEW R11                                        23.07 23.196 
      BMC, was Boole & Babbage                                          
       APPTUNE V11R2 SMF 102                               33.11 33.264 
       IMF 3.1 (for IMS 5.1)                               12.12        
       IMF 3.2 (for IMS 6.1 only)                          15.09        
       IMF 3.2 (for IMS 5.1 and 6.1+)                      16.04        
       IMF 3.3 (for IMS 7.1 and 8.1)                      *22.08        
       IMF 4.1 (for IMS 9.1)                              *26.02        
       IMF 4.4 (for IMS 9.1)                              *31.08        
       IMF 4.5 (for IMS 11.1)  (No change since 4.4)       31.08        
       IMF 4.6 a/k/a Mainview IMS                         *31.08        
       IMF 5.1 a/k/a Mainview IMS                         *34.01        
       IMF 5.2 a/k/a Mainview IMS                          34.01        
       Mainview for MQ Version 4.4                         29.03        
       Mainview for MQ Version 5.1                         30.02        
       Mainview for MQ Version 5.2                         33.01        
       Mainview for CICS Version 6.5 (CICS/TS 5.1)         30.30        
       Mainview for CICS Version 6.4 (CICS/TS 4.2)         30.04        
       Mainview for CICS Version 6.1                       26.26        
       Mainview Auto Operator data file                    28.28        
       Mainview for DB2 THRDHIST file                      20.20        
       Mainview for TCP/IP                                 20.20        
       Mainview for IP                                     34.??        
       Mainview for Batch Optimizer                        19.19        
      Memorex/Telex                                                     
       LMS 3.1                                             12.12A       
      Oracle V9, V10                                       24.06        
      SYNCSORT                                                          
       2.1                                                 33.05        
       1.4                                                 33.08        
      Amdahl                                                            
       APAF 4.1, 4.3                                       16.08        
      Velocity Software                                                 
       XAMAP 3.4                                           22.10        
       XAMAP 3406                                          24.03        
       XAMAP 3.7                                           27.10        
       XAMAP 4.1   Now Renamed to ZVPS 4.1                 29.07        
       XVPS  4.2                                           31.06        
       ZVPS  5.4                                          *33.07        
                                                                        
V.    Incompatibilities and Installation of MXG 35.36.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 35.36:                          
                                                                        
  a- Changes in MXG architecture made between 35.36 and prior versions  
     that can introduce known incompatibilities.                        
                                                                        
                                                                        
 2. Installation and re-installation procedures are described in detail 
    in member INSTALL (which also lists common Error/Warning messages a 
    new user might encounter), and sample JCL is in member JCLINSTT for 
    SAS Version 9.                                                      
                                                                        
    MXG Definitions with regard to MXG Software Changes:                
                                                                        
    COMPATIBLE   A change in a data record which did not alter either   
    COMPAT       the location or the format of all of the previously-   
                 kept MXG variables is COMPATIBLE, and you can continue 
                 to run the old version of MXG software, which will read
                 the new records without error, but none of any new data
                 fields or any new record subtypes will be created/kept 
                 until you install the MXG Version with this change.    
                                                                        
    INCOMPAT     A change in a data record that causes the current MXG  
                 version to fail, visibly or invisibly, with or without 
                 error conditions or messages, and the output datasets  
                 may contain wrong values and incomplete observations,  
                 and/or observations may have been lost.                
                 You MUST install the new MXG Version with this change  
                 to process data records that have been INCOMPATIBLY    
                 changed by their vendor.                               
                                                                        
    TOLERATE     In other words, the old MXG Version TOLERATES the new  
                 data records, if they are COMPATIBLY changed.          
                                                                        
    EXPLOIT      Once you use the new MXG Version to read the changed   
                 records, all of the new fields, subtypes, etc, that are
                 described in this change will be created in the MXG    
                 datasets, so the new MXG Version EXPLOITS the new data,
                 and you have full support of the new data records.     
                                                                        
      An MXG Version never "expires" nor "goes out of Support".  When   
      you put in a new product/subsystem/Release/APAR that incompatibly 
      changed its records then you must install the current MXG Version 
      or at least be using the minimum level of MXG that is currently   
      documented in the preceding list in section IV.                   
                                                                        
     COSMETIC     Some Changes will start with COSMETIC.  This indicates
                  that that change only alters a displayed value or may 
                  be a spelling error in a label, but it is "cosmetic"  
                  in that it ONLY affected the display, and the output  
                  data sets created are NOT impacted by this change.    
                                                                        
VI.   Online Documentation of MXG Software.                             
                                                                        
    MXG Documentation is now described in member DOCUMENT.              
    See also member INDEX, but it may be overwhelming.                  
                                                                        
                                                                        
VII.  Changes Log                                                       
                                                                        
--------------------------Changes Log---------------------------------  
                                                                        
 You MUST read each Change description to determine if a Change will    
 impact your site.  All changes have been made in this MXG Library.     
                                                                        
 Member CHANGES always identifies the actual version and release of     
 MXG Software that is contained in that library.                        
                                                                        
 The CHANGES selection on our homepage at http://www.MXG.com            
 is always the most current information on MXG Software status,         
 and is frequently updated.                                             
                                                                        
 Important changes are also posted to the MXG-L ListServer, which is    
 also described by a selection on the homepage.  Please subscribe.      
                                                                        
 The actual code implementation of some changes in MXG SOURCLIB may be  
 different than described in the change text (which might have printed  
 only the critical part of the correction that need be made by users).  
                                                                        
 Scan each source member named in any impacting change for any comments 
 at the beginning of the member for additional documentation, since the 
 documentation of new datasets, variables, validation status, and notes,
 are often found in comments in the source members.                     
                                                                        
                                                                        
Alphabetical list of important changes in MXG 35.36 after MXG 34.34:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  Many     35.308  SAS Defect 9.4 M5 PROC SQL NOERRORSTOP circumvention.
  Many     35.166  Support for z/OS 2.3 (many new variables), COMPAT.   
  Many     35.194  Unrequested log messages  MXGDEBUG: VMXGOPTR         
  ANAL118  35.241  Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.         
  ANALCNCR 35.091  New example count/plot concurrent TELNET sessions.   
  ANALDB2R 35.307  Broken DO Syntax in 35.11-35.35 if PDBOUT=PDB is used
  ANALFTP  35.087  New ANALFTP analysis provided five new reports.      
  ANALID   35.108  ANALID report TITLE for BUILDPDB can be tailored.    
  ASMRMFV  35.054  RMF Monitor III Enhancement for OPD data filtering.  
  ASMRMFV  35.135  RMF III Enhancements, Filtering.                     
  ASMRMFV  35.148  Must specify both SVP and RCD for RMF III CPUTM      
  ASMRMFV  35.154  STOPOVER using TYPERMFV if UWD records are created.  
  ASUM70PR 35.050  Error message if PDB.ASUMCELP does not have all 70s. 
  ASUM70PR 35.061  Enhancement adds SMT_NUM to PDB.ASUMCELP dataset.    
  ASUM70PR 35.144  MXGERROR:MISSING TYPE 70 RECORDS message.            
  ASUM70PR 35.150  Option %LET CECONLY=YES creates ASUMCEC/ASUMCELP only
  ASUMCELP 35.061  Variable SMT_NUM added to PDB.ASUMCELP with MT mode. 
  ASUMUOW  35.157  Variable DB2TCBTM removed from CPUUOWTM.             
  BLDSMPDB 35.167  VGETSORT revisions for PDB name, internal.           
  BLDSMPDB 35.200  New daily/weekly/monthly optional paths.             
  BUILD005 35.206  New %LET SPINSTC=365 keeps STC Account fields longer.
  BUILDPDB 35.088  Running MXG on ASCII, free SMF alloc at read end.    
  BUILDPDB 35.174  CPITCITM/CPISRITM Init, CPITCTTM/CPISRTTM added.     
  BUILDPDB 35.234  New EXPDBKEP lets you KEEP=/DROP= vars in JOBS/STEPS+
  CICINTRV 35.038  MXG correction for ITRM to NOT delete CICINTRV       
  CICINTRV 35.264  CICDS Dispatch dataset DISP+WAIT GE Interval DURATM. 
  DEDUP701 35.236  Duplicate 70 Subtype 1 records can cause bad results.
  FORMATS  35.243  MOBILE WORK CSV files for CICS/TS 5.3 missing prod.  
  GRAFCAPS 35.042  Example report of Resource Group CPU use and CAPPING.
  GRAFCEC  35.230  New graphs CPU/zip Hours/4HR MSU, replaces GRAFLPAR. 
  GRAFCEC  35.230  Replaces GRAFLPR, CPU/zIIP/4HR MSU graphs.           
  GRAFWRKX 35.018  WARNING but ZIPTM, IFATM, and ZIETM were not plotted.
  IHDRNDM  35.089  New NDM-CDI IHDRNDM exit for NDMRTYPE selection.     
  IMACDBNZ 35.027  Support for DB2ACCT NETEZZA Q8AC "Accumu" variables. 
  IMACICWU 35.158  Support for Mainview/CICS 7.1 SMF 110 BMCMVCIC.      
  IMACINIT 35.128  Note: OPTIONS NOCAPSOUT recommended for ODS users.   
  JCLTEST9 35.116  35.04 only. //MVJEIN DD in wrong step.               
  MDIJCL   35.299  Support for Luminex MDI box to run MXG on Linux.     
  RMFINTRV 35.006  Duplicate RMFINTRV if Multiple Capacity Groups exist.
  RMFINTRV 35.282  New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.  
  SMFINTRV 35.067  New START15INT/30INT/HRINT interval Starttimes.      
  TYPE0203 35.190  SMF type 2 subtype 2 (SMF Signature enabled) STOPOVER
  TYPE0203 35.283  Support for APAR OA52828, SMF Temporary Buffer size. 
  TYPE102  35.017  New DB2 ZPARMS added to T102S106 dataset.            
  TYPE102  35.046  Support for IFCID 125 Truncated fields.              
  TYPE102  35.047  Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.
  TYPE102  35.204  Support for new IFCID 376 variables in T102S376.     
  TYPE102  35.262  New DB2 zPARMS variables created in T102S106 dataset.
  TYPE102  35.262  Support for new DB2 zPARMS added by RSU1708 and 1709.
  TYPE103  35.134  Dataset TYPE103D vars T103DBYT/T103DREQ corrected.   
  TYPE110  35.105  CICS duration fields are now formatted TIME16.6.     
  TYPE113  35.141  SMF 113 Formula for RNI updated for z13.             
  TYPE113  35.246  SMF113/HIS formula for z14 L3P/RNI/SM1132SP changed. 
  TYPE113  35.310  Support for z14 SMF type 113 (INCOMPATIBLE).         
  TYPE115  35.011  For local time zones with +GMT, GMT115TM wrong.      
  TYPE116  35.192  MQMQUEUE INTS/STRT populated in subtype 2 records.   
  TYPE116  35.219  MQMACCT variable NETSNAME new format decoded.        
  TYPE117  35.015  Support for SMF 117 GTZ record.                      
  TYPE119  35.173  Support for SMF 119 Subtype 11 Zert record.          
  TYPE119  35.220  Zero observations in TYP11920 dataset.               
  TYPE119  35.245  SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED.         
  TYPE120  35.007  Liberty SMF 120 st 12 SM120CCC/CCD Year 2027.        
  TYPE120  35.024  Subtype 9 variables SMF1209EV,FI,EW no longer kept.  
  TYPE120  35.051  Support for Liberty 17.0.0.1 SMF 120 ST 12 new data. 
  TYPE120  35.060  Enhancement adds TOTAL/CP ONLY/ZIP CPU to TYP120BL.  
  TYPE120  35.060  SMF 120 ST 11 TYP120BL CP and zIIP variables added.  
  TYPE125  35.015  Support for SMF 125 GTZ record, untested.            
  TYPE129  35.109  Variables SM1209EX/EY/EZ/FA were dropped.            
  TYPE1415 35.040A IBM APAR OA51325 corrects missing UCB segment.       
  TYPE30   35.066  APAR OA59593 adds INELIGHONOR flag to SMF 30s.       
  TYPE30   35.205  Documentation of what is counted in SMF 30 EXCPs.    
  TYPE30_6 35.127  Negative values for Early Address Spaces corrected.  
  TYPE42   35.031  Variable S42DSIOS added to TYPE42DS.                 
  TYPE42   35.137  APAR OA44319 improves accuracy for I/O durations.    
  TYPE42   35.240  Support for APARS OA52132/OA52133/OA61734 UNTESTED.  
  TYPE42   35.274  Support for APAR OA53110 new TYPE42 variables.       
  TYPE42   35.289  TYPE42 APARs OA52132, OA52133, OA61734 now tested.   
  TYPE42   35.305  Third incorrect SRLEN STOPOVER correction.           
  TYPE6156 35.207  TYPE6156 enhancement adds FIRSTGEN and LASTGEN.      
  TYPE70   35.270  Support for Container Pricing in SMF 70.             
  TYPE70   35.282  New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.  
  TYPE7002 35.153  IBM RMF CRYPTO report TOTAL EXEC is AVERAGE EXEC.    
  TYPE7072 35.064  SMT Mode corrections, "Inflated" CPUZIPTM in MT=2    
  TYPE7072 35.093  Variables PLATBUSY/PCTOFHDWQ TYPE70/RMFINTRV wrong.  
  TYPE7072 35.113  35.04 only. TYPE79 SHARE weights wrong, ASUMCELP ok. 
  TYPE7072 35.285  Support for Container Pricing, new TYPE72TR dataset. 
  TYPE71   35.009  Support for APAR OA48913 with 2GB Memory Frames      
  TYPE74   35.146  TYPE749 Corrections, vars R749FPGBYTx, R749Dxxx.     
  TYPE74   35.182  MXG 34.07 INPUT STATEMENT EXCEEDED RMF 74 SUBTYPE 8. 
  TYPE74   35.193  Alignment for sync I/O variables.                    
  TYPE74   35.273  Support for APAR OA50761 Virtual Flash memory.       
  TYPE78   35.021  TYPE78PA variables R782LSMO/GMFO/GFRR are wrong.     
  TYPE80A  35.029  RACFTYPE=6 segment increased in length, error msgs.  
  TYPE80A  35.231  RACFDIRECTED allows DELETE of RACF records DTP=44.   
  TYPE80A  35.231  RACFDIRECTED allows delete of multiple RACF records. 
  TYPE89   35.271  Support for Container Pricing in SMF 89.             
  TYPE90A  35.199  z/OS 2.3 type 9 subtype 38 INPUT STATEMENT EXCEEDED  
  TYPE92   35.180  SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED RECORD.   
  TYPE991  35.123  New z/OS 2.2 variables added to TYPE991 dataset.     
  TYPEAXWY 35.150  Support for AXWAY Version 3.1.3, incomplete.         
  TYPEBBMQ 35.034  Support for BBMQ BMC Utility BBM9MD73 restructure.   
  TYPEBBMQ 35.176  Support for BBMQ QSDSTYPE='DISTRIBUTED SYSTEM TYPE'. 
  TYPEBE97 35.152  Support for Beta 97 Subtype 22 for version 430/610.  
  TYPEBE97 35.196  Support for BETA 97 Extended 610 Header (INCOMPATIBL)
  TYPEBETA 35.139  BETA93 and BETA97 Subtype 25 restructure support.    
  TYPEBETA 35.209  Support for BETA 93 Version 610 (INCOMPATIBLE).      
  TYPEBETA 35.297  Support for BETA 93 Version 610 (update) 620 (added).
  TYPEBVIR 35.260  BVIR History updated for 3.3 media codes and BVIR302.
  TYPEBVIR 35.260  Support for new media/devices and BVIR302 correction.
  TYPECIMS 35.197  IMF variables STRTTIME/ENDTIME now in microseconds.  
  TYPEDB2  35.016  DB2STATS QISTxxxx Storage multiplied by 4K vs 1K.    
  TYPEDB2  35.030  DB2STAT4 _REAL variables way too large.              
  TYPEDB2  35.081  DB2ACCTP, truncated QPACLOCN/COLN/PKID/ASCH/AANM     
  TYPEDB2  35.111  DB2 12.1 INVALID QLAC, CONTINUOUS DELIVERY CAUSED.   
  TYPEDB2  35.229  PDB.DB2STATB/STSBP protection for large gaps in data.
  TYPEDB2  35.248  Four QWA225 and QWB225 variables now kept/input.     
  TYPEDB2  35.267  DB2 Netezza IDAA variables Q8STxxxx corrected.       
  TYPEDB2  35.277  New IFCID=225 QWA225PRISTG_PAGE variable added.      
  TYPEDB2  35.280  Exit Members EXDB2STS and _EDB2STS are now valid.    
  TYPEDCOL 35.064A Multi-Volume DCOLDSET fields retained & populated.   
  TYPEIAM  35.107  Support for IAM Version 9.0.                         
  TYPEIMS  35.058  Support for IMS LOG 67D0 DIAGNOSTIC DC Log Record.   
  TYPEMVCI 35.062  Support for Mainview CICS CMRDETL file VER 6700.     
  TYPEMVCI 35.161  Support for BMC Mainview/CICS Version 7.1.           
  TYPEMVIP 35.055  Support for Mainview for IP PTF BPN2331 adds flag.   
  TYPEMVJE 35.094  Support for BMC Mainview for Java Environment.       
  TYPENMON 35.208  Nigel's Monitor changed HH:MM to N MINS, INCOMPAT.   
  TYPEOPAV 35.163  Support for Dell/EMC Mainframe Enabler PAV Optimizer 
  TYPEOPC  35.048  Support for IWS/TWS/OPC Version 9.3 ST 66 was ST 23. 
  TYPEOPSS 35.090  Support for CA's OPSS Product User SMF Record.       
  TYPEOSEM 35.010  OSEM User SMF INPUT EXCEEDED, invalid, circumvented. 
  TYPEPOEX 35.002  INVALID SMF Records caused STOPOVER ABEND.           
  TYPEPOEX 35.242  Support for Power Exchange Version 10.1.1.           
  TYPEPOEX 35.257  Protection for truncated Power Exchange SMF record.  
  TYPEQACS 35.288  Support for QAPMDISK with LENGTH=695.                
  TYPERMFV 35.005  Dataset ZRBLCP obs created for ONLINE LCPUADDRs.     
  TYPERMFV 35.028  New RMF III ZRBENC "long names" now input and kept.  
  TYPERMFV 35.044  ZRBCP SMT vars missing, new CPC_CECNAME variable.    
  TYPERMFV 35.191  Support for z/OS 2.3 ZRBASI and ZRBUWD new fields.   
  TYPERMFV 35.235  RMF III ZRBCPU enhanced with decodes of CPC_HOMEFLAG.
  TYPERMFV 35.259  35.10: ZRBASI deaccumulation was not correct.        
  TYPERMFV 35.259  IBM 4HR MSU (CPUAVB4H) in ZRBCPU per) interval.      
  TYPERMFV 35.259  MSU Count variables added to ZRBASI/ZRBCPU/ZRPLCP.   
  TYPERMFV 35.259  New ZRBLCPLPAR dataset with per-LPAR totals.         
  TYPERMFV 35.287  MXG 35.10/35.11 RMF III ZRBASI ASICPUTA was WRONG.   
  TYPERMFV 35.300  The CPUPHYAD format could fail creation with ABEND.  
  TYPEROSC 35.177  PDB.ROSCOE, ROSIGNON Logon Time, CONNECTM, corrected.
  TYPESVIE 35.059  Support for CA SYSVIEW for IMS 14, missing values.   
  TYPETMS5 35.278  Correction for TMS Stacked Tape Files wrong values.  
  TYPETPMX 35.261  Execution time for TYPETPMX halved by restructure.   
  TYPETPMX 35.261  Execution time reduction.                            
  TYPETPX  35.035  Protection for invalid TPX subtype 7 record.         
  TYPETPX  35.155  STOPOVER when IP Port was changed from 4 to 5 digit. 
  TYPEVMXA 35.025  Using _VMINPUT. z/VM variable VMDUSER was 1 byte.    
  TYPEVMXA 35.040  Support for Velocity ZWRITE z/VM MONWRITE records.   
  TYPEVMXA 35.079  z/VM 6.3 SMT in VXSYTPRP, VXAPLSO0 corrections.      
  TYPEVMXA 35.092  Additional support for z/VM 6.4 (INCOMPAT, SYTLCK).  
  TYPEVMXA 35.093  MXG 35.03 only. PLATBUSY/PCTOF HDW TYPE70/RMFINTRV.  
  TYPEVMXA 35.131  Variable CALENMT incorrect, new CALSHARE variable.   
  TYPEVMXA 35.132  Support for zVM 6.4 APAR VM66026 new variables.      
  TYPEVMXA 35.145  zVM SMT INTERVAL vars were incorrectly DIF()'d.      
  TYPEVMXA 35.165  New variables added to VXMTRMEM dataset.             
  TYPEVMXA 35.174A MONWRITE VXBYUSR _MT1 and _PRO (SMT times) corrected.
  TYPEVMXA 35.203  z/VM 6.4.17.1 INCOMPATIBLE fields.                   
  TYPEVMXA 35.221  zVM MONWRITE VXPRCPUP dataset corrected.             
  TYPEXAM  35.063  Support for XAMSYS wrong length, XMTCPSYS NAMENODE.  
  TYPEXAM  35.074  Velocity XAM SYTCPU invalid errors at vendor.        
  TYPEXAM  35.164  New variables added to XAMSYS dataset.               
  TYPEXAM  35.195  Support for zVPS XAM XAMPUP segment.                 
  TYPEXAM  35.218  XAMSYPUP dataset variables are now correctly aligned.
  TYPEXAM  35.223  zVPS/XAM extra SYTCUP with totals is now decoded.    
  TYPEZDP  35.162  Support for Dell/EMC Mainframe Enabler zDP           
  UTILBLDP 35.143  Options SUPPRESS enhanced, NEVER corrected.          
  UTILBLDP 35.225  New EXPDBVAR/EXPDBCDE/EXPDBOUT to create subset.     
  UTILBLDP 35.306  SUPPRESS=74 variable DEVN NOT FOUND ERROR.           
  UTILBLDX 35.149  New BUILDJCL=YES uses IFASMFDP to save CPU time.     
  UTILCMPR 35.292  Utility compares numeric variables in OLD/NEW dataset
  UTILEXCL 35.004  MXG 34.34 PDB.CICSDICT not FOUND - GET NEW UTILEXCL. 
  UTILEXCL 35.023  MXG 35.01.Old Dictionary Records were not used.      
  UTILEXCL 35.228  Support for 20 user character fields in CICSTRAN.    
  UTILEXCL 35.293  &MXGCIEXC "exit" to correct USER CMODHEAD typos.     
  UTILRMFI 35.026  Enhanced reporting if SRVCVLASS=SYSOTHER detected.   
  VGETSORT 35.112  35.04 only. ERROR Truncated SORTBY (name GT 32).     
  VGETxxxx 35.309  Protection for DATASET=PDB.dataset syntax.           
  VMAC38   35.136  NETVIEW ID=38 unexpected S38CCALR length corrected.  
  VMACSMF  35.266  SMF ID=2 SYSTEM=DUMY 14 byte records protected.      
  VMXGALOC 35.033  Month begin/logic revised, MNTHKEEP zero protected   
  VMXGFIND 35.117  Multiple input PDBs were read, only one was output.  
  VMXGPRNT 35.120  WPS only, MXG 35.04 Only, Blank Label ERROR.         
  VMXGSET  35.256  Example to read "concatenated" PDBs with PROC SQL.   
  VMXGSUM  35.020  MXG 35.01. Disregard MXGWARN VMXGSUM BACKLEVEL msg.  
  VMXGSUM  35.056  Correction for KEEPMNTH= (very rarely used) option.  
                                                                        
  See member CHANGESS for all changes ever made to MXG Software, or     
  the CHANGES frames at http://www.mxg.com.                             
                                                                        
Inverse chronological list of all Changes:                              
                                                                        
NEXTCHANGE                                                              
                                                                        
====== Changes thru 35.309 are in MXG 35.36 dated Jan 13, 2018========= 
                                                                        
Change 35.309  All of these macros have both a DDNAME and a DATASET     
VGETFMT        parameter but if you specified DATASET=PDB.dataset they  
VGETLABL       would all fail since they looked for WORK.PDB.dataset.   
VGETLEN        This change looks at the code and if DDNAME is null looks
VGETVAR        at dataset and uses the first 'word' delimited by '.' of 
Jan  8, 2018   DATASET as the DDNAME and the second for the DATASET. If 
               there is no '.' then DDNAME is set to &MXGWORK.          
                                                                        
Change 35.308  SAS defect in SAS 9.4 M5 PROC SQL, only M5 on z/OS, when 
ASUMUOW        PROC SQL is executed after OPTION OBS=0 was set, caused  
Jan  6, 2018   "SQL SET NOEXEC OPTION" error message and ERRORABEND.    
               Error occurred in default ASUMUOW, but ONLY if you did   
               NOT enable IMACUOW to create observations, as then, MXG  
               sets OBS=0 prior to this failing PROC SQL (which had no  
               prior error message than the NOEXEC and which is still   
               under investigation by SAS Support:  SAS NOTE nnnnn).    
               The circumvention is to add NOERRORSTOP to this PROC SQL 
               and to the several hundred other PROC SQLs in 51 members,
               and do it now to hopefully avoid the need for a SAS fix. 
               Most of the SAS examples of PROC SQL use NOERRORSTOP and 
               no MXG written PROC SQL has ever had a syntax error, so  
               this circumvention will likely be permanent.             
                 Option ERRORSTOP is the SAS Default for batch, and it  
                 determines whether PROC SQL stops executing if it      
                 encounters an error; option NOERRORSTOP instructs PROC 
                 SQL to execute the statements and to continue checking 
                 the syntax after an error occurs.                      
                                                                        
Change 35.307  ANALDB2R fails with broken DO syntax due to Change 35.263
ANALDB2R       (MXG 35.11) which incorrectly set the count of SORTBY=   
Jan  6, 2018   arguments, resulting in an error in the data steps, if   
               option PDBOUT=PDB is used.                               
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 35.306  UTILBLDP with SUPPRESS=74 variable DEVN NOT FOUND ERROR. 
UTILBLDP       If you specified SUPPRESS=74 the sort of the TYPE74CA    
Jan  6, 2018   dataset failed with BY variable DEVN not found.          
               When UTILBLDP found RMF datasets that are needed for     
               RMFINTRV are SUPPRESSED, we chose to still create them in
               WORK so that RMFINTRV would find them and not fail.      
               But a change to SUPPRESS logic nulled MACRO _CDE74 and   
               only 16 variables were kept (those that were INPUT in the
               other _CDEnnnn macros), and the _STY74 failed.           
               This change reinstates the logic that nulls the _Sxxxx   
               macro for suppressed RMF records so sorts will not fail, 
               but if you also want RMFINTRV to be valid, but don't want
               the high volume TYPE74's processed, then you should use  
               ZEROOBS=74 so the datasets will be created but with zero 
               OBS, so RMFINTRV will be happy.                          
                                                                        
Change 35.305 -Jan 04: MXG 35.35 didn't protect LENSR=480 length, caused
VMAC42         STOPOVER if you happen to have that length/APAR.         
Jan  4, 2018  -Jan 04, IBM confirmed their incorrect values and will now
               set SRLEN=160, and note that that does NOT include the   
               SYNC segment's 80 bytes when present.                    
              -Change 35.302 in MXG 35.36 was the original change.      
              -Change 36.023 in MXG 36.01 added invalid LENSR=232.      
                                                                        
Change 35.304  New variables in TYPE71 in z/OS 2.3:                     
VMAC71           SMF71L8M ='MIN 1MB*FRAMES*IN CSTORE'                   
Jan  4, 2018     SMF71L8X ='MAX 1MB*FRAMES*IN CSTORE'                   
                 SMF71L8A ='AVG 1MB*FRAMES*IN CSTORE'                   
                 SMF71L9M ='MIN 1MB*AVAILABLE*FRAMES*IN CSTORE'         
                 SMF71L9X ='MAX 1MB*AVAILABLE*FRAMES*IN CSTORE'         
                 SMF71L9A ='AVG 1MB*AVAILABLE*FRAMES*IN CSTORE'         
                 SMF71L10M='MIN 1MB*FRAMES*IN-USE BY*MEM OBJECTS'       
                 SMF71L10X='MAX 1MB*FRAMES*IN-USE BY*MEM OBJECTS'       
                 SMF71L10A='AVG 1MB*FRAMES*IN-USE BY*MEM OBJECTS'       
                                                                        
====== Changes thru 35.303 are in MXG 35.35 dated Jan  3, 2018========= 
                                                                        
Change 35.303  One z/OS SAS 9.4 M5 site gets SQL SET NOEXEC OPTION that 
VMXGUOW        terminates the job, currently under investigation by SAS 
Jan  4, 2018   support, but adding NOERRORSTOP option to the PROC SQL   
               does circumvent the error, so it has been added to the   
               one failing PROC SQL in hopes thats the only one needed. 
               This note will be revised when more is known.            
                                                                        
Change 35.302  SMF 42 st 5/6 with OA54112 now has three SRLEN values of 
VMAC42         of 240 and 400, and 480 from OA52132/OA52133/OA61745 in  
Jan  2, 2018   Change 35.289, and all three are wrong.                  
Jan  3, 2018   The actual length of the SR segment in each record is    
Jan  4, 2018   variable, with 160 bytes if there is no SYNC segment, or 
               240 bytes when the SYNC segment is present.  All three   
               are now protected.  The error caused STOPOVER ABEND.     
              -New variable  S42SNCONC='CONCURRENT*SYNC I/O*READ+WRITE' 
               added to TYPE42SR and TYPE42DS datasets.                 
              -Jan 03: another incorrect SRLEN value of 320 protected in
               MXG 35.36.                                               
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 35.301  If in your ASUMUOW you defined _LDB2ACC as something     
VMXGUOW        other than DB2ACCT.DB2ACCT (like DB2.DB2ACCT) and the    
Dec 30, 2017   DDNAME did not exist in your LIBNAME or DD statements    
               ASUMUOW would ABEND with a LIBREF not found.  Now the    
               code looks for this condition, gives you an MXGWARN      
               message and sets _LDB2ACC to _NULL_ so that ASUMUOW      
               will run.                                                
                                                                        
Change 35.300  The CPUPHYAD format could fail to be created with error  
VMACRMFV       messages of overlapped values, when there were multiple  
Dec 31, 2017   values of CPUPHYAD (CEC Speed), as when you change the   
               number of engines for an LPAR; that error caused the     
               TYPERMFV job to ABEND USER 999.                          
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.299  Luminex now offers a small Linux appliance called an MDI 
MDIADHOC       (Mainframe Data Integration) that provides another way to
MDIJCL         move MXG jobs off of zOS and onto an ASCII platform. Jobs
MDIJCL1        are still submitted from zOS, so your scheduling system  
MDIJCL2        is still in control, but the actual processing of the SMF
MDIJCL3        data occurs on the LINUX platform, and the output PDB's  
MDIJCL4        live on storage attached to the MDI.  Reports can be sent
MDIPDB         back to zOS or routed on your network wherever the MDI   
MDIPDB1        can attach.  Each job uses 2-3 virtual tape devices, for 
MDIPDB2        the SMF input, the SASLOG, and the SASLIST.  One site had
MDIPDB3        1TB of SMF, split when SMF was dumped into three outputs,
MDIPDB4        DB2, CICS, for each of 12 LPARS, so 36 concurrent jobs   
Dec 31, 2017   processed that data in a bit less than two hours on a    
Jan  6, 2018   single MDI.                                              
                                                                        
               These sample members provide examples of JCL and code    
               to run jobs on the MDI.  The JCL is very case sensitive  
               and casing for program names must match the case as      
               stored in your USERID.SOURCLIB.  Also the names and case 
               of the LOG and LIST datasets in the LUMXPROC must match  
               the program name.                                        
                                                                        
               MDIJCL /MDIPDB  runs a basic BUILDPDB adding the 42      
                               and 6156 data to the PDB using           
                               UTILBLDP and BLDSMPDB wirh AUTOALOC      
               MDIJCL1/MDIPDB1 runs a basic BUILDPDB adding the 42      
                               and 6156 data to the PDB using           
                               UTILBLDP and BLDSMPDB wirh AUTOALOC      
                               and suppressing CICS and DB2 data        
               MDIJCL2/MDIPDB2 runs VMXGALOC with READONLY=YES          
                               (which suppresss the aging of the        
                               directories) and then runs TYPS110       
                               and CICINTRV.                            
               MDIJCL3/MDIPDB3 runs VMXGALOC with READONLY=YES          
                               (which suppresss the aging of the        
                               directries) and then runs READDB2.       
               MDIJCL4/MDIPDB4 runs VMXGALOC with READONLY=YES          
                               (which suppresss the aging of the        
                               directries) and after MDIJCL2 and        
                               MDIJCL3 have run will run ASUMUOW.       
                                                                        
               MDIADHOC        JCL for adhoc reporting allows you to    
                               write your program on z/OS and run the   
                               MDI.                                     
   Thanks to Chuck Hopf, Independent Consultant, USA.                   
   Thanks to Earl Kline, Luminex, USA                                   
   Thanks to Paul Massengill, Luminex, USA                              
   Thanks to Daniel Saunders, Luminex, USA                              
   Thanks to David Feimer, Luminex, USA                                 
                                                                        
====== Changes thru 35.298 are in this MXG 35.12 dated Dec 26, 2017=====
                                                                        
Change 35.298  While all MXG Variables are upper case, mixed case names 
VGETFMT        are allowed, so you can easily create variable names with
VGETLABL       lower case characters, but the listed macros all failed  
VGETLEN        to find those variable names. The macros are revised to  
VGETVAR        UPCASE both sides of the compare without changing the    
Dec 23, 2017   returned variable name.                                  
                                                                        
Change 35.297  Support for BETA 93 Version 610 (update) and 620 (added).
EXTYBETK      -BETA1 blank values for BETADCR corrected and new vars:   
EXTYBETL         I001PTYPE='PROTOCOL*TYPE'                              
EXTYBETM         I001IPADDR='IP*ADDRESS'                                
EXTYBETN         I001HOST  ='HOST*NAME'                                 
FORMATS          I001PORT  ='HOST*NAME'                                 
VMACBETA         I001QUEUE ='HOST*NAME'                                 
VMXGINIT         I001FFPARM='HOST*NAME'                                 
Dec 23, 2017  -Support for 620 new subtype 59 creates three datasets and
               subtype 22 record is now decoded and creates BETA22VAL:  
                 TYBETK     BETA59    SUBTYPE 59 STC START/STOP         
                 TYBETL     BETA59RFF SUBTYPE 59 SFF JOB STATS          
                 TYBETM     BETA59SFF SUBTYPE 59 SFF JOB STATS          
                 TYBETN     BETA22VAL SUBTYPE 22 VALUES                 
                                                                        
Change 35.296  A WHERE clause in PROC SQL is case sensitive, and if you 
VGETLABL       create your own variable NAMEs with low case characters, 
VGETFMT        your variable will NOT be found; only upper case variable
VGETLEN        names are found.  MXG does not create low case names, and
Dec 20, 2017   cannot detect them in the WHERE clause.  No code changed.
                                                                        
Change 35.295  Support for 164-byte DBCTL segment for CICSTRAN dataset. 
IMACICDB                                                                
Dec 20, 2017                                                            
   Thanks to Ervin Claxon, CSX Technology, USA.                         
                                                                        
====== Changes thru 35.294 are in this MXG 35.12 dated Dec 20, 2017=====
                                                                        
Change 35.294  SMF 116 records with MQMSSSID mismatched to QWHSIDMQ     
VMAC116        printed MISMATCHED message on the log for every mismatch;
Dec 19, 2017   now, only the first three are printed.                   
   Thanks to Denise Williers, Wipro, USA.                               
                                                                        
Change 35.293  &MXGCIEXC is a new "exit" for UTILEXCL wherein you can   
UTILEXCL       correct mispellings in USER CMODHEAD field that cause the
VMXGINIT       DUPLICATE CONN report (same offset has two names, usually
Dec 19, 2017   caused by a typo by the CICS SYSPROG who does the DFHCT  
               assembly of that Monitor Control Table).  This change    
               circumvents the need to reassemble.  You would use:      
                 //SYSIN DD *                                           
                  %LET MXGCIEXC=                                        
                    %QUOTE(                                             
                           IF CMODHEAD='PSB ACTV' THEN DO;              
                            PUTLOG _N_= CMODNAME= CMODHEAD=             
                                   SMFPSRVR= MCTSSDRL= MCTSSDCN=;       
                            CMODHEAD='PSB ACTI';                        
                           END;  );                                     
                  %INCLUDE SOURCLIB(UTILEXCL);                          
                   _BLDDICT  _BLDEXCL  _RPTEXCL                         
   Thanks to Denise Williers, Wipro, USA.                               
                                                                        
Change 35.292  A utility to Compare numeric variables values in OLD and 
UTILCMPR       NEW versions of the same SAS dataset, using PROC MEANS to
Dec 30, 2017   compare the value of each statistic of each variable.    
                 %UTILCMPR(IN1=OLD.ZRBASI,IN2=NEW.ZRBASI);              
                                                                        
Change 35.291  GCHART AXIS statements were made compatible with WPS     
GRAFCEC        03.03.02.00.0222553, and some code was simplified and    
GRAFLPAR       logic added to STOP if no obs in RMFINTRV and to not     
GRAFWRKX       plot eligible times if there were none.                  
GRAFWRKC       The WPS graphs are printed in different order, all for a 
Dec 15, 2017   particular metric, whereas SAS prints all for an LPAR.   
               While GRAFLPAR is supported, it is obsolete and GRAFCEC  
               should be used instead, as it has superior reports.      
              -As WPS does not support SGPLOT, GRAFWRKC plots had to be 
               duplicated using the GBARLINE and GCHART procedures and  
               INCODE= added for data selection.                        
                                                                        
Change 35.290  Clear of _HSMPLEX macro added at end so that you can     
ASUMHSM        execute ASUMHSM multiple times in a single job.          
Dec 13, 2017                                                            
                                                                        
Change 35.289  Support for TYPE42 APARs OA52132, OA52133, and OA61734,  
VMAC42         originally coded in Change 35.240, has now been revised. 
Dec 12, 2017   A Subtype 5 STOPOVER was caused by new records with the  
               SRLEN=480 but with actual SR Segment length of 160, or   
               240 if the new SYNC segment is present, but the actual   
               length of the SYNC segment is 80 bytes with APAR only    
               documenting 72.  Finally, records with SRLEN=208 and no  
               SYNC segment are written with only 160 bytes documented. 
                                                                        
Change 35.288  Support for new TYPECONF GKEYPM variable and new length  
VMACQACS       of QAPMDISK of 695 to align those records, although no   
Dec 11, 2017   new fields are input in this iteration, awaiting doc.    
   Thanks to Larry E. Hanus, DST Systems, USA.                          
                                                                        
Change 35.287 -MXG 35.10 and 35.11 RMF III ZRBASI deaccumulate was WRONG
VMACRMFV       DESIGN: should NOT replace ASICPUTA with ASICPUTA_LF, and
Dec 15, 2017   WRONG IMPLEMENTATION: insufficient QA tests, causing the 
Dec 21, 2017   value in both variables to be frequently wrong, and if   
               there were multiple CEC Speeds (CPUPHYAD values) the MSU 
               value in ZRBASICPUMSU=ZRBASI*CPU MSU*COUNT was wrong.    
              -This change restores the original ASICPUTA value and the 
               deaccumulated higher resolution value is in ASICPUTA_LF  
               so YOU can choose to use the variable of YOUR choice.    
              -This change also adds variable CPC_CECNAME to ZRBLCP and 
               ZRBLCPLPAR datasets, and creates a format for CPUPHYAD   
               lookup (by SYSPLEX SYSTEM) from ZRBCPU to pass CPUPHYAD  
               into the ZRBASI dataset for MSU calculations.            
              -Duplicate ASI records for the same task in an interval do
               exist, as when a task changes it's JOB name, and they are
               visible in RMF III reports, but the deaccumulate can be  
               a missing value as IBM has not provided a way to identify
               which was the first observation and which was the second.
               In addition, records with seconds of CPUTCBTA value and  
               microseconds for CPUTCBTA_LF have been observed, so the  
               value of using CPUTCBTA_LF needs to be examined in your  
               data.  These issues are open with RMF development, and   
               this text will be updated when more is known.            
              -Dec 21: Invalid INPUT for PHYCPUAD message had no impact 
               but was corrected; was printed when no ZRBCPU matched.   
                                                                        
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.286  MXG variable IOTMNOCA, uncaptured IO Connect Time in 30s,
BUILD005       was incorrectly calculated in BUILDPDB and SMFINTRV using
BUIL3005       SMF30AIC-IOTMTOTL instead of -IOTMDASD causing negative  
SMFINTRV       values.  But SMF30AIC is the connect time for the ASID   
Dec  6, 2017   and Dependent Enclaves, but does NOT include FICON chans 
               which could also cause negative values.                  
   Thanks to Randy Hewitt, DXC Technology, USA.                         
                                                                        
Change 35.285  Support for Container Pricing in RMF 72 records creates  
EXTY72TR       new TYPE72TR dataset for Tenant Resource Group that are  
IMAC7072       added by APAR OA52694.  TYPE72TR has the same variables  
VMAC7072       that are in TYPE72GO with new variables for TRG          
VMAC79           R723GGTI='TENANT*IDENTIFIER'                           
VMXGINIT         R723GGTN='TENANT*NAME'                                 
Dec  7, 2017     R723GGKY='TENANT*SOLUTION*ID'                          
                 R723GGTF='TENANT*RESOURCE*GROUP?'                      
               and these variables added to both TYPE72GO and TYPE72TR: 
                 R723CPA_ACTUAL ='PHYSICAL*CPU*ADJUSTMENT*FACTOR'       
                 R723CPA_SCALING='SCALING*FACTOR*FOR*R723_ACTUAL'       
              -Flag variables added to TYPE792 and TYPE795 dataset      
                 R792FLG32='R792RGRP*IS A*TRG?'                         
                 R795FLG6='R795RGRP*IS A*TRG?'                          
                                                                        
Change 35.284 -MXG 35.11 inserted statements to create ZRBCPUxxxMSU vars
VMACRMFV       incorrectly inside MACRO _EZRBCPU and _EZRBLCP definition
Dec  6, 2017   causing UNINIT variable if you had tailored EZRBCPU.     
Dec  8, 2017  -Missing values for ZRBCPUZIPMSU were corrected.  The new 
Dec  9, 2017   ZRBLCPLPAR dataset requires the CPUG3 CPCDB, and SSHG3   
               tables, or ASMRMFV Table IDs of CPU and CPC, since SSH is
               always selected.                                         
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.283  Support for APAR OA52828 which allows customization of   
VMAC0203       the size of the SMF Temporary Buffer used to hold SMF    
VMAC7          data during IPL processing.                              
VMAC23         TYPE0 dataset new variable                               
Dec  5, 2017     SMF0TBUF='SMFTBUFF*PARAMETER*SPECIFIED*MEGABYTES'      
               TYPE7 dataset new variable                               
                 SMF7TBLS='BYTES LOST*DURING SMF*INITIALIZATION';       
               TYPE23 dataset new variable                              
                 SMF23MBU='MAX BYTES*STORED IN*SMFTBUFF'                
                                                                        
Change 35.282  A new set of variables added to TYPE70 and RMFINTRV to   
VMAC7072       capture the number and usage of IIP, IFL, and ICF CPS    
VMXGRMFI       for the platform (CEC).                                  
Dec 5,2017       PLATZIPCPUS - The number of IIPs on the CEC            
                 PLATZIPBUSY - The total % busy of all the IIPs         
                 PLATIFLCPUS - The number of IFLs on the CEC            
                 PLATIFLBUSY - The total % busy of all the IFLs         
                 PLATICFCPUS - The number of ICFs on the CEC            
                 PLATICFBUSY - The total % busy of all the ICFs         
                                                                        
Change 35.281  TACI802 dataset variable FINTIME was not converted from  
VMACMVIP       GMT to LOCAL Time zone.                                  
Dec  4, 2017                                                            
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 35.280  The Exit member EXDB2STS and _EDB2STS macro are now used 
VMACDB2        to give control of the output of PDB.DB2STATS; previously
Dec  6, 2017   defined but not used.                                    
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
====== Changes thru 35.279 are in this MXG 35.11 dated Dec  1, 2017=====
                                                                        
Change 35.279  Support for Dec 2017 z14 CPU MF formula update.          
ASUM113        The EXTND158 counter was moved from L3P to L4LP.         
VMAC113       -John's updated formulas are available at                 
VMACVMXA                                                                
Nov 30, 2017                                                            
   http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000066   
                                                                        
Change 35.278  Correction for TMS Stacked Tape Files; these variables   
TYPETMS5       were not retained from the first DSNB record into the    
VMACTMS5       "CHANGED" records so they were incorrect:                
Nov 30, 2017     RFILSEQ RLRECL RBLKSIZE RRECFM RSTPNAME RFILPERC;      
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.277  Support for IFCID=225 new fields in DB2STAT4 dataset:    
VMACDB2         QWA225PRISTG_PAGE   /**DBM1*PRVT ELIG*PGSTEAL*/         
Nov 28, 2017    QWB225PRISTG_PAGE   /**DIST*PRVT ELIG*PGSTEAL*/         
Dec  6, 2017   IBM DSECT notes these fields contain:                    
                 Number of Private discarded pages eligible for Page    
                 Steal. Currently backed frames which are still charged 
                 to DB2, minus this count, is the true REAL Storage     
                 usage at this time.                                    
                 I can not find the "currently backed frames" fields and
                 have asked IBM for help; this note will be updated when
                 the correct fields are known so the usage variable can 
                 be created.                                            
               IBM DB2 Support response Nov 30:                         
                 All IFCID225 fields are described in the dataset       
                 'DSNB10.SDSNIVPD(DSNWMSGS)'. It does not look like we  
                 capture that statistic. The values are captured from   
                 RMF and are included with DB2 statistics records to    
                 assist with reporting. Anything not contained will     
                 still be available in RMF.                             
              -Dec 6: UNINIT PRISTGDPAGE and correct spell as _PAGE.    
                                                                        
                                                                        
Change 35.276  Support for CICSTRAN User field RFSEMP01/RFSDATA creates 
IMACICWX       seven variables, RFSEMP01F1-RMSEMP01F7.                  
IMACAAAA                                                                
UTILEXCL                                                                
VMAC110                                                                 
Nov 27, 2017                                                            
                                                                        
Change 35.275  Addition of TYPE70TR dataset required protection in the  
ANALRMFR       PDB=SMF part of the program to prevent  the              
Nov 26, 2017      ERROR: No dataset open to look up variables.          
               when the _STY70TR was executed without prior build.      
                                                                        
Change 35.274  Support for APAR OA53110 adds new variables:             
VMAC42          S42DSRRU='AVG RESPONSE*RANDOM*READ*CACHE'               
Nov 22, 2017    S42DSRSU='AVG SERVICE*RANDOM*READ*CACHE'                
                SMF42IFW='AVERAGE*FAST-WRITE WAITS*PER MINUTE'          
                SMF42IHR='AVERAGE*HIT*RATIO'                            
                                                                        
Change 35.273  Support for APAR OA50761 adds new R7410FLG='Y' if the    
VMAC74         resource is Virtual Flash Memory.                        
Nov 22, 2017                                                            
                                                                        
Change 35.272  Change 34.151 set SYSLAST to the value of OUTDATA so that
VMXGSUM        subsequent PROC steps would automatically find the output
Nov 22, 2017   of VMXGSUM as the last dataset created, but if you added 
               any dataset options like (KEEP or (INDEX then while the  
               dataset was correctly created, an error message was      
               generated that either told you the dataset name was      
               invalid or that it exceeded 42 bytes depending on the SAS
               version you were running. NOTE: there must be a space    
               between the dataset name and any options you choose to   
               specify.                                                 
   Thanks to Robert Gilbert, BNP Paribas Fortis, BELGIUM.               
                                                                        
Change 35.271  Support for Container Pricing in SMF 89 records creates  
EXTY89R1      New variables in TYPE89 and TYPE892:                      
EXTY89R2         SMF89COREMODECP='CPUS*ACTIVE*ON CP*CORE'               
EXTY89TI         SMF89COREMODEZAAP='CPUS*ACTIVE*ON ZAAP*CORE'           
IMAC89           SMF89COREMODEZIIP='CPUS*ACTIVE*ON ZIIP*CORE'           
VMAC89         New variables in TYPE892:                                
VMXGINIT         SMF89CURREGS  ='INSTANCES*OF CURRENT*REGISTRATIONS'    
Nov 27, 2017     SMF89TRGREGS  ='INSTANCES*OF CURRENT TRG*REGISTRATIONS'
                 SMF89DELTAREGS='INTERVAL*DELTA*CURRENT*REGISTRATIONS'  
                 SMF89DELTATRG ='INTERVAL*DELTA*TRG*REGISTRATIONS'      
               New dataset TYPE89TI 'INTERSECTION TENANT RESOURCE GROUP'
                 PRODOWNR= 'SMF89TCPO PRODUCT*OWNER'                    
                 PRODNAME= 'SMF89TCPN PRODUCT*NAME'                     
                 PRODVERS= 'SMF89TCPV PRODUCT*VERSION'                  
                 PRODQUAL= 'SMF89TCPQ PRODUCT*QUALIFIER'                
                 PRODID  = 'SMF89TCPI PRODUCT*ID'                       
                 SMF89TIPO 'INTERSECTING*PRODUCT*OWNER'                 
                 SMF89TIPN 'INTERSECTING*PRODUCT*NAME'                  
                 SMF89TIPV 'INTERSECTING*PRODUCT*VERSION'               
                 SMF89TIPQ 'INTERSECTING*PRODUCT*QUALIFIER'             
                 SMF89TIPI 'INTERSECTING*PRODUCT*ID'                    
                 SMF89_TRG 'TENANT*RESOURCE*GROUP'                      
                 SMF89TCFG 'TENANT*USAGE*ENTRY*FLAGS'                   
                 SMF89TCCT 'TENANT*PRODUCT*INTERSECT*CP TCB TIME'       
                 SMF89TCZT 'TENANT*PRODUCT*INTERSECT*ZIIP TIME'         
               New dataset TYPE89R1 'TENANT RESOURCE GROUP DATA'        
                 SMF89TIPO='INTERSECTING*PRODUCT*OWNER'                 
                 SMF89TIPN='INTERSECTING*PRODUCT*NAME'                  
                 SMF89TIPV='INTERSECTING*PRODUCT*VERSION'               
                 SMF89TIPQ='INTERSECTING*PRODUCT*QUALIFIER'             
                 SMF89TIPI='INTERSECTING*PRODUCT*ID'                    
                 SMF89_TRG='TENANT*RESOURCE*GROUP'                      
                 SMF89TCFG='TENANT*USAGE*ENTRY*FLAGS'                   
                 SMF89TCCT='TENANT*PRODUCT*INTERSECT*CP TCB TIME'       
                 SMF89TCZT='TENANT*PRODUCT*INTERSECT*ZIIP TIME'         
               New dataset TYPE89R2 'TENANT RESOURCE GROUP DATA'        
                 SMF89TIPO='INTERSECTING*PRODUCT*OWNER'                 
                 SMF89TIPN='INTERSECTING*PRODUCT*NAME'                  
                 SMF89TIPV='INTERSECTING*PRODUCT*VERSION'               
                 SMF89TIPQ='INTERSECTING*PRODUCT*QUALIFIER'             
                 SMF89TIPI='INTERSECTING*PRODUCT*ID'                    
                 SMF89_TRG='TENANT*RESOURCE*GROUP'                      
                 SMF89NRTRG'CURRENT*TRG*REGISTRATIONS'                  
                                                                        
Change 35.270  Support for Container Pricing in RMF 70 records creates  
EXTY70TR       new TYPE70TR dataset with these Tennant Resource Group   
VMAC7072       variables in APAR OA52694:                               
VMXGINIT         TRG_NAME   ='TENANT*RESOURCE*GROUP*NAME'               
Nov 22, 2017     TRG_DESC   ='TENANT*RESOURCE*GROUP*DESCRIPTION'        
                 TRG_TNTID  ='TENANT*IDENTIFIER'                        
                 TRG_TNTNAME='TENANT*NAME'                              
                 TRG_SBID   ='TENANT*SOLUTION*ID'                       
                 TRG_SUCP   ='TENANT*CP*MSU*UNITS'                      
                 TRG_SUIFA  ='TENANT*ZAAP*MSU*UNITS'                    
                 TRG_SUSUP  ='TENANT*ZIIP*MSU**UNITS'                   
                 TRG_SULAC  ='TENANT*CP 4HR*AVERAGE*MSU'                
                                                                        
Change 35.269  Support for CICS User field USERPRC1/WANLUPRC.           
IMACAAAA                                                                
IMACICWV                                                                
PRODTEST                                                                
UTILEXCL                                                                
VMAC110                                                                 
Nov 21, 2017                                                            
                                                                        
Change 35.268  SAS 9.1.3 SP4 (SAS (R) 9.1 (TS01.01M3P02022006) failed   
SAS*           with  ERROR: OBTAIN FAILED FOR FILE SMF, RC=24. because  
Nov 19, 2017   the new parm EATTR=OPT was enabled for non-VSAM datasets,
               so they can reside on EAV volumes, but that was not      
               supported until SAS 9.2                                  
   Thanks to Jeffery Kirsch, Compuware, USA.                            
                                                                        
Change 35.267 -DB2 Netezza IDAA variables Q8STDSKB and Q8STDSKU were    
VMACDB2        both wrong; Q8STDSKU was incorrectly multiplied and DSKB 
Nov 17, 2017   was missing that multiplication.                         
              -Variables Q8STINSC/UPDC/DELC/DRPC/CRTC/CMTC/RBKC/OPNC    
               WERE ALL WRONGLY SET EQUAL TO Q8STACPU.                  
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.266  SMF ID=2 SYSTEM=DUMY "SMF Signature Enabled" records that
VMACSMF        are only 14 bytes were still created after APAR OA50483  
Nov 17, 2017   was installed, causing INPUT STATEMENT EXCEEDED error, as
               MXG expected these records to contain additional data in 
               either a subtype 1 or 2 record.  Now, MXG tests for the  
               length=14 and deletes these 'DUMY' records, silently.    
               The APAR reported the exposure was only when Logstream   
               data is read, and infrequently.                          
               In IBM's unstated defense, the "subtypes are valid" bit  
               wasn't turned on, justifying the original 14 byte length,
               but MXG had keyed off that unique system name of DUMY.   
               If you see the DUMY in a hex dump, you can circumvent    
               with  MACRO STOPOVER MISSOVER %  as your first //SYSIN.  
               to prevent the ABEND until you have this VMACSMF update. 
   Thanks to Paul Volpi, UHC, USA.                                      
   Thanks to Brian D. Peterson, UHC, USA.                               
   Thanks to Donald R. Striegel, UCH, USA.                              
                                                                        
Change 35.265  MXG 35.10.  BPHITRAT always missing in DB2STATB because  
VMACDB2        line 4057 (BPHITRAT=.;) should have been deleted.  You   
Nov 14, 2017   can recalculate in your reporting using                  
                 IF QBSTGET GT 0 THEN BPHITRAT=                         
                   (QBSTGET-(QBSTRIO+QBSTSPP+QBSTDPP+QBSTLPP))/QBSTGET; 
                 ELSE BPHITRAT=.;                                       
   Thanks to Rick Southby, Insurance Australia Group, AUSTRALIA.        
                                                                        
Change 35.264  CICS interval statistics in the Dispatcher Records, CICDS
VMAC110        dataset, have the sum of DSGTDT+DSGTWT, DISP+WAIT time   
VMXGCICI       that is greater than the interval DURATM, with DSGTWT as 
Nov 14, 2017   much as 5900 seconds for a 3600 second interval (and the 
               DSGTDT in those segments are milliseconds or less); that 
               sum was used calculate STARTIME and DURATDS.  Now, DURATM
               is stored in DSGTWT and used for calculations, and then  
               DSGTWT=DURATM-DSGTDT recalculates the possible wait time.
               See Change 36.076.                                       
              -The message "ERROR: IF YOU USE CICINTRV..." when MXG     
               detected the condition (DURATM GT INTERVAL REQUESTED)    
               is change to "MXGWARN:..." as few actually use CICINTRV. 
              -This data has only been seen from ancient CICS/TS 4.2.   
   Thanks to Ed Wieszczek, Zions Bank, USA.                             
                                                                        
Change 35.263  If you didn't specify a SORTBY= parameter for the ACCOUNT
ANALDB2R       report, it could fail trying to resolve a macro variable 
Nov 10, 2017   that did not exist.                                      
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 35.262  New DB2 zPARMS added include                             
FORMATS         QWP4MUDI='MORE*UNION*DISTRIBUTION' which is decoded by  
VMAC102                  a new format                                   
Nov 22, 2017    QWPRSTACS='STATCKGSRT'                                  
                QWP4BSACP='ALTERNATE*CP'                                
                QWP4UDBSG='UTIL*DBBSG'                                  
                QWP4ULBSG='UTIL*LGBSG'                                  
                QWP4CYFR ='COPY*FAST*REPLICATION'                       
                QWP4DDLM ='DDL*MATERIAL*IMMED*PEND'                     
                QWP4CDSTL='CACHDYN*BOTH*CAPTURE*LOAD*NONE'              
                QWP4ZHYPL='ZHYPERLINK*ENABLE*DISABLE*BDATABASE'         
                                                                        
Change 35.261  Execution run time for TYPETPMX halved by restructuring  
VMACTPMX       the 700 WHEN clauses into 13 subgroups of first letter of
Nov  8, 2017   the WHEN argument text value.                            
   Thanks to Kurt Gramling, TSYS, USA.                                  
                                                                        
Change 35.260  BVIR History file updated for formats for 3.3 media codes
FORMATS        and BVIR302 fields were corrected.                       
VMACBVIR                                                                
Nov  9, 2017                                                            
   Thanks to  Spain.                                                    
                                                                        
Change 35.259 -RMF III Interval MSU variables in ZRBASI/ZRBCPU/ZRBLCP   
VMACRMFV       with these counts of Million Service Units               
Nov  8, 2017     ZRBASICPUMSU='ZRBASI*CPU MSU*COUNT'                    
Nov 12, 2017     ZRBCPUCPUMSU='ZRBCPU*CPU MSU*COUNT'                    
Nov 18, 2017     ZRBCPUZIPMSU='ZRBCPU*ZIP MSU*COUNT'                    
Nov 24, 2017     ZRBLCPCPUMSU='ZRBLCP*CPU MSU*COUNT'                    
Nov 30, 2017   where the Software MSU Coefficient CPUPHYAD is used by   
                 ZRBCPUCPUMSU=CPUPHYSI*CPUPHYAD/1000000;                
                 So, an LPAR in a CEC with CPUPHYAD=20000, with the CPU 
                 Partition Dispatch time of 15 seconds in an interval,  
                 would have an MSU Count = (15*20000)/1000000 =0.3 MSU. 
                 If the interval duration was one minute, the IBM ACT   
                 "Actual" MSU on the RMF III CPC report, a projection   
                 of this interval's value to an hourly total as if all  
                 intervals were this value, would be 60*0.3=18 MSU per  
                 hour, which is the value in this new variable:         
                 ZRBLCPCPUMSUHR='ZRBLCP*IBM ACT MSU*PROJECTED*HRLYMSU'  
              -Dataset ZRBLCP contains data on ALL LPARS in a SYSPLEX,  
               reading data from only one SYSTEM in that SYSPLEX, but it
               has an obs for each LCPUADDR in each LPAR.  This change  
               creates new ZRBLCPLPAR dataset when ZRBLCP is sorted,    
               with the LPAR totals for each LCPUPRTY engine for each   
               interval, but there is no 4HR AVG MSU variable in ZRBLCP.
               To create ZRBLCPLPAR the CPUG3, CPCDB and SSHG3 tables   
               are needed.                                              
              -The actual IBM 4HR MSU (CPUAVG4H) is in ZRBCPU dataset   
               at one minute or even 30 second intervals, but you have  
               to read the data from every system to populate ZRBCPU for
               all LPARs.                                               
              -MXG 35.10, the deaccumulation of the six ZRBASI variables
               (actually added by z/OS 2.2) was not sufficiently tested 
               and could have incorrect values in these variables:      
              ASICPUTA_LF ASITCBTA_LF ASIIOCNT_S ASITRCA_S ASITET ASITRT
               for jobs that have duplicate names with different ASID-NR
               and only if you used TYPSRMFV or _SZRBASI to sort ZRBASI.
               The new-in-35.10 MXG deaccumulation of CPU_LF fields by  
               _SZRBASI failed to include the ASID number, PERIOD, and  
               JCTJOBID to deaccumulate those six variables.            
               The ZRBASI dataset created by TYPERMFV was not in error. 
              -As documented in Change 35.249, the value in ASICPUTA is 
               is larger with 35.10 because the higher resolution CPU in
               ASICPUTA_LF is stored in ASICPUTA, with ASICPUTA_ORIG    
               keeping the original lower value.                        
              -Nov 30: LPARNAME in ZRBCPU is now always populated.      
                                                                        
Change 35.258  35.09-35.10, Macro Language error, missing double periods
ANALID         in line   ANALID: &PDBMXG..SMFRECNT DOES NOT EXIST;      
Nov  7, 2017                                                            
                                                                        
Change 35.257  Power Exchange User SMF INPUT STATEMENT EXCEEDED ERROR;  
VMACPOEX       the record should have 21 POEX segments but has only 3,  
Nov  7, 2017   and the last segment is only 90 versus 95 bytes.         
               This change will be updated when the vendor's records are
               correct.  This was from 9.6.1, but I've recently read    
               that version's records with no errors.                   
   Thanks to Tracey Davidson, USBank, USA.                              
                                                                        
Change 35.256  No code change, but a new example using PROC SQL to read 
VGETDDS        "concatenated" PDB data libraries.                       
VMXGSET         // EXEC MXGSASV9                                        
Nov  7, 2017    //PDB1 DD                                               
                //PDB2 DD                                               
                %VGETDDS(DDNAMES=PDB: );                                
                DATA MYVIEW/VIEW=MYVIEW;                                
                %VMXGSET(DATASET=MNTHJOB);                              
                PROC SQL;                                               
                SELECT YEAR(DATEPART(JINITIME)) AS MYYEAR LABEL= 'YEAR',
                MONTH(DATEPART(JINITIME)) AS MYMONTH LABEL = 'MONTH',   
                SYSTEM, JOB, TYPETASK ,                                 
                ACCOUNT1, SUM(NORMCPU) AS TOTALNORMCPU  ,               
                JOB FROM MYVIEW                                         
                WHERE JOB LIKE 'MYJOB%'                                 
                  AND MONTH(DATEPART(JINITIME)) = 09                    
                  GROUP BY JOB, SYSTEM ;                                
   Thanks to Paul W Schreiber, AT&T, USA.                               
                                                                        
====== Changes thru 35.255 are in this MXG 35.10 dated Nov  6, 2017=====
                                                                        
Change 35.255 -MXG 35.10, Change 35.240 DIVIDE BY ZERO error when the   
VMAC42         IOCCOUNT=0 in TYPE42SR, now protected, but had no impact 
Nov  6, 2017   on the TYPE42SR dataset, DCMEPCT still missing.          
Nov 14, 2017  -Subtype 5 INPUT STATEMENT EXCEEDED when 68 bytes were    
               added for the SYNC segment, but SYNC Offset was zero.    
   Thanks to Jim Horne, Lowe's Companies, Inc., USA.                    
   Thanks to Stan Adriaensen, AXA-Tech, BELGIUM.                        
                                                                        
====== Changes thru 35.254 are in this MXG 35.10 dated Nov  6, 2017=====
                                                                        
Change 35.254  Variables QW0225_ECSA_aaaa and QW0225_ESQA_aaaa were     
VMACDB2        incorrectly multiplied by 4096.                          
Nov  5, 2017                                                            
   Thanks to Rick Southby, IAG, AUSTRALIA.                              
                                                                        
Change 35.253  Some of the macro variables coming back from  PROC SQL   
PDBAUDIT       are longer than the 262 character literal length since   
Nov  5, 2017   the spaces count and could generate spurious messages    
               particularly in the QA stream.                           
                                                                        
Change 35.252  MXGWARN message variable JESNR missing value and blank   
VGETJESN       TYPETEST is suppressed for records with SUBSYS='SMS' and 
Nov  4, 2017   JCTJOBID='INIT'; variable values are unchanged as those  
               records for tasks in initiation have neither.            
               VGETJESN already suppressed warning for JCTJOBID='MSTR'. 
                                                                        
Change 35.251  Support for CICS/TS 5.4 Statistics STID=21, adds BMS 3270
EXCICASG       counters to the CICVT (VTAM) dataset, new STID=149 record
VMAC110        creates new CICASG Statistics for the AS Domain.         
VMXGINIT                                                                
Nov  3, 2017                                                            
   Thanks to Perry Lim, Union Bank, USA.                                
                                                                        
Change 35.250  Support for Thruput Manager fields JBAACT JBDEA JLIMT and
VMACTPMX       REQUIRED.                                                
Nov  4, 2017                                                            
   Thanks to Kurt Gramling, TSYS, USA.                                  
                                                                        
Change 35.249 -Support for z/OS 2.3 RMF III CPUG3 record dataset ZRBCPU 
VMACRMFV       changed CPUHOOFF offset value caused some variables to   
Nov  3, 2017   be wrong, notable the Capacity Group Name and adjacent.  
              -Variable ASICPUTA in ZRBASI dataset will be larger with  
               this change, as IBM has added new accumulated ASICPUTA_LF
               (long float) field with higher resolution, which is now  
               deaccumulated and REPLACES ASICPUTA's original value.    
               New variable ASICPUTA_ORIG contains the original value.  
               The ASICPUTA_LF was 18% larger than ASICPUTA_ORIG.       
              -These accumulated fields are also now deaccumulated:     
                 ASITET  ASITRT  ASITCBTA_LF ASIIOCNT_S ASITRCA_S       
   Thanks to Kurt Gramling, TSYS, USA.                                  
                                                                        
Change 35.248  Variables QWA225SS and QWB225SS are now kept in DB2STATS,
VMACDB2        and two new-in-DB2 V12 REAL2G variables are input/kept.  
Nov  1, 2017    QWA225SS='DBM1*31-BIT*IN-USE*SYSTEM*AGENTS'             
                QWB225SS='DIST*31-BIT*IN-USE*SYSTEM*AGENTS'             
                QWA225HVPAGESINREAL2G='DBM1*HVPAGES*IN*REAL2G'          
                QWB225HVPAGESINREAL2G='DIST*HVPAGES*IN*REAL2G'          
   Thanks to Rick Southby, IAG, AUSTRALIA.                              
                                                                        
Change 35.247  Removed a debugging statement and corrected an 'uninit'  
ANALDB2R       variable message                                         
Oct 30, 2017  -If you used INTERVAL=, BEGTIME=, or ENDTIME= and did not 
               specify a SORTBY= the default is BY QWHSSSID QWHCPLAN and
               QWHCAID, so datetime variable QWACBSC is not carried     
               forward and no accounting report was created; this could 
               also cause duplicate variables in SORTBY list if QPACPKIC
               PACKTYPE or QWHSTCK were in the tailored SORTBY list.    
                                                                        
Change 35.246 -SMF 113/HIS formulas for the z14 were updated by IBM with
ASUM113        L3P changed, which is also impacted the RNI value which  
VMAC113        uses L3P.                                                
VMACVMXA      -The z13 code set the SM1132SP Speed value to 5000 because
Oct 27, 2017   the value was wrong, but that code was removed for the   
               z14, as those records contain the expected 5208 MHz.     
              -John's updated formulas are available at                 
   http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000066   
   Thanks to John P. Burg, IBM, USA.                                    
   Thanks to Nick Varley, SYNCSORT, USA.                                
                                                                        
Change 35.245  SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED because MXG  
VMAC119        expected full 4096 length for DIRU and DORU fields; now  
Oct 27, 2017   DILEN and DOLEN length of text are used for $VARYING4096.
   Thanks to David Campbell, Sun Trust, USA.                            
                                                                        
Change 35.244  New parameters TRNDKEEP and SPINKEEP added to let you    
VMXGALOC       control how many copies of each are retained.            
Oct 27, 2017                                                            
                                                                        
Change 35.243  MOBILE WORK CSV files for CICS/TS 5.3+ were missing the  
FORMATS        CICS Product Number; format MGIBMCI needed a new entries 
Nov  1, 2017   with 70='5655-Y04' and 71='5655-Y04'.                    
               Other related formats were also updated.                 
                                                                        
   Thanks to Patrick J. Holloman, Navy Federal Credit Union, USA.       
                                                                        
Change 35.242  Support for Power Exchange Version 10.1.1.               
VMACPOEX                                                                
Oct 25, 2017                                                            
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 35.241 -Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.             
ANAL119       -Uninit variables and incorrect date corrected 12/31.     
Oct 23, 2017                                                            
Dec 31, 2017                                                            
   Thanks to Jon Whitcomb, Great Lakes Educational Loan Service, USA.   
   Thanks to Earl Kline, Luminex, USA.                                  
                                                                        
Change 35.240  Support for APARs OA52132, OA52133, and OA61734, some of 
VMAC42         which fields were listed in the z/OS 2.3 SMF Manual.     
Oct 23, 2017   CODE HAS NOT BEEN TESTED WITH NEW RECORDS.               
               See Change 35.288.                                       
                                                                        
Change 35.239  MXG 34.09. RMFINTRV fails with macro GOT70PR not resolved
VMXGRMFI       when the PDB did not contain the expected PDB.TYPE70PR.  
Oct 22, 2017                                                            
   Thanks to Tracy Davidson, USBank. USA.                               
                                                                        
Change 35.238  A typo BASEWEEJ should have been BASEWEEK - only affected
VMXGALOC       the aging off of old WEEK directories.                   
Oct 22, 2017                                                            
                                                                        
Change 35.237  Internal utility; if the LIBNAME being searched was empty
VGETSORT       a spurious message about an invalid DO loop was printed. 
Oct 20, 2017                                                            
                                                                        
Change 35.236  Duplicate SMF 70 Subtype 1 records can cause bad results 
DEDUP701       due to the Split 70s duplicates, added SMT merges and the
Oct 20, 2017   multiple datasets that create TYPE70 that prevent the use
               of the normal NODUP in the final sort to remove dupes.   
               Hash logic from ANALDUPE is executed in the IMACFILE exit
               as SMF is read, examining only SMF 70 subtype 1, deleting
               duplicates prior to their input and reporting the first  
               three DUPES on the log if any were found.                
               You enable the 70 subtype 1 duplicate removal with       
                 //SYSIN DD *                                           
                 %let macfile=%quote(%include sourclib(dedup701););     
   Thanks to MP Welch, Bank of America, USA.                            
   Thanks to Garth Bloomfield, DXC Technology, AUSTRALIA.               
   Thanks to Peter Gray, DXC Technology, AUSTRALIA.                     
                                                                        
Change 35.235  RMF III ZRBCPU is enhanced with CPC_HOMEFLAG decoded:    
VMACRMFV        CPCCAPAVAIL='CAPACITY*VALUES*AVAILABLE?'                
Oct 20, 2017    CPCVARYCPU ='VARYCPU*OPTION*SET?'                       
                CPCLPARMGT ='WLM*LPAR*MANAGEMENT*ENABLED?'              
                CPCMTMETRIC='MULTI*THREADING*METRICS*AVAILABLE?'        
                CPCABSMSU  ='ABSMSU*CAPPING*OPTION*SET?'                
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.234  BUILDPDB/BUILDPD3 exit EXPDBKEP lets you KEEP= or DROP=  
BUILD005       all variables in JOBS/STEPS/SMFINTRV/NJEPURGE/PRINT.     
BUIL3005       Macros _KDBJOBS/_KDBSTEPS/_KDB30UV/_KDBNJEP/_KDBPRIN     
EXPDBKEP       were defined but were not referenced.  You put all your  
Oct 21, 2017   definitions in EXPDBKEP in your USERID.SOURCLIB using    
                    MACRO _DBJOBS  KEEP= A B C D . . %                  
                  or                                                    
                    MACRO _DBJOBS  DROP= A B C D . . %                  
               and then you instantiate them in BUILDPDB SYSIN using    
                   %LET MACKEEP= %QUOTE( %INC SOURCLIB(EXPDBKEP); );    
                   %INCLUDE SOURCLIB(BUILDPDB);                         
   Thanks to Thomas Orlando, UBS, SWITZERLAND.                          
                                                                        
Change 35.233  Protection for truncated SMF 80 Extended Relocate segment
VMAC80A        with 12 fields expected but only 10.5 fields are in the  
Oct 19, 2017   SMF record.  MXGERROR for the first three instances.     
               Record may have been truncated by ftp processing.        
                                                                        
Change 35.232  Documentation.  The zIIP CPU time for BMC Utilities is   
TYPE30         not recorded in SMF 30 records for the JOB/ASID of the   
Oct 19, 2017   Batch Utility job, but is in the 30s for BMC's XBM       
               Started Task.  IBM Utilities do record zIIP CPU time in  
               the SMF 30 for the batch job.                            
                                                                        
Change 35.231  Macro variable RACFDIRECTED allows DELETE of RACF records
VMAC80A        using the SMF80DTP/RACFTYPE=44 relocate segment, using   
VMXGINIT       segments with the subkeyword/EV44TXT='ORIGINATED_FROM'.  
Oct 18, 2017   MXG now populates variables NODE80A USERID and DIRECTED  
Dec  7, 2017   with values of DIRECTED_BY_AT, DIRECTED_BY_ONLY_AT or    
               DIRECTED_AUTOMATICALLY.  You would use this syntax:      
                  %LET RACFDIRECTED=                                    
                     %QUOTE(  IF NODE80A IN ('NODE1','NODE2')  AND      
                              USERID IN ('USERID1','USERID2')           
                              THEN DELETE; ) ;                          
                  %INCLUDE SOURCLIB(TYPS80A);                           
              -Dec 7: NODE was changed to NODE80A to avoid a conflict if
               TYPE80A and TYPE6 were used together.  The three fields  
               are created for the test but are not kept.               
   Thanks to Kerry J. Sommers, John Deere, USA.                         
   Thanks to Joan T. Keemle, John Deere, USA.                           
   Thanks to Francois Vancoppenolle, P&V Group, BELGIUM.                
                                                                        
Change 35.230 -GRAFCEC adds graphs of CPU and zIIP hours and the 4HR MSU
GRAFCEC        Avg consumption.  GRAFCEC now creates all of the charts  
GRAFLPAR       previously produced by GRAFLPAR, plus some new ones, thus
Oct 17, 2017   GRAFLPAR obsolete.  And GRAFCEC now allows multiple input
               libnames.  Dataset ASUMCELP must exist in the first data 
               library and must have non-zero obs, or GRAFCEC will die  
               with a dataset not found error.                          
              -GRAFLPAR error if you specified PDB=PDB PDB1 and using   
               SAS/GRAPH, it failed trying to write the graphics catalog
               to two libnames. Catalog will only be written to the     
               first of the two or more libnames specified by PDB=.     
               But note GRAFLPAR is now obsolete, replaced by GRAFCEC.  
   Thanks to Daniel Mckinzie, Zions Bank, USA.                          
                                                                        
Change 35.229 -Revised logic for DB2 Statistics Datasets deaccumulation 
VMACDB2        now protects for lost/skipped intervals of input data for
Oct 23, 2017   for these datasets:                                      
                    DB2STATB DB2STSBP DB2GBPST DB2NETZA                 
                    DB2STAT5 DB2STAT0 DB2STAT1 DB2STATR.                
               Large gaps (like missing a day) with repeated values in  
               QWHSISEQ caused large DURATM which caused BEGTIME to be a
               different date.  Since DB2 SMF 100 stat records can only 
               be written at one minute intervals, MXG now detects a gap
               of more than 120 second as the start of a new interval,  
               and it is DIF()'d but not output.                        
                 However, neither BEGTIME nor ENDTIME are on the minute 
                 DURATM values of a few seconds up to 100 seconds have  
                 been observed, hence the test value of 120 seconds.    
              -DB2STATS Variables QISEDPSL QISEDPSC QISEDPSM QISEDPSF   
               were incorrectly input with DB2 V11; the test GE 32 is   
               corrected to GE 232 for their input.                     
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.228  Support for up to 20 user character fields in CICSTRAN,  
IMACICAU       USERCHAR1-USERCHAR20, increased from only nine fields.   
IMACICBU                                                                
IMACICCU                                                                
IMACICDU                                                                
IMACICEU                                                                
IMACICFU                                                                
IMACICGU                                                                
IMACICHU                                                                
IMACICIU                                                                
IMACICJU                                                                
IMACICKU                                                                
IMACICLU                                                                
UTILEXCL                                                                
VMAC110                                                                 
Oct 11, 2017                                                            
                                                                        
Change 35.227  If you specified RMFINTRV=NO many bad things could have  
UTILBLDP       happened.  First, if you did not also suppress one or    
Oct 17, 2017   more of the records used by BUILDPDB, then RMFINTRV=NO   
               was ignored because the code looking for it was inside   
               of the SUPPRESS= logic.  If you DID suppress something   
               then you could have hit a problem with a missing %       
               sign on a MACRO.                                         
              -User ABENDS are replaced by messages on the OUTFILE to   
               tell you there was an error that terminated  UTILBLDP.   
              -if you suppress type 26 without specifying J2 or J3      
               it will now generate an error                            
              -if you useradd 102 without specifying the subtype        
               it will now generate an error                            
   Thanks to Trevor Holland, ANZ, AUSTRALIA.                            
                                                                        
Change 35.226  Unused Change Number.                                    
                                                                        
Change 35.225  WARNING: VARIABLE YSTEM NEVER REFERENCED because SYSTEM  
VMACTMO2       was missing the first S.                                 
Oct 10, 2017                                                            
   Thanks to Derek Purves, FDIC, USA.                                   
                                                                        
Change 35.225 -New UTILBLDP Parameters EXPDBVAR/EXPDBCDE/EXPDBOUT added 
UTILBLDP       to enable more tailoring and specifically to make it easy
Oct  8, 2017   to create a new dataset with a subset of variables and   
               obs from an existing MXG dataset, like this example to   
               create new CICSTRIM dataset with a subset of CICSTRAN    
               variables, and output only for selected CICS APPLIDs:    
                 USE EXPDBVAR TO BUILD A SUBSET OF CICSTRAN DATA FOR    
                 REPORTING PURPOSES                                     
                                                                        
                 %UTILBLDP(OUTFILE=INSTREAM,                            
                   BUILDPDB=YES,                                        
                   OUTFILE=INSTREAM,                                    
                   EXPDBVAR=                                            
                    CICSTRIM (KEEP=APPLID TRANNAME STRTTIME ENDTIME     
                      CPUTM ELAPSTM TASKNR USER ABCODE),                
                   EXPDBOUT=                                            
                    PROC SORT DATA=CICSTRIM OUT=PDB.CICSTRIM;           
                    BY ENDTIME APPLID TRANNAME TASKNR;,                 
                   MACKEEPX=                                            
                     MACRO _ECICTRN                                     
                       IF (RTYPE= 'E3'X OR RTYPE = 'T')                 
                       AND APPLID                                       
                         IN('CICSZFN3','CICSAUD3','CICSDBS')            
                       THEN OUTPUT CICSTRIM;                            
                      OUTTPUT _WCICTRN; %                               
                 );                                                     
                                                                        
Change 35.224  The _N110 "Product Null Macro" to suppress all CICS data 
VMAC110        sets for tailoring had new datasets added which caused   
Oct  8, 2017   only one dataset listed per line; that statement now has 
               two datasets per line, half as many lines/bytes.         
                                                                        
Change 35.223  The extra zVPS/XAM SYTCUP segment with totals was not    
VMACXAM        included in the SYTNLPS count of segments, and there is  
Oct  7, 2017   no LENDATA value for each subsegment, so MXG assumed 20  
               for LENDATA and detected the extra subsegment when SEGLEN
               was NE 20*SYTNLPS, but the 35.09 correction statement    
               SYTNLPS=SYTNLPS+1 was mistyped as SYTNLPS=SYTNLPS=1; so  
               only one obs per LPAR was output in XAMSYT dataset.      
               But other MXG corrections have increased the obs count,  
               depending on past MXG Version (eg. 35.06 to 35.09).      
               There will be one obs for each LCPUADDR in each LPARNAME,
               and an extra "total" obs with LCPUADDR='60'x (doc '40'x) 
               for each Engine Type in each LPARNAME, but these "total" 
               obs all have zero values in 4303 and 4313 releases.      
               There are also a pair of original LPARNAME='Totals'      
               subsegments at the start of each SYTCUP segment that are 
               not output by MXG.                                       
   Thanks to Paul Volpi, UHC, USA.                                      
   Thanks to David A. Sadler, UHC, USA.                                 
                                                                        
Change 35.222  Unused Change Number                                     
                                                                        
Change 35.221  Many zVM VXPRCPUP dataset variables values were not      
VMACVMXA       divided by 65536, two variables needed deaccumulation.   
Oct  4, 2017   The segment SSIZE is 96 but only 72 are documented.      
   Thanks to Pat Hansen, ADP, USA.                                      
   Thanks to Mike Chaves, ADP, USA.                                     
                                                                        
Change 35.220  MXG 35.09.  Zero observations in TYP11920 dataset due to 
VMAC119        a debugging asterisk left where it shouldn't have been in
Oct  4, 2017   line 2942 of VMAC119.                                    
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 35.219  MQMACCT variable NETSNAME is created from QWHCTOKN if it 
VMAC116        is populated, or from QWHCNID in not, but the format of  
Oct  4, 2017   the raw data is different; heuristics were revised to    
               recognize two formats found in this site's data, with    
               values AAAAAAAA.BBBBBBBB if QWHCTOKN is populated or     
               values CCCCCCCC.L when QWHCTOKN is not populated.        
               NETSNAME is also kept in MQMACCT1 and MQMQUEUE but it    
               should not have been, as it is always blank for those two
               datasets. And NETSNAME is not populated in MQMACCT       
               observations from BATCH/TSO Attach.                      
   Thanks to Jim Poletti, Edward D Jones, USA.                          
   Thanks to Art Morelock, Edward D Jones, USA.                         
                                                                        
Change 35.218  XAMSYPUP dataset's INPUT is now correctly aligned once it
VMACXAM        was explained that PL/1 "3 rsrvd(4) Char(4)" is SAS +16. 
Oct  3, 2017                                                            
                                                                        
====== Changes thru 35.217 are in this MXG 35.09 dated Oct  2, 2017=====
                                                                        
Change 35.217  Cosmetic, but format $MGSMFID had undetected-by-SAS      
ANALID         unbalanced quotes that impacted SMF ID=80 descriptions in
FORMATS        the ANALID SMF Report (default is on in BUILDPDB).       
Oct  2, 2017   Also option UNIFORM was added to the SUMMARY PROC PRINTs.
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.216  New macro that lets you 'join' variables from DB2ACCT    
JOINDB2        to the corresponding DB2ACCTP observations.  Written     
Oct 2, 2017    specifically to capture QWACWLME since the DB2ACCTP      
               records do not contain the QWAC segments but will        
               copy as many variables as you like from DB2ACCT to       
               DB2ACCTP.  NOTE: QWACWLME only exists in DDF records     
               and that is by IBM's design.                             
                                                                        
====== Changes thru 35.215 are in this MXG 35.09 dated Oct  2, 2017=====
                                                                        
Change 35.215  TRENDINT defaulted to WEEK rather than the value of the  
VMXGRMFI       INTTRND macro variable as documented. Also the TRNDRMFI  
TRNDRMFI       member was updated to include the TRENDINT parameter so  
Oct 2, 2017    that you can more easily see how to modify the interval. 
   Thanks to Steve Carlson, UCOP, USA.                                  
                                                                        
Change 35.214  Modified for efficiency.  If you specify ROLLSORT=NO     
UTILROLL       it now uses PROC APPEND instead of a data step which had 
Sep 30, 2017   to read both the input (ROLLTO) and output (ROLLFROM)    
               datasets.                                                
                                                                        
Change 35.213  z/VM variable VMDUFACT in dataset PDB.VXBYUSR should not 
VMACVMXA       have been deaccumulated as it is an end of interval count
Sep 28, 2017   of frames.                                               
   Thanks to Graham Harris, RBS, ENGLAND.                               
                                                                        
Change 35.212  Support for SMF 30 User Key CSA Audit Enhancements adds  
VMAC30         new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and   
Sep 28, 2017   the TYPE30_5 datasets.  This code change has been in MXG 
Feb 28, 2018   35.09 and later, but this change text replaced previous  
               "Reserved Change" on Feb 28, 2018.  This field was added 
               by APAR OA53355, but will only be needed thru z/OS 2.3,  
               as User Key Common Storage usage support ends there.     
               This is Health Check ZOSMIGV22R3_NEXT_VSM_USERKEYCOMM.   
               These APARs required no additional code changes:         
                OA53434 Corrects ASM DSECT Lengths, no MXG impact       
                OA53289 Corrects value of SMF30HVR from zero to valid.  
                OA45767 APAR that added the extra triplet caused OA53434
                                                                        
Change 35.211  Documentation. Variables QWACWLME QWACBSC QWACESC should 
VMACDB2        not have been kept in DB2ACCTP after IBM moved the DB2   
Sep 27, 2017   Package Data (IFCID 129) to its own ID=101 Subtype=1     
               record, which does not contain a QWAC segment.           
   Thanks to Glen Bowman, Wakefern, USA.                                
                                                                        
Change 35.210  Support for z14 SMF 113 records (INCOMPAT, EXTENDED array
ASUM113        now has 128 entries).  Default LABELs are now for z14.   
VMAC113        To change the default labels for z13, you would use:     
Sep 27, 2017     //SYSIN DD *                                           
Oct  1, 2017       %LET MACKEEP=  MACRO _XLA113  _XLA113D  %  ;         
                   %INCLUDE SOURCLIB(TYPS113,ASUM113);                  
               To create correct labels with both z13 and z14 data, you 
               must create separate datasets:                           
                 //SYSIN DD *                                           
                  %INCLUDE SOURCLIB(VMACF113);                          
                  DATA PDB.ASUM1131Z13;                                 
                  LABEL _XLA113D ;                                      
                  SET PDB.ASUM1131;                                     
                  IF SM113VN2=4;                                        
                  DATA PDB.ASUM1131Z14;                                 
                  LABEL _XLA113E ;                                      
                  SET PDB.ASUM1131;                                     
                  IF SM113VN2=5;                                        
                  RUN;                                                  
               Many of the RNI and other equations were changed for z14.
              -You can use  OPTIONS OBS=99; _RPT113; RUN; to print those
               calculated variables values from PDB.ASUM1131, the data  
               set you should use, as it contains interval data. The    
               original ASUM113 data set was accumulated and obs were   
               lost in deaccumulation.                                  
   Thanks to Elie Sawaya, RBC, CANADA.                                  
                                                                        
Change 35.209 -Support for BETA 93 Version 610, altered header fields   
FORMATS        and three new variables are added to dataset BETA0:      
VMACBETA         BETAPABS='MAX*PABS'                                    
Sep 29, 2017     BETASPAG='FIRST SPLIT*OVER GT*1 PAB'                   
Nov 22, 2017     BETABMOD='PAB PAGE*BREAK*MODE'                         
              -New values added to $MGBETAT format for BETA0.           
              -Support for subtype 51 RDATA1 and RDATA2 fields and      
               all segments are read and output - previously the first  
               segment was repetitively output.                         
               See Change 36.074 for Subtype 51 update.                 
                                                                        
   Thanks to Andreas Menne, Finanz Infoirmatik, GERMANY.                
                                                                        
Change 35.208  Nigel's Monitor for AIX and LINUX changed BBBP Endtime   
VMACNMON       was always "HH:MM" text, but new "N MINS" tripped MXG    
Sep 27, 2017   variables BBBPENDING051, UPHOURS, and BBBPENDING052,     
               UPTIME.                                                  
   Thanks to Steve McCulloch, TMS/CDS Group, CANADA.                    
                                                                        
Change 35.207  Enhancement for GDG datasets to add FIRSTGEN and LASTGEN 
VMAC6156       values of GATGEN to know the range of Generation values. 
Sep 25, 2017   No change, but variables GATEXTNO GATVER GATGEN GATWRAP  
               are from each GAT segment, so they should not have been  
               kept as they contain only the value of the last cell.    
   Thanks to Satish Kodavatiganti, John Deere, USA.                     
                                                                        
Change 35.206  If you need ACCOUNTn fields for long-running STCs in your
BUILD005       PDB.SMFINTRV dataset, you had to set SPINCNT in IMACSPIN 
BUIL3005       longer than the number of days between IPLs; if you had a
VMXGINIT       smaller value, then only that number of days of the      
Sep 25, 2017   PDB.SMFINTRV would have the ACCOUNTn fields populated.   
               This change creates optional macro variable &SPINSTC to  
               enable this change and to keep that many day's SPIN30_1  
               for STCs in the SPIN library for STC accounting, and you 
               can then set a much smaller value for the spining of you 
               other jobs. Use  %LET SPINSTC=365; to keep a year's data.
                 A large SPINCNT used to be important when you had lots 
                 of held print output, since BUILDPDB waits for the     
                 PURGE (26) record to know all SMF records for the job  
                 have been created.  But now, with output typically sent
                 to a spool handler, almost all jobs PURGE right after  
                 they terminate on z/OS, so now, you can set a small    
                 SPINCNT (1 or 2) and only SPIN the jobs that were in   
                 execution when SMF was dumped, or that run for more    
                 than a full day or two.                                
   Thanks to Gennady Katsnelson, IBM Global Technology Services, USA.   
                                                                        
Change 35.205  Documentation of what is counted in SMF 30 EXCP counts,  
TYPE30         from a posting to IBM-Main:                              
Sep 25, 2017   The EXCP count fields count whatever the IOS Driver      
               decided to pass into SMF in the IFASMFEX exit that       
               accumulates the type 30 EXCP fields.                     
               For example:                                             
                -For SAM, EXCP (an IOS driver) lets SAM do the calls    
                 to IEASMFEX.                                           
                -For non-SAM use of EXCP, EXCP calls IEASMFEX with      
                 a count of 1 so for non-SAM use of EXCP, it is the     
                 count of EXCPs                                         
                -And IEWFETCH (an IOS driver which fetches load modules)
                 counts the number of SSCH for non-VIO data sets, and   
                 uses EXCP for VIO data sets. So either way, it is the  
                 number of channel programs executed.                   
   Thanks to Jim Mulder z/OS Diagnosis,Design,Development,Test IBM Corp 
                                                                        
Change 35.204  Support for DB2 APARs PI71903 and PI84045 adds these     
VMAC102        new variables to IFCID 376 T102S376 dataset:             
Sep 28, 2017      QW0376SC='SCHEMA*NAME'                                
Oct 11, 2017      QW0376PR='SPECIFIC*NAME'                              
Dec  7, 2017      QW0376INC='INCOMPAT*PARMS'                            
                  QW0376SQL='SQL*TEXT';                                 
               Dec 7: Offsets for VL/VN corrected, no data for these    
               new fields yet.                                          
   Thanks to Lori A. Masulis, FMR, USA                                  
   Thanks to Steve McKee, FMR, USA.                                     
                                                                        
Change 35.203  z/VM 6.4.17.1 INCOMPATIBLE, fields inserted in SYTCUP and
EXSYTLCX       SYTLCK, and new VXSYTLCX data set created.               
VMACVMXA      -In SYTLCK when there are no shared/exclusive lock entries
VMXGINIT       (CALNMSXE=0) there are 8 bytes inserted where that second
Sep 28, 2017   array should not have existed.                           
              -In SYTCUP, SKIP logic was not correct with new data.     
   Thanks to Dr. Wolfgang Kueller, IT Solutions, AUSTRIA                
                                                                        
Change 35.202  Typo TEN should have been TUE. Most likely not an issue  
VMXGALOC       since that section of code was only used to CLEAR any    
Sep 18, 2017   exising LIBNAMEs before allocating new ones (which in    
               any case would happen when a new LIBNAME statement was   
               issued).                                                 
   Thanks to Steve Bagshaw, Marks & Spencer, ENGLAND.                   
                                                                        
Change 35.201  Modified to limit the number of LIBNAMEs reported where  
PDBAUDIT       the path name is the same.  First looks for a PATH where 
Sep 18, 2017   the LIBNAME is PDB and deletes any other LIBNAMEs with   
               that path then sorts on PATH and LIBNAME eliminating     
               all but the first occurrence of each PATH so that there  
               are not a lot of duplicate lists.  Needed for MXG QA.    
              -A new parameter PATHLIST= added with a default value     
               of NO. Change to YES to create report of the LIBNAMES    
               by PATH. Useful if you are running with AUTOALOC=YES.    
                                                                        
Change 35.200  New BLDSMPDB parameters support writing daily, weekly,   
VMXGALOC       monthly and trend "PDB's" to different paths (drives or  
VGETALOC       directories).  All default to the BASEDIR if left blank. 
BLDSMPDB         BASEWEEK=  sets the location of weekly database        
Sep 13, 2017     BASEMONTH= sets the location of monthly database       
                 BASETREND= sets the location of TREND database         
               If you choose to use these new destinations for your     
               output of BLDSMPDB, be aware and use caution since the   
               old destination's files will NOT be aged off, nor will   
               they be allocated for monthly/weekly processing. You will
               need to copy old data from the old path to the new path. 
                                                                        
Change 35.199  z/OS 2.3 type 90 subtype 38 INPUT STATEMENT EXCEEDED due 
VMAC90A        to incorrect offset and field length in the GA SMF manual
Sep 17, 2017   for SMF90T38_UTOKENUSERID which is 16 not 8 and at offset
               112 and not 118. Subtype 38/39 datetimes are now local.  
   Thanks to Bernie Ethridge, Fiserv, USA.                              
   Thanks to Paul Naddeo, Fiserv, USA.                                  
                                                                        
Change 35.198  z/VM 6.2.11 SYTLCK "BROKEN RECORD" error because SKIP was
VMACVMXA       not calculated correctly.                                
Sep 11, 2017                                                            
   Thanks to Kare Martin Torsvik, EVRY, NORWAY.                         
                                                                        
Change 35.197  IMF CIMSTRAN dataset datetime variables all now have     
VMACCIMS       microsecond resolution; MXG had overlooked the MIJUs.    
Sep 16, 2017    ACTARRV ARRVTIME STRTTIME TRNETIME ENDTIME TRNSTCKE     
Oct 26, 2017   INPQUETM, SERVICTM and RESPNSTM are now calculated from  
               those datetimes for microsecond resolution.              
   Thanks to Randy Hewitt, DXC Technology, USA.                         
                                                                        
Change 35.196  Support for BETA 97 extended header (INCOMPATIBLE) V 610.
EXTYB97D       All variables in all datasets are now INPUT and correct. 
IMACBE97       New dataset BE979751D is created from Subtype 51 with the
VMACBE97       database field details.                                  
VMXGINIT                                                                
Sep 15, 2017                                                            
   Thanks to Andreas Menne, Finanz Infoirmatik, GERMANY.                
                                                                        
Change 35.195  Support for PRCPUP segment in zVPS XAMSYS records creates
EXXAMPUP       new dataset   DDDDDD    DATASET   DESCRIPTION            
IMACXAM                      XAMPUP    XAMSYPUP  PRCPUP DATA            
VMACXAM       -The test for invalid SYTCUP segment was revised when the 
VMXGINIT       old test incorrectly reported an invalid segment.        
Sep  15, 2017                                                           
                                                                        
Change 35.194  Unrequested log messages containing   MXGDEBUG: VMXGOPTR 
ANAL116        were printed if you %LET MXGDEBUG= to a non-blank value. 
ANALDB2R       The LENGTH(&MXGDEBUG) test was removed from VPUTMSG and  
ASUMDB2A       relocated to each calling member, with revised logic:    
ASUMDB2R        %IF %UPCASE(&MXGDEBUG) NE VMXGSUM1 %THEN %DO;           
ASUMNTIN         %VMXGOPTR(OPTNAME=NOTES,NEWVALUE=NONOTES);             
TESTTRND        %END;                                                   
TRNDNTIN       The MXGDEBUG macro variable is primarily for internal MXG
VGETALOC       testing and it exists in only a few members; the enable  
VMACDB2        values are documented in each member's test statements.  
VMXG70PR       With this correction. MXGDEBUG=VMXGSUM1 was used for MXG 
VMXGALOC       QA which exposed these overlooked corrections:           
VMXGDSN       -ASUMDB2A QXHJINT typo was observed and removed.          
VMXGOPTR      -VMXG70PR LPMSUHR was missing.                            
VMXGRMFI      -ANAL116 had a superfluous ID=ENDDT argument, removed.    
VMXGSUM       -VGETALOC/VMXGALOC protected for blank MXGDEBUG.          
VPUTMSG       -VMXGSUM many calls to VPUTMSG revised so VMXGSUM1 now    
Sep 10, 2017   is also enabled if 2/3/4 are requested.                  
              -VMACDB2 did not keep SHIFT in DB2ACCTR dataset.          
              -VMXGRMFI had spurious SMF70GMN SMF70GMU MXGDEBUGs.       
              -ASUMNTIN did not keep one variable                       
              -TESTTRND builds PDB.CICS from ASUMCICX, clearing the     
               first PDB.CICS created by ASUMCICS which had different   
               kept variables and is not the recommended CICS summary.  
              -ASUMDB2R needs KEEPALL=YES for missing variable notes.   
              -TRNDNTIN needed a variable added to KEEP list.           
   Thanks to Donald Blaszka, WiPro, USA.                                
                                                                        
Change 35.193  Alignment correction for SMF74SBR/SBW/SQR/SQW sync I/O   
VMAC74         variables, and new SMF74SQRRATE/SMF74SQWRATE sync rates. 
Aug 30, 2017                                                            
                                                                        
Change 35.192  Variables WTASINTE/WTASINTS/WTASSTRT in MQMQUEUE dataset 
VMAC116        are missing values in obs created from SMF 116 Subtype 2 
Aug 29, 2017   (continuation) records, but now INTS/STRT are populated  
               by WQTTTIME and INTE is populated by SMFTIME.            
   Thanks to Raymond J. Smith, OPTUM, USA.                              
                                                                        
Change 35.191 -Support for z/OS 2.3 ZRBASI and ZRBUWD new fields are now
VMACRMFV       validated so the bypass execution tests (-99 EQ 99) are  
Sep  5, 2017   are now removed.                                         
              -Variable GEIFLG2 is now INPUT and kept in ZRBGEI dataset.
              -Unpopulated Extended Length EDE segment overlaid original
               INPUT of variables EDEPCKG EDEPROC EDEUSER EDETRXN EDEACC
               with blank values.                                       
              -Overlooked OPD variables now INPUT and kept:             
                 OPDDCTIIP='DELTA*TCB TIME*FOR*ZIIP'                    
                 OPDCTIIP='PROCESS*SYSTEM*USER COMPUTE*ON ZIIP'         
   Thanks to Kurt Gramling, T-SYS, USA.                                 
                                                                        
Change 35.190  SMF type 2 subtype 2 (SMF Signature enabled), ERROR INPUT
VMAC0203       EXCEEDED RECORD LENGTH due to MXG INPUT mis-alignment.   
VMACSMF       -Dataset TYPE0202 now keeps those signature variables, and
Aug 28, 2017   dataset TYPE0203 reverts to the way it originally was,   
               keeping only the header variables.                       
              -BUT: the type 2 subtype 1/2 records have SYSTEM='DUMY'   
               in the SMF header!  Since that is not a real system name,
               and because it could confuse any SMF Audit or analysis,  
               MXG's handling of the _SMF header in VMACSMF now detects 
               type=2 subtype=1/2 and SYSTEM='DUMY' and changes SYSTEM  
               to the actual SYSTEM (SMF2IRSID/SMF2GRSID) name.         
   Thanks to Daniel Erikols, Svenska Handelsbanken, SWEDEN.             
                                                                        
Change 35.189  Variables QPAC_PIPE_WAIT and QPAC_PIPE_COUNT are INPUT   
VMACDB2        and kept in dataset DB2ACCTP.                            
Aug 25, 2017                                                            
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.188  If default was set to "work" rather than "WORK" the case 
VMXGDEL        mismatch caused datasets to be deleted,                  
Aug 25, 2017                                                            
                                                                        
Change 35.187  Variable SM123USERNM was not kept, spelled SM123TARURI in
VMAC123A       the KEEP= list.                                          
Aug 23, 2017                                                            
   Thanks to Patricia Hansen, ADP, USA.                                 
                                                                        
====== Changes thru 35.186 are in this MXG 35.08 dated Aug 24, 2017=====
                                                                        
Change 35.186  New variables MKFLAGA/MKRLSOPT/MKLRTIME are created and  
VMACEDGS       kept in EDGSKREC dataset; variable MKSTORE2 is no longer 
Aug 23, 2017   valid, as it now contains the time part of MKLRTIME.     
Aug 25, 2017       MKLRTIME='LAST*REFERENCE*DATETIME'                   
                   MKFLAGA ='FLAG-A'                                    
                   MKRLSOPT='RELEASE OPTIONS'                           
              -Aug 25: MKLRTIME was missing value because 2-byte field  
               before the new date value was not documented, but the    
               hex record and doc offset showed 2 bytes were inserted.  
   Thanks to Marybeth Delphia, CPA Texas, USA.                          
                                                                        
Change 35.185  Change 35.167 forced you to have a PDB libname when you  
BLDSMPDB       may not have needed one. There are 4 executions of       
Aug 22, 2017   VGETSORT within BLDSMPDB with differing needs.           
               If running with RUNWEEK=YES the LIBNAME pointed to by    
               WEEKSTRT is used                                         
               If running with RUNWEEK=WTD the LIBNAME pointed to by    
               PDB is used                                              
               If running with RUNMNTH=YES the LIBNAME pointed to by    
               WEEK1 is used                                            
               If running with RUNMNTH=MTD the LIBNAME pointed to by    
               PDB is used                                              
                                                                        
Change 35.184  Test for LIBNAME count was removed as unneeded and it    
PDBAUDIT       caused termination of the QA test job with 35 libraries, 
Aug 23, 2017   and PDB.PDBAUDIT and SPIN.SPINAUDIT datasets not created.
               The original error it was supposed to prevent was found  
               to be unrelated the LIBNAME count.                       
                                                                        
Change 35.183  Five IFCIDS create new datasets, but only T102S389 and   
EX102389       T102S477 have the IFCID-specific variables; the three    
EX102404       others identify the event, but keep only the thirty-six  
EX102413       variables from the DB2 Header and Product segments.      
EX102414          DDDDDD   DATASET   DESCRIPTION                        
EX102477          102389   T102S389   ALL INDEXES WITH FTPS             
IMAC102           102404   T102S404   AUTHORIZATION COMPATIBILITY       
VMAC102           102413   T102S413   BEGIN WAIT FOR PIPE SUSPEND       
VMXGINIT          102414   T102S414   END WAIT FOR PIPE SUSPEND         
Aug 22, 2017      102477   T102S477   ALOC/DEALOC FAST TRAVERSE BLOCK   
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 35.182  MXG 35.07. INPUT STATEMENT EXCEEDED RMF 74, Change 35.166
VMAC74         tested SMF748LL instead of SMF748CL for the INPUT of the 
Aug 17, 2017   new field, which "worked" when there were link segments, 
               but this record had only the control segment and non-zero
               R748CRTN Return Code.                                    
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 35.181  Support for four new SYTSTSCP variables added:           
VMACXAM                                                                 
Aug 16, 2017                                                            
                                                                        
Change 35.180  MXG 35.07. SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED due
VMAC92         to MXG typo of 44 vs 4 in the INPUT, but also the 16-byte
Aug 18, 2017   STCKE format SMF92T50 was not decoded correctly. IBM also
               changed the format of SMF92RVN from NUM2. to PIB2., which
               caused INVALID DATA FOR SMF92RVN error messages.         
                                                                        
Change 35.179  Utility reads SMF and writes records for wanted JOBnames.
UWRITSMF                                                                
Aug 16, 2017                                                            
                                                                        
Change 35.178  Support for APAR OA49692 which adds variables to the BCP 
VMAC98         SMF type 98 record:                                      
Aug 14, 2017                                                            
 SM98SIG_AVG_CPUBUSY_CP='AV CP PCT*CPU BUSY*HIGH MTTW*/                 
 SM98SIG_AVG_CPUBUSY_ZAAP='AV ZAAP PCT*CPU BUSY*HIGH MTTW*/             
 SM98SIG_AVG_CPUBUSYR_ZIIP='AV ZIIP PCT*CPU BUSY*HIGH MTTW*/            
 SM98SIG_AVG_FDISPSPERWAKEUP_CP='AV CP FOREIGN*DISPATCHES*HIGH MTTW*/   
 SM98SIG_AVG_FDISPSPERWAKEUP_ZAAP='AV ZAAP FOREIGN*DISPATCHS*HIGH MTTW*/
 SM98SIG_AVG_FDISPSPERWAKEUP_ZIIP='AV ZIIP FOREIGN*DISPATCHS*HIGH MTTW*/
 SM98SIG_TOP_CPU_CP='CP CPU WITH*LARGEST*MTTW VALUE*/                   
 SM98SIG_TOP_CPU_ZAAP='ZAAP CPU WITH*LARGEST*MTTW VALUE*/               
 SM98SIG_TOP_CPU_ZIIP='ZIIP CPU WITH*LARGEST*MTTW VALUE*/               
 SM98SIG_2ND_CPU_CP='CP CPU*2ND LARGEST*MTTW VALUE*/                    
 SM98SIG_2ND_CPU_ZAAP='ZAAP CPU*2ND LARGEST*MTTW VALUE*/                
 SM98SIG_2ND_CPU_ZIIP='ZIIP CPU*2ND LARGEST*MTTW VALUE*/                
 SM98SIG_TOP2_MTTW_CP_TIMETOD='AV MTTW VALUE*FOR TOP*CP CPUS*/          
 SM98SIG_TOP2_MTTW_ZAAP_TIMETOD='AV MTTW VALUE*FOR TOP*ZAAP CPUS*/      
 SM98SIG_TOP2_MTTW_ZIIP_TIMETOD='AV MTTW VALUE*FOR TOP*ZIIP CPUS*/      
 SM98AVG_FDISPSPERWAKEUP_CP='AV FOREIGN*DISPATCHES*CP CPUS*/            
 SM98AVG_FDISPSPERWAKEUP_ZAAP='AV FOREIGN*DISPATCHES*ZAAP CPUS*/        
 SM98AVG_FDISPSPERWAKEUP_ZIIP='AV FOREIGN*DISPATCHES*ZIIP CPUS*/        
                                                                        
Change 35.177  PDB.ROSCOE dataset Logon Time ROSIGNON was incorrectly   
VMACROSC       set to the ROSTIME, Roscoe ASID Step Initiate Time, also 
Aug 11, 2017   causing thee CONECTTM calculation to be incorrect.       
   Thanks to Janne Jarvinen, CGI, FINLAND.                              
                                                                        
Change 35.176  Support for new BBMQ QSDSTYPE='DISTRIBUTED*SYSTEM*TYPE'  
FORMATS        variable added (compatibly) to BBMQQUES dataset with new 
VMACBBMQ       $MGBBMQT format decoding A=AS400, W=Windows, U=Unix.     
Aug 10, 2017                                                            
                                                                        
Change 35.175  Support for these APARs required no MXG code changes:    
VMAC30          OA53289 Corrects value of SMF30HVR from zero to valid.  
Aug  9, 2017    OA53434 Corrects ASM DSECT Lengths, no MXG impact       
                OA45767 APAR that added the extra triplet caused OA53434
                                                                        
Change 35.174  The original CPITCBTM/CPISRBTM "step initiator" CPU times
BUILD005       are totals, but CPITCITM CPISRITM are the "init" time of 
BUIL3005       day, at step initiation, and CPITCTTM CPISRTTM are the   
Aug  8, 2017   "term" time of day so those CPU times can be assigned to 
               the correct time of day (ALOCTIME or TERMTIME).  All four
               are now kept in both PDB.STEPS and PDB.JOBS.             
                that separated the original CPITCBTM/CPISRBTM           
               are now correctly input and are negatively deaccumulated 
   Thanks to David E. Kibitelsky, Broadridge, USA.                      
                                                                        
Change 35.174A zVM VXBYUSR dataset variables _MT1 and _PRO (SMT times)  
VMACVMXA       are now correctly input and are negatively deaccumulated 
Aug  5, 2017   with -DIF() while many CALxxxxx accumulated variables are
               positively DIF'ed, with no clue in the doc if the accum  
               is descending or ascending, except to look at data.      
                                                                        
Change 35.173  Support for SMF 119 Subtype 11 for ZERT data creates two 
EXT11911       new datasets                                             
EXT119DN          DDDDDD   DATASET  DESCRIPTION                         
FORMATS           T11911   TYP11911 ZERT ENCRYPTION SUBTYPE             
IMAC119           T119DN   TYP119DN ZERT DISTINGUISHED NAME             
VMAC119       -There is no GMT offset in Subtype 11 records; for the    
VMXGINIT       SAEVENT 03x and 04x Termination records, SAETIME is used 
Aug  4, 2017   and for 01x and 02x Connection records, SASTIME is used  
Aug 20, 2017   with SMFTIME and fuzzy logic to reset SASTIME/SAETIME to 
Aug 30, 2017   the local time zone.                                     
              -Only records with TLS or SSH protocol have been tested   
               with data; no IP-Filter nor IPSEC records have been read.
              -Aug 30: INPUT EXCEEDED.  Line 2775 in VMAC119 should be: 
                SMF119SC_TLS_CCERT_SER_LEN &PIB.1.                      
               instead of &PIB.1. This was not in MXG 35.08.            
   Thanks to Thomas Liu, Australia New Zealand Banking Group, AUSTRALIA 
                                                                        
Change 35.172  New ThruputManager fields INCLA1 JXJOU JXSTA1 JXSTA2 are 
VMACTPMX       supported.                                               
Aug  3, 2017                                                            
   Thanks to Scott Wiig, USBank, USA.                                   
                                                                        
====== Changes thru 35.171 are in this MXG 35.07 dated Aug  2, 2017=====
                                                                        
Change 35.171  zVM SMT Equivalent Time _MT1 variables in VXBYUSR dataset
VMACVMXA       now divided by /4096 to convert value to seconds.        
Aug  2, 2017                                                            
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.170  MXG spuriously reported MISSING TYPE 70 RECORDS for VM   
VMXG70PR       LPARs on IFLs. Now both MXGCIN and VMSYSTEM are used to  
Aug  2, 2017   remove those unwanted observations.                      
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.169  The incorrectly spelled variable QPSTDTW was kept in both
VMAC115        MQMBUFER and TY115215, but the correctly spelled QPSTDWT 
Jul 31, 2017   was only valid in MQMBUFER, and was missing in TY115215. 
               Now both variables are valid in both datasets.           
   Thanks to Doris Bentrez, IBM, USA.                                   
                                                                        
                                                                        
Change 35.168  Two errors both would show up when PDB= pointed at more  
ANALDB2R       than one LIBNAME. First the VGETOBS looking for the      
Jul 28, 2017    DB2 datasets would fail looking at multiple libnames.   
               Once that was fixed ANALDB2R only used the first in the  
               list of LIBNAMES - now it will use them all.             
                                                                        
Change 35.167  BLDSMPDB uses VGETSORT to determine the contents of      
BLDSMPDB       your LIBNAMES and the sort sequences (or lack) of        
Jul 28, 2017   all of the datasets.  It inconsistently used differing   
               libnames to make that determination which could miss     
               newly added datasets or changed sort orders. It will     
               now use the BASEPDB (usually PDB) LIBNAME in all cases   
               so that it will find the most recent examples.           
              -New option added to RUNWEEK. RUNWEEK=FORCE will force    
               the running of the weekly processing.  Point FORCEDAY    
               to the last date in the week if running with AUTOALOC.   
              -If you are running on ASCII with AUTOALOC=YES we do      
               not recommend using WTD or MTD processing as it can      
               make ABEND recovery difficult if the WTD or MTD          
               processing was done prior to the ABEND.                  
               We also do NOT recommend modifying default SORTEDBY      
               value from NO to YES since a change in sort orders       
               (as unusual as it might be) could cause problems.        
                                                                        
Change 35.166  Support for z/OS 2.3 changes, many new variables, COMPAT.
EXTY9208      -Support for SMF Record Types 127-2047, with ID 0-127 and 
EXTY9250       1152-2047 reserved for IBM use, and ID 127-1151 for USER 
EXTY9251       SMF record types.  The SMF header was extended by using  
EXTY9252       never-used ID=126 record type to identify this record has
EXTY9253       the extended header.  Note that new SMF exit IEFU86 is   
EXTY9254       taken for ALL SMF records, with or without the extended  
EXTY9255       header, and existing SMF exits IEFU83/84/85 are called   
EXTY9256       ONLY for records with standard header.                   
EXTY9257      -Dataset TYPE1415 new variables:                          
EXTY9258         SMF14DEF='ENCRYPTION*FLAG*BYTE'                        
EXTY9259         SMF14DET='ENCRYPTION*TYPE'                             
IMAC92           SMF14DKL='DASD*DATA SET*KEY*LABELS'                    
VMAC1415         Fields exist only if Encryption Subtype 9 exists.      
VMAC42        -Dataset TYPE4227 new variables:                          
VMAC62           SMF42RDSC_OLD='SMF42RDSC*OLD DSCB*DATA*FIELD'          
VMAC7072         SMF42RDSC_NEW='SMF42RDSC*NEW DSCB*DATA*FIELD'          
VMAC71           SMF42RKEY_OLD='SMF42RKEY*OLD DSCB KEY*DATASET*NAME'    
VMAC92           SMF42RKEY_NEW='SMF42RKEY*NEW DSCB KEY*DATASET*NAME'    
VMACSMF          The _ETY4227 output macro was relocated correctly so it
VMXGINIT         is outside the LN2 DO group, causing observations to   
VMAC73           now be created that were not previously output.        
VMAC74           Tested.                                                
VMAC75          -Dataset TYPE62 new variables:                          
VMAC76           SMF62DEF='ENCRYPTION*FLAG*BYTE'                        
VMAC77           SMF62DET='ENCRYPTION*TYPE'                             
VMAC78           SMF62DKL='DASD*DATA SET*KEY*LABEL'                     
VMAC79        -Dataset TYPE71 new variables, APAR OA52452 added.        
VMACRMFV         SMF71RFL='SMF71RFL*FLAGS'                              
Jul 18, 2017     SMF71NNF='AVG NON-NUC*FRAMES*COMPRISING*STORAGE'       
Jul 28, 2017     SMF71LSI='AVG SYS-INIT*DEMOTIONS*LARGE*TO 4K'          
                 SMF71LRI='AVG REQ-INIT*DEMOTIONS*LARGE*TO 4K'          
                 SMF71MHW='HWM 1MB*FRAMES*USED FOR*FIXED 1MB'           
                 SMF71PIS='AVG 4KB*PAGEINS*FROM SCM'                    
                 SMF71POS='AVG 4KB*PAGEOUTS*TO SCM'                     
                 SMF71PI1='AVG 1MB*PAGEINS*FROM SCM'                    
                 SMF71PO1='AVG 1MB*PAGEINS*FROM SCM'                    
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF71DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF71DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 Tested.                                                
              -Dataset TYPE72GO new variable:                           
                 R723GMLM='MEMORY*LIMIT*SPECIFIED?'                     
                 R723GMML='MEMORY*LIMIT*GB of*resgroup'                 
                 R723CTETX='TOTAL*TRANSACTION*ELAPSED*TIME'             
                 R723CXETX='TOTAL*TRANSACTION*EXECUTION*TIME'           
                 R723CETSX='SUM*ELAPSED*TIME*SQUARED'                   
                 R723CQDTX='TOTAL*QUEUE*DELAY*TIME'                     
                 R723CADTX='TIME*BATCH JOBS*INELIGIBLE*TO RUN'          
                 R723CCVTX='TIME*BATCH JOBS*SPENT*IN JCL CVTR'          
                 R723CIQTX='TIME*BATCH JOBS*INELIGIBLE*IN JOBQ'         
                 Tested; 35.06 only kept first two variables.           
              -Dataset TYPE7204 new variable:                           
                 R724ETX='TOTAL*EXECUTION*TIME*GROUP'                   
                 R724QTX='TOTAL*QUEUE*TIME*GROUP'                       
                 R724OR7A='MEMORY*POOL*SHORTAGE'                        
                 Tested.                                                
              -Dataset TYPE73 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF73DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF73DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 Tested.                                                
              -Dataset TYPE74 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF74DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF74DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 SMF74ATD='I/O DELAYS*PAV*ALIAS*THROTTLING'             
                 Tested.                                                
              -Dataset TYPE74CA new variable:                           
                 R745XSCS='SUBCHANNEL*SET*ID'                           
                 Tested.                                                
              -Dataset TYPE748 new variable:                            
                 R748CFSC='SUBCHANNEL*SET*ID*PHYS CONFIG'               
                 R748CSCS='SUBCHANNEL*SET*ID OF*FAILING*DEVICE'         
                 Tested/Corrected Change 35.182.                        
              -Dataset TYPE75 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF75DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF75DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 SMF75SCS='SUBCHANNEL*SET*ID'                           
                 Tested.                                                
              -Dataset TYPE76 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF76DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF76DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 Tested.                                                
              -Dataset TYPE77 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF77DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF77DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 Tested.                                                
              -Dataset TYPE78 new variables:                            
                 ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'                   
                 IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'                 
                 ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'                 
                 SMF78DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'          
                 SMF78DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'          
                 No Observations to test.                               
              -TYPE78CF dataset had zero observations with VMAC78 from  
               MXG 34.06 - corrected by 34.223 (34.07), 35.021 (35.02)  
               or 35.166 (in MXG 35.07).                                
              -Dataset TYPE791 update:                                  
                 R791SRC new MP Swap Reason Memory Pool Shortage        
                 No Observations to test.                               
              -Dataset TYPE796 new variables:                           
                 R796SCS='SUBCHANNEL*SET*ID'                            
                 No Observations to test.                               
              -Dataset TYPE79B new variables:                           
                 R79BSCS='SUBCHANNEL*SET*ID'                            
                 No Observations to test.                               
              -TYPE92xxx datasets not tested, no data.                  
              -NEW dataset TYPE9208: ZFS FILE SYSTEM MIGRATED           
                 SMF92GLUGNU='LOCAL*OR*REMOTE*MOUNT?'                   
                 SMF92GSN='FILE*SYSTEM*OWNER?'                          
                 SMF92GTM='DATETIME*OF*MIGRATION'                       
                 SMF92GMO='OFFSET OF*MOUNT*PARM*SECTION'                
                 SMF92GFT='FILE*SYSTEM*TYPE*MNTENTFSTYPE'               
                 SMF92GFM='FILE*SYSTEM*MODE*MNTENTFSMODE'               
                 SMF92GDN='FILE*SYSTEM*DEVICE NUMBER*MNTENTFSDEV'       
                 SMF92GDD='DDNAME*SPECIFIED*ON MOUNT*MNTENTFSDDNAME'    
                 SMF92GTN='FILE*SYSTEM*TYPE NAME*MNTENTFSTNAME'         
                 SMF92GFN='MIGRATION*TARGET*FILE*SYSTEM*NAME'           
                 SMF92GON='MIGRATION*SOURCE*FILE*SYSTEM*NAME'           
                 SMF92GBL='FILE*SYSTEM*BLOCK*SIZE'                      
                 SMF92GST='TOTAO*SPACE*IN FILE*SYSTEM'                  
                 SMF92GSU='ALLOCATED*SPACE IN*FILE*SYSTEM'              
                 SMF92GFG='FIRST*BINARY*FLAG'                           
                 SMF92GF2='SECOND*BINARY*FLAG'                          
              -NEW dataset TYPE9250: ZFS FILE SYSTEM EVENTS             
                 SMF92FSN='FILE*SYSTEM*NAME'                            
                 SMF92VOL='VOLSER*FIRST*EXTEND'                         
                 SMF92CCHH='CCCCHH*OF FIRST*EXTEND'                     
                 SMF92EVENT='FILE*SYSTEM*NAME'                          
                 SMF92SIZ='FORMATTED*SIZE OF*FILE*SYSTEM'               
                 SMF92T50=' STKE *FILE*SYSTEM*EVENT'                    
                 SMF92CODE='FAILED*OPERATIONS*ERROR*CODE'               
                 SMF92RSN='REASON*CODE'                                 
                 SMF92OVS='PRIOR*VOLUME*SERIAL'                         
                 SMF92OCH='CCCCHH*OF PRIOR*VOLUME*SERIAL'               
                 SMF92LRT='LOGFILE*RECOVERY*TIME'                       
                 SMF92LRP='LOG*PAGES*PROCESSED'                         
                 SMF92LRR='LOG*RECORDS*PROCESSED'                       
                 SMF92LRD='LOG*BLOCKS*MODIFIED'                         
                 SMF92LRE='REDO*DATA*RECORDS*PROCESSED'                 
                 SMF92LRF='FILL*RECORDS*PROCESSED'                      
                 SMF92LRN='NEW BLOCK*SECURITY*RECORDS*PROCESSED'        
                 SMF92SYS='SYSTEM*NAME*REPORTING*EVENT'                 
              -NEW dataset TYPE9251: COUNTS/RESPONSE TIME ZFS CALLS     
                 SMF92CCT='EVENT*DATETIME'                              
                 SMF92VCC='CALLS TO*FILE SYS*OWNED LOCALLY*OR R/O'      
                 SMF82VCX='CALLS*REQUIRED*TRANSMIT*FOR LOCAL'           
                 SMF92VCR='CALLS TO*FILE SYS*OWNED*REMOTELY'            
                 SMF92VCRX='CALLS*REQUIRED*TRANSMIT*FOR REMOTE'         
                 SMF92VCT='AVG TIME*PER CALL*LOCALLY*OWNED'             
                 SMF92VCRT='AVG TIME*PER CALL*REMOTELY*OWNED'           
                 SMF92VCN='CALLS TO*FILE SYS*LOCAL OR*REMOTE'           
              -NEW dataset TYPE9252: STATISTICS FOR ZFS USER FILE CACHE 
                 SMF92UCT  =' STCKE DATETIME*WHEN*STATISTICS'           
                 SMF92UCSCH='TIMES*DIRTY DATA**SKED FOR*WRITE TO DISK'  
                 SMF92UCSET='CALLS*TO CHANGE*ATTRIBUTES*OF A FILE'      
                 SMF92UCFSY='CALLS*TO SYNC*ALL DIRTY DATA*SYNC WAIT'    
                 SMF92UCUNM='CALLS*TO PURGE*USER CACHE'                 
                 SMF92UCRD ='CALLS*TO READ*FROM FILE*IN USER CACHE'     
                 SMF92UCRDA='ASYNC*READ-AHEADS*SCHEDULED*SEQUENTIALLY'  
                 SMF92UCWR ='CALLS*TO WRITE*TO FILE*IN USER CACHE'      
                 SMF92UCGET='CALLS CACHE*TO OBTAIN ATTRIBUTES'          
                 SMF92UCFL ='CALLS CACHE*TO FLUSH*ALL DATA FOR*FILE SYS'
                 SMF92UCDEL='WRITES*OF DIRTY DATA*AVOIDED'              
                 SMF92UCRDF='READ CALL*TO FILE CACHE*FOUND*A CACHE MISS'
                 SMF92UCWRF='WRITE CALL*TO FILE CACHE*FOUND*A CACHE MISS
                 SMF92UCRIO='READ I/OS*TO DISK*USER FILE CACHE'         
                 SMF92UCWRS='NORMAL*WRITE I/OS*SKED*BY FILE CACHE'      
                 SMF92UCWRE='WRITE I/OS*SKED*ERROR FOUND'               
                 SMF92UCWRR='WRITE I/OS*SKED*RECLAIM-STEAL'             
                 SMF92UCRWR='TASK WAITS*FOR SKED READ*FROM DISK'        
                 SMF92UCWW ='TASK WAITS*FOR WRITE*FILE*PENDING I/O'     
                 SMF92UCWWF='TASK WAITS*FOR PENDING I/O*FOR FSYNC CALLS'
                 SMF92UCWWE='TASK WAITS*FOR I/O*ERROR*PROCESSING'       
                 SMF92UCWWR='TASK WAITS*FOR I/O*RECLAIM-STEAL*PROCESSING
                 SMF92UCRST='TIMES*RECLAIM-STEAL*PROCESSING*WAS INVOKED'
                 SMF92UCCS ='CACHES*SPACES*LRU QUEUES* AND PAGEPOOLS'   
                 SMF92UCPCS='PAGES*IN EACH*CACHE SPACE'                 
                 SMF92UCSS ='SIZE OF*INDIVIDUAL*FILE SEGMENT'           
                 SMF92UCPGS='SIZE OF*A PAGE*IN THE USER*FILE CACHE'     
                 SMF92UCPGT='TOTAL PAGES*IN THE USER*FILE CACHE'        
                 SMF92UCPGF='FREE PAGES*IN THE USER*FILE CACHE'         
                 SMF92UCSGC='ALLOCATED*SEGMENT*STRUCTURES*IN FILE CACHE'
                 SMF92UCDSL='LENGTH*PER-CACHE*SPACE RECORD'             
              -NEW dataset TYPE9252X:CACHE SPACE NAME SEGMENT           
                 SMF92DSNAM='NAME OF*THE CACHE SPACE'                   
                 SMF92DSAS ='SEGMENTS*ALLOCATED'                        
                 SMF92DSFR ='FREE PAGES*IN CACHE LIST'                  
              -NEW dataset TYPE9253: STATISTICS FOR ZFS METADATA CACHE  
                 SMF92MCT ='DATETIME*WHEN*STATISTICS*WRITTEN'           
                 SMF92MCB ='BUFFERS IN THE METADATA CACHE.'             
                 SMF92MCLK='SEARCH CALLS*FOR BUFFER*IN METADATA CACHE'  
                 SMF92MCHT='SEARCH CALLS*CACHE HITS'                    
                 SMF92MCWP='CALLS TO*UPDATE*METADATA CACHE*BUFFER.'     
                 SMF92MCPW='PARTIAL*BUFFERS*WRITTEN'                    
                 SMF92MCBS='BYTES IN*METADATA*CACHE BUFFER.'            
              -NEW dataset TYPE9254: STATISTICS FOR ZFS LOCKING AND SLEE
              -NEW dataset TYPE9255: GENERAL ZFS DISK IO STATISTICS     
              -NEW dataset TYPE9256: TOKEN MANAGER                      
              -NEW dataset TYPE9257: ZFS USE OF MEMORY                  
              -NEW dataset TYPE9258: TRANSMIT/RECEIVES BETWEEN ZFS MEMBE
              -NEW dataset TYPE9259: PER-FILE SYSTEM USAGE              
              -RMF III UPDATES for z/OS 2.3:                            
              -ASMRMFV  Recent versions will execute without error to   
               create RMFBSAM output, but these new variables are output
               with this VMACRMFV update:                               
              -Dataset ZRBASI new variable:                             
                ASISTAFL ASI2GMEMOBJ ASI2GPGSBKD                        
              -Dataset ZRBDVT new variables:                            
                DVTSSID ='SUBCHANNEL*SET'                               
                DVTDEVN2='DEVICE*NUMBER*DVTDEVNR'/                      
                DVTENIDX4='INDEX OF*THIS*DVTG3*ENTRY'/                  
                DVTPREVI4='INDEX OF*PREVIOUS*DVTG3*ENTRY'               
              -Dataset ZRBGEI new variables:                            
                GEIGRMO ='FIXED*MEMOBJ*BACKED IN*2GB FRAMES'            
                GEIGRPR ='2GB FRAMES*FIXED IN*CSTORE'                   
                GEIGFUSE='2GB FRAMES*USED IN*FIXED*MEMOBJ'              
                GEIGSIZ ='2GB FRAMES*CAN BE*USED 2GB MEMOBJ'            
              -Dataset ZRBUWD new variables:                            
                UWDDEVNR4=DEVICE*TABLE*DVTG3*INDEX'                     
                                                                        
Change 35.165  Variables added to VXMTRMEM dataset:                     
VMACVMXA         RSAPIN0B ='PINNED*PAGES*CLASS 0*BELOW 2G'              
Jul 28, 2017     RSAPIN0A ='PINNED*PAGES*CLASS 0*ABOVE 2G'              
Aug  2, 2017     RSAPIN1B ='PINNED*PAGES*CLASS 1*BELOW 2G'              
                 RSAPIN1A ='PINNED*PAGES*CLASS 1*ABOVE 2G'              
                 RSAPINWP ='PINNED*PAGE COUNT*CAUSES WARNING'           
                 RSAPINFP ='TOTAL*PINNED*PAGE*COUNT'                    
                 RSAIOUSD ='BYTES*IOAT*SUBPOOL'                         
                 RSAIOSIZE='SIZE (MB)*IOT*SUBPOOL'                      
                 RSAIOWRNP='WARNING*PCT*IOAT*USED'                      
                 SYSHPIOM ='MAX*CONCURNT*PG*RQSTS'                      
                 SYSHPFLG ='HYPERPAV*PAGING*FLAGS'                      
                 RSAAGEFL ='GLOBAL*AGING*LIST*FLAGS'                    
               Variables added to VXSYTRSG dataset:                     
                 RSAPIN0B ='SYS TOT*PINNED*PAGES*CL 0 LT 2G'            
                 RSAPIN0A ='SYS TOT*PINNED*PAGES*CL 0 GT 2G'            
                 RSAPIN1B ='SYS TOT*PINNED*PAGES*CL 1 LT 2G'            
                 RSAPIN1A ='SYS TOT*PINNED*PAGES*CL 1 GT 2G'            
                 RSAPINWP ='PCT PINNED*CAUSED*WARNING'                  
                 RSAPINFP ='PCT PINNED*CAUSED*FAILURE'                  
                 RSAPINWC ='TIMES*WARNING*PCT*EXCEEDED'                 
                 RSAPINFC ='TIMES*FAILURE*PCT*EXCEEDED'                 
                 RSAIOUSD ='BYTES*USED*IOAT*SUBPOOL'                    
                 RSAIOWRNP='PCT*IOAT*SUBPOOL*VS SIZE'                   
                 RSAIOWRNC='TIMES*IOAT*SUBPOOL*WARNING'                 
                 RSAIOFALS='TIMES*IOAT*SUBPOOL*NOT AVAIL'               
                 RSAIOFAIL='TIME*NOT AVAIL*IOAT AND*AVAILLIST'          
               Variables corrected in VXBYUSR dataset, all              
               were missing the divide by 4096.                         
                                                                        
   Thanks to Patricia Hansen, ADP, USA.                                 
   Thanks to Mike Chaves, ADP, USA.                                     
                                                                        
Change 35.164  Variables added to XAMSYS dataset:                       
VMACXAM          RSACKMB2G='CP FRAMES*LT 2G*FOR DUMP'                   
Jul 26, 2017     RSACKMA2G='CP FRAMES*GT 2G*FOR DUMP'                   
                 RSAPIN0B ='PINNED*PAGES*CLASS 0*BELOW 2G'              
                 RSAPIN0A ='PINNED*PAGES*CLASS 0*ABOVE 2G'              
                 RSAPIN1B ='PINNED*PAGES*CLASS 1*BELOW 2G'              
                 RSAPIN1A ='PINNED*PAGES*CLASS 1*ABOVE 2G'              
                 RSAPINWP ='PINNED*PAGE COUNT*CAUSES WARNING'           
                 RSAPINFP ='TOTAL*PINNED*PAGE*COUNT'                    
                 RSAIOUSD ='BYTES*IOAT*SUBPOOL'                         
                 RSAIOSIZE='SIZE (MB)*IOT*SUBPOOL'                      
                 RSAIOWRNP='WARNING*PCT*IOAT*USED'                      
                 SYSHPIOM ='MAX*CONCURNT*PG*RQSTS'                      
                 SYSHPFLG ='HYPERPAV*PAGING*FLAGS'                      
                 RSAAGEFL ='GLOBAL*AGING*LIST*FLAGS'                    
   Thanks to Patricia Hansen, ADP, USA.                                 
   Thanks to Mike Chaves, ADP, USA.                                     
                                                                        
Change 35.163  Support for Dell EMC Mainframe Enablers for z/OS V8.2 for
EXPAVO01       their z Systems PAV Optimizer, PAVO product's user SMF   
EXPAVE01       record creates two new datasets:                         
IMACPAVO          DDDDDD    DATASET    DESCRIPTION                      
TYPEPAVO          TYPAVO    TYPEPAVO   PAVO OPTIMIZER DATA              
TYPSPAVO          TYPAVE    TYPEPAVE   PAVO EVENT                       
VMACPAVO                                                                
VMXGINIT       This support is incomplete and in active development;    
Aug 25, 2017   please contact SUPPORT@MXG.COM for current status.       
                                                                        
Change 35.162  Support for Dell EMC Mainframe Enablers for z/OS V8.2 for
EXZDPVDG       their z Systems Data Protector, zDP product's user SMF   
IMACZDP        record creates new TYPEZDP dataset:                      
TYPEZDP          DDDDDD    DATASET    DESCRIPTION                       
TYPSZDP          ZDPVDG    TYPEZDP    ZDP DATA                          
VMACZDP                                                                 
VMXGINIT                                                                
Jul 24, 2017                                                            
                                                                        
Change 35.161  Support for BMC Mainview/CICS Version 7.1 (CICS/TS 5.4)  
FORMATS        adds many new fields and updated formats.                
VMACMVCI                                                                
Jul 23, 2017                                                            
                                                                        
Change 35.160  Support for AXWAY Version 3.1.3; the documentation does  
VMACAXWY       not match the actual data records and some fields are not
Jul 21, 2017   input, pending feedback from the vendor.                 
   Thanks to Michael Reines, Decadis, GERMANY.                          
                                                                        
Change 35.159  VGETSORT now adds formats to the output for the sorted by
VGETSORT       variables for each dataset.  For each found member, there
Jul 28, 2017   will be a MACRO variable FMTx corresponding to the SRTx  
               variable that will contain the formats of the variables  
               in the SORTEDBY list. Where there is no specified format 
               CHAR is substituted.                                     
                                                                        
Change 35.158  Support for Mainview/CICS Optional SMF 110 BMCMVCIC field
IMACICWU       in dataset CICSTRAN.                                     
UTILEXCL                                                                
VMAC110                                                                 
Jul 18, 2017                                                            
                                                                        
Change 35.157  MXG 35.01-35.06.  Variable DB2TCBTM was removed from the 
VMXGUOW        CPUUOWTM value in PDB.ASUMUOW back in Change 32.014, but 
Jul 18, 2017   was put back in the equation in 35.01, in error, so it   
               is again removed from the equation, per text of 32.104.  
   Thanks to Rick Southby, Insurance Australia Group, AUSTRALIA         
                                                                        
Change 35.156  ERROR: VARIABLE DTOKEN/IMSRECCH NOT FOUND because they   
VMACIMS        were in the BY list for the IMS06 dataset sort but were  
Jul 16, 2017   not kept; now they are kept in IMS06.                    
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 35.155  TPX STOPOVER because the change in length of IP Port from
VMACTPX        4 to 5 digits was not fully protected.  Variable         
Jul 16, 2017   TPXIPPRT in datasets TPXTRMON/TPXTRMOF and variable      
               TPXIPADR in dataset TPXAPLOF values are now correct.     
               CA's record length change was in Feb, 2016, RO85818.     
   Thanks to Paul Naddeo, FISERV, USA.                                  
                                                                        
Change 35.154 -MXG 35.06 only, STOPOVER abend during TYPERMFV execution 
ASMRMFV        processing RMF III with option UWD (Use/Wait table) after
Jul 11, 2017   Change 35.148. Message RMFV006I may show incorrect RMF   
Jul 21, 2017   Monitor III table selections, but processing of the      
               actual selected tables still occurred. Message RMFV006I  
               could show NOZEROCPU when the default ZEROCPU setting was
               in effect for the ASI table.  Only ASMRMFV was changed.  
              -With this change if the NOSVP table option is in effect  
               then the RCD option will be forced to NORCD.             
              -Invalid RMFV012I and/or RMFV013I Sample RANGE and        
               SELECTED messages when RMF III data originates from a    
               time zone with time stamps later than the current TOD in 
               the time zone where ASMRMFV is executing.                
    Thanks to Betty Wong, Bank of America, USA                          
    Thanks to Roger Lowe, Northern Territory Government, AUSTRALIA.     
                                                                        
Change 35.153  The IBM RMF CRYPTO report shows a TOTAL EXEC TIME with a 
VMAC7072       value of 0.120 but that is actually the AVERAGE EXEC TIME
Jul  7, 2017   per call, and the unstated units are milliseconds, so the
               actual average value was 120 microseconds. In TYPE7002   
               dataset, the actual average value was 120 microseconds.  
               MXG Variable CRYCTE is the calculated average value,     
               0.000120 seconds, which is 120 microseconds. When printed
               with TIMW13.3 format, only three decimals were displayed 
               (0:00:00.000), so crypto duration variables are now      
               formatted TIME14.6 to display as 0:00:00.000120 to show  
               microseconds.                                            
   Thanks to Martha A. Knapik, Progressive, USA.                        
   Thanks to Douglas Wells, Progressive, USA.                           
                                                                        
Change 35.152  Support for BETA 97 Subtype 22 record for both version   
EXTYB97Q       430 and 610, although only 430 records have been read.   
EXTYB97R       New dataset BETA9722REL is created with the relocate     
FORMATS        segments for Subtype 22 records.                         
VMACBE97                                                                
VMXGINIT                                                                
Jul  9, 2017                                                            
                                                                        
====== Changes thru 35.151 are in this MXG 35.06 dated Jun 30, 2017=====
                                                                        
Change 35.151  BMC CMF TYPE74 subtype 8 records requires BMC PTF BQM1335
TYPE74         after IBM SuperPav support is installed, even if you are 
Jun 28, 2017   NOT using SuperPAVs. After IBMSuperPAV PTFs, the ESS Rank
               data are incorrect.  No code was changed in MXG.         
   Thanks to Jerry Ellis, Liberty Mutual, USA.                          
                                                                        
Change 35.150  Option %LET CECONLY=YES; creates PDB.ASUMCEC keeping only
VMXG70PR       the 68 CEC-Level variables, dropping 2794 LPAR-specific  
Jun 28, 2017   variables (generally useless, with unique variable names 
               for 60 LPARs) and creates PDB.ASUMCELP (no changes, but  
               with one observation per LPAR, it is THE dataset to use  
               to report LPAR data, with ONE set of variable names.)    
               NOTE: ALL LPARS in the CEC are summed into ASUMCEC.      
                     Only the first 60 have sets of kept unique names.  
               The ASUM70PR/ASUM70LP and ASUM70GC/ASUM70GL datasets are 
               not created when  %LET CECONLY=YES; is placed in your    
               //SYSIN prior to the INCLUDE of ASUM70PR.                
                                                                        
Change 35.149  New BUILDJCL=YES option creates JCL for two step job with
UTILBLDP       PGM=IFASMFDP control statements to select ONLY the SMF   
Jun 30, 2017   records needed for your UTILBLDP selections.             
                                                                        
Sep 30, 2017   On Sep 30, UTILBLDX from this change became UTILBLDP as  
               had been planned in the original text of this change,    
               and UTILBLDX was removed from MXG 35.09.                 
                                                                        
              -comparison of CPU savings:                               
               Using IFASMFDP to select SMF records can save CPU time,  
               especially for Ad Hoc jobs that select a relatively small
               number of SMF records.  Tests with a 15 GigaByte SMF file
               with 25 million records was used, but only 1.4 Million of
               those records (1 GB) were actually decoded and output.   
               But they had to be read and that costs CPU time:         
                                                            MM:SS       
                 READ ALL RECORDS                           14:56       
                 USE MXG MACFILE EXIT TO SKIP UNWANTED      12:43       
                                                                        
                 IFASMFDP READ ALL SELECT/WANTED             0:10       
                 READ SELECTED/WANTED                        2:25       
                                                                        
                -Using MACFILE, _SMF decodes the full header and then   
                 deletes unwanted. Decoding DATETIME variables is the   
                 most expensive INFORMAT so I inserted an exit to skip  
                 the unwanted immediately after the ID was input and    
                 prior to any DATETIME field, but the savings were much 
                 less than hoped for and much less than using IFASMFDP. 
                                                                MM:SS   
                  READ ALL with _SMF THEN DELETE UNWANTED        6:29   
                  READ ALL, DELETE AFTER ID READ                 4:45   
                                                                        
                -BUILDJCL for extreme cases provides extreme results:   
                 Selecting 194 SMF 115 records in a file of 300 million 
                 records (1 MB from 137 GB) dropped the CPU time from   
                 25 min to only 46 seconds, elapsed from 28 to 13 min.  
                                                                        
Change 35.148  RMF III CPUTM in datasets ZRBRCDS and ZRBRCDR is wrong if
ASMRMFV        ASMRMFV selected RCD records but didn't select SVP table.
ADOCRMFV       Creation of CPUTCBTM/CPUSRBTM from Service Units requires
VMACRMFV       the SVPCPU and SVPSRB coefficients.  ASMRMFV now selects 
Jun 27, 2017   SVP records when RCD is selected. Additionally, variable 
               CPUTM is set missing if there are no SVP data.           
               SO YOU MUST HAVE BOTH RCD AND SVP TABLES IN ASMRMFV.     
              -However, if the SVP table is selected, then the RCD table
               is NOT forced. The SVP table is now also moved to the    
               BASIC option table selection group from the MOST option  
               table selection group because the RCD was always part of 
               the BASIC option table group.                            
              -Minor performance improvement to UWD table processing    
               logic.                                                   
              -Several documentation Sections are updated to support the
               above changes:                                           
               Section  0 "Contents"                                    
               Section  4 "RMF III Table Selection Parameters"          
               Section 13 "Filtered Records"                            
               Section 26 "ASMRMFV and MXG PDB Data                     
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.147  Support for new segments create two new datasets:        
EXVSIDSK         DDDDDD    DATASET    DESCRIPTION                       
EXXAMPRC         VSIDSK    XMVSIDSK   VSIDISK Data                      
IMACXAM          XAMPRC    XAMSYPRC   LIMPOOL Data                      
VMACXAM                                                                 
VMXGINIT                                                                
Jun 28, 2017                                                            
   Thanks to Patricia Hansen, ADP, USA.                                 
   Thanks to Mike Chaves, ADP, USA.                                     
                                                                        
Change 35.146 -TYPE749 vars R749FPGBYTR and R749FPGBYTS were incorrectly
VMAC74         multiplied by 256; the two input variables had already   
Jun 23, 2017   been converted to bytes.                                 
              -TYPE749 variables decoded from SMF74DO offset were wrong;
               the +17 added to SMF74DO should have been +16.           
                  R749DMAR R749DMAW R749DFMT R749DBYR R749DBYT          
                  R749DFMT R749DPKR R749DPKT R749DWUP R749DWUM          
                  R749DFMT R749DBYX R749DFMT                            
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.145  Some zVM VXSYTPRP new SMT variables were incorrectly     
FORMATS        tested for error conditions with GT 8000000Nx values     
VMACVMXA       that no longer existed after their INPUT, causing large  
Jun 25, 2017   values in occasional observations.  They are now INPUT   
               with IB4 or IB4.3 INFORMATS so the first-bit-value causes
               a negative value, and the error tests are now LT 0 to    
               detect and delete them.  The MGVXAER format was revised  
               decode the negative values to print the error messages on
               the SAS log (for the first 3 of each error type).        
              -Some INTERVAL variables were incorrectly deaccumulated   
               that also caused occasional large values.                
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.144  These error messages, introduced in Change 35.050:       
ASUM70PR     MXGERROR:DATASETS ASUMCEC ASUMCELP ARE NOT VALID.  YOU ARE 
VMXG70PR     MXGERROR:MISSING TYPE 70 RECORDS FOR ONE OR MORE SYSTEMS.  
Jun 23, 2017 MXGERROR:SMF70LAC VALUES FOR THOSE SYSTEMS/CECS ARE INVALID
             MXGERROR:SEE CHANGE 35.144 TO CORRECT.                     
               impact the important ASUMCEC and ASUMCELP CEC-level data.
                  Datasets ASUM70PR and ASUM70LP are impacted, but they 
                  are SYSTEM-Level and are NOT recommended for analysis.
               The messages will result if you did NOT process type 70  
               records from ALL OF YOUR z/OS SYSTEMS in the CEC; for    
               that case, you need to read all 70 SMF records.          
               They can also result if your z/OS configuration uses z/OS
               SYSTEM names that are set in your SYS1.PARMLIB's IEASYSxx
               and are NOT the same as the SMF SYSTEM ID: for example,  
               if you set SYSTEM names in IEASYSxx to the LPARNAME.     
              -This change creates a new INCODE70 argument that can be  
               set externally by macro variable &INCODE70FORPR, so you  
               can change those SYSTEM name to LPARNAME.  Note, this is 
               only done internally in ASUM70PR code; there is no SYSTEM
               variable in ASUMCEC/ASUMCELP.  To use INCODE70FORPR, you 
               first need run this program and look at the output of    
                  PROC FREQ DATA=PDB.TYPE70PR;                          
                  TABLES LPARNAME*SMF70STN/NOROW NOCOL NOCUM NOPERCENT; 
               to verify that LPARNAME equals SMF70STN for ALL systems. 
               IF THAT IS TRUE, then you need to use either INCODE70= in
               your tailored ASUM70PR member (in your USERID.SOURCLIB), 
               or set the value prior to your ASUM70PR include, using:  
                 %LET INCODE70FOR70PR=%QUOTE(                           
                     IF SYSTEM NE LPARNAME THEN SYSTEM=LPARNAME;        
                 );                                                     
              -Newly added, once you have verified the preceding is TRUE
               you can let MXG do the heavy lifting and specify:        
                 %LET INCODE70FOR70PR=ENABLEAUTO;                       
               and MXG will generate the needed code to correct.        
               Don't hesitate to contact support@mxg.com for help.      
               See Change 36.027 for an example when LPARNAME is not    
               equal to SMF70STN.                                       
                                                                        
Change 35.143 -The UTIILBLDP option SUPPRESS is enhanced to recognize   
UTILBLDP       CICS to be the same as 110.                              
Jun 21, 2017  -If you specified SORTOUT=NEVER (not really recommended,  
               intended only for internal testing) it didn't work right:
               only the datasets where sort IS required were NOT sorted,
               (i.e. DIF() required for deaccumulate members) and  all  
               other datasets WERE sorted.  Now, NEVER sorts NOTHING,   
               and SORTOUT=NO option now sorts ONLY those members that  
               must be sorted for DIF().                                
                                                                        
Change 35.142  Format MG080QU has been updated with new z/OS 2.2 values 
FORMATS        for decoding variable RACFQUAL='EVENT*CODE*QUALIFIER'    
Jun 16, 2017                                                            
   Thanks to Lindsay Oxenham, Australia Defence Department, AUSTRALIA.  
                                                                        
Change 35.141  John Burg's 2017 formula for RNI for the z13 was changed 
ASUM113        from the 2.6 factor introduced in Change 33.033 in 2015  
VMAC113        to the new value of 2.3.  John's paper can be found at:  
VMACVMXA           http://www-03.ibm.com/support/                       
Jun 15, 2017            /techdocs/atsmastr.nsf/WebIndex/TC000066        
   Thanks to David Cogar, WellsFargo, USA.                              
                                                                        
Change 35.140  Support for short sub-sub-type ZPRTR1PL=188.             
VMACZPRO                                                                
Jun 15, 2017                                                            
                                                                        
Change 35.139 -Support for restructured BETA93 Subtype 25 (VMACBETA)    
VMACBETA       and for restructured BETA97 Subtype 25 (VMACBE97) which  
VMACBE97       adds new BE97DTKN DTOKEN variable.                       
Jun 21, 2017  -Variable BETALEXT has length $16 in VMACBETA subtypes    
Jun 26, 2017   21 and 25, but the first INPUT for subtype 0 and other   
               earlier subtype are length $12, so the kept length was   
               only 12.  Now, LENGTH BETALEXT $16 is set so the kept    
               variable length is the maximum 16 bytes.                 
   Thanks to Thomas Wigger, Finanz Informatik, GERMANY.                 
   Thanks to Dieter Haak, Finanz Informatik, GERMANY.                   
   Thanks to Robert Gilbert, BNP Paribas Fortis, BELGIUM.               
                                                                        
Change 35.138  TPX corrections to TPXIPPRT and TPXTRMON dataset.        
VMACTPX        The '07'x records are only LENGTH=101, so the TPXAPLON   
Jun  9, 2017   data set is still missing TPXIPADR and TPXIPPRT fields.  
   Thanks to Scott Wiig, USBank, USA.                                   
                                                                        
Change 35.137  Datasets TYPE42DS, TYPE42SR & TYPE42VT with APAR OA44319 
VMAC42         have increased accuracy for these I/O duration variables:
Jun  6, 2017   RESPTIME AVGCONTM AVGPNDTM AVGDISTM AVGCUQMS S42CONTM and
               AVGIOQMS.                                                
   Thanks to Ron Hawkins, Hitachi, USA.                                 
                                                                        
Change 35.136  Correction for NETVIEW ID=38 record with S38CCALR length 
VMAC38         less than expected length of 8 bytes.  Record is valid,  
Jun 14, 2017   MXG expected fixed length of 8 characters.               
   Thanks to Stuart Wildey, Morgan Stanley, ENGLAND.                    
                                                                        
Change 35.135 -Enhancements for 4 numeric data filters for RMF Monitor  
ADOCRMFV       III ASI (Address Space Information) table.               
ASMRMFV       -A pair of data filters are added to filter ASI entries   
VMACRMFV       based on the ASICPUTA (Total TCB+SRB time) field for each
Jun  6, 2017   MINTIME interval.  These filters are effective only if   
               the ASI table is selected.                               
                                                                        
               New Parameter  Alias(es)                                 
               -------------  ------------------------------------------
               ZEROCPU        ZCPU                               Default
               NOZEROCPU      NOZCPU, NZCPU                             
                                                                        
              -ZEROCPU is the default and results in all ASI entries    
               being output to the RMFBSAM file and thus all becoming   
               observations in the MXG PDB data set ZRBASI (depending   
               on other ASI filters that may be in use).                
                                                                        
               The default provides a compatible behavior with prior    
               ASMRMFV versions.                                        
                                                                        
              -NOZEROCPU results in all ASI entries with ASICPUTA=0     
               being filtered (depending on other ASI filters that may  
               be in use) and thus these do NOT become observations in  
               the MXG PDB data set ZRBASI.  The data volume to generate
               the PDB can be significantly reduced.                    
                                                                        
               In a test group of 21 RMF Monitor III VSAM data sets     
               78.3% of all ASI entries had ASICPUTA=0.  Actual results 
               may vary.                                                
                                                                        
              -While the NOZEROCPU setting might seem to be ALWAYS      
               desirable there are other considerations:                
                                                                        
               1) Filtering zero CPU time ASI entries will result in    
               time series gaps for some Address Spaces in some MINTIME 
               intervals in charts, plots, or reports.                  
                                                                        
               If such gaps are not acceptable, use the default ZEROCPU 
               parameter instead.  However, there will be a higher      
               number of PDB ZRBASI data set observations as in prior   
               ASMRMFV versions.                                        
                                                                        
               2) Zero CPU time conditions are NOT always due to pure   
               idleness for an Address Space.                           
                                                                        
               RMF Monitor III detected delays such as Processor,       
               Enqueue, Operator Reply, and Operator Mount separately or
               in combination can prevent accumulation of any CPU time  
               for an Address Space in a single MINTIME interval.       
                                                                        
               The NOZEROCPU parameter used alone with the NOKEEPDELAYS 
               default will filter out these entries so that further    
               investigation of a zero CPU time Address Space in a      
               MINTIME interval based on delays is impossible.          
                                                                        
              -With the above use of NOZEROCPU in mind an additional    
               pair of data filters are added to further filter ASI     
               entries based on the ASISWAIN (Number of Single State    
               Samples Delayed by ANY Resource) field for each MINTIME  
               interval.                                                
                                                                        
               This filter pair is effective only if the NOZEROCPU      
               parameter is in effect.                                  
                                                                        
               New Parameter  Alias(es)                                 
               -------------  ------------------------------------------
               KEEPDELAYS     KDELAYS, KDLYS, KEEPD                     
               NOKEEPDELAYS   NOKDELAYS, NOKDLYS, NOKEEPD        Default
                                                                        
              -With NOZEROCPU and NOKEEPDELAYS in effect all ASI entries
               with ASICPUTA=0 are filtered regardless if any delays    
               occurred or not during a MINTIME interval (if not already
               filtered by other ASI filters).                          
                                                                        
              -With NOZEROCPU and KEEPDELAYS in effect only ASI entries 
               with both ASICPUTA=0 AND ASISWAIN=0 (zero delays) in a   
               MINTIME interval are filtered (if not already filtered   
               by other ASI filters).                                   
                                                                        
               In a test group of 21 RMF Monitor III VSAM data sets with
               NOZEROCPU and KEEPDELAYS 75.8% of all ASI entries had    
               ASICPUTA=0 and ASISWAIN=0 and so were filtered.          
                                                                        
               This was only 2.5% less data filtered than with NOZEROCPU
               used alone.  Once again actual results may vary.         
                                                                        
              -NOZEROCPU and KEEPDELAYS are likely the best compromise  
               settings between ASI data reduction and retention of     
               delay information.  Neither are defaults.                
                                                                        
               However, for maximum data reduction use NOZEROCPU alone  
               if subsequent delay analysis is not required.            
                                                                        
              -If ZEROCPU/NOZEROCPU is specified multiple times the last
               occurrence takes effect.                                 
                                                                        
              -If KEEPDELAYS/NOKEEPDELAYS is specified multiple times   
               the last occurrence takes effect, but both are ignored   
               if ZEROCPU is in effect.                                 
                                                                        
              -The following chart shows ASI entries output to the      
               RMFBSAM file and thus also to the subsequent observations
               in MXG PDB ZRBASI data set based on the settings of      
               ZEROCPU/NOZEROCPU, KEEPDELAYS/NOKEEPDELAYS:              
                                                                        
               ---------------------------------------------------------
                        |    NOKEEPDELAYS       |  KEEPDELAYS           
                        |    (Default)          |                       
               ---------------------------------------------------------
               ZEROCPU  |All ASI entries output |All ASI entries output 
               (Default)|                       |                       
               ---------------------------------------------------------
               NOZEROCPU|Only ASI entries output|Only ASI entries output
                        |with ASICPUTA NE 0     |with ASICPUTA NE 0     
                        |                       |OR   ASISWAIN NE 0     
               ---------------------------------------------------------
                                                                        
              -ASIAND/ASIOR does NOT apply to ZEROCPU/NOZEROCPU and     
               KEEPDELAYS/NOKEEPDELAYS filters.  These are evaluated    
               independently of other ASI filters.                      
                                                                        
              -The order of ASI filter application is:                  
                                                                        
                1) ASISUBSYS=    <----                                  
                2) ASIWORKLOAD=      |                                  
                3) ASIRESGROUP=      |                                  
                4) ASISRVCLASS=      |--< ASIAND/ASIOR applies only     
                5) ASIRPTCLASS=      |    to these filters 1) to 8)     
                6) ASIJOBCLASS=      |                                  
                7) ASIJOBNAME=       |                                  
                8) ASIJESID=     <----                                  
                9) ZEROCPU/NOZEROCPU                                    
               10) KEEPDELAYS/NOKEEPDELAYS                              
                                                                        
              -The MXG00 record version is raised to x'09' from x'08'.  
               New fields added to the MXG00 record include:            
               ZEROCPU/NOZEROCPU and KEEPDELAYS/NOKEEPDELAYS settings   
                                                                        
              -Update message RMFV006I to show new output filters       
               ZEROCPU/NOZEROCPU/KEEPDELAYS/NOKEEPDELAYS.               
                                                                        
              -Several documentation Sections are updated to support    
               the above changes:                                       
                                                                        
               Section  0 "Contents"                                    
               Section  2 "Terminology"                                 
               Section  4 "RMF III Table Selection Parameters"          
               Section  5 "Input Data Selection Parameters"             
               Section  6 "Report Control Parameters"                   
               Section  7 "Output Data Control Parameters"              
               Section 12 "Messages"                                    
               Section 13 "Filtered Records"                            
               Section 31 "Summary"                                     
                                                                        
Change 35.134  Variables T103DBYT and T103DREQ are accumulated fields   
VMAC103        that are now correctly deaccumulated in TYPE103D dataset.
Jun  5, 2017   Variables T103DDNS and T103DKEE are always zero in test  
               data, so it is unknown if they also are accumulated.     
   Thanks to Joe Faska, DTCC, USA.                                      
                                                                        
Change 35.133  Test program COMPALL updated for new SMF products.  This 
COMPALL        utility compiles all of the SMF processing programs to   
Jun  5, 2017   ensure no CHAR/NUM conflicts in temporary variables.     
               Can not be run on z/OS because it requires 3292MB which  
               is more than the largest z/OS Private Area available.    
                                                                        
Change 35.132  Support for zVM 6.4 APAR VM66026 adds new variables;     
VMACVMXA      -Variable CUIDSSID='SUBSYSTEM*ID*SSID' is added to dataset
Jun  3, 2017   VXMTRDEV, VXIODVON, and VXIODDEF.                        
              -Variables added to VXIODVON                              
                PREFPATH RDEVHPPL CUIDSSID EQIDUID EQIEQID DEVCHAR      
                EDEVATTR                                                
              -Variables added to VXIODDEV                              
               RDEVNOAL RDEVYSAL RDEVIOQT RDEVIOQS CUIFCXPE RDEVWRAL    
               RDEVRDAL RDEVWXAL RDEVEXAL                               
                                                                        
Change 35.131  zVM variable CALENTMT was incorrectly divided by 16, and 
VMACVMXA       new variable CALSHARE='Hiperdispatch*Processor*SHARE is  
Jun  1, 2017   now created as CALSHARE=CALENTMT/65536;                  
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.130  Changes in VMXGSUM invocation in little used and mostly  
ASUM*          obsolete members so that WPS can handle QA stream:       
MNTH*          ASUMHPAI ASUMHPCS ASUMHPSU ASUMHPUX ASUMMWUX             
TRND*          MNTH70 MNTH70PR MNTH71 MNTH72 MNTH72GO MNTHCICS MNTHJOBS 
May 31, 2017   TRND70 TRND70SH TRND71 TRND72 TRND72GO                   
                                                                        
Change 35.129  Support for 7th, 8th, and 9th CICS User field.           
UTILEXCL                                                                
IMACIC7D                                                                
IMACIC8D                                                                
IMACIC9D                                                                
IMACIC7U                                                                
IMACIC8U                                                                
IMACIC9U                                                                
May 31, 2017                                                            
                                                                        
Change 35.128  Documentation Note.  ZFS and ODS users may need to change
IMACINIT       the MXG default CAPSOUT option to NOCAPSOUT since those  
May 26, 2017   system need to support both cases.  I don't think it is  
               safe for me to change the option as it could impact the  
               existing users on z/OS where it was originally needed.   
               But you can add  OPTIONS NOCAPSOUT: in the IMACINIT      
               member of your tailoring library if you determine it can 
               be changed with no impact.                               
                                                                        
Change 35.127  Dataset TYPE30_6 could have negative values for Early    
VMAC30         Address Spaces (ASIDs that start prior to JES init that  
May 26, 2017   have missing READTIME and JESNR) because of multiple     
               of the same JOB name, but adding variable ASID to the    
               BY list in MACRO _BTY30U6 corrects these errors.         
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.126  Variable SMF30SLM is decoded into these new variables in 
BUILD005       TYPE30_4 and PDB.STEPS in BUILDPDB and BUILDPD3:         
BUIL3005         SMF30SLMRB='REGIONBELOW*NONEXTENDED*REGION?'           
VMAC30           SMF30SLMRA='REGIONABOVE*EXTENDED*REGION?'              
May 26, 2017     SMF30SLMSB='SYSRESVBELOW*NONEXTENDED*REGION?'          
                 SMF30SLMSA='SYSRESVABOVE*EXTENDED*REGION?'             
                 SMF30SLMML='MEMLIMIT*ACTED ON*MEMLIMIT?'               
                 SMF30SLMBY='IEFUSI*BYPASSED*ALL*SMFLIM?'               
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.125  See Change 35.166.                                       
                                                                        
Change 35.124  Running WPS with more than 20 libnames caused WPS to fail
PDBAUDIT       so now with WPS if there are more than 20 LIBNAMES after 
May 22, 2017   removing the LIBNAMES not related to PDBAUDIT, MXG shuts 
               down with a message that only the first 20 were used.    
                                                                        
Change 35.123  Support for z/OS 2.2 updates to TYPE991 dataset adds many
VMAC99         new variables.                                           
May 22, 2017                                                            
   Thanks to David Cogar, WellsFargo, USA.                              
                                                                        
Change 35.122  Two new parameters added:                                
ANALCAPD       COMPANY= lets you override MXG in title statements       
May 22, 2017   OUTDATA= lets you preserve the dataset with actuals and  
               rolling 4 hour MSU values for further analysis.          
              -GRAPHICS code is enabled for WPS at 3.3 or higher.       
                                                                        
====== Changes thru 35.121 are in this MXG 35.05 dated May 15, 2017=====
                                                                        
Change 35.121  ERROR: MACRO KEYWORD DO APPEARS AS TEXT because the quote
ANALAVAI       after "DO'" and several other syntax errors corrected.   
May 13, 2017                                                            
   Thanks to Hai Huynh, Freddie Mac, USA.                               
                                                                        
Change 35.120  WPS only, MXG 35.04, Change 35.085.  A variable with no  
VMXGPRNT       label generated unintended text with multiple quotes     
May 16, 2017        Varname1='Label*(varname)''(next vrname)'           
               which is valid text for a SAS label, defined as the text 
               after an equal sign up to the text before the next token 
               that is followed by an equal sign, but this syntax was   
               was not accepted by WPS as a label, causing an ERROR.    
               The circumvention is to create a LABEL='NOLABEL' for     
               variables that do not have a label.                      
              -VMXGPRNT is used in ANAL113, ANAL116, VMXGFIND, VMXGPRAL 
               VMXGPRA1, VMXGPRNT, VMXGSRCH, and JCLPDB members.        
                                                                        
Change 35.119  READDB2 had a hard coded limit of 450 for IFCID, and 499 
READDB2        had been added in TYPE102s.  Now limit is 999.           
May 11, 2017                                                            
   Thanks to Lynn Hong, UCLA, USA.                                      
                                                                        
Change 35.118  Notes on the use of VIEWs in DATA steps that create more 
Document       than one DATASET.                                        
May 11, 2017    -Only one DATASET can be a view in a DATA step (and the 
                 BUILDPDB program already has one).                     
                -Any of the datasets can be the view, but that view MUST
                 be the first dataset referenced (read/sorted), or none 
                 of the other datasets will exist.                      
                -Views can dramatically reduce elapsed and CPU times and
                 I/O counts and durations, for instance for a DATA step 
                 followed by a SORT, where the VIEW eliminates the write
                 and read of the dataset that is created without a VIEW.
                 The VIEW doesn't have any impact on the resources used 
                 by the SORT.                                           
                -This example started as TYPE120 with the lower case    
                 lines added. WORK needs to be cleared in case there was
                 a dataset of the same name, whether it was a view or a 
                 dataset. The /view=typ1209r enables the view and names 
                 the one dataset, and the _st1209r "data set sort macro"
                 is invoked first, and then made blank so the _S120     
                 "product sort macro" can sort the other datasets:      
                                                                        
                     proc datasets ddname=work mt=all kill;             
                     %INCLUDE SOURCLIB(VMACSMF,VMAC120,IMACKEEP);       
                     DATA                                               
                     _VAR120  /view=typ1209r                            
                     _SMF                                               
                     _CDE120                                            
                     run;                                               
                     _st1209r                                           
                     run;                                               
                     macro _st1209R  %                                  
                     _S120;                                             
                     RUN;                                               
                 The DATA/SORT took 6 hours, the VIEW/SORT took 2.      
   Thanks to Joe Faska, DTCC, USA.                                      
   Thanks to Michael Oujesky, DTCC, USA.                                
                                                                        
Change 35.117 -VMXGFIND did not correctly build the output dataset names
VMXGFIND       when multiple input PDBs were to be read; while all were 
May 11, 2017   read, only one was output.                               
   Thanks to David A. Sadler, Optum, USA.                               
                                                                        
Change 35.116   35.04 only. The TYPSMVJE test was in TESSUSR1 but should
JCLTEST9        have been in TESSOTHR member, so TESSUSR1 step failed   
May 16, 2017    because //MVJEIN DD was not found in that step's JCL.   
                Add //MVJEIN DD DUMMY to the TESSUSR1 step.             
                TYPSQACS replaced TESSQACS in //TESTQAPM step.          
                                                                        
   Thanks to Tony Ferullo, MIB, Inc., USA.                              
   Thanks to Rod Feak, MIB, Inc., USA.                                  
                                                                        
Change 35.115   Reserved Change Number.                                 
                                                                        
Change 35.114   New variables added to TYPE749 PCIE data found in SMF   
VMAC74          manual refresh:                                         
May 10, 2017       R749FLAG='VALIDITY*FLAG'                             
                   R749NET1='1ST*PORT*PNET ID'                          
                   R749NET2='2ND*PORT*PNET ID'                          
                   R749DBYX='BYTES*TRANSMITTED*BY PCIE*FUNCTION'        
                                                                        
Change 35.113   MXG 35.04 only, TYPE70 SHARE weights wrong, although the
VMAC7072        PDB.ASUMCELP values were correct and recommended for the
May 10, 2017    analysis of LPAR weights.                               
   Thanks to Andrew Petersen, CSC, AUSTRALIA.                           
                                                                        
Change 35.112 -MXG 35.04 Only, only with variable names longer than 32  
VGETSORT       bytes. ERROR Truncated SORTBY variable name not found.   
May  9, 2017   The LENGTH for the new SORT variables is $32 now.        
May 11, 2017   VGETSORT is used in BLDSMPDB, UTILROLL and MULTIPDB.     
              -VGETSORT: Cosmetic, UNINIT variable NOBS message because 
               it was not in the KEEP list, but had no impact.          
                                                                        
Change 35.111  DB2 12.1, INVALID QLAC SEG ERROR, LENQLAC=218, new       
VMACDB2        field QLACPRLV was inserted by DB2 CONTINUOUS DELIVERY,  
VMACDB2H       but was unknown to MXG as there was no notification by   
May  9, 2017   IBM that a field was inserted.  MXG detected the change, 
May 11, 2017   printed the ERROR message, and deleted the record, so    
               some observations in DB2ACCT were not output.  The error 
               led to the discovery of an updated DB2 MACLIB with this  
               text in DSNDQLAC member:                                 
                  e26995  Continuous Delivery.                          
                  Product functional/build level. QLACPRLV. s28617      
               but a search for s28617 discovered nothing.  Only a      
               search for the new field, QLACPRLV found it was added.   
               But there were no other references to the s28617 nor     
               e26995 tokens in the other MACLIB members.               
                                                                        
               Of course, now that I know this new field name, Google   
               found both fields referenced in APAR PI74456:            
                 "IFCID 3 accounting information will now provide the   
                  partner's functional/service/build level in a new     
                  QLACPRLV field."                                      
                 "IFCID 365 location statistics information will now    
                  provide the partner's functional/service/build level  
                  in a new QLSTPRLV field."                             
                                                                        
               The real issue raised with DB2 support and unanswered    
               as of this writing is: HOW AM I SUPPOSED TO KNOW that    
               fields were inserted by Continuous Delivery.             
                                                                        
               These header fields are now kept in DB2ACCT:             
                 QWHS_MOD_LVL='MOD LEVEL FOR*CONTINUOUS*DELIVERY'       
                 QWHS_REC_INCOMPAT='INCOMPATIBLE*CHANGE*VALUE'          
                 QWHS_REC_COMPAT='COMPATIBLE*CHANGE*VALUE'              
                 QWHS_REC_VALIDITY='CHECK*NEEDED FOR*INCOMPAT*COMPAT'   
               The current MOD_LVL is V12R1M100 and MXG's COMPAT and    
               INCOMPAT count of changes is zero before and after this  
               INCOMPAT change.  It is unclear how these fields could   
               be used, since they are after the record was changed.    
   Thanks to Dennis Gaetner, Fiduciagad, GERMANY.                       
   Thanks to Sieghart Seith, Fiduciagad, GERMANY.                       
                                                                        
Change 35.110  Processing //PRISMAPR DD caused ERROR: UNDETERMINED I/O  
VMACPRPR       FAILURE because the DCB attributes were set for SMF, but 
May  9, 2017   PRISMAPR input records are FB/256/27904.                 
   Thanks to Gene Heikkinen, Blue Cross Minnesota, USA.                 
                                                                        
Change 35.109  Variables SM1209EX/EY/EZ/FA were accidentally dropped by 
VMAC120        Change 35.024 from dataset TYP120R; you can correct with 
May  5, 2017     MACRO _KT1209R  SM1209EX SM1209EY SM1209EZ SM1209FA %  
               in your IMACKEEP tailoring member until you update MXG.  
   Thanks to Larry A. Gray, Lowes, USA.                                 
                                                                        
Change 35.108  The ANALID report's TITLE can be changed with the TITLE= 
ANALID         argument, if you invoke %ANALID yourself, but BUILDPDB's 
VMXGINIT       invocation is internal, so this new macro variable       
May  5, 2017    %LET MXGTITLEANALID=SMF RECORDS AUDIT REPORT;           
   Thanks to Robert Chavez, Florida Power and Light, USA.               
                                                                        
Change 35.107  Support for IAM Version 9.0.                             
VMACIAM                                                                 
May  4, 2017                                                            
                                                                        
Change 35.106  Adds an array of system IDs SYS1-SYS10 and creates new   
VMXGUOW        variables SYSTEMCICS (system of origin of the 110) and   
May  4, 2017   SYSTEMDB2 (system where the 101 was found) to the        
               PDB.ASUMUOW dataset.                                     
                                                                        
Change 35.105  The CICS duration fields are now formatted TIME16.6      
VMAC110        to show the full resolution to the microsecond. FORMATS  
May  4, 2017   only impact the printed/displayed value of the variable. 
                                                                        
====== Changes thru 35.104 are in this MXG 35.04 dated May  1, 2017=====
                                                                        
Change 35.104  Support for EDGR/RMM APAR OA46947 which prints asterisks 
VMACEDGR       for RVCOMPRAT and RVPHYUSED when values can't be derived.
May  2, 2017   Only warning and hex dumps were printed; the output data 
               sets were correctly built; this change suppressed the    
               log messages when the values are asterisks.              
   Thanks to Craig Collins, State of Wisconsin, USA.                    
                                                                        
Change 35.103  If you specified "defer=yes" in lower case and the input 
VMXGSET        was on tape you got a 413 ABEND because the compare to   
Apr 28, 2017   defer= was comparing to upper case. Not reported, found. 
                                                                        
Change 35.102 -z/VM 6.3 and 6.4, BROKEN CONTROL RECORD ERROR because the
VMACVMXA       INPUT STSI $VARYING255 STSILEN @; failed when STSILEN was
Apr 28,2017    greater than 255; increased to 512 in VXMTRTOP.          
              -Also 6.3, VXIODVSW code didn't protect the undocumented  
               extra 4 bytes.  And these new variables are now created: 
                 LANFORW  ='LAN*FORWARDING*FLAGS'                       
                 OASPORTN ='OSA*PORT*NUMBER'                            
                 ACCTYPE  ='ACCESS*LIST*TYPE*FLAG'                      
              -New variables in VXSTSYG dataset:                        
                 RCCSCAPF='BFP*ZIP*CAPABILITY'                          
                 RCCCCAPF='BFP*CP*CAPABILITY'                           
                 RCCNCAPF='NOMINAL*CP*CAPABILITY'                       
                 SSI1PCPS='CP CORE*SPEED*CYCLE*PER MICRO'               
                 SSI1SCPS='ZIP CORE*SPEED*CYCLE*PER MICRO'              
              -New variables in VXSTSYG dataset:                        
                 RSAWRTHROTS='TIMES*LIMITED*PAGING*BANDWIDTH'           
                 RSAPRTHROTS='TIMES*PARTIAL*WRITE*THROTTLE'             
                 RSANDMREC='GLOBAL*RECLAIM*TASK*INITIATED'              
                 RSANDMRND='NDMBKS*RETURNED*GLOBAL*RECLAIM'             
              -New variables in VXSTORSP dataset:                       
                PLSNDMRQ='FROM*RECYCLE'                                 
                PLSNDMLO='NDMBK REQS*RECYCLE*LOCAL*SUPPLIED'            
                PLSNDMGL='NDMBK REQS*RECYCLE*GLOBAL*SUPPLIED'           
                PLSNDMG2L='NDMBKS MOVED*GLOBAL*TO LOCAL'                
                PLSNDMDX='TIMES*TASK*RETURNED*CHAIN*TO LOCAL'           
                PLSNDMRET='NDMBKS*RETURNED*TO LOCAL'                    
                PLSNDML2G='NMDBKS*MOVED*LOCAL TO*GLOBAL'                
                PLSNDMREL='NMDBKS*RETURNED*TO FREE'                     
                PLSNDMREC='TIME*LOCAL*RECLAIM*INITIATED'                
                PLSNDMRND='NDMBKS*RETURNED*TO FREE*LCL RECLAIM'         
                PFXCLPLCNT='FRAMES*CLEARED*LOCAL*AVAIL*PLUS'            
                PLSCLALLO='CLEARED*LOCAL*AVAILABLE*LLOW THRESH'         
                PLSCLALHI='CLEARED LOCAL AVAILABLE*LHIGH THRESH'        
                PLSCLALADDED='FRAMES*ADDED TO*CLEARED*LOCAL'            
                PLSCLALFWREMOVED='FRAMES*ADDED TO*PROCESSED*LIST'       
                PLSCLALTRIMMED='FRAMES*TRIMMED*CLEARED*LOCAL'           
                PLSFPPFENTERED='TIMES*FPP FAULT*ENTERED*FOR GUEST'      
                PLSFPPFSUCCESS='TIMES*FPP FAULT*SUCCESSFUL'             
                PLSCPPFENTERED='TIMES*FPP FAULT*ENTERED*FOR CP'         
                PLSCPPFSUCCESS='TIMES*FPP FAULT*SUCCESSFUL*FOR CP'      
                PLSCPPFMDC='TIMES*FPP FAULT*EXITED*CACHE'               
                PLSCLALREQUESTS1='TIMES*FRAME REQ*CLEARED*AVAIL LIST'   
                PLSCLALUNFILLED1='TIMES*REQUEST*FOUND LAL*EMPTY'        
                PLSCLALREPLENOD='TIMES*REQUEST*FOUND CLA*EMPTY*DEMAND'  
                PLSCLALUNFILLED2='TIMES*REQUEST*FOUND CLA*EMPTY*BEFORE' 
                PLSCLALREQUESTS2='TIMES*REQUEST*FROM*CLA LIST'          
                PLSCLALUNFILLED3='TIMES*REQUEST*FOUND CLA*EMPTY*BEFORE3'
                PLSBGCTM='CPU TIME*BACKGROUND*REPLEN*CL GAL'            
                PLSCGALREQUESTS='TIMES*WANTED*MOVE FRAMES*CGAL TO CLLA' 
                PLSCGALFRAMESR='FRAMES*WANTED*MOVE*CGAL TO CLLA'        
                PLSCGALMOVED='FRAMES*MOVED*CGAL TO CLLA'                
                PLSCGALNOLOCK='TIMES NOT*MOVED*CGAL TO CLLA*LOCK'       
                PLSCGALUNFILLEDN='FRAMES NOT*MOVED*CGAL TO CLLA*FILL'   
                PLSCGALWANTING='TIMES*CGLA*INSUFFICIENT*FRAMES'         
                PLSCGALUNFILLEDW='FRAMES NOT*MOVED*CGAL TO CLAL*DW'     
                PLSULALCNT='FRAMES ON*UNCLEARED*LAL'                    
                PLSULALLO='UNCLEARED*LOCAL*AVAILABLE*LIST LOW TH'       
                PLSULALHI='UNCLEARED*LOCAL*AVAILABLE*LIST HI TH'        
                PLSULALREQUESTS1='FRAME REQ*UNCLEARED*LAL'              
                PLSULALUNFILLED1='TIMES REQ*UNCLEAR LAL*BEFORE*ATTEMPT' 
                PLSULALREPLENOD='TIMES REQ*UNCLEAR LAL*AND*ATTEMPT'     
                PLSULALUNFILLED2='TIMES REQ*UNCLEAR LAL*BEFORE*FILLED'  
                PLSSWPROCLCNT='FRAMES*ON THE*SOFTWARE*PROCESSED LIST'   
   Thanks to James T. Barton, Veterans Administration, USA.             
                                                                        
Change 35.101  New parameter OUTCODE= lets you insert some code just    
VMXGGETM       prior to the end of VMXGGETM. Should be complete data    
Apr 28,2017    or PROC STEPS.                                           
   Thanks to Craig Collins, State of Wisconsin, USA.                    
                                                                        
Change 35.100  SYSLOG code has been updated; the old code was 2016.     
SYSLOG                                                                  
May  2, 2017                                                            
   Thanks to Karl Lasecki, Chemical Abstracts Service, USA.             
                                                                        
Change 35.099  ANALID relocate.                                         
                                                                        
Change 35.098  RMF III Filter enhancements.                             
ADOCRMFV      -Enhancements for character data filtering for RMF Monitor
ASMRMFV        III CPU (Processor Data Control Block), CPC (CPC Data    
VMACRMFV       Control Block), improved message RMFV029* DEAD SPACE     
Apr 26, 2017   controls, better error message formats and content, and  
               other usability and performance gains.                   
                                                                        
              -1 new character filter is added to support CPU entry     
               selection from this table to the RMFBSAM output file.    
               This filter is effective only if the CPU or CPC table is 
               selected and applies to BOTH tables.                     
                                                                        
               New Keyword    Aliases                                   
               ------------   ------------------------------------------
               CPUSYSTEM=     CPUSYSID=, CPUSID=                        
                                                                        
               Since this is the only filter for this table there are NO
               CPUAND/CPUOR parameters.                                 
                                                                        
               Syntax and usage mirrors that used for the existing      
               SYSTEM= parameter for selection by SMF Sysid using ranges
               and/or patterns.                                         
                                                                        
              -1 new filter is added to support CPC entry selection     
               from this table to the RMFBSAM output file.  This filter 
               applies ONLY to the CPC (not the CPU) table.             
                                                                        
               New Keyword    Aliases                                   
               ------------   ------------------------------------------
               CPCSYSTEM=     CPCSYSID=, CPCSID=                        
                                                                        
               Since this is the only filter for this table there are NO
               CPCAND/CPCOR parameters.                                 
                                                                        
               Syntax and usage mirrors that used for the existing      
               SYSTEM= parameter for selection by SMF Sysid using ranges
               and/or patterns.                                         
                                                                        
              -TUTORIAL:                                                
               The new CPCSYSTEM= parameter may appeal to large         
               installations running multiple z/OS LPARs on a CEC       
               (Central Electronic Complex) and using RMF Monitor III   
               gathering data on several of them.                       
                                                                        
               RMF Monitor III creates the CPCDB (Central Processing    
               Complex Data Block) table for each instance of RMF       
               Monitor III on a given CEC except if the LPAR is a z/VM  
               guest.                                                   
                                                                        
               The CPCDB (aka CPC) has LPAR settings and Logical        
               Processor data for every image on the CEC whether it be  
               a z/OS LPAR or not.                                      
                                                                        
               There is no RMF III option to turn off CPC data          
               collection, so this parameter is an alternative.         
                                                                        
               As long as the RMF Monitor III MINTIME, CYCLE, and SYNC  
               options are identical redundant CPC tables for every RMF 
               Monitor III native (non-guest) LPAR on the CEC are       
               created at every MINTIME interval.                       
                                                                        
               The MXG PDB build will create a ZRBLCP observation for   
               each Logical Processor for each LPAR for every MINTIME   
               interval.  For installations with several RMF Monitor III
               LPARs on a CEC this can result in a lot of extra, but not
               useful duplicate SAS ZRBLCP observations.                
                                                                        
               See new documentation Section 30 "CPC Data Relief        
               Technique" for more details on use of CPCSYSTEM=.        
                                                                        
               It is a user responsibility to set up CPCSYSTEM= for each
               CEC configuration properly and to track any LPAR SYSID   
               changes as they occur.  An incorrect CPCSYSTEM=          
               specification will result in loss of data in the MXG     
               ZRBLCP SAS data set should the SYSID no longer exist     
               or be misspelled.                                        
                                                                        
              -CSR (Common Storage Remaining) processing now moves CSR  
               entries in blocks for as many entries that fit to the    
               RMFBSAM output buffer when NO CSR character data filters 
               are used.                                                
                                                                        
               When these filters were added in MXG Change 34.373       
               processing changed to move one CSR entry at a time to the
               output buffer.  However, this is an unnecessary overhead 
               if no CSR filtering is in effect.  The earlier processing
               technique is restored for this case.                     
                                                                        
               A test with 21 RMF Monitor III sample data sets at the   
               35.098 level showed about a 1% CPU reduction for CSR     
               processing with no filters used compared to the 34.373   
               level.  This will vary with the number of CSR entries    
               and RMF III VSAM data sets processed.                    
                                                                        
              -The MXG00 record version is raised to x'08' from x'07'.  
               New fields added to the MXG00 record include:            
               CPUSYSTEM= and CPCSYSTEM= Range/Pattern maximums         
               CPUSYSTEM= and CPCSYSTEM= Range/Pattern table sizes      
               % of available TIOT entries used                         
                ASMCPCRX='MAXIMUM*CPCSYSTERM*RANGES'                    
                ASMCPCPX='MAXIMUM*CPCSYSTERM*PATTERNS'                  
                ASMCPURX='MAXIMUM*CPUSYSTERM*RANGES'                    
                ASMCPUPX='MAXIMUM*CPUSYSTERM*PATTERNS'                  
                ASMSHSPL='WARNING*LIMIT*PCT SPACE*USE'                  
                ASMCPCRS='SIZE*CPCSYSTEM*RANGE*TABLE'                   
                ASMCPCPS='SIZE*CPCSYSTEM*PATTERN*TABLE'                 
                ASMCPURS='SIZE*CPUSYSTEM*RANGE*TABLE'                   
                ASMCPUPS='SIZE*CPUCSYSTEM*PATTERN*TABLE'                
                                                                        
              -TIOT entries used percentage is added to the RMFV000I    
               message.  TIOT usage information is grouped on a single  
               report line.                                             
                                                                        
              -Support for ILIMIT= (alias ILIM=) and SLIMIT= (alias     
               SLIM=) keywords is added to control appearance of        
               the RMFV029* DEAD SPACE message (*=I,W,E,S).             
                                                                        
               Previous versions of ASMRMFV could issue this message for
               exhausted RMF III indexes even when the VSAM data set    
               usage was relatively high.  In this case re-allocating   
               the VSAM data set to make it smaller is not productive.  
                                                                        
               ILIMIT= specifies a percentage in the range of 0 to 100  
               as a threshold for RMF III VSAM Data Set Header (DSH)    
               indexes usage.  The default is 100.                      
                                                                        
               SLIMIT= specifies a percentage in the range of 0 to 100  
               as a threshold for RMF III VSAM Data Set space usage.    
               The default is 95.                                       
                                                                        
               The defaults of ILIMIT=100 and SLIMIT=95 with INDEXES and
               SPACE options in effect mean that if all 1110 sample     
               indexes are exhausted in the Data Set Header (DSH)       
               record, but the RMF Monitor III VSAM data set is 95% or  
               more utilized no DEAD SPACE condition is flagged.        
                                                                        
               See the documentation for RMFV029* for how the settings  
               of NOINDEXES/INDEXES, NOSPACE/SPACE, ILIMIT=, and SLIMIT=
               parameters interact.                                     
                                                                        
               Users who find RMFV029* a nuisance rather than an aid    
               can suppress it completely with ILIMIT=0 and SLIMIT=0.   
                                                                        
               ILIMIT= and SLIMIT= values in effect are displayed in    
               message RMFV037I.                                        
                                                                        
               Section 22 RMF III VSAM Data Set Index Usage and Sizing  
               is updated to discuss use of ILIMIT= and SLIMIT= options.
                                                                        
              -There are now 4 distinct levels for messages that can    
               have variable severity based on the settings of the      
               various existing *ERR= condition keywords:               
                                                                        
               *ERR     Message                              Return     
               Setting  Suffix          Meaning              Code       
               -------  ------  -------------------------   ---------   
               IGNORE     I     Ignore error/continue       No change   
               WARN       W     Warn   error/continue       0004        
               ERROR      E     Issue  error/may continue   0008        
               ABEND      S     Issue  error/Abend U0998    N/A (1)     
                                                                        
               (1) Abends have a distinct Reason Code but no Return     
               Code.                                                    
                                                                        
               In past ASMRMFV versions 'E' suffixed messages           
               inconsistently may or may not have resulted in an Abend. 
                                                                        
              -Distributed *ERR settings remain as:                     
                                                                        
               Keyword     DEFAULT         CONTROLS                     
               ---------   -------  -------------------------           
               ALLOCERR=    WARN    DYNAMIC ALLOCATION ERRORS           
               ATTRERR=     WARN    DATA SET ATTRIBUTE ERRORS           
               CATERR=      WARN    CSI CATALOG LOOKUP ERRORS           
               DEADERR=     WARN    VSAM DEAD SPACE ERRORS              
               DSIGERR=     WARN    DSIG ID (DSH) ERRORS                
               DSNERR=      WARN    CSI DSNAME LOOKUP ERRORS            
               DUPERR=      WARN    DUPLICATE DSNAME ERRORS             
               EMPTYERR=    IGNORE  EMPTY VSAM DATA SET ERRORS          
               PATTERR=     ABEND   PATTERN AND/OR RANGE ERRORS         
               READERR=     ABEND   VSAM READ I/O ERRORS                
               TABERR=      WARN    RMF III TABLE VALIDATE ERRORS       
               TYPEERR=     WARN    DATA SET TYPE ERRORS                
               RCERR=       WARN    REPORT CLASS FIND ERRORS            
               RGERR=       WARN    RESOURCE GROUP FIND ERRORS          
               SCERR=       WARN    SERVICE CLASS FIND ERRORS           
               WLERR=       WARN    WORKLOAD FIND ERRORS                
                                                                        
              -ASMRMFV will now generate the correct message format for 
               variable severity messages during assembly based on the  
               defaults above.  This avoids unnecessary tailoring during
               ASMRMFV initiation.  Any user overrides of the above     
               settings will still require tailoring of related         
               messages by ASMRMFV during start up.                     
                                                                        
              -Internal error message generation interface updated for  
               following messages:                                      
               RMFV004E, RMFV005*, RMFV007S, RMFV034S, RMFV035*,        
               RMFV056* (*=I,W,E,S)                                     
                                                                        
               Improvements for these messages include:                 
                                                                        
               3 separate error messages subroutines replaced by one    
               for code path length reduction.                          
                                                                        
               Extraneous blanks in these error messages eliminated     
               for better legibility.                                   
                                                                        
               Clearer and less cryptic error descriptions.             
                                                                        
              -RMFV006E message had incorrect timestamp when FROMDATE=  
               exceeded TODATE=                                         
                                                                        
              -RMFV007S message missing DDNAME when RMFBSAM DD was not  
               present.                                                 
                                                                        
              -RMFV007S message will now show N/A when a Reason Code is 
               not available for a failed function or service.          
                                                                        
              -Improve logic of DOW= keyword processing when using a    
               range, i.e. DOW=day1:day2 to examine the last half of    
               the day of week range if an error is found in the first  
               half.  Also leading and trailing colons are stripped     
               before length checking.                                  
                                                                        
              -Former documentation Section 30 Summary is now Section 31
               and former Section 31 Bibliography is now Section 32.    
                                                                        
              -Several documentation Sections are updated to support    
               the above changes:                                       
                                                                        
               Section  0 "Contents"                                    
               Section  5 "Input Data Selection Parameters"             
               Section  6 "Report Control Parameters"                   
               Section  8 "Error Handling Parameters"                   
               Section 12 "Messages"                                    
               Section 13 "Filtered Records"                            
               Section 16 "Return Codes"                                
               Section 25 "Ranges and Patterns"                         
               Section 30 "CPC Data Relief Technique"                   
               Section 31 "Summary"                                     
               Section 32 "Bibliography"                                
                                                                        
Change 35.097  Four IMF variables that are INPUT with TODSTAMP8 are now 
VMACCIMS       formatted DATETIME25.6 to display full microseconds. The 
Apr 25, 2017   other datetimes are limited to DATETIME21.2 resolution.  
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 35.096  New UTILROLL utility combines all SAS datasets from one  
UTILROLL       or more SAS data libraries (think "hourly" PDB runs) into
JCLROLL1       another LIBNAME (think "daily" PDB), either concatenating
JCLROLL2       the new data, or interleaving to preserve the sort order.
VGETSORT       If the ROLLTO LIBNAME is empty or the dataset being added
Apr 24, 2017   added to does not exist the code will ignore the ROLLTO  
               LIBNAME and use only the ROLLFROM to create the ROLLTO   
               datasets.                                                
              -VGETSORT could return bad information if there was       
               a variable name longer than 8 bytes.  Length was         
               increased to 32 and NOBS ENG were added to the output.   
                                                                        
Change 35.095  APPL PCT variables are created in TYPE72GO to match the  
VMAC7072       RMF Workload report values:                              
Apr 24, 2017     APPLCP   ='APPL PCT*OF 1 CPU*CPU TIME*ON CP'           
                 APPLAAPCP='APPL PCT*OF 1 CPU*ZAAP ELIG*ON CP'          
                 APPLIIPCP='APPL PCT*OF 1 CPU*ZIIP ELIG*ON CP'          
                 APPLAAP  ='APPL PCT*OF 1 CPU*CPU TIME*ON ZAAP'         
                 APPLIIP  ='APPL PCT*OF 1 CPU*CPU TIME*ON ZIIP'         
               with this code:                                          
              IF R723MCF  GT 0 THEN                                     
               APPLCP=   100*CPUTM/(DURATM*R723MCF);                    
              IF R723MCFI GT 0 THEN DO;                                 
                APPLAAPCP=100*CPUIFETM/(DURATM*R723MCFI);               
                APPLAAP=  100*(256*CPUIFATM/R723NFFI)/(DURATM*R723MCFI);
              END;                                                      
              IF R723MCFS GT 0 THEN DO;                                 
                APPLIIPCP=100*CPUZIETM/(DURATM*R723MCFS);               
                APPLIIP=  100*(256*CPUZIPTM/R723NFFS)/(DURATM*R723MCFS);
              END;                                                      
   Thanks to Ray Bole, IBM Global Services, USA.                        
                                                                        
Change 35.094  Support for BMC Mainview for Java Environment creates    
EXMVJE01          DDDDDD    MXG       MXG                               
EXMVJE02          DATASET   DATASET   DATASET                           
EXMVJE04          SUFFIX    NAME      LABEL                             
EXMVJE07                                                                
EXMVJE08          MVJE01    MVJE01    JMX MEMORY SUMMARY                
EXMVJE12          MVJE02    MVJE02    JMX THREAD SUMMARY                
IMACMVJE          MVJE04    MVJE04    JMX CLASS LOADING SUMMARY         
TYPEMVJE          MVJE07    MVJE07    JMX GARBAGE COLLECTION SUMMARY    
TYPSMVJE          MVJE08    MVJE08    JMX MEMORY POOLS                  
VMACMVJE          MVJE12    MVJE12    JMX CPU USAGE                     
VMXGINIT                                                                
Apr 25, 2017                                                            
                                                                        
Change 35.093  MXG 35.03 only, variable PLATBUSY in TYPE70/RMFINTRV and 
VMAC7072       PCTOFHDW in RMFINTRV were incorrect after Change 35.064  
Apr 22,2017    revised the SHARE calculations.                          
   Thanks to Paul Naddeo, FISERV, USA.                                  
   Thanks to Robin Hanley, FISERV, USA.                                 
   Thanks to David Bixler, FISERV, USA.                                 
                                                                        
Change 35.092  Support for z/VM 64 (INCOMPATIBLE).                      
VMACVMXA      -Dataset VXSYTCUG new variables                           
Apr 20,2017      SSI2MTIF='MULTITHREADING*CONFIGURATION'                
                 SSI2MTGF='MULTITHREAD*GENERAL*PROC*CONFIG'             
                 SSI2MTID='MULTITHREAD*MAX*TID'                         
                 LCUTCTOD='DATETIME*WHEN CORE*INFO*FETCHED'             
              -Dataset VXMTRSYS new variable                            
                 CALFLAG3-'MISCELLANEOUS*FLAGS*/                        
              -Datasets VXUSEACT and VXUSELOF new variables             
                 VMDTTIME_MT1='TOTAL*MT-1*EQUIVALENT*TIME'              
                 VMDVTIME_MT1='RUN*MT-1*EQUIVALENT*TIME'                
                 VMDVTMP_MT1 ='EQUIV*MT-1*VTIME*ON PRIMARY'             
                 VMDTTTP_MT1 ='EQUIV*MT-1*VTIME+SIM*PRIMARY'            
                 VMDVTMS_MT1 ='EQUIV*MT-1*VTIME*ON SECNDRY'             
                 VMDTTMS_MT1 ='EQUIV*MT-1*VTIME+SIM*SECNDRY'            
                 VMAVTMP_PRO ='TOTAL*MT-1*PRORATED*CORE*PRI'            
                 VMATTMP_PRO ='RUN*MT-1*PRORATED*CORE*PRI'              
                 VMAVTMS_PRO ='TOTAL*MT-1*PRORATED*CORE*SEC'            
                 VMATTMS_PRO ='RUN*MT-1*PRORATED*CORE*SEC'              
                 PROBITS='PRORATED*CORE*TIME*BITS'                      
              -Datasets VXPRCPUP new variables                          
                 WHIOCAPV='MAX*CORES*PERMITTED'                         
                 WHIOCTVR='CALCULATED*T/V*RATIO'                        
                 WHIOPTVR='CEILING*PROJECTED*T/V*RATIO'                 
                 SRXTVCNF='CONFIDENCE*PERCENTAGE'                       
                 CALTVALG='CEILING*PROJECTION*ALGORITHM'                
                 WHIOTVCT='CEILING*PROJECTION*VALID*SAMPLES*/           
                 WHIOGCPV='MAXIMUM*AGGREGATE*CORES'                     
              -Datasets VXIODVSW new variables                          
                 VQSAFLAG ='LACP*CONFIGURATION'                         
                 NIDLAPRE ='PREVIOUS*LOAD*BALANCE'                      
                 NIDLACUR ='CURRENT*LOAD*BALANCE'                       
                 NID_TOTPFCNT='PREVIOUS*LOAD*BALANCE*FRAMES'            
              -New segments IODPAD,IODPON,MTRPCI are not yet supported. 
              -These 6.4 segments don't exist in my test data so these  
               changes have NOT been validated yet:                     
                 PRCCUP SYTCUG SYTCUM SYTCUP                            
   Thanks to Diana L. Bodner, Progressive, USA.                         
                                                                        
Change 35.091 -Sometimes failed with a two level dataset name (unknown  
ANALCNCR       cause). VGETOBS logic modified.  Now will run SGPLOT     
Apr 22, 2017   if your SAS version is GE 9.3.                           
              -New example to count/plot concurrent TELNET sessions from
               the TYP11921 dataset.                                    
                                                                        
Change 35.090 -Support for CA'S OPSS Product USER SMF Record.           
VMACOPSS       These datasets are created:                              
Apr 22, 2017                                                            
May  9, 2017      DDDDDD     MXG       MXG                              
                  DATASET    DATASET   DATASET                          
                  SUFFIX     NAME      LABEL                            
                                                                        
                  OPSS01     TYPOPSS1  SS TERMINATION SUMMARY           
                  OPSS02     TYPOPSS2  SS OSF SERVER TERMINATION        
                  OPSS03     TYPOPSS3  SS AOF RULE DISABLEMENT          
                  OPSS04     TYPOPSS4  SS GLOBAL VARIABLE               
                  OPSS05     TYPOPSS5  SS SQL STATISTICS                
                  OPSS06     TYPOPSS6  SS IMS BMP STATISTICS            
                  OPSS07     TYPOPSS7  SS OSF TRANSACTION               
                  OPSS08     TYPOPSS8  SS EPI STATS                     
   Thanks to Bruce Sloss, PNC, USA.                                     
                                                                        
Change 35.089  The NDM-CDI new IHDRNDM exit member allows selection of  
IHDRNDM        which NDM Record Types are output with this logic:       
VMACNDM          //SYSIN DD *                                           
VMXGINIT          %LET MACNDMH= %QUOTE( IF NDMRTYPE='CT';) ;            
Apr 19, 2017      %INCLUDE SOURCLIB(TYPSNDM);                           
                                                                        
Change 35.088 -Running MXG on ASCII to read SMF using ftp access method 
BUILDPDB       can free the SMF allocation when SMF read is completed   
Apr 15, 2017   with this tailoring in your //SYSIN:                     
                  %LET EPDBOUT=%QUOTE(                                  
                    FILENAME SMF CLEAR;                                 
                   );                                                   
               If your SMF data is a GDG, this will unblock the base GDG
               name as soon as possible.                                
              -If running MXG on z/OS, add FREE=CLOSE to the //SMF DD to
               also free the allocation when the read is complete.      
                                                                        
Change 35.087  New ANALFTP analysis of FTP has five report examples:    
ANALFTP         GENERATE REPORTS FROM PDB                               
Apr 14, 2017    GENERATE REPORTS FROM SMF                               
                GENERATE REPORTS FROM SMF AND STORE DATA IN PDB         
                GENERATE REPORTS FROM SMF LOOKING FOR A USER            
                GENERATE REPORTS FROM SMF LOOKING FOR A DATASET         
               Reports are from TYPE119 records; see also ANAL119 and   
               ANALCNCR for additional reports.                         
                                                                        
                                                                        
Change 35.086  New variable FSBYTERATE='TRANSMISSION*BYTE*RATE' is added
VMAC119        to TY119070 dataset.                                     
ANALFTP                                                                 
Apr 13, 2017                                                            
                                                                        
Change 35.085  Possible exposure with too long a code line generated by 
VMXGPRNT       VMXGPRAL print with variable name and label as heading.  
Apr 13, 2017   With 32 character variable name and 40 character label,  
               the line generated could be 109 characters, exceeding the
               z/OS limit of 72 (S=72,S2=72).  Two lines are now created
               and the label truncated (no more than 5 lost) to trim if 
               needed.                                                  
                                                                        
Change 35.084  UTILCOPY failed if it found no datasets to copy with an  
UTILCOPY       undefined macro variable NUMMEM.  Now it tells you that  
Apr 10, 2017   it did not find anything to copy.                        
                                                                        
Change 35.083  DB2 Trace IFCID=316 dataset T102S316 variable QW0316TS is
VMAC102        now correctly converted to a datetime value.             
Apr 10, 2017                                                            
                                                                        
Change 35.082  Reserved Change Number                                   
Apr  2, 2017                                                            
                                                                        
Change 35.081  DB2ACCTP dataset, these "truncated" variables            
VMACDB2           QPACLOCN QPACCOLN QPACPKID QPACASCH QPACAANM          
Apr  2, 2017   were increased to $128 LENGTH, but the longer length text
               was not input when QPACOFFn was non-zero due to incorrect
               circumvention for prior invalid length in Change 31.015. 
   Thanks to Rachel Holt, Fidelity Systems, USA.                        
                                                                        
Change 35.080 *New z/OS 2.2 Changes found in Jan 2017 SMF Manual.       
VMAC30        -VMAC30.                                                  
Apr  1, 2017     New variable SMF30JF1='JOB/SESS*ID'                    
              *This change is incomplete.                               
                                                                        
Change 35.079  Some accumulated z/VM 6.3 SMT fields in VXSYTPRP dataset 
VMACVMXA       weren't deaccumulated, and the below new unaccumulated   
Mar 31, 2017   counters contain an error code '80'x in first bit when   
Apr  5, 2017   the counter cannot be populated that is now decoded and  
Apr 11, 2017   the first two instances of each error is printed on the  
FORMATS        SAS log, although there is nothing you can do for these  
               these error conditions, and the variable is set to a     
               missing value for these intervals.                       
                   SYTPRP_CAL_CAPBYTYPE    SYTPRP_CAL_MAXCAPBYTYPE      
                   SYTPRP_CAL_MTUTILBYCORE SYTPRP_CAL_MTUTILBYTYPE      
                   SYTPRP_CAL_PRODBYCORE   SYTPRP_CAL_PRODBYTYPE        
              -Dataset VXAPLSL0 was "hosed" because my loop was         
               DO CPUNR=1 TO NRCPUS, but first CPU is CPUNR=0, and      
               the CPUNR at the end of the segment had been overlooked. 
              -PFXPRKWT is now deaccumulated.                           
              -The VXAPLSLx dataset only has observations output when   
               there was activity by the Linux machine; the LINXTIME is 
               the "wake up" time in this interval and is used to create
               DELTALINXTM=MRHDRTOD-LINXTIME with the maxiumum duration 
               of an interval that that VMDUSER could have been active. 
              -These variables added to VXMTRSYS:                       
                RCCCCAPF RCCSCAPF SYSMTFLG RCCMTRSM RCCMTCFM RCCMTPMT   
                RCCMTTDW RCCMTFRS RCCCOMXT RCCCOALL                     
                CAL_RCCACMNT1-4='CPUTYPE-1-4*ACTIVATED*THREADS'         
                CAL_CPUTYPE1-4='CPUTYPE-1-4*CPU*TYPE'                   
                CAL_RCCSYMNT1-4='CPUTYPE-1-4*MAXIMUM THREADS*SOFTWARE'  
                CAL_RCCHWMNT1-4='CPUTYPE-1-4*MAXIMUM*THREADS*HARDWARE'  
                CAL_RCCCOMNT1-4='CPUTYPE-1-4*REQUESTED*THREADS'         
                CAL_RCCCRMNT1-4='CPUTYPE-1-4*REQUESTED*THREADS'         
                CAL_RCCSMMNT1-4='CPUTYPE-1-4*SPECIFIED*THREADS'         
              -These variables added to VXSYTCUP:                       
                LCXCMTIT='MT*IDLE*TIME'                                 
                LCXCHPCP='LPAR GROUP*ABS CAPACITY*CAP VALUE'            
                CALGCAPV='ABSOLUTE*CAP*AMOUNT'                          
              -Variable RDEVCTRG is removed from the DIDIO test to      
               create VXIODDEV because it is always non-zero and the    
               only non-zero field for non-DASD records.                
              -The SMT Busy Time calculation was revised to             
                LCXCMTBY=(2*LCUCACTM)-LCXCMTIT                          
   Thanks to Graham Harris, RBS, ENGLAND.                               
                                                                        
Change 35.078  If you specified SORTEDBY=YES and you run the daily and  
BLDSMPDB       weekly/monthly processing in the same SAS execution of   
Mar 31, 2017   BLDSMPDB the SORTEDBY= was ignored because VMXGSUM used  
               the same MACRO variable name making it a GLOBAL macro    
               variable to VMXGSUM and overriding the BLDSMPDB used     
               parameter.  NO data was lost - just not in the order     
               you may have expected. Circumvented by holding the       
               value in a LOCAL macro variable and the reinstating      
               it after DAILY processing is completed.                  
                                                                        
Change 35.077  Comments only.  Some enhanced comments in examples       
UTILBLDP       and a redundant WANTSMF in one example was removed.      
Mar 31, 2017                                                            
   Thanks to John Compton, WPS, ENGLAND.                                
                                                                        
Change 35.076  Some long RMF III variables have '00'x null characters   
VMACRMFV       instead of blanks at the end; they are converted to      
Mar 29, 2017   blanks.                                                  
                                                                        
Change 35.075  TYPE1415 records have subtype 5 segments for TAPE and all
FORMATS        datasets with a Data Class. For records without subtype 5
VMAC1415       the below flag variables are now set to 'FF'x and will   
Mar 29, 2017   print "NOT AVAILABLE" with new $MGNOTAV format:          
                  SMF14BFG SMF14FLGS SMF14FLG2 DEB2XUPF EADSCBOK        
                  DCBEEX31 XTIOTYES                                     
               Variable SMF14ALIAS will be blank and SMF14LBS will be a 
               missing value.                                           
   Thanks to Michael Oujesky, DTCC, USA.                                
                                                                        
Change 35.074 -INVALID SYTCPU segment messages with SEGLEN=48 and NRCPS 
EXXAMPRC       30 (SEGLEN should be 684) are valid and a problem is open
EXXMVPID       with Barton.                                             
FORMATS       -New VSIPID Process Segment creates XMVISPID dataset.     
IMACXAM       -New PRCCPU LIMPOOL Segment creates XAMSYPRC dataset, but 
VMACXAM        values for FLAGSPRC have '60'x for both limited cpuaffon.
VMXGINIT                                                                
Mar 28, 2017                                                            
                                                                        
Change 35.073  DB2ACCT variables QWACALOG and QWACALCT are now always   
VMACDB2        missing values; they have been reserved for years, but   
Mar 28, 2017   MXG code had still INPUT them causing confusion.         
   Thanks to Peter Gray, HPE Australia, AUSTRALIA.                      
                                                                        
====== Changes thru 35.072 are in this MXG 35.03 dated Mar 27, 2017=====
                                                                        
Change 35.072 -MXG 35.03. VMAC1415, hex dumps but no error, because     
VGETJESN       line 962 in VMAC1415  IF VOLSER NE VOLSER1 THEN LIST;    
VMAC1415       left from debugging needs to be deleted.                 
Mar 24, 2017  -WARNING TYPETASK NOT DECODED, JCTJOBID=A0000022 expected 
Mar 27, 2017   either 'ASCH' or 'OMVS' in to be stored in TYPETASK from 
               variable SUBSYS, but this task has SUBSYS blank. Now, if 
               SUBSYS is blank, TYPETASK='APPC' is stored.              
   Thanks to Paul Naddeo, Fiserv, USA.                                  
                                                                        
Change 35.071  Reserved Change Number.                                  
Mar 23, 2017                                                            
                                                                        
Change 35.070  New fields are added to zPROTECT SMF records:            
VMACZPRO       New variable in ZPROT05:                                 
Mar 23, 2017    ZPRRAUSR='ALTERNATE*USERID'                             
               New variable in ZPROT16:                                 
                ZPRTMINP='MIN*REQUEST*PERFORMANCE*TIME'                 
                ZPRTMAXP='MAX*REQUEST*PERFORMANCE*TIME'                 
                ZPRTAVGP='MEAN*REQUEST*PERFORMANCE*TIME'                
                ZPRTAUSR='ALTERNATE*USERID'                             
                ZPRNPROT='PROTECT*OPERATIONS'                           
                ZPRNACCE='ACCESS*OPERATIONS'                            
                                                                        
====== Changes thru 35.069 are in this MXG 35.03 dated Mar 22, 2017=====
                                                                        
Change 35.069  Support for CICS Version TS/5.4 Beta 11 adds three new   
UTILEXCL       variables to CICSTRAN:                                   
VMAC110          LPARNAME='LPAR*NAME'                                   
Mar 21, 2017     MPSRACT='TIMES WHEN*POLICY*EVALUATED*AND TRIGGERED'    
                 MPSRECT='TIMES WHEN*POLICY*RULES WERE*EVALUATED'       
   Thanks to Andy Wharmby, IBM CICS Hursley, ENGLAND.                   
                                                                        
Change 35.068  Support for MQ Version 9.1 SMF 115 new Subtype 201 record
EXTY115Y       creates new dataset:                                     
FORMATS           dddddd   dataset   description                        
IMAC115           TY115Y   MQ115201  MQ SUBTYPE 201 PAGESET STATS       
VMAC115        Mar 27: FORMATS MG115EX and MG115PS added.               
VMXGINIT                                                                
Mar 20, 2017                                                            
Mar 27, 2017                                                            
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.067 -Standalone execution failed because &PDBMXG.SMFINTRV     
SMFINTRV       needed to be &PDBMXG..SMFINTRV, but MXG invocations in   
Mar 14, 2017   BUILDPDB/BUILDPD3 were correct so no error there.        
Apr 18, 2017  -Three new interval START datetimes are created so you    
               can directly summarize to that interval by your choice of
                 START15INT='FIFTEEN*MINUTE*INTERVAL*START'             
                 START30INT='THIRTY*MINUTE*INTERVAL*START'              
                 STARTHRINT='HOUR*INTERVAL*START'                       
               Apr 11: Revised.  Those three variables are now created  
               by VMXGDUR, with the DEFAULT SMFINTSYNC59 "SYNC59" option
               defaulting to YES, to be consistent with RMFINTRV.       
               If your records are NOT "SYNC59", i.e., are written :00  
               use  %LET SMFINTSYNC59=NO;  in your //SYSIN.             
               Unlike other "INTRV" programs that invoke VMXGDUR to     
               create new summary datasets, SMFINTRV does NOT summarize 
               TYPE30_V records; instead it only combines the multiple  
               SMF 30 records (MULTIDD='Y' steps with LOTS of DDs) into 
               one observation per interval with all EXCPs totaled.     
               If you do want to summarize PDB.SMFINTRV across intervals
               the ANALSMFI program provides that example.              
                                                                        
Change 35.066  APAR OA59593 adds new flag variable                      
BUIL3005        SMF30CAS_INELIGHONOR='ELIG WORK*IS NOT*OFFLOADED*TO CP?'
BUILD005       to SMF 30 TYPE30_V/TYPE30_4/TYPE30_V datasets to identify
VMAC30         jobs whose eligible work was NOT offloaded to CPs for    
Mar 19, 2017   help.  The variable is also added to PDB.SMFINTRV and    
               PDB.STEPS datasets.                                      
                                                                        
Change 35.065  Almost "cosmetic": READDB2 could create dataset DB2STATR 
READDB2        even though you did not request it, due to Change 34.265 
Mar 14, 2017   that overlaid a token for DB2NETZA.  No obs were output. 
                                                                        
Change 35.064   SMT Mode corrections and enhancements.                  
VMAC7072       -ZIPACTTM in PDB.ASUMCELP is the best source of per-LPAR 
Mar 13, 2017    hardware zIIP CPU busy, created in BUILDPDB/ASUM70PR.   
                This change adds SMT_NUM to PDB.ASUMCELP to identify the
                SMT mode.                                               
               -Variable ZIPACTTM in PDB.TYPE70 could be too small for  
                an LPAR when in SMT_NUM=2; in rare cases the last LPAR's
                was not included.                                       
               -Correction for ZIPACTTM in TYPE70 also caused           
                  PLATBUSY LPARSHAC LPARSHAR TOTSHARC TOTSHARE          
                  ZIPSHARC ZIPSHARE LZIPSHAC LZIPSHAR                   
                to also be corrected/changed values in compares.        
               -TYPE70/TYPE70PR variables CPUID SMT_CORE_ID LCPUADDR and
                (new) SMT_THREAD are now formatted numeric HEX2. to     
                to match RMF reporting formats.                         
               -In the ASID TYPE30 and Service Class TYPE72GO data, the 
                recorded MT=2 CPUZIPTM/ZIPUNITS values are "inflated"   
                above the actual hardware zIIP time, and the hardware   
                equivalent can not be calculated using R723MCFS, the    
                Maximum Multi-Threading Capacity Factor.                
                  LPAR with 7 zIIP engines in SMT_NUM=2 MT=2 mode:      
                  UPTIME: 1:45  ZIPACTTM: 1:31  72-CPUZIPTM: 2:05 hh:mm 
                          105 min          91 min             125 min   
                  "Above Inflation Factor" 125/91=1.37                  
                  Interval R723MCFS              =1.17871               
                  "MCSF Equivalent zIIP CPU= 125/1.17871 = 106 min      
                but that is as large as the UPTIME of 105 minutes.      
                And IBM's range of R723MCFS values is 1.1 to 1.4,       
                with a theoretical max of 2.0.                          
                                                                        
                So: what to do?  Maybe Nothing. This is what is recorded
                now in SMF 30/72 records in MT=2 mode (AND ONLY in ASID 
                and SRVCLASS records): NO INFLATED VALUES IN RMF 70 SMF 
                data that are used for zIIP capacity metrics.  So, while
                the values are too large, their interval sum can be used
                to determine the proportion of the MT=2 zIIP usage for  
                each workload, job, or service class.                   
                                                                        
                Apr 10: IBM SMT folks have examined these data and have 
                confirmed my conclusions that the values are inflated.  
                August: IBM confirmed that at very high or very low util
                the SMT values are inflated; it's unclear if that will  
                ever change.                                            
                                                                        
                Daniel Rosa's available online 2015 SHARE paper "IBM z  
                Systems z13 Simultaneous Multi-Threading R(Evolution)"  
                discusses the MT=2 metrics.                             
                                                                        
                Jul 30, 2018: The CAPZIPRT can exceed 100% due to this  
                inflation of 30/72 CPUZIPTM when SMT Mode is enabled.   
                                                                        
Change 35.064A  Multi-Volume DCOLDSET records populate some fields only 
VMACDCOL        in the first (DCDVOLSQ=1) record. When TYPSDCOL program 
Mar 10, 2017    is used, these fields are retained from the first record
                and are now output in PDB.DCOLDSET.                     
               -Records with DCDVOLSQ=0 were created in WORK.TYPEDCOL   
                but were then not output in the first record logic, but 
                now they are output to PDB.DCOLDSET.                    
                                                                        
Change 35.063  -XAMSYS records with SYTCUP SEGLEN=148 but SYTNLPS=2 or 3
VMACXAM         are wrong, protected by changing SYTNLPS to 5 while the 
Mar 10, 2017    problem is opened with Barton now to resolve.           
               -XMTCPSYS dataset variable NAMENODE was blank because the
                128-byte CONTACT was reduced to 64, then NAMENODE, then 
                64 bytes are inserted to keep the original SEGLEN.      
   Thanks to Matthew L. Rennebohm, State of Wisconsin, USA.             
                                                                        
Change 35.062  Support for Mainview for CICS CMRDETL file VER 6700      
VMACMVCI       changes that caused INPUT STATEMENT EXCEEDED error.      
Mar  6, 2017                                                            
   Thanks to DJ Chen, AST/Southwood Shared Resource Center, USA.        
                                                                        
Change 35.061  Enhancement for PDB.ASUMCELP (per-LPAR CEC data) adds the
VMXG70PR       variable SMT_NUM to identify the SMT Mode of zIIPs, from 
Mar  7, 2017   the PDB.TYPE70EN dataset, and protection if that dataset 
               was not copied to the PDB data library. SMT_NUM will be a
               missing value for PHYSICAL and IFL-Only LPARS, or LPARS  
               with no zIIPs.                                           
                                                                        
Change 35.060  Enhancement for SMF 120 Subtype 11 TYP120BL new variables
VMAC120        containing TOTAL, CP ONLY, and ZIP ONLY CPU times:       
Mar  5, 2017     SM120BCPUTM='TOTAL*CPUTIME*USED*BCA1-BBZ1'             
                 SM120BCPCPUTM='CP ONLY*CPUTIME*USED*BCA2-BBZ2'         
                 SM120BZIPCPUTM='ZIP ONLY*CPUTIME*USED'                 
               are calculated, thanks to the IBM WebSphere Developer who
               educated me that the 16-byte binary TIMEUSED format used 
               in this record for the START and END Accumulated CPU data
               contains two 8-byte CPU times: the TOTAL CP+ZIIP in the  
               first 8 bytes and the CP ONLY CPU time in the second 8.  
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.059  Support for CA SYSVIEW for IMS 14.0 update in 2014 Change
VMACSVIE       32.170 has now been tested with actual data, and these   
Mar  4, 2017   variables had missing values that are now corrected.     
Mar 27, 2017    IMTR_CLK_SUBQ06_TIME IMTR_CLK_MPP_CPU IMTR_CLK_SMB_ENQ  
                IMTR_CLK_CNT_ENQ     IMTR_CLK_MXG_END IMTR_CLK_CNT_GU   
                IMTR_CLK_UOW_END     IMTR_CLK_UOW_START                 
                IMTR_CLK_SCHEDULE_TIME                                  
               -Mar 23: Several TODSTAMP variables were not converted   
                from GMT to local time zone.                            
   Thanks to Denise Williers, Wipro, USA.                               
                                                                        
Change 35.058  Support for IMS LOG 67D0 DIAGNOSTIC RECORD for DC '02'x  
EX67D002       created new IMS67D002 dataset.  Note that both D0TIME and
FORMATS        IMSSTCK are both GMT because there is no GMT offset in   
IMACIMS        the 67D0 log record.                                     
VMACIMS                                                                 
VMXGINIT                                                                
Mar  2, 2017                                                            
   Thanks to Rosa Maria Martinez Alonso, Bustia, SPAIN.                 
                                                                        
Change 35.057  Reserved Change.                                         
Mar  1, 2017                                                            
                                                                        
Change 35.056 -If you used KEEPMNTH= (very rare) an MDY() could fail.   
VMXGSUM       -If your INCODE= contains a DATA step, the CLASSNWAY      
Mar  1, 2017   option failed, but now a DATA step's existence in the    
               INCODE is parsed, and if found, SUMBYCLASS is reset.     
                                                                        
Change 35.055  Support for Mainview for IP PTF BPN2331 that adds        
VMACMVIP       variable TNDSTATX='CONNECTION*STATE*ACTIVE*CLOSED?'      
Mar  1, 2017   variable to the I490 dataset.                            
                                                                        
Change 35.054 -RMF Monitor III enhancement for OPD (OMVS Process Data)  
ADOCRMFV       table character data filtering and usability.            
ASMRMFV       -These filters are intended for building ad hoc MXG RMF   
VMACRMFV       III PDBs for studies avoiding the overhead of generating 
Mar  1, 2017   a full OPD table-based PDB.  They control which OPD table
               entries are output to the RMFBSAM file.                  
              -Five new filters are added to support OPD entry selection
               from this table to the RMFBSAM output file.  These       
               filters are effective only if the OPD table is selected. 
                                                                        
               They are applied in the order shown when multiple        
               different keywords are used.                             
                                                                        
               New Keyword    Aliases                                   
               ------------   ------------------------------------------
               OPDPROCNAME=   OPDPROCNA=, OPDPROCNM=, OPDPROC=, OSDPROC=
                              OPDPN=                                    
               OPDJOBNAME=    OPDJOBNA=,  OPDJOBNM=,  OPDJOB=,  OPDJN=  
               OPDUSERNAME=   OPDUSERNA=, OPDUSERNM=, OPDUSER=, OPDUN=  
               OPDAND         None                                      
               OPDOR          None                                      
                                                                        
               The order of OPD filter application is:                  
               1) OPDPROCNAME=                                          
               2) OPDJOBNAME=                                           
               3) OPDUSERNAME=                                          
                                                                        
              -TUTORIAL:                                                
               Ranges of the form keyword=first:last may be used with   
               any of the above keywords except OPDAND and OPDOR.       
               The colon character ':' is required for a paired range   
               specification.  All entries GE the first value and LE the
               last value are selected for output to the RMFBSAM file.  
               The first value may not exceed the last value in EBCDIC  
               collating sequence or an error is flagged.               
               Single unpaired values may be specified for a range      
               simply as keyword=first and in this case the colon ':' is
               omitted.                                                 
               Patterns may also be used with any of the above keywords 
               except OPDAND and OPDOR and include one or more Wild Card
               characters to match the respective OPD data field.       
               A pattern contains one or more special Wild Card         
               characters as follows:                                   
                 Wild                                                   
                 Card   Matches                                         
                 ----   ------------------------------------------------
                 *      0 or more characters                            
                 %      1 Non-blank character                           
                 +      1 Numeric character (0-9)                       
                 _      1 Alphabetic character or _  (a-z, A-Z, _)      
                 .      1 National character (@, #, $)                  
                 !      1 Special character (not a-z, A-Z, 0-9, @, #, $)
                 ?      A blank string if used by itself                
                 ?      1 Blank character (X'40') if used with any other
                          characters                                    
               Ranges may not be wild carded.  If wild carded the range 
               value becomes a pattern instead and is processed as such.
               See Section 25 "Ranges and Patterns" in the ADOCRMFV     
               member or ASMRMFV source code for more details on usage  
               of ranges and patterns.                                  
              -OPDPROCNAME= selects OPD tables by 1-8 character z/OS JCL
               Procedure Name.  Proc Name characters are validated to   
               those allowed by JCL syntax.  Both ranges and patterns   
               with wild cards may be specified.  Up to 16 ranges and 16
               patterns are supported.  The default is OPDPROCNAME=ALL. 
               NOTE: There is only ONE OSDPROC field per OPD table.  If 
               the OPDPROCNAME= value does not match, then the ENTIRE   
               OPD table with all entries is excluded.  Use OPDPROCNAME=
               with care and discretion and only if the OSDPROC contents
               are well understood.  Almost always OSDPROC is simply    
               'OMVS'.                                                  
              -OPDJOBNAME= selects OPD entries by 1-8 character z/OS    
               Job Name.  Job Name characters are validated to those    
               allowed by JCL syntax.  Both ranges and patterns with    
               wild cards may be specified.  Up to 32 ranges and 32     
               patterns are supported.  The default is OPDJOBNAME=ALL.  
               Job Names must be 1-8 characters in length and may       
               include any characters A-Z, #, $, or @.  Numeric digits  
               (0-9) may be used only after the first character.        
              -Examples for OPDJOBNAME= :                               
               OPDJN=PROD1234:PROD5678 selects only address spaces with 
               a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a     
               range.  Note use of the keyword alias OPDJN for coding   
               convenience.                                             
               OPDJOBNAME=.* is a pattern that selects only address     
               spaces with a Job Name that begins with a national       
               character.                                               
               OPDJOBNAME=*++ is a pattern that selects only address    
               spaces with a Job Name that ends with 2 numeric digits.  
               OPDJOBNAME=ABC:ABC88888 is a range that selects only     
               address spaces with a Job Name that is GE 'ABC     ' and 
               LE 'ABC88888'.                                           
              -OPDUSERNAME= selects OPD entries by 1-8 character z/OS   
               User Name.  User Name characters are validated to those  
               allowed by JCL syntax.  Both ranges and patterns with    
               wild cards may be specified.  Up to 32 ranges and 32     
               patterns are supported.  The default is OPDUSERNAME=ALL. 
               User Ids must be 1-8 characters in length (1-7 characters
               for TSO Ids) and may include any characters A-Z, #, $, or
               @.  Numeric digits (0-9) may be used only after the first
               character.                                               
              -Examples for OPDUSERNAME= :                              
               OPDUSERNAME=JOE8888 selects only address spaces with a   
               login User Name of 'JOE8888'.                            
               OPDUSERNAME=JOE:JOE8888 selects only address spaces with 
               a login User Name that is GE 'JOE' and LE 'JOE8888'.     
               OPDUSERNAME=.* selects only address spaces with a login  
               User Name that begins with a national character (@, #,   
               $).                                                      
               OPDUSERNAME=*++ selects only address spaces with a login 
               User Name that ends with 2 numeric digits (00-99).       
              -OPDAND (default) indicates that selection results from   
               the two different OPD filter keywords are logically      
               ANDed.                                                   
              -OPDOR indicates that selection results from the two      
               different OPD filter keywords are logically ORed.        
               Example 1 with OPDAND in effect:                         
               OPDJOBNAME=ABC*     OPDUSERNAME=SAM*                     
               only selects Address Spaces in the RMF Monitor III       
               OPD table that have a Job Name starting with 'ABC'       
               AND a User Name beginning with 'SAM'.                    
               Otherwise the Address Space is filtered and will NOT     
               appear in the result MXG PDB.                            
               The logical AND results in more restrictive              
               filtering because 2 conditions must be met for an        
               OPD entry to be selected.                                
                                                                        
               Example 2 with OPDOR in effect:                          
               OPDJOBNAME=ABC*     OPDUSERNAME=SAM*                     
               selects Address Spaces in the RMF Monitor III OPD table  
               that have a Job Name starting with 'ABC' OR a User Name  
               beginning with 'SAM'.                                    
               If the Address Space does not match either selection it  
               is filtered and will not appear in the result MXG PDB.   
               The logical OR results in less restrictive filtering than
               Example 1 above because any of the 2 conditions results  
               in data selection of an OPD entry.                       
              -The JOBNAME= (alias JOB=) keyword for multi-table        
               selection is expanded to include job names from the OPD  
               table as well as the ASI and CSR tables.  This is a      
               convenience feature to avoid having to code the Job Name 
               parameter three times when the same job names from all   
               three tables are of interest.                            
              -The ASI, CSR, and OPD tables must all be selected for the
               JOBNAME= multi-table selection keyword to function       
               completely.  Otherwise only entries from selected tables 
               are filtered.                                            
               Note that most RMF III tables do not contain common      
               character data fields, but in this case the ASI, CSR, and
               OPD tables all do contain a Job Name.                    
               JOBNAME= Examples:                                       
               JOBNAME=ABC88888 selects only address spaces with a Job  
               Name of 'ABC88888' in either ASI, CSR, or OPD tables and 
               is equivalent to coding:                                 
               ASIJOBNAME=ABC88888                                      
               CSRJOBNAME=ABC88888                                      
               OPDJOBNAME=ABC88888                                      
               JOBNAME=ABC:ABC88888 selects only address spaces with a  
               Job Name that is GE 'ABC' and LE 'ABC88888' in either    
               ASI, CSR, or OPD tables and is equivalent to coding:     
               ASIJOBNAME=ABC:ABC88888                                  
               CSRJOBNAME=ABC:ABC88888                                  
               OPDJOBNAME=ABC:ABC88888                                  
               JOBNAME=.* selects only address spaces with a Job Name   
               that begins with a national character in either ASI, CSR,
               or OPD tables and id equivalent to coding:               
               CSRJOBNAME=.*                                            
               OPDJOBNAME=.*                                            
              -Some RMFV001I Execution Environment messages have been   
               reformatted to include DFSMS/MVS version, CPC Name, LPAR 
               Name (if not a VM Guest), or VM Userid (if a VM Guest).  
               TIOT statistics are now grouped on the same message line.
              -The Creation date was not valid when non-VSAM data set   
               was incorrectly provided as a RMF III data set.  CRDATE  
               is removed from the RMFV008I message in this case.       
              -The MXG00 record version is raised to x'07' from x'06'.  
               New fields added to the MXG00 record are:                
               IPL timestamp in LOCAL and GMT time                      
               IPL volume serial                                        
               TIOT size in K and bytes                                 
               TIOT maximum and used entries                            
               CPC Name, LPAR Name, and VM UserId                       
               DFSMS/MVS level                                          
              -Several documentation Sections are updated to support    
               the above changes:                                       
               Section  5 "Input Data Selection Parameters"             
               Section 12 "Messages"                                    
               Section 13 "Filtered Records"                            
               Section 25 "Ranges and Patterns"                         
               Section 30 "Summary"                                     
              -VMACRMFV was updated to add new variables to ZRBASM:     
                 ASMDFLVL='EXECUTION*DFSMS/MVS*LEVEL'                   
                 ASMOPNRX='MAXIMUM*OPDPROCNAME*RANGES'                  
                 ASMOPNPX='MAXIMUM*OPDPROCNAME*PATTERNS'                
                 ASMOJNRX='MAXIMUM*OPDJOBNAME*RANGES'                   
                 ASMOJNPX='MAXIMUM*OPDJOBNAME*PATTERNS'                 
                 ASMOUNRX='MAXIMUM*OPDUSERNAME*RANGES'                  
                 ASMOUNPX='MAXIMUM*OPDUSERNAME*PATTERNS'                
                 ASMOJNRS='SIZE*OPDJOBNAME*RANGE*TABLE'                 
                 ASMOJNPS='SIZE*OPDJOBNAME*PATTERN*TABLE'               
                 ASMOPNRS='SIZE*OPDPROCNAME*RANGE*TABLE'                
                 ASMOPNPS='SIZE*OPDPROCNAME*PATTERN*TABLE'              
                 ASMSPGAO='SPG*MULTI*FILTER*LOGIC*I/O?'                 
                 ASMSINDD='SYSIN/SYSINA*DCB*DDNAME'                     
                 ASMVFREE='FREE=CLOSE*OPTION?'                          
                 ASMSINMG='SYSIN*MEMBER*OR*GENERATION'                  
                 ASMOUNRS='SIZE*OPDUSERNAME*RANGE*TABLE'                
                 ASMOUNPS='SIZE*OPDUSERNAME*PATTERN*TABLE'              
                 ASMIPLTL='LAST IPL*LOCAL*TIME'                         
                 ASMIPLTG='LAST IPL*GMT*TIME'                           
                 ASMTIOTB='MAXIMUM*TIOT SIZE*BYTES'                     
                 ASMTIOTK='MAXIMUM*TIOT SIZE*IN K'                      
                 ASMTIOTX='MAXIMUM*TIOT*ENTRIES'                        
                 ASMTIOTU='CURRENT*TIOT*ENTRIES*IN USE'                 
                 ASMCPCNM='CPC*NAME'                                    
                 ASMLPARN='LPAR*NAME'                                   
                 ASMVMUID='VM*USERID'                                   
                 ASMIPLVL='IPL*VOLUME*SERIAL*NUMBER'                    
                                                                        
Change 35.053  SYSOTHER checking is enhanced.  Test for CPUTM NE 0 added
VMXGRMFI       to SYSOTHER detection, since if the CPUTM is 0 it cannot 
Feb 28, 2017   impact totals, but workload names and descriptions are   
               identified so you can find the culprit, since nothing    
               should ever fall thru to Service Class SYSOTHER.         
                                                                        
Change 35.052  DATETIME syntax was revised per change 35.022, although  
TRNDVMXA       the new VMXGSUM correctly supported the old syntax with  
Feb 28, 2017   no error.                                                
                                                                        
Change 35.051  Support for Liberty 17.0.0.1 SMF 120 Subtype 12 COMPAT   
VMAC120        enhancements, adds these variables to TYP12012 dataset:  
Feb 28, 2017     SM120CDO='REFERENCE*TYPE' MG120CD format decodes:      
                       1='1:READER'                                     
                       2='2:PROCESSOR'                                  
                       3='3:WRITER'                                     
                       4='4:CHECKPOINT'                                 
                       5='5:BATCHLET'                                   
                       6='6:PARTITION_MAPPER'                           
                       7='7:PARTITION_REDUCER'                          
                       8='8:PARTITION_COLLECTOR'                        
                       9='9:PARTITION_ANALYZER'                         
                      10='10:DECIDER'                                   
                 SM120CDU='PHYSICAL*CPU*ADJUSTMENT*RCTPCPUA'            
                 SM120SU_SEC='CPU*RATE*ADJUSTMENT*RMCTADJC'             
                 SM120CDW='REPOSITORY*TYPE*JPA* OR MEM'                 
                 SM120CDX='JOB*STORE*REF*ID'                            
                 SM120CDY='SM120CDY*FLAGS'                              
                Next six variables are only valid in step end record    
                 SM120CDZ='STEP*START*LIMIT'                            
                 SM120CEA='CHUNK*STEP*CHECKPOINT*POLICY' decodes:       
                       0='0:ITEM'                                       
                       1='1:CUSTOM'                                     
                 SM120CEB='CHUNK*STEP*ITEM*COUNT'                       
                 SM120CEC='CHUNK*STEP*TIME*LIMIT'                       
                 SM120CED='CHUNK*STEP*SKIP*LIMIT'                       
                 SM120CEE='CHUNK*STEP*RETRY*LIMIT'                      
                                                                        
Change 35.050  PDB.ASUMCELP REQUIRES SMF 70s from ALL SYSTEMs to be read
VMXG70PR       to correctly populate all variables.  Each SMF 70 record 
Feb 27, 2017   contains a "This System" segment that populates TYPE70,  
               and an "LPAR Segment" for each LPAR, for TYPE70PR, so the
               LPAR data can be reported & summarized from a SMF 70 from
               only one system, but then all the "This System" variables
               are wrong, notably, SMF70LAC, the IBM 4HR AVG MSU, which 
               will contain ONLY the MSU from the one "This System".    
               This change compares TYPE70 and TYPE70PR to detect if    
               there are missing TYPE70 or TYPE70PR data, printing a    
               a PROC FREQ with missing systems identified, and printing
               a log message that SMF70LAC will be wrong.               
                                                                        
Change 35.049  Support for MAINVIEW FOR IMS 5.3 a/k/a IMF or CIMS which 
VMACCIMS       COMPATIBLY added these variables to the CIMSTRAN dataset:
Mar 12, 2017     TRNMSYS ='MQ*REMOTE*SYSTEM*NAME'                       
                 TRNDSYS ='DB2*REMOTE*SYSTEM*NAME'                      
                 TRNFLTRD='SOME*CALLS*NOT TRACED*FILTERS?'              
                 TRNPRELD='PGM*WAS*PRELOADED'                           
                 TRNINFL ='TRN WAS*CAUGHT*INFLIGHT'                     
               Was reserved change number until Sep 23, 2018            
                                                                        
Change 35.048  Support for IWS Version 9.3, a/k/a TWS and was OPC, which
VMACOPC        replaces subtype 23 with new subtype 66 with the original
Feb 24, 2017   variables plus these four new variables                  
                 TRLDURS23='DURATION'                                   
                 TRLOID23 ='OPERATION*ID'                               
                 TRLOLDST23='OLD*STATUS'                                
                 TRLREADY23='START*DATETIME*WAIT*OPR'                   
               The new subtype 66 record is output in the OPC23 dataset 
               so your reports won't have to be changed.                
   Thanks to Teuvo Virsu, TIETO,                                        
                                                                        
Change 35.047  Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.    
VMAC102                                                                 
Feb 24, 2017                                                            
                                                                        
Change 35.046  Support for IFCID 125 Truncated Package Collection and   
FORMATS        Package Name fields, and new variables for Runtime       
VMAC102        Adaptive Index in T102S125 dataset:                      
Feb 20, 2017     QW0125TI='INDEX*PROBING*RIDS IN*INDEX'                 
                 QW0125QI='INDEX*PROBING*RIDS*IN*KEYRANGE'              
                 QW0125_TRSN='REASON*LEG*WAS*TERMINATED?'               
                 QW0125_PRSN='REASON*LEG*NOT*PROBED?'                   
                 QW0125_ORSN='REASON*LEG*WAS*REORDERED?'                
                 QW0125_FRSN='REASON*LEG*WAS*MARKED FULL?'              
                                                                        
Change 35.045  ANALDB2R variable QWHSRELN format expanded from 3.1 to   
ANALDB2R       4.1 to print full 10.1 Release value in reports.         
Feb 20, 2017                                                            
                                                                        
Change 35.044 -The new ZRBCPU SMT Multithreading variables were always  
VMACRMFV       missing due to an invalid MXG test for LENLEFT.          
Feb 20, 2017  -New variables found in the Dec 2016 Programmers Guide:   
               Dataset ZRBCPU:                                          
                 CPC_CECNAME='CPC*CEC*NAME'                             
                 LPARHWGR='LPAR*HW*GROUP*NAME'                          
               Dataset ZRBLCP:                                          
                 LCPUHWLW='HW*GROUP*CAP*LIMIT'                          
                 LPARHWGR='LPAR*HW*GROUP*NAME'                          
              -APAR OA58688 adds these new fields.                      
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.043  SMF74NID, the Network ID, contains 26 EBCDIC and 2 hex   
VMAC74         bytes that don't "print pretty".  Variable SMF74NIDTWO   
Feb 20, 2017   keeps those two bytes, formatted $HEX4. for printing.    
   Thanks to Pierre Pascal Joulin, Societe Generale, FRANCE.            
                                                                        
Change 35.042  Sample code that creates charts of resource group CPU    
GRAFCAPS       usage and capping.                                       
Feb 17, 2017                                                            
                                                                        
Change 35.041  DCOLLECT format MGDCOSG adds new 6='6:COPYPOOL' value to 
FORMATS        map that value in variable DSGFTYPE.                     
Feb 17, 2017                                                            
   Thanks to J. Alan Gray, CareFirstBlueCrossBlue Shield, USA.          
   Thanks to Stanley M. Helms, CareFirstBlueCrossBlue Shield, USA.      
                                                                        
Change 35.040A IBM APAR OA51325 corrects invalid SMF 15 record missing  
VMAC1415       the UCB segment causing VOLSER to be truncated to two    
Feb 17, 2017   characters.  No code change to support the corrections.  
                                                                        
Change 35.040  Support for Velocity Software ZWRITE file z/VM MONWRITE  
VMACVMXA       records which have a new BEGINMTR value for each (hour)  
VMXGINIT       period, which caused the first interval of each (hour) to
Feb 15, 2017   be lost, because normal MONWRITE records have a single   
               BEGINMTR value for each file.  But the ZWRITE records are
               contiguous in spite of changed BEGINMTR, so this support 
               is enabled with   %LET MXGZWRITE=YES;  in SYSIN  which   
               will set BEGINMTR only from the first instance so only   
               the very first interval is lost per day.                 
                 // EXEC MXGSASV9                                       
                 //VMINPUT DD DSN=YOUR.ZWRITE.MONWRITE.DATA,DISP=SHR    
                 //PDB     DD DSN=YOUR.ZWRITE.PDB,DISP=OLD              
                 //SYSIN   DD *                                         
                   %LET MXGZWRITE=YES;                                  
                   %INCLUDE SOURCLIB(VMACVMXA,IMACKEEP);                
                    _TESTVM   /*READS VMINPUT */                        
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.039  MQMQUEUE variable WQQTYPE is mapped by MG116QT format    
FORMATS          VALUE  MG116QT                                         
VMAC116          1='1:LOCAL'                                            
Feb 15, 2017     2='2:MODEL'                                            
                 3='3:ALIAS'                                            
                 6='6:REMOTE'                                           
                 7='7:CLUSTER'                                          
              -GMTOFF116 calculation revised correcting occasional      
               missing values in WQCLOSTI, WQOPENTI, and WQTTTIME.      
               (WQCLOSTI can be validly missing).                       
              -APAR PI70580 corrects invalid WQBASENA variable values,  
               which seem to occur in every second segment in each      
               SMF record, but other segment's values are valid.        
   Thanks to Raymond Smith, Optum TECH, USA.                            
   Thanks to Pietro Rosella, Canadian National Rails, CANADA            
                                                                        
Change 35.038  MXG 34.04 added PROC DELETE DATA=:CIC after PDB.CICINTRV 
CICINTRV       had been created, intending to delete ONLY CICS Stats    
VMXGCICI       datasets to free up //WORK space for subsequent use, but 
Feb 14, 2017   if CICINTRV was intentionally left in //WORK, it was then
               unintentionally deleted by that colon modifier, and ITRM 
               expected it to be left in WORK as it had been previously.
               Since no one had actually asked for this cleanup, it has 
               been removed from VMXGCIC.  But, added at the bottom of  
               the CICINTRV member, inside a comment block, is the code 
               to delete all of those CICS Stats, if you do wish to.    
   Thanks to Don Barnard, North Carolina State Government, USA.         
   Thanks to Chris Weston, SAS Institute ITRM, USA.                     
                                                                        
Change 35.037  ASUMDB2P expected variables QPACDBRM/QPACPACK would be   
ANALDB2R       populated, but those bits were removed in DB2 V10, so now
ASUMDB2P       PACKTYPE is blank.                                       
Feb 14, 2017  -ANALD2R was not correctly rolling up the control break   
               totals in the Accounting SHORT report.                   
                                                                        
Change 35.036  VMXGSUM will now tell you with an MXGNOTE when it cannot 
VMXGSUM        use CLASS NWAY and why it cannot.  There are two cases:  
Feb 11, 2017     - Use of DESCENDING in the SUMBY                       
                 - same dataset name for input and output and no OUTCODE
                   specified                                            
               It will also now display the final setting of SUMBYCLASS.
   Thanks to Tim Hare, Southwood Shared Resource Center, USA.           
                                                                        
====== Changes thru 35.035 are in this MXG 35.02 dated Feb 10, 2017=====
                                                                        
Change 35.035  Protection for Invalid TPX Subtype 7 record with Segment 
VMACTPX        TPX07LEN=93 but only 44 bytes remain in the record. MXG  
Feb 10, 2017   silently deleted the record, because of prior invalid 07x
Feb 14, 2017   causing zero obs in TPXAPLON Logon dataset. The first 44 
               are now INPUT, and the remainder conditionally input.    
              -Feb 14: Correction for undocumented 8 byte insert        
               in '06' and a blank in TPXSNAME.                         
              -Feb 14: Each pair of subtype 01 TPXSTART records have the
               same SMF time, but the second record is a continuation of
               the first record, which is not supportable; a problem    
               report will be opened with TPX Support.                  
              -TPX PTFS R088919 and R085818 correct some errors, while  
               CA Fix TR95030 corrects the bad subtype 1 records which  
               turned out to subtype 2 records with wrong subtype.      
   Thanks to Scott Wiig, USBank, USA.                                   
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 35.034  Support for the BBMQ large segment record structure that 
VMACBBMQ       are created by the BMC BBM9MD73 utility program that     
Feb 10, 2017   extracts the records from the history file for TYPEBBMQ  
               to then process.   Both old and new format records are   
               supported with this change and there were no changes to  
               the MXG datasets.                                        
                                                                        
Change 35.033  Logic to determine the begin/end of month was robusted   
VMXGALOC       and non-zero length MNTHKEEP will always display the     
Feb  9, 2017   MONTH Libname value.                                     
                                                                        
Change 35.032  Documentation Only.  DCOLLECT records can contain the JOB
VMACDCOL       and STEP and the TIME of the Creating JOB for DISP=NEW   
Feb  9, 2017   datasets, but the EATTR option must be specified either  
               in the DATACLASS definition or with a DD statement.      
   Thanks to Paul Newton, IBM RDP Dallas, USA.                          
                                                                        
Change 35.031  Variable S42DSIOS='RW TO*METRO*MIRROR*SECONDARY' is added
VMACDB2        to dataset TYPE42DS, having been overlooked.             
Feb  9, 2017                                                            
   Thanks to Stephen Hoar, Lloyds Banking, ENGLAND                      
                                                                        
Change 35.030  DB2 statistics dataset DB2STAT4 QW0225_LMWRITE_REAL and  
VMACDB2        _QW0225_LMCTYRL_REAL were incorrectly very large due to  
Feb  7, 2017   a 4-byte misalignment.                                   
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.029  RACF SMF70DTP/RACFTYPE=6 segment was increased in length 
VMAC80A        from 124 to 136 but had not been protected for a change. 
Feb  7, 2017   Three additional keyword variables  ADDLKEY1-ADDLKEY3    
               are added to TYPE8010 and TYPE8013 datasets.             
   Thanks to Coen Wessels, GTS Infrastructure, SWITZERLAND.             
                                                                        
Change 35.028  Support for RMF III dataset ZRBENC new "long name" fields
ASMRMFV        that were added by z/OS 2.1 but not captured by ASMRMFV. 
VMACRMFV       Variables EDEPCKG EDEPROC EDEUSER EDETRXN ECEACCT were   
Feb  6, 2017   increased in length and these new variables are kept:    
                  EDESCHEDENV         ='SCHEDULING*ENVIRONMENT*NAME'    
                  EDESCHEDENVLN       ='S E NAME LENGTH'                
                  EDESUBSYSCOLLECT    ='SUBSYSTEM*COLLECTION*NAME'      
                  EDEPCKGLN           ='PACKAGE*NAME*LENGTH'            
                  EDEPROCLN           ='PROCEDURE*NAME*LENGTH'          
                  EDECLIENTIPADDR     ='CLIENT*IP*ADDRESS'              
                  EDECLIENTIPADDRLN   ='CLIENT*IP*ADDRESS*LENGTH'       
                  EDEUSERLN           ='CLIENT*USERID*LENGTH'           
                  EDETRXNLN           ='CLIENT*TRANSACTION*NAME*LENGTH' 
                  EDECLIENTWRKSTATION ='CLIENT*WORKSTATION'             
                  EDECLIENTWRKSTALN   ='CLIENT*WORKSTATION*LENGTH'      
                  EDEACCTLN           ='CLIENT*ACCOUNT*LENGTH'          
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.027  Support for DB2 NETEZZA DB2ACCT Q8AC Accumulated fields: 
IMACDBNZ         Q8ACINSC='INSERT*STATEMENTS*SENT TO IDAA*FROM DB2'     
Feb  6, 2017     Q8ACUPDC='UPDATE*STATEMENTS*SEND TO IDAA*FROM DB2'     
                 Q8ACDELC='DELETE*STATEMENTS*SEND TO IDAA*FROM DB2'     
                 Q8ACDRPC='DROP*STATEMENTS*SEND TO IDAA*FROM DB2'       
                 Q8ACCRTC='CREATE*STATEMENTS*SEND TO IDAA*FROM DB2'     
                 Q8ACCMTC='COMMIT*STATEMENTS*SEND TO IDAA*FROM DB2'     
                 Q8ACRBKC='ROLLBACK*STATEMENTS*SEND TO IDAA* FROM DB2'  
                 Q8ACOPNC='OPEN*STATEMENTS*SEND TO IDAA*FROM DB2'       
                 Q8ACROWI='ROWS*INSERTED*TO IDAA*BY DB2'                
                 Q8ACROWU='ROWS*UPDATED*ON IDAA*BY DB2'                 
                 Q8ACROWD='ROWS*DELETED*ON IDAA*BY DB2'                 
                 Q8ACROWC='ROWS*RETURNED*BY IDAA*TO DB2'                
               These variables are output in DB2ACCT, but they appear   
               to be defective, as they are supposed to be ACCUMULATED  
               but the 2012 and 2013 test data I have has breaks in the 
               expected monotonic increase, so if you are interested in 
               these fields, please send current SMF 101 data so I can  
               investigate if the accumulation is now valid.            
                                                                        
Change 35.026  If MXG detects Service Class Name of SYSOTHER, error msgs
UTILRMFI       are printed when SMF 72 records are processed. SYSOTHER  
Feb  1, 2017   should never happen; it is the fall thru service class   
               when WLM can't classify work and runs at the lowest DPRTY
               in MTTW mode, and thus should NOT ever happen! Now, when 
               UTILRMFI is run to examine the problem, it will also read
               the PDB.SMFINTRV or PDB.TYPE30_4 dataset to find what    
               tasks were classified into SYSOTHER, reporting JOB name, 
               READTIME, JESNR, and SRVCLASS and RPTCLASS. If there are 
               type 30 records they will be reported but there may not  
               be any, if no tasks actually went to the service classes,
               or the workload is one where there is no type 30 record  
               (e.g., DDF). All workloads in your WLM classification    
               rules should have a default service class SPECIFIED:     
              -Unclassified work will default to one of two places      
                - Started Tasks default to SYSSTC                       
                - All other work defaults to SYSOTHER                   
               Neither is a good choice.  SYSSTC runs at very high DP   
               and SYSOTHER runs at very LOW DP. While very low may be  
               appropriate for workloads you do not know, very high is  
               almost certainly not.                                    
              -Reports 1 thru 3 already exist.                          
              -Report 4 is added to give you the job names, read times  
               jes numbers, service and report class where the service  
               class is SYSOTHER, from 30_4 and SMFINTRV.               
              -Report 5 is added to show you any DB2ACCT records that   
               may have landed in SYSOTHER as they may not be in a type 
               30 record.                                               
              -Report 6 is added to show you all tasks falling into     
               SYSSTC, from 30_4, SMFINTRV and 30_6.                    
              -Report 7 is added as a table of CPU consumption by       
               service class and system, from TYPE72GO.                 
              -Report 8 is added as a table of CPU consumption          
               by report class and system from TYPE72GO.                
                                                                        
Change 35.025  Using the _VMINPUT macro to read VB z/VM MONWRITE data   
VMACVMXA       incorrectly set the length of VMDUSER to only one byte.  
Feb  1, 2017                                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 35.024  SMF 120 Subtype 9 variables SM1209EV/EW/SM1209FI are not 
VMAC120        kept. In TYP1209U detail dataset, they are output either 
Feb  3, 2017   in new variables SM1209xxEJBDET or SM1209xxWEBDET, and in
               datasets TYP1209R and TYP1209N they are summed and output
               in SM1209xxEJB and SM1209xxWIB variables.                
               The TIME format was removed from the EW count variables. 
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.023  MXG 35.01. If UTILEXCL executed with //PDB DD DISP=OLD,  
UTILEXCL       only the NEW dictionary records read from SMF are used   
Jan 29, 2017   to create the IMACEXCL, and old dictionary records are   
               lost; only the new records are output in PDB.CICSDICT.   
                (The step DATA _LCICDIC; SET _WCICDIC; to add the LABEL 
                 was changed to SET _LCICDIC to correct this error.)    
   Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA 
                                                                        
Change 35.022  ANCIENT syntax of DATETIME in SUMBY in user tailored     
VMXGSUM        invocation of VMXGSUM (pre MXG Version 21 example!) can  
Jan 29, 2017   cause VMXGSUM, which is used EXTENSIVELY internally in   
               MANY MXG members, to fail, sometimes with only a message 
               WARNING: VARIABLE QWACBSC ALREADY EXISTS ON WORK.MXGSUM3 
               or it can ABEND with ERROR FUNCTION COMPBL TOO FEW ARGS. 
               Only three sites reported the error with MXG 35.01/34.34.
               Primary exposure was this syntax,                        
                   SUMBY= . . .DATETIME . . . ,                         
                   ID= . . . QWACBSC . . . ,                            
                   DATETIME= QWACBSC,                                   
               which caused the output dataset variables QWACBSC and    
               DATETIME have missing values.                            
                 The correct syntax replaces DATETIME in the SUMBY= :   
                 with the DATETIME= variable, and removes the DATETIME= 
                 variable from the ID= argument,                        
               This error was exposed in MXG 34.05 in Change 34.151 for 
               the CLASSNWAY update that is also corrected.  But, even  
               though unlikely, this change detects the old syntax with 
               DATETIME in SUMBY= argument, changes to correct syntax,  
               and tells you what was done for you in a log note.       
               If you had DATETIME in the SUMBY= list and also did NOT  
               explicitly use the DROPDT=NO option, then DATETIME       
               variable is kept in the output dataset.                  
              -Unrelated, this change adds the FLORCEIL parameter to    
               VMXGSUM so you can create interval start or end times as 
               you can do in VMXGDUR. Setting FLORCEIL=CDIL sets the END
               time or FLORCEIL=FLOOR sets the START time, and the label
               indicates START or END.                                  
              -Note: this internal MXG Change could be INCOMPATIBLE with
               programs that worked perfectly previously; send your code
               VMXGSUM invocation and we will update your code.         
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 35.021  MXG 35.01, TYPE78PA variables R782LSMOxx and R782GFMOxxx 
VMAC78         and R782GFFRxxx are incorrect; R782LSMOMIN should have   
Jan 27, 2017   been INPUT before R782LSMONTME, but statement was lost   
               causing R782LSMOMIM UNINIT message.                      
   Thanks to Paul Naddio, FISERV, USA.                                  
                                                                        
Change 35.020  MXG 35.01. Spurious MXGWARN: VMXGSUM BACKLEVEL MXG 3434  
VMXGSUM        note has no impact; the VMXGDUM in 35.01 is correct, but 
Jan 25, 2017   the VMXGVERS call was not updated with '35.01' text.     
                                                                        
Change 35.019 -Support for changed SYTCPU with SYTNLPS=1 SEGLEN=48      
VMACXAM        that caused INVALID SEGMENT record, XAMSYT dataset.      
Jan 26, 2017  -Support for new SYTLC3 segment in XAMSYS records         
Mar  2, 2017   was added on March 2, adding these new variables:        
                 CALLCKID='CALL*CHECKID'                                
                 INDEX   ='TO MATCH*HISTORY DATA'                       
                 SECONDS ='SECONDS'                                     
                 CALXSCNT='TOTAL*SPIN*TIMES*EXCLUSIVE'                  
                 CALXTIME='TOTAL*SPIN*TIME'                             
                 CALSSCNT='SPIN*TIMES*SHARED'                           
                 CALSTIME='SPIN*TIME*SHARED*MODE'                       
                 CALCADSH='CAD*INSTRUCTIONS*OBTAIN*LOCK'                
                 CALCADEX='CAD*INSTRUCT*OBTAIN*EXCL LOCK'               
              -Support for new HSTME2 segment in XAMTCP was added       
               on March 2, changing only the length of DESCR to         
               60 bytes.                                                
   Thanks to Patricia Hansen, ADP, USA.                                 
                                                                        
Change 35.018  An extraneous character in the SU_SEC format raised a    
GRAFWRKX       WARNING but did not cause an error, but ZIPTM, IFATM, and
Jan 26, 2017   ZIETM were not being properly summed, causing the ZIP ZAP
               and ZIE graphs to be suppressed.                         
              -ODS PROCLABEL statements added to make the index 'pretty'
               when creating HTML or PDF output.                        
   Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.       
                                                                        
Change 35.017  New DB2 ZPARMs are added to  T102S106 Dataset:           
VMAC102           QWP4MNSU='MATERIALIZE*NODET*SQLTUDF?'                 
Jan 25, 2017      QWP4DSINUN='DISALLOW*SELINTO*UNION?'                  
                  QWP4MTAD='MOVE*TO*ARCHIVE*DEFAULT'                    
   Thanks to Lai Fai Wong, Bank of America, USA.                        
                                                                        
Change 35.016  DB2STATS dataset, these seven storage variables          
VMACDB2          QISTWSTG  QISTDGTTSTG QISTDGTTCTO QISTDGTTMXU          
Jan 24, 2017     QISTWFSTG QISTWFCTO   QISTWFMXU                        
               were multiplied by 4096 (page size) instead of by 1024   
               to convert KB to bytes for MGBYTES. format.              
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 35.015  Support for SMF 117 written by GTZ (conflicts with 117   
VMAC117        from Message Broker), now GTZ record is ID=125.          
Jan 20, 2017  -If you use TYPE117, it will delete any GTZ records and   
               tell you that they were NOT Message Broker records.      
              -To process the 117s from GTZ, use this in //SYSIN DD     
               until you have the APAR that writes them as 125's:       
                 %LET MACFILE=                                          
                   %QUOTE(IF ID+117 THEN DO;                            
                            INPUT @15+OFFSMF SM117SSI $EBCDIC4. @;      
                            IF SM117SSI='GTZ ' THEN ID=125;             
                          END;                                          
                          );                                            
               and tell MXG to process both 117 and 125 records.        
                                                                        
====== Changes thru 35.014 are in this MXG 35.01 dated Jan 20, 2017=====
                                                                        
Change 35.014  A variable with DATETIME embedded in the name caused an  
VMXGSUM        branch in the code building the SUMBY string and caused  
Jan 19, 2017   the SORT to fail with a variable not found.              
   Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA 
                                                                        
Change 35.013  If you used AUTOALOC=YES with RUNMNTH=MTD on the second  
BLDSMPDB       day of the month, the previous month may have been       
Jan 18, 2017   deleted.                                                 
                                                                        
Change 35.012  Old protection for APAR OA24074 caused ZERO DIVIDE ID=70 
VMAC7072       if CPUUPTM and CPUPATTM were identical, now protected.   
Jan 18, 2017                                                            
   Thanks to Job Varkey, Verisk Analytics, USA.                         
   Thanks to Cesar V. Cocco, Verisk Analytics, USA.                     
                                                                        
Change 35.011  For local time zones with +GMT, variable GMT115TM was    
VMAC115        one hour too large, fortunately impacting only variables 
Jan 17, 2017   QJSTIOMAXIOT1-4 and QJSTIOMAXSUST1-4 in MQMLOG dataset.  
   Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA 
                                                                        
Change 35.010  OSEM User SMF INPUT STATEMENT EXCEEDED, invalid record   
VMACOSEM       with length of last segment not provided if there was    
Jan 26, 2017   more than one segment. The year 2000 vendor DSECT does   
Apr  3, 2018   show a '00'x terminates the record, so that is now used  
               to detect the length of the last segment.                
               Code sent in Mar, 2018 but VMACOSEM updated in 36.04.    
   Thanks to Nilton D Junior, IBM, BRAZIL.                              
                                                                        
Change 35.009  Support for APAR OA48913 metrics for 2GB Memory Frames.  
VMAC71        -New variables in TYPE 71:                                
Jan 13, 2017     SMF71GAA='AVG 2GB FRAMES*IN LFA*NOT IN-USE'            
                 SMF71GAM='MIN 2GB FRAMES*IN LFA*NOT IN-USE'            
                 SMF71GAX='MAX 2GB FRAMES*IN LFA*NOT IN-USE'            
                 SMF71GFA='AVG TOTAL*2GB FRAMES*CAN BE USED'            
                 SMF71GFM='MIN TOTAL*2GB FRAMES*CAN BE USED'            
                 SMF71GFX='MAX TOTAL*2GB FRAMES*CAN BE USED'            
                 SMF71GOA='AVG FIXED 2GB*OBJECTS*ALLOCATED'             
                 SMF71GOM='MIN FIXED 2GB*OBJECTS*ALLOCATED'             
                 SMF71GOX='MAX FIXED 2GB*OBJECTS*ALLOCATED'             
                 SMF71GRA='AVG 2GB PAGES*FIXED*IN CSTORE'               
                 SMF71GRM='MIN 2GB PAGES*FIXED*IN CSTORE'               
                 SMF71GRX='MAX 2GB PAGES*FIXED*IN CSTORE'               
                 SMF71GUA='AVG 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
                 SMF71GUH='HWM*2GB FRAMES*USED'                         
                 SMF71GUM='MIN 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
                 SMF71GUX='MAX 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
                -New variables in TYPE78PA:                             
                 R782GFMOMIN ='MIN FIXED*MEMOBJ*BACKED IN*2GB FRAMES'   
                 R782GFMONTME='TIME STAMP*OF MIN*MEMOBJ*BACKED*IN 2GB'  
                 R782GFMOMAX ='MAX FIXED*MEMOBJ*BACKED IN*2GB FRAMES'   
                 R782GFMOXTME='TIME STAMP*OF MAX*MEMOBJ*BACKED*IN 2GB'  
                 R782GFMOAVG ='AVG FIXED*MEMOBJ*BACKED IN*2GB FRAMES'   
                 R782GFFRMIN ='MIN 2GB PAGES*FIXED*IN CSTORE'           
                 R782GFFRNTME='TIME STAMP*OF MIN*PAGES*FIXED*IN CSTORE' 
                 R782GFFRMAX ='MAX 2GB PAGES*FIXED*IN CSTORE'           
                 R782GFFRXTME='TIME STAMP*OF MAX*PAGES*FIXED*IN CSTORE' 
                 R782GFFRAVG ='AVG 2GB PAGES*FIXED*IN CSTORE'           
                                                                        
Change 35.008  TYPE42 variable S42CSID, the SSID is now formatted HEX4. 
VMAC42         as are the other SSID variables in TYPE42 datasets.      
Jan 12, 2017                                                            
   Thanks to Michael Friske, FMR, USA.                                  
                                                                        
Change 35.007  Liberty SMF 120 subtype 12 TYP12012 dataset variables    
VMAC120        SM120CCC and SM120CCD had year 2027 plus 1 day later     
Jan 12, 2017   because MXG added the DEL6070 seconds between 1960-1970  
               TWICE.  Variable SM120CCB, also on the 1970 epoch, was   
               correct as DEL6070 (315619200) was only added ONCE.      
   Thanks to Steve McKee, FMR, USA.                                     
                                                                        
Change 35.006  Duplicate RMFINTRV obs were created if multiple Capacity 
VMXGRMFI       Group Names existed in the TYPE70PR data; MXG did not    
Jan 10, 2017   select the obs with SYSTEM=SMF70STN and inadvertently    
Jan 25, 2017   output duplicated records; Most values were exact dupes, 
               but SMF70GNM SMF70GMU TOTMEMR values were different.     
              -This error was introduced in MXG 34.01, Change 34.029.   
              -Protected archaic DURSET and DETAIL interval Jan 25.     
   Thanks to Joachim Sarkoschitz, DATEV, DENMARK.                       
   Thanks to Frank Fischer, Concordia, GERMANY.                         
                                                                        
Change 35.005  RMF III dataset ZRBLCP observations were created for each
VMACRMFV       LCPUADDR in the LPAR, only if the LCPU Dispatch Time was 
Jan 10, 2017   non-zero, but that test is changed to output LCPUADDRs   
               that are ONLINE (by testing LCPUONL), so that ZRBLCP has 
               an observation for every ONLINE LCPU Address, to match   
               the RMF CPC screen data.                                 
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 35.004  MXG 34.34. Debugging PROC CONTENTS statements were left  
UTILEXCL       that caused DATASET PDB.CICSDICT NOT FOUND errors, if the
Jan 10, 2017   //PDB DD had DISP=NEW, Lines 891, 892, and 898 need to be
               deleted, but that only exposed a second error causing the
               same error message; the PROC APPEND had transposed the _W
               and _L tokens - Base must be _L and NEW must be _W.      
   Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.       
                                                                        
Change 35.003  Cosmetic. Variables ADSRXXXX, ADSRYYYY, ADSR5ST are now  
VMACEREP       converted to EBCDIC..                                    
Jan  6, 2017                                                            
                                                                        
Change 35.002  Another INVALID SMF RECORD Informatica POWER EXCHANGE    
VMACPOEX       caused STOPOVER ABEND because POEXLEN=52 but there are   
Jan  6, 2017   are only 32 bytes left in the record; its missing the    
               last five counters for the Client POEXCLIE dataset.      
               Datetime variables POEXSTRX/POEXENDX are now kept.       
   Thanks to Scott Wiig, USBank, USA.                                   
                                                                        
Change 35.001  The year end interval with STARTTIME=31DEC2016:23:55:00  
VMACNMON       incorrectly had ENDTIME=01JAN2016:00:00 because MXG used 
Jan  4, 2017   the AAA record's DATECH value to get the year, but that  
               was the date of the start of the monitor.  Now, the DATE 
               in the ZZZZ record is used.                              
   Thanks to Florent Boulesteix, INOVANS partenaire CAAGIS, FRANCE.     
                                                                        
                                                                        
LASTCHANGE: Version 35.