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

MXG NEWSLETTER THIRTY-THREE

****************NEWSLETTER THIRTY-THREE*********************************
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
                                                                        
             MXG NEWSLETTER NUMBER THIRTY-THREE February 23, 1998       
                                                                        
Technical Newsletter for Users of MXG :  Merrill's Expanded Guide to CPE
                                                                        
                         TABLE OF CONTENTS                          Page
                                                                        
I.   Annual MXG Software Version 15.15 shipped with this Newsletter.   2
II.   MXG Technical Notes                                              6
 1. Measurement of CPU Utilization in PR/SM,MDF,MLPF environments.     6
 2. FAT32 file system reduces MXG space needed from 139MB to 68MB.    11
III.  MVS Technical Notes.                                            11
 1. APAR OW25609 corrects a stoppage of SMF type 30 interval recs.    11
 2. APAR OW28289 changes counts in type 30 TAPNMNTS/TAPSMNTS vars.    11
 3. APAR OW28613 corrects errors in the JES2 Type 26 Purge record.    12
 4. APAR OW28256 reports invalid CPU times in RMF CPURCTTM.           12
 5. APAR OW26619 for OS/390 V2.4, in Goal Mode corrects WLM errors.   12
 6. APAR OW26421 for OS/390 V1.3 is needed only for ASMTAPES.         12
 7. SYNCSORT 3.6 can ABEND 0C9 in a PROC SORT; SYNCSORT fix SY49930.  12
 8. APAR OW30153 corrects type 30 Measured Usage (MULC) segments.     12
 9. APAR OW30059 (PTF available 12Dec97) reports type 42 errors.      13
10. APAR PQ09396 (Target 26Dec97) for MQSERIES SMF type 116.          13
11. APAR PQ09083 for subtype '51'x of the FTP SMF record (VMACFTP).   13
12. Job Accounting for Started Tasks is available with MVS/ESA 5.1.   13
13. What happens to measurements in a Y2K Test System in an LPAR?     13
14. Almost-Duplicate TYPE74 records, differing only by one second.    14
15. Channel Type variable CHANTYPE in dataset TYPE73 still exists.    14
16. APAR OW27855 corrects PSF/MVS-written type 6 SMF records.         14
17. APAR OW20844 enables JES2 job numbers greater than 32000.         14
IV.   DB2 Technical Notes.                                            14
V.    IMS Technical Notes.                                            14
 1. Support for Boole's IMF 3.2 (for IMS 6.1) added in MXG 15.09.     14
 2. Discussion of IMS Log support in MXG Software.                    14
VI.   SAS Technical Notes.                                            15
 1. There are no MXG problems using Version 6.09 of the SAS System.   15
VII.  CICS Technical Notes.                                           15
 1. You can use USER instead of TERMINAL to bill CICS transactions.   15
VIII. Windows NT Technical Notes.                                     16
 1. Use  /B "Binary" switch on the COPY command to eliminate '3F'x.   16
IX.   Incompatibilities and Installation of MXG 15.15.                16
X.    Online Documentation of MXG Software.                           17
XI. Changes Log                                                       17
     Alphabetical list of important changes                           17
     Changes 15.382 thru 15.207                                    21-64
                                                                        
      COPYRIGHT (C) 1998 MERRILL CONSULTANTS DALLAS TEXAS USA           
                                                                        
           =====    What's Really Hot in MXG 15.15    =====             
                                                                        
   The really big features in MXG, aside from the hundreds of new       
   software product versions that are now supported, PTFs, etc,         
   are the externalization of the DDname for each PDB dataset into      
   &PDByyyy macro variables, for ease in tailoring BUILDPDB, and the    
   &MACxxxx macro variables now defined in each VMACxxxx member that    
   permit you to re-define the _L and _K macros that are defined in the 
   IMACxxxx members in your USERID.SOURCLIB; now you can change the IMAC
   tailoring library macro definitions on the fly, without an EDIT!     
   See the text of Changes 15.356 and 15.320 for full details.          
                                                                        
   Not all of the externalization of the IMACxxxx tailoring has been    
   delivered in MXG 15.15.  I am still developing _Syyyyyy SORT macros  
   for each dataset, and _Eyyyyyy exit macros to override the EXyyyyyy  
   dataset exit members, and will then replace the hardcoded PROC SORTs 
   in BUILDPDB with their corresponding _Syyyyyy macro, but that's still
   work in progress.                                                    
                                                                        
   More ADOCxxxx members exist now, but most new ones have only DOCVER's
   short contents.  However, now I can implement automatic update of new
   variables in each ADOC member, preserving other documentation in each
   member, and will expand the documentation to include the member that 
   creates each data set, sort order, etc., as time permits.            
                                                                        
   See member CHANGES in MXG 15.15 for any last minute additions after  
   the newsletter printing and the software building, or better still,  
   see the CHANGES section of our homepage, www.MXG.com, which is always
   the first place to look for MXG Software status.  While you are there
   please subscribe to the MXG-L ListServer; it is my primary method of 
   software announcements, and many fine technical discussions among MXG
   users have occurred on MXG-L (you can read them from the archives!). 
           ================================================             
                                                                        
                                                                        
                                                                        
                                                                        
