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

MXG CHANGES 33.33

=========================member=CHANGE33================================
 /* COPYRIGHT (C) 1984-2016 MERRILL CONSULTANTS DALLAS TEXAS USA */     
                                                                        
Annual  MXG Version 33.33  is dated Jan 18, 2016, thru Change 33.327    
First   MXG Version 33.33 was dated Jan 11, 2016, thru Change 33.321    
        MXG Version 33.13 was dated Dec 23, 2015, thru Change 33.311    
First   MXG Version 33.13 was dated Dec 21, 2015, thru Change 33.309    
        MXG Version 33.12 was dated Dec  1, 2015, thru Change 33.286    
First   MXG Version 33.12 was dated Nov 27, 2015, thru Change 33.284    
        MXG Version 33.11 was dated Nov  2, 2015, thru Change 33.260    
        MXG Version 33.10 was dated Oct 20, 2015, thru Change 33.250    
        MXG Version 33.09 was dated Sep 15, 2015, thru Change 33.217    
        MXG Version 33.08 was dated Aug 20, 2015, thru Change 33.195    
First   MXG Version 33.08 was dated Aug 17, 2015, thru Change 33.189    
        MXG Newsletter SIXTY-SIX was dated Aug 17, 2015.                
        MXG Version 33.07 was dated Jul 22, 2015, thru Change 33.172    
First   MXG Version 33.07 was dated Jul 17, 2015, thru Change 33.170    
        MXG Version 33.06 was dated Jun 11, 2015, thru Change 33.141    
        MXG Version 33.05 was dated May 19, 2015, thru Change 33.128    
Second  MXG Version 33.05 was dated May 12, 2015, thru Change 33.124    
First   MXG Version 33.05 was dated May 12, 2015, thru Change 33.123    
        MXG Version 33.04 was dated Apr 29, 2015, thru Change 33.112    
        MXG Version 33.03 was dated Mar 31, 2015, thru Change 33.085    
Second  MXG Version 33.03 was dated Mar 29, 2015, thru Change 33.084    
First   MXG Version 33.03 was dated Mar 27, 2015, thru Change 33.083    
        MXG Version 33.02 was dated Feb 27, 2015, thru Change 33.047    
First   MXG Version 33.01 was dated Feb 20, 2015, thru Change 33.044    
ANNUAL: MXG Version 32.32 was dated Jan  6, 2015, thru Change 32.309    
                                                                        
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 33.33 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 33.33.                  
VI.   Online Documentation of MXG Software.                             
VII.  Changes Log                                                       
                                                                        
  Member NEWSLTRS contains Technical Notes, especially APARs of interest
  and is updated with new notes frequently.  All Newsletters are online 
  at http://www.mxg.com in the "Newsletters" frame.                     
                                                                        
  Member CHANGES contains the changes made in the current MXG version.  
  Member CHANGESS contains all changes that have ever been made to MXG. 
  All MXG changes are also online at http://www.mxg.com, in "Changes".  
                                                                        
========================================================================
                                                                        
                                                                        
I.  MXG Version 33.33 re-dated Jan 18, 2016, thru Change 33.327.        
                                                                        
  Major CHANGES added in MXG 33.33, dated Jan 18, 2016:                 
                                                                        
  TYPE110  33.326  MXG 32.10-First MXG 33.33. Increased CPU in SMF 110s 
                   from 300 to 500 seconds for 22GB SMF 110s, corrected.
  TYPEVMXA 33.327  Data set VMBYUSR missing many observations.          
  VMXGALOC 33.325  Correction for WEEK1 allocation.                     
  TYPEXAM  33.324  zVPS variable CALENTMT changed from numeric, conflict
                                                                        
  Major CHANGES added in MXG 33.33, dated Jan 11, 2016:                 
                                                                        
  TYPEXAM  33.320  Support for zVPS z13 SMT mode new variables.         
  TYPE70EC 33.318  Data Set SORT70EC NOT SORTED, configuration changed. 
  TYPE42   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE64   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE71   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE74   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE99   33.308  New variables compatibly added by z/OS 2.2.          
  SMFSRCH  33.307  Support for multiple text strings in LOOKFOR=.       
  ASUMCELP 33.306  Variables SMF70GNM, SMF70GMU, SMF70WLA added.        
  ANALACTM 33.312  Correction for more than one service policy.         
                                                                        
  Major CHANGES added in MXG 33.13, dated Dec 23, 2015:                 
                                                                        
  UTILBLDP 33.311  Execution stops if BUILDPDB=YES, with &SPINUOW error.
                                                                        
  Major CHANGES added in First MXG 33.13, dated Dec 21, 2015:           
                                                                        
Critical Change for ITRM USERS (MXG 33.12+):                            
  ITRM     33.301  ITRM users MUST add %LET EPDBOUT= _SDB2SBP;          
                   inserted between %CMPROCES... and %CPSTART....       
                   ERROR: File WORK.SUMSTSBP.DATA does not exist.       
Critical Change for z/OS 2.2 MXGTMNT/TAPE MOUNT MONITOR:                
  ASMTAPEE 33.207  ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.     
                   IBM changes cause ABEND S0E0-28, must reassemble.    
New Products Support                                                    
  TYPEIMS  33.298  Support for IMS 14.1 log records (COMPATIBLE)        
  TYPE74   33.305  z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC,
                   (new Storage Class Memory data).                     
  TYPE78   33.305  z/OS 2.2 new variables in TYPE78PA.                  
  TYPEVMXA 33.299  Support for zVM 6.3 MONWRITE z13 SMT MODE.           
Errors Corrected:                                                       
  TYPEDB2  33.303  Multiple DB2 100 Subtype 1 created multiple DB2STATS.
  TYPE102  33.294  SMF 102 IFCIDs 81E5-8160,8051x INPUT EXCEEDED DRROR  
Enhancements                                                            
  ANALIDDY 33.290  ANALIDDY tabulates ANALID SMF data by date, used to  
                   investigate SMF dumping problems.                    
                                                                        
                                                                        
  Major CHANGES added in MXG 33.12, dated Dec  1, 2015:                 
                                                                        
Reason for this new version:                                            
  TYPE7072 33.280  PDB.TYPE70 z13 SMT mode ZIPCPUS value may be wrong.  
New Products Support:                                                   
  TYPEDB2  33.279  Support for DB2 Simulated Buffer Pool PDB.DB2STSBP.  
  MOBWRK02 33.279  Support for DB2 Simulated Buffer Pool dataset.       
  TYPE102  33.264  Support for APPTUNE 11.2 INCOMPATIBLE change in 8005.
  TYPE119  33.262  Support for SMF 119 subtypes 2, 5, 6, 7, 41-44, 97.  
Errors corrected:                                                       
  TYPE102  33.273  DB2 SMF 102 IFCID=109 INVALID DO LOOP CONTROL ERROR. 
  TYPE1415 33.270  Variable SMF14ALIAS misspelled so it was not kept.   
  TYPE120  33.267  SMF 120 dataset TYP120JI only output first instance. 
  TYPEXAM  33.266  MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND.      
  TYPETPMX 33.265  ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong.     
Enhancements:                                                           
  JCLASMXG 33.275  Assemble/Link Edit all five MXG ASM programs install.
  ASMRMFV  33.274  ASMRMFV Updates.                                     
  MXGLOG   33.162  MXGLOG write enabled by //MXGLOG or FILENAME MXGLOG, 
                   automatically.                                       
                                                                        
                                                                        
  Major CHANGES added in MXG 33.11, dated Nov  2, 2015:                 
                                                                        
Reason for this new version:                                            
  TYPE110  33.257  CICS/TS 5.3 BETA CICSTRAN new field added INCOMPAT   
         This should be the last REQUIRED MXG update for CICS/TS 5.3.   
New Products Support:                                                   
  TYPEXAM  33.259  Support for zVPS Release 4230 for z13 SMT mode.      
Enhancements:                                                           
  TYPEIMST 33.252  Variable SYSTEM can be added to TYPE56FA with SYSPARM
                                                                        
                                                                        
  Major CHANGES added in MXG 33.10, dated Oct 20, 2015:                 
                                                                        
New Products Support:                                                   
  TYPE121  33.231  Support for JZOS Java Runtime Performance SMF 121.   
  TYPEATF  33.245  Support for OMEGAMON ATF IMS Log Record LCODE A2.    
  TYPE6    33.233  Support for APAR OA46136 adds IPADDR in PSF SMF 6.   
  TYPEVMXA 33.242  Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode.  
  TYPERACF 33.238  Support for RACF IRRDBU00 Record Type 1560.          
  TYPEEDA  33.237  Support for EDA V7706 (INCOMPATIBLE, data inserted). 
  TYPETPMX 33.232  Support for Thruput Manager VARNAME=$ORIGIO.         
  TYPEDOS  33.248  Support for zVSE/Power Version 9 Release 2 accounting
Enhancements:                                                           
  ANALCAPD 33.225  Major revision to analysis of Capping, now by LPAR.  
  ASMRMFV  33.222  RMF III DVT Character data Filtering saves DASD.     
  ANAL2642 33.230  Example to select TYPE26 and match with TYPE42.      
  ANAL1430 33.230  Example to select TYPE14 and match with TYPE30.      
  VMACUCB  33.245  DEVCLASS=41 decode identifies specific CTC type.     
  TYPE80A  33.243  RACF Type 80 record "subtypes" (RACFEVNT) for ANALID.
  IMAC30IO 33.240  EXCPxxxx and IOTMxxxx can be dropped for nonexistent.
  TYPE7072 33.239  New _KTY70DR to drop variables from TYPE70 dataset.  
  TYPE102  33.236  All DB2 zPARM QWP4xxxx fields are now correct.       
  TYPE42   33.230  Summed vars S42READS,S42WRITES added to TYPE42DS.    
Error Corrections:                                                      
  TYPE74   33.234  TYPE74HO false duplicates were being removed.        
  TYPENDM  33.229  NDM PT records INPUT EXCEEDED, INCOMPAT inserts.     
  TYPE22   33.227  Dataset TYPE22PB RECONFIG PCIE had zero observations.
  TYPE74   33.228  SMF 74 St 9 z/OS 2.1 z/13 INPUT STATEMENT EXCEEDED.  
  TYPE103  33.223  Short SMF 103 Subtype 13 INPUT EXCEEDED error.       
  TYPE102  33.250  SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED.           
                                                                        
                                                                        
  Major CORRECTIONS added in MXG 33.09, dated Sep 15, 2015:             
                                                                        
  ASMTAPEE 33.207  ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.     
                   IBM changes cause ABEND S0E0-28, must reassemble.    
  TYPE7072 33.217  z13, SMT Mode, error: LPARCPUS=0 in PDB.TYPE70PR.    
  TYPE110  33.198  CICS/TS 5.3 BETA, MNSEGCL=5, INPUT STATEMENT EXCEEDED
                   IBM inserted new data. Datasets CICSRDS/RDFI/RDQU.   
  TYPETMO2 33.210  More TMON/CICS Version 3 and Version 4 corrections.  
                   MONITASK in V3.3 fixed, MONISYST in V3.3 and 4.0.    
                   ASG APAR corrects two obscure fields in 4.0.         
  TYPE7072 33.216  Support for APAR OA47042 WLM MOBILE Resources in RMF.
  TYPECDC  33.201  Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2 
  TYPEAXWY 33.199  Support for AXWAY SMF record, INCOMPATIBLE, inserts. 
  TYPE120  33.213  Support for WASODM Operational Decision Manager 8.7. 
  TYPEMGCR 33.212  Support for MEGACRYPTION Version 6, INCOMPATIBLE.    
  TYPE30   33.206  z/OS 2.2 Job Correlation SMF30COR input/kept.        
  BUILDPDB 33.204  Variable IOTMNODD was never calculated in PDB.JOBS.  
  TYPEXAM  33.202  Velocity ZVPS 5.4 XAMSYT had zero observations.      
  TYPE113  33.197  Variable LPBUSY created in ASUM113 like TYPE113.     
  TYPEDB2  33.205  DB2ACCTP variables QPACPKID/LOCN/ may be truncated.  
  TYPEBVIR 33.196  TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected.     
  TYPE70   33.200  TYPE70xx datasets now have VARYed interval data kept.
                                                                        
                                                                        
  Major CORRECTIONS added in MXG 33.08, dated Aug 20, 2015:             
                                                                        
CRITICAL, REQUIRED CHANGES (that caused redate/refresh of 33.08):       
  TYPETMO2 33.195  TMON/CICS Version 4 was still wrong in 1st 33.08.    
                                                                        
                                                                        
  Major enhancements added in FIRST MXG 33.08, dated Aug 18, 2015:      
                                                                        
CRITICAL, REQUIRED CHANGES:                                             
  TYPE7072 33.186  z13 INCOMPATIBLE ERROR, SMT-MODE, if VARY CP online. 
                   The VARY put the new CP after the IIPs which broke   
                   MXG logic so the new engine was not seen, causing the
                   CPU metrics to be wrong for all intervals after the  
                   VARY, requiring redesign of the MXG SMT logic.       
  TYPETMO2 33.188  TMON/CICS Version 4.0, REQUIRED, MXG coding error.   
  TYPESYNC 33.184  Support for SYNCSORT Release 1.4 (INCOMPAIBLE).      
NEW SUPPORT ITEMS:                                                      
  TYPExxxx 33.189  Support for z/OS 2.2 COMPATIBLE, but many additions. 
  TYPEMAR  33.183  Support for MAR Hitachi Command Suite Mainframe      
  VMAC115  33.180  Support for MQ Version 8 subtype 215 record          
  TYPEBBMQ 33.175  New IHDRBBMQ "Infile Header Exit" for selection.     
  ASMRMFV  33.182  New filters for RMF III ASI Filtering reading RMFVSAM
CORRECTIONS:                                                            
  TYPE74   33.185  zEDC TYPE749 zero divide fixed, R749DFMT formatted.  
  TYPE70PR 33.174  IFL Processor count corrected to number in LPAR.     
  TYPE7072 33.179  TYPE70EN z13 SMT Mode, blank LPARNAME, SMF70MTTT fix.
  TYPE113  33.173  z13 SM1132SP incorrectly forced, should be 5000 MHz. 
OTHER ENHANCEMENTS:                                                     
  TYPE102  33.187  Dataset T102S106 zPARM variables added.              
  TYPE30   33.185  zEDC variables labels now INFLATE/DEFLATE.           
  RMFINTRV 33.181  Enhancement to ADD variables to be kept in RMFINTRV. 
  JCLPDB9  33.178  JCL Example for BUILDPDB, ANALxxxx members revised.  
                                                                        
                                                                        
  Major enhancements added in MXG 33.07, dated Jul 20, 2015:            
                                                                        
  TYPE120  33.171  Many SMF 120 ST 9 UNEXPECTED MULTIPLE SEGMENT on log 
                                                                        
                                                                        
  Major enhancements added in MXG 33.07, dated Jul 17, 2015:            
                                                                        
  TYPE74   33.155  TYPE74ST now has SCM variables, TYPE74MO is no more. 
  TYPE78   33.156  Support for APAR OA44525, zHPF Extended Distance II. 
  TYPE115  33.151  Support for MQ V8.0 MQCHIN, ERROR.VMAC115.OFFQCCT.   
  TYPE116  33.151  Support for MQ V8.0 MQCHININ, ERROR.VMAC116.LENQWHS. 
  TYPE119  33.144  Support for Type 119 new subtypes 94 and 95.         
  TYPECZA  33.166  Support for Correlog z/OS Agent User SMF record.     
  MXGLOGDO 33.162  "MXGLOG" option to send MXG Messages to MXGLOG.      
  TYPE22   33.146  New TYPE22PB dataset created for Reconfigured PCIE.  
  SMFSRCH  33.159  Support for compressed SMF in SMFSRCH LOOKFOR        
  ANALID   33.159  Support for compressed SMF for DB2 Version/Subtype.  
  ANALQBAT 33.147  Analysis of Batch Queue Times SMF30HQT/JQT/RQT/SQT.  
  TYPEXAM  33.157  zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected.       
  TYPEBVIR 33.145  BVIR VTS Grid dataset BVIR33 wrong for second plus.  
  TYPENDM  33.143  INPUT STATEMENT EXCEEDED NDM-CDI PT record.          
  IMAC6ESS 33.158  Type 6 ESS zero len segment INPUT STATEMENT EXCEEDED.
                                                                        
                                                                        
  Major enhancements added in MXG 33.06, dated Jun 11, 2015:            
                                                                        
  TYPERMFV 33.140  RMF III RCD records INCOMPATIBLY CHANGED for z13.    
                                                                        
  TYPE7072 33.138  z13 in SMT Mode zIIP variables in TYPE70xx datasets, 
                   especially TYPE70EN, could be missing, or DUPLICATE  
                   RECORD message could be printed.  REQUIRED FOR SMT.  
                   The MXG SMT support has come in several iterations as
                   new sequences of data exposed untested logic but this
                   appears to finally resolve the one-to-many merge.    
                   If you testing SMT on z13, please email MXG Support  
                   with subject: SMT UPDATES so we can inform you if    
                   there are any further required changes for SMT mode. 
                   Aug 17, 2015: MXG 33.08 is NOW required for SMT mode.
                   See Change 33.186.                                   
  TYPE30   33.132  Support for zEDC metrics in TYPE30 is now correct.   
  ANAL9914 33.139  z13 Processor Topology Report from SMF TYPE9914 data.
  SMFSRCH  33.131  SMFSRCH enhancements, ANALID, LOOKFOR list, AND/OR.  
  TYPEAA   33.137  Support for Compuware ABEND-AID USER SMF Record.     
  TYPECIMS 33.136  Support for MainView for IMS 5.2 (a/k/a IMF).        
  TYPEOSEM 33.133  ZOSEM User SMF - INPUT STATEMENT EXCEEDED error.     
  TYPETMS5 33.129  Support for TMS new TRTCH values for TS1140.         
  ASUM113  33.130  Missing values in SMF70xx merged into PDB.ASUM113.   
  ANALDB2R 33.134  Number reports mis-reported,ANALID added, headings.  
                                                                        
                                                                        
  Major enhancements added in MXG 33.05, dated May 19, 2015:            
                                                                        
  Sites with z13 in SMT-mode or sites with zEDC need this refresh:      
                                                                        
  TYPE7072 33.128  Zero OBS in TYPE70 for non-SMT if SMT SMF read first 
  TYPE74   33.127  zEDC TYPE749 dataset was finally revised correctly.  
     Aug 17,2015 added: MXG 33.08 required for SMT mode.                
                                                                        
                                                                        
  Major enhancements added in MXG 33.05, dated May 12, 2015:            
                                                                        
  TYPE7072 33.121  z13 SMT-mode TYPE70/TYPE70PR data is WRONG 33.03-04. 
                   ONLY SMT-mode type 70 records were wrong.            
  TYPETANZ 33.123  Support for Tandem ZMS Style records.                
  TYPEZCOS 33.116  Support for ZCOST AutoSoftCapping Version V3.0.00    
  SMFSRCH  33.117  SMFSRCH corrections, TYPE30_D now populated.         
  TYPEBBMQ 33.115  Mainview for Mq BBMQBUFF variables corrected.        
  TYPECIMS 33.114  IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN. 
  TYPE102  33.113  Some T102S106 DB2 zPARM values were misaligned/wrong.
  TYPE120  33.120  New IHDR120 header exit created for TYPE120 tailoring
  IMACICMX 33.119  The optional IMACICMX for length=384 had missing END.
                                                                        
                                                                        
  Major enhancements added in MXG 33.04, dated Apr 29, 2015:            
                                                                        
  TYPE110  33.112  Support for CICS/TS 5.3 OPEN BETA (INCOMPATIBLE).    
                   Note: IBM Changed CICS 5.3 Default to STGPROT=YES    
                   Note: MXG 33.08-plus is required.  Change 33.192.    
  TYPETMO2 33.099  TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG.     
  TYPEBBMQ 33.090  Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT)      
  TYPE42   33.108  Support for APARs OA45944,OA45897 new SMF 42 metrics.
  TYPE74   33.087  Support for RMF 74 Subtype 9 zEDC Accelerator.       
  TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE).     
  TYPEQACS 33.101  Support for iSeries 7.2 (COMPATIBLE, new LRECLs).    
  TYPEXAM  33.086  Support for Velocity Software zVPS XAM Version 5.4.  
  TYPENMON 33.104  Support for NMON CPUnr with three digits.            
  TYPE110  33.106  CICSEXCE variable EXCMTYPE decodes Exception type.   
  UTILCVRT 33.105  Alternate table needed for no TRANSCODE PROC CPORT.  
  ASMRMFV  33.100  Protect invalid ASI table index in UWD, 0C4 ABEND.   
  TYPE7072 33.096  z13 with SMT PROCVIEW=CORE, SMT-NUM not kept.        
  TYPENMON 33.092  Some NMON BBBPnnnn variables were mis-assigned.      
                                                                        
                                                                        
  Major enhancements added in MXG 33.03, dated Mar 29, 2015:            
                                                                        
  TYPE7072 33.071  FULL z13 SUPPORT. MXG 33.03 IS REQUIRED FOR SMT MODE,
                   i.e., for PROCVIEW CORE.  FOR non-SMT, PROCVIEW CPU, 
                   the many changes were COMPATIBLY made.               
      Aug 17,2015: See Change 33.186, MXG 33.08 IS NOW REQUIRED FOR SMT.
                                                                        
               For SMT PROCVIEW CORE Mode, MXG Change 33.046 in 33.02   
               updated the TYPE70 dataset, but this Change 33.071 in MXG
               33.03 is required to update the new SMT metrics correctly
               in the TYPE70PR dataset, to get the CPUID, LCPUADDR, and 
               CORE_ID from the four segments that don't have the same  
               number of segments: OFFCPUD and SMF70COS have 20 for the 
               6 online CPs, 4 offline CPs, and 5 zIIPs with CPU_NUM=2, 
               while SMF70BDN/LPARCPUX has only 18 segments (with the   
               CORE_NUM needed to look-up the LCPUADDR), and there are  
               only 14 Core_ID values.                                  
                                                                        
               This was a complex update to a CRITICAL MXG MEMBER, with 
               500+ lines of code inserted lines into the 27,000 lines. 
               The SMT Mode data has been validated with RMF records,   
               with a wide range of LPAR configurations.  When in SMT   
               mode, please examine the new data carefully and contact  
               support@mxg.com if you have questions.                   
                                                                        
               Note: If you read the changed SMT mode RMF 70s with an   
               old MXG, RMFINTRV may have NEGATIVE CPUOVHTM values and  
               the %PCTCPUBY values may be over 100%.                   
  TYPE99   33.053  Support for z13 updates to type 99 subtype 14.       
  TYPE113  33.052  z13 Support for HIS SMF 113, many new equations.     
  UTILEXCL 33.049  New reports, trans without dictionary, READTIME.     
  VMXGINIT 33.062  %LET MXGDEBUG=FULL; shows OPTIONS, enables diags.    
  TYPEDOL  33.060  DCOLLECT Cluster/Multi-VOL now have Class variables. 
  TYPE102  33.067  DB2 Trace IFCID=220 misaligned, ILLEGAL ARGUMENT.    
  TYPE105  33.061  GDPS SMF 105 INPUT STATEMENT EXCEED if no XVMX seg.  
  ANALDB2R 33.069  SAS 9.3 does not have dictionary for DESTINATIONS.   
  TYPEDB2  33.068  Variable Q8STCCPU not kept after Change 30.133.      
  TYPETHAO 33.059  Support for Thales Security Resource Mgr RF1100.     
  FTPING   33.056  OPTIONS OBS=0 fails read with ftp access method.     
  ANALHSM  33.050  Graphics part had a NOT SORTED condition.            
  TYPETPMX 33.070  TOKENID INCLAI, three $LIST_L and $RESTAR added.     
  Many     33.078  All %MACROs from SASAUTOS are replaced by %SYSFUNC() 
                                                                        
                                                                        
  Major enhancement added in MXG 33.02, dated Feb 27, 2015:             
                                                                        
  Many     33.046  Support z/OS on z13 RMF/SMF APARs for z/OS 2.1+      
                                                                        
           MXG 33.01 CHANGES noted one z13 site had NEGATIVE CPUOVHTM,  
           but that was ONLY IF z/OS on z13 is in MULTI-THREADING MODE. 
           MXG was unaware of IBM's restructuring the RMF type 70 SMF   
           record's calculation of CPU BUSY time for the new MT mode,   
           but this MAJOR CHANGE restructured TYPE70 processing in MXG  
           to order by CORE_ID and CPU_NUM rather than CPUID/LCPUADDR.  
           If you have ANY non-MXG programs that read RMF 70s to get the
           CPU BUSY time, they MUST BE REWRITTEN for MT Mode records.   
                                                                        
           A Technical Newsletter note on Multi_Threading is planned;   
           this original note then stated an initial opinion of mine:   
           "although relatively few sites have workloads that will be   
           able to exploit that architecture, which can increase thruput
           but elongate individual tasks elapsed time", but I've changed
           my opinion about "relatively few sites":  ANY SITE with zIIPs
           or IFLs are VERY LIKELY to find SMT to be a benefit.         
                                                                        
                                                                        
  Major enhancement added in MXG 33.01, dated Feb 23, 2015:             
                                                                        
  Many     33.023  Support z/OS on z13 RMF/SMF APARs (z/OS: COMPATIBLE) 
   However: One site's z13 stress test shows TYPE70 CPU time MUCH LESS  
            than TYPE72 Service Class CPU time (which matches 30s) for  
            many intervals, but valid data before and after the test,   
            causing NEGATIVE CPUOVHTM messages on the log and RMFINTRV  
            observations will have negative CPUOVHTM (uncaptured CPU).  
            NOTE: THIS ERROR WAS CORRECTED IN MXG 33.02, SEE ABOVE NOTE.
                                                                        
  TYPEVMXA 33.016  Support for zVM 6.3 on z13 (INCOMPATIBLE).           
  TYPEMWLX 33.037  Support for HP MeasureWare for Linux -               
  VMAC30   33.005  Support for APAR OA45767 adds zEDC statistics.       
  TYPEBBMQ 33.030  Support for BMC Mainview for MQ 5.2 (REQUIRED)       
  TYPENTMU 33.028  Support for EDS User SMF Record from NETMENU program.
  TYPEXPTR 33.040  Support for SystemWare XPTR 5.2 subtype 140, ex-st-40
  SMFSRCH  33.041  SMFSRCH redesigned to read the SMFOUT with UTILBLDP. 
  ASUM70PR 33.032  New SMF70WTI/WTS/WTU added to ASUM70LP/ASUMCELP      
  MOBWRKSU 33.039  Summarization of Mobile Work CSV file combines split.
  TYPEDB2  33.025  QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB. 
  RMFINTRV 33.024  ANY work in service class SYSOTHER, new log messages.
  ASMRMFV  33.021  ASMRMFV skips RCD if no Reporting Classes defined.   
  TYPEQACS 33.020  iSeries change in record length can force USER ABEND.
  TYPE60   33.038  Type 60 with no VVR INPUT STATEMENT EXCEEDED again.  
  TYPE80A  33.036  RACF SMF 80 record, TOKxxxxx fields increased length 
  TYPEIMS  33.034  Variables SYSABEND,USRABEND decoded in IMS56FA.      
  TYPEVMXA 33.043  zVM VXUSEACT/VXUSEINT NOT SORTED ERROR.              
  UTILBLDP 33.042  Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found
                                                                        
                                                                        
    Please read CHANGESS for the complete list of major enhancements.   
                                                                        
  See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
  current MXG Technical Notes.                                          
                                                                        
                                                                        
  All of these enhancements are described in the Change Log, below.     
                                                                        
II.   SAS Version requirement information:                              
                                                                        
   SAS Versions                                                         
     The current version nomenclature is SAS 9.4 TS1M3 (9.4M3) printed  
     as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for     
     "SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled),      
     for SAS 9.4 Maintenance Level M3 and m2.                           
                                                                        
     SAS V9.4 M3 Is RECOMMENDED, but MXG executes without error using   
     SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.   
                                                                        
     SAS V9.4 M2 Is RECOMMENDED. SAS 9.4 M2 is at LEVEL A SAS Support   
     SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support    
     SAS V9.3   SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works.     
                But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
                see CHANGE 29.169, IS REQUIRED:                         
                  The %MACRO compiler error is in processing %LET       
                  statements. While only two MXG members failed         
                  repeatedly in MXG QA tests on z/OS, there were random 
                  %LET errors in ASCII QA tests, so ANY use of %LET     
                  statement on ANY platform are vulnerable to this      
                  error, as the %MACRO compiler is SAS portable code,   
                  used on all platforms.  So this is NOT just an MXG    
                  error, but impacts ALL SAS programs.                  
                SAS9.3 is LEVEL A support from SAS.                     
     SAS V9.2   Was recommended, prior to 9.3, and was error-free with  
                MXG 26.03. SAS Hot Fix for SAS Note 37166 is required to
                use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2      
                Decompression Infile Exit, but SAS V9.2 does execute ok.
                9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.    
     SAS V9.1.3 must be at Service Pack 4.  Additionally, on z/OS 1.10  
                only, 9.1.3 requires SAS Hot Fix for SN-35332.          
                9.1.3 is support level C by SAS Institute, Sep 30, 2013.
                SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.    
     SAS V8.2 IS SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS 
                with SAS 8.2.                                           
                SAS 8.2 is Level C Support from SAS as of Dec 31, 2011. 
                                                                        
      JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used  
                                                                        
      ***************************************************************   
      As documented in Change 27.356, for SAS V9.2 or later):           
      The standard SAS JCL Procedure can be used for MXG with SAS V9.2+ 
           // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                  
           //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR     
      or you can continue to use the MXGSAS93 JCL Procedure example.    
      ***************************************************************   
                                                                        
      MXG 26.03 thru MXG 33.03 will execute under the previously listed 
      SAS Versions on all supported platforms                           
                                                                        
      Unrelated to the above SAS Note/Hot Fix, ODS users will want to   
      use MXG 29.06+, because SAS V9.3 did expose incompatibilities in  
      MXG code for ODS reporting, that were fixed in MXG Version 29.06. 
      See Changes 29.159 and 29.169.                                    
                                                                        
                                                                        
      And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,  
      the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe). 
        Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors  
        can occur even though //XXXXXXXX DD is a valid SAS Data Library.
        This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does   
        NOT occur with SAS V9.2, nor with z/OS 1.9.  It can be          
        circumvented by adding a LIBNAME statement that specifies the   
        ENGINE name. See the Technical Note in Newsletters for SN-35332.
        Note that SAS V9.1.3 is now at "Level B" Support from SAS.      
                                                                        
      Old MXG code may continue to execute with SAS V8.2, but V8 is now 
      "Level C" support from SAS Institute, and there are known errors  
      in V8.2 that are only fixed in SAS V9.  I no longer QA with V8.2; 
      While many MXG programs (accidentally) will still execute under   
      V8.2, I cannot guarantee that all of MXG executes error free.     
      PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!           
         If you are absolutely stuck on V8, you need to copy MXG member 
         V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.           
                                                                        
      MXG Software has not executed under SAS V6 in many years.         
                                                                        
      The "PDB" libraries (i.e., SAS data libraries) must be created by 
      SAS V8 or later, but any of those data libraries can be read or   
      updated by the SAS Versions that MXG Supports, above.             
                                                                        
                                                                        
      For SAS Version V9.3:                                             
        SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note 
        SN43828 is REQUIRED.  See text of Change 29.159.                
        With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions    
        26.03 or later execute under SAS V9.3 on all platforms.         
                                                                        
        SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and  
        SAS V9.4 are interchangeable and can be read/written by any of  
        those versions, provided they are on the same platform.         
          BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the 
          same "platform" and attempting to read/use the FORMAT catalog 
          created on one of those "platforms" on the other "platform"   
          will error out to remind you of that difference!              
        SAS V9.4 did change some V9.3 ODS processing defaults and syntax
        that might cause errors with MXG 29.05 or earlier; MXG 29.06,   
        Change 29.160 documents the major revisions made in MXG to fully
        support ODS, and MXG 29.06 is STRONGLY recommended for ODS with 
        SAS V9.3 or SAS V9.4.                                           
                                                                        
      For (Archaic) SAS Version V9.2 (TS1M0):                           
                                                                        
        Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.  
                                                                        
        On z/OS, SAS changed the DSNAMES for some of the SAS libraries, 
        so you do need to use the new MXGSAS92 JCL Procedure for MXG,   
        but it still uses the CONFIGV9 configuration file.              
                                                                        
        ****************************************************************
        However, NEW, and documented in Change 27.356, with SAS V9.2+:  
          The standard SAS JCL Procedure can be used for MXG:           
             // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'                
             //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR   
          instead of using the MXGSAS92 JCL Procedure example.          
        ****************************************************************
                                                                        
        SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3, 
        and V9.4. "PDBs" can be read/written interchangeably between    
        these SAS versions.                                             
                                                                        
        MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS   
        and with NO ERRORS reported.                                    
          Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a  
          new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
          code). That warning is harmless (to MXG code) and all MXG     
          created SAS datasets were correct, even with that warning.    
          The ONLY exposure was ONLY on z/OS, and ONLY if condition code
          tests are used in your MXG jobstreams.                        
                                                                        
        SAS Version 9.2 requires z/OS 1.7 or later, both officially as  
        documented by SAS Institute, and actually as V9.2 fails with 0C4
        under z/OS 1.4.                                                 
                                                                        
      For SAS V9.1.3 on z/OS with Service Pack 4:                       
                                                                        
        On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.                     
                                                                        
        CONFIGV9 now specifies V9SEQ instead of V6SEQ.  As V6SEQ does   
        not support long length character variables, it can't be used.  
                                                                        
       SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.  
                                                                        
       For (back-level!) SAS V9.1 or V9.1.2 on z/OS:                    
        SN-013514 is REQUIRED to be able to read datasets that were     
          created by V6SEQ (tape) engine.                               
        SN-012437 is REQUIRED to prevent creation of corrupt/unreadable 
          datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.            
        Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT 
          SAFE without those two hot fixes, and if you do NOT have those
          two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.    
                                                                        
        With MXG 23.02 or later, V9SEQ is the default sequential engine 
        specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
        you MUST install the two hot fixes listed above.                
                                                                        
       For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
         as an absolute minimum level when that SAS Version was last    
         supported by MXG Software.  PLEASE INSTALL SAS V9.x ASAP.      
                                                                        
       Sequential Engine Status:                                        
          V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.   
          V8SEQ was always safe under SAS V8.2, but it wasted CPU time  
            by always compressing when writing in tape format.          
          V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ    
                 should no longer be used, as it does not support long  
                 length variables.                                      
                                                                        
      GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:              
                                                                        
      MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and
      Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,   
      but MXG users execute MXG on MANY (ALL??) SAS platforms, including
      AIX, Linux, and other 'nix' variants, on many different hardware  
      platforms, and since they all work we don't need to list them.  If
      SAS executes so does MXG.                                         
                                                                        
      Prior QA tests have been run with all SAS releases available at   
      that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880, 
      and on HP-UX v11.11 model rp5470, confirming full compatibility.  
                                                                        
      MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS  
      platform without errors! Each new MXG version is also tested with 
      the SAS ITSV/ITRM product by the ITRM developers.                 
                                                                        
                                                                        
III.  WPS Version requirement information:                              
                                                                        
      WPS Version 3.1.1 maintenance level 731 required for PDB to tape  
      WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.     
      WPS Version 3.01  is required for MOBILWRK, PICTURE fails in 2.5. 
      WPS Version 3.01  executed MXG 32.03 BUILDPDB with no errors.     
      WPS Version 3.0   requires MXG 31.09 (see Change 31.251).         
      WPS Version 2.4   required MXG 27.09 (see Change 27.239).         
      WPS Version 2.3.5 required MXG 27.05.                             
                                                                        
      See NEWSLETTERS for WPS Support Statement.                        
                                                                        
      WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID" 
      when the LIBNAME PDB does not exist; there would also have been a 
      prior log message  NOTE: Library PDB does not exist   as the clue.
                                                                        
                                                                        
IV.   MXG Version Required for Hardware, Operating System Release, etc. 
                                                                        
   MXG is usually NOT sensitive to z/OS Hardware changes, but:          
                                                                        
     The z/EC12 with 85+ engines required MXG 30.07.                    
     Support for 255 engines was added in MXG 31.04.                    
     The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.        
                                                                        
   However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was  
   INCOMPATIBLY CHANGED, and MXG 33.09 is REQUIRED (PCTCPUBY WRONG!), to
   read the SMT-format RMF records (which are written if you have zIIP  
   engines AND have 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.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        
      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        
      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 OPEN BETA            Sep 31, 2015        33.08        
      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.??        
      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        
      DFSMS/MVS 1.1                    Mar 13, 1993        11.11        
      DFSMS/MVS 1.2                    Jun 24, 1994        12.02        
      DFSMS/MVS 1.3                    Dec 29, 1995        13.09        
      DFSMS/MVS 1.4                    Sep 28, 1997        15.04        
      DFSMS/MVS 1.4 HSM                Sep 23, 1998        16.04        
      DFSMS/MVS 1.5                    ??? ??, 1999        16.04        
      DFSORT SMF V1R5                  Mar  1, 2006        24.02        
      MQM 1.1.2, 1.1.3, 1.1.4          Apr 25, 1996        14.02        
      MQ Series 1.2.0                  May 26, 1998        16.02        
      MQ Series 2.1.0                  Oct  2, 1999        17.07        
      MQ Series 5.2                    Dec 16, 2000        18.10        
      MQ Series 5.3                    Dec 16, 2002        21.05        
      MQ Series 6.0                    Feb 14, 2006        23.23        
      Websphere MQ Series 7.0          ??? ??, 2009       *28.06        
      Websphere MQ Series 7.1          MAR 12, 2011        29.03        
      Websphere MQ Series 8.0          Jun 24, 2011        29.05        
      NETVIEW 3.1 type 37              ??? ??, 1996        14.03        
      NPM 2.0                          Dec 17, 1993        12.03        
      NPM 2.2                          Aug 29, 1994        12.05        
      NPM 2.3                          ??? ??, 1996        15.08        
      NPM 2.4                          Nov 18, 1998        17.01        
      NPM 2.5                          Feb ??, 2000        18.02        
      NPM 2.6                          Nov ??, 2001        19.06        
      RMDS 2.1, 2.2                    Dec 12, 1995        12.12        
      RMDS 2.3                         Jan 31, 2002        19.11        
      TCP/IP 3.1                       Jun 12, 1995        12.12        
      TCP/IP 3.4                       Sep 22, 1998        16.04        
      WebSphere 5.0 APAR PQ7463        Aug 19, 2003        21.04        
      WebSphere 6.0                    Feb 18, 2006        23.23        
      WebSphere 7.0                    Oct  7, 2010        28.06        
      WebSphere 8.0                    Jul 17, 2011        29.05        
      DOS/VSE POWER V6.3.0             Dec 19, 1998        16.08        
      VM/ESA  2.0                      Dec 23, 1992        10.04        
      VM/ESA  2.1                      Jun 27, 1993        12.02        
      VM/ESA  2.2                      Nov 22, 1994        12.06        
      VM/ESA  2.3                      Jun  1, 1998        16.08        
      VM/ESA  2.4                      Mar  1, 2001        19.03        
      z/VM    3.1                      Mar  1, 2001        19.03        
      z/VM    3.1 DATABYTE=0           May  2, 2002        20.02        
      z/VM    4.2 ??                   May  2, 2002        20.02        
      z/VM    4.4                      Jan 22, 2005        22.22        
      z/VM    5.1                      Jan 22, 2005        22.22        
      z/VM    5.2                      Jan 22, 2006        24.01        
      z/VM    5.3 TOLERATE             Jun  7, 2007        25.05        
      z/VM    5.3 NEW VARIABLES        Sep 12, 2008        26.08        
      z/VM    5.4 (COMPATIBLE)         Sep 12, 2008       *27.01        
      z/VM    6.1 (NO CHANGES)         Jul  7, 2008        27.01        
      z/VM    6.2                      Dec  2, 2011        29.04        
      z/VM    6.3 INCOMPATIBLE         Jul 23, 2013        31.05        
      IMS log 4.1                      Jul  4, 1994        12.02        
      IMS log 5.1                      Jun  9, 1996        14.05        
      IMS log 6.1                      ???  ?, 199?        20.03        
      IMS log 7.1                      ???  ?, 200?        20.03        
      IMS log 8.1                      May 21, 2003        21.02        
      IMS log 9.1                      Mar 96, 2004       *26.01        
      IMS log 10.1                     Mar 06, 2007       *26.01        
      IMS log 11.1                     Apr  1, 2010       *28.02        
      IMS log 12.1                     Jan 23, 2012       *29.29        
      IMS log 13.1 (NOT 56FA)          May 25, 2013        31.03        
      IMS log 13.1 (56FA RECORD)       May 27, 2014        32.05        
      IMS log 14.1 COMPATIBLE          Dec 19, 2015        33.13        
      AS400 3.7.0                      Nov  1, 1996        15.01        
      AS400 4.1.0                      Dec 30, 1996        15.08        
      AS400 4.2.0                      Apr 27, 1998        16.02        
      AS400 4.4.0                      Sep 27, 1999        17.07        
      AS400 4.5.0                      Jul 27, 2000        18.07        
      AS400 5.2.0 - Most records       Jul 23, 2003        21.03        
      AS400 5.2.0 - QAPMMIOP           Jul 23, 2003        22.04        
      AS400 5.3.0                      Jan 22, 2005        22.22        
      AS400 5.4.0                      Aug 26, 2006        24.06        
      AS400 6.1.0                      Jun 29, 2008        26.05        
                                                                        
    Note: Asterisk by the version number means the Version number       
          was changed (to the MXG version required), after an earlier   
          MXG version was listed as supporting this product release,    
          usually because an APAR modified the product's data records.  
          Or a coding error in MXG could be the reason for the change!  
                                                                        
    Availability dates for non-IBM products and MXG version required:   
                                                                        
                                                        MXG Version     
      Product Name                                       Required       
                                                                        
      Demand Technology                                                 
       NTSMF Version 1 Beta                                14.11        
       NTSMF Version 2.0                                   15.05        
       NTSMF Version 2.1                                   15.06        
       NTSMF Version 2.2                                   16.04        
       NTSMF Version 2.3                                   17.10        
       NTSMF 2.4.4                     Aug  9, 2002        20.04        
       NTSMF 2.4.5   INCOMPAT          Apr  1, 2003        21.02        
       NTSMF 2.4.7                     Sep 30, 2004        22.08        
       NTSMF 3.1.4                     Mar 15, 2009        27.01        
       NTSMF 4.0                       Mar 15, 2011        29.03        
      Landmark                                                          
       The Monitor for DB2 Version 2                       13.06        
       The Monitor for DB2 Version 3.0                     16.02        
       The Monitor for DB2 Version 3.1                     20.04        
       The Monitor for DB2 Version 4.0                     22.10        
       The Monitor for DB2 Version 5.0                     30.02        
       The Monitor for CICS/ESA 1.2 -                      12.12        
       The Monitor for CICS/ESA 1.3 -                      15.01        
       The Monitor for CICS/ESA 2.0 -                      15.06        
       The Monitor for CICS TCE 2.1 -                      20.04        
       The Monitor for CICS TCE 2.2 - 20.335, 21.134       21.04        
       The Monitor for CICS TCE 2.3 including CICS/TS 3.1  22.08        
       The Monitor for CICS TCE 3.2 (almost all)           25.11        
       The Monitor for CICS TCE 3.2 (almost all)           27.01        
       The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2)  29.07        
       TMON/CICS 3.4 (for CICS/TS 5.1)               30.30-32.12        
        (Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)              
       TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099)     33.04        
       TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195)    *33.09        
       The Monitor for MVS/ESA 1.3  -                      12.05        
       The Monitor for MVS/ESA 1.5  -                      12.05        
       The Monitor for MVS/ESA 2.0  -                      15.09        
       The Monitor for MVS/ESA 3.0  -                      19.19        
       TMON/MVS Version 4.4                                32.04        
                                                                        
      Candle                                                            
       Omegamon for CICS V200 User SMF                     12.05        
       Omegamon for CICS V300 User SMF                     13.06        
       Omegamon for CICS V400 User SMF                     16.02        
       Omegamon for CICS V400 type 110 segments            16.02        
       Omegamon for CICS V500 User SMF                     18.01        
       Omegamon for IMS V110 (ITRF)                        12.12        
       Omegamon for IMS V300 (ITRF)                        14.04        
       Omegamon for IMS V550/V560 (ITRF)                   25.05        
       Omegamon for MVS V300                               13.05        
       Omegamon for MVS V400                               13.06        
       Omegamon for DB2 Version 2.1/2.2                    13.05        
       Omegamon for VTAM V160                              12.04A       
       Omegamon for VTAM V400                              15.15        
       Omegamon for VTAM V500                              18.08        
       Omegamon for SMS V100/V110                          12.03        
      CA                                                                
       ACF2 6.2                                            16.04        
       ASTEX 2.1                                           14.04        
       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                          31.08        
       Mainview for MQ Version 4.4                         29.03        
       Mainview for MQ Version 5.1                         30.02        
       Mainview for MQ Version 5.2                         33.01        
       Mainview for CICS Version 6.5 (CICS/TS 5.1)         30.30        
       Mainview for CICS Version 6.4 (CICS/TS 4.2)         30.04        
       Mainview for CICS Version 6.1                       26.26        
       Mainview Auto Operator data file                    28.28        
       Mainview for DB2 THRDHIST file                      20.20        
       Mainview for TCP/IP                                 20.20        
       Mainview for 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 33.33.                  
                                                                        
                                                                        
 1. Incompatibilities introduced in MXG 33.33:                          
                                                                        
  a- Changes in MXG architecture made between 33.33 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.                   
                                                                        
                                                                        
                                                                        
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 33.33 after MXG 32.32:    
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  ANAL1430 33.230  Example to select TYPE14 and match with TYPE30.      
  ANAL2642 33.230  Example to select TYPE26 and match with TYPE42.      
  ANAL9914 33.139  z13 Processor Topology Report from SMF TYPE9914 data.
  ANALACTM 33.312  Correction for more than one service policy.         
  ANALCAPD 33.225  Major revision to analysis of Capping, now by LPAR.  
  ANALDB2R 33.069  SAS 9.3 does not have dictionary for DESTINATIONS.   
  ANALDB2R 33.134  Number reports mis-reported,ANALID added, headings.  
  ANALHSM  33.050  Graphics part had a NOT SORTED condition.            
  ANALID   33.159  Support for compressed SMF for DB2 Version/Subtype.  
  ANALIDDY 33.290  ANALIDDY tabulates ANALID SMF data by date.          
  ANALQBAT 33.147  Analysis of Batch Queue Times SMF30HQT/JQT/RQT/SQT.  
  ASMRMFV  33.021  ASMRMFV skips RCD if no Reporting Classes defined.   
  ASMRMFV  33.100  Protect invalid ASI table index in UWD, 0C4 ABEND.   
  ASMRMFV  33.182  New filters for RMF III ASI Filtering reading RMFVSAM
  ASMRMFV  33.222  RMF III DVT Character data Filtering saves DASD.     
  ASMRMFV  33.274  ASMRMFV Updates.                                     
  ASMTAPEE 33.207  ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.     
  ASUM113  33.130  Missing values in SMF70xx merged into PDB.ASUM113.   
  ASUM70PR 33.032  New SMF70WTI/WTS/WTU added to ASUM70LP/ASUMCELP      
  ASUMCELP 33.306  Variables SMF70GNM, SMF70GMU, SMF70WLA added.        
  BLDSMPDB 33.031  Wrong Start Week date with FORCEDAY and low case.    
  BUILDPDB 33.204  Variable IOTMNODD was never calculated in PDB.JOBS.  
  FTPING   33.056  OPTIONS OBS=0 fails read with ftp access method.     
  IMAC30IO 33.240  EXCPxxxx and IOTMxxxx can be dropped for nonexistent.
  IMAC6ESS 33.158  Type 6 ESS zero len segment INPUT STATEMENT EXCEEDED.
  IMACICMX 33.119  The optional IMACICMX for length=384 had missing END.
  ITRM     33.301  ITRM users MUST use %LET EPDBOUT= _SDB2SBP.          
  JCLASMXG 33.275  Assemble/Link Edit all five MXG ASM programs install.
  JCLPDB9  33.178  JCL Example for BUILDPDB, ANALxxxx members revised.  
  MANY     33.046  SUPPORT for z13 processor in MULTITHREADING MODE.    
  MOBWRK02 33.279  Support for DB2 Simulated Buffer Pool dataset.       
  MOBWRKSU 33.039  Summarization of Mobile Work CSV file combines split.
  RMFINTRV 33.024  ANY work in service class SYSOTHER, new log messages.
  RMFINTRV 33.181  Enhancement to ADD variables to be kept in RMFINTRV. 
  SMFSRCH  33.041  SMFSRCH redesigned to read the SMFOUT with UTILBLDP. 
  SMFSRCH  33.117  SMFSRCH corrections, TYPE30_D now populated.         
  SMFSRCH  33.131  SMFSRCH enhancements, ANALID, LOOKFOR list, AND/OR.  
  SMFSRCH  33.159  Support for compressed SMF in SMFSRCH LOOKFOR        
  SMFSRCH  33.307  Support for multiple text strings in LOOKFOR=.       
  TYPE102  33.067  DB2 Trace IFCID=220 misaligned, ILLEGAL ARGUMENT.    
  TYPE102  33.113  Some T102S106 DB2 zPARM values were misaligned/wrong.
  TYPE102  33.126  BMC APPTUNE 102 INPUT EXCEEDED if DATA SHARING.      
  TYPE102  33.187  Dataset T102S106 zPARM variables added.              
  TYPE102  33.236  All DB2 zPARM QWP4xxxx fields are now correct.       
  TYPE102  33.250  SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED.           
  TYPE102  33.264  Support for APPTUNE 11.2 INCOMPATIBLE change in 8005.
  TYPE102  33.273  DB2 SMF 102 IFCID=109 INVALID DO LOOP CONTROL ERROR. 
  TYPE102  33.294  SMF 102 IFCIDs 81E5-8160,8051x INPUT EXCEEDED DRROR  
  TYPE103  33.223  Short SMF 103 Subtype 13 INPUT EXCEEDED error.       
  TYPE105  33.061  GDPS SMF 105 INPUT STATEMENT EXCEED if no XVMX seg.  
  TYPE110  33.106  CICSEXCE variable EXCMTYPE decodes Exception type.   
  TYPE110  33.198  CICS/TS 5.3 BETA, MNSEGCL=5, INPUT STATEMENT EXCEEDED
  TYPE110  33.257  CICS/TS 5.3 CICSTRAN (final) new field added INCOMPAT
  TYPE110  33.326  MXG 32.10-First MXG 33.33. Increased CPU in SMF 110s 
  TYPE113  33.052  z13 Support for HIS SMF 113, many new equations.     
  TYPE113  33.173  z13 SM1132SP incorrectly forced, should be 5000 MHz. 
  TYPE113  33.197  Variable LPBUSY created in ASUM113 like TYPE113.     
  TYPE115  33.151  Support for MQ V8.0 MQCHIN, ERROR.VMAC115.OFFQCCT.   
  TYPE116  33.151  Support for MQ V8.0 MQCHININ, ERROR.VMAC116.LENQWHS. 
  TYPE119  33.144  Support for Type 119 new subtypes 94 and 95.         
  TYPE119  33.262  Support for SMF 119 subtypes 2, 5, 6, 7, 41-44, 97.  
  TYPE120  33.120  New IHDR120 header exit created for TYPE120 tailoring
  TYPE120  33.213  Support for WASODM Operational Decision Manager 8.7. 
  TYPE120  33.267  SMF 120 dataset TYP120JI only output first instance. 
  TYPE121  33.231  Support for JZOS Java Runtime Performance SMF 121.   
  TYPE1415 33.270  Variable SMF14ALIAS misspelled so it was not kept.   
  TYPE22   33.146  TYPE22PB dataset created for Reconfigured PCIE.      
  TYPE22   33.227  Dataset TYPE22PB RECONFIG PCIE had zero observations.
  TYPE30   33.132  New zEDC metrics in TYPE30 are now correct.          
  TYPE30   33.185  zEDC variables labels now INFLATE/DEFLATE.           
  TYPE30   33.206  z/OS 2.2 Job Correlation SMF30COR input/kept.        
  TYPE42   33.108  Support for APARs OA45944,OA45897 new SMF 42 metrics.
  TYPE42   33.230  Summed vars S42READS,S42WRITES added to TYPE42DS.    
  TYPE42   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE6    33.233  Support for APAR OA46136 adds IPADDR in PSF SMF 6.   
  TYPE60   33.038  Type 60 with no VVR INPUT STATEMENT EXCEEDED again.  
  TYPE64   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE70   33.200  TYPE70xx datasets now have VARYed interval data kept.
  TYPE7072 33.071  z13 SUPPORT. MXG 33.03 REQUIRED ONLY FOR SMT MODE    
  TYPE7072 33.096  z13 with SMT PROCVIEW=CORE, SMT-NUM not kept.        
  TYPE7072 33.121  z13 SMT-mode TYPE70/TYPE70PR data is WRONG 33.03-04. 
  TYPE7072 33.125  SMF70CAN/CTN restored, CPUWAIT-LPARBUSY for zIIPs.   
  TYPE7072 33.128  Zero OBS in TYPE70 for non-SMT if SMT SMF read first 
  TYPE7072 33.138  z13 in SMT Mode, TYPE70EN had missing values for ZIP.
  TYPE7072 33.179  TYPE70EN z13 SMT Mode, blank LPARNAME, SMF70MTTT fix.
  TYPE7072 33.186  z13 INCOMPATIBLE ERROR, SMT-MODE, when VARY CP online
  TYPE7072 33.217  z13 in SMT MODE ONLY: LPARCPUS=0 in PDB.TYPE70PR     
  TYPE7072 33.239  New _KTY70DR to drop variables from TYPE70 dataset.  
  TYPE7072 33.280  PDB.TYPE70 z13 SMT mode ZIPCPUS value may be wrong.  
  TYPE7072 33.318  Data Set SORT70EC NOT SORTED corrected with sort.    
  TYPE70EC 33.318  Data Set SORT70EC NOT SORTED, configuration changed. 
  TYPE70PR 33.174  IFL Processor count corrected to number in LPAR.     
  TYPE71   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE74   33.087  Support for RMF 74 Subtype 9 zEDC Accelerator.       
  TYPE74   33.127  zEDC TYPE749 dataset was finally revised correctly.  
  TYPE74   33.155  TYPE74ST now has SCM variables, TYPE74MO is no more. 
  TYPE74   33.185  zEDC TYPE749 zero divide fixed, R749DFMT formatted.  
  TYPE74   33.228  SMF 74 St 9 z/OS 2.1 z/13 INPUT STATEMENT EXCEEDED.  
  TYPE74   33.234  TYPE74HO false duplicates were being removed.        
  TYPE74   33.305  z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC.
  TYPE74   33.316  New variables compatibly added by z/OS 2.2.          
  TYPE78   33.156  Support for APAR OA44525, z HPF Extended Distance II.
  TYPE78   33.305  z/OS 2.2 new variables in TYPE78PA.                  
  TYPE80A  33.036  RACF SMF 80 record, TOKxxxxx fields increased length 
  TYPE80A  33.243  RACF Type 80 record "subtypes" (RACFEVNT) for ANALID.
  TYPE99   33.053  Support for z13 updates to type 99 subtype 14.       
  TYPE99   33.308  New variables compatibly added by z/OS 2.2.          
  TYPEAA   33.137  Support for Compuware ABEND-AID USER SMF Record.     
  TYPEATF  33.245  Support for OMEGAMON ATF IMS Log Record LCODE A2.    
  TYPEAXWY 33.199  Support for AXWAY SMF record, INCOMPATIBLE, inserts. 
  TYPEBBMQ 33.030  Support for BMC Mainview for MQ 5.2 (REQUIRED)       
  TYPEBBMQ 33.090  Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT)      
  TYPEBBMQ 33.115  Mainview for Mq BBMQBUFF variables corrected.        
  TYPEBBMQ 33.175  New IHDRBBMQ "Infile Header Exit" for selection.     
  TYPEBVIR 33.145  BVIR VTS Grid dataset BVIR33 wrong for second plus.  
  TYPEBVIR 33.196  TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected.     
  TYPECDC  33.201  Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2 
  TYPECIMS 33.114  IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN. 
  TYPECIMS 33.136  Support for MainView for IMS 5.2 (a/k/a IMF).        
  TYPECZA  33.166  Support for Correlog z/OS Agent User SMF record.     
  TYPEDB2  33.025  QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB. 
  TYPEDB2  33.068  Variable Q8STCCPU not kept after Change 30.133.      
  TYPEDB2  33.142  Variables QWACATWT and QWACPQCT corrected.           
  TYPEDB2  33.205  DB2ACCTP variables QPACPKID/LOCN/ may be truncated.  
  TYPEDB2  33.279  Support for DB2 Simulated Buffer Pool PDB.DB2STSBP.  
  TYPEDB2  33.303  Multiple DB2 100 Subtype 1 created multiple DB2STATS.
  TYPEDOL  33.060  DCOLLECT Cluster/Multi-VOL now have Class variables. 
  TYPEDOS  33.248  Support for zVSE/Power Version 9 Release 2 accounting
  TYPEEDA  33.237  Support for EDA V7706 (INCOMPATIBLE, data inserted). 
  TYPEID   33.045  ANALID report printed '110.001' vice '110.1.1'.      
  TYPEIMS  33.034  Variables SYSABEND,USRABEND decoded in IMS56FA.      
  TYPEIMS  33.298  Support for IMS 14.1 log records (COMPATIBLE)        
  TYPEIMST 33.252  Variable SYSTEM can be added to TYPE56FA with SYSPARM
  TYPEMAR  33.183  Support for MAR Hitachi Command Suite Mainframe      
  TYPEMGCR 33.212  Support for MEGACRYPTION Version 6, INCOMPATIBLE.    
  TYPEMWLX 33.037  Support for HP MeasureWare for Linux -               
  TYPENDM  33.143  INPUT STATEMENT EXCEEDED NDM-CDI PT record.          
  TYPENDM  33.229  NDM PT records INPUT EXCEEDED, INCOMPAT inserts.     
  TYPENMON 33.092  Some NMON BBBPnnnn variables were mis-assigned.      
  TYPENMON 33.104  Support for NMON CPUnr with three digits.            
  TYPENTMU 33.028  Support for EDS User SMF Record from NETMENU program.
  TYPEOSEM 33.133  ZOSEM User SMF - INPUT STATEMENT EXCEEDED error.     
  TYPEQACS 33.020  iSeries change in record length can force USER ABEND.
  TYPEQACS 33.101  Support for iSeries 7.2 (COMPATIBLE, new LRECLs).    
  TYPERACF 33.238  Support for RACF IRRDBU00 Record Type 1560.          
  TYPERMFV 33.140  RMF III RCD records INCOMPATIBLY CHANGED for z13.    
  TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE).     
  TYPESYNC 33.184  Support for SYNCSORT Release 1.4 (INCOMPAIBLE).      
  TYPETANZ 33.123  Support for Tandem ZMS Style records.                
  TYPETHAO 33.059  Support for Thales Security Resource Mgr RF1100.     
  TYPETMO2 33.099  TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG.     
  TYPETMO2 33.188  TMON/CICS Version 4.0, REQUIRED, MXG coding error.   
  TYPETMO2 33.210  More TMON/CICS Version 3 and Version 4 corrections.  
  TYPETMS5 33.129  Support for TMS new TRTCH values for TS1140.         
  TYPETPMX 33.070  TOKENID INCLAI, three $LIST_L and $RESTAR added.     
  TYPETPMX 33.232  Support for Thruput Manager VARNAME=$ORIGIO.         
  TYPETPMX 33.265  ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong.     
  TYPEVMXA 33.043  zVM VXUSEACT/VXUSEINT NOT SORTED ERROR.              
  TYPEVMXA 33.242  Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode.  
  TYPEVMXA 33.299  Support for zVM 6.3 MONWRITE z13 SMT MODE.           
  TYPEVMXA 33.327  Data set VMBYUSR missing many observations.          
  TYPEXAM  33.086  Support for Velocity Software zVPS XAM Version 5.4.  
  TYPEXAM  33.157  zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected.       
  TYPEXAM  33.202  Velocity ZVPS 5.4 XAMSYT had zero observations.      
  TYPEXAM  33.259  Support for zVPS Release 4230 for z13 SMT mode.      
  TYPEXAM  33.266  MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND.      
  TYPEXAM  33.320  Support for zVPS z13 SMT mode new variables.         
  TYPEXAM  33.324  zVPS variable CALENTMT changed from numeric, conflict
  TYPEXPTR 33.040  Support for SystemWare XPTR 5.2 subtype 140, ex-st-40
  TYPEZCOS 33.116  Support for ZCOST AutoSoftCapping Version V3.0.00.   
  UTILBLDP 33.042  Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found
  UTILBLDP 33.159  BUILDPDB=NO incorrect for type 102 2 byte subtypes.  
  UTILCVRT 33.105  Alternate table needed for no TRANSCODE PROC CPORT.  
  UTILEXCL 33.049  New reports, trans without dictionary, READTIME.     
  UTILEXCL 33.255  ARRAY EXCEEDED when more than 999 connectors.        
  VGETDDS  33.208  z/OS Only.  Multiple tape mounts with DDNAMES=PDB:.  
  VMAC115  33.180  Support for MQ Version 8 subtype 215 record          
  VMAC30   33.005  Support for APAR OA45767 adds zEDC statistics.       
  VMACUCB  33.245  DEVCLASS=41 decode identities specific CTC type.     
  VMXGALOC 33.325  Correction for WEEK1 allocation.                     
  VMXGINIT 33.062  %LET MXGDEBUG=FULL; shows OPTIONS, enables diags.    
  VMXGINIT 33.162  "MXGLOG" option to send MXG Messages to MXGLOG.      
                                                                        
                                                                        
                                                                        
  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 33.327 were in MXG 33.33 dated Jan 18, 2016=========
                                                                        
Change 33.327  Dataset VMBYUSR was missing many observations because the
VMACVMXA       timestamp in MRHDRTOD in VXUSEACT did not exactly match  
Jan 15, 2016   the MRHDRTOD in VXUSEINT which are key MERGE variables.  
               Circumvention was to merge with the FLOOR(MRHDRTOD).     
   Thanks to Joseph J. Faska, DTCC, USA.                                
                                                                        
Change 33.326 -MXG 32.10-MXG 33.33.  Increase in CPU time for SMF 110   
VMAC110        record processing, 300 to 500 seconds, 22 GB, due to     
Jan 15, 2016   multiple executions of RESOLVE function where only one   
               was needed, to populate character variable CICXLTR, which
               is only used to enhance error messages if EXCLUDED fields
               are found.                                               
              -Too many warning messages were printed if Compressed CICS
               data was read on z/OS without the CICSIFUE INFILE exit,  
               and too many "ok on ASCII" messages were printed.        
   Thanks to Perry Lim, Union Bank, USA.                                
                                                                        
Change 33.325 -Change 32.220 added new BASECICS and BASEDB2 parameters  
BLDSMPDB       that let you send DB2 and/or CICS datasets to a different
VMXGALOC       drive, but did not tell you that if you did not use them,
UTILBLDP       those datasets were written to BASEDIR. Default is now   
Jan 17, 2016   a NULL string so that behavior is unchanged and the log  
Jan 18, 2016   now notes where CICSTRAN and DB2ACCT are allocated.      
              -Change 32.262 incorrectly set the WEEK WEEK1 libnames to 
               be the current week when RUNWTD was NO and when RUNWTD   
               was YES the WTD LIBNAME was not allocated.  Fortunately, 
               the only exposure is that if a user wanted to run a      
               report with WEEK1, it would have been empty since the    
               week had not been run to populate it.                    
              -UTILBLDP failed to include ASUMDBSS because an AND in the
               macro was misspelled as AMD and the compiler does not see
               it as a syntax error.                                    
              -BLDSMPDB debugging statements left in code.              
   Thanks to Richard Krueger, Sentry, USA.                              
                                                                        
Change 33.324  zVPS variable CALENTMT was changed from numeric to char  
VMACXAM        causing a conflict if OLD and NEW datasets were combined.
Jan 13, 2016   CALENTMT is restored to CHAR, new variable CALENTMTN has 
               the actual numeric CPU ENTITLEMENT value.                
   Thanks to David A. Sadler, OPTUM, USA.                               
                                                                        
Change 33.323  New fields added to Thruput Manger are supported:        
VMACTPMX          CONTR   ='CONTR'                                      
Jan 12, 2016      JCL_SJB ='JCL_SJB'                                    
                  JCL_SJC ='JCL_SJC'                                    
                  JCL_SJG ='JCL_SJG'                                    
                  JAL_T   ='JAL_T'                                      
               There is a defective entry with '   ST_L' that should be 
               'LIST_L' that prints an error message that it was skipped
               while we investigate with the vendor.                    
                                                                        
Change 33.322  The new JOB Correlation Token SMF30COR and SMF26JCR are  
VMAC26J2       populated with 64 bytes of '00'x for OMVS and most STCs, 
VMAC30         which then print as 64 unprintable characters. The '00'X 
Jan 12, 2016   are translated to blanks.  But it is unclear why this new
               token is created; the READTIME JOB JESNR uniquely match  
               and only require 24 bytes, and are in many more SMF      
               records than just these two.                             
                                                                        
====== Changes thru 33.321 were in MXG 33.33 dated Jan 11, 2016=========
                                                                        
Change 33.321 -Change 33.297 failed if OPTIONS USER=PDB is used, because
VMAC7072       the PROC DATASETS (to change a label) coded a LIB=WORK   
Jan  9, 2016   which failed when USER=PDB.  The LIB=&MXGWORK argument   
Aug 31, 2017   now finds the dataset (replacing a WORK.TEMP70EN fix.)   
              -BUT: IN GENERAL MXG DOES NOT SUPPORT OPTIONS USER=PDB,   
               "out of the box": both BUILDPDB and UTILBLDP can fail    
               or can NOT fail but produce missing values when USER=PDB 
               is used, and it typically requires additional tailoring  
               for a specific purpose, especially when accumulated data 
               requires DIF(), and may require a second execution of    
               %VMXGINIT.  Contact support@mxg.com if you have a need.  
              -Aug 2017: Note that using WORK=PDB in CONFIG has the same
               exposure and thus that is also not supported.            
   Thanks to Scott Wiig, USBank, USA.                                   
                                                                        
Change 33.320  Support for zVPS z13 SMT Mode adds these variables:      
VMACXAM       -Dataset XAMCPUTO:                                        
Jan  7, 2016     CALENTMT='ENTITLEMENT'                                 
                 CORID   ='CORE*ID'                                     
                 PFXPOLAR='POLARIZATION'                                
                 RCCTOPDI='DSVBK*INDEX'                                 
                 TID     ='THREAD*ID'                                   
              -Datasets XAMCPUBY, XAMIFLBY, XAMIFLTO, XAMCPUTO:         
                 AVGTDBYCORE='AVG*TD*BY CORE'                           
                 AVGTDBYTYPE='AVG*TD*BY TYPE'                           
                 BUSYTIMEBYCORE='BUSY*TIME*BY CORE'                     
                 BUSYTIMEBYTYPE='BUSY*TIME*BY TYPE'                     
                 CAPBYTYPE='CAP*BY TYPE'                                
                 INTERVALTIMEBYCORE='INTERVAL*TIME*BY CORE'             
                 INTERVALTIMEBYTYPE='INTERVAL*TIME*BY TYPE'             
                 MAXCAPBYTYPE='MAX*CAP*BY TYPE'                         
                 MTUTILBYCORE='MT*UTIL*BY CORE'                         
                 MTUTILBYTYPE='MT*UTIL*BY TYPE'                         
                 PF2CADCT ='COUNT CAD*FOR*SPINLOCK*NODLAY'              
                 PF2TSCAD ='COUNT CAD*DURING*TSGET*REQSTS'              
                 PF2TSCNT ='COUNT*TSGET*REQUESTS'                       
                 PF2TSGTM ='ELAPSED*CONSUMED*BY TSGET'                  
                 PFXPRKWT ='PARKED*WAIT TIME*TOT UNIT'                  
                 PRODBYCORE='PROD*BY CORE'                              
                 PRODBYTYPE='PROD*BY TYPE'                              
                 SAMPLEDCORESBYTYPE='SAMPLED*CORES*BY TYPE'             
                 SAMPLES='SAMPLES'                                      
                                                                        
Change 33.319  The OPTION NONOTES statement added for the MXGLOG option 
VMXGINIT       must be reset to NOTES prior to the %MACRO statement. In 
Jan  8, 2016   some cases the NONOTES remained incorrectly in effect,   
Jan 22, 2016   which could suppress the INFILE SMF information and the  
               "dataset has nnn obs" notes on the SAS log.  The Exposure
               was limited to 33.07-33.13, and only with a tailored MXG 
               execution with a VIEW driven by a PROC SORT.             
               Jan 23: The OPTION NOTES was mis-located, suppressing the
               printing of   NOTE: Fileref=SOURCLIB and the DSNAMEs.    
   Thanks to Scott Wiig, US Bank, USA.                                  
                                                                        
Change 33.318  Data Set SORT70EC NOT SORTED was corrected with an extra 
VMAC7072       PROC SORT.  It appears a change in the configuration was 
Jan  5, 2016   made during the interval that caused the not sorted data.
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.317  Documentation of APARs corrections; NO CHANGES WERE MADE.
VMAC1415      -TYPE1415 APAR OA47899 corrects SMF 14/15 written at EOV  
VMAC92         that did not contain the Type 1 Compressed Format data   
VMAC74         set section.                                             
VMAC80A       -TYPE92 APAR OA49128 corrects invalid value in SMF92CTO.  
VMAC116       -TYPE74 APAR OA48860 corrects SMF74DTS,SMF74DCT that are  
Jan  3, 2016   not set correctly for a device after HYPERSWAP.          
              -TYPE80A APAR PI52900 for CICS/TS 5.2, adds CICS NETNAME  
               to SMF 80 record when DFHSN1102 SIGNON FAILS.            
              -TYPE116 APAR PI53551 MQ z/OS V8 Class 3 data may be      
               incorrect for CICS and CHIN Thread Control Blocks.       
              -Users of IBM CICS PA V5.1/5.2 NEED APAR PI43779 to       
               correct report files, especially LIST, that have file    
               blocking of ONE, wasting DISK space and CPU time.        
                                                                        
Change 33.316 -The many new variables added in z/OS 2.2 in Change 33.189
VMAC42         are now kept.                                            
VMAC64        -TYPE64 new variables                                     
VMAC71           SMF64SSR='SECONDARY*SPACE*REDUCTION?'                  
VMAC74           SMF64FCC='BEGINNING*CCHH'                              
Dec 30, 2015     SMF64TCC='BENDING*CCHH'                                
                 SMF64VSN='VOLUME*SERIAL*NUMBER'                        
                 SMF64CUU='DEVICE*NUMBER'                               
                 SMF64IND='SPINDLE*IDENTIFICATION'                      
                 SMF64UTY='*UNIT*TYPE'                                  
              -TYPE71 new variables                                     
                 SMF714KA='AVB*1MB FIXED*USED*4K REQ'                   
                 SMF714KM='MIN*1MB FIXED*USED*4K REQ'                   
                 SMF714KX='MAX*1MB FIXED*USED*4K REQ'                   
                 SMF71C2A='AVG*HIGH VIRTUAL*COMMON*1MB FIXED'           
                 SMF71C2M='MIN*HIGH VIRTUAL*COMMON*1MB FIXED'           
                 SMF71C2X='MAX*HIGH VIRTUAL*COMMON*1MB FIXED'           
                 SMF71C3A='*AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'         
                 SMF71C3M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'          
                 SMF71C3X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'          
                 SMF71CPA='AVB*HI VIRT*COMMON*INUSE'                    
                 SMF71CPM='*MIN*HI VIRT*COMMON*INUSE'                   
                 SMF71CPX='*MAX*HI VIRT*COMMON*INUSE'                   
                 SMF71PLA='AVB*1MB PGBL*BACKED*1MB PGBL'                
                 SMF71PLM='MIN*1MB PGBL*BACKED*1MB PGBL'                
                 SMF71PLX='MAX*1MB PGBL*BACKED*1MB PGBL'                
                 SMF71S2A='AVG*OBJECTS*SHARED MEM*BACK 1MB'             
                 SMF71S2M='MIN*OBJECTS*SHARED MEM*BACK 1MB'             
                 SMF71S2X='MAX*OBJECTS*SHARED MEM*BACK 1MB'             
                 SMF71S3A='AVG*FRAMES*SHARED HIGH*4K*ON SCM'            
                 SMF71S3M='MIN*FRAMES*SHARED HIGH*4K*ON SCM'            
                 SMF71S3X='MAX*FRAMES*SHARED HIGH*4K*ON SCM'            
                 SMF71S4A='AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'          
                 SMF71S4M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'          
                 SMF71S4X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'          
              -TYPE74 new variable                                      
                 R748RAI  ='RANK*ADAPTER*PAIR*ID'                       
                                                                        
Change 33.315  z/OS 2.2 JOB='*MASTER*' JCTJOBID='MSGR' SUBSYS='SMS' was 
VGETJESN       not expected, caused WARNING TYPETASK NOT DECODED, now   
Dec 27, 2015   is protected, with TYPETASK='STC' now set.               
                                                                        
Change 33.314  Unused Change Number.                                    
                                                                        
Change 33.313  Documentation. Type 30 EXCP/IOTM NODD/TODD/TOTL variables
TYPE30         in the "raw" TYPE30_4/TYPE30_5/TYPE30_V datasets created 
Dec 24, 2015   directly from SMF, are wrong or misleading for jobs with 
               MULTIDD='Y' continuation records (they contain only EXCP 
               and IOTM fields). The variables ARE VALID in the datasets
               PDB.JOBS/PDB.STEPS/PDB.SMFINTRV, built by BUILDPDB or the
               ONLYINTV program, where MXG logic combines the MULTIDDs  
               and then correctly populates those variables.            
                 For MULTIDD='Y' jobs, the first record can be a FLUSH  
                 that contains NO DD segments, so NUMDD=0 and the TODD  
                 variables are missing values.  The TOTL in the MULTIDD 
                 records is missing, since that field is the total for  
                 the step, and that is only in the first SMF 30 record. 
                 And since NODD=TOTL-TODD, the NODD is also missing.    
                 And since they can be individually wrong, the sum of   
                 these variables in those "raw" TYPE30xx datasets is    
                 unusable.                                              
                                                                        
Change 33.313  Cosmetic.  Comments enhanced.                            
BLDSMPDB                                                                
Dec 23, 2015                                                            
                                                                        
Change 33.312  If you had more than a single service policy in your data
ANALACTM       the report of the WLM service definition was not sorted  
Dec 23, 2015   by the policy name resulting in reports printed by the   
               importance level instead of the service policy.          
                                                                        
====== Changes thru 33.311 were in MXG 33.13 dated Dec 23, 2015=========
                                                                        
Change 33.311 -UTILBLDP with IMACKEEP= fails execution with syntax error
UTILBLDP       due to invalid comment termination in the generated code 
Dec 23, 2015   that referenced &SPINUOW macro variable.                 
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
Change 33.310  MXG's ANALZPCR is no longer usable, nor needed, since IBM
ANALZPCR       zPCR will now read a "printed" IBM RMF CPU report to     
Dec 21, 2015   create the zPCR input in External File Format V2.0 that  
               is required for zPCR V8.7.                               
                                                                        
====== Changes thru 33.309 were in First MXG 33.13 dated Dec 21, 2015===
                                                                        
Change 33.309  Variable QCSTDNRT, previously reserved, is now input and 
VMAC116        formatted as a time, with NS*RESOLUTION*TIME' in         
Dec 21, 2015   dataset MQCHININ.                                        
   Thanks to Robert Miles Standish, UBS, USA.                           
                                                                        
Change 33.308  Support for z/OS 2.2 new variables SMF 99 ST 14 added    
VMAC99            S99E_AN_CI     ='CPU/CORE*CONTAINER*INFO*/            
Dec 21, 2015      S99E_AN_CI_FLAGS='CI_FLAGS'                           
Dec 22, 2015      S99E_AN_CI_NL   ='CPU/CORE*TOPOLOGY*INFO'             
                  S99E_AN_CI_NL1  ='CONTAINER*ID OF*NESTING*LEVEL 1'    
                  S99E_AN_CI_NL2  ='CONTAINER*ID OF*NESTING*LEVEL 2'    
                  S99E_AN_CI_NL3  ='CONTAINER*ID OF*NESTING*LEVEL 3'    
                  S99E_AN_CI_NL4  ='CONTAINER*ID OF*NESTING*LEVEL 4'    
                  S99E_AN_CI_NL5  ='CONTAINER*ID OF*NESTING*LEVEL 5'    
                  S99E_AN_CI_NLINUSE='HIGHEST*NESTING*LEVELUSED'        
                  S99E_AN_INFO   ='AFFINITY*NODE*INFO'                  
                  S99E_AN_TOPO   ='CPU/CORE*TOPOLOGY*INFORMATION'       
                  S99E_CP_BOOKID ='BOOK*ID'                             
                  S99E_CP_CHIPID ='CHIP*ID'                             
               to dataset TYPE99EN, and these variables to TY99EP:      
                  S99E_CP_BOOKID ='BOOK*ID'                             
                  S99E_CP_CHIPID ='CHIP*ID'                             
              -Each subtype 14 dataset now has all of the header        
               variables kept.                                          
   Thanks to Erling Andersen, SMT, DENMARK.                             
                                                                        
Change 33.307 -SMFSRCH was supposed to support multiple text strings in 
SMFSRCH        LOOKFOR=, with ANDOR=, but it only supported one string; 
VMXGSRCH       multiple strings caused nothing to be found.             
Dec 21, 2015   Now, multiple LOOKFOR= strings are supported, but only   
Dec 29, 2015   with "OR" logic, i.e., any LOOKFOR= string will be found.
               It's impractical to support multiple ANDed stings with   
               LOOKFOR=, but the SELECTION= alternative to LOOKFOR=     
               provides complete control including ANDs of strings.     
              -VMXGSRCH messages when a VALUE= was found now print the  
               VALUE= that was searched, or when a VARS= is used, then  
               all of the matching variables names are listed, instead  
               of a blank line.                                         
                                                                        
Change 33.306  The Group Capacity Variables SMF70GNM (Group Name) and   
VMXG70PR       SMF70GMU (MAXIMUM LICENSE UNITS) are kept in the Per-LPAR
Dec 20, 2015   CEC-Level dataset PDB.ASUMCELP (built automatically in   
Dec 22, 2015   BUILDPDB by the include of member ASUM70PR).             
Jan  8, 2015  -SMF70WLA is added to ASUMCELP for the systems whose SMF  
               70's were read.                                          
              -Variable ZIPCPUS was ROUNDed to two decimal places, to   
               print pretty, as the calculated value often was x.99999, 
               and debugging _PRN70PR macro was added to VMXG70PR.      
                                                                        
Change 33.305 -Support for z/OS 2.2 RMF 74 Subtype 10 SCM Storage Class 
EXTY7410       Memory statistics creates new datasets:                  
EXTY74SC                                                                
IMAC74           dddddd  dataset   description                          
VMAC74           TY7410  TYPE7410  SCM EADM AGGREGATE STATS             
VMAC78           TY74SC  TYPE74SC  SCM CONFIGURATION MEASUREMENT        
Dec 18, 2015  -New z/OS 2.2 variables (COMPATIBLE) in TYPE78PA:         
                 R782LSMOMIN ='MIN FRAMES*ARE USED*SHARED*MEMOBJ='      
                 R782LSMONTME='TIME STAMP*OF MIN*SHARED*MEMOBJ='        
                 R782LSMOMAX ='MAX FRAMES*ARE USED*SHARED*MEMOBJ='      
                 R782LSMOXTME='TIME STAMP*OF MAX*SHAREDMEMOBJ='         
                 R782LSMOAVG ='AVG FRAMES*ARE USED*SHARED*MEMOBJ='      
                                                                        
Change 33.304  Dataset TYP120xx variable SM120RULEXSUM was a typo for   
VMAC120        SM120RULEXFSUM and now, SM120RULEXSUM doesn't exist.     
Dec 16, 2015                                                            
   Thanks to Homayoun Riazi, OPTUM, USA.                                
                                                                        
Change 33.303  "Duplicate" obs were created in PDB.DB2STATS when DB2    
VMACDB2        used more than 24 buffers in an interval, because DB2    
Dec 16, 2015   creates (unexpected) multiple SMF 100 subtype 1 records  
               for that interval, but the QWHSSTCK time is not exactly  
               the same, and QWHSSTCK must be used because DB2 stats    
               records don't contain an interval start time value. There
               were no actual duplicated data, but additional obs with  
               the same SMFTIME and only buffer metrics were created in 
               the PDB.DB2STATS statistics summary dataset.             
               Now, the data is ordered by QWHSISEQ and the QWHSSTCK of 
               the first instance is stored in both PDB.DB2STATB and in 
               the new PDB.DB2STSBP buffer datasets, and the corrected  
               QWHSSTCK is used to create PDB.DB2STATS.                 
   Thanks to Rachel Holt, Fidelity Systems, USA.                        
   Thanks to Lori Masulis, Fidelity Systems, USA.                       
                                                                        
Change 33.302  Support for two optional CICS user fields:               
IMACICWR         CMODHEAD  CMODNAME   Variable                          
IMACICWS         OMEGCICS  OMEGCICS   OMEGCICS   $EBCDIC104.            
IMACAAAA         USER      STARPOL    STARPOL     $EBCDIC92.            
UTILEXCL                                                                
VMAC110                                                                 
Dec 15, 2015                                                            
                                                                        
Change 33.301  ITRM 33.12+ ERROR: WORK.SUMSTSPB.DATA does not exist.    
ITRM          -ITRM users of MXG 33.12+ MUST use EPDBOUT macro variable 
Dec 11, 2015   to correctly sort the new DB2STSBP Simulated Buffer Pool 
               with this %LET statement inserted:                       
                  %CMPROCES . . .                                       
                  %LET EPDBOUT= _SDB2SBP ;                              
                  %CPSTART . . .                                        
              -If you have not installed the ITRM Hot Fix 45583/41019,  
               you already have an EPDBOUT= _SDB2ST4 _SDB2225, so your  
               circumvention would be:                                  
                  %LET EPDBOUT=_SDB2ST4 _SDB2225 _SDB2SBP ;             
   Thanks to Richard Schwarz, IBM, USA.                                 
                                                                        
Change 33.300  New variables added to DB2ACCTx and DB2STATx datasets by 
ASUMDB2A       DB2 Version 11 are added to existing summary datasets.   
ASUMDB2B       The new dataset DB2STSBP summary is added in VMXGDBSS.   
ASUMDB2G                                                                
ASUMDB2P                                                                
VMXGDBSS                                                                
Dec 11, 2015                                                            
Dec 14, 2015                                                            
   Thanks to Wayne Bell, UNIGROUP, USA.                                 
                                                                        
Change 33.299  Support for zVM 6.3 MONWRITE z13 SMT Mode; fields were   
VMACVMXA       inserted (INCOMPATIBLE) in SYTPRP after Change 33.242.   
Dec 11, 2015   zVM 6.3.15.1 records have been validated.  These         
               records have been validated.  These variables are added  
               to VXSYTPRP dataset:                                     
                  PF2CADCT     ='UNDELAYED*CAD*INSTRUCTIONS'            
                  PF2TSCAD     ='CAD*INSTRUCTIONS*EXECUTED'             
                  PF2TSCNT     ='TSGET*REQUESTS'                        
                  PF2TSGTM     ='TSGET*REQUEST*ELAPSED*TIME'            
                  PFXPOLSR     ='CORE*POLARIZATION'                     
                  SYTPRP_CAL_PLSIPTEI='IPTE 1/2*ACQUISITIONS'           
                  SYTPRP_COREXTCT='COUNT*MT*COUNTERS*EXTRACTED'         
                  SYTPRP_COREXTTT='DURATION OF*EXTRACT*MT*COUNTERS'     
                  SYTPRP_PFXCPUCH='TIMES WHEN*SIEIHCPU FFFF*SWITCHES'   
                  SYTPRP_PFXPRGCT='TIMES WHEN*SIEIHCPU FFFF'            
                  SYTPRP_PLSIIA  ='IPTE 2*ACQUISITIONS'                 
                  SYTPRP_PLSIIADD='TIMES WHEN*ACQUIRED*AS SHARE'        
                  SYTPRP_PLSIIHDSSQCH='SSQ TIME*CONTINUOUS*HELD'        
                  SYTPRP_PLSIIWTSSQCH='SSQ TIME*CONTINUOUS*HELD'        
                  SYTPRP_PLSIIHLD='DURATION*CONTINUOUS*HELD'            
                  SYTPRP_PLSIINHLD ='INTERVAL*COUNT*CONTINUOUS*HELD'    
                  SYTPRP_PLSIIWTM='WAIT TIME*IPTE*INTERLOCK*ACQUISITION'
                  SYTPRP_PLSPTLCA='CALLS SET*PENDING*NON-LOCAL'         
                  SYTPRP_PLSPTLCD='CALLS SET*PENDING*HOST TLB'          
                  SYTPRP_PLSPTLCL='CALLS TO*PURGE*LOCAL*TLB'            
                                                                        
Change 33.298  Support for IMS 14.1 log records (COMPATIBLE).           
VMACIMS        The IMS56FA dataset added two new variables              
Dec 10, 2015     DLRDIR='DL/I*IR*CALLS'                                 
                 DLRDMR='DL/I*MR*CALLS'                                 
               in existing reserved bytes.                              
                                                                        
                                                                        
Change 33.297 -Label for PCTCPUBY was corrected for PDB.TYPE70EN, which 
VMAC7072       had incorrectly been "LPAR*CPU*BUSY".                    
VMXGWORL      -VMXGWORL enhanced to parse the result into two macro vars
Dec 10, 2015   &MXGWORLLIB and &MXGWORLDSN so that PROC DATASETS, which 
               requires them separately, could be used to change labels.
                                                                        
Change 33.296  If you specified IMACKEEP= to retain the IMACKEEP that is
UTILBLDP       generated, invalid syntax for _TIMEDIF/_SPINUOW/_SPINCNT 
Dec  9, 2015   could be generated; the NULL value default should have   
               suppressed the generation of these macros; now it does.  
               The ECHO=YES default will now display the IMACKEEP text. 
   Thanks to Richard Krueger, Sentry, USA.                              
                                                                        
Change 33.295  Cosmetic.  Prints messages when there are datasets in OLD
VMXGCOMP       that are not in NEW, or vice versa.                      
Dec 8, 2015                                                             
                                                                        
Change 33.294  INPUT EXCEEDED ERROR for SMF 102 records written by BMC's
FORMATS        Mainview for DB2, IFCIDs 815Ex-8160x - Accounting Rollup 
VMACDB2H       and IFCID 80F1x - Data Collector, which were unknown and 
Dec  9, 2015   unsupported in MXG.  These records contain unique SMF 102
Dec 18, 2015   header segments that do not match MXG expectations that  
               caused the error.  But since no one has actually asked   
               for these subtypes, this change circumvents the problem  
               Decimal IFCIDS deleted are 33009,33118,33119,and 33120.  
               by skipping these subtypes in SMF 102 processing in MXG. 
              -The ANALID report (VMACID,FORMATS) is updated to be aware
               of and describe these 102 subtypes in its reports.       
                                                                        
Change 33.293  MACRO _TIMEDIF % set instead of MACRO _TIMEDIF 0 % caused
UTILBLDP       a 22-322 Syntax Error.                                   
Dec  5, 2015                                                            
                                                                        
Change 33.292  When printing of the found datasets is requested, the    
VMXGFIND       heading has the LIBNAME and MEMNAME printed.             
Dec  5, 2015                                                            
                                                                        
Change 33.291  Support for BMC Mainview for CICS Version 7.0 (COMPAIBLE)
VMACMVCI       adds these new variables for CICS/TS 5.3 to CMRDETL:     
Dec  6, 2015      T6E70XCT='70*EXTENSIONS*LENGTH'                       
                  T6EDSAWC='ALLOCATE*THREAD*WAIT*COUNT'                 
                  T6EDSAWF='ALLOCATE*THREAD*WAIT*FLAG'                  
                  T6EDSAWT='ALLOCATE*THREAD*WAIT*TIME'                  
                  T6EEIBTR='INTERNAL*PROCESSING*FIELD'                  
                  T6EJSRPL='JSON*RESPONSE*MSG LENGTH'                   
                  T6EJSRQL='JSON*REQUEST*MSG LENGTH'                    
                  T6ELSTN_ACPTOK ='SUCCESSFUL*ACCEPTS'                  
                  T6ELSTN_CHILDTK='CHILD*SUBTASKS*STARTED'              
                  T6ELSTN_DISPROG='DISABLED*PROGRAM'                    
                  T6ELSTN_DISTRAN='DISABLED*TRANSACTION'                
                  T6ELSTN_GVSKTFL='GIVESOCKET*FAILURES'                 
                  T6ELSTN_REJAUTH='REJECTED*NOT AUTH'                   
                  T6ELSTN_REJSECU='REJECTED*SECURITY'                   
                  T6ELSTN_REJTDIO='REJECTED*TD*I/O'                     
                  T6ELSTN_REJTDLN='REJECTED*TD*LENGTH'                  
                  T6ELSTN_REJTDNS='REJECTED*TD*NO SPACE'                
                  T6ELSTN_TACPTOK='TERM*SUCCESSFUL*ACCEPTS'             
                  T6ELSTN_TCHILDTK  ='TERM*CHILD*SUBTASKS*STARTED'      
                  T6ELSTN_TDISPROG  ='TERM*DISABLED*PROGRAM'            
                  T6ELSTN_TDISTRAN  ='TERM*DISABLED*TRANSACTION'        
                  T6ELSTN_TGVSKTFL  ='TERM*GIVESOCKET*FAILURES'         
                  T6ELSTN_TREJAUTH  ='TERM*REJECTED*NOT*AUTH'           
                  T6ELSTN_TREJSECU  ='TERM*REJECTED*SECURITY'           
                  T6ELSTN_TREJTDIO  ='TERM*REJECTED*TD*I/O'             
                  T6ELSTN_TREJTDLN  ='TERM*REJECTED*TD*LENGTH'          
                  T6ELSTN_TREJTDNS  ='TERM*REJECTED*TD*NO SPACE'        
                  T6ELSTN_TUNDTRAN  ='TERM*UNDEFINED*TRANSACTION'       
                  T6ELSTN_UNDTRAN='UNDEFINED*TRANSACTION'               
                  T6ENCGET='COUNTER*DCOUNTER*REQUESTS'                  
                  T6ETOTL_TINITT ='TOTAL*INIT*TIME'                     
                  T6ETOTL_TOTHRT ='TOTAL*OTHER*TIME'                    
                  T6ETOTL_TREADT ='TOTAL*READ*TIME'                     
                  T6ETOTL_TSLCTT ='TOTAL*SELECT*TIME'                   
                  T6ETOTL_TWRITT ='TOTAL*WRITE*TIME'                    
                  T6ETRUE_ATTACH ='DYNAMIC*SUBTASK*COUNT'               
                  T6ETRUE_INITCKC='INIT*CALL*COUNT'                     
                  T6ETRUE_INITCKF='INIT*CALL*FLAG'                      
                  T6ETRUE_INITCKT='INIT*CALL*CLOCK'                     
                  T6ETRUE_OPENAPI='OPEN*API*COUNT'                      
                  T6ETRUE_OTHRCKC='OTHER*CALL*COUNT'                    
                  T6ETRUE_OTHRCKF='OTHER*CALL*FLAG'                     
                  T6ETRUE_OTHRCKT='OTHER*CALL*CLOCK'                    
                  T6ETRUE_READCKC='READ*CALL*COUNT'                     
                  T6ETRUE_READCKF='READ*CALL*FLAG'                      
                  T6ETRUE_READCKT='READ*CALL*CLOCK'                     
                  T6ETRUE_REUS ='REUSABLE*COUNT'                        
                  T6ETRUE_SLCTCKC='SELECT*CALL*COUNT'                   
                  T6ETRUE_SLCTCKF='SELECT*CALL*FLAG'                    
                  T6ETRUE_SLCTCKT='SELECT*CALL*CLOCK'                   
                  T6ETRUE_TATTACH='TERM*DYNAMIC*SUBTASK*COUNT'          
                  T6ETRUE_TCBLIM ='TCB*LIMIT*REACHED*COUNT'             
                  T6ETRUE_TINIT='TASK TERM*TOTAL INITS'                 
                  T6ETRUE_TOPENAPI  ='TERM*OPEN*API*COUNT'              
                  T6ETRUE_TOTHR='TASK TERM*TOTAL OTHERS'                
                  T6ETRUE_TREAD='TASK TERM*TOTAL READS'                 
                  T6ETRUE_TREUS='TERM*REUSABLE*COUNT'                   
                  T6ETRUE_TSLCT='TASK TERM*TOTAL SELECTS'               
                  T6ETRUE_TTCBLIM='TERM*TCB*LIMIT*COUNT'                
                  T6ETRUE_TWRIT='TASK TERM*TOTAL WRITES'                
                  T6ETRUE_WRITCKC='WRITE*CALL*COUNT'                    
                  T6ETRUE_WRITCKF='WRITE*CALL*FLAG'                     
                  T6ETRUE_WRITCKT='WRITE*CALL*CLOCK'                    
                  T6ETSGSC='SHARED*TS*GETS'                             
                  T6ETSPSC='SHARED*TS*PUTS'                             
               In addition, these existing file segments that have no   
               extended data now create these variables:                
                  PSEUDOFILE='PSEUDO*FILE*NAME'                         
                  PSEUDOFILT='PSEUDO*FILE*DURATION'                     
                  PSEUDOFILC='PSEUDO*FILE*COUNT'                        
                  ADABASFILE='ADABAS*FILE*NAME'                         
                  ADABASFILT='ADABAS*FILE*DURATION'                     
                  ADABASFILC='ADABAS*FILE*COUNT'                        
                  SAPFILE='SAP*FILE*NAME'                               
                  SAPFILT='SAP*FILE*DURATION'                           
                  SAPFILC='SAP*FILE*COUNT'                              
                  DATACOMFILE='DATACOM*FILE*NAME'                       
                  DATACOMFILT='DATACOM*FILE*DURATION'                   
                  DATACOMFILC='DATACOM*FILE*COUNT'                      
                  IDMSFILE='IDMS*FILE*NAME'                             
                  IDMSFILT='IDMS*FILE*DURATION'                         
                  IDMSFILC='IDMS*FILE*COUNT'                            
                  SUPRAFILE='SUPRA*FILE*NAME'                           
                  SUPRAFILT='SUPRA*FILE*DURATION'                       
                  SUPRAFILC='SUPRA*FILE*COUNT'                          
                  S2KFILE='S2K*FILE*NAME'                               
                  S2KFILT='S2K*FILE*DURATION'                           
                  S2KFILC='S2K*FILE*COUNT'                              
                  GENFILE='GEN*FILE*NAME'                               
                  GENFILT='GEN*FILE*DURATION'                           
                  GENFILC='GEN*FILE*COUNT'                              
                                                                        
Change 33.290  The ANALID report tabulates all SMF data in the SMF file;
ANALIDDY       the new ANALIDDY tabulates the SMF data by DATE of the   
TYPEIDDY       SMFTIME so day-to-day counts can be compared.            
VMACID         The syntax for the new report is:                        
VMACIDDY                                                                
Dec  4, 2015     %ANALIDDY(READSMF=YES,PRINT=YES,PDBOUT=WORK);          
Dec  5, 2015                                                            
   Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.           
                                                                        
Change 33.289  z/OS only. If you used BLDSMPDB to build a MONTHLY PDB:  
BLDSMPDB      -If the 1st of the month fell on a Sunday then the code   
Dec  3, 2015   miscalculated the start of the last weekly and caused    
               the last few days of the month to be missing.            
              -If the 1st of the month did not match the start of the   
               week then the last few days were duplicated because the  
               logic looked for daily data GE then the start of the     
               week and should have looked for GT.                      
                                                                        
Change 33.288  Reserved Change.                                         
                                                                        
Change 33.287 -The PDB.CICDS CICS Dispatcher Statistics dataset now has 
ADOC110        variable DSxPCT='AA TCB*PERCENT*USAGE', the IBM estimate 
VMAC110        of each CICS TCB's percentage usage.                     
Dec  3, 2015  -ADOC110 now documents the new TCBs added in CICS/TS 2.2. 
                                                                        
====== Changes thru 33.286 were in MXG 33.12 dated Dec  1, 2015=========
                                                                        
Change 33.286  Six TYP1194L variables LxLCLLNKID and LxRMTLNKID were    
VMAC119        incorrectly changed from numeric to character in first   
Dec  1, 2015   33.12. They were corrected in final Dec 1 refresh.       
               All six are formatted with HEX8 format for consistency.  
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
Change 33.285  Cosmetic, eliminate non-impacting warning that numeric   
ASUMTALO       variable AVGDRIVE has different lengths in ASUMTALO and  
TRNDTALO       TRNDTALO, because an ancient statement in member ASUMTALO
Nov 30, 2015   specified LENGTH AVGDRIVE 4  while TRNDTALO invoked      
               VMXGSUM which sets LENGTH DEFAULT=&MXGLEN that is the    
               correct syntax to set stored length 5 on EBCDIC or 6 on  
               ASCII, which are the required lengths for SAS variables  
               that fully support 4-byte input fields.  Observed in QA. 
                                                                        
====== Changes thru 33.284 were in MXG 33.12 dated Nov 27, 2015=========
                                                                        
Change 33.284  Warning message in TYPE26J2 that the MXG created variable
VMAC26J2       INREASON is blank is removed; not all purge records have 
Nov 27, 2015   enough information to populate the created variable, e.g.
               JCL error in INTRDR populates only READTIME, JPURTIME and
               SYSREAD.                                                 
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
Change 33.283 -INVALID DATA for WORD5UP in BBBP ENDING UPTIME because   
VMACNMON       the expected HH:MM format is sometimes 'HH HRS' when the 
Nov 26, 2015   value is 'HH:00'.  The HRS text is now removed so the 11 
               hour value is valid eliminating the error message.       
              -NMON records missing data and the LF delimiter exist and 
               they cause strange errors.                               
               -One record with TYPE of DISKBSIZEAAA is clearly missing 
                data and an LF before the AAA, which is a new record    
                TYPE.  This record caused an INVALID ARRAY error because
                MXG tested for TYPE=:'DISKBKSIZE', starting with, for   
                possible numeric suffixes often used in NMON.           
               -Another record had only CPAAA, causing an UNKNOWN TYPE  
                log message.                                            
               -A third TYPE=LPAR has 22 valid fields but was missing   
                the LF separator and had a valid AAA record concat.     
                This record caused an INVALID INPUT error because MXG   
                expected numbers in the up to 24 fields in TYPE LPAR.   
              -Because NMON is character data, all numeric fields are   
               created with INPUT() functions, but now, with these bad  
               data records, the INPUT functions are now protected with 
               the ?? token to suppress the ERROR, PUT _ALL_, and LIST  
               log messages.                                            
              -Disk error messages "NRCOUNTERS NE DSKSEQNR" that were   
               cited as due to bad data in Change 31.164 are corrected. 
               They were due to new DISKBUSY1/DISKREAD1/etc objects that
               NMON created when there were more than 150 devices that  
               were NOT supported until now.                            
   Thanks to Steve McCulloch, TMX/CDS Group, CANADA.                    
                                                                        
Change 33.282  SMF 90 records contain the ENCRYPTED/MASKED UTOKEN value 
FORMATS        as documented in Change 33.189, which noted IBM does plan
VMAC90A        to change to the UNMASKED value, but the encryption logic
Nov 25, 2015   is only an Exclusive OR with '55'x and mapping the result
Nov 27, 2015   into a one byte character which is then INPUT as $EBCDIC,
Dec  1, 2015   so the TOKxxxxx variables in the TYPE90A dataset are now 
               plain text values if the field was MASKED.               
              -The 80-byte SMF90T37UTOKEN is decoded into its TOKxxxxx  
               variables, now set to LENGTH $8 (they are INPUT() with a 
               SUBSTR() which defaults to length of the input variable),
               and so it is no longer kept.                             
              -New FORMAT MGHEXNM was needed to map the XOR value to the
               character hex value for the output.                      
              -Dec 1: Error  +;  was corrected.                         
   Thanks to Peter Relson, IBM z/OS Development, USA.                   
                                                                        
Change 33.281  A valid WARNING was printed from an SQL step due to a    
VMXGSIZE       WHERE clause.  Logic reordered to eliminate the warning. 
Nov 24, 2015                                                            
                                                                        
Change 33.280  PDB.TYPE70 for z13 in SMT mode could have the wrong count
VMAC7072       in ZIPCPUS, ZIP70PAT, and ZIPUPTM because SMF70PAT was   
Nov 21, 2015   incorrectly added to ZIP70PAT when SMF70ONT is missing.  
   Thanks to Joachim Sarkoschitz, DATEV, GERMANY.                       
                                                                        
Change 33.279 -Support for DB2 Simulated Buffer Pool statistics segment,
ANALDB2R       creates new PDB.DB2STSBP dataset with per pool data, and 
ASUMDBSS       four sets of QBnSxxxx interval totals in PDB.DB2STATS and
EXDB2SBP       ASUMDBSS creates new ASUMDBSP summary dataset.           
IMACDB2       -MOBILEWORK programs QAMOB and MOBWRK02 required updates  
MOBWRK02       to support/protect this new dataset                      
QAMOB         -Buffer Hit Ratios for the SBP are created but set to a   
READDB2        missing value, pending data for validation.              
VMACDB2       -ANALDB2R compile fakers for QWxxxxDB were corrected.     
VMXGDBSS      -The names of tokens/datasets for SBP mirror STB:         
VMXGINIT          DB2STB    DB2SBP                                      
Nov 18, 2015      DB2STSTB  DB2STSBP                                    
Nov 22, 2015      DB2STAB   DB2STSB                                     
Nov 23, 2015      ASUMDBSB  ASUMDBSP                                    
Nov 26, 2015      MACSTAB   MACSTSB                                     
Dec 18, 2015      D2BPSIN   D2SBPIN                                     
                  D2SBPIN   D2SBPOU                                     
              -There is no count of pages-not-in-the-pool so there is no
               buffer hit ratio for the simulated buffer pool that I can
               calculate.  Variable QBSPREADS is the total number of    
               requests that caused a read.                             
   Thanks to Lai Fai Wong, Bank of America, USA.                        
                                                                        
Change 33.278  If you used INTERVAL=MONTH, MXGDURTM was missing for the 
VMXGDUR        31-day months, except December, when it was non-missing  
Nov 18, 2015   but was 41 days of seconds, because the statement        
                 IF MONTH IN(1.3.5.7.8.10,12) THEN MXGDURTM=41*86400;   
               should have been                                         
                 IF MONTH IN(1,3,5,7,8,10,12) THEN MXGDURTM=31*86400;   
               periods are not allowed, but do NOT create a SAS error.  
               This is old, present in MXG 30.09 but not in MXG 26.26.  
   Thanks to Chris Weston, SAS Institute ITRM, USA.                     
                                                                        
Change 33.277  If you tried to use Example TWO to create ASUMUOW, an    
IMACUOW        error resulted due to a misplaced percent sign; Example  
Nov 19, 2015   THREE did not tell you how to create "MYDATA", and while 
               Example FIVE did work, it was inconsistent with others.  
   Thanks to Chris Weston, SAS Institute ITRM, USA.                     
                                                                        
Change 33.276  RMF III variables GEILF4K and GEILP4K in dataset ZRBGEI  
VMACRMFV       were reversed in their INPUT order; GEILF4K precedes     
Nov 16, 2015   GEILP4K now.                                             
   Thanks to Kurt Gramling, Total Systems.                              
                                                                        
Change 33.275  Assemble/Link Edit all five MXG ASM programs for install.
ASMRMFV        The existing single ASM/LKED members are restructured so 
CICSIFUE       the ASM code is isolated from the JCL so the new JCLASMXG
EXITCICS       member will create all five loadlib members in one job.  
JCLASMXG       ASMRMFV  - Used in JCLRMFV to process RMF III VSAM file, 
MNVWIFUE                    output RMFBSAM read by TYPERMFV.            
MXGTMNT                     (Individual ASM/LKED is in JCLASM3/ASMRMFV) 
TMONEXIT       CICSIFUE - Used in TYPEDB2/TYPE110/TYPE112 to decompress 
Nov 16, 2015                IBM SMF records 100, 101, 102, 110, and 112 
Nov 23, 2015                SMF records.                                
Nov 27, 2015                (Individual ASM/LKED is in EXITCICS)        
               MNVWIFUE - Used in TYPEBBMQ to read compressed BBMQVSAM  
                           and in TYPECMFV to read BMC MainView data.   
                            (Individual ASM/LKED is in ASMMNVW)         
               MXGTMNT  - The MXG Tape Mount Monitor Program, read by   
                           TYPETMNT                                     
                            (Individual ASM/LKED is in ASMTAPEE)        
               TMONEXIT - Used in TYPETMO2 to decompress MONICICS       
                           TMON/CICS data.                              
                            (Individual ASM/LKED is in EXITMON6)        
               The original documentation comments are in appendices    
               at the end of JCLASMXG.                                  
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 33.274 -Enhancement for character data filtering for RMF Monitor 
ADOCRMFV       III CSR (Common Storage Remaining) table and other       
ASMRMFV        usability improvements.                                  
Nov 16, 2015  -These filters are intended for building ad hoc MXG RMF   
               III PDBs for studies avoiding the overhead of generating 
               a full CSR table based PDB.  They control which CSR table
               entries are output to the RMFBSAM file.                  
              -Four new filters are added to support CSR entry selection
               from this table to the RMFBSAM output file.  These       
               filters are effective only if the CSR table is selected. 
               They are applied in the order shown when multiple        
               different keywords are used.                             
                                                                        
               New Keyword    Aliases                                   
               ------------   ----------------------------------------- 
               CSRJOBNAME=    CSRJOBNA=, CSRJOBNM=,  CSRJOB=,   CSRJN=  
               CSRJESID=      CSRJESNO=, CSRJESNUM=, CSRJESNR=, CSRJID= 
               CSRAND         None                                      
               CSROR          None                                      
                                                                        
              -TUTORIAL:                                                
               Ranges of the form keyword=first:last may be used with   
               any of the above keywords except CSRAND and CSROR.       
                                                                        
               The colon character ':' is required for a paired range   
               specification.  All entries GE the first value and LE the
               last value are selected for output to the RMFBSAM file.  
                                                                        
               The first value may not exceed the last value in EBCDIC  
               collating sequence or an error is flagged.               
                                                                        
               Single unpaired values may be specified for a range      
               simply as keyword=first and in this case the colon ':' is
               omitted.                                                 
                                                                        
               Patterns may also be used with any of the above keywords 
               except CSRAND and CSROR and include one or more Wild Card
               characters to match the respective CSR data field.       
                                                                        
               A pattern contains one or more special Wild Card         
               characters as follows:                                   
                                                                        
               Wild                                                     
               Card   Matches                                           
               ----   ------------------------------------------------- 
               *      0 or more characters                              
               %      1 Non-blank character                             
               +      1 Numeric character (0-9)                         
               _      1 Alphabetic character or _  (a-z, A-Z, _)        
               .      1 National character (@, #, $)                    
               !      1 Special character (not a-z, A-Z, 0-9, @, #, $)  
               ?      A blank string if used by itself                  
               ?      1 Blank character (X'40') if used with any other  
                        characters                                      
                                                                        
               Ranges may not be wild carded.  If wild carded the range 
               value becomes a pattern instead and is processed as such.
                                                                        
               See Section 25 "Ranges and Patterns" in the ADOCRMFV     
               member or ASMRMFV source code for more details on usage  
               of ranges and patterns.                                  
                                                                        
              -CSRJOBNAME= selects CSR entries by 1-8 character z/OS    
               Job Name.  Job Name characters are validated to those    
               allowed by JCL syntax.  Both ranges and patterns with    
               wild cards may be specified.  Up to 64 ranges and 64     
               patterns are supported.  The default is CSRJOBNAME=ALL.  
                                                                        
              -Examples for CSRJOBNAME= :                               
               CSRJN=PROD1234:PROD5678 selects only address spaces with 
               a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a     
               range.  Note use of the keyword alias CSRJN for coding   
               convenience.                                             
                                                                        
               CSRJOBNAME=.* is a pattern that selects only address     
               spaces with a Job Name that begins with a national       
               character.                                               
                                                                        
               CSRJOBNAME=*++ is a pattern that selects only address    
               spaces with a Job Name that ends with 2 numeric digits.  
                                                                        
               CSRJOBNAME=ABC:ABC88888 is a range that selects only     
               address spaces with a Job Name that is GE 'ABC     ' and 
               LE 'ABC88888'.                                           
                                                                        
              -CSRJESID= selects CSR entries by 8 character JES Job     
               Identification.  Both ranges and patterns with wild cards
               may be specified.  Since a JES Id is one subsystem       
               character followed by 7 digits or three subsystem        
               characters followed by 5 digits not all pattern          
               characters may be used with this keyword.                
                                                                        
               See Section 25 "Ranges and Patterns" in the ADOCRMFV     
               member or ASMRMFV source code for more details on usage  
               of ranges and patterns.                                  
                                                                        
              -For convenience any leading zeros in the numeric portion 
               of the JES Id may be omitted and will be filled in       
               automatically.  Up to 64 ranges and 64 patterns are      
               supported.  The default is CSRJESID=ALL.                 
                                                                        
              -Examples for CSRJESID= :                                 
               CSRJID=J0000100:J0001123 is a range that selects all     
               address spaces with batch JES Id numbers GE 100 and LE   
               1123.  Note use of keyword alias CSRJID for coding       
               convenience.                                             
                                                                        
               CSRJID=J100:J1123 is a range that selects the same       
               address spaces as above with the leading zeros omitted   
               for coding convenience.                                  
                                                                        
               CSRJESID=JOB12345:JOB32001 is a range that selects all   
               address spaces with batch JES Id numbers GE 12345 and LE 
               32001 for installations with 5 digit JES Id numbers as a 
               range.                                                   
                                                                        
               CSRJESID=J1* is a range that selects all address spaces  
               with a JES ID that begins with 'J1'.  This would include 
               J1000000 through and including J1999999.                 
                                                                        
              -CSRAND (default) indicates that selection results from   
               the two different CSR filter keywords are logically      
               ANDed.                                                   
                                                                        
              -CSROR indicates that selection results from the two      
               different CSR filter keywords are logically ORed.        
                                                                        
              -Examples of CSRAND/CSROR:                                
                                                                        
               With CSRAND (default) in effect:                         
               CSRJESID=J10*    CSRJOBNAME=XYZ*                         
               are two patterns that select ONLY jobs whose JES ID      
               begins with 'J10' AND Job Name begins with 'XYZ'.        
               CSRAND provides more restrictive CSR entry selection.    
                                                                        
               With CSROR in effect:                                    
               CSRJESID=J10*    CSRJOBNAME=XYZ*                         
               are two patterns that select jobs whose JES ID begins    
               with 'J10' OR Job Name begins with 'XYZ'.  CSROR provides
               less restrictive CSR entry selection.                    
                                                                        
              -Selection results from repeats of the same CSR filter    
               keyword are always logically ORed.                       
              -The order of CSR filter application is:                  
               1) CSRJOBNAME=                                           
               2) CSRJESID=                                             
              -New support for the concept of multi-table selection with
               filters JOBNAME= (alias JOB=) and JESID= (alias JID=) to 
               allow selection by Job Name and/or JES Identification    
               jobname from both the RMF Monitor III ASI and CSR tables 
               with one keyword.                                        
              -This is a convenience feature to avoid having to code the
               Job Name or JES ID selection parameters twice when the   
               same jobs from both tables are of interest.              
              -Both the ASI and CSR tables must be selected for these   
               multi-table selection keywords to function completely.   
               Otherwise, only entries from the one selected table are  
               filtered.                                                
                                                                        
               Note that most RMF III tables do not contain common      
               character data fields, but in this case the ASI and CSR  
               do.                                                      
                                                                        
              -Example of JOBNAME= :                                    
               JOBNAME=ABC* or JOB=ABC* is equivalent to coding         
               ASIJOBNAME=ABC*                                          
               CSRJOBNAME=ABC*                                          
                                                                        
              -Example of JESID= :                                      
               JESID=JOB01000:JOB01999 or JID=JOB01000:JOB01999         
               is equivalent to coding                                  
               ASIJESID=JOB01000:JOB01999                               
               CSRJESID=JOB01000:JOB01999                               
                                                                        
               NOTE: If a job has ended before the selected MINTIME     
               intervals it will ONLY appear in the MXG ZRBCSR data set 
               and NOT the MXG ZRBASI data set.                         
                                                                        
              -Reduced processing overhead for CSR tables.              
              -RMFV056* (*=I,W,E) message is no longer issued twice when
               a single unpaired range value is in error.               
              -All invalid characters detected in a pattern are now     
               shown in multiple RMFV056* (*=I,W,E) messages.  Before   
               only the first character in error was displayed.  This   
               could result in repeated runs of ASMRMFV just to find all
               the invalid characters in a pattern.                     
              -The error message generation process has been rewritten  
               for improved efficiency, consistency, clarity, and       
               usability.                                               
                                                                        
               For example, the problem data area in RMFV004* and       
               RMFV056* messages that shows the text in error is        
               expanded from 24 to 63 characters.  Also all length      
               errors are displayed in the same format.                 
                                                                        
              -Added new documentation Section 26 "ASMRMFV and SAS PDB  
               Relationships" that explains which RMF III tables        
               correspond to which eventual MXG SAS datasets.  If the   
               required RMF III table is not selected in ASMRMFV the MXG
               dataset will have zero observations.                     
                                                                        
               All ASMRMFV users should review this useful information. 
              -Old documentation Section 26 "Summary" is now Section 27.
              -The PATTERR= parameter was not effective because it was  
               not processed until all parameters were read.  This was  
               too late because pattern error handling must occur during
               the actual parameter process as patterns are being       
               scanned.                                                 
              -PATTERR= parameter handling now occurs immediately when  
               found in the JCL PARM field or SYSIN DD stream including 
               severity tailoring of message RMFV056* (*=I,W,E).        
              -The default value for PATTERR= is now PATTERR=ABEND.     
               Before the default was PATTERR=WARN.  An incorrect       
               pattern value could result in a waste of processing      
               resources building an MXG PDB that did not contain the   
               data desired and so that default was inappropriate.      
              -The documentation is updated to make it clear that       
               PATTERR= applies to BOTH pattern AND range errors.  There
               is no RANGEERR= parameter.                               
              -DISK is now supported as a value alias for the DEVTYPE=  
               keyword in DVT table filtering so that DEVTYPE=DISK may  
               be used.  Any truncation of 'DISK' as a character value  
               (DIS,DI,D) is also allowed.                              
              -DVTT= was missing in documentation as an alias for       
               DEVTYPE= although it was always supported.               
              -First message RMFV001I now also displays the system GMT  
               offset as GMT OFFSET=-hh:mm:ss or GMT OFFSET=+hh:mm:ss as
               extracted from the z/OS Communication Vector Table (CVT) 
               in addition to the existing current date and time of     
               ASMRMFV beginning execution.                             
              -A new RMFV001I message shows the ASMRMFV beginning       
               execution date and time in GMT.                          
              -A MAXDSNAMES= value exceeding maximum supported &DSNMAX  
               value was not flagged as an error.                       
              -Message RMFV034S did not correctly display the number of 
               used table entries when a range or pattern table was     
               exhausted.                                               
              -Several documentation Sections are updated to support    
               the above changes:                                       
               Section  5 "Input Data Selection Parameters"             
               Section  8 "Error Handling Parameters"                   
               Section 12 "Messages"                                    
               Section 13 "Filtered Records"                            
               Section 17 "Abend Reason Codes"                          
               Section 25 "Ranges and Patterns"                         
               Section 26 "ASMRMFV and SAS PDB Relationships" (NEW)     
               Section 27 "Summary"                                     
                                                                        
Change 33.273  DB2 SMF 102 Trace IFCID=109 INVALID DO LOOP CONTROL ERROR
VMAC102        was caused by unexpected/invalid QWT02R10/L/N triplet    
Nov 12, 2015   with all zeros; which is the only segment in the 109 with
               QW0109RC, the Bind Return code, so I presumed it was the 
               purpose for the record and did not test for the existence
               of a non-zero count.  Now, I do test, and still output an
               observation, which will have QW0109RC a missing value.   
   Thanks to Karl-Olaf, JN Data, DENMARK.                               
                                                                        
Change 33.272  Cosmetic change to eliminate numeric conversion messages.
ASUMTALO                                                                
VMXGRMFI                                                                
Nov 11, 2015                                                            
                                                                        
Change 33.271  TYPETMO2 processing of compressed records did not print  
VMACTMO2       the warning message if the internal MXG decompression is 
Nov 11, 2015   used on z/OS instead of the EXITMON6 Infile Exit.        
                                                                        
Change 33.270  Variable SMF14ALIAS, the Alias Data Set Name in TYPE1415,
VMAC1415       added by z/OS 2.2 and MXG 33.01, was spelled SMR14ALIAS  
Nov 10, 2015   in the KEEP= list so it was not kept.  With MXG 33.01+   
               use  MACRO _KTY1415 SMF14ALIAS %  in your IMACKEEP to    
               keep the variable until you drop in the next MXG Version.
               Field was added by APAR PI69296.                         
   Thanks to Robert Obee, IMS Health, USA.                              
                                                                        
Change 33.269  UTILBLDP changes the default to ECHO=YES, so that the    
UTILBLDP       generated code is automatically printed on the SAS log,  
Nov  9, 2015   so we can examine the output without requesting a rerun  
               to enable ECHO, if there is a problem in execution.      
                                                                        
Change 33.268 -Support for SEVEN USER-USER fields in CICSTRAN, and      
IMACICVY       several other unique fields.                             
IMACICVZ       To enable these user fields, you need to specify         
IMACICWA         %LET NREXCLUSER=7;                                     
IMACICWB         %INCLUDE SOURCLIB(UTILEXCL);                           
IMACICWC         _BLDDICT                                               
IMACICWD         _BLDEXCL                                               
IMACICWE         _RPTEXCL                                               
IMACICWF      -Variable JOB is added to CICSTRAN.CICSTRAN (the JOB name 
IMACICWG       of the CICS region).                                     
IMACICWH                                                                
IMACICWI                                                                
IMACICWJ                                                                
IMACICWL                                                                
IMACICWM                                                                
IMACICWN                                                                
IMACICWP                                                                
IMACICWQ                                                                
UTILEXCL                                                                
VMAC110                                                                 
VMXGINIT                                                                
Nov 11, 2015                                                            
   Thanks to Jens Ove Stogaard, NORDEA, SWEDEN.                         
                                                                        
Change 33.267  SMF 120 dataset TYP120JI only output the first instance; 
VMAC120        the offset for the INPUT was not updated by the length.  
Nov  6, 2015                                                            
   Thanks to Elie Sawaya, Royal Bank of Canada, CANADA.                 
                                                                        
Change 33.266  MXG 33.11 only. ERROR:  VARIABLE SYTPN NOT FOUND, only if
VMACXAM        _SXAM is used to sort the zVPS datasets; SYTPN should not
Nov  6, 2015   be in the new _BXAMCU2 and _BXAMCUV "By List" macros as  
               it does not exist in those two new datasets.             
   Thanks to Matthew Brooks, OPM, USA.                                  
   Thanks to Robert Richards, OPM, USA.                                 
   Thanks to Leslie W. Mitchell, OPM, USA.                              
                                                                        
Change 33.265  ThruputManager dataset TPMSLM variables TPMSLXGF/TPMSLXGN
VMACTPMX       are TODSTAMP8. STCK datetimes, so their incorrect INPUT  
Nov  6, 2015   with &PIB.8.6 and subsequent divide by 4096 was invalidly
               creating dates in 2076, since that is a duration value   
               (same as MSEC8) rather than a datetime value.            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.264  Support for APPTUNE 11.2 INCOMPATIBLE changes to the 8005
VMAC102        IFCID record. Some truncated 8005 records are created    
Nov  5, 2015   that MXG detects and reports the first instance, and the 
Nov 23, 2015   vendor reports a correction will be provided.  Datasets  
               T1028004, T1028005, and T102800B have been data-tested.  
   Thanks to Rudi Claes, KBC, BELGIUM.                                  
                                                                        
Change 33.263  Support for User CICS field BTMASK.                      
IMACAAAA                                                                
IMACICVX                                                                
UTILEXCL                                                                
VMAC110                                                                 
Nov  4, 2015                                                            
                                                                        
Change 33.262  Support for SMF 119 subtypes 41-44 (previously, zero obs)
FORMATS        and for the below fields added in z/OS 2.1 or earlier    
VMAC119        that had been overlooked.                                
Nov  6, 2015  -Subtype 2, dataset TYP11902:                             
                 TTLCLSMCLINKID='LOCAL*SMC-R*LINK*ID '                  
                 TTRMTSMCLINKID='REMOTE*SMC-R*LINK*ID'                  
                 TTSMCREASON   ='SMC-R*LINK*FAILURE*REASON*CODE'        
                 TSMCFLAGS     ='SMC-R*FLAG'                            
                 FORMAT $MG119RC is created to decode the Reason Code.  
              -Subtype 5, dataset TYP11905:                             
    TSSMCRACTIVEOPENED ='ACTIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'     
    TSSMCRACTLNKOPENED ='ACTIVE*SMC-R*LINKS*OPENED'                     
    TSSMCRCONNCLOSED   ='CLOSED*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'     
    TSSMCRCURRESTAB    ='TCP*CONNECTIONS*ACROSS*SMC-R LINKS'            
    TSSMCRCURRESTABLNKS='CURRENT*ACTIVE*SMC-R*LINKS'                    
    TSSMCRINRSTS       ='SMC-R*INBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE' 
    TSSMCRINSEGS       ='SMC-R*INBOUND*WRITE*OPERATIONS'                
    TSSMCRLNKACTTIMEOUT='SMC-R*LINK*ACTIVATION*TIMEOUTS'                
    TSSMCRLNKSCLOSED   ='SMC-R*LINKS*CLOSED'                            
    TSSMCROUTRSTS      ='SMC-R*OUTBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE'
    TSSMCROUTSEGS      ='SMC-R*OUTBOUND*WRITE*OPERATIONS'               
    TSSMCRPASLNKOPENED ='PASSIVE*SMC-R*LINKS*OPENED'                    
    TSSMCRPASSIVEOPENED='PASSIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'    
    TSTCEPHPORTAVAIL   ='AVAILABLE*TCP*EPHEMERAL*PORTS'                 
    TSTCEPHPORTEXH     ='BIND*FAILS*NO TCP*EPHEMERAL*PORTS'             
    TSTCEPHPORTINUSE   ='TCP*EPHEMERAL*PORTS*CURRENTLY*IN USE'          
    TSTCEPHPORTMXUSE   ='MAXIMUM*TCP*EPHEMERAL*PORTS*USED'              
                 TSUDPBFA='BIND*FAILS*NO*UDP*EPHEMERAL'                 
                 TSUDPAVA='AVAILABLE*UDP*EPH*EPHEMERAL'/                
                 TSUDPUSE='INUSE*UDP*EPH*EPHEMERAL'                     
                 TSUDPMAC='MAXIMUM*UDP*EPH*EPHEMERAL'/                  
                 TS6CEALO='ECSA*CURRENT'                                
                 TS6CENIU='ECSA*FREE'                                   
                 TS6CPALO='PRIVATE*CURRENT'                             
                 TS6CPNIU='PRIVATE*FREE'                                
                 TS6SMCFC='SMCR*FIXED*CURRENT'/                         
                 TS6SMCFM='SMCR*FIXED*MAX'                              
                 TS6SMCSC='SMCR*SEND*CURRENT'                           
                 TS6SMCSM='SMCR*SEND*MAX'                               
                 TS6SMCRC='SMCR*RECV*CURRENT'                           
                 TS6SMCRM='SMCR*RECV*MAX'                               
              -Subtype 6, dataset TYP11906:                             
                 IFQDXNET='PHYSICAL*NETWORK*ID'                         
              -Subtype 7, dataset TYP11907:                             
                 FFSESSID='FTP*ACTIVITY*SESSION*ID'                     
              -Subtypes 41-44, all datasets are now populated.          
              -Subtypes 97.  Variable SSH_FSPATH2 now INPUT and kept;   
               The three variables SSH_FSPATH/FSPATH1/FSPATH2 should    
               have been named FCPATH to match their IBM field names.   
              -Variables EXTWTRNM,JESUBSYS,JOB,LOCLINFO,READTIME are    
               not kept in datasets TYP11941/42/43/44/4L, where they    
               don't exist and should never have been kept.             
   Thanks to James T. Sherpey, Bank of America, USA.                    
   Thanks to David M. Wrobel, Bank of America, USA.                     
   Thanks to Jennifer D. Ayers, West Virginia State Government, USA.    
                                                                        
Change 33.261  Internal code change, to make user tailoring easier.     
VMAC7072       In dataset TYPE72GO, only two variables are kept for the 
Nov  4, 2015   calculated percentage variables, PCTxxxxx and VALDSAMP,  
               since the numerator value R723yyyy can be re-calculated  
               in the EXTY72GO exit and KEPT in the _KTY72GO macro in   
               your tailored IMACKEEP.  But by changing the variable    
               name in the INPUT to the R723yyyy field name and using it
               for the PCTxxxxx calculation, those R723yyyy variables   
               can be added to TYPE72GO with only _KTY72GO tailoring, so
               the EXTY72GO tailoring is not required. The code for the 
               TYPE72MN dataset was similarly revised internally.       
   Thanks to Erling Andersen, SMT, DENMARK.                             
                                                                        
====== Changes thru 33.260 were in MXG 33.11 dated Nov  2, 2015=========
                                                                        
Change 33.260  ANALSMDU report analyzes an SMF file for duplicate data  
ANALSMDU       showing if/when duplicate data exists in separate dump   
Nov  2, 2015   groups, with record numbers so duplicates can be removed,
               and tabulating if duplicate data exists in individual SMF
               dumps.                                                   
   Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.           
                                                                        
Change 33.259  Support for zVPS Release 4230 for z13 is SMT mode        
EXXAMCUV       creates two new datasets:                                
EXXAMCU2         dddddd   dataset   description                         
IMACXAM          XAMCU2   XAMCU2                                        
VMACXAM          XAMCUV   XAMCUV                                        
VMXGINIT                                                                
Oct 30, 2015                                                            
                                                                        
Change 33.258  Support for CICS USER field TORM.                        
UTILEXCL                                                                
VMAC110                                                                 
Oct 30, 2015                                                            
   Thanks to Don Deckard, Wal*Mart, USA.                                
   Thanks to Cheryl Jordan, Wal*Mart, USA.                              
                                                                        
Change 33.257  This change is REQUIRED for CICS/TS 5.3.  The final new  
UTILEXCL       CICS/TS 5.3 field, as always inserted, INCOMPATIBLY,     
VMAC110        DSAPTHWT, is now supported, supported, creating variables
Oct 29, 2015     DSAPTHCN='WAIT COUNT*FOR DSA*PATH'                     
                 DSAPTHTM='WAIT TIME*FOR*DSA*PATH'                      
               Field was added in Beta 14.                              
   Thanks to Anthony Hirst, Wells Fargo, USA.                           
                                                                        
Change 33.256  CICS Count of TCB Change Mode Requests was originally in 
VMAC110        IBM CMODIDNT=248 CHMODECT, a four byte counter, but that 
Oct 29, 2015   was replaced in CICS/TS 1.3 with CMODIDNT=247 DSCHMDLY   
               which is an 8-byte wait duration plus update counter that
               created these two variables that are now re-labeled:     
                DSCHMDCN='DSCHMDLY*COUNT*TCB*CHANGE MODE*REQUESTS'      
                DSCHMDTM='DSCHMDLY*DURATION*CHANGE MODE*REQUESTS'       
                                                                        
Change 33.255  UTILEXCL failed with ARRAY EXCEEDED when more than 999   
UTILEXCL       connectors exist; arrays increased to 1999.              
Oct 27, 2015                                                            
   Thanks to Erling Andersen, SMT, DENMARK.                             
                                                                        
Change 33.254  MXG 33.09-33.10. Using WORK=SASWORK caused TYPE7072 code 
VMAC7072       to fail; temporary datasets TYPE70EC and TYPE70EN did not
VMXGINIT       have &Wdddddd/&Pdddddd in their _Wdddddd/_Ldddddd tokens,
Oct 26, 2015   so they were written to //WORK instead of //SASWORK, no  
Oct 31, 2015   error, but inconsistent.  Change 33.217 for z/13+SMT 70's
               revised MXG code for TYPE70EC/EL/EN datasets had replaced
               _WTY70EN with DATA TYPE70EN (the same when WORK=WORK),   
               but the VMXGDEL deleted DATASET WORK.TYPE70EN when it    
               should not have.  There is nothing illegal about setting 
               Options WORK=SASWORK, and it was previously supported,   
               but it had not been recommended by MXG, and is unneeded  
               since //WORK can be multi-volume.                        
   Thanks to Scott Bickel, Kansas State Government, USA.                
                                                                        
Change 33.253  Added processing of TYPE32 records to tabulate TSO MSU   
SAGANAL        for each COMMAND in new Report 32.  Report 19, PROC PLOT 
Oct 30, 2015   was removed from _RPTALL as it was only used in testing. 
Nov  3, 2015   New Report 32 tabulates HOURLY TSO MSU for NAT commands. 
                                                                        
Change 33.252  IMS Transaction dataset TYPE56FA does not contain SYSTEM,
TYPEIMST       the MVS SYSTEM ID, but you can pass the SYSTEM name into 
VMACIMS        SAS from each JOB's JCL using the SYSPARM() statement:   
Oct 22, 2015   // EXEC MXGSAS94,OPTIONS='SYSPARM="SYSA"'                
               or the SYSTEM can be set with SYSPARM in your //SYSIN    
                 OPTIONS SYSPARM="SYSA";                                
               Then, inside MXG first-time logic that creates ZDATE and 
               ZTIME, retrieves that value with  SYSTEM=SYSPARM();  and 
               variable SYSTEM is RETAINED and OUTPUT in each dataset.  
              -SHIFT was added to all IMS datasets based on IMSSTCK.    
               Only VMACIMS was changed; TYPEIMST is just for reference.
              -For years, the only JCL for SYSPARM that worked had EIGHT
               quotes before and FIVE after the text, and I have a 2013 
               example, but that syntax now fails with SAS 9.4, and SAS 
               now documents the much cleaner double quote syntax.      
               Both IMS and BVIR require you to supply the SYSTEM thru  
               SYSPARM=, and other members use SYSPARM to enable debug. 
               All of the JCL examples with OPTIONS=SYSPARM= now use the
               double quotes for both instream and in JCL.              
              -Variable ZTIME is added to all IMS datasets that have the
               ZDATE variable now.                                      
   Thanks to David A Bernhardt, Verizon, USA.                           
                                                                        
Change 33.251  CICSTRAN variable OSTART=ORIGINATING*TASK*START*DATETIME 
UTILEXCL       was on GMT; MXG overlooked the need to convert it to the 
VMAC110        local time zone.                                         
Oct 20, 2015                                                            
   Thanks to David Shaw, M & T Bank, USA.                               
   Thanks to Douglas Donoho, M & T Bank, USA.                           
                                                                        
                                                                        
====== Changes thru 33.250 were in MXG 33.10 dated Oct 20, 2015=========
                                                                        
Change 33.250 -SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED RECORD LENGTH  
VMAC102        because QWT02R2L is two bytes shorter than the actual    
Oct 18, 2015   DB2 10.1 records.                                        
              -SMF 102 IFCID 220 INVALID ARGUMENT appears to be a truly 
               invalid record, with DSNAME where DDNAME should be.  The 
               error is circumvented by validating the DHMS arguments   
               while the record is investigated.  Variable QW0220OT is  
               the datetime stamp being calculated from characters, and 
               will be missing for invalid input, without the error.    
   Thanks to Joe Babcock, General Motors, USA.                          
                                                                        
Change 33.249  Decoding of DEVCLASS=41 now identifies specific CTC type:
VMACUCB           DEVTYPE    DEVICE        Description                  
Oct 15, 2015      previous   CTC                                        
                    05X      CTC-OSA        OSA                         
                    06X      CTC-OSAD       OSA DIAG DEV                
                    07X      CTC-IQD        HIPERSOCKETS                
                    09X      CTC-OSAN       OSA ZBX NETWK               
                    0AX      CTC-OSAM       OSA ZBX MGMT NETWK          
                    32X      CTC-FIC        FICON                       
                   other     CTC                                        
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.248  Support for zVSE/Power Version 9 Release 2 Accounting.   
TYPEDOS        Only minor changes were required, including protection   
Oct 13, 2015   for SEGCNT larger than the number of device segments in  
               the record (caused STOPOVER).                            
                                                                        
Change 33.247 -If you use UTILEXCL and have more than four "triplets":  
VMAC110         WARNING: THE QUOTED STRING CURRENTLY BEING PROCESSED HAS
Oct 14, 2015    BECOME MORE THAN 262 CHARACTERS message is printed.     
               This warning has NO impact.  Change 33.203 added the text
               in MACRO _CICXLTR (the list of "triplets" in IMACEXCL) to
               MXG diagnostic PUT statements about EXCLUDED fields. Each
               triplet test is one line of text so four triplets exceed 
               a SAS internal limit of 262 character for quoted text in 
               PUT statements in macro resolution. Change 33.203 used   
                 $LENGTH CICXLTR $32000;                                
                 %LET CICXLTR=%QUOTE(_CICXLTR);                         
                 CICXLTR=SYMGET('CICXLTR');                             
               to store the text in macro variable &CICXLTR, and then   
               used  "&CICXLTR"  to print the text in the PUT statement,
               but that's the macro resolution causing the warning!     
               Now, by using                                            
                 CICSXLTR=RESOLVE('_CICXLTR');                          
               to directly store the old-style macro text into the data 
               step variable CICSXLTR, that variable can be used in the 
               PUT statement, with no macro resolution needed and hence 
               no warning message.   Sites with SAS 9.1 may need to     
               change RESOLVE to COMPRESS. Contact support@mxg.com.     
               This shows how easy it is to store the text contents of  
               an old-style substitution macro into a variable.         
              -CICS/TS 5.3, close comment missing for TSQIOSCN in the   
               INPUT statement, causing new-in-5.3 variables in CICSRDQU
               Resource dataset TSQGESTM/GESCN/PUSTM/PUSCN/GESBY/PUSBY  
               to be wrong.                                             
              -CICS/TS 5.2 MNSEGCL=5 records with MNR5LENT=96 caused    
               STOPOVER because MXG expected 104 (5.3 value).           
                                                                        
Change 33.246 -Using UTILBLDP with BUILDPDB=YES, if you suppressed type 
UTILBLDP       6, 26, or 30, the job failed in BUILD005 when it tried   
ZTILBLDP       to process the non-existent datasets.  Now, if any of the
Oct 20, 2015   datasets are not created, then BUILD005 is suppressed,   
               and warning message is printed.                          
              -A second execution of UTILBLDP in the same SAS Session   
               failed with old-style macro errors that are now resolved 
               and UTILBLDP can be re-executed as often as needed.      
              -The changes to support second execution were extensive   
               and thus extensively tested, but, just in case, the prior
               UTILBLDP from MXG 33.09 is stored in ZTILBLDP.           
   Thanks to Michael Reines, Decadis, GERMANY.                          
                                                                        
Change 33.245  Support for OMEGAMON ATF IMS Log Record LCODE A0 records:
EXATFA0          dddddd  dataset  description                           
IMACATF          ATFA0   IMSATFAO  ATF IMS LCODE A0                     
TYPEATF          ATFDB   IMSATFDB  ATF IMS DBD                          
TYPSATF          ATFDL   IMSATFDL  ATF IMS DLI DB                       
TYPEATFI         ATFDT   IMSATFDT  ATF IMS DLI TM                       
TYPSATFI         ATFD2   IMSATFD2  ATF IMS DB2                          
VMACATF          ATFMQ   IMSATFMQ  ATF IMS MQ                           
VMACIMS          ATFOA   IMSATFOA  ATF IMS OTHER A                      
VMXGINIT         ATFOB   IMSATFOB  ATF IMS OTHER B                      
Oct 19, 2015  -Application Trace Facility is a component of Omegamon XE 
Nov 17, 2015   for IMS v531. Detail trace data from intercepts capture  
               application execution for IMS related threads, including 
               DB2 and MQ API calls from an IMS application. The detail 
               data, possibly millions of intercepts per transaction, is
               summarized into new IMS LOG A0 record.  It's unlikely to 
               trace everything always, so this is not a replacement for
               the IMS 56FA Log Record (TYPEIMST) for IMS chargeback and
               response/resource reporting, but there is more data in   
               ATF - notably the DBD information - than in the 56FA, so 
               if selectively enabled for trouble children, it might be 
               a useful source for IMS trouble shooting.                
              -TYPEATFI reads IMSLOG format records, TYPEATF reads the  
               alternate destination, ATFLOG, if that option is chosen. 
              -MXG member TYPEIMS7 is updated to process ATF records if 
               found along with all other IMS Log records.              
              -The IBM default is A0, but that can be changed with the  
               MACRO _IDATF using %LET MACKEEP= tailoring in //SYSIN.   
              -ATF replaces the old ITRF component of Omegamon/XE.      
              -This is the support for Phase I.  Additions are coming.  
              -Nov 17:  INPUT @LOCVARSEG+ATFXSNzzO syntax is REQUIRED   
               because ATFXSNzzO offset can be zero, and the SAS syntax 
               INPUT @A+B is NOT the same as INPUT @B+A and the first   
               variable MUST ALWAYS BE NON-ZERO.  When in doubt, use    
               LOC=A+B; INPUT @LOC.                                     
                                                                        
Change 33.244  Unused Change Number.                                    
                                                                        
Change 33.243  RACF Type 80 records don't have variable SUBTYPE because 
ANALID         the RACFEVNT value is used instead, but now, RACFEVNT is 
FORMATS        INPUT in the SMF Header processing and stored in SUBTYPE 
UTILBLDP       so that the ANALID report will tabulate (and describe,   
VMACSMF        using the updated SMFID format) each type 80 subtype.    
Oct 10, 2015   And, UTILBLDP selection by SUBTYPE (WANTSMF=80.02) is now
               supported for ID=80 records.                             
                 NEVER USE TYPE80/TYPS80, ALWAYS USE TYPE80A/TYPS80A.   
                                                                        
Change 33.242  Support for z/VM 6.3.15.0 VXSYSPRT (0.02) z13 SMT mode.  
VMACVMXA       New SMT-related variables added to the end of the record.
Oct 10, 2015   But: See Change 33.299, REQUIRED.                        
                                                                        
Change 33.241  A SUM statement is added to the audit report of datasets 
PDBAUDIT       in your BUILDPDB that reports the total number of pages, 
Oct  9, 2015    variables, size, and bytes in each PDB data library.    
                                                                        
Change 33.240  TYPE30xx device summary variables for non-existent device
IMAC30IO       types (EXCP3350/IOTM3350) can be dropped from all TYPE30s
Oct  9, 2015   and PDB.JOBS and PDB.STEPS by tailoring IMAC30IO to save 
               disk space (one PDB reduced 400MB from 2500MB to 2100MB).
               A new example in comment block can be enabled to keep    
               only the variables for current device types.             
                                                                        
Change 33.239  Some TYPE70 variables can't be DROPped using _KTY70 with 
VMAC7072       DROP= because the TYPE70 dataset is not created directly 
Oct  8, 2015   as SMF is read (when _KTY70 is used for TYPE70SP). TYPE70
               is created from TYPE70SP and TYPE70PR with multiple DATA 
               DATA steps and Split Record processing.  Using _KTY70    
               also has a risk of dropping a variable needed in the data
               steps that follow.  This change creates _KTY70DR, a null 
               old-style MACRO that can be used to drop any variables in
               TYPE70 dataset, safely.  This syntax in your //SYSIN:    
                 %LET MACKEEP= MACRO _KTY70DR DROP= IF: VF: APPC: %  ;  
               drops all variables starting with IF, VF, or APPC.       
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.238  Support for RACF Flat File of IRRDBU00 record type 1560  
EXRA1560       creates new dataset                                      
IMACRACF        DDDDDD DATASET  DESCRIPTION                             
VMACRACF        RA1560 RACF1560 GENERAL RESOURCE CERTIFICATE INFORMATION
VMXGINIT        CERTN_NAME       ='GENERAL*RESOURCE*NAME'               
Oct  8, 2015    CERTN_CLASS_NAME ='GENERAL*RESOURCE*PROFILE*CLASS'      
                CERTN_ISSUER_DN  ='ISSUERS*DISTINGUISHED*NAME'          
                CERTN_SUBJECT_DN ='SUBJECTS*DISTINGUISHED*NAME'         
                CERTN_SIG_ALG    ='CERTIFICATE*SIGNATURE*ALGORITHM'     
   Thanks to Robert Miles Standish, UBS, USA.                           
                                                                        
Change 33.237  Support for EDA v7706 (INCOMPATIBLE, two existing 8-byte 
VMACEDA        user fields were expanded in place to 20 bytes).  There  
Oct  6, 2015   is no version field in their record; the length of the   
               record for each subtype is now used to create EDAVERS to 
               read either the new or old version records transparently.
   Thanks to Valentine Wudarczyk, BNYMellon, USA.                       
                                                                        
Change 33.236  DB2 zPARM QWP4xxxx fields marked (S)-SERVICEABILITY were 
VMAC102        not always kept, but IBM is now using these three fields 
Oct 14, 2015     QWP4INLP='INLISTP'                                     
                 QWP4MXOS='MAX*OPT*STOR'                                
                 QWP4SHDE='SUPPRESS*HINT*SQLCODE*DYN'                   
                 QWP4XMLO='XML*PROCESSING*OPTIONS'                      
               The first two were kept but unlabeled.  Now all (S) are  
               kept and labeled in T102S106 dataset. The first six have 
               actual labels, the others have their name as LABEL.      
                 QWP4ACCS QWP4ADMT QWP4INLP QWP4MXOS QWP4SHDE QWP4XMLO  
                 QWP4AST  QWP4CDE1 QWP4COC1 QWP4COC2 QWP4CTHR QWP4CUT   
                 QWP4FLKT QWP4LTDM QWP4MQTH QWP4MS4A QWP4MXCE QWP4MXOC  
                 QWP4MXOE QWP4MXTB QWP4PLIM QWP4RMTI QWP4SCLC QWP4SCTM  
                 QWP4SELD QWP4SPC  QWP4SPS  QWP4STHR QWP4TJTH QWP4TTRS  
                 QWP4ULB2 QWP4ULFR QWP4ZUT                              
              -Variables QWP4ACCS and QWP4DFID character values were not
               correct when test was EBCDIC, and QWP4OZTM is now numeric
               datetimestamp instead of $CHAR8. hex value.              
   Thanks to Lai Fai Wong, Bank of America, USA.                        
                                                                        
Change 33.235  Documentation. RED ALERT APAR OA48941 IS REQUIRED BY ALL 
VMAC74         z/OS SITES and MUST BE INSTALLED PRIOR TO DEC 15 2015 to 
Oct  6, 2015   prevent failure at IPL if the APAR is NOT installed.     
               The error is in Unicode Service Conversation iconv()     
               calls which is NOT USED IN MXG. but TELNET and many other
               programs are impacted.                                   
                                                                        
Change 33.234  Change 33.155 added R744SNAM to TYPE74HO dataset, which  
VMAC74         accidentally corrected an unreported error in the NODUP  
Oct  4, 2015   sort to create PDB.TYPE74HO: false duplicates were being 
               deleted, so the prior PDB.TYPE74HO dataset was incorrect.
               The number of obs correctly increased with this change.  
               And R744CNAM and R744SNAM are added to the end of the    
               _BTY74HO BY List to formally correct the NODUP sort.     
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.233  Support for APAR OA46136 that adds File Transfer Section 
VMAC6          with IP Address and Port Number to PSF-created SMF 6.    
Oct  1, 2015   No change was required; fields automatically INPUT/KEPT  
               when the section exists.                                 
                                                                        
Change 33.232  Support for Thruput Manager VARNAME=$ORIGIO NOT FOUND    
VMACTPMX       message creates new ORIGIO='ORIGINAL*INSYSID' variable   
Sep 30, 2015   in the TYPETPMX dataset.                                 
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.231  Support for JZOS Java Runtime Performance Stats SMF 121  
EXTY121        creates three new datasets:                              
EXTY121G          dddddd  dataset   description                         
EXTY121G          TY121   TYPE121   JZOS JAVA RUNTIME STATISTICS        
FORMATS           TY121G  TYPE121G  JZOS JAVA RUNTIME GARBAGE COLLECTION
TYPE121           TY121T  TYPE121T  JZOS JAVA RUNTIME THREADS           
TYPS121        and new FORMAT $MG121TC for thread category.             
VMXG121                                                                 
VMXGINIT                                                                
Oct  8, 2015                                                            
                                                                        
Change 33.230 -Example ANAL1430 selects TYPE1415 (non-VSAM) and TYPE64  
ANAL1430       (VSAM) records by DSNAME, then merges BY READTIME JOB to 
ANAL2642       select the the TYPE30_4 (Step end) for that JOB to get   
VMAC42         the RACFUSER field that opened that dataset.             
Sep 30, 2015   HOWEVER, this example in ANAL1430 can ONLY capture those 
               datasets that were CLOSED, and ONLY if that JOB had a    
               step terminate record in the SMF file.                   
              -Example ANAL2642 selects TYPE26J2 (Job Purge) by SUBMUSER
               and selects TYPE42DS (Interval Dataset Activity) by DSN  
               to report each JOB and DSNAME for that SUBMUSER.         
              -Type 42 subtype 6 TYPE42DS dataset has new variables     
                 S42READS=SUM(S42AMDRB,S42AMSRB,S42AMZRG,S42DSHRD);     
                 S42WRITES=SUM(S42AMDBW,S42AMSWB,S42AMZWB,S42DSHWR);    
               the sum of direct and sequential BLOCKS, directory reads/
               writes, and zHPF reads and writes.                       
   Thanks to Alyona Bertneski, JPMorgan, USA.                           
                                                                        
Change 33.229  Support for NDM PT records with zIIP CPU times (INCOMPAT)
VMACNDM        inserted these three new variables in NDMPT dataset:     
Sep 28, 2015     PTECP0='CPU TIME*SPENT ON*CP'                          
                 PTECP1='CPU TIME*SPENT ON*ZIIP'                        
                 PTECP2='ZIIP*QUALIFIED*PART OF*PTECP0'                 
               The inserted data caused INPUT STATEMENT EXCEEDED ERROR. 
               The prior PT record format's UNC and UNN variables were  
               cleaned up.                                              
   Thanks to David Guess, Blue Cross Blue Shield of South Carolina, USA.
                                                                        
Change 33.228  z/OS 2.1 z/13 SMF 74 St 9 INPUT STATEMENT EXCEEDED for a 
VMAC74         record with R749DEVN='Hardware Accelerator' but without  
Sep 25, 2015   expected Hardware Accelerator and Hardware Compression   
               segments that MXG INPUT because of that DEVN value.  The 
               record is valid as it contains zeros in the two triplet's
               NUMBER OF fields, SMF749FN,SMF7491N, so MXG logic now    
               knows to test those fields prior to the input of the     
               SMF749FO,SMF7491O segments, while the reason for their   
               absence is being investigated.                           
   Thanks to David Marone, SGS-BP, ITALY.                               
                                                                        
Change 33.227  Dataset TYPE22PB 'RECONFIGURED PCIE PFIDS' had zero obs  
VMAC22         due to misalignment in the MXG INPUT statement.  See also
Sep 23, 2015   Change 33.146.                                           
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.226  Documentation.  ERROR: THE GIF DRIVER CAN NOT FIND ANY   
MXGSAS92       FONTS and PHYSICAL FILE MVS:SYS3.SAS.SASMONO.TTF.. DOES  
Sep 23, 2015   NOT EXIST occurred on z/OS when the old MXGSAS92 PROC    
               was used for SAS 9.4, instead of using MXGSAS94 PROC.    
               This DD statement was added and is required for SAS 9.4  
                 // DD DSN=&SASHLQ..CONFIG(COMMON),DISP=SHR             
               in the //CONFIG DD concatenation.                        
                                                                        
Change 33.225  Major Revision to this Analysis of Capping now uses the  
ANALCAPD       PDB.ASUMCELP dataset with data for each LPAR, rather than
Sep 20, 2015   using only the PDB.ASUMCEC summary dataset for the CEC,  
               with new parameters to allow for selection by LPAR and/or
               to set different cap values for different LPARs:         
                 INCODE= a stub of code for selecting data              
                 CEC= one or more CEC serials separated by spaces       
                 LPAR=one or more LPAR/cap values separated by spaces   
               The plot shows the "Overflow MSU", an estimate of how    
               long it would take at the cap to get the same number of  
               MSUs consumed when the rolling 4 hour avg was over the   
               cap. So  the total MSU consumed above the cap based on   
               the rolling average pro-rated across the four hour       
               average keeping the system at the cap until all of the   
               excess MSUs are consumed.                                
                                                                        
Change 33.224  Cosmetic. Unexpected Unit Address SMFWKUAD='000000'X     
VMACSYNC       (which normally is a 3-byte EBCDIC like '181'/'F1F8F1'x) 
Sep 18, 2015   for a SYNCSORT SORTWK DD segment caused ILLEGAL ARGUMENT 
               message when it was used to create SYNCDV and SYNCUN with
               SYNCDV=INPUT(SMFWKUDA,HEX6.) syntax, as the HEX6 informat
               doesn't support the null value.  This DD segment also has
               " 0 " for the value in VOL variable.  Null now protected.
   Thanks to Joseph J. Faska, DTCC, USA.                                
                                                                        
Change 33.223  Short SMF 103 Subtype 13 record caused INPUT STATEMENT   
VMAC103        EXCEEDED Error.  The segment is documented to contain 56 
Sep 18, 2015   bytes plus a name field, but the record contains only 48 
               bytes.  Circumvention: Use the Name-Length Field and its 
               location to determine if this is 48 or 56 length. Input  
               normal for 56. For short 48 record, the two 8-byte fields
               are changed to 4 so the NAME field aligns, causing Bytes 
               and Requests are zero in the short records, but the      
               short record will be output with valid server name.      
   Thanks to Shabida Khan, Royal Bank of Canada, CANADA.                
                                                                        
Change 33.222 -Major enhancement for character data filtering for RMF   
ADOCRMFV       Monitor III DVT (Device Table) entries and other         
ASMRMFV        improvements.                                            
Sep 18, 2015  -These filters are intended for building ad hoc MXG RMF   
Sep 21, 2015   III PDBs for studies avoiding the overhead of generating 
               a full DVT table based PDB.  They control which DVT table
               entries are output to the RMFBSAM file.                  
              -Four filters are added to support DVT entry selection    
               from this table to the RMFBSAM output file.   These      
               filters are effective only if the DVT table is selected. 
                 They are applied in the order shown when multiple      
                 different keywords are used.                           
                 New Keyword    Aliases                                 
                 ------------   --------------------------------------  
                 DVTDEVNUM=     DVTDEVNO=  DVTDEVNR=  DVTDEV=  DVTN=    
                 DVTVOLSER=     DVTVOLI=   DVTVOL=    DVTSER=  DVTV=    
                 DVTAND         None                                    
                 DVTOR          None                                    
              -TUTORIAL:                                                
               Ranges of the form keyword=first:last may be used with   
                any of the above keywords except DVTAND and DVTOR.      
               The colon character ':' is required for a range          
                specification.  All entries GE the first value and LE   
                the last value are selected for output to the RMFBSAM   
                file.                                                   
               The first value may not exceed the last value or an error
                is flagged.                                             
               Ranges may not be wild carded.  If wild carded the range 
                value becomes a pattern instead.                        
               Single values may be specified for a range simply as     
                keyword=first and in this case the colon ':' is omitted.
               Patterns may also be used with any of the above keywords 
                except DVTAND and DVTOR and include one or more wild    
                card characters to match the respective DVT data field. 
                  Wild                                                  
                  Card  Matches                                         
                  ----  ------------------------------------------------
                  *     0 or more characters                            
                  %     1 Non-blank character                           
                  +     1 Numeric character (0-9)                       
                  _     1 Alphabetic character or _  (a-z, A-Z, _)      
                  .     1 National character (@, #, $)                  
                  !     1 Special character (not a-z, A-Z, 0-9, @, #, $)
                  ?     A blank string if used by itself                
                  ?     1 Blank character (X'40') if used with any other
                          characters                                    
               See Section 25 in the ADOCRMFV member for more details on
                usage of ranges and patterns.                           
              -DVTDEVNUM= (and any of its aliases) selects DVT entries  
                by Device Number.  Both ranges and patterns with wild   
                card characters may be specified.  Up to 64 ranges and  
                64 patterns are supported. The default is DVTDEVNUM=ALL.
               Any valid 4 hex character device number with or without  
                pattern characters in the range of 0000-FFFF may be     
                specified.                                              
               For ranges the Device Number is treated as a binary      
                number in arithmetic comparisons.                       
               For patterns the Device Number is converted to hex       
                characters (0-F) prior to pattern matching.             
               NOTE: Due to the nature of hexadecimal characters not all
                characters and/or patterns may be used with DVTDEVNUM=. 
                See documentation for details.                          
              -Examples for DVTDEVNUM=                                  
               DVTDEVNUM=0A00 selects the device with address 0A00 only.
               DVTDEVNUM=0A00:0FFF selects all devices with addresses GE
                0A00 and LE 0FFF.                                       
               DVTDEVNUM=A00:FFF selects the same devices as above with 
                the leading zeros omitted for coding convenience.       
               All leading zeros may be omitted if desired when ranges  
                are used.  Leading zeros may NOT be omitted when        
                patterns are used unless they are included in the       
                pattern.                                                
               DVTDEVNUM=0*F and DVTDEVNUM=*F produce quite different   
                results.                                                
               DVTDEVNUM=B* selects all devices with addresses from B000
                through and including BFFF.                             
               DVTDEVNUM=10* selects all devices with addresses from    
                1000 through and including 10FF.                        
               DEVDEVNUM=C*FE selects all devices with addresses C0FE,  
                C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE,   
                CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE.                 
               DEVDEVNUM=C+FE selects all devices with addresses C0FE,  
                C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, and C9FE
                as '+' is a digit (0-9) pattern character.              
               DVTDEVNUM=C%FE selects all devices with addresses C0FE,  
                C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE,   
                CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE as '%' is a      
                placeholder pattern character.                          
               DVTDEVNUM=C_FE selects all devices at addresses CAFE,    
                CBFE, CCFE, CDFE, CEFE, and CFFE as '_' is an alphabetic
                pattern character.                                      
              -DVTVOLSER= (and any of its aliases) selects DVT entries  
                by Volume Serial Number.  Both ranges and patterns with 
                wild card characters may be specified.  Up to 64 ranges 
                and 64 patterns are supported.  The default is          
                DVTVOLSER=ALL.                                          
               Any valid 1-6 character Volume Serial with or without    
                pattern characters may be specified.  Per JCL syntax a  
                Volume Serial Number is 1 through 6 alphanumeric,       
                national ($,#,@), or special characters.                
               NOTE: Since just about any keyboard character is valid in
                a Volume Serial please take extra care when coding to   
                avoid unintended results in the MXG PDB.                
              -Examples for DVTVOLSER=                                  
               DVTVOLSER=C99999 selects the volume serial C99999 only.  
               DVTVOLSER=C00000:C99999  selects all volume serials GE   
                'C00000' and LE 'C99999'.                               
               DVTVOLSER=10* selects all volume serials starting with   
                '10' followed by up to 4 more characters.               
               DVTVOLSER=H+++++ selects all volume serials starting with
                'H' followed by 5 digits.                               
               DVTVOLSER=K*A selects all volume serials starting with   
                'K' that have a final character 'A' with up to 4        
                intervening characters.                                 
              -DVTAND (default) indicates that selection results from   
                DVTDEVNUM= and DVTVOLSER= DVT filter keywords are       
                logically ANDed.  DVTAND is effectively ignored if DVT  
                records are NOT selected                                
               Results for selected Devices for the same DVTxxxxxx=     
                keyword are ALWAYS logically ORed.                      
               NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and          
                ZEROIO/NOZEROIO are applied independent of the use of   
                DVTAND.                                                 
              -DVTOR indicates that selection results from DVTDEVNUM=   
                and DVTVOLSER= DVT filter keywords are logically ORed.  
                DVTOR is effectively ignored if DVT records are NOT     
                selected                                                
               Results for selected Devices for the same DVTxxxxxx=     
                keyword are ALWAYS logically ORed.                      
               NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and          
                ZEROIO/NOZEROIO are applied independent of the use of   
                DVTOR.                                                  
              -Examples with DVTAND in effect: DVTDEVNUM=CA00:CAFF      
                DVTVOLSER=SMF* only selects device entries in the DVT   
                table that have a Device Number GE CA00 and LE CAFF AND 
                that have a Volume Serial Number that starts with 'SMF'.
               DVTDEVNUM=CA00:CAFF  DVTVOLSER=SMF*  DVTVOLSER=PAG* only 
                selects device entries in the DVT table that have a     
                Device Number GE CA00 and LE CAFF AND that have a Volume
                Serial Number that starts with either 'SMF' or 'PAG'.   
              -Examples with DVTOR in effect: DVTDEVNUM=CA00:CAFF       
                DVTVOLSER=SMF* selects device entries in the DVT table  
                that have a Device Number GE CA00 and LE CAFF OR that   
                have a Volume Serial Number that starts with 'SMF'.     
               DVTDEVNUM=CA00:CAFF  DVTVOLSER=SMF*  DVTVOLSER=PAG*      
                selects device entries in the DVT table that have a     
                Device Number GE CA00 and LE CAFF OR that have a Volume 
                Serial Number that starts with 'SMF' or 'PAG'.          
               The logical OR results in less restrictive filtering     
                because any of the 3 conditions results in data         
                selection of a DVT entry.                               
               NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and          
                ZEROIO/NOZEROIO are applied independent of the use of   
                DVTOR.                                                  
              -The order of DVT filter application is:                  
                1) DEVTYPE=                                             
                2) DVTDEVNUM=                                           
                3) DVTVOLSER=                                           
                4) ZEROIO/NOZEROIO                                      
              -Section 5 "Input Data Selection Parameters" in           
                documentation is updated with discussion of all the new 
                DVT selection keywords and aliases.                     
              -Section 26 "Summary" in documentation is updated for the 
                new DVT keywords.                                       
              -Message RMFV034I did not display correctly on a Device   
                Number match with DVTDEVNUM= and SHOWMATCH options in   
                effect.                                                 
              -Version entry for z/OS 2.2 in RMF release table was not  
                Correct.                                                
                                                                        
Change 33.221  RMF III data with CPUHOLEN GT 480 and CPUVERG3 EQ 5 ABEND
VMACRMFV       INPUT STATEMENT EXCEEDED RECORD LENGTH error when IBM    
Sep 17, 2015   changed CPUHOLEN to 740 but did not update CPUVERG3.     
                                                                        
Change 33.220  Mini-tutorial on how the INFORMAT in an INPUT function   
SAGANAL        caused the MSU values to be off by a factor of 100 (an   
Sep 17, 2015   error that was immediately obvious!).  SAGANAL builds    
               format $SYS2CAP that maps SMF70CPA to TIME+SYSTEM, and   
               then retrieves a value with this INPUT function that     
               uses the 10.2 INFORMAT to "read" the $SYS2CAP value:     
                 SMF70CPA=INPUT(PUT(TIMESYS,$SYS2CAP.),10.2);           
               which worked, but only accidentally, because all previous
               $SYS2CAP values contained a decimal.  But if the value in
               $SYS2CAP was an integer, the .2 in the 10.2 INFORMAT told
               SAS to divide by 100. Removal of the .2 that never should
               have been there corrects the error.                      
                                                                        
Change 33.219  MXG 33.09 Only.  VARIABLE MAXCCPUC IS UNINITIALIZED msg, 
VMACBVIR       typo, caused MAXDCUPC to be a missing value in BVIR10.   
Sep 17, 2015                                                            
                                                                        
Change 33.218  MXG-created variable WTTOTIOTM (DBMS/IO TOTAL OTHER WAIT)
ADOC110        did not include these recently-added wait variables:     
VMAC110           DSCHMDTM FCVSWTTM VCXCWTTM ISALWTTM TCALWTTM TDELWTTM 
Sep 16, 2015      TDILWTTM                                              
                                                                        
====== Changes thru 33.217 were in MXG 33.09 dated Sep 15, 2015=========
                                                                        
Change 33.217  z13 in SMT Mode ONLY:  LPARCPUS=0 in PDB.TYPE70PR.       
VMAC7072       This is the last reported issue with MXG code for z13 in 
Sep 13, 2015   SMT mode, and both SMT=1 and SMT=2 data have been tested.
               So this change in MXG 33.09 is REQUIRED for z13 SMT mode.
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.216  Support for APAR OA47042 adds MOBILE RESOURCES in RMF 70 
VMAC7072       and 72 for MOBILE PRICING that eliminates the need to    
Sep 11, 2015   process the CICS and IMS transaction records, by using   
               new WLM Service Definition Qualifier types of Connection 
               Type (CT) and/or Client Transaction Name (CTN) to set the
               new WLM Classification "Reporting Attribute" that can be 
               set to NONE/MOBILE which WLM uses to identify mobile work
               in these new variables.                                  
              -Dataset TYPE70 new variables:                            
                 SMF70LACM='MOBILE*LONGTERM*AVERAGE*MSU/HR'             
                 SMF70LACA='CAT A*LONGTERM*AVERAGE*MSU/HR'              
                 SMF70LACB='CAT B*LONGTERM*AVERAGE*MSU/HR'              
              -Dataset TYPE72GO new variables:                          
                 R723TSUCP ='TOTAL*GP*SERVICE*MSU/HR'                   
                 R723TSUSP ='TOTAL*ZIIP*SERVICE*MSU/HR'                 
                 R723TSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR'             
                 R723MSURCP='MOBILE*GP*SERVICE*MSU/HR'                  
                 R723MSURSP='TOTAL*ZIIP*SERVICE*MSU/HR'                 
                 R723MSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR'             
                 R723ASUCP ='CAT A*GP*SERVICE*MSU/HR'                   
                 R723ASUSP ='CAT A*ZIIP*SERVICE*MSU/HR'                 
                 R723ASUOCP='CAT A*ELIGIBLE*SERVICE*MSU/HR'             
                 R723BSUCP ='CAT B*GP*SERVICE*MSU/HR'                   
                 R723BSUSP ='CAT B*ZIIP*SERVICE*MSU/HR'                 
                 R723BSUOCP='CAT B*ELIGIBLE*SERVICE*MSU/HR'             
               These metrics may be available for z/OS 2.2 and z/OS 2.1 
               later this year.                                         
               Note that R723TSUCP=SUM(CPUUNITS,SRBUNITS);              
                                                                        
Change 33.215  Documentation change only. Added an example of using     
VMXGSUM        VGETDDS to drive the input to VMXGSUM.                   
Sep  9, 2015                                                            
                                                                        
Change 33.214  If UTILBLDP was executed twice in the same session, and  
UTILBLDP       the USERADD= option was used, the second execution failed
Sep 10, 2015   because the _IDxxxx "SMF Record Macros" were not cleared.
   Thanks to Michael Reines, Decadis, GERMANY.                          
   Thanks to Ron Hawkins, HDS, USA.                                     
                                                                        
Change 33.213  Support for WASODM Operational Decision Manager 8.7.1 SMF
VMAC120        Type 120 Subtype 100 (MXG Dataset TY120100) INCOMPATIBLE.
Sep 10, 2015   The record was completely restructured internally, and   
Oct  8, 2015   these ruleset statistics now exist in SM120HDV=3 records:
                  SM120RULEXBAD  ='RULESET*FAILED*EXECUTION*COUNT'      
                  SM120RULEXCALLS='RULESET*NUMBER*OF*CALLS'             
                  SM120RULEXCMAX ='RULESET*MAX*CPU*JAVA TIME'           
                  SM120RULEXCMIN ='RULESET*MIN*CPU*JAVA TIME'           
                  SM120RULEXCPU  ='RULESET*TOTAL*CPU*JAVA TIME'         
                  SM120RULEXFSUM ='RULESET*SUM OF*FIRED*RULES'          
                  SM120RULEXNUM  ='RULESET*SUCCESSFUL*EXECUTION*COUNT'  
                  SM120RULEXPATH ='RULESET*EXECUTION*PATH'              
                  SM120RULEXTIME ='RULESET*TOTAL*ELAPSED*JAVA TIME'     
                  SM120RULEXTMAX ='RULESET*MAX*ELAPSED*JAVA TIME'       
                  SM120RULEXTMIN ='RULESET*MIN*ELAPSED*JAVA TIME'       
              -SM120HDV=1 records (in Versions 8.5.1.0 and 8.6.0.0) and 
               SM120HDV=2 records (in Versions 8.5.1.2) contain only    
               these counters: SM120RULEXNUM SM120RULEXBAD SM120RULEXSUM
              -Records with no Extension segment are now output; these  
               appear to be interval records when there was no activity.
               New variable SM120EXNNR identifies if the record has an  
               extension, and if so, which one.                         
              -The prior TY120100 dataset was incorrectly/wrongly built 
               with the number of observations in WORK.TY120100 higher  
               than the number of input records, and the number of obs  
               in PDB.TY120100 too few (and wrong).                     
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.212  Support for MEGACRYPTION Version 6 SMF records,          
VMACMGCR       (MGCRLEV='2') which incompatibly increased the length of 
Sep  8, 2015   the MGCRBYTE and MGCRKS fields from 4 to 8 and 40 to 60. 
    Thanks to Randy Schlueter, First Data Corporation, USA              
                                                                        
Change 33.211  New variables are added in DB2 Trace Dataset T102S199.   
VMAC102          QW0199SC='LAST TIME*DATABASE*STATISTICS*UPDATED'       
Sep  8, 2015     QW0199ID='MORE*RECORDS*OR*LAST?'                       
                 QW0199SD='SHADOW*COPY?'                                
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 33.210  More TMON/CICS Version 3 AND Version 4 corrections.      
VMACTMO2      -MONITASK for Version 3 was wrong in MXG 33.08, with      
Sep 11, 2015   misalignment starting at variable CICOVHTM.              
              -MONITASK Version 4 requires ASG PTF TH03803 to correct   
               invalid values in variables TASTCPUC and TASTCPOC.       
              -The MONISYST dataset was misaligned and has been updated 
               and validated with both 3.3 and 4.0 records.             
   Thanks to Francois Vancoppenolle, PV Group, BELGIUM.                 
                                                                        
Change 33.209  Cosmetic changes from ITRM Validation.                   
VMAC102       -VMXG70PR: Temporary variable N60PLUSLPAR no longer kept  
VMAC110                  in PDB.ASUM70PR and PDB.ASUMCEC datasets.      
VMAC119       -VMAC110:  Variables DS7START,DS7LSTRT now labeled.       
VMAC50        -VMAC102:  The nineteen QWn196Ha variables added by 31.236
VMAC7072                 are now labeled/formatted/Length consistently. 
VMAC74        -VMACNDM:  Offset variable NDMGPE1D is no longer kept in  
VMAC75                   NDMRT dataset.                                 
VMAC76                   Variables NDMZLIBR/LIBS PTRESTRECORD labeled.  
VMAC77        -VMACSTC:  STC14TOD and STC27TPX variables are labeled.   
VMAC99        -VMAC119:  Variables SMF119SM_ and SMF119FT_ are labeled. 
VMACNDM       -VMAC50:   Variable TY40EXTL labeled.                     
VMACSTC       -VMAC7072: Temp variables R725QSR1/QSR2/QST1/QST2 are not 
VMACXCOM                 kept since they were already used to create the
VMXG70PR                 SSQ variables R725QSRQ R725QSTQ.               
Sep  6, 2015  -VMAC74-7: Variables SMF74/75/76/77/GIE are labeled.      
              -VMAC99:   Variables S99CMTFLGS1/2 label typo corrected.  
              -VMACXCOM: Many XCOxxxxx variables are labeled.           
   Thanks to Chris Weston, SAS Institute, USA.                          
                                                                        
Change 33.208  z/OS ONLY.  If you use VGETDDS with  DDNAMES=PDB:  syntax
VGETDDS        (to read all DDNAMEs starting with PDB), and those DDs   
Sep  6, 2015   are on tape, VGETDDS mounted all of the tapes twice, once
               to detect is is a SAS dataset and then once to actually  
               read the data.  Now, once VGETDDS finds that a PDBn DD   
               points to a tape device, it will presume all the others  
               are also tape, and thus eliminate the double mounts. But,
               if a DDNAME that matches the test is NOT a SAS dataset   
               the job ABENDs with ERROR:LIBRARY PDBn IS NOT IN A VALID 
               FORMAT FOR ACCESS METHOD V9SEQ or if UNIT=AFF is used but
               DEFER=YES was NOT, then a SYSTEM 413 ABEND occurs trying 
               to open all tape devices at the same time.               
              -The typically unneeded MXGNOTE messages are now skipped  
               with the MXGEXIMSG option.                               
                                                                        
Change 33.207  z/OS 2.2: REQUIRES ML-55 of MXGTMNT, for ABEND S0E0-28.  
ASMTAPEE       In z/OS 2.2, IBM's CSRPOOL service, called by MCSOPMSG in
Sep  8, 2015   ASMTAPEE, puts diagnostic data into GR0, AR0, and AR15,  
               none of which are expected to be preserved, but R15 was  
               used by ASMTAPEE, because it was unused and available.   
               Now ASMTAPEE clears AR15 to eliminate the ABEND exposure.
                                                                        
Change 33.206  z/OS 2.2 Job Correlation Variables SMF30COR is now INPUT 
BUILD005       kept in TYPE30xx datasets, and also output in PDB.JOBS,  
VMAC30         PDB.STEPS, and PDB.SMFINTRV.  Variable SMF26JCR was INPUT
Sep  4, 2015   and kept in TYPE26J2 previously, but now it is also kept 
               in PDB.JOBS and PDB.NJEPURGE datasets with BUILDPDB.     
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.205  DB2ACCTP variables QPACPKID/QPACLOCN/QPACASCH/QPACAANM   
VMACDB2        and QPACCOLN could be truncated even though they have    
Sep  2, 2015   valid extended name segments.  The LENGTH test for the   
               new PAR QUERY fields wrongly INPUT them when they did not
               exist, causing the DELFIX circumvention to incorrectly be
               invoked, causing the extended segments to not be input.  
   Thanks to Tom Adams, State Farm, USA.                                
   Thanks to Shankar Chatterjee, State Farm, USA.                       
                                                                        
Change 33.204  Variable IOTMNODD was never calculated in PDB.JOBS/STEPS,
BUIL3005       and the value in IOTMTODD was actually IOTMNODD.  The    
BUILD005       three calculations of IOTMTODD= should be IOTMNODD=.     
Sep  2, 2015                                                            
   Thanks to Rick Southby, Insurance Australia Group Limited, AUSTRALIA.
                                                                        
Change 33.203  Cosmetic.  EXCLUDED FIELDS FOUND messages now print your 
VMAC110        site's IMACEXCL testing values, so you can see if this is
Sep  1, 2015   for a new dictionary triplet that needs a UTILEXCL rerun.
               This was originally added in Change 29.262, but somehow, 
               the needed quotes and ampersand "&CICXLTR" syntax got    
               changed to CICXLTR, which printed nothing.               
                                                                        
Change 33.202  Velocity ZVPS 5.4 dataset XAMSYT has zero observations   
VMACXAM        because Change 33.157's recalculated SYTNLPS was zero.   
Aug 29, 2015   The actual SYTNLPS+1 in the non-Total record is now used 
Sep  2, 2015   and the false INVALID SYTCUP SEGMENT message is removed. 
Sep 11, 2015  -Unexpected CPID='GPs' value is now output in XAMCPUTO as 
               there were no records with CPID='Total".                 
   Thanks to Douglas C. Walter, CitiCorp, USA.                          
   Thanks to Brent Turner, Citigroup, USA.                              
                                                                        
Change 33.201  Support IBM INFOSPHERE CHANGE DATA CAPTURE VERSION 10.2.1
VMACCDC        adds many new variables to the CDI, CDO, CDW, DLR, DSL,  
Aug 30, 2015   DTC, OSC, SCT, SDT, TCT, and new TDT segments.  However, 
               the SCT and TCT data does not match the documentation and
               both SCTCPU and TCTCPU are invalid with this iteration.  
   Thanks to Phil Grasser, Norfolk Southern, USA.                       
                                                                        
Change 33.200 -TYPE70xx datasets have always contained ONLY data for the
VMAC7072       engines that were ONLINE at interval end, and that had   
Aug 28, 2015   NOT been VARYed ONLINE (i.e., CAI='01'X). Engines that   
               were IPL's (CAI='03'X) were NOT output, because the data 
               in those startup intervals was inconsistent in early MVS.
               However, those partial interval's data is not only valid,
               it is actually now required to prevent wrong or missing  
               values for CECSER in TYPE70/TYPE70PR/TYPE70EN datasets,  
               and to capture the IPL interval's resources.             
              -TYPE70EN variable CPUBSYTM is now correctly set missing  
               for zIIP/zAAP engines, since it is a CP engine metric.   
              -More observations are now output, so PROC COMPARE will   
               see differences in these variables:                      
                 TYPE70:   CECSER   CPUACTTM CPUMVSTM CPUWAITM PCTCPUBY 
                           PCTMVSBY PCTRDYWT PLCPRDYQ SHORTCPS          
                 TYPE70PR: CECSER                                       
                 TYPE70EN: CECSER   CPUBSYTM CPUMVSBY                   
                                                                        
Change 33.199  The AXWAY SMF record was INCOMPATIBLY changed by an      
VMACAXWY       increase of a field length.                              
Aug 31, 2015                                                            
   Thanks to Rachel Holt, FMR, USA.                                     
                                                                        
Change 33.198 -CICS/TS 5.3 BETA, Resource Class (MNSEGCL=5) could cause 
VMAC110        INPUT STATEMENT EXCEEDED INPUT because only 112 bytes of 
Aug 27, 2015   the MNR5LENT=120 bytes were read.                        
                                                                        
Change 33.197 -Variable LPBUSY in TYPE113 is the TOTAL BUSY for all CPs 
ASUM113        and can exceed 100% with multiple engines, but variable  
VMAC113        LPARBUSY in ASUM113 is the CPU BUSY OF ONE ENGINE.  New  
Aug 24, 2015   variable LPBUSY is now created in ASUM113 with TOTAL BUSY
               to provide both perspectives on percent busy.            
              -Variable SRBSTATE is now created in ASUM113 to complement
               the existing PRBSTATE variable.                          
   Thanks to David Cogar, Wells Fargo, USA.                             
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.196  BVIR variable's values are revised to match IBM reports. 
VMACBVIR       TVCSIZE is now internally in bytes, formatted MGBYTES,   
Aug 30, 2015    and the label corrected.                                
               AVGCPUSE is now percent (95.5) instead of 0.95 fraction. 
               AVGDEFTH is now correct, was 1000 too large.             
   Thanks to Patricia J. Jones, DST Systems, USA.                       
                                                                        
====== Changes thru 33.195 were in MXG 33.08 dated Aug 20, 2015=========
                                                                        
Change 33.195  TMON/CICS Version 4.0 Support was still wrong, with an   
VMACTMO2       extra 8 bytes INPUT that shouldn't have been, so that    
Aug 20, 2015   MXG 33.08 dated Aug 20 is NOW required for version 4.0.  
              -Variables TASTCPUC and TASTCPOC in dataset MONITASK have 
               invalid data values, await PTF from ASG.                 
   Thanks to Francois Vancoppenolle, PV Group, BELGIUM.                 
   Thanks to Dirk Thys, PV Group, BELGIUM.                              
                                                                        
Change 33.194 -The modern CLRMFV Clist is incompatible with the archival
ZCLRMFV        ZASMRMFV program because RMF III files are allocated with
Aug 19, 2015   RMFC prefixed DDNAMEs and the archival version of        
               ZASMRMFV is not aware of these.  This results in message:
               RMFV015E +++ERROR: NO VALID RMF III INPUT FILES FOUND+++ 
              -A new Clist ZCLRMFV for use with ZASMRMFV only is created
               with this change that will only allocate RMF III data    
               sets with RMFV DDNAME prefixes.                          
    Thanks to Tom Drager, Aurora Health Care                            
                                                                        
Change 33.193  ANALDSET abend IEC145I 413-04 with DDNAME=ADDPROG because
ANALDSET       the DATA step inserted by Change 32.187 broke the logic  
Aug 19, 2015   for UNIT=AFF by trying to read and write to and from the 
               same tape device.                                        
   Thanks to Randy Hewitt, HP Canada, CANADA.                           
                                                                        
Change 33.192 -CICS/TS 5.3 Beta added two new variables to CICSTRAN that
UTILEXCL       caused UTILEXCL to report UNKNOWN WBJSNRQL and WBJSNRPL  
VMAC110        fields, but the IMACEXCL it created has a syntax error,  
Aug 18, 2015   And, since the two fields were INSERTED, the MXG INPUT   
               without IMACEXCL caused subsequent fields to be invalid  
               as they were misaligned.  Now, 70/378/3376 are expected  
               values for 5.3 default SMFPSRVR, MCTSSDCN, and MCTSSDRL. 
               (Other values will generate the RUN UTILEXCL messages.)  
              -The CICSRDQU records have new reserved fields inserted,  
               that caused misalignment.                                
               =====================================================    
               CICS/TS 5.3 IS STILL IN BETA, with final GA is Sep 31,   
                so IBM is still free to make other changes.             
               =====================================================    
   Thanks to Paul C. Gordon, Bank of America, USA.                      
                                                                        
Change 33.191  UTICBLDP error message COMPBL HAS TOO MANY ARGUMENTS was 
UTILBLDP       due to an unneeded second COMPBL invocation for MACKEEPX.
Aug 18, 2015   The second execution was removed, but the error was also 
               triggered by comments with "* comment text ;" syntax, and
               using " /* comment text */ " syntax also circumvented the
               error.  In general, that second syntax is more robust,   
               but in this case, placing the comments OUTSIDE the MACRO 
               circumvents the need to parse either comment syntax.     
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.190  While the WORK.TY115215 dataset is created by TYPE115,   
VMAC115        using TYPS115 did not create PDB.TY115215 because the    
VMXGINIT       _STY115X dataset sort macro for TY115215 was not added   
Aug 17, 2015   in the _S115 "product" sort macro for SMF type 115s.     
               This caused dataset TY115215 to not be listed in DOCVER. 
                                                                        
====== Changes thru 33.189 were in MXG 33.08 dated Aug 17, 2015=========
                                                                        
Change 33.189  Support for z/OS 2.2 (COMPATIBLE, but LOTS NEW STUFF):   
BUILD005      -TYPE0203: Support for new ID=2 SUBTYPE=1 and 2 records   
EXTY4227       create two new datasets in VMAC0203:                     
EXTY9037        DDDDDD    DATASET    DESCRIPTION                        
FORMATS         TY0201    TYPE0201   TYPE 2 SUBTYPE 1 SIGNATURE GROUP   
IMAC42          TY0202    TYPE0202   TYPE 2 SUBTYPE 2 SIGNATURE INTERVAL
IMAC90A       -TYPE1415: Change 33.026 added support for LONG WANTED new
VMAC0203        variables SYSPLEX JESNR JCTJOBID TYPETASK, but the pre- 
VMAC104         GA SMF Manual had the order of SYSPLEX/JCTJOBID while   
VMAC106         the actual order is JCTJOBID/SYSPLEX and the typo will  
VMAC1415        be corrected for the Sub-type 3 record.                 
VMAC30         -Sub-type 5, length is 72 but 70 in SMF Manual; two bytes
VMAC42          are skipped                                             
VMAC6156       -SMF14ALIAS now created.                                 
VMAC74         -SMF14DSVER value is '01'x but bits 0, 1, 2, are listed  
VMAC90A         in the SMF Manual.  Await IBM answer.                   
VMAC99         -JOB variable has un-printable characters in the 14/15s, 
VMACCTLG        but valid characters are in JOB variable in 30s, in pre-
VMXGINIT        GA data. Await IBM answer.  SMF14ESL=26 STY=5 (old      
Mar  8, 2015    length) protected.                                      
Jun  8, 2015  -TYPE26J2: New IBM JCTJOBID=:'G' value will set the MXG   
Jul 21, 2015    TYPETASK='JOBG', only in TYPE26J2 Purge Records for a   
Jul 24, 2015    JOBGROUP's logging job's purge, which is the only place 
Aug  4, 2015    that 'G' value is externalized in SMF records.          
Aug 17, 2015  -TYPE30 : New ABEND='EVICT' value set in TYPE30 for jobs  
Mar  1, 2016            evicted with $EJ,STEP,HOLD.                     
              -TYPE42: Change 33.026 added support for new TYPE4227     
                dataset provide the VTOC AUDIT LOG with these variables:
                  JCTJOBID  ='SMF42RNJO*JOB NUMBER'                     
                  JESNR     ='JES*NUMBER'                               
                  TYPETASK  ='TYPE*OF*TASK;                             
                  SMF42RIND ='SMF42RIND*RECORD*INDICATOR'               
                  SMF42RSEEK='SMF42RSEEK*VTOC*TRACK*ID'                 
                  SMF42RSRCH='SMF42RSRCH*VTOC*RECORD*ID'                
                  SMF42RCMDS='SMF42RCMDS*CCW*COMMAND*CODES'             
                  SMF42RUPSW='SMF42RUPSW*CALLERS*ADDRESS'               
                  SMF42RUTOK='SMF42RUTOK*USER*SECURITY*TOKEN'           
                  SMF42RRSV ='SMF42RRSV*DEVICE*IS*RESERVED?'            
                  SMF42RKEY ='SMF42RKEY*DSCB KEY*DATASET*NAME'          
                  SMF42RDSC ='SMF42RDSC*DSCB*DATA*FIELD'                
                  SMF42RACT ='SMF42RACT*ACTIVITY*TYPE'                  
                  with these possible activities in SMF42RACT that are  
                  decoded by $MG042VT format:                           
                    'D***'='D***:DFSMS ACTIVITY'                        
                    'DCVF'='DCVF:CVAFDIR'                               
                    'DCRE'='DCRE:DADSM DATASET CREATE'                  
                    'DEXT'='DEXT:DADSM DATASET EXTEND'                  
                    'DPAR'='DPAR:DADSM DATASET PARTIAL RELEASE'         
                    'DREN'='DREN:DADSM DATASET RENAME'                  
                    'DDEL'='DDEL:DADSM DSCB SCRATCH'                    
                    'DUPD'='DUPD:DADSM DSCB UPDATE'                     
                    'DFRG'='DFRG:DFSMSDSS DEFRAG'                       
                    'DCON'='DCON:DFSMSDSS CONSOLIDATE'                  
                    'DDMP'='DDMP:DFSMSDSS DUMP'                         
                    'DRST'='DRST:DFSMSDSS RESTORE'                      
                    'IOBE'='IOBE:IOBE NOT PROVIDED'                     
                    'USER'='USER:IOBEUSER NOT SPECIFIED'                
              -TYPE42: Support subtype 5/6 APAR OA44322/OA44319 CMR+    
                and new microsecond metrics was added in Change 32.113. 
              -TYPE74: Change 32.305 added support for new TYPE 74      
                variables: R744MNEL R744MNEC R744NSRK                   
              -TYPE90A:  Updated for new Type 90 subtype 37 to create   
                new TYPE9037 dataset that reports any changes to APF    
                status.  The RACF UTOKEN has '55'X values in SMF data   
                because it's value is "MASKED", i.e., encrypted, while  
                MXG expected the "UNMASKED" values that are in UTOKEN in
                other SMF records (42, 80, 119).  The existing SMF 90   
                subtypes 29 and 31 also contain the MASKED UTOKEN, but  
                IBM Development has stated their intention to change to 
                UNMASK the UTOKEN in all three of those 90 subtypes.    
                HOWEVER: SEE CHANGE 33.282 - MXG now "unencrypts".      
                 The RACROUTE REQUEST=TOKENMAP can do the "unmasking",  
                 and can be used even on a system that was not the one  
                 on which the SMF record was created, but that can only 
                 be used on z/OS; even there it would take SIGNIFICANT  
                 effort to issue a RACROUTE from within a SAS data step.
                 But since the data length is 80 bytes either way, and  
                 the data is not secret, it really needs to be UNMASKED 
                 to be of value, so IBM's future correction is welcome. 
              -TYPE90A: Two variables added to TYPE9037 dataset.        
                        Formats added to TYPE9037 variables.            
              -TYPE99 : Five variables added to TYPE9912 dataset.       
              -TYPE104: Platform Types that create SMF Type 104 records 
                        are expanded and format updated:                
                          VALUE MG104PT                                 
                           0='0:AIX ON SYSTEM P'                        
                           1='1:LINUX ON SYSTEM X'                      
                           2='2:LINUX ON Z SYSTEM'                      
                           3='3:WINDOWS ON SYSTEM X'                    
                                                                        
              -TYPE106: Support for new ID=106 SUBTYPE=1 and 2 records  
                        create two new datasets in VMAC106              
                DDDDDD    DATASET    DESCRIPTION                        
                TY1061    TYPE1061   BCPII HWISET API CALLS             
                TY1062    TYPE1062   BCPII HWICMD API CALLS             
                Mar 1, 2016: Incorrect length for SMF6ASDL, corrected   
                             to input 4 bytes.                          
              -VMACCTLG and VMAC6156 were updated Nov 27, 2014.         
               Support for GDGE, GDG Extended GDGLIMIT=999 in z/OS 2.2. 
               New variable GATEXTND='E' flags the extended mode, new   
               variables GATLIMTE/GATCNTE are INPUT but also kept in the
               existing GATLIMIT/GATCNT to preserve existing reports.   
               Some overlooked flag variables in the 05 Catalog Segment 
               are now decoded and kept in datasets TYPE6156 (from SMF  
               (type 61, 65, 66) and TYPECTLG (from the IDCAMS EXPORT   
               CATALOG flat file).  These are all the 05 fields now:    
                 GATALLOC='GATALLOC*FIFO OR*LIFO?'                      
                 GATCNT  ='GDG*COUNT'                                   
                 GATDELET='DELETE*WHEN*LIMIT*EXCEEDED*0=OLD*1=ALL?'     
                 GATEXTND='GATEXTND*EXTENDED*OR CLASSIC?'               
                 GATEXTNO='GATEXTNO'                                    
                 GATGEN  ='GATGEN  '                                    
                 GATLIMIT='MAXIMUM*GDS*ENTRIES*IN GDG*BASE'             
                 GATLIMTE='EXTENDED*GAT*GATLIMIT'                       
                 GATPURGE='GATPURGE*YES OR*NO?'                         
                 GATSCRTH='SCRATCH*FORMAT 1*DSCB*0=NO*1=YES?'           
                 GATVER  ='GATVER  '                                    
                 GATWRAP ='GATWRAP '                                    
                 GDGATTR ='GDGATTR'                                     
              -BUILD005 protects for TYPETASK='JOBG' in JCTJOBID.       
                                                                        
Change 33.188  TMON/CICS Version 4.0, these four MONITASK variables were
VMACTMO2       divided by 4096, TWICE:                                  
Aug 13, 2015     TASTCPUT TASTCPOT TACNTRTM TACNTWTM                    
               and these MONIAMQ variables were NOT divided because the 
               test was GT 4 and it should have been GE 4.              
                 TAAMQOPT TAAMQCLT TAAMQGTT TAAMQPTT TAAMQP1T           
                 TAAMQIQT TAAMQSTT                                      
               This change is REQUIRED to support TMON/CICS Version 4.  
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.187  DB2 T102S106 didn't keep variables QWP4RSMX and QWP4ACAN 
VMAC102        and these zparms were not input.                         
Aug 14, 2015      QWP1CSMF='SMFCOMP'                                    
Aug 20, 2015      QWP1FLG2='QWP1FLG2*FLAG*BITS'                         
                  QWP1LOGT='LOG*CHECKPOINT*TYPE'                        
                  QWP4ABVC='QWP4ABVC*SERVICEABILITY'                    
                  QWP4ACAN='QWP4ACAN*SERVICEABILITY'                    
                  QWP4CGAA  ='GET_ACCEL_ARCHIVE*0=NO*1=YES*/            
                  QWP4CQAC  ='QUERY*ACCELERATION'                       
                  QWP4EXQRY ='QWP4EXQRY'                                
                  QWP4FCPPRC='FLASHCOPY*PPRC'                           
                  QWP4QACO  ='QUERY*ACCEL*OPTIONS'                      
                  QWP4RFRP  ='REC_FASTREPLICATION'                      
                  QWP4RLPR  ='REORG*LIST*PROCESSING'                    
                  QWP4RPSN  ='REORG*PART*SORT*NPSI'                     
                  QWP4RSMX='QWP4RSMX*SERVICEABILITY'                    
                  QWP4STMN  ='REALSTORAGE*MANAGEMENT'                   
                  QWP4WFRD  ='MAX RID*BLOCKS*TEMP STG*PER RID LIST'     
                  QWP4_BIF_COMPAT='BIF*COMPATIBILITY'                   
                  QWP9DDFCIP='DDF COMPAT*IDENTITY*PRIOR VERSION*NNR'    
   Thanks to Lai Fai Wong, Bank of America, USA.                        
                                                                        
Change 33.186 -An INCOMPATIBLE z13 ERROR, only in SMT-MODE, and only if 
VMAC7072       a CP engine is varied online, is now corrected. When a   
Aug 16, 2015   a z13 in SMT mode varied a new CP online, MXG did not see
               the new engine, causing PDB.TYPE70 and PDB.TYPE70EN to   
               be wrong, with incorrect PCTCPUBY and NRCPUS=. and no    
               dispatch times for the new CP engine in PDB.TYPE70.      
               An IBM error is only partially responsible: after the    
               VARY, the value for SMF70CIX in the PR/SM LP Data Section
               is incorrect (1, for CP, instead of 6, for zIIP) in both 
               of the zIIP sections for the second zIIP engine, causing 
               MXG to identify those zIIPs as CP Engines, mismatching   
               the engines in the CPU Data Section.  That error is      
               circumvented by revising MXG to use the SMF70TYP value   
               from the CPU data section (which is clearly what IBM had 
               to use in their RMF reports).  A second error was MXG's: 
               the new CP Engine PR/SM section was located AFTER those  
               zIIP sections, but MXG's original SMT logic was correct  
               only when all CPs preceded the zIIPs.  That incorrect    
               MXG logic was revised to now be order independent.       
              -TYPE70PR does NOT contain SMT variables, those data are  
               only output in PDB.TYPE70EN since they can only be       
               populated from "this" system's TYPE70 records.           
   Thanks to Douglas C. Walter, CitiCorp, USA.                          
   Thanks to Brent Turner, Citigroup, USA.                              
                                                                        
Change 33.185 -Labels for TYPE30 ZEDC variables with _INF_/_DEF_ are now
FORMATS        spelled out as INFLATE and DEFLATE.                      
VMAC30        -TYPE74 subtype 9 DIVIDE BY ZERO caused by R749FRQC=1 is  
VMAC74         eliminated by changing test to R749FRQC GT 1 since more  
Aug 11, 2015   than one instance is required to calculate STD (Standard 
Aug 17, 2015   Deviation) statistic.                                    
Aug 20, 2015   New variable PCTCRDBY added to TYPE749 dataset for card  
Aug 30, 2015   busy percentage.                                         
              -TYPE74 variables used to create SSQ (Sums of Squares) are
               no longer kept since the STD variables are calculated.   
              -Variable R749DFMT is now labeled 'PCIE*FUNCTION*TYPE' and
               is decoded by MG074DF format to describe which sets of   
               variables are populated:                                 
                 0='0:DMA COUNTERS'                                     
                 1='1:ETHERNET INTERFACE'                               
                 2='2:WORK UNITS'                                       
               However, records with SMF749DL=16 do not contain R749DFMT
               so R749DFMT will be missing, causing all of these sets of
               variables to have missing values:                        
                0: R749DMAR R749DMAW R749DBYR R749DBYT R749DPKR         
                1: R749DBYR R749DBYT R749DPKR R749DPKT                  
                2: R749DWUP R749DWUM                                    
               SMF749DL=40 is required for PCIE Function Type Data to   
               actually exist.                                          
              -Aug 17: INVALID type 30 zEDC segments (SMF30USO points   
               to the middle of the EXCP Section, or points beyond the  
               end of the record) were just confirmed by IBM support,   
               and occur because the SMF30USN count is not being reset  
               to zero in the "Continuation", MXG MULTIDD='Y' records.  
               The MXG Logic now only inputs the SMF30USO segment when  
               MULTIDD=' ', i.e., only for the base/original record.    
               Aug 25: IBM APAR OA48717 will correct the invalid zEDC   
                       triplet information in the TYPE30 record.        
              -Aug 20: zEDC Compression Ratios for Inflate/Deflate are  
               created and kept in all TYPE30 datasets.                 
              -Aug 30: zEDC Compression Ratios for Inflate/Deflate are  
               created and kept in TYPE749 datasets.                    
   Thanks to Joseph J. Faska, DTCC, USA.                                
                                                                        
Change 33.184  Support for SYNCSORT Release 1.4 (INCOMPATIBLE).  Change 
VMACSYNC       33.102A added support for Release 2.1, which has the same
Aug 11, 2015   SMF data, so this change now tests SYNCVAL GE 1.4 to now 
               populate READTIME and many other variables that are wrong
               without this change.                                     
   Thanks to Joseph J. Faska, DTCC, USA.                                
                                                                        
Change 33.183  Support for MAR Hitachi Command Suite Mainframe Analytics
EXMAR01        Recorder, user SMF records creates these dataset:        
EXMAR02                                                                 
EXMAR03          DDDDDD     MXG       MXG                               
EXMAR04          DATASET    DATASET   DATASET                           
EXMAR05          SUFFIX     NAME      LABEL                             
EXMAR06                                                                 
IMACMAR          MAR01      MARST01   LOST SMF INFORMATION              
TYPEMAR          MAR02      MARST02   LDEV INFORMATION                  
TYPSMAR          MAR03      MARST03   MPB INFORMATION                   
VMACMAR          MAR04      MARST04   PRGP INFORMATION                  
VMXGINIT         MAR05      MARST05   PORT INFORMATION                  
Aug 11, 2015     MAR06      MARST06   MP USAGE TO TWENTY                
                                                                        
Change 33.182 -Major enhancement for character data filtering for ASI   
ADOCRMFV       RMF Monitor III table entries and other improvements.    
ASMRMFV       -These filters are intended for building ad hoc MXG RMF   
Aug  1, 2015   III PDBs for studies avoiding the overhead of generating 
               a full ASI table based PDB.  They control which ASI table
               entries are output to the RMFBSAM file.                  
              -10 new filters are added to support ASI entry selection  
               from this table to the RMFBSAM output file.   These      
               filters are effective only if the ASI table is selected. 
               They are applied in the order shown when multiple        
               different keywords are used.                             
                                                                        
               New Keyword    Aliases                                   
               ------------   --------------------------------------    
               ASISUBSYS=     ASISUB=     TYPETASK=                     
               ASIWORKLOAD=   ASIWKLD=    ASIWNM=     ASIWL=            
               ASIRESGROUP=   ASIRESGRP=  ASIGNM=     ASIRG=            
               ASISRVCLASS=   ASISCLASS=  ASICNM=     ASISC=            
               ASIRPTCLASS=   ASIRCLASS=  ASIRNM=     ASIRC=            
               ASIJOBCLASS=   ASIJCLAS=   ASICLASS=   ASIJC=            
               ASIJOBNAME=    ASIJOBNA=   ASIJOBNM=   ASIJOB=    ASIJN= 
               ASIJESID=      ASIJESNO=   ASIJESNUM=  ASIJESNR=  ASIJID=
               ASIAND         None                                      
               ASIOR          None                                      
                                                                        
              -TUTORIAL:                                                
               Ranges of the form keyword=first:last may be used with   
               any of the above keywords except ASIAND and ASIOR.  The  
               colon character ':' is required for a range              
               specification.                                           
                                                                        
               However, single values may be specified for a range      
               simply as keyword=first and in this case the colon ':'   
               can be omitted.                                          
                                                                        
               All ASI entries GE the first value and LE the last value 
               are selected for output to the RMFBSAM file.  Ranges may 
               not be wild carded only patterns.  The first value in a  
               range may not be GT the last value or an error is noted. 
                                                                        
               Patterns may also be used with any of the above keywords 
               except ASIAND and ASIOR and include one or more wild card
               characters to match the respective ASI data field.       
                                                                        
               Wild                                                     
               Card   Matches                                           
               ----   ------------------------------------------------- 
               *      0 or more characters                              
               %      1 Non-blank character                             
               +      1 Numeric character (0-9)                         
               _      1 Alphabetic character or _  (a-z, A-Z, _)        
               .      1 National character (@, #, $)                    
               !      1 Special character (not a-z, A-Z, 0-9, @, #, $)  
               ?      A blank string if used by itself                  
               ?      1 Blank character (X'40') if used with any other  
                        characters                                      
                                                                        
               See Section 25 in the ADOCRMFV member for more details on
               usage of ranges and patterns.                            
                                                                        
              -ASISUBSYS= selects ASI entries by host Subsystem Name:   
               APPC, JOB, OMVS, STC, TSU, UNKN.                         
                                                                        
               More than one subsystem may be requested.  Ranges and/or 
               patterns may also be used, but are generally unnecessary 
               given the limited possible choices.  Only those IBM      
               subsystems defined in the ASI table are supported.       
               Subsystem names are validated.  The default is           
               ASISUBSYS=ALL.                                           
                                                                        
               For ease in coding and recall there are several value    
               aliases allowed with ASISUBSYS=.                         
                                                                        
               Subsystem                                                
               Name                  Supported Values                   
               ---------   -----------------------------------------    
               APPC        A, AP, APP, APPC, AS, ASC, ASCH              
               JOB         J, JO, JOB, JOBS, B, BA, BAT, BATC, BATCH    
               OMVS        O, OM, OMV, OMVS                             
               STC         S, ST, STC, STA, STAS, STASK, STASKS         
               TSU         T, TS, TSO, TSU, TSUS                        
               UNKN        U, UN, UNK, UNKN, UNKNO, UNKNOW, UNKNOWN,    
                           UNKNOWNS                                     
                                                                        
              -Examples for ASISUBSYS=                                  
               ASISUBSYS=JOB selects only Batch jobs.                   
               ASISUBSYS=J:S selects Batch jobs, OMVS address spaces,   
               and Started Tasks because these all fall into the range. 
               ASISUBSYS=JOB ASISUBSYS=TSO selects Batch job and        
               TSO user address spaces.                                 
              -ASIWORKLOAD= selects ASI entries by 8 character WLM      
               Workload Name.  Both ranges and patterns with wild card  
               characters may be specified.  Up to 64 ranges and 64     
               patterns are supported.  The default is ASIWORKLOAD=ALL. 
              -Examples for ASIWORKLOAD=                                
               ASIWL=PROD:TEST selects all WLM Workloads GE 'PROD' and  
               LE 'TEST' using a range.  Note use of keyword alias      
               ASIWL.                                                   
               ASIWORKLOAD=PROD* selects only address spaces with a WLM 
               Workload Name that begins with 'PROD' as a pattern.      
               ASIWORKLOAD=TEST+++ selects only address spaces with a   
               WLM Workload Name that begins with 'TEST' followed by 3  
               digits as a pattern.                                     
               ASIWORKLOAD=? selects only address spaces with a blank   
               WLM Workload Name as a pattern.                          
               ASIWORKLOAD=%* selects only address spaces with a        
               non-blank WLM Workload Name as a pattern.                
              -ASIRESGROUP= selects ASI entries by 8 character WLM      
               Resource Group Name.  Both ranges and patterns with wild 
               card characters may be specified.  Up to 32 ranges and 32
               patterns are supported.  The default is ASIRESGROUP=ALL. 
              -Examples for ASIRESGROUP=                                
               ASIRG=CAP10:CAP20 selects all WLM Resource Groups GE     
               'CAP10' and LE 'CAP20' as a range.  Note use of keyword  
               alias ASIRG.                                             
               ASIRESGROUP=CAP__ selects only address spaces with a WLM 
               Resource Group Name that begins with 'CAP' followed by 2 
               alphabetic characters as a pattern.                      
               ASIRESGROUP=CAP%%% selects only address spaces with a WLM
               Resource Group Name that begins with 'CAP' followed by 3 
               characters as a pattern                                  
               ASIRESGROUP=? selects only address spaces with a blank   
               WLM Resource Group Name as a pattern.                    
               ASIRESGROUP=%* selects only address spaces with a        
               non-blank WLM Resource Group Name as a pattern.          
              -ASISRVCLASS= selects ASI entries by 8 character WLM      
               Service Class Name.  Both ranges and patterns with wild  
               cards may be specified.  Up to 64 ranges and 64 patterns 
               are supported.  The default is ASISRVCLASS=ALL.          
              -Examples for ASISRVCLASS=                                
               ASISC=BATHIGH:BATLOW selects all WLM Service Classes GE  
               'BATHIGH' and LE 'BATLOW' as a range.  Note the use of   
               keyword alias ASISC.                                     
               ASISRVCLASS=*HIGH selects only address spaces with a WLM 
               Service Class Name that ends with 'HIGH' as a pattern.   
               ASISRVCLASS=*+* selects only address spaces with a WLM   
               Service Class Name that contain only one numeric         
               character as a pattern.                                  
               ASISRVCLASS=? selects only address spaces with a blank   
               WLM Service Class Name as a pattern.                     
               ASISRVCLASS=%* selects only address spaces with a        
               non-blank WLM Service Class Name as a pattern.           
              -ASIRPTCLASS= selects ASI entries by 8 character WLM      
               Report Class Name.  Both ranges and patterns with wild   
               cards may be specified.  Up to 64 ranges and 64 patterns 
               are supported.  The default is ASIRPTCLASS=ALL.          
              -Examples for ASIRPTCLASS=                                
               ASIRC=DB2:TSO selects all WLM Report Classes GE 'DB2' and
               LE 'TSO' as a range.  Note the use of keyword alias      
               ASIRC.                                                   
               ASIRPTCLASS=LOW.%%% selects only address spaces with a   
               WLM Report Class Name that begins with with 'LOW',       
               followed by a national character, and then followed by 3 
               more characters as a pattern.                            
               ASIRPTCLASS=MED++* selects only address spaces with a WLM
               Report Class Name that begins with 'MED', followed by 2  
               digits, and then possibly other characters as a pattern. 
               ASIRPTCLASS=? selects only address spaces with a blank   
               WLM Report Class Name as a pattern.                      
               ASIRPTCLASS=%* selects only address spaces with a        
               non-blank WLM Report Class Name as a pattern.            
              -ASIJOBCLASS= selects ASI entries by JES Job Class.       
               Both ranges and patterns with wild cards may be          
               specified.  Up to 32 ranges and 32 patterns are          
               supported.  The default is ASIJOBCLASS=ALL.              
              -Examples for ASIJOBCLASS=                                
               ASIJC=A:D selects only address spaces with a JES Job     
               Class of A, B, C, or D as a range.  Note use of the      
               keyword alias ASIJC.                                     
               ASIJOBCLASS=+ selects only address spaces with a numeric 
               JES Job Class of 0-9 as a pattern.                       
               ASIJOBCLASS=? selects only address spaces with a blank   
               JES Job Class as a pattern.                              
               ASIJOBCLASS=%* selects only address spaces with a        
               non-blank JES Job Class as a pattern.                    
              -ASIJOBNAME= selects ASI entries by 8 character z/OS Job  
               Name.  Job Name characters are validated to those allowed
               by JCL syntax.  Both ranges and patterns with wild cards 
               may be specified.  Up to 64 ranges and 64 patterns are   
               supported.  The default is ASIJOBNAME=ALL.               
              -Examples for ASIJOBNAME=                                 
               ASIJN=PROD1234:PROD5678 selects only address spaces with 
               a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a     
               range.  Note use of the keyword alias ASIJN.             
               ASIJOBNAME=.* selects only address spaces with a Job Name
               that begins with a national character as a pattern.      
               ASIJOBNAME=*++ selects only address spaces with a Job    
               Name that ends with 2 numeric digits as a pattern.       
              -ASIJESID= selects ASI entries by 8 character JES Job     
               Identification.  Both ranges and patterns with wild cards
               may be specified.  Since a JES Id is one character       
               followed by 7 digits or three characters followed by 5   
               digits not all pattern characters may be used with this  
               keyword.  For convenience any leading zeros in the       
               numeric portion of the JES Id may be omitted and will be 
               filled in automatically.  Up to 64 ranges and 64 patterns
               are supported.  The default is ASIJESID=ALL.             
              -Examples for ASIJESID=                                   
               ASIJID=J0000100:J0001123 selects all address spaces      
               with batch JES Id numbers GE 100 and LE 1123 as a        
               range.  Note use of keyword alias ASIJID.                
               ASIJID=J100:J1123 selects the same address spaces as     
               above with the leading zeros omitted for coding          
               convenience.                                             
               ASIJESID=JOB12345:JOB32001 selects all address spaces    
               with batch JES Id numbers GE 12345 and LE 32001 for      
               installations with 5 digit JES Id numbers as a           
               range.                                                   
               ASIJESID=J1* selects all batch address spaces with a     
               JES ID that begins with '1' as a pattern.                
              -ASIAND (default) indicates that selection results from   
               two or more different ASI filter keywords are logically  
               ANDed.                                                   
              -ASIOR indicates that selection results from two or more  
               different ASI filter keywords are logically ORed.        
              -Examples of ASIAND/ASIOR:                                
               With ASIAND in effect                                    
               ASISUBSYS=BATCH  ASIJOBNAME=XYZ*                         
               selects ONLY batch jobs whose those job names begin with 
               'XYZ'.  ASIAND (default) provides more restrictive ASI   
               entry selection.                                         
               With ASIOR in effect                                     
               ASISUBSYS=BATCH   ASIJOBNAME=XYZ*                        
               selects ALL batch jobs OR any job names beginning with   
               'XYZ' even if they ran under another subsystem.  ASIOR   
               provides less restrictive ASI entry selection.           
              -Selection results from repeats of the SAME ASI filter    
               keyword are always logically ORed.                       
              -New parameter SYSAND (default) indicates that selection  
               results from the SYSPLEX= and SYSTEM= filter keywords for
               the Data Set Header (DSH) table when both are specified  
               are logically ANDed.                                     
              -New parameter SYSOR indicates that selection results from
               the SYSPLEX= and SYSTEM= filter keywords for the Data Set
               Header (DSH) table when both are specified are logically 
               ORed.  SYSOR must be coded when needed.                  
              -Examples of SYSAND/SYSOR:                                
               With SYSAND in effect                                    
               SYSPLEX=PROD    SYSTEM=SYSP                              
               selects ONLY RMF III data sets originating from the PROD 
               sysplex AND the SYSP LPAR.  SYSAND (default) provides    
               more restrictive RMF III data set selection.             
               With SYSOR in effect                                     
               SYSPLEX=PROD    SYSTEM=SYSP                              
               selects ALL RMF III data sets originating from the PROD  
               sysplex OR any data sets for the SYSP LPAR even if SYSP  
               is part of a different Sysplex.  SYSOR provides less     
               restrictive RMF III data set selection.                  
              -Selection results for multiple SYSPLEX= values are always
               logically ORed.                                          
              -Selection results for multiple SYSTEM= values are always 
               logically ORed.                                          
              -The '_' pattern character now matches lower case in      
               addition to upper case alphabetic characters in a source 
               string.                                                  
              -The '_' pattern character will now match an underscore in
               a source string.  While this character is not technically
               alphabetic, the underscore is sometimes used in some WLM 
               names for better legibility.                             
              -A new pattern character '?' will allow selection of      
               completely blank source strings when used only by itself.
               When '?' is used with other characters in a pattern a    
               single imbedded blank in a source string is matched.     
              -Example of ? pattern character:                          
               ASIRPTCLASS=? selects all ASI entries that do not have a 
               WLM Report Class assigned or that could not be found by  
               ASMRMFV.  That field in the ASI entry must be completely 
               blank to select that entry.                              
              -A new pattern character '!' will match special characters
               in a source string.  For this purpose special characters 
               are those bytes in the EBCDIC code table that are NOT    
               alphabetic (a-z, A-Z), numeric (0-9), national (@,#,$),  
               or blank (X'40') and have been assigned to a character.  
              -Example of ! pattern character:                          
               X'5C' is assigned the EBCDIC asterisk '*' and would match
               the ! pattern character.  However, X'00' does not match  
               this pattern character because no EBCDIC character is    
               assigned to this byte.                                   
               ASIJOBNAME=!MASTER! selects the *MASTER* address space.  
               Coding ASIJOBNAME=*MASTER* in this case instead may      
               produce different results because the '*' is a pattern   
               character itself representing zero to many characters.   
               So any job name with 'MASTER' imbedded would be selected.
              -Section 5 "Input Data Selection Parameters" is updated   
               with discussion of all the new ASI selection keywords and
               aliases.                                                 
              -A new Section 25 "Ranges and Patterns" has been added to 
               the documentation to explain use of these features in    
               detail.                                                  
              -A new Section 26 "Summary" is added to replace the old   
               Section 25 and includes a summary of the new ASI keywords
               and all pattern characters.                              
              -New parameter SHOWALL (alias SA) indicates that the      
               settings for all possible filter keywords that take range
               and/or pattern values are to be displayed in the ASMRMFV 
               log in message RMFV006I even when no filters have        
               actually been specified for a particular keyword.  These 
               display as keyword=ALL.                                  
              -New parameter NOSHOWALL (alias NOSA) indicates that only 
               filter keywords that have actual range and/or pattern    
               values specified are to be displayed in the ASMRMFV log  
               in message RMFV006I.  This option helps reduce the size  
               of the ASMRMFV log.  NOSHOWALL is the default.           
              -Section 6 "Report Control Parameters" is updated to add  
               SHOWALL/NOSHOWALL parameters.                            
              -Several messages are slightly changed either to          
               accommodate longer ASMRMFV keywords for the ASI filter   
               selection or to display their settings.                  
                                                                        
Change 33.181  Enhancement for RMFINTRV/TRNDRMFI to ADD variables to be 
VMXGRMFI       kept.  While the existing VMXGRMFI program provides many 
Jul 30, 2015   arguments (R70ID, R70MAX, R70SUM, etc) that can be used  
               in your tailored %VMXGRMFI call, those arguments require 
               you to list ALL of the variables to be kept.  This change
               adds the ADD70ID=, ADD70MAX=, etc., arguments that only  
               list the variables to be added.                          
   Thanks to Joachim Sarkoschitz, DATEV, GERMANY.                       
                                                                        
Change 33.180  Support for MQ Version 8 subtype 215 record which creates
VMAC115           DDDDDD    DATASET    DESCRIPTION                      
VMXGINIT          TY115X    TY115215   TYPE 115 ST 215 BUFFER STATS     
Jul 30, 2015  -New variables QPSTFLAG0 and QPSTFLAG1 added to TY115215  
               and MQMBUFER datasets.                                   
                                                                        
Change 33.179 -z13 in SMT Mode could have blank LPARNAME in TYPE70EN and
VMAC7072       MXG variable SMF70MTTT (misnamed, IBM field is SMF70MTIT)
Jul 29, 2015   is now deaccumulated in PDB.TYPE70EN.                    
Aug  4, 2015  -For SMT Mode, for complete detail per-engine data, use   
               the PDB.TYPE70EN dataset instead of PDB.TYPE70.          
              -This change also populated SMF70WTI/WTS/WTU in TYPE70PR  
               with zeros or real values that were previously missing.  
              -Aug 4. Corrected SORT error due to delete with TYPE7072. 
                                                                        
Change 33.178  Many of the ANAL* members in JCLPDB9 were old (some had  
JCLPDB9        not been touched in decades) or archaic and in some cases
Jul 29, 2015   had been replaced by more robust and up to date members. 
               These are ONLY included as examples; it is NOT likely    
               that you would execute ALL of these example ANALxxxx     
               reports in your production BUILDPDB.                     
                 ANALCONT - replaced by VMXGPRAL                        
                 ANALMPL  - replaced by ANALINIT                        
                 ANALTURN - replaced by ANALINIT                        
                 ANALAVAL - removed since successful execution requires 
                            user tailoring                              
                 ANALESV  - obsolete                                    
                 GRAFWRKX - added                                       
                 GRAFCEC  - added                                       
                 All report members now have comments describing them   
                 Commented ODS statement added to route output to PDF   
                                                                        
Change 33.177 -A new parameter PRINT was added.  A value of ALL/DETAIL  
ANALRANK       generates a report for each of the variable named in the 
ANALPROG       VARS parameter, and a summary report with the rankings   
Jul 28, 2015   of ALL variables is produced.                            
               A value of DETAIL generates only the individual named    
               variable report.                                         
               A value of SUMMARY only generates the summary report.    
               SUMMARY is assumed if PRINT is left blank.               
              -A third example generates a report similar to ANALPROG.  
                                                                        
Change 33.176  Unused Change.                                           
                                                                        
Change 33.175  Support for IHDRBBMQ "Infile Header Exit" for TYPEBBMQ   
IHDRBBMQ       and associated macro variable &MACBBMH permits selection 
VMACBBMQ       of data to be output after the BBMQ Header has been read.
VMXGINIT                                                                
Jul 27, 2015                                                            
                                                                        
Change 33.174  The number of IFL processors in an LPAR was incorrectly  
VMXG70PR       set to the number of IFLS on the CEC and IFL busy was    
Jul 21, 2015   also incorrect since it was based on the CEC not on the  
               LPAR.                                                    
                                                                        
Change 33.173  For the z13, SM1132SP was forced because the value in the
ASUM113        z13 SMF 113 records is not correct, but SM1132SP=5000 is 
VMAC113        the correct value, not 5.  This impacted only EFFGHZ and 
Jul 22, 2015   LPARBUSY values.                                         
   Thanks to David Cogar, Wells Fargo, USA.                             
                                                                        
====== Changes thru 33.172 were in MXG 33.07 dated Jul 22, 2015=========
                                                                        
Change 33.172 -If you specified USERADDS=NOUSERID and IDs over 128 were 
ANALID         found, an EOF test that built the macro variable that was
Jul 22, 2015   used in UTILBLDP was never executed.                     
              -A superfluous RETURN; caused an error if you specified   
               SMFAUDIT=NO.                                             
                                                                        
Change 33.171  MXGLOG code failed to wrap a PUT with a DO group, causing
VMAC120        potentially MANY of these log messages to be printed"    
Jul 20, 2015     ***SMF 120 SUBTYPE 9 UNEXPECTED MULTIPLE SEGMENT.      
                _N_=2 SYSTEM=XX SMFTIME=19JUL2015:00:04:54.20 SM1209AK=1
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
====== Changes thru 33.170 were in MXG 33.07 dated Jul 17, 2015=========
                                                                        
Change 33.170  The test to identify IPV6 IP address was incorrect.      
VMACCTCP                                                                
Jul 16, 2015                                                            
                                                                        
Change 33.169  The z13 protection for zero divide for TLB1CYCL,PTEPCTMI,
ASUM113        TLB1MSRT still used the zEC12 EXTND133+EXTND140 values   
Jul 16, 2015   but the z13 changed the divisor to EXTND129+EXTND134,    
               which should have been also been used for the zero test. 
               Luckily, the incorrect test was non-zero so the correct  
               values were calculated.                                  
   Thanks to David Cogar, Wells Fargo, USA.                             
                                                                        
Change 33.168  The SMF 30 INSTRUCTION count variables require HIS to be 
VMAC30         enabled, or all _INST counters will be missing values.   
Jul 15, 2015   These two new variables are now created to identify why. 
                SMF30_INSTCAPTDISRUPTION='NO*INSTRUCTION*COUNTERS'      
                SMF30_INCOMPLETE_DATA='INSTRUCTION*COUNTERS*INCOMPLETE' 
               From Bob Rodgers SHARE 2014 SYSPROG Goody Bag notes:     
               - To get instruction counts in Counter Data Section,     
                 HIS must activate the CPU Measurement Facility to      
                 collect at least the basic counter set.                
                - MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B) is minimal        
                - MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B,E) is recommended  
                - SMFPRMxx must contain the keyword SMF30COUNT          
   Thanks to Alfred Holz, Express-Scripts, USA.                         
                                                                        
Change 33.167  MXGDB2B1 report checked for a macro variable that could  
ANALDB2R       only be defined if you are on SAS 9.4 or higher.  A %LET 
Jul 13, 2015   was added to instantiate the variable to protect ancient 
               versions.                                                
                                                                        
Change 33.166  Support for Correlog z/OS Agent SMF User record created  
EXTYCZA        new dataset.                                             
IMACCZA          dddddd   dataset   Description                         
TYPECZA          TYCZA    TYPECZA   Correlog z/OS AGENT                 
TYPSCZA                                                                 
VMACCZA                                                                 
VMXZGINIT                                                               
Jul 29, 2015                                                            
                                                                        
Change 33.165  Subtype 24 XPTR records decoded                          
VMACXPTR                                                                
Jul  9, 2015                                                            
                                                                        
Change 33.164 -If you specified READDB2 with IFCIDS=ALL and PDBOUT=WORK 
READDB2        some IFCIds (22 and 217) that create multiple datasets   
VMAC102        failed in their sort of those additional datasets looking
Jul  8, 2015   for a PDB LIBNAME.  In addition if you specifically      
               requested (for example) IFCIDS=I22 it would fail looking 
               for _C102I22 since the code to create that dataset is in 
               _C102022.  READDB2 now converts I22 to 22 U17 v17 T17 to 
               217.                                                     
              -The _S102 "sort all 102s" macro now skips 202/225/230/239
               and 369 because they are NOT 102s and instead are created
               in 100.2, 100.4, 100.3, 101.1, and 100.5 ID/Subtypes.    
                                                                        
Change 33.163  CICSTRAN variable PHSTARTM was incorrectly INPUT as PIB4 
VMAC110        time of day, and PHSTARCN was input as a counter, but now
UTILEXCL       PHSTARTM is INPUT TODSTAMP8, formatted DATETIME21.2, and 
Jul  7, 2015   converted to local zone; PHSTARCN should never have been 
               created so it no longer is.                              
   Thanks to David Shaw, M&T Bank, USA.                                 
   Thanks to Doug Donoho, M&T Bank, USA.                                
                                                                        
Change 33.162  "MXGLOG" option to send MXG Messages to MXGLOG filename. 
VMXGINIT       Macros %MXGLOGDO, %MXLOGPUT and MXLOGEND are defined in  
VMACSMF        VMXGINIT.  If an //MXGLOG DD or FILENAME MXGLOG is used, 
Jul 10, 2015   MXG will automatically enable and send MXG messages to   
Jul 12, 2015   the MXGLOG file on z/OS; on ASCII you send those messages
Jul 14, 2015   to FILENAME MXGLOG 'c:\mxg\mxglog.txt'; but note that the
Nov 23, 2015   file is written with MOD, so you may need to clear the   
               file with DATA _NULL_; FILE MXGLOG;                      
               Status:  These members' messages are updated:            
                 VMAC0    VMAC0203 VMAC10   VMAC113  VMAC115            
                 VMAC116  VMAC120  VMAC21   VMAC22   VMAC23   VMAC26J2  
                 VMAC30   VMAC42   VMAC6    VMAC6156 VMAC7    VMAC7072  
                 VMAC71   VMAC73   VMAC74   VMAC75   VMAC76   VMAC77    
                 VMAC78   VMAC89   VMAC8911 VMACDB2  VMACID   VMACTMNT  
                 VMACSMF  VMXG70PR                                      
               These include all members in the default BUILDPDB.       
               The last change-date wasn't updated in these members, as 
               the changes did not impact the output datasets.          
               The syntax of the messages written to MXG log will be    
                  MXGLOG::MXGtype.member.nnn                            
               where type is INFO, WARNING or ERROR,                    
                     member is the member name that creates the message 
                     nnn is a sequence number in that member name.      
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 33.161  Support for MOBILEWRK to read BMC's IMF/CIMSTRAN FA IMS  
MOBWRKI3       log records to create CIMSTRAN and use in MOBWRKI3, or   
MOBWRKI4       to use existing CIMSTRAN dataset(s) in MOBWRKI4.         
MOBILWRK       Only comments updated in MOBILWRK.                       
Jul  6, 2015                                                            
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 33.160  Reserved Change Number, now Unused.                      
                                                                        
Change 33.159  Support for ANALID and VMXGSRCH to decompress DB2 or CICS
ANALID         records, on z/OS when EXITCICS/CICSIFUE exit is not used,
DB2DECOM       or on ASCII, where EXITCICS cannot be installed.         
MXGDECOM      -For ANALID, the DB2 Product section, containing IFCID and
SMFSRCH        SUBTYPE and DB2 Version, is compressed, so those values  
UTILBLDP       are missing.  Optional new SMFDECOMP=DB2 argument invokes
VMAC110        the MXG internal code to decompress 101 and 102 records  
VMACDB2        so those values can be reported. (Not needed for CICS as 
VMACSMF        its version/subtype is the uncompressed area.)           
VMXGINIT      -For SMFSRCH, compressed CICS 110 and DB2 101/102 records 
Jul 17, 2015   couldn't be searched. New SMFDECOMP=BOTH or DB2 or CICS  
               argument will invoke the MXG decompression code so those 
               records can be searched for the LOOKFOR text.            
              -WARNING: The internal Code decompression requires A LOT  
               more CPU time than the EXITCICS exit.  A 5GB DB2 SMF file
               required 34 CPU minutes with the internal algorithm, but 
               only 13.5 CPU minutes using EXITCICS.  That is why YOU   
               must choose to enable the SMFDECOMP decompression.       
              -You can also force decompression of CICS and/or DB2 data 
               when only the _SMF (decode SMF header macro) is used:    
                 %LET MXGDECOMP= BOTH or DB2 or CICS ;                  
                 %INCLUDE SOURCLIB(VMACSMF);                            
                 DATA; _SMF;                                            
               The decompressed record will be in variable _INFILE_.    
              -UTILBLDP is invoked by SMFSRCH to create all datasets in 
               the selected SMF records; testing exposed an incorrectly 
               built macro for type 102 when BUILDPDB=NO and the IFCID  
               was only 2 characters long.                              
              -The decompression %MACROs MXGDECOM and DB2DECOM are now  
               defined in those members and the redundant definitions   
               in VMACSMF, VMAC110 and VMACDB2 are removed, since the   
               AUTOCALL facility will resolve them when referenced.     
                                                                        
Change 33.158  Type 6 ESS zero length segment caused INPUT STATEMENT    
IMAC6ESS       EXCEEDED STOPOVER error condition when the segment was   
Jul  3, 2015   the last ESS segment.  GEPARMKY=0016x and 0027x have been
               observed with zero segment length, which would seem to be
               an IBM error (to be investigated with IBM Support) but   
               protection is added to prevent the STOPOVER error.       
               In testing this change with on-hand SMF 6 records from   
               other users four new ESS segments are now decoded:       
                 ESSCKPTPAGE ESSOVERLAYB ESSOVERLAYF ESSDUPLEX          
   Thanks to Andreas Menne, Finanz Informatik, GERMANY.                 
                                                                        
Change 33.157  zVM XAM ERROR SYTCUP SEGMENT LENGTH occurs if the online 
VMACXAM        engine count is changed, because XAM does NOT change the 
Jul  1, 2015   value in SYTNLPS, which always contains the number of    
               INSTALLED engines (and the same is true of variable NCPUS
               from the SUBSUM segment).  This change recalculates the  
               number of engines into SYTNLPS based on SEGLEN, which XAM
               does update, and which is then used to input the actual  
               online CP segments.                                      
   Thanks to Patricia Hansen, ADP, USA.                                 
   Thanks to Mike Chaves, ADP, USA.                                     
                                                                        
Change 33.156  Support for APAR OA44525, zHPF Extended Distance II.     
VMAC78        -New variables added to TYPE78CF dataset:                 
VMAC79           R783CTMW='TRANSPORT*MODE*WRITE*COUNT'                  
Jun 30, 2015     R783CTRD='1ST XFER*READY*DISABLED*WRITE COUNT'         
                 R783TMWM='XPORT*WRITE*COUNT*DCM CHANNELS'              
                 R783TRDM='1ST XFER*READ*DISABLED*DCM CHANNELS'         
              -New variables added to TYPE79EF dataset:                 
                 R79ECTRD='1ST XFER*READY*DISABLED*WRITE COUNT'         
                 R79ETMWM='XPORT*WRITE*COUNT*DCM CHANNELS'              
                 R79ETRDM='1ST XFER*READ*DISABLED*DCM CHANNELS'         
                 PCTPTHBY='PERCENT*CHPID PATH*BUSY'                     
                                                                        
Change 33.155 -TYPE74ST dataset now has Storage Class Memory variables  
VMAC74         that were incorrectly output in TYPE74MO dataset, which  
Jul  5, 2015   should never have been created and no longer is.         
Oct  4, 2015  -Text added Oct 4, 2015:                                  
               Variable R744SNAM=STRUCTURE NAME was added to TYPE74DU   
               and TYPE74HO datasets, but not noted in the change text, 
               nor was it added to the _BTY74HO BY List, but in Oct it  
               was observed that the addition of R744SNAM to TYPE74HO   
               caused a CORRECT INCREASE in number of observations in   
               PDB.TYPE74HO (even though the WORK.TYPE74HO had the same 
               number of observations).  Because R744SNAM was not kept, 
               the previously NODUP sort was incorrectly removing obs   
               that were not duplicates, and its addition accidentally  
               prevented their removal.  Change 33.234 now updates the  
               BY list to explicitly include R744SNAM.                  
                 -MXG Internal Note on no longer creating a dataset: The
                  macro variables PTY74MO/WTY74MO in VMXGINIT, and all  
                  the _xTY74MO old-style macro tokens must still be     
                  defined in VMAC74, just in case they were used in user
                  tailoring.  Member EXTY74MO also must exist to protect
                  tailored code, and the_STY74MO token was removed from 
                  _STY74 to prevent a dataset not found condition.      
   Thanks to Sandy Stromberg, OPTUM, USA.                               
                                                                        
Change 33.154  BY statement was missing on SGPLOT and GPLOT so title1   
ANALCAPD       had #BYVAL1 rather than the value of CECSER.             
Jun 25, 2015                                                            
                                                                        
Change 33.153  IMF version 5100 record caused INPUT STATEMENT EXCEEDED  
VMACCIMS       ERROR due to MXG misalignment of the Trace Table that    
Jun 24, 2015   caused TRNEXTEN=1 when it should have been zero.         
                                                                        
Change 33.152  ANALWHO (WHO deleted/modified my Dataset) is revised to  
ANALWHO        check and see if any data was found and now confirms     
Jun 24, 2015   in an MXGNOTE that observations were NOT found.          
               The REPORT data that is created is now deleted before    
               ending.  JOB parameter is added to allow you to specify  
               a specific job name to seek.                             
   Thanks to Dave Ireland, USDA, USA.                                   
                                                                        
Change 33.151   ERROR.VMAC115.OFFQCCT. INVALID SECTION TRIPLET.         
VMAC115         ERROR.VMAC116.LENQWHS. INVALID PRODUCT SECTION TRIPLET. 
VMAC116         are corrected.  Change 32.172 created new MQ V8.0       
Jun 24, 2015    datasets MQCHIN and MQCHININ, but documented that the   
Jun 30, 2015    code had not been tested with data.  Now it has been.   
               -The MQCHIN 115 records ADP, SSL, and DSN segments are   
                significantly longer than documented and don't agree    
                with their contents in CSQDQCTA; this will be pursued   
                with IBM MQ Support.                                    
               -The MQCHININ 116 dataset is only output if there was    
                activity; that logic is in _ETY116A if you do want to   
                output all segments.                                    
               -Jun 30: WTASCTSR is now correctly aligned and non-zero. 
   Thanks to Robert Miles Standish, UBS, USA.                           
   Thanks to Thomas Orlando, UBS, USA.                                  
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.150  Variable PCTDLZIP='ZIP*DELAY*PERCENT' is created in the  
VMAC7072       TYPE72GO dataset.                                        
Jun 22, 2015                                                            
   Thanks to Jan Tielemans, KBC, BELGIUM.                               
                                                                        
Change 33.149  Dataset TYPE115 variable QESDBFPT was not divided by     
VMAC115        4096.                                                    
Jun 22, 2015                                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.148 -SMFSRCH can't search for text in compressed DB2 or CICS  
SMFSRCH        SMF records unless the EXITCICS INFILE exit is installed 
Jun 22, 2015   on z/OS.                                                 
              -At present, on ASCII, SMFSRCH can not search compressed  
               records because the internal decompression algorithm is  
               executed AFTER the _INFILE_ has been populated. This is  
               under investigation for a possible solution.             
              -If SMFSRCH found type 102 records with an IFCID LT 100,  
               it incorrectly called UTILBLDP with a token of 102.83,   
               which should have been 102.083.  Now fixed.              
              -SMFSRCH will now suppress processing of 102 records if a 
               subtype of 0 is found, since this means the data is      
               compressed, and you are not using the EXITCICS exit.     
              -If a subtype GE 8000 is found the subtype is then        
               converted to BMC.                                        
                                                                        
CHANGE 33.147  Analysis of batch queue times using SMF30HQT SMF30JQT    
ANALQBAT       SMF30RQT and SMF30SQT variables rather than values that  
Jun  20, 2015  are calculated as in ANALINIT. This is a member which    
               you need to tailor in your USERID.SOURCLIB. There are    
               changes you must make (look for CHANGE HERE in the       
               member.)  It requires are least SAS 9.3 since it uses    
               ODS and creates PDF output.                              
                                                                        
Change 33.146  There are two SECID='0B'x SMF Type=22 records.  RECIND=9 
EXTY22PB       records create the existing TYPE22_B with the I/O Config 
IMAC22         changes. New TYPE22PB dataset is created from SECID='0B'x
VMAC22         that do not have RECIND=9, with Reconfigured PCIE.       
VMXGINIT       function identifiers.                                    
Jun 19, 2015                                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.145  BVIR VTS Grid dataset BVIR33 was incorrect for the second
VMACBVIR       and subsequent Grid-Cluster Containers.                  
Jun 18, 2015   Variable TMDLYCPY is now kept in BVIR33, overlooked.     
Jul  7, 2015   Variables MAXAHCT AVEAHCT MAXBHCT AVEBHCT are now kept in
               BVIR20.                                                  
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
   Thanks to Mike Creech, Black Knight Financial Services, USA.         
                                                                        
Change 33.144  Support for SMF Type 119 new Subtypes 94 and 95 create   
EXT11994          dddddd   dataset  description                         
EXT11995          T11994   TYP11994  SSH Client Connect Start           
FORMATS           T11995   TYP11995  SSHD Server Connect Start          
IMAC119        The $MG110AM/CI/MA/CO formats were updated with new      
VMAC119        values.                                                  
VMXGINIT                                                                
Jun 23, 2015                                                            
   Thanks to Hyrum Smith, Schwab, USA.                                  
                                                                        
Change 33.143 -INPUT STATEMENT EXCEEDED NDM-CDI PT RECORD, shortened by 
VMACNDM        4 bytes, variable PTUNCH34 now $EBCDIC30 vs 34.          
Jun 15, 2015  -Truncated fields for CT record - MXG Message is correct, 
               vendor contacted.                                        
                                                                        
Change 33.142  Variable QWACATWT was missing the divide by 4096 and the 
VMACDB2        variable QWACPQCT should have been input &PIB.4.         
Jun 15, 2015                                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
====== Changes thru 33.141 were in MXG 33.06 dated Jun 11, 2015=========
                                                                        
Change 33.141  Documentation only.  The EXITCICS/CICSIFUE INFILE exit   
EXITCICS       WILL NOT work with VSAM SMF input, on SAS log shown as   
Jun 11, 2015              DSNAME=SYS1.MAN1,                             
                          VOLUME=Z21SMF,DISP=SHR,UNIT=3390,             
                          TYPE=NONINDEXED,SPANNED=YES,                  
                          RECORDSIZE=(.,32767),AMP=('AMORG'),RECORDS=0  
                Maybe the DSNAME=SYS1.MAN1 is a clue, but it is the AMP=
                parameter that identifies the SMF file as a VSAM file.  
                The SAS log also reported:                              
                   MXGNOTE: SMF EXIT CICS IS IN USE.                    
                   ERROR: ERROR DETECTED BY INFILE/FILE EXIT: .         
                   FATAL: UNRECOVERABLE I/O ERROR DETECTED IN THE       
                          EXECUTION OF THE DATA STEP PROGRAM.           
   Thanks to Greg Meyer, ISUZU, USA.                                    
                                                                        
Change 33.140  RMF III RCD records INCOMPATIBLY changed for z13 causing 
VMACRMFV       invalid values in SVCLCNM and other variables in RBRCDR. 
Jun 11, 2015   The change apparently was RMF APAR OA44101 supporting    
Jun 16, 2015   Simultaneous MultiThreading (SMT) on the IBM z13 server  
               that extended the Resource Collection Data Period Data   
               (RCDPD) array entries in the RMF Monitor III RCD table.  
              -Test IF RCDPLSC GE 0 corrected to IF RCDPLSC GT 0. When  
               RCDPLSC=0, there is no LC Service Class Extension. Have  
               NOT ACTUALLY seen RCDPLSC=0, so this is for safety and   
               not an actual error.                                     
   Thanks to Michael Kampert, Schwab, USA.                              
                                                                        
Change 33.139  Contributed Processor Topology Report for z13, using SMF 
ANAL9914       Type 99 Subtype 14 records. Syntax for SYS1 report, Z13: 
Jun  9, 2015     %ANAL9914(SYSTEM=SYS1,SYSTYPE=Z13)                     
   Thanks to Raymond J. Smith, OPTUM, USA.                              
                                                                        
Change 33.138 -z13 in SMT Mode, TYPE70EN had missing or mis-aligned     
VMAC7072       values when there was a second zIIP engine.              
Jun  9, 2015  -z13 in SMT Mode, PCTMVSBY was incorrect by a few percent 
Jun 11, 2015   because LPARBUSY time was incorrectly subtracted.        
              -z13 in SMT Mode zIIP variables in TYPE70xx datasets,     
               could be missing, or DUPLICATE RECORD message could be   
               printed.  REQUIRED FOR SMT.  The MXG SMT support has come
               in several iterations as new sequences of data exposed   
               untested logic but this appears to finally resolve the   
               one-to-many merge. If you are testing SMT on z13, please 
               email MXG Support with subject: SMT UPDATES so we can    
               inform you if there are any further required changes for 
               SMT mode.                                                
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
   Thanks to Scott Wiig, US Bank, USA.                                  
   Thanks to Douglas C. Walter, CitiCorp, USA.                          
   Thanks to Brent Turner, Citigroup, USA.                              
                                                                        
Change 33.137  Support for Compuware ABEND-AID USER SMF Record creates  
FORMATS        new ABENDAID dataset with many details on each intercept.
EXABNAID                                                                
IMACAA                                                                  
TYPEAA                                                                  
TYPSAA                                                                  
VMACAA                                                                  
VMXGINIT                                                                
Jun  5, 2015                                                            
                                                                        
Change 33.136  Support for MainView for IMS 5.2 (a/k/a IMF, CONTROL/IMS)
FORMATS        for COMPATIBLE changes.                                  
VMACCIMS      -New variables added to CIMSTRAN:                         
Jun  3, 2015     TRNDLCMX='MAX*DC*CALL*TIME'                            
                 TRNDLDMX='MAX*DB*CALL*TIME'                            
                 TRNESSMX='MAX*ESS*CALL*TIME'                           
                 TRNDLWMX='MAX*WAIT*NOT-IO*TIME'                        
                 TRNDLDTH='DLI DB*OR*ESS CALLS*GE THRESHOLD'            
                 TRNDLCTH='DLI*DC* GE*THRESHOLD'                        
                 TRNDLDER='DLI*CALL*ERRORS'                             
                 TRNESSER='ESS*CALL*ERRORS'                             
                 TRN1STCP='SCHD*FIRST*DLI*CPU'                          
              -New values added to variables SMQFLAG, PROGTYPE          
               FLGSPCHR.                                                
                                                                        
Change 33.135  Support for Optional CICS User CMODNAME=VMX CMODHEAD=VMX 
IMACICVP       segments.                                                
IMACICVQ                                                                
IMACICVR                                                                
IMACICVT                                                                
IMACICVU                                                                
IMACAAAA                                                                
UTILEXCL                                                                
VMAC110                                                                 
Jun  9, 2015                                                            
                                                                        
Change 33.134 -ANALDB2R mis-reported the number of reports produced     
ANALDB2R       when accounting reports were requested but no data met   
READDB2        the selection criteria.                                  
May 26, 2015  -READDB2 applied selection criteria inappropriately to    
               the 105 106 and 107 IFCIDS which are subsystem specific. 
              -ANALID parameter added to ANALDB2R to pass to READDB2 so 
               that you can see what records were in the input data.    
              -Page headings on PMSPR01 were incorrect for the first    
               page of the second and subsequent DB2 subsystems reports.
              -If the input to PMLOL02 and PMLOK03 was a SAS dataset on 
               tape, the T102S172 dataset was missing from the PROC COPY
               that moves the data to DASD (zOS only) since there must  
               be concurrent dataset open for these reports             
   Thanks to Judy Xu, WiPro, USA.                                       
                                                                        
CHANGE 33.133  ZOSEM User SMF INPUT STATEMENT EXCEEDED because MXG had  
VMACOSEM       expected an 8-byte Resource field length.  Since this    
May 21, 2015   resource looks like it might be a DSNAME, the resource   
               array variables are expanded to 44 bytes.                
   Thanks to John Schoenbeck, IBM Global Services, USA.                 
                                                                        
CHANGE 33.132  These eight new TYPE30 variables with zEDC metrics were  
VMAC30         misaligned because the triplet was incorrectly input:    
May 21, 2015     SMF30_US_COMPRREQ      SMF30_US_COMPRREQ_PROB          
Jan  4, 2016     SMF30_US_QUEUETIME     SMF30_US_EXECTIME               
                 SMF30_US_DEF_UNCOMPRIN SMF30_US_DEF_COMPROUT           
                 SMF30_US_INF_COMPRIN   SMF30_US_INF_DECOMPROUT         
               These variables now also have "ZEDC" in their label.     
              -Jan 2016: APAR OA48268 corrects invalid values in the    
               first four variables above, especially when SMF data     
               is from logstream processed by IFASMFDL.                 
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
CHANGE 33.131 -SMFSRCH failed if the SMF file contained only one USER   
SMFSRCH        record type and you had specified that nnn type value in 
UTILBLDP       your USERADD=XXXX/nnn argument. The USERADD= erroneously 
May 22, 2015   had nnn which generated a call to INCLUDE VMACnnn.       
May 25, 2015  -SMFSRCH now invokes %ANALID report to tabulate the SMF   
               records, subtypes, versions, etc., that were selected;   
               any undefined user records selected are identified.      
              -SMFSRCH LOOKFOR= supports multiple strings with ANDOR    
               choice, and new SELECTION= argument lets you write your  
               own IF statement for the selection.                      
              -UTILBLDP needed revision to delete the ID VIEW that was  
               introduced with the addition of %ANALID.  If ID is found 
               in a non-BUILDPDB context the _SID sort is suppressed and
               the ID VIEW is deleted.                                  
              -ASCII only, SMFSRCH.  LENGTH from INFILE statement is now
               used in place of LENGTH=LENGTH(_INFILE_) for the written 
               length, after an SMF 79 record with a blank last byte was
               truncated, and detected by an MXG ERROR message, causing 
               the SAS documentation TO BE READ, that stated that the   
               LENGTH() function returns the length of the string, but  
               EXCLUDING any trailing blanks.                           
   Thanks to Mike Obrien, Bank of America, USA.                         
                                                                        
CHANGE 33.130  Missing values in SMF70xxx variables in PDB.ASUM1131 and 
ASUM113        (now archaic PDB.ASUM113 from no longer supported subtype
May 20, 2015   2 Type 113s) if the SMF SYSTEM variable in Type 70 does  
               not match SMF70STN in the PR/SM LCPUADDR segments. This  
               logic has been used since always to read from TYPE70PR   
                   IF SYSTEM=SMF70STN;                                  
                   SYSTEM=SYSNAME;   (IBM SMF70SNM - From IEASYSXX)     
               to use the SYSNAME for the merge with TYPE113.           
               In this new data with SYSTEM NOT matching SMF70STN, it   
               was observed that SMF70STN matched SYSNAME, but now, the 
               original SYSTEM is unchanged:                            
                   IF SYSTEM=SMF70STN OR SYSNAME=SMF70STN;              
                   IF SYSTEM=SMF70STN THEN SYSTEM=SYSNAME;              
                   /* ELSE LEAVE THE SMF 70 ORIGINAL SYSTEM FOR MATCH */
              -Do not use Subtype 2 SMF 113 with accumulated data; they 
               may not always match up with 70PR because 113 data is    
               lost.  Always use Subtype 1 INTERVAL HIS data.  IBM has  
               stated they will NOT update Subtype 2 records.           
   Thanks to Virginie Peigney, CA-SILCA, FRANCE.                        
                                                                        
CHANGE 33.129  Support for TMS new TRTCH values for Device Type TS1140, 
VMACTMS5       EE4/EE4M/EE4X and EF4/EF4M/EF4X.                         
May 20, 2015                                                            
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
====== Changes thru 33.128 were in MXG 33.05 dated May 19, 2015=========
                                                                        
CHANGE 33.128  z13 with one or more LPARs enabled for SMT-mode will have
VMAC7072       zero observations in the TYPE70 dataset from all NON-SMT 
May 19, 2015   mode systems, UNLESS, ACCIDENTALLY, the SMT-mode systems 
               are all at the end of your input SMF file.  The SMTSEGNR 
               variable that identifies this is an SMT-mode record was  
               incorrectly retained.                                    
   Thanks to Scott Wiig, US Bank, USA.                                  
                                                                        
CHANGE 33.127  Dataset TYPE749 zEDC PCIE and Hardware Accelerator FIXED.
VMAC74         Change 33.124 replaced with logic to match all segments. 
May 18, 2015   This change is required for valid TYPE749 data.          
May 22, 2015   May 22: STD and AVG variables created for Queue/Execute  
               durations, which are now formatted TIME16.6.             
   Thanks to David Cogar, Wells Fargo, USA.                             
   Thanks to Carl D. Ellis, Wells Fargo, USA.                           
                                                                        
CHANGE 33.126  APPTUNE SMF 102 INPUT STATEMENT EXCEEDED if DATA SHARING 
VMACDB2H       (32) header is present.  The product section for APPTUNE 
May 19, 2015   records is not at the end of the SMF 102 but instead is  
               at the beginning of the record. Change 32.148 revised the
               header input logic, to support unexpected out-of-order   
               headers, but the LENLEFT calculations used record LENGTH.
               Now for APPTUNE 102s (QWHSIID GE 8000x), the ENDPROD is  
               used to determine the LENLEFT for all header segments.   
     Thanks to Jan Tielemans, KBC, BELGIUM.                             
                                                                        
CHANGE 33.125  Further SMT-related changes.                             
VMAC7072      -CPUWAITM now subtracts LPARBUSY from CPUWAITM for zIIPs. 
May 16, 2015   earlier code had the subtraction for CPs, with no impact.
              -SMF70CAN/SMF70CTN variables are again kept in TYPE70PR.  
   Thanks to Jim Horne, Lowe's, USA.                                    
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
====== Changes thru 33.124 were in MXG 33.05 dated May 12, 2015=========
                                                                        
CHANGE 33.124  MXG support for 74-9 zEDC was revised again, when it was 
VMAC74         discovered that only the first card was output, and that 
May 13, 2015   the number of PCIE pairings of the PO/DO segments is not 
May 18, 2015   the same as the number of Hardware Accelerator FO/10     
               segments. Original change text here removed, See 33.127. 
              -Variable R749LAID was removed; there is no adapter id.   
              -These new variables were added from the DO segments      
                R749DBYR R749DBYT R749DFMT R749DPKR R749DPKT            
                R749DWUP R749DWUM                                       
              -May 18: See Change 33.127, which is REQUIRED.            
   Thanks to David Cogar, Wells Fargo, USA.                             
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
====== Changes thru 33.123 were in MXG 33.05 dated May 12, 2015=========
                                                                        
CHANGE 33.123  Support for Tandem ZMS Style of records; the previous MXG
VMACTANZ       support was for what are now "Legacy Style" records.     
May 12, 2015                                                            
   Thanks to Mark Goforth, First National of Nebraska, USA.             
                                                                        
CHANGE 33.122  Reserved Change.                                         
                                                                        
CHANGE 33.121  z13 SMT-mode TYPE70/PR data IS WRONG in MXG 33.03-33.04. 
VMAC7072       In ONLY RMF 70 records written in SMT-mode, the datasets 
May 12, 2015   TYPE70, TYPE70PR, RMFINTRV, ASUM70PR, ASUM70LP, ASUMCEC, 
               and ASUM70PR can have incorrect values. MXG 33.03 support
               for z13 SMT-mode records continued to use LCPUADDR from  
               the PHYSICAL to merge with CPUID in the CPUD segment and 
               the results matched initial RMF reports, but now I find  
               that the LCPUADDR won't always match the CPUID value!    
               And, one mismatch destroys the merge, trashing both the  
               TYPE70 and TYPE70PR datasets.                            
               The code had to be redesigned to sort and merge on the   
               physical sequence to pair up the two segments to create  
               the per-LCPUADDR TYPE70PR dataset and populate TYPE70.   
                                                                        
               IBM RMF Support confirmed that "LCPUADDR/SMF70VPA in the 
               PHYSICAL segment is retrieved from the Diag 204 interface
               and is generated by the hardware/firmware when the core  
               is brought into the configuration.  It does not match the
               logical core id in SMF70VPA which is provided by z/OS in 
               the PR/SM logical processor data section(s) of the home  
               partition"                                               
                                                                        
               The example had an LCPUADDR=7 in PHYSICAL for a zIIP, but
               there was no corresponding CPUID=7 in the CPUD segment.  
               I was also confused when a box with 5 CP cores and 5 zIIP
               cores in PHYSICAL had SIX unique CORE_IDs, but that was  
               because the home partition had 4 logical CP cores and 2  
               logical zIIP cores, which results in the 8 CPU data      
               sections, with 6 unique CORE_IDs.                        
                                                                        
CHANGE 33.120  New member IHDR120 for the SMF TYPE=120 WebSphere record 
IHDR120        in %INCLUDEd after the header and Product segments have  
VMAC120        been INPUT, and the "instream" macro variable MAC120H is 
VMXGINIT       defined so that you can select/tailor after those header 
May  6, 2015   variables have been input.                               
                                                                        
CHANGE 33.119  The optional IMACICMX member for Omegamon with CMRDATA of
IMACICMX       length 384 was missing a final END; statement, causing a 
May  6, 2015   syntax error if UTILEXCL told you to tailor IMACICMX.    
                                                                        
CHANGE 33.118 -The RESULTS window now lists the report number and short 
SAGANAL        title for all reports produced by PROCs that support the 
May  7, 2015   CONTENTS= option to label the result. (Procs FREQ, MEANS,
               and CONTENTS do not support that feature.)               
              -Report 31 added with top ten MSU hours for CICS DFHSIP.  
              -Number of variables kept reduced to 68 from 1533; syntax 
               CPU: and CPI: for TYPE30 kept TYPE70PR CPU: variables.   
                                                                        
CHANGE 33.117 -MXG 33.04. SMFSRCH found no records if USERADDS= was not 
SMFSRCH        specified.  Logic added for USERADDS=NOUSERID was wrong. 
UTILBLDP       Logic corrected, but USERADDS=XXXX/nnnn (even if _IDXXXX 
May  6, 2015   is already defined in IMACKEEP) will circumvent.         
              -It was also possible to skip all user record selection   
               due to an ENDOFFILE test that is removed.                
              -The TYPE30_D dataset (each DD in SMF 30) is not populated
               by MXG default, and although the only text is the DDNAME,
               since SMFSRCH is to find and print all SMF records found,
               new TY30UD argument is defined in UTILBLDP (default is   
               blank), and TY30UD=YES default is set in SMFSRCH, so that
               dataset TYPE30_D will be populated if type 30 records are
               selected, or you can use TY30UD=NO in your SMFSRCH call  
               to prevent any observations to be created in TYPE30_D.   
              -ECHO=YES specified in SMFSRCH to always print the MXG    
               created by UTILBLDP on the log.                          
              -In testing, an exposure was observed: multiple uses of   
               the file INSTREAM caused text to be overridden, which did
               not cause an error, but some sites have made INSTREAM to 
               be a permanent dataset, and this exposure could lead to  
               errors for those sites.                                  
               The //INSTREAM DD was intended to be temporary and used  
               internally as the destination for writing SAS code that  
               is then executed with %INCLUDE INSTREAM.  These members  
               no longer use INSTREAM; instead, each writes/reads from  
                FILENAME TMXGxxxx CATALOG 'WORK.MXGTEMP.TMXGxxxx.LOG';  
               in the WORK file so no DD is required, and no conflict!  
               A few members (notably UTILBLDP) do externalize INSTREAM,
               and they were not changed.                               
                ANALCOMP VMXGPRAL VMXGPRNT QAWPS8   QA94648 SAGANAL     
                PRINTLOG ONLYJOBS ASUMMSUS ANALRRTM ANALPGM ANALCOMP    
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
CHANGE 33.116  Support for ZCOST AutoSoftCapping Version V3.0.00 adds   
EXZCO02S       subtypes and data.  These are the datasets MXG creates:  
EXZCO02W         DDDDDD    Dataset   Description                        
EXZCO04C          ZCO01     ZCOS01    ZCOST CPC                         
EXZCO04G          ZCO02     ZCOS02    ZCOST LPAR                        
EXZCO04L          ZCO02S    ZCOS02S   ZCOST SERVICE CLASS PERIOD        
EXZCO04P          ZCO02W    ZCOS02W   ZCOST WLM INPORTANCE              
EXZCO04R          ZCO03     ZCOS03    ZCOST SYSPLEX/CPC                 
VMACZCOS          ZCO04G    ZCOS04GP  ZCOST GENERAL PARMS               
VMXGINIT          ZCO04C    ZCOS04CP  ZCOST CPC PARMS                   
May  5, 2015      ZCO04L    ZCOS04LP  ZCOST LPAR PARMS                  
May 28, 2015      ZCO04P    ZCOS04PG  ZCOST GENERAL PERIOD PARMS        
                  ZCO04R    ZCOS04PL  ZCOST LPAR PERIOD PARMS           
               This support was completed in MXG 33.06.                 
                                                                        
CHANGE 33.115  Mainview for MQ BBMQBUFF dataset EFFICIENCY variables are
VMACBBMQ       now correctly input as RB4 instead of PIB. Variables are 
Apr 29, 2015   SBPIAWPE SPBRAWPE SBPSAWPE.                              
                                                                        
CHANGE 33.114  BMC IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN; 
VMACCIMS       it was incorrectly in the CIMSDBDS dataset KEEP=list.    
Apr 29, 2015   "zAAP" in Label changed to 'ZIP' (Feb 2006):             
                 CPUZIPTM='CPU TIME*ON ZIP*ENGINES'                     
                 TRXZAOCP='CPU TIME*ZIP ELIGIBLE*RAN ON CP'             
   Thanks to Betty Wong, Bank of America, USA.                          
                                                                        
CHANGE 33.113  Some T102S106 variables (DB2 zPARM flags and values) were
FORMATS        misaligned, not INPUT, or had wrong/no decoding format.  
VMAC102        Align: QWP2DMIN,QWP2DSEC                                 
Apr 30, 2015   Format: Use $MGD361U for QWP4SECA1_TYPE, QWP4SECA2_TYPE  
               Format: New $MGD106P for QWPBDL, QWPBSDL                 
               Input: QWP4S1IL for DB2 V10, was only V11 and wrong.     
   Thanks to Lai Fai, Bank of America, USA.                             
                                                                        
====== Changes thru 33.112 were in MXG 33.04 dated Apr 29, 2015=========
                                                                        
CHANGE 33.112 -Support for CICS/TS 5.3 OPEN BETA (INCOMPATIBLE) AND:    
UTILEXCL       NOTE THAT 5.3 now sets STGPROT=YES as the IBM DEFAULT, to
VMAC110        INTENTIONALLY cause an ABEND for storage overlays caused 
Apr 29, 2015   by dubious programming techniques where a task has       
May  1, 2015   modified storage owned by another task.  These ABENDs    
               will need application programmer design changes; the APP 
               should have been fixed long ago - IBM is looking forward!
              -New variables (INCOMPATIBLE) inserted in CICSTRAN dataset
                  NCGETCN ='NAMED*COUNTER*SERVER*REQUESTS'              
                  TSGETSCN='SHARED*TEMP*STORAGE*GETS'                   
                  TSPUTSCN='SHARED*TEMP*STORAGE*PUTS'                   
                  May 1: Original Note wrong here, NO ERROR in TSTOTCN. 
              -New variables inserted in CICSRDQU dataset (MNSEGCL=5):  
                 TSQGESTM='SHARED*TSQUEUE*GET*TIME'                     
                 TSQGESCN='SHARED*TSQUEUE*GET*COUNT'                    
                 TSQPUSTM='SHARED*TSQUEUE*PUT*TIME'                     
                 TSQPUSCN='SHARED*TSQUEUE*PUT*COUNT'                    
                 TSQGESBY='SHARED*TSQUEUE*GET*BYTES'                    
                 TSQPUSBY='SHARED*TSQUEUE*PUT*BYTES'                    
              -"WRITING OF PERFORMANCE DATA IS MORE EFFICIENT WHEN      
               FIELDS ARE NOT EXCLUDED." was noted in a comment.        
                                                                        
CHANGE 33.111 -The ANALID report that tabulates SMF record types is     
ANALID         enhanced to optionally invoke %UTILBLDP to create MXG    
SMFSRCH        code to build all possible MXG datasets from ALL records 
UTILBLDP       in the input SMF file, and to optionally run the program,
VMXGPRAL      -This change originally documented macro variables UTILBLD
VMXGINIT       VMXGPRA but they were removed in Change 33.117, unused.  
Apr 27, 2015  -VMXGPRAL revised to print the LIB.DSNAME + LABEL without 
May 27, 2015.  extra blanks and periods.                                
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
CHANGE 33.110 -Support for TS7700 HYDRA Version 3.2A (COMPATIBLE)       
EXBVR302       creates new BVIR302 dataset with the  Extended HSM Cache 
FORMATS        Partition Container Statistics from subtype 30 record.   
IMACBVIR      -Variables added to BVIR01 dataset:                       
VMACBVIR         THRUPUT AHEADCNT BEHNDCNT                              
VMXGINIT      -Changed records have BVIRVERS=6.                         
Apr 24, 2015                                                            
   Thanks to Tim Campbell, TELUS, CANADA.                               
                                                                        
CHANGE 33.109 -Support for TYPE 23 zEDC variables SMF23BBC/SMF23BAC has 
VMAC23         been corrected and validated.  Those two variables plus  
Apr 23, 2015   SMF23PFT SMF23PFM SMF23PFH SMF23CWN SMF23NCN are now     
               correctly aligned and are now output in dataset TYPE23LS 
               and removed from dataset TYPE23.                         
              -Two new fields were documented in the z/OS 2.1 SMF Manual
               but IBM has confirmed they only exist in z/OS 2.2:       
                 SMF23BBC='ZEDC*UNCOMPRESSEDSED*BYTES*TOTAL'            
                 SMF23BAC='ZEDC*COMPRESSED*BYTES*TOTAL'                 
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
CHANGE 33.108  Support for APARs OA45944 and OA45897 which adds new data
VMAC42         for contention counts for record locks, component1 and   
Apr 23, 2015   component2 locks:                                        
              -New variables in dataset TYPE42S1:                       
                 SMF42FUA ='ACCUMULATION*WAITERS FOR*RECORD LOCK'       
                 SMF42FUB ='RECORD LOCKS*HASHED TO*SAME ENTRY(/         
                 SMF42FUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42FUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42FUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42FUG ='LOCKS*HASHED TO*SAME*ENTRY'                 
              -New variables in dataset TYPE42S2:                       
                 SMF42FVA ='ACCUMLATION*WAITERS*FOR RECORD*LOCK'        
                 SMF42FVB ='RECORD LOCKS*HASHED TO*SAME ENTRY'          
                 SMF42FVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42FVE ='ACCUMULATION*WAITERS*FOR UPGRADELOCK'       
                 SMF42FVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42FVG ='LOCKS*HASHED TO*SAME*ENTRY'                 
              -New variables in dataset TYPE42S3:                       
                 SMFA2FUA ='ACCUMULTION*WAITERS*FOR RECORD*LOCK'        
                 SMFA2FUB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMFA2FOD ='ACCUMULTION*WAITERS*FOR DIWA*LOCK'          
                 SMFA2FOE ='ACCUMULTION*WAITERS*FOR UPGRADE*LOCK'       
                 SMFA2FOF ='ACCUMULTION*WAITERS*FOR COMP2*LOCK'         
                 SMFA2FOG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42S4:                       
                 SMFA2FVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMFA2FVB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMFA2FVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMFA2FVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMFA2FVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMFA2FVG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42D1:                       
                 SMF42GUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42GUB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42GUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42GUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42GUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42GUG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42D2:                       
                 SMF42GVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42GVB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42GVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42GVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42GVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42GVG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42D3:                       
                 SMF42GUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42GUB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42GUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42GUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42GUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42GUG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42D4:                       
                 SMF42GVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42GVB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42GVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'         
                 SMF42GVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42GVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42GVG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42L1:                       
                 SMF42HUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42HUB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42HUD ='ACCUMULATION*WAITERS*FOR DIWA2*LOCK'        
                 SMF42HUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42HUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42HUG ='LOCKS*HASHED*TO SAME*ENTRY'                 
              -New variables in dataset TYPE42L2:                       
                 SMF42HVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'       
                 SMF42HVB ='LOCKS*HASHED*TO SAME*ENTRY'                 
                 SMF42HVC ='ACCUMULATION*WAITERS*FOR DIWA2*LOCK'        
                 SMF42HVD ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'      
                 SMF42HVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'        
                 SMF42HVG ='LOCKS*HASHED*TO SAME*ENTRY'                 
                                                                        
CHANGE 33.107 -DB2PM-like reports PMACC02/4 class 3 delay section was   
ANALDB2R       missing TCP/IP LOB and the global contention corrected   
Apr 26, 2015   from only parent locks to include all contention delays. 
              -In PMAUD02 there were uninitialized variables corrected. 
              -The z/OS external sort can not be used if the length of  
               an observation is greater than 32760 bytes, and many of  
               the DB2 102 records contain 32K SQL Text variables.      
               For the AUDIT reports, the SQL text is reduced to 80     
               bytes, since that is all IBM's DB2PM reports, and the    
               full text is still in the T102Snnn dataset.              
              -If you asked for AUTHCHG in the AUDIT= parameter and     
               there were any IFCID 83 records the selection criteria   
               were not applied and that caused missing timestamps in   
               the report headers.                                      
              -If there were 0 OBS in the IFCID 142 dataset then a      
               a work file was not cleaned up.                          
    Thanks to Neil Ervin, Wells Fargo, USA                              
                                                                        
Change 33.106  New variable EXCMTYPE in CICSEXCE (Exception) dataset    
FORMATS        is created to describe the exception event:              
VMAC110           1='DATABASE REQUEST POLICY RULE'                      
Apr 22, 2015      2='FILE REQUEST'                                      
                  3='PROGRAM REQUEST'                                   
                  4='START REQUEST'                                     
                  5='STORAGE REQUEST'                                   
                  6='SYNCPOINT REQUEST'                                 
                  7='TD QUEUE REQUEST'                                  
                  8='TIME REQUEST'                                      
                  9='TS QUEUE REQUEST'                                  
                  10='WAIT FOR CF LOCKING REQUEST'                      
                  11='WAIT FOR CF NON-LOCKING REQUEST'                  
                  12='WAIT FOR UDSA'                                    
                  13='WAIT FOR EUDSA'                                   
                  14='WAIT FOR CDSA'                                    
                  15='WAIT FOR ECDSA'                                   
                  16='WAIT FOR SDSA'                                    
                  17='WAIT FOR ESDSA'                                   
                  18='WAIT FOR RDSA'                                    
                  19='WAIT FOR ERDSA'                                   
                  20='WAIT FOR GCDSA'                                   
                  21='WAIT FOR GUDSA'                                   
                  22='WAIT FOR GSDSA'                                   
                  23='WAIT FOR TEMPORARY STORAGE'                       
                  24='WAIT FOR STRING FOR FILE'                         
                  25='WAIT FOR STRING FOR LSRPOOL'                      
                  26='WAIT FOR STRING FOR DFHTEMP'                      
                  27='WAIT FOR BUFFER FOR LSRPOOL'                      
                  28='WAIT FOR BUFFER*FOR DFHTEMP'                      
   Thanks to Bahman Nejad, Union Bank, USA.                             
   Thanks to Perry Lim, Union Bank, USA.                                
                                                                        
Change 33.105  Using PROC CPORT to copy z/OS data libraries to ASCII can
IMACFMTS       corrupt values in character variables with $HEX format if
UTILCVRT       those variables did not have the TRANSCODE=NO attribute  
Apr 21, 2015   set, or they were built with an ancient SAS version prior
               to that attribute.  If you have downloaded PDBs and see  
               $HEX variables are wrong (check CPUTYPE in TYPE70), the  
               UTILCVRT program can be used to convert those $HEX vars  
               back to their correct values. Maybe. The default mapping 
               table is the $MGAS2EB format in FORMATS, using a table   
               created in 2009 for PROC CPORT translation, replacing an 
               earlier table created from IND$FILE.  However, now using 
               the CPORT table under both Windows and Linux does NOT map
               characters correctly; the alternative $MGAS2EB table from
               IND$FILE must be used. That alternative format is defined
               in Example 2 in a comment block in the IMACFMTS member.  
               Copy IMACFMTS to your USERID.SOURCLIB, remove the comment
               block in Example 2, and run the FORMATS step of JCLINSTL 
               (%INCLUDE SOURCLIB(FORMATS); with DISP=OLD on //LIBRARY) 
               and the alternative table values will be used.           
    Thanks to Warren Cravey, Fidelity, USA.                             
    Thanks to Rachel Holt, Fidelity, USA.                               
                                                                        
Change 33.104  NMON CPU records can now contain three digits, CPU001, so
VMACNMON       the logic to create CPUNR now decodes two or three digits
Apr 21, 2015   for CPUnnn, PCPUnnn and SCPUnnn.                         
   Thanks to Raissa Moussu, METROLOGFIE AIX EN PROVENCE, FRANCE.        
                                                                        
Change 33.103  VMXGPRAL (PRINT/MEAN/FREQ ALL datasets &ALL variables in 
VMXGPRAL       a "PDB" data library, with both Label and Variable Name) 
Apr 15, 2015   enhanced for FREQ with TABLE= option to choose what      
               variables are tabulated.  TABLES=_CHAR_, will only show  
               the character variables.  Without the TABLES= argument,  
               all variables will be tabulated.                         
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE, test for 
VMACSYNC       SYNCLVL for ancient Release 3.7 conflicted) causing many 
Apr 15, 2015   variables to be missing values with no error message,    
               notably, CPUZIPTM is a missing value without this change.
   Thanks to Roger Foreman, Transunion, USA.                            
                                                                        
Change 33.102  DB2 V10 INVALID DATA FOR QLACCPUR and QLACDBAT when field
VMACDB2        QLACLOCN was relocated because it's longer than 8 bytes, 
Apr 14, 2015   but the length of the relocated field in XLENLOCN is NOT 
               in LENLOCN causing misalignment when XLENLOCN GT 20.     
   Thanks to Betty Wong, Bank of America, USA.                          
                                                                        
Change 33.101  Support for iSeries 7.2 (COMPATIBLE with new LRECLS).    
VMACQACS       Comments in VMACQACL list LRECLs and 7.2 records tested. 
Apr 13, 2015  -New variables in QAPMDISK:                               
                 DSLVLMP ='LEVEL OF*MIRRORED*PROTECTION'                
                 DSLSCNDS='LOG*SENSE*COMMANDS*ISSUED'                   
                 DSLSRT  ='LOG*SENSE*RESPONSE*TIME'                     
              -New variables in QAPMJOBM (QAPMJOBMI):                   
                 JBTNAME     ='THREAD*NAME'                             
                 JBSLTCNT    ='SHORT*LIFESPAN*ENTRY*COUNT'              
                 JBSACPU     ='ACCUMULATED*JOB*SCALED*CPU TIME'         
                 JBINDCPU    ='THREAD*UNSCALED*CPU TIME*USED'           
                 JBSINDCPU   ='THREAD*SCALED*CPU TIME*USED'             
                 JBCPUWC     ='PROCESSOR*ELAPSED*TIME'                  
                 JBVPDLY     ='VIRTUAL*PROCESSOR*DELAY*TIME'            
                 JBSEIZECNT  ='SIEZE*COUNT'                             
                 JBPSLCKCNT  ='PROCESS*SCOPED*LOCK*COUNT'               
                 JBTSLCKCNT  ='THREAD*SCOPED*LOCK*COUNT'                
                 JBPSRCDLCK  ='PROCESS*SCOPED*DATABASE*LOCK*COUNT'      
                 JBTSRCDLCK  ='THREAD*SCOPED*DATABASE*LOCK*COUNT'       
                 JBNFOGDT    ='OFF-GROUP*DISPATCH*TIME'                 
                 JBNFOGMA    ='OFF-GROUP*PAGE*FRAMES'                   
                 JBPGEZSTL   ='PAGES*MARKED*EASY TO*STEAL'              
                 JBSQLCLK    ='SQL*CLOCK*TIME'                          
                 JBSQLCPU    ='THREAD*UNSCALED*SQL*TIME'                
                 JBSQSCPU    ='THREAD*SCALED*SQL*CPU TIME'              
                 JBSQLDBR    ='SQL*SYNCHRONOUS*DATABASE*READS'          
                 JBSQLNDBR   ='SQL*SYNCHRONOUS*NONDATABASE*READS'       
                 JBSQLDBW    ='SQL*SYNCHRONOUS*DATABASE*READS'          
                 JBSQLNDBW   ='SQL*SYNCHRONOUS*NONDATABASE*READS'       
                 JBSQLADBR   ='SQL*ASYNCHRONOUS*DATABASE*READS'         
                 JBSQLANDBR  ='SQL*ASYNCHRONOUS*NONDATABASE*READS'      
                 JBSQLADBW   ='SQL*ASYNCHRONOUS*DATABASE*WRITES'        
                 JBSQLANDBW  ='SQL*ASYNCHRONOUS*NONDATABASE*WRITES'     
                 JBAGCRT     ='ACTIVATION*GROUPS*CREATED'               
                 JBPGMSACT   ='PROGRAM*ACTIVATIONS*CREATED'             
                 JBCURTMP    ='CURRENT*TEMPORARY*STORAGE'               
                 JBPEAKTMP   ='PEAK*TEMPORARY*STORAGE'                  
                 JBMAXTMP    ='MAXIMUM*TEMPORARY*STORAGE'               
                 JBTMPPGA    ='4K UNITS*ALLOC*TEMPORARY*STORAGE'        
                 JBTMPPGD    ='4K UNITS*DEALLOC*TEMPORARY*STORAGE'      
                 JBHSQLSTMT  ='HIGH*LEVEL*SQL*STATEMENTS'               
                 JBTICC      ='THREAD*INSTRUCTION*COUNT*CHARGED'        
                 JBTICU      ='THREAD*INSTRUCTION*COUNT*USED'           
                 JBTTMBU     ='THREAD*VIRTUAL*TIME'                     
                 JBPICC      ='PROCESS*HDW INSTR*COUNT*CHARGED'         
                 JBPRRSCPTY  ='PROCESSOR*RESOURCE*PRIORITY'             
              -New variables in QAPMJOBO (QAPMJOBOS):                   
                 JBFSOPN  'FILE*SYSTEM*OPENS''                          
                 JBFSDC   'FILE*SYSTEM*DIRECTORY*CREATES'               
                 JBFSNDC  'FILE*SYSTEM*NON-DIRECTORY*CREATES*           
                 JBFSDD   'FILE*SYSTEM*DIRECTORY*DELETES'               
                 JBFSNDD  'FILE*SYSTEM*NON-DIRECTORY*DELETES*           
                 JBSPLFC  'SPOOLED*FILES*CREATED*BY THIS JOB*           
                 JBSBMJOBS'JOBS*SUBMITTED*OR SPAWNED.'                  
                 JBSQLSTMT'SQL*STATEMENTS'                              
                 JBLWTSQL 'SQL*RELATED*DATABASE*WRITES*(LOGIC           
                 JBLRDSQL 'SQL*RELATED*DATABASE*READS*(LOGICA           
                 JBDBUSQL 'SQL*RELATED*DATABASE*MISCELLANEOUS           
                 JBPASCMP 'SQL*PAS*COMPRESSIONS*ALL THREADS'            
                 JBPKGCMP 'SQLPKG*COMPRESSIONS'                         
                 JBCTHD   'CONNECTED*THREAD*IDENTIFIER'                 
                 JBCJNAM  'CONNECTED*JOB*NAME'                          
                 JBCJUSR  'CONNECTED*JOB*USER'                          
                 JBCJNBR  'CONNECTED*JOB*NUMBER'                        
              -New variables in QAPMPOLB (QAPMPOOLB):                   
                 POPGS4    ='POOL*4K*PAGES'                             
                 POPGS64   ='POOL*64K*PAGES'                            
                 PODBF4    ='POOL*DATABASE*4K*PAGE*FAULTS'              
                 PODBF64   ='POOL*DATABASE*64K*PAGE*FAULTS'             
                 PONDBF4   ='POOL*NONDATABASE*4K*PAGE*FAULTS'           
                 PONDBF64  ='POOL*NONDATABASE*64K*PAGE*FAULTS'          
                 PODBPG4   ='POOL*DATABASE*4K*PAGES*READ'               
                 PODBPG64  ='POOL*DATABASE*64K*PAGES*READ'              
                 PONDPG4   ='POOL*NONDATABASE*4K*PAGES*READ'            
                 PONDPG64  ='POOL*NONDATABASE*64K*PAGES*READ'           
                 POUNAL4   ='UNALLOCATED*4K*PAGES'                      
                 POUNAL64  ='UNALLOCATED*64K*PAGES'                     
                 POAGED4   ='POOL*4K*PAGES*AGED/                        
                 POAGED64  ='POOL*64K*PAGES*AGED'                       
                 POSTLN4   ='POOL*4K*PAGES*STOLEN'                      
                 POSTLN64  ='POOL*64K*PAGES*STOLEN'                     
                 POUNUSE4  ='POOL*4K*PAGES*UNUSED'                      
                 POUNUSE64 ='POOL*64K*PAGES*UNUSED'                     
                 POSYNC4   ='POOL*4K*PAGE*SYNC I/O'                     
                 POSYNC64  ='POOL*64K*PAGE*SYNC I/O'                    
                 POASYNC4  ='POOL*4K*PAGE*ASYNC I/O'                    
                 POASYNC64 ='POOL*64K*PAGE*ASYNC I/O'                   
                 POPGOUT4  ='POOL*4K*PAGE*OUTS'                         
                 POPGOUT64 ='POOL*64K*PAGE*OUTS'                        
                 POPGABLE4 ='POOL*4K*PAGES*PAGEABLE'                    
                 POPGABLE64='POOL*64K*PAGES*PAGEABLE'                   
                 POATMPT4  ='POOL*4K*ALLOCATION*ATTEMPTS                
                 POATMPT64 ='POOL*64K*ALLOCATION*ATTEMPTS               
                 POAPS4    ='POOL*4K*AFFINITY*SUCCESSES                 
                 POAPS64   ='POOL*64K*AFFINITY*SUCCESSES                
                 POAPMIG4  ='POOL*4K*AFFINITY*MISSES                    
                 POAPMIG64 ='POOL*64K*AFFINITY*MISSES                   
                 POAPMOG4  ='POOL*4K*AFFINITY*MISSES*OFFGROUP'          
                 POAPMOG64 ='POOL*64K*AFFINITY*MISSES*OFFGROUP'         
                 POCRTPG64 ='POOL*4K*PAGES*CREATED'                     
                 POBRKPG64 ='POOL*64K*PAGES*BROKEN*UP'                  
                 POPOSIZB  ='POOL*SIZE*KB'                              
                 POUNALB   ='UNALLOCATED*POOL*SPACE*KB'                 
              -New variables in QAPMSYST (QAPMSYSTEM):                  
                 SYVPID    ='VIRTUAL*SHARED*POOL ID'                    
                 SYVPCAP   ='VIRTUAL*SHARED POOL*ENTITLED*CAPACITY'     
                 SYPPLU    ='PHYSICAL*SHARED POOL*CPU TIME*USED'        
                 SYPPLA    ='PHYSICAL*SHARED POOL*CPU TIME*AVAILABLE'   
                 SYPTHV    ='HYPERVISOR*CPU*TIME'                       
                 SYPTINT   ='INTERRUPT*CPU*TIME'                        
                 SYPTWS    ='WAITTASK*TIME'                             
                 SYPTDN    ='DONATED*CPU*TIME'                          
                 SYSSPTU   ='SCALED*CPU*TIME*USED'                      
                 SYUCAPF   ='PARTITION*UNCAPPED*FLAG'                   
                 SYDONF    ='PARTITION*DONATION*FLAG'                   
                 SYPTWAIT  ='VIRTUAL*PROCESSOR*THREAD WAIT*EVENT TIME'  
                 SYPTREADY ='VIRTUAL*PROCESSOR*THREAD WAIT*READY TIME'  
                 SYPTLATEN ='VIRTUAL*PROCESSOR*THREAD DISPATCH*LATENCY' 
                 SYPTACT   ='VIRTUAL*PROCESSOR*THREAD*ACTIVE TIME'      
                 SYPTIDLE  ='VIRTUAL*PROCESSOR*THREAD*IDLE TIME'        
                 SYPTINTR  ='VIRTUAL*PROCESSOR*THREAD*INTERRUPT TIME'   
                 SYFRMCPU  ='PROCESSOR*FIRMWARE*TIME USED'              
                 SYFRMSCPU ='PROCESSOR*SCALED*FIRMWARE*TIME USED'       
                 SYPFOLDSW ='PROCESSOR*FOLDING*SWITCH*STATE'            
                 SYPFOLDST ='PROCESSOR*FOLDING*STATE'                   
                 SYEMMAJCDE='ENERGY*MANAGEMENT*MAJOR CODE'              
                 SYEMMINCDE='ENERGY*MANAGEMENT*MINOR CODE'              
                 SYEMATTR  ='ENERGY*MANAGEMENT*ATTRIBUTES'              
                 SYEMPWRLMT='ENERGY*MANAGEMENT*POWER DRAW*LIMIT WATTS'  
                 SYSQLCPU  ='UNSCALED*SQL*CPU TIME*USED'                
                 SYSQLSCPU ='SCALED*SQL*CPU TIME*USED'                  
                 SYOSTMP   ='CURRENT*TEMPORARY*STORAGE*ALLOCATED*NONDB' 
                 SYDBTMP   ='CURRENT*TEMPORARY*STORAGE*ALLOCATED*DB'    
                 SYAJOBTMP ='CURRENT*TEMPORARY*STORAGE*CHARGED*ACTIVE'  
                 SYEJOBTMP ='CURRENT*TEMPORARY*STORAGE*CHARGED*EMDED'   
                 SYUSERTMP ='CURRENT*USER*TEMPORARY*STORAGE'            
                 SYPSLPU   ='PHYSICAL*SHARED POOL*SCALED*CPU TIME*USED' 
                 SYTRUNIC  ='HARDWARE*INSTRUCTIONS'                     
                 SYTRUNVTB ='NON-IDLE*PROCESSOR*VIRTUAL*TIME'           
                 SYTITUIC  ='INTERRUPT*INSTRUCTION*COUNT'               
                 SYTFRMIC  ='FIRMWARE*INSTRUCTION*COUNT'                
   Thanks to Raymond J. Smith, United Health Group, USA.                
                                                                        
Change 33.100 -Protect RMF III for invalid ASI table index in UWD table 
ASMRMFV        entry that caused ABEND S0C4 in FINDAS when the invalid  
Apr 12, 2015   index value was really bad, i.e., it exceeded the number 
               of entries in the ASI table and an attempt was made to   
               access data from well beyond the ASI table's end.        
    Thanks to Randy Schlueter, First Data Corporation, USA              
                                                                        
Change 33.099  MXG 32.13-MXG 33.03.  TMON/CICS Version 3.4 AND EARLIER. 
VMACTMO2      -Dataset MONITASK CPU time (TASCPUTM) and ALL DURATION    
Apr 11, 2015   variables are WRONG, TOO SMALL, by a factor of 4096.     
               In TMON Version 4, all durations were changed from the   
               original microseconds to TODSTAMP, which requires the    
               division by 4096, but the MXG code inserted for MONITASK 
               was mis-located and applied to all TMON versions.        
              -Less critical, and wrong ONLY with Version 4 records: ALL
               duration variables in all OTHER MONIxxxx datasets were   
               NOT divided by 4096, so they are TOO LARGE by 4096.      
   Thanks to Andrew Petersen, CSC, AUSTRALIA.                           
                                                                        
Change 33.098  NMON (AIX/LINUX) CPU variables in PDB.NMONCPUD and in the
VMACNMON       PDB.NMONINTV were revised and missing values corrected.  
Apr 10, 2015   The individual CPUNR data in PDB.NMONCPUD from the three 
               CPUnn, PCPUnn, and SCPUnn records are the variables      
               prefixed with CPUNxxxx,PCPUNxxxx,SCPUNxxxx with suffixes 
               BUSY,IDLE,SYS,USER,WAIT.                                 
               The interval CPU_ALL, PCPU_ALL, and SCPU_ALL record's    
               in PDB.NMONINTV are prefixed PCPUxxxx,APCPUxxxx,ASCPUxxxx
               with the same suffixes (plus variable APCPUENTCAP).      
               The BUSY variables are calculated for all observations.  
   Thanks to Florent Boulesteix, INOVANS partenaire CAAGIS, FRANCE.     
                                                                        
Change 33.097 -SMFSRCH utility (select SMF records containing text and  
SMFSRCH        create all MXG datasets from those selected records) adds
Apr  9, 2015   new PRINT= option with YES/NO/nnn to print all, none, or 
               the first nnn observations of each dataset.  The PRINTIT=
               argument's YES or NO are still supported, but the PRINT= 
               argument is the more common spelling in MXG macros.      
              -Set USERADDS=NOUSERID, and all matching SMF types are    
               reported, but the 128-255 USER SMF records are skipped,  
               This avoids an abend if not all of your USER records are 
               mapped in IMACKEEP, MACKEEP, OR USERADDS= argument.      
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 33.096 -z13 with SMT PROCVIEW=CORE, dataset TYPE70PR, variable   
VMAC7072       SMT_NUM, the count of threads for each core, wasn't kept.
Apr 12, 2015  -TYPE70PR variable SMF70MTTT, MULTI-THREADING*IDLE*TIME,  
               which is actually SMF70MTIT mis-spelled, is accumulated, 
               requiring an additional sort and DIF() to deaccumulate.  
               As is ALWAYS the case when IBM writes ACCUMULATED values,
               the value for the first instance of each LCPUADDR in each
               LPAR will be a missing value.  Some cases when the next  
               accumulated value was slightly smaller than the prior are
               also set to missing value, but if they occur in your data
               a PMR should be raised with IBM support.  The label for  
               SMF70MTTT now contains 'SMF70MTIT' to compensate.        
   Thanks to Don Deese, Computer Management Sciences, USA.              
                                                                        
Change 33.095  Optional SUMMARY=SMFBYTES/SMFRECNT argument will produce 
ANALID         a report sorted by DESCENDING &SUMMARY to print largest  
Apr  3, 2015   first.                                                   
                                                                        
Change 33.094  Format MGSMFID did not describe SMF 115 records subtypes 
FORMATS        5, 6, and 7.                                             
Apr  3, 2015                                                            
   Thanks to Paul Bennett, Euroclear, BELGIUM.                          
   Thanks to Edmond Dierickx, Euroclear, BELGIUM.                       
                                                                        
Change 33.093  MXG 33.03. Disabled debug statement  *PUTLOG +2 'DEBUG..;
VMAC7072       was followed by an unmatched */, but there was no syntax 
Apr  3, 2015    error, because SAS recognized the asterisk as the start 
               of another comment, that ended with the semicolon of the 
               next statement, HOLICFTM=ICFACTTM;, so that statement was
               absorbed and not executed.  Fortunately, only ICF time in
               some unusual circumstances, when the time had to be held,
               might have been impacted.                                
   Thanks to MP Welch, Bank of America, USA.                            
                                                                        
Change 33.092 -Some BBBPnnn variables were mis-assigned values: BBBP040 
VMACNMON       and BBBP049 because the BBBP40 'MAXIMUM CAPACITY' text   
Apr  8, 2015   overlapped with BBBP49 'MAXIMUM CAPACITY OF POOL'.  All  
               text tests are expanded to prevent the overlap.          
              -The MERGE of CPUD/CPUNP/CPUNS datasets had DUPLICATE     
               MERGE VARIABLES when the number of CPUs (observations)   
               in those datasets were not equal.  Since CPUD has the    
               the primary CPU metrics, the MERGE was split into two    
               steps, first the three CPUD/CPUNP/CPUNS with CPUNR added 
               to the BY list, and now OUTPUT only if CPUD is present,  
               whether or not the other two datasets are present for    
               this CPUNR.  Then the second step MERGES the output with 
               SNAPMAP to create PDB.NMONCPUD with the CPU metrics for  
               each CPUNR.                                              
              -Diagnostic tests for DISKBUSY counter errors corrected.  
   Thanks to Raissa Moussu, METROLOGFIE AIX EN PROVENCE, FRANCE.        
                                                                        
Change 33.091  Support for CICS User fields USERAGT, ORIGUOW, and       
IMACAAAA       ORIGTGID.                                                
IMACICVM                                                                
IMACICVN                                                                
IMACICVO                                                                
UTILEXCL                                                                
VMAC110                                                                 
Apr  2, 2015                                                            
   Thanks to Rob Hollingum, HSBC, ENGLAND.                              
                                                                        
Change 33.090  Mainview for MQ PTFs corrected the Offset ENTO value from
VMACBBMQ       the always incorrect prior value of 28 for BBMQQUES 'E6' 
Apr  2, 2015   to the correct value of 32, but this is an INCOMPATIBLE  
               change which mis-aligned MXG input, because MXG has known
               to skip over those four bytes.  Logic revised to support 
               either value since the records are otherwise unchanged.  
               BPL2458(MVMQ51) and BPL2459(MVMQ52) were the PTFs.       
   Thanks to Jim Swinarski, Credit-Suisse, USA.                         
                                                                        
Change 33.089  Not Used.                                                
                                                                        
Change 33.088  Some duration variables in RMF III ZRBxxxx datasets still
VMACRMFV       had TIME12.2 format but have millisecond resolution, so  
Apr  1, 2015   they are all changed to TIME13.3 to show all decimals.   
                                                                        
Change 33.087 -RMF Type 74 Subtype 9 zEDC Hardware Accelerator support. 
VMAC74         The TYPE749 dataset was created with RMF 2.1 support back
Apr  1, 2015   in Change 31.153, but that INPUT was inhibited, awaiting 
May  4, 2015   test records, and this update has been validated with    
May  6, 2015   zEDC PCIE type 74 subtype 9 records.                     
              -May  4: Variables R7491IIS and R74i1IOS corrected to add 
               II2 and IO2 instead of II1 and IO1.                      
              -May  6: Variables R7491BPS and R7491BPC were incorrectly 
               multiplied in conversion to bytes - way too large.       
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
Change 33.086  Support for Velocity Software zVPS a/k/a XAM Version 5.4.
VMACXAM        Status April 9:                                          
Apr  7, 2015  -All updates have been made with these exceptions:        
EXXAMIFL        Segments not documented, have data records, skipped:    
EXXAMIFT         TCP: LINMEM LINCPU LINITF                              
VMXGINIT         DEV: IODSZI                                            
Apr  9, 2015    New Segments, no data, not skipped, will print msg.     
Apr 23, 2015       TCP:ORASYS ORAPGA ORASGA ORAWTS                      
                   VSECFG VSESYS VSECPU JVMSYS                          
              -INFILE XAMCPU changes:                                   
                 NEW dataset XAMIFLBY for individual IFL engine stats.  
                 NEW dataset XAMIFLTO for TOTAL IFL engine stats.       
              -INFILE XAMUSR changes:                                   
              -New variables in USRCON segment added to dataset XAMUSR: 
                 CALCFGEM ='CALICFCT'                                   
                 CALCPCT  ='CALCPCT'                                    
                 CALICFCT ='CALICFCT'                                   
                 CALIFLCT ='CALIFLCT'                                   
                 CALZAPCT ='CALAZPCT'                                   
                 CALZIPCT ='CALZIPCT'                                   
                 LIMPOOL  ='POOL*NAME*USER IS*ASSIGNED'                 
                 RDMMMASK ='LGR*DMN*BITMASK*SSI SLOTS'                  
                 RDMNAME  ='LGR*DOMAIN*FROM*USEACT'                     
                 RELO1    ='CAUSED*BY*LGR?'                             
                 RLOMVOPT ='LGR*FLAG*BYTE'                              
                 SSHABSSH ='ABSOLUTE*SHARE'                             
                 SSHFLG1  ='SSHFLG1*SHARE*FLAG'                         
                 SSHLIMH  ='LIMIT IS*HARD?'                             
                 SSHMXLSH ='MAXIMUM*SHARE'                              
                 SSHMXSHA ='MAX*SHARE*IS IN*ABS?'                       
                 SSHNMSHA ='NORMAL*SHARE*IS IN*ABS?'                    
                 SSHRELSH ='RELATIVE*SHARE'                             
                 VMDIDENT ='IDENTITY*VMDBK?'                            
                 VMDREOFL ='REORDER ON?'                                
                 VMDREOFL1='VMDREOFL1*FLAG'                             
                 VMDRLLST ='DATETIME*WHEN*LGR*ADDED'                    
                 VMDRLOLG ='ORIGINAL*MEMBER*LOGGED ON'                  
                 VMDRLSRC ='NAME FROM*WHERE LAST*LGR'                   
              -New variables in USRACT segment added to dataset XAMUSR: 
                 AGLA2G      ='PRIVATE AGELIST >2GB'                    
                 AGLB2G      ='PRIVATE AGELIST <2GB'                    
                 CALCPFNR    ='PGS IBR WRITTEN, REREF'                  
                 CALCPFRY    ='PGS IBR BACKED'                          
                 CALCPINT    ='PRIVATE PAGES INSTANTD'                  
                 CALCPINV    ='PGS MADE IBR'                            
                 CALCPPFA    ='PGS RE-REFD AGELIST'                     
                 CALCPPFI    ='PGS RE-REFD IBR'                         
                 CALCPREL    ='PGS RELEASE DAG10/214'                   
                 CALCPXRL    ='PGS XSTORE RELEASED'                     
                 CALCTXBK    ='EXSTOR PG BLOCKS'                        
                 CALDSPCT    ='COUNT TIMES DISPATCHED'                  
                 CALDWTCT    ='COUNT READY TO BE DISPATC'               
                 IBRA2G      ='PRIVATE IBR PGS < 2GB'                   
                 IBRB2G      ='PRIVATE IBR PGS <2GB'                    
                 INS         ='PRIVATE PAGES'                           
                 RABISA2G    ='NON REF'D PGS > 2GB'                     
                 RABISB2G    ='NON REF'D PGS < 2GB'                     
                 VMACPSN     ='VMACPSN'                                 
                 VMAIIA      ='IPTE ILOCK ACQ'S METHOD 2'               
                 VMAIIADD    ='IPTE ILOCK ADDED HOST SHR'               
                 VMAIIHLD    ='TIME HOST SHARES HEALD'                  
                 VMAIINHLD   ='INTERVALS HOST SHARES HLD'               
                 VMAIIWTM    ='TIME WAITING IPTE ILOCK'                 
                 VMAIPTEI    ='IPTE ILOCK ACQUISITIONS'                 
                 VMATTIME_PRO='VMATTIME_PRO'                            
                 VMATTMP_PRO ='VMATTMP_PRO'                             
                 VMATTMS_PRO ='VMATTMS_PRO'                             
                 VMAVTIME_PRO='VMAVTIME_PRO'                            
                 VMAVTMP_PRO ='VMAVTMP_PRO'                             
                 VMAVTMS_PRO ='VMAVTMS_PRO'                             
                 VMDCACHN    ='MDC INSERTS'                             
                 VMDCPUCH    ='SIE INTERUPTS'                           
                 VMDCRPGM    ='REFERENCED PGMBK'                        
                 VMDCTSTA    ='SIGP STARTS'                             
                 VMDCTSTO    ='SIGP STOPS'                              
                 VMDCUPGM    ='UNREFERENCED PGM'                        
                 VMDDSRSV    ='TIMES LIMIT SET RESRVD'                  
                 VMDDTPLX    ='DETACH COMMANDS SSI'                     
                 VMDDTTOD    ='SSI DETACH CMD VTIME'                    
                 VMDDTTOT    ='DETACH COMMANDS'                         
                 VMDLKPLX    ='LINK COMMAND, SSI'                       
                 VMDLKTOD    ='SSI LINK CMD VTIME'                      
                 VMDLKTOT    ='LINK COMMANDS,'                          
                 VMDPBKCT    ='PGMBK COUNT'                             
                 VMDSSIZE    ='VMDSSIZE'                                
                 VMDSTFHW    ='HI WATER STEAL WEIGHT'                   
                 VMDSTLFC    ='STEAL WEIGHT FACTOR'                     
                 VMDTMORD    ='PGMBK REORDERED'                         
                 VMDTTIME_MT1='VMDTTIME_MT1'                            
                 VMDTTMP     ='TOT TCPU PRIMARY CPU'                    
                 VMDTTMP_MT1 ='VMDTTMP_MT1'                             
                 VMDTTMS     ='TOT TCPU SECONDARY CPU'                  
                 VMDTTMS_MT1 ='VMDTTMS_MT1'                             
                 VMDUFACTC   ='FRAMES OF UFO ACTIVE'                    
                 VMDUFIBRC   ='FRAMES OF IBR'                           
                 VMDUFOLKCT  ='UFO SPIN LOCK COUNT'                     
                 VMDUFOLKTM  ='UFO SPIN LOCK TIME'                      
                 VMDVTIME_MT1='VMDVTIME_MT1'                            
                 VMDVTMP     ='TOT VCPU PRIMARY CPU'                    
                 VMDVTMP_MT1 ='VMDVTMP_MT1'                             
                 VMDVTMS     ='TOT VCPU SECONDARY CPU'                  
                 VMDVTMS_MT1 ='VMDVTMS_MT1'                             
                 VMDWASTE    ='TIMES PGFLTS AGELIST'                    
                 VMDWKPLX    ='WRKALLEG COUNTS, SSI'                    
                 VMDWKTOD    ='VTIME, WRKALLEG SSI'                     
                 VMDWKTOT    ='WRKALLEG COUNTS'                         
                 VMUDSPETM   ='TIME DISPATCHED'                         
                 VMUDWTETM   ='TIME READY TO BE DISPATCH'               
                 VMUNREBAL   ='CONFIG REBALANCES'                       
                 VMUREBAL    ='VMUREBAL'                                
                 VMUVMLTL0='1ST*TOPOLOGY*STEALS'                        
                 VMUVMLTL1='2ND*TOPOLOGY*STEALS'                        
                 VMUVMLTL2='3RD*TOPOLOGY*STEALS'                        
                 VMUVMLTL3='4TH*TOPOLOGY*STEALS'                        
                 VMUVMLTL4='5TH*TOPOLOGY*STEALS'                        
                 VMUVMLTL5='6TH*TOPOLOGY*STEALS'                        
                 VMUVMTL0='1ST*TOPOLOGY*MOVES*FOR WORK'                 
                 VMUVMTL1='2ND*TOPOLOGY*MOVES*FOR WORK'                 
                 VMUVMTL2='3RD*TOPOLOGY*MOVES*FOR WORK'                 
                 VMUVMTL3='4TH*TOPOLOGY*MOVES*FOR WORK'                 
                 VMUVMTL4='5TH*TOPOLOGY*MOVES*FOR WORK'                 
                 VMUVMTL5='6TH*TOPOLOGY*MOVES*FOR WORK'                 
              -INFILE XAMCPU changes:                                   
                Known problem, to be corrected in zVPS next iteration:  
                  IFL records have only CPUID='IFLs' with TOTAL values. 
                  There are no CPUID='IFLnnn' records for each IFL, and 
                  the values in that CPUID='IFLs' record are the same as
                  the values in the CPUID='TOTAL' record.               
              -New variables in SYTSYP segment added to both datasets   
               XAMCPUBY and XAMCPUTO:                                   
                 PLSPAGPS='COUNT*SSCH*FOR PG/SPOOL'                     
                 PLSSTKPE='ETS*DROP*COUNT'                              
                 PLSTMRCE='GUEST*ENABLE*COUNT'                          
                 PLSPRVSC='SVC*INTERUPT*COUNT'                          
              -New variables in SYTPRP segment added to both datasets   
               XAMCPUBY and XAMCPUTO:                                   
                 CPUCOUNT='CPU*COUNTS*FOR NCPU+1'                       
                 PFXFST44='SIMULATION*DIAG44'                           
                 PFXFSTPX='PARTIAL*EXECUTION*INTERUPTS'                 
                 PFXFSTSG='SIMULATION*SIGP'                             
                 PFXFSTXC='REFLECTIONS*GUEST*EXTERN '                   
                 PLS9CDSP='ALREADY*DISPATCHED'                          
                 PLS9CNR ='VMDSTATE*LT*VMDREADY'                        
                 PLS9CSWT='AND*SOFT*WAIT'                               
                 PLS9CWT ='AND*IN WAIT*STATE'                           
                 STEALPCT='LPAR*STEAL*TIME'                             
              -New variables in SYTRSP segment added to both datasets   
               XAMCPUBY and XAMCPUTO:                                   
                 PLSALECL='LT*2GB*LIST'                                 
                 PLSALECG='GT*2GB*LIST'                                 
              -New variables in SYTCOM segment added to both datasets   
               XAMCPUBY and XAMCPUTO:                                   
                 PLSIUCVT='TOTAL*IUCV*COUNT'                            
                 PLSISEVS='VSWITCH*TO A VM*SUCCESS'                     
                 PLSISTVS='VM TO A*VSWITCH*SUCCESS'                     
                 PLSISUVS='FAILED*VSWITCH IUCV'                         
                 PLSISEAS='ASYNCMD*TO A VM*SUCCESS'                     
                 PLSISTAS='VM TO A*ASYNCMD*SUCCESS'                     
                 PLSISUAS='FAILED*ASYNCMD IUCV'                         
                 PLSISESC='SCLP TO A*VM*SUCCESS'                        
                 PLSISTSC='VM TO A*SCLP*SUCCESS'                        
                 PLSISUSC='FAILED*SCLP*IUCV'                            
                 PLSISEVE='VMEVENT*TO A VM*SUCCESS'                     
                 PLSISTVE='VM TO A*VMEVENT*SUCCESS'                     
                 PLSISUVE='FAILED*VMEVENT*IUCV'                         
              -New variable in SYTSCP segment added to both datasets    
               XAMCPUBY and XAMCPUTO:                                   
                 PLSDSPCN='100*LOOP CNT*ON*&SCHED LCK'                  
              -New variable in STORSP segment added to both datasets    
               XAMCPUBY and XAMCPUTO:                                   
                 PLSASFCG='TIMES*ONE PAGE*FROM*GT 2G*LIST'              
                 PLSASFCL='TIMES*ONE PAGE*FROM*CONTIG*LIST'             
                 PLSESSA ='ESSA*INSTRUCTION*COUNT'                      
                 PLSLTDPE='LONG TERM*DORM*EMERGENCY*PASSES'             
                 PLSPCPAG='CMM*MAYBE*VOLATILE*STOLEN'                   
                 PLSPUPAG='CMM*MAYBE*VOLATILE*UNCH PGS*STOLEN'          
                 PLSUPAGE='CMM*UNUSED*STOLEN'                           
                 PLSUPREC='CMM*UNUSED'                                  
                 PLSVPAGE='CMM*VOLATILE*STOLEN'                         
              -New variable in PRCMFC segment added to both datasets    
               XAMCPUBY and XAMCPUTO:                                   
                 CCFCPUSP   ='CPU*SPEED '                               
                 CYCLECNT   ='CYCLE*COUNT*NOT IN*WAIT'                  
                 INSTRCNT   ='INSTRUCTIONS*EXECUTED'                    
                 L1ICACHW   ='LEVEL 1*ICACHE*DIRECTORY'                 
                 L1IPENAL   ='L1*PENALTY*CYCLE*COUNT'                   
                 L1DCACHW   ='LEVEL 1*DCACHE*DIRECTORY'                 
                 L1DPENAL   ='L1*PENALTY*CYCLE*COUNT'                   
                 PCYCLECNT  ='CYCLE*COUNT*NOT IN*WAIT'                  
                 PINSTRCNT  ='INSTRUCTIONS*EXECUTED'                    
                 PL1ICACHW  ='LEVEL 1*CACHE*DIRECTORY'                  
                 PL1IPENAL  ='L1*PENALTY*CYCLE*COUNT'                   
                 PL1DCACHW  ='LEVEL 1*CACHE*DIRECTORY'                  
                 PL1DPENAL  ='L1*PENALTY*CYCLE*COUNT'                   
                 CCFEXT0='0TH*COUNTER'                                  
                 CCFEXT1='1ST*COUNTER'                                  
                  . . .                                                 
                 CCFEXT62='62TH*COUNTER'                                
                 CCFEXT63='63TH*COUNTER'                                
                 CPI     ='CYCLES*PER*INSTRUCTION'                      
                 PRB     ='PERCENT*PROBLEM*STATE'                       
                 L1MP    ='LEVEL 1*MISS*PER INST'                       
                 L2P     ='PCT FROM*LEVEL 2'                            
                 L3P     ='PCT FROM*LEVEL 3*SAME'                       
                 L4LP    ='PCT FROM*LEVEL 4*SAME'                       
                 L4RP    ='PCT FROM*LEVEL 4*REMOTE'                     
                 MEMP    ='PCT*FROM*MEMORY'                             
              -New variable in PRCRCD segment added to both datasets    
               XAMCPUBY and XAMCPUTO:                                   
                 CALENTMT='CPU*ENTITLEMENT'                             
                 RCCTOPDS='TOPOLOGY*BIT*MASK'                           
                 PFXDSPCS='LONG*PATHS*THRU*DISP2'                       
                 PLSDSPCM='TIMES*DISP*VMDBK*MOVED'                      
                 PLSSTLTL0='0TH*CNT*STOLEN*VMDBKS'                      
                 PLSSTLTL1='1ST*CNT*STOLEN*VMDBKS'                      
                 PLSSTLTL2='2ND*CNT*STOLEN*VMDBKS'                      
                 PLSSTLTL3='3RD*CNT*STOLEN*VMDBKS'                      
                 PLSSTLTL4='4TH*CNT*STOLEN*VMDBKS'                      
                 PLSSTLTL5='45H*CNT*STOLEN*VMDBKS'                      
              -New variable in PRCDHF segment added to both datasets    
               XAMCPUBY and XAMCPUTO:                                   
                 DSVASSOC ='ONLINE*CPUS'                                
                 DSVUNPRK ='UNPARKED*CPUS'                              
                 HFUSERZ  ='TIMES*NO VMDBK*IN DLIST'                    
              -INFILE XAMSYS changes:                                   
               /* SYTEP2 */                                             
                  TCT_FCOP ='FICON*OPS*FCX*CMDS'                        
                  TCT_DFCOP='DEFRD*FICON/FCX*OPS'                       
                  SCT_FCOP ='SUMMATION*COUNT*OPS'                       
                  TCT_FCXTM='FCX*TRANSFER*OPS'                          
                  TCT_DFCXTM='DEFERRED*FCX*XFERS'                       
                  SCT_FCXTM ='SUMMATION*FCX*XFERS'                      
               /* STOSHR */                                             
                  ASCCTRSV='RESERVED*BY*SET*RESERVED'                   
                  ASCDSRSV='CNTLIMITED*BY*SET*RESERVED'                 
               /* SYTCUM */                                             
                  LCUSMTM='SYSTEM*MGMT*TIME'                            
                  PCTSYSM='PCT*SYSTEM*MGMT TIME'                        
               /* SYTSYG */                                             
                  MAI_MISS='MISSING*ADAPTR*INTERUPTS'                   
                  MAI_UREC='UNRECOVERABLE*ADAPTR*INT'                   
                  FXRDONE ='FCX*I/O*COMPLETE'                           
                  FXRWRITE='FCX*WRITES'                                 
               /* STORSG */                                             
                  SECONDS  ='SECONDS'                                   
                  RSAAVCLT ='LT 2G*CONTIG*AVAIL LIST*LO'                
                  RSAAVCHT ='LT 2G CONTIG*AVAIL LIST*HI'                
                  RSAAVCLG ='GT 2G CONTIG*AVAIL LIST*LO'                
                  RSAAVCHG ='GT 2G CONTIG*AVAIL LIST*HI'                
                  RSAEMLO  ='LOW*THRESHOLD'                             
                  RSAEMHI  ='HI*GHREHSOLD'                              
                  RSAEMCPC ='CURRENT*POOL*SIZE'                         
                  RSAEMERG ='EMERGENCY*PGMBK*REQUESTS'                  
                  RSAEMBLO ='TIMES*CPC LT LO'                           
                  RSAEMPTY ='TIMES*CPC*EMPTY'                           
                  RSAEMDFR ='TIMES*PGMBK*DEFERRED'                      
                  RSASWPWT ='PG WRITES*TO*DISK LT 2GB'                  
                  RSASWP2G ='PGMBK WRITES*TO*DISK GT 2GB'               
                  RSAAGEPC ='RSAAGEPC'                                  
                  RSARSDMX ='SET*RESERVED*SYSMAX'                       
                  RSAAGESZ ='TARGET*AGING*LIST'                         
                  RSAAGINC ='FRAMES*ON AGING*LIST'                      
                  RSAEWNDD ='CHANGED*PGS ON*AGELST'                     
                  RSAEWRFO ='REF-D*PGS ON*AGELIST'                      
                  EWCIF    ='CHNGED*PGS*PAGING*OUT'                     
                  EWRIF    ='FEF-D*PGS*PAGING*OUT'                      
                  AGRDY    ='TOTAL*FRMS*ON*AGELIST'                     
                  AGRDYRFW ='REF-D*PGS*WRITTEN'                         
                  AGRDYRFN ='REF-D*PGS*NOT*WRITTEN'                     
                  AVLCTB2S ='AVAILLIST*LT*2GB*SNGL'                     
                  AVLCTB2C ='AVAILLIST*LT*2GB*CONTI'                    
                  AVLCTA2S ='AVAILLIST*GT*2GB*SNGL'                     
                  AVLCTA2C ='AVAILLIST*GT*2GB*CONTI'                    
                  DSTMACT  ='TOD*DEMAND*SCAN*RUNNG'                     
                  CHGWRTOL ='CHNGD*PGS*RE-WRITOLD'                      
                  REFWRTBY ='REF-D*PGS*BYPASS WRT'                      
                  CHGWRTNW ='CHNGD*PGS*RE-WRITNEW'                      
                  REFWRTNW ='REF-D*PGS*RE-WRITTEN'                      
                  AGRECLM  ='PGS*RECLAIMED*AGELIST'                     
                  EXMET    ='DEMAND*SCAN*COMPLETES'                     
                  EXTIM    ='DEMNDSCAN*INCOMPLETES'                     
                  EXCPU    ='DEMANDSCAN*SLOWCPU'                        
                  INVUFO   ='PRIVATE*PGS*INVALDTED'                     
                  INVVUFO  ='PRIVATE*VDSKINVALDTED'                     
                  INVSUFO  ='SHARED*PGS*INVALIDATD'                     
                  RVLUFO   ='PRIVATE*PGS*RE-VALID'                      
                  RVLVUFO  ='PRIV*VDISK*PGS*RE-VAL'                     
                  RVLSUFO  ='SHARED*PGS*REVALIDATD'                     
                  RVLAGL   ='PGS*REVALID*ON*AGELST'                     
                  WRTONDMD ='PGS*RECLAIMED*POSTWRT'                     
                  DSCYCLE  ='DEMAND*SCANS'                              
                  USRVISIT ='USERS*VISITED'                             
                  USRSKIP  ='USERS*SKIPPED'                             
                  RSAALSKL ='AGELIST*PGS*PINNED'                        
                  RSAALSKF ='AGELST*FRMSERIALIZED'                      
                  RSAALSKP ='AGELST*PGSERIALIZED'                       
                  RSAALSKR ='AGLSTSETRESERVED'                          
                  AGRVLRFN ='REREF-D*PGS*NOTWRITTN'                     
                  AGRVLRFW ='REREF-D*PGS*WRITTEN'                       
                  AGRVLCHN ='REREF-D*CHNGD*PGS NW'                      
                  AGRVLCHW ='REREF-D*CHNGD*PGS WRT'                     
                  AVLRQB2S ='SNGLPG*REQUESTS*LT 2GB'                    
                  AVLRQA2S ='SNGLPG*REQUESTS*GT 2GB'                    
                  AVLRQB2C ='CONTIG*REQUESTS*LT 2GB'                    
                  AVLRQA2C ='CONTIG*REQUESTS*GT 2GB'                    
                  AVLRETB2S='RETURNS*SINGLE*LT 2GB'                     
                  AVLRETA2S='RETURNS*SINGLE*GT 2GB'                     
                  AVLRETB2C='RETURNS*CONTIG*LT 2GB'                     
                  AVLRETA2C='RETURNS*CONTIG*GT 2GB'                     
                  AVLPTA2GC='PROTECT* GT 2GB*LIST SIZ'                  
                  AVLPTB2GS='PROTECT*SNGLS* LT   2GB'                   
                  WRTHROTS ='DEMAND*SCAN*THROTTLES'                     
                  PRTHROTS ='PARTIAL*THROTTLES'                         
               /* MTRSCH */                                             
                  SRMFLAGS='SRMFLAGS'                                   
               /* MTRSYS */                                             
                  SYSCMODE='SYSCMODE'                                   
                  VCPUF   ='VCPU ACCOUNTING FACTOR'                     
                  TCPUF   ='TCPU ACCOUNTING FACTOR'                     
                  DIOF    ='DASD I/O FACTOR '                           
                  STORF   ='RESIDENT STORAGE FACTOR'                    
                  CHARGE  ='CHARGE PER UNIT'                            
                  SYSCCR  ='CAPCHANGE*REASON*STSI*1.1.1'                
                  SYSCAI  ='CAPADJUSTMENT*STSI*1.1.1 '                  
                  SYSESTAT='ENSEMBLE*STATUS'                            
                  STITODOF='STP*TOD*CLOCK*OFFSET'                       
                  SYSSTPFL='STP*CONFIGURATION*INFO'                     
                  SYSSTPF2='FLAGS'                                      
                  SYSPLVOL='SSI*PDR*VOLUME*SERIAL'                      
                  SYSCSSID='CHANNEL*SUBSYSTEM*(CSS)*ID'                 
                  SYSCPMOD='CP*LOAD*MODULE'                             
                  HCPLODCK='TOD OF*SYSTEM*GENERATION'                   
                  SLMENSID='URM*ENSEMBLE*ID'                            
               /* MTRMEM */                                             
                  SYSGSTBY='STANDBY*REAL*STORAGE*SIZE'                  
                  SYSGSTRS='RESERVED*REAL*STORAGE*SIZE'                 
               /* SYTXSG */                                             
                  TCMPINVA='PAGE*FAULTS*RESOLVED*PGINTRK'               
                  TCMSTKEX='TIMES*CPEBK*DEFERED*TRKWRT'                 
                  CMSTKPFK='TIMES*CPEBK*DEFERED*TRKFLT'                 
               /* SYTUWT */                                             
                  CALLLCP ='LIMIT*LIST*CP WAIT'                         
                  CALLLZAP='LIMIT*LIST*ZAP WAIT'                        
                  CALLLIFL='LIMIT*LIST*IFL WAIT'                        
                  CALLLZIP='LIMIT*LIST*ZIP WAIT'                        
                  CALCFCP ='CF WAIT*WAIT FOR*CP'                        
                  CALCFZAP='CF WAIT*WAIT FOR*ZAP'                       
                  CALCFIFL='CF WAIT*WAIT FOR*IFL'                       
                  CALCFZIP='CF WAIT*WAIT FOR*ZIP'                       
                  CALSWCP ='SIM WAIT*WAIT FOR*CP'                       
                  CALSWZAP='SIM WAIT*WAIT FOR*ZAP'                      
                  CALSWIFL='SIM WAIT*WAIT FOR*IFL'                      
                  CALSWZIP='SIM WAIT*WAIT FOR*ZIP'                      
                  CALCWCP ='CPU WAIT*WAIT FOR*CP'                       
                  CALCWZAP='CPU WAIT*WAIT FOR*ZAP'                      
                  CALCWIFL='CPU WAIT*WAIT FOR*IFL'                      
                  CALCWZIP='CPU WAIT*WAIT FOR*ZIP'                      
                  CALCRCP ='VMDBKS*RUNNING*ON CP'                       
                  CALCRZAP='VMDBKS*RUNNING*ON ZAP'                      
                  CALCRIFL='VMDBKS*RUNNING*ON IFL'                      
                  CALCRZIP='VMDBKS*RUNNING*ON ZIP'                      
                  CALLLICF='LIMIT*LIST*IN ICF'                          
                  CALCFICF='CONSOLE*FUNCTION*MASTER'                    
                  CALSWICF='SIMULATION'                                 
                  CALCWICF='CPU*WAIT'                                   
                  CALCRICF='RUNNING'                                    
                  /* SYTUSR */                                          
                  RLOIB='ACTIVE*INBOUND*LGRS'                           
                  RLOOB='ACTIVE*OUTBOUND*LGRS'                          
               /* SYTRSG */                                             
                  RSASNG2G='SINGLE*FRAMES*GT 2GB*AVAIL'                 
                  RSASNGAV='SINGLE*FRAMES*LT 2GB*AVAIL'                 
               /* SUBSUM */                                             
                  NCPCAPABIZE='CPU*CAPABILITY*FACTOR'                   
                  OVERCOMMIT ='OVERCOMMIT'                              
                  STORAGESIZE='STORAGE*SIZE'                            
                  XSTORESIZE ='XSTORE*SIZE'                             
              -INFILE XAMDEV changes:                                   
              -New variable in CONFIG segment added to XAMDEV dataset:  
                  EDEVATTR='EDEVATTR'                                   
                  RDEVHPPL='HYPERPAV*POOL*NUMBER'                       
                  CALDEVFLAGS='CALDEVFLAGS'                             
                  DEVPTHS ='DEVPTHS'                                    
              /*IODDEV */                                               
                  PAVINELG  ='I/O*INELIGIBLE*TO STEAL'                  
                  PAVUSES   ='I/O*STEALS'                               
                  PAVSSCH   ='BASE*PAV*SSCH'                            
                  PAVCOUNT  ='PAV*DEVICE*COUNT'                         
                  PAVCNTIM  ='PAV*ALIAS*CONNECT*TM'                     
                  PAVCPTIM  ='PAV*ALIAS*PEND*TM'                        
                  PAVCDTIM  ='PAV*ALIAS*DISC*TM'                        
                  PAVCQTIM  ='PAV*ALIAS*QUEUE*TM'                       
                  PAVCATIM  ='PAV*ALIAS*ACTIVE*TM'                      
                  PAVDBTIM  ='PAV*ALIAS*SUBCHAN*TM'                     
                  PAVIRTIM  ='PAV*ALIAS*QUEUE*TM'                       
                  PAVCC3S   ='PAV*ALIAS*CC3*IO CNT'                     
                  RDEVSKSM64='TOTAL*SEEK*CYCLINDERS'                    
                  RDEVWXCT  ='COUNT*FCX*WRITES'                         
                  RDEVRXCT  ='COUNT*FCX*READS'                          
              -INFILE XAMTCP changes:                                   
               /*VSIUSR*/                                               
                  STGSAMPS='STGSAMPS'                                   
                  VMPEAK  ='PEAK*USAGE'                                 
                  VMSIZE  ='CURRENT*USAGE'                              
                  VMLCK   ='CURR*MLOCKED*MEMORY'                        
                  VMHWM   ='PEAK*RSS'                                   
                  VMRSS   ='RESIDENT*SET*SIZE'                          
                  VMDATA  ='SIZE*DATA*SEGMENT'                          
                  VMSTK   ='SIZE*OF*STACK'                              
                  VMEXE   ='SIZE*TEXT*SEGMENT'                          
                  VMLIB   ='SHARED*LIBRARY*USAGE'                       
                  VMPTE   ='PAGETABLE*ENTRIES*SIZE'                     
                  VMSWAP  ='SWAP*SPACE*USED'                            
               /*VSINAP*/                                               
                  STGSAMPS ='STGSAMPS'                                  
                  VMPEAK   ='PEAK*USAGE'                                
                  VMSIZE   ='CURRENT*USAGE'                             
                  VMLCK    ='CURR*MLOCKED*MEMORY'                       
                  VMHWM    ='PEAK*RSS'                                  
                  VMRSS    ='RESIDENT*SET*SIZE'                         
                  VMDATA   ='SIZE*DATA*SEGMENT'                         
                  VMSTK    ='SIZE*OF*STACK'                             
                  VMEXE    ='SIZE*TEXT*SEGMENT'                         
                  VMLIB    ='SHARED*LIBRARY*USAGE'                      
                  VMPTE    ='PAGETABLE*ENTRIES*SIZE'                    
                  VMSWAP   ='SWAP*SPACE*USED'                           
                  PROCID   ='PROCID'                                    
                  PPIDL    ='PPIDL'                                     
                  PROCNAMEL='PROCNAMEL'                                 
                  PATHNAMEL='PATHNAMEL'                                 
                  APPLIDSS ='APPLIDSS'                                  
               /*VSISFT*/                                               
                  PRTY     ='PRTY'                                      
                  STGSAMPS ='STGSAMPS'                                  
                  VMPEAK   ='PEAK*USAGE'                                
                  VMSIZE   ='CURRENT*USAGE'                             
                  VMLCK    ='CURR*MLOCKED*MEMORY'                       
                  VMHWM    ='PEAK*RSS'                                  
                  VMRSS    ='RESIDENT*SET*SIZE'                         
                  VMDATA   ='SIZE*OF DATA*SEGMENT'                      
                  VMSTK    ='SIZE*OF*STACK'                             
                  VMEXE    ='SIZE*OF TEXT*SEGMENT'                      
                  VMLIB    ='SHARED*LIBRARY*USAGE'                      
                  VMPTE    ='PAGETABLE*ENTRIES*SIZE'                    
                  VMSWAP   ='SWAP*SPACE*USED'                           
                  PROCID   ='PROCID'                                    
                  PPIDL    ='PPIDL'                                     
                  PROCNAMEL='PROCNAMEL'                                 
                  PATHNAMEL='PATHNAMEL'                                 
                  APPLIDSS ='APPLIDSS'                                  
               /*VSISYS*/                                               
                  PROCTOT  ='PROCTOT'                                   
                  STATIC   ='STATIC'                                    
                  TIMED    ='TIMED'                                     
                  RELEASEP ='RLS RATE*IN PAGES'                         
                  RELEASETM='RLS TIME*IN SECONDS'                       
                  SWAPINESS='SWAPINESS'                                 
                  CPUCOUNT ='CPUCOUNT'                                  
               /*HSTMEM*/                                               
                  RWFLAG ='RWFLAG'                                      
                  BOOTFLG='BOOTFLG'                                     
                  BUFFER ='BUFFER'                                      
                  BUFFERCH='BUFFERCH'                                   
                  DESCR is expanded to 32 positions (Apr 23)            
               /*UCDSYS*/                                               
                  ANONYMOUS='ANONYMOUS'                                 
                  SHARED   ='SHARED'                                    
                                                                        
====== Changes thru 33.085 were in MXG 33.03 updated Mar 31, 2015=======
                                                                        
Change 33.085  Change 33.078 VGETDDS removal of SASAUTOS was incorrect, 
VGETDDS        causing ERROR 22-322 generated by Macro Variable TOSET;  
Mar 30, 2015   DDNAMES was corrected to DDOUT.                          
   Thanks to Jim Horne, Lowe's, USA.                                    
                                                                        
Change 33.084  Change 33.018 was dropped between 33.01 and 33.02.       
EXTY8036       New dataset TYPE8036 (EXEC WITH SETUID/SETGID) and new   
EXTY8056       dataset TYPE8056 (CHECK FILE OWNER) are now created and  
IMAC80A        variable TOKMPROCUSERMAX is now spelled correctly so the 
VMAC80A        UNINIT TOKPROCUSERMAX message is eliminated.             
VMXGINIT                                                                
Mar 29, 2015                                                            
                                                                        
====== Changes thru 33.083 were in MXG 33.03 dated Mar 27, 2015=========
                                                                        
Change 33.083  Summary datasets PDB.ASUM70PR/PDB.ASUM70LP have INCORRECT
VMXG70PR       values for intervals when ALL LPARs are NOT active for   
Mar 27, 2015   the full summary interval you requested, e.g., you set   
               INTERVAL=HOUR (in your TAILORED ASUM70PR member or your  
               %VMXG70PR invocation) but the first RMF records in each  
               SMF file was the 23:50 START, written at 00:00.01, which 
               created an ASUM70PR HOURLY observation, (for EACH system,
               as each SYSTEM creates TYPE70PR for each LPAR it "sees") 
               with a START of 23:00, but with only 10 minutes DURATM.  
               Or, if you activate an LPAR at 10:30, the ASUM70PR obs   
               will have only 30 minutes DURATM.  The incorrect DURATM  
               impacts the individual LPAR durations, and the PCTCPUBY  
               in ASUM70PR (the SYSPLEX value, and NOT the busy of the  
               SMF SYSTEM that created the ASUM70PR observation) is     
               wrong and can be greater than 100%.                      
                                                                        
              -These defective observations can be deleted by testing   
               that DURATM is less than your requested summary INTERVAL.
                                                                        
              -OR: THE CORRECT VALUES ARE IN THE PDB.ASUMCEC/ASUMCELP   
               datasets, and since there is only one observation in the 
               PDB.ASUMCEC for each interval (for each CECSER), you do  
               not have to select which SYSTEM's record is used in your 
               reports (and your reports will be produced even if that  
               SYSTEM goes away!).                                      
                                                                        
               And, at this time, the underlying error in VMXG70PR has  
               NOT been resolved; it is related to the PER-SYSTEM logic 
               which is clearly vulnerable to individual system metrics,
               but the newer and more robust per-CEC logic resolves the 
               error, or the defective observations can be deleted.     
               (If these are abnormal hours, maybe you still want to    
               delete them, even when using the PDB.ASUMCEC data!).     
               With 60 PROC/DATA steps in the complex VMXG70PR logic,   
               the risk of damage to the good might not justify trying  
               to repair                                                
              -No logic was changed; debugging PROC PRINTs were inserted
               but are disabled.                                        
                                                                        
Change 33.082  DCOLLECT dataset DCOLDSET now contains variable DCDCMTYP 
VMACDCOL       decoded from DCDEXFLG to identify compression type, using
Mar 26, 2015   MG014CT macro (added in MXG 33.01 for TYPE1415) to print 
               these possible values:                                   
                   0='0:NOT COMPRESSED/UNKNOWN'                         
                   1='1:GENERIC'                                        
                   2='2:TAILORED'                                       
                   3='3:ZEDC'                                           
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
Change 33.081 -New _READALL macro processes 70s, 72s,and 30s in one pass
SAGANAL        of SMF to significantly reduce elapsed run time.         
Mar 27, 2015  -The 4HR Average Zip Eligible MSU is added to REPORT 3.   
Apr  8, 2015  -New REPORT 30 with the CAPTURE RATIO shows the IBM 4HOUR 
IMACSAG        AVERAGE MSU and the TOTAL MSU CAPTURED in the RMF 72     
VMXGINIT       Service Class records.                                   
Apr 13, 2015  -New IMACSAG and &MACSAG exits permit report selection for
               specific dates.                                          
                                                                        
Change 33.080  Documentation note.  The default BUILDPDB builds the ID  
TYPEID         dataset using a VIEW and then invokes %ANALID to report. 
Mar 24, 2015   The VIEW is NOT deleted, but if you have added code that 
               uses the ID dataset (like PROC SORT DATA=ID), the entire 
               SMF INPUT FILE WILL BE READ AGAIN, or, if you have used  
               FREE=CLOSE, that second read will fail with FILE SMF NOT 
               ASSIGNED.  You can prevent the second read by disabling  
               the view, using  %LET VWVMACID=;  to disable for ID, but 
               that will require more //WORK disk space.                
                                                                        
Change 33.079  Protection for truncated SMF Type 22 Subtype 11 LRECL=32 
VMAC22         (LENGTH=28) when that subtype must be at least 140 bytes.
Mar 24, 2015                                                            
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
Change 33.078  %MACROs that SAS puts in SASAUTOS (%TRIM,%LOWCASE,others)
UTILBLDP       have been completely removed from all MXG members, since 
Mar 23, 2015   we still find sites that do not have FILENAME SASAUTOS to
               resolve those functions (that SHOULD, IMO, been delivered
               as real functions and avoid 20 years of SASAUTO errors). 
               These were the final members that now use %SYSFUNC().    
                 ANALRANK BLDNTPDB READDB2 UTILBLDP UTILDUMP VGETALOC   
                 VGETDDS VMXGALOC VMXGCAPT VMXGFIND VMXGPRAL VMXGSRCH   
                 ZAUTOCHK VMXGPARS                                      
                                                                        
Change 33.077  WPS Only. MXG TYP120xx SMF 120 datasets can have strange 
VMAC120        characters in UCS text because there were two tests for  
VMXGINIT       &SYSVER GE 8.2 that are now corrected to &SASVER GE 8 in 
Mar 23, 2015   VMAC120 and VMXGINIT (which incorrectly set &UCS2B4).    
               For WPS, the &SYSVER returns 3.01 (and is 9.4 for SAS),  
               and it is used when the sub-version is needed, but MXG   
               intended to set &SASVER to 8 for WPS, and use the first  
               digit of &SYSVER for &SASVER for SAS, for both WPS/SAS   
               and SAS V8/V9 selections.                                
               8 for WPS (and is 9 for SAS) so that &SASVER can be used 
               to detect WPS and/or SAS V9 features.  And, in VMXGINIT  
               the actual value set for &SASVER was 8.2 instead of 8 for
               WPS.  And since I needed to find any other exposures, I  
               removed a number of archaic tests for &SASVER 5 and 6 in 
               these members:                                           
                 BUIL3001 BUILD001 BUILDPD3 BUILDPDB DOCPDB   FORMATS   
                 IMACPDBX JCLUXRE6 MONTHBL3 MONTHBLD MONTHBLS MONTHWEK  
                 PRODTEST PRODTESW TYPSIMS  TYPSIMS7 VFMT102  VMAC120   
                 VMAC7072 VMACIMS  VMXGINIT WEEKBL3D WEEKBL3T WEEKBLDD  
                 WEEKBLDT                                               
   Thanks to Erling Andersen, SMT, DENMARK.                             
                                                                        
Change 33.076  Support for IMS56FA Chained/Switched INPQUETM correction.
TYPEIMST       INPQUETM for chained transactions (have same ARRVTIME) is
TYPSIMST       revised to use the prior transaction's HELDENDTIME as the
VMACIMS        the "ARRVTIME" for the next transaction.  Variable SWITCH
Mar 24, 2015   identifies if this was the first, or subsequent, switched
               transaction, and HELDENDTIME is kept in IMS56FA. Variable
               RESPNSTM is also recalculated with the new INPQUETM.     
               The correction is made in the _SIMS56G dataset sort macro
               so it requires a full sort of the IMS56FA dataset; the   
               TYPSIMST member has the JCL and SYSIN example to use to  
               correct INPQUETM and create the IMS56FA.IMS56FA dataset. 
               The TYPEIMST member creates WORK.IMS56FA, unsorted and   
               uncorrected.                                             
               Or, to create ALL of the IMS log datasets and correct    
               the INPQUETM, you can use                                
                 %INCLUDE SOURCLIB(TYPEIMS7);                           
               which invokes the _SIMS46X sort macro to sort both the   
               46x and 56x IMS log records and fix IMS56FA's INPQUETM,  
               writing all IMS datasets to //WORK, but you can use      
               %LET PIMSxxx=YOURDD; to send individual datasets to your 
               chosen DDNAME.                                           
   Thanks to Thomas Peiper, TIETO, FINLAND.                             
                                                                        
Change 33.075  When VMXGDBAA was run, the KEEPIN= logic in VMXGSUM could
VMXGSUM        fail, resulting in UNINITIALIZED VARIABLEs notes for     
VMXGDBAA       QWACESC and other variables.  Exposed when removing the  
Mar 22, 2015   AUTOCALL macros from VMXGDBAA, was not actually reported.
                                                                        
Change 33.074  Support for Mainview for MQ version 5.2 BBMQQUES 'E6'    
VMACBBMQ       with these new variables added:                          
Mar 22, 2015     QSAC6NXG ='NEXT*AC6 RECORD*WITH THIS*HASH'             
                 QSIBGETC ='CONSUMED*MQGET*BYTES'                       
                 QSIBGTCF ='GET*BYTES*CONSUMED*RATE'                    
                 QSIFPUT  ='FAST*PUT*COUNT'                             
                 QSILMPUT1='LARGEST*MQPUT1*SESSION'                     
                 QSISMPUT1='SMALLEST*MQPUT1*INTERVAL'                   
                 QSISTCKB ='INTERVAL*START*DATETIME*STAMP'              
                 QSQUDPTH ='UNCOMMITTED*MESSAGES'                       
                 QSSBGETC ='CONSUMED*MQGET*BYTES'                       
                 QSSBGTCF ='GET*BYTES*CONSUMED*RATE'                    
                 QSSBGTCR ='GET*BYTES*CONSUMED*RATE'                    
                 QSSFPUT  ='FAST*PUT*COUNT'                             
                 QSSFPUT1 ='FAST*PUT1*COUNT'                            
                 QSSLMPUT1='LARGEST*MQPUT1*SESSION'                     
                 QSSSMPUT1='SMALLEST*MQPUT1*SESSION'                    
                 QSSSTCKB ='SESSION*START*DATETIME*STAMP'               
                 QWIFPUT1 ='FAST*PUT1*COUNT'                            
               and these old variables are no longer input and will be  
               missing values in BBMQQUES:                              
                 QSIFBGTF QSIFBGTR QSIFBP1F QSIFBP1R QSIFBPT1 QSIFBPTF  
                 QSIFBPTR QSIFBPUT QSINDSCR QSSFBGTF QSSFBP1F QSSFBPT1  
                 QSSFBPTF QSSFBPTR QSSFBPUT                             
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.073  New variable FCBYTERATE added to TYP11903 and TYP11907   
VMAC119        datasets.                                                
Mar 22, 2015                                                            
                                                                        
Change 33.072  SMF 103 Documentation.  For the Apache Server (which must
VMAC103        be used in z/OS 2.2 where the prior Domino Server is not 
Mar 22, 2015   supported), the JOB name can be passed into the D record 
               with a variable -  export JOBNAMEH="WEBSRV02" - in the   
               shell scripts that start the Apache Web Server and using 
               this JOBNAMEH variable as ServerName ${JOBNAMEH} in the  
               httpd.conf file.                                         
               The SMF 103 record has been written by the same product  
               since its inception, but the IBM product names have      
               included these:                                          
                "HTTP Web Sphere Server"                                
                 Lotus Domino GO Webserver R4                           
                 Internet Connection Secure Server (R3,R2)              
                 and now, in 2015, Apache Server.                       
   Thanks to Joseph J. Faska, DTCC, USA.                                
                                                                        
Change 33.071  z13 SUPPORT. MXG 33.03 REQUIRED ONLY FOR PROCVIEW CORE.  
VMAC7072       For PROCVIEW CPU non-SMT, NO CHANGES WERE MADE TO RMF 70.
Mar 21, 2015                                                            
               For SMT PROCVIEW CORE Mode, MXG Change 33.046 in 33.02   
               updated the TYPE70 dataset, but this Change 33.071 in MXG
               33.03 is required to update the new SMT metrics correctly
               in the TYPE70PR dataset, to get the CPUID, LCPUADDR, and 
               CORE_ID from the four segments that don't have the same  
               number of segments: OFFCPUD and SMF70COS have 20 for the 
               6 online CPs, 4 offline CPs, and 5 zIIPs with CPU_NUM=2, 
               while SMF70BDN/LPARCPUX has only 18 segments (with the   
               CORE_NUM needed to look-up the LCPUADDR), and there are  
               only 14 Core_ID values.                                  
                                                                        
               This was a complex update to a CRITICAL MXG MEMBER, with 
               500+ lines of code inserted lines into the 27,000 lines. 
               The SMT Mode data has been validated with RMF records,   
               with a wide range of LPAR configurations.  When in SMT   
               mode, please examine the new data carefully and contact  
               support@mxg.com if you have questions.                   
                                                                        
               Note: If you read the changed SMT mode RMF 70s with an   
               old MXG, RMFINTRV may have NEGATIVE CPUOVHTM values and  
               the %PCTCPUBY values may be over 100%.                   
                                                                        
           Specifically, if z/OS is IPL'd with LOADxx PROCVIEW CORE, on 
           a processor that is SMT capable, then whether or not MT is   
           Active, and even if MT=1 is specified, then the RMF 70 record
           is restructured with CORE_ID.                                
                                                                        
           This support was validated with z/OS 2.1 and z13 data.       
                                                                        
                                                                        
Change 33.070  New INCLAI, three $LIST_L and $RESTAR TOKENIDs, added by 
VMACTPMX       ThruPut Manager AE+ V7R1.0 create five new variables     
Mar 20, 2015    INCLA1  JBL54043 JBL54L44 JBL54L45  RESTAR              
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
Change 33.069  SAS 9.4 has a dictionary entry for DESTINATIONS but      
ANALDB2R       older releases do not. On zOS, report MXGDB2B1 used this 
Mar 20, 2015   to see if the active destination for ODS was listing and 
               to bypass the graphics code in that report. The PROC SQL 
               is now only used when we find SAS 9.4 or greater.        
              -Spurious message were produced indicating reports were   
               requested when you specified report=NO because the code  
               was checking the length and not the value.               
              -If the DB2STATB dataset was empty or non-existent the    
               macro variable GOTRMF did not exist and raised an        
               unresolved MACRO variable error.                         
   Thanks to Randy Hewitt, HP, USA.                                     
                                                                        
Change 33.068  Change 30.133 typo caused Q8STCCPU to not be kept.       
VMACDB2                                                                 
Mar 20, 2015                                                            
   Thanks to Tim King, Blue Cross Blue Shield of South Carolina, USA.   
                                                                        
Change 33.067  DB2 Trace ID=102 IFCID=220 misaligned, causing ILLEGAL   
VMAC102        ARGUMENT TO MDY function.  The QW0220xx variables are    
Mar 17, 2015   now kept.                                                
   Thanks to Randy Hewitt, HP, USA.                                     
                                                                        
Change 33.066  VMXGPPDS failed when used as  documented, unable to find 
VMXGPPDS       MYPDS because the last few lines of the macro incorrectly
Mar 17, 2015   tried to execute the macro with the defaults.            
                                                                        
Change 33.065  If %VGETLIBS found no LIBNAMEs were allocated, it failed 
VGETLIBS       with MACRO variables not found.  Now if there are none   
Mar 17, 2015   found, it dies a graceful death and tells you that it    
               found no matching LIBNAMES.                              
                                                                        
Change 33.064  Format $MGSTCRT new values for SMF19RTM/RTE variables:   
FORMATS           '07'X='07X:VTV MOVE'                                  
Mar 16, 2015      '08'X='08X:ALTERNATE RECALL'                          
   Thanks to Mike Jacques, BB&T, USA.                                   
                                                                        
Change 33.063  In parsing a quoted literal such as '15MAR2015'D, to make
VMXGPARS       the text more readable, the D could be separated from the
Mar 26, 2015   Quote, resulting in a 180 Syntax Error.  VMXGPARS now    
               recognizes a DT following a quote and/or any non-blank   
               character and extends the string.                        
                                                                        
Change 33.062 -In Change 31.209, VMXGSUM's %TRIM AUTOCALLed function was
VMXGSUM        replaced by the internal %SYSFUNC function, to circumvent
VMXGINIT       errors when sites don't have AUTOCALL/MAUTOSOURCE/etc set
Mar 16, 2015   up correctly, but %TRIM crept back in VMXGSUM and is now 
VMXGPARS       again replaced with %SYSFUNC.                            
              -MXGDEBUG=FULL option executes PROC OPTIONS VALUE, to show
               each option's value and how it was set, PROC PRINTs the  
               SASHELP tables VLIBNAM to show all LIBNAMES, and VEXFL to
               show all External FILENAMES - (is there a SASAUTOS??),   
               and enables these full source code diagnostic options    
                OPTIONS SOURCE SOURCE2 MACROGEN MPRINT SYMBOLGEN;       
               to print full source with line numbers on the SAS log.   
               Invoke the FULL option in //SYSIN with this syntax:      
                 %LET MXGDEBUG=FULL; %VMXGINIT;                         
              -The %LEFT in %VMXGPARS was replaced.                     
                                                                        
Change 33.061  GDPS SMF 105 INPUT STATEMENT EXCEEDED when XVMX segment  
VMAC105        was not present; the bit test was insufficient to confirm
Mar 16, 2015   the segment was extended so a length test was added.     
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.060A Change text was lost, added May 2016.                    
ANAL113        Dataset ASUM113 was replaced by ASUM1131 for reports.    
Mar 11, 2015                                                            
                                                                        
Change 33.060 -DCOLLECT Cluster dataset DCOLCLUS now contains variables 
VMACDCOL       DCDDATCL,DCDMGTCL,DCDSTGCL, Data/Management/Storage Class
Mar 11, 2015   that are retained from the immediately preceding type D  
Mar 21, 2015   record prior to the type A record, when the "D" record's 
               DSNAME matches the "A" records' Cluster Name.            
              -In DCOLDSET dataset, multi-volume records now contain    
               those three Class variables in all observations; in the  
               DCOLLECT records, those fields are only populated in the 
               DCDVOLSQ=1 records.  This change revised the _SDCODSN    
               Data Set Sort to propagate from the first to subsequent  
               volume's observations. You MUST USE TYPSDCOL to invoke   
               that _SDCODSN data set sort or classes will be blank in  
               the 2nd and subsequent volumes.                          
              -Mar 21: DCOLDSET dataset label added to PROC SORT.       
   Thanks to John Kim, Worker's Compensation Board of Alberta, CANADA.  
                                                                        
Change 33.059  Support for Thales Security Resource Manager RG1100.     
EXTHALRT      -New variables added to THALSUMD dataset:                 
IMACTHAL         THAASID ='SSID OF*ORIGIN*APPL-AS'                      
VMACTHAL         THADBUSY='BUSY*WITH*USER*REQUESTS'                     
VMXGINIT         THADINTV='INTERVAL*DURATION'                           
Mar 10, 2015     THADNCNT='REQUESTS*PROCESSED'                          
Mar 24, 2015     THADOVER='BUSY*WITH*SRM*REQUESTS'                      
Apr 15, 2015     THADUFLG='DEVICE*CONTINUOUS*USE*OR NOT'                
              -New THALRESP Response Time dataset, with variables:      
                 THAASID  ='SSID OF*ORIGIN*APPL-AS'                     
                 THAJBNM  ='JOBNAME*OF ORIGIN*USER APPL'                
                 THARSTCK ='USER*MESSAGE*INITIATION*TIME'               
                 THARFDBK ='FEEDBACK*CODE*SET BY*SRM'                   
                 THARPRI  ='MESSAGE*PRIORITY'                           
                 THAMTYPE ='MESSAGE*TYPE*HSM*CODE'                      
                 THAERRCD ='ERROR*CODE*SET BY*HSM'                      
                 THARINTV1='1ST*INTERVAL*ELAPSED*TIME'                  
                    . . .                                               
                 THARINTV12='12TH*INTERVAL*ELAPSED*TIME'                
              -Note: TYPETHAL replaced TYPESRHS.                        
              -Mar 24: THAHSM formatted $HEX16, THAHSMR $HEX32.         
              -Apr 15: THALRESP updated and validated with data.        
               Datasets THALEXCE,THALVIOL,THALSUMD,THALRESP have these  
               variables decoded from THAHAM/THAHAMR:                   
                THAHSMCH='HSM*CHANNEL*DEVICE*NAME'                      
                THAHSMIP='HSM*IP*ADDRESS'                               
                THAHSMAX='HSM*IP*AUXILLARY*PORT'                        
                THASMVT ='HSM*VTAM*DEVICE*NAME'                         
   Thanks to Yves Cinq-Mars, IBM Global Services, CANADA.               
                                                                        
Change 33.058  Support for CICS User Field DNDBKR/DNDBKR in CICSTRAN.   
IMACICVK                                                                
UTILEXCL                                                                
VMAC110                                                                 
Mar  8, 2015                                                            
   Thanks to Michael Creech, Black Knight Financial Services, USA.      
                                                                        
Change 33.057  ECHO= option added in Change 32.154 but not documented:  
UTILBLDP       If you want to see the code that was created by UTILBLDP,
VMXGPARS       it can be printed on the LOG by specifying either the new
Mar 10, 2015   ECHO=YES (or ECHO=Y) argument, or with MXGEXIMSG=YES.    
Mar 20, 2015  -%LEFT replaced in VMXGPARS.                              
                                                                        
Change 33.056  Using OPTIONS OBS=0 to create zero-observation datasets  
SAGANAL        from SMF data, read via the ftp access method, executing 
UTILBLDP       on ASCII, failed with these messages:                    
Mar 11, 2015      NOTE: <<< 451 Transfer aborted: send error.           
                  NOTE: >>> QUIT                                        
                  ERROR: Bad request. Use the debug option for more info
               SAS Note http://support.sas.com/kb/14/679.html documents 
               that OBS=0 can not be used with ftp access method.       
               Tailoring to build RMFINTRV from only 70s and 72s used   
                 %INCLUDE SOURCLIB(TYPS7072);                           
               to create the TYPE70 and TYPE72GO datasets for input to  
               create the RMFINTRV dataset with CPU metrics, but using  
                 OPTIONS OBS=0;                                         
                 %%INCLUDE SOURCLIB(TYPS71,TYPS73,TYPS74,TYPS75,TYPS78);
                 RUN;                                                   
               to create the other datasets required for RMFINTRV, but  
               creating them with zero observations so they take no disk
               space, preventing B37 if high volume ID=74 SMF records   
               were accidentally in the input SMF file. Each TYPS member
               opens the SMF filename, although no records are read.    
               This ancient and inefficient syntax was replaced with    
                  %UTILBLDP(OUTFILE=INSTREAM,                           
                            BUILDPDB=NO,                                
                            USERADD=7072 71 73 74 75 78,                
                            ZEROOBS=71 73 74 75 78);                    
                  %INCLUDE INSTREAM;                                    
              -But using UTILBLDP under Linux raised errors because some
               macros (%QCMPRES, %LEFT) were not found because SASAUTOS 
               is not allocated by default under Linus (CH 33.051) and  
               were unresolved.  But Change 31.209 had stated that those
               macros were replaced by SYSFUNC calls to avoid the long  
               standing problem trying to use SAS-supplied SASAUTOS     
               macros, so UTILBLDP is now free of SASAUTO macros.       
   Thanks to David F. Salsieder, American Family Insurance, USA.        
                                                                        
Change 33.055  Support for CICS User Field USER/MEBTRAN in CICSTRAN.    
IMACICVK                                                                
UTILEXCL                                                                
VMAC110                                                                 
Mar  8, 2015                                                            
   Thanks to Jeff Fracas, WiPro, USA.                                   
                                                                        
Change 33.054  Reserved Change Number.                                  
                                                                        
Change 33.053 -Support for z13 updates to type 99 subtype 14, STRONGLY  
VMAC99         RECOMMENDED by IBM to be enabled for PROCVIEW CORE to    
Mar  8, 2015   allow you to see which LPARs end up where.               
               Variables were added to both TYPE99EM and TYPE99EP.      
                                                                        
Change 33.052  z13 Support updates.                                     
VMAC113       -With PROCVIEW CORE, SMF 113 was INCOMPATIBLY changed to  
ASUM113        add COREID etc to support SMT, with changes to MANY of   
Mar 14, 2015   the calculated variables that were not in Change 33.023. 
Apr 10, 2015  -The SPEED value for the zIIP can incorrectly be zero but 
               MXG sets SM1132SP=5 for the z13 to circumvent the known  
               occasional incorrect value.                              
              -With PROCVIEW CPU, non-SMT mode, RNI was incorrect, with 
               a negative value, that was also corrected by this change.
              -Apr 10: zEC12 RNI 1st factor changed from 2.2 to 2.3.    
                                                                        
Change 33.051  MXG initialization revised so the FILENAME SASAUTOS isn't
VMXGINIT       listed in the list of input source libraries, as Linux by
Mar  3, 2015   default does not have a SASAUTOS filename allocated.     
                                                                        
Change 33.050  Graphics code had a not sorted condition caused by the   
ANALHSM        order of the variables in the BY list.  Protection added 
Mar  3, 2015   for all missing values in a variable, which caused ODS   
               graphics to print warning and suppressed changes in the  
               tick value formats by using XAXIS YAXIS code.            
   Thanks to Lindsay Oxenham, IBM, AUSTRALIA.                           
                                                                        
Change 33.049  Three new UTILEXCL reports may be printed. REPORT 00 will
UTILEXCL       print all dictionary records read in today from SMF.     
Mar  2, 2015   REPORT 00 prints any Transaction Records that do NOT have
               a dictionary record, and REPORT 000 shows each of the    
               APPLIDs that did not have a dictionary record.  Both 00  
               and 000 reports show the SYSTEM and READTIME of those    
               Transaction Records, since THAT is when the dictionary   
               record was written, so you know which day's SMF to read  
               to find those missing dictionary triplet records.        
   Thanks to Scott Barry, SBBWorks, Inc., USA.                          
                                                                        
Change 33.048 -When a GETDSAB error occurred the Reason Code was        
ADOCRMFV       displayed as NNNN in severe error message RMFV007S.      
ASMRMFV        The Reason Code is only valid if the Return Code is      
Feb 27, 2015   12.  In all other cases the Reason Code for this         
               situation will display as blanks.                        
              -Update documentation for message RMFV007S.               
              -REQUIREMENT: In order to implement these features the    
               ASMRMFV utility program from this MXG change must be     
               installed.  See MXG SOURCLIB member JCLASM3 for sample   
               JCL for the assembly and link-edit install steps.        
           Thanks to Wayne Bell, UniGroup, Inc.                         
                                                                        
====== Changes thru 33.047 were in MXG 33.02 dated Feb 27, 2015=========
                                                                        
Change 33.047 -UTILEXCL updated to skip the CICS/TS 3.2 OMEGAMON CMRDATA
IMACICM0       segment when it is the incorrect length of 200 bytes.    
UTILEXCL       Change 28.027 discusses, but only told you to install the
Feb 27, 2015   correction; this change circumvents by telling you to use
               the IMACICM0 (instead of the normal IMACICMR) to skip.   
   Thanks to Donald Blaszka, Wipro, USA.                                
   Thanks to Jeff Fracas, Wipro, USA.                                   
                                                                        
Change 33.046  New variables in TYPE70 for z13 MULTITHREADING:          
FORMATS                                                                 
VMAC23     MXG 33.01 CHANGES noted one z13 site had NEGATIVE CPUOVHTM,  
VMAC26J2   but that was ONLY IF z/OS on z13 is in MULTI-THREADING MODE. 
VMAC26J3   MXG was unaware of IBM's restructuring the RMF type 70 SMF   
VMAC7072   record's calculation of CPU BUSY time for the new MT mode,   
VMAC71     but this MAJOR CHANGE restructured TYPE70 processing in MXG  
VMAC75     to order by CORE_ID and CPU_NUM rather than CPUID/LCPUADDR.  
Feb 26, 2015                                                            
           If NOT Multi-Threading, new metrics were COMPATIBLY ADDED.   
Mar 21, 2015                                                            
           Specifically, if z/OS is IPL'd with LOADxx PROCVIEW CORE, on 
           a processor that is SMT capable, then whether or not MT is   
           Active, and even if MT=1 is specified, then the RMF 70 record
           is restructured with CORE_ID.  While this change in MXG 33.02
           updated the TYPE70 dataset, MXG 33.03 is REQUIRED now for the
           complete support for the TYPE70PR changes as well.           
                                                                        
                 SMF70MCF ='MULTITHREADING*MAXIMUM*CAPACITY*GP'         
                 SMF70MCFS='MULTITHREADING*MAXIMUM*CAPACITY*ZIIP'       
                 SMF70MCFI='MULTITHREADING*MAXIMUM*CAPACITY*ZAAP'       
                 SMF70CF  ='MULTITHREADING*CAPACITY*GP'                 
                 SMF70CFS ='MULTITHREADING*CAPACITY*ZIIP'               
                 SMF70CFI ='MULTITHREADING*CAPACITY*ZAAP'               
                 SMF70ATD ='AVERAGE*THREAD*DENSITY*GP'                  
                 SMF70ATDS='AVERAGE*THREAD*DENSITY*ZIIP'                
                 SMF70ATDI='AVERAGE*THREAD*DENSITY*ZAAP'                
               New variables in TYPE70PR                                
                 SMF70MTID='MAXIMUM*THREAD*IDENTIFICATION'              
                 SMF70MTTT='MULTI*THREADING*IDLE*TIME'                  
                 Variables SMF70CAN/SMF70CTN are now correctly missing  
                 values for an LPAR with no engines (LCPUADDR=. also).  
                 These variables were previously incorrectly populated. 
                 The order of these offline LPARS may be different now. 
               New variables in TYPE71                                  
                 SMF71MCF='MULTITHREADING*MAXIMUM*CAPACITY'             
                 And several PIB4 variables are now INPUT as RB8.       
               TYPE75 SMF75AVL now input as floating point.             
               New variables in TYPE799 dataset:                        
                 R799CUQ ='CU*QUEING*TIME'                              
                 R799CN2 ='DEVICE*FLAG*ESTENSION*2'                     
                 R799CSC ='SUBCHANNEL*SET*IE'                           
               New variables in TYPE89 dataset:                         
                 SMF89CR ='0=CP CREDITS*1=IB CREDITS'                   
               New variables in TYPE9005 dataset:                       
                 SMF90ESWT='SWT*VALUE'                                  
                 SMF90ETWT='TWT*VALUE'                                  
               New variables in TYPE23 dataset:                         
                 SMF23BBC='ZEDC*UNCOMPRESSEDSED*BYTES*TOTAL'            
                 SMF23BAC='ZEDC*COMPRESSED*BYTES*TOTAL'                 
               New variable in TYPE26J2 and TYPE26J3                    
                 SMF26JCR='JOB*CORRELATOR'                              
               In multi-threading mode, the TYPE70PR data is changed    
               from a one-to-one mapping of CPUID and LCPUADDR to the   
               CORE_ID, and a core can have 2 CPUs. The CPUID value from
               the CPU Data Section is used to select the suffix for    
               those datasets that have a unique set of variable names  
               for each LPAR (TYPE70,ASUM70PR,ASUMCEC).                 
                                                                        
Change 33.045  The SMF 110 ST 1 record descriptions in the ANALID report
VMACID         incorrectly stored 110.001 in variable IDANDSUB instead  
VMACSMF        of values 110.101-110.106, so only '110.001' was printed 
Feb 23, 2015   instead of these possible descriptions;                  
                  110.1.1:CICS DICTIONARY MNSEGCL=1                     
                  110.1.3:CICS TRANSACTION MNSEGCL=3                    
                  110.1.4:CICS EXCEPTION MNSEGCL=4                      
                  110.1.5:CICS RESOURCE MNSEGCL=5                       
                  110.1.6:CICS IDENTITY MNSEGCL=6                       
               While this is only a cosmetic error, these are important 
               enough that I refreshed 33.01 to add this change.        
   Thanks to Andre G Amoretto, IBM Global Services, BRAZIL.             
                                                                        
                                                                        
====== Changes thru 33.044 were in MXG 33.01 dated Feb 20, 2015=========
                                                                        
Change 33.044  See Change 33.155.  These data are now in TYPE74ST.      
VMAC74         Corrections for TYPE74MO SCM Structure dataset. The test 
Feb 19, 2015   for length had incorrect syntax, but fortunately did not 
               cause a false positive.  There was a missing */ in the   
               INPUT that misaligned data.   Also, it appears, from this
               note 2 on page 366 of z/OS V2R1.0 RMF Report Analysis    
               that TYPE74MO can have zero observations because:        
               "SCM statistics are only included in the SCM Structure   
                Summary for those structures that make use of the SCM   
                storage extension and have set a non-zero maximum SCM   
                size. If none of the structures is configured to exploit
                SCM, the SCM Structure Summary displays message: No     
                storage class memory data available."                   
   Thanks to Otto Burgess, ATPCO, USA.                                  
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.043  DATASET VXUSEACT/VXUSEINT NOT SORTED ERROR because the BY
VMACVMXA       lists for the MERGE were not identical.                  
Feb 19, 2015                                                            
   Thanks to Chris Weston, SAS Institute, USA.                          
                                                                        
Change 33.042  Using INCLAFTR=BUIL3005 for JES3 failed with PDB.TYPE25 ,
UTILBLDP       not found because UTILBLDP incorrectly blanked _STY25.   
Feb 19, 2015                                                            
   Thanks to Paul Volpi, UHC, USA.                                      
                                                                        
Change 33.041  SMFSRCH did not read the SMFOUT file of selected records,
FORMATS        due to an undocumented change in VMXGINIT that replaced  
SMFSRCH        &SMF with SMF, preventing changing the input DDNAME and  
VMXGINIT       causing the full input SMF file to be read by TYPESMF,   
Feb 18, 2015   287 times!  TYPESMF is replaced by a tailored UTILBLDP   
Feb 23, 2015   invocation that only processes the selected record types,
Feb 24, 2015   and in only one step.  And a PROC FORMAT that could fail 
               with overlapped values was replaced in the new design.   
               The selected record types are reported, and if you have  
               user SMF records selected, you will need to use USERADDS 
                %SMFSRCH(USERADDS=xxxx/nnn yyyy/mmm) to tell MXG which  
               xxxx product has which nnn SMF record type.              
              -Format MGSMFPR maps SMF Record Type to Product Suffix for
               the UTILBLDP USERADD= argument.                          
              -Feb 23: Harmless APPARENT UNRESOLVED ADDIDS if no records
               were selected corrected.                                 
              -If SMFSRCH failed to find your text in SMF, it generated 
               a call to UTILBLDP with BUILDPDB=NO and USERADD= to null 
               which caused UTILBLDP to fail with MACRO variables not   
               found.  Now if no records are found, it terminates with: 
                 MXGNOTE: NO RECORDS WERE FOUND CONTAINING &LOOKFOR;    
                 MXGNOTE: SMFSRCH WILL BE TERMINATED;                   
               and if UTILBLDP has BUILDPDB=NO and USERADD=blank it will
               terminate with:                                          
                 MXGERROR: YOU SPECIFIED BUILDPDB=NO BUT DID NOT;       
                 MXGERROR: SPECIFY A USERADD= SO UTILBLDP DOES;         
                 MXGERROR: NOT HAVE ANYTHING TO DO AND WILL SET;        
                 MXGERROR: THE OUTFILE TO A NULL DATASET;               
               and since the OUTFILE is NULL a following include of that
               file will not fail since it is empty.                    
                                                                        
Change 33.040  Support for SystemWare XPTR 5.2 subtype 140 record which 
VMACXPTR       now contains what used to be in their subtype 40 record. 
Feb 18, 2015                                                            
   Thanks to Phil Grasser, Norfolk Southern, USA.                       
                                                                        
                                                                        
Change 33.039  Summarization of Mobile Work CSV files to combine hours  
MOBWRKSU       that were split between two CSV files.  All files from a 
Feb 19, 2015   family are concatenated to the //CSVINPUT DD and the     
               summarized CSV data is written to //CSVSUMRY DD.         
              -CSVSUMRY was originally DISP=MOD, to collect the input   
               from four sources, but DISP=MOD can not be used for a    
               PDSE member, so the MOD file is written to an internal   
               catalog file, which is then copied to //CSVSUMRY.        
                                                                        
Change 33.038  Change 30.082 added protection for SMF type 60 record    
VMAC60         with no VVR segment, but the protection was insufficient,
Feb 17, 2015   and an INPUT STATEMENT RECORD EXCEEDED error could still 
               occur.  Now, the remaining length is verified.           
   Thanks to Tabbitha Flink, FirstData, USA.                            
                                                                        
Change 33.037  Support for HP MeasureWare for Linux.                    
ADOCMWLX      -ADOCMWLX has the REPORT command to extract the fields MXG
EXMWLXAP       expects, so it must be used to create MXG's input data.  
EXMWLXCO      -CPU Times in the MWLXGLOB dataset are presumed to be the 
EXMWLXDS       per-CPU values in the record; they have been multiplied  
EXMWLXGL       by the number of CPUs.  Other times are as found.        
EXMWLXLA      -ALL STORAGE variables contain BYTES and are formatted    
EXMWLXPR       with MGBYTES for total bytes and MGBYTRT for byte rates. 
EXMWLXTT       Fields in the record in KB have been converted to bytes. 
IHDRMWLX      -IHDRMWLX or &MACMWLH can be used to select which TYPE    
IMACMWLX       records are to be read.                                  
TYPEMWLX                                                                
TYPSMWLX                                                                
VMACMWLX                                                                
VMXGINIT                                                                
Feb 13, 2015                                                            
Feb 20, 2015                                                            
   Thanks to Roman Gudz, Penske, USA.                                   
                                                                        
Change 33.036 -RACF SMF 80 record, SMF80TP2=301, Command Segment Data   
VMAC80A        segments "CTOKENKY" and "CTOKENTM" are supported.        
Feb 12, 2015  -The variable length TOKxxxxx fields do not document their
               max length, and MXG can get INPUT RECORD EXCEEDED errors 
               if an input field is longer than the defined length in   
               its $VARYINGnn informat. These variables are increased to
               $VARYING64 to hopefully avoid the error condition:       
                TOKCOMPANY  TOKCOUNTRY  TOKFNAME    TOKMNAME    TOKLNAME
                TOKMCARRIER TOKMCANSWR1 TOKMCANSWR2 TOKMCANSWR3         
                TOKMCBADCNT                                             
   Thanks to Phil Grasser, Norfolk Southern, USA.                       
                                                                        
Change 33.035  RACF SMF 80 record, SMF80TP2=301, Command Segment Data   
VMAC80A        segment "AUTOGID" decodes 4 variables but their contents 
Feb 11, 2015   is not known at this time:                               
                 TOKMAUTOGID01 TOKMAUTOGID02 TOKMAUTOGID03              
                 TOKMAUTOGID04                                          
   Thanks to Harald Seifert, HUK-COBURG, GERMANY.                       
                                                                        
Change 33.034  The variables SYSABEND and USRABEND were created but not 
VMACIMS        decoded in the IMS56FA transaction dataset. Now, COMPCODE
Feb 10, 2015   is decoded into these two useful IMS transaction abend   
               code variables in all record that contain it.            
   Thanks to Raymond J. Smith, OPTUM, USA.                              
                                                                        
Change 33.033  WPS 3.1.1 maint level 731 will now write multiple output 
WEEKBLD        datasets to sequential format data libraries without the 
Feb 10, 2015   need to use DISP=MOD.  Without MOD and 731, each write   
               overwrote the prior, leaving only the last dataset.      
                                                                        
Change 33.032 -Variables SMF70WTI/SMF70WTS/SMF70WTU (new WTI-s) were ok 
VMAC7072       in dataset TYPE70EN, but were always zero in TYPE70PR.   
VMXG70PR       TYPE70PR is now corrected, but those values only exist   
Feb  8, 2015   in the "THIS PART" TYPE70 records, so you must read ALL  
               system's TYPE70s to properly populate these variables.   
               They are always missing in the LPARNAME='PHYSICAL's      
              -VMXG70PR is updated so the PDB.ASUM70LP and PDB.ASUMCELP 
               LPAR Summary datasets contain those variables, but only  
               if RMF type 70 records from ALL systems are input.       
                                                                        
Change 33.031  Using BLDSMPDB and FORCEDAY to re-run a daily job could  
BLDSMPDB       incorrectly calculate the start of week, depending on the
VMXGALOC       case of your typed code.  Now when you specify FORCEDAY  
Feb 19, 2015   to rerun SMF data, ZDATE will be set to FORCEDAY+1.      
Feb 26, 2015   Error was introduced in MXG 32.11, Change 32.253.        
               And all of the tests where casing can impact are now     
               now protected with %UPCASE compiler functions, but the   
               members remain lower case because of earlier problem in  
               casing in Linux systems; it might not still be required, 
               but not worth the exposure and time spent for no value.  
                                                                        
Change 33.030  Mainview for MQ 5.2 support is corrected; the wrong byte 
VMACBBMQ       was used to detect compressed records, causing spurious  
Feb  5, 2015   messages that individual records were compressed.        
   Thanks to Greg Tuben, BMC Software, Inc., USA.                       
                                                                        
Change 33.029  The iSeries a/k/a AS400 QAPM "suffix" was replaced by the
TYPEQACS       "QACS" suffix years ago, but those old QAPM members are  
Feb  4, 2015   now removed; they were causing false positives in the MXG
               QA tests, and served no purpose.  All of the xxxxQAPM are
               deleted, and these exit members that weren't carried into
               the QACS product were also deleted.                      
                   dddddd     exit         dddddd     exit              
                   token      member       token      member            
                  _WQAPASY    EXQAPASY    _WQAPPOO    EXQAPPOO          
                  _WQAPBSC    EXQAPBSC    _WQAPRWS    EXQAPRWS          
                  _WQAPDDI    EXQAPDDI    _WQAPSTD    EXQAPSTD          
                  _WQAPECL    EXQAPECL    _WQAPSTL    EXQAPSTL          
                  _WQAPFRL    EXQAPFRL    _WQAPSTY    EXQAPSTY          
                  _WQAPIDL    EXQAPIDL    _WQAPX25    EXQAPX25          
                  _WQAPJOB    EXQAPJOB                                  
                  _WQAPLAP    EXQAPLAP                                  
               While the SUFFIX QAPM is retired, the names of all of the
               datasets created by TYPEQACS are unchanged and all start 
               with QAPMxxxx.                                           
                                                                        
Change 33.028  Support for EDS User SMF Record from NETMENU Program,    
COMPALL        creates new dataset:                                     
EXTYNTMU          DDDDDD   DATASET   DESCRIPTION                        
FORMATS           TYNTMU   NETMENU   SMF NETMENU RECORD DATABASE        
IMACNTMU                                                                
TYPENTMU                                                                
TYPSNTMU                                                                
VMACNTMU                                                                
VMXGINIT                                                                
Feb  3, 2015                                                            
   Thanks to Joe Babcock, General Motors, USA.                          
                                                                        
Change 33.027  Example from SAS Help to delete all GLOBAL'ed USER MACRO 
VMXGDELV       Variables, used only in the QA JOB when new code caused  
Feb  3, 2015   an unexplained error (the "TURN SPOOL ON" message) in    
               Step 34, but there was no error when Step 34 ran first.  
               By clearing all Global Macros before Step 34, the actual 
               unresolved macro variable error was then unmasked, but   
               maybe only accidentally!  To clear and re-initialize     
                 %VMXGDELV;%INCLUDE SOURCLIB(VMXGINIT);%VMXGINIT;       
               is needed so that the GLOBAL statement in VMXGINIT is    
               re-executed.  And because %VMXGDELV cleared the flag     
               variable MXGINIT, %VMXGINIT prints the Welcome To MXG    
               message, instead of the the re-initialization message.   
                                                                        
Change 33.026  Reserved Change Number.                                  
                                                                        
Change 33.025 -Variable QBSTBPIN='BUFFER*POOL*IO*INTENSITY' based on IBM
ANALDB2R       Tivoli calculation is added to DB2STATB dataset and also 
VMACDB2        ANALDB2R reports the value.                              
VMXGDBSS         QBSTBPIN=SUM(QBSTRIO,QBSTSPP,QBSTLPP,QBSTDPP,QBSTIMW,  
Feb  3, 2015                  QBSTWIO)/QBSTVPL;                         
Feb 26, 2015  -ASUMDBSB now reports both average and maximum QBSTBPIN.  
              -Debugging test IF SYSTEM='SYSG' removed from DB2B1 Buffer
               Pool Statistics reports                                  
              -Feb 26: Protected QBSTBPIN from divide by zero error when
               QBSTVPL=0 when no buffers were allocated in the pool.    
   Thanks to Tim Hare, Hare Systems Support, USA.                       
   Thanks to Jonathan Bathmaker, Southern California Electric, USA.     
   Thanks to Tom Buie, Southern California Electric, USA.               
                                                                        
Change 33.024  Test added to detect ANY work in service class SYSOTHER. 
UTILRMFI       The UTILRMFI utility is cited in error messages that your
UTILWORK       CPUTM does not match CPU72TM when building RMFINTRV: run 
VMXGRMFI       UTILRMFI to examine your VMXGRMFI workload definitions to
Feb  3, 2015   find what work was overlooked.  However, if there is any 
               work in the SYSOTHER Service Class (which itself is an   
               error in your site's WLM Classification Rules), that may 
               cause the mismatch, since that work probably also doesn't
               have a Reporting Class.  Now you are alerted of the WLM  
               definition error.  Note that SYSOTHER is also undesired  
               because that work is MTTW DISCRETIONARY, so whatever is  
               falling thru is NOT going to get much service.           
                                                                        
Change 33.023  Support for new z/OS z13 hardware metrics (COMPATIBLE):  
FORMATS       -APAR OA43493 RMF Support Cryptographic Express5S cards:  
VMAC30         New Crypto Processor types in R7023CT/24CT/25CT variables
VMAC7072       decoded by $MGRMFCY/MGRMFCZ formats in datasets TYPE7002,
VMAC74         TYPE70X2, and TYPE70Y3.                                  
VMAC113        New variables in TYPE70Y2 dataset:                       
VMACVMXA        R702AMGB='DATA BYTES*FOR*GENERATE*AES MACS'             
Jan 29, 2015    R702AMGC='CALLS TO*GENERATE*AES MACS'                   
ASUM113         R702AMGI='INSTRUCTIONS*TO GENERATE*AES MACS'            
Feb 25, 2015    R702AMVB='DATA BYTES*FOR*VERIFIED*AES MACS'             
May 21, 2015    R702AMVC='CALLS TO*VERIFY*AES MACS'                     
                R702AMVI='INSTRUCTIONS*TO VERIFY*AES MACS'              
                R702DEGC='CALLS*TO GENERATE*ECC*SIGNATURES'             
                R702DEVC='CALLS*TO VERIFY*ECC*SIGNATURES'               
                R702DRGC='CALLS*TO*GENERATE*RSA*SIGNATURES'             
                R702DRVC='CALLS TO VERIFY*RSA*SIGNATURES'               
                R702FPDB='DATA BYTES*DECIPHERED*USING FPE'              
                R702FPDC='CALLS TO*DECIPHER*USING FPE'                  
                R702FPDI='INSTRUCTIONS*TO DECIPHER*USING FPE'           
                R702FPEB='DATA BYTES*ENCIPHERED*USING FPE'              
                R702FPEC='CALLS TO*ENCIPHER*USING*FPE'                  
                R702FPEI='INSTRUCTIONS*TO ENCIPHER*USING FPE'           
                R702FPTB='DATA BYTES*TRANSLATED*USING FPE'              
                R702FPTC='CALLS TO*TRANSLATE*DATA*USING FPE'            
                R702FPTI='INSTRUCTIONS*TO TRANSLATE*USING FPE'          
              -APAR OA44502 RMF Support Coupling Channel Path Type CS5: 
                Format $MG074OM updated and applied to variable R744HOPM
                in dataset TYPE74HO.                                    
              -APAR OA30563, Enhanced SMF 30 and 89 recording; metrics  
               listed in the updated APAR were added in Change 28.175.  
               The APAR adds new MAXEVENTINTRECS with zero default,     
               so the new capacity changed interval 30/89 records will  
               not be created with that zero value.                     
              -APAR OA35175, SMFPRMxx options DSPSIZMAX; the TYPE23     
               dataset updates were actually made in Change 29.177.     
              -APAR OA45985, RMF support for zHYPERWRITE in 2107 CU.    
               Adds new variable HYPERWRT='Y' to TYPE74 if requested.   
              -SMF 113 has new z13 counters and revised calculations,   
               including RNI and its component variables:               
                 RNI=2.6*(0.4*L3P+1.6*L4LP+3.5*L4RP+7.5*MEMP)/100;      
               Corrections made March 5.  However, the new counter      
               descriptions do not yet exist.                           
               Note that variables L15P L2LP L2RP are always missing    
               values on the z13.                                       
               Without this change, negative RNI values for z13 even in 
               non-SMT mode were created.                               
              -May 21: ZEDC added to the label for those eight metrics. 
                                                                        
Change 33.022  A JES3 site TERSE with UNPACK failed with DCB attributes 
DOC            //SYSPRINT DD RECFM=FBA,LRECL=133,BLKSIZE=13232, but with
Jan 28, 2015   only the message   AMA504I  RETURN CODE: 12  and no clue.
               Removal of the DCB attributes successfully untersed.     
               However, it was NOT the non-multiple of LRECL for BLKSIZE
               that was the error. A prior IDCAMS step had a //SYSPRINT 
               DD that JES3 made into a temporary DSNAME, and the same  
               DSNAME was then used in the TERSE step, but the different
               BLKSIZE caused the conflict and RETURN CODE.  That's my  
               story and I'm stikin' to it until I learn more about why 
               JES3 passed a temporary DSNAME for //SYSPRINT.  However, 
               there is NO need for DCB attributes on SYSOUT= DDnames,  
               so to avoid ANY future exposure, I've removed all DCB    
               from those DDs in all MXG examples.                      
              -All //OUTPUT DDs for PGM=FTP were removed, as //SYSPRINT 
               is used for all messages when there is no //OUTPUT DD.   
   Thanks to Tom Adams, State Farm Mutual Automobile Insurance, USA.    
                                                                        
Change 33.021 -If no Reporting Classes were defined, ASMRMFV skipped all
ADOCRMFV       RCD tables as invalid due to a faulty calculation, with a
ASMRMFV         RMFV035W **WARNING:159 RCD TABLES SKIPPED DUE TO ERRORS 
CLRMFV         and ultimately set a Return Code 16.  Should be very rare
JCLRMFV        since most sites DO define Reporting Classes.            
JCLCRMFV      -Change 32.055 did not fully resolve the RED table issue: 
JCLdRMFV        RMFV035E:1 RED TABLES SKIPPED DUE TO INVALID ID OR FLAG 
Jan 26, 2015   the Invalid Resource bit may be set for Processor entries
               in the RED table in a MINTIME interval due to normal     
               processor change events, so these are not true RED table 
               errors and ASMRMFV was incorrectly issuing an RMFV035W   
               warning message and Return Code 16 for this transient and
               insignificant return code.                               
              -ASMRMFV now will NOT alter the Return Code, issuing a    
               distinct RMFV035I information message for this condition 
               regardless of the setting of the TABERR= option:         
                 RMFV035I -IGNORED-:  nnnnn RED TABLES SKIPPED DUE TO   
                 INVALID PROCESSOR RESOURCE FLAG---                     
              -After Change 32.289 the number of Policy Indexes Used    
               in informational message RMFV028I as triggered by the    
               INDEXES option could be incorrect.                       
              -The MXG table was shown in the Detail Report with the    
               NOSHOWZERO option in effect even when zero records were  
               output.  This table is only output once for the first    
               RMF III data set processed.                              
              -The RMFV006I FILTER message for ASI, DVT, and CFI table  
               specific options is now always shown even if none of     
               these tables are selected for a minor performance gain,  
               as selection logic for what to display was revised.      
              -Unnecessary checks for I/O errors on the SYSPRINT file   
               are removed.  An ABEND occurs with any I/O error on this 
               file so the additional checks were unneeded.             
              -Updates for revised messages RMFV006I and RMFV035I are   
               made to Section 12 "Messages" in ASMRMFV and ADOCRMFV    
               documentation members.                                   
              -REQUIREMENT: In order to implement these features the    
               ASMRMFV utility program from this MXG change must be     
               installed.  See MXG SOURCLIB member JCLASM3 for sample   
               JCL for the assembly and link-edit install steps.        
   Thanks To John Wynn, IBM Global Technology Services, USA.            
                                                                        
Change 33.020  AS/400 iSeries fixed-length records change lengths with a
VMACQACS       new version, so you may have to change the LRECL in your 
Feb  2, 2015   FILENAME statement on ASCII or in your JCL on z/OS.      
               The length change is usually detected with MXG messages  
               on the log with "PAD RECORD FOUND AND DELETED".          
               Now, you can specify %LET MXGABND=NNNN; in //SYSIN to    
               force USER ABEND NNNN if more than 10 PAD records        
               are found.  Use 0001 thru 4096 for the NNNN value.       
               New messages identify the filename and dsname being read.
   Thanks to Raymond J. Smith, OPTUM, USA.                              
                                                                        
Change 33.019  Variables TOKQUEST1-TOKQUEST3, TOKCANSWR1-TOKCANSWR3 and 
VMAC80A        CBADCNT are added to dataset TYPE80TK.                   
Jan 21, 2015                                                            
   Thanks to Phil Grasser, Norfolk Southern, USA.                       
                                                                        
Change 33.018 -RACF TYPE8025 Record with DTP=30 segment with 'C0'X value
VMAC80A        for the status ('80'x=ACTIVE,'40'x=BACKUP) caused ERROR: 
Jan 21, 2015   INVALID RACF ID=80 RACFTYPE=30 SEGMENT SKIPPED, because I
Feb  5, 2015   didn't realize a DSNAME could be both ACTIVE and its own 
Feb 23, 2015   BACKUP, so I had created two sets of variable names, with
               RACFDBxx for the ACTIVE segment and RACFDKxx for BACKUP. 
               Test for '80'x first, now stores into RACFDBxx variables,
               or '40'x or 'C0'x store into RACFDKxx variable names.    
              -For BACKUP-ONLY ('40'x) segments, both UNIT NAME/VOLSER  
               are not populated, while both are in the ('C0'X) record. 
              -Feb 23: TOKMPROCUSERMAX variable decoded.                
               See Change 33.084.                                       
   Thanks to Karl Lasecki, American Chemical Society, USA.              
                                                                        
Change 33.017  Documentation only!  Example added that sends all of the 
UTILBLDP       DB2ACCTx datasets to a single //DB2ACCT LIBNAME, and uses
Jan 21, 2015   MACKEEPX in UTILBLDP to control dataset destinations and 
               sorts and could also be used to limit variables.  The    
               DB2KEEP= parameter in BLDSMPDB is used to tailor the     
               number of generations retained to control the storage    
               needed for these normally-large datasets (ASCII only with
               AUTOALOC=YES).                                           
                                                                        
Change 33.016  Support for z/VM 6.3 on z13 processor (INCOMPATIBLE).    
VMACVMXA      -The PRCMFC 5.13 record's new CSVN=4 hardware counters    
Jan 20, 2015   caused MXG code to fail with "BROKEN CONTROL RECORD".    
               Circumvented by skipping the extra 24 bytes, await       
               the actual documentation of those new counters before    
               decoding.                                                
               IN PROGRESS.                                             
                                                                        
Change 33.015  DCOLLECT variable DCDCREAT-DATETIME*WHEN*DATASET*CREATED 
VMACDCOL       is added to dataset DCOLDSET; the time part wasn't in the
Jan 20, 2015   original record, but was added by APAR OA30006 in 2009.  
               DCDCREAT is only populated if both DCDCREDT and DCDTIMEC 
               are non-zero.                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.014  Support for z/13 processor increase to 85 LPARs was added
VMAC7072       in MXG 32.06, Change 32.162, July, 2014, changing the    
Jul 27, 2015   statement to ARRAY S70LPCP {86}  _TEMPORARY_; to  support
Jan 19, 2015   85 "real" LPARs plus the PHYSICAL "LPAR".  Support for   
               255 engines was added silently in MXG 31.04 in 2013.     
                                                                        
Change 33.013  Support for CTG Version 9.1 (COMPATIBLE).                
EX111WS       -Variable added to CTGSE System Environment dataset:      
EX111WSX         CTGC31MAX='LIMIT OF*USED*MEMORY*ELOAL'                 
IMAC111       -Two new segments, WS and WSX create new datasets:        
VMAC111           DDDDDD   DATASET   DESCRIPTION                        
VMXGINIT          111WS    TY111WS   WEB SERVICE ALL                    
Jan 20, 2015      111WSX   TY111WSX  WEB SERVICE INSTANCE               
   Thanks to David Marone, SGS, ITALY.                                  
                                                                        
Change 33.012  Unused Change Number.                                    
                                                                        
Change 33.011 -INPUT STATEMENT EXCEEDED, DFSORT SMF 16, OFFSTAT=640 and 
VMAC16         LENSTAT=64, but record is TRUNCATED with LENGTH only 636,
Jan 14, 2015   so there is no STAT segment in the record.               
               A PUTLOG ERROR message is written for the first three    
               instances, the TYPE116 dataset is output, but variables  
               RECIND01-RECIND16 will be missing values.  This text will
               be revised when an APAR exists.  DFSORT Release 2.01.    
              -These variables added in DFSORT 2.01, but not listed in  
               the manual's changes, nor marked as new with the expected
               vertical bars, are now added to dataset TYPE16:          
                 ICEDYINC='INITIAL*INCREMENT'                           
                 ICEDYMAX='FINAL*EXPMAX*DYNAMIC*VALUE'                  
                 ICEDYOLD='FINAL*EXPOLD*DYNAMIC*VALUE'                  
                 ICEDYRES='FINAL*EXPRES*DYNAMIC*VALUE'                  
                 ICETUNE ='TUNE*VALUE*IN*EFFECT'                        
   Thanks to Kerry Sommers, John Deere, USA.                            
                                                                        
Change 33.010  No errors have been reported, but ARRAY WORDS statements 
VMAC112        raised conflicts if TYPE112/TYPEEZAM/TYPETMNT are read   
VMACEZSM       together; only one ARRAY NAME can be used in a DATA step.
VMACTMNT       These are temporary arrays for parsing with different    
Jan 12, 2015   dimensions and variable lengths, so the ARRAY NAMEs are  
               made unique to eliminate the exposure.                   
                                                                        
Change 33.009  IBM Updates to SMF 14/15 for zEDC Compression Indicator  
FORMATS        SMF30XF1 adds values and is now decoded by $MG014ED:     
VMAC1415         '0'='0:SIZE VALUES INVALID'                            
Jan 12, 2015     '1'='1:COMPRESSION REJECTED'                           
                 '2'='2:ZEDC WRITTEN UNCOMPRESSED'                      
                 '3'='3:ZEDC SOFTWARE DECOMPRESSED'                     
               and new SMF14CMPTYPE='Compression Type' variable is      
               added and decoded by MG014CT format:                     
                  0='0:NOT COMPRESSED/UNKNOWN'                          
                  1='1:GENERIC'                                         
                  2='2:TAILORED'                                        
                  3='3:ZEDC'                                            
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.008  ONLYCIDS example creates ONLY the PDB.CICDS Dispatcher   
ONLYCIDS       Statistics dataset, that contains interval CPU time for  
Jan 12, 2015   each CICS Interval, and can be used for CPU Time Metric  
               in IBM Mobile Work Discount                              
   Thanks to Scottie Long, Navy Federal Credit Union, USA.              
                                                                        
Change 33.007  TYPERMF incorrectly requires a //PDB DD because it was   
TYPERMF        not updated when the 2005 "SPLIT70 logic" created the    
Jan 11, 2015   TYPE70EN dataset, written to PDB by default.  Like the   
               two existing %LETS for PTY70 and PTY70PR in TYPERMF,     
               a  %LET PTY70EN=WORK; is needed so //PDB is not used.    
   Thanks to George Baranoff, Safeway, USA.                             
                                                                        
Change 33.006 -SAS Error "No MKLEs found" and "ERROR: VM 1319:" is a    
DOCUMENT       virtual storage issue, usually too small a REGION= size, 
Jan 11, 2015   but also a known SAS Version 9.2 defect, see below.      
              -The MXG QA "BUILDPDB" JOB (with a few added SMF types)   
               increased from 130MB in 31.31 to 140MB in 32.32.         
              -Each new MXG version adds new variables, datasets, and   
               code which cause the REGION size to increase a little.   
               Unfortunately, the z/OS REGION is a LIMIT not a BENEFIT, 
               so you get to periodically increase the REGION= value,   
               and/or check with your site's "REGION SIZE POLICE" to    
               find their actual limit for REGION=0M, and/or what JOB   
               CLASS/RACFUSER will let you allocate the REGION needed.  
              -There is NO ACTUAL RESOURCE "consumed" by REGION size.   
              -The actual step region size is in the IEF032I message on 
               joblog for each step:    EXT: 130,852K    SYS: 12,088K   
               EXT is the region size "Above the 16MB Line" and SYS is  
               the size of the Private Area on this system. Their sum is
               the region size allocated to this step, or               
                   130,852+12,088=142,940K=140MB REGION size.           
               -The SAS log shows "And 130852K Above the Line" matching 
                the EXT value exactly. SAS also reports a value for the 
                "Below the Line", but it is (small) amount used, not the
                actual size of the Private Area, which must be included 
                in the REGION limit.                                    
               -One site moving from an ancient MXG version still had   
                REGION=6M on their JOB Card from the prior millennium.  
                You get the system default of 32MB Above the Line plus  
                the Private Area, or about 42MB, but because their daily
                job was split into parallel pieces, it actually had     
                worked (accidentally?) until 32.32.                     
              -SAS needs REGION size for referenced FORMATS, for dataset
               buffers, for arrays, for SAS VIEWs, and for the CICSIFUE 
               SMFEXIT=CICS INFILE exit to load.                        
              -SAS Version 9.2 is Class C support from SAS and it had   
               fatal errors in virtual storage on z/OS that were ONLY   
               corrected by SAS 9.3 or 9.4.                             
              -One 9.2 site's tailored BUILDPDB ran in 130MB with 30.01,
               needed 159MB with 32.32, but when the CICSIFUE exit was  
               enabled, the job failed and IEF032I reported only 97MB   
               had been allocated.  Rerun with 32.32 and SAS 9.4 and    
               WITH the exit needed 179 MB, and ran with no error.      
              -MXG 33.03 QA BUILDPDB on z/OS 2.1, SAS 9.4(TS1M2) needed:
                142M with View Disabled and no CICS EXIT Enabled.       
                147M with the View Enabled (default), and no Exit.      
                149M with both the VIEW (ID, for ANALID) and with EXIT. 
                                                                        
     Copied from NEWSLTRS:                                              
                                                                        
     SAS USER U1319 ABEND if EXITCICS/CICSIFUE and /VIEW=_WCICTRN used, 
     or with BUILDPDB, if back level SAS 9.1.3 SP4 without Hot Fix 37166
     is used.  SAS Error is corrected in SAS 9.2.                       
                                                                        
     Using a VIEW for CICSTRAN with the CICSIFUE decompression INFILE   
     user exit caused a USER ABEND U1319 error, that is now corrected in
     the SAS HotFix for SAS Note 37166.                                 
     This SYSIN input caused the U1319 abend :                          
        %LET SMFEXIT=CICS;                                              
        %INCLUDE SOURCLIB(VMACSMF,VMAC110,VMXGUOW,IMACKEEP);            
        DATA                                                            
        _VAR110                                                         
          /VIEW=_WCICTRN;                                               
        _SMF                                                            
        _CDE110                                                         
        _S110                                                           
     with these cryptic messages on the SAS log:                        
        +No MKLEs found                                                 
        +ERROR: VM 1319: The PCE address= 1848CB54                      
                         and MEMORY address=000D98D8                    
        IEA995I SYMPTOM DUMP OUTPUT  749                                
        USER COMPLETION CODE=1319                                       
     Removing /VIEW=_WCICTRN, the execution works fine with the Exit.   
     Also using TYPS110 worked fine (because it doesn't have a /VIEW).  
                                                                        
     But the same error message will occur with BUILDPDB due to the view
     for VMACID.  This error can be circumvented by inserting this      
     statement in your //SYSIN                                          
         %LET VWVMACID=;                                                
     which disables that sole VIEW in the BUILDPDB.                     
                                                                        
     Change 27.260 is a VERY-EXPENSIVE-ON-Z/OS-alternative to EXITCICS. 
                                                                        
   Thanks to Jerry Massey, Compuware, USA.                              
   Thanks to Dave Greene, Compuware, USA.                               
                                                                        
Change 33.005  Support for APAR OA45767 adds compression statistics for 
VMAC30         the zEDC compression engines to the TYPE30_4,_5,_V,_6,   
BUILD005       PDB.STEPS and PDB.SMFINTRV datasets, and these variables 
BUIL3005       (plus the _INST_ variables added by Change 31.153) are   
Jan  9, 2015   now also summed into the PDB.JOBS dataset.               
                SMF30_US_COMPRREQ       SMF30_US_COMPRREQ_PROB          
                SMF30_US_DEF_COMPROUT   SMF30_US_DEF_UNCOMPRIN          
                SMF30_US_EXECTIME       SMF30_US_INF_COMPRIN            
                SMF30_US_INF_DECOMPROUT SMF30_US_QUEUETIME              
   Thanks to Scott Barry, SBBWorks Inc., USA.                           
                                                                        
Change 33.004 -(Archaic) SAS V9.1.3 JCLTES91 messages with MXG 32.32.   
JCLTES91       Running the JCLTES91 with SAS V9.1.3 & MXG 32.32:        
VMACIDMJ       -VMACIDMJ contains FORMAT RECDATE DATE11.; which is not  
Jan  9, 2015    supported in SAS V9.1.3; if you use VMACIDMJ (unlikely!)
                change to DATE9.                                        
               -JCLTES91 TESTOTHR step needed //IMSMERGE DD DUMMY after 
                the existing //IMSLOG DD DUMMY.  Added.                 
   Thanks to Lee Lewis, SPVM Quebec, CANADA.                            
                                                                        
Change 33.003  Support for user CICS USERMOB and USEREOT segments.      
IMACAAAA       -UTILEXCL was updated for these two user fields.         
IMACICVI       -Testing exposed that the MXG "EXCLUDED FIELDS" detection
IMACICVJ        in TYPE110 does NOT work if there are optional segments 
PRODTEST        that INCREASE the MCTSSDRL, since MXG can only detect if
UTILEXCL        MCTSSDCN/MCTSSDRL are SMALLER than the default size for 
VMAC110         that SMFPSRVR.  UTILEXCL is now updated to not only read
Jan  8, 2015    the Dictionary records, but also any CICSTRAN records to
Jan 15, 2015    produce two new reports of any APPLID/TRIPLETs that are 
Jan 19, 2015    found in transactions but don't have Dictionary records.
               -For completeness, there are two additional tests in the 
                TYPE110 processing that can detect excluded fields:     
                 a. TASKNR is a Packed Decimal, and that will be a      
                    missing value if the INPUT is mis-aligned.          
                    Unfortunately, TASKNR is near the front of the      
                    record, and most Excludes are newer fields further  
                    into the record.                                    
                 b. A test for CPUTM GT 10*ELAPSTM, because CPU fields  
                    are further into the record.  See Change 29.076 why 
                    the factor of 10 is needed (for knee-capped CPs).   
   Thanks to Rob Hollingum, HSBC, ENGLAND.                              
                                                                        
Change 33.002  z/OS 2.1 overlooked variables are added in TYPE74OM.     
VMAC74           OMVSCLMN='MIN SHARED*STORAGE MB*ALLOCATED PER CYCLE'   
Jan  8, 2015     OMVSCLMX='MAX SHARED*STORAGE MB*ALLOCATED PER CYCLE'   
                 OMVSCSLR='ACCUM SHARED*STORAGE*ALLOCATED*INTERVAL'     
                 OMVSMQDS='MAX*QUEUED SIGNALS*ALLOWED*PER PROCESS'      
                 OMVSMSLR='MAXIMUM*STORAGE MB*AVAIL*SHAREDM'            
                 OMVSOLMN='MIN ATTEMPTS*EXCEED MAXIMUM*REGION PER CYCLE'
                 OMVSOLMX='MAX ATTEMPTS*EXCEED MAXIMUM*REGION PER CYCLE'
                 OMVSOQDS='ACCUM ATTEMPT*EXCEED MAX*QUEUED*INTERVAL'    
                 OMVSOQMN='MIN ATTEMPT*EXCEED MAX QUEUED PER CYCLE'     
                 OMVSOQMX='MAX ATTEMPT*EXCEED MAX QUEUED PER CYCLE'     
                 OMVSOSLR='ACCUM ATTEMPTS*EXCEED MAX*INTERVAL'          
   Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.                    
                                                                        
Change 33.001  Typo, variable ESTBUTES corrected to ESTBYTES.           
ANALTLMS                                                                
Jan  6, 2015                                                            
   Thanks to Pierre-Pascal Joulin, SOCGEN, FRANCE.                      
                                                                        
LASTCHANGE: Version 33.