MXG Version 36.04 is  dated May  8, 2018, thru Change 36.091.   
        MXG Version 36.03 was dated Apr  2, 2018, thru Change 36.064.   
        MXG Version 36.02 was dated Mar  5, 2018, thru Change 36.050.   
First   MXG Version 36.01 was dated Feb  6, 2018, thru Change 36.026.   
Annual  MXG Version 35.36 was dated Jan  8, 2018, thru Change 35.309.   
        The Last MXG Newsletter SIXTY-NINE was dated Jan  3, 2018.      
Instructions for ftp download can be requested by using this form:                          
Your download instructions will be sent via return email.               
Contents of member CHANGES:                                             
I.    Current MXG Software Version 36.04 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 36.04.                  
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 in the "Newsletters" frame.                     
  Member CHANGES contains the changes made in the current MXG version.  
  Member CHANGESS contains all changes that have ever been made to MXG. 
  All MXG changes are also online at, in "Changes".  
I.  MXG Version 36.04 dated May  8, 2018, thru Change 36.091.           
==Major CHANGES added in MXG 36.04, dated May  8, 2018 thru 36.091.     
New Products Support                                                    
  TYPE122A 36.066  Support for IBM Devel z Systems IDZ SMF 122 record.  
  TYPE119  36.079  Support for SMF 119 subtypes 24, 38, 39, 40, and 45. 
  TYPEACF2 36.075  ACF2 INVALID SMF RECORD, ACSMFREL=0, should be 6.2.  
  TYPEIAM  36.071  INPUT STATEMENT EXCEEDED IAM 9.2 Length Changed.     
  TYPE7072 36.073  Support for z14 ZR1, new SMF70MAXPU variable COMPAT. 
  ANALID   36.081  Support for four-digit SMF Record type reporting.    
  TYPEDCOL 36.086  z/OS 2.3 DCOLLECT Encryption Variables added DCOLDSET
  TYPE99   36.072  New EWLM & SERV variables added to TYPE99_6 dataset. 
  CONFIG   36.067  MXG default CAPSOUT option for z/OS now NOCAPSOUT.   
ERROR Correction:                                                       
  TYPESTC  36.084  Dataset STCVSM11 Change 34.237 variables corrected.  
  TYPEDB2  36.082  DB2 BPHITRAT corrected.                              
  CONFIG   36.078  OPTION SORTBLKREC corrects DFSORT OC4 in SAS 9.4 M3. 
  TYPE110  36.077  CICDS Dispatcher Statisticw DSGTWT corrected.        
  TYPEBETA 36.074  Variables BETALOG reversed, subtype 51 doesn't match.
==Major CHANGES added in MXG 36.03, dated Apr  2, 2018 thru 36.064.     
New Products Support                                                    
  TYPEQACS 36.051  AS/400 Ver 7.3, INCOMPAT LRECL, undoc fields.        
  TYPE74   36.057  z/OS RMF 2.3 Enhancements, APARs, new SMF manual.    
  TYPEXBM  36.060  Support for BMC Extended Buffer Mgr XBM User SMF     
     All updates in the Jan, 2018, SMF Manual are included in 36.03.    
  TYPE74   36.056  DEVNR5HEX displays 5-hex-nybble zWrite DEVICE NR.    
  SMFINTRV 36.053  SMF Interval INTBTIME/INTETIME all DATETIME25.6      
ERROR Correction:                                                       
  TYPEVMXA 36.062  VXBYUSR deaccum corrected for new _MT1 variables.    
  TYPEXAM  36.061  Invalid SYTNLPS value in SYTCUP prevented output.    
  UTILBLDP 36.059  CHAR OPERAND FOUND if USERADD=ID was requested.      
  TYPE82   36.055  New TYPE8231 was misaligned, trunc 0203 protected.   
  BLDSMPDB 36.054  &PDBPATH was not initialized, when MTD requested.    
  ANALDB2R 36.058  36.02 Only, missing %END corrected.                  
==Major CHANGES added in MXG 36.02, dated Mar  5, 2018 thru 36.050.     
New Products Support                                                    
  TYPEIMS  36.040  Support for unpopulated IMS 56FA with APAR UI50912.  
  TYPEXCOM 36.047  Support for XCOM Version 36.02 (COMPATIBLE).         
  TYPENDM  36.046  Support for NDM-CDI Version 5.2, corrects NDMCPU plus
  TYPERHEL 36.043  Initial support for NMON Red Hat Linux RHEL monitor. 
  TYPE82   36.036  Support for new SMF 82 subtype 82 JOB-Level Crypto.  
ERROR Correction:                                                       
  TYPE119  36.038  "INVALID SMF 119 TYPE 81" corrected, not invalid.    
  TYPEDB2  36.037  Var QWHSACE missing from DB2STSBP sort, ABEND        
  ANALCAPD 36.042  ERROR: FOUND "IF" when the CEC= option was used.     
  TYPE7072 36.035  Incorrect LPAR/ZIP SHAR/SHAC if last engine was IFL. 
  MOBWORK  36.045  Enhanced Mobile Work 4 Hour MSU reporting datasets.  
  TYPEIMS  36.044  Variable IMSVERS, the value in your _IMSVERS is kept.
  TYPE70PR 36.039  TYPE70PR variable LPARZIPS, online zips, added.      
==Major CHANGES added in MXG 36.01, dated Feb  6, 2018 thru 36.026.     
New Products Support                                                    
  TYPE120  36.022  Support for Liberty SMF 120 ST 100 (COMPAT). 
  TYPEVMXA 36.025  Support for zVM64 Level 40061701/1702 (INCOMPATIBLE).
                   36.01 is required for these levels, Broken CR errors.
  TYPETPMX 36.024  Support for ThruPutManager Release 18.02 TMT7113.    
  TYPE70TR 36.003  New 70 Tenant Resource Group TRG updated/validated   
  TYPE72TR 36.003  New 72 Tenant Resource Group TRG updated/validated   
  TYPE89   36.003  New 89 Tenant Resource Group TRG updated/validated   
  UTILBPV  36.007  Program to examine the BPV cylinder value for EAV.   
  TYPE110  36.008  CICS/TS 5.3 CPU variables in Statistics CICM dataset.
  TYPEPOEX 36.002  PowerExchange updated, trashed CPU values, open prob.
