COPYRIGHT (C) 1984-2023 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES 42.03
=========================MEMBER=CHANGE42================================
/* COPYRIGHT (C) 1984-2024 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG VERSION 42.03 is dated Sep 15, 2024, thru Change 42.072
MXG VERSION 42.02 was dated Jun 22, 2024, thru Change 42.048.
MXG VERSION 42.01 was dated Mar 15, 2024, thru Change 42.022.
ANNUAL MXG VERSION 41.41 was dated Jan 10, 2024, thru Change 41.122.
New TECHNOTES previously in NEWSLTRS are now in CHANGESS.
Instructions for ftp download can be requested by using this form:
http://www.mxg.com/Software_Download_Request
Your download instructions will be sent via return email.
Contents of member CHANGES:
I. Current MXG Software Version 42.03' is available upon request.
II. SAS Version requirement information.
III. WPS Version requirement information.
IV. MXG Version Required for Hardware, Operating System Release, etc.
V. Incompatibilities and Installation of MXG 42.03'.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains old Technical Notes. many of which are still
valid, but the last was in 2018. Now, TECHNOTES and FLASHes are in
CHANGES/CHANGESS. which are also online.
Member CHANGES contains the changes made in this current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
CHANGESS and NEWSLTRS are also online at http://www.mxg.com,
========================================================================
I. MXG VERSION 42.03 DATED Sep 15, 2024, THRU CHANGE 42.072
==MAJOR CHANGES ADDED IN MXG 42.03, DATED Sep 15, 2024 THRU 42.072.====
ERRORS CORRECTED
VMACRMFV 42.069 z/.OS 3.1 ERROR Array Subscript out of range.
VMAC80A 42.052 TYPE80A INPUT EXCEEDED, long TOKXUGROUPS.field.
VMAC119 42.049 Support for TYP11938 Subtype 38 dataset EXCEEDED.
VMAC102 42.054 SMF 102 IFCID 196 misaligned, IBM stored zero.
VMAC119 42.071 Correction to dataset TYP11906 & TYP11945 variables.
VMAC119 42.065 Only first segment SMF 119 Subtype 44 was output.
NEW SUPPORT
VMAC113 42.064 IBM changed z/16 RNI coeff from 4.3 to 4.2
VMAC7072 42.070 Support for Martin Packers Home Address blog post.
VMAC122A 42.037 Support SMF 122 Subtype 2 IBM Dependency.
VMAC1415 42.063 z/OS 3.1 new variables in TYPE1415.
VMAC30 42.062 Variables IOUNITS IOCOEFF MSOUNITS MSOCOEFF zeroed.
ENHANCEMENT
==MAJOR CHANGES ADDED IN MXG 42.02, DATED Jun 22, 2024 THRU 42.048.====
ERRORS CORRECTED
VMXG70PR 42.048 OBS count wrong in ASUMCEC, MSUHR Values wrong.
VMAC102 42.041 TYPE102 IFCID 365 INPUT EXCEEDED REDORD LENGTH.
VMAC82 42.042 CPU LOOP with SMF 82 SUBTYPE 40.SMF82_Tag increased
NEW SUPPORT
VMAC119 42.047 Support for new variables in TYP11912 TLS.
VMAC102 42.037 Support for new ZPARMS in T102S106
VMAC80A 42.025 Support for RACF APAR OA61951 PHRASEINT.
VMAC99 42.022 Support for APAR OA65652 new variables TYPE99Q2.
VMAC122A 42.037 Support SMF 122 Subtype 2 IBM Dependency.
VMAC80A 42.025 Support for APAR OA61951 RACF PHRASEINT
VMAC80A 42.038 Support for new Tokens TOKDBV2 and TOKOWNERS
ENHANCEMENT
VMAC119 42.045 ZERT TYP11912DN missing observations
==MAJOR CHANGES ADDED IN MXG 42.01, DATED MAR 15, 2024 THRU 42.022.====
ERRORS CORRECTED
VMAC102 42.001 Records with QWHSNSDA GT 4 had missing values.
UCICSCNT 42.002 Utility INPUT STATEMENT EXCEEDED CICS subtype 2.
VMAC102 42.001 Many Missing Values in Many TYPE102 datasets.
VMAC102 42.013 DB2 SMF 102 IFCID 172 INPUT EXCEEDED LENGTH ZERO
VMAC102 42.019 DB2 SMF 102 IFCID 365 INPUT EXCEEDED LENGTH ZERO
VMAC112 42.006 Omegamon for CICS ONDV SUPRA INPUT EXCEEDED.
VMAC119 42.017 ZERT SMF 119 Subtype 12 TYP1192SUM corrections
CICSIFUE 42.020 CICSIFUE Decompression U4038LE Abend with WPS.
ENHANCEMENT
ANAL115 42.004 Major overhaul of report/analyusis member for MQ.
VMAC30 42.008 Support for APAR OA65055 TYPE30 JAVA CPU ZIP SU
VMAC99 42.009 Support for APAR OA65055 TYPE99SL JAVA CPU ZIP SU
VMAC99 42.022 Support for APAR OA65652 SMF 99 Subtype 2
VMACRACF 42.016 Support for RACF IRRDBU00 RACTYPE=0161 records.
VMXGSUM 42.007 New Parameter NOMXGECHO suppress print of parms.
========================================================================
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M8 (9.4M8),
"M8", or with options VERSIONLONG;
"SAS 9.4 (9.04.01M8P080520)" on z/OS
9.4 (TS04.01M8P08052020)" on ASCII.
SAS V9.4 M8 is RECOMMENDED, but MXG executes without error
using SAS Version 9.4 M0-M2 or M4-M6 or SAS Version 9.3 M0-M2.
SAS V9.4.M7 and M8 for ASCII executiion require SAS HOT FIX 69871.
SAS V9.4 M5 is REQUIRED with z/OS 2.3 with Eight-Byte USERIDs
for Interactive TSO (DMS) SAS Sessions. SAS Note 61339.
Only on z/OS, SAS 9.4 "M5" requires MXG 35.36+ because it adds the
NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect
described in SAS Note 61672. But SAS apparently does not plan for
a defect correction since the MXG Circumvention solves for MXG and
the text of 61672 simply describes the circumvention needed because
MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect.
See Change 35.309 for more details on using NOERRORSTOP for your
own PROC SQLs.
SAS V9.4 M3 is NOT RECOMMENDED. See Change 36.128 SAS Note 61906
that reports 40% Increase in CPU time with M3.
SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.
SAS V9.3 SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.
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 B 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 on
that platform.
9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.
SAS V9.1.3 causes JCLTEST9/TESSOTHR to ABEND, TOO MANY ARGUMENTS
FOR COUNTW() requires SAS Version 9.2 so 9.1.3 can NOT
safely be used for MXG. See CHANGE 41.046, Jun 21, 2023.
SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
Support level C by SAS Institute, Sep 30, 2013.
SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.
SAS V8.2 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 DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
But CONFIMXG is required for sites with NLS issues, and you must
use JCLCONFI to create/update the MXG.FORMATS catalog if you use
CONFIG='MXG.SOURCLIB(CONFIMXG)'.
For no NLS, you can use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 42.03 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 was 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 TEN and
Linux on 64-bit hardware, 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 4.04 (04.04.01.00.005305 has been tested.
DO NOT USE 4.03.01 nor 4.04.00, INVALID CPU BUSY in TYPE70.
Error was introduced in 4.03.01 and 4.04.00. See Change 39.171.
Must be at 4.03.02.00.8569+ or 4.04.00.03.3277+/
WPS Version 4.01 USER 4037 ABEND, See Change 37.116.
WPS Version 4.0 reportedly fixed version 3 problems.
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:
-Support for z/16 processor data.
MXG 38.07 or later is needed, but 40.01 will ABEND, see below
SMF: Only SMF 113 records were incompatibly changed, but there is no
execution error as only counter labels and values were changed,
causing coefficients for the calculated variables (RMI,etc) to
also be changed and default coefficients are changed to z/16,
You should use separate SAS steps for each processor type; MXG
will OUTPUT only the processor type you requested in //SYSIN,
and will skip other processor type records, so you do NOT need
to pre-process SMF records to select processor type. You will
want to rename one pair of datasets if you want to put them in
the same PDB Data Library.
For z/15 you would use
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA11F %
%INCLUDE SOURCLIB(TYPS113,ASUM113);
and for z/16 you would use
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA11G %
%INCLUDE SOURCLIB(TYPS113,ASUM113);
to get correct values in TYPE1131 and ASUM1131 datasets.
MXG Support for z/16 for SMF 113 requires 40.05 for z/OS and
40.03 for zVM.
MXG 40.01 will ABEND due to a TYPE30 error exposed by the z/16.
with z/OS 2.5 or APAR OA61511. You can correct by changing the
line 1812 in VMAC30 from 192 to 220, or ask support for the
current VMAC30 member with Change 40.050.
Many other SMF and Data Gatherer records were updated in 40.04.
RMF ASMRMFV processes RMF III data with no errors, Change 40.068
added some new fields. New DNG3 table support was in 40.05.
-Support for z/15 processor data.
The z/15 and z/15 T02 processors INCOMPATIBLY changed the SMF 113
records by inserting 32 new EXTEND and 4 CRYPTO counters, causing
ARRAY SIZE EXCEEDED with BUILDPDB which processes the SMF 113s.
Support for counter changes for both models was in MXG 37.08.
If you use MIPS in reports, the format $MGRMIPS provides the
MIPS/MSU value for each processor; the z15 values were updated
in MXG 37.08, and the z15 TO2 values were updated in MXG 38.04.
These MXG programs use $MGRMIPS: ASUMMIPS GRAFCEC GRAFWLM
GRAFWRKX and TYPERMFV (RMF III).
The z/14 also inserted SMF 113 fields, supported in MXG 36.07.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
And z/VM on the z15 requires MXG 38.02, PRCMFC/MFM COUNTERS caused
HARDWARE COUNTER messages, PRCMFC/PRCMFM no obs. Change 38.048.
The z13 processor INCOMPATIBLY CHANGED, the new SMT-MODE RMF 70, and
MXG 34.03 was REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF
(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).
SMF Back Levels: MXG 37.08 or later is required for both z15 & z/16
SMF 113 change, but those back level versions could fail due
to other records changed by subsystem updates you made for the
z/16 (e.g.CICS TS/6.1 which requires MXG 40.02) that didn't
exist when that back=level was created..
The new zEDC/EADM compression hardware requires MXG 38.05 to support
new metrics.
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
z/OS 2.3 Many new variables Sep 24, 2017 35.166 35.09*
z/OS 2.3 RMF III Support Sep 24, 2017 35.190 35.09*
z/OS 2.3 type 2 st 2 STOPOVER Sep 24, 2017 35.190 35.09*
z/OS 2.3 type 90 st 38 STOPOVER Sep 24, 2017 35.199 35.09*
z/OS 2.4 Compatible from SMF Manual Sep 2019 37.166 37.07.
z/OS 2.4 Compatible from SMF Manual May 2020 38.105 38.05.
z/OS 2.4 Compatible from SMF Manual Apr 2021 39.075 39.03.
z/OS 2.4 Compatible RMF III PGMR Apr 1 2021 39.074 39.03.
z/OS 2.5 Compatible from SMF Aug 12,2021 39.06.
z/OS 2.5 Compatible RMF III Aug 12,2021 39.08.
z/OS 2.5 RMF III 4 new tables Aug 12,2021 39.08.
z/OS 2.5 Protects Possible New 72.3 fields (40.078) 40.04.
z/OS 3.1 Support in MXG 39.08 New vars in 41.05 CH 41.092.
z/OS 3.1 Support is in MXG 41.05+ :
Change 41.092 Support for z/OS 3.1 SMF Manual changes (COMPATIBLE).
VMAC26J2 We and several customers have tested z/OS 3.1 records
VMAC30 with back levels of MXG that support z/OS 2.5 (39.08)
VMAC7072 with no errors reported, and we expect no issues.
VMAC79 Change 41.096 added the new AI data in TYPE99 and
Oct 26, 2023 there were other APARs in 3.1, but we expect no issues.
New variables were added, see Change 41.092 full text.
This change was in MXG 41.05.
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
z13 SMT MT=2 CPUZIPTM TYPE70 Mar 21, 2016 35.03
z14 SMF 113 INCOMPAT, ABEND Oct 2, 2017 35.11
z14 113 LPARBUSY missing value Aug 8, 2018 36.07
z14 ZR1 New SMF70MAXPU variable May 8, 2018 36.04
z15 New SMF 113 fields INCOMPAT Nov 18, 2020 37.08
z15 z/VM MFC counters, INCOMPAT Mar 23, 2020 38.02
z15 ANAL9914 Support CH 39.006 Jan 14, 2021 39.01
z/16 NEW SMF113 values, NO ABEND See CHANGE 40.070 40.03
z/16 MXG 38.07 OR LATER IS NEEDED. 38.07
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
CICS/TS 5.4 GA Jun 17, 2017 35.03
CICS/TS 5.5 GA (INCOMPAT) Jan 29, 2018 36.11
CICS/TS 5.6 GA (INCOMPAT) Jun 1, 2020 38.07
CICS/TS 5.6 NEW DATA (COMPAT) Oct 5, 2020 38.09
CICS/TS 6.1 ONE NEW (INCOMPAT) Jan 11, 2020 40.01
CICS/TS 6.1 ONE NEW (INCOMPAT) Sep 20, 2020 40.02
CICS/TS 6.1 UTILEXCL/IMACEXCL OK Aug 15, 2022 40.05
CICS/TS 6.1 VMAC110 NO IMACEXCL May 31, 2023 41.02
CICS/TS 6.2 INCOMPATIBLE BETA16 Sep 20, 2023 41.04
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.08
DB2 12.1 NETEZZA CORRECTIONS Oct 5, 2016 34.08
DB2 12.1 QLAC INSERTS DB2ACCT May 15, 2017 35.05*
DB2 13.1 NEW DATA NO ERRORS Jan 2017 40.40
DB2 13.1 IDAA/NETEZZZ ONLY ABEND Mar 19, 2013 41.01
DB2 13.1 ABEND 41.06/41.41 102 Jan 12, 2024 42.01
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
Websphere MQ Series 9.1 Mar 20, 2017 35.03
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
z/VM 6.4 SYTLCK Incompat Apr 26, 2016 34.04
z/VM 6.40061802 ABEND Jan 22, 2019 37.02
z/VM 7.1 INCOMPAT ABEND Feb 14, 2019 37.02
z15 z/VM MFC counters, INCOMPAT Mar 23, 2020 38.02
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.07
IMS log 15.1 NO CHANGES Mar 1, 2018 35.07
IMS log 15.4 NO CHANGES Mar 1, 2018 35.07
IMS log 15.4 Minor Chg 42.033 May 8, 2024 42.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
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 DB2 Version 5.0 30.02
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 CICS TCE 3.3 (for CICS/TS 4.1,4.2) 29.07
TMON/CICS 3.4 (for CICS/TS 5.1) 30.30-32.12
(Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)
TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099) 33.04
TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195) *33.09
TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257 34.08
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
TMON/MVS Version 4.4 32.04
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-BROADCOM
ACF2 6.2 was 16.04 but ABEND, ACSMFREL=0 May 2018 36.05
ASTEX 2.1 14.04
IDMS 18 32.05
IDMS 19 (INCOMPAT after PTF R084146 Change 34.164) 33.05
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
APPTUNE V11R2 SMF 102 33.11 33.264
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) *31.08
IMF 4.5 (for IMS 11.1) (No change since 4.4) 31.08
IMF 4.6 a/k/a Mainview IMS *31.08
IMF 5.1 a/k/a Mainview IMS *34.01
IMF 5.2 a/k/a Mainview IMS 34.01
IMF 5.3 a/k/a Mainview IMS 35.03
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2, 5.3, 5.4 33.01
Mainview for CICS Version 6.5 (CICS/TS 5.1) 30.30
Mainview for CICS Version 6.4 (CICS/TS 4.2) 30.04
Mainview for CICS Version 6.1 26.26
Mainview Auto Operator data file 28.28
Mainview for DB2 THRDHIST file 20.20
Mainview for TCP/IP 20.20
Mainview for IP 34.??
Mainview for Batch Optimizer 19.19
Memorex/Telex
LMS 3.1 12.12A
Oracle V9, V10 24.06
SYNCSORT
2.1 33.05
1.4 33.08
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 Now Renamed to ZVPS 4.1 29.07
XVPS 4.2 31.06
ZVPS 5.4 *33.07
V. Incompatibilities and Installation of MXG 42.03.
1. Incompatibilities introduced in MXG 42.03:
a. Changes in MXG architecture made between 42.03 and prior versions
that can introduce known incompatibilities.
IF YOU HAVE MEMBER E2TY70 IN YOUR USERID.TAILORING SOURCE LIBRARY,
YOU MUST CHANGE _LTY70 to _WTY70 in that member. CHANGE 38.105.
The error before this correction will be:
ERROR: DATA SET "PDB.TYPE70" was not specified on the DATA stmt.
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.
An MXG Version never "expires" nor "goes out of Support". When
you put in a new product/subsystem/Release/APAR that incompatibly
changed its records then you must install the current MXG Version
or at least be using the minimum level of MXG that is currently
documented in the preceding list in section IV.
COSMETIC Some Changes will start with COSMETIC. This indicates
that that change only alters a displayed value or may
be a spelling error in a label, but it is "cosmetic"
in that it ONLY affected the display, and the output
data sets created are NOT impacted by this change.
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 42.03:
Dataset/
Member Change Description
ANAL115 42.004 Major overhaul of report/analyusis member for MQ.
BUILDPDB 42.021 New variable MAXWKSET MAXIMUM*WORKING*SET added.
CICSIFUE 42.020 CICSIFUE Decompression U4038LE Abend with WPS.
UCICSCNT 42.002 Utility INPUT STATEMENT EXCEEDED CICS subtype 2.
VMAC102 42.001 Many Missing Values in Many TYPE102 datasets.
VMAC102 42.013 DB2 SMF 102 IFCID 172 INPUT EXCEEDED LENGTH ZERO
VMAC102 42.019 DB2 SMF 102 IFCID 365 INPUT EXCEEDED LENGTH ZERO
VMAC102 42.037 Support for new ZPARMS in T102S106
VMAC102 42.041 TYPE102 IFCID 365 INPUT EXCEEDED REDORD LENGTH.
VMAC112 42.006 Omegamon for CICS ONDV SUPRA INPUT EXCEEDED.
VMAC119 42.017 ZERT SMF 119 Subtype 12 TYP1192SUM corrections
VMAC119 42.045 ZERT TYP11912DN missing observations
VMAC122A 42.037 Support SMF 122 Subtype 2 IBM Dependency.
VMAC80A 42.025 Support for APAR OA61951 RACF PHRASEINT
VMAC80A 42.038 Support for new Tokens TOKDBV2 and TOKOWNERS
VMAC82 42.042 CPU LOOP with SMF 82 SUBTYPE 40.SMF82_Tag increased
VMAC30 42.008 Support for APAR OA65055 TYPE30 JAVA CPU ZIP SU
VMAC99 42.009 Support for APAR OA65055 TYPE99SL JAVA CPU ZIP SU
VMAC99 42.022 Support for APAR OA65652 SMF 99 Subtype 2
VMACRACF 42.016 Support for RACF IRRDBU00 RACTYPE=0161 records.
VMXG70PR 42.048 OBS count wrong in ASUMCEC, MSU Values wrong.
VMXGSUM 42.007 New Parameter NOMXGECHO suppress print of parms.
VMAC119 42.071 Correction to dataset TYP11906 & TYP11945 variables.
VMAC7072 42.070 Support for MartinPackers Home Address blog post.
VMACRMFV 42.069 z/.OS 3.1 ERROR Array Subscript out of range.
VMAC119 42.049 Support for TYP11938 Subtype 38 dataset EXCEEDED.
VMAC119 42.065 Only first segment SMF 119 Subtype 44 was output.
VMAC113 42.064 IBM changed z/16 RNI coeff from 4.3 to 4.2
VMAC1415 42.063 z/OS 3.1 new variables in TYPE1415.
VMAC30 42.062 Variables IOUNITS IOCOEFF MSOUNITS MSOCOEFF zeroed.
VMAC102 42.054 SMF 102 IFCID 196 misaligned, IBM stored zero.
VMAC80A 42.052 TYPE80A INPUT EXCEEDED, long TOKXUGROUPS.field.
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at https://www.mxg.com.
Inverse chronological list of all Changes in MXG Version 42.03
NEXTCHANGE:
====== CHANGES THRU 42.072 ARE IN MXG 42.03 DATED Sep 15, 2024 =========
Change 42.072 You can now send MQ data to a separate database with
BLDSMPDB different numbers of pseudo-GDGs on ASCII.
VMXGALOC To use you must either use the reroutex options in
Sep 13, 2024 BLDSMPDB or override the _L****** macro in MACKEEP.
Change 42.071 -Dataset TYP11906 variables IFINBITRT/IFOUBITRT/IFBITRATE
VMAC119 could have missing values because they were calculated
Sep 6, 2024 before DURATM had been correctly populated from IFDURTM.
-Dataset TYP11945 variable DM_ISDURATION incorrectly input
as datetime instead of duration.
Thanks to Karl Lasecki,CAS, USA.
Change 42.070 -Support for Martin Packer's RMF Processing Home Address
VMAC7072 Fields in his blog https://mainframeperformancetopics.com
VMAC74 /2024/06/14/engineering-part-7-rmf-processor-home-address
Aug 31, 2024 fields/
-Dataset TYPE74CF from SMF 74 Subtype 4 Segment PO:
Labels added for CFPBGS01-16 and CFPCCT01-16.
Numeric variables CFPTLE01-16 are set to missing values;
they were incorrectly created as numeric variables and
are replaced by $HEX32 Character variables CFPTLECH01-16.
-Dataset TYPE70PR from SMF 70 Logical Processor Section
Labels for SMF70CORTn (which should have been SMF70CORDn)
provide additional decoding of their contents.
SMF70CORT1='DISPATCH*LOC*TOPO NESTING*LEVEL1*ZERO'
SMF70CORT2='DISPATCH*LOC*TOPO NESTING*LEVEL2*CHIP'
SMF70CORT3='DISPATCH*LOC*TOPO NESTING*LEVEL3*DCM'
SMF70CORT4='DISPATCH*LOC*TOPO NESTING*LEVEL4*DRAWER'
SMF70CORT5='DISPATCH*LOC*TOPO NESTING*LEVEL5*ZERO'
SMF70CORT6='DISPATCH*LOC*TOPO NESTING*LEVEL6*ZERO'
Format MG070NL for SMF70MAXNL='MAXIMUM*TOPOLOGY*NESTING'
decodes these values:
0='0:NO INFORMATION'
1='1:NO NESTING STRUCTURE'
2='2:NESTING LEVELS AVAILABLE'
3='3:NESTING LEVELS AVAILABLE'
4='4:NESTING LEVELS AVAILABLE'
5='5:NESTING LEVELS AVAILABLE'
6='6:NESTING LEVELS AVAILABLE'
Thanks to Martin Packer,IBM, UK.
Change 42.069 VMACRMFV experiencing two issues with zoS 3.1
VMACRMFV -ERROR: Array subscript out of range at line 22512
Sug 22, 2024 -Incorrect navigation to service/report class data zos 3.1
Failing instruction (ACTTIME=RTSTHR) occurs when all
buckets in RCDDEN are zero and the DO loop sweeping the
array exits with the implied array element pointer left
at 15 (beyond the array boundary).
With 3.1 the Resource collection data entry added
RCDSRVFLG and a two byte reserved field that triggered
mis-aligning the class data input statement. Navigation
to the class data now makes use of the RCDSCOF/RCDRCOF
plus RCDCLX fields to locate the class data.
Thanks to Kurt Gramling, TSYS, USA.
Change 42.068 Variable RACF263 path name has been increased to maximum
VMAC80a length 1024 from the arbitrary length 255 definition of
Aug 21, 2024 the pathname.
Thanks to David Obernoder, DATEV eG, GERMANY.
Change 42.067 -Corrections/additions in TYP11938 Subtype 38 dataset.
VMAC119 Only first segment was outputis corrected.
Aug 17, 2024 Variable DM_LSDURATION formatted TIME12.2..
Variable DM_LSPNETID was not Kept.
Two new variables added.
DM_LSRMTHOSTNAME.
DM_LSEID ='SMC-D*ENTERISE*ID*EID'
Variables input as $CHAR format $HEX corrections
DM_LSLCLGID DM_LSRMTGID $HEX16.
Thanks to Karl Lasecki,CAS, USA.
Change 42.066 The label for IECZSTC3='ZSORT*PH1*TCB TIME is corrected
VMAC16 to 'ZSORT*PH3*TCB TIME'.
Aug 5, 2024
Thanks to John Donoghue, AIB, IRELAND>
Change 42.065 Only the first segment of SMF 119 Subtype 44 was output..
VMAC119
Aug 5, 2024
Thanks to Svend Zaunick, F-I, GERMANY.
Thanks to Fynn Schoelzel, F-I, GERMANY.
Change 42.064 IBM Changed the z/16 coefficient for RNI from 4.3 to 4.1.
ASUM113 Doc is at https://www.ibm.com/support/pages/node/6354583.
VMAC113
Aug 5, 2024
Thanks to John Burg, IBM, USA.
Change 42.063 Updates in z/OS 3.1 SMF Manual dated Jul 23, 2024;
TYPE1415 -TYPE1415 new variables
Jul 29, 2024 DSENCRYP='DSENCRYP*TOK'
DSENHKEY='DSENCARC*HKEY'
DSENCREJ='DSENCREJ'
-TYPE99Q2 Support for APAR OA65652 added by Change 42.022.
Change 42.062 Variables IOUNITS IOCOEFF MSOUNITS MSOCOEFF are zero.in
TYPE30 TYPE30xx and TYPE72GO datasets starting in z/OS 2.5/3.1.
TYPE7072 IBM fields R723CIOC R723MIOC R723CMSO R723MMSO are listed
Jul 29, 2024 "always zero" in the SMF Manual for 2.5 dated May 24,2022
and SMF03LOC SMF30MSC coefficients are "always zero" in
the SMF manual for z/OS 3.1 dated Apr 19, 2024. And the
variable EXCPRMF in TYPE30xx is also zero as it was based
on IOUNITS. I've not found any IBM notes on when/why.
Change 42.061 Variables SMF70PMU='AVG BLKED*DISPATCH*UNITS*PROMOTED' in
TYPE7072 dataset TYPE70 was incorrectly calculated.
Jul 24, 2024
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.060 MXG TYPExxxx members normally output dataset to WORK,
TYPE99 while TYPSxxxx members sort and output to PDB, but if all
Jul 18, 2024 dataset's have accumulated data, the _Sxxxx Product Sort
macro is added in the TYPExxxx member, or if only some of
the datasets are accumulated, the _Sdddddd Data Set Sort
macro is added so that the DIF() functions are invoked to
deaccumulate and output the correct data to PDB.
These SMF datasets have accumulated data:
all datasets 99 103 113 79
some datasets MQM NPM TPX WECR.
The _S99 was missing in MXG 42.01 and 42.02 in TYPE99.
Thanks to Keith C. Shaffer, Evernorth, USA.
Thanks to Altino Pimentel, Evernorth, USA.
Change 42.059 Dataset ASUM70GL the Group Capacity LPAR detail, variable
VMXG70PR MINENTIT, the Minimum Entitlement of an LPAR in a
Jul 17, 2024 capacity group, was incorrectly calculated as the LPARs
group weighted share of the total complex MSU (which,
among other thjngs, is greater than the complex weighted
share of the total complex MSUs). MINENTIT incorrectly
was greater than theMAXENTIT.
Thanks to Matthew T. Chappell, Queensland Government, AUSTRALIA
Change 42.058 New variables added to DCOLLECT DCOLMIGS Data Set
VMACDCOL UM_CLOUD_NAME_LENGTH='CLOUD*CONNECTION*NAME*LENGTH'
Jul 16, 2024 UM_CLOUD_NAME='CLOUD*NETWORK*CONNECTION*NAME'
UM_CONTAINER_NAME='CLOUD*NETWORK*CONNECTION*NAME'
UM_OBJ_NUMBER= 'NUMBER*OF OBJECTS*STORED'
UM_CLD_COMP_PERCENT='PERCENT*SAVED BY*TCT COMPRESSION'
Thanks to Raj C. Xavier, FMR, USA.
Thanks to Kulvinder Makkar,FMR,USA.
Change 42.057 If you run CICINTRV and look at the log you would see a
UTILDUR bogus MXGWARN message. It can be ignored as it is a
VMXGCICI result of VMXGSUM printing the code it generates. UTILDUR
Jul 15, 2024 now checks the durations in the data and if it is larger
than the requested interval produces an MXGWARN message.
Tkanks to John Roderick, DC GOV, USA.
Change 42,056 Example 4 failed. Doc was corrected and member
UTILBLDP TYPEJOBS was created.
TYPEJOBS
JCLPDBJB
Jul 4, 2024
Change 42.055 New variables added to ASUM1131 dataset by Martin show
ASUM113 the components of MEMP, the Percent Sourced from Memory:
VMAC113 MEMLP ='PERCENT*SOURCED*SAME*DRAWER'
Jul 4, 2024 MEMRP ='PERCENT*SOURCED*OTHER*DRAWER'
The calculations are for z/16 and exposed MXG values for
MEMP used the z/15 equations.
Thanks to Michael.Fleissig, Huk-Coburg, Germany
Thanks to Martin Packer, IBM, ENGLAND.
Change 42.054 SMF 102 IFCID 196 dataset T102S196 was misaligned because
VMAC102 the undocumented IBM change to store zero in the triplet
Jul 3, 2024 length field and store the length value in the first two
bytes of the segment was not correctly handled in MXG.
Thanks to James Lieser, Optum, USA.
Thanks to Peter Vikeras, Optum,USA
Change 42.053 If you used SPINSTC, you could get 0 obs in pdb.jobs
BUILD005 because of faulty logic. The code checked the value of
BUIL3005 SPINSTC and entered a DO loop that then checked the
Jul 2, 2024 typetask for STC and prevented the ELSE DO from from
being executed and setting OKFLAG from being set to 1
which causes jobs to be output. The check for STC was
added to check for SPINSTC and ELSE DO removed.
Thanks to Shivang Sharma,ENSONO, USA.
Thanks to Dana A Mccreary, UPS, USA
Thanks to Arnold Kim, UPS, USA.
Thanks to D. Barry, UPS, USA.
Change 42.052 -TYPE80A INPUT EXCEEDED due to unexpected short length 7
VMAC80A for TOKXUGROUPS field, now using $VARYING INFORMAT.
Jun 29, 2024 -Support for TYPE80Z TOKXRGROUPS field also using VARYING.
Thanks to Swapna Gavini, Kyndryl, AUSTRALIA.
Change 42.051 Utility program IMACDSCK finds all DSNAMES.is enhanced to
EXDCODSN look at datasets created by DCOLLECT.
EXDCOCLU
EXDCOMIG
EXDCOBKP
IMACDSCK
Jun 28, 2024
Thanks to Scott Barry, SBBTechLLC, USA.
Change 42.050 Format $MGCICDS for variables SMDDSAIN in dataset CICSMD
FORMATS and variable SMSDSAIN in dataset CICSMDSA values 0Ax-0Dx.
Jun 25, 2024 were added.
Thanks to Matthew T. Chappell, Queensland Government, AUSTRALIA
Change 42.049 SMF 119 Subtype 38 INPUT STATEMENT EXCEEDED INVALID DATA
VMAC119 for PIB4 because lines 4035-4040 were missing the period
Jun 24, 2024 at the end of the &PIB.4. INFORMAT. SAS Only detects the
error when that code is executed, i.e. for a subtype=38.
Thanks to Janet Harris, NTRS, USA.
Thanks to Leopoldo E. Esparza, NTRS, USA.
Thanks to Suresh Upputuri, NTRS, USA.
====== CHANGES THRU 42.048 ARE IN MXG 42.02 DATED Jun 22, 2024 =========
Change 42.048 -IFLMSUHR was calculated incorrectly and additional OBS
VMXG70PR were output because a SET was used instead of a MERGE.
Jun 22, 2024 This caused incorrect ASUMCEC observation counts and
some incorrect duration values.that were introduced in
MXG Version 42.01.
-MSUHR totals were wrong (ZIPMSUHR ICFMSUHR IFLMSUHR
IFAMSUHR)
-ASUM70GC dataset was incorrectly summarized at the
LPAR level instead of capacity group.
Thanks to Matthew T. Chappell, Queensland Government, AUSTRALIA
Change 42.047 New variables added to TYP11912TLS dataset:
FORMATS S11912SS_TLS_SRV_HS_SM /*SERVER*HS_SIG_METHOD*/
VMAC119 S11912SS_TLS_CLI_HS_SM /*CLIENT*HS_SIG_METHOD*/
Jun 20, 2024 S11912SS_TLS_NEG_KEY_SH /*NEGOTIATED*KEY_SHARE*/
Thanks to Luis Mendoza, ICE, USA.
Change 42.046 Modified to check FMTSEARCH for values other than (WORK
VMXGINIT LIBRARY) or to see if you are using WPS; then the check
Jun 15, 2024 for old or non-existent formats is bypassed. Using
IMACFMTS and keeping formats in LIBRARY rather than
using FMTSEARCH is recommended. NOTE: on z/OS, those
ddnames must have DISP=NEW or OLD if you plan to add or'
modify formats.
Change 42.045 ZERT dataset TYP11912DN and TYP11912SUM were missing obs
VMAC119 because the triplet count fields NUM11906 and NUM11907
Jun 14, 2024 in Subtype 12 records were always one, but IBM never
documented that one segment could contain many obs and
never provided the actual count. The DO to NUM11906/07
was replaced with DO WHILE LENLEFT logic to determine the
actual number of observations that are in the segment.
Thanks to Jorge Fong, City of New York, USA.
Change 42.044 Now allows you to specify how many LPARS to keep in
VMXG70PR ASUMCEC/70pr New parameter LPARS2KEEP= lets you specify
Jun 7, 2024 the number of LPARS to keep. This can significantly
reduce the size of the resulting dataset. In one test
using 20 the size of ASUMCEC was reduced by 61%! In order
to simplify the logic 5 10 20 or 30 LPARS are kept so if
you specify 4 5 are kept. If you specify a number smaller
than the number of LPARS found in the data a WARNING
message is created and LPARS2KEEP is set to a null
string.
Change 42.043 If you added a PROC COPY after CICINTRV it failed since
CICINTRV the datsets had been deleted by VMXGCICI. Deletion was
VMXGCICI removed from VMXGCICI and left inside of comments in
JUN 3, 2024 CICINTRV.
Thanks to Keith C. Shaffer, Evernorth, USA.
Change 42.042 CPU LOOP with SMF 82 SUBTYPE 40. SMF82_TAG '010F'x was
VMAC82 increased to 16 bytes.
Jun 3, 2024
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.041 TYPE102 IFCID 365 INPUT EXCEEDED RECORD MXG 42.01.
VMAC102 New fields added that exposed issues with QLSTLEN not
May 27, 2024 matching actual length of data.
QLSTNTPLH='TERMINATED*HIGH*PERFORMANCE'
QLSTNTILS='TERMINATED*TOP*SOCKET*CLOSED'
Thanks to John Kim, Morgan Stanley, USA
Change 42.040 The TYPE70 dataset has 18 Arrays with 255 variables that
VMAC7072 have suffix M0-M8,MA-MZ,YA-YC,ZA-ZZ.102-255 & start with
May 27, 2024 CPUEDT CPUPAT CPUPDT CPUWAI IFATYP IFAWAI
IORATE MVSWAI PCTCPB PCTIFB PCTONL PCTTPI
PCTZIB ZIPWAI LCPUDE LCPUWA PCTCIB CAI
that contain the metrics for each CPU.
It's highly likely that you have never used any of these
per-CPU variables in this poor design, because each array
is summed into the actual metric of interest that you
have been using, for example CPUEDTTM is the Effective
Dispatch Time for the interval and theren't any knobs
to turn for each of the individual CPUs. But there might
be a need to examine some of those individual CPU metrics
when SMT is active, which is why the TYPE70EN per-engine
dataset was created with a single set of variables and an
observation per engine per thread per interval so those
unwieldy array variables in TYPE70 are not really needed.
And that's good, because with SMT, they are incorrectly
stored in the wrong array entry. For example, the IORATEx
variables for CPU 0,1,2,and 3 are not in the expected
IORATE0/IORATE1/IORATE2/IORATE3 variables, but are found
in IORATE0/IORATE2/IORATE4 with missing values in those
IORATE1/3/5 variables: MXG confused CPUID with THREAD.
But as those individual rates are summed into the IORATE
variable which is the interval value, no data was lost.
Only a single MXG user has reported this error, and this
code was implemented in the Spring of 2015. With no other
reported issues with these unlikely-to-be-needed TYPE70
variables, and with the availability of TYPE70EN dataset,
and the exposure of creating a new problem in the very
complex support for the SMF 70 record, this error can not
be corrected safely.
Change 42.039 TYPE 119 formats $MG119CF and $MG119KA were corrected.
FORMATS
May 20, 2024
Thanks to Matthew T. Chappell, Queensland Government, AUSTRALIA
Change 42.038 Support new tokens TOKDB2 and TOKOWNERS in TYPE80TK.
VMAC80A
May 19, 2024
Thanks to Bruce Henson, CITIGROUP, ENGLAND
Thanks to Harald Seifert. HUK-COLBURG, GERMANY.
Change 42.037 New DB2 Zparms added to dataset T102S106.
VMAC102 MXG Variable IBM ZPARM
May 19, 2024 QWP4AUDIWU ALLOW_UPD_DEL_INS_WITH_UR
QWP4DSSAR DISALLOW_SSARAUTH
QWP4FCXC FLASHCOPY*XCXC
QWP4LSSIC LA_SINGLESEL_ISOCS_CDY
QWP4LIRO LOAD_RO_OBJECTS
QWP4MXUDF MAX_UDF
QWP4MXAIDC MAX_MEMORY_FOR_AI_DATA_CACHING
QWP4PKGDEPLVL PACKAGE_DEPENDENCY_LEVEL
QWP4RTNP REORG_TS_NOPAD_DEFAULT
QWP4LTMX SPREG_LOCK_TIMEOUT_MAX
QWP1STIMM STATIME_MAIN
QWP4STPGS STATPGSAMP
QWP4TCNE TABLE_COL_NAME_EXPANSION
QWP4TSCT TS_COMPRESSION_TYPE
QWP4UTHIST UTILITY_HISTORY
QWP4UBCDC UTILS_BLOCK_FOR_CDC
Thanks to Lai Fai Wong, Bank of America, USA.
Change 42.036 Support for TOKDANAM values XUHSTORY XUTIMING XUGROUPS in
VMAC80A TYPE80TK.
May 15, 2024 Support for EV44VAL length greater than 80 error messages
RACF EV(44) ERROR. INVALID RACFDLNN and INPUT EXCEEDED.
Thanks to Bheema Linga Prasad Kammara, NAB, AUSTRALIA.
Thanks to Bhuvaneshwari Shanmugam, NAB, AUSTRALIA.
Change 42.035 Change 41.085 opens the format library to check and be
VMXGINIT sure it is current. That means that if you use fmtsearch
May 15, 2024 to point at user formats you must specify disp=old on
the dd statement if you want to update it (zOS only).
Note: This Change was doc only. See Change 42.046.
Thanks to Raymond Smith, OPTUM, USA.
Change 42.034 -Using a TAPE (SEQUENTIAL) data library for the PDB data
VMXGSUM library has NEVER been wise due to the restrictions that
May 15, 2024 only one dataset can be open at a time, which required
protection in BUILDPDB logic, and, in the past, the time
needed for rewinds, now nonexistent with virtual tape,
but also the loss of datasets after an existing dataset
if that existing dataset is updated. MXG has protected
the BUILDPDB process to allow use of tape, but a change
to VMXGSUM is needed to permit that process. There has
always been a warning message for SEQUENTIAL PDB DD.
Change 42.033 -IMS LOG ENQFLAG=0CX and FLAG2=41X is output to IMS35P.
VMACIMS -Variable LG50RTKN kept in IMS5950 and TPCPRTKN kept in
May 9, 2024 IMS56FA.
Thanks to Oscar Curero, NTTDATA, SPAIN
Change 42.032 Documentation only, note that only one DEST will be set.
VGETDEST
May 1, 2024
Change 42.031 -New variable MAXWKSET 'MAXIMUM*WORKING*SET (K BYTES)' is
BUILD005 created in PDB.JOBS with the maximum value of any step.
BUIL3005 -Using a TAPE (SEQUENTIAL) data library for the PDB data
SPUNJOBS library has NEVER been wise due to all of the rewinds
May 13, 2024 needed to retrieve PDB datasets, MXG has protected the
BUILDPDB process to support it, but a change to VMXGSUM
is needed to protect that process. And, virtual tape has
mitigated those concerns.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 42.030 -The TYPE30_6 Early Address Space SMF 30 subtype 6 records
VMAC30 variables SRVSRBTM and SRVTCBTM and CPUTOTTM were wrong
Apr 25, 2024 when BOOST was active because they were calculated prior
to the DIF() deaccumulate logic. These three variables
are not the standard CPUTCBTM CPUSRBTM and CPUTM times
that are in the SMF 30 records. The three variables are
calculated from Service Units and added when it was
claimed that they were more accurate than TIME fields.
-Variable BOOSTCLASS was wrong if BOOSTACTIVE was missing
value in the TYPE30xx datasets, when it should have been
blank.
Thanks to Stephen Hoar, Lloyds Banking, ENGLAND.
Change 42.028 DELTATM in PDB.VXINTUSR was incorrectly divided by the
VMACVMXA number of configured engines ENGCONFG; that division is
Apr 18, 2024 removed.
Thanks to Stephen Hoar, Lloyds Banking, ENGLAND.
Change 42.027 Support for IBM Dependency Based Build SMF 122 Subtype 2.
VMAC122A Note the product suffix is 122A because there was an
Apr 18, 2024 earlier Tivoli SMF 122 record.
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.026 DCB Attributes RECFM=F LRECL=660 are added to the INFILE
VMACCTLT CONTROLT so that file can be read from a pipe. Normally,
Apr 9, 2024 the FILENAME statement is used to supply attributes but
those attributes are not available with a pipe.
Since the CONTROL-T file is unlikely to ever be changed,
there was no need to use macro variables for them.
Change 42.025 Support for APAR OA61951 which added RACF PHRASEINT, the
FORMATS PASSWORD PHRASE CHANGE INTERVAL for both PASSWORD and for
VMAC80A SETROPTS with these added changes:
Apr 3, 2024 -Added new KW18 vars for PHRASEINT.
-Commented out the references to KW24S102 to KW24S109,
these were created from an IBM reserved field in error.
The correct values are in the following byte and already
decoded as KW24SP70- KW24SP77. Unfortunately the
subsequent keyword specified and keyword ignored flag
numbers are now out of sync as a result.
-Removed newly added KW24PA00-KW24PA01 as KW24PALG turned
out not to be a bit masked field.
https://www.ibm.com/docs/en/zos/3.1.0?topic=records-reco
rd-type-80-racf-processing-record incorrectly shows
these values as bits 0 and 1 but data had a value of 01X
for KDFAES. KW24PALG is now formatted to display values.
ftp://public.dhe.ibm.com/s390/zos/racf/pdf/oa43999.pdf
shows the correct definition (0=existing algorithm,
1=KDFAES).
-Flags KW24I108, KW24I109, KW24S116, KW24S117 (originally
for EIMREGISTRY and NOEIMREGISTRY) have been repurposed,
I108/S116 is now ENHANCEDGENERICOWNER and I109/S117 is a
reserved bit. This changed in the manuals in z/OS V2R3.
-Corrected XMBALLRACF to XBMALLRACF in two labels.
-KW24SCLV label has been changed from
"SECURITY*AUDIT*VALUE" to "SECLABEL*AUDIT*VALUE"
-KW24SP40 fixed typo in label
-Added KW24MLSO KW24POPT KW24PWSR to $HEX formats and to
&MXGNOTRA.
-Fixed CHGINTRV to set missing when 0FFX, not 0FFFFFFFFX.
Confirmed this with a PASSWORD USER(xxx) NOINTERVAL.
-Dataset TYPE8018 new variables CHGINTRV PHRINTRV.
-Dataset TYPE8024 new variables KW24PALG KW24PHRI.
-Variables USRSEKTN KW24PWSR are $HEX formatted.
Thanks to Matthew T Chappell, Queensland Government, AUSTRALIA.
Change 42.024 Variable SIISPCT for z16 in SMF 113 datasets, using E164
ASUM1134 counter instead of E170.
VMAC113
Mar 21, 2024
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.023 ANAL9914 report CECTYPE test did not include Z16 so no
ANAL9914 REPORT=JIM was produced, even though there is no change
Mar 19, 2024 for the 16.
Thanks to Marvin L. Silverman, Bank of America, USA.
====== CHANGES THRU 42.022 ARE IN MXG 42.01 DATED MAR 15, 2024 =========
Change 42.022 Support for APAR OA65652 which adds variables to TYPE99Q2
VMAC99 PQAVQREQ='AVERAGE*QUEUED*REQUESTS'
Mar 12, 2024 PQBATQTM='BATCH*QUEUE*TIME'
PQBATSEL='BATCH*JOBS*SELECTED'
Change 42.021 INVALID REFERBACK IN THE COND FIELD in JCLASMXG example
JCLASMXG that assembles all MXG ASM members due to ASMRMFX in the
Mar 9, 2024 COND instead of ASMRMFI.
Thanks to MP Welch, Bank of America, USA.
Change 42.020 Using CICSIFUE under WPS results in U4038 LE abend with
CICSIFUE the following error message:
Mar 12, 2024 CEE3194E An attempt was made to initialize an AMODE24
program when the XPLINK(ON) run-time option was in
effect. AMODE24 programs are not supported in an
XPLINK environment.
So AMODE 31 and RMODE 31 statements were added to each
CSECT in CICSIFUE. CICSIFUE is the z/OS Exit to
decompress CICS and DB2 SMF records; see EXITCICS to
install the exit, which saves significant CPU Time
processing those data records.
Change 42.019 DB2 SMF 102 IFCID 365 now has the Length QWT02R2L zero
VMAC102 requiring revision to read the Length at the Offset.
Mar 6, 2024 I can find no documentation when individual IFCIDS are
being changed, I fear maybe every time an IFCID is to
be updated. The advantage of the header zero length
is that the individual segments can be different lengths.
Thanks to Harald Seifert, HUK-COLBURG, GERMANY.
Change 42.018 When I/O velocity is not enabled, the VELOCCPU was not
VMAC7072 correct; it should have been set to VELOCITY. Observed
Mar 6, 2024 that R723CTOU contains both GP and IIP usage but R723CCUS
only contains GP usage.
Thanks to Stephen Hoar, Lloyds Banking, ENGLAND.
Change 42.017 ZERT SMF 119 Subtype 12 dataset TYP11912SUM (ZERT COMMON)
VMAC119 2024 observations were not output if there was a sixth triplet
Mar 1, 2024 (Certificate DN) segment, causing S11912SASECPROTOS to
only contain 0 (NO CRYPTO) and S11912SASESSIONID only C
so none of the observations were for encrypted sessions..
Thanks to Richard A Warren, USBank, USA.
Thanks to ???, IBM SMF 119 Support, USA.
Change 42.016 Support for RACF IRRDBU00 Unload RACTYPE=0151 creates new
EXRAC151 RACF0151 dataset 'Group CSDATA Custom Fields'.
IMACRACF GPCSD_NAME ='GROUP*NAME'
VMACRACF GPCSD_TYPE ='DATA*TYPE*FOR*CUSTOM*FIELD'
VMXGINIT GPCSD_KEY ='CUSTOM*FIELD*KEYWORD'
Mar 1, 2024 GPCSD_VALUE='CUSTOM*FIELD*VALUE'
Thanks to Nathan Battles, Navy Federal, USA.
Change 42.015 -SMF70CSF was missing for ICF IFL LPARS. Now added as
VMXG70PR the MAX value for all LPARS. ICF/IFL MSU values were
Feb 25, 2024 added to ASUMCELP. Count of ICF LPARS added to ASUMCEC.
Mar 9, 2024 -Unrelated, could have a SORT ERROR on GMTOFFTM and the
Mar 15, 2024 variable was not carried forward into ASUMCELP dataset.
Thanks to Scott Barry, SBBTechLLC, USA.
Thanks to Perry Metzel, Alight, USA.
Change 42.014 NOTE: INVALID NUMERIC DATA "xxxxxxxx'x for some datetime
VMACBETA variables in BETA30 and BETA31 datasets due to typo were
Feb 20, 2024 present since last update in 2021. No ABEND, just NOTES.
Thanks to Tino Buschmann, ITZBund, GERMANY.
Change 42.013 -INPUT EXCEDED SMF 102 IFCID 172 when QWT02R2L NOT ZERO.
VMAC102 Change 41.112 supported the undocumented case when the
Feb 20, 2024 length field was zero, but records with zero length were
not correctly decoded.
-ZERO OBSERVATIONS in T102S196 due to debugging statement
IF QWTR22L=196 THEN DELETE. But the 196 has similar
length issues as the preceding 172 structure. Code was
revised and tested for QWT02R2N=1 records, but records
with QWT02R2N=2 are needed to verify.
Thanks to John Milne, Kyndryl, AUSTRALIA.
Change 42.012 LINUX ONLY. ASCII IEBUPDTE to build directory of files
IEBUPDTE would have build directories with a backslash \ rather
Feb 19, 2024 than a forwardslash / if the last character was not /.
Change 42.011 Testing corrections. S031PSTP had missing period in the
VMACBETA $EBCDIC8 informat, but subtype 30 and 31 are misaligned
Feb 19, 2024 and doc is needed to investigate.
Thanks to Tino Buschmann, ITZBund, GERMANY
Change 42.010 Variable CRYIAES='AVG BYTES*PER AES ENCRYPT*SERVICE CALL'
VMAC7072 was incorrectly formatted as a time when it is just a
Feb 18, 2024 numeric value.
Thanks to Graham Harris, Natwest, ENGLAND.
Change 42.009 Support for APAR OA65055 which adds JAVA CP and zIIP
VMAC99 service units to dataset TYPE99SL:
Feb 15, 2024 S99RTCAPLEADTIME ='RTCAP*LEAD*TIME*MINUTES'
S99TIME_TO_CAP ='TIME*TO*CAP*SECONDS'
S99TIME_TO_CAP_GROUP='TIME*TO*CAP*GROUP*SECONDS'
S99SUS_ZIIP ='ZIIP*ELIG*UNWEIGH*SU ON*ZIIP'
S99SUS_ZIIP_ON_CP ='ZIIP*ELIG*UNWEIGH*SU ONCP'
S99SUS_JAVA_ON_ZIIP ='ZIIP*ELIG*UNWEIGH*JAVA SU*ON ZIIP'
S99SUS_JAVA_ON_CP ='ZIIP*ELIG*UNWEIGH*JAVA SU*ON CP'
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.008 Support for APAR OA65055 which adds JAVA CP and zIIP time
VMAC30 to TYPE30_V, TYPE30_4, TYPE30_5, PDB.SMFINTRV datasets:
Feb 8, 2024 SMF30_TIME_JAVA_ON_ZIIP ='JAVA*WORK*ON ZIP'
SMF30_ENCLAVE_TIME_JAVA_ON_ZIIP ='JAVA*ENCLAVE*ON ZIP'
SMF30_DEPENC_TIME_JAVA_ON_ZIIP ='JAVA*DEPENC*ON*ZIP'
SMF30_TIME_JAVA_ON_CP ='JAVA*WORK*ON*CP'
SMF30_ENCLAVE_TIME_JAVA_ON_CP ='JAVA*ENCLAVE*ON*CP'
SMF30_DEPENC_TIME_JAVA_ON_CP ='JAVA*DEPENC*ON*CP'
Thanks to Jan Tielemans, KBC, BELGIUM
Change 42.007 Added VMXGSUM parameter MXGNOECHO= to suppress printing
VMXGSUM all of the VMXGSUM parameters, enabled by specifying YES
Feb 8, 2024 in your VMXGSUM invocation. Added %GLOBAL macro variable
NOMXGECHO which can be externally set before VMXGSUM is
invoked, with %LET NOMXGECHO=YES; to suppress listing.
Thanks to Harald Seifert, HUK-COLBURG, GERMANY.
Change 42.006 INPUT STATEMENT EXCEEDED for Omegamon for CICS ONDV
VMAC112 for SUPRA records. The MXG TEST for FOCVER GE 'V560'
Feb 6, 2024 should have been for V550 to INPUT SATTACH since that
field was present in the V550 record and its INPUT
then aligned SUSEDF and SRECLEN correctly.
Thanks to Gaetan Martel, Intact, CANADA
Change 42.005 -JCL examples added and comments revised to show how to
GRAFCEC use ODS for reports instead of the MXGODSxxxx arguments
Feb 7, 2024 that should not have been created.
-Corrected duplicate BY statement missed by SAS.
Thanks to Tom Maccabe, Dominion Energy, USA.
Change 42.004 Sgnifcant overhaul of this report/analysis member for MQ:
ANAL115 New parameters added to simplify report criteria.
Jan 31, 2024 INCODECFS=code to limit CFS report
INCODEBUF=COde to limit buffer report
INCODELOG=code to limit LOG report
INCODEMSG=code to limit db2 REPORTS
Parameters were put in alpha order.
TY115201 ADDED as input to LOG report
TY115215 ADDED as input to buffer report
Change 42.003 If you run with RUNWEEK=NO and FIRSTRUN=YES option OBS=0
BLDSMPDB was set to copy PDB to days of week but 0 OBS was not
Jan 18, 2024 reset so anything after BUILDPDB had 0 OBS. Statement was
moved so that it will always be run.
Thanks to Jim Poletti, Edward Jones, USA.
Change 42.002 INPUT STATEMENT EXCEEDED reading subtype 2 Statistics
UCICSCNT records which are not compressed because MXGDECOM was
Jan 17, 2024 incorrectly invoked for subtypes one and two.
Thanks to Raymond Smith, OPTUM, USA.
Thanks to Ronald W. Bassett, OPTUM, USA.
Change 42.001 MXG 41.06 and 41.41. Change 41.112 accidentally changed
VMAC102 the INPUT names for QWT02R4L-QWT02R9L to QWT02R4LX-R9LX
Jan 12, 2024 so the correct named variables were missing values and
those segments were not input, causing missing values for
all of the variables that should have been input.
Impacted all IFCIDS with QWHSNSDA GT 4.
Thanks to Jan Tielemans, KBC, BELGIUM
LASTCHANGE: Version 42.