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

See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for

current MXG Technical Notes.

All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Versions

The current version nomenclature is SAS 9.4 TS1M3 (9.4M3) printed

as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for

"SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled),

for SAS 9.4 Maintenance Level M3 and m2.
SAS V9.4 M3 Is RECOMMENDED, but MXG executes without error using

SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.

SAS V9.4 M2 is USABLE. SAS 9.4 M2 is at LEVEL A SAS Support

SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support

SAS V9.3 SAS 9.3 TS1M2 is USABLE. SAS 9.3 TS1M1 works.

But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,

see CHANGE 29.169, IS REQUIRED:

The %MACRO compiler error is in processing %LET

statements. While only two MXG members failed

repeatedly in MXG QA tests on z/OS, there were random

%LET errors in ASCII QA tests, so ANY use of %LET

statement on ANY platform are vulnerable to this

error, as the %MACRO compiler is SAS portable code,

used on all platforms. So this is NOT just an MXG

error, but impacts ALL SAS programs.

SAS9.3 is LEVEL A support from SAS.

SAS V9.2 Was recommended, prior to 9.3, and was error-free with

MXG 26.03. SAS Hot Fix for SAS Note 37166 is required to

use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2

Decompression Infile Exit, but SAS V9.2 does execute ok.

9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.

SAS V9.1.3 must be at Service Pack 4. Additionally, on z/OS 1.10

only, 9.1.3 requires SAS Hot Fix for SN-35332.

9.1.3 is support level C by SAS Institute, Sep 30, 2013.

SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.

SAS V8.2 IS SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS

with SAS 8.2.

SAS 8.2 is Level C Support from SAS as of Dec 31, 2011.

JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used
***************************************************************

As documented in Change 27.356, for SAS V9.2 or later):

The standard SAS JCL Procedure can be used for MXG with SAS V9.2+

// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'

//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR

or you can continue to use the MXGSAS94 JCL Procedure example.

***************************************************************
MXG 26.03 thru MXG 34.07 will execute under the previously listed

SAS Versions on all supported platforms

Unrelated to the above SAS Note/Hot Fix, ODS users will want to

use MXG 29.06+, because SAS V9.3 did expose incompatibilities in

MXG code for ODS reporting, that were fixed in MXG Version 29.06.

See Changes 29.159 and 29.169.

And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,

the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).

Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors

can occur even though //XXXXXXXX DD is a valid SAS Data Library.

This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does

NOT occur with SAS V9.2, nor with z/OS 1.9. It can be

circumvented by adding a LIBNAME statement that specifies the

ENGINE name. See the Technical Note in Newsletters for SN-35332.

Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now

"Level C" support from SAS Institute, and there are known errors

in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;

While many MXG programs (accidentally) will still execute under

V8.2, I cannot guarantee that all of MXG executes error free.

PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!

If you are absolutely stuck on V8, you need to copy MXG member

V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.

MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by

SAS V8 or later, but any of those data libraries can be read or

updated by the SAS Versions that MXG Supports, above.

For SAS Version V9.3:

SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note

SN43828 is REQUIRED. See text of Change 29.159.

With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions

26.03 or later execute under SAS V9.3 on all platforms.

SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and

SAS V9.4 are interchangeable and can be read/written by any of

those versions, provided they are on the same platform.

BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the

same "platform" and attempting to read/use the FORMAT catalog

created on one of those "platforms" on the other "platform"

will error out to remind you of that difference!

SAS V9.4 did change some V9.3 ODS processing defaults and syntax

that might cause errors with MXG 29.05 or earlier; MXG 29.06,

Change 29.160 documents the major revisions made in MXG to fully

support ODS, and MXG 29.06 is STRONGLY recommended for ODS with

SAS V9.3 or SAS V9.4.

For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,

so you do need to use the new MXGSAS92 JCL Procedure for MXG,

but it still uses the CONFIGV9 configuration file.
****************************************************************

However, NEW, and documented in Change 27.356, with SAS V9.2+:

The standard SAS JCL Procedure can be used for MXG:

// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'

//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR

instead of using the MXGSAS92 JCL Procedure example.