ERROR Correction:                                                       
  TYPE42   36.023  Yet another STOPOVER ABEND, due to Invalid LENSR=232.
  TYPE0    36.009  INVALID TYPE 0 LENGTH=70 is valid, wrongly deleted.  
  TYPE30   36.012  The created GMTOFF30 could be .01 seconds plus/minus.
  PDBAUDIT 36.011  %PDBAUDIT(LIBNAMES="Not All" fails with syntax error.
  TYPE73   35.010  TYPE73 dataset, variable CHFXRATE slightly wrong.    
  TYPE119  36.008  Variable TTAPLDAT in dataset TYP11902 misaligned.    
  TYPE119  36.018  STOPOVER ABEND: SMF 119 Subtype 81, at IBM now.      
  TYPE115  36.005  QWHSDURN different in subtype 231, new vars, cleanup.
  TYPETCP  36.001  TYPETCP (archaic 118) APISTART date was on GMT.      
  TYPEBETA 36.015  ERROR when TYPEBETA and TYPE70 used together.        
    Please read CHANGESS for the complete list of major enhancements.   
  See member NEWSLTRS or the Newsletters frame at 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     
     Only on z/OS, SAS 9.4 "M5" requires MXG 35.36 because it adds the  
     NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect 
     that will be corrected in SAS Note 61672 defect.  See Change 35.309
     for more details on using NOERRORSTOP for your own PROC SQLs.      
     SAS V9.4 M5 Is RECOMMENDED, but MXG executes without error         
     using SAS Version 9.4 M0-M4 or SAS Version 9.3 M0-M2.              
     SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.      
     SAS V9.3   SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.  
                But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
                see CHANGE 29.169, IS REQUIRED:                         
                  The %MACRO compiler error is in processing %LET       
                  statements. While only two MXG members failed         
                  repeatedly in MXG QA tests on z/OS, there were random 
                  %LET errors in ASCII QA tests, so ANY use of %LET     
                  statement on ANY platform are vulnerable to this      
                  error, as the %MACRO compiler is SAS portable code,   
                  used on all platforms.  So this is NOT just an MXG    
                  error, but impacts ALL SAS programs.                  
                SAS9.3 is LEVEL A support from SAS.                     
     SAS V9.2   Was recommended, prior to 9.3, and was error-free with  
                MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to 
                use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2      
                Decompression Infile Exit.  but SAS V9.2 does execute on
                that platform.                                          
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
                Support level C by SAS Institute, Sep 30, 2013.         
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
                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)'                  
      or you can continue to use the MXGSAS94 JCL Procedure example.    
      MXG 26.03 thru MXG 35.36 will execute under the previously listed 
      SAS Versions on all supported platforms                           
      Unrelated to the above SAS Note/Hot Fix, ODS users will want to   
      use MXG 29.06+, because SAS V9.3 did expose incompatibilities in  
      MXG code for ODS reporting, that were fixed in MXG Version 29.06. 
      See Changes 29.159 and 29.169.                                    
      And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,  
      the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe). 
        Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors  
        can occur even though //XXXXXXXX DD is a valid SAS Data Library.
        This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does   
        NOT occur with SAS V9.2, nor with z/OS 1.9.  It can be          
        circumvented by adding a LIBNAME statement that specifies the   
        ENGINE name. See the Technical Note in Newsletters for SN-35332.
        Note that SAS V9.1.3 is now at "Level B" Support from SAS.      
      Old MXG code may continue to execute with SAS V8.2, but V8 is now 
      "Level C" support from SAS Institute, and there are known errors  
      in V8.2 that are only fixed in SAS V9.  I no longer QA with V8.2; 
      While many MXG programs (accidentally) will still execute under   
      V8.2, I cannot guarantee that all of MXG executes error free.     
      PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!           
         If you are absolutely stuck on V8, you need to copy MXG member 
         V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.           
      MXG Software has not executed under SAS V6 in many years.         
      The "PDB" libraries (i.e., SAS data libraries) must be created by 
      SAS V8 or later, but any of those data libraries can be read or   
      updated by the SAS Versions that MXG Supports, above.             
      For SAS Version V9.3:                                             
        SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note 
        SN43828 is REQUIRED.  See text of Change 29.159.                
        With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions    
        26.03 or later execute under SAS V9.3 on all platforms.         
        SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and  
        SAS V9.4 are interchangeable and can be read/written by any of  
        those versions, provided they are on the same platform.         
          BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the 
          same "platform" and attempting to read/use the FORMAT catalog 
          created on one of those "platforms" on the other "platform"   
          will error out to remind you of that difference!              
        SAS V9.4 did change some V9.3 ODS processing defaults and syntax
        that might cause errors with MXG 29.05 or earlier; MXG 29.06,   
        Change 29.160 documents the major revisions made in MXG to fully
        support ODS, and MXG 29.06 is STRONGLY recommended for ODS with 
        SAS V9.3 or SAS V9.4.                                           
      For (Archaic) SAS Version V9.2 (TS1M0):                           
        Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.  
        On z/OS, SAS changed the DSNAMES for some of the SAS libraries, 
        so you do need to use the new MXGSAS92 JCL Procedure for MXG,   
        but it still uses the CONFIGV9 configuration file.              
        However, NEW, and documented in Change 27.356, with SAS V9.2+:  
          The standard SAS JCL Procedure can be used for MXG:           
             // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                
          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.                                      
      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 ( is required Change 34.266.  
         and other errors with 3.00 or 3.01 have been corrected in the  
         current WPS version.                                           
      WPS Version 3.01.1 maintenance level 731 required for PDB to tape 
      WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.     
      WPS Version 3.01  is required for MOBILWRK, PICTURE fails in 2.5. 
      WPS Version 3.01  executed MXG 32.03 BUILDPDB with no errors.     
      WPS Version 3.0   requires MXG 31.09 (see Change 31.251).         
      WPS Version 2.4   required MXG 27.09 (see Change 27.239).         
      WPS Version 2.3.5 required MXG 27.05.                             
      See NEWSLETTERS for WPS Support Statement.                        
      WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID" 
      when the LIBNAME PDB does not exist; there would also have been a 
      prior log message  NOTE: Library PDB does not exist   as the clue.
IV.   MXG Version Required for Hardware, Operating System Release, etc. 
   MXG is usually NOT sensitive to z/OS Hardware changes, but:          
     The z/EC12 with 85+ engines required MXG 30.07.                    
     Support for 255 engines was added in MXG 31.04.                    
     The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.        
   However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was  
   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:               
                                       Availability     MXG Version     
      Product Name                     Date              Required       
      MVS/ESA 4.1                      Oct 26, 1990         8.8         
      MVS/ESA 4.2                      Mar 29, 1991         9.9         
      MVS/ESA 4.2.2                    Aug 15, 1991         9.9         
      MVS/ESA 4.3                      Mar 23, 1993        10.10        
      MVS/ESA 5.1.0 - compatibility    Jun 24, 1994        12.02        
      MVS/ESA 5.1.0 - Goal Mode        May  3, 1995        13.01        
      MVS/ESA 5.2.0                    Jun 15, 1995        13.05        
      MVS/ESA 5.2.2                    Oct 19, 1995        13.09        
      OS/390  1.1.0                    Feb 22, 1996        14.01        
      OS/390  1.2.0                    Sep 30, 1996        14.05        
      OS/390  1.3.0 Compatibility Mode Mar 28, 1997        14.14        
      OS/390  1.3.0 WLM Goal Mode      Mar 28, 1997        15.02        
      OS/390  2.4.0                    Sep 28, 1997        15.06        
      OS/390  2.5.0                    Feb 24, 1998        15.06        
      OS/390  2.6.0                    Sep 24, 1998        16.04        
      OS/390  2.7.0                    Mar 26, 1999        16.09        
      OS/390  2.7.0 APAR OW41318       Mar 31, 2000        18.03        
      OS/390  2.8.0                    Aug 24, 1999        16.09        
      OS/390  2.8.0 FICON/SHARK        Aug 24, 1999        17.08        
      OS/390  2.8.0 APAR OW41317       Mar 31, 2000        18.03        
      OS/390  2.9.0                    Mar 31, 2000        18.03        
      OS/390 2.10.0                    Sep 15, 2000        18.06        
      OS/390  PAV                      Oct 24, 2000        18.09        
      z/OS 1.1                         Mar 30, 2001        18.11        
      z/OS 1.1 on 2064s                Mar 30, 2001        19.01        
      z/OS 1.1 with correct MSU        Mar 30, 2001        19.02        
      z/OS 1.2                         Oct 31, 2001        19.04        
      z/OS 1.1,1.2 APARs to 78         Oct 31, 2001        19.05        
      z/OS 1.2+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.3+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.2 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.3 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.4 Tolerate                Sep 27, 2002        20.03        
      z/OS 1.4 Support                 Sep 27, 2002        20.06        
      z/OS 1.4 Over 16 CPUs/LPARs      May 29, 2003        21.02        
      z/OS 1.4 DFSMS/rmm, RACF         Aug 29, 2003        21.04        
      z/OS 1.5                         Mar 31, 2004        21.21        
      z/OS IRD ASUM70PR/ASUMCEC        Sep 22, 2003       *24.10        
      z/OS IRD TYPE70PR                Mar 11, 2004       *24.10        
      z/OS IRD TYPE70,RMFINTRV         Mar 22, 2002       *24.10        
      z/OS 1.6 - No IFAs               Sep 30, 2004       *22.09        
      z/OS 1.6 - With IFAs             Sep 30, 2004       *22.11        
      z/OS 1.7 (COMPATIBLE CHANGES)    Sep 30, 2005       *24.10        
      z/OS 1.7 (SPLIT70 CORRECTION)    Sep 30, 2005       *24.10        
      z/OS IFA data in RMF 79s         Sep 30, 2005        23.10        
      z/OS 1.8 - ASMTAPEE assembly     Sep 30, 2005       *25.03        
      z/OS 1.8 - SMF 119 INCOMPAT      Sep 30, 2005       *25.06        
      z/OS More than 32 LPARs          Jan 30, 2006       *24.24        
      z/OS SPLIT RMF 70 records        Jan 30, 2006       *24.24        
      z/OS Dupe SYSTEMs in a SYSPLEX   Jan 30, 2006       *24.02        
      z/OS IRD errors corrected        May 15, 2006        24.03        
      z/OS ASUMCEC errors corrected    May 15, 2006       *24.24        
      z/OS ASUM70LP errors corrected   Jun 13, 2006       *24.24        
      z/OS zIIP Processor Support      Jun 22, 2006       *24.24        
      z/OS Dedicated zIIP Support      Mar  8, 2008       *26.01        
      z/OS Dedicated zAAP Support      Mar  8, 2008        26.01        
      z/OS 1.8 (COMPATIBLE CHANGES)    Sep 20, 2006       *24.24        
      z/OS 1.9 (INCOMPAT, 54 CPs)      Sep 27, 2007        25.10        
      z/OS 1.9 MXGTMNT at ML-39 reASM  Sep 27, 2007        25.10        
      z/OS new z10 variables           Mar  5, 2008        26.01        
      z/OS 1.8 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.9 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.10 (INCOMPAT, MXG code)   Sep 15, 2008        26.07        
      z/OS 1.10 With HiperDispatch     Sep 15, 2008       *26.10        
      z/OS 1.10 RMF III, SMF 119       Jul 20, 2009        27.05        
      z/OS 1.11                        Sep  2, 2009        27.08        
      z/OS 1.11 New 30 variables       Apr 14, 2010       *28.02        
      z/OS 1.12                        Aug 17, 2010       *28.05        
      z/OS 1.12 SMF 85 Subtype 79      Aug 17, 2010       *29.03        
      z/OS 1.12 VMGUEST option         Aug 17, 2010       *29.06        
      z/OS 1.13                        Sep 30, 2011        29.03        
      z/OS 1.13 - MXGTMNT only         Dec 15, 2011        29.08        
      z/OS 1.13 SMF 119 ST 6 INCOMPAT  Feb  7, 2012        30.01        
      z/OS 2.1  - Most Records support Jul 23, 2013        30.05        
      z/OS 2.1  - ID=0 ERROR MESSAGE   Jul 23, 2013        31.07        
      z/OS 2.1  - ID=85 INCOMPAT       Jul 23, 2013        32.03        
      z/OS 2.1  - ID=70 SMF70CPA       Jul 23, 2013        32.03        
      z/OS 2.1  - INPUT STATEMENT EXCEEDED ERROR SMF 74    33.10        
      z/OS 2.2  COMPATIBLE CH 33.189   Aug 19, 2015        33.08        
      z/OS 2.2 MXGTMNT ABEND S0E0-28   Sep 15, 2015        33.09        
               REQUIRES ASMTAPE ML-55  Sep 15, 2015        33.09        
      z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr  5, 2016        34.02        
      z/OS 2.2 SPLIT 73, ABEND 33.068  Apr  5, 2016        34.02        
      z/OS 2.2 JES2 8-char JOBCLASS    Oct  7, 2016        34.07        
      z/OS 2.2 NEW SMF 124 IOS Spvr    Oct  7, 2016        34.07        
      z/OS 2.3 Many new variables      Sep 24, 2017 35.166 35.09*       
      z/OS 2.3 RMF III Support         Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 2 st 2 STOPOVER    Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 90 st 38 STOPOVER  Sep 24, 2017 35.199 35.09*       
      z990 CPUs - CPUTYPE '2084'x      Aug 25, 2003        21.04        
      z890 CPUs - CPUTYPE '2086'x      Jun 24, 2004        22.07        
      z9   CPUs - CPUTYPE '2094'x      Jul 20, 2005       *24.24        
      z9EC CPUs - CPUTYPE '2094'x:                                      
             with 64-bit z/OS - no change required        *24.24        
             with 32-bit z/OS only:    Aug 26, 2006        24.06        
      z9BC CPUs - CPUTYPE '2096'x:                                      
             with 64-bit z/OS - no change required         24.01        
             with 32-bit z/OS only:    Jul 27, 2006       *24.24        
      z10  CPUs - CPUTYPE '2097'x      Dec  7, 2008        25.11        
      z10  HiperDispatch/Parked Time   Mar  3, 2008       *26.10        
      z196 (INCOMPAT IF GT 64 ENG)     Aug 17, 2010        28.05        
      zEC12                            Nov 14, 2012        30.07        
      z13   non-SMT Mode               May 27, 2014        32.05        
      z13   SMT Mode Change 33.217     Sep 15, 2015       *33.09        
      z13   SMT Mode NRZIPCPU 34.106   May 10, 2016        34.03        
      z13   SMT MT=2 CPUZIPTM TYPE70   Mar 21, 2016        35.03        
      z14   SMF 113 Records INCOMPAT   Oct  2, 2017        35.09        
      CICS/CTG V9 Transaction Gateway  ??  ??  2013        31.31        
      CICS/ESA 3.2                     Jun 28, 1991         9.9         
      CICS/ESA 3.3                     Mar 28, 1992        10.01        
      CICS/ESA 4.1                     Oct 27, 1994        13.09        
      CICS/ESA 5.1 aka CICS/TS V1R1    Sep 10, 1996        14.07        
      CICS-Transaction Server V1R1     Sep 10, 1996        14.07        
      CICS-TS V1R1 with APAR UN98309   Sep 15, 1997        15.06        
      CICS-TS V1R2  CICS/TS 1.2        Oct 27, 1997        15.06        
      CICS-TS V1R3  CICS/TS 1.3        Mar 15, 1999        17.04        
      CICS-TS V2R1  CICS/TS 2.1        Mar 15, 2001        18.11        
      CICS-TS V2R2  CICS/TS 2.2        Feb  9, 2002        19.19        
       CICSTRAN subtype 1 support only                    *19.19        
       CICSTRAN subtype 2 completed                       *19.08        
      CICS-TS V2R3  CICS?TS 2.3        Dec 19, 2003                     
       Using UTILEXCL to create IMACEXCL:                  21.04        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04        
      CICS-TS V2R3  CICS/TS 2.3        Aug 13, 2004        22.04        
      CICS-TS V3R1  CICS/TS 3.1        Jan 18, 2005        22.22        
      CICS-TS for Z/OS Version 3.1     Mar 15, 2005                     
       Using UTILEXCL to create IMACEXCL:                  22.13        
       Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22        
      CICS-TS V3R2  CICS/TS 3.2        Dec  6, 2007        25.11        
      CICS-TS for Z/OS Version 3.2     Jun 29, 2007        25.03        
      CICS-TS/3.2 Compressed Records   Nov  3, 2007        25.11        
      CICS-TS/4.1 (CICSTRAN INCOMPAT)  Mar 13, 2009        27.01        
      CICS-TS/4.1 (STATISTICS ST=2)    Sep 18, 2009        27.08        
      CICS-TS/4.2 CICSTRAN/STATISTICS  Jun 24, 2011        29.03        
      CICS-TS/4.2 CICSRDS MNSEGCL=5    Jun 24, 2011       *29.05        
      CICS-TS/4.2 INVALID STID=116     Jan 31, 2012       *30.01        
      CICS-TS/5.1 (INCOMPATIBLE)       Dec 14, 2012       *30.08        
      CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013       *30.30        
      CICS-TS/5.1 MNSEGCL=5 INCOMPAT   Jun 17, 2013       *31.03        
      CICS-TS/5.2 COMPATIBLE CICSTRAN  Jun 13, 2014       *31.03        
      CICS-TS/5.2 INCOMPAT Statistics  Jun 13, 2014       *32.03        
      CICS-TS/5.3 INCOMPAT CICSTRAN    Apr 29, 2015        33.04        
      CICS-TS/5.3 RESOURCE SEGCL=5     Sep 31, 2015        33.09        
      CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015        33.11        
      CICS-TS/5.3 GA date              Dec 11, 2015        33.33        
      CICS-TS/5.3 MNSEGCL=5 INPUT ERR  Mar 21, 2016        34.02        
      CICS-TS/5.4 OPEN BETA  Aug       Aug 11, 2016        34.06        
      CICS-TS/5.4 OPEN BETA  Nov       Nov 11, 2016        34.09        
      CICS-TS/5.4 GA                   Jun 17, 2017        35.03        
      DB2 2.3.0                        Oct 28, 1991        10.01        
      DB2 3.1.0                        Dec 17, 1993        13.02        
      DB2 4.1.0 Tolerate               Nov  7, 1995        13.07        
      DB2 4.1.0 Full support           Sep 11, 1996        14.07        
      DB2 5.1.0 Tolerate               Jun 27, 1997        14.14        
      DB2 5.1.0 Full support           Jun 27, 1997        15.02        
      DB2 6.1.0 initial support        Mar 15, 1999        16.09        
      DB2 6.1.0 all buffer pools       Mar 15, 1999        18.01        
      DB2 6.1.0 parallel DB2           Mar 15, 1999        19.19        
      DB2 7.1.0 parallel DB2           Mar 31, 2001        19.19        
      DB2 7.1.0 corrections            Mar 31, 2001        20.06        
      DB2 8.1 Tolerate, no packages    Mar 31, 2004        20.20        
      DB2 8.1 New Data Packages wrong  Mar 31, 2004        21.08        
      DB2 8.1 Support with Packages    Mar 31, 2004       *23.09        
      DB2 8.1 with all zIIP Variables  Sep 30, 2006        24.08        
      DB2 8.1 +PK47659                 Sep 12, 2008        26.08        
      DB2 9.1 See Change 25.265.       Dec  7, 2007        25.11        
      DB2 9.1 Full Support +PK/56356   Sep 12, 2008        26.08        
      DB2 10.1 Tolerate                Oct  1, 2010        28.06        
      DB2 10.1 New vars + Compressed   Nov  1, 2010       *28.07        
      DB2 10.1 Invalid Header pre APAR Jan 12, 2011       *28.28        
      DB2 10.1 IFCID=225 INCOMPAT      Sep 23, 2011       *29.07        
      DB2 10.1 QWHCCV for QWHCATYP=8   Oct  3, 2011       *30.07        
      DB2 10.1 DBID/OBID decode        Jan 21, 2013       *30.30        
      DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013       *31.04        
               (ONLY IMPACTS DB2STATS)                                  
      DB2 11.1 TOLERATE DB2 V11.1      Jun 21, 2013        30.30        
      DB2 11.1 DB2STATS QLST CORRECT   Jun 21, 2013        31.04        
      DB2 11.1 SUPPORT NEW VARIABLES   Jun 21, 2013        31.08        
      DB2 11.1 IRLM NEW SEGMENT        Jun 21, 2013        32.10        
      DB2 12.1 COMPATIBLE              Oct  5, 2016        34.08        
      DB2 12.1 NETEZZA CORRECTIONS     Oct  5, 2016        34.08        
      DB2 12.1 QLAC INSERTS DB2ACCT    May 15, 2017        35.05*       
      DFSMS/MVS 1.1                    Mar 13, 1993        11.11        
      DFSMS/MVS 1.2                    Jun 24, 1994        12.02        
      DFSMS/MVS 1.3                    Dec 29, 1995        13.09        
      DFSMS/MVS 1.4                    Sep 28, 1997        15.04        
      DFSMS/MVS 1.4 HSM                Sep 23, 1998        16.04        
      DFSMS/MVS 1.5                    ??? ??, 1999        16.04        
      DFSORT SMF V1R5                  Mar  1, 2006        24.02        
      MQM 1.1.2, 1.1.3, 1.1.4          Apr 25, 1996        14.02        
      MQ Series 1.2.0                  May 26, 1998        16.02        
      MQ Series 2.1.0                  Oct  2, 1999        17.07        
      MQ Series 5.2                    Dec 16, 2000        18.10        
      MQ Series 5.3                    Dec 16, 2002        21.05        
      MQ Series 6.0                    Feb 14, 2006        23.23        
      Websphere MQ Series 7.0          ??? ??, 2009       *28.06        
      Websphere MQ Series 7.1          MAR 12, 2011        29.03        
      Websphere MQ Series 8.0          Jun 24, 2011        29.05        
      Websphere MQ Series 9.1          Mar 20, 2017        35.03        
      NETVIEW 3.1 type 37              ??? ??, 1996        14.03        
      NPM 2.0                          Dec 17, 1993        12.03        
      NPM 2.2                          Aug 29, 1994        12.05        
      NPM 2.3                          ??? ??, 1996        15.08        
      NPM 2.4                          Nov 18, 1998        17.01        
      NPM 2.5                          Feb ??, 2000        18.02        
      NPM 2.6                          Nov ??, 2001        19.06        
      RMDS 2.1, 2.2                    Dec 12, 1995        12.12        
      RMDS 2.3                         Jan 31, 2002        19.11        
      TCP/IP 3.1                       Jun 12, 1995        12.12        
      TCP/IP 3.4                       Sep 22, 1998        16.04        
      WebSphere 5.0 APAR PQ7463        Aug 19, 2003        21.04        
      WebSphere 6.0                    Feb 18, 2006        23.23        
      WebSphere 7.0                    Oct  7, 2010        28.06        
      WebSphere 8.0                    Jul 17, 2011        29.05        
      DOS/VSE POWER V6.3.0             Dec 19, 1998        16.08        
      VM/ESA  2.0                      Dec 23, 1992        10.04        
      VM/ESA  2.1                      Jun 27, 1993        12.02        
      VM/ESA  2.2                      Nov 22, 1994        12.06        
      VM/ESA  2.3                      Jun  1, 1998        16.08        
      VM/ESA  2.4                      Mar  1, 2001        19.03        
      z/VM    3.1                      Mar  1, 2001        19.03        
      z/VM    3.1 DATABYTE=0           May  2, 2002        20.02        
      z/VM    4.2 ??                   May  2, 2002        20.02        
      z/VM    4.4                      Jan 22, 2005        22.22        
      z/VM    5.1                      Jan 22, 2005        22.22        
      z/VM    5.2                      Jan 22, 2006        24.01        
      z/VM    5.3 TOLERATE             Jun  7, 2007        25.05        
      z/VM    5.3 NEW VARIABLES        Sep 12, 2008        26.08        
      z/VM    5.4 (COMPATIBLE)         Sep 12, 2008       *27.01        
      z/VM    6.1 (NO CHANGES)         Jul  7, 2008        27.01        
      z/VM    6.2                      Dec  2, 2011        29.04        
      z/VM    6.3 INCOMPATIBLE         Jul 23, 2013        31.05        
      z/VM    6.3 z/13                 Jan 23, 2016        33.33        
      z/VM    6.4 SYTLCK Incompat      Apr 26, 2016        34.04        
      IMS log 4.1                      Jul  4, 1994        12.02        
      IMS log 5.1                      Jun  9, 1996        14.05        
      IMS log 6.1                      ???  ?, 199?        20.03        
      IMS log 7.1                      ???  ?, 200?        20.03        
      IMS log 8.1                      May 21, 2003        21.02        
      IMS log 9.1                      Mar 96, 2004       *26.01        
      IMS log 10.1                     Mar 06, 2007       *26.01        
      IMS log 11.1                     Apr  1, 2010       *28.02        
      IMS log 12.1                     Jan 23, 2012       *29.29        
      IMS log 13.1 (NOT 56FA)          May 25, 2013        31.03        
      IMS log 13.1 (56FA RECORD)       May 27, 2014        32.05        
      IMS log 14.1 COMPATIBLE          Dec 19, 2015        35.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        
       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        
       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        
       ACF2 6.2                                            16.04        
       ASTEX 2.1                                           14.04        
       IDMS 18                                             32.05        
       IDMS 19 (INCOMPAT after PTF R084146 Change 34.164)  33.05        
       NETSPY 4.7                                          14.03        
       NETSPY 5.0                                          14.03        
       NETSPY 5.2                                          16.05        
       NETSPY 5.3                                          18.03        
       NETSPY 6.0                                          20.10 20.305 
       NETSPY 7.0                                          20.10 20.305 
       SAR/VIEW R11                                        23.07 23.196 
      BMC, was Boole & Babbage                                          
       APPTUNE V11R2 SMF 102                               33.11 33.264 
       IMF 3.1 (for IMS 5.1)                               12.12        
       IMF 3.2 (for IMS 6.1 only)                          15.09        
       IMF 3.2 (for IMS 5.1 and 6.1+)                      16.04        
       IMF 3.3 (for IMS 7.1 and 8.1)                      *22.08        
       IMF 4.1 (for IMS 9.1)                              *26.02        
       IMF 4.4 (for IMS 9.1)                              *31.08        
       IMF 4.5 (for IMS 11.1)  (No change since 4.4)       31.08        
       IMF 4.6 a/k/a Mainview IMS                         *31.08        
       IMF 5.1 a/k/a Mainview IMS                         *34.01        
       IMF 5.2 a/k/a Mainview IMS                          34.01        
       Mainview for MQ Version 4.4                         29.03        
       Mainview for MQ Version 5.1                         30.02        
       Mainview for MQ Version 5.2                         33.01        
       Mainview for CICS Version 6.5 (CICS/TS 5.1)         30.30        
       Mainview for CICS Version 6.4 (CICS/TS 4.2)         30.04        
       Mainview for CICS Version 6.1                       26.26        
       Mainview Auto Operator data file                    28.28        
       Mainview for DB2 THRDHIST file                      20.20        
       Mainview for TCP/IP                                 20.20        
       Mainview for IP                                     34.??        
       Mainview for Batch Optimizer                        19.19        
       LMS 3.1                                             12.12A       
      Oracle V9, V10                                       24.06        
       2.1                                                 33.05        
       1.4                                                 33.08        
       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.04.                  
 1. Incompatibilities introduced in MXG 36.04:                          
  a- Changes in MXG architecture made between 36.04 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            
 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 36.04 after MXG 35.36:    
  Member   Change    Description                                        
  ANALCAPD 36.042  ERROR: FOUND "IF" when the CEC= option was used.     
  ANALID   36.081  Support for four-digit SMF Record type reporting.    
  ASCIIDSN 36.020  ASCII version of JCLDAYDS with SAS FTP for TMC/DCOL. 
  CONFIG   36.067  MXG default CAPSOUT option for z/OS now NOCAPSOUT.   
  CONFIG   36.078  OPTION SORTBLKREC corrects DFSORT OC4 in SAS 9.4 M3. 
  DOCUMENT 36.013  APAR OA27291 OC4 USEZOSV1R9RULE(NO) z/OS 1.10+       
  MOBWORK  36.045  Enhanced Mobile Work 4 Hour MSU reporting datasets.  
  PDBAUDIT 36.011  %PDBAUDIT(LIBNAMES="Not All" fails with syntax error.
  TYPE0    36.009  INVALID TYPE 0 LENGTH=70 is valid, wrongly deleted.  
  TYPE110  36.008  CICS/TS 5.3 CPU variables in Statistics CICM dataset.
  TYPE110  36.077  CICDS Dispatcher Statisticw DSGTWT corrected.        
  TYPE115  36.005  QWHSDURN different in subtype 231, new vars, cleanup.
  TYPE119  36.008  Variable TTAPLDAT in dataset TYP11902 misaligned.    
  TYPE119  36.018  STOPOVER ABEND: SMF 119 Subtype 81, at IBM now.      
  TYPE119  36.038  "INVALID SMF 119 TYPE 81" corrected, not invalid.    
  TYPE119  36.079  Dupport for SMF 119 subtypes 24, 38, 39, 40, and 45. 
  TYPE120  36.022  Support for Liberty SMF 120 ST 100 (COMPAT). 
  TYPE122A 36.066  Support for IBM Devel z Systems IDZ SMF 122 record.  
  TYPE30   36.012  The created GMTOFF30 could be .01 seconds plus/minus.
  TYPE42   36.023  Another invalid LENSR=232, STOPOVER ABEND OA54668.   
  TYPE7072 36.035  Incorrect LPAR/ZIP SHAR/SHAC if last engine was IFL. 
  TYPE70PR 36.039  TYPE70PR variable LPARZIPS, online zips, added.      
  TYPE70TR 36.003  New 70 Tenant Resource Group TRG updated/validated   
  TYPE72TR 36.003  New 72 Tenant Resource Group TRG updated/validated   
  TYPE73   35.010  TYPE73 dataset, variable CHFXRATE slightly wrong.    
  TYPE82   36.036  Support for new SMF 82 subtype 82 JOB-Level Crypto.  
  TYPE89   36.003  New 89 Tenant Resource Group TRG updated/validated   
  TYPE99   36.072  New EWLM & SERV variables added to TYPE99_6 dataset. 
  TYPEACF2 36.075  ACF2 INVALID SMF RECORD, ACSMFREL=0, should be 6.2.  
  TYPEBETA 36.015  ERROR when TYPEBETA and TYPE70 used together.        
  TYPEBETA 36.074  Variables BETALOG reversed, subtype 51 doesn't match.
  TYPEDB2  36.037  Var QWHSACE missing from DB2STSBP sort, ABEND        
  TYPEDB2  36.082  DB2 BPHITRAT corrected.                              
  TYPEDCOL 36.086  z/OS 2.3 DCOLLECT Encryption Variables added DCOLDSET
  TYPEIAM  36.071  INPUT STATEMENT EXCEEDED IAM 9.2 Length Changed.     
  TYPEIMS  36.040  Support for unpopulated IMS 56FA with APAR UI50912.  
  TYPEIMS  36.044  Variable IMSVERS, the value in your _IMSVERS is kept.
  TYPENDM  36.046  Support for NDM-CDI Version 5.2, corrects NDMCPU plus
  TYPEPOEX 36.002  PowerExchange updated, trashed CPU values, open prob.
  TYPERHEL 36.043  Initial support for NMON Red Hat Linux RHEL monitor. 
  TYPESTC  36.084  Dataset STCVSM11 Change 34.237 variables corrected.  
  TYPETCP  36.001  TYPETCP (archaic 118) APISTART date was on GMT.      
  TYPETPMX 36.024  Support for ThruPutManager Release 18.02 TMT7113.    
  TYPEVMXA 36.025  Support for zVM64 Level 40061702 (INCOMPATIBLE).     
  TYPEXCOM 36.047  Support for XCOM Version 36.02 (COMPATIBLE).         
  UTILBPV  36.007  Program to examine the BPV cylinder value for EAV.   
  TYPE7072 36.073  Support for z14 ZR1, new SMF70MAXPU variable COMPAT. 
  See member CHANGESS for all changes ever made to MXG Software, or     
  the CHANGES frames at                             
Inverse chronological list of all Changes:                              
====== Changes thru 36.091 are in MXG 36.04 dated May  8, 2018==========
Change 36.091  If DB2ACCT existed but had 0 OBS input was set to _NULL_ 
VMXGUOW        resulting in many UNITIALIZED variable messages. VMXGUOW 
May  7, 2018   now checks only for the existence of the dataset and if  
               it does not exist sets it to _NULL_.                     
Change 36.090  If you tailored IMACDB2 to redefine MACRO _Lxxxxxx's and 
ANALDB2R       you specified only a single level name, so those datasets
May  3, 2018   are written to WORK, and did not specify a PDBOUT,       
               you could get this syntax error                          
               due to incorrect logic, now corrected, in ANALDB2R.      
               Originally posted to MXG-L as possible issue with SAS    
               V9.3 to V9.4 migration, the thread was updated/corrected.
               Change 31.104, MXG 31.03, May 2013, created the exposure;
               the user's good run was with MXG 31.01.                  
   Thanks to Dennis Longnecker, State of Washington Courts, USA.        
Change 36.089  APAR OA54884 for z/OS 2.3 ONLY reports very high I/O EXCP
DOCUMENT       counts in EXCPTOTL (Address Space Total, SMF30TEX) that  
May  1, 2018   was observed in the MASTER address space, but could occur
               in any address space.                                    
Change 36.088  SAS Note 51008 Java versions 1.6/1.7/1.8 can cause errors
DOCUMENT        ERROR: The Java proxy could not create a new xxxxxxxx.  
May  1, 2018    ERROR: shmag() failed in Java extension rc -1 errno 124 
                ERROR: Unable to attach current thread.                 
               on z/OS.  That Note the circumvention is to add this line
               to your SASHLQ.CONFIG(SITE) configuration PDS member.    
               SAS Support reported SAS does not support Java 8 yet;    
               see also SAS Note 51195.                                 
Change 36.087  Support for SRDF Version xxx.                            
VMACSRDF       indicates if the LCU contains at least one FICON channel.
Apr 27, 2018   In Progress, coded, but untested with longer records.    
Change 36.086  DCOLLECT Encryption Variables are now kept in DCOLDSET:  
VMACDCOL       indicates if the LCU contains at least one FICON channel.
Apr 24, 2018     DCDTYPE ='ENCRYPTION*TYPE'                             
                 DCDKLBL ='ENCRYPTION*KEY*LABEL'                        
               The IBM Documentation does not provide DCDTYPE values to 
               decdode.  These fields were added by z/OS 2.3.           
   Thanks to Mike Creech, Black Knight, USA.                            
Change 36.085  Variable IOPDSTX is now kept in TYPE78IO dataset; bit 1  
VMAC78         indicates if the LCU contains at least one FICON channel.
Apr 24, 2018                                                            
   Thanks to Lane Thorne, Honda of America Manufacturing, USA.          
Change 36.084  Dataset STCVSM11 variables added by Change 34.237 were   
VMACSTC        incorrectly labeled and inconsistent, now corrected:     
Apr 23, 2018     STC11NHR='HOST*INTERFACE*I/OS'                         
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
Change 36.083  EXPDBINC EXPDBVAR EXPDBCDE can now be used with UTILBLDP 
UTILBLDP       and BUILDPDB=NO so you can create your own custom dataset
Apr 27, 2018   with control of variables, etc.  This example creates the
               PDB.SMFHEADER dataset with four variables kept from every
               SMF header:                                              
                  %UTILBLDP(USERADD=ID 118,BUILDPDB=NO,                 
                       (KEEP=SYSTEM SMFTIME ID SUBTYPE),                
                     EXPDBCDE=OUTPUT PDB.SMFHEADER;,                    
                   %INCLUDE INSTREAM;                                   
              -Unrelated, unprintable '08'x character introduced 35.09  
               is removed.                                              
   Thanks to Randy Hewitt, DXC, USA.                                    
Change 36.082  Correction for DB2 BPHITRAT variable to replace the sum  
VMACDB2        of RIO/SPP/DPP/LPP with DIO/LIO/RIO/SIO.                 
Apr 19, 2018                                                            
Change 36.081  Support for four-digit SMF Record Type ID (MAX 2047) for 
ANALID         the ANALID report.                                       
FORMATS       -Format $MGSMFID text shifted one byte to the right; a few
IMACSMFF       record descriptions lost 1 character to keep 37 maximum. 
VMACID        -VMACID,VMACSMF formats are now SMFIDSUB $8. SMFIDCH $4.  
VMACSMF        increasing the LENGTH of those variables by one byte,    
Apr 23, 2018   format 7.3 references are changed to 8.4 for IDANDSUB.   
Apr 27, 2018  -Unfortunately, if you have used IMACSMFF to label your   
               user SMF Record Descriptions, you will need to replicate 
               all and insert a blank at the beginning of each existing 
               3-character record type, to match the new example in that
               IMACSMFF member:                                         
                 '2047.001'='2047.001:MAX POSSIBLE VALUE AND LABEL'     
              -One line summary report with total records and bytes and 
               the time range of the input SMF file is added.           
Change 36.080  VMXGGETM utility accepts SMF selection syntax nnnn.mmm   
VMXGGETM       where nnnn is the SMF Record Type (max is now 2047) and  
Apr 18, 2018   where mmm is the subtype.  VMXGGETM creates an output SMF
               file with example records of each selected type.         
Change 36.079 -Support for new SMF 119 subtypes 24, 38, 39, 40, and 45. 
EXT11924       creates these new datasets:                              
EXT11938         dddddd   Dataset   Description                         
EXT11939         T11924  TYP11924  TNPROFILE                            
EXT11940         T11938  TYP11938  SmcdLnkStats                         
EXT11945         T11939  TYP11939  SmcdLnkStart                         
IMAC119          T11940  TYP11940  SmcdLnkEnd                           
VMAC119          T11945  TYP11945  IsmStats                             
VMXGINIT       Untested with data.                                      
Apr 18, 2018  -New BitRate variables added to TYP11906 dataset:         
Apr 26, 2018     IFINBITRT='INBOUND*BITS PER*SECOND'                    
                 IFOUBITRT='OUTBOUND*BITS PER*SECOND'                   
                 IFBITRATE='TOTAL*BITS PER*SECOND'                      
              -CO:Z subtypes 192 and 193 are validated with data.       
Change 36.078  z/OS, SAS 9.4 M3 with IBM DFSORT, ABEND 0C4 in SASVZSR1, 
CONFIGxx       when sorting a large dataset. SAS notes 57676 and 58629  
Apr 17, 2018   circumvent the error with these options                  
               which could alternately be specified in your CONFIGxx,   
               but SORTBLKMODE has been the SAS Default for years. The  
               SORTBLKREC option is not yet documented by SAS.          
               This is documentation only, no code was changed.         
Change 36.077  With a BY statement in your VMXGSUM INCODE, there is no  
VMXGSUM        guarantee that the data order will be correct, and if you
Apr 14, 2018   also  %LET MXGSUMCLASS=YES or CLASSNWAY to YES, the data 
May  8, 2018   step may fail. VMXGSUM now looks at the first word in the
               INCODE= and if it is BY sets CLASSNWAY to NO.            
Change 36.076  CICS Statistics Dispatcher CICDS dataset set DSGTWT to   
VMAC110        DURATM when DSGTWT was greater (Change 35.264), but that 
Apr 14, 2018   should only have been done for SMFSTRQT='INT' as DURATM  
               doesn't exist in the 'REQ', 'USS', nor 'EOD' records.    
   Thanks to Paul Volpi, UHC, USA.                                      
VMACACF2       MXG tests for the last release, 6.2, but new ACF2 record 
Apr 14, 2018   has '00'x instead of '62'x in byte 119, causing MXG test 
               for 6.2 to fail.  This change forces ACSMFREL=6.2 if it  
               is zero for this INCOMPATIBLE CHANGE to the ACF2 record. 
               The CA fix is PI24126 and a reassembly of DMGSMF exit.   
   Thanks to Michael K Yuan, Navy Federal Credit Union, USA.            
Change 36.074  Variables BETALOG in BETA50 and B97LOG in BETA9750 were  
VMACBETA       reversed, OFF was ON and ON was OFF, bit test corrected. 
VMACBE97       Beta97 RDATA fields subtype 51 don't match documentation,
Apr 17, 2018   await reply from vendor for those fields.                
   Thanks to Andreas Menne, Finanz Informatik, GERMANY.                 
Change 36.073  Support for z14 ZR1 adds new variable to TYPE70 dataset: 
Apr 12, 2018                                                            
Change 36.072  Variables now INPUT for TYPE99_6 subtype 6 dataset:      
VMAC99            PSERV        ='SERVICE*DURING*INTERVAL'               
Apr 12, 2018      PISERV       ='ZAAP*SERVICE*DURING*INTERVAL'          
                  PSSERV       ='ZIIP*SERVICE*DURING*INTERVAL'          
                  TIME_AT_PDP_USING='TIME AT*PDP USING*SAMPLES'         
                  TIME_AT_PDP    ='TIME AT*PDP*ACCUMULATOR'             
                  PCT_USING_PDP  ='PCT*TIME*USING*SAMPLES'              
                  SMF996_FLAGS   ='SMF996_FLAGS'                        
                  EWLM_LOCAL_PI  ='EWLM*LOCAL*PI'                       
                  EWLM_GLOBAL_PI ='EWLM*GLOBAL*PI'                      
                  SMF996EWLM     ='EWLM*MANAGED?'                       
                  SMF996IOPR     ='I/O*PRIORITY?'                       
                  SMF996INEL     ='ZIP*INELIGIBLE?'                     
   Thanks to Randall Schlueter, First Data, USA.                        
Change 36.071  IAM User SMF INPUT STATEMENT EXCEEDED because unexpected 
VMACIAM        short segment lengths IAMIAINL=148 (MXG expected 204) and
Apr  8, 2018   IAMIASTL=148 (MXG Expected 204) were encounered, and now 
               protected for these IAM 9.2 records.                     
   Thanks to Paul Naddeo, FISERV, USA.                                  
Change 36.070  VMXGDUR rejected INTERVAL=THREEHOUR but the warning      
VMXGDUR        message said that was correct. It was looking for THREEHR
Apr  8, 2018   but will now accept THREEHOUR, EIGHTHOUR, or TWELVEHOUR. 
Change 36.069  Dataset CICSTRAN variables DURATM and DSGTWT were missing
VMXGCICI       values in CICS Statistics SMFSTREQ='USS','REQ',or 'EOD'  
Apr  6, 2018   records as the DURATM only existes in the 'INT' records. 
               But using the DIF(COLLTIME) a pseudo DURATM is created   
               and used to populate/correct DSGTWT and DURATM.          
Change 36.068 -Two new enhancements.                                    
ADOCRMFV      -A new RMFBSAM record with an MXG01 id is now output      
ASMRMFV        for every successfully processed RMF III VSAM data set.  
VMACRMFV       VSAM attributes and statistics are included as well as   
Apr  6, 2018   many ASMRMFV statistics and counters, and the record is  
May  5, 2018   output in new dataset ZRBAS1.                            
              -Between the existing MXG00 record and the new MXG01      
               record nearly all information on an ASMRMFV log is       
               captured. The MXG01 data becomes the ZRBASMDS (?) data   
               set in the result PDB.                                   
              -MXG01 records are only created for RMF III VSAM data sets
               that open and close successfully.  There are no MXG01    
               records generated for:                                   
                Empty VSAM data sets (VSAM considers this an error)     
                VSAM data sets that are not an RRDS type                
                VSAM data with an invalid CISIZE for RMF III data       
                VSAM data with an invalid LRECL for RMF III data        
                Non-VSAM data sets                                      
               The above conditions have been flagged in the ASMRMFV    
               Log for a long time.                                     
              -Two new parameters UPCASE/NOUPCASE control the handling  
               of values assigned in keyword=value usage.               
              -UPCASE (alias UC) is the default and provides the same   
               behavior as in prior ASMRMFV versions which force all    
               PARM and SYSIN (or alternative) input data to upper case 
              -NOUPCASE (alias NOUC) is the default and does not alter  
               any values assigned to a keyword.  And thus lower case   
               values can be assigned to a keyword.                     
              -However, for most (if not all) data filters currently    
               supported by ASMRMFV only upper case values are accepted.
               For example, Sysplex Ids, System Ids, Job Names, Job     
               Classes, and so on are all required by IBM syntax rules  
               to be in upper case.  Lower case values are flagged as   
               errors by ASMRMFV validation routines.                   
              -NOUPCASE is a feature primarily intended for future      
               filtering enhancements where lower case values could     
               be accepted.                                             
              -NOINDEXES and/or NOSPACE parameters might not work       
               correctly in all situations and this has been corrected. 
               Messages were not always suppressed when they should     
               have been.                                               
              -Message RMFV105I produced for ASMRMFV Detail and         
               Summary reports now shows the full 5 character RMF III   
               table id instead of just the first 3 characters.  This   
               change was needed to distinguish MXG00 and MXG01 output  
               record statistics.                                       
              -Minor changes to messages RMFV037I, RMFV041I, RMFV051*   
               (*= S,E,W,I), and RMFV106W.                              
              -Several documentation Sections are updated to support    
               the above changes:                                       
               Section  5 "Input Data Selection Parameters"             
               Section 12 "Messages"                                    
               Section 31 "Summary"                                     
               Section 32 "Bibliography"                                
Change 36.067  z/OS, MXG's default CAPSOUT option causes lower case text
CONFIGxx       to be upper cased, but MXG recommends NOCAPSOUT for ODS, 
Apr  5, 2018   and the SAS default on z/OS is NOCAPSOUT.  I don't know  
               why I changed the SAS default years ago, but "CAPSOUT" is
               removed from all of the example MXG CONFIGxx members, so 
               your site's default value will be used.                  
Change 36.066  Support for "IBM Developer for z Systems IDZ" SMF 122    
EXTY122A       subtype 1 record creates new dataset TYPE122A.  TYPE122A 
IMAC122A       is used because there is a TYPE122 record (that is/was?) 
TYPE122A       previously written by Tivoli Allocation. The Product Name
TYPS122A       The Product Name field contains 'C2AE'x before and after 
VMAC122A       the name, where 'AE'x is the ASCII registered copyright  
VMXGINIT       symbol, but 'C2'x is a Danish A with a ring above!  Both 
Apr  4, 2018   are printed on ASCII SAS, but both are blank on z/OS, and
               on z/OS lower case characters are converted to upper case
               by the $ASCIIn. INFORMAT.                                
   Thanks to Tory Lepak, Aetna, USA.                                    
Change 36.065  AS400 7.3 QAPMDISK new fields below are now documented   
VMACQACS       and are added to QAPMDISK dataset, transparently.        
Apr  3, 2018   MXG created the PCTCLEAN and DSFSMAPBY variables:        
                DSFSMAPSZ ='FREE SPACE*MAP 4K*PAGES*COUNT'              
                DSFSCLEAN ='CLEAN*4K PAGES*FREE SPACE*COUNT'            
                DSFSCLEAN0='LEVEL 0*CLEAN BLOCKS*PAGES 1-7'             
                DSFSCLEAN1='LEVEL 1*CLEAN BLOCKS*PAGES   8'             
                DSFSCLEAN2='LEVEL 2*CLEAN BLOCKS*PAGES  16'             
                DSFSCLEAN3='LEVEL 3*CLEAN BLOCKS*PAGES  32'             
                DSFSCLEAN4='LEVEL 4*CLEAN BLOCKS*PAGES  64'             
                DSFSCLEAN5='LEVEL 5*CLEAN BLOCKS*PAGES 128'             
                DSFSCLEAN6='LEVEL 6*CLEAN BLOCKS*PAGES 156'             
                DSFSDIRTY ='DIRTY*4K PAGES*FREE SPACE*COUNT'            
                DSFSDIRTY0='LEVEL 0*DIRTY BLOCKS*PAGES 1-7'             
                DSFSDIRTY1='LEVEL 1*DIRTY BLOCKS*PAGES   8'             
                DSFSDIRTY2='LEVEL 2*DIRTY BLOCKS*PAGES  16'             
                DSFSDIRTY3='LEVEL 3*DIRTY BLOCKS*PAGES  32'             
                DSFSDIRTY4='LEVEL 4*DIRTY BLOCKS*PAGES  64'             
                DSFSDIRTY5='LEVEL 5*DIRTY BLOCKS*PAGES 128'             
                DSFSDIRTY6='LEVEL 6*DIRTY BLOCKS*PAGES 256'             
                PCTCLEAN='PERCENT*CLEAN*PAGES IN*FREE SPACE'            
====== Changes thru 36.064 are in MXG 36.03 dated Apr  2, 2018========= 
Change 36.064  All updates in the Jan, 2018, SMF Manual are included in 
SMF MANUAL     MXG Version 36.03, except new SMF 122, which is not in   
Mar 30, 2018   that SMF Manual.                                         
Change 36.063  DB2 V9 ONLY, zero obs in DB2STATB and other statistics   
VMACDB2        datasets listed in Change 35.299, which revised deaccum  
Mar 29, 2018   logic and expected one minute statistics intervals, but  
               that IBM Change to force the DB2 Statistics Interval to  
               one minute wasn't introduced until DB2 Version 10!       
   Thanks to Don Blaszka, Wipro Limited, USA.                           
Change 36.062  Further VXBYUSR logic revised to use only 2 decimals for 
VMACVMXA       all _MT1 DIF() functions; these data have only two digit 
Apr  1, 2018   time resolution, but the divide by 4096 produced false   
               digits in 3rd and 4th place that, coupled with these     
               very large 2-complement numbers, cause MXG to falsely    
               detect a break in deaccumulation.   See also 36.052.     
Change 36.061  Invalid SYTNLPS value in SYTCUP records prevented their  
VMACXAM        output; pending Velocity fix, SYTNLPS=(SEGLEN-28)/20; is 
Mar 20, 2018   used to calculate the actual number of segments.         
Change 36.060  Support for BMC Extended Buffer Manager XBM SMF Record.  
EXXBMDS           -The Data Set Statistics Record can have seven OIDs:  
EXXBMCA            OID   Variables   Segment                            
EXXBMCC            113   xbmDSSnn    Dataset Statistics                 
EXXBMCE            113   xbmSDSnn    Snapshot Data Set Statistics       
EXXBMCS            154   xbmDB2nn    DB2 Statistics                     
IMACXBM            158   xbmSUSnn    Snapshot Utilities Statistics      
TYPEXBM            199   xbmVSAnn    VSAM Statistics                    
TYPSXBM            272   xbmEPSnn    Extended Prefetch Statistics       
VMACXBM            242   xbmIMSnn    IMS Statistics                     
VMXGINIT         and all seven segments are output in XBMDSET dataset.  
Mar 21, 2018         DDDDDD   Dataset       Description                 
                     XBMDS    XBMDSET       XBM Data Set Record         
                 (Only the first four OID's have been data-validated).  
                -The Cache Statistics Record can have four OIDs,        
                    1   xbmCSSnn    Configuration Start Section         
                    2   xbmCEEnn    Configuration End/Stop Section      
                    3   xbmCCCnn    Configuration Change Statistics     
                  106   xbmCACnn    Cache Statistics Section            
                 and each is output in a separate dataset:              
                    DDDDDD   Dataset       Description                  
                    XBMCA    XBMCACHE      XBM Cache Record             
                    XBMCS    XBMCSTRT      XBM Configuration Start      
                    XBMCE    XBMCEND       XBM Configuration End        
                    XBMCC    XBMCHG        XBM Configuration Change     
   Thanks to Flavio Lima, MetLife, USA.                                 
Change 36.059 -If you specified USERADD=ID a CHAR OPERAND FOUND IN %EVAL
UTILBLDP       error indicated that a numeric was needed, which was due 
Mar 21, 2018   to the compiler interpreting %STR(/VIEW=ID) as a formula.
               Resolved by using %QUOTE rather than %STR, like the other
               references in UTILBLDP.                                  
              -The SMF AUDIT report was not being produced, now is.     
Change 36.058  Missing %END in PMAUD02 corrected and BEGTIME and ENDTIME
ANALDB2R       paramters enabled for MXGDB2B1 report.  MXG 36.02 only,  
Mar 23, 2018   introduced by Change 36.048.                             
   Thanks to Randy Hewitt, DXC, USA.                                    
Change 36.057  Support for z/OS 2.3 RMF Changes (SHARE Sacramento 2018):
EXTY748S      -Support for APAR OA53411 for more than 65535 devices adds
FORMATS        SMF74SMF bit and populates existing SMF74LSN with a flag 
IMAC74         when multiple logical SMF records were created, but these
VMAC7072       variables are not kept, and don't impact MXG's reading of
VMAC74         the individual physical SMF records; the variables are   
VMXGINIT       available in the EXTY74 exit, if ever of interest.       
Mar 26, 2018  -Support for APAR OA50760 72.3/4, was in Change 35.125.   
              -Support for APAR OA50761 74.10, was in Change 35.273.    
              -Support for APAR OA52694 72.3 TYPE72TR+ in Change 36.050.
              -Support for APAR OA50762 74.9 new bit existing R749FLAG. 
              -Support for APAR OA50693 70.2 CEX6C/CEX6A/CEX6P Crypto   
               updated $MGRMFCX/$MGRMFCY/MGRMFCZ formats.               
              -Support for APAR OA50755 74.1 was in Change 35.193.      
              -Support for APAR OA50755 74.9 was in Change 35.146.      
              -Support for APAR OA53411 adds 74.5 vars to TYPE74CA.     
                 R7451SRR='SYNC I/O*CACHE*READ*REQUESTS'                
                 R7451SRH='SYNC I/O*CACHE*READ*HITS'                    
                 R7451SWR='SYNC I/O*CACHE*READ*REQUESTS'                
                 R7451SWH='SYNC I/O*CACHE*READ*HITSS'                   
              -Support for APAR OA53411 74.8 adds new Synchronous I/O   
               Link Statistics Segment that creates new TYPE748S data   
               set with these variables:                                
                 R748SWDH='SYNC*I/O*LINK WIDTH*LANES'                   
                 R748SCBR='SYNC I/o*CACHE*BYTES*READ'                   
                 R748SCro='SYNC I/o*CACHE*READ*OPERATIONS'              
                 R748SCRT='SYNC I/o*CACHE*READ*TIME'                    
                 R748SCBW='SYNC I/o*CACHE*BYTES*WRITE'                  
                 R748SCWO='SYNC I/o*CACHE*WRITE*OPERATIONS'             
                 R748SNBW='SYNC I/O*CACHE*WRITE*TIME'                   
              -Support for APAR OA51913, z14 physical core addresses    
               greater than 191, was protected in MXG 31.04, which      
               supports the maximum possible value of 255, even though  
               z/OS doesn't even support 191.                           
              -Support for Jan 2018 SMF Manual and APAR OA52003 that    
               added these variables to TYPE74ST Structure dataset:     
                 R744SIAD R744SADN R744SIXC R744SXSC R744SXST R744SXSQ  
                 R744SADO R744SADR R744SQCH R744SXFL R744SWDR R744SWAC  
                 R744SRDR R744SRAC R744SWEC R744SREC R744SWED R744SWES  
                 R744SRED R744SRES                                      
                 R744SIAD R744SADN R744SIXC R744SXSC R744SSXT R744SXSQ  
                 R744SADR R744SQCH R744SXFL                             
                 R744SWDR R744SWAC R744SRDR R744SRAC R744SWEC R744SREC  
                 R744SWED R744SWES R744SRED R744SRES                    
              -Support for Jan 2018 SMF Manual which added to TYPE74DU: 
                 R744RSST R744RIDP R744RCPI R744RCPN R744RSGS R744RSA1  
                 R744RSA2 R744RSA3 R744RSA4 R744RSA5 R744RSA6 R744RSA7  
                 R744RSA8 R744RSID R744RSC  R744RAMC R744RAMS R744RAMS  
                 R744RAMP R744RAMN                                      
Change 36.056  zHyperwrite enables DB2 to perform parallel log writes to
VMAC74         PPRC primary and secondary volumes, but they are the same
VMAC79         4-hex-digit DEVNR, and because they can be concurrently  
Mar 15, 2018   active, RMF Reports now display 5-hex-digit DEVNR, with  
               the first nySbble containing the SubChannel ID, 'sdddd'X,
               where the SubChanel ID is 0,1,2 or 3. There was no change
               to the SMF 74/79 records, as the SubChannel ID is already
               in those records, and the 5-hex-digit display is only in 
               RMF reports/data: they won't exist in other SMF records. 
               MXG variable DEVNR5HEX is created in TYPE74, TYPE74CA,   
               TYPE748 and TYPE796 as DEVNR5HEX=65536*SMF74SCS+DEVNR    
               with FORMAT DEVNR5HEX HEX5. format.                      
Change 36.055  New TYPE8231 dataset was misaligned and the VMXGINIT for 
VMAC82         _WTY8231 thru _WTY8247 was corrected to write to WORK    
VMXGINIT       rather than to PDB.                                      
Mar 13, 2018  -Mar 20: Invalid Subtype 31 with only 4 bytes for 0203 TAG
Mar 20, 2018   encountered, circumvented, and reported to IBM.          
Apr 12, 2018  -Apr 12: MXG's problem was that the SMF82_TRIPL_LENGTH    
               field was presumed to be the length following it, but it 
               was 8 with when 4 bytes remained, so I presumed there was
               truncated data for the TAG 0203 segment.  IBM Support    
               responded with a very detailed decoding of the record    
               with their utility that matched MXG's values, concluding:
               "To sum up, the length of 08 that you are referencing    
                does not mean that 8 bytes will follow. It means the    
                length in the record is composed of the length of the   
                data item (4 bytes) plus the length of the tag and      
                size info (another 4 bytes)."                           
                While TAGs have different lengths, since each TAG's     
                length is fixed, MXG did not need to use that field,    
                so no MXG code change was required, and no data was     
   Thanks to Andreas Menne, Finanz Informatik, GERMANY.                 
   Thanks to David A. Hilliard, IBM Support, GERMANY.                   
Change 36.054  A missing paren caused BLDSMPDB to fail, and %macro      
BLDSMPDB       &PDBPATH was not initialized in PDBAUDIT. BLDSMPDB only  
PDBAUDIT       failed when MTD was used which then caused SAS to set    
Mar 13, 2018   OBS=0 and caused PROC SQLs in PDBAUDIT to then fail.     
               PDBAUDIT is now protected for the 0 OBS case             
   Thanks to Harold Zbiegien, American Greetings, USA.                  
Change 36.053  INTBTIME and INTETIME variables are now all DATETIME25.6 
BUIL3005       formatted, even though only those INPUT with TODSTAMP8   
BUILD005       will have all six decimals populated, SMFSTAMP informat  
SMFINTRV       only has 2 decimals.  INTETIME in SMF 91 with TODSTAMP8  
VMAC30         informat forced the format change, since you can't have  
VMAC91         different formats for the same variable name in datasets 
Mar  8, 2018   created in the same DATA step.                           
   Thanks to Randy Hewitt, DXC, USA.                                    
Change 36.052  Revision to z/VM VXBYUSR logic to correct large values   
VMACVMXA       in many deaccumulated durations when there were multiple 
Mar  7, 2018   logon values in CALTODON for the same user, and/or when  
               a guest has been relocated.  Logic to recalculate DELTATM
               from HFRATE*HFQCNT was causing output of first instances,
               so it was removed.  A heuristic was added to test that   
               the record DELTATM was not more than 2*INTERVAL since    
               that also detects a return of a relocate to delete.      
               See Change 36.062.                                       
   Thanks to Graham Harris, RBS, ENGLAND.                               
Change 36.051  Support for AS/400 Version 7.3 Collection Services.      
VMACQACS      -New GDES fields added to QAPMCONF dataset for keys       
Mar  7, 2018   FL PM TY TZ T1 T2 T3 T4 U1 U2 U3 U4 XS                   
Mar 16, 2018  -New DATETIMECH,UTCTIMECH 26-character datetimes and      
Mar 23, 2018   DSQUEOPS counter added to QAPMDISK record, which now     
Mar 26, 2018   has LRECL=751 (YOU MUST SET IN YOUR JCL/FILENAME).       
               See change 36.065.                                       
====== Changes thru 36.050 are in MXG 36.02 dated Mar  5, 2018========= 
Change 36.050  TYPE72GO variables R723CPA_ACTUAL and R723CPA_SCALING    
VMAC7072       added by APAR OA52694, were trashed because they were    
Mar  2, 2018   input when they shouldn't have been; the test for INPUT  
Mar  6, 2018   should have been GE 276 instead of repeated GE 268.      
               Mar 6: New variable ORG70CPA was added to TYPE70 and     
               TYPE70PR, but the label statement had OGT70CPA causing   
               a harmless UNINIT variable message on the log.           
   Thanks to Al Sherkow, I/S Management Strategies, Ltd.                
Change 36.049  Change 35.200 left off the trailing / or ] on the        
VGETALOC       directory names if you did not supply it and it could    
Mar  2, 2018   result in no allocations and a failure of a following    
               VMXGSET. Now if we dont find the / or \ we supply it.    
   Thanks to Richard Krueger, Sentry, USA.                              
Change 36.048  For PMAUD02 report SORTBY use is restored, but the first 
ANALDB2R       variable in the list must be QWHSSSID, and variables not 
Mar  2, 2018   in the below list will terminate with error messages.    
               The default values are QWHSSSID QWHSSTCK; if that first  
               variable is not DB2 or QWHSSSID, QWHSSSID is inserted.   
               Allowed variables are:                                   
                 DB2        - THE DB2 SUBSYSTEM ID                      
                 PLAN       - THE DB2 PLAN NAME                         
                 AUTHID     - THE AUTHORIZATION ID                      
                 CONNID     - THE CONNECTION ID                         
                 CONNTYPE   - THE CONNECTION TYPE                       
                 CORRID     - THE CORRELATION ID                        
                 QWHSSSID   - THE DB2 SUBSYSTEM ID                      
                 QWHCPLAN   - THE DB2 PLAN NAME                         
                 QWHCAID    - THE AUTHORIZATION ID                      
                 QWHCOPID   - THE ORIGINAL AUTHORIZATION ID             
                 QWHCCN     - THE CONNECTION ID                         
                 QWACATYP   - THE CONNECTION TYPE                       
                 QWHCCV     - THE CORRELATION ID                        
                 QWHSSTCK   - THE TIME OF THE EVENT                     
   Thanks to Scott Swindling, PREMERA, USA.                             
Change 36.047  Support for XCOM Version 12.0 (COMPATIBLE) adds variables
VMACXCOM         XCOMGWDP='GATEWAY*DPATH'                               
Feb 28, 2018     XCOMSSLT='SSL*VERSION'                                 
   Thanks to Alfredo Antonio Gonzalez Ortega, ITNOW, SPAIN              
   Thanks to Sergi Vilaseca Punti, ITNOW, SPAIN                         
   Thanks to Miguel Fco. Monferrer Carvajal, ITNOW, SPAIN               
Change 36.046  Support for NDM Version 5.2 corrects NDMCPU and adds     
VMACNDM        these variables to the NDMCT dataset:                    
Mar  1, 2018     NDMCLASS   ='PROCESS*SESSION*CLASS'                    
Apr  6, 2018     NDMCTFLAG17='FASP17*OVERRIDE*TO FASP=NO'               
                 NDMCTFLAG18='FASP18*OVERRIDE*TO FASP=NO'               
                 NDMCTGPF   ='GENERAL*PURPOSE*FLAG'                     
                 NDMDBLKSZ  ='DESTINATION*BLKSIZE'                      
                 NDMDDSORG  ='DESTINATION*DSORG'                        
                 NDMDLRECL  ='DESTINATION*LRECL'                        
                 NDMDRECFM  ='DESTINATION*RECFM'                        
                 NDMFASPBW  ='FASP*BANDWIDTH*KBITS'                     
                 NDMFASPFT  ='FASP*FILESIZE*THRESHOLD'                  
                 NDMFASPPL  ='FASP*POLICY'                              
                 NDMPNRLS   ='PNODE*C:D*VERSION'                        
                 NDMSBLKSZ  ='SOURCE*BLKSIZE'                           
                 NDMSDSORG  ='SOURCE*DSORG'                             
                 NDMSLRECL  ='SOURCE*LRECL'                             
                 NDMSMFID   ='SMFID*THAT*CREATED'                       
                 NDMSMRLS   ='SNODE*C:D*VERSION'                        
                 NDMSRECFM  ='SOURCE*RECFM'                             
                 NDMSTEPOS  ='STEP*OFFSET*IN*TCQ'                       
                 NDMXDATE   ='PROCESS*STOP*DATE'                        
                 NDMXTIME   ='PROCESS*STOP*TIME'                        
                 NDMZWINR   ='COMPRESSION*WINDOW*SIZE'                  
                -Apr 6: Reported Truncated CERI and CERT to IBM.        
                -Apr 16: IBM APAR PI24126 corrects the truncation,      
                 but makes no mention of the truncation.  That fix      
                 required reassembly of DGMSMF.                         
   Thanks to Heimir Hauksson, Barclays Technology Center, ENGLAND.      
   Thanks to Robert Richards, OPM, USA.                                 
   Thanks to Walter J Freeman, OPM, USA.                                
   Thanks to Otto A. Burgess, OPM, USA.                                 
Change 36.045  Support for enhanced Mobile Work 4HOUR MSU reporting.    
FORMATS       -New parameter, TYPE=, for the type of mobile work, to    
MOBMWRT        be added to your %MOBMWRT invocation in your MOBWRKxx    
MOBWRK72       tailored members, where TYPE=DB2 CICS IMS WAS or MQ to   
MOBWRK73       create the WORK.MWRT_BLD_SUM_&TYPE dataset that is then  
MOBWRKMS       used to create the new MOBILE.MSU_&TYPE dataset with the 
Feb 28, 2018   4 hour rolling average MSU for that &TYPE of workload.   
              -MOBWRKMS provides reporting on the new &TYPE datasets.   
              -Some improvements in SMF70CPA calculation in MOBWRK73,   
               and ORIGCPUTM/CPUCPONLY/CICDSCPUTM are init to missing   
               in MOBWRK72.                                             
              -FORMAT mwrtdt is enhanced to support years beyond 2042.  
   Thanks to Al Sherkow, I/S Management Strategies, Ltd.                
Change 36.044  The value you set in MACRO _IMSVERS mm.n % is now kept   
VMACIMS        in variable IMSVERS in IMS0708 and IMS07 datasets.       
Mar  1, 2018   (The IMS56FA transaction dataset already has IMSVERSN    
               that is created from that IMS log record.)               
   Thanks to Alfredo Gonzalez, La Caixa, SPAIN.                         
Change 36.043  Initial support for NMON Nigel's Monitor for RHEL Release
EXRHELAA       14i with Red Hat Enterprise Linux 6.7.                   
EXRHELBP       The data with 1 second interval is suspect as the times  
EXRHELCI       of the interval are often 2 or 3 seconds apart.          
EXRHELME       The developers page is at ''  
EXRHELNS       The BBBP fields are not currently decoded since the RHEL 
EXRHELCD       text is not consistent with the NMON contents.           
EXRHELDS      -Mar 6: FULLCOMD in RHELUARG expanded to 4096 bytes and   
EXRHELIN       WORK dataset CPUBUSY is deleted; the values of CPU_ALL   
EXRHELJF       variables are output in RHELINTV Interval Dataset.       
EXRHELTO         DDDDDD  MXG       MXG                                  
EXRHELUA         DATASET DATASET   DATASET                              
EXRHELMT         SUFFIX  NAME      LABEL                                
Mar  1, 2018     RHELMT  RHELBBBPMOUNT   RHEL BBBP MOUNT                
Mar 14, 2018     RHELCD  RHELCPUD        RHEL CPU DETAIL                
Mar 28, 2018     RHELDS  RHELDISK        RHEL DISK                      
Apr  6, 2018     RHELIN  RHELINTV        RHEL MONITOR INTERVAL          
                 RHELJF  RHELJFSF        RHEL JFSFILE                   
                 RHELNT  RHELNETW        RHEL NETWORK                   
                 RHELTO  RHELTOP         RHEL TOP PROCESS               
                 RHELUA  RHELUARG        RHEL UARG PROCESS              
              -Apr 6: RHELAAA now output for each concatenated input    
               file; only the first was output previously.              
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
   Thanks to Andreas Windisch, HUK-COBURG, GERMANY.                     
Change 36.042  ANALCAPD ERROR: FOUND "IF" when expecting ... when the   
ANALCAPD       CEC= options was used, due to a missing semicolon.       
Feb 22, 2018                                                            
   Thanks to Norbert T. Wagner, Deutsche-Boerse, GERMANY.               
Change 36.041  The MXGERROR:MISSING TYPE70 message is now MXGWARN:MISS  
VMXG70PR       because it's only an alert to be examined (Change 36.026)
Feb 20, 2018   to see if the SYSTEMs listed are the systems of interest.
               Only variables in dataset ASUMCELP observations for those
               LPARs whose 70s were not read are impacted, and in many  
               cases the message is generated because the SMF data from 
               a sandbox LPAR was not present in that day's SMF input.  
   Thanks to Ed Wieszczek, Zions Bank Corporation, USA.                 
Change 36.040  Support for IMS 56FA Record APAR UI50912. COMPATIBLE as  
VMACIMS        it uses a reserved field for the new TPCEXTOF offset to  
Feb 19, 2018   the TPCE DSECT, but TPCEXTOF is zero so the extension    
               is not populated by THIS APAR, so it is also not input.  
   Thanks to Heimir Hauksson, Barclays, ENGLAND.                        
Change 36.039  Enhancement to dataset TYPE70PR creates new LPARZIPS with
VMAC7072       the number of online ZIIP engines for each LPAR for each 
Feb 19, 2018   interval.                                                
   Thanks to Kurt Gramling, TSYS, USA.                                  
Change 36.038  The MXG "INVALID SMF 119 TYPE 81" message in MXG 36.01   
Feb 19, 2018   but I had misunderstood the DS_DOOFF offset to be the    
               offset into the SMF buffer to the DORU field; IBM L3     
               Support corrected me: it is the offset into the RU that  
               will be moved into the DORU field, if the DORU is larger 
               than 4096 bytes, so that the anomaly's data will be in   
               in the SMF record.  The circumvention is removed and the 
               DORU variable is correctly populated.                    
              -Variable IST119DS_SID was changed from numeric to char   
               with $HEX16. format.                                     
   Thanks to Gary Zaetz, IBM z/OS Communications Server Support, USA.   
   Thanks to David Campbell, SUNTRUST, USA.                             
Change 36.037  Variable QWHSACE was missing from the BY list for dataset
Feb 19, 2018   INPUT STATEMENT EXCEEDED.  This code has been executing  
               and accidentally working since MXG 35.10, last year,     
               before two site's data records with multiple QWHSACEs    
               exposed my coding error.                                 
   Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.    
   Thanks to Kare Martin Torsvik, IBM Services, NORWAY                  
Change 36.036  Support for new Subtype 31 SMF 82 JOB-level crypto stats.
Feb 14, 2018                                                            
               During testing of this update, Error Message UNDECLARED  
               ARRAY YPE8231 (note T is missing) was caused by VMXGINIT 
               typo setting PTY8231=DEFAULT instread of setting WTY8231.
               Just a developers note as for that " YPExxxx" error text 
               shows up in testing from time to time.                   
Change 36.035  If the last engine type in an LPAR was an IFL, the MXG   
VMAC7072       calculation of LPARSHAR/LPARSHAC and LZIPSHAR/LZIPSHAC   
Feb 14, 2018   was incorrect in the TYPE70 dataset.                     
   Thanks to Andrew Petersen, DXC, AUSTRALIA.                           
Change 36.034  Some debugging options added when MXGEXIMSG=YES and a bad
VGETOBS        branch to end modified so that if the dataset you seek   
Feb 14, 2018   does not exist and debugging is on you will get the      
               message that it did not exist.                           
Change 36.033  Analysis of different I/O counts between SMF 42 subtype 6
ANAL4274       and type74 subtype 1.                                    
Feb 13, 2018                                                            
Change 36.032  WebSphere INVALID Subtype 9 messages were cause by the   
VMAC120        absence of ELSE clauses that are now corrected.          
Feb 12, 2018                                                            
   Thanks to Jim Horne, Lowe's, USA.                                    
VMACDB2H       issue, but rather is due to BMC APPTUNE SMF 102 records  
Feb 11, 2018   with Data Sharing Group sections that were incorrecly    
               decoded by MXG logic, now corrected.  The ERROR is real  
               in that observations were NOT output in some datasets.   
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
Change 36.030  Old-style substitution macro _HSMINTV added so you can   
ASUMHSM        easily change the default HOUR interval to you choice.   
Feb  6, 2018   If you want the interval to be QTRHOUR and the final     
               output written to dataset HSM.QTRHOUR, you would use:    
                 %LET MACKEEP=%QUOTE(                                   
                   MACRO _LSUHSM HSM.QTRHOUR % /* SETS OUTPUT DSN */    
                   MACRO _HSMINTV QTRHOUR % /* SETS INTERVAL */         
                 %INCLUDE SOURCLIB(ASUMHSM);                            
   Thanks to Randy Hewitt, DXC, USA.                                    
Change 36.029  Variables SM120RULEXFBOM/DEB/MON/FTRC are one-bit fields 
VMAC120        that MXG incorrectly INPUT as one-byte variables.        
Feb  8, 2018                                                            
   Thanks to Paul Volpi, UHC, USA.                                      
   Thanks to Jack Hyde, UHC, USA.                                       
Change 36.028  Change 35.124 introduced code that stopped PDBAUDIT with 
PDBAUDIT       a memory limitation problem with WPS when more than 20   
Feb  8, 2018   LIBNAMEs were found.  Change 35.201 then accidentally    
               circumvented that error by removing duplicate entries,   
               but the real error was that DICTIONARY.MEMBERS returned  
               all libname.member entries, (THOUSANDS in MXG QA JOB),   
               rather than the LIBNAME entries from DICTIONARY.LIBNAMES.
               The error message is inactive.                           
   Thanks to Earl Kline, Luminex, USA.                                  
Change 36.027  More invalid LENSR=304 and 448 for SMF 42 Subtype 5;     
VMAC42         IF LENSR IN(232,240,320,400,448,480) THEN LENSR=160;     
Feb  8, 2018   The line was also moved up to after the DO because       
               those large values with lots of SR segments caused the   
               MXG test for INVALID SR Length exceeds record length.    
               The correcting APAR number is OA54663, but it did not    
               acknowledge the multiplicity of incorrect values when    
               it "Updated SMF42SRL to contain only length of SMF4205A".
   Thanks to Luis Mendoza, Black Knight, USA.                           
   Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.    
====== Changes thru 36.026 are in MXG 36.01 dated Feb  6, 2018========= 
VMXG70PR       datasets, with some incorrect values in those datasets   
Feb  5, 2018   when those messages are printed, not just SMF70LAC, when 
               either the data from a system is not input, or if your   
               LPARNAME/SYSTEM/SYSNAME/SMF70STN names are inconsistent. 
               Change 35.144 introduced the message and provided a way  
               if your SMF70STN matches LPARNAME, but you may need the  
               below logic to create consistent names.                  
                   %LET INCODE70FOR70PR=%QUOTE(                         
                     LENGTH SMF70STN $8;                                
                     IF      SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';     
                     ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';     
                     ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';     
                     IF      SYSNAME='ZUT1ACP1' THEN SYSNAME='ACP1';    
                     ELSE IF SYSNAME='ZUT1DEV1' THEN SYSNAME='DEV1';    
                     ELSE IF SYSNAME='ZUT1PRD1' THEN SYSNAME='PRD1';    
                     IF      SMF70STN='ZUT1ACP1' THEN SYSTEM='ACP1';    
                     ELSE IF SMF70STN='ZUT1DEV1' THEN SYSTEM='DEV1';    
                     ELSE IF SMF70STN='ZUT1PRD1' THEN SYSTEM='PRD1';    
                     IF      SMF70STN='ZUT1ACP1' THEN SMF70STN='ACP1';  
                     ELSE IF SMF70STN='ZUT1DEV1' THEN SMF70STN='DEV1';  
                     ELSE IF SMF70STN='ZUT1PRD1' THEN SMF70STN='PRD1';  
                     IF      SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';     
                     ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';     
                     ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';     
                     IF      SYSNAME='ZUT1ACP1' THEN SYSNAME='ACP1';    
                     ELSE IF SYSNAME='ZUT1DEV1' THEN SYSNAME='DEV1';    
                     ELSE IF SYSNAME='ZUT1PRD1' THEN SYSNAME='PRD1';    
                   %INCLUDE SOURCLIB(ASUM70PR);                         
   Thanks to Ed Wieszczek, Zions Bank, USA.                             
Change 36.025  Support for zVM64 Level 40061701 and 1702 INCOMPATIBLE.  
VMACVMXA       Changes to MTRSYS 1.04 for SKIP calculation and MTREND   
Feb  6, 2018   1.11 logic required for new instance where the rest of   
               the record contains only nulls.                          
   Thanks to Graham Harris, RBS, ENGLAND.                               
Change 36.024  Support for ThruPutManager Release/Version 18.02 COMPAT, 
VMACTPMX       PTF Level TMT7113, adds new variable JXJBSTXT to dataset 
Feb  1, 2018   TYPETPMX, with label 'JXJBSSYSAFF*TEXT'.                 
               Long labels and variables with blank labels corrected.   
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
Change 36.023  Yet another ID 42 ST 5 INPUT STATEMENT EXCEEDED due to   
VMAC42         yet another invalid LENSR of 232 that should be 160.     
Jan 29, 2018   NOW: IF LENSR IN(232,240,320,400,480) THEN LENSR=160;    
               See Change 35.302 and 35.305 original invalid LENSRs.    
               IBM APAR OA54663 has been opened to fix the reported     
               problem. (Note IBM calls it "reported", apparently       
               until they have accepted and fixed the issue!)           
   Thanks to Bradley A. Foxhall, BNY, USA.                              
Change 36.022  Support for Liberty SMF 120 Subtype 100 (COMPAT) 
VMAC120        added two new fields to dataset TY120100:                
                SM120RULEXPNUM='RULESET*NUMBER OF*PARAMETERS*/          
              -Unknown Subtype logic added to print a hex dump if found.
   Thanks to Paul Volpi, UHC, USA.                                      
   Thanks to Jack Hyde, UHC, USA.                                       
Change 36.021  Allocation utility VMXGALOC is enhanced so that if your  
VMXGALOC       have specified DB2KEEP=0 or CICSKEEP=0 or SPINKEEP=0, the
Jan 25, 2018   directories are not created.  This is primarily for      
               specialized tailoring where you want to send output data 
               to different directories than the normal PDB processing, 
               as SPIN CICSTRAN and DB2 are neither needed or desirable 
               with those arguments (DAILYDSN being a good example).    
Change 36.020  ASCII version of JCLDAYDS that uses the SAS FTP engine to
ASCIIDSN       process TMC and DCOLLECT data.                           
Jan 25, 2018                                                            
Change 36.019  Change to output dataset label to reflect the correct    
TRNDDSNS       source of the data.                                      
Jan 25, 2018                                                            
Change 36.018  Obscure DB2 GTF file ASCII-only conversion utility to    
UDB2GTFA       assemble 256 byte pieces had the COL=OUTCOL that should  
Jan 25, 2018   have been COL=OUTLOC, causing no output records.  Was NOT
               reported, accidentally discovered.  But nasty to find.   
Change 36.017  INVALID SMF 119 SUBTYPE 81 RECORD has IST1219DS offset   
VMAC119        of 2899 and IST1219DS length of 2164 but the record is   
Jan 25, 2018   only 3076 bytes long, causing INPUT STATEMENT EXCEEDED.  
               Test added to print MXGERROR and delete the record while 
               opening a problem with IBM support.                      
   Thanks to David Campbell, Suntrust, USA.                             
Change 36.016  Enhancement to create optional SMFHEADER dataset with    
TYPEID         selected variable from the SMF header when READSMF=YES   
VMXGINIT       is used.  These two macros (default blank) enable:       
Jan 24, 2018     %LET SMFHEADERDATASET1=                                
                 %LET SMFHEADERDATASET2=                                
                    %QUOTE( OUTPUT PDB.SMFHEADER; ) ;                   
   Thanks to Randy Hewitt, DXC, USA.                                    
Change 36.015  Variable CPUID $EBCDIC8 ERROR when TYPEBETA and TYPE70   
VMACBETA       records were processed together - CPUID is a numeric but 
Jan 24, 2018   VMACBETA had an incorrect/old BETA93 reference.          
   Thanks to Lothar Koppe, Provinzial, GERMANY.                         
Change 36.014  ANALHSM Report 3 Title was overlaid if BYVAL was used.   
Jan 22, 2018                                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
Change 36.013  Documentation only.  APAR OA27291 corrects ABEND S0C4 if 
NEWSLTRS       USEZOSV1R9RULE(NO), the default, is used with Netview    
Jan 22, 2018   NvDM at z/OS 1.10 or higher, in DIAGxx member of parmlib.
   Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.           
Change 36.012  The created GMTOFF30 value could be .01 seconds more or  
VMAC30         .01 less than the exact hourly offset when SMF30IST was  
Jan 22, 2018   not the same second as INTBTIME, complicated by the two  
               different resolutions, .01 in SMF30IST/SMFSTAMP8/local,  
               .000001 in the higher resolution INTBTIME/TODSTAMP/GMT,  
               the only source of the GMT delta in SMF 30s. This change 
               impacts variables ACTDLYTM EXECTM INTBTIME INTETIME and  
               SYNCTIME with the PROC COMPARE difference less than .01. 
               And note that if you have not specified SYNC in SMFPRMxx,
               the TYPE30_V/SMFINTRV datasets are useless for any type  
               of interval totals.                                      
Change 36.011 -MXG 35.09-36.  Using %PDBAUDIT(LIBNAMES='Not _ALL_",     
PDBAUDIT       overriding the internal _ALL_ default, the program       
Jan 19, 2018   failed with a syntax error pointing to a Paren.          
              -If LIBNAMES=PDB was used, and //PDB DD is tape, the      
               program fails with PDB.PDBAUDIT NOT FOUND, because the   
               option EXCLUDESEQ=YES is the default to NOT READ tape    
               PDB libraries.  Now, if your PDBAUDIT= is on tape, and   
               EXCLUDESEQ=YES, the program will tell you that you must  
               change that to NO, so the program will report on the     
               contents of the tape Data Library, but there is no output
               of the PDB.PDBAUDIT dataset to that tape, as that could  
               destroy existing datasets on the sequential mode tape.   
               It is NOT recommended that you build your PDB on tape    
               because of performance issues: tapes have no directory   
               so the full tape has to be read to determine its contents
               for PDBAUDIT, and worse for BUILDPDB, where datasets are 
               written AND read-from the //PDB, each reference has to   
               start at the beginning of the tape and read all data     
               to get to that dataset.                                  
              -If you do want your daily PDB on tape, you should write  
               to temp DASD for the //PDB, to eliminate the rereads, and
               then PROC COPY from //PDB to tape after all your reports 
               were created from the temp DASD PDB.  And, since this PDB
               for BUILDPDB is NOT on tape, PDB.PDBAUDIT will be created
               and output to the temp PDB so it is included in the copy.
              -Note that if you do use EXCLUDESEQ=NO with PDB on tape,  
               there are no observation counts in the PDBAUDIT reports. 
   Thanks to Peter Ten Eyck, American National, USA.                    
Change 36.010  TYPE73 dataset variable CHFXRATE should have been divided
VMAC73         SMF73PTI, the corrected elapsed time, and not by DURATM. 
Jan 18, 2018                                                            
   Thanks to Steve Olenik, IBM, USA.                                    
Change 36.009  Message: INVALID TYPE 0 RECORD with LENGTH=70 was deleted
VMAC0          but that length is now valid when SMF0TBUF was added, but
Jan 18, 2018   its length was not added to the test for valid lengths.  
                 The test for each valid TYPE 0 record length is needed 
                 because, many times, sysprogs installing a product that
                 writes SMF records, incorrectly fail to set a record ID
                 and the product writes type 0 records, which were not  
                 valid IPL records, and thus were deleted by MXG, with  
                 the message.  I failed to add 70 to the test.          
              -And, this site had records that were LENGTH=52 that are  
               not IPL records, accidentally written.  Do you recognize 
               what product has values like these in that record?:      
          CHAR  ;... 3....E09ZBLOK. .. 3....LIDPOST BLKLDPSTLOADED   52 
          NUMR  E000B3181F509923622800B3181F394762302323472336145400    
   Thanks to Bruce Sloss, PNC, USA.                                     
Change 36.008  Variable TTAPLDAT in dataset TYP11902 was mis-aligned due
VMAC119        to INPUT that should have been INPUT @OFF11905 TTAPLDAT. 
Jan 15, 2018                                                            
   Thanks to Bob Davidson, LloydsBanking, ENGLAND.                      
Change 36.007  Scott Barry posted the UTILBPV program to examine the BVP
UTILBPV        cylinder value to minimize wasted space in the Cylinder  
Jan 15, 2018   Managed Area using EAV Volumes, using your DCOLLECT data.
               Datasets larger than the BPV value are written to the    
               Cylinder-Managed Space, while dataset smaller than BPV   
               are written to the Track-Managed Space.                  
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
Change 36.006 -CICS/TS 5.3 new CPU variables in Statistics CICM dataset:
VMAC110           MNGCPUT ='TOTAL*CPU*TIME'                             
Jan 15, 2018      MNGTONCP='TOTAL*CPU*TIME*ON CP'                       
                  MNGOFLCP='TOTAL*CPU*TIME*OFFLOAD*ON CP'               
              -Variable MNGWLMCC now tests the correct bit.             
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
Change 36.005 -TYPE115 header variable QWHSDURN in SMF 115 subtype 231  
VMACDB2H       has a value that requires a divide by 4096, while that   
VMAC115        same field in all other SMF 115 subtypes is microseconds.
Jan 18, 2018  -Header variable QWHSTIME and QWHSDURN are added to all   
Feb  2, 2018   datasets that have the 52-byte DB2 QWHS header segment:  
                TYPE115201 TYPE115215, subtypes 1, 201, 215, and 213.   
              -Variable QIS1EXPF is INPUT and kept in TYP115201 dataset.
              -The BY lists for 1155/115A/115L/115N were revised and now
               duplicates are removed (the 1155 and 1156 have MANY dupes
              -Variables QSSTCN64/QSSTCR64, ABOVE THE BAR CONTRACTIONS  
               and SHORT ON STORAGE counts added to MQMLOG dataset.     
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
Change 36.004  Correction for DB2 V11 IFCID 376 INPUT STATEMENT EXCEEDED
VMAC102        STOPOVER ERROR because the code incorrectly expected the 
Jan 14, 2018   V12 truncated offsets that are now unread with DB2 V11.  
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
Change 36.003 -TYPE70TR TRG dataset misalignment was corrected when data
VMAC7072       records were received from IBM, but with these questions:
VMAC89          Split 70 records have a 70 TRG segment in each record,  
Jan 17, 2018    and the second record's TRG data is identical.          
              -TYPE72TR TRG dataset has negative values for R723TSUCP:  
               IBM RMF replies: Negative values can occur in certain    
               cases.  When transaction processor usage is reported to  
               WLM through IWM4RPT or IWM4MNTF services, the consumed   
               service units are accounted to the transaction service or
               report classes, and deducted from the region's service   
               and report classes. If the number of transactions is very
               small and a single transaction reports high processor    
               times, it can occur that processor times become negative.
               R723CETSX is natively in "squared microseconds" but is   
               converted to "squared millisecs" to match R723CETS units.
              -TYPE89 documentation had offset at 64 with length 80, but
               actual offset/length are 36/52, causing the original MXG 
               code to not INPUT the TRG TRO/TCO segments, so datasets  
               TYPE80TI, TYPE89R1, and TYPE89R2 had zero observations.  
              -With these changes, Tenant Resource Group, TRG datasets  
               have been validated with data.                           
Change 36.002 -Support for PowerExchange redesigned as some variables   
VMACPOEX       should not have been output in some datasets.            
Jan  9, 2018   The four CPU times POEXCPUG, CPUC, CPUD, and POEXCPUL:   
Jan 22,2018    POEXLIST keeps only POEXCPUG and POEXCPUL                
                POEXCLIE keeps only POEXCPUG and POEXCPUC; the variables
                         from FILE and DB2 segments are removed as they 
                         were only from the last segment.               
                POEXDB2  keeps only POEXCPUG and POEXCPUD               
                POEXFILE has no CPU times.                              
              -New CPU time variables are added to POEXLIST POEXCLIE:   
                POEXGTOF='CPU OFFLOAD*ELIGIBLE*ON*CP'                   
              -New DB2 variable added to POEXDB2 dataset:               
              -HOWEVER: These CPU values are trashed and we've been     
               waiting for a vendor response for several days.          
Change 36.001  TYPETCP (SMF 118) APISTART datetime was on GMT, the only 
VMACTCP        field with SMFSTAMP informat not on local time zone.     
Jan  9, 2018   Labels with MBYTES changed to BYTES since they all use   
               the MGBYTES format that prints the suffix letter.        
   Thanks to Randy Hewitt, DXC Technology, USA.                         
LASTCHANGE: Version 36.