* copyright (C) 1984-2019 merrill consultants dallas texas usa

DB2 10.1 Invalid Header pre APAR Jan 12, 2011 28.28

DFSMS/MVS 1.1 Mar 13, 1993 11.11

DFSMS/MVS 1.2 Jun 24, 1994 12.02

DFSMS/MVS 1.3 Dec 29, 1995 13.09

DFSMS/MVS 1.4 Sep 28, 1997 15.04

DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04

DFSMS/MVS 1.5 ??? ??, 1999 16.04

DFSORT SMF V1R5 Mar 1, 2006 24.02

MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02

MQ Series 1.2.0 May 26, 1998 16.02

MQ Series 2.1.0 Oct 2, 1999 17.07

MQ Series 5.2 Dec 16, 2000 18.10

MQ Series 5.3 Dec 16, 2002 21.05

MQ Series 6.0 Feb 14, 2006 23.23

MQ Series 7.0 ??? ??, 2009 *28.06

NETVIEW 3.1 type 37 ??? ??, 1996 14.03

NPM 2.0 Dec 17, 1993 12.03

NPM 2.2 Aug 29, 1994 12.05

NPM 2.3 ??? ??, 1996 15.08

NPM 2.4 Nov 18, 1998 17.01

NPM 2.5 Feb ??, 2000 18.02

NPM 2.6 Nov ??, 2001 19.06

RMDS 2.1, 2.2 Dec 12, 1995 12.12

RMDS 2.3 Jan 31, 2002 19.11

TCP/IP 3.1 Jun 12, 1995 12.12

TCP/IP 3.4 Sep 22, 1998 16.04

WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04

WebSphere 6.0 Feb 18, 2006 23.23

WebSphere 7.0 Oct 7, 2010 28.06

DOS/VSE POWER V6.3.0 Dec 19, 1998 16.08

VM/ESA 2.0 Dec 23, 1992 10.04

VM/ESA 2.1 Jun 27, 1993 12.02

VM/ESA 2.2 Nov 22, 1994 12.06

VM/ESA 2.3 Jun 1, 1998 16.08

VM/ESA 2.4 Mar 1, 2001 19.03

z/VM 3.1 Mar 1, 2001 19.03

z/VM 3.1 DATABYTE=0 May 2, 2002 20.02

z/VM 4.2 ?? May 2, 2002 20.02

z/VM 4.4 Jan 22, 2005 22.22

z/VM 5.1 Jan 22, 2005 22.22

z/VM 5.2 Jan 22, 2006 24.01

z/VM 5.3 TOLERATE Jun 7, 2007 25.05

z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08

z/VM 5.4 (COMPATIBLE) Sep 12, 2008 27.01*

z/VM 6.1 (NO CHANGES) Jul 7, 2008 27.01

IMS log 4.1 Jul 4, 1994 12.02

IMS log 5.1 Jun 9, 1996 14.05

IMS log 6.1 ??? ?, 199? 20.03

IMS log 7.1 ??? ?, 200? 20.03

IMS log 8.1 May 21, 2003 21.02

IMS log 9.1 Mar 96, 2004 26.01*

IMS log 10.0 Mar 06, 2007 26.01*

IMS log 11.0 Apr 1, 2010 28.02*

AS400 3.7.0 Nov 1, 1996 15.01

AS400 4.1.0 Dec 30, 1996 15.08

AS400 4.2.0 Apr 27, 1998 16.02

AS400 4.4.0 Sep 27, 1999 17.07

AS400 4.5.0 Jul 27, 2000 18.07

AS400 5.2.0 - Most records Jul 23, 2003 21.03

AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04

AS400 5.3.0 Jan 22, 2005 22.22

AS400 5.4.0 Aug 26, 2006 24.06

AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number

was changed (to the MXG version required), after an earlier

MXG version was listed as supporting this product release,

usually because an APAR modified the product's data records.

Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version

Product Name Required

Demand Technology

NTSMF Version 1 Beta 14.11

NTSMF Version 2.0 15.05

NTSMF Version 2.1 15.06

NTSMF Version 2.2 16.04

NTSMF Version 2.3 17.10

