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

MXG CHANGES 38.04

========================MEMBER=CHANGE38================================ 
 /* COPYRIGHT (C) 1984-2020 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
        MXG VERSION 38.04 is  dated May 25, 2020, thru Change 38.081.   
        MXG VERSION 38.03 was dated May  7, 2020, thru Change 38.071.   
        MXG VERSION 38.02 was dated Mar 23, 2020, thru Change 38.048.   
        MXG VERSION 38.01 was dated Feb 17, 2020, thru Change 38.027.   
                                                                        
Annual  MXG VERSION 37.37 was dated Jan  6, 2020, thru Change 37.272.   
        The Final MXG Newsletter SIXTY-NINE was dated Jan  3, 2018.     
        New TECHNOTES previously in NEWSLTRS are now in CHANGESS.       
                                                                        
Instructions for ftp download can be requested by using this form:      
  http://www.mxg.com/Software_Download_Request                          
Your download instructions will be sent via return email.               
                                                                        
Contents of member CHANGES:                                             
                                                                        
I.    Current MXG Software Version 38.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 38.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 http://www.mxg.com in the "Newsletters" frame, although there are  
  no new NEWSLTRS updates; they are now found in CHANGESS as TECHNOTEs. 
                                                                        
  Member CHANGES contains the changes made in the current MXG version.  
  Member CHANGESS contains all changes that have ever been made to MXG. 
  All MXG changes are also online at http://www.mxg.com, in "Changes".  
                                                                        
========================================================================
                                                                        
                                                                        
I.  MXG VERSION 38.04 DATED MAY 25, 2020, THRU CHANGE 38.081.           
                                                                        
==MAJOR CHANGES ADDED IN MXG 38.04, DATED MAY 25, 2020 THRU 38.081.     
                                                                        
ABEND CORRECTED:                                                        
  BLDSMPDB 38.081  MXG 38.03 only.  BLDSMPDB WEEKLY JOB ABENDS, typo.   
                      Line 667 has     1   %END;  remove the "1".       
                   Only on z/OS and only if WEEK is a GDG.              
ERRORS CORRECTED:                                                       
  TYPE30_6 38.072  Revised deaccumulate for accumulated subtype 6.      
  TYPEDB2  38.075  Support for APAR PH14037 DB2ACCTP QPACPKID truncated.
                     No MXG Change, IBM APAR corrected wrong offset.    
  ANAL119  38.073  Cleanup and removal of a typo.                       
NEW SUPPORT:                                                            
  FORMATS  38.082  Support for z15 T02 values in $MGRMIPS format.       
  TYPE42   38.079  Support for APAR OA59541 for Type 42 Subtype 27.     
  TYPE102  38.077  SMF102 IFCID 143/144 increase length QW014xUR.       
                                                                        
==MAJOR CHANGES ADDED IN MXG 38.03, DATED MAY 16, 2020 THRU 38.071.     
                                                                        
EXPOSURE CORRECTED:                                                     
  AUTOINST 38.054  ASCII Unique INSTREAM create for Concurrent Sessions.
                  -ALL ASCII SITES SHOULD PUT %AUTOINST IN IMACINIT.    
ERRORS CORRECTED                                                        
  TYPE123A 38.061  Datetime values were 2080 instead of 2020, MXG error.
  TYPECMFV 38.063  CMF VSAM INVALID DATA messages, wrong informat.      
  TYPECIMS 38.058  CIMS/IMF CIMSDBD/DB2/MQ Zero Obs 37.37-38.02         
  VMXGOPTR 38.056  ANALHSM caused Error "SAS Option Name OPTIONS 1".    
  TYPE70   38.055  PCTMVSBY incorrect after 37.123. (NOT PCTCPUBY!!!).  
  ASMRMFV  38.064  Support for APAR OA58759, caused Condition Code 4.   
  TYPEXCOM 38.069  XCOM input did not skip the 461 bytes added in 12.0. 
New Support                                                             
  TYPE119  38.068  Support for Comm Server SMF 119 Subtype 11 ZERT data.
  TYPE110  38.060  SET MONITOR FREQ hourly CICSTRAN for long runners.   
  UTILROLL 38.065  UTILROLL example to combine PDBs created every 4hr.  
  TYPEDB2  38.062  Support DB2 APAR PI92652,PI82191 and DPAGE support.  
  TYPESVIE 38.057  Support for SYSVIEW Subtype 2 record one min detail. 
  TYPEXAM  38.059  zVPS XAMCUV LCPUID=96 Totals records now deleted.    
  VMACSMF  38.051  SAS FTP Access Method &MXGABND=1 set to print errors.
  TYPE42   38.067  Yet another TYPE42 invalid LENSR in subtype 5 42's.  
                                                                        
==MAJOR CHANGES ADDED IN MXG 38.02, DATED MAR 23, 2020 THRU 38.048.     
                                                                        
ERRORS CORRECTED                                                        
  VMACSMF  38.033  SMF Signature Type 2 St 1/2 MANY BACK2BACK LOG msgs  
  TYPE112  38.040  OMEGAMON TEMS St 38 INVALID ARGUMENT LENGTH CHANGED. 
  TYPE73   38.038  Variable SHIFT was not populated.                    
New Product Support                                                     
  TYPEVMXA 38.047  z/VM MONWRITE 6.4.19.1 z15 INCOMPATIBLE.             
                   Many Log Messages, PRCMFC/PRCMFM empty, rest okay.   
  TYPE70   38.031  Support for APAR OA56683 SMFBOOST System Recovery    
  TYPE62   38.041  Support for APAR OA57105, adds JOBID SYSPLEX.        
  TYPE64   38.041  Support for APAR OA57105, adds JOBID SYSPLEX.        
  TYPETPMX 38.039  Support for new INREI and JCLJJ in TYPETPMX.         
Enhancements                                                            
  TYPE116  38.037  MQMACCTQ/MQMACCT/MQCFSTAT/MQMQUEUE/ revisions.       
  TYPE113  38.035  TYPE113 Counters EXTND247/252/264/265 now labeled.   
  TYPEVMXA 38.019  z/VM VXAPLSLM variable SHARERAM zero if not RHEL8.   
  TYPE89   38.034  APAR OA59002 corrects TYPE89 var SMF89UZT values.    
                                                                        
==MAJOR CHANGES ADDED IN MXG 38.01, DATED Feb 17, 2020 THRU 38.027.     
                                                                        
ERRORS CORRECTED                                                        
  CONFIMXG 38.004  MXG 37.37 only, 1024 should be OPEN_ED=1047.         
  TYPE80A  38.017  INPUT EXCEEDED due to a HOME segment with no data.   
  ANALID   38.010  ERROR "OPTORG4" if you changed SMFAUDIT to NO.       
  UTILBLDP 38.008  Error after Change 37.149 if first USERADD is IDMS.  
New Product Support                                                     
  FORMATS  38.020  Support for SMF73CPT 33/34 connection types.         
  TYPE102  38.019  Support for DB2 APAR PH18739 var QW0389IT in T102S389
  TYPEIMS  38.014  Support for APAR PH14569/PH21001 IMS 22 log record.  
  TYPEBETA 38.013  Support for BETA (93) and BETA97 Version 7.1.0       
  TYPEBE97 38.013  Support for BETA (93) and BETA97 Version 7.1.0       
  TYPE42   38.011  Support for APAR OA57718, zHyperLink TYPE42DS stats. 
  TYPEIAM  38.006  Support for IAM 9.3 Spin 3 INCOMPATIBLE inserts.     
  FORMATS  38.003A R744HOPM $MG074HO new '50x:CL5 10GBIT/S CEE ROCE'.   
  TYPEIDMS 38.003  IDMSTAS UOW/NETNAME added, TASUFLD1-3 corrected.     
  TYPETMS5 38.002  Variables BYTEPRC and BESKEY added to TMS/DSNBRECD.  
  BUILDIMS 38.001  All selections now work, new INPUTCLNR variable.     
New Analysis/Reporting                                                  
  ANAL95TH 38.018  PROC TABULATE 95th pct response stats CICSTRAN/JOBS. 
  ANALATNC 38.005  Report Code for Latent Demand analysis, examples of  
                   reports: https://www.mxg.com/downloads/analatnc      
  DOCVLONG 38.012  Creates a DOCVLONG with all DOCVER data on one line. 
  ANALSIIS 38.009  Analysis of Store Into Instruction Stream enhanced.  
                                                                        
    Please read CHANGESS for the complete list of major enhancements.   
                                                                        
  See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
  current MXG Technical Notes.                                          
                                                                        
                                                                        
  All of these enhancements are described in the Change Log, below.     
                                                                        
II.   SAS Version requirement information:                              
                                                                        
   SAS Versions                                                         
     The current version nomenclature is SAS 9.4 TS1M6 (9.4M6), "M6",   
     or "SAS 9.4 (9.04.01M6P110718)" if the OPTION VERSIONLONG is       
     enabled.                                                           
                                                                        
     Only on z/OS, SAS 9.4 "M5" requires MXG 35.36+ because it adds the 
     NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect 
     described in SAS Note 61672.  But SAS apparently does not plan for 
     a defect correction since the MXG Circumvention solves for MXG and 
     the text of 61672 simply describes the circumvention needed because
     MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect. 
     See Change 35.309 for more details on using NOERRORSTOP for your   
     own PROC SQLs.                                                     
                                                                        
     SAS V9.4 M6 is RECOMMENDED, but MXG executes without error         
     using SAS Version 9.4 M0-M2 or M4-M6 or SAS Version 9.3 M0-M2.     
                                                                        
     SAS V9.4 M5 is REQUIRED with z/OS 2.3 with Eight-Byte USERIDs      
                for Interactive TSO (DMS) SAS Sessions. SAS Note 61339. 
                                                                        
     SAS V9.4 M3 is NOT RECOMMENDED.  See Change 36.128 SAS Note 61906  
                that reports 40% Increase in CPU time with M3.          
                                                                        
     SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.      
                                                                        
     SAS V9.3   SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.  
                But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
                see CHANGE 29.169, IS REQUIRED:                         
                  The %MACRO compiler error is in processing %LET       
                  statements. While only two MXG members failed         
                  repeatedly in MXG QA tests on z/OS, there were random 
                  %LET errors in ASCII QA tests, so ANY use of %LET     
                  statement on ANY platform are vulnerable to this      
                  error, as the %MACRO compiler is SAS portable code,   
                  used on all platforms.  So this is NOT just an MXG    
                  error, but impacts ALL SAS programs.                  
                SAS9.3 is LEVEL A support from SAS.                     
     SAS V9.2   Was recommended, prior to 9.3, and was error-free with  
                MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to 
                use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2      
                Decompression Infile Exit.  but SAS V9.2 does execute on
                that platform.                                          
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
                Support level C by SAS Institute, Sep 30, 2013.         
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
     SAS V8.2   SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS! 
                with SAS 8.2.                                           
                SAS 8.2 is Level C Support from SAS as of Dec 31, 2011. 
                                                                        
      JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used  
                                                                        
      ***************************************************************   
      As documented in Change 27.356, for SAS V9.2 or later):           
      The standard SAS JCL Procedure can be used for MXG with SAS V9.2+ 
           // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                  
           //MXGNAMES DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR        
      But CONFIMXG is required for sites with NLS issues, and you must  
      use JCLCONFI to create/update the MXG.FORMATS catalog if you use  
      CONFIG='MXG.SOURCLIB(CONFIMXG)'.                                  
      For no NLS, you can  use the MXGSAS94 JCL Procedure example.      
      ***************************************************************   
                                                                        
      MXG 26.03 thru MXG 36.11 will execute under the previously listed 
      SAS Versions on all supported platforms                           
                                                                        
      Unrelated to the above SAS Note/Hot Fix, ODS users will want to   
      use MXG 29.06+, because SAS V9.3 did expose incompatibilities in  
      MXG code for ODS reporting, that were fixed in MXG Version 29.06. 
      See Changes 29.159 and 29.169.                                    
                                                                        
                                                                        
      And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,  
      the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe). 
        Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors  
        can occur even though //XXXXXXXX DD is a valid SAS Data Library.
        This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does   
        NOT occur with SAS V9.2, nor with z/OS 1.9.  It can be          
        circumvented by adding a LIBNAME statement that specifies the   
        ENGINE name. See the Technical Note in Newsletters for SN-35332.
        Note that SAS V9.1.3 is now at "Level B" Support from SAS.      
                                                                        
      Old MXG code may continue to execute with SAS V8.2, but V8 is now 
      "Level C" support from SAS Institute, and there are known errors  
      in V8.2 that are only fixed in SAS V9.  I no longer QA with V8.2; 
      While many MXG programs (accidentally) will still execute under   
      V8.2, I cannot guarantee that all of MXG executes error free.     
      PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!           
         If you are absolutely stuck on V8, you need to copy MXG member 
         V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.           
                                                                        
      MXG Software has not executed under SAS V6 in many years.         
                                                                        
      The "PDB" libraries (i.e., SAS data libraries) must be created by 
      SAS V8 or later, but any of those data libraries can be read or   
      updated by the SAS Versions that MXG Supports, above.             
                                                                        
                                                                        
      For SAS Version V9.3:                                             
        SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note 
        SN43828 is REQUIRED.  See text of Change 29.159.                
        With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions    
        26.03 or later execute under SAS V9.3 on all platforms.         
                                                                        
        SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and  
        SAS V9.4 are interchangeable and can be read/written by any of  
        those versions, provided they are on the same platform.         
          BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the 
          same "platform" and attempting to read/use the FORMAT catalog 
          created on one of those "platforms" on the other "platform"   
          will error out to remind you of that difference!              
        SAS V9.4 did change some V9.3 ODS processing defaults and syntax
        that might cause errors with MXG 29.05 or earlier; MXG 29.06,   
        Change 29.160 documents the major revisions made in MXG to fully
        support ODS, and MXG 29.06 is STRONGLY recommended for ODS with 
        SAS V9.3 or SAS V9.4.                                           
                                                                        
      For (Archaic) SAS Version V9.2 (TS1M0):                           
                                                                        
        Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.  
                                                                        
        On z/OS, SAS changed the DSNAMES for some of the SAS libraries, 
        so you do need to use the new MXGSAS92 JCL Procedure for MXG,   
        but it still uses the CONFIGV9 configuration file.              
                                                                        
        ****************************************************************
        However, NEW, and documented in Change 27.356, with SAS V9.2+:  
          The standard SAS JCL Procedure can be used for MXG:           
             // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                
             //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR   
          instead of using the MXGSAS92 JCL Procedure example.          
        ****************************************************************
                                                                        
        SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3, 
        and V9.4. "PDBs" can be read/written interchangeably between    
        these SAS versions.                                             
                                                                        
        MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS   
        and with NO ERRORS reported.                                    
          Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a  
          new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
          code). That warning is harmless (to MXG code) and all MXG     
          created SAS datasets were correct, even with that warning.    
          The ONLY exposure was ONLY on z/OS, and ONLY if condition code
          tests are used in your MXG jobstreams.                        
                                                                        
        SAS Version 9.2 requires z/OS 1.7 or later, both officially as  
        documented by SAS Institute, and actually as V9.2 fails with 0C4
        under z/OS 1.4.                                                 
                                                                        
      For SAS V9.1.3 on z/OS with Service Pack 4:                       
                                                                        
        On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.                     
                                                                        
        CONFIGV9 now specifies V9SEQ instead of V6SEQ.  As V6SEQ does   
        not support long length character variables, it can't be used.  
                                                                        
       SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.  
                                                                        
       For (back-level!) SAS V9.1 or V9.1.2 on z/OS:                    
        SN-013514 is REQUIRED to be able to read datasets that were     
          created by V6SEQ (tape) engine.                               
        SN-012437 is REQUIRED to prevent creation of corrupt/unreadable 
          datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.            
        Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT 
          SAFE without those two hot fixes, and if you do NOT have those
          two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.    
                                                                        
        With MXG 23.02 or later, V9SEQ is the default sequential engine 
        specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
        you MUST install the two hot fixes listed above.                
                                                                        
       For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
         as an absolute minimum level when that SAS Version was last    
         supported by MXG Software.  PLEASE INSTALL SAS V9.x ASAP.      
                                                                        
       Sequential Engine Status:                                        
          V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.   
          V8SEQ was always safe under SAS V8.2, but it wasted CPU time  
            by always compressing when writing in tape format.          
          V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ    
                 should no longer be used, as it does not support long  
                 length variables.                                      
                                                                        
      GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:              
                                                                        
      MXG QA tests are executed with V9.4, on z/OS, on Windows TEN and  
      Linux on 64-bit hardware, but MXG users execute MXG on MANY       
      (ALL??) SAS platforms, including AIX, Linux, and other 'nix'      
      variants, on many different hardware platforms, and since they all
      work we don't need to list them. If SAS executes so does MXG.     
                                                                        
      Prior QA tests have been run with all SAS releases available at   
      that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880, 
      and on HP-UX v11.11 model rp5470, confirming full compatibility.  
                                                                        
      MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS  
      platform without errors! Each new MXG version is also tested with 
      the SAS ITSV/ITRM product by the ITRM developers.                 
                                                                        
                                                                        
III.  WPS Version requirement information:                              
                                                                        
      WPS Version 4.1 USER 4037 ABEND, See Change 37.116.               
      WPS Version 4.0 reportedly fixed version 3 problems.              
      WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.  
         and other errors with 3.00 or 3.01 have been corrected in the  
         current WPS version.                                           
      WPS Version 3.01.1 maintenance level 731 required for PDB to tape 
      WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.     
      WPS Version 3.01  is required for MOBILWRK, PICTURE fails in 2.5. 
      WPS Version 3.01  executed MXG 32.03 BUILDPDB with no errors.     
      WPS Version 3.0   requires MXG 31.09 (see Change 31.251).         
      WPS Version 2.4   required MXG 27.09 (see Change 27.239).         
      WPS Version 2.3.5 required MXG 27.05.                             
                                                                        
      See NEWSLETTERS for WPS Support Statement.                        
                                                                        
      WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID" 
      when the LIBNAME PDB does not exist; there would also have been a 
      prior log message  NOTE: Library PDB does not exist   as the clue.
                                                                        
                                                                        
IV.   MXG Version Required for Hardware, Operating System Release, etc. 
                                                                        
   MXG is usually NOT sensitive to z/OS Hardware changes, but:          
                                                                        
     The z15 and z15 T02 processors INCOMPATIBLY changed the SMF 113    
     records by inserting 32 new EXTEND and 4 CRYPTO counters, causing  
     ARRAY SIZE EXCEEDED with BUILDPDB which processes the SMF 113s.    
     Support for counter changes for both models was in MXG 37.08.      
        If you use MIPS in reports, the format $MGRMIPS provides the    
        MIPS/MSU value for each processor; the z15 values were updated  
        in MXG 37.08, and the z15 TO2 values were updated in MXG 38.04. 
        These MXG programs use $MGRMIPS: ASUMMIPS GRAFCEC GRAFWLM       
        GRAFWRKX and TYPERMFV (RMF III).                                
                                                                        
     The z/14 also inserted SMF 113 fields, supported in MXG 36.07.     
     The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.        
     The z/EC12 with 85+ engines required MXG 30.07.                    
     Support for 255 engines was added in MXG 31.04.                    
                                                                        
     MXG 38.02 supports the new z/OS 2.4 SMF manual fields, COMPATIBLY. 
                                                                        
     AND z/VM on the z15 requires MXG 38.02, PRCMFC/MFM COUNTERS caused 
     HARDWARE COUNTER messages, PRCMFC/PRCMFM no obs.  Change 38.048.   
                                                                        
   The z13 processor INCOMPATIBLY CHANGED, the new SMT-MODE RMF 70, and 
   MXG 34.03 was REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF 
   (which are written if you have zIIP engines AND have enabled the new 
   PROCVIEW CORE option for Multi-Threading, even if only one thread is 
   enabled).                                                            
                                                                        
   The new zEDC compression hardware requires MXG 33.07 to support the  
   new metrics.                                                         
                                                                        
   For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.        
                                                                        
                                                                        
    Availability dates for the IBM products and MXG version required for
    error-free processing of that product's data records:               
                                                                        
                                       Product's                        
                                       Availability     MXG Version     
      Product Name                     Date              Required       
                                                                        
      MVS/ESA 4.1                      Oct 26, 1990         8.8         
      MVS/ESA 4.2                      Mar 29, 1991         9.9         
      MVS/ESA 4.2.2                    Aug 15, 1991         9.9         
      MVS/ESA 4.3                      Mar 23, 1993        10.10        
      MVS/ESA 5.1.0 - compatibility    Jun 24, 1994        12.02        
      MVS/ESA 5.1.0 - Goal Mode        May  3, 1995        13.01        
      MVS/ESA 5.2.0                    Jun 15, 1995        13.05        
      MVS/ESA 5.2.2                    Oct 19, 1995        13.09        
      OS/390  1.1.0                    Feb 22, 1996        14.01        
      OS/390  1.2.0                    Sep 30, 1996        14.05        
      OS/390  1.3.0 Compatibility Mode Mar 28, 1997        14.14        
      OS/390  1.3.0 WLM Goal Mode      Mar 28, 1997        15.02        
      OS/390  2.4.0                    Sep 28, 1997        15.06        
      OS/390  2.5.0                    Feb 24, 1998        15.06        
      OS/390  2.6.0                    Sep 24, 1998        16.04        
      OS/390  2.7.0                    Mar 26, 1999        16.09        
      OS/390  2.7.0 APAR OW41318       Mar 31, 2000        18.03        
      OS/390  2.8.0                    Aug 24, 1999        16.09        
      OS/390  2.8.0 FICON/SHARK        Aug 24, 1999        17.08        
      OS/390  2.8.0 APAR OW41317       Mar 31, 2000        18.03        
      OS/390  2.9.0                    Mar 31, 2000        18.03        
      OS/390 2.10.0                    Sep 15, 2000        18.06        
      OS/390  PAV                      Oct 24, 2000        18.09        
      z/OS 1.1                         Mar 30, 2001        18.11        
      z/OS 1.1 on 2064s                Mar 30, 2001        19.01        
      z/OS 1.1 with correct MSU        Mar 30, 2001        19.02        
      z/OS 1.2                         Oct 31, 2001        19.04        
      z/OS 1.1,1.2 APARs to 78         Oct 31, 2001        19.05        
      z/OS 1.2+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.3+ APAR OW52227           Apr 26, 2002        20.02        
      z/OS 1.2 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.3 JESNR Z2 MODE           Apr 26, 2002        20.03        
      z/OS 1.4 Tolerate                Sep 27, 2002        20.03        
      z/OS 1.4 Support                 Sep 27, 2002        20.06        
      z/OS 1.4 Over 16 CPUs/LPARs      May 29, 2003        21.02        
      z/OS 1.4 DFSMS/rmm, RACF         Aug 29, 2003        21.04        
      z/OS 1.5                         Mar 31, 2004        21.21        
      z/OS IRD ASUM70PR/ASUMCEC        Sep 22, 2003       *24.10        
      z/OS IRD TYPE70PR                Mar 11, 2004       *24.10        
      z/OS IRD TYPE70,RMFINTRV         Mar 22, 2002       *24.10        
      z/OS 1.6 - No IFAs               Sep 30, 2004       *22.09        
      z/OS 1.6 - With IFAs             Sep 30, 2004       *22.11        
      z/OS 1.7 (COMPATIBLE CHANGES)    Sep 30, 2005       *24.10        
      z/OS 1.7 (SPLIT70 CORRECTION)    Sep 30, 2005       *24.10        
      z/OS IFA data in RMF 79s         Sep 30, 2005        23.10        
      z/OS 1.8 - ASMTAPEE assembly     Sep 30, 2005       *25.03        
      z/OS 1.8 - SMF 119 INCOMPAT      Sep 30, 2005       *25.06        
      z/OS More than 32 LPARs          Jan 30, 2006       *24.24        
      z/OS SPLIT RMF 70 records        Jan 30, 2006       *24.24        
      z/OS Dupe SYSTEMs in a SYSPLEX   Jan 30, 2006       *24.02        
      z/OS IRD errors corrected        May 15, 2006        24.03        
      z/OS ASUMCEC errors corrected    May 15, 2006       *24.24        
      z/OS ASUM70LP errors corrected   Jun 13, 2006       *24.24        
      z/OS zIIP Processor Support      Jun 22, 2006       *24.24        
      z/OS Dedicated zIIP Support      Mar  8, 2008       *26.01        
      z/OS Dedicated zAAP Support      Mar  8, 2008        26.01        
      z/OS 1.8 (COMPATIBLE CHANGES)    Sep 20, 2006       *24.24        
      z/OS 1.9 (INCOMPAT, 54 CPs)      Sep 27, 2007        25.10        
      z/OS 1.9 MXGTMNT at ML-39 reASM  Sep 27, 2007        25.10        
      z/OS new z10 variables           Mar  5, 2008        26.01        
      z/OS 1.8 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.9 With HiperDispatch      Sep 15, 2008       *26.10        
      z/OS 1.10 (INCOMPAT, MXG code)   Sep 15, 2008        26.07        
      z/OS 1.10 With HiperDispatch     Sep 15, 2008       *26.10        
      z/OS 1.10 RMF III, SMF 119       Jul 20, 2009        27.05        
      z/OS 1.11                        Sep  2, 2009        27.08        
      z/OS 1.11 New 30 variables       Apr 14, 2010       *28.02        
      z/OS 1.12                        Aug 17, 2010       *28.05        
      z/OS 1.12 SMF 85 Subtype 79      Aug 17, 2010       *29.03        
      z/OS 1.12 VMGUEST option         Aug 17, 2010       *29.06        
      z/OS 1.13                        Sep 30, 2011        29.03        
      z/OS 1.13 - MXGTMNT only         Dec 15, 2011        29.08        
      z/OS 1.13 SMF 119 ST 6 INCOMPAT  Feb  7, 2012        30.01        
      z/OS 2.1  - Most Records support Jul 23, 2013        30.05        
      z/OS 2.1  - ID=0 ERROR MESSAGE   Jul 23, 2013        31.07        
      z/OS 2.1  - ID=85 INCOMPAT       Jul 23, 2013        32.03        
      z/OS 2.1  - ID=70 SMF70CPA       Jul 23, 2013        32.03        
      z/OS 2.1  - INPUT STATEMENT EXCEEDED ERROR SMF 74    33.10        
      z/OS 2.2  COMPATIBLE CH 33.189   Aug 19, 2015        33.08        
      z/OS 2.2 MXGTMNT ABEND S0E0-28   Sep 15, 2015        33.09        
               REQUIRES ASMTAPE ML-55  Sep 15, 2015        33.09        
      z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr  5, 2016        34.02        
      z/OS 2.2 SPLIT 73, ABEND 33.068  Apr  5, 2016        34.02        
      z/OS 2.2 JES2 8-char JOBCLASS    Oct  7, 2016        34.07        
      z/OS 2.2 NEW SMF 124 IOS Spvr    Oct  7, 2016        34.07        
      z/OS 2.3 Many new variables      Sep 24, 2017 35.166 35.09*       
      z/OS 2.3 RMF III Support         Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 2 st 2 STOPOVER    Sep 24, 2017 35.190 35.09*       
      z/OS 2.3 type 90 st 38 STOPOVER  Sep 24, 2017 35.199 35.09*       
                                                                        
      z/OS 2.4 Compatible from SMF Manual Sep 2019 37.166  37.07.       
                                                                        
      z990 CPUs - CPUTYPE '2084'x      Aug 25, 2003        21.04        
      z890 CPUs - CPUTYPE '2086'x      Jun 24, 2004        22.07        
      z9   CPUs - CPUTYPE '2094'x      Jul 20, 2005       *24.24        
      z9EC CPUs - CPUTYPE '2094'x:                                      
             with 64-bit z/OS - no change required        *24.24        
             with 32-bit z/OS only:    Aug 26, 2006        24.06        
      z9BC CPUs - CPUTYPE '2096'x:                                      
             with 64-bit z/OS - no change required         24.01        
             with 32-bit z/OS only:    Jul 27, 2006       *24.24        
      z10  CPUs - CPUTYPE '2097'x      Dec  7, 2008        25.11        
      z10  HiperDispatch/Parked Time   Mar  3, 2008       *26.10        
      z196 (INCOMPAT IF GT 64 ENG)     Aug 17, 2010        28.05        
      zEC12                            Nov 14, 2012        30.07        
      z13   non-SMT Mode               May 27, 2014        32.05        
      z13   SMT Mode Change 33.217     Sep 15, 2015       *33.09        
      z13   SMT Mode NRZIPCPU 34.106   May 10, 2016        34.03        
      z13   SMT MT=2 CPUZIPTM TYPE70   Mar 21, 2016        35.03        
      z14   SMF 113 INCOMPAT, ABEND    Oct  2, 2017        35.11        
      z14   113 LPARBUSY missing value Aug  8, 2018        36.07        
      z14 ZR1 New SMF70MAXPU variable  May  8, 2018        36.04        
      z15 New SMF 113 fields INCOMPAT  Nov 18, 2020        37.08        
      z15 z/VM MFC counters, INCOMPAT  Mar 23, 2020        38.02        
      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        
      CICS-TS/5.5 GA (COMPAT)          Jan 29, 2018        37.01        
      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        
      z/VM    6.40061802 ABEND         Jan 17, 2019        37.02        
      z/VM    7.1        ABEND         Feb 14, 2019        37.02        
      IMS log 4.1                      Jul  4, 1994        12.02        
      IMS log 5.1                      Jun  9, 1996        14.05        
      IMS log 6.1                      ???  ?, 199?        20.03        
      IMS log 7.1                      ???  ?, 200?        20.03        
      IMS log 8.1                      May 21, 2003        21.02        
      IMS log 9.1                      Mar 96, 2004       *26.01        
      IMS log 10.1                     Mar 06, 2007       *26.01        
      IMS log 11.1                     Apr  1, 2010       *28.02        
      IMS log 12.1                     Jan 23, 2012       *29.29        
      IMS log 13.1 (NOT 56FA)          May 25, 2013        31.03        
      IMS log 13.1 (56FA RECORD)       May 27, 2014        32.05        
      IMS log 14.1 COMPATIBLE          Dec 19, 2015        33.07        
      IMS log 15.1 NO CHANGES          Mar  1, 2018        35.07        
      AS400 3.7.0                      Nov  1, 1996        15.01        
      AS400 4.1.0                      Dec 30, 1996        15.08        
      AS400 4.2.0                      Apr 27, 1998        16.02        
      AS400 4.4.0                      Sep 27, 1999        17.07        
      AS400 4.5.0                      Jul 27, 2000        18.07        
      AS400 5.2.0 - Most records       Jul 23, 2003        21.03        
      AS400 5.2.0 - QAPMMIOP           Jul 23, 2003        22.04        
      AS400 5.3.0                      Jan 22, 2005        22.22        
      AS400 5.4.0                      Aug 26, 2006        24.06        
      AS400 6.1.0                      Jun 29, 2008        26.05        
                                                                        
    Note: Asterisk by the version number means the Version number       
          was changed (to the MXG version required), after an earlier   
          MXG version was listed as supporting this product release,    
          usually because an APAR modified the product's data records.  
          Or a coding error in MXG could be the reason for the change!  
                                                                        
    Availability dates for non-IBM products and MXG version required:   
                                                                        
                                                        MXG Version     
      Product Name                                       Required       
                                                                        
      Demand Technology                                                 
       NTSMF Version 1 Beta                                14.11        
       NTSMF Version 2.0                                   15.05        
       NTSMF Version 2.1                                   15.06        
       NTSMF Version 2.2                                   16.04        
       NTSMF Version 2.3                                   17.10        
       NTSMF 2.4.4                     Aug  9, 2002        20.04        
       NTSMF 2.4.5   INCOMPAT          Apr  1, 2003        21.02        
       NTSMF 2.4.7                     Sep 30, 2004        22.08        
       NTSMF 3.1.4                     Mar 15, 2009        27.01        
       NTSMF 4.0                       Mar 15, 2011        29.03        
      Landmark                                                          
       The Monitor for DB2 Version 2                       13.06        
       The Monitor for DB2 Version 3.0                     16.02        
       The Monitor for DB2 Version 3.1                     20.04        
       The Monitor for DB2 Version 4.0                     22.10        
       The Monitor for DB2 Version 5.0                     30.02        
       The Monitor for CICS/ESA 1.2 -                      12.12        
       The Monitor for CICS/ESA 1.3 -                      15.01        
       The Monitor for CICS/ESA 2.0 -                      15.06        
       The Monitor for CICS TCE 2.1 -                      20.04        
       The Monitor for CICS TCE 2.2 - 20.335, 21.134       21.04        
       The Monitor for CICS TCE 2.3 including CICS/TS 3.1  22.08        
       The Monitor for CICS TCE 3.2 (almost all)           25.11        
       The Monitor for CICS TCE 3.2 (almost all)           27.01        
       The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2)  29.07        
       TMON/CICS 3.4 (for CICS/TS 5.1)               30.30-32.12        
        (Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)              
       TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099)     33.04        
       TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195)    *33.09        
       TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257      34.08        
       The Monitor for MVS/ESA 1.3  -                      12.05        
       The Monitor for MVS/ESA 1.5  -                      12.05        
       The Monitor for MVS/ESA 2.0  -                      15.09        
       The Monitor for MVS/ESA 3.0  -                      19.19        
       TMON/MVS Version 4.4                                32.04        
                                                                        
      Candle                                                            
       Omegamon for CICS V200 User SMF                     12.05        
       Omegamon for CICS V300 User SMF                     13.06        
       Omegamon for CICS V400 User SMF                     16.02        
       Omegamon for CICS V400 type 110 segments            16.02        
       Omegamon for CICS V500 User SMF                     18.01        
       Omegamon for IMS V110 (ITRF)                        12.12        
       Omegamon for IMS V300 (ITRF)                        14.04        
       Omegamon for IMS V550/V560 (ITRF)                   25.05        
       Omegamon for MVS V300                               13.05        
       Omegamon for MVS V400                               13.06        
       Omegamon for DB2 Version 2.1/2.2                    13.05        
       Omegamon for VTAM V160                              12.04A       
       Omegamon for VTAM V400                              15.15        
       Omegamon for VTAM V500                              18.08        
       Omegamon for SMS V100/V110                          12.03        
      CA                                                                
       ACF2 6.2 was 16.04 but ABEND, ACSMFREL=0 May 2018   36.05        
       ASTEX 2.1                                           14.04        
       IDMS 18                                             32.05        
       IDMS 19 (INCOMPAT after PTF R084146 Change 34.164)  33.05        
       NETSPY 4.7                                          14.03        
       NETSPY 5.0                                          14.03        
       NETSPY 5.2                                          16.05        
       NETSPY 5.3                                          18.03        
       NETSPY 6.0                                          20.10 20.305 
       NETSPY 7.0                                          20.10 20.305 
       SAR/VIEW R11                                        23.07 23.196 
      BMC, was Boole & Babbage                                          
       APPTUNE V11R2 SMF 102                               33.11 33.264 
       IMF 3.1 (for IMS 5.1)                               12.12        
       IMF 3.2 (for IMS 6.1 only)                          15.09        
       IMF 3.2 (for IMS 5.1 and 6.1+)                      16.04        
       IMF 3.3 (for IMS 7.1 and 8.1)                      *22.08        
       IMF 4.1 (for IMS 9.1)                              *26.02        
       IMF 4.4 (for IMS 9.1)                              *31.08        
       IMF 4.5 (for IMS 11.1)  (No change since 4.4)       31.08        
       IMF 4.6 a/k/a Mainview IMS                         *31.08        
       IMF 5.1 a/k/a Mainview IMS                         *34.01        
       IMF 5.2 a/k/a Mainview IMS                          34.01        
       IMF 5.3 a/k/a Mainview IMS                          35.03        
       Mainview for MQ Version 4.4                         29.03        
       Mainview for MQ Version 5.1                         30.02        
       Mainview for MQ Version 5.2, 5.3, 5.4               33.01        
       Mainview for CICS Version 6.5 (CICS/TS 5.1)         30.30        
       Mainview for CICS Version 6.4 (CICS/TS 4.2)         30.04        
       Mainview for CICS Version 6.1                       26.26        
       Mainview Auto Operator data file                    28.28        
       Mainview for DB2 THRDHIST file                      20.20        
       Mainview for TCP/IP                                 20.20        
       Mainview for IP                                     34.??        
       Mainview for Batch Optimizer                        19.19        
      Memorex/Telex                                                     
       LMS 3.1                                             12.12A       
      Oracle V9, V10                                       24.06        
      SYNCSORT                                                          
       2.1                                                 33.05        
       1.4                                                 33.08        
      Amdahl                                                            
       APAF 4.1, 4.3                                       16.08        
      Velocity Software                                                 
       XAMAP 3.4                                           22.10        
       XAMAP 3406                                          24.03        
       XAMAP 3.7                                           27.10        
       XAMAP 4.1   Now Renamed to ZVPS 4.1                 29.07        
       XVPS  4.2                                           31.06        
       ZVPS  5.4                                          *33.07        
                                                                        
V.    Incompatibilities and Installation of MXG 38.04.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 38.04:                          
                                                                        
  a- Changes in MXG architecture made between 38.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 http://www.MXG.com            
 is always the most current information on MXG Software status,         
 and is frequently updated.                                             
                                                                        
 Important changes are also posted to the MXG-L ListServer, which is    
 also described by a selection on the homepage.  Please subscribe.      
                                                                        
 The actual code implementation of some changes in MXG SOURCLIB may be  
 different than described in the change text (which might have printed  
 only the critical part of the correction that need be made by users).  
                                                                        
 Scan each source member named in any impacting change for any comments 
 at the beginning of the member for additional documentation, since the 
 documentation of new datasets, variables, validation status, and notes,
 are often found in comments in the source members.                     
                                                                        
                                                                        
Alphabetical list of important changes in MXG 37.08 after MXG 36.36:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  ANAL95TH 38.018  PROC TABULATE 95th pct response stats CICSTRAN/JOBS. 
  ANALATNC 38.005  Report Code for Latent Demand analysis, examples at  
                     https://www.mxg.com/downloads/Latent_Demand        
  ANALID   38.010  ERROR "OPTORG4" if you changed SMFAUDIT to NO.       
  ANALSIIS 38.009  Analysis of Store Into Instruction Stream enhanced.  
  ASMRMFV  38.064  Support for APAR OA58759, caused Condition Code 4.   
  AUTOINST 38.054  ASCII Unique INSTREAM needed for Concurrent Sessions.
  BUILDIMS 38.001  All selections now work, new INPUTCLNR variable.     
  CONFIMXG 38.004  MXG 37.37 only, 1024 should be OPEN_ED=1047.         
  DOCVLONG 38.012  Creates a DOCVLONG with all DOCVER data on one line. 
  FORMATS  38.003A R744HOPM $MG074HO new '50x:CL5 10GBIT/S CEE ROCE'.   
  FORMATS  38.020  Support for SMF73CPT 33/34 connection types.         
  TYPE102  38.019  Support for DB2 APAR PH18739 var QW0389IT in T102S389
  TYPE110  38.060  Long Running CICS Trans, SMF 110 every hour.         
  TYPE110  38.060  SET MONITOR FREQ hourly CICSTRAN for long runners.   
  TYPE112  38.040  OMEGAMON TEMS St 38 INVALID ARGUMENT LENGTH CHANGED. 
  TYPE113  38.035  TYPE113 Counters EXTND247/252/264/265 now labeled.   
  TYPE116  38.037  MQMACCTQ/MQMACCT/MQCFSTAT/MQMQUEUE/ revisions.       
  TYPE123A 38.061  Datetime values were 2080 instead of 2020, MXG error.
  TYPE42   38.011  Support for APAR OA57718, zHyperLink TYPE42DS stats. 
  TYPE62   38.041  Support for APAR OA57105, adds JOBID SYSPLEX.        
  TYPE64   38.041  Support for APAR OA57105, adds JOBID SYSPLEX.        
  TYPE70   38.031  Support for APAR OA56683 SMFBOOST System Recovery    
  TYPE70   38.055  PCTMVSBY incorrect after 37.123. (NOT PCTCPUBY!!!).  
  TYPE73   38.038  Variable SHIFT was not populated.                    
  TYPE80A  38.017  INPUT EXCEEDED due to a HOME segment with no data.   
  TYPE89   38.034  APAR OA59002 corrects TYPE89 var SMF89UZT values.    
  TYPEBE97 38.036  Support for BETA (93) and BETA97 Version 7.1.0       
  TYPEBETA 38.036  Support for BETA (93) and BETA97 Version 7.1.0       
  TYPECIMS 38.058  CIMS/IMF CIMSDBD/DB2/MQ Zero Obs 37.37-38.02         
  TYPECMFV 38.063  CMF VSAM INVALID DATA messages, wrong informat.      
  TYPEDB2  38.062  Support DB2 APAR PI92652,PI82191 and DPAGE support.  
  TYPEIAM  38.006  Support for IAM 9.3 Spin 3 INCOMPATIBLE inserts.     
  TYPEIDMS 38.003  IDMSTAS UOW/NETNAME added, TASUFLD1-3 corrected.     
  TYPEIMS  38.014  Support for APAR PH14569/PH21001 IMS 22 log record.  
  TYPESVIE 38.057  Support for SYSVIEW Subtype 2 record one min detail. 
  TYPETMS5 38.002  Variables BYTEPRC and BESKEY added to TMS/DSNBRECD.  
  TYPETPMX 38.039  Support for new INREI and JCLJJ in TYPETPMX.         
  TYPEVMXA 38.019  z/VM VXAPLSLM variable SHARERAM zero if not RHEL8.   
  TYPEVMXA 38.047  z/VM MONWRITE 6.4.19.1 z15 INCOMPATIBLE.             
  TYPEXAM  38.059  zVPS XAMCUV LCPUID=96 Totals records now deleted.    
  UTILBLDP 38.008  Error after Change 37.149 if first USERADD is IDMS.  
  UTILROLL 38.065  UTILROLL example to combine PDBs created every 4hr.  
  VMACSMF  38.033  SMF Signature Type 2 St 1/2 MANY BACK2BACK LOG msgs  
  VMACSMF  38.051  SAS FTP Access Method &MXGABND=1 set to print errors.
  VMXGINIT 38.046  SAS Option REUSE=YES is forced to REUSE=NO DEFAULT.  
  VMXGOPTR 38.056  ANALHSM caused Error "SAS Option Name OPTIONS 1".    
  TYPEXCOM 38.069  XCOM input did not skip the 461 bytes added in 12.0. 
  TYPE119  38.068  Support for Comm Server SMF 119 Subtype 11 ZERT data.
  TYPE42   38.067  Yet another TYPE42 invalid LENSR in subtype 5 42's.  
  BLDSMPDB 38.081  MXG 38.01 only.  BLDSMPDB WEEKLY JOB ABENDS, typo.   
  FORMATS  38.082  Support for z15 T02 values in $MGRMIPS format.       
  VMAC42   38.079  Support for APAR OA59541 for Type 42 Subtype 27.     
  VMAC102  38.077  SMF102 IFCID 143/144 increase length QW014xUR.       
  VMACDB2  38.075  Support for APAR PH14037 DB2ACCTP QPACPKID truncated.
  ANAL119  38.073  Cleanup and removal of a typo.                       
  TYPE30_6 38.072  Revised deaccumulate for accumulated subtype 6.      
                                                                        
  See member CHANGESS for all changes ever made to MXG Software, or     
  the CHANGES frames at http://www.mxg.com.                             
                                                                        
Inverse chronological list of all Changes:                              
                                                                        
NEXTCHANGE                                                              
                                                                        
====== CHANGES THRU 38.081 WERE IN MXG 38.04 DATED MAY 25, 2020 ========
                                                                        
Change 38.081  MXG 3803 only. The WEEKLY BLDSMPDB failed due to a typo  
BLDSMPDB       in line 667, which has   1    %end;                      
May 25, 2020   Remove that 1.                                           
               The error only occurs if BLDSMPDB is run on z/OA AND only
               if WEEK points to a GDG.                                 
   Thanks to Jim S. Horne, Lowes, USA.                                  
                                                                        
Change 38.080  Support for z15 T02 8562 processor's (156 models) values 
FORMATS        in $MGRMIPS format, used in ASUMMIPS,GRAFCEC,GRAFWLM,    
May 24, 2020   GRAFWRKX and VMACRMFV(RMFIII) to map the MIPS per MSU.   
               If you use those programs to report MIPS, you need 38.04.
                                                                        
Change 38.079  Support for APAR OA59541 for TYPE42 Subtype 27, adds new 
FORMATS        variables;                                               
VMAC42           SMF42REOS='ERASE*ON*SCRATCH?'                          
May 23, 2020     SMF42RZRTY='ZHPF*CHANNEL*PROGRAM*FAILED?'              
                 SMF42RCTCAH='TRANSPORT*COMMAND*AREA*HEADER*7FX'        
                 SMF42RCTCAL='TCA*LENGTH'                               
                 SMF42RCFDCW='FIRST*DEVICE*COMMAND*WORD'                
                 SMF42RCDSCB='DSCBS*WRITTEN'                            
                 SMF42RCLROP='LOCATE*RECORD*OPERATION'                  
                 SMF42RCLRAB='LOCATE*RECORD*AUXILARY*BYTE'              
                 SMF42RCLRIC='LOCATE*RECORD*IMBEDDED*OP CODE'           
                 SMF42RCLRC ='LOCATE*RECORD*COUNT'                      
               and format $MG042VT was updated for new values.          
                                                                        
Change 38.078  zVPS PLSDSPCN LABEL contained an unintended & character. 
VMACXAM                                                                 
May 22, 2020                                                            
                                                                        
Change 38.077  DB2 SMF 102 IFCID 143/144 fields QW0143UR/QW0144UR were  
ANALDB2R       increased to 10 bytes, 6 reserved bytes and new QW0143SI 
VMAC102        and QW0144SI were inserted before QW014xUR in VMAC102,   
May 22, 2020   and the format for QW0143UR/144UR in ANALDB2R updated.   
   Thanks to Terry Chao, DC Government, USA.                            
                                                                        
Change 38.076  Comments revised for the MIPFACTR which is now set from  
GRAFWRKX       the CPFCNAME using the $MGRMIPS format.                  
May 20, 2020                                                            
                                                                        
Change 38.075  DB2 APAR PH14037/UI65711 corrects the offset in DB2ACCTP 
VMACDB2        records for QPACLOCN/QPACCOLN/QPACPKID/QPACASCH/QPACAANM 
May 20, 2020   variables, which caused them to still be truncated. The  
               error was introduced by APAR PH05989/UI61107.  There was 
               no change to MXG code, the IBM APAR corrected the offset.
                                                                        
Change 38.074  PDBAUDIT in BUILDPDB audits the daily PDB size metrics,  
PDBAUDIT       including the SAS compression percent PCOMPRESS, which   
May 19, 2020   can be a negative value, whenever compressing a dataset  
               would have increased its size, and is reported by SAS:   
               "Compressing dataset PDB.STCVSM15 increased by 11.43 pct"
               These datasets always have a small number of variables.  
   Thanks to Randy Hewitt, DXC Technology, USA.                         
                                                                        
Change 38.073  Significant cleanup of ANAL119 after a typo was found in 
ANAL119        37.37 version (extraneous 3 preceding a RUN.)  IPHOSTS DD
May 16, 2020   is no longer required but will be used if it is present  
               and all data steps are skipped if the input datasets are 
               not found.                                               
   Thanks to Tom Kelman, ATOS, USA.                                     
                                                                        
Change 38.072  Type 30 Subtype 6 records have accumulated values but not
VMAC30         all INST counts were deaccumulated, CPUASRTM correction  
May 15, 2020   was subtracted from raw rather than DIF'd values causing 
               a spurious warning message, and minimum SMF time .01 sec 
               was only a few hundred CPUUNITS which caused some small  
               negative values when CPUASRTM was non-zero.              
               The subtype 6 interval records are written instead of 2/3
               for Early ASIDs, STCs that start before JES is up, like  
                  ALLOCAS CAMASTER CONSOLE GRS  JES2AUX PCAUTH RASP     
                  SMSPDSE SMSPDSE1 TRACE                                
   Thanks to Harald Seifert, Huk-Coberg, GERMANY.                       
                                                                        
====== CHANGES THRU 38.071 WERE IN MXG 38.03 DATED MAY  7, 2020 ========
                                                                        
Change 38.071  SAGANAL option SYNC59 was incorrectly flooring ENDTIME,  
SAGANAL        but now uses VMXGDUR to set the Interval Started. SYNC59 
May  6, 2020   adds 1 minute and uses that hour, so with 15 min interval
               data written at SYNC59, these are the hour intervals into
               which the 15 min interval data is assigned.              
                 Original     15:59  16:14  16:29  16:44  16:59  17:14  
                 SYNC  0 hour  15     16     16     16     16     17    
                 SYNC 59 hour  16     16     16     16     17     17    
               Using SYNC59 for SYNC59 data matches common sense.       
                                                                        
Change 38.070  CICS Statistics 110-2 with SMFSTRQT='EOD' End of Day data
VMAC110        have invalid large values, with the same value repeated  
May  2, 2020   for dozens of unique events in time sequence that would  
               normally be accumulated values with zero deltas when they
               are deaccumulated, BUT EOD are NOT accumulated data. Each
               obs is a separate event, and most values are wrong.  In  
               addition, when EOD obs go thru MXG deaccum, obs are lost.
               Intervals of 24 hours are not very useful for analysis.  
               EOD was accidentally set, and you can sum INT data to get
               daily totals if that's what you need.                    
               So, I can not make a business case that the EOD interval;
               is needed, and with a circumvention, I'm not going to    
               pursue a PMR that would waste IBM and Customer time.     
              -When EOD records go thru Deacculation, many observations 
               are lost; I experimented with CICXML to bypass deaccum   
               for EOD, which did preserve observations, but I'm not.   
               going to implement that for other statistics datasets.   
               DO NOT USE EOD FOR SMFSTRQT STATISTICS REQUEST TYPE.     
                                                                        
Change 38.069  XCOM input did not skip the 461 bytes added in 12.0.     
VMACXCOM                                                                
May  1, 2020                                                            
   Thanks to Peter J. Gray, DXC, AUSTRALIA.                             
                                                                        
Change 38.068  Support for Comm Server SMF 119 Subtype 11 ZERT revised  
EXT119ZE       to create new TYP119ZE dataset for each Zert instance,   
IMAC119        which can have more than one obs per record, and remove  
VMAC119        those variables from TYP11911 which has only one obs per 
VMXGINIT       SMF 119 subtype 11 record.                               
Apr 30, 2020   Updates to 73/74 for ICN1762 for IKET are not done, may  
               need data.                                               
                                                                        
Change 38.067  Yet another TYPE42 invalid LENSR in Subtype 5 records has
VMAC42         revised the logic to compare the delta between offsets   
Apr 30, 2020   with NRSR*LENSR, and if the do not, recalculate length   
               by dividing the delta by the NRSR, and if the CALCSRLEN  
               is an integer, use the new length for LENSR, or delete.  
               This was from old customer data and may not be a current 
               value, but this should finally eliminate exposures.      
   Thanks to John Compton, Worldprogramming, ENGLAND                    
                                                                        
Change 38.066  Dataset ASUMCAPT was not labeled.                        
VMXGCAPT                                                                
Apr 24, 2020                                                            
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 38.065  UTILROLL will rollup all observations in all datasets in 
UTILROLL       a data library into all datasets in another data library.
Apr 29, 2020   New examples added to combine PDBs created every four    
               hours into a daily PDB library, and to copy multiple days
               back to WORK for reporting. Modified to use PROC SQL to  
               get the engine of the output libname on z/OS so it works 
               for tape or sequential PDBs.  Also added FORCE to the    
               PROC APPEND to prevent warnings and added SORTEDBY and   
               ALLDATA datasets created by the macro to ROLLDROP.       
                                                                        
Change 38.064 -After New Function APAR OA58759 of 3/26/2020 for RMF the 
ASMRMFV        ERB3RDEC decompression load module does not contain an   
Apr 24, 2020   expected FMID. As a result ASMRMFV issues warning message
               RMFV091W that the module is not from IBM. Processing     
               continues normally, but Return Code 0004 is set.         
              -ASMRMFV will now also check for an 'IBM' character string
               in ERB3RDEC before issuing RMFV091W. The RMFV091W message
               was also incorrectly formatted.                          
                                                                        
Change 38.063  Variables WKRSENCP/WKRSENCV/WKRIENCP/WKRIENCV caused     
VMACCMFV       INVALID DATA messages because they were INPUT as &RB.4.  
Apr 24, 2020   (which worked fine when the fields were zeros) but they  
               are non-zero and are input with &PIB.4 informat.         
   Thanks to John Kim, TELUS, CANADA.                                   
                                                                        
Change 38.062 -DB2STAT0 variable QW0225_WARN was incorrectly treated as 
VMACDB2        bytes, and it is SERVICEABILITY.                         
Apr 22, 2020  -Support for APAR PI92652 that adds I/O Interrupt CPU time
               variables QWSxIIPT variables in dataset DB2STAT4.        
              -Support for APAR PI82191 that adds 3 _DPAGE variables to 
               dataset DB2STAT4, which per the APAR text, are now also  
               subtracted to correct the three _REAL variables.  The    
               APAR text listed a fourth  PVTSTG_DPAGE field, but it    
               does NOT exist in the records with segment length 320.   
   Thanks to Scott Barry, SBBTechLLC, USA.                              
                                                                        
Change 38.061  Support for z/OS Connect EE SMF 123 Version 2 Records    
EXTY1232       create new dataset:                                      
IMAC123A         DDDDDD   DATASET   Description                         
VMAC123A         TY123A   TYPE123A  Z/OS CONNECT EE AUDIT V1            
VMXGINIT         TY1232   TYPE1232  z/OS CONNECT EE AUDIT V2            
Apr 30, 2020   The new version 2 record creates new TYPE1232 dataset    
               because of many new variables.                           
              -Member TYPE123A creates TYPE123A and TYPE1232 for EE.    
              -Member TYPE123  is archaic, for the S/390 Parallel Query 
               Server SPQS SMF 123 Record datasets DB2SPQS/DB2SPQAB.    
   Thanks to Adam Banbury, PNC, USA.                                    
   Thanks to Robert Carter, PNC, USA.                                   
   Thanks to Robert Richards, PNC, USA.                                 
                                                                        
Change 38.060  CICSTRAN observations are written at task termination,   
VMAC110        so long running transactions won't have observations,    
Apr  9, 2020   but the CICS SET MONITOR command FREQUENCY argument will 
               create interval CICSTRAN observations, which can be      
               identified with RTYPE='F'.  RTYPE formatted values:      
                 'C'='C:TERMINAL CONVERSE'                              
                 'D'='D:USER EMP DELIVER REQUEST'                       
                 'F'='F:FREQUENCY REQUEST'                              
                 'M'='M:SEMI-PERMANENT MIRROR SUSPEND'                  
                 'S'='S:SYNCPOINT'                                      
                 'T'='T:TASK TERMINATION'                               
   Thanks to Rob Hollingum, HSBC, ENGLAND                               
   Thanks to Renata Hoyland, HSBC, ENGLAND                              
                                                                        
Change 38.059 -zVPS XAMCUV records with LPARNAME='TOTAL' weren't output 
EXXAMCUV       because they duplicate the detail record's values. zVPS  
FORMATS        now sets LCUCPUID=96 for all total records, so the test  
VMACXAM        to NOT output in EXXAMCUV now tests to skip the 96's.    
Apr  8, 2020   This test is located in the Data Set Exit member so that 
               you can always override my decision to not OUTPUT them.  
              -Variables LCUCPUID LCXCPTYP are added to the _BXAMCUV BY 
               list for dataset XAMCUV.                                 
              -XAMCUV records have LCXCPTYP=1 for CP/GP engine instead  
               of zero, so the MGXAMTY format now maps that value also. 
   Thanks to John Holiday, Queensland Government, AUSTRALIA.            
                                                                        
Change 38.058  CIMS/IMF datasets CIMSDBD,CIMSDB2,CIMSMQ had zero obs    
VMXGINIT       in 37.37-38.02 because the three SELECTDBD/DB2/SELECTMQ  
Apr 21, 2020   macro variables added for BUILDIMS were only %GLOBALed   
               in VMXGINIT where they should have been %LET to defaults.
               The three statements have been added to VMXGINIT, but you
               can insert these three statements in your //SYSIN for    
               your CIMS/IMF processing jobs and they will be populated.
                 %LET SELECTDBD=%STR(OUTPUT _WIMFDBD;) ;                
                 %LET SELECTDB2=%STR(OUTPUT _WIMFDB2;) ;                
                 %LET SELECTMQ =%STR(OUTPUT _WIMFMQ;) ;                 
   Thanks to Andreas Menne, Finanz Informatik, GERMANY.                 
                                                                        
Change 38.057  Support for SYSVIEW Subtype 2 record creates new datasets
IMACSVIE         PDB.SV02INT  - Interval Data - One Obs per Minute.     
VMACSVIE                        Merge of 263 datasets, 1440 Obs daily.  
VMXGINIT         PDB.SV02MQ   - MQ Interval Data - One obs per MQ Subsys
Apr 20, 2020                    Merge of 25 datasets, 2880 Obs daily.   
                 PDB.SV02LP   - LPAR Interval Data - one per ARGEIGHT,  
                                individual LCPUADDR 0000-000B, and ALL  
                                CP,IFA,IIP,SP, 24480 obs THIS LPAR.     
                 PDB.SV02CP   - CPUPLPAR for all LPARs, 47520 obs.      
                 PDB.SV02WL   - WLM Service/Reporting Class 250560 obs. 
                 PDB.SV02PLOT - Control Variables, one obs/record.      
   Thanks to Nagaraj Pudokotia, ATOS, INDIA.                            
   Thanks to Martyn Jones, CPTGLOBAL, ENGLAND.                          
                                                                        
Change 38.056 -If you tried to reset an option with VMXGOPTR to ORIGINAL
ANALHSM        that hadn't previously been set using VMXGOPTR, the code 
VMXGOPTR       generated here was "OPTIONS 1;" which caused ERROR 13-12:
Apr  6, 2020   Unrecognized SAS option name 1, and execution terminated.
              -Now: VMXGOPTR detects that that option had not been set, 
               stores the current value and does not execute OPTIONS.   
              -ANALHSM was the culprit that exposed the error and was   
               corrected.                                               
   Thanks to Jack Hyde, OPTUM, USA.                                     
                                                                        
Change 38.055  Change 37.123 (MXG 37.04) incorrectly changed variable   
VMAC7072       PCTMVSBY which impacted PLCPRDYQ and SHORTCPS in datasets
VMXGRMFI       PDB.TYPE70 and PDB.RMFINTRV.                             
Apr 30, 2020                                                            
   Thanks to Paul Naddeo, Fiserv, USA.                                  
   Thanks to David Bixler, Fiserv, USA                                  
   Thanks to Robin Hanley, Fiserv, USA                                  
   Thanks to Bernie Ethridge, Fiserv, USA.                              
                                                                        
Change 38.054 -ALL ASCII SITES SHOULD ENABLE %AUTOINST IN IMACINIT.     
AUTOINST      -Concurrent ASCII SAS sessions can error due to INSTREAM  
IMACINIT       file sharing. The same INSTREAM.SAS file is used on ASCII
May  3, 2020   for every session, so multiple concurrent sessions error 
               because of the uninteded file sharing. The new &AUTOINST 
               %MACRO creates the temporary INSTREAM file in the session
               WORK libname, which is not sharable with other sessions. 
                 FILENAME INSTREAM CATALOG 'WORK.TEMP.INSTREAM.SOURCE'; 
                a. Put the %AUTOINST; statement in the member IMACINIT  
                   in your "USERID.SOURCLIB" tailoring library and the  
                   unique file name will always be allocated.           
                b. Put the %AUTOINST; in AUTOEXEC, replacing the        
                   INFILE INSTREAM statement.                           
                c. Issue the %AUTOINST; in your SYSIN at start.         
              -ALL ASCII SITES SHOULD PUT %AUTOINST IN IMACINIT.        
              -z/OS sites can enable %AUTOINST in IMACINIT and then the 
               INSTREAM filename will always be created if it was not   
               already allocated.                                       
                                                                        
Change 38.053  Typo, variable not found, QHSSSID should be QWHSSSID.    
ANALDB2T                                                                
Mar 30, 2020                                                            
   Thanks to Douglas C. Walter, CITIGROUP, USA.                         
                                                                        
Change 38.052  Spurious WARNING: MISSING %MEND Statement for VMXG344 is 
BUILDPDB       sometimes printed after prior error conditions; adding   
BUILDPD3       the name of the %MACRO to the %MEND eliminates message.  
BUILD001                                                                
BUIL3001                                                                
Mar 29, 2020                                                            
                                                                        
Change 38.051  Using the SAS FTP Access Method, &MXGABND=1 is now set so
VMACSMF        that errors (e.g. the SMF file is in use) that can cause 
Mar 27, 2020   the SAS Session to hang doing nothing, instead will now  
               terminate with USER ABEND 69.                            
               If the session still hangs, and you have access to the   
               directory where the SAS log is being written by that     
               active session, you should be able to get read access to 
               the active session's log to see if there are messages    
               before you kill the session.                             
   Thanks to Richard Way, Office Depot, USA.                            
   Thanks to Amlan Mitra, Office Depot, USA.                            
                                                                        
Change 38.050  Variable QBSTPCO in dataset DB2STATB was always a        
VMACDB2        missing value after DB2 Version 9 due to MXG logic       
Mar 24, 2020   error for its INPUT.                                     
   Thanks to Flavio Lima, US.IBM.COM, USA.                              
                                                                        
Change 38.049 -New parameter ROLLWEEKS=5 added to let you keep more     
BLDSMPDB       weeks than the 5 needed to build a month. NOTE: this     
Mar 24, 2020   only applies on zOS or ASCII with STATIC libnames.       
               With GDGs on zOS or AUTOALOC on ASCII ROLLWEEK is        
               disabled.                                                
              -So if you want to keep 6 weeks of rolling weekly         
               data specify rollweeks=6.  If the WEEK6 LIBNAME is       
               not found an error message is generated.                 
   Thanks to Richard Haynes, Blue Cross Blue Shield of Kansas, USA.     
                                                                        
====== CHANGES THRU 38.048 WERE IN MXG 38.02 DATED Mar 23, 2020 ========
                                                                        
Change 38.048  Support for z15 INCOMPATIBLE z/VM MONWRITE 6.4.19.1 due  
VMACVMXA       to insertion of new EXTND256-EXTND287 counters in dataset
Mar 20, 2020   VXPRCMFC and new variables CORCTLMT CORTLSEQ in VXPRCMFM.
               Many ERROR. PRCMFC HARDWARE COUNTER UNEXPECTED messages, 
               and datasets VXPRCMFC/VXPRCMFM have no observations, but 
               all the other z/VM MONWRITE datasets are not impacted    
   Thanks to David Campbell, SunTrust, USA.                             
                                                                        
Change 38.047  Variables R7023DID/R7024DID, Domain ID, are added to the 
VMAC7072       end of the BY List for datasets TYPE7002 and TYPE70X, and
Mar 18, 2020   R7023DID is kept in TYPE7002.                            
   Thanks to Stephen Hoar, Lloyds, ENGLAND.                             
                                                                        
Change 38.046  Data Set Labels were revised:                            
VMACDB2          DB2PST: DB2 STATS GLOBAL BUFF POOL                     
Mar 17, 2020     DB2PAT: DB2 GLOBAL BUFF POOL ATTRIBS                   
                                                                        
Change 38.045  MXG sets option REUSE=NO to prevent a User change to YES 
VMXGINIT       in this just-discovered obscure option, that controls how
Mar 17, 2020   free-space is used when new observations are added to an 
               existing compressed SAS dataset, i.e., whether new obs   
               are inserted in free space or added at the end, but with 
               REUSE=YES, and COMPRESS=YES, the POINT= dataset option   
               ABENDs because it cannot open compressed SAS datasets.   
               MXG uses POINT= and sets COMPRESS=YES default value.     
               PROC APPEND disregards REUSE=YES, adding new obs at the  
               end of the dataset.  REUSE is an attribute of the dataset
               and cannot be changed for that dataset.                  
   Thanks to Richard Haynes, Blue Cross Blue Shield of Kansas, USA.     
                                                                        
Change 38.044  VSAM Extended Addressability datasets values for sizes   
VMAC60         VVRDSHA VVRDSHU VVRHARBA VVRHURBA must be multiplied by  
Mar 15, 2020   VVRAMCIV, the CISIZE.  New variable VVREXTAD='Y' if this 
               is an Extended Addressability dataset (not to be confused
               with Extended Format datasets).                          
   Thanks to Michael Friske, FMR, USA.                                  
                                                                        
Change 38.043  Documentation only.  Example 10 show ways to select or   
READDB2        exclude data by QWHSSSID SubSystem ID.                   
Mar 14, 2020                                                            
                                                                        
Change 38.042  Your USER SMF record type descriptions are in IMACSMFF in
IMACSMFF       your tailoring, which adds them to $MGSMFID when FORMATS 
Mar 13, 2020   is run, but the MXG syntax - an eight-character VALUE,   
               with a leading blank if TYPE is LT 1000 - was not stated.
               A seven-character value without blank caused no error,   
               but those types had no description in ANALID reports.    
   Thanks to Jeff Harder, Indiana Farm Bureau Insurance, USA.           
                                                                        
Change 38.041  Support for APAR OA57105, adds to TYPE62/64              
VMAC62          Dataset TYPE62 New Variables                            
VMAC64             SMF62JOBID  ='JOB*ID'                                
Mar 12, 2020       SMF62SYSPLEX='SYSPLEX'                               
                   Variable SMF62DEF removed, did not exist and caused  
                   variables SMF62DET and SMF62DKL to be missing/blank. 
                Dataset TYPE64 New Variables                            
                   SMF64JOBID  ='JOB*ID'                                
                   SMF64SYSPLEX='SYSPLEX'                               
                                                                        
Change 38.040  OMEGAMON TEMS Subtype 35 INVALID ARGUMENT THREE because  
VMAC112        the text length was increased from MXG's original guess  
Mar 14, 2020   of 256 with a length of 261, so the lengths are now 512. 
   Thanks to Jim Czechanski, Northwestern Mutual, USA.                  
                                                                        
Change 38.039  Support for new variables INREI and JCLJJ in TYPETPMX.   
VMACTPMX                                                                
Mar  5, 2020                                                            
   Thanks to Scott Barry, SBBTechLLC, USA.                              
                                                                        
Change 38.038  Dataset TYPE73 variable SHIFT was not populated; the code
VMAC73         for IMACSHFT was only in the code blocks for TYPE73P/L.  
Mar  4, 2020                                                            
   Thanks to Mark Hiltbruner, State of South Dakota, USA.               
                                                                        
Change 38.037 -MQM Header/Correlation variables that are now kept:      
VMAC116         Dataset  MQMACCTQ                                       
Mar 11, 2020     QWHCAID  QWHCCVMQ QWHCCN                               
                 QWHCPSB  QWHCPST  QWHCTASK QWHCTNO QWHCTRN QWHCXTYP    
                 QWHSACE  QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN  QWHSSTCK    
                 QWHSWSEQ WTCORREL                                      
                Dataset  MQMACCT                                        
                 QWHCAID  QWHCCN   QWHCCVMQ QWHCNID QWHCOPID QWHCPSB    
                 QWHCPST  QWHCTASK QWHCTNO  QWHCTRN QWHCXTYP QWHSACE    
                 QWHSIDMQ QWHSISEQ QWHSRN  QWHSSTCK QWHSWSEQ            
                Dataset MQCFSTAT                                        
                 DSECT WTCORREL WTASINTE WQBASENA                       
                Dataset MQCHININ                                        
                 QWHSACE QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN QWHSSTCK      
                 QWHSWSEQ                                               
                Dataset MQMQUEUE                                        
                 QWHCAID  QWHCCCMQ QWHCCN                               
                 QWHCPSB  QWHCPST  QWHCTASK QWHCTNO QWHCTRN QWHCXTYP    
                 QWHSACE  QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN  QWHSSTCK    
                 QWHSWSEQ                                               
              -Alignment of the WTAS INPUT now populates WTAS variables.
              -The code segment for SUBTYPE=2 was relocated.            
              -Dataset MQMACCTQ is only output for SUBTYPE=1.           
   Thanks to Richard Simpson, CPTGLOBAL, AUSTRALIA.                     
   Thanks to Martyn Jones, CPTGLOBAL, ENGLAND.                          
                                                                        
Change 38.036 -TYPEBETA variables L030SRCJCSY/JCUS, S055IPSERVI were    
VMACBETA       incorrectly spelled in the KEEP= list and are now kept   
VMACBE97       as L030SRCJCSYS/L030SRCRCUSR/S055IPSEVI.                 
Mar  1, 2020  -TYPEBE97 variables B9759STY_1HEX B9759STY_2HEX were also 
               corrected to B9759STY_1_HEX andB975STY_2_HEX.            
                                                                        
Change 38.035  TYPE1131 vars EXTND247/252/264/265 now KNOWN COUNTERs.   
VMAC113                                                                 
Feb 28, 2020                                                            
   Thanks to Harald Seifert, Huk-Coburg, GERMANY.                       
                                                                        
Change 38.034  APAR OA59002 corrects invalid values in SMF89UZT in the  
TECHNOTE       TYPE89 dataset.                                          
Feb 27, 2020                                                            
   Thanks to Nick Varley, SYNCSORT, USA.                                
                                                                        
Change 38.033 -SMF Signature Type 2 Subtype 1 and 2 can print MANY log  
VMACSMF        "BACK2BACK HEADER" messages, if you have changed the     
Feb 28, 2020   IFASMFDL program default option SIGSTRIP to NOSIGSTRIP.  
               IFASMFDL is the "SMFDUMP" program for SMF LogStreams, and
               that SIGSTRIP default is to "Strip", i.e. NOT WRITE the  
               SMF Type 2 Subtype 1/2 records to the Output SMF file.   
              -The MXG _SMF Record Processing logic that writes those   
               Header/Trailer/First/Last diagnostics messages was not   
               updated when the VMAC0203 was updated in 2017, and these 
               new type 2 records caused spurious log messages. Datasets
               TYPE0201/TYPE0202/TYPE0203 were correct as the messages  
               have no impact on output datasets. You can use           
                                                                        
         ==>   TO SUPPRESS PRINTING OF ALL SMF DIAGNOSTIC MESSAGES, USE:
         ==>    //SYSIN DD *                                            
         ==>    %LET SMFPUTHD=NO;                                       
                                                                        
               or you can restore your IFASMFDL JOB to SIGSTRIP default,
               or you can use VMACSMF with Change 38.033+ (MXG 38.02).  
              -If you are back-level at MXG 36.04, then you will also   
               also need the DODSCRDT/READRATE/VMXGINIT members.        
               Macro variable SMFPUTHD was added in MXG 31.31.          
              -This _SMF header code is ALWAYS USED WHEN MXG READS SMF, 
               so you will see those diagnostic messages, when TYPE 2,  
               subtype 1 or 2 records are present, in the SMF file,     
               even if you didn't request Type 02 record processing.    
                 Change 35.266 notes "Even After OA?????, SYSTEM='DUMY' 
                 Type 02 14 byte records were still found." and they    
                 still are; the first SMF Header Message with NOSIGSTRIP
                 has "DUMY' and not the actual system, but the "FIRST"  
                 message that follows will have the actual SYSTEM name. 
                 (The APAR number in that APAR change is lost.)         
              -There were fifty ID=2 ST 1/2 messages per minute, or     
               about 288,000 SYSOUT print lines per day, which could    
               could cause a 722 SYSTEM ABEND.                          
                 How did I miss this in 2017 when subtype support was   
                 added? The original customer could not ftp SMF data, so
                 LIST; was used to print a hex dump of each subtype,    
                 which UTILBHEX converted to readable records, so there 
                 were (only) two back to back (expected) ID=2 records.  
               You must be at MXG 37.06 or later to use this VMACSMF.   
   Thanks to Douglas C. Walter, CITIGROUP, USA.                         
                                                                        
Change 38.032  Many missing values in WSFAUDIT dataset from TYPEWSF are 
VMACWSF        valid as the record only contains nulls starting in byte 
Feb 26, 2020   153.  Vendor is to be contacted.                         
                                                                        
Change 38.031  Support for APAR OA56683 adds SMFBOOST variables (System 
FORMATS        Recovery Boost) to dataset TYPE70:                       
VMAC7072          BOOSTACTIVE='BOOST*ACTIVE*FULL*INTERVAL'              
Feb 20, 2020      BOOSTINFO  ='BOOST*INFO*PARTIAL*INTERVAL'             
                  BOOSTCLASS ='BOOST*CLASS'                             
               and FORMAT MG070SB decodes BOOSTACTIVE and BOOSTINFO as  
               ZIP or SPEED or BOTH. CLASS is either IPL or SHUTdown.   
   Thanks to Martin Packer, IBM, EUROPE!                                
                                                                        
Change 38.030  The example user tailoring for multiple TMS catalogs in  
ADOCTMS5       ADOCTMS5 (that you EDIT into your IHDRTMS5) ABEND 992 if 
Feb 20. 2020   the CRDDD days value was greater than 366; now an error  
               message and hex dump of the first 5 eliminates the ABEND.
                                                                        
Change 38.029  z/VM MONWRITE dataset VXAPLSLM (Z/VM LINUX MEMORY)       
VMACVMXA       variable SHARERAM is zero if Linux is not RHEL8.         
Feb 14. 2020                                                            
                                                                        
Change 38.028 -FDF (Field Data Filter) support added for the RMF Monitor
ADOCRMFV       III ZFXG3 (zFS Performance Data Table).   General ASMRMFV
ASMRMFV        support for this table already existed.                  
VMACRMFV      -Sysout output lines from ASMRMFV assembly reduced.       
Feb 21, 2020                   ** IMPORTANT **                          
Feb 28, 2020  -National character (@#$) pattern filter is now the '^'   
               caret character NOT the '.' period character.  There was 
               a conflict when an RMF III table field contained a       
               DSNAME.  The caret character may not print with some     
               SYSOUT character sets.                                   
              -This documentation section in member ADOCRMFV is added   
               for new FDF support:                                     
               44 Filtering The ZFXG3 Table                             
               Remaining existing section numbers are incremented by 1. 
              -FDF GOVAT macro call for ZFXG3 table was incomplete.     
               Table selection would not occur when needed if ZFXG3 was 
               not explicitly selected when using FDF.                  
              -VMACRMFV did not populate variable ENCCFL2 in ZRBENC.    
                                                                        
====== CHANGES THRU 38.027 WERE IN MXG 38.01 DATED Feb 17, 2020 ========
                                                                        
Change 38.027 -TYPE42D3 and TYPE42D4 datasets had the below variables   
VMAC42         incorrectly INPUT as SMF42Gxx instead of SMFA2Gxx so they
Feb 13, 2020   were not kept nor labeled.                               
               Dataset TYPE42D3                                         
                 SMFA2GUA SMFA2GUB SMFA2GUD SMFA2GUE SMFA2GUF SMFA2GUG  
                 SMFA2GSH SMFA2GSI SMFA2GSJ SMFA2GSK                    
               Dataset TYPE42D3                                         
                 SMFA2GVA SMFA2GVB SMFA2GVD SMFA2GVE SMFA2GVF SMFA2GVG  
                 SMFA2GTH SMFA2GTI SMFA2GTJ SMFA2GTK                    
               Some SMF42Gxx and SMFA2Gxx variable's label incorrectly  
               had "*DASD" which was removed.                           
   Thanks to Michael Friske, FMR, USA.                                  
                                                                        
Change 38.026 -New variables STC28CTP and STC28FLG are now INPUT and    
VMACSTC        kept in dataset STCVSM28, variables STC19CTP and STC28CTP
Feb 13, 2020   are formatted $MGSTCCT to display Cartridge Type.        
   Thanks to Randy Hewitt, DXC, USA.                                    
                                                                        
Change 38.025  Support for CICSTRAN Optional CPICAOR/CPICAOR user field 
IMACICXC       that populates USERCHAR.                                 
UTILEXCL                                                                
Feb 12, 2020                                                            
                                                                        
Change 38.024 -Support for zVM VXPRCAPM dataset Crypto Types 11,12,13   
VMACVMXA       CEX5S/CEX6S/CEX7S, which printed "UNDECODED CRYPTO TYPE".
Feb 10, 2020  -Variable IODSSCH in VXIODDEV dataset is incorrect for    
               intervals with more than 65K I/Os, short by 65K counts,  
               but RDEVSKCT captures all I/Os, so MXG now sets variable 
               IODSSCH=RDEVSKCT for those intervals.                    
   Thanks to Graham Harris, RBS, ENGLAND.                               
                                                                        
Change 38.023  RMF ZFX variables ZFX_IO_WAIT_TIME, ZFX_LOCK_WAIT_TIME   
VMACRMFV       and ZFX_MONITORED_SLEEP_TIME in dataset ZRBZFX can be    
Feb 10, 2020   negative values because the ZfS interface bases average  
               response times on requests since last statistics reset,  
               which can be very long. zFS development is aware of their
               design flaw but have not yet responded with a correction.
                                                                        
Change 38.022  Label for EXTEND164 was changed for the z14 and z15 to:  
VMAC113         EXTND164='DIRWRIT*TO L1-I*ON CHIP*L3 INTVNT'            
Feb 10, 2020                                                            
   Thanks to George A. Frey, PNC, USA.                                  
                                                                        
Change 38.021  PROC TIMEPLOT example to show concurrent job executions  
ANALJOBS       and SGPLOTS of ANALCNCR statistics for all jobs or for   
Feb 9, 2020    selected jobs.                                           
                  %ANALJOBS(PDB=PDB,INCODE=if JOB I: ('SYS','PAY'));    
                                                                        
Change 38.020  Support for TYPE73 variable SMF73CPD Connection Types are
FORMATS        added to $MG073CD format.                                
Feb 7, 2020      '33'X='33X:COUPLING EXPRESS SR'                /*OSM*  
                 '34'X='34X:COUPLING EXPRESS LR'                /*OSM*  
   Thanks to Ehren Bailey, Progressive Insurance, USA.                  
                                                                        
Change 38.019  Support for DB2 APAR PH18739 EPIC 1016 that adds  a new  
VMAC102        variable QW0389IT='NUMBER*OF INDEX*TRANSVERSALS' to      
Feb 6, 2020    dataset T102S389, COMPATIBLE, using a reserved field.    
   Thanks to Harald Seifert, Huk-Coburg, GERMANY.                       
                                                                        
Change 38.018  SAS levels prior to TS1M6 for ODS PDF should avoid use   
TECHNOTE       of CONTENTS on the ODS statement.  There are several     
Feb 5, 2020    errors that can be caused and any graphs may overlay     
               the contents. For details see:                           
               http://support.sas.com/kb/20/666.html                    
                                                                        
Change 38.017 -TYPE80A INPUT EXCEEDED ERROR due to a HOME segment that  
VMAC80A        had no data following, now protected.                    
Feb 11, 2020  -Support for TYPE80TK fields TOKMARCHIDE,TOKMSISEMAIL,    
               TOKMARCSISID TOKMIRRDAUTO.                               
              -SMF 80 SHORT EXTENDED RELOCATE FOUND messages were caused
               when a field input with $VARYINGnn LEN was increased with
               the actual data length LEN that is greater than the nn.  
              -The TYPE80TOK segments with TOKSUBSY='CSDATA' are "user" 
               or "customer" fields added by vendors or installations.  
               One CSDATA record where TOKDANAM=SISLAST was the last in 
               the record was truncated, with length 16 with only 14    
               bytes followed. Other SISxxxx segments were the last in  
               the record and were not truncated. An MXGNOTES is printed
               when truncation is detected and protected.               
   Thanks to Joe Faska, DTCC, USA.                                      
                                                                        
Change 38.016A ANAL95TH uses PROC TABULATE to create 95th percentile,   
ANAL95TH       mean and max response and resource statistics, with      
Feb  5, 2020   two examples of CICSTRAN.CICSTRAN by TRANNAME, one       
               across all executions and one by TRANNAME for 15 min     
               intervals, and one for PDB.JOBS by JOBCLASS for hour     
               intervals, but the syntax can be used for any data.      
   Thanks to Robert Barth Cross, IBM, USA.                              
                                                                        
Change 38.016  SGPLOTS referenced &PDBMXG..NATADAPCT which did not      
ANALNATR       exist. Changed to PDBOUT.NATADAPCT.                      
Feb  5, 2020                                                            
   Thanks to Mark Hiltbruner, State of South Dakota, USA.               
                                                                        
CHANGE 38.015  See Change 38.061.                                       
                                                                        
CHANGE 38.014A ASCII Execution ERROR: Template 'Styles.MXGxxxx' was     
TECHNOTE       unable to write to template store when attempting to     
Jan 29, 2020   update the FORMAT directory, because a separate SAS      
               Windows session was using the LIBRARY catalog.           
                                                                        
CHANGE 38.014  Support for IMS APAR PH14569(v14) and PH21001 (V15)      
VMACIMS        which populates the USERID field in IMS 22 log record.   
Jan 29, 2020                                                            
                                                                        
CHANGE 38.013  Support for BETA93 and BETA97 Version 7.1.               
FORMATS       -Variables added to BETA9749 dataset:                     
VMACBETA        B9749PGM B9749VER B9749PTF B9749CDT B9749CTM B9749RC    
VMACBE97        B9749IC B9749STIME B9749ETIME B9749INFO B9749SELPTM     
EXTYB97T        B9749SCPUTM B9749SGETIO B9749SPUTIO                     
EXTYB97U        and the accounting fields are correctly aligned now.    
EXTYB97V      -New dataset BETA9755 variables:                          
VMXGINIT        B9755INDICAT B9755USER B9755IPCLN B9755IPSEV            
Feb 13, 2020    B9755IFLGS B9755HOSTIPORT B9755SERVPORT B9755IPHOST     
                B9755IPCLIENT B9755IPSERV B9755IPSERVI                  
              -New dataset BETA9759 variables:                          
                B9759MAXSUBT B9759CURSUBT B9759STBYTE B9759RQUST        
                B9759VERSION B9759INTERCNT B9759INTERTIME B9759NTAB1    
                B9759NTAB2 B9759STY_1 B9759STY_2 B9759ALLCNTW           
                B9759ALLCNTN B9759ALLCNTS B9759ALLCNTB                  
              -New dataset BETA9759SFF variables:                       
                B9759MJRCPU B9759MJRCPUN B9759MJRSRB B9759MJRSRBN       
                B9759MJRZIIP B9759MJRZIIPN B9759MJRCPU B9759MJRCPUN     
                B9759MJRSRB B9759MJRSRBN B9759MJRZIIP B9759MJRZIIPN     
              -New dataset BETA9759SFF variables:                       
                B9759MNRCPUN B9759MNRSRB B9759MNRSRBN B9759MNRZIIP      
                B9759MNRZIIPN B9759MNRCPU B9759MNRCPUN B9759MNRSRB      
                B9759MNRSRBN B9759MNRZIIP B9759MNRZIIPN                 
              -Datasets BETA0, BETA1, BETA55, BETA59  also have new     
                variables; they are listed in DOCVER38.                 
   Thanks to Andreas Menne, Finanz Informatik, GERMANY.                 
                                                                        
CHANGE 38.012  The MXG member DOCVER documents all variables in all MXG 
DOCVLONG       datasets, originally one line per variable, but the long 
Jan 25, 2020   variable names and MXG's 72-character z/OS limit caused  
               two lines to be needed.  The DOCVLONG program creates the
               "DOCVLONG.TXT" file with one line per variable with new  
               LRECL=94 to contain all the information.  This change    
               corrected an ERROR if the variable name ended in NUM and 
               was 13 characters long.                                  
                                                                        
                 ON Z/OS:                                               
                //  EXEC MXGSASV9                                       
                //INDOCVER DD DSN='MXG.SOURCLIB(DOCVER),DISP=SHR        
                //DOCVLONG DD DSN='MXG.DOCVLONG,TXT,DISP=(,CATLG),      
                //         DD RECFM=FB LRECL=94 BLKSIZE=34500.          
                //         DD SPACE=(CYL,(40,4))                        
                //SYSIN DD *                                            
                   %INCLUDE SOURCLIB(DOCVLONG);                         
                ON ASCII:                                               
                 FILENAME INDOCVER 'D:\MXG\SOURCLIB\DOCVER.SAS';        
                 FILENAME DOCVLONG 'D:\MXG\USERID\DOCVLONG.TXT';        
                  %INCLUDE SOURCLIB(DOCVLONG);                          
                                                                        
CHANGE 38.011  Support for APAR OA57718 that adds new zHyperlink write  
VMAC42         statistics to TYPE42DS dataset.                          
Jan 23, 2020                                                            
                                                                        
Change 38.010  If you changed the default SMFAUDIT=YES option to NO,    
ANALID         to suppress the SMF Audit Report (BUILDPDB,ANALID),      
Jan 24, 2020   inside ANALID, the VMXGOPTR utility could fail           
                  MXGNOTE: END OF ANALID                                
                  NOTE: Line generated by the macro variable "OPTORG4". 
               Change 37.245's setting options with VMXGOPTR in ANALID  
               were mis-located inside SMFAUDIT=YES block in MXG 37.08, 
               now relocated in MXG 38.01.                              
   Thanks to John Milne, IBM, AUSTRALIA                                 
                                                                        
Change 38.009  If you specified GRAPHS=YES and your system is old and   
ANALSIIS       not have the option SYSODSGRAPHICS or you are on z/OS    
READRATE       where it is 0 until an ODS GRAPHICS command is issued,   
Jan 24, 2020   the code defaulted to using PROC PLOT where XAXIS is not 
               supported. ANALSIIS and READRATE were both modified to   
               use the version executing to choose SGPLOT vs PLOT, and  
               XAXIS was removed from the PROC PLOT.                    
   Thanks to Mike Martin, North Carolina NCSECU, USA.                   
                                                                        
CHANGE 38.008  Change 37.149 was in error if first USERADD= was IDMS.   
UTILBLDP                                                                
Jan 22, 2020                                                            
   Thanks to Scott Barry, SBBTechLLC, USA.                              
                                                                        
Change 38.007  The BY LIST for PROC MEANS DATA=_LVMAINT inside INTVBLD  
VMACVMXA       is changed to BY CECSER SYSTEM, removing BEGINMTR, which 
Jan 21, 2020   caused tens of thousands of useless statistics.          
   Thanks to Scott Barry, SBBTechLLC, USA.                              
                                                                        
Change 38.006  Support for IAM 9.3 Spin 3 INCOMPATIBLE due to relocation
VMACIAM        and insertion of fields; many new variables in TYPEIAM.  
Feb  5, 2020                                                            
   Thanks to Mike Jacques, BBandT, USA.                                 
                                                                        
Change 38.005  "Expressing Latent Demand as a Single Number" report code
ANALATNC       starts by graphing a latency number for all systems by   
Feb  5, 2020   interval on a single graph and drills down to individual 
               systems from there, displaying SMF70U00-15 variables in a
               stacked bar graph with the latency number and MVS Busy   
               for each systems as lines on top of the bar. Latency is a
               number based on bucket sizes of the SMF70U: (or SMF70Q:  
               for older OSes), designed to compress all the buckets to 
               a single number and allow multiple systems on a single   
               graph. While interesting, it takes interpretation to make
               sense of it, especially since it is logarithmic. I think 
               IBM may have done this deliberately because the SMF70Q:  
               variables worked out to exactly 9 using the obvious max  
               bucket value. I fudged the max bucket value when I went  
               to SMF70U: variables to make it come out to 10. The main 
               purpose though is to allow the drill down from a common  
               start to the system details.                             
               Jim's full paper, and report examples are found at:      
                 https://www.mxg.com/downloads/Latent_Demand            
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
Change 38.004  MXG 37.37 ERROR: INVALID VALUE FOR OPTION ENCODING is    
CONFIMXG       due to 1024 in CONFIGMXG should be OPEN_ED-1047.         
Jan 15, 2020                                                            
   Thanks to Jeff.Harder, Indiana Farm Bureau Insurance, USA.           
                                                                        
Change 38.003A FORMAT $MG074OM for dataset TYPE74HO variable R744HOPM   
FORMATS        has new value '50'x='50x:CL5 10 GBIT/S CEE ROCE'         
Jan 15, 2020                                                            
   Thanks to Scott Barry, SBBTechLLC, USA.                              
                                                                        
Change 38.003  IDMSTAS dataset now contains UOW and NETNAME variables:  
VMACIDMS          TASCUOWI='CICS*UOW*ID'                                
Jan 24, 2020      TASCUOWS='CICS*UOW*SEQ'                               
                  TASCNETN='CICS*NETWORK*UOW*ID'                        
              -Variables TASUFLD1-TASUFLD3 are now correctly input for  
               CICS records (IDM6623 corrected IDM6618).                
   Thanks to Scott Barry, SBBTechLLC, USA.                              
   Thanks to Paola Rosero, Centre de services partages du Quebec, CANADA
                                                                        
Change 38.002  Variable BYTEPRC='PCT OF*BYTES*WRITTEN' is added to both 
VMACTMS5       TMS.TMS and variable BESKEY='TAPE*ENCRYPTION*KEY*INDEX   
Feb  7, 2020   is added to TMS.DSNBRECD.                                
   Thanks to Umamaheswara Reddy, JPMCHASE, USA.                         
                                                                        
Change 38.001  BUILDIMS now works correctly with all selection options. 
BUILDIMS       See Change 37.221 for details                            
FORMATS       -Variable LTERM in CIMSTRAN dataset from IMF records can  
VMACCIMS       contain '00'x, which are now translated to blanks.       
VMACIMS       -New variable INPUTCLNR in dataset CIMSTRAN and LASTCLNR  
VMXGINIT       in dataset CIMSPROG are created with the decimal class   
Jan 20, 2020   number.  INPUTCL2 and LASTCLA2 have the HEX values.      
                                                                        
====== CHANGES THRU 37.275 WERE IN MXG 38.01 DATED Jan 20, 2020 ========
                                                                        
Change 37.275  SYNCSORT SMF WRKDVTYP and STWKSDEV device type variables 
FORMATS        values were changed some time in the way past 3350 era,  
Jan  9, 2020   but MXG Format MGSYNDV was not updated until now.        
   Thanks to Randy Hewitt, DXC. USA.                                    
                                                                        
Change 37.274  TYPE1415 Harmless NOTE: DUPLICATE BY VARIABLES, because  
VMAC1415       OPENTIME was repeated in _BTY1415 was supposedly fixed   
Jan  7, 2020   but wasn't until 38.01.                                  
   Thanks to Douglas C. Walter, CITIGROUP, USA.                         
                                                                        
Change 37.273  Using TYPE26J2 incorrectly to read JES 3 records caused  
VMAC26J2       INPUT STATEMENT EXCEEDED. Change 37.026 had added logic  
Jan  7, 2020   to delete those JES3 records when using TYPE26J2/BUILDPDB
               but tested for SUBS=3, when SUBS=5 is the JES3 SUBSYS.   
LASTCHANGE: Version 38.