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

MXG CHANGES 37.02

=========================MEMBER=CHANGE37=============================== 
 /* COPYRIGHT (C) 1984-2019 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
        MXG VERSION 37.02 is  dated Mar 11, 2019, thru Change 37.057.   
                                                                        
Updated MXG VERSION 37.01 was dated Feb  3, 2019, thru Change 37.031.   
First   MXG VERSION 37.01 was dated Feb  1, 2019, thru Change 37.029.   
Annual  MXG Version 36.36 was dated Jan  4, 2019, thru Change 36.255.   
        The Last MXG Newsletter SIXTY-NINE was dated Jan  3, 2018.      
                                                                        
Instructions for ftp download can be requested by using this form:      
  http://www.mxg.com/Software_Download_Request                          
Your download instructions will be sent via return email.               
                                                                        
Contents of member CHANGES:                                             
                                                                        
I.    Current MXG Software Version 37.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 37.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, although there are  
  no new NEWSLTRS updates; they are now found in CHANGESS as TECHNOTEs. 
                                                                        
  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 37.02 DATED Mar 11, 2019, THRU CHANGE 37.057.           
                                                                        
==MAJOR CHANGES ADDED IN MXG 37.02, DATED Mar 11, 2019 THRU 37.057.     
                                                                        
ERRORS CORRECTED                                                        
  TYPENDM  37.047  NDM-CDI dataset NDMCT var NDMCPU 256 times too large.
  READDB2  37.042  MXG 37.01.  Blank WANTONLY Cosmetic %SYSFUNC message 
  TYPE74   37.040  TYPE749 variable R7491DEFCOMPRATIO wrong value.      
  TYPE42   37.034  Two more ABENDS invalid SMF 42 LENSR 520/592 protect.
  TYPE74   37.032  TYPE749 z/EDC Divide by ZERO protection failed.      
  TYPE7072 37.044  BMC CMF VERSNRMF values 792 and 794 for z/OS 2.3.    
NEW SUPPORT                                                             
  TYPEDCOL 37.041  Support for APAR OA54879, DCDEXFLG not used FOR zEDC.
  MANY     37.037  Support for SMF Manual Changes in Jan 14, 2019 Doc.  
  TYPEAXW  37.033  Support for Axway V3.3.2 2018/06/27 restructure.     
  UTILMISS 37.053  Utility to remove all variables that are all missing.
  TYPEDB2  37.035  DB2 V12 overlooked Package variables in DB2ACCTP.    
  TYPE102  37.051  IFCID 319 new variables created and kept.            
ENHANCEMENT                                                             
  JCLPDBJB 37.048  Example "BUIDPDB" creates only JOB-related datasets. 
  TYPERMFV 37.055  CFACT Coupling Facility Structure Activity Report.   
  ANALMQ   37.039  MQ Reports replicating IBM's MQSMF program.          
  ANALHSM1 37.038  Combined TYPE6156+HSMFSRST report, thrashing pri-mig?
  TYPE70PR 37.046  SMF70BPS/SMF70ACS expanded for each engine type.     
  TECHNOTE 37.043  Executing MXG on ASCII, WORK needs to be local.      
                                                                        
==MAJOR CHANGES ADDED IN MXG 37.01, DATED Feb  3, 2019 THRU 37.030.     
                                                                        
  ASMRMFV  37.030  ASMRMFV 36.12-37.01 NOZEROCPU filter didn't.         
                   Caused out of space condition.  Typically, NOZEROCPU 
                   filters out 3/4 of the ZRBASI records.               
                                                                        
==MAJOR CHANGES ADDED IN MXG 37.01, DATED Feb  1, 2019 THRU 37.030.     
                                                                        
ABEND Avoidance                                                         
  TYPEDB2  37:014  ABEND: DB2 SMF 100 ST 1 NETEAZZA/IDAA DB2STATS.      
  TYPEVMXA 37.012  ABEND: ZVM MONWRITE NEW 40061802 Service Level.      
  TYPEVMXA 37.028  ABEND: ZVM MONWRITE new z/VM 7.1 (INCOMPAT).         
ERRORS CORRECTED                                                        
  TYPE92   37.002  TYPE9208 INPUT STATEMENT EXCEEDED, manual wrong.     
  TYPERMFV 37.001  Some RMF III ZRBASI fields blank/wrong in 36.36.     
  TYPE119  37.003  TYP11952 SMF119ML_IP_IPV4 wrongly compressed TIRIP.  
  VMXGPRAL 37.006  Unbalanced parens in variable label, non fatal.      
  TYPE92   37.017  Many non-fatal corrections were made to type 92.     
  TYPEEDGR 37.015  RMM variable EDGRTIME had missing values.            
  ANALCNCR 37.013  New Concurrency example counts steps and tapes.      
NEW SUPPORT                                                             
  TYPEBETA 37.007  Support for Beta93 V6.2 Subtypes 1-3.                
  TYPE102  37.005  Support for DB2 102 Trace IFCID 404.                 
  TYPESTC  37.018  Support for STC HSC Subtype 32 and 33 new datasets.  
  TYPE26J2 37.026  Local SubSystem TYPE26J2 not output, SMF6SBS NE 2.   
  VMXGALOC 37.021  New parms YR2KEEP and BASEYEAR for Yearly PDB.       
ENHANCEMENT                                                             
  EMAIL    37.027  Example added to email SAS CondCode from ASCII SAS.  
  ANALID   37.016  New report showing total/min/max for each SYSTEM.    
  VMXGUOW  37.011  Enhanced for easy CICSTRAN-only PDB.ASUMUOW.         
  ANAL89   37.029  Reference line SMF70LAC (4HRAV) added to MSU plots.  
TECHNOTES                                                               
  TECHNOTE 37.004  Reading z/OS DATA with SAS FTP Access needs RCMD     
                                                                        
    Please read CHANGESS for the complete list of major enhancements.   
                                                                        
  See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
  current MXG Technical Notes.                                          
                                                                        
                                                                        
  All of these enhancements are described in the Change Log, below.     
                                                                        
II.   SAS Version requirement information:                              
                                                                        
   SAS Versions                                                         
     The current version nomenclature is SAS 9.4 TS1M5 (9.4M5), "M5",   
     or "SAS 9.4 (TS04.01M5P09132017)" if the OPTION VERSIONLONG is     
     enabled.                                                           
                                                                        
     Only on z/OS, SAS 9.4 "M5" requires MXG 35.36+ because it adds the 
     NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect 
     described in SAS Note 61672.  But SAS apparently does not plan for 
     a defect correction since the MXG Circumvention solves for MXG and 
     the text of 61672 simply describes the circumvention needed because
     MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect. 
     See Change 35.309 for more details on using NOERRORSTOP for your   
     own PROC SQLs.                                                     
                                                                        
     SAS V9.4 M5 is RECOMMENDED, but MXG executes without error         
     using SAS Version 9.4 M0-M2 or M4-M5 or SAS Version 9.3 M0-M2.     
                                                                        
     SAS V9.4 M5 is REQUIRED with z/OS 2.3 with Eight-Byte USERIDs      
                for Interactive TSO (DMS) SAS Sessions. SAS Note 61339. 
                                                                        
     SAS V9.4 M3 is NOT RECOMMENDED.  See Change 36.128 SAS Note 61906  
                that reports 40% Increase in CPU time with M3.          
                                                                        
     SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.      
                                                                        
     SAS V9.3   SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.  
                But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
                see CHANGE 29.169, IS REQUIRED:                         
                  The %MACRO compiler error is in processing %LET       
                  statements. While only two MXG members failed         
                  repeatedly in MXG QA tests on z/OS, there were random 
                  %LET errors in ASCII QA tests, so ANY use of %LET     
                  statement on ANY platform are vulnerable to this      
                  error, as the %MACRO compiler is SAS portable code,   
                  used on all platforms.  So this is NOT just an MXG    
                  error, but impacts ALL SAS programs.                  
                SAS9.3 is LEVEL A support from SAS.                     
     SAS V9.2   Was recommended, prior to 9.3, and was error-free with  
                MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to 
                use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2      
                Decompression Infile Exit.  but SAS V9.2 does execute on
                that platform.                                          
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
                Support level C by SAS Institute, Sep 30, 2013.         
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
     SAS V8.2   SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS! 
                with SAS 8.2.                                           
                SAS 8.2 is Level C Support from SAS as of Dec 31, 2011. 
                                                                        
      JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used  
                                                                        
      ***************************************************************   
      As documented in Change 27.356, for SAS V9.2 or later):           
      The standard SAS JCL Procedure can be used for MXG with SAS V9.2+ 
           // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                  
           //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR     
      or you can continue to use the MXGSAS94 JCL Procedure example.    
      ***************************************************************   
                                                                        
      MXG 26.03 thru MXG 36.11 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 TEN and  
      Linux on 64-bit hardware, 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 Z14 CHANGED ONLY THE SMF 113 RECORD INCOMPATIBLY and that      
     was supported in MXG 35.11, but ASUM113 variable LPARBUSY was      
     missing until corrected in MXG 36.07.  The new SMF70MAXPU variable 
     was added in MXG 36.04.                                            
                                                                        
     The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.        
     The z/EC12 with 85+ engines required MXG 30.07.                    
     Support for 255 engines was added in MXG 31.04.                    
                                                                        
                                                                        
   However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was  
   INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to
   read the SMT-format RMF records (which are written if you have zIIP  
   engines AND have enabled the new PROCVIEW CORE option for            
   Multi-Threading, even if only one thread is enabled).                
                                                                        
   The new zEDC compression hardware requires MXG 33.07 to support the  
   new metrics.                                                         
                                                                        
   For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.        
                                                                        
                                                                        
    Availability dates for the IBM products and MXG version required for
    error-free processing of that product's data records:               
                                                                        
                                       Product's                        
                                       Availability     MXG Version     
      Product Name                     Date              Required       
                                                                        
      MVS/ESA 4.1                      Oct 26, 1990         8.8         
      MVS/ESA 4.2                      Mar 29, 1991         9.9         
      MVS/ESA 4.2.2                    Aug 15, 1991         9.9         
      MVS/ESA 4.3                      Mar 23, 1993        10.10        
      MVS/ESA 5.1.0 - compatibility    Jun 24, 1994        12.02        
      MVS/ESA 5.1.0 - Goal Mode        May  3, 1995        13.01        
      MVS/ESA 5.2.0                    Jun 15, 1995        13.05        
      MVS/ESA 5.2.2                    Oct 19, 1995        13.09        
      OS/390  1.1.0                    Feb 22, 1996        14.01        
      OS/390  1.2.0                    Sep 30, 1996        14.05        
      OS/390  1.3.0 Compatibility Mode Mar 28, 1997        14.14        
      OS/390  1.3.0 WLM Goal Mode      Mar 28, 1997        15.02        
      OS/390  2.4.0                    Sep 28, 1997        15.06        
      OS/390  2.5.0                    Feb 24, 1998        15.06        
      OS/390  2.6.0                    Sep 24, 1998        16.04        
      OS/390  2.7.0                    Mar 26, 1999        16.09        
      OS/390  2.7.0 APAR OW41318       Mar 31, 2000        18.03        
      OS/390  2.8.0                    Aug 24, 1999        16.09        
      OS/390  2.8.0 FICON/SHARK        Aug 24, 1999        17.08        
      OS/390  2.8.0 APAR OW41317       Mar 31, 2000        18.03        
      OS/390  2.9.0                    Mar 31, 2000        18.03        
      OS/390 2.10.0                    Sep 15, 2000        18.06        
      OS/390  PAV                      Oct 24, 2000        18.09        
      z/OS 1.1                         Mar 30, 2001        18.11        
      z/OS 1.1 on 2064s                Mar 30, 2001        19.01        
      z/OS 1.1 with correct MSU        Mar 30, 2001        19.02        
      z/OS 1.2                         Oct 31, 2001        19.04        
      z/OS 1.1,1.2 APARs to 78         Oct 31, 2001        19.05        
      z/OS 1.2+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.3+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.2 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.3 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.4 Tolerate                Sep 27, 2002        20.03        
      z/OS 1.4 Support                 Sep 27, 2002        20.06        
      z/OS 1.4 Over 16 CPUs/LPARs      May 29, 2003        21.02        
      z/OS 1.4 DFSMS/rmm, RACF         Aug 29, 2003        21.04        
      z/OS 1.5                         Mar 31, 2004        21.21        
      z/OS IRD ASUM70PR/ASUMCEC        Sep 22, 2003       *24.10        
      z/OS IRD TYPE70PR                Mar 11, 2004       *24.10        
      z/OS IRD TYPE70,RMFINTRV         Mar 22, 2002       *24.10        
      z/OS 1.6 - No IFAs               Sep 30, 2004       *22.09        
      z/OS 1.6 - With IFAs             Sep 30, 2004       *22.11        
      z/OS 1.7 (COMPATIBLE CHANGES)    Sep 30, 2005       *24.10        
      z/OS 1.7 (SPLIT70 CORRECTION)    Sep 30, 2005       *24.10        
      z/OS IFA data in RMF 79s         Sep 30, 2005        23.10        
      z/OS 1.8 - ASMTAPEE assembly     Sep 30, 2005       *25.03        
      z/OS 1.8 - SMF 119 INCOMPAT      Sep 30, 2005       *25.06        
      z/OS More than 32 LPARs          Jan 30, 2006       *24.24        
      z/OS SPLIT RMF 70 records        Jan 30, 2006       *24.24        
      z/OS Dupe SYSTEMs in a SYSPLEX   Jan 30, 2006       *24.02        
      z/OS IRD errors corrected        May 15, 2006        24.03        
      z/OS ASUMCEC errors corrected    May 15, 2006       *24.24        
      z/OS ASUM70LP errors corrected   Jun 13, 2006       *24.24        
      z/OS zIIP Processor Support      Jun 22, 2006       *24.24        
      z/OS Dedicated zIIP Support      Mar  8, 2008       *26.01        
      z/OS Dedicated zAAP Support      Mar  8, 2008        26.01        
      z/OS 1.8 (COMPATIBLE CHANGES)    Sep 20, 2006       *24.24        
      z/OS 1.9 (INCOMPAT, 54 CPs)      Sep 27, 2007        25.10        
      z/OS 1.9 MXGTMNT at ML-39 reASM  Sep 27, 2007        25.10        
      z/OS new z10 variables           Mar  5, 2008        26.01        
      z/OS 1.8 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.9 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.10 (INCOMPAT, MXG code)   Sep 15, 2008        26.07        
      z/OS 1.10 With HiperDispatch     Sep 15, 2008       *26.10        
      z/OS 1.10 RMF III, SMF 119       Jul 20, 2009        27.05        
      z/OS 1.11                        Sep  2, 2009        27.08        
      z/OS 1.11 New 30 variables       Apr 14, 2010       *28.02        
      z/OS 1.12                        Aug 17, 2010       *28.05        
      z/OS 1.12 SMF 85 Subtype 79      Aug 17, 2010       *29.03        
      z/OS 1.12 VMGUEST option         Aug 17, 2010       *29.06        
      z/OS 1.13                        Sep 30, 2011        29.03        
      z/OS 1.13 - MXGTMNT only         Dec 15, 2011        29.08        
      z/OS 1.13 SMF 119 ST 6 INCOMPAT  Feb  7, 2012        30.01        
      z/OS 2.1  - Most Records support Jul 23, 2013        30.05        
      z/OS 2.1  - ID=0 ERROR MESSAGE   Jul 23, 2013        31.07        
      z/OS 2.1  - ID=85 INCOMPAT       Jul 23, 2013        32.03        
      z/OS 2.1  - ID=70 SMF70CPA       Jul 23, 2013        32.03        
      z/OS 2.1  - INPUT STATEMENT EXCEEDED ERROR SMF 74    33.10        
      z/OS 2.2  COMPATIBLE CH 33.189   Aug 19, 2015        33.08        
      z/OS 2.2 MXGTMNT ABEND S0E0-28   Sep 15, 2015        33.09        
               REQUIRES ASMTAPE ML-55  Sep 15, 2015        33.09        
      z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr  5, 2016        34.02        
      z/OS 2.2 SPLIT 73, ABEND 33.068  Apr  5, 2016        34.02        
      z/OS 2.2 JES2 8-char JOBCLASS    Oct  7, 2016        34.07        
      z/OS 2.2 NEW SMF 124 IOS Spvr    Oct  7, 2016        34.07        
      z/OS 2.3 Many new variables      Sep 24, 2017 35.166 35.09*       
      z/OS 2.3 RMF III Support         Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 2 st 2 STOPOVER    Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 90 st 38 STOPOVER  Sep 24, 2017 35.199 35.09*       
      z990 CPUs - CPUTYPE '2084'x      Aug 25, 2003        21.04        
      z890 CPUs - CPUTYPE '2086'x      Jun 24, 2004        22.07        
      z9   CPUs - CPUTYPE '2094'x      Jul 20, 2005       *24.24        
      z9EC CPUs - CPUTYPE '2094'x:                                      
             with 64-bit z/OS - no change required        *24.24        
             with 32-bit z/OS only:    Aug 26, 2006        24.06        
      z9BC CPUs - CPUTYPE '2096'x:                                      
             with 64-bit z/OS - no change required         24.01        
             with 32-bit z/OS only:    Jul 27, 2006       *24.24        
      z10  CPUs - CPUTYPE '2097'x      Dec  7, 2008        25.11        
      z10  HiperDispatch/Parked Time   Mar  3, 2008       *26.10        
      z196 (INCOMPAT IF GT 64 ENG)     Aug 17, 2010        28.05        
      zEC12                            Nov 14, 2012        30.07        
      z13   non-SMT Mode               May 27, 2014        32.05        
      z13   SMT Mode Change 33.217     Sep 15, 2015       *33.09        
      z13   SMT Mode NRZIPCPU 34.106   May 10, 2016        34.03        
      z13   SMT MT=2 CPUZIPTM TYPE70   Mar 21, 2016        35.03        
      z14   SMF 113 INCOMPAT, ABEND    Oct  2, 2017        35.11        
      z14   113 LPARBUSY missing value Aug  8, 2018        36.07        
      z14 ZR1 New SMF70MAXPU variable  May  8, 2018        36.04        
      CICS/CTG V9 Transaction Gateway  ??  ??  2013        31.31        
      CICS/ESA 3.2                     Jun 28, 1991         9.9         
      CICS/ESA 3.3                     Mar 28, 1992        10.01        
      CICS/ESA 4.1                     Oct 27, 1994        13.09        
      CICS/ESA 5.1 aka CICS/TS V1R1    Sep 10, 1996        14.07        
      CICS-Transaction Server V1R1     Sep 10, 1996        14.07        
      CICS-TS V1R1 with APAR UN98309   Sep 15, 1997        15.06        
      CICS-TS V1R2  CICS/TS 1.2        Oct 27, 1997        15.06        
      CICS-TS V1R3  CICS/TS 1.3        Mar 15, 1999        17.04        
      CICS-TS V2R1  CICS/TS 2.1        Mar 15, 2001        18.11        
      CICS-TS V2R2  CICS/TS 2.2        Feb  9, 2002        19.19        
       CICSTRAN subtype 1 support only                    *19.19        
       CICSTRAN subtype 2 completed                       *19.08        
      CICS-TS V2R3  CICS?TS 2.3        Dec 19, 2003                     
       Using UTILEXCL to create IMACEXCL:                  21.04        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04        
      CICS-TS V2R3  CICS/TS 2.3        Aug 13, 2004        22.04        
      CICS-TS V3R1  CICS/TS 3.1        Jan 18, 2005        22.22        
      CICS-TS for Z/OS Version 3.1     Mar 15, 2005                     
       Using UTILEXCL to create IMACEXCL:                  22.13        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22        
      CICS-TS V3R2  CICS/TS 3.2        Dec  6, 2007        25.11        
      CICS-TS for Z/OS Version 3.2     Jun 29, 2007        25.03        
      CICS-TS/3.2 Compressed Records   Nov  3, 2007        25.11        
      CICS-TS/4.1 (CICSTRAN INCOMPAT)  Mar 13, 2009        27.01        
      CICS-TS/4.1 (STATISTICS ST=2)    Sep 18, 2009        27.08        
      CICS-TS/4.2 CICSTRAN/STATISTICS  Jun 24, 2011        29.03        
      CICS-TS/4.2 CICSRDS MNSEGCL=5    Jun 24, 2011       *29.05        
      CICS-TS/4.2 INVALID STID=116     Jan 31, 2012       *30.01        
      CICS-TS/5.1 (INCOMPATIBLE)       Dec 14, 2012       *30.08        
      CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013       *30.30        
      CICS-TS/5.1 MNSEGCL=5 INCOMPAT   Jun 17, 2013       *31.03        
      CICS-TS/5.2 COMPATIBLE CICSTRAN  Jun 13, 2014       *31.03        
      CICS-TS/5.2 INCOMPAT Statistics  Jun 13, 2014       *32.03        
      CICS-TS/5.3 INCOMPAT CICSTRAN    Apr 29, 2015        33.04        
      CICS-TS/5.3 RESOURCE SEGCL=5     Sep 31, 2015        33.09        
      CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015        33.11        
      CICS-TS/5.3 GA date              Dec 11, 2015        33.33        
      CICS-TS/5.3 MNSEGCL=5 INPUT ERR  Mar 21, 2016        34.02        
      CICS-TS/5.4 OPEN BETA  Aug       Aug 11, 2016        34.06        
      CICS-TS/5.4 OPEN BETA  Nov       Nov 11, 2016        34.09        
      CICS-TS/5.4 GA                   Jun 17, 2017        35.03        
      DB2 2.3.0                        Oct 28, 1991        10.01        
      DB2 3.1.0                        Dec 17, 1993        13.02        
      DB2 4.1.0 Tolerate               Nov  7, 1995        13.07        
      DB2 4.1.0 Full support           Sep 11, 1996        14.07        
      DB2 5.1.0 Tolerate               Jun 27, 1997        14.14        
      DB2 5.1.0 Full support           Jun 27, 1997        15.02        
      DB2 6.1.0 initial support        Mar 15, 1999        16.09        
      DB2 6.1.0 all buffer pools       Mar 15, 1999        18.01        
      DB2 6.1.0 parallel DB2           Mar 15, 1999        19.19        
      DB2 7.1.0 parallel DB2           Mar 31, 2001        19.19        
      DB2 7.1.0 corrections            Mar 31, 2001        20.06        
      DB2 8.1 Tolerate, no packages    Mar 31, 2004        20.20        
      DB2 8.1 New Data Packages wrong  Mar 31, 2004        21.08        
      DB2 8.1 Support with Packages    Mar 31, 2004       *23.09        
      DB2 8.1 with all zIIP Variables  Sep 30, 2006        24.08        
      DB2 8.1 +PK47659                 Sep 12, 2008        26.08        
      DB2 9.1 See Change 25.265.       Dec  7, 2007        25.11        
      DB2 9.1 Full Support +PK/56356   Sep 12, 2008        26.08        
      DB2 10.1 Tolerate                Oct  1, 2010        28.06        
      DB2 10.1 New vars + Compressed   Nov  1, 2010       *28.07        
      DB2 10.1 Invalid Header pre APAR Jan 12, 2011       *28.28        
      DB2 10.1 IFCID=225 INCOMPAT      Sep 23, 2011       *29.07        
      DB2 10.1 QWHCCV for QWHCATYP=8   Oct  3, 2011       *30.07        
      DB2 10.1 DBID/OBID decode        Jan 21, 2013       *30.30        
      DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013       *31.04        
               (ONLY IMPACTS DB2STATS)                                  
      DB2 11.1 TOLERATE DB2 V11.1      Jun 21, 2013        30.30        
      DB2 11.1 DB2STATS QLST CORRECT   Jun 21, 2013        31.04        
      DB2 11.1 SUPPORT NEW VARIABLES   Jun 21, 2013        31.08        
      DB2 11.1 IRLM NEW SEGMENT        Jun 21, 2013        32.10        
      DB2 12.1 COMPATIBLE              Oct  5, 2016        34.08        
      DB2 12.1 NETEZZA CORRECTIONS     Oct  5, 2016        34.08        
      DB2 12.1 QLAC INSERTS DB2ACCT    May 15, 2017        35.05*       
      DFSMS/MVS 1.1                    Mar 13, 1993        11.11        
      DFSMS/MVS 1.2                    Jun 24, 1994        12.02        
      DFSMS/MVS 1.3                    Dec 29, 1995        13.09        
      DFSMS/MVS 1.4                    Sep 28, 1997        15.04        
      DFSMS/MVS 1.4 HSM                Sep 23, 1998        16.04        
      DFSMS/MVS 1.5                    ??? ??, 1999        16.04        
      DFSORT SMF V1R5                  Mar  1, 2006        24.02        
      MQM 1.1.2, 1.1.3, 1.1.4          Apr 25, 1996        14.02        
      MQ Series 1.2.0                  May 26, 1998        16.02        
      MQ Series 2.1.0                  Oct  2, 1999        17.07        
      MQ Series 5.2                    Dec 16, 2000        18.10        
      MQ Series 5.3                    Dec 16, 2002        21.05        
      MQ Series 6.0                    Feb 14, 2006        23.23        
      Websphere MQ Series 7.0          ??? ??, 2009       *28.06        
      Websphere MQ Series 7.1          MAR 12, 2011        29.03        
      Websphere MQ Series 8.0          Jun 24, 2011        29.05        
      Websphere MQ Series 9.1          Mar 20, 2017        35.03        
      NETVIEW 3.1 type 37              ??? ??, 1996        14.03        
      NPM 2.0                          Dec 17, 1993        12.03        
      NPM 2.2                          Aug 29, 1994        12.05        
      NPM 2.3                          ??? ??, 1996        15.08        
      NPM 2.4                          Nov 18, 1998        17.01        
      NPM 2.5                          Feb ??, 2000        18.02        
      NPM 2.6                          Nov ??, 2001        19.06        
      RMDS 2.1, 2.2                    Dec 12, 1995        12.12        
      RMDS 2.3                         Jan 31, 2002        19.11        
      TCP/IP 3.1                       Jun 12, 1995        12.12        
      TCP/IP 3.4                       Sep 22, 1998        16.04        
      WebSphere 5.0 APAR PQ7463        Aug 19, 2003        21.04        
      WebSphere 6.0                    Feb 18, 2006        23.23        
      WebSphere 7.0                    Oct  7, 2010        28.06        
      WebSphere 8.0                    Jul 17, 2011        29.05        
      DOS/VSE POWER V6.3.0             Dec 19, 1998        16.08        
      VM/ESA  2.0                      Dec 23, 1992        10.04        
      VM/ESA  2.1                      Jun 27, 1993        12.02        
      VM/ESA  2.2                      Nov 22, 1994        12.06        
      VM/ESA  2.3                      Jun  1, 1998        16.08        
      VM/ESA  2.4                      Mar  1, 2001        19.03        
      z/VM    3.1                      Mar  1, 2001        19.03        
      z/VM    3.1 DATABYTE=0           May  2, 2002        20.02        
      z/VM    4.2 ??                   May  2, 2002        20.02        
      z/VM    4.4                      Jan 22, 2005        22.22        
      z/VM    5.1                      Jan 22, 2005        22.22        
      z/VM    5.2                      Jan 22, 2006        24.01        
      z/VM    5.3 TOLERATE             Jun  7, 2007        25.05        
      z/VM    5.3 NEW VARIABLES        Sep 12, 2008        26.08        
      z/VM    5.4 (COMPATIBLE)         Sep 12, 2008       *27.01        
      z/VM    6.1 (NO CHANGES)         Jul  7, 2008        27.01        
      z/VM    6.2                      Dec  2, 2011        29.04        
      z/VM    6.3 INCOMPATIBLE         Jul 23, 2013        31.05        
      z/VM    6.3 z/13                 Jan 23, 2016        33.33        
      z/VM    6.4 SYTLCK Incompat      Apr 26, 2016        34.04        
      IMS log 4.1                      Jul  4, 1994        12.02        
      IMS log 5.1                      Jun  9, 1996        14.05        
      IMS log 6.1                      ???  ?, 199?        20.03        
      IMS log 7.1                      ???  ?, 200?        20.03        
      IMS log 8.1                      May 21, 2003        21.02        
      IMS log 9.1                      Mar 96, 2004       *26.01        
      IMS log 10.1                     Mar 06, 2007       *26.01        
      IMS log 11.1                     Apr  1, 2010       *28.02        
      IMS log 12.1                     Jan 23, 2012       *29.29        
      IMS log 13.1 (NOT 56FA)          May 25, 2013        31.03        
      IMS log 13.1 (56FA RECORD)       May 27, 2014        32.05        
      IMS log 14.1 COMPATIBLE          Dec 19, 2015        33.07        
      IMS log 15.1 NO CHANGES          Mar  1, 2018        35.07        
      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 was 16.04 but ABEND, ACSMFREL=0 May 2018   36.05        
       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        
       IMF 5.3 a/k/a Mainview IMS                          35.03        
       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 36.11.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 37.02:                          
                                                                        
  a- Changes in MXG architecture made between 37.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 37.02 after MXG 36.36:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  ANALCNCR 37.013  New Concurrency example counts steps and tapes.      
  ANALHSM1 37.038  Combined TYPE6156+HSMFSRST report, thrashing pri-mig?
  ANALID   37.016  New report showing total/min/max for each SYSTEM.    
  ANALMQ   37.039  MQ Reports replicating IBM's MQSMF program.          
  ASMRMFV  37.030  ASMRMFV 36.12-37.01 NOZEROCPU filter didn't.         
  EMAIL    37.027  Example added to email SAS CondCode from ASCII SAS.  
  MANY     37.037  Support for SMF Manual Changes in Jan 14, 2019 Doc.  
  READDB2  37.042  MXG 37.01.  Blank WANTONLY Cosmetic %SYSFUNC message 
  TECHNOTE 37.004  Reading z/OS DATA with SAS FTP Access needs RCMD     
  TECHNOTE 37.043  Executing MXG on ASCII, WORK needs to be local.      
  TYPE102  37.005  Support for DB2 102 Trace IFCID 404.                 
  TYPE119  37.003  TYP11952 SMF119ML_IP_IPV4 wrongly compressed TIRIP.  
  TYPE26J2 37.026  Local SubSystem TYPE26J2 not output, SMF6SBS NE 2.   
  TYPE42   37.034  Two more invalid SMF 42 LENSR 520 and 592 added.     
  TYPE7072 37.044  BMC CMF VERSNRMF values 792 and 794 for z/OS 2.3.    
  TYPE70PR 37.046  SMF70BPS/SMF70ACS expanded for each engine type.     
  TYPE74   37.032  TYPE749 z/EDC Divide by ZERO protection failed.      
  TYPE74   37.040  TYPE749 variable R7491DEFCOMPRATIO wrong value.      
  TYPE92   37.002  TYPE9208 INPUT STATEMENT EXCEEDED, manual wrong.     
  TYPE92   37.017  Many non-fatal corrections were made to type 92.     
  TYPEAXW  37.033  Support for Axway V3.3.2 2018/06/27 restructure.     
  TYPEBETA 37.007  Support for Beta93 V6.2 Subtypes 1-3.                
  TYPEBETA 37.007  Support for Beta93 Version 6.2 subtypes 2 and 3.     
  TYPEDB2  37.035  DB2 V12 overlooked Package variables in DB2ACCTP.    
  TYPEDB2  37:014  ABEND: DB2 SMF 100 ST 1 NETEAZZA/IDAA DB2STATS.      
  TYPEDCOL 37.041  Support for APAR OA54879, DCDEXFLG not used FOR zEDC.
  TYPEEDGR 37.015  RMM variable EDGRTIME had missing values.            
  TYPENDM  37.047  NDM-CDI dataset NDMCT var NDMCPU 256 times too large.
  TYPEMDM  37.015  RMM variable EDGRTIME had missing values.            
  TYPERMFV 37.001  Some RMF III ZRBASI fields blank/wrong in 36.36.     
  TYPESTC  37.018  Support for STC HSC Subtype 32 and 33 new datasets.  
  TYPEVMXA 37.012  ABEND: ZVM MONWRITE NEW 40061802 Service Level.      
  TYPEVMXA 37.028  Support for z/VM 7.1 (INCOMPAT, BROKEN CONTROL).     
  VMXGALOC 37.021  New parms YR2KEEP and BASEYEAR for Yearly PDB.       
  VMXGPRAL 37.006  Unbalanced parens in variable label, non fatal.      
  VMXGUOW  37.011  Enhanced for each CICSTRAN-only PDB.ASUMUOW.         
  TYPERMFV 37.055  CFACT Coupling Facility Structure Activity Report.   
  UTILMISS 37.053  Utility to remove all variables that are all missing.
  TYPE102  37.051  IFCID 319 new variables created and kept.            
  JCLPDBJB 37.048  Example "BUIDPDB" creates only JOB-related datasets. 
                                                                        
  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 37.057 ARE IN MXG 37.02 DATED Mar 11, 2019 ======== 
                                                                        
Change 37.057  Analysis of what your WLM Classification Rules do, using 
ANALRULE       SMF 30, 101 and 110 to produce three reports for where   
Mar 10, 2019   work is sent by SYSTEM and TYPETASK, routing for CICS    
               transactions by SYSTEM and APPLID, and routing for DDF.  
                                                                        
Change 37.056 -TYPE30 variable CPUERROR was incorrectly formatted $HEX8.
VMAC30         but it is only a 2-byte field, now formatted $HEX4., but 
Mar  9, 2019   because the $HEX8 forced the length to be $4, it is still
               set to $4, to prevent changed length errors.             
              -Flag variables SMF30T32 and SMF30T33 are now kept.       
                                                                        
Change 37.055  RMF III dataset ZRBCFI, CFACT Coupling Facility Activity 
FORMATS        Report, which is actually a CF per-Structure report, is  
VMACRMFV       printed by invoking _CFACT after TYPSRMFV.  Macro _CFACT 
Mar  9, 2019   is defined at the bottom of VMACRMFV.                    
   Thanks to Ervin Claxon, CSX, USA.                                    
                                                                        
Change 37.054  Using report classes to define workloads in RMFINTRV is a
UTILWORK       good way to group workloads but will only work if all    
Mar  9, 2019   workloads have a default report class, UTILWORK now      
               detects this condition and warns that the use of report  
               classes should not be attempted until this can be        
               resolved                                                 
                                                                        
Change 37.053  New utility contribution, UTILMISS, will create a data   
UTILMISS       set from an existing dataset, removing all variables that
Mar  7, 2019   have all numeric missing values, and characters blank.   
   Thanks to Jim Horne, Lowes, USA.                                     
                                                                        
Change 37.052  Variable CPUERROR in TYPE30 datasets is a two-byte field 
VMAC30         but was accidentally made length $4 some time ago due to 
Mar  7, 2019   a blank that gave it $HEX8 format which forced length 4. 
               The correct $HEX4. format is now applied, but LENGTH $4  
               is also forced, since a change in length will cause PROC 
               APPEND to fail if the user didn't specify FORCE.  These  
               TYPE30xx datasets are too critical to not protect.       
                                                                        
Change 37.051 -IFCID 319 variable QW0319FL is replaced by a variable    
VMAC102        for each bit:                                            
Mar  7, 2019    QW0319UR='CALLER*PASSED*USER*REG*NAME?'                 
                QW0319AE='AES*ENCRYPTION*BEING*USED?'                   
                QW0319SC='COMPATIBLE*WITH*TCPALVER?'                    
                QW0319SE='SECURE*CONNECTION?'                           
               -Variable QW0319RI is INPUT and Kept.                    
               -Variables QW0319AE QW0319IY QW0319SC QW0319SE kept.     
               -New variable QW0319LU='LUNAME*IF*SNA' is created        
   Thanks to Warren Cravey, FMR, USA.                                   
                                                                        
Change 37.050  UTILBLDP now accepts USERADD=100 or 101 or both, and     
UTILBLDP       invokes USERADD=DB2, but if only 100 or 101 alone are    
Mar  6, 2019   requested, the other record's datasets are _NULL_ed.     
               UTILBLDP now accepts USERADD=CICS (to read SMF 110)      
                                                                        
Change 37.049  Variable ASIQSCANREQ is kept in RMF III ZRBASI dataset.  
VMACRMFV                                                                
Mar  6, 2019                                                            
                                                                        
Change 37.048  Example to "BUILDPDB" only JOB-related Datasets enhanced 
JCLPDBJB       to support both JES2 and JES3.                           
Mar  5, 2019                                                            
                                                                        
Change 37.047  NDM-CDI dataset NDMCT variable NDMCPU was 256 times too  
VMACNDM        large and character NDMRIUP6/NDMTYPFK shifted because of 
Mar  1, 2019   a 1 byte misalignment in the MXG Input Statement.        
   Thanks to Mike Creech, BKFS, USA.                                    
   Thanks to Roger Foreman, BKFS, USA.                                  
   Thanks to Glenn Halligan, BKFS, USA.                                 
   Thanks to David Kelley, BKFS, USA.                                   
                                                                        
Change 37.046  Variables SMF70BPS/SMF70ACS for each SMF70CIN engine     
VMAC7072       type are variables CP70BPS/IFA70BPS/ZIP70BPS/IFL70BPS    
Mar  5, 2019   and CP70ACS/IFA70ACS/ZIP70ACS/IFL70ACS in PDB.TYPE70PR.  
               and PDB.ASUMCELP (recommended LPAR analysis) and ASUM70LP
               (which is BY SYSTEM and has duplicate data.              
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 37.045  The CTG Version, CTGRVN was added to each of the CTG     
VMAC111        datasets created from SMF 111 Records and variables      
Mar  5, 2019   CTGIALRQ CTGLCNFA are kept in dataset TY111CXI.          
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 37.044  The BMC CMF Product generally updates VERSNRMF only on a 
VMAC7072       CMF Release Boundary; values of both 792 (2.2) and 794   
VMAC71         (2.3) exist on z/OS 2.3.  MXG does NOT use VERSNRMF for  
VMAC72         any logic, but this correction for CMF records sets the  
VMAC73         VERSNRMF=794 if it was 792 and RMFSRCL Record Level is   
VMAC74         81 or 82 depending on subtype.                           
VMAC75                                                                  
VMAC76                                                                  
VMAC77                                                                  
VMAC78                                                                  
VMAC79                                                                  
Mar  1, 2019                                                            
   Thanks to Joe Faska, DTCC, USA.                                      
                                                                        
Change 37.043  Executing MXG on ASCII under a VM product, or with WORK  
TECHNOTE       on a network drive, bad things can happen. We SRONGLY    
Feb 21, 2019   recommend keeping the WORK file local to the system on   
               which you are executing SAS.                             
               Two Known Errors:                                        
               -This error was found with WORK on a network drive:      
                 ERROR: Unable to obtain valid utility file pathname.   
               -This error was found under VM with WORK on a network    
                 drive:                                                 
                 ERROR: A lock is not available for WORK.OPTVAR.DATA.   
                 This one can be circumvented by adding                 
                    -filelockwait 30                                    
                 to your SAS command or as an OPTION in SAS.CFG file.   
                                                                        
                                                                        
Change 37.042  Change 37.024 did not protect for a blank WANTONLY, but  
READDB2        only generated a cosmetic error that %SYSFUNC did not    
Feb 19,2019    have right number of arguments.                          
                                                                        
Change 37.041  DCOLLECT APAR OA54879 reports that DCDEXFLG is NOT USED  
VMACDCOL       for zEDC compression and is now "DATA SIZES NOT VALID'   
Feb 19,2019    and is for non-VSAM Extended Format Data Sets.           
               Data set sizes that are not valid in either or both of   
               DCDUDSIZ or DCDCUDSZ variables, which might contain non  
               zero values, but should not be used.                     
   Thanks to Robert Chavez, FPL, USA.                                   
                                                                        
Change 37.040  Dataset TYPE749 variable R7491DEFCOMPRATIO wrong value   
VMAC74         is corrected to                                          
Feb 19,2019       IF R7491IOB GT 0 THEN                                 
                    R7491INFCOMPRATIO=R7491IIB/R7491IOB;                
                  ELSE R749INFCOMPRATIO=.;                              
               Variables were reversed in the calculation.              
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 37.039  Three MQ reports matching IBM's MQSMF program. Currently 
ANALMQ         the reports are a queue summary, a detail report of PUTS,
Feb 14,2019    and a detail report of GETS.  The GETS/PUTS reports can  
               be output to either or both SYSOUT or CSV files.         
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 37.038  Simple report that combines catalog records (TYPE6156)   
ANALHSM1       with HSM activity (HSMFSRST) to generate a report of     
Feb 14, 2019   datasets that may be thrashing between primary and       
               migration.                                               
   Thanks to Richard Way, Office Depot, USA.                            
                                                                        
Change 37.037  Updates found in the Jan 14, 2019 SMF Manual,            
FORMATS        with more changes to come in 37.03 when validated.       
VMAC124       -New Datasets                                             
VMAC41          TYPE42VO='PER-VOLUME STATISTICS'                        
VMAC42          TYPE42HI='HIGH RESPONSE TIME JOBS'                      
VMAC7072      -TYPE70 New variables                                     
VMAC74          SMF70_IPL_TIME   ='IPL*DATETIME*OF*PARTITION'           
VMAC78          SMF70_TRG_M_COUNT='TRG*MEMORY*CONSUMPTION*SAMPLES'      
Feb 19, 2019  -TYPE70TR New variable                                    
                TRG_MEM          ='TENANT*MEMORY*CONSUMPTION*MGBYTES'   
              -TYPE7002 New variables                                   
                R7023SCOPE='80X=CPC SCOPE*40X=SYSTEM*SCOPE'             
                R7023DID='DOMAIN*ID'                                    
              -TYPE70X2 New variables                                   
                R7024SCOPE='80X=CPC SCOPE*40X=SYSTEM*SCOPE'             
                R7024DID='DOMAIN*ID'                                    
              -TYPE70Y3 New variables                                   
                R7025SCOPE='80X-CPC SCOPE*40X=SYSTEM*SCOPE'             
                R7025DID  ='DOMAIN*ID'                                  
              -TYPE749 New Variables                                    
                R749LKID='SYNC*I/O*LINK*IDENTIFER'                      
              -TYPE78IO Change                                          
                R783DSTX relocated.                                     
              -TYPE41 Change                                            
                SKIP LOGIC protection for future, no impact now.        
              -TYPE 42 SUBTYPE 5 New Variables                          
                S42VRID1='DELAYS*TIME*1-10 MICROSEC'                    
                S42VRID3='DELAYS*TIME*100-10000 MICROSEC'               
                S42VRID4='DELAYS*TIME*1-10 MILLISEC'                    
                S42VRID5='DELAYS*TIME*10-100 MILLISEC'                  
                S42VRID6='DELAYS*TIME*OVER*100 MILLISEC'                
                S42VRIDM='MAXIMUM*I/O*INTERRUPT*DELAY TIME'             
                S42VRIDT='DATETIME*OF THE*MAXIMUM'                      
                S42VRIDA='AVERAGE*I/O*INTERRUPT*DELAY TIME'             
                S42VRBSY='TOTAL*BUSY*TIME'                              
                S42VRRSP='COMMANDS*DELAYED*BASE*RESERVED'               
                S42VRRSN='CHANNEL*PROGRAMS*WITH*RESERVE'                
                S42VRRES='DURATION*WHEN*RESERVED'                       
                S42VRREX='LONGEST*CONTINUOUS*RESERVED'                  
                S42VRRSR='AVERAGE*RESPONSE*PROGS WITH*RESERVE'          
              -TYPE 42 SUBTYPE 6 New Variables                          
                S42SNAVGARDELAY  ='AVG APPLICATION*RESUME*DELAY'        
                S42SNARDELAYCOUNT='AVG APPLICATION*RESUME*DELAYS'       
                S42DXMXI         ='STORAGE*SUBSYSID*FOR S42DSMXR'       
              -TYPE124 New variable                                     
                SM124S1WWPN='WORLDWIDE*PORT*NAME'                       
                                                                        
Change 37.036  Some IFA variables were not populated in the four output 
VMAC7072       datasets created by ASUM70PR; all IFA variable names are 
VMXG70PR       unchanged, but all "ZAAP" text in labels is now "ZCBP".  
Mar  5, 2019                                                            
                                                                        
Change 37.035  DB2 V12 overlooked Package Variables now INPUT and KEEP: 
VMACDB2         QPACAWLH         ='LATCH*WAIT*TIME'                     
Feb  7, 2019    QPACANLH         ='WAITS*TRACE*EVENTS*LATCH'            
Mar  5, 2019    QPACRLNU         ='THREADS*TO ROLL DATA'                
                QPACAACC         ='WAITS*TRACE*EVENTS*ACCELERATOR'      
                QPACAACW         ='WAIT TIME*ACCELERATOR*REQUESTS'      
                QPAC_PQS_WAIT    ='WAIT TIME*TO SYNC*PARALLEL*QUER'     
                QPAC_PQS_COUNT   ='SUSPENDS*WAITING*SYNC*PARALLEL'      
                QPAC_PIPE_WAIT   ='WAIT TIME*PIPE'                      
                QPAC_PIPE_COUNT  ='WAITS*FOR*PIPE'                      
                QPAC_COPYID      ='PACKAGE*COPY*ID'                     
              -Macros _N100/N101/_S100/_S101 defined for UTILBLDP.      
                                                                        
Change 37.034  Two more SMF 42 subtype 5 ABENDING invalid LENSR=520/592 
VMAC42         length values added to the test. APAR OA54668 corrects.  
Feb  7, 2019   LENSR IN(232,240,320,376,400,480,448,304,520,560,592,640)
                                                                        
Change 37.033  Support for Axway V3.3.2 2018/06/27 restructured User    
VMACAXWY       SMF record.                                              
Feb  6, 2019                                                            
   Thanks to Warren Cravey, FMR, USA.                                   
                                                                        
Change 37.032  TYPE749 z/EDC data, DIVIDE BY ZERO protection failed if  
VMAC74         both R7491DCT and R7491ICT were zero; R741BPS had been   
Feb  5, 2019   included in the test, but it's always non-zero so the    
               test now is IF SUM(R7491DCT,R7491ICT) GT 0 THEN          
         R749FPGBPRT=(1048576*R7491BPC/((R7491DCT+R7491ICT)*R7491BPS)); 
   Thanks to Harald Seifert, Huk-Coburg, GERMANY.                       
                                                                        
====== CHANGES THRU 37.031 WERE IN MXG 37.01 DATED Feb  3, 2019=========
                                                                        
Change 37.031  Bar charts of MIPS and % CPU added to the analysis work  
GRAFWLM        by IMPORTANCE, originally based on Peter Enrico's paper. 
Feb  3, 2019                                                            
                                                                        
Change 37.030  MXG 36.12-37.01 ASMRMFV ASI NOZEROCPU filter stopped     
ASMRMFV        filtering which could cause a significant increase in the
Feb  3, 2019   size of the RMFBSAM file and the PDB.ZRBASI dataset.     
               ASICPUTA_LF was added by Change 36.241 to that filter,   
               but it is an accumulated field that can not be used as it
               is always non-zero. NOZEROCPU is supported for z/OS 2.2+ 
              -Section 5 "Input Data Control Parameters" is updated.    
                                                                        
====== CHANGES THRU 37.029 WERE IN MXG 37.01 DATED Feb  1, 2019=========
                                                                        
Change 37.029  A reference line of the values for SMF70LAC (overall     
ANAL89         rolling 4 hour avg MSU) added to interval MSU charts.    
Feb  1, 2019                                                            
                                                                        
Change 37.028  Support for z/VM 7.1 (INCOMPAT, BROKEN CONTROL RECORD)   
VMACVMXA       due to insert in VXPRCDHF plus the change in HCPCPEID    
Jan 31, 2019   value for the Service Level test from '40061802 for 6.4  
Feb 14, 2019   to '10071802' for 7.1 that failed when tested for 'GE'/  
               New variable ZVMVERS='07.1.18.1' is created so GE can be 
               used for IF ZVMVERS GE tests.  There were 32 bytes added 
               to PRCDHF, but the 7.1 DSECT only shows on byte added.   
              -Heuristic (ZZQUCT+1) test revised, false positive caused 
               large VMDTTIME value.                                    
                                                                        
   Thanks to Graham Harris, RBS, ENGLAND.                               
                                                                        
Change 37.027  Example added to email the final condition code of a SAS 
EMAIL          job running in the backgroound on ASCII.                 
Jan 31, 2019                                                            
                                                                        
Change 37.026  If you create your own SUBSYSTEM that handles JES2 output
VMAC26J2       the SUBS value in SMF 26 records is not the expected 0002
Jan 30, 2019   for JES2 (or 0003 for JES3), but instead is a two byte   
               character field.  Previously, MXG TYPE26J2 only output   
               SUBS=2 execution purge records.  Now, if the SUBS is 3,  
               the JES3 record is deleted with MXGERROR messages that   
               TYPE26J3/BUILDPD3 must be used for JES3. If the SUBS is  
               other than 2, the records are presumed to be valid JES2  
               records, but MXGWARN messages print the SUBSYSTEM name.  
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 37.025  CICS variable A11ACTCI in CICS Statistics dataset CICDQG 
VMAC110        was INPUT but not KEPT.                                  
Jan 29, 2019                                                            
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 37.024  Using READDB2 with WANTONLY arguments DB2ST/DB2PST caused
READDB2        ERROR: Char Operand in the %EVAL, due to a superfluous   
Jan 29, 2019   AND in an %IF statement that also exposed that PDBOUT=YES
Feb  1, 2019   failed in the PROC SORT of the DB2STATx datasets.        
               The WANTONLY doc has been updated to note that           
                 WANTONLY DOES NOT SUPPORT DB2STATS DB2STATR DB2GBPST   
                 DB2STATB DB2SDTSBP AND DB2STAT5 DATASETS.              
   Thanks to Keith C. Shaffer, Cigna, USA.                              
   Thanks to James Cyr. Cigna, USA.                                     
                                                                        
Change 37.023  Unused Change Number.                                    
                                                                        
Change 37.022  The new $MGRMIPS format that maps IBM processor model to 
GRAFWRKX       MSU and MIPS capacity (created in 37.001) is now used in 
GRAFCEC        these Graphs, which use PDB.ASUMCELP which has variable  
Jan 28, 2019   CPCFNAME so MIPS can be calculated from percent busy:    
                 MIPS=PCTBUSY/100*PUT(CPCFNAME,$MGRMIPS.);              
               The CPCFNAME is constructed from CPU TYPE and MODEL as   
                  CPCFNAME=PUT(CPUTYPE,$HEX4.)!!'-'!!CPCMODEL;          
               programatically, or manually as '3906-420' for that z14. 
   Thanks to Ervin Claxon, CSX, USA.                                    
                                                                        
Change 37.021  If you run on ASCII with autoaloc=yes and did not put an 
VMXGALOC       execution of VMXGALOC in your IMACINIT (strongly our     
Jan 28, 2019   recommendation) but added a second execution of VMXGALOC 
               and the parameters did not precisely match those you used
               in BLDSMPDB and did not specify READONLY=YES to suppress 
               the aging off of old directories you could potentially   
               lose data as it deleted old directories. This change now 
               looks to see it you specified READONLY as NO and the     
               current days PDB has already been created it will        
               generate an MXGNOTE and set READONLY to YES.             
              -YR2KEEP and BASEYEAR parameters are added to let you     
               allocate a yearly PDB, Defaults to 0, so it won't be     
               created or allocated unless you enable it, and you will  
               need to update your BLDSMPDB to add the dataset names    
               you want created in the yearly directories.  Contact     
               support@mxg.com if you need help.                        
                                                                        
Change 37.020  Unused Change Number.                                    
                                                                        
Change 37.019  Documentation note for VMXGUOW/ASUMUOW.  If you have a   
VMXGUOW        tailored CICSTRAN dataset and have dropped any variables,
Jan 25, 2019   you may get an UNITIALIZED message for those variables in
               ASUMUOW. While this is an expected and non-critical error
               you can remove the error by editing the _KUOWIDC _KUOWCIC
               or _Kuowcix macros where the variables appear and simply 
               remove the variable(s) from the list.                    
                                                                        
Change 37.018  Support for STC HSC Subtype 32 & 33 create new datasets  
EXSTCV32          STCVSM32='RESERVED,INTERNAL USE'                      
EXSTCV33          STCVSM33='MVCPOOL USAGE'                              
VMXGINIT                                                                
VMACSTC                                                                 
Jan 27, 2019                                                            
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 37.017  Many non-fatal corrections were made to type 92:         
VMAC92        -Several 16-byte STCKE datetimes inputs were wrong:       
Jan 24, 2019   SMF92CCT,SMF92MCT,SMF92CCT,SMF92FSMN                     
              -GMT92OFF had to be relocated around the STCKE INPUT.     
              -Subtype 50+ have 72 byte data section, 32 for LT 50.     
              -Subtype 50 variables LRP-LRN only in SMF92EVENT=1,       
               and INPUT changed from &PIB.4.3 to &PIB.4.0.             
              -Subtype 50 variables OVS/OCH only in SMF92EVENT=4        
              -Poor Labels SMF92EVENT/SMF92VOL/SMF92CCHH/SMF92VCN       
               were enrichened.                                         
              -Subtype 50 SMF92OCH corrected format to HEX for CCHH.    
              -Variable SMF92ADN only kept in TYPE9217 dataset.         
              -Subtype 59 only the first instance was output.           
              -Subtype 52 and 54 had incorrect SKIP values.             
              -Subtype 58 SMF92TRL relocated outside the loop.          
              -Subtype 59 2 byte filler removed with STCKE fix.         
               This demonstrates the difficulty in writing new code     
               with no SMF records to test. SMF 92 code was updated     
               in Aug 2017 in Change 35.180, expecting a user to send   
               SMF data if problems were observed, and that didn't      
               happen until January 2019, with most of the above fixes  
               mostly done by these two users:                          
   Thanks to John Compton, World Programming Ltd, ENGLAND.              
   Thanks to Steve Bagshaw, ITMetrics, ENGLAND.                         
                                                                        
Change 37.016  Report showing total bytes/counts and min/max datetimes  
ANALID         for each SYSTEM is added as the second report.           
Jan 19, 2019                                                            
                                                                        
Change 37.015  Variable EDGRTIME had missing values with DATEFORM=E/A/I;
FORMATS        RHDTFORM logic moved ahead of EDGRTIME for H record and  
VMACEDGR       label corrected to EDGRTIME='REPORT*DATE TIME'           
Jan 20, 2019                                                            
   Thanks to Lindsay Oxenham, Department of Defence, AUSTRALIA.         
                                                                        
Change 37.014  INPUT EXCEEDED DB2STAT1 SMF 100 Subtype 1 NETEZZA/IDAA   
VMACDB2        record because IBM changed the length of OFFQ8ST segment 
Jan 18, 2019   but couldn't change LENQ8ST because it is a single field 
               in the header that should apply to all segments. But the 
               correct length is now set with LENQ8ST=Q8STNAME_OFF+8;   
               using the end of the name field for the actual length.   
   Thanks to Graham Harris, RBS, ENGLAND.                               
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 37.013  New example to count both TAPEDRVS and STEPS, and the    
ANALCNCR       Concurrency with only one pass of the data.              
Jan 20, 2019                                                            
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 37.012  z/VM Service Level 40061802 INPUT STATEMENT EXCEEDED due 
VMACVMXA       to VMMTRSYS inserting 60 bytes in the 1.04 record.       
Jan 17, 2019                                                            
   Thanks to Craig S. Bigler, Progressive Insurance, USA.               
                                                                        
Change 37.011  Variables QXFETCH/QWACSPEB UNINITIALIZED due to misspell.
VMXGUOW        Enhanced to make it easy to only process CICSTRAN data:  
Jan 19, 2019     IF  _LDB2ACC=_NULL_, DB2 data will not be read.        
Jan 25, 2019     IF  _INMQ=_NULL_ MQ data will not be read.             
               Counts of OBS before and after are created and if the    
               OBS reduction is LT 2, an MXGNOTE advises you to skip    
               using ASUMUOW which can be very CPU intensive and is     
               really needed for heavy CICS MRO sites, to cosolidate    
               those multiple CICSTRAN observations into one UOW,       
               Unit of Work observation.                                
   Thanks to Gary Keeres, Indianapolis Power & Light, USA.              
                                                                        
Change 37.010  Reserved Change Number.                                  
FORMATS                                                                 
VMAC89                                                                  
Jan 16, 2019                                                            
                                                                        
Change 37.009  The $%VGETOBS(DDNAME=&PDBMXG should be (DDNAME=&PDBMXG1  
GRAFCEC        although no error occurred unless you had set a value    
Jan 14, 2019   other than "PDB" for the location of the input PDB.      
   Thanks to Tom MacCabe, Dominion Energy, USA.                         
                                                                        
Change 37.008  Enhancement, addition of INCODE= parameter to allow      
GRAFWRKX       selection by date or system with your inserted code.     
Jan 11, 2019   Suppressed a no longer needed graphics catalog note.     
                                                                        
Change 37.007 -Support for Beta93 Version 6.2 subtypes 2 and 3, which   
VMACBETA       both have a lot of undocumented data: subtype 2 docs 140 
Jan 22, 2019   but length is 208 and subtype 3 docs 156 with 224 length.
                                                                        
Change 37.006 -If MXGDEBUG has length GT 0 and DSNSTRING or DATASET are 
VMXGPRAL       zero, debugging messages are created by VMXGPRAL.        
VMAC102       -Unmatched parens in data set labels read by VMXGPRAL     
Jan 11, 2019   caused non-fatal error messages for datasets with obs:   
                 ERROR: Expected close parenthesis after macro function.
               All MXG dataset's labels were examined and VMAC102 for   
               IFCIDs 84 85 86 87100 101 174 AND 175 were corrected.    
                                                                        
Change 37.005   Support for DB2 102 Trace IFCID/SUBTYPE 404 populates   
VMAC102         T102S404 (Authorization Compatibility) dataset with     
Jan 10, 2019    QW0404xx variables.                                     
   Thanks to Warren Cravey, FMR, USA.                                   
                                                                        
Change 37.004  Reading z/OS DATA using the SAS FTP Access method needs  
TECHNOTE       the RCMD='SITE RDW' argument:                            
Jan  9, 2019      FILENAME SMF FTP ("'SYS1.SMF'" "'SYS2.SMF'" ... )     
                          USER='XXXXXX' HOST='YYYYYYY' DEBUG            
                          S370VS RCMD='SITE RDW' LRECL=32760            
                          PASS='XXXXXXXX' PASSIVE;                      
               If RCMD is not used, the transfer will time out when     
               PASSIVE is specified, or will produce a RACF ERROR       
               if PASSIVE was not specified.                            
                                                                        
Change 37.003  SMF119 dataset TYP11952 variable SMF119ML_IP_IPV4 was    
VMAC119        wrongly compressed of blanks from variable TIRIP instead 
Jan  8, 2019   of from SMF119ML_IP_IPV4 in line 4519.                   
    Thanks to Randy Shumate, RELX Group, USA                            
                                                                        
Change 37.002 -SMF92 Subtype 8 INPUT STATEMENT EXCEEDED because the     
VMAC92         documented length of SMF92GDD in the SMF Manual is 4,    
Jan  8, 2019   but the length in the record is 8 bytes.                 
              -There were also numerous non-fatal corrections:          
              -SMF92 Subtype 50, SMF92STHCL missing period, and names   
               SMF90OIOCCL/SMF82VCX were corrected to SMF92.            
   Thanks to Miroslav Kubik, IBM Corportion, CZECH REPUBLIC.            
   Thanks to John Compton, World Programming Ltd, ENGLAND.              
                                                                        
Change 37.001 -Improve ability to propagate variables of interest to    
ADOCRMFV       multiple SAS data sets during RMF III PDB build.         
ASMRMFV       -RMF III CPCDB table fields CPC_CecMSU, CPC_LparMSU, and  
FORMATS        CPC_HomeLPName, are added to MXG01 record from the first 
VMACRMFV       MINTIME interval for each RMF III VSAM dataset at open,  
Jan  6, 2019   but those MXG01 values are the the values only at start. 
Jan 14, 2019  -Format $MGRMIPS is created to map GEIMODEL/GEIIMDL to    
Jan 29, 2019   create the CPC_CECMIPS using IBM's LSPRITR table:        
Feb  2, 2019   IBM Resource Link: Large Systems Performance Reference   
               https://www-01.ibm.com/servers/resourcelink/             
                  lib03060.nsf/pages/lspritrzOsv2r2?OpenDocument        
              -RMF III GEI table fields GEIMODEL and GEIMDL added to    
               MXG01 record from the first MINTIME interval for each    
               RMF III VSAM data set, but the MXG01 value is only the   
               RMF III start. But by RETAINing these fields from the    
               GEI and CPU records, and by relocating the write of the  
               GEI, CPU, and CPCDB records before the ASI records for   
               each interval, the CEC MODEL/Speed and MSU/MIPS capacity 
               variables CPC_CECNAME CPUCEMSU CPUCEMIPS CPULPMSU        
               GEIMODEL GEIIMDL and LPARNAME are populated in ZRBASI    
               and several other datasets.                              
              -NOTE: Not all the fields mentioned above are always      
               static.  Use the RMF III DATASET SWITCH option to force  
               RMF III to overwrite the oldest data set whenever it is  
               started if separation of configuration changes by data   
               set is desired.                                          
              -CSVQUERY macro added to show load module size in Change  
               36.241 for ASMRMFV destroyed pointer to SCT (Step Control
               Table).  This caused ASMPGM and ASMSTEPN fields in MXG00 
               record to be garbage and also in message in VMACRMFV.    
              -Section 12 "Messages" is updated.                        
              -In MXG 36.36 the fields GEIIMDL/GEIMODE were added to    
               ZRBASI, but they could be incorrect, precipitating       
               this change in logic in VMACRMFV.                        
                                                                        
LASTCHANGE: Version 37.