NTSMF 2.4.4 Aug 9, 2002 20.04

NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02

NTSMF 2.4.7 Sep 30, 2004 22.08

NTSMF 3.1.4 Mar 15, 2009 27.01

Landmark

The Monitor for DB2 Version 2 13.06

The Monitor for DB2 Version 3.0 16.02

The Monitor for DB2 Version 3.1 20.04

The Monitor for DB2 Version 4.0 22.10

The Monitor for CICS/ESA 1.2 - 12.12

The Monitor for CICS/ESA 1.3 - 15.01

The Monitor for CICS/ESA 2.0 - 15.06

The Monitor for CICS TCE 2.1 - 20.04

The Monitor for CICS TCE 2.2 - 20.335, 21.134 21.04

The Monitor for CICS TCE 2.3 including CICS/TS 3.1 22.08

The Monitor for CICS TCE 3.2 (almost all) 25.11

The Monitor for CICS TCE 3.2 (almost all) 27.01

The Monitor for MVS/ESA 1.3 - 12.05

The Monitor for MVS/ESA 1.5 - 12.05

The Monitor for MVS/ESA 2.0 - 15.09

The Monitor for MVS/ESA 3.0 - 19.19

The Monitor for CICS/TS V2.3 for CICS/TS 3.1 22.08

Candle

Omegamon for CICS V200 User SMF 12.05

Omegamon for CICS V300 User SMF 13.06

Omegamon for CICS V400 User SMF 16.02

Omegamon for CICS V400 type 110 segments 16.02

Omegamon for CICS V500 User SMF 18.01

Omegamon for IMS V110 (ITRF) 12.12

Omegamon for IMS V300 (ITRF) 14.04

Omegamon for IMS V550/V560 (ITRF) 25.05

Omegamon for MVS V300 13.05

Omegamon for MVS V400 13.06

Omegamon for DB2 Version 2.1/2.2 13.05

Omegamon for VTAM V160 12.04A

Omegamon for VTAM V400 15.15

Omegamon for VTAM V500 18.08

Omegamon for SMS V100/V110 12.03

CA

ACF2 6.2 16.04

ASTEX 2.1 14.04

NETSPY 4.7 14.03

NETSPY 5.0 14.03

NETSPY 5.2 16.05

NETSPY 5.3 18.03

NETSPY 6.0 20.10 20.305

NETSPY 7.0 20.10 20.305

SAR/VIEW R11 23.07 23.196

BMC, was Boole & Babbage

IMF 3.1 (for IMS 5.1) 12.12

IMF 3.2 (for IMS 6.1 only) 15.09

IMF 3.2 (for IMS 5.1 and 6.1+) 16.04

IMF 3.3 (for IMS 7.1 and 8.1) 22.08*

IMF 4.1 (for IMS 9.1) 26.02*

IMF 4.4 (for IMS 9.1) 27.07*

Memorex/Telex

LMS 3.1 12.12A

Oracle V9, V10 24.06

Amdahl

APAF 4.1, 4.3 16.08

Velocity Software

XAMAP 3.4 22.10

XAMAP 3406 24.03

XAMAP 3.7 27.10

V. Incompatibilities and Installation of MXG 28.28.

1. Incompatibilities introduced in MXG 28.28:

a- Changes in MXG architecture made between 28.28 and prior versions

that can introduce known incompatibilities.

1. -The WEEKBLD/MONTHBLD may fail with TYPE72DL NOT SORTED if you

have a tailored WEEKBLD/MONTHBLD that references TYPE72DL. The

only prevention is to change the sort order in WEEKBLD/MONTHBLD

BEFORE you create your weekly with 28.28 to this order:

MACRO _DSET TYPE72DL %

MACRO _BYLIST SYSPLEX SYSTEM SYSNAME STARTIME %

to eliminate the exposure to this rare possible error.

-Or, the WEEKBLD/MONTHBLD sort order testing can be disabled

(as documented in comments) using:

//SYSIN DD *

%LET MXGNOBY= MACRO _BY % MACRO _SORTBY % ;

%INCLUDE SOURCLIB(MONTHBLD);