****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,

and V9.4. "PDBs" can be read/written interchangeably between

these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS

and with NO ERRORS reported.

Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a

new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return

code). That warning is harmless (to MXG code) and all MXG

created SAS datasets were correct, even with that warning.

The ONLY exposure was ONLY on z/OS, and ONLY if condition code

tests are used in your MXG jobstreams.

SAS Version 9.2 requires z/OS 1.7 or later, both officially as

documented by SAS Institute, and actually as V9.2 fails with 0C4

under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does

not support long length character variables, it can't be used.

SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:

SN-013514 is REQUIRED to be able to read datasets that were

created by V6SEQ (tape) engine.

SN-012437 is REQUIRED to prevent creation of corrupt/unreadable

datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.

Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT

SAFE without those two hot fixes, and if you do NOT have those

two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.

With MXG 23.02 or later, V9SEQ is the default sequential engine

specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2

you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required

as an absolute minimum level when that SAS Version was last

supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:

V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.

V8SEQ was always safe under SAS V8.2, but it wasted CPU time

by always compressing when writing in tape format.

V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ

should no longer be used, as it does not support long

length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and

Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,

but MXG users execute MXG on MANY (ALL??) SAS platforms, including

AIX, Linux, and other 'nix' variants, on many different hardware

platforms, and since they all work we don't need to list them. If

SAS executes so does MXG.

Prior QA tests have been run with all SAS releases available at

that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,

and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS

platform without errors! Each new MXG version is also tested with

the SAS ITSV/ITRM product by the ITRM developers.

III. WPS Version requirement information:

WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.

and other errors with 3.00 or 3.01 have been corrected in the

current WPS version.

WPS Version 3.01.1 maintenance level 731 required for PDB to tape

WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.

WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.

WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.

WPS Version 3.0 requires MXG 31.09 (see Change 31.251).

WPS Version 2.4 required MXG 27.09 (see Change 27.239).

WPS Version 2.3.5 required MXG 27.05.

See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"

when the LIBNAME PDB does not exist; there would also have been a

prior log message NOTE: Library PDB does not exist as the clue.

IV. MXG Version Required for Hardware, Operating System Release, etc.

MXG is usually NOT sensitive to z/OS Hardware changes, but:
The z/EC12 with 85+ engines required MXG 30.07.

Support for 255 engines was added in MXG 31.04.

The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was

INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to

read the SMT-format RMF records (which are written if you have zIIP

engines AND have enabled the new PROCVIEW CORE option for

Multi-Threading, even if only one thread is enabled).
The new zEDC compression hardware requires MXG 33.07 to support the

new metrics.

For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.

Availability dates for the IBM products and MXG version required for

error-free processing of that product's data records:
Product's

Availability MXG Version

Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8

MVS/ESA 4.2 Mar 29, 1991 9.9

MVS/ESA 4.2.2 Aug 15, 1991 9.9

MVS/ESA 4.3 Mar 23, 1993 10.10

MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02

MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01

MVS/ESA 5.2.0 Jun 15, 1995 13.05

MVS/ESA 5.2.2 Oct 19, 1995 13.09

OS/390 1.1.0 Feb 22, 1996 14.01

OS/390 1.2.0 Sep 30, 1996 14.05

OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14

OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02

OS/390 2.4.0 Sep 28, 1997 15.06

OS/390 2.5.0 Feb 24, 1998 15.06

OS/390 2.6.0 Sep 24, 1998 16.04

OS/390 2.7.0 Mar 26, 1999 16.09

OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03

OS/390 2.8.0 Aug 24, 1999 16.09

OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08

OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03

OS/390 2.9.0 Mar 31, 2000 18.03

OS/390 2.10.0 Sep 15, 2000 18.06

OS/390 PAV Oct 24, 2000 18.09

z/OS 1.1 Mar 30, 2001 18.11

z/OS 1.1 on 2064s Mar 30, 2001 19.01

z/OS 1.1 with correct MSU Mar 30, 2001 19.02

z/OS 1.2 Oct 31, 2001 19.04

z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05

z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02

z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02

z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03

z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03

