CONFIGV9 22.207 NOTHREADS specified for 9.1.2 error, fixed in 9.1.3.
(the NOTHREADS change caused the Aug 13 re-date of MXG 22.08!),
CONFIGV9 22.108 CRITICAL Hot Fix SN-012437 Required for SAS V9.1.2
CONFIGV9 22.123 SAS V9 on MVS VB INCOMPAT: S2=72 must be S2=0.
MXGSASV9 22.130 Revised MXG JCL example for SAS V9, NLS names, etc.
MXGSASV9 22.126 SAS dsnames must be "W0", w-zero, not w-oh.
CONFIGV9 22.108 Support for V6SEQ under SAS V9.1
UTILS2ER 22.123 Utility to detect errors with S2=0 in your programs.
FLASH 22.108 CRITICAL SAS Hot Fix SN-012437 is REQUIRED for V9.1.2
Many 22.184 SAS V9.1.2 $VARYING design change protected.
AUTOEXEU 22.102 autoexec.sas file for unix, protects SASAUTOS error.
Some 22.108 Support for SAS V9.1 and V6SEQ without Hot Fix.
Many 22.192 Protection for PROC SYNCSORT error with SAS V9.1.2
Additional important enhancements in MXG 22.08:
TYPETMO2 22.191 Support for ASG/TMON TCE for CICS/ESA 2.3, COMPATIBLE
Many 22.180 Support for IFA CPU variables for zAAP processors.
Many 22.177 Update to define MACRO _Vdddddd for numeric SMF plus.
Many 22.192 All INFORMAT $NOTRAN statements were removed.
TYPEIMS7 22.199 Major revision to IMS0708 dataset, all events output.
VMACDB2H 22.196 Support for extended length DB2 id variables.
TYPENTSM 22.193 Support for NTSMF Exchange/Outlook/DTS CPU objects.
TYPENTSM 22.190 Support for NTSMF MicroStrategy Server objects.
TYPEOMVT 22.186 Omegamon/VTAM V520 IRNUM 29 Divide by zero corrected.
TYPE80A 22.185 Invalid SMF 80 Extended Relocate Section protected.
ANALRMFR 22.181 Enhancements to RMF reporting.
ADOC110 22.189 Major updated added 1300 lines of CICS documentation.
Note: The Aug 20 re-date of MXG 22.08 was made only because it was
easy to do; I discovered that members were missing from the
3480 tapes (not from ftp nor CD-rom shipments) and so I chose
to create replacement tapes with the added changes that were
made during the week.
Major enhancements added in MXG 22.07
TYPE7072 22.152 Support for IFA Processors, APAR OA05731.
TYPE7072 22.137 Support for z890 CPUTYPE 2086, OS/390-INCOMPAT.
TYPE74 22.141 Support for RMF 74 subtype 8 ESS Link Stats record.
TYPETNG 22.170 Support for TNG Windows Server 2003 new objects+fix.
IMACICHO 22.169 Hogan optional CICS data member now exists
TYPEHMF 22.168 Support for HMF V2.7 new subtypes, compatible.
TYPEHPDM 22.166 Support for STK ExHPDM user SMF record.
BUILDPDB 22.165 BUILDPDB detects overlapped SMF data previously read.
IMAC6ESS 22.161 Support for ESS GEPARMKY 003Bx and 0045x fields.
TYPETNG 22.160 REGION reduced for JCLTEST8 TESTOTHR due to TYPETNG.
UTILBLDP 22.149 Enhancement supports subtype selection in ZEROOBS.
VGETENG 22.148 Enhancement to get Engine and Device Type of LIBNAME
ASUM42DS 22.147 Performance enhancement reduce I/O, CPU using view.
TYPE119 22.146 TYP119nn datasets had GMT time zone, now have local.
JCLRMF 22.143 Example to create "RMF-only" PDB from SMF data.
ASUMUOW 22.139 Variables APPLID/USER/LUNAME/TERMINAL incorrect.
ANAL4GB 22.138 Revised to use DCOLLECT to detect large VSAM files.
IEFU84 22.136 SMF exit to get Initiator Name and Number for jobs.
ASUM70PR 22.135 MVS System Name of each LPAR, SMF70STN, added.
TYPE70 22.134 Percent when each engine online PCTONLN0-PCTONLNX.
TYPENDM 22.133 Support for several additional NDM-CDI subtypes.
TYPENSPY 22.131 TYPENSPY and TYPENETM combined, only one SMF record.
TYPENETM 22.131 TYPENSPY and TYPENETM combined, only one SMF record.
MXGSASV9 22.130 Revised MXG JCL example for SAS V9, NLS names, etc.
UTILCONT 22.175 Utility to Inventory the Megabyte Sizes of PDBs.
Major enhancements added in MXG 22.06
Really major:
Change 22.123 - SAS V9 on "MVS" INCOMPAT due to RECFM=VB on the
SAS-supplied SASMACRO library requires the MXG
default S2=72 be changed to S2=0, which itself
raises another potential incompatibility in SAS
programs, so new UTILS2ER must be run against
your SAS programs before migration to SAS V9,
or your programs may have strange ABENDs. See
extensive discussion in text of Change.
Change 22.121 - CPU time for DB2 Parallel Trans was not output
(i.e., lost, could be very large) in DB2ACCT.
See the Change text, and also the DB2 Technical
Note in Newsletter FORTY-FIVE.
CONFIGV9 22.123 SAS V9 on MVS VB INCOMPAT: S2=72 must be S2=0.
UTILS2ER 22.123 Utility to detect errors with S2=0 in your programs.
TYPEDB2 22.121 DB2 Parallel CPU time lost, not output in DB2ACCT.
TYPEDB2 22.124 MXG 22.04-05, QWHSSTCK missing in SMF 102 trace data.
EXDB2ACC 22.121 DB2 Parallel CPU time lost, not output in DB2ACCT.
TYPEIPAC 22.125 Support for IPAC subtype 5 IPAC05 corrections.
IMAC6ESS 22.117 Support for optional ESS segment GEPARMKY=003Bx.
BUILDPDB 22.115 JES3 PDB only; wrong TYPE26J3 used in BUILDPD3.
TYPE102G 22.109 TYPE102G to read DB2 Trace written to GTF didn't.
BLDIMPDB 22.128 ASCII equivalent of JCL for JCLIMSLx execution.
TYPEIMSA 22.113 ASCII execution only, APPLID not readable.
TYPEEDGS 22.112 INPUT STATEMENT EXCEEDED with MVRECLEV '02'x.
ANALFIOE 22.127 Run time improvement if SMF, instead of PDB, input.
BLDSMPDB 22.111 unix case sensitivity corrections
BLDNTPDB 22.111 unix case sensitivity corrections
MXGSASV9 22.126 SAS dsnames must be "W0", w-zero, not w-oh.
Major enhancements added in MXG 22.05
CONFIGV9 22.108 Support for V6SEQ under SAS V9.1
FLASH 22.108 CRITICAL SAS Hot Fix SN-012437 is REQUIRED for V9.1.2
TYPE102C 22.104 Support for Candle Omegamon II for DB2 IFCID Trace.
AUTOEXEU 22.102 autoexec.sas file for unix, protects SASAUTOS error.
Major enhancements added in MXG 22.04
TYPE110 22.094 Support for CICS/TS 2.3 with no EXCLUDEd fields.
(If you use UTILEXCL with your CICS/TS 2.3 data,
there was no error, but CICSTRAN without IMACEXCL
was wrong if all fields were present in 110-1.)
TYPEQACS 22.095 Support for OS/400 5.2 QAPMMIOP record new fields.
TYPETNG 22.085 Support for NT objects SESSION and USER in TNG cubes.
TYPEAIX 22.083 Support for AIX PTX new objects.
TYPEIBSM 22.079 Support for IBM Session Manager user SMF record.
TYPETPMX 22.077 Support for alternative multiple-ACCT field TPM data.
TYPE74 22.075 Support for 1024 structures in Coupling Facility.
UTILEXCL 22.068 Support for optional RMI data in CICSTRAN.
VMXGINIT 22.096 Macro variables &MACINTV and &MAC30DD created.
TYPEDB2 22.090 MXG 22.02-22.03 only. QWHSSTCK 1960 date in DB2ACCT.
TYPEDB2 22.084 Large QBSTGET in DB2STATB due to DB2 restart fixed.
TYPE70 22.087 Non-PR/SM, IORATE/PCTTPI variables too low.
TYPE7072 22.072 TYPE72GO with R723CWMN GT 0, Periods not output.
MONTHASC 22.064 Example "MONTHBLD" for ASCII systems.
AUTOEXEC 22.064 LIBNAME DUMMY added to support MONTHASC.
Major enhancements added in MXG 22.03
Revision of ThruPut Manager TYPETPMX to not use ARRAYS to save CPU.
(34 new datasets); Change 22.060.
Major enhancements added in MXG 22.02
If you are using IRD, you must install MXG 22.12 or later:
(This note originally said MXG 22.02, but now, Change 22.307 in
MXG 22.12 is required for IRD values to be correct!)
--Full Support for IRD (Intelligent Resource Director) is now in all
CPU-related datasets. IRD support was incremental in MXG:
Datasets When MXG Version Change
ASUM70PR/ASUMCEC Sep 22, 2003 21.05 21.170
TYPE70PR Mar 11, 2004 22.01 22.011
TYPE70,RMFINTRV Dec 2, 2005 22.12 22.307
PCTCPUBY in TYPE70 and RMFINTRV were wrong in any interval when IRD
varied CPUs offline. I'm embarrassed, since PCTCPUBY is the second
most important variable in all of MXG (CPUTM for billing is the most
important); this is the first PCTCPUBY error in MXG's history! When
all engines remained online, however, there was no error.
BUILDPDB 22.052 PDB.STEPS can have wrong EXCP,IOTM,TAPExxxx values,
but only in rare circumstance of identical INITTIMEs.
RMFINTRV 22.050 Variable PCTCPUBY wrong in RMFINTRV when IRD active.
TYPE70 22.050 Variable PCTCPUBY wrong in TYPE70 when IRD is active.
DB2STATB 22.045 Negative QBSTGET, other QBSTxxx, when 4-byte wrapped.
TYPEDB2 22.042 DB2 Stats records not written in subtype order.
ANALALL 22.040 Example now can write all SMF for selected job(s).
ASMTAPEE 22.038 ML-31 of MXGTMNT corrects GMT, MSC APAR support.
Major enhancements added in MXG 22.01
VMXGRMFI 22.017 BUILDPDB run time elongation, if output is to tape.
Circumvention: USE FREE=CLOSE on tape DDs. See text.
TYPE117 22.029 Support for SMF 117 WBIMB WebSphere Business Integrat
TYPE82 22.005 Support for SMF 82 Crypto subtypes 14 thru 19.
TYPEENDV 22.032 Support for Endeavor Release 4.0, INCOMPATIBLE.
TYPEHURN 22.006 Support for Huron/Object Star additional subtypes.
TYPESMSX 22.030 Support for DF/SMS Storage Class Exit User SMF record
Many 22.018 Hardcoded "SPIN" DDname now &SPININ,&SPINOUT macros.
TYPE120 22.014 WebSphere SMF 120s had GMT for many timestamps.
TYPE30 22.022 Variable SRVTCBTM,SRVSRBTM,CPUTOTTM created in TYPE30
TYPETMNT 22.012 RACFUSER/RACFTERM reversed, GMT times, INPUT EXCEEDED
TYPETPMX 22.008 (Final?) revisions to internal Thruput array names.
TYPE30 22.021 Job delays SMF30HQT/JQT/RQT/SQT revisions.
See member NEWSLTRS or the Newsletters frame at www.mxg.com for
current MXG Technical Notes that used to be in CHANGES.
All of these enhancements are described in the Change Log, below.
SAS Version requirement information:
MXG 22.08 or later is REQUIRED for SAS V9.1.2 or V9.1.3; see
"Major Enhancements in MXG 22.08" in CHANGES for details.
MXG executes best under the most recent SAS Version, with all
Critical HotFixes installed by your SAS Installer:
For 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 V7SEQ,V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3; earlier MXG notes that
they were required for 9.1.3 are wrong.
For SAS Version 8.2, HotFix Bundle 82BX08 is REQUIRED to be safe.
Sequential Engine Status:
V9SEQ is fixed in V9.1.3; it would be my default in CONFIGV9,
but I can't tell that you are at V9.1.3, and because V9SEQ
was badly broken prior to 9.1.3, I still have to use V6SEQ
and MXG's default in CONFIGV9. You should change to V9SEQ
in CONFIGV9 if you have installed SAS V9.1.3.
V6SEQ, if used under V9.1.2, requires SN-013514.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
MXG New Version QA tests are executed on z/OS with SAS V9.1.3 and
V8.2, and on (archaic) V6.09, and on Windows XP with SAS V9.1.3.
Previous tests of MXG Software have been run with SAS V9.1.2, SAS
V8.2 and V9.1 with Linux RH8 on Intel, with V9.1 on Solaris v2.8
model v880, and V9.1 on HP-UX v11.11 model rp5470, confirming full
compatibility. So MXG executes with SAS V9.1+ or SAS V8.2 on
every possible SAS platform! Each new MXG version is also tested
with SAS/ITSV/ITRM by ITRM developers.
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 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 21.05
z/OS IRD TYPE70PR Mar 11, 2004 22.01
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 22.12
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04
z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07
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 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
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 Mar 31, 2004 20.20
DB2 8.1 New Data Supported Mar 31, 2004 21.08
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
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
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
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
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
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
Note: Asterisk before 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
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 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/ESA 2.1 - 20.04
The Monitor for CICS/ESA 2.2 - 20.335, 21.134 21.04
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
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 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
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
Memorex/Telex
LMS 3.1 12.12A
Amdahl
APAF 4.1, 4.3 16.08
Velocity Software
XAMAP 3.4 22.10
II. Incompatibilities and Installation of MXG 22.10.
1. Incompatibilities introduced in MXG 22.22 (since MXG 21.21):
a- Changes in MXG architecture made between 22.22 and 21.21 that might
introduce incompatibilities.
NONE.
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.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
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.
A change that alters any previously kept variable is
INCOMPATIBLE, and requires the new version to be used.
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.
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.
III. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
See also member INDEX, but it may be overwhelming.
IV. 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.
_PAGE_ 8
Alphabetical list of important changes in MXG 22.22 after MXG 21.21:
Dataset/
Member Change Description
Many 22.018 Hardcoded "SPIN" DDname now &SPININ,&SPINOUT macros.
Many 22.177 Update to define MACRO _Vdddddd for numeric SMF plus.
Many 22.180 Support for IFA CPU variables for zAAP processors.
Many 22.184 SAS V9.1.2 $VARYING design change protected.
Many 22.192 All INFORMAT $NOTRAN statements were removed.
Many 22.192 Protection for PROC SYNCSORT error with SAS V9.1.2
Some 22.108 Support for SAS V9.1 and V6SEQ without Hot Fix.
ADOC110 22.189 Major updated added 1300 lines of CICS documentation.
ANAL4GB 22.138 Revised to use DCOLLECT to detect large VSAM files.
ANAL94 22.114 IBM VTS Stat Report used SMFTIME, not STARTIME.
ANALALL 22.040 Example now can write all SMF for selected job(s).
Dostları ilə paylaş: |