-Or with BLDSMPDB, specify SORTEDBY=NO to disable the sort test.

See Change 28.324.

2. -If you use ASUMDB2x or ASUMDBSx datasets, see Change 28.220.
3. -If you have tailored MXG DB2 Processing using _NDB2 and then

invoke _SDB2STS (to create PDB.DB2STATS), you must also have

MACRO _WDB2ST4 DB2STAT4 % inserted AFTER the _NDB2 so that

the PDB.DB2STAT4 dataset exists when PDB.DB2STATS is created.

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 JCLINST9 for

SAS Version 9.

MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either

COMPAT the location or the format of all of the previously-

kept MXG variables is COMPATIBLE, and you can continue

to run the old version of MXG software, which will read

the new records without error, but none of any new data

fields or any new record subtypes will be created/kept

until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG

version to fail, visibly or invisibly, with or without

error conditions or messages, and the output datasets

may contain wrong values and incomplete observations,

and/or observations may have been lost.

You MUST install the new MXG Version with this change

to process data records that have been INCOMPATIBLY

changed by their vendor.

TOLERATE In other words, the old MXG Version TOLERATES the new

data records, if they are COMPATIBLY changed.

EXPLOIT Once you use the new MXG Version to read the changed

records, all of the new fields, subtypes, etc, that are

described in this change will be created in the MXG

datasets, so the new MXG Version EXPLOITS the new data,

and you have full support of the new data records.

VI. Online Documentation of MXG Software.

MXG Documentation is now described in member DOCUMENT.

See also member INDEX, but it may be overwhelming.

VII. Changes Log
--------------------------Changes Log---------------------------------
You MUST read each Change description to determine if a Change will

impact your site. All changes have been made in this MXG Library.

Member CHANGES always identifies the actual version and release of

MXG Software that is contained in that library.

The CHANGES selection on our homepage at http://www.MXG.com

is always the most current information on MXG Software status,

and is frequently updated.
Important changes are also posted to the MXG-L ListServer, which is

also described by a selection on the homepage. Please subscribe.

The actual code implementation of some changes in MXG SOURCLIB may be

different than described in the change text (which might have printed

only the critical part of the correction that need be made by users).
Scan each source member named in any impacting change for any comments

at the beginning of the member for additional documentation, since the

documentation of new datasets, variables, validation status, and notes,

are often found in comments in the source members.

Alphabetical list of important changes in MXG 28.28 after MXG 27.27:

Dataset/

Member Change Description

Many 28.175 Support for z/OS 1.12 (COMPATIBLE)

ANALCAPD 28.169 Estimate the impact of a Defined Capacity Limit.

ANALDB2R 28.004 Extreme Detail DB2 Trace Report PMTRC01 revised.

ANALDB2R 28.146 Major enhancement to DB2PM-like reporting.

ANALDB2R 28.214 ANALDB2R report select did not honor BEGTIME/ENDTIME.

ANALDBJS 28.290 DB2 analysis adds JESNR and REAdTIME to DB2ACCT.

ANALDUPE 28.308 Removal of Duplicate SMF (or any) records.

ANALID 28.257 ERROR: VARIABLE IDANDSUM ... with PDB,DISP=OLD

ANALZPCR 28.021 Major fixes/enhancements for complex zPCR models.

ASMIMSL6 28.066 Support for IMS Version 11 (INCOMPATIBLE).

ASMTAPEE 28.041 Do NOT use ASMTAPEE ML-45/46, CPU SPIKE: ML-47 fixed.

ASUMCICR 28.281 Count/average response time by DATE for each APPLID.

ASUMDB2- 28.220 DB2 Summary ASUMDBxx and Trending TRNDDBxx revisions.

ASUMTAPE 28.008 Large size SPIN.SPINMOUN,SPIN.SPINSYSL found, shrunk.

ASUMTAPE 28.008 SPIN.SPINSYSL dataset could grow forever.

ASUMUOW 28.124 WTIRIOTM in PDB.ASUMUOW could be larger than IRESPTM.

ASUMUOWT 28.284 ASUMUOWT (for ASG-TMON MRO) revised to use VMXGUOW.