z/OS 1.4 Tolerate Sep 27, 2002 20.03

z/OS 1.4 Support Sep 27, 2002 20.06

z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02

z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04

z/OS 1.5 Mar 31, 2004 21.21

z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10

z/OS IRD TYPE70PR Mar 11, 2004 *24.10

z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10

z/OS 1.6 - No IFAs Sep 30, 2004 *22.09

z/OS 1.6 - With IFAs Sep 30, 2004 *22.11

z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10

z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10

z/OS IFA data in RMF 79s Sep 30, 2005 23.10

z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03

z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06

z/OS More than 32 LPARs Jan 30, 2006 *24.24

z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24

z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02

z/OS IRD errors corrected May 15, 2006 24.03

z/OS ASUMCEC errors corrected May 15, 2006 *24.24

z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24

z/OS zIIP Processor Support Jun 22, 2006 *24.24

z/OS Dedicated zIIP Support Mar 8, 2008 *26.01

z/OS Dedicated zAAP Support Mar 8, 2008 26.01

z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24

z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10

z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10

z/OS new z10 variables Mar 5, 2008 26.01

z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10

z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10

z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07

z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10

z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05

z/OS 1.11 Sep 2, 2009 27.08

z/OS 1.11 New 30 variables Apr 14, 2010 *28.02

z/OS 1.12 Aug 17, 2010 *28.05

z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03

z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06

z/OS 1.13 Sep 30, 2011 29.03

z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08

z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01

z/OS 2.1 - Most Records support Jul 23, 2013 30.05

z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07

z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03

z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03

z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10

z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08

z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09

REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09

z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02

z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02

z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07

z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07

z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04

z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07

z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24

z9EC CPUs - CPUTYPE '2094'x:

with 64-bit z/OS - no change required *24.24

with 32-bit z/OS only: Aug 26, 2006 24.06

z9BC CPUs - CPUTYPE '2096'x:

with 64-bit z/OS - no change required 24.01

with 32-bit z/OS only: Jul 27, 2006 *24.24

z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11

z10 HiperDispatch/Parked Time Mar 3, 2008 *26.10

z196 (INCOMPAT IF GT 64 ENG) Aug 17, 2010 28.05

zEC12 Nov 14, 2012 30.07

z13 non-SMT Mode May 27, 2014 32.05

z13 SMT Mode Change 33.217 Sep 15, 2015 *33.09

z13 SMT Mode NRZIPCPU 34.106 May 10, 2016 34.03

CICS/CTG V9 Transaction Gateway ?? ?? 2013 31.31

CICS/ESA 3.2 Jun 28, 1991 9.9

CICS/ESA 3.3 Mar 28, 1992 10.01

CICS/ESA 4.1 Oct 27, 1994 13.09

CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07

CICS-Transaction Server V1R1 Sep 10, 1996 14.07

CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06

CICS-TS V1R2 CICS/TS 1.2 Oct 27, 1997 15.06

CICS-TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04

CICS-TS V2R1 CICS/TS 2.1 Mar 15, 2001 18.11

CICS-TS V2R2 CICS/TS 2.2 Feb 9, 2002 19.19

CICSTRAN subtype 1 support only *19.19

CICSTRAN subtype 2 completed *19.08

CICS-TS V2R3 CICS?TS 2.3 Dec 19, 2003

Using UTILEXCL to create IMACEXCL: 21.04

Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04

CICS-TS V2R3 CICS/TS 2.3 Aug 13, 2004 22.04

CICS-TS V3R1 CICS/TS 3.1 Jan 18, 2005 22.22

CICS-TS for Z/OS Version 3.1 Mar 15, 2005

Using UTILEXCL to create IMACEXCL: 22.13

Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22

CICS-TS V3R2 CICS/TS 3.2 Dec 6, 2007 25.11

CICS-TS for Z/OS Version 3.2 Jun 29, 2007 25.03

CICS-TS/3.2 Compressed Records Nov 3, 2007 25.11

CICS-TS/4.1 (CICSTRAN INCOMPAT) Mar 13, 2009 27.01