I.   Annual MXG Software Version 15.15 was shipped to all sites,        
     along with the printed copy of MXG Newsletter THIRTY-THREE,        
     during the last week of February, 1998, by US Air Mail.            
                                                                        
 1. Major enhancements added in MXG 15.15 dated 23Feb1998:              
                                                                        
   Support for OS/390 Release 2.5 (no changes, need 15.04 or later).    
   Support for AIX commands IOSTAT/PSSTAT/VMSTAT output into SAS.       
   Support for StorageTek's VSM SMF records subtypes 9 thru 25.         
   Support for IDMS Journal format for IDMS V12.                        
   Support for Boole's IMF 3.2 (for IMS 6.1) INCOMPATIBLE               
   Landmark TMON for CICS V2 variables renamed.                         
   Landmark for MVS V2 INPUT STATEMENT EXCEEDED.                        
   New &MACxxxx macro variable added to all VMACs to override IMACs.    
   All VMACs for SMF records now start with IF ID=....                  
                                                                        
    Major enhancements added in MXG 15.08 dated 15Jan1998:              
                                                                        
   Support for Netview NPM Version 2.3 and APAR OW17876.                
   Support for AS/400 - OS/400 Release 4.1.0 (INCOMPATIBLE).            
   Support for IICS SMF type 103 (Internet Connection Secure Server).   
   Support for RMF type 79 subtype 15 (IMS IRLM Long Lock) record.      
   Hardcoded "PDB." DDname externalized into &PDBxxxx macro variables.  
   ASUMUOW option to get real TRANNAME instead of CPMI/CSMI tranname.   
   Performance improvements in BUILDPDB (_CDE's ordered, ELSE DOs).     
   New _Sxxyyy "PROC SORT" macros defined for PDB datasets in IMACs.    
                                                                        
    Major enhancements added in MXG 15.07 dated 18Dec1997:              
                                                                        
   Support for DPPX/370 Performance Reporter output.                    
   Support for MODEL204 Version 3.4 INCOMPATIBLE.                       
   Support for SAR CA-VIEW SMF exit SARSRQUX.                           
   Support for Omegamon for VTAM V400 (COMPATIBLE).                     
   Support for Landmark the Monitor for MVS Version 2 (INCOMPATIBLE).   
   Support for SAR CA-VIEW SARSRQUX SMF record.                         
   Support for Fujitsu's AIM V20 AIM/RDBII SMF type 98 record.          
   ASMTAPES ML-15 adds dump suppression, OS/390 1.3 JCT changes.        
     (MXG 15.06 said it contained ML-15, but actually still had ML-14). 
   VELOCITY variables are now multiplied by 100.                        
                                                                        
    Major enhancements added in MXG 15.06 dated 24Nov1997:              
                                                                        
   Support for CICS Transaction Server 1.2, INCOMPATIBLE.  IBM inserted 
      new fields in the middle of CICSTRAN record, so you must install  
      MXG 15.06 or later for CICS TS 1.2 processing.  New statistic data
      is also captured; see Change 15.274.                              
   Support for Landmark's The Monitor for CICS/ESA 2.0, INCOMPATIBLE.   
   CICS TS V1.1 APAR UN98309 INCOMPATIBLE,  Must install MXG 15.06.     
   Support for NTSMF Version 2.1 (INCOMPATIBLE), install MXG 15.06.     
   CICINTRV logic validated, must use this newest revision.             
   Duplicate CICS UOWTIME values due to SAS non-resolution of DATETIMEs.
   Support for Subtype 11 Type 88 System Logger.                        
   Support for Applied Expert Systems Clever TCP/IP.                    
   Support for HP MeasureWare for Terra Data OS.                        
   Support for DFSORT APAR PN71137 (COMPATIBLE).                        
   Support for HP MeasureWare for Terra Data OS in TYPEMWTE.            
   Support for Boole & Babbage MQ Series MVMQS VSAM History Records.    
   OS/390 R2.4 Goal Mode IBM Doc Error INVALID DATA R723CIDT fixed.     
   New IHDR110 exit for CICS record selection by APPLID.                
   Utility to recreate VBS from data with no RDW/BDW.                   
    Major enhancements added in MXG 15.05 dated 02Oct1997:              
                                                                        
   Support for JES3 TYPE26 APAR OW26297 adds account fields.            
   Support for APPC APAR OW16975 APAR-in-Error (INCOMPATIBLE).          
   Support for 255 Structures in a Coupling Facility (INCOMPAT).        
   Support for CA's IDMS 14.0 (INCOMPATIBLE).                           
   Support for BETA93 Release 1.3 (INCOMPATIBLE) (subtype 21 only).     
   Support for SMF type 91 new subtype 21 (SmartBatch) data.            
   Support for TCP/IP 3.2 API Calls record changes.                     
   Duplicate MULTIDD='Y' step records may not be deleted in BUILDPDB.   
   Catalog SMF Type 65 record INPUT STATEMENT EXCEEDED corrected.       
   PDB.ASUMUOW options externalized, zero obs now created by default.   
   DB2 Trace 102 subtype 140 INPUT STATEMENT EXCEEDED.                  
   Iceberg / IXFP subtypes 2,3,4 not output, MXG 15.02-15.04 only.      
   TYPE70 variable PCTMVSBY incorrect in MXG 15.01-15.04.               
                                                                        
   Major enhancements added in MXG 15.04 dated 01Sep1997:               
                                                                        
   MXG 15.04 Software is now over one million lines (1,008,660)!        
                                                                        
   MXG now protects ALL date fields for year 2000.                      
   Support for OS/390 Version 2 Release 4 (COMPATIBLE).                 
   Support for "Goal Mode SMF" type 99 subtype 6.                       
   Support for DCOLLECT in DFSMS 1.4 (COMPATIBLE)                       
   Support for VTAM 4.4 changes to SMF type 50.                         
                                                                        
   Support for CA-1/TMS Release 5.2 (COMPATIBLE).                       
   Support for ObjectStar 3.0 (INCOMPATIBLE in MXG).                    
   Support for Xerox's XPSM Version 2 SMF records.                      
   Support for HMF SMF Subtype 11 (DS3 Statistics).                     
   Support for five new NTSMF Objects.                                  
   Support for VM ADSM Account Records in VM/ESA.                       
   Support for TMON/DB2 record type "DE".                               
   Support for Boole MainView for CICS stat records.                    
   Support for Catalog Cell 'E7'(Alias) and invalid '05'x segment.      
   Support for RACFEVNT=22 and 59 in TYPE80A.                           
   Support for Shared Medical CICS Journal OASMON records.              
   Support for Peregrine's Service Center SMF record.                   
   Table of Holidays for SHIFT example added in IMACSHFT.               
                                                                        
   Major enhancements added in MXG 15.03 dated 30Jun1997:               
                                                                        
   Support for NTSMF Version 2.0 (INCOMPATIBLE; 15.02 was not correct). 
   Support for Windows NT 4.0 Service Pack 2 (INCOMPATIBLE also).       
   Support for IXFP SMF subtypes 6 and 7 (SNAPSHOT, SPACE UTILIZATION)  
   Support for TYPE1415 APAR OW25263 (for 3590s).                       
   Support for TYPE42 APAR OW26451/OW26543/OW26497 MAXRSPTM added.      
   Support for TYPE42 APAR OW20921 adds TYPE42VT VTOC/VVDS counts.      
   Support for OMVS RACF data with RACF utility IRRDBU00.               
   Support for new fields in TYPEEDGR DFSMSrmm extracts.                
   ASMTAPES at ML-14 populates fields, protects 0C4 ABENDs better.      
   RMFINTRV now allows Report RPGNs/Classes to be used in IMACWORK.     
   Format MGBYTRT (Bytes per Second) can truncate value on the left.    
   BUILDPDB enhanced to rename WORK.STEPS for IT Service Vision.        
   Leap second support for type 30, 110, and 100-102 "GMT" conversion   
   Trending for TYPE72GO into TREND.TRND72GO added.                     
   ANALCNCR Example counts Avg & Max Logged-ON TSO users from PDB.JOBs. 
                                                                        
   Major enhancements added in MXG 15.02:                               
                                                                        
   Support for DB2 Version 5.1 (MXG 14.14 tolerates, COMPATIBLE!!)      
   Support for Filetek's Optical Disk SMF record                        
   Support for OMVS data in RACF database (IRRDBU00 unload)             
   Enhancements to VMXGSUM for OBS=0 processing                         
   Replacement for MXG 15.01's defective CICINTRV.                      
   ASMTAPES Technical Note updated - cause of 0C4 is now known.         
                                                                        
   Major enhancements added in MXG 15.01:                               
                                                                        
   Errors in MXG 14.14 that are fixed in MXG 15.01:                     
                                                                        
   ASMTAPES (ML13) is available, recovers from 0C4s, see MXG Tech Notes.
   WORK.CICINTRV.DATA DOES NOT EXIST.                                   
   OS/390 R3 Goal only: Type 72 INPUT STATEMENT EXCEEDED RECORD LENGTH. 
   FILE counts in TYPETMON were incorrect before and after 14.14.       
                                                                        
   New Support in MXG 15.01:                                            
                                                                        
   ANALDDCN to analyze impact of DDCONS(NO) on duplicated SMF bytes     
   TYPEIMSD for IMS DBCTL transactions from IMS 07/08 log records       
   SMFPRM00 with first draft of MXG discussion for SMF parameters       
   Support and exploitation of new TALO fields added by ASMTAPES ML-12. 
   Support for APAR OW25152 (adds PRINTWAY Queue Name to TYPE6).        
   Support for Altai's ZARA Tape Management Release 1.2                 
   Support for Anacom's Anastack spooler's type 6 SMF                   
   Support for Boole and Babbage IMF 3.2.                               
   Support for CA-DISPATCH Version 6 with 5-digit JESNR                 
   Support for CA-ROSCOE Version 6 SMF record verified.                 
   Support for COMPAQ hardware NTSMF objects.                           
                                                                        
   Support for Hitachi 7700 changes to TYPE74CA/CACHET90 (INCOMPAT)     
   Support for Landmark's Performance Works/Smart Agents for UNIX 4.0   
   Support for MEMO subtype 8 creates new MEMODIST dataset.             
   Support for NETSPY Version 5.0 is already in MXG 14.14               
   Support for Virtual Tape Server additions to SMF type 94             
   Support for World Wide Web Common Log Format records.                
   Support for all OS/400 Release 3.7.0 records.                        
   UDUMPEBC utility for MVS-like LIST; hex dump under ASCII systems.    
                                                                        
  All of these enhancements are described in the Change Log, below.     
                                                                        
    Availability dates for the IBM products and MXG version required:   
                                                                        
                                       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     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        
      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                     Oct 27, 1997        15.06        
      CRR 1.6                          Jun 24, 1994.       12.02        
      CRR 1.7                          Apr 25, 1996.       14.02        
      DB2 2.3.0                        Oct 28, 1991.       10.01        
      DB2 3.1.0                        Dec 17, 1993.       13.02A       
      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        
      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        
      MQM 1.2, 1.3, 1.4                Apr 25, 1996.       14.02        
      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        
      RMDS 2.1, 2.2                    Dec 12, 1995.       12.12        
      TCP/IP 3.1                       Jun 12, 1995.       12.12        
      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        
      IMS     4.1                      Aug  6, 1994        12.02        
      IMS     5.1                      Jun  9, 1996        14.05        
      AS400 3.7.0                      Nov  1, 1996        15.01        
      AS400 4.1.0                      Dec 30, 1996        15.08        
                                                                        
    Availability dates for non-IBM products and MXG version required:   
                                       Availability     MXG Version     
      Product Name                     Date or Change    Required       
                                                                        
      Microsoft                                                         
       Windows NT 4.0 and NT 3.51                          14.14        
       Windows NT 4.0 Service Pack 2                       15.03        
      Demand Technology                                                 
       NTSMF Version 1 Beta                                14.11        
       NTSMF Version 2.0                                   15.03        
       NTSMF Version 2.1                                   15.06        
      Landmark                                                          
       The Monitor for DB2 Version 2                       13.06        
       The Monitor for DB2 Version 3                       15.03        
       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 MVS/ESA 1.3  -                      12.05        
       The Monitor for MVS/ESA 1.5  -                      12.05        
       The Monitor for MVS/ESA 2.0  -                      15.09        
      Candle                                                            
       Omegamon for CICS V200 User SMF                     12.05        
       Omegamon for CICS V300 User SMF                     13.06        
       Omegamon for IMS V110 (ITRF)                        12.12        
       Omegamon for IMS V300 (ITRF)                        14.04        
       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 SMS V100/V110                          12.03        
      CA                                                                
       ASTEX 2.1                                           14.04        
       NETSPY 4.7                                          14.03        
       NETSPY 5.0                                          14.03        
      Boole & Babbage                                                   
       IMF 3.1 (for IMS 5.1)                               12.12        
      Memorex/Telex                                                     
       LMS 3.1                                             12.12A       
                                                                        
                                                                        
II.  MXG Technical Notes                                                
                                                                        
 1. Measurement of CPU Utilization in PR/SM,MDF,MLPF environments.      
                                                                        
   This note was written for ACHAP10, "Processor Utilization".          
                                                                        
   The ASUM70PR dataset is built from the TYPE70PR detail data using    
     %INCLUDE SOURLIB(ASUM70PR);   as shown in JCLPDB6 example.  There  
   is one observation in ASUM70PR from each MVS SYSTEM for each RMF     
   Interval, and that observation describes the utilization of each of  
   the LPARS, and their sum, which is the hardware busy of the platform.
      If you have multiple MVS Systems, and if you process their SMF    
      data together, then duplicate data will exist in ASUM70PR, since  
      SYSA's type 70 record will describe all LPARs, and SYSB's type 70 
      will also describe all LPARs, so you must select only one set of  
      observations (from SYSA or from SYSB) to avoid duplication.       
                                                                        
   For each partition, the Partition Dispatch Time and the Effective    
   Dispatch Time (and their difference, the CPU time when this partition
   was dispatched for LPAR management of this partition) are recorded.  
   There is also a "pseudo" partition named "PHYSICAL" that exists only 
   in the RMF type 70 record that records the LPAR management dispatch  
   time that could not be charged to a specific partition.              
                                                                        
                  Schematic of ASUM70PR observation                     
                                                                        
                 Total Partition Dispatch (CPU) Time                    
      CPUACTTM= LPnUPDTM summed for all real partitions + LPPUPDTM      
                                                                        
                              CPUACTTM                                  
    ______________________________________________________________      
                                                                        
                                                                        
        LPAR #1         LPAR #2        LPAR # 3       "PHYSICAL"        
      LP1UPDTM        LP2UPDTM        LP3UPDTM         LPPUPDTM         
      Dispatched      Dispatched      Dispatched       Dispatched       
    _______________ _______________ _______________ ______________      
                                                                        
         LP1UEDTM        LP2UEDTM        LP3UEDTM                       
          LPAR1           LPAR2           LPAR3                         
         Effective       Effective       Effective                      
                                                                        
                                                                        
    __              __              __              ______________      
                                                                        
     1               2               3                "Physical"        
   LP1MGTTM        LP2MGTTM        LP3MGTTM           LPPUPDTM          
     In-partition LPAR Management Time            Unassigned LPAR time  
                                                                        
      Important variables in PDB.ASUM70PR dataset:                      
                                                                        
      LPnUPDTM  - Partition Dispatch Duration for LPAR n.               
      LPnUEDTM  - Partition Effective Dispatch Duration for LPAR n.     
      LPnMGTTM  - LPnUPDTM minus LPnUEDTM, this partition management.   
      LPPUPDTM  - Physical partition dispatch duration.                 
      PARTNCPU  - Number of engines in this platform.                   
      PCTCPUBY  - Percent CPUs were Busy in all LPARS, equal to the sum 
                  of all partition's (including PHYSICAL) dispatch time,
                  minus HiperDispatch Parked Time, divided by the Total 
                  "capacity" of all ONLINE, NON-PARKED engines:         
                  100*CPUACTTM/(NRCPUS*DURATM).  This is the percent    
                  of the total capacity of the box that was used.  If   
                  the Average NRCPUS is 5.5, and CPUACTTM was 4 hours   
                  in a one hour interval, PCTCPUBY would be 72% busy.   
      PCTLnBY   - Percent "Physically" Busy in LPAR n, equal to the LPAR
                  Dispatch time divided by the Total "capacity" of all  
                  engines in the box:  100*LPnUPDTM/(PARTNCPU*DURATM).  
                  If an LPAR was dispatched for 1 hour, and the CEC has 
                  5 engines, then PCTLnBY for that LPAR would be 20%,   
                  because that LPAR used 20% of the hardware platform.  
      PCTLnOV   - Percent "Physically" Busy in "LPAR Overhead" in this  
                  LPAR, 100*LPnMGTTM/(PARTNCPU*DURATM).                 
      LPnNRPRC  - Number of engines available to LPAR n.                
      LPnDUR    - LPAR n's "Up time" or "Availability time to execute   
                  CPU", the sum of DURATM across all LCPUs in LPAR n,   
                  or LPnDUR=LPnNPRC*DURATM.  This is the duration when  
                  this LPAR could have been dispatched.  If the LPAR was
                  IPL'd as a 3-engine MVS machine, in one hour, it would
                  have 3 hours of "Up Time" (or 3 hours of "capacity"). 
      LPCTnBY   - Percent "Logically" Busy in LPAR n, equal to the LPAR 
                  Dispatch time for the partition divided by the LPAR's 
                  "Up Time", 100*LPnUPDTM/LPnDUR.  If a 3-engine LPAR   
                  was dispatched for 60 minutes in one hour, its LPCTnBY
                  would be 33%.  This variable describes the percent of 
                  LPAR capacity, in contrast to variable PCTLnBY which  
                  describes the percent of Hardware Platform capacity.  
                  If that same 3-engine LPAR was executing on a 5-engine
                  CEC, PCTLnBY would be 20%, because that LPAR used 20% 
                                                                        
                  of the hardware platform, while LPCTnBY is 33% of the 
                  CPU time available to this LPAR.                      
      LPnCAP    - 'Y' if this partition is capped.                      
      LPnCHG    - 'Y' if something changed in LPAR n.                   
      LPnDED    - 'Y' if this partition has all-dedicated-CPUs.         
      LPCTnOV   - Percent "Logically" Busy in "LPAR Overhead"           
                  100*LPnMGTTM/LPnDUR, describes how much of the        
                  Dispatch Duration was for management of this LPAR.    
                                                                        
      Important variables in PDB.TYPE70PR dataset:                      
                                                                        
      LPARNUM   - Logical Partition Number, = PARTISHN in TYPE70 dataset
      LCPUPDTM  - Partition Dispatch Time                               
      LCPUEDTM  - Partition Effective Dispatch Time                     
                                                                        
    The following example is real data from a 5-engine CEC (Central     
    Electronic Complex, the preferred name for a platform).  This CEC   
    has three LPARs: LP1 has two engines (and is lightly used), LP2 has 
    five engines, and LP3 has three engines.  All CPUs are shared and   
    Wait Completion is No.  One hourly observation in ASUM70PR showed:  
                                                                        
             PARTNCPU  5          - Number of real engines in CEC       
             DURATM    1:00:00.05 - Duration interval                   
             CPUACTTM  4:40:35.32 - Total CPU Dispatch, all engines     
             CPUOVHTM    15:35.40 - Total CPU Overhead in LPARS         
             LPPUPDTM     6:40.28 - Total "Physical" Overhead           
             PCTCPUBY  93.53%     - CPUACTTM as a percent of hardware   
             PCTOVHD    5.20%     - CPUOVHTM as a percent of hardware   
             PCTPOV     2.22%     - LPPUPDTM as a percent of hardware   
                                                                        
                          LP1            LP2            LP3             
             LPnNRPRC     2              5              3               
             LPnDUR       2:00:00.10     5:00:00.25     3:00:00.15      
             LPnUPDTM        4:49.67     3:33.06.54       55:58.85      
             LPnUEDTM        2:56.63     3:29:16.51       52:46.77      
             LPnMGTTM        1:53.03        3:50.02        3:12.07      
             LPCT1BY      4.02%          71.04%         31.10%          
             LPCT1OV      1.57%           1.28%          1.78%          
             PCTL1BY      1.61%          71.04%         18.66%          
             PCTL1OV       .63%           1.28%          1.07%          
                                                                        
             The LP2 has the same PCTL2BY as LPCT2BY because it can use 
             all five engines, and its logical and physical utilization 
             are the same.  The LP3, with only three engines available  
             to its MVS, shows it is using 18.66% of the five hardware  
             engines (PCTL3BY), while LPCT3BY shows that this actually  
             is 31.1% of the CPU time possible for those three logical  
             CPUs available to LP3.                                     
                                                                        
    The dispatch time measurements in ASUM70PR are always accurate in   
    describing the total platform busy and each LPARs use of the total, 
    because when an LPAR is dispatched, its processors are not available
    to any other LPAR, and thus ASUM70PR does report platform capacity. 
                                                                        
    Furthermore, if all CPUs are shared and Wait Completion is No, the  
    ASUM70PR dispatch duration is the actual CPU busy time, so not only 
    is the total platform capacity known, but also the utilization of   
    individual LPARs is measured in ASUM70PR.                           
                                                                        
                                                                        
    The problem arises when CPUs are Dedicated to an LPAR, or when Wait 
    Complete = Yes is used, because the dispatch time in those cases is 
    NOT equal to the CPU executing time.  While a dispatch time of one  
                                                                        
    hour does mean that one hour of total platform capacity was used by 
    an LPAR, (i.e., not available to other LPARs), the actual CPU time  
    used by that LPAR may be a lot less than one hour.  What we need is 
    the Wait time measured inside each MVS system, which is in the MVS  
    TYPE70 dataset, but each type 70 record only has a single TYPE70    
    segment (for the LPAR in which this MVS System executed); we do not 
    get a TYPE70 segment for the other LPARs.  But MXG does store the   
    MVS Wait Time from the TYPE70 segment into variable ORIGWAIT in the 
    TYPE70PR observation for each LCPUADDR, which shows this data:      
                                                                        
                                                                        
    Wait Complete = YES example:  System SYSC (LPARCPUS=2 PARTNCPU=4)   
                                                                        
                            LPARNUM=PARTISHN=2                          
                LCPU=0                           LCPU=1                 
             DURATM=15 min                    DURATM=15 min             
     --------------------------------- -------------------------------  
                                                                        
          8 min             7 min                15min                  
     -------------------- ------------ -------------------------------  
       Dispatched          LPAR Wait          Dispatched                
       LCPUPDTM 70PR         calc             LCPUPDTM 70PR             
                                                                        
       5 min      3 min     7 min           11 min             4 min    
     ---------- ========= ------------ --------------------- =========  
      ORIGWAIT   BUSY      LPAR Wait      ORIGWAIT             BUSY     
        70       calc        calc            70                calc     
                                                                        
                                                                        
    This LPAR has two LCPUs, Wait Complete=Yes, but due to the other    
    LPAR on this platform (that was also using Wait Complete=Yes), the  
    LCPU=0 was dispatched for only 8 minutes of the 15 minute interval, 
    while LCPU=1 was dispatched for all 15 minutes.  The ORIGWAIT from  
    TYPE70 shows that LCPU=0 was actually CPU Busy for only 3 minutes,  
    and LCPU=1 was actually CPU Busy for only 4 minutes.                
                                                                        
    While there are only two LCPUs for this LPAR, this LPAR is in a     
    platform that has four engines, so the ASUM70PR calculation is:     
        PCTL2BY = (8 disp +  15 disp )/ (4*15) = 23/60 = 38%            
    because 38% of the dispatch capacity of the four engines in the     
    hardware platform was consumed by this LPAR in this interval.       
                                                                        
    However, RMF in its CPU Activity Report calculates two percentages  
    (and MXG replicates in both TYPE70 and TYPE70PR data):              
                                                                        
    PCTCPUBY = "LPAR Busy Time" = (3 busy + 4 busy) / (2 * 15)   = 23%  
                                                                        
    PCTMVSBY = "MVS Busy Time"  = (10 busy+lparwait + 4 busy)/30 = 48%  
                                                                        
    The "LPAR Busy Time" shows that this LPAR was busy for 7 of the 30  
    minutes that the two engines in the LPAR could have been executing, 
    and thus is a measure of how busy the MVS system might have been.   
                                                                        
    However, the "MVS Busy Time" calculated by IBM is at best confusing 
    and at worst wrong, for Wait Completion = Yes LPARs, because it     
    calculates the MVS busy time as DURATM minus ORIGWAIT, adding the 3 
    minutes busy and 7 minutes of LPAR wait from LCPU=0 to the 4 minutes
    busy from LCPU=1 to conclude 14 minutes of "busy time" out of the   
    30 minutes that the two engines could have been executing, for 48%! 
                                                                        
    But the MVS SRM never saw those possible 30 minutes of execution; it
    was dispatched for only 8 + 15 = 23 minutes, so a far more accurate 
    measure is "SRM Busy Time", the busy time over the dispatched time: 
                                                                        
                                                                        
    PCTSRMBY = "SRM Busy Time" = (3 busy + 4 busy) / 23 (dispatch) = 30%
                                                                        
    which more accurately reflects what MVS can do with Wait Comp=Yes,  
    and it strongly suggests that the IBM "MVS Busy Time" is wrong for  
    Wait Comp=Yes.                                                      
                                                                        
       (The example used the Partition Dispatch times, but to be        
        slightly more precise, using the Effective Dispatch times would 
        show what was delivered to MVS.  I am still deciding if I should
        create a new variable for PCTSRMBY, but want to send this       
        preliminary note to MXG-L, so I will update this part of this   
        note at a later date.)                                          
                                                                        
                                                                        
    Dedicated example:  System SYSA (LPARCPUS=3 PARTNCPU=4)             
                        LCPU=0   Dedicated, Wait=No                     
                        LCPU=1,2 Shared, Wait=No                        
                                                                        
                            LPARNUM=PARTISHN=5                          
           LCPU=0                                                       
      DURATM=15 min                          DURATM=15 min              
     ---------------------         ------------------------------------ 
                                                 LCPU=1                 
      14:59.20                      5:48.92         8:25.73   0:45.35   
     ---------------------         =============== --------- ---------- 
      Dispatched                    Dispatched      ORIGWAIT  Non-Disp  
      LCPUPDTM 70PR                 LCPUPDTM 70PR     70      Non-Wait  
                                     BUSY                      calc     
                                                                        
                                                 LCPU=2                 
      3:11.51    11:48.49           5:49.20         8:25.41   0:45.39   
     ---------- ==========         =============== --------- ---------- 
      ORIGWAIT     BUSY             Dispatched      ORIGWAIT  Non-Disp  
        70         calc             LCPUPDTM 70PR      70     Non-Wait  
                                     BUSY                       calc    
                                                                        
                                                                        
    For all the three LCPUs in this LPAR, MXG calculates in ASUM70PR:   
      PCTL5BY = 100* ( 26.5 / 4*15) = 100 * 26.5 /60  = 44.37%          
    because the total dispatch time of the three LCPUs was 26.5 minutes 
    of the possible 60 minutes of dispatch time in the four engines of  
    the platform, and this is this LPAR's use of dispatch capacity.     
                                                                        
    But if we have the TYPE70PR observation from the system that has the
    ORIGWAIT measurement from TYPE70 for that dedicated LCPU, we can see
    the LPAR's total CPU busy time was only 11:48 + 5:48 + 5:49, or 22.5
    minutes, since 3 minutes of that dispatch time was in MVS wait time!
                                                                        
    The IBM RMF calculations for each LCPU and the total for all three  
    LCPUs in this LPAR show:                                            
                                                                        
        LCPU  PCTCPUBY   (calc)     PCTMVSBY   (calc)       Status      
         0     78.72   (11:48/15)    78.72   (11:48/15)    Ded,Wait=No  
         1     38.77   ( 5:48/15)    43.81   ( 6:33/15)    Shr,Wait=No  
         2     38.80   ( 5:49/15)    43.84   ( 6:34/15)    Shr,Wait=No  
        all    52.10   (23:17/45)    55.46   (24:55/45)    Combined     
                                                                        
    For the Dedicated LCPU, both PCTCPUBY and PCTMVSBY are calculated   
      PCTCPUBY=PCTMVSBY= 100*(DURATM-ORIGWAIT)/DURATM  = 78.7%          
      PCTMVSBY=PCTCPUBY= 100*(DURATM-ORIGWAIT)/DURATM  = 78.7%          
                                                                        
    For the Shared, Non-Wait LCPUs, the "LPAR Busy Time" is             
      PCTCPUBY= 100*LCPUPDTM/DURATM = 38.7%                             
    but the IBM calculation for the "MVS Busy Time" is                  
      PCTMVSBY= 100*(DURATM-ORIGWAIT)/DURATM = 43.8%                    
    because the PCTMVSBY value includes the 45 seconds of non-dispatched
    non-wait time recorded in the MVS Busy Time calculation!            
                                                                        
    Again, while PCTCPUBY is legitimate, PCTMVSBY raises more questions 
    than it answers.                                                    
                                                                        
    To summarize what percentages are printed where by IBM and reported 
    where by MXG, on RMF CPU Activity Report, the "LPAR Busy Time Perc" 
    is variable PCTCPUBY, and the "MVS Busy Time Perc" is variable      
    PCTMVSBY in dataset TYPE70 (and now in TYPE70PR as well).  On RMF's 
    Partition Data Report, IBM's "Logical Processors Total" is variable 
    LPCTnBY, and IBM's "Physical Processors Total" is PCTLnBY in dataset
    ASUM70PR for each LPAR, and the "Physical Processors Total" is the  
    variable PCTCPBUY in ASUM70PR.                                      
                                                                        
    Note:  I intend to revise this note as I learn more, especially for 
    Millennium and/or MDF, in the near future.  The purpose of this     
    much of the note was to document what is calculated by MXG and by   
    IBM when you try to compare RMF reports to MXG datasets, and to     
    point out basic problems if you have Dedicated or Wait Comp = YES.  
    Not only is there a problem in ASUM70PR in that we do not know the  
    true CPU busy time, we also have assumed the "capacity" was the     
    DURATM of the interval, but that is not always the case, especially 
    when LPAR weighting is taken into account.  No single percentage    
    value can be used, as it depends on your perspective.  ASUM70PR     
    reports usage percentages of the "dispatch" capacity, while TYPE70  
    still must be used to understand what is happening inside each MVS. 
                                                                        
 2. FAT32 file system reduces space needed for MXG from 139MB to 68MB.  
                                                                        
    On Windows 95 and Windows NT with FAT File Systems, the MXG Source  
    Library directory DIR command shows 3549 files totaling 57.7 MB,    
    but the files in that directory actually required 139.1 Megabytes   
    of disk space!  The 2GB disk drive with 32K cluster size wastes     
    space if the file is less than 32KBytes, and as only 272 of MXG's   
    source files are over 32K in size, the other 3277 small files waste 
    lots of disk space with large cluster size under FAT file systems.  
                                                                        
    Well that is a dead problem with the newer FAT32 file system that   
    virtually eliminates the space waste problem.  That same source     
    library required only 68.23 MegaBytes on a 9GB FAT32 disk drive!    
                                                                        
                                                                        
III. MVS Technical Notes.                                               
                                                                        
 1. APAR OW25609 corrects a stoppage of SMF type 30 interval records    
    (subtypes 2 & 3) and type 23 records, after a serialization problem.
    The APAR applies to MVS/4.3 thru OS/390 2.4.                        
                                                                        
 2. APAR OW28289 changes counts in type 30 variables TAPNMNTS/TAPSMNTS  
    (SMF30PTM/SMF30TPR).  In DF/SMS 1.2 and earlier, tape mount counts  
    were the number of physical mounts (actually, a count of volumes    
    that were verified by OPEN/CLOSE/EOV via a loadpoint read of the    
    VOL1 tape label).  That was changed by an SPE to DF/SMS 1.2.0 (which
    was included in DF/SMS 1.3.0 and 1.4.0); IBM decided instead to     
    count logical volumes (i.e., increment the mount count when OPEN    
    processing is entered with the tape drive in a ready state and with 
    the mounted volume at loadpoint).  A document change was prepared   
    but never distributed, and now IBM is backing out the SPE's effect, 
                                                                        
    and with this APAR, the counts revert to physical mount counts.  The
    APAR's text is confusing, because it lists PTFs for DF/SMS releases 
    1B0, 1C0, and 1D0, which turn out to be DFSMS 1.2, 1.3, and 1.4,    
    respectively.  If you depend on the count of tape mounts in type 30 
    records, you will want to apply this PTF.                           
                                                                        
 3. APAR OW28613 corrects errors in the JES2 Type 26 Purge record in the
    SMF26OAG Accounting Section offset.  I earlier thought MXG would not
    fail, but without that APAR, MXG offset validation was insufficient,
    an INPUT STATEMENT EXCEEDED occurs.  Now, Change 15.330 circumvents 
    the wrong value for SMF26OAG, but the ACCOUNTn fields in TYPE26J2   
    will be blank until you install to APAR to correct IBM's error.     
    Fortunately, MXG only uses the TYPE26J2 ACCOUNTn fields for jobs    
    that do not produce type 30s (JCL Errors or Cancel before start).   
                                                                        
 4. APAR OW28256 reports invalid CPU times measured (once again!) in RMF
    type 72 field SMF72RCT (MXG Variable CPURCTTM, which is summed into 
    variable CPUTM); PTF was available November 14 1997.  This causes   
    the total CPU time captured in type 72 records to exceed the total  
    CPU busy time, causing the Uncaptured CPU time (misnamed as CPUOVHTM
    and labeled as "Overhead") to be negative in RMFINTRV.  This same   
    field was in error in 1992, fixed then by APAR OY51878.  MXG now    
    detects the negative value and prints this error message on the log:
      "ERROR. NEGATIVE CPU-UNCAPTURED-TIME (TYPE70-TYPE72)".            
    See text of Change 15.238 for more details.                         
                                                                        
 5. APAR OW26619 for OS/390 V2.4, in Goal Mode corrects WLM errors found
    by IBM during final function test, and corrects SMF values.         
                                                                        
 6. APAR OW26421 for OS/390 V1.3 is needed only for ASMTAPES. In OS/390 
    IBM created two 4-byte fields for Y2K support to replace the 3-byte 
    fields JCTSSD and JCTJMRJD (step and job start/init dates), but I   
    missed that change, so ASMTAPES still used the 3-byte fields.  But  
    IBM also zeroed the 3-byte fields, which caused INVALID DATA when   
    TYPETMNT was executed, and variable INITTIME has missing value.     
    This APAR restores the dates in the 3-byte fields, so INITTIME will 
    not be missing.  The next maintenance level of the MXG ASMTAPES will
    avoid the exposure by using the 4-byte fields if they are present.  
                                                                        
 7. SYNCSORT 3.6 can ABEND 0C9 during a PROC SORT; SYNCSORT fix SY49930 
    is the correction.                                                  
                                                                        
 8. APAR OW30153 corrects type 30 Measured Usage (MULC) segments.  There
    are multiple occurrences of the same product name and qualifier for 
    PRODNAME=CICS PRODQUAL=DFHKETCB in the interval records that should 
    have had only a single segment.  There are still other errors that  
    are not addressed in creating the subtype 4 and subtype 5 records   
    from the interval records.  One CICS job had 39 DHFKETCB segments in
    its interval records (subtype 2 and 3), but had 37 segments in its  
    step termination record (subtype 4) and then had only 36 segments in
    its job termination record (subtype 5).  Further, the job had 12    
    DFHSIP segments in the interval records but had 16 segments in both 
    step and job terminate.  Finally, the job had 2 DFHDUP segments in  
    the job term but none in either the interval or step term records.  
    A new problem has been opened with IBM on this error.               
    Note that old APAR OW16176, which consolidates MULC sections for    
    each product, should be installed.  Increasing SMF buffers with     
    APAR OW12836 is also recommended to minimize the problems with SMF  
    buffers, and especially specification of DDCONS=NO in SMFPRMxx in   
    SYS1.PARMLIB is strongly recommended to eliminate the SMF address   
    algorithm to consolidate DD segments.                               
                                                                        
    Note added Dec 30, 1997:                                            
    APAR PN80497 corrects a problem after applying UN84065 with Measured
    Usage (MULC) that can create millions of type 30 subtype 3 records  
    with the same product name in the MULC segment.  The problem        
    occurred with an IMS BMP that used MQ Series.  The excess records   
    could cause IEE979W SMF DATA LOST - NO BUFFER SPACE AVAILABLE.      
                                                                        
 9. APAR OW30059 (PTF available 12Dec97) reports type 42 values for     
    Direct Write and Direct Read SMF42DWB/SMF42DRB and this APAR is     
    likely the fix that was originally described in note 26 in MVS      
    Technical Notes in MXG Newsletter THIRTY-TWO for APAR OW20926.      
    When the channel program did single CI reads and writes, residual   
    data was left in the counter that was not used.                     
                                                                        
10. APAR PQ09396 (Target 26Dec97) for MQSERIES SMF type 116 reports     
    inconsistencies between 115 and 116 record's statistics. The more   
    elaborate description (this text added Mar 27, 1998): The numbers   
    MQGET and MQPUT (MXG Variables QMACGETx and QMACPUTx in MQMACCT     
    dataset from 116 record) are significantly less than the totals     
    reported from 115 records, because the data fields containing the   
    116 records were incremented outside of latch control, which led    
    to the counts being cleared at the same time they were updated,     
    causing certain of the counts to be lost.  The PTF for this APAR    
    will update the fields containing the totals of MQI requests via a  
    CS instruction, hence they will be protected from being cleared     
    whilst being updated.                                               
                                                                        
11. APAR PQ09083 is for subtype '51'x of the FTP SMF record (VMACFTP).  
    The text mentions SMF Record Type 51, but there is no type 51 SMF   
    record (yet).  The APAR corrects missing values in variables        
    DVGSETME/DVGSEDTE in dataset FTP51X.                                
                                                                        
12. Job Accounting for Started Tasks became available with MVS/ESA 5.1, 
    because you can now have a JOB card in the JCL for your STC's, and  
    can put ACCOUNT parameters in that JOB card that show up in MXG's   
    ACCOUNTn variables in PDB.JOBS/PDB.PRINT/PDB.STEPS datasets.  The   
    JCL Reference Manual Sections 7.2, 7.3, and 16.7 discuss how.       
                                                                        
13. What happens to measurements if I have a Y2K Test System in an LPAR?
                                                                        
    You can use the ASUM70PR dataset and select the observations from   
    your production LPAR (SYSTM='PROD') to measure the Y2K Partition's  
    resources, since the STARTIME of the records with SYSTEM='PROD'     
    will be your local time of day.                                     
                                                                        
    All of the records written on SYSTEM='Y2K' will have the year 2000  
    dates (although the READTIME value could be earlier if jobs were    
    read into the hold queue before IPLing with year 2000).  Since the  
    Y2K system will be re-IPL'd repetitively with the same start value  
    (probably 31DEC99:23:45:00), RMF interval data will appear to have  
    duplicate data and the jobs/steps from all IPLs will be jumbled     
    together, because MXG sorts RMF data by STARTIME and job data by    
    READTIME.                                                           
                                                                        
    You can extract SYSTEM='Y2K' data for a specific "test run" by      
    finding the record number (_N_) of each SMF IPL record, using:      
       %INCLUDE SOURCLIB(VMACSMF);                                      
       DATA _NULL_;                                                     
       _SMF;                                                            
       IF ID=0 THEN PUT 'IPL RECORD FOUND ' _N_= SMFTIME=;              
    and then use the record number of the specific IPL to select only   
    the SMF records desired.  If you wanted the third run, and the third
    IPL record had _N_=8,000 and the next IPL record had _N_=10,000, you
    would use this logic:                                               
       %INCLUDE SOURCLIB(VMACSMF);                                      
       DATA _NULL_;                                                     
       _SMF;                                                            
       FILE SMFOUT DCB=SMF;                                             
       IF 8000 LE _N_ LE 9999 THEN PUT _INFILE_;                        
       IF _N_ EQ 10000 THEN STOP;                                       
    to write to //SMFOUT DD only those records for that test run.       
                                                                        
    There is an alternative.  You can use the IPL PROMPT feature to     
    require the operator to reply with the (local) time and the reason  
    (describe the test run) for each IPL, and there will be a SUBTYPE=8 
    observation in dataset TYPE90 with variables DTIME and IPLREASN with
    the operator's reply, so the TYPE90 dataset can be used to identify 
    the records in each test run (variable SMFRECNR, equal to _N_, was  
    added to the TYPE90 dataset by Change 15.267).                      
    You must have specified PROMPT(IPLR) or PROMPT(ALL) in member       
    SMFPRMxx in SYS1.PARMLIB dataset to prompt the operator for the     
    reply at each IPL.                                                  
                                                                        
14. Almost-Duplicate TYPE74 records, differing only by one second in the
    STARTIME, can be written by Boole & Babbage's CMF Product, if both  
    IPM and CPM modes are enabled.  This has happened recently as sites 
    installed OS/390.  In MXG's TYPE7xxx datasets, variable PRODUCT will
    be 'CMF-IPM' in one almost-duplicate record, and 'CMF-CPM' in the   
    other observation.  Boole does NOT recommend both modes!            
                                                                        
15. Channel Type variable CHANTYPE in dataset TYPE73 still exists, but  
    variable SMF73CPD provides a better description as it describes both
    ESCON and Parallel Channel types.  SMF73CPD was new in MVS/ESA 5.1. 
                                                                        
16. APAR OW27855 corrects PSF/MVS-written type 6 SMF records so that    
    they now contain the node number of the current node in field       
    SMF6ROUN, which MXG decodes into variable NODE and RMOTID in TYPE6  
    dataset.                                                            
                                                                        
17. APAR OW20844 enables JES2 job numbers greater than 32000, but has   
    no impact on MXG, since MXG has supported 5-digit JES Numbers thru  
    99999 from the JCTJOBID for several years.                          
                                                                        
IV.  DB2 Technical Notes.                                               
                                                                        
 1. There are no DB2 Technical Notes in this newsletter.                
                                                                        
V.   IMS Technical Notes.                                               
                                                                        
 1. Support for Boole's IMF 3.2 (for IMS 6.1) was added in MXG 15.09.   
    Candle has not informed me of any changes in their ITRF product.    
                                                                        
 2. Discussion of IMS Log support in MXG Software.                      
                                                                        
    I strongly recommend you use an IMS monitor (was Boole or Candle)   
    IMF from BMC, Mainview for IMS from ASG, ITRF from IBM/Candle)      
    that creates a transaction record, rather than attempt to use       
    IBM's IMS log for transaction response and resource measurement.    
                                                                        
    See MXG newsletter TWENTY-FIVE, IMS Technical Notes, for the MXG    
    position statement of the technical reasons why you cannot measure  
    the response time and resources (CPU, DL/I calls) for transactions  
    with only IBM's standard IMS log records.                           
                                                                        
    NOTE INSERTED IN 2015:  NOW USE THE TYPEIMST PROGRAM TO PROCESS     
    THE IBM IMS LOG RECORD 56FA, WHICH IS A PER-TRANSACTION RECORD      
    WITH CORRECT RESPONSE AND CPU TIMES.  SEARCH NEWSLTERS FOR IMS56FA. 
                                                                        
    However, you CAN use the TYPEIMS7 MXG program to get accurate counts
    of transactions and resources by transaction, because it uses IMS 07
    and IMS 08 log records, written for each deschedule of an IMS       
    program, which contains the count of IMS transactions that were run 
    during that program schedule (can be 1, usually is at least 5       
    transactions per schedule, and be millions for WFIs), the           
    transaction name, and the total CPU time and DL/I calls for all     
    of those IMS transactions.  But you cannot get accurate resources   
    per transaction from the IMS 07/08 records.  At best, you can get   
    the "average" of each group of transaction processed if you are     
    willing to divide the CPU time by the number of transactions run,   
    and you'll get fractional numbers of DL/I calls per transaction!    
                                                                        
    MXG Member TYPEIMFL will read the IMS log and will select and create
    all possible datasets from any combination of Boole's IMF log       
    records (LCODE=FAx) IBM IMS log records (01,03,07,08,31x,36x,40x,   
    plus fastpath 59x subtypes 01,03,36x,37x,38x) and SAP IMS log       
    records (LCODE=AEx), and the new statistics subtypes as well.       
    Members TYPEIMFL and TYPEIMS7 both use macros that are defined in   
    VMACIMS to decode those IMS log records, and which are fully        
    supported by MXG.                                                   
                                                                        
    It is not the reading of the IMF, IBM, and SAP IMS log records that 
    is the problem, but rather it is the construction of the            
    many-records-per-transaction-without-a-merge-key into a single      
    transaction record with per-transaction resources and response that 
    is in principle impossible with IMS log records.                    
                                                                        
    Nevertheless if you still must try to get IMS response time with    
    only IBM's IMS log records, because your management still won't buy 
    you an IMS monitor tool, then, at your own risk, you can probably   
    get good results with the MXG assembly program ASMIMSL6 (IMS 6+) and
    the JCLIMSL6 example.  The ASM program acts like an IMS MPR and     
    reads the log to figure out which records go with which transaction,
    and writes a copy of the IMS log records with an appendage to       
    identify the transaction, and then the MXG SAS programs invoked in  
    JCLIMSLG read the extended IMS log records to crate dataset IMSTRAN 
    with observations on a per-transaction basis.  These transaction    
    records will always contain only average CPU and DL/I calls, but the
    response time for each transaction is usually quite accurate,       
    although a few transactions may not be perfectly matched and can    
    have very large response times (and sometimes the output queue time 
    is accurately very large!).  It is not guaranteed that ASMIMSL6 will
    exist, but it is my hope to continue to provide this crutch for IMS 
    sites unwilling to purchase an IMS monitor.                         
                                                                        
                                                                        