BLDSMPDB 28.125 Support for Week/Month if first-day-of-week NOT MON.

BLDSMPDB 28.177 Continued minor enhancements.

BLDSMPDB 28.218 Includes ASUMDBAA/TRNDDBAA caused errors, replaced.

BUILDPDB 28.037 PDB.SMFINTRV will have EXCP/IOTM counts for FLUSHED.

BUILDPDB 28.071 PDB.STEPS/PDB.JOBS duplicates if FLUSHED steps.

BUILDPDB 28.139 Recently added SMF30xxx variables kept in PDB.STEPS.

BUILDPDB 28.305 PDB.NJEPURGE did not contain all NJE-variables.

CONFIGVx 28.128 ERROR APPARENT MACRO TRIM NOT RESOVED: DOCUMENTATION.

DB2ACCT 28.277 NETSNAME/UOWTIME only created for QWHCATYP=4 (CICS).

DFH$MOLS 28.223 JCL example to use IBM CICS decompression utility.

EXIT112 28.027* Do NOT assemble EXIT112 for SMF 110/112, use EXITCICS

EXITCICS 28.223 Support for DB2 V10 Compressed SMF records.

EXITCICS 28.251 ASMA144E Begin-to-continue due to char in col 72.

EXITCICS 28.298 EXITCICS decompresses SMF 100,101,102,110 and 112.

FIXTRNCD 28.049 TRANSCODE attribute can be added to old PDBs

FORMATS 28.082 UDDDDDD, $MGDDDDD and $MGDDDSN updated.

GRAFCEC 28.261 SAS/GRAPH example charts CEC Utilization by engine

IMACCADI 28.172 Support for CA-Dispatch V11 SMF 6 INCOMPATIBLE.

IMACICMR 28.032 Protect 200-byte CMRDATA on CICS/TS 3.2 (s/b 256).

IMACZDAT 28.174 Example to set ZDATE when you rebuild a past PDB.

JCLINSTT 28.328 Complete JCL example to ftp/unterse/install on z/OS.

JCLTEST9 28.330 Prelim 28.28 only, default ASUMUOW could fail.

MULTIPDB 28.168 Create a PDB library with all datasets from many PDBs

MXGSAS92 28.070 SAS 9.2 TS2M2 DSNAMES may have changed

READDB2 28.083 READDB2/ANALDB2R did not honor MACDB2H/MACKEEP.

READDB2 28.211 COPYONLY argument wrote ALL SMF records.

READDB2 28.250 COPYONLY logic now works.

SASAUTOS 28.194 Invalid 'BA'x in TRIM member on z/OS ERROR 22.

SMFRECNT 28.089 BUILDPDBs PDB.SMFRECNT now has bytes and counts.

TRNDDB2- 28.220 DB2 Summary ASUMDBxx and Trending TRNDDBxx revisions.

TYPE0 28.009 INVALID DATA FOR CVTTZ in z/OS 1.11 Type 0 fixed.

TYPE0 28.313 Variable CVTTZ in TYPE0 could be one second wrong.

TYPE102 28,206 APPTUNE SMF 102 IFCID 8133 invalid offset ERROR.

TYPE102 28.116 Support for SMF 102 IFCID 263 decodes unique fields.

TYPE102 28.156 Support for IFCID=27 specific variables.

TYPE102 28.325 DB2 SQL-text variables only 100 bytes if COMPRESS=NO.

TYPE103 28.036 TYPE1032 deaccum needed PORTNR, label changed.

TYPE110 28.087 Internal Decompression Algorithm use now ERROR:'d.

TYPE110 28.134 INVALID STIDLEN=0 after STID=116 was harmless, fixed.

TYPE110 28.154 Improved detection of EXCLUDED CICS fields.

TYPE110 28.247A Example using _Kdddddd to create new datasets revised

TYPE110 28.285 CICS Statistics Subtype 2 STID=143 corrected.

TYPE111 28.329 CTG records had zero observations in TY111CXI "IPIC".

TYPE113 28.075 John Burg formulas for TYPE113 HIS data are added.

TYPE113 28.140 Major revision to SMF 113 support, TYPE70PR vars add.