CICS-TS/4.1 (STATISTICS ST=2) Sep 18, 2009 27.08

CICS-TS/4.2 CICSTRAN/STATISTICS Jun 24, 2011 29.03

CICS-TS/4.2 CICSRDS MNSEGCL=5 Jun 24, 2011 *29.05

CICS-TS/4.2 INVALID STID=116 Jan 31, 2012 *30.01

CICS-TS/5.1 (INCOMPATIBLE) Dec 14, 2012 *30.08

CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013 *30.30

CICS-TS/5.1 MNSEGCL=5 INCOMPAT Jun 17, 2013 *31.03

CICS-TS/5.2 COMPATIBLE CICSTRAN Jun 13, 2014 *31.03

CICS-TS/5.2 INCOMPAT Statistics Jun 13, 2014 *32.03

CICS-TS/5.3 INCOMPAT CICSTRAN Apr 29, 2015 33.04

CICS-TS/5.3 RESOURCE SEGCL=5 Sep 31, 2015 33.09

CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015 33.11

CICS-TS/5.3 GA date Dec 11, 2015 33.33

CICS-TS/5.3 MNSEGCL=5 INPUT ERR Mar 21, 2016 34.02

CICS-TS/5.4 OPEN BETA Aug Aug 11, 2016 34.06

CICS-TS/5.4 OPEN BETA Nov Nov 11, 2016 34.09

DB2 2.3.0 Oct 28, 1991 10.01

DB2 3.1.0 Dec 17, 1993 13.02

DB2 4.1.0 Tolerate Nov 7, 1995 13.07

DB2 4.1.0 Full support Sep 11, 1996 14.07

DB2 5.1.0 Tolerate Jun 27, 1997 14.14

DB2 5.1.0 Full support Jun 27, 1997 15.02

DB2 6.1.0 initial support Mar 15, 1999 16.09

DB2 6.1.0 all buffer pools Mar 15, 1999 18.01

DB2 6.1.0 parallel DB2 Mar 15, 1999 19.19

DB2 7.1.0 parallel DB2 Mar 31, 2001 19.19

DB2 7.1.0 corrections Mar 31, 2001 20.06

DB2 8.1 Tolerate, no packages Mar 31, 2004 20.20

DB2 8.1 New Data Packages wrong Mar 31, 2004 21.08

DB2 8.1 Support with Packages Mar 31, 2004 *23.09

DB2 8.1 with all zIIP Variables Sep 30, 2006 24.08

DB2 8.1 +PK47659 Sep 12, 2008 26.08

DB2 9.1 See Change 25.265. Dec 7, 2007 25.11

DB2 9.1 Full Support +PK/56356 Sep 12, 2008 26.08

DB2 10.1 Tolerate Oct 1, 2010 28.06

DB2 10.1 New vars + Compressed Nov 1, 2010 *28.07

DB2 10.1 Invalid Header pre APAR Jan 12, 2011 *28.28

DB2 10.1 IFCID=225 INCOMPAT Sep 23, 2011 *29.07

DB2 10.1 QWHCCV for QWHCATYP=8 Oct 3, 2011 *30.07

DB2 10.1 DBID/OBID decode Jan 21, 2013 *30.30

DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013 *31.04

(ONLY IMPACTS DB2STATS)

DB2 11.1 TOLERATE DB2 V11.1 Jun 21, 2013 30.30

DB2 11.1 DB2STATS QLST CORRECT Jun 21, 2013 31.04

DB2 11.1 SUPPORT NEW VARIABLES Jun 21, 2013 31.08

DB2 11.1 IRLM NEW SEGMENT Jun 21, 2013 32.10

DB2 12.1 COMPATIBLE Oct 5, 2016 34.07

DFSMS/MVS 1.1 Mar 13, 1993 11.11

DFSMS/MVS 1.2 Jun 24, 1994 12.02

DFSMS/MVS 1.3 Dec 29, 1995 13.09

DFSMS/MVS 1.4 Sep 28, 1997 15.04

DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04

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

DFSORT SMF V1R5 Mar 1, 2006 24.02

MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02

MQ Series 1.2.0 May 26, 1998 16.02

