COPYRIGHT (C) 1984-2023 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES 40.40
=========================MEMBER=CHANGE40================================
/* COPYRIGHT (C) 1984-2023 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG VERSION 40.40 is dated Feb 3, 2023, thru Change 40.162.
MXG VERSION 40.07 was dated Jan 16, 2023, thru Change 40.154.
MXG VERSION 40.06 was dated Oct 23, 2022, thru Change 40.134.
MXG VERSION 40.05 was dated Aug 15, 2022, thru Change 40.101.
MXG VERSION 40.04 was dated Jun 29, 2022, thru Change 40.078.
MXG VERSION 40.03 was dated Jun 23, 2022, thru Change 40.077.
First MXG VERSION 40.03 was dated Jun 15, 2022, thru Change 40.073.
MXG VERSION 40.02 was dated May 5, 2022, thru Change 40.055.
MXG VERSION 40.01 was dated Mar 5, 2022, thru Change 40.032.
First MXG VERSION 40.01 was dated Mar 4, 2022, thru Change 40.031.
ANNUAL MXG VERSION 39.39 was dated Jan 5, 2022, thru Change 39.227.
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 40.40 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 40.40.
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 40.40 DATED Feb 3, 2023, THRU CHANGE 40.162.
==MAJOR CHANGES ADDED IN MXG 40.40, DATED Feb 3, 2023 THRU 40.162.====
ENHANCEMENTS
VMAC113 40.162 Support for z16 AI WAIUCPU/CAIUCPU/AIUCPU/AIUCPI
VMAC1154 40.158 Initial Support 4 subtypes of SMF 1154 Compliance
==MAJOR CHANGES ADDED IN MXG 40.07, DATED Jan 16, 2023 THRU 40.154.====
INCOMPATIBILITY SUPPORTED
TYPERMFX 40.150 IBM change to SMF 70.1 SPLIT records, TYPE70PR IMPACT
Requires REASSEMBLY of SPLIT into VBS LRECL GT 32760
Only sites with many LPARS & ENGINES have 70.1 splits
USE RMFSPLIT program to see if you have SPLIT 70.1.
See Change 40.150 and 40.150A for reassembly support.
ERRORS CORRECTED
VMXGGETM 40.147 UTILGETM utility Memory Failure SAS Hot Fix 66883.
VMACVMXA 40.141 OUT OF ORDER error sorting VXUSEACT, BY list wrong.
VMACVMXA 40.140 RNI in VXPRCMFC was always zero, ++ syntax accepted.
VMACCIMS 40.139 UOWTIME in CIMSTRAN wrong prevented CICSTRAN merge.
VMACDB2H 40.138 QWHCCTKN QWHCEUID QWHCEUTX QWHCEUWN not %U Unicode.
VMAC7072 40.137 BOOSTACTIVE=2 /*BOTH*/ was never tested.
VMXGINIT 40.136 SAS VIYA error, blank needed after close paren.
ENHANCEMENTS
VMAC115 40.154 Support for SMF 115 Subtype 216 creates TY115216.
ZMAC110 40.149 Possible Update for CICS/TS 6.2, not data tested yet.
VMAC99 40.148 Support for TYPE 99 Subtypes 9 and 10.
ASUM70PR 40.146 ICF LPARs can be output in ASUMCELP and ASUM70LP.
ANALCEC 40.145 New report on how LPARs on your CEC
VMAC102 40.135 DB2 Function Level 501 revised labels new fields.
==MAJOR CHANGES ADDED IN MXG 40.06, DATED Oct 23, 2022 THRU 40.134.====
ENHANCEMENTS
TYPE113 40.121 TYPE113 can only validly process one CPU type.
TYPE110 40.129 Support for CICS/TS 6.1 Stat variables in CICWBG.
TYPE110 40.129 Support for CICS/TS 6.1 new CICTLS Stat dataset.
GRAFCEC 40.126 Support for TREND data restored.
SMFMANUL 40.125 Updates from Sep 26, 2022 SMF Manual Refresh.
ERRORS CORRECTED
TYPE0 40.127 Zero obs in PDB.IPL dataset for some IPLs.
TYPE90A 40.107 Correction for TYPE9040 Boost variable SMF9040T.
TYPE30 40.105 INTBTIME/INTETIME Missing in SMFINTRV corrected.
TYPE7072 40.104 Variable SMF70TYP in TYPE70PR always 2:IIP.
UTILEXCL 40.100 CICS/TS 6.1 ERROR 22-322, comma should be period.
IBM APARS
TYPE7072 40.102 IBM APAR OA62064 corrects CPUSER/SMF70SER '5555'X.
==MAJOR CHANGES ADDED IN MXG 40.05, DATED Aug 15, 2022 THRU 40.101.====
ERRORS CORRECTED
UTILEXCL 40.100 CICS/TS 6.1 SOFLAG SYNTAX ERROR IN CREATED IMACEXCL.
TYPE30 40.098 MXG 40.01 only INPUT EXCEEDED,SMF30CONFOLOW invalid.
TYPE74 40.096 TYPE749 PCIE Statistics only first bucket was output.
VMAC119 40.086 TYP11911 variables corrected, formats updated.
VMAC73 40.084 Invalid counters SMF73CMG=2 when CHPID was Varied.
ENHANCEMENTS
VMXGHSM 40.099 z/OS 2.5 dataset SFSMSHSM new variables added.
VMACVMXA 40.095 Support for z/VM 7.2 MONWRITE VXPRCMFC HIS counters.
TECHNOTE 40.090 MXG Variables/Datasets that include RUCSA metrics.
VMACSVIE 40.089 New variables added to SV34TRAN and SV35TRAN.
VMAC42 40.088 Support for APAR OA59611 adds S42DS2MV
VMAC30 40.087 Dedicated Memory variables added.
VMACRMFV 40.085 New ZRBASI time variables added in z/OS 2.4 & 2.5.
BUILD005 40.082 Sixty variables added to TYPE30_4 now in PDB.STEPS.
==MAJOR CHANGES ADDED IN MXG 40.04, DATED Jun 29, 2022 THRU 40.078.====
Change 40.078 MXG 39.09 and earlier fail with APAR OA61811/OA62502.
VMAC7072 due to an MXG error for SMF 72 Subtype 3 TYPE72GO that
Jun 25, 2022 failed to test for new fields after the last segment,
which caused INPUT mis-alignment and invalid data values.
-WE STRONGLY SUGGEST YOU INSTALL THE CURRENT MXG 40.04
WHICH AVOIDS THE COMPLEXITY OF THE BELOW CIRCUMVENTION
AND PROVIDES SIGNIFICANT OTHER ENHANCEMENTS AFTER YOUR .
BACKLEVEL VERSION. PLEASE USE THE FORM AT
HTTPS://WWW.MXG.COM/SOFTWARE_DOWNLOAD_REQUEST
You can circumvent this MXG error by:
-Download files at http://www.mxg.com/downloads/
The APAR inserted new fields in SMF 72 Subtype 3 TYPE72GO
that exposed an MXG coding error that failed to test for
new added fields after the last new segment, causing the
INPUT misalignment and invalid data values to be created.
There MAY be INVALID DATA FOR R723IFAT messages or other
fields printed, but those are accidental and there might
not be ANY log messages that the error occurred. And even
if there are INVALID DATA messages, they do not set a
CONDITION CODE, so there may be no clue on the log that
the error occurred.
MXG 39.39 thru MXG 40.03 correctly input the new data.
but only this change or MXG 40.04 has the protection for
additional new fields in any future IBM updates..
PTFs: z/OS 2.3 UJ07991
PTFs: z/OS 2.4 UJ07990
PTFs: z/OS 2.5 UJ07989
==MAJOR CHANGES ADDED IN MXG 40.03, DATED Jun 23, 2022 THRU 40.077.====
ERRORS CORRECTED
VGETDDS 40.075 MEMBER FROM 40.02 REPLACED FIRST 40.03 MEMBER
VMXGSET 40.075 MEMBER FROM 40.02 REPLACED FIRST 40.03 MEMBER
VMAC42 40.076 ERROR: SHORT 42 SUBTYPE 6 ACCESS METHOD SECTION.
ENHANCEMENTS
VMACNDM 40.074 NDMCT new TLSVERSION variable (1.1,1.2,1.3) added.
==MAJOR CHANGES ADDED IN MXG 40.03, DATED Jun 15, 2022 THRU 40.073.====
ERRORS CORRECTED
VMAC110 40.063 CICSTRAN variables DSAPTHTM JVMTHDTM MAXHTDTM wrong.
VMACBVIR 40.056 Dataset BVIR302 had only half the observations.
ENHANCEMENTS
FORMATS 40.062 TYPE119SSH KEX_METHOD and KEX_ALG $MG119KX updated.
VMACEDGR 40.061 Datasets EDGRDEXT and EDGRXEXT updates.
VMACRMFV 40.060 RMF III updates for ZRBRED, and FORMATS.
BUILD005 40.057 Protection for DUPLICATE TYPE30 SUBTYPE 1 message.
NEW SUPPORT
VMAC80A 40.059 Support for SMF 80 RACFTYPE=67 updated TYPE8081.
VMAC90A 40.058 Support for APAR OA60660 for TYPE9040 BOOST.
==MAJOR CHANGES ADDED IN MXG 40.02, DATED May 5,2022 THRU 40.055.
CHANGE 40.042 in MXG 40.02 is REQUIRED for CICS/TS 6.1 BETA 25+
which removed fields from CICS 110 Records (May 2022)..
Change 40.001 in MXG 40.01 was required for CICS/TS 6.1 BETA 22
(March 2022) which also incompatibly changed the CICS 110 records.
TYPE30 ABEND with MXG 40.01 with z/OS 2.5 or APAR OA61511 that
is corrected by Change 40.050 in MXG 40.02.
ERRORS CORRECTED
ASMRMFV 40.028 -ASMRMFV now accepts PARM='F=Y,T=Y' syntax (CC=08)
ASMRMFV 40.036 Logic for ZEROLP option corrected for CPCDB.
TECHNOTE 40.040 IBM APAR PH40410 corrects negative DB2 QPACZITM.
TYPE0 40.039 z/OS 2.5 TYPE 0 IPL lengths 78/83 not in table.
TYPE30 40.050 Support for OA61511 Crypto/NNPI counts in SMF 0 & 30.
TYPE7072 40.034 TYPE70 vars SMF70PMT/SMF70PMU were corrected.
TYPEDCOM 40.038 Reserved fields overlooked, misalignment.
TYPERMFV 40.029 ERROR: ARRAY SUBSCRIPT 51 OUT OF RANGE ARRAY ALHTNEXT
VMXG70PR 40.035 Vars SMF70GMU/SMF70CPA/SMF70WLA missing in ASUMCELP.
VMXGUOW 40.041 LIBNAME PDB NOT FOUND if did not ask for MQ data.
==MAJOR CHANGES ADDED IN MXG 40.01, DATED Mar 5, 2022 THRU 40.032.
NEW MXG VERSION 40.01 REQUIRED FOR CICS/TS 6.1 BETA 22.
TYPE110 40.001 CICS/TS 6.1 BETA 22 INSERT NEW FIELD, INCOMPATIBLE.
ERRORS CORRECTED
TYPE74 40.005 R742PUTx variables in TYPE74PA divided by 1E-6 twice.
TYPE16 40.014 BAD SMF 16 DFSORT, JOB had S222, INPUT EXCEEDED
TYPEVMXA 40.010 Broken Control Record ABEND z/VM 7.2.21.02.
TYPERMFV 40.029 ERROR: ARRAY SUBSCRIPT 51 OUT OF RANGE ARRAY ALHTNEXT
TYPERMFV 40.028 -ASMRMFV now accepts PARM='F=Y,T=Y' syntax (CC=08).
ENHANCEMENTS
ASUM115 40.002 Summarization/Trending for MQ SMF 115 and 116.
All of these enhancements are described in the Change Log, below.
========================================================================
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M7 (9.4M7),
"M7", or with options VERSIONLONG;
"SAS 9.4 (9.04.01M7P080520)" on z/OS
9.4 (TS04.01M7P08052020)" on ASCII.
SAS V9.4 M7 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 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 A support from SAS.
SAS V9.2 Was recommended, prior to 9.3, and was error-free with
MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to
use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2
Decompression Infile Exit. but SAS V9.2 does execute on
that platform.
9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.
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 36.11 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows 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 z16 processor data.
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 z16,
You must use separate SAS steps for each processor type and
read only SMF 113 from that processor type.
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 ASUM1131 dataset.
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 z16.
Change 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 z15 processor data.
The z15 and z15 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 & z16
SMF 113 change, but those back level versions could fail due
to other records changed by subsystem updates you made for the
z16 (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.
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
z16 NEW SMF113 values, NO ABEND See CHANGE 40.070 40.03
z16 MXG 38.07 OR LATER IS NEEDED.
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 SOFLAG Aug 15, 2022 40.05
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*
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
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 40.40.
1. Incompatibilities introduced in MXG 40.40:
a. Changes in MXG architecture made between 40.40 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 40.40:
Dataset/
Member Change Description
ANALCEC 40.145 New report on how LPARs on your CEC
ASMRMFV 40.028 -ASMRMFV now accepts PARM='F=Y,T=Y' syntax (CC=08)
ASMRMFV 40.036 Logic for ZEROLP option corrected for CPCDB.
ASUM115 40.002 Summarization/Trending for MQ SMF 115 and 116.
ASUM70PR 40.146 ICF LPARs can be output in ASUMCELP and ASUM70LP.
BUILD005 40.057 Protection for DUPLICATE TYPE30 SUBTYPE 1 message.
BUILD005 40.082 Sixty variables added to TYPE30_4 now in PDB.STEPS.
FORMATS 40.062 TYPE119SSH KEX_METHOD and KEX_ALG $MG119KX updated.
GRAFCEC 40.126 Support for TREND data restored.
JCLRMFX 40.150 Support for IBM INCOMPATIBLE CHANGE RMF 70 ST 1.
SMFMANUL 40.125 Updates from Sep 26, 2022 SMF Manual Refresh.
TECHNOTE 40.040 IBM APAR PH40410 corrects negative DB2 QPACZITM.
TECHNOTE 40.090 MXG Variables/Datasets that include RUCSA metrics.
TYPE0 40.039 z/OS 2.5 TYPE 0 IPL lengths 78/83 not in table.
TYPE0 40.127 Zero obs in PDB.IPL dataset for some IPLs.
TYPE110 40.001 CICS/TS 6.1 BETA 22 INSERT NEW FIELD, INCOMPATIBLE.
TYPE110 40.001 CICS/TS 6.1 OPEN BETA 22 REQUIRES MXG 40.01 INCOMPAT.
TYPE110 40.042 -CICS/TS 6.1 BETA 25 removed fields, INCOMPATIBLE.
TYPE110 40.129 Support for CICS/TS 6.1 Stat variables in CICWBG.
TYPE113 40.070 -Support for z16 SMF 113 Labels and Equations INCOMPT
TYPE113 40.121 TYPE113 can only validly process one CPU type.
TYPE113 40.128 Code block for LSPRWKLD missing in TYPE1131/TYPE113.
TYPE16 40.014 TRUNCATED SMF 16 DFSORT record, INPUT EXCEEDED
TYPE30 40.017 TYPE30_4/30_5 EXCPTOTL wrong for MULTIDD='Y'
TYPE30 40.025 Support or OA61511 Crypto/NNPI counters ABEND 40.01
TYPE30 40.098 MXG 40.01 only INPUT EXCEEDED,SMF30CONFOLOW invalid.
TYPE30 40.105 INTBTIME/INTETIME Missing in SMFINTRV corrected.
TYPE7072 40.034 TYPE70 vars SMF70PMT/SMF70PMU were corrected.
TYPE7072 40.102 IBM APAR OA62064 corrects CPUSER/SMF70SER '5555'X.
TYPE7072 40.104 Variable SMF70TYP in TYPE70PR always 2:IIP.
TYPE74 40.005 R742PUTx variables in TYPE74PA divided by 1E-6 twice.
TYPE74 40.096 TYPE749 PCIE Statistics only first bucket was output.
TYPE90A 40.107 Correction for TYPE9040 Boost variable SMF9040T.
TYPEDCOM 40.038 Reserved fields overlooked, misalignment.
TYPERMFV 40.029 ERROR: ARRAY SUBSCRIPT 51 OUT OF RANGE ARRAY ALHTNEXT
TYPEVMXA 40.010 Broken Control Record ABEND z/VM 7.2.21.02.
TYPEZCOS 40.037 New ZCOS01TI='ZCOS*DATETIME' created.
UTILEXCL 40.100 CICS/TS 6.1 ERROR 22-322, comma should be period.
VMAC102 40.135 DB2 Function Level 501 revised labels new fields.
VMAC110 40.063 CICSTRAN variables DSAPTHTM JVMTHDTM MAXHTDTM wrong.
VMAC110 40.129 New dataset CICTLS (CICS TLS CIPHER) STID=151.
VMAC115 40.154 Support for SMF 115 Subtype 216 dataset TY115216.
VMAC119 40.086 TYP11911 variables corrected, formats updated.
VMAC1154 40.158 Initial Support 4 subtypes of SMF 1154 Compliance
VMAC30 40.087 Dedicated Memory variables added.
VMAC42 40.088 Support for APAR OA59611 adds S42DS2MV
VMAC7072 40.137 BOOSTACTIVE=2 /*BOTH*/ was never tested.
VMAC73 40.084 Invalid counters SMF73CMG=2 when CHPID was Varied.
VMAC80A 40.059 Support for SMF 80 RACFTYPE=67 updated TYPE8081.
VMAC90A 40.058 Support for APAR OA60660 for TYPE9040 BOOST.
VMAC99 40.148 Support for TYPE 99 Subtypes 9 and 10.
VMACBVIR 40.056 Dataset BVIR302 had only half the observations.
VMACCIMS 40.139 UOWTIME in CIMSTRAN wrong prevented CICSTRAN merge.
VMACDB2H 40.138 QWHCCTKN QWHCEUID QWHCEUTX QWHCEUWN not %U Unicode.
VMACEDGR 40.061 Datasets EDGRDEXT and EDGRXEXT updates.
VMACRMFV 40.060 RMF III updates for ZRBRED, and FORMATS.
VMACRMFV 40.085 New ZRBASI time variables added in z/OS 2.4 & 2.5.
VMACSVIE 40.089 New variables added to SV34TRAN and SV35TRAN.
VMACVMXA 40.095 Support for z/VM 7.2 MONWRITE VXPRCMFC HIS counters.
VMACVMXA 40.140 RNI in VXPRCMFC was always zero, ++ syntax accepted.
VMACVMXA 40.141 OUT OF ORDER error sorting VXUSEACT, BY list wrong.
VMXG70PR 40.035 Vars SMF70GMU/SMF70CPA/SMF70WLA missing in ASUMCELP.
VMXGGETM 40.147 UTILGETM utility Memory Failure SAS Hot Fix 66883.
VMXGHSM 40.099 z/OS 2.5 dataset SFSMSHSM new variables added.
VMXGINIT 40.136 SAS VIYA error, blank needed after close paren.
VMXGUOW 40.041 LIBNAME PDB NOT FOUND if did not ask for MQ data.
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:
NEXTCHANGE
====== CHANGES THRU 40.162 ARE IN MXG 40.40 DATED Feb 3, 2023 =========
Change 40.162 New z/16 AI variables in TYPE1131 and ASUM1131 are added:
ASUM113 WAIUCPU='WAITING*FOR ACCESS*TO AIU'
VMAC113 CAIUCPU='EXECUTING*AIU'
Feb 2, 2023 AIUCPU='TOTAL*AIU*CPU'
AIUCPI='AIU*EXECUTING*CYCLES PER*INSTRUCTION'
These values and other z16 enhancements are in John
Burg's paper "How To Measure Those New z16 Capabilities"
from the IBM WSC Tech Bytes Conference, available at:
https://www.ibm.com/support/pages/wsc-tech-bytes-
conference-proceedings
Change 40.161 Format MG030NP for variable SMF30_NNPICTRS_ENTRY_ID in
VMAC30 dataset TYPE30NP decodes the 27 NNPA AIU Entry IDs.
Jan 29, 2023 Format MG030CP for variable SMF30_CRYPTRS_ENTRY_ID in
dataset TYPE30CP decodes the 156 Crypto Entry IDs.
Thanks to Mark C. Smith, IRS, USA.
Thanks to Mike R. Deneseus, IRS, USA.
Change 40.160 Variable S11912SS_SSH_SKEY_LEN in dataset TYPE11912SSH's
VMAC119 label was corrected from CLIENT to SERVER. The slash in
Jan 26, 2023 label for variable SMF119SC_SSH_CKEY_TYPE was removed.
Thanks to John Milne, Kyndryl, AUSTRALIA
Change 40.159 TYPE74ST variable R744QFLG was incorrectly formatted as a
VMAC74 one-byte $HEX2 value variable, but it is a bit-value and
Jan 27, 2023 these new variables decode the individual bits:
R744QFLG0='NORMAL*ACTIVE*INSTANCE*OF STRUCTURE'
R744QFLG1='NEW*INSTANCE*DURING*REBUILD'
R744QFLG2='OLD*INSTANCE*DURING*REBUILD'
R744QFLG3='JUST*ADDED OR*DELETED*INSTANCE'
R744QFLG4='IN HOLD*DELETION*NOT*FINISHED'
R744QFLG5='DUMP*INITIATED*FOR STRUCTURE'
R744QFLG6='STRUCTURE*REBUILD*IN*PROGRESS'
R744QFLG7='IN PROGRESS*REBUILD*IS DUPLEXING'
Thanks to Keith C. Shaffer, Cigna, USA.
Change 40.158 Initial support for 4 subtypes of SMF 1154 Compliance
EXB5401A-I Monitoring data. These are the 23 datasets created from
EXB5402A-B Subtype 01-04 and there are another 19 subtypes so this
EXB5403A-H will take some time to complete.
EXB5404A-D dddddd datasetE description subtype
FORMATS B5401A TYB5401A TCP/IP STACK 01
IMAC1154 B5401B TYB5401B IPV4 CONFIG 01
TYPE1154 B5401C TYB5401C IPV6 CONFIG 01
TYPS1154 B5401D TYB5401D TCP CONFIG 01
VMAC1154 B5401A TYB5401A TCP/IP STACK 01
VMXGINIT B5401B TYB5401B IPV4 CONFIG 01
Jan 24, 2023 B5401C TYB5401C IPV6 CONFIG 01
B5401D TYB5401D TCP CONFIG 01
B5401E TYB5401E UDP CONFIG 01
B5401F TYB5401F GLOBAL CONFIG 01
B5401G TYB5401G PORT CONFIG 01
B5401H TYB5401H MANAGEMENT CONFIG 01
B5401I TYB5401I NETWORK CONFIG 01
B5402A TYB5402A FTP DAEMON GENERAL 02
B5402B TYB5402B FTP DAEMON DATA 02
B5403A TYB5403A TN3270 TELNET GENERAL 03
B5403B TYB5403B TM3270 TELNET GLOBAL 03
B5403C TYB5403C TN3270 TELNET PARMS 03
B5403D TYB5403D TN3270 PARMS GROUPS 03
B5403E TYB5403E TN3270 PARMS MAP 03
B5403F TYB5403F TN3270 LUMAP 03
B5403G TYB5403G TN3270 PRTMAP 03
B5403H TYB5403H TN3270 RESTRICT APPL 03
B5404A TYB5404A CSSMTP IDENTIFICATION 04
B5404B TYB5404B CSSMTP CONFIGURATION 04
B5404C TYB5404C CSSMTP TARGET SERVER 04
B5404D TYB5404D CSSMTP CONFIGURATION DA 04
Change 40.157 New variables in XMSYTCUV dataset:
VMACXAM LCXHGPCP='LPAR*GROUP*CAPACITY'
Jan 20, 2023 CALGCAPV='LPAR*GROUP*CAPPING'
LCUCWCPL='WAIT*COMPLETION*FLAG?'
LCUCCAPP='ON*PARTITION*CAPPING?'
LCXCCON ='CPU*ONLINE*FLAG?'
LCXPOLTP='CORE*POLARIZATION'
Change 40.156 Change 40.105 failed to remove the IF SUBSTEP GT 0 test,
SMFINTRV causing INTBTIME and INTETIME in PDB.SMFINTRV to still be
VMAC30 missing values. The corrected member was not moved from
Jan 20, 2023 the test to production sourclib.
Thanks to Peter A. Vikeras, OPTUM, USA.
Thanks to Raymond J. Smith, OPTUM, USA.
Thanks to Ralph J. Romano, OPTUM, USA.
Change 40.155 TYPE74 variables AVGIOQMS, DEVIOQTM and AVGRSPMS were
VMAC74 incorrect because they used NRREQENQ instead of SMF74IOS
Jan 20, 2023 for the duration. Variable AVGENQUE could also be missing
because it tested a "no longer used" bit in DEVIND that
is sometimes used!
Thanks to Jan Tielemans, KBC, BELGIUM.
====== CHANGES THRU 40.154 ARE IN MXG 40.07 DATED Jan 16, 2023 =========
Change 40.154 Support for SMF 115 Subtype 216 creates TY115216 dataset.
VMAC115
Jan 16, 2023
Change 40.153 TYPE8500 variables R850RC and R850RS labels incorrectly
VMAC85 had "TIME" but they are not time variables.
Jan 12, 2023
Thanks to Scott Rowe, SSA, USA.
Change 40.152 -TYPE71 variables SMF71S3A/SMF713S3M/SMF713S3X labels
VMAC71 were corrected from "ON SCM" to "IN CSTORE".
Jan 11, 2023
Thanks to Rick Southby, IAG, AUSTRALIA.
Change 40.151 -Variables added to SYSVIEW dataset SV34TRAN:
VMACSVIE IMTR_CLK_OPNCLS_ELAP='APPLICATION*OPEN/CLOSE*TIME'
Jan 3, 2023 IMTR_CNT_BYTES_IN ='TOTAL*INPUT*BYTES'
IMTR_CNT_BYTES_OUT ='TOTAL*OUTPUT*BYTES'
-Variables added to SYSVIEW dataset SV35TRAN:
IMRA_APPL_ELAPSED ='APPLICATION*ELAPSED*TIME'
IMRA_CNT_BYTES_IN ='AVERAGE*I/P*MESSAGE*BYTES'
IMRA_CNT_BYTES_OUT ='AVERAGE*O/P*MESSAGE*BYTES'
Change 40.150B Updates for Change 40.150 Split RMF 70 Subtype 1:
ASMRMFX ASMRMFX - ASM CODE FOR REASSEMBLY (USE IN JCLRMFX1)
JCLRMFXA JCLRMFXA- JCL TO ASSEMBLE ASMRMFX FOR REASSEMBLY
JCLASMXG JCLASMXG- Assemble all SEVEN MXG ASM MEMBERS
JCLRMFX JCLRMFX - Three STEP SAS REASSEMBLY JOB (TYPERMFX)
JCLRMFX1 JCLRMFX1- Three Step ASM REASSEMBLY JOB (ASMRMFX)
TYPERMFX TYPERMFX- SAS CODE FOR REASSEMBLY (USE IN JCLRMFX)
ASMMACS ASMMACS - MACROS FOR ASM PROGRAMS
ADOCRMFX ADOCRMFX- DOCUMENT REASSEMBLY PROGRAMS/JOBS
Jan 30, 2023 SEE CHANGE 41.012 for REQUIRED SAS HOT FIXES.
Change 40.150A Updates for Change 40.150 Split RMF 70 Subtype 1 were
JCLRMFX made. Only SMF 70 subtype 1 records are processed, the
TYPS7001 RMF 73 was included only because split 73s were available
Jan 15, 2023 for testing the reassembly and there is no need for any
other Split records to be reassembled at this time.
The TYPS7073 program was renamed to TYPS7001.
The TYPERMFX reassembly program works on z/OS with both
SAS and WPS, but does not currently work on ASCII; so we
are developing an ASMRMFX for ASCII sites.
Reassembled large LRECL records can be processed on ASCII
directly with the FTP ACCESS method using SITE RDW and
S370VS. or downloaded with RECFM=U,BLKSIZE=32760 and then
using S370VBS on the ASCII INFILE statement.
SEE CHANGE 41.012 FOR REQUIRED SAS HOT FIXES.
Thanks to Thomas D Foster, SSA, USA.
Thanks to Mark London, SSA, USA
Thanks to Ashley Klunk, SSA, USA
Thanks to Jaipal Nimmala, SSA, USA.
CHANGES THRU 40.150 WERE IN MXG 40.07 DATED Jan 16, 2023 Early Adopters
Change 40.150 -INCOMPATIBLE CHANGE TO SMF 70.1 FOR SITES CREATING SPLIT
ADOCRMFX SMF records. ONLY IMPACTS MXG TYPE70PR PR/SM DATASET.
FORMATS -ONLY SITES WITH LOTS OF ENGINES AND LPARS CREATE THEM.
JCLRMFX This program will tell you if you have split records:
RMFSPLIT //SPLITS EXEC MXGSAS94 (your SAS JCL Procedure)
TYPERMFX //SMF DD DSN=YOUR.SMF,DISP=SHR
TYPS7001 %INCLUDE SOURCLIB(VMACSMF);
VMAC7072 DATA;_SMF;IF ID=70 AND SUBTYPE=1;
VMACSMF INPUT @OFFSMF+47 NRCPUD &PIB.2.
VMACSMFL @OFFRMFP+74 SMF70RAN &PIB.2.
VMXGINIT @OFFRMFP+104 SMF70RBR &PIB.2.
Jan 16, 2023 @;
PUTLOG _N_= SYSTEM= SMFTIME= RMFSRCL= HEX2.
SMF70RAN= SMF70RBR= LENGTH= NRCPUD=;
IF NRCPUD=0, that SYSTEM uses the alternate algorithm and
its SMF 70.1 records must be reassembled, with MXG 40.07.
You can also use the 40.07 RMFSPLIT program report.
-SPLIT records are created when the length of data for an
interval exceeds 32760 bytes and multiple 32760 byte
blocks are created. If LPAR COUNT*ENGINE COUNT*88 is GT
26,000 you have split records (10 LPARS and 30 ENGINES).
APARs OA62064 and OA63108 changed IBM's "old" breaking
algorithm to the "new" breaking algorithm but with no
mention of that change!!!
-The good news with the new SPLIT records is that the
TYPE70 dataset is CORRECTLY created. It is ONLY the
TYPE70PR PR/SM dataset that has missing or incorrect
values that were previously populated from those
now-non-existent segments. Fortunately, there is no
execution error, just bad data in TYPE70PR and in the
ASUMxxxx datasets created from TYPE70PR.
-Previously, for the SMF70 Subtype 1 record, each SPLIT
record repeated the CPU Data Sections and the Logical
Core Sections, so the TYPE70PR PR/SM dataset could be
created, since some fields from CPUD and CORE segments
are needed, but the new algorithm no longer writes those
sections in the 2nd and subsequent SPLIT records, and
this broke the back of the MXG PR/SM implementation,
which had been designed to match the record contents.
-IBM Claims the change was NOT INCOMPATIBLE, stating that
it has ALWAYS BEEN A REQUIREMENT TO SORT and Reassemble
the split records into a single VBS Record with the
larger LRECL, (77,000 in this case), using the fields in
the Reassembly Area fields, but IBM does NOT provide a
utility to create those records, and neither IFASMFDP nor
DFSORT can process records with LRECL greater than 32760.
-The alternate splitting logic was already implemented
with z/OS 2.2 but with APAR OA62064 (which introduces
record level x'8F' for SMF 70 subtype 1) additional
fields were added to the CPU data section so that in
case of large LPARs with many processors it becomes more
likely that the alternate splitting is used.
-If the alternate algorithm is used, the value of NRCPUD,
the count of CPU Detail Sections, will be zero in the
second and subsequent split records, RMFSPLIT provides
that reporting, and NRCPUD is available in _SMF. header.
-In z/OS 2.5 IBM does offer the GRBRMFR service that can
be called to assist with the reassembly, but that service
will NOT be provided for z/OS 2.4 or earlier releases.
-The MXG Solution is the new TYPERMFX SAS program and the
example JCLRMFX whose first step Selects and SORTS the
70.1 and 73 SMF records (the SORT ensures split records
are in the correct order required for reassembly). The
second step uses the SAS TYPERMFX program to reassemble
and write out the Large LRECL records, which are then
read by the SAS TYPS7001 program in the third step to
create the TYPE70 TYPE70EN TYPE70PR and TYPE73 datasets,
and which %includes ASUM70PR to create these datasets
ASUM70GC ASUM70GL ASUM70LP ASUMCELP ASUMCEC
in the output PDB Data Library, which can then be used
for reports, and/or copied into the daily PDB library.
Changes made:
-JCLRMFX is the three step reassembly & PDB create job.
-TYPERMFX SAS program to reassemble into Large LRECL recs
-TYPS7001 reads LRECL SMF and creates the PDB.
-VMACSMFL replaces _SMF to use &LRGLRECL for SMF to input
the Large LRECLs and should only be used with JCLRMFX.
-VMACSMF and VMACSMFL were updated to decode SMF70RAN and
other RMF reassembly variables available for _SMF..
-FORMATS set RMFSRCL HEX2. so '8F'x is printed.
-VMXGINIT GLOBALs &LRGLRECL and sets it to 264000; the
largest reassembled LRECL was 77000 bytes.
-VMAC7072 was updated to add SMF70RAN/RBR/RSQ reassembly
variables to TYPE70.
-New RMFSPLIT program reads today's SMF data and alert
you if you have split records and whether data is lost.
-New member ADOCRMFX has detail documentation on the
Reassembly program TYPERMFX and the JCLRMFX example.
-SAS and WPS both work correctly with a download LRGLRECL
reassembled file with RECFM=U on the download.
-SEE CHANGE 41.012 FOR REQUIRED SAS HOT FIXES.
Change 40.149 -Support for CICS/TS 6.2 new fields added. New fields:
ZMAC110 XSNLNACT - DFHTASK 048 - FAILED AUOR NOLOG NOTAUTH
ZTILEXCL XSNLNFCT - DFHTASK 049 - FAILED AUOR NOLOG NOTFIND
FORMATS -SMFPSRVR is 75 for CICS/TS 6.2 so formats were updated:
Jan 8, 2023 MGVERCIC $MGVERCIC $MGSYIL
-The two members ZMAC110 and ZTILEXCL (ONLY in 40.40 with
BUILTBY= JAN 26, 2023 Change 40.149) are the updated code
for the CICS/TS 6.2, but they have not been tested with
6.2 Records. You can copy/rename them to UTILEXCL and
VMAC110 in your "USERID.SOURCLIB" to test and validate
this change, and advise of your success to support.
Thanks to Todd Gagle, Broadcom, USA.
Change 40.148 Support for TYPE 99 Subtypes 9 and 10.
VMAC99
Dec 2, 2022
Change 40.147 Array size of 2047,33165 required 550MB Region and caused
VMXGGETM Memory Failure errors if SAS Hot Fix 66883 for z/OS was
Dec 1, 2022 not applied. The array was much larger than was needed.
The first size (2047) is the number of possible SMF IDs
(2047) and 33165 was set to the number of combinations,
but it only needs to be the number of possible subtypes
for an ID. Current maximum subtype is 499 for the DB2
DB2 101 trace records, but 4096 was chosen since that
only requires a 110 MB REGION size. And, VMXGGETM is only
used to create a test file of two of your SMF records so
it's not routinely executed by UTILGETM.
Thanks to Allana Jacob, Kyndryl, CANADA.
Thanks to Pranav Yader, Kyndryl, CANADA.
Thanks to Amha Tsegaye, Kyndryl, CANADA.
Change 40.146 -Corrections to ASUMCELP dataset. SMF70LAC is now the MAX
ASUM70PR value to more accurately match SCRT reports, and GMTOFFTM
VMXG70PR and SMF70CPA are now populated.
Nov 28, 2022 -The ICF LPARS observations can now be created in ASUMCELP
Dec 3, 2022 and ASUM70LP datasets if you specify %LET ICFLPARS=YES;
before your %INCLUDE SOURCLIB(ASUM70PR) statement.
That will increase the number of obs in ASUMCELP/ASUM70PR
and most of the current LPAR variables will have missing
values, as only the ICF metrics are populated in the ICF
observations and the ICF metrics are missing values in
other LPAR observations. The ICF observations will have
LPARICFS NE 0.
Thanks to Joseph Montana, BKFS, USA.
Change 40.145 A report program that will show you in spreadsheet form
ANALCEC how the LPARs on your CEC are defined. It will tell you
Nov 21, 2022 how many MSU/MIPS are available to MVS based on the
Dec 25, 2022 lowest of cap values and CPUs assigned to LPAR.
Thanks to Miguel Fernandez, BNYMellon, USA.
CHANGE 40.144 The last line of MDIZERO was an unclosed comment causing
MDIZERO SLP to abend. MDIZERO now creates the OUT_DIR if it does
IEBUPDTE not exist. IEBUPDTE cosmetic updates with PUTLOGS.
Nov 21. 2022
Change 40.143 Change 40.103 was still incorrect, RECFM=VBS is needed to
VMACDCOL support any BLKSIZE value in the dumped DCOLLECT or IMS
VMACIMS VB records.
Nov 21, 2022
Thanks to Richard Egan, Westpac, AUSTRALIA.
Change 40.142 Uninitialized S30DM2GFAILED variable corrected, variable
BUILD005 D30DMINUSEADM2GHWM now output, and some labels for these
BUIL3005 new Dedicated Memory metrics were corrected.
VMAC30
Nov 18, 2022
Change 40.141 Variable CALTODON was incorrectly in the MACRO _BUSEACT
VMACVMXA sort list for VXUSEACT, causing an OUT OF ORDER error.
Nov 15, 2022 triggered by the Daylight Savings Time Change.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.140 -z/VM VXPRCMFC (SMF113 equivalent) RNI was always zero due
VMACVMXA to a typo that caused L3P to always be a missing value.
Nov 16, 2022 -Lines 6310 (z14/15) and 6375 (z16) creating L4RP both had
++ but the SAS Compiler did not flag that error, which
did not impact the value in L4RP for the z16, as all of
the EXTND counts in that statement were zero on this box
which only had one drawer. L4RP is non zero in others.
Thanks to Graham Harris, NatWest, ENGLAND
Change 40.139 Change 37.095 incorrectly decoded UOWTIME which prevented
VMACCIMS merging CIMSTRAN and CICSTRAN datasets.
Nov 14, 2022
Thanks to Charles Piggott, R+V Allgemeine Versicherung AG, GERMANY.
Change 40.138 DB2 variables QWHCCTKN QWHCEUID QWHCEUTX QWHCEUWN are not
VMACDB2H %U Unicode fields, but MXG incorrectly converted them
Nov 3, 2022 with $ASCII128 informat (when they were "truncated" with
offset). Now they are converted with $EBCDIC128.
Thanks to Paul Weissman, UBS, USA.
Change 40.137 Bit test to set BOOSTACTIVE=2 /*BOTH*/ was never tested
VMAC7072 if either ZIP or SPEED boost was active.
Oct 26, 2022
Thanks to Peter J. Gray, ANZ DXC, AUSTRALIA.
Change 40.136 SAS VIYA error %SUBSTR(&SYSVER,1,1)EQ V needed a blank
VMXGINIT between the ) and the V.
Oct 26, 2022
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 40.135 DB2 ZPARM ADDED by Function Level 501 replacing FL 100.
FORMATS -T102S106 labels revised:
VMAC102 QWP4TSCT='COMPRESSION*TYPE*F=FIXED*H=HUFFMAN'
Oct 27, 2022 QWP4ENKL='ENCRYPTION*KEYLABEL'
Nov 14, 2022 QWP4AUTCSU='AUTH*COMPATIBILITY*SELECT FOR UNLOAD'
QWP4CDSTL='CACHDYN*BOTH*CAPTURE*LOAD*NONE'
QWP4CDRL='COMPRESS*DIRLOB?'
QWP4SFPR='STATFDBK*PROFILE?'
QWP4DDLM='DDL*MATERIALIZATION*IMMEDIATE*PENDING'
QWP4DINA='DEFAULT*INSERT*ALGORITHM'
QWP4PSPN='PAGESET*PAGENUM*ABSOLUTE*RELATIVE?'
-T102S106 new variables:
QWP4DSSAR='DISALLOW*SSARAUTH?'
QWP4UBCDC/*UTILS*BLOCK*FOR*CDC?*/
QWP4LIRO /*LOAD*RO*OBJECTS?*/
QWP4UZS /*UTIL*USE*ZSORT?*/
QWP4RINSU/*REORG*INDEX*NOSYSUT1?*/
QWP4RICLD/*REORG*IC LIMIT*DASD*/
QWP4RICLT/*REORG*IC LIMIT*TAPE*/
QWP4LDISCALE/*LOAD*DEL*IMPLICIT*SCALE*/
QWP4SUBSTRCP='SUBSTR*COMPATABILITY*P=PREV*C=CURR'
Thanks to Lai Fai Wong, Bank of America, USA.
====== CHANGES THRU 40.134 ARE IN MXG 40.06 DATED Oct 23, 2022 =========
Change 40.134 BMC CMF MXGWARN:IMPOSSIBLE VALUE DETECTED TYPE70PR CPU
VMAC7072 LCPUPDTM Dispatch Time z/16 Data under z/OS 2.4, not RMF.
Oct 21, 2022 MANY of those messages were printed, now limited to ten.
Nov 2, 2022 Some LCPUADDR engines had hundreds of hours of LCPUPDTM
Nov 14, 2022 Partition Dispatch Time for PHYSICAL LPAR. This message
has always and continues to set LCPUPDTM to zero,
Nov 2: BMC reports their error was introduced in BQM1809,
workaround is to back out BQM1809 and a circumvention is
given in that Case if you can't back it out.
Nov 14: BMC APAR BQM1868 will correct when available.
Change 40.133 New parameter added and now listed in alphabetic order.
ANALDB2R New LISTIDS=NO (DEFAULT) suppresses the reports from
ANALDBTR VFMT102 that listed all of the OBID DBIDs found and used
READDB2 in the PROC FORMAT. Generally only useful for debugging.
VFMT102
Oct 23, 2022
Change 40.132 DB2ACCTP variables QBACSYI QBACSYIT and QBACIOC were
VMACDB2 missing values because they were missing in the revised
Oct 19, 2022 INPUT statement.
Thanks to Raymond J. Smith, OPTUM, USA.
Thanks to Ralph J. Romano, OPTUM, USA.
Change 40.131 Support for new TYPE7 variable SMF7DTYPX to report flood
VMAC7 filtered SMF records for all types (0-2047), to replace
Oct 11, 2022 SMF7DTYP which was only one byte for only 0-255 records.
If the dropped record is greater than 255, SMF7DTYP will
contain 126, which is the extended type indicator value.
Change 40.130 Support for SMF 106, updated and validated with all four
VMAC106 records creating these four datasets:
Oct 11, 2022 (LABEL='TY1061: BCPII HWISET API CALLS'
(LABEL='TY1062: BCPII HWICMD API CALLS'
(LABEL='TY1063: BCPII HWIREST NO OPS API CALLS'
(LABEL='TY1064: BCPII HWIREST OPS API CALLS'
Thanks to Hans Langeveld, KLM, THE NETHERLANDS.
Thanks to Mark Duifs, KLM, THE NETHERLANDS.
Change 40.129 Support for CICS/TS 6.1 (COMPATIBLE) new vars/dataset:
EXCICTLS -New variables in CICWBG (CICS URIMAPS) STID=101.
FORMATS WBGENRFC='ENTRYPOINT*REF*COUNT'
SCICSORT WBGDIUTA='DIRECT*USER*TRAN*ATT'
VMAC110 WBGSJMSR='SCHEME*JMS*REQUEST'
VMXGINIT WBGSIIOR='SCHJEME*IIOP*REQUEST'
Oct 12, 2022 WBGPIPEL='PIPELINE*REQUESTS'
-New variables in CICSJS (JVMSERVER) STID=116.
SJSCOCAU='CODE*CACHE*USED'
SJSCOCAA='CODE*CACHE*ALLOCATED'
SJSDACAU='DATA*CACHE*USED'
SJSDACAA='DATA*CACHE*ALLOCATED'
SJSCLSTU='CLASS*STORAGE*USED'
SJSCLSTA='CLASS*STORAGE*ALLOCATED'
SJSCLCAS='CLASSCACHE*SIZE'
SJSCLCAF='CLASSCACHE*FREE'
-Cosmetic. CICS/TS 6.1 WARNING about SKIPPED FIELDS for
STID's 48 is now skipped, as the new fields are
reserved fields.
-New dataset CICTLS (CICS TLS CIPHER) STID=151.
OCCIPHER='TLS*CIPHER*CODE'
OCTLSINB='INB CICS*CONFIG*TLS*CIPHERS'
OCTLSOUT='OUT CICS*CONFIG*TLS*CIPHERS'
OCATTINB='INB ATTLS*CIPHERS'
OCATTOUT='OUT ATTLS*CIPHERS'
OCDATETM='TLS*DATETIME'
-This should be the last update to CICS/TS 6.1 SMF data.
Thanks to Rob D'Andrea, NATWEST, ENGLAND.
Change 40.128 The Code Block to create variable LSPRWKLD was missing in
VMAC113 TYPE1131/TYPE113 datasets, but only TYPE1131/ASUM1131 is
Oct 6, 2022 used, as IBM no longer updates the subtype 2.
Thanks to Ronald W. Basset, OPTUM, USA.
Change 40.127 -WARNING SMF 90-10 WITHOUT PRECEEDING TYPE0 message and/or
VMAC0 zero observations in PDB.IPL dataset. DOWNTM calculation
VMAC90A revised and used to confirm ID=0 IPL SMF was found before
Oct 7, 2022 ID=90.10 IPL SRM.
-Blank LABELs in VMAC90A updated.
Thanks to Karthick Bojjireddy, HSBC, USA.
Change 40.126 A prior change dropped support for the TREND data. That
GRAFCEC is now restored and ODS PROCLIB added to make indices
Oct 4, 2022 more meaningful.
Thanks to Tom S. MacCabe, Dominion Energy Services, Inc., USA.
Change 40.125 Updates from Sep 26, 2022 SMF Manual Refresh.
VMAC74 TYPE74CA Variables R745INCR/BYTR/BYTW/RTIR/RTIW Reserved.
Oct 3, 2022 TYPE74CA Variables CSDS/CSIM reserved.
TYPE74DU Variable R744RFLG='STATUS*FLAGS'
TYPE75 Doc updated: UCBTYPE is only valid if Page Space
Type is not SCM, i.e., SCMPGTYP NE 'Y'.
Change 40.124 ERROR: UNABLE TO RESTORE 'BASE.FREQ.ONEWAYFREQA' FROM
PROC FREQ TEMPLATE STORE! is due to back level SAS at 9.1.3 and
Oct 2, 2022 issuing ODS commands in VMXGINIT. Install Current SAS.
Change 40.123 If a DB2 subsystem is restarted during the period covered
VFMT102 by the input SMF data, it is possible to get duplicate
Oct 1, 2022 values for a given DBID OBID. This change detects that
and flags the problem with an MXGWARN message and keeps
only the last OBS found when there is more than one.
Change 40.122 Typo, LENGT(& should be LENGTH(&
GRAFCEC
Sep 30, 2022
Thanks to Tom S. MacCabe, Dominion Energy Services, Inc., USA.
Change 40.121 TYPE113 can only validly process one CPU type at a time,
ASUM113 but prior to this change, all CPU types were incorrectly
VMAC113 output, and only observations from the default CPU type
Sep 30, 2022 (z15 in 40.02- SM113VN2=6, z16 in 40.03+ SM113VN2=7) or
the requested CPU type (if you reset MACRO _XLA113 per
Change 40.095) contained valid data values and correct
variable's labels. This change detects the value in MACRO
_XLA113 and only outputs those observations, printing an
MXGWARN message if other types were found in SMF data,
and creating 0 obs in TYPE113/TYPE1131 if no requested
CPU type records were found.
Note that if you have multiple CPU Types, z16 and z15,
you would use the default z16 in your normal BUILDPDB and
output the TYPE1131 and ASUM1131 datasets to your normal
PDB data library, and would run a second step, changing
changing _XLA113 to _XLA113F for the z15 and changing the
//PDB DD to a DIFFERENT DATA LIBRARY as the two datasets
TYPE1131/ASUM1131 CAN NOT BE COMBINED and they must be
separately analyzed. The simplest job is
// EXEC MXGSASV9
//SMF DD DSN=YOUR.SMF113.DATA,DISP=SHR
//PDB DD DSN=YOUR.Z15.TYPE113.PDB,DISP=OLD
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA113F % ;
%INCLUDE SOURCLIB(TYPS113,ASUM113);
but the more complete job which enhances the ASUM1131
data set with TYPE70PR data would be
// EXEC MXGSASV9
//SMF DD DSN=YOUR.SMF113.SMF70.DATA,DISP=SHR
//PDB DD DSN=YOUR.Z15.TYPE113.PDB,DISP=OLD
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA113F % ;
%UTILBLDP(BUILDPDB=NO,USERADD=7072 113,
OUTFILE=INSTREAM,
WANTSMF=70.1 113.1,
INCLAFTR=ASUM70PR ASUM113);
%INCLUDE INSTREAM; RUN;
You could tailor your BUILDPDB to create an SMF file with
only the needed SMF records for the second job adding the
//SMFOUT DD DSN=YOUR.SMF113.SMF70.DATA,DISP=(,CATLG). . .
and using
//SYSIN DD *
%LET MACFILE=
%QUOTE(
FILE SMFOUT DCB=SMF;
IF (ID=70 AND SUBTYPE=1) OR (ID=113 AND SUBTYPE=1)
THEN PUT _INFILE;
FILE LOG; );
-ASUM113 was corrected to CRYPTO83 instead of CRYPTO70.
Thanks to Ralph J. Romano, OPTUM, USA.
Change 40.120 Flag variables added to TYPE16:
VMAC16 ICETOOL ='CALLED*BY*ICETOOL?'
Sep 28, 2022 APFAUTH ='RUNNING*APF*AUTHORIZED?'
MOBJWORK='MEMORY*OBJECTS*USED FOR*WORK?'
JOINKEY1='INVOKED*JOINKEYS*SUBTASK 1?'
JOINKEY2='INVOKED*JOINKEYS*SUBTASK 2?'
Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
Change 40.119 If you add type120 data to the PDB you could get an array
VGETSORT subscript out of range message in a weekly or monthly
Sep 27, 2022 job. VGETSORT is used to build a list of the datasets
that could possibly be added to the week or month and
includes the variables in the SORTEDBY list. This was
kept in an array that was 20 deep but some some of the
type 120 datasets have very long _B lists and exceeded
the array size. Array was expanded to 50.
Change 40.118 Unused Change Number
Sep 22, 2022
Change 40.117 Format MGXAMPO is created to map values of PFXPOLAR for
FORMATS the Polarization and PFXPOLAR is now a numeric value.
VMACXAM
Sep 21, 2022
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 40.116 New DB2 V12 variables added in DB2STAT0/DB2STATS:
VMACDB2 QTGSLCAIC QTGSDGBL QTGSLICNT QTGSGICNT QTGSGCONT
Sep 20, 2022 QTGSFCONT QTGSCPLOK QTGSCNOTY
New DB2 V12 variables added in DB2STAT1/DB2STATS and
DB2ACCTP and DB2ACCT:
QTXALCMM QTXALCMU QTXALCSM QTXACRLK QTXACWLK
QTXACRUK QTXACWUK QTXACRCH QTXACWCH QTXACRNT
QTXACNNT QTXACRCP QTXACWCP QTXACRAL QTXACWAL
QTXACWSY QTXASRCL QTXAUCNT QTXALCCP QTXACGEN
QTXACRQF QTXACWQF QTXADLCL QTXATOUT QTXARTRY
QTXANRTY QTXASUSP QTXARSUM QTXASTAT QTXADEAD
QTXATIME
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.115 Support for DB2 IFCID 314.
FORMATS Format MGD314R added.
VMAC102
Oct 11, 2022
Thanks to Lai Fai Wong, Bank of America, USA.
Change 40.114 UTILGETM/VMXGGETM ERROR: Array Subscript out of range.
VMXGGETM This utility, used only in JCLTESx program to create the
SMFSMALL file, still had the old limit of SMF Type values
of 256, but now the maximum TYPE is 2047, with 0-127 and
1152-2047 for IBM with 128-1151 available for users.
The actual record type in the record is 126, which tells
MXG this is an Extended SMF Header record with the true
ID in that header. The specific record was TYPE=1153,
the JES2 Monitor record.
Thanks to Jim S. Horne, Lowe's, USA.
Thanks to Saddam Hussain, Lowe's, USA
Change 40.113 Updates from Aug 23, 2022 SMF Manual:
VMAC7072 -TYPE70 new variable:
VMAC73 ALTVMMACHINE='RUNNING*UNDER*ALTERNATE*VM MACHINE'
Sep 10, 2022 -TYPE73 new variables:
Oct 17, 2022 SMF73NT1='PNET ID OF*ETHERNET*NETWORK*1ST PORT'
SMF73NT2='PNET ID OF*ETHERNET*NETWORK*2ND PORT'
-Note that no SMF 78 Subtype 3 records are written if your
system is running under an Alternate Virtual Machine.
-Oct 17: VMAC73 Early Adopter's 40.06 STOPOVER corrected.
Change 40.112 CICS TS/6.1 is SMFPSRVR 74 but FORMATs printed TS5.7.
FORMATS No impact on code as all tests are for 74.
Aug 6, 2022
Change 40.111 -The CICS Resource & Identity records, 110 subtype 1 with
TYPE110 MNSEGCL=5 or 6 create these seldom needed datasets that
UTILBLDP can take a lot of disk space and they compress poorly:
Sep 2. 2022 MNSEGCL=5 RESOURCE
COUNTER SEG DATASET
MNR5NUMI CICSRDS CICS RESOURCE DATA CLASS
MNR5NUMF CICSRDFI CICS RESOURCE FILE DETAIL
MNR5NUMT CICSRDQU CICS RESOURCE TSQUEUE DETAIL
MNR5NUMD CICSRDPL CICS RESOURCE DPL DETAIL
MNR5NUMU CICSRDUR CICS RESOURCE URIMAP DETAIL
MNR5NUMW CICSRDWB CICS RESOURCE WEBSVC DETAIL
MNSEGCL=6 IDENTITY
COUNTER DATASET
MNI6NUMI CICSIDNT CICS IDENTITY TRANSACTION INFO
MNI6NUMD CICSIDND CICS IDENTITY REALM/DISTING
They can be made zero obs dataset using
%LET MACFILE=
%QUOTE(
IF ID=110 AND SUBTYPE=1 AND MNSEGCL IN (5,6)
THEN DELETE; );
in your SYSIN, or with UTILBLDP by adding MNSEGCL5
and/or MNSEGCL6 or MNSEGCL to the SUPPRESS= parameter.
In addition, when TYPS110 is used, they are never sorted
nor written to the PDB data library, in VMAC110 comments:
MACRO S110:
/* SUBTYPE=1, CICS MONITOR DATASETS: */
/* _SCICTRN - CICSTRAN IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDS - CICSRDS IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDD - CICSRDPL IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDF - CICSRDFI IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDQ - CICSRDQU IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDU - CICSRDUR IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICRDW - CICSRDQB IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICIDN - CICIDNTY IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICIDD - CICIDNDD IS NOT SORTED TO PDB, HIGH VOLUME.*/
/* _SCICACC - CICSACCT NOT SORTED, PRE-CICS/ESA ONLY. */
/* _SCICSYS - CICSYSTM NOT SORTED, PRE-CICS/ESA ONLY. */
Change 40.110 -If you specified FIRSTRUN=YES and RUNWEEK=NO the SAS
BLDSMPDB OPTION OBS=0 was still in effect, causing all subsequent
Sep 2, 2022 datasets to have 0 OBS which could also cause an ERROR.
Thanks to Doug Medland, Kyndryl, CANADA
Change 40.109 ERROR 557-185:Variable SETPDB is not an object because
ANAL307X SET&PDBMXG..TYPExxxx was missing the blank between SET
Aug 30, 2022 and &PDBMXG.
Thanks to Karl Lasecki, American Chemical Society, USA.
Change 40.108 The LFAAREA was introduced in 2017 but no one noticed in
VMAC71 those 5 years that it was not included in the CSTORE size
Aug 30, 2022 which suggest memory is not the critical resource it once
was! Variable CSTORE is updated to include SMF71GRX,
the maximum frame size of the LFA, converted to bytes to
match CSTORE UNITS.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 40.107 Correction for TYPE9040 BOOST dataset SMF9040T/IBM _ETOD,
VMAC90A which is valid in both START and END event records, but
Aug 27, 2022 in the START record is the projected END of BOOST time.
and was incorrectly compared with SMFTIME to create the
GMTOFF9040 offset value. New variables:.
SMF9040STR the SMFTIME of the START event.
SMF9040EGMT the SMF9040T before GMTOFFSET in END
SMF9040SGMT the SMF9040T before GMTOFFSET in START
SMF9040TE the SMF9040T after GMTOFFSET in END
The last three variables are needed for the GMTOFF9040
calculation (by descending sort and retained from END.)
You must use %INCLUDE SOURCLIB(TYPS9040) or
%INCLUDE SOURCLIB(TYPE9040); _STY9040
because the GMT correction is in the dataset SORT.
-Note that the CAPTURAT in RMFINTRV can be over 100% in
Boosted intervals, and IBM says that is correct and will
eventually provide a documentation update.
Thanks to Peter Relson, IBM z/OS Core Design, USA.
Thanks to Jim S. Horne, Lowe's, USA.
Change 40.106 Support for new variables in MONITASK dataset, added by:
VMACTMO2 PTF TH04514 in V4.2 for CICS/TS 5 AND 6.
Aug 25, 2022 TAHWMRUL='RULE*RECORD'
TARECSEQ='RECORD*SEQUENCE*FLAG'
TAABNCD2='ABEND*CODE'
Thanks to Daniel D. Hamiel, NEDBANK, SOUTH AFRICA.
Change 40.105 Variables INTBTIME/INTETIME were missing if the first 30
VMAC30 was a subtype 2/3 for an OMVS (SUBSTEP GT 0) record.
SMFINTRV Change 25.089 set SMF30IST to missing IF SUBSTEP GT 0
Aug 24, 2022 because in 2007 it contained the original INITTIME and
not the current interval's start time, and could not be
used to create the GMTOFF30 (that MXG must calculate
because IBM has never put it in the 30 records!).
Now, the value in SMF30IST for OMVS jobs is valid and
no longer set missing and the INTBTIME/INTETIME are
now valid in that first 30 record.
See Change 40.156 correction.
Thanks to Ronald W. Bassett, OPTUM, USA.
Change 40.104 Variable SMF70TYP in TYPE70PR was always 2:IIP, while in
VMAC7072 TYPE70EN, it correctly mapped 0:CP 1:IFA 2:IIP, which are
Aug 22, 2022 the only engine types in TYPE70EN. But in TYPE70PR, the
Dec 10, 2022 correct variable is SMF70CIX which maps all five engines:
1:CP 3:IFA 4:IFL 5:ICF and 5:ZIIP. But now SMF70TYP does
correctly map it's three engine types in TYPE70PR.
Thanks to Pat Perreca, Wakefern, USA.
Change 40.103 The INFILE statement for IMSLOG didn't supply attributes
VMACDCOL LRECL and RECFM for the execution system, needed if they
VMACIMS are not supplied in the FILENAME IMSLOG statement. There
Aug 22, 2022 was also a logic error in both VMACIMS/VMACDCOL INFILEs.
Thanks to Ervin Claxon, CSX, USA.
Thanks to David Feimer, Luminex, USA.
Change 40.102 APAR OA62064 corrects invalid CPUSER/SMF70SER '5555'x
VMAC7072 values, although that is not stated in the text, which
Aug 18, 2022 notes that APAR introduces z16 support. IBM says the
bad serial number is also addresses in that APAR.
No change was made to MXG code.
Thanks to Rob D'Andrea, NATWEST, ENGLAND
====== CHANGES THRU 40.101 ARE IN MXG 40.05 DATED Aug 15,2022 ==========
Change 40.101 TYPE6 ESS segments with GEPARNLN=0 are valid null values,
IMAC6ESS so the MXGERROR INVALID IMAC6ESS RECORD SKIPPED is now
Aug 8, 2022 only written if GEPARMNL GT LENGTH.
Change 40.100 CICS/TS 6.1 ERROR 22-322 using UTILEXCL -SOFLAG $CHAR4,
UTILEXCL the comma after CHAR4 should be a period.
Aug 8, 2022
Thanks to Gennady Katsnelson, Kyndryl, USA
Change 40.099 -Support for VMXGHSM DFSMSHSM Data Areas z/OS 2.5 Chap 15,
VMXGHSM DVL-Dump Volume Record adds these variables to HSMDVL:
Aug 6, 2022 DVLDEVT='SOURCE VOL*UCB TYPE'
DVLFVALD='VOLUME HAS*VALID COPIES'
DVLMEDIA='MEDIA*TYPE'
DVLSEQNR='SEQUENCE*NUMBER'
DVLSTACK='NUMBER*OF DUMPS*STACKED'
Thanks to Lindsay Oxenham, Defense, AUSTRALIA
Change 40.098 MXG 40.01 only. INPUT STATEMENT EXCEDED, INVALID data for
VMAC30 SMF30CONFOLOW because the INFORMAT &PIB.2 was missing the
Aug 4, 2022 final period, It should have been &PIB.2. with period.
Thanks to Mary Kay Pettengill, Sirius, USA.
Change 40.097 If you are using Luminex MDI you could get a S013 ABEND
MDIZERO in your z/OS job, if it did not produce any output in
Aug 4, 2022 SASLIST. This change adds a data step that creates a
single page of output to prevent the ABEND, You may want
to add this datastep to your tailored IMACINIT or to
every job you submit to the MDI from z/OS.
data _null_;
file print;
put 'page output to prevent s013 abend. Change 40;097';
run;
Change 40.096 Dataset TYPE749, PCIE Statistics, only output the first
VMAC74 SYNC I/O Response Distributions buckets. Sets of 10 FLG,
Aug 4, 2022 Read, and Write Range and Sample Counts are created.
Thanks to Raymond J. Smith, OPTUM, USA.
Thanks to Ralph J. Romano, OPTUM, USA.
Change 40.095 -Support for z/16 MONWRITE VXPRCMFC Hardware HIS data with
FORMATS z/VM Release 7.2.21.2 and new CRYPTO types in VXPRCAPM.
VMAC113 The z16 changed labels and uses different variables and
VMACVMXA coefficients in the RNI and other metrics calculations.
Aug 3 2022 The calculations/coefficients are correct for each CPU,
but the variable labels default to those for the z16.
To process z15 and get correct labels you must use:
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA113F %
Thanks to Graham Harris, NatWest, ENGLAND.
Change 40.094 If you don't want to run a week but do want to run a
VMXGALOC month-to-date, both members had problems. VMXGALOC
BLDSMPDB did not create the MONTH directories and BLDSMPDB did
Aug 1, 2022 not execute the MTD code and tried to initialize the
non-existent week directories when FIRSTRUN=YES was
used.
Thanks to Doug Medland, Kyndryl, CANADA;
Change 40.093 Using the SAS FTP ACCESS method, the ftp process can hang
TECHNOTE if HSM is migrating the SMF data file either from disk to
Jul 26, 2022 or tape back to disk. Writing SMF data to tape will
eliminate the exposure.
Change 40.092 ANALMQ and ANALAVAI were not honoring the PDB= parameter,
ANALMQ instead always looked in DDNAME of PDB. Now, the PDB=
ANALAVAI argument is honored for the LIBNAME.
Jul 26, 2022
Change 40.091 The first step in moving MXG to a LUMINEX MDI is to copy
MDIZERO USERID.SOURCLIB from z/OS to LINUX. This JCL uses the
Jul 26, 2022 PROC SOURCE on ZOS to create an IEBUPDTE input file that
is then decoded and reconstructed on LINUX using the
IEBUPDTE.SAS program in the MXG Sourclib.
Change 40.090 MXG Variables/Datasets that contain/include RUCSA metrics
TECHNOTE Dataset TYPE78VS
Jul 26, 2022 R782FLG='RUCSA*IS*DEFINED?'
R782RUCA='RUCSA*ADDRESS*BELOW*16M'
R782RUCS='RUCSA*SIZE*BELOW*16M'
R782ERUCA='RUCSA*ADDRESS*ABOVE*16M'
R782ERUCS='RUCSA*SIZE*ABOVE*16M'
From IBM FIELD R782CSAU:
CSAUSED0='CSA*USED*MIN BELOW'
CSAUSED1='CSA*USED*MIN BELOW TIME'
CSAUSED2='CSA*USED*MAX BELOW'
CSAUSED3='CSA*USED*MAX BELOW TIME'
CSAUSED4='CSA*USED*AVERAGE BELOW'
CSAUSED5='CSA*USED*MIN ABOVE'
CSAUSED6='CSA*USED*MIN ABOVE TIME'
CSAUSED7='CSA*USED*MAX ABOVE'
CSAUSED8='CSA*USED*MAX ABOVE TIME'
CSAUSED9='CSA*USED*AVERAGE ABOVE'
From IBM FIELD R782CSAF:
CSAFREE0='CSA*FREE*MIN BELOW'
CSAFREE1='CSA*FREE*MIN BELOW TIME'
CSAFREE2='CSA*FREE*MAX BELOW'
CSAFREE3='CSA*FREE*MAX BELOW TIME'
CSAFREE4='CSA*FREE*AVERAGE BELOW'
CSAFREE5='CSA*FREE*MIN ABOVE'
CSAFREE6='CSA*FREE*MIN ABOVE TIME'
CSAFREE7='CSA*FREE*MAX ABOVE'
CSAFREE8='CSA*FREE*MAX ABOVE TIME'
CSAFREE9='CSA*FREE*AVERAGE ABOVE'
From IBM FIELD R782CSLF:
CSALARG0='CSA*LARGEST*FREE*MIN BELOW'
CSALARG1='CSA*LARGEST*FREE*MIN BELOW TIME'
CSALARG2='CSA*LARGEST*FREE*MAX BELOW'
CSALARG3='CSA*LARGEST*FREE*MAX BELOW TIME'
CSALARG4='CSA*LARGEST*FREE*AVERAGE BELOW'
CSALARG5='CSA*LARGEST*FREE*MIN ABOVE'
CSALARG6='CSA*LARGEST*FREE*MIN ABOVE TIME'
CSALARG7='CSA*LARGEST*FREE*MAX ABOVE'
CSALARG8='CSA*LARGEST*FREE*MAX ABOVE TIME'
CSALARG9='CSA*LARGEST*FREE*AVERAGE ABOVE'
From IBM FIELD R782CSAL:
CSAALOC0='CSA*ALLOC*MIN BELOW'
CSAALOC1='CSA*ALLOC*MIN BELOW TIME'
CSAALOC2='CSA*ALLOC*MAX BELOW'
CSAALOC3='CSA*ALLOC*MAX BELOW TIME'
CSAALOC4='CSA*ALLOC*AVERAGE BELOW'
CSAALOC5='CSA*ALLOC*MIN ABOVE'
CSAALOC6='CSA*ALLOC*MIN ABOVE TIME'
CSAALOC7='CSA*ALLOC*MAX ABOVE'
CSAALOC8='CSA*ALLOC*MAX ABOVE TIME'
CSAALOC9='CSA*ALLOC*AVERAGE ABOVE'
Dataset TYPE71 IBM NAME
CSAPGAV ='CSA TOTAL*CSTORE*FRAMES*AVERAGE' SMF71AVP
CSAPGMN ='CSA TOTAL*CSTORE*FRAMES*MINIMUM' SMF71MNP
CSAPGMX ='CSA TOTAL*CSTORE*FRAMES*MAXIMUM' SMF71MXP
CSLPFXAV='CSA FIXED*CSTORE*FRAMES*AVERAGE' SMF71AVC
CSLPFXMN='CSA FIXED*CSTORE*FRAMES*MINIMUM' SMF71MNC
CSLPFXMX='CSA FIXED*CSTORE*FRAMES*MAXIMUM' SMF71MXC
Change 40.089 New variables added to dataset SV34TRAN:
VMACSVIE IMTR_CNT_SYNCPOINT='TOTAL*SYNCPOINT*COUNT'
Jul 26, 2022 IMTR_CLK_SYNC_ELAPSED='SYNCPOINT*ELAPSED*TIME'
IMTR_CLK_OSAM_SYNC ='OSAM*SYNCPOINT*TIME'
IMTR_CLK_VSAM_SYNC ='VSAM*SYNCPOINT*TIME'
IMTR_CLK_APPL_ELAPSED='APPLICATION*ELAPSED*TIME'
New variables added to dataset SV35TRAN:
IMRA_SYNC_ELAPSED ='TOTAL*SYNCPOINT*ELAPSED*TIME'
IMRA_DB2_ELAPSED ='TOTAL*DB2*ELAPSED*TIME'
IMRA_MQ_ELAPSED ='TOTAL*MQ*ELAPSED*TIME'
IMRA_DB2_SQL ='TOTAL*DB2*SQL*CALLS'
IMRA_SYNCPOINT ='TOTAL*SYNCPOINT*COUNT'
IMRA_OSAM_SYNC ='TOTAL*OSAM*SYNCPOINT*TIME'
IMRA_VSAM_SYNC ='TOTAL*VSAM*SYNCPOINT*TIME'
IMRA_APPL_ELAPSED ='APPLICATION*ELAPSED*TIME'
Change 40.088 Dataset TYPE42DS variable S42DS2DL is labeled and new
VMAC42 variable S42DS2MV is created. APAR OA59611.
Jul 18, 2022.
Change 40.087 Dedicated Memory variables added to TYPE30_4 (PDB.STEPS),
BUILD005 and TYPE30_V (PDB.SMFINTRV).
BUIL3005 S30DMREQUESTED2G S30DMMINREQUESTED2G S30DMASSIGNED2G
VMAC30 S30DMINUSEAS2G S30DMINUSEASFIXED1M
Jul 18, 2022 S30DMINUSEASPAGEABLE1M S30DMINUSEAS4K
S30DMINUSEASDATTABLES S30DMINUSEAS4KHWM
S30DMINUSEASPAGEABLE1MHWM S30DMINUSEASFIXED1MHWM
S30DMINUSEAS2GHWM S30DMINUSEASDATTABLESHWM
S30DMINUSEHWM S30DM2GFAILED S30DM1MFAILED S30DM4KFAILED
S30DMINUSEAS2GHWM S30DM2GFAILED
Change 40.086 -Dataset TYP11911 Variable SMF119SC_SSH_KEX_METHOD is now
FORMATS created and the incorrect spelled SMF119SC_SSH_KEX_ALG is
VMAC119 set to '0000'X and LABELed 'DO NOT USE'.
Jul 15, 2022 -Format $MG119KX METHOD and $MG119KA ALGORITHM updated to
match the z/OS 2.5 IP Programmer's Guide values.
Thanks to Joe Faska, DTCC, USA.
Change 40.085 New ZRBASI time variables added in z/OS 2.4 and 2.5
VMACRMFV ASI_EJST='TCP*PROCESSOR*TIME*ALL TYPES'
Jul 12, 2022 ASI_SRBT='NON-PREMPT*SRB TIME*ALL TYPES'
ASICPUTA_CP='ALL*NONENCLAVE*TIME*ON CP'
ASI_CP_PHTM='PREEMPT*CLASS SRB*TIME*ON CP'
Change 40.084 TYPE73 data for SMF73CMG=2 Channel Measurement Group has
VMAC73 counters with invalid counts if the CHPID was VARIED in
Jul 11, 2022 the interval. These variables are now set missing for
those intervals CHFACTV/DFER/RATE/XACTV/XDFER/CHFXRATE
PBUSBY PCHANBY PNCHANBY SMF73EOC/EOD/EOS/ETC/ETD/ETS/PUC
TBC/SMF73TUC.
The three Channel Measurement Groups are described as:
1 - Channels like CNC or CTC
2 - Ficon or OSA Express
3 - Hypersockets
Thanks to Vance Breckenridge, FMR, USA.
Change 40.083 If you specified PATHLIST=YES to get a report of the
PDBAUDIT active LIBNAMES there were duplicate lines (SAS only)
Jul 8, 2022 caused by the return of 4 lines per LIBNAME from the PROC
SQL. A sort was added with NODUP to eliminate the extra
lines.
Change 40.082 There are 60 variables added by IBM to the TYPE30_4 data
BUILD005 that were not also added to the PDB.STEPS BUILDPDB data
BUIL3005 set, that are now added for completeness:
Jul 6, 2022 ASID CPUZIPTM_CPUIFATM_INST ENCLACTM ENCLCPSU
ENQTIME EXCPERR EXSRMERR IARVAPIN IARVEPIN IARVPSEC
IEFUSICH IEFUSIME SMF30ACB SMF30ACR SMF30CAI SMF30CCR
SMF30CHC SMF30CONFLAG1 SMF30CONFLAG2 SMF30CONFLAG3
SMF30CONFOLOW SMF30CR SMF30CRM SMF30DAS SMF30DSCC
SMF30HQT SMF30INV SMF30JF1 SMF30JQT SMF30NCR
SMF30NRDS SMF30PCF SMF30PF1 SMF30PF2 SMF30PFF
SMF30PFL SMF30PIN SMF30PRJ SMF30RQT SMF30RTR SMF30SCF
SMF30SLM SMF30SME SMF30SQT SMF30T32 SMF30T33 SMF30TF2
SMF30TIH SMF30TIS SMF30TIU SMF30_INCOMPLETE_DATA
SMF30_INSTCAPTDISRUPTION SMF30_INST_FLGS1_MRS
SMF30_RAXFLAG5 SMF30_RAXFLAG6 SMF30_RCMTADJN SRBCOEFF
SRMNODAT SUBSTEP WLMNAME
Change 40.081 If you did not have an SMF DD or FILENAME statement and
VMACSMF your program tried to read SMF data you got a very odd
Jul 5, 2022 failure caused by the failure to create the SMFENG macro
variable. The variable is now initialised to NO SMF
INFILE FOUND and will be set to DISK or FTP with SAS or
a blank value with WPS.
Change 40.080 In the process of debugging the problem for which 40.006
VMXGSUM was the fix we added an UPCASE function as well as a
Jul 5, 2022 COMPBL function against the incode. Since all character
compares in SAS are case sensitive this can cause an
invalid compare if you are trying to compare values in
the INCODE and are expecting a lower case value. This
change removes the UPCASE but leaves the COMPBL which was
really the solution to the problem.
Thanks to Matthew I. Chappell, Queensland Government, AUSTERALIA
Change 40.079 NOTE: "Variable LENTYP50 may not be initialized" had no
VMAC50 real impact, as that variable was only to be kept and was
Jun 30, 2022 not actually used. Now, correctly set to LENGTH.
Thanks to Randy Schlueter, Fiserv, USA.
====== CHANGES THRU 40.078 ARE IN MXG 40.04 DATED Jun 29,2022 ==========
Change 40.078 MXG 39.09 and earlier fail with APAR OA61811/OA62502,
VMAC7072 due to an MXG error for SMF 72 Subtype 3 TYPE72GO that
Jun 25, 2022 failed to test for new fields after the last segment,
which caused INPUT mis-alignment and invalid data values.
PTFs: z/OS 2.3 UJ07991
PTFs: z/OS 2.4 UJ07990
PTFs: z/OS 2.5 UJ07989
-WE STRONGLY SUGGEST YOU INSTALL THE CURRENT MXG 40.04
WHICH AVOIDS THE COMPLEXITY OF THE BELOW CIRCUMVENTION
AND PROVIDES SIGNIFICANT OTHER ENHANCEMENTS AFTER YOUR .
BACKLEVEL VERSION. PLEASE USE THE FORM AT
HTTPS://WWW.MXG.COM/SOFTWARE_DOWNLOAD_REQUEST
You can circumvent this MXG error by:
-Downloading files at http://www.mxg.com/downloads/
The APAR inserted new fields in SMF 72 Subtype 3 TYPE72GO
that exposed an MXG coding error that failed to test for
new added fields after the last new segment, causing the
INPUT misalignment and invalid data values to be created.
There MAY be INVALID DATA FOR R723IFAT messages or other
fields printed, but those are accidental and there might
not be ANY log messages that the error occurred. And even
if there are INVALID DATA messages, they do not set a
CONDITION CODE, so there may be no clue on the log that
the error occurred.
MXG 39.39 thru MXG 40.03 correctly input the new data.
but only this change or MXG 40.04 has the protection for
additional new fields.
Change 40.077 -Variables SYNCNCIN SYNCNCON SYNCKEXN are added and they
FORMATS are decoded by format $MGSYNNG. Format $MGSYNEQ updated
VMACSYNC for 'C9'X for SORTL.
Jun 24, 2022 -Format $MGSYNNG for Reason Code is missing values of
Nov 14, 2022 '06'x '07'x '0F' '10'x '11'x '13'x '18'x
Nov 21, 2022 -Variable SYNCEQLS is a multi-bit flag variable that is
correctly decoded, but to identify SORTL was used, you
must test the values of '08'x or 'C9'x so now there are
eight one=byte variables for each bit for simpler tests:
SYNSOTRP='SORTOUT*DATA*STRIPING?'
SYNSITRP='SORTIN*DATA*STRIPING?'
SYNBPSI ='BATCHPIPES*MVS*DATASET*SORTIN?'
SYNBPDS ='BATCHPIPES*MVS*DATASET*PRESENT?'
SYNEQUON='EQUALS*ON?'
SYNCMPO ='COMPRESSED*SORTOUT*WITH*STARTIO?'
SYNCMPI ='COMPRESSED*SORTOUT*WITH*STARTIO?'
SYNSORTL='SORTL*ALGORITHM*USED?'
Thanks to Jan Tielemans, KBC, BELGIUM.
====== CHANGES THRU 40.076 ARE IN MXG 40.03 DATED Jun 23,2022 =========
Change 40.076 ERROR: SHORT 42 SUBTYPE 6 ACCESS METHOD SECTION due to
VMAC42 a reserved field that was overlooked.
Jun 23, 2022
Thanks to Robert Chavez, Florida Power & Light, USA.
Change 40.075 Members VGETDDS and VMXGSET in First MXG 40.03 were
VGETDDS replaced with those members from 40.02, Change 40.072
VMXGSET "enhanced" those members to support more than 99 DDs, but
Jun 23, 2022 the enhancement could fail (only one report).
Change 40.074 Variable TLSLEVEL 1.1/1.2/1.3 is added to NDMCT dataset.
VMACNDM
Jun 21, 2022
Thanks to Luis Mendoza, BKFS, USA.
====== CHANGES THRU 40.073 ARE IN MXG 40.03 DATED Jun 15,2022 =========
Change 40.073 S11912SAFLAGX40,20,10,08,04 were byte-tested ('80'X) so
VMAC119 only one bit was tested, but the field can have multiple
Jun 14, 2022 bits so the fields now are bit-tested ('1.......'B).
Thanks to Tom White, Bank of America, USA.
Thanks to Charlie Carlson, Bank of America, USA.
Change 40.072 Hardcoded limit of 99 DDs in VMXGSET limited VGETDDS.
VGETDDS Limit replaced by better logic with no limit; IBM has
VMXGSET increased the maximum number of generations to 999.
Jun 10, 2022
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.071 Explanation of DB2 differences with PROC COMPARE.
VMACDB2 -DB2ACCT QB1C/QB2C/QB3C/QB4C suffix HPG/HRE/HRF/HWF/HWR
VMACDB2H and SWU are always missing values after Change 39.200,
Jun 5, 2022 they were replaced by SYIT/SYI/IOC/RSV3/RSV2/RSV1.
All other DB2ACCT variables matched.
-Datetime variables QWHSSTCK BEGTIME ENDTIME MXG 39.04+
(Change 39.099) were 26 seconds early due to MXG logic
that creates DB2GMTDB GMT Offset (IBM does not provide)
which incorrectly thought leap seconds were included in
the TODSTAMP fields. The subtraction was removed.
BUT: No site ever reported that 26 second delta!
-DB2STAT4 QW0225 variables are larger; were 4 bytes now 8,
and _REAL now includes _AUX & _DPAGE. (and AUX is 12288).
Variable QW0225_WARN is corrected to bytes from blocks.
-Datasets DB2ACCTR DB2ACCTW DB2STAT1 and DB2STAT2 match.
-Dataset DB2ACCTB variables QBACCIOD/SYI/SYIT are also
missing after Change 39.200 which reused their slots..
-All Q8ACxxxx and Q8STxxxx variables are only populated
with DB2NETEZZA.
Change 40.071 SMF42 Subtype 6 enhanced with new TYPE42DS variables:
VMAC42 S42JDVER='VERSION*NUMBER'
Jun 2, 2022 S42JDST1='STEP*NUMBER'
S42JDSTN='STEP*NAME'
Change 40.070 Support for z16 HIS SMF 113 data.
VMAC113 -Many labels are changed, and different counters are used
ASUM113 for RNI and the other metrics so the default support in
Jun 2, 2022 40.03 is only for the z16 metrics. You will need to use
separate jobs/steps to process each hardware platform.
For the z/15 SMF you would use
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA113F %
and for the z/16 SMF you would use
//SYSIN DD *
%LET MACKEEP= MACRO _XLA113 _XLA113G %
(or just use the default without a %LET statement.
Change 40.069 Updates from May 22, 2022 SMF Manual:
VMAC30 -TYPE30_4 TYPE30_5 TYPE30_6 TYPE30_V datasets
VMAC7072 New variables:
VMAC74 SMF30CONFOLOW SMF30CONFLAG1-SMF30CONFLAG3
VMAC90A
May 31, 2022
Change 40.068 Updates from May 24, 2022 Data Gatherer Manual:
VMACRMFV -ZRBASI dataset
May 31, 2022 New flag variables:
ASITRGRP='TENANT*RESOURCE*GROUP?'
ASIRCVBO='RECOVERY*BOOST?'
-ZRBLCP dataset
New variable
LCPUTOPC='TOPOLOGY*HAS*CHANGED'
-ZRBDNG NEW Dataset:
Await Test Data to update ASMRMFV and then VMACRMFV.
Change 40.067 -Service policy selection correction post-IPL checking to
ASMRMFV enable sample set BEG/END time to coincide policy's.
May 30, 2022 -Cosmetic: correct RMFV008 DSORG alignment
-Cosmetic: match ASM field names to match VMACRMFV
-Restored REDID type variables to correct type
-Errors processing UWDG3 record corrected.
-Two sites have received CC=4 due to the BEG/END & REDIT
change, because IBM Data Gatherer Support has been unable
to replicate the warning, and we need to know if other
sites have the issue. If so, please use SENDVSAM to send
your VSAM RMF III file so we can get it to IBM support.
-It is also possible to get CC=4 for "WARNING:DEAD SPACE"
but we are examining if that should be INFORMATIONAL for
the next iteration of ASMRMFV.
Change 40.066. Variable ECMTSTMP in z/VM dataset VXSYTEPM was wrong; it
VMACVMXA was not scaled by 128 microseconds.
May 27, 2022
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.065. TYPS103 ERROR: Attempt to open two sequential members
VMAC103 if //PDB was on tape. The _STY1032 sort macro had //PDB
May 27, 2022 library for both the INPUT and OUTPUT.
Thanks to Cesar V. Cocco, JPMorgan Chase, USA.
Change 40.064. Reserved Change.
May 31, 2022
Change 40.063. Variables DSAPTHTM JVMTHDTM MAXHTDTM in CICSTRAN are
VMAC110 correct if UTILEXCL was used to create your IMACEXCL,
May 24, 2022 but those variables were NOT divided by 4096 (for STCK)
if you didn't use UTILEXCL and didn't have an IMACEXCL.
This change adds the missing /4096 for those variables.
And WTOTIOTM was also wrong because it includes DSAPTHTM
Thanks to Lorena Ortenzi, Kyndryl, ITALY.
Thanks to Alessandro Cappobianco, Kyndryl, ITALY.
Change 40.062. Dataset TYP11912SSH variable S11912SS_SSH_KEX_METHOD and
FORMATS S11912SS_SSH_KEX_ALG that are formatted with $MG119KX did
May 20, 2022 not decode new values added by z/OS 2.4. Now values are:
VALUE $MG119KX
'0000'X='UNKNOWN'
'0001'X='NONE'
'0002'X='DIFFIE-HELLMAN-GROUPEXCHANGESHA256'
'0003'X='DIFFIE-HELLMAN-GROUPEXCHANGESHA1'
'0004'X='DIFFIE-HELLMAN-GROUP14-SHA1'
'0005'X='DIFFIE-HELLMAN-GROUP1-SHA1'
'0006'X='ECDH-SHA2-NISTP256'
'0007'X='ECDH-SHA2-NISTP384'
'0008'X='ECDH-SHA2-NISTP521'
'0009'X='GSS-GROUP1-SHA1'
'000A'X='GSS-GROUP14-SHA1'
'000B'X='GSS-GEX-SHA1'
'000C'X= 'DIFFIE-HELLMAN-GROUP14-SHA256'
'000D'X= 'DIFFIE-HELLMAN-GROUP16-SHA512'
'000E'X= 'DIFFIE-HELLMAN-GROUP19-SHA512'
'000F'X= 'CURVE25519-SHA256'
'1002'X= 'DIFFIE-HELLMAN-GROUP19-EXCHANGESHA256(ICSF)'
'1003'X= 'DIFFIE-HELLMAN-GROUP19-SHA1(ICSF)'
'1004'X= 'DIFFIE-HELLMAN-GROUP14-SHA1(ICSF)'
'1005'X= 'DIFFIE-HELLMAN-GROUP1-SHA1(ICSF)'
'1006'X= 'ECDH-SHA2-NISTP256(ICSF)'
'1007'X= 'ECDH-SHA2-NISTP256(ICSF)'
'1008'X= 'ECDH-SHA2-NISTP521(ICSF)'
'1009'X= 'GSS-GROUP1-SHA1(ICSF)'
'100A'X= 'GSS-GROUP14-SHA1(ICSF)'
'100B'X= 'GSS-GEX-SHA1(ICSF)'
;
Thanks to Eviatar Farchy, DTCC, USA.
Change 40.061.-RMM Extract Dataset EDGRDEXT new variables added:
VMACEDGR RDLRED ='LASTREF*EXTRA DAYS'
May 20, 2022 RDWHILECATON='WHILE*CATALOG=ON*Y,N?'
RDWHILECATUX='WHILE*CAGALOG*UNTIL*EXPIRED*Y?'
-RMM Extract Dataset EDGRXEXT new variables added:
XVKEYLABEL1='ENCRYPTION*KEY*LABEL 1'
XVKEYENCOD1='ENCRYPTION*ENCODING*METHOD 1'
XVKEYLABEL2='ENCRYPTION*KEY*LABEL 2'
XVKEYENCOD2='ENCRYPTION*ENCODING*METHOD 2'
XVMEDINF ='MEDIA*INFORMATION'
XVIRMMUSE ='IRRM*USED?'
XVWORM ='WORM*USED?'
XVHOLD ='VOLUME*HOLD?'
XVESB ='EXPD*SET BY*VOLUME'
XDESB ='VEXPDT*SET BY*DATASET'
XVUCDATE ='VOLUME*LAST*USER*CHANGE*DATE'
XVUCTIME ='VOLUME*LAST*USER*CHANGE*TIME'
XDUCDATE ='DATASET*LAST*USER*CHANGE*DATE'
XDUCTIME ='DATASET*LAST*USER*CHANGE*TIME'
XDVEX ='VRSEL*EXCLUDE?'
XVRETMET ='RETENTION*METHOD'
XVRMSB ='RETENTION*SET*BY'
XVCOMP_RAT ='COMPRESSION*RATIO*FOR VOLUME'
XVPHYS_USED='ACTUAL*SPACE*USED*ALL FILES'
XDCOMP_RAT ='COMPRESSION*RATIO*FOR FILE'
XDPHYS_SIZE='DATA ON*TAPE*AFTER*COMPRESSION'
XDLRED ='LASTREF*EXTRA*DAYS'
XVEXRB ='EXPDT*RETAINBY'
XVEDM ='VOLUME*EDM?'
XDWHILECATON='DSN*WHILECATALOG*ON?'
XDWHILECATUX='DSN*WHILECATALOG*UX?'
Thanks to John E. Benik, Optum, USA.
Change 40.060. RMF III update for ZRBRED dataset, and for FORMATS.
FORMATS
VMACRMFV
May 16, 2022
Change 40.059 -Support for SMF 80 RACFTYPE=67 records adds variables to.
VMAC80A RACF dataset TYPE8081:
May 12, 2022 RA67BITS='PASSTICKET*EVAL*HEX'
RA67RTRN='PASSTICKET*RETURN*CODE*HEX'
RA67REAS='PASSTICKET*REASON*CODE*HEX'
RA67NAME='PASSTICKET*APPLICATION*NAME'
-Only 5 UNKNOWN RACFTYPE messages are printed.
Thanks to Craig S. Bigler, Progressive, USA.
Thanks to Martha A. Knapik, Progressive, USA.
Change 40.058 Support for APAR OA60660 for TYPE9040 BOOST.
FORMATS -New values for Formats MG090ID for SMF9040IDNR and
VMAC90A MG090EV for SMF9040E.
May 23, 2022 -New variables
BOOSTLEVEL='BOOST*LEVEL'
RPBDISABLE='RPB*DISABLED?'
SMF9040RPBDU='RPB*DURATION*DELTA'
SMF9040RPBPO='RPB*DURATION*POTENTIAL'
SMF9040RPBPD='RPB*DURATION*POT DELTA'
SMF9040RPBPE='RPB*DURATION*POT E'
SMF9040RPBED='RPB*DURATION*POT E DELTA'
Change 40.057 BUILDPDB CRITICAL ERROR DUPLICATE TYPE30 SUBTYPE 1 FOUND
BUILD005 can result when testing BUILDPDB jobs that ABENDED or if
BUIL3005 the same SMF file was read in multiple BUILDPDB jobs.
May 9, 2022 This enhancement inserts a PROC SORT NODUPKEY to remove
any duplicates, printing log notes if any were found.
Thanks to John Barnes, Zions Bank Corp.
Change 40.056 Dataset BVIR302 had only half the number of observations
VMACBVIR it should have had starting in MXG 39.04 thru MXG 40.02.
May 6, 2022 due to a 2 byte misalignment for the second of the pair.
====== CHANGES THRU 40.055 ARE IN MXG 40.02 DATED May 5,2022 =========
Change 40.055 -Variable ZCOS01TI corrected.
VMACZCOS -Support for subtype 5 in progress, text will be updated
Apr 29, 2022 if/when subtype 5 data with populated triplets received.
Thanks to Virginie Peigney, CA-GIP, FRANCE.
Thanks to Claude Tetard, CA-GIP, FRANCE.
Change 40.054 Variables added to TYPE122A dataset:
VMAC122A SMF122T1S3F_VUON ='CLIENT*ACTIVATION CODE*PROVIDED?'
Apr 28, 2022 SMF122T1S4_UUID ='UUID'
SMF122T1S1_SYSPLEX='SYSPLEX*NAME'
ZEXPLAPIVERSIONCLIENT='ZEXPLAPI*VERSION*CLIENT'
ZEXPLAPIVERSIONHOST='ZEXPLAPI*VERSION*HOST'
PRODUCTAPIVERSIONHOST='PRODUCTAPI*VERSION*HOST'
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 40.053 -Variables SMF92WID added to all datasets.
VMAC92 -Subtype 11 and 16 records are both output in TYPE9211;
Apr 26, 2022 the value in SMF92STP identifies the subtype.
Dataset TYPE9216 will always have zero observations.
-New variables in Dataset TYPE9211:
SMF92CF4='Y';/*FILE*WAS*CACHED?*/
SMF92CF5='Y';/*FILE*HAD*DENY*READ?*/
SMF92CF6='Y';/*FILE*HAD*DENY*WRITE?*/
-Tests for length SMF92ILN changed to GE 72 or 32 vs EQ.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.052 Variables TVCSIZE and TVCSIZE8 are now correct.
VMACBVIR
Apr 26, 2022
Thanks to Maria Paola Bramosi, Kyndryl, ITALY
Thanks to Lorena Ortenzi,Kyndryl, ITALY
Thanks to Valeria Consiglio, Kyndryl, ITALY.
Change 40.051 -Clean-up of ZRBASM dataset corrected alignments and added
VMACRMFV new variables
Apr 26, 2022 ASMZLP='OUTPUT*ZERO*LP*LPARS?'
ASMIFE='IF=*KEY*WORD*ERRORS?;
ASMSLSIZ='EXECUTION*STEP LVL*PGM SIZE'
ASMDCPCRX='MAXIMUM*CPCNAME*RANGES'
ASMDCPCPX='MAXIMUM*CPCNAME*PATTERNS'
ASMDLPRRX='MAXIMUM*LPARNAME*RANGES'
ASMDLPRPX='MAXIMUM*LPARNAME*PATTERNS'
-These variables were retained from ZRBSSHG3 and output in
ZRBBDSIH and the six ZRBSVCx datasets, but they are now
removed because they are either missing or have wrong
values, retained from from a prior sample set when there:
are multiple sample sets input:
GMTOFF SSHGOSYN SHIFT CPC_CECNAME LPARNAME SSHTIBEG
SSHTIEND SSHRMFVN SSHMPRNR SSHGOMNT
-If you use PROC APPEND, you MUST specify FORCE and NOWARN
when there are changes between DATA= and BASE= datasets,
to allow the APPEND and to prevent the WARNING MESSAGE
and to prevent the CONDITION CODE 4.
Change 40.050 -MXG 40.01, SMF30 ABEND with z/16 SMF or APAR OA61511 due
VMAC30 to MXG coding error for new Crypto counters. Line 1812
Apr 22, 2022 IF OFFPROD GE 193 THEN DO; in VMAC30 needs to be GE 220
to circumvent this error. That APAR was in RSU2301.
Change 40.049 An extra paren in the Dataset Label for IFCID 100 and 101
VMAC102 did not impact their creation, but VMXGPRAL died when it
Apr 20, 2022 tried to print those dataset labels.
Change 40.048 -ASUM70PR Hardware Capping variables SMF70HWGRNAME,
VMXG70PR SMF70HWGR_CAP_LIMIT and SMF70HW_CAP_LIMIT are added to
Apr 25, 2022 dataset ASUMCELP.
-TYPE70PR variable SMF70HWGR_CAP_LIMIT LABEL statement
updated to 'IN NR ENGINES'.
-CODE WARNING Message YES or not NO suppresses report.
Thanks to Shantanu Gupta, ENSONO, USA.
Change 40.047 Support for IBM CL/SuperSession V3.1 found undocumented
VMACNAF bytes and incorrect record lengths and invalid SMFSTAMP
Apr 16, 2022 values that had '20'x instead of '01'x for century bit.
Thanks to Linda S. Berkley, DISA, USA.
Change 40.046 HSMFSRBO and HSMFSRST dataset variable FSR2_UNAM was
VMACHSM INPUT as VARYING1024 but INPUT(FSR2_UNAM,$EBCDIC128.).
Apr 12, 2022 kept only the first 128 bytes. Now all 1024 are kept.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 40.045 Support for APAR OA61609 for TYPE82 records.
FORMATS -FORMAT $MG082AL updated for STAT_ENG_ALG_NAM in SMF8231.
VMAC82 -FORMAT $MG082LA updated for SMF82_TAG_KEY_ALG in SMF8241.
Apr 7, 2022 -Variable STAT_ENG_CARD_ID is now readable in SMF8231.
-These Subtypes have changes in this APAR but I don't have
test data: 1,41,42,45,46,48
-Support for Z16 Hardware ICSM-CEX8S for Dilithium 6-5 R3,
and 8-7 R3 Support in CCA and PKCS, Kyber in CCA/PKCS.
Thanks to Luis Mendoza, BKFS, USA.
Change 40.044 No impact, but three TYPE70 variables are now reserved:
VMAC7072 SMF70MDL_CBP SMF70MCR_CBP and SMF70NCR_CBP were intended
Apr 7, 2022 to be populated for the CBP (Container Based Processor)
engine which was never implemented, and IBM confirms
there is no plan to do so going forward. The CBP fields
replaced the discontinued zAAP fields. MXG was updated to
support the ESP sites that also never happened. All zAAP
variable's names were unchanged, but CBP was added to all
labels; I don't intend to remove the CBP text..
Change 40.043 Replaced with Change 40.067.
Change 40.042 CICS/TS 6.1 BETA 25 removed fields 291 (SOCPSCT) and 293
VMAC110 (SOPSHWM) from CICSTRAN records. INCOMPATIBLE.
Apr 4, 2022
Change 40.041 If you ran VMXGUOW in a SAS session without a PDB DDNAME,
VMXGUOW and you did not ask for MQ data (MXGMQAdd=yes) you could
Apr 4, 2022 get an error LIBREF PDB NOT FOUND.
Thanks to Roger Lowe, NT Government, AUSTRALIA
Change 40.040 In May 2021 negative values in DB2 QPACZITM Package Ziip
TECHNOTE time was reported to IBM. The error is addressed by APAR
Mar 31, 2022 PH40410 with PTF UI79705 for DB2 V12.1. This error
impacts users of external stored procedures and UDFs when
a stored procedure or UDF is cancelled in the middle of
its processing. The SP/UDF recovery processing will get
control, and in that recovery processing, code is missing
or incorrect to record the times for the DB2 Accounting
Record. Code was added or fixed in the cancel thread
scenario.
Thanks to Glenn Bowman, Wakefern, USA.
Change 40.039 z/OS 2.5 TYPE 0 IPL record lengths 78 and 83 were not in
VMAC0 the list of valid record lengths causing ***VMAC0.ERROR
Mar 31, 2022 messages and those records were not input. For a true IPL
the ERROR message is followed by a 90-10 PUTLOG which is
the confirmation the type 0 was for an IPL.
Thanks to Andreas Menne, Finanz Informatik, GERMANY
Change 40.038 DATACOM INPUT missed reserved field causing misalignment
VMACDCOM and incorrect values. New variables added..
Mar 30, 2022
Thanks to Linda S. Berkley, DISA, USA.
Change 40.037 New variable ZCOS01TI is created as a datetime value from
VMACZCOS character variable ZCOS01TM. Missing values are created
Mar 25, 2022 for values of 00.000.00-00:00 or all zeroes.
Thanks to Pier-Pascal Jouilin, SOCGEN, FRANCE
Change 40.036 -ASMRMFV ZEROLP logic has been corrected to properly build
ASMRMFV CPCDB records. With 39.227, the logical processor
ADOCRMFV sections were padded with binary zeros which tripped up
Mar 22, 2022 VMACRMFV analysis of the CPCDB records.
CHANGE 40.035 Variables SMF70GMU, SMF70CPA, and SMF70WLA were missing
VMXG70PR values in dataset ASUMCELP.
Apr 23, 2022 This is not yet implemented. Contact Support.
CHANGE 40.034 TYPE 70 BLOCKED WORKLOAD variables SMF70PMT and SMF70PMU
VMAC7072 were corrected. SMF70PMU is rounded up to next 1% in the
Mar 21, 2022 RMF Report, but MXG has left the actual value.
Thanks to Flavio Lima, Kyndryl, USA.
CHANGE 40.033 VM Accounting VMID='C0'x and USER='RCSC' INVALID DATA FOR
TYPEVM CPUMODEL because the format of the record changes and the
Mar 30, 2022 C0 record for RSCS has not yet been found. CPUMODEL is
protected.
Thanks to Linda Berkley, DISA, USA.
====== CHANGES THRU 40.032 ARE IN MXG 40.01 DATED Mar 4, 2022 =========
CHANGE 40.032 -If you ran VMXGUOW in a different SAS session than the
ASUMUOW one that created the input data sets, VMACDB2,VMAC110 and
VMXGUOW VMAC116 members are needed to resolve MACROs, but MXG
Mar 17, 2022 39.39 and earlier did not include VMAC116, causing zero
obs in the MQ data since the step would try to use the
_LTY116 and _LTY1161 which do not exist without VMAC116.
-ASUMUOW example in comments was updated.
Thanks to Nagaraj Pudukotai,
====== CHANGES THRU 40.031 ARE IN MXG 40.01 DATED Mar 4, 2022 =========
CHANGE 40.031 Replaced by Change 40.032.
Change 40.030 IMTR_TRN_ fields after STEPNAME were misaligned; the four
VMACSVIE UNDOC bytes after IMTR_TRN_CLASS1 should be after USERID.
Mar 2, 2022 Select WHEN statements had underscore in text that should
be dashes. Variable IMTR_DAC_DBDLET was added to KEEP and
to MACRO _DR3ADA
Thanks to James Robbins, Broadcom, USA.
Thanks to Don Cleveland, KYNDRYL, USA
Change 40.029 ERROR: ARRAY SUBSCRIPT 51 OUT OF RANGE ARRAY ALHTNEXT.
VMACRMFV The default array size of 50 lock holders was too small;
Mar 2, 2022 the temporary arrays were increased to 500 taking only
2Mib virtual storage to eliminate any exposure.
Thanks to Randy Schlueter, Fiserv, USA.
Change 40.028 -ASMRMFV now accepts PARM='F=Y,T=Y' syntax which caused
ASMRMFV CC=8 in 39.39 (and EA 40.01) due to Change 39.100.
Mar 2, 2022 Syntax of PARM='FROM=FROM,TO=Y' will work with 39.39.
Thanks to Len Shenfield, ADP, USA.
Thanks to David Dittmar, ADP, USA.
Change 40.027 $MGSMFID Format for ANALID new 90.040 (BOOST INFORMATION)
FORMATS and 90.41 (CVTLSO CHANGE). values added.
Feb 25, 2022
Change 40.026 TYPE72GO variables RDCENDxx were not input, because the
VMAC7072 test for LENSCS GE 815 should have been 813.
Feb 25, 2022
Change 40.025 Support for OA61511 Crypto/NNPI counts in SMF 0 and 30
EXTY30CP ABENDS SMF 30 in MXG 40.01, See Change 40.050 in 40.02.
EXTY30NP -New variables added to TYPE0 dataset.
IMAC30 SMF0_NUM_CRYPCTRS='CRYPTO*COUNTERS*SUPPORTED'
VMAC30 SMF0_NUM_NNPICTRS='NNPI*COUNTERS*SUPPORTED'
VMAC0 SMF0_FLAGS='SMF0*FLAGS'
VMXGINIT -New TYPE30CP and TYPE30NP datasets Crypto/NNPI counts.
Feb 25, 2022 TYPE30CP - CRYPTO COUNTERS
SMF30CONFLAG1='FIRSTREC*SET OF*TWO OR*MORE'
SMF30CONFLAG2='SECOND*NOT*LAST'
SMF30CONFLAG3='LAST OF*TWO OR*MORE'
SMF30_CRYPCTRS_ENTRY_ID='CRYPTO*COUNTER ENT ID'
SMF30_CRYPCTRS_VALUE ='CRYPTO*COUNTER*VALUE'
SMF30CPA='SMF30CPA SECTIONS SUBSEQUENT'
TYPE30NP - NNPI COUNTERS
SMF30CONFLAG1='FIRSTREC*SET OF*TWO OR*MORE'
SMF30CONFLAG2='SECOND*NOT*LAST'
SMF30CONFLAG3='LAST OF*TWO OR*MORE'
SMF30_CRYPCTRS_ENTRY_ID='CRYPTO*COUNTER ENT ID'
SMF30_CRYPCTRS_VALUE ='CRYPTO*COUNTER*VALUE'
SMF30NPA='SMF30NPA SECTIONS SUBSEQUENT'
Change 40.024 Macro variables MXGALERT MXGMAILFROM MXGMAILTO added for
VMXGINIT a future enhancement.
Feb 25, 2022
Change 40.023 SMF 102 IFCID 220 Argument to function MDY IS INVALID
VMAC102 was caused by +4 misalignment of the INPUT statement.
Feb 23, 2022
Thanks to Randall Schlueter, FISERV, USA.
Change 40.022 Format $MGRMFRE decodes variable REDREDID in ZRBRED
FORMATS
VMACRMFV
Feb 13, 2022
Change 40.021 TYPETPMX variable JCLJJR was not decoded because TOKFIELD
VMACTPMX contains a lower case character that was not expected.
Feb 9, 2022
Thanks to Ralph J. Romano, OPTUM, USA.
Change 40.020 Added second TESTSTRING2 to delete invalid records that
VMACCTLC have a blank in byte 9.
Feb 9, 2022
Thanks to Craig Collins, State of Wisconsin, USA.
Thanks to Maggie Buday, State of Wisconsin, USA.
Change 40.019 Format MGKILO was extended to decode EXABYTE VALUES.
FORMATS
Feb 8, 2022
Thanks to Jorge Fong, DOITT.NYC.
Change 40.018 Dataset TYPE115S was misaligned because 8 bytes were
VMAC115 added to the SM1152NQ segments.
Feb 8, 2022
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 40.017 The TYPE30_4/TYPE30_5 dataset variables EXCPTOTL/EXCPNODD
VMAC30 IOTMTOTL/IOTMNODD counts are wrong for jobs/steps that
Feb 7, 2022 have MULTIDD='Y' records. These are additional SMF 30
records created when there are more DDs than will fit in
one 32K record and they contain the extra TODD counts.
The "real" step record that contains the address space
EXCPTOTL/IOTMTOTL counts has MULTIDD=' ' with some TODD
counts, but NODD=TOTL-TODD can't be calculated in that
MULTIDD=' ' record because of the TODD counts that are in
those other MULTIDD='Y' records. And NODD can't be
calculated in those records that don't have the TOTLs.
The logic to combine those MULTIDD='Y' records and to
create a single TYPE30_4/TYPE30_5 obs with correct counts
is in the BUILDPDB logic, and you can use this example to
create only the PDB.STEPS and PDB.JOBS datasets and use
them in place of TYPE30_4 and TYPE30_5:
%LET MXGANALID=NO;
%LET MACFILE= %QUOTE (
IF ID=6 OR ID=26 OR (ID=30 AND SUBTYPE IN (1,4,5) ); );
%INCLUDE SOURCLIB(BUILD001,BUILD005);
PROC DATASETS LIB=PDB;
DELETE
DB2ACCT DB2ACCTB DB2ACCTG DB2ACCTP DB2ACCTR DB2ACCTW
DB2GBPAT DB2GBPST DB2NETZA DB2ST225 DB2STAT0 DB2STAT1
DB2STAT2 DB2STAT4 DB2STAT5 DB2STATB DB2STATR DB2STATS
DB2STSBP NJEPURGE PRINT SMFINTRV SPIN26 SPIN30TD
SPIN30_1 SPIN30_4 SPIN30_5 SPIN6 SPUNJOBS;
Thanks to Jeffrey S. Britton, IRS, USA.
Thanks to Mark C. Smith, IRS, USA.
Thanks to Twanna G. Wiley, IRS, USA.
Change 40.016 z/OS 1.12 and 1.13 write SMF 42 Subtype 5 with LENSR=96
VMAC42 that MXG detected and deleted with a warning message, but
Feb 2, 2022 APAR OA53110 (2017) that added the new zHPF fields and
set LENSR=160 is not available for these back-levals.
However the records are valid for those 96 bytes and are
now output with no message.
Thanks to Jeffrey Fracas, ENSONO. USA.
Change 40.015 ASCII execution. If you use VMXGALOC and choose to send
VMXGALOC DB2 or CICS to a different location than the BASEDIR=
Jan 28, 2022 directory, the aging of directories failed because it was
looking for that directory. Now, BASEDB2 and BASECICS are
used.
NOTE: VMXGALOC only deletes the directory indicated by
the KEEP&&&&- parameters so if you have been running for
a while you may need to do a manual cleanup. Assume today
is Jan 28 and you used CICSKEEP=3. CICS220127 would be
created and CICS220124 would be deleted leaving
220125-220127 but any prior to 220124 would remain and
would need to be manually deleted
Thanks to Jose Rivera, UPS, USA.
Change 40.014 TYPE 16 SORT records can have offsets that point beyond
VMAC16 the record length causing INPUT STATEMENT EXCEEDED error.
Jan 28, 2022 Now prints TRUNCATED SMF 16 RECORD INDS or OTDS log
message that identifies the job that created the record,
and the record is deleted. One bad record was created
by a job using PGM=ICETOOL that had an ABEND S222.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 40.013 Format $MGSYNEQ decodes variable SYNEQULS.
FORMATS
VMACSYNC
Jan 31, 2022
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 40.012 Variable R742PUSE in dataset TYPE74PA is changed from the
VMAC74 count of 1K blocks to the number of bytes and formatted
Jan 28, 2022 MGBYTES so it can be directly compared with R742PMXM.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 40.011 -Variable TPCRELEASE added to dataset XMTCPSYS.
EXVSIDIA -Support for VSIDIA Segment with Linux Diagnose Codes
FORMATS creates XMVSIDIA dataset.
VMACXAM
VMXGINIT
Jan 31, 2022
Thanks to Douglas C. Walter, CITIGROUP, USA.
Thanks to Arthur Koerner, CITIGROUP, USA
Change 40.010 z/VM 7.2.21.02 ABEND with Broken Control Record corrected
VMACVMXA
Jan 27, 2022
Thanks to Rob D'Andrea, NATWEST, ENGLAND.
Change 40.009 Variables QCSTSLSN/QCSTSLCN/QCSTSLCS are added to dataset
TYPE116 MQCHININ.
Jan 26, 2022
Thanks to Gennady Katsnelson, Kyndryl, USA.
Change 40.008 The DCB Attributes were incorrectly added to VMACBVIR in
TYPEBVIR line 55 in VMACBVIR. They are now removed and only the
Jan 24, 2022 JFCB=BVIRJFCB is set for z/OS execution.
Thanks to Jorge Fong, DOITT.NYC.
Change 40.007 -If you did not specify an offset for a system 0 was used
TIMEBILD and if you did not specify a GMT offset 0 was used again.
VMAC30 Now both produce MXGNOTEs and the offset is still set to
Jan 31, 2022 0 and the GMT offset is to the same value as the offset.
-Variable INTBTIME was corrected for TIMEBILD.
Thanks to Rob G. Hollingum, HSBC,
Change 40.006 Very odd problem from an ASCII user. It appears that
VMXGSUM their IMACSHFT member may have been created using a
VMXGRMFI TEXT EDITOR that leaves out the CRLF at the end of each
Jan 23, 2022 line creating a long string. When that string hit the
incode logic it choked and probably broke a line in the
middle or a word. THere were two solutions and both are
implemented. First VMXGSUM was modified and the COMPBL
function is used to get rid of blanks. Second the
redundant IMACSHFT call in the first TYPE75 summary was
removed. Error surfaced as INDEX VALUE error on log.
Change 40.005 R742PUTx variables in TYPE74PA were divided by 1E-6 after
VMAC74 being INPUT with INFORMAT &PIB.8.6 which also divides the
Jan 19, 2022 PIB8 value by one million.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 40.004 Hard-coded DATA FINL70PR1/VIEW=FINL70PR1 was overlooked
VMXG70PR and its VIEW could not be disabled with %LET MXGVIEW=NO.
VMXGINIT Now, macro variable &VWTY70PR is used. Early WPS did not
Jan 14, 2022 support VIEWS.
Thanks to John Compton, World Programming, ENGLAND.
Thanks to Chris Hill, World Programming, ENGLAND.
Change 40.003 PDB.RMFINTRV new variable MSUSCRT=CPUEFFTM*SMF70CPA/1E6
VMXGRMFI estimates the MSU reported by IBM's SCRT.
Jan 12, 2022
Thanks to Thomas Heitlinger, Atruvia, GERMANY
Change 40.002 Summarization and Trending for MQ SMF 115 data. MXG 39.39
ASUM115X had added ASUMMQAC and TRNDMQAC for MQ SMF 116 data.
TRND115X
VMXGINIT
Jan 11, 2022
Change 40.001 CICS/TS 6.1 OPEN BETA 22 Jan 22, 2022 REQUIRES MXG 40.01
TYPE110 because a second new field was inserted in the CICSTRAN
UTILEXCL record. The first was added/supported in MXG 39.07.
Jan 11, 2022
LASTCHANGE: Version 40.