TYPE113 28.166 Major revision - TYPE113 - John Burg's SHARE 2010.

TYPE113 28.226 Variable LPBUSY,LPARBUSY replaced LPARCPU.

TYPE113 28.279 "Near duplicate" ASUM113 intervals are corrected.

TYPE116 28.221 WebSphere MQ 7.01 INVALID WQ SEGMENT error messages.

TYPE119 28.175 Support for SMF 119 new subtypes 32-37 and 48-52.

TYPE119 28.293 Support for OpenSSH SMF 119 subtypes 96-98.

TYPE120 28.038 SMF 120 SUBTYPE 9 INPUT STATEMENT EXCEEDED RECORD

TYPE120 28.133 Support for WebSphere SMF 120 Subtype 20, untested.

TYPE120 28.258 Support for WebSphere ID=120 SUBTYPE=20 records

TYPE30 28.031 z/OS 1.11 GA added variables to SMF 30 and SMF 71.

TYPE30 28.246 New CPITCxTM/CPISRxTM wrong in MXG 28.06.

TYPE30 28.302 TYPE30MU duplicate records exist, non-dupes removed.

TYPE42 28.072 TYPE42X4 Above the BAR LRU dataset variables wrong.

TYPE42 28.150 Type 42 subtype 15 correction for TYPE42S1 dataset.

TYPE42 28.158 Support for APAR OA31648 TYPE42D1/D3 buff get retries

TYPE6156 28.289 Variables GATLIMIT and GATCNT added to TYPE6156.

TYPE70 28.175 Support for z196: INCOMPAT ONLY WITH GT 64 ENGINES.

TYPE7072 28.099 Variable CPULHKTM, CPU TIME Lock Promoted, TYPE72GO.

TYPE7072 28.242 In-Ready Work Unit SMF70U00-U15, etc were all wrong.

TYPE7072 28.246 CP eng 64-95 vars shouldn't have been kept in TYPE70.

TYPE70EN 28.224 TYPE70EN PCTCPUBY was 100% for a parked CP engine.

TYPE70EN 28.299 Wrong values for CPUID=0 in PDB.TYPE70EN.

TYPE74 28.039 R7451RID now one byte, R7451FLG/TYPE74CA overlays.

TYPE74 28.208 R7451TIM wrong, R7451CT3/CT4/PRT/PWT also wrong.

TYPE74 28.212 TYPE74ID (small) created, saves pass of TYPE74CA.

TYPE80A 28.107 TOKDANAM LDAPHOST,BINDDN,BINDPW,APPLNAM,UTYPE,JPNUM.

TYPE84 28.077 Support for all JES3 JMF TYPE84 subtypes.

TYPE89 28,282 Support for APAR OA31615, adds zIIP/zAAP CPU times.

TYPE89 28.015 Support for z/TPM SMF 89 record, subtype wrong byte.

TYPE89 28.272 SMF89HOF/SMF89DTO for SCRT don't use last 3 nybbles.

TYPE89 28.304 SMF 89 with no usage segment INPUT EXCEEDED error.

TYPE89 28.331 INVALID DATA FOR SMF89CZT if APAR OA31615 installed.

TYPE92 28.106 SMF92PPN, Path Name, was blank.

TYPECIMS 28.028 BMC IMF INPUT STATEMENT EXCEEDED, short record.

TYPECIMS 28.084 BMC IMF INPUTCLS and LASTCLAS variables restored.

TYPECTCP 28.108 Support for CleverView for TCP/IP TN3270 SMF subtype.

TYPECTCP 28.160 Support for CleverView GMT offset, CTCPIPAD fixed.

TYPEDB2 28.010 Variable SHIFT (from QWHSSTCK, END) kept in datasets.

TYPEDB2 28.051 Support for DB2 APAR PK62161 new SQL Counters.

TYPEDB2 28.073 DB2STATS had missing values for QW0225 variables.

TYPEDB2 28.222 ITRM only, DB2STAT4 NOT SORTED ERROR.

TYPEDB2 28.264 Support for DB2 Version 10. COMPLETELY INCOMPATIBLE.