MQ Series 2.1.0 Oct 2, 1999 17.07

MQ Series 5.2 Dec 16, 2000 18.10

MQ Series 5.3 Dec 16, 2002 21.05

MQ Series 6.0 Feb 14, 2006 23.23

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

Websphere MQ Series 7.1 MAR 12, 2011 29.03

Websphere MQ Series 8.0 Jun 24, 2011 29.05

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

NPM 2.0 Dec 17, 1993 12.03

NPM 2.2 Aug 29, 1994 12.05

NPM 2.3 ??? ??, 1996 15.08

NPM 2.4 Nov 18, 1998 17.01

NPM 2.5 Feb ??, 2000 18.02

NPM 2.6 Nov ??, 2001 19.06

RMDS 2.1, 2.2 Dec 12, 1995 12.12

RMDS 2.3 Jan 31, 2002 19.11

TCP/IP 3.1 Jun 12, 1995 12.12

TCP/IP 3.4 Sep 22, 1998 16.04

WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04

WebSphere 6.0 Feb 18, 2006 23.23

WebSphere 7.0 Oct 7, 2010 28.06

WebSphere 8.0 Jul 17, 2011 29.05

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

VM/ESA 2.0 Dec 23, 1992 10.04

VM/ESA 2.1 Jun 27, 1993 12.02

VM/ESA 2.2 Nov 22, 1994 12.06

VM/ESA 2.3 Jun 1, 1998 16.08

VM/ESA 2.4 Mar 1, 2001 19.03

z/VM 3.1 Mar 1, 2001 19.03

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

z/VM 4.2 ?? May 2, 2002 20.02

z/VM 4.4 Jan 22, 2005 22.22

z/VM 5.1 Jan 22, 2005 22.22

z/VM 5.2 Jan 22, 2006 24.01

z/VM 5.3 TOLERATE Jun 7, 2007 25.05

z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08

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

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

z/VM 6.2 Dec 2, 2011 29.04

z/VM 6.3 INCOMPATIBLE Jul 23, 2013 31.05

z/VM 6.3 z/13 Jan 23, 2016 33.33

IMS log 4.1 Jul 4, 1994 12.02

IMS log 5.1 Jun 9, 1996 14.05

IMS log 6.1 ??? ?, 199? 20.03

IMS log 7.1 ??? ?, 200? 20.03

IMS log 8.1 May 21, 2003 21.02

IMS log 9.1 Mar 96, 2004 *26.01

IMS log 10.1 Mar 06, 2007 *26.01

IMS log 11.1 Apr 1, 2010 *28.02

IMS log 12.1 Jan 23, 2012 *29.29

IMS log 13.1 (NOT 56FA) May 25, 2013 31.03

IMS log 13.1 (56FA RECORD) May 27, 2014 32.05

IMS log 14.1 COMPATIBLE Dec 19, 2015 33.13

AS400 3.7.0 Nov 1, 1996 15.01

AS400 4.1.0 Dec 30, 1996 15.08

AS400 4.2.0 Apr 27, 1998 16.02

AS400 4.4.0 Sep 27, 1999 17.07

AS400 4.5.0 Jul 27, 2000 18.07

AS400 5.2.0 - Most records Jul 23, 2003 21.03

AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04

AS400 5.3.0 Jan 22, 2005 22.22

AS400 5.4.0 Aug 26, 2006 24.06

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

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

MXG version was listed as supporting this product release,

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

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

Product Name Required

Demand Technology

NTSMF Version 1 Beta 14.11

NTSMF Version 2.0 15.05

NTSMF Version 2.1 15.06

NTSMF Version 2.2 16.04

NTSMF Version 2.3 17.10

NTSMF 2.4.4 Aug 9, 2002 20.04

NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02

NTSMF 2.4.7 Sep 30, 2004 22.08

NTSMF 3.1.4 Mar 15, 2009 27.01

NTSMF 4.0 Mar 15, 2011 29.03

Landmark

The Monitor for DB2 Version 2 13.06

The Monitor for DB2 Version 3.0 16.02

The Monitor for DB2 Version 3.1 20.04