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

MXG code for ODS reporting, now corrected in MXG Version 29.06.

See Changes 29.159 and 29.169.

To find the Hot Fix for all platforms, open http://www.sas.com,

and then search SAS Notes for 43828 (NOT SN-43828, NOT E80004),

and then Pull Down the Hot Fix tab.

MXG 26.03 thru MXG 29.29 will execute under SAS V9.2, or with

SAS V9.1.3 with Service Pack 4, on all supported SAS platform.

SAS Hot Fix for SAS Note 37166 is required to use a VIEW with

the MXG EXITCICS/CICSFIUE CICS/DB2 Decompression Infile Exit.

SAS V9.1.3 is NOT supported by SAS on Windows SEVEN platform.
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.

Old MXG code may continue to execute with SAS V8.2, but V8 is now

"Level B" 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 can not guarantee that all of MXG executes error free.

PLEASE INSTALL V9.2/V9.3, FOR BOTH OF US, TO AVOID FIXED PROBLEMS.

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 Hot Fix SN43828 is required; see text of Change 29.159.

With that hot Fix, MXG Versions 26.03 or later should execute

under SAS V9.3 on all platforms without error.

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

are interchangeable and can be read/written by any of those

versions, provided they are on the same platform. (On ASCII,

the 32-bit and 64-bit SAS versions are NOT the same "platform".)

SAS V9.3 did change 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 V9.3 ODS, and MXG 29.06 is STRONGLY recommended for ODS

with SAS V9.3.

For 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, and V9.2.

V9.2-created "PDBs" can be read/written by SAS V8.2 or V9.1.3,

and vice versa.
MXG Versions 26.03+ execute with SAS V9.2 with NO (new) 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.
MXG QA tests are executed on z/OS with SAS V9.1.3 and V9.2 and

on Windows XP with 32-bit INTEL, and on Windows Seven Ultimate

32-bit and 64-bit OS on 64-bit hardware, but MXG is installed

on many more hardware and software platforms: 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 SAS V9.1.3 or V9.2 on every possible 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 2.4 requires MXG 27.09 (see Change 27.239).

WPS Version 2.3.5 required MXG 27.05.

See NEWSLETTERS for "MXG Support for WPS Software"
IV. MXG Version Required for Hardware, Operating System Release, etc.

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, 2010 29.03

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

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

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 V2R2 CICS/TS 2.2 Feb 9, 2002 19.19

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 V3R2 CICS/TS 3.2 Dec 6, 2007 25.11

CICS-TS for Z/OS Version 2.1 Mar 15, 2001 18.11

CICS-TS for Z/OS Version 2.2 Jan 25, 2002 19.19

CICSTRAN subtype 1 support only *19.19

CICSTRAN subtype 2 completed *19.08

CICS-TS for Z/OS Version 2.3 Dec 19, 2003

Using UTILEXCL to create IMACEXCL: 21.04

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

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

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

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 Full plus 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*

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

Webshpere 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

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*

IMS log 12.0 Jan 23, 2012 29.29*

AS400 3.7.0 Nov 1, 1996 15.01

AS400 4.1.0 Dec 30, 1996 15.08

AS400 4.2.0 Apr 27, 1998 16.02

AS400 4.4.0 Sep 27, 1999 17.07

AS400 4.5.0 Jul 27, 2000 18.07

AS400 5.2.0 - Most records Jul 23, 2003 21.03

AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04

AS400 5.3.0 Jan 22, 2005 22.22

AS400 5.4.0 Aug 26, 2006 24.06

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

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

MXG version was listed as supporting this product release,

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

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

Product Name Required

Demand Technology

NTSMF Version 1 Beta 14.11

NTSMF Version 2.0 15.05

NTSMF Version 2.1 15.06

NTSMF Version 2.2 16.04

NTSMF Version 2.3 17.10

NTSMF 2.4.4 Aug 9, 2002 20.04

NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02

NTSMF 2.4.7 Sep 30, 2004 22.08

NTSMF 3.1.4 Mar 15, 2009 27.01

NTSMF 4.0 Mar 15, 2011 29.03

Landmark

The Monitor for DB2 Version 2 13.06

The Monitor for DB2 Version 3.0 16.02

The Monitor for DB2 Version 3.1 20.04

The Monitor for DB2 Version 4.0 22.10

The Monitor for 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*

IMF 4.5 (for IMS 11.1) (No change since 4.4) 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

XAMAP 4.1 29.07

V. Incompatibilities and Installation of MXG 29.29.

1. Incompatibilities introduced in MXG 29.29:

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

that can introduce known incompatibilities.

2. Installation and re-installation procedures are described in detail

in member INSTALL (which also lists common Error/Warning messages a

new user might encounter), and sample JCL is in member JCLINSTT for

SAS Version 9.

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

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

kept MXG variables is COMPATIBLE, and you can continue

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

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

fields or any new record subtypes will be created/kept

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

version to fail, visibly or invisibly, with or without

error conditions or messages, and the output datasets

may contain wrong values and incomplete observations,

and/or observations may have been lost.

You MUST install the new MXG Version with this change

to process data records that have been INCOMPATIBLY

changed by their vendor.

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

data records, if they are COMPATIBLY changed.

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

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

described in this change will be created in the MXG

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

and you have full support of the new data records.

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 29.29 after MXG 28.28:

Dataset/

Member Change Description

Many 29.169 MXG ODS HTML ASCII examples failed if no PATH=.

ANALDB2R 29.145 Performance and Reporting Enhancements

ASMDBLKU 29.289 ASMDBLKU, ASM version of UDEBLOCK, revised.

ASMRMFV 29.187 Do not use ASMRMFV in MXG29.05, fails with 0C4 ABEND.

ASMRMFV 29.217 Enhanced RMF III RCDSD section support.

ASMRMFV 29.279 RMF III RCD INPUT STATEMENT EXCEEDED error.

ASMTAPEE 29.280 "YOU SPECIFIED ASCENV" Assembly error with z/OS 1.13.

ASUM113 29.193 zVM MONWRITE VXPRCMFC (SMF 113 for z/VM) included.

ASUM113 29.243 Calculation of ESTSCP1M incorrectly had small values.

ASUM4HRS 29.268 %MACRO calculates "Four Hour" running average values

ASUM70PR 29.092 ZIPCPUS/IFACPUS included parked time.

ASUMMIPS 29.237 Calculation of ZIPUSED and ZIEUSED incorrect.

ASUMUOW 29.007 Doc: variables required for ASUMUOW/ASUMCICX.

ASUMUOW 29.009 ASUMUOW fails is //CICSTRN,//DB2ACCT on tape.

ASUMUOW 29.188 Case 4 example prevents blank TRANNAME in ASUMUOW.

BLDSMPDB 29.008 SORTEDBY=NO default to eliminate NOTSORTED exposure.

BLDSMPDB 29.017 LIBNAME WEEK1 not found corrected.

BLDSMPDB 29.246 A dash in filename text tripped up %UPCASE().

BLDSMPDB 29.292 Support for execution under unix.