TYPEDB2 28.326 Invalid DB2 V10 Distributed Header protected in MXG.

TYPEEDGR 28.029 RMM datetime vars have always been wrong time zone.

TYPEIMFS 28.137 Support for BMC IMF records written in SMF format.

TYPEIMFS 28.193 Full support for IMF records in SMF format.

TYPEIMS 28.131 IMS Log 56X record subtype 15x INVALID DATA/STOPOVER.

TYPEIMS 28.165 LCODE=56x TPCPSSTY09x INPUT STATEMENT EXCEEDED.

TYPEIMS7 28.066 Support for IMS Version 11 (INCOMPATIBLE).

TYPEIMS7 28.310 Support for IMS/DBCTL transactions in IMS0708.

TYPEIMSA 28.311 Support for IMS/DBCTL transactions in IMSTRAN.

TYPEITRF 28.162 Support for ITRF V420 IF2 (COMPATIBLE).

TYPEITRF 28.227 INPUT STATEMENT EXCEEDED RECORD LENGTH type=17x.

TYPEMIM 28.262 Support for CA MIM RESOURCE SHARING R11.7 (COMPAT)

TYPEMVAO 28.118 Support for BMC Mainview Auto Operator data file.

TYPEMVCI 28.065 Support for BMC CICS CMRDETL C660 for CICS/TS 4.1

TYPEMXI 28.126 Support for Rocket Software MXG User SMF record.

TYPENDM 28.327 Connect Direct/NDM 'RT' record INCOMPATIBLY changed.

TYPENMON 28.176 Support for SARMON - Solaris SAR in NMON format.

TYPENMON 28.275 Support for NMON FCREAD/FCWRITE/XFERIN/XFEROUT record

TYPENTSM 28.042 New Sentry VM 3.1.4.3 adds VMWARE objects/metrics.

TYPENTSM 28.119 Support for Performance Sentry NTSMF Version 3.1.4.4.

TYPEOMMQ 28.263 Support for IBM/OMEGAMON XW MQ flat file (INCOMPAT)

TYPERMVV 28.048 RMFV CPUG3 was misaligned in z/OS 1.11

TYPESAVR 28.127 Support for revised CA $AVERS SMF record (INCOMPAT).

TYPESTC 28.005 Support for Sun StorageTek VSM Version 6.2 and 7.0.

TYPESTC 28.005 Support for Sun StorageTek Version 6.2 and 7.0

TYPESTC 28.244 STC/STK/Oracle VSM user SMF records support revised.

TYPESVIE 28.138 Support for SysView Subtype 3 records.

TYPETCP 28.300 TYPETCP (SMF 118) Port Numbers (Dec) wrong on ASCII.

TYPETMNT 28.079 WARNING: TOTAL LENGTH OF VARIABLES MUST BE LT 32760.

TYPETMS 28.040 CA-1 Retention and VMRECORD extensions, need data.

TYPETMS5 28.148 TMS DEVTYPE was blank for TRTCH 'F0'x thru 'FF'x.

TYPETMVT 28.287 Support for ASG-TMON for VTAM subtype 'SX' record.

TYPETNG 28.216 NSM RH018 defective records with zero values.

TYPETNG 28.273 Support for more than 9999 instances in CA NSM/TNG.

TYPETPFC 28.152 Support for zTPFC TPF Continuous Monitoring updates.

TYPETPX 28.260 IP address and Port Number now decoded in TPX SMF.

TYPEVM 28.157 Support for VM ACCOUNT ID='09' ISFC record.

TYPEVMXA 28.025 MXG CPU Loop in TYPEVMXA, new CEX3C PRCAPMCT=9 crypto

TYPEVMXA 28.307 Short LINUXKRNL MONWRITE record caused errors.

TYPEVMXA 28.315 PFXCPUAD in VXSYTCUM is the LCPUADDR, no CPUID.

TYPEWPMO 28.086 Support for Windows Performance Monitor PERFMON file.

TYPEXAM 28.153 XAM TCP dataset's TOTCPU incorrectly divided by 100.

TYPEZCOS 28.151 Support for zCost AutoSoftcapping V 1.5.00 SMF.

