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

MXG CHANGES 35.05

=========================member=CHANGE35================================
 /* COPYRIGHT (C) 1984-2017 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
        MXG Version 35.05 is  dated May 15, 2017, thru Change 35.121    
        MXG Version 35.04 is  dated May  1, 2017, thru Change 35.104    
        MXG 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-EIGHT was dated Jan  3, 2017.              
                                                                        
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.05 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.05.                  
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.05 dated May 15, 2017, thru Change 35.121            
                                                                        
==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 OA51484 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 TS1M3 (9.4M3) printed  
     as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for     
     "SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled),      
     for SAS 9.4 Maintenance Level M3 and m2.                           
                                                                        
     SAS V9.4 M3 Is RECOMMENDED, but MXG executes without error using   
     SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.   
                                                                        
     SAS V9.4 M2 is USABLE. SAS 9.4 M2 is at LEVEL A SAS Support        
     SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support    
     SAS V9.3   SAS 9.3 TS1M2 is USABLE. SAS 9.3 TS1M1 works.           
                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 ok.
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 must be at Service Pack 4.  Additionally, on z/OS 1.10  
                only, 9.1.3 requires SAS Hot Fix for SN-35332.          
                9.1.3 is support level C by SAS Institute, Sep 30, 2013.
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
     SAS V8.2 IS 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.05 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        
      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        
      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        
      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        
      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.05.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 35.05:                          
                                                                        
  a- Changes in MXG architecture made between 35.05 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.05 after MXG 34.34:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  ANALCNCR 35.091  New example count/plot concurrent TELNET sessions.   
  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.  
  ASUM70PR 35.050  Error message if PDB.ASUMCELP does not have all 70s. 
  ASUM70PR 35.061  Enhancement adds SMT_NUM to PDB.ASUMCELP dataset.    
  ASUMCELP 35.061  Variable SMT_NUM added to PDB.ASUMCELP with MT mode. 
  BUILDPDB 35.088  Running MXG on ASCII, free SMF alloc at read end.    
  CICINTRV 35.038  MXG correction for ITRM to NOT delete CICINTRV       
  GRAFCAPS 35.042  Example report of Resource Group CPU use and CAPPING.
  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. 
  JCLTEST9 35.116  35.04 only. //MVJEIN DD in wrong step.               
  RMFINTRV 35.006  Duplicate RMFINTRV if Multiple Capacity Groups exist.
  SMFINTRV 35.067  New START15INT/30INT/HRINT interval Starttimes.      
  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.
  TYPE110  35.105  CICS duration fields are now formatted TIME16.6.     
  TYPE115  35.011  For local time zones with +GMT, GMT115TM wrong.      
  TYPE117  35.015  Support for SMF 117 GTZ record.                      
  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.       
  TYPE42   35.031  Variable S42DSIOS added to TYPE42DS.                 
  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. 
  TYPE71   35.009  Support for APAR OA51484 with 2GB Memory Frames      
  TYPE78   35.021  TYPE78PA variables R782LSMO/GMFO/GFRR are wrong.     
  TYPE80A  35.029  RACFTYPE=6 segment increased in length, error msgs.  
  TYPEBBMQ 35.034  Support for BBMQ BMC Utility BBM9MD73 restructure.   
  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.   
  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.     
  TYPEMVIP 35.055  Support for Mainview for IP PTF BPN2331 adds flag.   
  TYPEMVJE 35.094  Support for BMC Mainview for Java Environment.       
  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.           
  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.    
  TYPESVIE 35.059  Support for CA SYSVIEW for IMS 14, missing values.   
  TYPETPX  35.035  Protection for invalid TPX subtype 7 record.         
  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.  
  TYPEXAM  35.063  Support for XAMSYS wrong length, XMTCPSYS NAMENODE.  
  TYPEXAM  35.074  Velocity XAM SYTCPU invalid errors at vendor.        
  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.      
  UTILRMFI 35.026  Enhanced reporting if SRVCVLASS=SYSOTHER detected.   
  VGETSORT 35.112  35.04 only. ERROR Truncated SORTBY (name GT 32).     
  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.         
  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.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'" should have been a semicolon.                
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 13, 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 11, 2017    because //MVJEIN DD was not found in that step's JCL.   
                Add //MVJEIN DD DUMMY to the TESSUSR1 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 varibles 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.               bkh        
                  Product functional/build level. QLACPRLV. s28617      
               and a search for s28617 discovered new QLSTPRLV had also 
               been added.  But there were no other references to the   
               the e26995 or s28617 tokens in the other MACLIB members. 
                                                                        
               Of course, now that I know the field names, 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 the 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, Bluc 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 arameter 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 that is undocumented.     
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 variable's 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.  
                At this time, they are still continuing investigation.  
                                                                        
                Daniel Rosa's available online 2015 SHARE paper "IBM z  
                Systems z13 Simultaneous Multi-Threading R(Evolution)"  
                discusses the MT=2 metrics.                             
                                                                        
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  Reserved Change Number.                                  
Mar 12, 2017                                                            
                                                                        
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.                                  
   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   
               show a '00'x terminates the record, so that is now used  
               to detect the length of the last segment.                
   Thanks to Nilton D Junior, IBM, BRAZIL.                              
                                                                        
Change 35.009  Support for APAR OA51484 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.