VI.  SAS Technical Notes.                                               
                                                                        
 1. There are no MXG problems using the Version 6.09 of the SAS System. 
    In fact, there have been no MXG problems with Version 6.08 at TS430 
    or later maintenance levels!  Perhaps that is because MXG Software  
    is now a standard part of the SAS Quality Assurance test stream?    
                                                                        
VII. CICS Technical Notes.                                              
                                                                        
 1. How can you use USER instead of TERMINAL to bill CICS transactions. 
                                                                        
    IBM note RTA000013242 Library item Q451666 answers the question,    
    "How can you use USER instead of TERMINAL to bill CICS transactions 
    in an ISC or MRO CICS environment (i.e., when using transaction     
    routing?", by pointing out that when you specify USERSEC=IDENTIFY   
    or ATTACHSEC(IDENTIFY) on the SYSTEM entry or CONNECTION definition,
    the USER field is then propagated into the records created in the   
    AOR and other regions observations in CICSTRAN.CICSTRAN.            
                                                                        
    If you are billing CICS and DB2 by transactions, you really should  
    look at the ASUMUOW member that summarizes CICSTRAN and DB2ACCT and 
    their CPU times into one record per Unit of Work, reducing the      
    number of "things" you have to count.  ASUMUOW keeps both TERMINAL  
                                                                        
    and USER as well as both CICS and DB2 CPU times plus CICS response  
    buckets in its output dataset PDB.ASUMUOW.  If you were using       
    ASUMCICS to create PDB.CICS summary data, you will find ASUMUOW     
    preserves the CICS resource and response fields from PDB.CICS and   
    adds in the DB2 information.  ASUMUOW replaces the earlier ANALDB2C 
    report program that merged DB2ACCT and CICSTRAN records.            
                                                                        
VIII. Windows NT Technical Notes.                                       
                                                                        
 1. Use  /B "Binary" switch on the COPY command to eliminate '3F'x.     
                                                                        
    Two sites had STOPOVER ABENDS on MVS reading NTSMF data that had    
    been COPYed under Windows NT Server before uploading to MVS.  The   
    hex dump showed a one-byte physical record containing a '3F'x.      
    Another site's TYPENTSM job failed with a 180 abend; the VMACNTSM   
    member had been COPYed, and an extra line containing '3F'x had been 
    appended to the source file.  It is apparently a documented fact    
    that the COPY command can add an ASCII End-of-File Character at     
    the end of a copy whenever multiple input files are copied into an  
    output file.  That ASCII End-of-File Character then becomes the     
    separate physical record on MVS after uploading and translation     
    from ASCII to EBCDIC with ftp.  Using the  /B  "Binary" switch on   
    the COPY command was found to eliminate the extra character.        
    To read the uploaded file with the short record without ABENDing,   
    you can change MXG's STOPOVER option to MISSOVER by using:          
         MACRO STOPOVER MISSOVER %                                      
    as your first SAS statement, before the %INCLUDEs in your SYSIN.    
                                                                        
IX.   Incompatibilities and Installation of MXG 15.15.                  
                                                                        
 1. Incompatibilities introduced in MXG 15.15 (since MXG 14.14):        
                                                                        
  a- IMACs that were changed (if they exist in your USERID.SOURCLIB, you
     must refit your tailoring, starting with the new IMAC member):     
                                                                        
     IMACPTF, if you install PTF UN98309 for CICS Transaction Server 1.1
                                                                        
  b- Other incompatibility changes:                                     
                                                                        
     Users of SAS ITSV V1 and V2.0 and SAS/CPE must install the two line
       circumvention described in the text of Change 15.320 to use MXG  
       Version 15.08 or later.  SAS ITSV Version 2.1 is compatible and  
       the circumvention is not required.                               
                                                                        
                                                                        
  c- These products were incompatibly changed by their vendor, and they 
     require MXG Version 15.xx as indicated:                            
                                                                        
      Boole's IMF 3.2 (for IMS 6.1)           MXG 15.09  Change 15.372  
      CICS TS V1.2                            MXG 15.06  Change 15.274  
      CICS TS V1.1 APAR UN98309               MXG 15.06  Change 15.258  
      Landmark TMON CICS 2.0                  MXG 15.06  Change 15.281  
      Landmark TMON MVS 2.0                   MXG 15.09  Change 15.346  
      NTSMF Version 2.1                       MXG 15.06  Change 15.249  
      255 Structures in a Coupling Facility   MXG 15.06  Change 15.226  
      BETA93 Release 1.3                      MXG 15.06  Change 15.237  
      IDMS 14.0                               MXG 15.05  Change 15.218  
      Coupling Facility more than 64 Structs  MXG 15.05  Change 15.226  
      APPC APAR OW16975 APAR-in-Error         MXG 15.05  Change 15.227  
      ObjectStar 3.0                          MXG 15.04  Change 15.195  
      NTSMF Version 2.0                       MXG 15.03  Change 15.147  
      DB2 Version 5.1.0 two SMF 102 IFCIDs    MXG 15.02  Change 15.095  
      Hitachi 7700 Cache R.R. records         MXG 15.01  Change 15.008  
                                                                        
 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 JCLINSTL.    
                                                                        
                                                                        
X.    Online Documentation of MXG Software.                             
                                                                        
    MXG Documentation is now described in member DOCUMENT.              
                                                                        
                                                                        
XI.   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 of the MXG SOURCLIB will always be more accurate than   
 the printed changes in a Newsletter, because the software is normally  
 created after the newsletter is sent to the printer!  Member CHANGES   
 on the www.MXG.com homepage are the most timely, as they are updated   
 (sometimes) between MXG versions.                                      
                                                                        
 Member CHANGES always identifies the actual version and release of     
 MXG Software that is contained in that library.                        
                                                                        
 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 can be made by paper).   
                                                                        
 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 after MXG 14.14 now in MXG 15.15:
                                                                        
  Dataset/                                                              
  Member   Change    Description                                        
                                                                        
  Many     15.167  MXG now protects ALL date fields for year 2000.      
  Many     15.169  SAS inconsistencies between MVS and ASCII fixed.     
  Many     15.320  Hardcoded PDB. DDname externalized with &PDBxx macro.
  Many     15.354  All VMACs for SMF records start with IF ID=....      
  Many     15.356  New &MACxxxx macro variable added to all VMACs.      
  Many     15.170  Support for OS/390 Version 2 Release 4 (COMPAT).     
  None     15.373  Support for OS/390 Version 2 Release 5 (no changes). 
  ADOC1415 15.304  Using 14/15 records to determine dataset size.       
  ADOCTAND 15.119  Cannot use Tandem's ftp program to upload Measure.   
  AIXPDS   15.337  Support for AIX commands IOSTAT/PSSTAT/VMSTAT.       
  ANALAVAL 15.262  Availability analysis example with PROC CALENDAR.    
  ANALBATW 15.378  'Batch Window' graphical reports from PDB.JOBS/STEPS.
  ANALCISH 15.365  CICS reports CICNQG, CICSLGS, CICLGR are added.      
  ANALCNCR 15.126  New example counts Avg and Max Logged on TSO Users.  
  ANALCNCR 15.174  ANALCNCR with large INTERVAL had large WORK space.   
  ANALDB2R 15.191  ANALDB2R fails, ERROR 31-185 if no PLAN in SORTBY.   
  ANALDB2R 15.223  Some datetimes shifted right two positions, overlay. 
  ANALDB2R 15.279  APPARENT MACRO &SORTUOW NOT RESOLVED error.          
  ANALDBTR 15.259  Pairing DB2 IFCID 59 & 63 wrong if multiple 63s.     
  ANALDBXX 15.173  Merge DB2 102s with DB2ACCT and CICSTRAN example.    
  ANALDDCN 15.062  Analysis of impact of DDCONS(NO)'s duplicate bytes.  
  ANALMULT 15.367  Corrected values of EXCPNODD/IOTMNODD for MULTIDD=Y. 
  ASMIMSLG 15.229  Archaic pre-DFP 3.0 systems retrofit.                
                                                                        
  ASMTAPES 15.047  ML-13 of ASMTAPES protects 0C4s, stays up, etc.      
  ASMTAPES 15.141  ASMTAPES ML-14 populates fields, protects 0C4s.      
  ASMTAPES 15.285  ML-15 adds dump suppression, OS/390 1.3 JCT changes. 
  ASMTAPES 15.291  MXG 15.06 did not contain ML-15; MXG 15.07 does.     
  ASMVVDS  15.302  Out of Storage eliminated, UCBs above 16MB           
  ASUMTALO 15.077  Exploitation of TALO Interval Records added by ML-12 
  ASUMTALO 15.301  Starting/Ending Interval counts include SPUN.        
  ASUMUOW  15.079  IRESPTM, ENDTIME corrected.                          
  ASUMUOW  15.221  Specific reference to TEMP01 caused error, removed.  
  ASUMUOW  15.307  MROTRAN count included "spun" observation counts.    
  ASUMUOW  15.315  ASUMUOW option to get real TRANNAME versus CPMI/CSMI.
  BUILDPD3 15.020  JES3 BUILDPD3 had extra observations created.        
  BUILDPD3 15.235  Duplicate step records might not be deleted.         
  BUILDPDB 15.235  Duplicate step records might not be deleted.         
  BUILDPDB 15.329  _CDExxxx macros reordered, now inside ELSE DOs.      
  CICINTRV 15.251  CICINTRV logic corrected, must use this version.     
  CLMXGSAS 15.084  Sample CLISTs for MXG and SAS execution under TSO.   
  CONFIG   15.194  MXG default for MEMSIZE raised from 48M to 64M       
  CONFIG   15.293  YEARCUTOFF=1960 is now MXG default, protects non-Y2K.
  DIFFDB2  15.070  DB2STATS values are negative in startup interval.    
  DIFFDB2  15.278  Variables B1HITRAT-B4HITRAT were wrong.              
  EXPDB30V 15.142  PDB exit EXPDB30V added for PDB.SMFINTRV.            
  FORMATS  15.057  New RACF events decoded by MG080EV.                  
  FORMATS  15.109  Format MGBYTRT (Byte per second) truncated on left.  
  FORMATS  15.152  Formats $MGHEX2H, $MGHEX4H, $MGHEX8H blanks '40'x.   
  FORMATS  15.175  CICS formats $MGCICDL,$MGCICDS corrected.            
  IHDR110  15.268  CICS Type 110 Header Exit for record selection.      
  IMACICBB 15.179  Support for Boole MainView for CICS stat records.    
  IMACICSM 15.157  Support for Shared Medical CICS Journal OASMON.      
  IMACKEEP 15.123  Member IMACKEEP is documented as archaic.            
  IMACPDB  15.002  Variable TERMIND added to PDB.STEPS.                 
  IMACPDB  15.048  Variables SMF6FDNM/SMF6PDNM (Formdef/PrintDef) kept. 
  IMACPDB  15.091  Variables ACTBYTES/ACTPAGES from TYPE26J2 in PDB.    
  IMACSHFT 15.151  Table of Holidays for SHIFT example added.           
  IMACUOW  15.221  SORT output destination, other options externalized. 
  IMACs    15.328  New _Sxxyyy "PROC SORT" macro defined in IMACs.      
  INSTALL  15.277  VM/CMS cannot use a MACLIB member for CONFIG option. 
  NTINTRV  15.255  Multi-processors properly summarized in NTINTRV.     
  RMFINTRV 15.138  Report RPGNs/Classes can be used in IMACWORK!!!      
  RMFINTRV 15.238  "ERROR. NEGATIVE CPU OVERHEAD TIME (TYPE70-TYPE72)". 
  RMFINTRV 15.250  Test CPUTM NE CPU72TM too strong due to truncation.  
  SMFPRM00 15.053  First draft of MXG recommendations for SMF parms.    
  TRND72GO 15.135  Trending for TYPE72GO WLM Goal Mode Service Classes. 
  TYPE102  15.113  DB2 Trace IFCID=125 logic revised.                   
  TYPE102  15.121  Negative values for DB2 fields decoded with format.  
  TYPE102  15.132  DB2 Trace dataset T102S106 now corrected.            
  TYPE102  15.216  DB2 Trace 102 subtype 140 INPUT STATEMENT EXCEEDED.  
  TYPE102  15.245  DB2 Type 102 Subtype 140 INPUT STATEMENT EXCEEDED.   
  TYPE102  15.245  Invalid Type 102 subtype 140 protection added.       
  TYPE103  15.313  Support for ICSS SMF type 103 (Websphere).           
  TYPE110  15.133  Leap Seconds support correct "GMT" to local.         
  TYPE110  15.258  APAR UN98309 CICS TS V1.1 INCOMPATIBLE               
  TYPE110  15.269  UOWTIME duplicate values, UOWIDCHR added to resolve. 
  TYPE110  15.274  Support for CICS Transaction Server 1.2 INCOMPATIBLE.
  TYPE116  15.043  TYPE116 variable QWHCTNO remains numeric.            
  TYPE116  15.241  MQ Series type 116 blank CICS TASKNR, questions.     
  TYPE116  15.241  Type 116 INVALID DATA FOR QWHCTASK message           
  TYPE1415 15.124  Support for APAR OW25263 (for 3590s)                 
  TYPE1415 15.239  New variable LASTVOFL flags if this is Last Volume.  
  TYPE16   15.243  Support for DFSORT APAR PN71137 (COMPATIBLE).        
  TYPE16   15.243  Support for DFSORT APAR PN71337 added flag fields.   
  TYPE26J3 15.228  APAR OW26297 adds job account fields to JES3 type 26.
  TYPE26J3 15.273  JES3 ACCOUNT fields in type 26 were not read.        
                                                                        
  TYPE28   15.336  Support for NPM 2.3 and APAR OW17876.                
  TYPE28   15.362  NPM type 28 subtype 82 error corrected.              
  TYPE30   15.063  TYPE30OM for OMVS discoveries                        
  TYPE30   15.065  EXCP/IOTM for UCB addresses over '8000'x wrong.      
  TYPE30   15.133  Leap Seconds support converts "GMT" to local.        
  TYPE30   15.227  APAR OW16975 INCOMPATIBLY in error, APPC type 30.    
  TYPE42   15.106  Support for APAR OW20921 creates TYPE42VT (VTOC+).   
  TYPE42   15.112  Support for APAR OW26451/OW26453/OW26497 MAXRSPTM+.  
  TYPE42   15.358  TYPE42AU dataset was incorrectly built.              
  TYPE50   15.185  Support for VTAM 4.4 changes to SMF type 50.         
  TYPE6    15.009  Support for APAR OW25152 (PRINTWAY Print Queue Name) 
  TYPE6    15.015  Support for Anacom's Anastack spooler type 6 SMF.    
  TYPE6    15.016  Support for CA-DISPATCH Version 6 w/5-digit JSENR.   
  TYPE6    15.039  Invalid "MVS PSF DOWNLOAD" type 6 records, APAR.     
  TYPE6156 15.176  Support for Invalid Catalog Cell '05'x segment.      
  TYPE6156 15.193  Another invalid '04' Catalog Cell STOPOVER.          
  TYPE6156 15.222  INPUT STATEMENT EXCEEDED, Change 15.166 was wrong.   
  TYPE7072 15.004  OS/390 R3 type 72 INPUT STATEMENT EXCEEDED RECORD.   
  TYPE7072 15.013  Variable SSTORE72 (Shared Pages Bytes) created.      
  TYPE7072 15.023  TYPE70 variable PCTMVSBY wrong in MDF shared CPUs    
  TYPE7072 15.026  New variable VELONOIO calculates NO I/O Velocity.    
  TYPE7072 15.038  TYPE72GO PERFINDX, R723CIRC and R723CICT wrong.      
  TYPE7072 15.182  TYPE72GO VELOCITY wrong for Discretionary/System     
  TYPE7072 15.183  TYPE72GO was OUTPUT when NOACTVTY was zero.          
  TYPE7072 15.214  TYPE70 PCTMVSBY incorrect MXG 15.01-15.04.           
  TYPE7072 15.270  OS/390 R2.4 Goal MODE INVALID DATA FOR R723CIDT/CDQT 
  TYPE70PR 15.299  TYPE70PR had no obs for deactivated partition.       
  TYPE71   15.064  Variable SLOTUTIL added to TYPE71 - slot usage       
  TYPE72GO 15.297  VELOCITY variables are now multiplied by 100.        
  TYPE74   15.008  Support for Hitachi 7700 Cache Records (INCOMPAT)    
  TYPE74   15.011  Variable SMF744PN added to TYPE74CF to count CPUs.   
  TYPE74   15.058  Cache TYPE74CA clean up and new variables added.     
  TYPE74   15.226  Support for SMF type 74 CF more than 64 structures.  
  TYPE78   15.061  PCTDIRPT/PCTCUBSY in TYPE74CF wrong.                 
  TYPE80A  15.107  Dataset TYPE8025 now created for RACF Event 25.      
  TYPE80A  15.158  Support for RACFEVNT=22 and 59, repeated segments.   
  TYPE80A  15.309  RACF RVARY INPUT STATEMENT EXCEEDED 1.0.9.2 release. 
  TYPE88   15.257  Support for subtype 11 type 88 System Logger.        
  TYPE90   15.267  Variable SMFRECNR is now kept.                       
  TYPE91   15.213  Support for SMF type 91 subtype 21 SMARTBATCH data.  
  TYPE92   15.003  OMVS file GMT datetimestamps now converted to local. 
  TYPE94   15.073  Support for Virtual Tape Server additions to SMF 94. 
  TYPE94   15.130  TYPE94 variable SMF94ETO restored.                   
  TYPE99   15.165  Support for "Goal Mode SMF" type 99 subtype 6.       
  TYPE99   15.357  Support for APAR OW29790.                            
  TYPEACF2 15.197  ACF2JR dataset variable ACLFLDVL populated.          
  TYPEAIMR 15.311  Support for Fujitsu's AIM V20 AIM/RDBII SMF type 98. 
  TYPEBBMQ 15.263  Support for Boole & Babbage MQ Series VSAM file.     
  TYPEBETA 15.181  INVALID ARGUMENT in BETA93 SMF record *RELOAD*.      
  TYPEBETA 15.237  Support for BETA93 Release 3.1 (INCOMPATIBLE).       
  TYPECACH 15.008  Support for Hitachi 7700 Cache Records (INCOMPAT)    
  TYPECIMS 15.033  ABENDSYS/ABENDUSR in IMF 1.3+ is corrected.          
  TYPECIMS 15.082  Support for Boole and Babbage IMF 3.2 (for IMS 6.1.) 
  TYPECIMS 15.372  Support for Boole's IMF 3.2 (for IMS 6.1) INCOMPAT   
  TYPECMF  15.187  Variable C279SSI changed from numeric to character.  
  TYPECMF  15.376  CMF Subtype 15 now creates CMF16MAP & CMF16LPA.      
  TYPECMF  15.377  CMF Cache dataset CMF27CSC now contains CMF27C93.    
  TYPECMFV 15.380  Boole & Babbage CMF VSAM History File supported.     
  TYPECTCP 15.248  Support for Applied Expert Systems Clever TCP/IP.    
  TYPECTLG 15.166  Support for Catalog Cell 'E7' (Alias).               
  TYPECTLT 15.276  IOA/Control-T 5.0 variable DSEXPDT changed.          
  TYPECTLT 15.306  CONTROL-T vars DSUSECT/DSEXCP wrong, undoc bytes.    
  TYPEDB2  14.095  Support for DB2 Version 5.1.0 (COMPATIBLE).          
                                                                        
  TYPEDB2  15.133  Leap Seconds support correct "GMT" to local.         
  TYPEDB2  15.269  UOWTIME duplicate values, UOWIDCHR added to resolve. 
  TYPEDCOL 15.108  High Used RBA can be greater than Allocated Space.   
  TYPEDCOL 15.163  Support for DCOLLECT in DFSMS 1.4 (COMPAT).          
  TYPEDCOL 15.324  VOLSER added to DCOLLECT DCOLCLUS dataset.           
  TYPEDPPX 15.305  Support for DPPX/370 Performance Reporter output.    
  TYPEEDGR 15.140  Support for new fields in DFSMSrmm extracts.         
  TYPEEDGS 15.021  Variables EDGSADTE,EDGSARSD,EDGSASID, formats value. 
  TYPEEREP 15.246  EREP records past logical EOF were read from DASD.   
  TYPEFTEK 15.102  Support for Filetek Optical Disk SMF record          
  TYPEHMF  15.192  Support for HMF SMF Subtype 11 (DS3 Statistics).     
  TYPEHPTE 15.247  Support for HP MeasureWare for Terra Data OS.        
  TYPEHURN 15.195  Support for ObjectStar 3.0 (INCOMPATIBLE).           
  TYPEICE  15.134  Support for IXFP SMF subtypes 6 and 7                
  TYPEICE  15.215  IXFP subtypes 2,3,4 not output, MXG 15.02-15.04 only.
  TYPEIDMJ 15.363  Support for IDMS Journal format for IDMS V12.        
  TYPEIDMS 15.218  Support for CA's IDMS 14.0 (INCOMPATIBLE).           
  TYPEIDMS 15.264  IDMS 10.02 observations not output.                  
  TYPEIMFL 15.375  Read IMF + SAP + IBM IMF log records at one time.    
  TYPEIMSD 15.081  Support for IMS DBCTL transactions from IMS 07/08s.  
  TYPEM204 15.303  Support for MODEL204 Version 3.4 INCOMPATIBLE.       
  TYPEMEMO 15.071  Support for MEMO subtype 8, creates MEMODIST dataset 
  TYPEMIM  15.059  Segments not output after MIMCNT=0 with MIM V 3.     
  TYPEMON2 15.281  Support for Landmark's The Monitor for CICS/ESA 2.0. 
  TYPEMWSU 15.068  Revised support for HP's MeasureWare for SUN         
  TYPEMWTE 15.247  Support for HP MeasureWare for Terra Data OS.        
  TYPEMWUX 15.022  HP-MW and HP-PCS base date now JAN1970 vice JAN70.   
  TYPENSPY 15.067  Support for NETSPY Version 5.0 is in MXG 14.14.      
  TYPENSPY 15.069  ARSPHOST missing in NSPYLU dataset for NETSPY 4.4    
  TYPENSPY 15.168  Zero obs in NSPYTIC3 corrected.                      
  TYPENTSM 15.012  NTSMF records from NT 3.51 now supported.            
  TYPENTSM 15.027  NTSMF new objects created by COMPAQ hardware.        
  TYPENTSM 15.147  Support for NTSMF Version 2.0 (INCOMPAT).            
  TYPENTSM 15.147  Support for Windows NT 4.0 Service Pack 2 (INCOMPAT) 
  TYPENTSM 15.190  Support for five new NTSMF Objects.                  
  TYPENTSM 15.220  Support for NTSMF Version 2.1 (COMPAT), new objects. 
  TYPENTSM 15.249  Support for NTSMF Version 2.1 (INCOMPATIBLE).        
  TYPENTSM 15.265  NTSMF Version 2.0.H caused INPUT STATEMENT EXCEEDED. 
  TYPEOMVT 15.150  INPUT STATEMENT EXCEEDED Omegamon VTAM 200 IRNUM=12. 
  TYPEOMVT 15.296  Support for Omegamon for VTAM V400 (COMPATIBLE).     
  TYPEOPC  15.188  OPC 3.1 datasets OPC23, OPC29, OPC31 corrected.      
  TYPEOPC  15.256  OPC type 29 INPUT STATEMENT EXCEEDED error.          
  TYPEPW   15.010  Support for Landmark's Performance Works/Smart Agent 
  TYPEQAPM 15.052  Support for all OS/400 Release 3.7.0 records.        
  TYPEQAPM 15.105  Dataset QAPMAPPN has variables wrong.                
  TYPEQAPM 15.127  AS/400 variable AS400SYN missing if SYSTEM LT 8.     
  TYPEQAPM 15.316  Support for OS/400 Release 4.1.0 (INCOMPATIBLE).     
  TYPERACF 15.103  Support for RACF utility IRRDBU00's OMVS RACF data.  
  TYPERDS  15.144  Zero observations in TYPERDS1-TYPERDS7 datasets.     
  TYPERMFV 15.321  Some RMF III VSAM variables were corrected.          
  TYPERMFV 15.355  CSA and SQA values were wrong; should be &RB.4.      
  TYPEROSC 15.017  Support for CA-ROSCOE Version 6 SMF is verified.     
  TYPESARX 15.300  Support for SAR CA-VIEW SMF exit SARSRQUX.           
  TYPESFTA 15.030  SOFTAUDIT collect only at JOB record was deleted.    
  TYPESTC  15.186  STK 4400, STCLMU variables decoded.                  
  TYPESVCC 15.200  Support for Peregrine's Service Center SMF.          
  TYPETCP  15.234  Support for TCP/IP 3.2 API Calls record changes.     
  TYPETMDB 15.114  TMON/DB2 subtype "DW" now supported.                 
  TYPETMDB 15.184  Support for TMON/DB2 record type "DE".               
  TYPETMNT 15.077  Support for new fields added by ML-12 of ASMTAPES.   
  TYPETMNT 15.110  Enhancements in preparation for ASMTAPES ML-14.      
  TYPETMO2 15.353  Landmark TMON for CICS V2 variables renamed.         
  TYPETMON 15.001  File counts incorrect in TYPETMON datasets.          
                                                                        
  TYPETMON 15.054  Variables SYSTEM/SYSID truncated to only one byte.   
  TYPETMON 15.139  Landmark CICS fix TT00032 creates one bad record.    
  TYPETMON 15.266  MXG 15.04-MXG 15.05 only. CREATIME, other dates wrong
  TYPETMON 15.294  SYSID was length five instead of length four.        
  TYPETMS5 15.199  Support for CA-1/TMS Release 5.2 (COMPATIBLE).       
  TYPETMV2 15.346  Landmark for MVS V2 INPUT STATEMENT EXCEEDED.        
  TYPEVLFC 15.230  Support for VLF Catalog activity from SYSLOG.        
  TYPEVM   15.189  Support for VM ADSM Account Records in VM/ESA.       
  TYPEWWW  15.086  Support for World Wide Web Common Log Format records 
  TYPEXPSM 15.172  Support for Xerox's XPSM Version 2 SMF records.      
  TYPEZARA 15.074  Support for Altai's ZARA Tape Management Release 1.2 
  TYPEZARA 15.323  Packed Decimals protected, DATELU corrected.         
  UDUMPEBC 15.085  Utility to produce MVS-like LIST; hex dump on ASCII. 
  UTILCONT 15.056  Now a %MACRO - displays SAS dataset sizes (in MB).   
  UTILUOW  15.335  CICS MRO - which CICSTRAN record has real TRANNAME.  
  UVBSNRDW 15.242  Utility to re-create SMF VBS with no RDW/BDWs.       
  UVBSNRDW 15.242  Utility to recreate VBS from data with no RDW/BDW.   
  VMAC80A  15.289  RACF DTP EV44xxxx variables added for RACFEVNT=13.   
  VMACIMSA 15.275  SAP IMS timestamp SAPTIMTR is Start of Transaction.  
  VMACSTC  15.364  Support for StorageTek's VSM SMF records.            
  VMACUCB  15.125  VIO detection conflict with DEVNR='7FFFF'x.          
  VMXGCOMP 15.100  %MACRO utility to compare SAS Data Libraries         
  VMXGOPTR 15.099  %MACRO to reset (most) SAS Options.                  
  VMXGSUM  15.098  Enhancement to protect OBS=0, and USER= options.     
  WEEKBLDT 15.115  Dataset TYPE77 causes failure, wrong BY list.        
  YEAR2000 15.045  DATETIMExx won't display yyyy if truncated.          
  YEAR2000 15.167  MXG now protects ALL date fields for year 2000.      
  YEAR2000 15.293  MXG cannot protect all non-Y2K-compliant dates.      
                                                                        
Inverse chronological list of all Changes:                              
                                                                        
                                                                        
===Changes thru 15.382 were printed in MXG NEWSLETTER THIRTY-THREE===   
===Changes thru 15.206 were included in MXG 15.04 dated Sep 01, 1997=== 
===Changes thru 15.206 were published in MXG NEWSLETTER THIRTY-TWO===== 
                                                                        
 All Changes are in member CHANGESS and all Newsletters are in NEWSLTRS.