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

MXG CHANGES 35.02

=========================member=CHANGE35================================
 /* COPYRIGHT (C) 1984-2017 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
        MXG Version 35.02 is  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.02 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.02.                  
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.02 dated Feb 10, 2017, thru Change 35.034            
                                                                        
  Major CHANGES added in MXG 35.02, dated Feb 10, 2017 thru 35.034.     
                                                                        
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 wil 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.02 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        
      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        
      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        
      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        
       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.02.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 35.02:                          
                                                                        
  a- Changes in MXG architecture made between 35.02 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.02 after MXG 34.34:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  GRAFWRKX 35.018  WARNING but ZIPTM, IFATM, and ZIETM were not plotted.
  IMACDBNZ 35.027  Support for DB2ACCT NETEZZA Q8AC "Accumu" variables. 
  RMFINTRV 35.006  Duplicate RMFINTRV if Multiple Capacity Groups exist.
  TYPE102  35.017  New DB2 ZPARMS added to T102S106 dataset.            
  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.  
  TYPE125  35.015  Support for SMF 125 GTZ record, untested.            
  TYPE42   35.031  Variable S42DSIOS added to TYPE42DS.                 
  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.  
  TYPEDB2  35.016  DB2STATS QISTxxxx Storage multiplied by 4K vs 1K.    
  TYPEDB2  35.030  DB2STAT4 _REAL variables way too large.              
  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.  
  TYPEVMXA 35.025  Using _VMINPUT. z/VM variable VMDUSER was 1 byte.    
  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.   
  VMXGALOC 35.033  Month begin/logic revised, MNTHKEEP zero protected   
  VMXGSUM  35.020  MXG 35.01. Disregard MXGWARN VMXGSUM BACKLEVEL msg.  
  TYPETPX  35.035  Protection for invalid TPX subtype 7 record.         
  TYPEBBMQ 35.034  Support for BBMQ BMC Utility BBM9MD73 restructure.   
                                                                        
  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.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
               causing zero obs in TPXAPLON Logon dataset. The first 44 
               are now INPUT, and the remainder conditionally input.    
   Thanks to Scott Wiig, USBank, USA.                                   
                                                                        
Change 35.034  Support for the BBMQ large segment record structure that 
TYPEBBMQ       are created by the BMC BBM9MD73 utility program that     
Feb  9, 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 monontonic icrease, 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  2, 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, sometims 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.  
   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 - pending.      
              -Support for new HSTME2 segment in XAMTCP - pending       
   Thanks to Patricia Hansen, ADP, USA.                                 
                                                                        
Change 35.018  An extraneous character im the SU_SEC format raised a    
GRAFWRKX       WARNING but did not cause an error, but ZIPTM, IFATM, and
Jan 28, 2017   ZIETM were not being properly summed, causing the ZIP ZAP
               and ZIE graphs to be suppressed.                         
              -ODS PROCLABEL statments 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 multiplkied 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.