TYPEZTPF 28.043* zTPF has major revisions in Performance Data

UTILBLDP 28.209 INCLAFTR=BUILD005,BUILDPDB=NO failed.

UTILEXCL 28.259 Spurious "WRONG LENGTH OF 200 FOR CMRDATA"

UTILGETM 28.312 No Reporting Class data in SMFSMALL with NRECORD=10.

UTILNPRT 28.268 Identify non-print chars, for SAS Enterprise Guide.

UTILPDSL 28.179 Utility to read PDS/PDSE directories of a concat.

UTILWORK 28.123 Utility for TYPE72GO to assist workload definitions.

VGETDDS 28.014 Colon in DDNAMES= worked only with DDNAMES=PDB:)

VGETOBS 28.034 %TRIM() references here removed, still in VMXGSUM.

VMXGFIND 28.012 Kewl tool, find all obs in all datasets meeting test.

VMXGINIT 28.023 MXGERROR/USER ABEND 990 if NOWORKINIT is enabled.

VMXGINIT 28.057 ERROR MACRO %ABORT IS NOT IMPLEMENTD, SAS 8.2 ONLY.

VMXGINIT 28.081 OPTIONS VARLENCHK=NOWARN eliminates SAS V9.2 WARNINGS

VMXGSET 28.098 DSETOPT= optional argument for data set options.

VMXGSRCH 28.147 Kewl Tool. Find all instances of VARIABLE='VALUE'.

VMXGSUM 28.105 Optional KEEPWEEK/MNTH/YEAR/DAYS/AFTER keeps TRENDs.

VMXGSUM 28.249 VMXGSUM enhanced with MODE and MEDIAN statistics

WEEKBLD 28.324 WEEKBLD/MONTHBLD/BLDSMPDB dataset TYPE72DL NOT SORTED
See member CHANGESS for all changes ever made to MXG Software.

Inverse chronological list of all Changes:

NEXTCHANGE: Version 28.
====== Changes thru 28.331 were in MXG 28.28 dated Jan 18, 2011=========
Change 28.331 INVALID DATA FOR SMF89CZT if APAR OA31615 is installed.

VMAC89 Change 28.282 claimed support, but without test data, and

Jan 15, 2011 the error was because MXG input SMF89CNO as two bytes but

it is a four byte field, causing the misalignment.

Jan 19: I didn't get records in time for 28.28 and this

change did NOT correct this error, but Change 29.002 did.

Thanks to Scott Barry, SBBWorks, USA.
Change 28.330 Prelim 28.28 default ASUMUOW in JCLTEST9 (does NOT read

VMXGUOW ANY input) failed, on all platforms with SAS V9.1.3 or on

Jan 15, 2011 SAS V9.2 on z/OS. There is NO error if you have IMACUOW

tailored to create observations in PDB.ASUMUOW. The

error message is a NO BY VARIABLES ERROR, but the actual

error was a DATA SET NOT FOUND error that was masked by

the OPTIONS NODSNFERR in VMXGUOW. Changes 28.316/28.284

added logic to print an MXGWARN when there was no input,

by creating a second dataset in an existing DATA step,

but that second dataset is NOT created when OPTIONS OBS=0

is set and the first dataset is a /VIEW, unless SAS V9.2

on Windows/Unix is used. The SAS defect was fixed only

for ASCII V9.2, but is now reopened by SAS Tech Support.

But MXG code was revised to eliminate the second dataset,

and tests now are for dataset existence rather than for

non-zero observations.

And why didn't MXG QA catch the error? Because we tailor

IMACUOW to create observations, which didn't fail.

Thanks to Mike Rounceville, Blue Cross Blue Shield of NC, USA
Change 28.329 CTG records had zero observations in TY111CXI "IPIC"

VMAC111 because MXG's length test was incorrect. The Version 8

Jan 14, 2011 documentation has several new fields that are now input

Jan 19, 2011 if the record length test is satisfied.

Jan 19: The VMAC111 was NOT updated in time for MXG 28.28

because I had no test data for validation; this update is

now made, but there are still no observations in either

TY111CXI or TY111CXE datasets because there are no SMF