COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES ALL
========================================================================
/* COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA */
========================================================================
This member (CHANGESS) contains ALL changes to ALL MXG Versions, so
that you can search a single member if you are looking for information.
(Use EXCLUDE ALL then FIND ===member= ALL to see MXG Version.)
Member CHANGES still contains the current changes, incompatibilities,
hot notes, etc., and the members CHANGEnn still contain the changes
that were introduced in MXG Version nn.
Member NEWSLTRS contains new technical notes and all past newsletters.
=========================member=CHANGE36================================
/* COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG VERSION 36.09 is dated Oct 18, 2018, thru Change 36.197.
MXG VERSION 36.08 was dated Sep 10, 2018, thru Change 36.170.
MXG Version 36.07 was dated Aug 8, 2018, thru Change 36.149.
MXG Version 36.06 was dated Jul 9, 2018, thru Change 36.128.
MXG Version 36.05 was dated Jun 13, 2018, thru Change 36.119..
MXG Version 36.04 was dated May 8, 2018, thru Change 36.091.
MXG Version 36.03 was dated Apr 2, 2018, thru Change 36.064.
MXG Version 36.02 was dated Mar 5, 2018, thru Change 36.050.
First MXG Version 36.01 was dated Feb 6, 2018, thru Change 36.026.
Annual MXG Version 35.36 was dated Jan 8, 2018, thru Change 35.309.
The Last MXG Newsletter SIXTY-NINE was dated Jan 3, 2018.
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 36.09 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 36.09.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest
and is updated with new notes frequently. All Newsletters are online
at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
All MXG changes are also online at http://www.mxg.com, in "Changes".
========================================================================
I. MXG VERSION 36.09 DATED OCT 18, 2018, THRU CHANGE 36.197.
==MAJOR CHANGES ADDED IN MXG 36.09, DATED Oct 18, 2018 THRU 36.197.
ERROR Correction
TYPE42 36.194 Another 42 Subtype 5 LENSR=376 invalid value ABEND.
TYPEXAM 36.195 zVPS MTRSYS Serious Error ABEND, undoc SEGLEN=336.
TYPEPOEX 36.183 Power Exchange USER SMF STOPOVER if File Length zero
TYPE74 36.191 Type 74 Subtype 8 R748Sxxx Sync I/O misaligned.
TYPEXAM 36.181 Support for zVPS/XAM USEDIAG segment (INCOMPAT).
UTILBLDP 36.180 UTILBLDP with RMFINTRV=NO/BUILDPD=YES, no PDB.TYPE70.
TYPE89 36.178 New Target Resource Group TYPE89R2 incomplete/wrong.
READDB2 36.172 READB2(IFCIDS=0-999) failed at highest IFCID 367.
UTILBLDP 36.176 MXG 36.08, Extraneous % with EXPDBOUT= 180 ABEND.
New Products Support
TYPE30 36.188 Support for SMF 30 USERKEY RAX Bit 4 CSA RAXFLAGS.
APAR OA53534 added SMF30_RAXFLAGS, MXG in 35.09
This change decodes each bit.
TYPEIMST 36.192 Support for IMS Version 15 IMS56FA (COMPATIBLE).
ANAL9914 36.171 Support for z/14 Clusters IBM Processor Topology rpt.
TYPERMFV 36.196 Support for new z/OS 2.3 variables (COMPATIBLE)
TYPECMFV 36.173 Support for Mainview MVS History Records new datasets
TYPEZCOS 36.174 Support Auto Soft Capping (ZCOS) Version 4.2 INCOMPAT
UTILEXCL 36.179 Support for USER CICS fields USER3/USER3 and ATOUSER.
Enhancements
TYPETMS5 36.193 Estimated bytes after IDRC added variables.
TYPE84 36.184 JES 2 JMF Subtype 21 INPUT EXCEEDED ABEND.
==MAJOR CHANGES ADDED IN MXG 36.08, DATED SEP 10, 2018 THRU 36.170.
ERROR Correction
TYPE70 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS
RMFINTRV 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS
New Products Support
TYPECIMS 36.167 Support for BMC Energizer for IMS Connect for IMF.
TYPE30 36.150 Support for APAR OA54589, OSPROTECT, TRUSTED.
TYPECIMS 36.162 Support for multiple IMS SYSTEMS, using JFCB DSNAME.
TYPEVMXA 36.155 Support for z/VM LINUX LNXAPPL Process & Summary data
TYPE106 36.152 New SMF 106 variables decoded and formatted.
TYPE42 36.151 New variables from Jul 30, 2018 SMF Manual.
TYPE62 36.151 New variables from Jul 30, 2018 SMF Manual.
Enhancements
ANAL89 36.165 Analysis of SMF 89 data, including MSU from CPU time.
TYPECIMS 36.163 IMS56FA obs for CPI-C had incorrect INPQUETM.
GRAFWLM 36.153 New HIGHTOLOW parm to reverse IMPORTANCE order.
==Major CHANGES added in MXG 36.07, dated Aug 8, 2018 thru 36.149.
New Products Support
TYPERSDA 36.143 Support for RSD Folders Version 6.0 AUDIT (INCOMPAT).
TYPEPOEX 36.135 Support for PowerExchange Version 10.
TYPEWSF 36.132 Support for EOS Version 160 (INCOMPATIBLE).
Enhancements
COMPINTV 36.144 Compare RMF/SMF/CICS/DB2 Interval CPU Time captured.
READDB2 36.140 New SORT102=NO option can suppress T102Snnn sorts.
UTILBLDP 36.139 AUDITAFTER, SUPPRESS=ID, SORTOUT=NO revisions.
RMFINTRV 36.136 MXGABNDRMFI option will ABEND if OTHER Work found.
ERROR Correction
TYPE102 36.138 Dataset T102S018 was misaligned.
TYPERHEL 36.137 Invalid data for variable MICROCODE.
TYPE120 36.134 WebSphere SMF 120 subtypes 5/6 only first was output.
ASUM113 36.133 Variable LPARBUSY was not calculated for z14.
TYPESMF 36.131 MXGREADSMF=LOGGER didn't invoke CICSIFUE exit.
Technical Notes
MXGNOTE 36.141 zHPF Channel Utilization
SASNOTE 36.129 SAS Not 61906 SAS 9.4 TS1M3 High CPU fixed in M4/M5.
==Major CHANGES added in MXG 36.06, dated Jul 9, 2018 thru 36.128.
ABEND Circumvention
TYPE42 36.124 SMF 42 ABEND, more invalid values found, protected.
APAR OA54663 corrects IBM Invalid values.
New Products Support
TYPEBVIR 36.120 Support for BVIR V412 History HSM Compression data.
TYPE119 36.127 Support for ZERT SMF type 119 Subtype 12
ERROR Correction:
READDB2 36.121 READDB2(IFCIDS=ALL) did not create DB2STATS dataset.
==Major CHANGES added in MXG 36.05, dated Jun 13, 2018 thru 36.119.
New Products Support
TYPESRDF 36.112 Support for SRDF Symmetric Remote Data Facility VV.RR
TYPE80A 36.108 Support for RACF TOKENs REQTCRE and ADMINCII'
TYPE102 36.102 Support for DB2 V11 APARS PI71903/PI84045/PI82755.
TYPE101 36.101 Support for NDM-CDI OP record.
Enhancements:
JCLCPORT 36.111 Sample JCL to move WPS datasets to SAS.
TYPENMON 36.109 Significant CPU reduction processing NMON data.
TYPERHEL 36.109 Significant CPU reduction processing RHEL data.
ASUMUOW 36.107 Using ROLLUPS is useless with ASUMUOW, suppress DB2.
ERROR Correction:
ASMRMFV 36.110 SOC7 ABEND reading non-Extended Format VSAM dataset.
TYPEDB2 36.114 DB2ACCTR dataset has been misaligned, NRQLAC GT 1.
TYPEDB2 36.113 Incorrect test for QPAC_PIPE_WAIT/COUNT in DB2ACCTP.
THIS HAS NOT BEEN TESTED WITH DB2 V12 NRQLAC GT 1.
A POSTING TO MXG-L WILL REPORT SUCCESS/PROBLEMS.
TYPE42 36.106 TYPE42DS Encryption variables were not kept.
TYPESYSX 36.105 TYPESYSL renamed to TYPESYSX to avoid conflict.
TYPEACF2 36.100 ACF2 6.2 Change 36.076 didn't correct STOPOVER.
READDB2 36.092 ACCTSORT=NO was not working, data ended up in WORK.
==Major CHANGES added in MXG 36.04, dated May 8, 2018 thru 36.091.
New Products Support
TYPE122A 36.066 Support for IBM Devel z Systems IDZ SMF 122 record.
TYPE119 36.079 Support for SMF 119 subtypes 24, 38, 39, 40, and 45.
TYPEACF2 36.075 ACF2 INVALID SMF RECORD, ACSMFREL=0, should be 6.2.
TYPEIAM 36.071 INPUT STATEMENT EXCEEDED IAM 9.2 Length Changed.
TYPE7072 36.073 Support for z14 ZR1, new SMF70MAXPU variable COMPAT.
Enhancements:
ANALID 36.081 Support for four-digit SMF Record type reporting.
TYPEDCOL 36.086 z/OS 2.3 DCOLLECT Encryption Variables added DCOLDSET
TYPE99 36.072 New EWLM & SERV variables added to TYPE99_6 dataset.
CONFIG 36.067 MXG default CAPSOUT option for z/OS now NOCAPSOUT.
ERROR Correction:
TYPESTC 36.084 Dataset STCVSM11 Change 34.237 variables corrected.
TYPEDB2 36.082 DB2 BPHITRAT corrected.
CONFIG 36.078 OPTION SORTBLKREC corrects DFSORT OC4 in SAS 9.4 M3.
TYPE110 36.077 CICDS Dispatcher Statistics DSGTWT corrected.
TYPEBETA 36.074 Variables BETALOG reversed, subtype 51 doesn't match.
==Major CHANGES added in MXG 36.03, dated Apr 2, 2018 thru 36.064.
New Products Support
TYPEQACS 36.051 AS/400 Ver 7.3, INCOMPAT LRECL, undoc fields.
TYPE74 36.057 z/OS RMF 2.3 Enhancements, APARs, new SMF manual.
TYPEXBM 36.060 Support for BMC Extended Buffer Mgr XBM User SMF
All updates in the Jan, 2018, SMF Manual are included in 36.03.
Enhancements:
TYPE74 36.056 DEVNR5HEX displays 5-hex-nybble zWrite DEVICE NR.
SMFINTRV 36.053 SMF Interval INTBTIME/INTETIME all DATETIME25.6
ERROR Correction:
TYPEVMXA 36.062 VXBYUSR deaccum corrected for new _MT1 variables.
TYPEXAM 36.061 Invalid SYTNLPS value in SYTCUP prevented output.
UTILBLDP 36.059 CHAR OPERAND FOUND if USERADD=ID was requested.
TYPE82 36.055 New TYPE8231 was misaligned, trunc 0203 protected.
BLDSMPDB 36.054 &PDBPATH was not initialized, when MTD requested.
ANALDB2R 36.058 36.02 Only, missing %END corrected.
==Major CHANGES added in MXG 36.02, dated Mar 5, 2018 thru 36.050.
New Products Support
TYPEIMS 36.040 Support for unpopulated IMS 56FA with APAR UI50912.
TYPEXCOM 36.047 Support for XCOM Version 36.02 (COMPATIBLE).
TYPENDM 36.046 Support for NDM-CDI Version 5.2, corrects NDMCPU plus
TYPERHEL 36.043 Initial support for NMON Red Hat Linux RHEL monitor.
TYPE82 36.036 Support for new SMF 82 subtype 82 JOB-Level Crypto.
ERROR Correction:
ASUM70PR 36.041 MXGERROR:MISSING TYPE70 now MXGWARN:MISSING TYPE70.
TYPE119 36.038 "INVALID SMF 119 TYPE 81" corrected, not invalid.
TYPEDB2 36.037 Var QWHSACE missing from DB2STSBP sort, ABEND
ANALCAPD 36.042 ERROR: FOUND "IF" when the CEC= option was used.
TYPE7072 36.035 Incorrect LPAR/ZIP SHAR/SHAC if last engine was IFL.
Enhancements:
MOBWORK 36.045 Enhanced Mobile Work 4 Hour MSU reporting datasets.
TYPEIMS 36.044 Variable IMSVERS, the value in your _IMSVERS is kept.
TYPE70PR 36.039 TYPE70PR variable LPARZIPS, online zips, added.
==Major CHANGES added in MXG 36.01, dated Feb 6, 2018 thru 36.026.
New Products Support
TYPE120 36.022 Support for Liberty 8.9.1.0 SMF 120 ST 100 (COMPAT).
TYPEVMXA 36.025 Support for zVM64 Level 40061701/1702 (INCOMPATIBLE).
36.01 is required for these levels, Broken CR errors.
TYPETPMX 36.024 Support for ThruPutManager Release 18.02 TMT7113.
TYPE70TR 36.003 New 70 Tenant Resource Group TRG updated/validated
TYPE72TR 36.003 New 72 Tenant Resource Group TRG updated/validated
TYPE89 36.003 New 89 Tenant Resource Group TRG updated/validated
UTILBPV 36.007 Program to examine the BPV cylinder value for EAV.
TYPE110 36.008 CICS/TS 5.3 CPU variables in Statistics CICM dataset.
TYPEPOEX 36.002 PowerExchange updated, trashed CPU values, open prob.
ERROR Correction:
TYPE42 36.023 Yet another STOPOVER ABEND, due to Invalid LENSR=232.
TYPE0 36.009 INVALID TYPE 0 LENGTH=70 is valid, wrongly deleted.
ASUM70PR 36.026 MXGERROR: MISSING TYPE 70 RECORDS impact ASUMCEC/LP.
TYPE30 36.012 The created GMTOFF30 could be .01 seconds plus/minus.
PDBAUDIT 36.011 %PDBAUDIT(LIBNAMES="Not All" fails with syntax error.
TYPE73 35.010 TYPE73 dataset, variable CHFXRATE slightly wrong.
TYPE119 36.008 Variable TTAPLDAT in dataset TYP11902 misaligned.
TYPE119 36.018 STOPOVER ABEND: SMF 119 Subtype 81, at IBM now.
TYPE115 36.005 QWHSDURN different in subtype 231, new vars, cleanup.
TYPEDB2 36.004 DB2 V11 IFCID 376 INPUT STATEMENT EXCEEDED. V11 only.
TYPETCP 36.001 TYPETCP (archaic 118) APISTART date was on GMT.
TYPEBETA 36.015 ERROR when TYPEBETA and TYPE70 used together.
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes.
All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M5 (9.4M5), "M5",
or "SAS 9.4 (TS04.01M5P09132017)" if the OPTION VERSIONLONG is
enabled.
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
that will be corrected in SAS Note 61672 defect. See Change 35.309
for more details on using NOERRORSTOP for your own PROC SQLs.
SAS V9.4 M5 is RECOMMENDED, but MXG executes without error
using SAS Version 9.4 M0-M2 or M4-M5 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.
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 DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
or you can continue to use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 36.09 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 3.02 (03.02.03.00.016221) is required Change 34.266.
and other errors with 3.00 or 3.01 have been corrected in the
current WPS version.
WPS Version 3.01.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
THE Z14 CHANGED ONLY THE SMF 113 RECORD INCOMPATIBLY and that
was supported in MXG 35.11, but ASUM113 variable LPARBUSY was
missing until corrected in MXG 36.07. The new SMF70MAXPU variable
was added in MXG 36.04.
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.
However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was
INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to
read the SMT-format RMF records (which are written if you have zIIP
engines AND have enabled the new PROCVIEW CORE option for
Multi-Threading, even if only one thread is enabled).
The new zEDC compression hardware requires MXG 33.07 to support the
new metrics.
For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.
Availability dates for the IBM products and MXG version required for
error-free processing of that product's data records:
Product's
Availability MXG Version
Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8
MVS/ESA 4.2 Mar 29, 1991 9.9
MVS/ESA 4.2.2 Aug 15, 1991 9.9
MVS/ESA 4.3 Mar 23, 1993 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30, 1996 14.05
OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02
OS/390 2.4.0 Sep 28, 1997 15.06
OS/390 2.5.0 Feb 24, 1998 15.06
OS/390 2.6.0 Sep 24, 1998 16.04
OS/390 2.7.0 Mar 26, 1999 16.09
OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
z/OS 1.1 on 2064s Mar 30, 2001 19.01
z/OS 1.1 with correct MSU Mar 30, 2001 19.02
z/OS 1.2 Oct 31, 2001 19.04
z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05
z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.4 Tolerate Sep 27, 2002 20.03
z/OS 1.4 Support Sep 27, 2002 20.06
z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02
z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04
z/OS 1.5 Mar 31, 2004 21.21
z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10
z/OS IRD TYPE70PR Mar 11, 2004 *24.10
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10
z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10
z/OS IFA data in RMF 79s Sep 30, 2005 23.10
z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03
z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06
z/OS More than 32 LPARs Jan 30, 2006 *24.24
z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24
z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02
z/OS IRD errors corrected May 15, 2006 24.03
z/OS ASUMCEC errors corrected May 15, 2006 *24.24
z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24
z/OS zIIP Processor Support Jun 22, 2006 *24.24
z/OS Dedicated zIIP Support Mar 8, 2008 *26.01
z/OS Dedicated zAAP Support Mar 8, 2008 26.01
z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24
z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10
z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10
z/OS new z10 variables Mar 5, 2008 26.01
z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05
z/OS 1.11 Sep 2, 2009 27.08
z/OS 1.11 New 30 variables Apr 14, 2010 *28.02
z/OS 1.12 Aug 17, 2010 *28.05
z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03
z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06
z/OS 1.13 Sep 30, 2011 29.03
z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08
z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01
z/OS 2.1 - Most Records support Jul 23, 2013 30.05
z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07
z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03
z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03
z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10
z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08
z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09
REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09
z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02
z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02
z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07
z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07
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*
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
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
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
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 35.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
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 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 36.09.
1. Incompatibilities introduced in MXG 36.09:
a- Changes in MXG architecture made between 36.09 and prior versions
that can introduce known incompatibilities.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
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 36.09 after MXG 35.36:
Dataset/
Member Change Description
ANAL89 36.165 Analysis of SMF 89 data, including MSU from CPU time.
ANAL9914 36.171 Support for z/14 Clusters in IBM Processor Topology.
ANALCAPD 36.042 ERROR: FOUND "IF" when the CEC= option was used.
ANALID 36.081 Support for four-digit SMF Record type reporting.
ASCIIDSN 36.020 ASCII version of JCLDAYDS with SAS FTP for TMC/DCOL.
ASMRMFV 36.110 SOC7 ABEND reading non-Extended Format VSAM dataset.
ASUM113 36.133 Variable LPARBUSY was not calculated for z14.
ASUM70PR 36.026 MXGERROR: MISSING TYPE 70 RECORDS impact ASUMCEC/LP.
ASUM70PR 36.041 MXGERROR:MISSING TYPE70 now MXGWARN:MISSING TYPE70.
ASUMUOW 36.107 Using ROLLUPS is useless with ASUMUOW, suppress DB2.
CONFIG 36.067 MXG default CAPSOUT option for z/OS now NOCAPSOUT.
CONFIG 36.078 OPTION SORTBLKREC corrects DFSORT OC4 in SAS 9.4 M3.
DOCUMENT 36.013 APAR OA27291 OC4 USEZOSV1R9RULE(NO) z/OS 1.10+
GRAFWLM 36.153 New HIGHTOLOW parm to reverse IMPORTANCE order.
JCLCPORT 36.111 Sample JCL to move WPS datasets to SAS.
MOBWORK 36.045 Enhanced Mobile Work 4 Hour MSU reporting datasets.
MXGNOTE 36.141 zHPF Channel Utilization
PDBAUDIT 36.011 %PDBAUDIT(LIBNAMES="Not All" fails with syntax error.
READDB2 36.092 ACCTSORT=NO was not working, data ended up in WORK.
READDB2 36.121 READDB2(IFCIDS=ALL) did not create DB2STATS dataset.
READDB2 36.140 New SORT102=NO option can suppress T102Snnn sorts.
READDB2 36.172 IFCIDS=0-999 failed, only 367 are defined, now warns.
RMFINTRV 36.136 MXGABNDRMFI option will ABEND if OTHER Work found.
RMFINTRV 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS
SASNOTE 36.129 SAS Not 61906 SAS 9.4 TS1M3 High CPU fixed in M4/M5.
TYPE0 36.009 INVALID TYPE 0 LENGTH=70 is valid, wrongly deleted.
TYPE101 36.101 Support for NDM-CDI OP record.
TYPE102 36.102 Support for DB2 V11 APARS PI71903/PI84045/PI82755.
TYPE102 36.138 Dataset T102S018 was misaligned.
TYPE106 36.152 New SMF 106 variables decoded and formatted.
TYPE110 36.008 CICS/TS 5.3 CPU variables in Statistics CICM dataset.
TYPE110 36.077 CICDS Dispatcher Statistics DSGTWT corrected.
TYPE115 36.005 QWHSDURN different in subtype 231, new vars, cleanup.
TYPE119 36.008 Variable TTAPLDAT in dataset TYP11902 misaligned.
TYPE119 36.018 STOPOVER ABEND: SMF 119 Subtype 81, at IBM now.
TYPE119 36.038 "INVALID SMF 119 TYPE 81" corrected, not invalid.
TYPE119 36.079 Support for SMF 119 subtypes 24, 38, 39, 40, and 45.
TYPE119 36.127 Support for ZERT SMF type 119 Subtype 12
TYPE120 36.022 Support for Liberty 8.9.1.0 SMF 120 ST 100 (COMPAT).
TYPE120 36.134 WebSphere SMF 120 subtypes 5/6 only first was output.
TYPE122A 36.066 Support for IBM Devel z Systems IDZ SMF 122 record.
TYPE30 36.012 The created GMTOFF30 could be .01 seconds plus/minus.
TYPE30 36.150 Support for APAR OA54589, OSPROTECT, TRUSTED.
TYPE42 36.023 Another invalid LENSR=232, STOPOVER ABEND OA54668.
TYPE42 36.106 TYPE42DS Encryption variables were not kept.
TYPE42 36.124 SMF 42 ABEND, more invalid values protected.
TYPE42 36.151 New variables from Jul 30, 2018 SMF Manual.
TYPE62 36.151 New variables from Jul 30, 2018 SMF Manual.
TYPE70 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS
TYPE7072 36.035 Incorrect LPAR/ZIP SHAR/SHAC if last engine was IFL.
TYPE7072 36.073 Support for z14 ZR1, new SMF70MAXPU variable COMPAT.
TYPE70PR 36.039 TYPE70PR variable LPARZIPS, online zips, added.
TYPE70TR 36.003 New 70 Tenant Resource Group TRG updated/validated
TYPE72TR 36.003 New 72 Tenant Resource Group TRG updated/validated
TYPE73 35.010 TYPE73 dataset, variable CHFXRATE slightly wrong.
TYPE80A 36.108 Support for RACF TOKENs REQTCRE and ADMINCII'
TYPE82 36.036 Support for new SMF 82 subtype 82 JOB-Level Crypto.
TYPE89 36.003 New 89 Tenant Resource Group TRG updated/validated
TYPE99 36.072 New EWLM & SERV variables added to TYPE99_6 dataset.
TYPEACF2 36.075 ACF2 INVALID SMF RECORD, ACSMFREL=0, should be 6.2.
TYPEACF2 36.100 ACF2 6.2 Change 36.076 didn't correct STOPOVER.
TYPEBETA 36.015 ERROR when TYPEBETA and TYPE70 used together.
TYPEBETA 36.074 Variables BETALOG reversed, subtype 51 doesn't match.
TYPEBVIR 36.120 Support for BVIR V412 History HSM Compression data.
TYPECIMS 36.162 Support for multiple IMS SYSTEMS, using JFCB DSNAME.
TYPECIMS 36.163 IMS56FA obs for CPI-C had incorrect INPQUETM.
TYPECIMS 36.167 Support for BMC Energizer for IMS Connect for IMF.
TYPEDB2 36.004 DB2 V11 IFCID 376 INPUT STATEMENT EXCEEDED. V11 only.
TYPEDB2 36.037 Var QWHSACE missing from DB2STSBP sort, ABEND
TYPEDB2 36.082 DB2 BPHITRAT corrected.
TYPEDB2 36.113 Incorrect test for QPAC_PIPE_WAIT/COUNT in DB2ACCTP.
TYPEDB2 36.114 DB2ACCTR dataset has been misaligned, NRQLAC GT 1.
TYPEDCOL 36.086 z/OS 2.3 DCOLLECT Encryption Variables added DCOLDSET
TYPEIAM 36.071 INPUT STATEMENT EXCEEDED IAM 9.2 Length Changed.
TYPEIMS 36.040 Support for unpopulated IMS 56FA with APAR UI50912.
TYPEIMS 36.044 Variable IMSVERS, the value in your _IMSVERS is kept.
TYPENDM 36.046 Support for NDM-CDI Version 5.2, corrects NDMCPU plus
TYPENMON 36.109 Significant CPU reduction processing NMON data.
TYPEPOEX 36.002 PowerExchange updated, trashed CPU values, open prob.
TYPEPOEX 36.135 Support for PowerExchange Version 10.
TYPERHEL 36.043 Initial support for NMON Red Hat Linux RHEL monitor.
TYPERHEL 36.109 Significant CPU reduction processing RHEL data.
TYPERHEL 36.137 Invalid data for variable MICROCODE.
TYPERSDA 36.143 Support for RSD Folders Version 6.0 AUDIT (INCOMPAT).
TYPESMF 36.131 MXGREADSMF=LOGGER didn't invoke CICSIFUE exit.
TYPESRDF 36.112 Support for SRDF Symmetric Remote Data Facility VV.RR
TYPESTC 36.084 Dataset STCVSM11 Change 34.237 variables corrected.
TYPESYSX 36.105 TYPESYSL renamed to TYPESYSX to avoid conflict.
TYPETAND 36.118 Support for Tandem TMF Transaction DATA, TANDTMF.
TYPETCP 36.001 TYPETCP (archaic 118) APISTART date was on GMT.
TYPETPMX 36.024 Support for ThruPutManager Release 18.02 TMT7113.
TYPEVMXA 36.025 Support for zVM64 Level 40061702 (INCOMPATIBLE).
TYPEVMXA 36.155 Support for z/VM LINUX LNXAPPL Process & Summary data
TYPEWSF 36.132 Support for EOS Version 160 (INCOMPATIBLE).
TYPEXCOM 36.047 Support for XCOM Version 36.02 (COMPATIBLE).
UTILBLDP 36.139 AUDITAFTER, SUPPRESS=ID, SORTOUT=NO revisions.
UTILBLDP 36.176 MXG 36.08, Extraneous % with EXPDBOUT= 180 ABEND.
UTILBPV 36.007 Program to examine the BPV cylinder value for EAV.
VMAC30 36.175 Support for SMF 30 User Key CSA RAXFLAGS OA53434.
VMACCMFV 36.173 Support for Mainview MVS History Records new datasets
VMACZCOS 36.174 Support for AutoSoftCapping ZCOS Version 4.2 INCOMPAT
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at http://www.mxg.com.
Inverse chronological list of all Changes:
NEXTCHANGE
====== CHANGES THRU 36.197 ARE IN MXG 36.09 DATED Oct 18, 2018==========
Change 36.197 Reserved Change Number.
Change 36.196 Support for new z/OS 2.3 RMF III variables (COMPATIBLE)
VMACRMFV added to ZRBASI/ZRBRCDD/ZRBRCDP/ZRBRCDS/ZRBRCDT/ZRBRCDX
Oct 15, 2018 and ZRBSVPC. The new variables are listed in DOCVER36.
-ZRBASI, existing variables now correctly populated:
ZRBDCTIA/ZRBGMN/ZRBGMX/ZRBIDLE/ZRBWNM/ZRBGDE/ZRBDNM.
Change 36.195 zVPS MTRSYS segment with undocumented SEGLEN=336 caused
VMACXAM Serious Error messages and missing output data.
Oct 15, 2018
Thanks to Patricia Hansen, ADP, USA.
Change 36.194 Yet another invalid LENSR value TYPE42 Subtype 5 ABEND,
VMAC42 value LENSR=376 added to Change 36.124.
Oct 15, 2018
Change 36.193 Estimated bytes after IDRC compression added to TMS as
TYPETMS5 TAPEBYTC and to DSNBRECD as DSNBYTEC. Just like the
Oct 11, 2018 TAPEBYTE and DSNBYTE variables (estimates based on
BLKSIZE*BLKCNT) these are best guess estimates.
Change 36.192 Support for IMS Version 15 (COMPATIBLE) dataset IMS56FA.
VMACIMS New string TPCPTHRSESSN contains the pair of TPCPTHRS and
Oct 11, 2018 TPCPESSN for up to six External Subsystems, TPCXLEN has
the length of the TPCX, still 60 reserved bytes.
Thanks to Robert Taylor, Wisconsin Dept of Administration, USA.
Change 36.191 New Type 74 Subtype 8 dataset TYPE748S SYNC I/O variables
VMAC74 R748SCWT R748SNBW R748SNWO R748SNWS R748SNWT were INPUT
Oct 11, 2018 and FORMATted and LENGTHed and LABELed incorrectly.
Thanks to Steve Olenik, IBM, USA.
Change 36.190 A reference line showing the memory allocated to each
GRAFWRKX LPAR was added to the memory graph. The scale on the Y
Oct 11, 2018 axis is 0 to the MAX memory for any LPAR in the data.
Change 36.189 Variable SM113CPT added to the SMF 113 report to show
ANAL113 the engine type.
Oct 9, 2018
Thanks to Jim Horne, Lowes, USA.
Change 36.188 Support for new Bit 4 of SMF30_RAXFLAGS and creation of
BUILD005 these new bit-level variables with explanation in label
BUIL3005 SMF30_RAXFLAG0='RAX0*USERKEY*COMMON*AUDIT*ENABLED?'
VMAC30 SMF30_RAXFLAG1='RAX1*USERKEY*COMON*AUDIT*USAGE?'
Oct 16, 2018 SMF30_RAXFLAG2='RAX2*USERKEY*CADS*USAGE?'
SMF30_RAXFLAG3='RAX3*USERKEY*CHANGE*KEY*USAGE?'
SMF30_RAXFLAG4='RAX4*USERKEY*RUCSA*USAGE?'
that are added to TYPE30_4/TYPE30_5/TYPE30_6/TYPE30_V
and PDB.STEPS for BUILDPDB (JES2) and BUILDPD3 (JES3).
(Variable RAXFLAGS was added in MXG 35.09.)
Thanks to MP Welch, Bank of America, USA.
Change 36.187 WPS does not honor OPTIONS NOXWAIT so there may be times
BLDSMPDB when it is necessary to respond to a message.
PROCSRCE
UTILCPLG
VMXGALOC
Oct 5, 2018
Change 36.186 Labels for variables RECORDS, INSERTS, RETRVALS, UPDATES
VMAC16 and DELETES are now consistent for these three records.
VMAC64
VMACSYNC
Oct 4, 2018
Thanks to Warren Cravey, FMR, USA.
Change 36.185 For want of an & PDB= was not honored but always looked
GRAFCIMP for the data in PDB.
Oct 4, 2018
Change 36.184 JES 2 JMF subtype 21 INPUT RECORD EXCEEDED LENGTH because
VMAC84 triplets were misaligned and this was the first instance
Oct 3, 2018 of that subtype to test.
Oct 11, 2018 -Value of JMFINTRV is 60+ hours, JMFDELTA is 90 minutes,
so the two percentage calculations use JMFDELTA.
Thanks to Jim Horne, Lowes, USA.
Thanks to Joe Faska, DTCC, USA.
Change 36.183 -Power Exchange USER SMF record STOPOVER if the File Name
VMACPOEX had zero length. Invalid record detected and printed on
Oct 3, 2018 log and skipped, while vendor investigates.
Oct 18, 2018 -Invalid new triplet record with no SECT segment deleted,
and a record with truncated General Section is deleted.
-The GMT offset depends on POEXENDT; if it's missign the
offset can't be calculated. Pending a vendor correction,
MXG Retains the GMTOFFEX and uses that value instead,
which could cause missint values for STRT/ENDT.
Thanks to Scott Wiig, US Bank, USA.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.182 MXG 36.07-36.08. Possible syntax error in a SYSFUNC due
MONTHBLD to Change 36.145, which changed a QCMPRES to a SYSFUNC
MONTHBL3 (changed only to protect possible user typing errors)
MONTHBL3 but should have used QSYSFUNC, because SYSFUNC saw the
MONTHDSK commas as operands and failed. The member from 36.06 all
MONTHASC the way to 32.05 can be used. Fortunately, MONTHBLD is
PRODTEST normally tailored into the "USERID.SOURCLIB" so the ERROR
PRODTESW only impacts new users of the MONTHPDB in 36.07-36.08.
Oct 3, 2018
Change 36.181 Support for zVPS USEDIAG segment adds variables DIAGNBR
VMACXAM and DIAGVALUE to datasets XMUSVCPU and XAMUSR.
Oct 2, 2018
Thanks to Patricia Hansen, ADP, USA.
Change 36.180 -UTILBLDP with RMFINTRV=NO and BUILDPDB=YES did not create
UTILBLDP PDB.TYPE70 nor the other PDB.TYPE7x datasets. The "NO"
Oct 4, 2018 should have suppressed only the %INCLUDE of RMFINTRV in
MACRO _INTRMF, but it also suppressed the seven _S7xxxxx
data set sort macros. RMFINTRV=YES is automatic with
BUILDPDB=YES, and now RMFINTRV=NO and BUILDPDB=YES will
create the 70s but not create PDB.RMFINTRV. If you want
to build PDB.RMFINTRV and the ASUM70PR datasets from only
the 70 and 72 SMF records, see EXAMPLE 3A/3B in UTILBLDP.
Thanks to Ralph Gifford, AIG, USA.
Change 36.179 Support for USER CICS fields USER3/USER3 and ATOUSER.
IMACAAAA
IMACICWZ
IMACICXA
VMAC110
UTILEXCL
Sep 28, 2018
Thanks to Richard Baker, ATO, AUSTRALIA.
Change 36.178 Target Resource Group dataset TYPE89R2 was incomplete and
VMAC89 fields were misaligned.
Sep 28, 2018
Thanks to Greg Goshia, Ohio Farmers Insurance, USA.
Change 36.177 Reserved Change Number.
Change 36.176 Extraneous % in UTILBLDP could cause 180 ERROR and ABEND.
UTILBLDP Line 665 had a stray percent sign, MXG 36.08 only.
Sep 20, 2018 The EXPDBOUT= argument exposes the error.
Thanks to Tom MacCabe, Dominion Energy, USA
Change 36.175 Support for SMF 30 User Key CSA Audit Enhancements adds
VMAC30 new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and
Sep 28, 2018 the TYPE30_5 datasets. Change 35.212 (MXG 35.09+) Sep
Feb 28, 2018 2017 made the code change but the change text was still
Sep 20, 2018 a "Reserved Change" until Feb 28, 2018, but had the old
35.212 Change Number, so it was only in CHANGESS member.
The IBM Record Change was made by APAR OA53355, but will
only be needed thru z/OS 2.3, as User Key Common Storage
usage support ends there.
This is Health Check ZOSMIGV22R3_NEXT_VSM_USERKEYCOMM.
These APARs required no additional code changes:
OA53434 Corrects ASM DSECT Lengths, no MXG impact
OA53289 Corrects value of SMF30HVR from zero to valid.
OA45767 APAR that added the extra triplet caused OA53434
See Change 36.188 which added new bit-level variables.
Change 36.174 Support for Auto Soft Capping (ZCOS) Version 4.2 added
VMACZCOS these variables, INCOMPATIBLY, due to a new field that
Sep 21, 2018 was inserted prior to a triplet.
Dataset ZCOS01:
ZCOS01PC4HA='TOTAL*CATEGORYA*R4H OF LPARS'
ZCOS01PC4HB='TOTAL*CATEGORYB*R4H OF LPARS'
ZCOS01PC4HM='TOTAL*MOBILE*R4H OF LPARS'
ZCOSDETO='SMF*INTERVAL*END*TIME'
ZCOSDDTO='SMF*INTERVAL*DURATION'
ZCOSDOTO='GMT*OFFSET'
Dataset ZCOS02:
ZCOSPR4HA='4H CATEGORYA MSU AVERAGE'
ZCOSPR4HB='4H CATEGORYB MSU AVERAGE'
ZCOSPR4HM='4H MOBILE MSU AVERAGE'
ZCOSPS4H ='4H TOTAL MSU AVERAGE AT SMF IV TIME'
ZCOSPS4HA='4H CATEGORYA MSU AVERAGE AT SMF IV TIME'
ZCOSPS4HB='4H CATEGORYB MSU AVERAGE AT SMF IV TIME'
ZCOSPS4HM='4H MOBILE MSU AVERAGE AT SMF IV TIME'
ZCOSPSTIM='ZCOSPSTIM*DATETIME*STAMP'
Dataset ZCOS04GP:
ZCOSMOBT='MOBILE*TARGET*R/S/D'
ZCOSCMPR='MANAGE*BILLING*CPM?'
ZCOSCMPF='CMP*FLYING*MSU MGT?'
Dataset ZCOS04CP:
ZCOS04CTHR='CPC*CONTROL*THRESHOLD'
Dataset ZCOS04LP:
ZCOS04PDLV='MSU*DISTRIB*LEVEL*BOUNDARY'
Change 36.173 -Support for Mainview MVS History Records. The new BMC
EXCMFV02 MD73 utility creates these 28 new RTIN records, which
EXCMFV09 create these 28 new datasets with CMRDETL information.
EXCMFV0C
EXCMFV0D
EXCMFV0F DDDDDD Dataset Description
EXCMFV10 Tested Block
EXCMFV16 CMFV02 CMFV02 JOB STEP 02 JSRE
EXCMFV17 CMFV09 CMFV09 HSM Delay 09 HSRE
EXCMFV18 CMFV0C CMFV0C Wait Use 0C CRRE
EXCMFV21 CMFV0D CMFV0D Crypto Hardware 0D CRRE
EXCMFV2E CMFV0F CMFV0F Crypto ICSF 0F CIRE
EXCMFV34 CMFV10 CMFV10 Address Space 10 ADRE
EXCMFV47 CMFV16 CMFV16 Lock 16 LKRE
EXCMFV48 CMFV17 CMFV17 VSAN RLS Activity 17 RLRE
EXCMFV49 CMFV18 CMFV18 VSAM RLS LRU 18 RURE
EXCMFV50 CMFV21 CMFV21 System Summary 21 SLRE
EXCMFV51 CMFV2E CMFV2E Data Set 23 DSRE
EXCMFV52 CMFV34 CMFV34 Unix Process 34 UPRE
EXCMFV54 CMFV47 CMFV47 WLM Extended Period 47 MXRE
EXCMFV70 CMFV48 CMFV48 WLM Addr Space/Enclave 48 MTRE
EXCMFV71 CMFV49 CMFV49 WLM Enclave Classify 49 MCRE
EXCMFV72 CMFV50 CMFV50 XCF Path 50 XPRE
EXCMFV73 CMFV51 CMFV51 XCF System 51 XSRE
EXCMFV74 CMFV52 CMFV52 XCF Source/Destination 52 XDRE
EXCMFV80 CMFV54 CMFV54 WLM Server 54 MWRE
EXCMFV81 CMFV70 CMFV70 System Summary 70 SBRE
EXCMFV82 CMFV71 CMFV71 Device 71 DBRE
EXCMFVFD CMFV72 CMFV72 Address Space 72 ABRE
EXCMFW18 CMFV73 CMFV73 WLM 73 WBRE
IHDRCMFV CMFV74 CMFV74 LPAR 74 LBRE
VMACCMFV CMFV80 CMFV80 ZFS Aggregate 80 ZSRE
VMXGINIT CMFV81 CMFV81 ZFS Cache 81 ZCRE
Oct 17, 2018 CMFV82 CMFV82 PCIE Activity 82 PCRE
CMFVFD CMFVFD SCM 83 FDRE
CMFW18 CMFV181 DEVICE 18-1 DLRE
-The three files contain these RTIN values:
SHRT only contains 70x 71x 72x 73x 74x
LONG only contains 0Cx 10x 18x 21x
NORM contains all except 0Cx 10 11 12 13 14 15
and contains C0 C1 C2 C4 CC CD CE CF D0 D1 D2 D3 D4
that are not documented.
-RTIN 18 appears both in LONG (1) and NORM (0), so the
CMFV18 and CMFW18 DDDDDDs create CMFV18 and CMFV181.
-These RTINs were supported, no longer documented:
25 26 27 28 29 33 41 42 43 45 53 96 97
-These RTINs are not yet supported, await DSECTs:
11 12 13 15 1E 2A 2B 2C 2D
-Truncated RTIN '47'x with ENTL=1204 vs 1536 protected.
Change 36.172 READDB2(IFCIDS=0-999) failed when it got past IFCID 367,
READDB2 the current high IFCID. That syntax requires contiguous
Sep 13, 2018 values, so if you specify a value GT 367 the upper limit
is reset to 367 and a note is printed on the log. If you
really want to create ALL of the IFCIDS use IFCIDS=ALL.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.171 Support for z/14 Clusters added to IBM Processor Topology
ANAL9914 Report.
Sep 13, 2018
Thanks to Raymond J. Smith, OPTUM, USA.
====== CHANGES THRU 36.170 ARE IN MXG 36.08 DATED SEP 10, 2018==========
Change 36.170 For sites with 8-byte values for SMF70STN or SYSNAME or
SAGANAL with 4-byte values that don't match SYSTEM, or MXGWARNs
Sep 9, 2018 about TYPE70 or TYPE70PR data missing, you will need to
use the output of this PROC FREQ report
PROC FREQ DATA=PDB.TYPE70PR (WHERE=(SMF70STN=SYSNAME));
TABLES SYSNAME*SMF70STN/NOROW NOCOL NOCUM NOPCT;
to update the new SELSTN macro variable to set the SYSTEM
from the corresponding SMF70STN value:
%LET SELSTN=
%QUOTE(
IF STN(_I_) EQ 'DHECPROD' THEN STN(_I_)='DHEC';
ELSE IF STN(_I_) EQ 'DHECTEST' THEN STN(_I_)='DHCT';
ELSE IF STN(_I_) EQ 'PROD' THEN STN(_I_)='SYS1';
ELSE IF STN(_I_) EQ 'TEST' THEN STN(_I_)='SYST';
ELSE PUTLOG _N_= _I_= STN(_I_)= SYSTEM=;
);
Thanks to Henry Jenkins, South Carolina State Government, USA.
Change 36.169 Change 36.077 checked for the word BY in the first 2
VMXGSUM bytes of INCODE but there is no reason the BY would have
Sep 8, 2018 to be in the first two bytes, so logic was revised to
find any " BY " text in the INCODE. If the first text
in the INCODE= was a %INCLUDE, it failed because the
percent sign needed to be protected with %SUPERQ().
Change 36.168 Dataset BVIR20 variables MAX/AVE AHCT/BHCT were incorrect
VMACBVIR as the +46 after DEVINTDL is their input location and
Sep 8, 2018 removed.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.167 Support for BMC Energizer for IMS Connect which populates
VMACCIMS TRNOTxxx variables in CIMSTRAN dataset, but TRNOTCON was
Sep 7, 2018 not converted to local, and new CONNECT*SERVICE*DURATION
in new CONNECTM variable.
Thanks to Randy Hewitt, DXC, USA.
CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33+ TOTAL ENGINES.
NO IMPACT TO PDB.TYPE70PR,ASUMCELP/ASUMCEC/ASUM70PR/ASUM70LP.
Change 36.166 Dataset PDB.TYPE70 skips LCPUADDR/CPUID 64 and higher and
VMAC7072 does NOT include any of those engine's CPU time, UP time,
Sep 9, 2018 nor NRCPUS count, causing CPUACTTM for CPs to be less
than the CPUTM in TYPE72GO Service Classes, which causes
log messages NEGATIVE UNCAPTURED CPU TIME in RMFINTRV.
-This error can occur with as few as 33 total engines; as
in this case, with 13 CPs and 19 zIIPs, IBM skipped every
other LCPUADDR so the last ZIP was '3F'x, and when a 14th
CP was added, it became '40'X and exposed the MXG error.
-ONLY PDB.TYPE70/PDB.RMFINTRV are impacted; PDB.TYPE70PR
and PDB.ASUMCELP/ASUMCEC/ASUM70PR/ASUM70LP datasets that
are created from TYPE70PR capture all engines' data.
-This MXG error was introduced in 2013 in 31.04 support
for 255 engines; previously separate variables for every
engine, 0 thru 63 were created and kept; but new dataset
TYPE70EN was created with all engines details so new vars
were not needed to be kept, but they were still created
for the summary into TYPE70, but the old logic to update
the IFATYPE array still stopped at engine 63.
You can use this program to read your PDB.TYPE70PR data
to see if you are exposed, and the CPU TIME lost, if any:
DATA CPUMISSED;
SET PDB.TYPE70PR;
IF LCPUPDTM GT 0 AND SMF70CIN IN ('CP' 'IIP');
KEEP SMF70CIN SYSTEM LCPUPDTM RANGE;
IF LCPUADDR LT 64 THEN RANGE='INCLUDED-LT 64 ';
IF LCPUADDR GE 64 THEN RANGE='NOT INCLUDED-GT 64';
PROC FREQ;
TABLES SMF70CIN*RANGE*SYSTEM/NOCOL NOCUM NOROW;
WEIGHT LCPUPDTM;
TITLE LOST/INCLUDED PDB.TYPE70 CPU TIMES HIGH LCPUADDR;
to see how much CPU was included or lost in PDB.TYPE70.
-Normally, CPs LCPUADDR start at zero, followed by zips,
so the impact is more likely for zip metrics, but when
CPs are added dynamically, they get the next LCPUADDR.
Only PDB.TYPE70 and PDB.RMFINTRV datasets are impacted.
and only resources summed from individual engines; the
4HR Average MSU SMF70LAC and similar "interval variables"
are not impacted by this error.
Neither the PDB.TYPE70PR nor the four ASUM70PR datasets
PDB.ASUMCELP,ASUMCEC,ASUM70PR,ASUM70LP are impacted.
Thanks to Jim Horne, Lowes, USA.
Change 36.165 Analysis of SMF 89 data, including conversion of CPU time
ANAL89 into MSU values, with several reports.
Sep 10, 2018
Thanks to Edward Cornish, Verisk, USA.
Change 36.164 Variable SMF82KVL is added to TYPE8207 with number of
VMAC82 nibbles in SMF82KV field. ICN 1652.
Aug 30, 2018
Change 36.163 IMS56FA observations for CPI-C PROGTYPHX='10'X do not
VMACIMS have an ARRVTIME so their INPQUETM can't be known, but
Sep 7, 2018 MXG incorrectly calculated wrong values. Now INPQUETM
is missing when ARRVTIME is unknown.
Change 36.162 Variable SYSTEM does not exist in IMS Log Records but MXG
IHDRIMS can set it from SYSPARM() on the // EXEC JCL statement,
VMACIMS but that applies to the entire IMS log that was read.
VMXGINIT Now, to process multiple IMS system's logs in one job,
Aug 28, 2018 JFCB=IMSJFCB is added so the DSNAME in the first 44 bytes
can be used in tailoring member IHDRIMS or instream use
%LET MACIMSH= in your SYSIN to set the variable SYSTEM.
For example, if the second node in your DSNAME is SYSTEM,
%LET MACIMSH= %QUOTE( SYSTEM=SCAN(IMSJFCB,2,'.'); );
will populate variable SYSTEM with that value.
-Variable PROGTYPE='C' is now set for PROGTYHX='10'X.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.161 If OUT70GL=WORK.xxxxxxxx, ASUM70PR program failed with
VMXG70PR DATASET PDB.ASUM70GL NOT FOUND because the _LSU70GL
Aug 28, 2018 token instead of macro variable &OUT70GL was used.
Thanks to Jutta Gleixner-Schmid, Allianz, GERMANY.
Change 36.160 MXG 36.07 only. Debugging PUTLOG statements that filled
VMACCIMS the log were disabled.
Aug 27, 2018
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 36.159 DB2STAT2 field QDBPFRAM, Frame Size, in SMF is $EBCDIC2
VMACDB2 with text values of 4K, 1M, 2G, but MXG input QDBPFRAM
Aug 27, 2018 as PIB2 numeric causing wrong values (62151 for 2G).
New QDBPFRAMCH character variable has the 4K/1M/2G text,
and QDBPFRAM remains numeric now with the correct bytes
(for calculations), printing 4K, 1024K, 2048M with the
MGBYTES format.
Thanks to Lori A. Masulis, FMR, USA
Change 36.158 Support for APARs OA55574/OA55609/OA55610 adds new
VMACDCOL variables in dataset TYPEDSET:
Aug 25, 2018 DCDCMPTV='COMPRESSION*TYPE*VALID'?
DCDCTYPE='COMPRESSION*TYPE'
although MXG variable DCDCMTYP already contains the
compression type, decoded from DCDEXFLG. ICN 1650.
Change 36.157 -Variable FCVSWTTM in CICSTRAN was incorrect, containing
VMAC110 the same value in FCXCWTTM.
Aug 26, 2018 -Variable SMFPSSPN, the Specific APPLID is now kept in the
CICSTRAN dataset.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.156 While these ODS members do work within the limitations of
VMXGODSO their programming, ODS is evolving so quickly and there
VMXGODSC are so many permutations and combinations that they are
TECHNOTE no longer a practical answer for most applications.
Aug 23, 2018 Some MXG GRAFxxxx and ANAL members have ODS parameters,
but you may find it preferable to wrap many reports in a
single ODS package. For example, to run GRAFWRKX+GRAFCEC
and send the results to a single ODS PDF file, use:
ODS LISTING CLOSE; /* always needed on zOS */
OPTIONS ORIENTATION=LANDSCAPE;
ODS GRAPHICS/ WIDTH=10IN HEIGHT=7.5IN;
ODS PDF FILE='D:/MYPDF.PDF' STYLE=MXGSTYLE1;
%GRAFWRKX;
%GRAFCEC;
RUN;
ODS PDF CLOSE;
RUN;
-MXGSTYLE1 was used here because the default style used by
ODS results in bars of solid colors so close together it
can be difficult to tell one bit of the bar from another.
MXGSYLE1 uses brighter colors and patterns to make it
simpler to tell who is on first. MXGSTYLE1 is created
and stored in the FORMATS library by the FORMATS member.
STYLE is just one of many ODS options you may wish to
use which is what makes VMXGODSO/VMXGODSC obsolete.
CHANGE 36.155 Support for Z/VM LINUX LNXAPPL Process & summary APL data
EOAPLLXP creates these new datasets:
EXAPLLXF dddddd dataset description
EXAPLLXP APLLXF VXAPLLXF LNXAPPL FILE SYSTEM DATA
EXAPLLXS APLLXS VXAPLLXS LNXAPPL SUMMARY DATA
IMACVMXA APLLXP VXAPLLXP LNXAPPL PROCESS DATA
VMACVMXA -The VXAPLLXP process dataset only outputs a process that
VMXGINIT had non-zero TOTAL_TIME or CTOTAL_TIME; if you want all
Aug 25, 2018 process records to be output, edit member EOAPLLXP into
Sep 13, 2018 your tailoring library and remove the conditional test.
-SAMPTIME and UPTIME are not valid values, investigating.
-Crypto Type 12:CEX6C is now recognized and output in the
VXPRCAPM dataset.
-Dataset VXPRCMFC is now populated for z14, CSVN=5.
-Sep 13: RESID corrected to RESIDENT, comments deleted.
Thanks to Graham Harris, RBS, ENGLAND.
Change 36.154 Support for CMODHEAD=NRXENTRY CMODNAME=NRXDATA optional
IMACAAAA CICS SMF 110 CICSTRAN segment and new NRXENTRY variable.
IMACICWY
UTILEXCL
VMAC110
Aug 18, 2018
Change 36.153 New parameter added that can be used to reverse the
GRAFWLM order of data on the charts produced. GRAFWLM has
GRAFWRKX always produced bar charts with the most important
Aug 24, 2018 work at the top and the least important (discretionary)
at the bottom. Now this parameter HIGHTOLOW (default
is YES, original order) if set to NO reverses the order.
-Old default YES has UNCAPTURED at top and DISCRETIONALY
at bottom, NO reverses that order.
-Some ODS logic was corrected - changed from NE to EQ.
-Some statements reordered for logical ordering
Preceding changes were only in GRAFWLM.
-Only in GRAFWRKX, the default values for width and height
were reduced to 7.5 and 10 inches to eliminate warning
messages that the values were too large.
Thanks to Daniel McKinzie, Zions Bank, USA.
Change 36.152 -New Formats created to decode SMF 106 variables
FORMATS SMF6ACTP MG106CT. SMF6ACTY MG106CD. SMF6ATYP MG106SE.
VMAC106 -TYPE1061 dataset SMF6ASET has character and numeric value
Aug 17, 2018 that are not documented; MXG creates multiple SMF6ASETxx.
-TYPE1062 dataset SMFCMDPM contains two binary fields that
are decoded in SMF6A001/002 variables but seem too large
to be look up tables for parameters.
Thanks to Joe Faska, DTCC, USA.
Change 36.151 Updates from SMF Manual Jul 30, 2018.
FORMATS -Format MG022ET adds values
VMAC42 5='5:COUPLING FACILITY CONTROL UNIT'
VMAC62 6='6:LOGICAL PARTITION ENTRY'
Aug 12, 2018 9='9:PCIE FUNCTION'
-Variables added to TYPE42SR dataset:
S42SCRRU='AVG*RANDREAD*CACHEHIT*RESPTM'
S42SCRSU='AVG*RANDREAD*CACHEHIT*SERVICTM'
-Variables added to TYPE62 dataset:
SMF62IND_2='CATALOG*OR CRA*RECORD?'
SMF62IND_3='VVDS*OR*ICF*RECORD?'
SMF62IND_4='SMS*CLASS*INFO*INCLUDED?'
SMF62IND_5='DATASET*IS*ENCRYPTED?'
Change 36.150 Support for APAR OA54589, OSPROTECT/TRUSTED/NOTRUSTED
BUILD005 adds these new variables to TYPE30_4 and PDB.STEPS:
BUIL3005 SMF30CAS_OA54589_0='SMF30CAS*OA54589*BYTE 0'
VMAC30 SMF30CAS_OA54589_1='SMF30CAS*OA54589*BYTE 1'
Aug 12, 2018 SMF30CAS_OA54589_2='SMF30CAS*OA54589*BYTE 2'
Aug 27, 2018 SMF30CAS_OA54589_3='SMF30CAS*OA54589*BYTE 3'
These variables are created from the bit tests for the
preceding Byte variables listed in the SMF Manual:
SMF30CAS_OSPROTECT='OSPROTECT';
SMF30CAS_UNTRUSTED='UNTRUSTED?'
SMF30CAS_TRUSTED='TRUSTED?'
====== Changes thru 36.149 are in MXG 36.07 dated Aug 8, 2018==========
Change 36.149 One site's IMF data has TRNETIME/TRNSTCKE two hours early
VMACCIMS (STRTTIME,ENDTIME) but TRNCVTTZ (GMT Offset) is zero and
VMXGINIT the site has not responded with their local/GMT times, so
Aug 8, 2018 this may be a temporary circumvention, but macro variable
IMFGMTOFF is created with value of zero and when it was
set &LET IMFGMTOFF=7200; before the %INCLUDE, the times
were correct. This change text will be updated when it
is known why these times, previously always the same time
zone as the ARRVTIME, are now different at this site.
Change 36.148 The combination of a PROC DATASETS with no MT= option and
ANALRMFR with a DELETE statement with a wildcard S: caused QA job
Aug 8, 2018 to fail with WPS because it honored the MT=ALL default to
delete both datasets starting with S, but unexpectedly
also deleted the SASMACR CATALOG dataset, which caused QA
to subsequently fail. But SAS only deleted datasets so QA
did not fail. Since the actual intent was to only delete
datasets, adding MT=DATA to the PROC DATASETS corrected
for both SAS and WPS. However, using MT=ALL with SAS
still only deleted datasets, printing this note:
WORK.SASMACR cannot be deleted because it's in use.
Change 36.147 Support for APAR OA52810 Data Set Encryption in DCOLMIGS
FORMATS dataset, adds new variables:
VMACDCOL
Aug 8, 2018
Thanks to Luc Gielis, KBC, BELGIUM
Change 36.146 -If you are not running MRO or you do not see a reduction
ASUMUOW in the OBS count between CICSTRAN and ASUMUOW on the
MXG NOTE order of 2:1 or better, it may indicate that the use of
Aug 7, 2018 MRO is not significant and it may be that running ASUMUOW
is a waste of resources. ASUMUOW has to sort all of the
CICSTRAN and DB2ACCT and MQ records to be able to merge
everything together and can be very resource intensive.
-If you have DB2 ROLLUPS that data becomes very suspicious
since one DB2 record can represent many transactions and
it is best in that case to not use ASUMUOW with DB2 data
as documented in change 36.107.
-If you find that running ASUMUOW is expensive or that you
are not achieving any serious reduction in OBS in ASUMUOW
dataset using ASUMUOW compared to the OBS in CICSTRAN,
then don't run ASUMUOW: instead, use ASUMCICS to create
the PDB.CICS dataset.
-All of the DB2 CPU time is captured in the CICS records;
only the class 3 wait times/counts are lost, but those
are primarily deep diagnostics, where it may be much
better to run ANALDB2R against the PDB.DB2ACCT dataset
selecting the desired transaction.
Change 36.145 QCMPRES is an AUTOCALL macro and we try to avoid using
ANALDB2R them since they have caused issues in the past. This
MONTHASC change replaces QCMPRES by a %SYFUNC(COMPBL) call to
MONTHBLD compress blanks for safety.
MONTHBL3
MONTHDSK
PRODTEST
PRODTESW
Aug 7, 2018
Change 36.144 -Compare Interval CPU time Captured RMF/SMF/CICS/DB2 with
COMPINTV totals and plots of each system. The ancient program was
Aug 8, 2018 restructured as a macro that can either read SMF data or
extract the data from an existing PDB. Parameters allow
you to limit the scope of the data being analyzed. The
output is a combination of PROC MEANS, TABULATEs, and
SGPLOTs and will show you capture ratios for RMF and SMF
for both CPUs and ZIPs as well as the CPU times from
RMF, SMF, CICS, and DB2.
-See the member for documentation on parameters and
usage.
-Some examples of usage
Read SMF and create reports on half hour intervals
%compintv(compinterval=halfhour);
-Get data from pdb and report on half hour intervals
%compintv(compinterval=halfhour,readsmf=no);
Change 36.143 Support for RSD Folders Version 6.0 Audit Records with
FORMATS INCOMPATIBLE updates. Only version 6.0 is supported, and
VMACRSDA one inconsistent record format is under investigation
Aug 5, 2018 and is not output.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.142 The MXGKEEP= default was incorrectly changed to NO in
VMXGINIT MXG 36.04, but the default MXGKEEP=NO is restored, as
Aug 5, 2018 YES can cause errors if there are INCODE variables.
Change 36.141 zHPF Channel Utilization
MXG Note zHPF was introduced by IBM to reduce channel utilization
Jul 31, 2018 and to improve data transfer performance. At the core,
the difference between zHPF enabled and traditional
FICON channels is the schema employed to transmit
channel programs and data. For traditional CCWs, a
channel program (comprised of multiple CCWs) is
transmitted from the channel to the subsystem in very
small chunks, CCWs and data blocks. Each turn around
increases channel utilization and as the utilization
increases, the acknowledgement coming back from the
subsystem experience delays like Volkswagens driving in
a sea of semis.
What zHPF does is it packs the CCWs and data blocks into
Transmission Control Words, i.e., TCWs. By reducing the
number of turnarounds required to transmit CCWs and data
blocks, the portion of channel utilization resulting
from the turnarounds is reduced. Moreover, by reducing
the number of turnarounds required for data transfer,
the effective data transfer rate is increased.
Finally, your mileage may vary. If your I/O stream
primarily supports VSAM or DB2 datasets, you will see a
lot of difference. If you have a large fraction of
traditional access methods, your level of benefits may
be reduced.
The TYPE73 Channel Busy is the primary indicator of the
benefit of zHPF.
Thanks to Dr. H. Pat Artis, Performance Associates, USA.
Change 36.140 New READDB2 parameter SORT102 with SORT102=YES default
READDB2 can be changed to SORT102=NO to suppress the sorting of
Jul 27, 2018 T102Sxxx trace datasets and to suppress VFMT102 execution
that creates $MGDB2DB and $MGDB2OB formats when 105/107
IFCIDS are selected. They are used by ANALDB2R to match
DBID/OBID in trace datasets.
Thanks to Laifai Wong, Bank of America, USA.
Change 36.139 UTILBLDP enhancements and corrections.
UTILBLDP -If you asked for DB2 trace records and specified
Aug 7, 2018 SORTOUT=NO the T102xxxx datasets were still sorted.
-New parameter AUDITAFTER added with a default of NO.
With BUILDPDB=NO, PDBAUDIT is not executed by UTILBLDP.
With BUILDPDB=YES and AUDITAFTER=NO, there is no change:
PDBAUDIT is executed after BUILDPDB but before MXGINCL
and INCLAFTR programs are executed.
With BUILDPDB=YES and AUDITAFTER=YES, PDBAUDIT is now
executed after all of the specified MXGINCL and INCLAFTR
members are executed.
With BUILDPDB=YES and AUDITAFTER=NEVER, PDBAUDIT is not
executed.
-Now if you specify SUPPRESS=ID with BUILDPDB=YES, the
creation of dataset ID and execution of ANALID are
suppressed. Previously this caused an ABEND.
Thanks to Laifai Wong, Bank of America, USA.
Change 36.138 DB2 IFCID 18 dataset T102S018 was misaligned with wrong
VMAC102 input lengths, for both DB2 V12 and V11.
Jul 27, 2018
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.137 -INVALID DATA for variable MICROCODE that MXG input as a
VMACRHEL numeric, is caused by character values '0x3c', so new
Jul 30, 2018 MICROCODECH character variable is created and MICROCODE
is set to a missing value to prevent VARIABLE NOT FOUND
errors.
-WARNING COUNT USER IN DROP/KEEP/RENAME list was printed
if the MXG Default OPTIONS DKROCOND=NOWARN was changed,
but they shouldn't have been in the KEEP list and are now
removed, and PROGNAME has been added to RHELUARG dataset.
-Datasets left in WORK are now deleted.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 36.136 If you want to ABEND when RMFINTRV workload definitions
VMXGRMFI fall thru to OTHER, i.e., a Service or Reporting Class
VMXGINIT was found that was not mapped in your WORK= definitions,
Jul 23, 2018 you can force a user ABEND nnnn using non-zero NNNN in
%LET MXGABNDRMFI=nnnn; in your sysin.
The log will list the first undefined SRVCLASS value.
Thanks to Wayne Bell, UNIGROUP, USA.
Change 36.135 -Support for PowerExchange Version 10 was redesigned as
VMACPOEX some variables should not have been output in some of
Jan 9, 2018 the datasets, and a number of new variables are kept.
Jan 22, 2018 The four CPU times POEXCPUG, CPUC, CPUD, and POEXCPUL:
Jul 20 ,2018 POEXLIST keeps only POEXCPUG and POEXCPUL
POEXCLIE keeps only POEXCPUG and POEXCPUC; the variables
from FILE and DB2 segments are removed as they
were only from the last segment.
POEXDB2 keeps only POEXCPUG and POEXCPUD
POEXFILE has no CPU times.
-New CPU time variables are added to POEXLIST POEXCLIE:
POEXGSID='POWER*CENTER*SESSION*ID'
POEXGMNM='MAP*NAME'
POEXGTCP='CPU*TIME*ON*CP'
POEXGTOT='CPU*TIME*ON*ZIIP'
POEXGTOF='CPU OFFLOAD*ELIGIBLE*ON*CP'
-New DB2 variable added to POEXDB2 dataset:
POEX2QTY='DB2*CONNECTION*02X=CAF*12X=RRSAF'
Thanks to Scott Wiig, US Bank, USA.
Change 36.134 WebSphere SMF 120 subtypes 5 and 6 only output the first
VMAC120 method per bean, but there can be many. The logic was
Jul 20, 2018 corrected and all are now output in TYP120JC/TYP120JI.
Thanks to Nick Varley, SYNCSORT, USA.
Change 36.133 Variable LPARBUSY was not calculated for z14 processor
ASUM113 in dataset PDB.ASUM1131.
Jul 18, 2018
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.132 Support for EOS Version 160 (INCOMPATIBLE) Audit/Account
VMACWSF records. Only the END records (subtype 4 and 20) have
Aug 5, 2018 valid begin and end times and have their GMT times reset
Sep 26, 2018 to local time zone.
Change 36.131 Reading compressed DB2/CICS data with MXGREADSMF=LOGGER
VMACSMF did not invoke the EXITCICS CICSIFUE exit; the &SMFEXIT
Jul 12, 2018 macro variable was not in the LOGGER's INFILE statement.
-If you have compressed CICS or DB2 records and want to
read the LOGGER data, you must use the CICSIFUE INFILE
exit (EXITCICS); the internal MXG decompression code is
not supported for that combination.
Thanks to John Compton, World Programming, ENGLAND.
Change 36.130 Variable NDMUID is now populated from NDMZUID in NDMCT
VMACNDM and NDMFI datasets with the full 64 byte user id.
Jul 12, 2018
Thanks to Amlyn Parry, Barclays, ENGLAND
Thanks to Heimir Hauksson, Barclays, ENGLAND
Change 36.129 SAS Note 61906 reports SAS 9.4 TS1M3 on z/OS might
SAS NOTE experience poor performance in DATA steps, with CPU time
Jul 12, 2018 increase of 40% reported. The issue is fixed in TS1M4
Aug 8, 2018 and later. See http://support.sas.com/kb/61/906.html
A hot fix was planned for TS1M3, note created Feb 28 and
modified Mar 8, 2018; no Hot Fix was created since M4/M5
corrected the poor performance. But Aug 8, 2018 SAS Tech
Support suggested for SAS 9.4 at TS1M3 that using
// EXEC SASPROC,OPTIONS='MSYMTABMAX=20000000'
to increase the size of the macro symbol table from 1M to
19M would and did eliminate the CPU time increase.
Subsequently, Tech Support said using 2M syntax would and
did resolve the problem.
====== Changes thru 36.128 are in MXG 36.06 dated Jul 9, 2018==========
Change 36.128 z/OS SAS 9.4 M2 Note 58492 reports reading tape data sets
SAS NOTE can fail with ERROR: LIBRARY WEEK31 IS NOT A VALID FORMAT
Jul 4, 2018 FOR ACCESS METHOD SASV7SEQ, but that error message is not
correct. The error is not an invalid format, but is a
memory allocation error. SAS 9.4 M2 added support for LBI
(Large Block Interface), which allocates a buffer for
each tape data library below the 16MB line, and a large
number of SAS tape libraries can exhaust that memory
area. Unfortunately, increasing the REGION size does NOT
increase the below the line size. Reducing the number of
tape data libraries can circumvent the error, which is
corrected in SAS 9.4 M4, and there is a Hot Fix for M2
and M3.
Change 36.127 Support for ZERT SMF type 119 subtype 12 creates datasets
EXT11912 DDDDDD Dataset Description
EXT119C1 T11912 TYP11912SUM ZERT 12 SUMMARY
EXT119C2 T119C1 TYP11912TLS ZERT 12 TLS
EXT119C3 T119C2 TYP11912SSH ZERT 12 SSH
EXT119C4 T119C3 TYP11912IPSEC ZERT 12 IPSEC
FORMATS T119C4 TYP11912DN ZERT 12 DISTINGUISHED NAME
IMAC119
VMAC119
VMXGINIT
Jul 3, 2018
Thanks to Rodger Foreman, Black Knight, USA
Thanks to Luis Mendoza, Black Knight, USA
Change 36.126 Reserved Change Number.
Jul 2, 2018
Change 36.125 Variable SRDGCOMM was replaced by SRDGNAME, but due to
VMACSRDF use of SRDGCOMM in existing reports, both are kept now.
Jun 29, 2018
Thanks to Joe Faska, DTCC, USA.
Change 36.124 SMF 42 Subtype 5 ABEND, more invalid LENSR=560/640.
VMAC42 As reported in Change 36.027, APAR OA54663 corrects.
Jun 29, 2018 MXG circumvention extended to protect these values:
IF LENSR IN(232,240,320,376,400,448,480,560,640)
THEN LENSR=160;
LENSR=376 added Oct 15 in Change 36.124.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.123 Error Documentation: BMC's CMF SMF 74 Subtype 8 SMF74IET
VMAC74 field is incorrect, and causes R748AEBC to be invalid.
Jun 26, 2018 BMC1316 corrects. NO MXG CODE CHANGE.
Change 36.122 Examples in comments for both z/OS and ASCII execution
SAGANAL are revised and enhanced to create HTML output files in
Jun 22, 2018 either a PDSE or in a ZFS File System or ftp to MXG.
Jul 6, 2018 The KEEP CPI: CPU: replaced by specific list of TYPE30_V
Jul 22, 2018 variables, reducing kept from 1533 to the intended 64.
Thanks to Tennie Olson, TIAA,USA.
Change 36.121 If you specified READDB2(IFCIDS=ALL), dataset DB2STATS
READDB2 wasn't created; circumvent with (IFCIDS=ALL STATISTICS).
Jun 16, 2018 MXG 35.03-36.05.
Thanks to Hans Coolen, Allianz Technology, THE NETHERLANDS.
Change 36.120 Support for BVIR History HSM Compression Container V412
EXBVR303 creates new dataset:
FORMATS DDDDDD Dataset Description
VMACBVIR BVR303 BVIR303 HSM COMPRESSION CONTAINER
Jun 16, 2018 and new format MGBVIME decodes Compression Method
Thanks to Bradley Leis, TELUS, CANADA.
====== Changes thru 36.119 are in MXG 36.05 dated Jun 13, 2018==========
Change 36.119 -Formats MG119CI and MG119MA did not decode new values for
FORMATS variables SSH_CIPHER and SSH_MAC in TYP11994 & TYP11995,
VMAC119 and protection for unknown values prints the $HEX4 value.
Jun 13, 2018 -New variable T119RCID='RECORD*ID' added to all datasets.
Change 36.118 Support for TANDEM TMF data creates new TANDTMF dataset.
EXTANTMF DDDDDD DATASET DESCRIPTION
IMACTAND TANTMF TANDTMF TMF TRANSACTION DATA
VMACTAND
VMXGINIT
Jun 11, 2018
Thanks to Kurt Gramling, TSYS, USA.
Change 36.117 SORTBY= is not a valid option for the PMAUD02 trace
ANALDB2R report. If you happened to specify QWHSSSID it worked
Jun 11, 2018 but that was a coincidence. Now produces a message to
tell you and sets SORTBY to QWHSSTCK QWHSSSID.
Change 36.116 STCVSM11 variables NIO and CUB in VSM6 are now bytes so
VMACSTC new variables are created with B added as last character.
Jun 13, 2018 The previous code did not initialize the six calculated
Jun 15, 2018 variables, causing their sum to be greater than the CUB
Jun 22, 2018 and NIO variables; that is corrected.
Jul 2, 2018 -Jun 15: First 36.05. Two Debugging PUTLOGs removed.
-Jun 22: Test to identify VSM6 vs earlier now tests for
VSM6 or ELSE DO; for any other STC11VTS name value.
-Jul 2: Test to identify VSM6 now tests STC11CSP for
values of 1000 or 8000 based on this site's values for
STC11INM to modify that test:
PROC SORT DATA=STCVSM11;
BY STC11CSP;
PROC FREQ;
TABLES STC11CSP*STC11TOL/NOROW NOCOL NOPERCENT;
TITLE STCVSM11 TABULATIONS;
RUN;
PROC FREQ;BY STC11CSP;
TABLES STC11INM*STC11TOL/NOROW NOCOL NOPERCENT;
TITLE STCVSM11 TABULATIONS;
RUN;
PROC MEANS N MIN MAX SUM; BY STC11CSP;RUN;
Thanks to Randy Hewitt, DXC, USA.
Change 36.115 Unused Change Number.
Change 36.114 DB2ACCTR dataset has been misaligned when QLACOFF1 is not
VMACDB2 zero, i.e. if QLACLOCN field is longer than 16 bytes, and
Jun 10, 2018 there is more than one QLAC segment, due to 2 undoc bytes
in the second and subsequent segments, but it was only
INVALID DATA FOR QLACCPUL/QLACDBWT messages that exposed
the error - no user had reported the bad QLACxxxx values,
suggesting DB2ACCTR has not been important nor used!
And those QLAC variables are also kept in DB2ACCT, but
only from the LAST QLAC segment, because originally there
was only one QLAC segment.
Option a: Leave the QLAC variables in DB2ACCT as-is
with this documentation that they are only
from the last segment.
Option b: Set all QLAC variables in DB2ACCT missing
but keep them; dropping existing variables
by MXG is unsafe because it could cause
an ABEND with VARIABLES NOT FOUND if you
have an old report that references then.
I have NOT chosen this option.
Option c: Create macro _DRPQLAC listing all QLAC vars
kept in DB2ACCT so you can add
MACRO _KDB2ACR DROP=_DRPQLAC %
in your IMACKEEP to always drop them from
DB2ACCT, or use you can use
%LET MACKEEP=
MACRO _KDB2ACR DROP=_DRPQLAC % ;
in the //SYSIN of your DB2ACCT create job.
MACRO DRPQLAC is created and available, but
it does not drop QLACLOCN,QLACCNVR due to
references to those variables in others.
Thanks to Scott Wiig, US Bank, USA.
Change 36.113 Incorrect test for GE 526 corrected to GE 538 to input
VMACDB2 QPAC_PIPE_WAIT and QPAC_PIPE_COUNT to correct those two
Jun 5, 2018 variable's values.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.112 Support for Dell EMC Mainframe Enablers 8.30, previously
EXSRDF02 SRDF, Symmetric Remote Data Facility, creates separate
EXSRDF03 datasets for each subtype:
EXSRDF04 DDDDDD DATASET DESCRIPTION
EXSRDF06 SRDF02 SRDFA02 TOLERANCE MODE CHG
EXSRDF07 SRDF03 SRDFA03 ACT CHANGE
EXSRDF08 SRDF04 SRDFA04 SECONDARY DELAY
IMACSRDF SRDFAA SRDFAA REGULAR INTERVAL 05
VMACSRDF SRDF06 SRDFA06 RECULAR MSC INTERVAL
VMXGINIT SRDF07 SRDFA07 WRITE PACING GROUP
Apr 27, 2018 SRDF08 SRDFA08 WRITE PACING DEVICE
Jun 5, 2018
Change 36.111 JCL examples to CPORT/CIMPORT data from WPS to SAS,
JCLCPORT and vice versa on z/OS and ASCII.
Jun 4, 2018
Change 36.110 -S0C7 Abend reading non-Extended Function VSAM dataset in
ADOCRMFV SHOWSP subroutine after Change 36.068 (MXG 36.04 only).
ASMRMFV Extended Function VSAM datasets support striping and
Jun 2, 2018 compression and extended addressability. It is an
attribute of the Data Class. LISTC ENT('dataset') ALL
command will display EXTENDED attribute if file is EF.
-Common RMFV030I and RMFV031I messages now issued for
either EF or non-EF VSAM data sets.
-Documentation Section updated to support the above
changes: Section 12 "Messages"
Thanks to Randy Shumate, RELX Group, USA
Change 36.109 INPUT X $VARYING32000 is very CPU/Elapsed expensive when
TYPENMON the maximum length of the input records is small. Adding
TYPERHEL LENGTH X $1926; reduced 111 CPU seconds to only 40, so a
TYPSNMON _NULL_ data step is added to TYPENMON to find the maximum
TYPSRHEL record length, and the INPUT NMONTEXT $VARYING32000.; is
VMACNMON replaced with this logic, using the _INFILE_ variable:
VMACRHEL LENGTH NMONTEXT $ &NMONLENGTH ;
Jun 5, 2018 NMONTEXT=TRANWRD(_INFILE_,',,',', ,');
It is the actual LENGTH of NMONTEXT that is the major
impact on CPU and Elapsed times, but on z/OS, the LRECL
has some impact, so you need to use an LRECL that is
greater than the MAXNMONLENGTH, printed on the SAS log.
The calculation of the NRWORDSIN that was needed for SAS
V8 and early WPS was revised with added CPU reduction.
The same changes are made for the RHEL/NMON processing.
Steve Bagshaw gets credit for this discovery!
Thanks to Steve Bagshaw, ITMetrics, ENGLAND.
Thanks to Steve McCulloch, TMX, CANADA.
Change 36.108 Support for RACF TOKENs REQTCRE and ADMINCII creates
VMAC80A TOKMADMINCII='TOKEN*ADMINCII'
Jun 1, 2018 TOKMREQTCRE='TOKEN*REQTCRE'
variables in TYPE80TK dataset.
Thanks to Bruce Hewson, Citibank N.A., SINGAPORE.
Change 36.107 If you are using ROLLUPS in DB2 to reduce the volume of
ASUMUOW data then it becomes unlikely that you will get a good
VMXGUOW match between CICSTRAN and DB2ACCT. Further with some
May 31, 2018 of the more recent changes in VMAC110 other than the
class 3 wait times and counts from DB2ACCT there is
not a lot of information added to ASUMUOW from the
DB2ACCT data. To suppress the use of DB2ACCT in your
ASUMUOW invocation all you need to do is to modify the
_LDB2ACC substitution macro to point to _NULL_ as shown
in this code:
%LET MACKEEP=%QUOTE(
MACRO _YESOBS %
MACRO _NOOBS %
MACRO _LDB2ACC _NULL_ %
);
OPTIONS SOURCE SOURCE2;
%INCLUDE SOURCLIB(VMXGUOW);
_NOOBS
OPTIONS NODSNFERR NOVNFERR;
_SUOWCIC /* SORT CICSTRAN DATA */
_SUOWDB2 /* SORT DB2 DATA */
_SUOWMQ /* SORT MQ SERIES DATA */
_SUOWSPN /* CREATE ASUMUOW DATASET */
%VMXGUOW;
_YESOBS
OPTIONS DSNFERR VNFERR;
The new VMXGUOW drops the DB2ACCT variables with the
above suppression, keeping only 99 in the new
PDB.ASUMUOW, previously there were 144.
Only comments were added in ASUMUOW with this example.
Change 36.106 TYPE42DS Encryption variables were INPUT but not KEPT nor
VMAC42 labeled nor formatted:
May 31, 2018 S42AMRIB='S42AMRIB*BYTES*READ'
S42AMWIB='S42AMWIB*BYTES*WRITTEN'
S42AMRBD='READ BYTES*DECRYPTED*OR ELIGIBLE'
S42AMWBE='WRITE BYTES*ENCRYPTED*OR ELIGIBLE'
S42AMRCI='VSAM*CI-S READ OR*PHYSICAL*BLOCKS'
S42AMWCI='VSAM*CI-S WRITTEN*PHYSICAL*BLOCKS'
With the large number of TYPE42DS observations, if you
want to only select datasets with encryption counts:
%LET MACFILE=
%QUOTE(IF ID=42 THEN DO; IF SUBTYPE=6; END; );
%LET MACKEEP=
%QUOTE(
MACRO _ETY42DS
IF S42AMRBD GT 0 OR S42AMWBE GT 0 THEN DO;
OUTPUT _WTY42DS;
END;
% );
%INCLUDE SOURCLIB(TYPE42);RUN;
which will only populate TYPE42DS when bytes GT zero.
Syntax note: The original MACFILE syntax suggested
%LET MACFILE= %QUOTE( IF ID=42 AND SUBTYPE=6; );
is fine for ONLY the TYPE42 program, but if that was
used with BUILDPDB, only the 42.6 would be read, hence
the above, safer selection will pass all other SMF
records in case you want to process other records.
Thanks to David Cogar, Wells Fargo, USA.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.105 Example SYSLOG processing TYPESYSL/TYPSSYSL/VMACSYSL that
TYPESYSL was added in 34.04 renamed TYPESYSX/TYPSSYSX/VMACSYSX due
May 24, 2018 to conflict with TYPESYSL dataset created by TYPETMNT.
Change 36.104 Reserved Change.
May 23, 2018
Change 36.103 Format MGSTCCS for variable STC11CSP in STCVSM11 dataset
FORMATS has new value '8000'x='8000X:VSM6 FICON CHANNEL'.
May 23, 2018
Thanks to Randy Hewitt, DXC, USA.
Change 36.102 DB2 V11 APARS PI71903,PI84045,PI82755 added offsets _SC,
VMAC102 _PR, _INC, and _SQL to populate those fields that were
May 22, 2018 previously only in DB2 V12. MXG test changed to GE 11.1.
The timestamp variable QW0376TS in old data was invalid
(e.g. '1A6CE0BD12FCB083'x, a date in 1914!) and was set
to a missing value; now whatever is there is input so it
may still be incorrect.
Thanks to Joachim Sarkoschits, DATEV, GERMANY.
Change 36.101 Support for NDM-CDI OP (Operator Clist Record) creates
EXNDMOP NDMOP dataset.
VMACNDM
VMXGINIT
May 21, 2018
Thanks to Michael Oujesky, DTCC, USA.
Change 36.100 ACF2 Version 6.2 circumvention in Change 36.075 exposed
VMACACF2 another STOPOVER as LENLEFT was not correctly calculated.
May 23, 2018
Thanks to Jim Horne, Lowe's, USA.
Thanks to Mohammed Naseer, Lowe's USA.
Change 36.099 Support for RACF TOKDANAM IBMLABEL creates new TOKLABEL
VMAC80A variable in TYPE80TK dataset.
May 23, 2018
Thanks to Coen Wessels, IBM, GERMANY
Change 36.098 Format MGMOCTY, used for Information Builder's FOCUS,
FORMATS has two new values for BEGIN and END. Only FORMAT was
VMACFOCU changed, no change was made to VMACFOUU.
May 17, 2018
Thanks to Tim Hare, Hare Systems, USA.
Change 36.097 The default triplet length for CICS/TS 5.2 to detect and
VMAC110 report there are excluded fields is corrected to 365/3260
May 14, 2018 from 373/3356 (which had included optional fields).
Thanks to Paul Maradin, DXC, USA
Thanks to Larry McCulley, DXC, USA
Change 36.096 Line seven should have two periods, &PDBMXG..ACF2AR.
ANALACF2
May 14, 2018
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.095 The %LET MXGABND=nnnn; option to abend instead of error
VMACBBMQ is added to the BBMQ processing. See Change 21.384.
May 11, 2018
Change 36.095 New 4-digit example format in tailoring IMACSMFF fails on
IMACSMFF WPS Version 4, under investigation, but add the comments
May 9, 2018 as shown here to circumvent:
/* COMMENT OUT - DEFAULT BREAKS WPS V4
'2047.000'='2047.000:MAX VALUE AND LABEL NO SUBTY'
'2047.001'='2047.001:MAX VALUE LABEL WITH SUBTYPE'
END COMMENT */
The default IMACSMFF is always executed when SMF is read.
Change 36.094 MXG 35.12-36.04. If you use IMACFMTS to add your site's
FORMATS own FORMATs, the RUN; statement in member FORMATS after
Apr 10, 2018 the VALUE $MGRMVOS statement should NOT have been added.
Thanks to Robert Debartolo, Cognizant, USA.
Change 36.093 CICS Dispatcher Statistics CICDS dataset, DSGTMADQ was
VMAC110 too large; field is now input &PIB.4.2 with two decimals.
Apr 9, 2018
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.092 ACCTSORT=NO was not working as advertised. The datasets
READDB2 ended up in WORK rather than PDBOUT.
Apr 9, 2018
====== Changes thru 36.091 are in MXG 36.04 dated May 8, 2018==========
Change 36.091 If DB2ACCT existed but had 0 OBS input was set to _NULL_
VMXGUOW resulting in many UNITIALIZED variable messages. VMXGUOW
May 7, 2018 now checks only for the existence of the dataset and if
it does not exist sets it to _NULL_.
Change 36.090 If you tailored IMACDB2 to redefine MACRO _Lxxxxxx's and
ANALDB2R you specified only a single level name, so those datasets
May 3, 2018 are written to WORK, and did not specify a PDBOUT,
you could get this syntax error
ERROR: THE FUNCTION COMPBL REFERENCED BY THE %SYSFUNC
OF %QSYSFUNC MACRO FUNCTION HAS TOO FEW ARGUMENTS.
due to incorrect logic, now corrected, in ANALDB2R.
Originally posted to MXG-L as possible issue with SAS
V9.3 to V9.4 migration, the thread was updated/corrected.
Change 31.104, MXG 31.03, May 2013, created the exposure;
the user's good run was with MXG 31.01.
Thanks to Dennis Longnecker, State of Washington Courts, USA.
Change 36.089 APAR OA54884 for z/OS 2.3 ONLY reports very high I/O EXCP
DOCUMENT counts in EXCPTOTL (Address Space Total, SMF30TEX) that
May 1, 2018 was observed in the MASTER address space, but could occur
in any address space.
Change 36.088 SAS Note 51008 Java versions 1.6/1.7/1.8 can cause errors
DOCUMENT ERROR: The Java proxy could not create a new xxxxxxxx.
May 1, 2018 ERROR: shmag() failed in Java extension rc -1 errno 124
ERROR: Unable to attach current thread.
on z/OS. That Note the circumvention is to add this line
JREOPTIONS=(
-Djava.lang.ClassLoader.lazyInitialization=false)
to your SASHLQ.CONFIG(SITE) configuration PDS member.
SAS Support reported SAS does not support Java 8 yet;
see also SAS Note 51195.
Change 36.087 Unused Change Number.
Change 36.086 DCOLLECT Encryption Variables are now kept in DCOLDSET:
VMACDCOL indicates if the LCU contains at least one FICON channel.
Apr 24, 2018 DCDTYPE ='ENCRYPTION*TYPE'
DCDKLBL ='ENCRYPTION*KEY*LABEL'
The IBM Documentation does not provide DCDTYPE values to
decode. These fields were added by z/OS 2.3.
Thanks to Mike Creech, Black Knight, USA.
Change 36.085 Variable IOPDSTX is now kept in TYPE78IO dataset; bit 1
VMAC78 indicates if the LCU contains at least one FICON channel.
Apr 24, 2018
Thanks to Lane Thorne, Honda of America Manufacturing, USA.
Change 36.084 Dataset STCVSM11 variables added by Change 34.237 were
VMACSTC incorrectly labeled and inconsistent, now corrected:
Apr 23, 2018 STC11NHR='HOST*INTERFACE*I/OS'
STC11NHW='HOST*INTERFACE*CUBUSY*DURATION'
STC11NRR='REMOTE*INTERFACE*I/OS'
STC11NRW='REMOTE*INTERFACE*CUBUSY*DURATION'
STC11NIR='IP*INTERFACE*I/OS'
STC11NIW='IP*INTERFACE*CUBUSY*DURATION'
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.083 EXPDBINC EXPDBVAR EXPDBCDE can now be used with UTILBLDP
UTILBLDP and BUILDPDB=NO so you can create your own custom dataset
Apr 27, 2018 with control of variables, etc. This example creates the
PDB.SMFHEADER dataset with four variables kept from every
SMF header:
%UTILBLDP(USERADD=ID 118,BUILDPDB=NO,
EXPDBVAR=PDB.SMFHEADER
(KEEP=SYSTEM SMFTIME ID SUBTYPE),
EXPDBCDE=OUTPUT PDB.SMFHEADER;,
OUTFILE=INSTREAM
);
%INCLUDE INSTREAM;
-Unrelated, unprintable '08'x character introduced 35.09
is removed.
Thanks to Randy Hewitt, DXC, USA.
Change 36.082 Correction for DB2 BPHITRAT variable to replace the sum
VMACDB2 of RIO/SPP/DPP/LPP with DIO/LIO/RIO/SIO.
Apr 19, 2018
Change 36.081 Support for four-digit SMF Record Type ID (MAX 2047) for
ANALID the ANALID report.
FORMATS -Format $MGSMFID text shifted one byte to the right; a few
IMACSMFF record descriptions lost 1 character to keep 37 maximum.
VMACID -VMACID,VMACSMF formats are now SMFIDSUB $8. SMFIDCH $4.
VMACSMF increasing the LENGTH of those variables by one byte,
Apr 23, 2018 format 7.3 references are changed to 8.4 for IDANDSUB.
Apr 27, 2018 -Unfortunately, if you have used IMACSMFF to label your
user SMF Record Descriptions, you will need to replicate
all and insert a blank at the beginning of each existing
3-character record type, to match the new example in that
IMACSMFF member:
'2047.001'='2047.001:MAX POSSIBLE VALUE AND LABEL'
-One line summary report with total records and bytes and
the time range of the input SMF file is added.
Change 36.080 VMXGGETM utility accepts SMF selection syntax nnnn.mmm
VMXGGETM where nnnn is the SMF Record Type (max is now 2047) and
Apr 18, 2018 where mmm is the subtype. VMXGGETM creates an output SMF
file with example records of each selected type.
Change 36.079 -Support for new SMF 119 subtypes 24, 38, 39, 40, and 45.
EXT11924 creates these new datasets:
EXT11938 dddddd Dataset Description
EXT11939 T11924 TYP11924 TNPROFILE
EXT11940 T11938 TYP11938 SmcdLnkStats
EXT11945 T11939 TYP11939 SmcdLnkStart
IMAC119 T11940 TYP11940 SmcdLnkEnd
VMAC119 T11945 TYP11945 IsmStats
VMXGINIT Untested with data.
Apr 18, 2018 -New BitRate variables added to TYP11906 dataset:
Apr 26, 2018 IFINBITRT='INBOUND*BITS PER*SECOND'
IFOUBITRT='OUTBOUND*BITS PER*SECOND'
IFBITRATE='TOTAL*BITS PER*SECOND'
-CO:Z subtypes 192 and 193 are validated with data.
Change 36.078 z/OS, SAS 9.4 M3 with IBM DFSORT, ABEND 0C4 in SASVZSR1,
CONFIGxx when sorting a large dataset. SAS notes 57676 and 58629
Apr 17, 2018 circumvent the error with these options
// EXEC MXGSAS94,OPTIONS='SORTBLKMODE SORTBLKREC=5000'
which could alternately be specified in your CONFIGxx,
but SORTBLKMODE has been the SAS Default for years. The
SORTBLKREC option is not yet documented by SAS.
http://support.sas.com/kb/57676
http://support.sas.com/kb/58629
This is documentation only, no code was changed.
Change 36.077 With a BY statement in your VMXGSUM INCODE, there is no
VMXGSUM guarantee that the data order will be correct, and if you
Apr 14, 2018 also %LET MXGSUMCLASS=YES or CLASSNWAY to YES, the data
May 8, 2018 step may fail. VMXGSUM now looks at the first word in the
INCODE= and if it is BY sets CLASSNWAY to NO.
Change 36.076 CICS Statistics Dispatcher CICDS dataset set DSGTWT to
VMAC110 DURATM when DSGTWT was greater (Change 35.264), but that
Apr 14, 2018 should only have been done for SMFSTRQT='INT' as DURATM
doesn't exist in the 'REQ', 'USS', nor 'EOD' records.
Thanks to Paul Volpi, UHC, USA.
Change 36.075 ACF2 INVALID SMF RECORD, ACSMFREL=0 VS 6.2, ERRRORABEND.
VMACACF2 MXG tests for the last release, 6.2, but new ACF2 record
Apr 14, 2018 has '00'x instead of '62'x in byte 119, causing MXG test
for 6.2 to fail. This change forces ACSMFREL=6.2 if it
is zero for this INCOMPATIBLE CHANGE to the ACF2 record.
The CA fix is PI24126 and a reassembly of DMGSMF exit.
Thanks to Michael K Yuan, Navy Federal Credit Union, USA.
Change 36.074 -Variables BETALOG in BETA50 and B97LOG in BETA9750 were
VMACBETA reversed, OFF was ON and ON was OFF, bit test corrected.
VMACBE97 -TYPEBE97 subtype 31 revised: like TYPEBETA, there can be
Apr 17, 2018 an R1 and R2 value for each FIELDNAME, but TYPEBETA PUT
May 15, 2018 the text value into a character variable for R1 and R2,
but those values were then difficult to test. TYPEBE97
instead creates nine pair of variables with true values
(like Dates, Times, HEX, etc).
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 36.073 Support for z14 ZR1 adds new variable to TYPE70 dataset:
VMAC7072 SMF70MAXPU='CORES*PHYSICALLY*AVAILABLE*THIS MODEL'
Apr 12, 2018
Change 36.072 Variables now INPUT for TYPE99_6 subtype 6 dataset:
VMAC99 PSERV ='SERVICE*DURING*INTERVAL'
Apr 12, 2018 PISERV ='ZAAP*SERVICE*DURING*INTERVAL'
PSSERV ='ZIIP*SERVICE*DURING*INTERVAL'
TIME_AT_PDP_USING='TIME AT*PDP USING*SAMPLES'
TIME_AT_PDP ='TIME AT*PDP*ACCUMULATOR'
PCT_USING_PDP ='PCT*TIME*USING*SAMPLES'
SMF996_FLAGS ='SMF996_FLAGS'
EWLM_LOCAL_PI ='EWLM*LOCAL*PI'
EWLM_GLOBAL_PI ='EWLM*GLOBAL*PI'
SMF996EWLM ='EWLM*MANAGED?'
SMF996IOPR ='I/O*PRIORITY?'
SMF996INEL ='ZIP*INELIGIBLE?'
SMF99_NUM_EXT_SC='EXTERNAL*SERVICE*CLASSES'
Thanks to Randall Schlueter, First Data, USA.
Change 36.071 IAM User SMF INPUT STATEMENT EXCEEDED because unexpected
VMACIAM short segment lengths IAMIAINL=148 (MXG expected 204) and
Apr 8, 2018 IAMIASTL=148 (MXG Expected 204) were encountered, and now
protected for these IAM 9.2 records.
Thanks to Paul Naddeo, FISERV, USA.
Change 36.070 VMXGDUR rejected INTERVAL=THREEHOUR but the warning
VMXGDUR message said that was correct. It was looking for THREEHR
Apr 8, 2018 but will now accept THREEHOUR, EIGHTHOUR, or TWELVEHOUR.
Change 36.069 Dataset CICSTRAN variables DURATM and DSGTWT were missing
VMXGCICI values in CICS Statistics SMFSTREQ='USS','REQ',or 'EOD'
Apr 6, 2018 records as the DURATM only exists in the 'INT' records.
But using the DIF(COLLTIME) a pseudo DURATM is created
and used to populate/correct DSGTWT and DURATM.
Change 36.068 -Two new enhancements.
ADOCRMFV -A new RMFBSAM record with an MXG01 id is now output
ASMRMFV for every successfully processed RMF III VSAM data set.
VMACRMFV VSAM attributes and statistics are included as well as
Apr 6, 2018 many ASMRMFV statistics and counters, and the record is
May 5, 2018 output in new dataset ZRBAS1.
May 9, 2018 -Between the existing MXG00 record and the new MXG01
record nearly all information on an ASMRMFV log is
captured. The MXG01 data becomes the ZRBASMDS (?) data
set in the result PDB.
-MXG01 records are only created for RMF III VSAM data sets
that open and close successfully. There are no MXG01
records generated for:
Empty VSAM data sets (VSAM considers this an error)
VSAM data sets that are not an RRDS type
VSAM data with an invalid CISIZE for RMF III data
VSAM data with an invalid LRECL for RMF III data
Non-VSAM data sets
The above conditions have been flagged in the ASMRMFV
Log for a long time.
-Two new parameters UPCASE/NOUPCASE control the handling
of values assigned in keyword=value usage.
-UPCASE (alias UC) is the default and provides the same
behavior as in prior ASMRMFV versions which force all
PARM and SYSIN (or alternative) input data to upper case
internally.
-NOUPCASE (alias NOUC) is the default and does not alter
any values assigned to a keyword. And thus lower case
values can be assigned to a keyword.
-However, for most (if not all) data filters currently
supported by ASMRMFV only upper case values are accepted.
For example, Sysplex Ids, System Ids, Job Names, Job
Classes, and so on are all required by IBM syntax rules
to be in upper case. Lower case values are flagged as
errors by ASMRMFV validation routines.
-NOUPCASE is a feature primarily intended for future
filtering enhancements where lower case values could
be accepted.
-NOINDEXES and/or NOSPACE parameters might not work
correctly in all situations and this has been corrected.
Messages were not always suppressed when they should
have been.
-Message RMFV105I produced for ASMRMFV Detail and
Summary reports now shows the full 5 character RMF III
table id instead of just the first 3 characters. This
change was needed to distinguish MXG00 and MXG01 output
record statistics.
-Minor changes to messages RMFV037I, RMFV041I, RMFV051*
(*= S,E,W,I), and RMFV106W.
-Several documentation Sections are updated to support
the above changes:
Section 5 "Input Data Selection Parameters"
Section 12 "Messages"
Section 31 "Summary"
Section 32 "Bibliography"
Change 36.067 z/OS, MXG's default CAPSOUT option causes lower case text
CONFIGxx to be upper cased, but MXG recommends NOCAPSOUT for ODS,
Apr 5, 2018 and the SAS default on z/OS is NOCAPSOUT. I don't know
why I changed the SAS default years ago, but "CAPSOUT" is
removed from all of the example MXG CONFIGxx members, so
your site's default value will be used.
Change 36.066 Support for "IBM Developer for z Systems IDZ" SMF 122
EXTY122A subtype 1 record creates new dataset TYPE122A. TYPE122A
IMAC122A is used because there is a TYPE122 record (that is/was?)
TYPE122A previously written by Tivoli Allocation. The Product Name
TYPS122A The Product Name field contains 'C2AE'x before and after
VMAC122A the name, where 'AE'x is the ASCII registered copyright
VMXGINIT symbol, but 'C2'x is a Danish A with a ring above! Both
Apr 4, 2018 are printed on ASCII SAS, but both are blank on z/OS, and
on z/OS lower case characters are converted to upper case
by the $ASCIIn. INFORMAT.
Thanks to Tory Lepak, Aetna, USA.
Change 36.065 AS400 7.3 QAPMDISK new fields below are now documented
VMACQACS and are added to QAPMDISK dataset, transparently.
Apr 3, 2018 MXG created the PCTCLEAN and DSFSMAPBY variables:
DSFSMAPSZ ='FREE SPACE*MAP 4K*PAGES*COUNT'
DSFSCLEAN ='CLEAN*4K PAGES*FREE SPACE*COUNT'
DSFSCLEAN0='LEVEL 0*CLEAN BLOCKS*PAGES 1-7'
DSFSCLEAN1='LEVEL 1*CLEAN BLOCKS*PAGES 8'
DSFSCLEAN2='LEVEL 2*CLEAN BLOCKS*PAGES 16'
DSFSCLEAN3='LEVEL 3*CLEAN BLOCKS*PAGES 32'
DSFSCLEAN4='LEVEL 4*CLEAN BLOCKS*PAGES 64'
DSFSCLEAN5='LEVEL 5*CLEAN BLOCKS*PAGES 128'
DSFSCLEAN6='LEVEL 6*CLEAN BLOCKS*PAGES 156'
DSFSFRAGIX='FREE SPACE FRAGMENTATION INDEX'
DSFSDIRTY ='DIRTY*4K PAGES*FREE SPACE*COUNT'
DSFSDIRTY0='LEVEL 0*DIRTY BLOCKS*PAGES 1-7'
DSFSDIRTY1='LEVEL 1*DIRTY BLOCKS*PAGES 8'
DSFSDIRTY2='LEVEL 2*DIRTY BLOCKS*PAGES 16'
DSFSDIRTY3='LEVEL 3*DIRTY BLOCKS*PAGES 32'
DSFSDIRTY4='LEVEL 4*DIRTY BLOCKS*PAGES 64'
DSFSDIRTY5='LEVEL 5*DIRTY BLOCKS*PAGES 128'
DSFSDIRTY6='LEVEL 6*DIRTY BLOCKS*PAGES 256'
PCTCLEAN='PERCENT*CLEAN*PAGES IN*FREE SPACE'
DSFSMAPBY='FREE*SPACE*SIZE*MGBYTES'
====== Changes thru 36.064 are in MXG 36.03 dated Apr 2, 2018=========
Change 36.064 All updates in the Jan, 2018, SMF Manual are included in
SMF MANUAL MXG Version 36.03, except new SMF 122, which is not in
Mar 30, 2018 that SMF Manual.
Change 36.063 DB2 V9 ONLY, zero obs in DB2STATB and other statistics
VMACDB2 datasets listed in Change 35.299, which revised deaccum
Mar 29, 2018 logic and expected one minute statistics intervals, but
that IBM Change to force the DB2 Statistics Interval to
one minute wasn't introduced until DB2 Version 10!
Thanks to Don Blaszka, Wipro Limited, USA.
Change 36.062 Further VXBYUSR logic revised to use only 2 decimals for
VMACVMXA all _MT1 DIF() functions; these data have only two digit
Apr 1, 2018 time resolution, but the divide by 4096 produced false
digits in 3rd and 4th place that, coupled with these
very large 2-complement numbers, cause MXG to falsely
detect a break in deaccumulation. See also 36.052.
Change 36.061 Invalid SYTNLPS value in SYTCUP records prevented their
VMACXAM output; pending Velocity fix, SYTNLPS=(SEGLEN-28)/20; is
Mar 20, 2018 used to calculate the actual number of segments.
Change 36.060 Support for BMC Extended Buffer Manager XBM SMF Record.
EXXBMDS -The Data Set Statistics Record can have seven OIDs:
EXXBMCA OID Variables Segment
EXXBMCC 113 xbmDSSnn Dataset Statistics
EXXBMCE 113 xbmSDSnn Snapshot Data Set Statistics
EXXBMCS 154 xbmDB2nn DB2 Statistics
IMACXBM 158 xbmSUSnn Snapshot Utilities Statistics
TYPEXBM 199 xbmVSAnn VSAM Statistics
TYPSXBM 272 xbmEPSnn Extended Prefetch Statistics
VMACXBM 242 xbmIMSnn IMS Statistics
VMXGINIT and all seven segments are output in XBMDSET dataset.
Mar 21, 2018 DDDDDD Dataset Description
XBMDS XBMDSET XBM Data Set Record
(Only the first four OID's have been data-validated).
-The Cache Statistics Record can have four OIDs,
1 xbmCSSnn Configuration Start Section
2 xbmCEEnn Configuration End/Stop Section
3 xbmCCCnn Configuration Change Statistics
106 xbmCACnn Cache Statistics Section
and each is output in a separate dataset:
DDDDDD Dataset Description
XBMCA XBMCACHE XBM Cache Record
XBMCS XBMCSTRT XBM Configuration Start
XBMCE XBMCEND XBM Configuration End
XBMCC XBMCHG XBM Configuration Change
Thanks to Flavio Lima, MetLife, USA.
Change 36.059 -If you specified USERADD=ID a CHAR OPERAND FOUND IN %EVAL
UTILBLDP error indicated that a numeric was needed, which was due
Mar 21, 2018 to the compiler interpreting %STR(/VIEW=ID) as a formula.
Resolved by using %QUOTE rather than %STR, like the other
references in UTILBLDP.
-The SMF AUDIT report was not being produced, now is.
Change 36.058 Missing %END in PMAUD02 corrected and BEGTIME and ENDTIME
ANALDB2R parameters enabled for MXGDB2B1 report. MXG 36.02 only,
Mar 23, 2018 introduced by Change 36.048.
Thanks to Randy Hewitt, DXC, USA.
Change 36.057 Support for z/OS 2.3 RMF Changes (SHARE Sacramento 2018):
EXTY748S -Support for APAR OA53411 for more than 65535 devices adds
FORMATS SMF74SMF bit and populates existing SMF74LSN with a flag
IMAC74 when multiple logical SMF records were created, but these
VMAC7072 variables are not kept, and don't impact MXG's reading of
VMAC74 the individual physical SMF records; the variables are
VMXGINIT available in the EXTY74 exit, if ever of interest.
Mar 26, 2018 -Support for APAR OA50760 72.3/4, was in Change 35.125.
-Support for APAR OA50761 74.10, was in Change 35.273.
-Support for APAR OA52694 72.3 TYPE72TR+ in Change 36.050.
-Support for APAR OA50762 74.9 new bit existing R749FLAG.
-Support for APAR OA50693 70.2 CEX6C/CEX6A/CEX6P Crypto
updated $MGRMFCX/$MGRMFCY/MGRMFCZ formats.
-Support for APAR OA50755 74.1 was in Change 35.193.
-Support for APAR OA50755 74.9 was in Change 35.146.
-Support for APAR OA53411 adds 74.5 vars to TYPE74CA.
R7451SRR='SYNC I/O*CACHE*READ*REQUESTS'
R7451SRH='SYNC I/O*CACHE*READ*HITS'
R7451SWR='SYNC I/O*CACHE*READ*REQUESTS'
R7451SWH='SYNC I/O*CACHE*READ*HITSS'
-Support for APAR OA53411 74.8 adds new Synchronous I/O
Link Statistics Segment that creates new TYPE748S data
set with these variables:
R748SIID='SYNC*I/O*INTERFACE*ID'
R748STYP='SYNC*I/O*LINK*TYPE'
R748SSPD='SYNC*I/O*LINK*SPEED'
R748SWDH='SYNC*I/O*LINK WIDTH*LANES'
R748SSTE='SYNC*I/O*LINK*STATE'
R7451INC='BYTES*TIME*INDETERMINABLE'
R748SCBR='SYNC I/o*CACHE*BYTES*READ'
R748SCro='SYNC I/o*CACHE*READ*OPERATIONS'
R748SCRS='SUCCESSFUL*CACHE*READ*OPERATIONS'
R748SCRT='SYNC I/o*CACHE*READ*TIME'
R748SCBW='SYNC I/o*CACHE*BYTES*WRITE'
R748SCWO='SYNC I/o*CACHE*WRITE*OPERATIONS'
R748SCWS='SUCCESSFUL*CACHE*WRITE*OPERATIONS'
R748SNBW='SYNC I/O*CACHE*WRITE*TIME'
R748SNWO='NVS*BYTES*WRITTEN'
R748SNWS='NVS*WRITE*OPERATIONS'
R748SNWT='NVS*WRITE*TIME'
-Support for APAR OA51913, z14 physical core addresses
greater than 191, was protected in MXG 31.04, which
supports the maximum possible value of 255, even though
z/OS doesn't even support 191.
-Support for Jan 2018 SMF Manual and APAR OA52003 that
added these variables to TYPE74ST Structure dataset:
R744SIAD R744SADN R744SIXC R744SXSC R744SXST R744SXSQ
R744SADO R744SADR R744SQCH R744SXFL R744SWDR R744SWAC
R744SRDR R744SRAC R744SWEC R744SREC R744SWED R744SWES
R744SRED R744SRES
R744SIAD R744SADN R744SIXC R744SXSC R744SSXT R744SXSQ
R744SADR R744SQCH R744SXFL
R744SWDR R744SWAC R744SRDR R744SRAC R744SWEC R744SREC
R744SWED R744SWES R744SRED R744SRES
-Support for Jan 2018 SMF Manual which added to TYPE74DU:
R744RSST R744RIDP R744RCPI R744RCPN R744RSGS R744RSA1
R744RSA2 R744RSA3 R744RSA4 R744RSA5 R744RSA6 R744RSA7
R744RSA8 R744RSID R744RSC R744RAMC R744RAMS R744RAMS
R744RAMP R744RAMN
Change 36.056 zHyperwrite enables DB2 to perform parallel log writes to
VMAC74 PPRC primary and secondary volumes, but they are the same
VMAC79 4-hex-digit DEVNR, and because they can be concurrently
Mar 15, 2018 active, RMF Reports now display 5-hex-digit DEVNR, with
the first nybble containing the SubChannel ID, 'sdddd'X,
where the SubChannel ID is 0,1,2 or 3. No change was made
to the SMF 74/79 records, as the SubChannel ID is already
in those records, and the 5-hex-digit display is only in
RMF reports/data: they won't exist in other SMF records.
MXG variable DEVNR5HEX is created in TYPE74, TYPE74CA,
TYPE748 and TYPE796 as DEVNR5HEX=65536*SMF74SCS+DEVNR
with FORMAT DEVNR5HEX HEX5. format.
Change 36.055 New TYPE8231 dataset was misaligned and the VMXGINIT for
VMAC82 _WTY8231 thru _WTY8247 was corrected to write to WORK
VMXGINIT rather than to PDB.
Mar 13, 2018 -Mar 20: Invalid Subtype 31 with only 4 bytes for 0203 TAG
Mar 20, 2018 encountered, circumvented, and reported to IBM.
Apr 12, 2018 -Apr 12: MXG's problem was that the SMF82_TRIPL_LENGTH
field was presumed to be the length following it, but it
was 8 with when 4 bytes remained, so I presumed there was
truncated data for the TAG 0203 segment. IBM Support
responded with a very detailed decoding of the record
with their utility that matched MXG's values, concluding:
"To sum up, the length of 08 that you are referencing
does not mean that 8 bytes will follow. It means the
length in the record is composed of the length of the
data item (4 bytes) plus the length of the tag and
size info (another 4 bytes)."
While TAGs have different lengths, since each TAG's
length is fixed, MXG did not need to use that field,
so no MXG code change was required, and no data was
truncated.
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Thanks to David A. Hilliard, IBM Support, GERMANY.
Change 36.054 A missing paren caused BLDSMPDB to fail, and %macro
BLDSMPDB &PDBPATH was not initialized in PDBAUDIT. BLDSMPDB only
PDBAUDIT failed when MTD was used which then caused SAS to set
Mar 13, 2018 OBS=0 and caused PROC SQLs in PDBAUDIT to then fail.
PDBAUDIT is now protected for the 0 OBS case
Thanks to Harold Zbiegien, American Greetings, USA.
Change 36.053 INTBTIME and INTETIME variables are now all DATETIME25.6
BUIL3005 formatted, even though only those INPUT with TODSTAMP8
BUILD005 will have all six decimals populated, SMFSTAMP informat
SMFINTRV only has 2 decimals. INTETIME in SMF 91 with TODSTAMP8
VMAC30 informat forced the format change, since you can't have
VMAC91 different formats for the same variable name in datasets
Mar 8, 2018 created in the same DATA step.
Thanks to Randy Hewitt, DXC, USA.
Change 36.052 Revision to z/VM VXBYUSR logic to correct large values
VMACVMXA in many deaccumulated durations when there were multiple
Mar 7, 2018 logon values in CALTODON for the same user, and/or when
a guest has been relocated. Logic to recalculate DELTATM
from HFRATE*HFQCNT was causing output of first instances,
so it was removed. A heuristic was added to test that
the record DELTATM was not more than 2*INTERVAL since
that also detects a return of a relocate to delete.
See Change 36.062.
Thanks to Graham Harris, RBS, ENGLAND.
Change 36.051 Support for AS/400 Version 7.3 Collection Services.
VMACQACS -New GDES fields added to QAPMCONF dataset for keys
Mar 7, 2018 FL PM TY TZ T1 T2 T3 T4 U1 U2 U3 U4 XS
Mar 16, 2018 -New DATETIMECH,UTCTIMECH 26-character datetimes and
Mar 23, 2018 DSQUEOPS counter added to QAPMDISK record, which now
Mar 26, 2018 has LRECL=751 (YOU MUST SET IN YOUR JCL/FILENAME).
See change 36.065.
====== Changes thru 36.050 are in MXG 36.02 dated Mar 5, 2018=========
Change 36.050 TYPE72GO variables R723CPA_ACTUAL and R723CPA_SCALING
VMAC7072 added by APAR OA52694, were trashed because they were
Mar 2, 2018 input when they shouldn't have been; the test for INPUT
Mar 6, 2018 should have been GE 276 instead of repeated GE 268.
Mar 6: New variable ORG70CPA was added to TYPE70 and
TYPE70PR, but the label statement had OGT70CPA causing
a harmless UNINIT variable message on the log.
Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Change 36.049 Change 35.200 left off the trailing / or ] on the
VGETALOC directory names if you did not supply it and it could
Mar 2, 2018 result in no allocations and a failure of a following
VMXGSET. Now if we don't find the / or \ we supply it.
Thanks to Richard Krueger, Sentry, USA.
Change 36.048 For PMAUD02 report SORTBY use is restored, but the first
ANALDB2R variable in the list must be QWHSSSID, and variables not
Mar 2, 2018 in the below list will terminate with error messages.
The default values are QWHSSSID QWHSSTCK; if that first
variable is not DB2 or QWHSSSID, QWHSSSID is inserted.
Allowed variables are:
DB2 - THE DB2 SUBSYSTEM ID
PLAN - THE DB2 PLAN NAME
AUTHID - THE AUTHORIZATION ID
CONNID - THE CONNECTION ID
CONNTYPE - THE CONNECTION TYPE
CORRID - THE CORRELATION ID
QWHSSSID - THE DB2 SUBSYSTEM ID
QWHCPLAN - THE DB2 PLAN NAME
QWHCAID - THE AUTHORIZATION ID
QWHCOPID - THE ORIGINAL AUTHORIZATION ID
QWHCCN - THE CONNECTION ID
QWACATYP - THE CONNECTION TYPE
QWHCCV - THE CORRELATION ID
QWHSSTCK - THE TIME OF THE EVENT
Thanks to Scott Swindling, PREMERA, USA.
Change 36.047 Support for XCOM Version 12.0 (COMPATIBLE) adds variables
VMACXCOM XCOMGWDP='GATEWAY*DPATH'
Feb 28, 2018 XCOMSSLT='SSL*VERSION'
XCOMCIPHN='SSL*CIPHER*NAME'
XCOMRCNT='RESTART*COUNT'
XCOMPLEXQ='ORIGIN*PLEXQ*GROUP*NAME'
Thanks to Alfredo Antonio Gonzalez Ortega, ITNOW, SPAIN
Thanks to Sergi Vilaseca Punti, ITNOW, SPAIN
Thanks to Miguel Fco. Monferrer Carvajal, ITNOW, SPAIN
Change 36.046 Support for NDM Version 5.2 corrects NDMCPU and adds
VMACNDM these variables to the NDMCT dataset:
Mar 1, 2018 NDMCLASS ='PROCESS*SESSION*CLASS'
Apr 6, 2018 NDMCTFLAG17='FASP17*OVERRIDE*TO FASP=NO'
NDMCTFLAG18='FASP18*OVERRIDE*TO FASP=NO'
NDMCTGPF ='GENERAL*PURPOSE*FLAG'
NDMDBLKSZ ='DESTINATION*BLKSIZE'
NDMDDSORG ='DESTINATION*DSORG'
NDMDLRECL ='DESTINATION*LRECL'
NDMDRECFM ='DESTINATION*RECFM'
NDMFASPBW ='FASP*BANDWIDTH*KBITS'
NDMFASPFT ='FASP*FILESIZE*THRESHOLD'
NDMFASPPL ='FASP*POLICY'
NDMPNRLS ='PNODE*C:D*VERSION'
NDMSBLKSZ ='SOURCE*BLKSIZE'
NDMSDSORG ='SOURCE*DSORG'
NDMSLRECL ='SOURCE*LRECL'
NDMSMFID ='SMFID*THAT*CREATED'
NDMSMRLS ='SNODE*C:D*VERSION'
NDMSRECFM ='SOURCE*RECFM'
NDMSTEPOS ='STEP*OFFSET*IN*TCQ'
NDMUSERN='USER*SENSE*FROM*FMH71'
NDMXDATE ='PROCESS*STOP*DATE'
NDMXTIME ='PROCESS*STOP*TIME'
NDMZFLAG='Z*FEATURE*FLAGS'
NDMZWINR ='COMPRESSION*WINDOW*SIZE'
-Apr 6: Reported Truncated CERI and CERT to IBM.
-Apr 16: IBM APAR PI24126 corrects the truncation,
but makes no mention of the truncation. That fix
required reassembly of DGMSMF.
Thanks to Heimir Hauksson, Barclays Technology Center, ENGLAND.
Thanks to Robert Richards, OPM, USA.
Thanks to Walter J Freeman, OPM, USA.
Thanks to Otto A. Burgess, OPM, USA.
Change 36.045 Support for enhanced Mobile Work 4HOUR MSU reporting.
FORMATS -New parameter, TYPE=, for the type of mobile work, to
MOBMWRT be added to your %MOBMWRT invocation in your MOBWRKxx
MOBWRK72 tailored members, where TYPE=DB2 CICS IMS WAS or MQ to
MOBWRK73 create the WORK.MWRT_BLD_SUM_&TYPE dataset that is then
MOBWRKMS used to create the new MOBILE.MSU_&TYPE dataset with the
Feb 28, 2018 4 hour rolling average MSU for that &TYPE of workload.
-MOBWRKMS provides reporting on the new &TYPE datasets.
-Some improvements in SMF70CPA calculation in MOBWRK73,
and ORIGCPUTM/CPUCPONLY/CICDSCPUTM are init to missing
in MOBWRK72.
-FORMAT mwrtdt is enhanced to support years beyond 2042.
Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Change 36.044 The value you set in MACRO _IMSVERS mm.n % is now kept
VMACIMS in variable IMSVERS in IMS0708 and IMS07 datasets.
Mar 1, 2018 (The IMS56FA transaction dataset already has IMSVERSN
that is created from that IMS log record.)
Thanks to Alfredo Gonzalez, La Caixa, SPAIN.
Change 36.043 Initial support for NMON Nigel's Monitor for RHEL Release
EXRHELAA 14i with Red Hat Enterprise Linux 6.7.
EXRHELBP The data with 1 second interval is suspect as the times
EXRHELCI of the interval are often 2 or 3 seconds apart.
EXRHELME The developers page is at 'http://nmon.sourceforge.net'
EXRHELNS The BBBP fields are not currently decoded since the RHEL
EXRHELCD text is not consistent with the NMON contents.
EXRHELDS -Mar 6: FULLCOMD in RHELUARG expanded to 4096 bytes and
EXRHELIN WORK dataset CPUBUSY is deleted; the values of CPU_ALL
EXRHELJF variables are output in RHELINTV Interval Dataset.
EXRHELNT
EXRHELTO DDDDDD MXG MXG
EXRHELUA DATASET DATASET DATASET
EXRHELMT SUFFIX NAME LABEL
IMACRHEL
TYPERHEL RHELAA RHELAAA RHEL MONITOR AAA CONFIGURATION
TYPSRHEL RHELBP RHELBBBP RHEL MONITOR BBBP CONFIGURATION
VMACRHEL RHELCI RHELBBBPCPUINFO RHEL BBBP CPUINFO
VMXGINIT RHELME RHELBBBPMEMINFO RHEL BBBP MEMINFO
Mar 1, 2018 RHELMT RHELBBBPMOUNT RHEL BBBP MOUNT
Mar 6, 2018 RHELNS RHELBBBPNETSTAT RHEL BBBP NETSTAT
Mar 14, 2018 RHELCD RHELCPUD RHEL CPU DETAIL
Mar 28, 2018 RHELDS RHELDISK RHEL DISK
Apr 6, 2018 RHELIN RHELINTV RHEL MONITOR INTERVAL
RHELJF RHELJFSF RHEL JFSFILE
RHELNT RHELNETW RHEL NETWORK
RHELTO RHELTOP RHEL TOP PROCESS
RHELUA RHELUARG RHEL UARG PROCESS
-Apr 6: RHELAAA now output for each concatenated input
file; only the first was output previously.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Thanks to Andreas Windisch, HUK-COBURG, GERMANY.
Change 36.042 ANALCAPD ERROR: FOUND "IF" when expecting ... when the
ANALCAPD CEC= options was used, due to a missing semicolon.
Feb 22, 2018
Thanks to Norbert T. Wagner, Deutsche-Boerse, GERMANY.
Change 36.041 The MXGERROR:MISSING TYPE70 message is now MXGWARN:MISS
VMXG70PR because it's only an alert to be examined (Change 36.026)
Feb 20, 2018 to see if the SYSTEMs listed are the systems of interest.
Only variables in dataset ASUMCELP observations for those
LPARs whose 70s were not read are impacted, and in many
cases the message is generated because the SMF data from
a sandbox LPAR was not present in that day's SMF input.
Thanks to Ed Wieszczek, Zions Bank Corporation, USA.
Change 36.040 Support for IMS 56FA Record APAR UI50912. COMPATIBLE as
VMACIMS it uses a reserved field for the new TPCEXTOF offset to
Feb 19, 2018 the TPCE DSECT, but TPCEXTOF is zero so the extension
is not populated by THIS APAR, so it is also not input.
Thanks to Heimir Hauksson, Barclays, ENGLAND.
Change 36.039 Enhancement to dataset TYPE70PR creates new LPARZIPS with
VMAC7072 the number of online ZIIP engines for each LPAR for each
Feb 19, 2018 interval.
Thanks to Kurt Gramling, TSYS, USA.
Change 36.038 The MXG "INVALID SMF 119 TYPE 81" message in MXG 36.01
VMAC119 bypassed an INPUT STATEMENT EXCEEDED LENGTH ERROR ABEND,
Feb 19, 2018 but I had misunderstood the DS_DOOFF offset to be the
offset into the SMF buffer to the DORU field; IBM L3
Support corrected me: it is the offset into the RU that
will be moved into the DORU field, if the DORU is larger
than 4096 bytes, so that the anomaly's data will be in
in the SMF record. The circumvention is removed and the
DORU variable is correctly populated.
-Variable IST119DS_SID was changed from numeric to char
with $HEX16. format.
Thanks to Gary Zaetz, IBM z/OS Communications Server Support, USA.
Thanks to David Campbell, SUNTRUST, USA.
Change 36.037 Variable QWHSACE was missing from the BY list for dataset
VMACDB2 ZZDB2SBP causing READDB2/TYPEDB2/BUILDPDB to ABEND with
Feb 19, 2018 INPUT STATEMENT EXCEEDED. This code has been executing
and accidentally working since MXG 35.10, last year,
before two site's data records with multiple QWHSACEs
exposed my coding error.
Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.
Thanks to Kare Martin Torsvik, IBM Services, NORWAY
Change 36.036 Support for new Subtype 31 SMF 82 JOB-level crypto stats.
EXTY8228
EXTY8229
EXTY8230
EXTY8240
EXTY8241
EXTY8242
EXTY8243
EXTY8244
EXTY8245
EXTY8246
EXTY8247
IMAC82
VMAC82
VMXGINIT
Feb 14, 2018
During testing of this update, Error Message UNDECLARED
ARRAY YPE8231 (note T is missing) was caused by VMXGINIT
typo setting PTY8231=DEFAULT instead of setting WTY8231.
Just a developers note as for that " YPExxxx" error text
shows up in testing from time to time.
Change 36.035 If the last engine type in an LPAR was an IFL, the MXG
VMAC7072 calculation of LPARSHAR/LPARSHAC and LZIPSHAR/LZIPSHAC
Feb 14, 2018 was incorrect in the TYPE70 dataset.
Thanks to Andrew Petersen, DXC, AUSTRALIA.
Change 36.034 Some debugging options added when MXGEXIMSG=YES and a bad
VGETOBS branch to end modified so that if the dataset you seek
Feb 14, 2018 does not exist and debugging is on you will get the
message that it did not exist.
Change 36.033 Analysis of different I/O counts between SMF 42 subtype 6
ANAL4274 and type74 subtype 1.
Feb 13, 2018
Change 36.032 WebSphere INVALID Subtype 9 messages were cause by the
VMAC120 absence of ELSE clauses that are now corrected.
Feb 12, 2018
Thanks to Jim Horne, Lowe's, USA.
Change 36.031 INVALID DB2 RECORD CREATED BY ASG/TMON is NOT an ASG
VMACDB2H issue, but rather is due to BMC APPTUNE SMF 102 records
Feb 11, 2018 with Data Sharing Group sections that were incorrectly
decoded by MXG logic, now corrected. The ERROR is real
in that observations were NOT output in some datasets.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.030 Old-style substitution macro _HSMINTV added so you can
ASUMHSM easily change the default HOUR interval to you choice.
Feb 6, 2018 If you want the interval to be QTRHOUR and the final
output written to dataset HSM.QTRHOUR, you would use:
%LET MACKEEP=%QUOTE(
MACRO _LSUHSM HSM.QTRHOUR % /* SETS OUTPUT DSN */
MACRO _HSMINTV QTRHOUR % /* SETS INTERVAL */
);
%INCLUDE SOURCLIB(ASUMHSM);
Thanks to Randy Hewitt, DXC, USA.
Change 36.029 Variables SM120RULEXFBOM/DEB/MON/FTRC are one-bit fields
VMAC120 that MXG incorrectly INPUT as one-byte variables.
Feb 8, 2018
Thanks to Paul Volpi, UHC, USA.
Thanks to Jack Hyde, UHC, USA.
Change 36.028 Change 35.124 introduced code that stopped PDBAUDIT with
PDBAUDIT a memory limitation problem with WPS when more than 20
Feb 8, 2018 LIBNAMEs were found. Change 35.201 then accidentally
circumvented that error by removing duplicate entries,
but the real error was that DICTIONARY.MEMBERS returned
all libname.member entries, (THOUSANDS in MXG QA JOB),
rather than the LIBNAME entries from DICTIONARY.LIBNAMES.
The error message is inactive.
Thanks to Earl Kline, Luminex, USA.
Change 36.027 More invalid LENSR=304 and 448 for SMF 42 Subtype 5;
VMAC42 IF LENSR IN(232,240,320,400,448,480) THEN LENSR=160;
Feb 8, 2018 The line was also moved up to after the DO because
those large values with lots of SR segments caused the
MXG test for INVALID SR Length exceeds record length.
The correcting APAR number is OA54663, but it did not
acknowledge the multiplicity of incorrect values when
it "Updated SMF42SRL to contain only length of SMF4205A".
Thanks to Luis Mendoza, Black Knight, USA.
Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.
====== Changes thru 36.026 are in MXG 36.01 dated Feb 6, 2018=========
Change 36.026 MXGERROR:MISSING TYPE70 RECORDS impacts ASUMCEC/ASUMCELP
VMXG70PR datasets, with some incorrect values in those datasets
Feb 5, 2018 when those messages are printed, not just SMF70LAC, when
either the data from a system is not input, or if your
LPARNAME/SYSTEM/SYSNAME/SMF70STN names are inconsistent.
Change 35.144 introduced the message and provided a way
if your SMF70STN matches LPARNAME, but you may need the
below logic to create consistent names.
%LET INCODE70FOR70PR=%QUOTE(
LENGTH SMF70STN $8;
IF SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';
ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';
ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';
IF SYSNAME='ZUT1ACP1' THEN SYSNAME='ACP1';
ELSE IF SYSNAME='ZUT1DEV1' THEN SYSNAME='DEV1';
ELSE IF SYSNAME='ZUT1PRD1' THEN SYSNAME='PRD1';
IF SMF70STN='ZUT1ACP1' THEN SYSTEM='ACP1';
ELSE IF SMF70STN='ZUT1DEV1' THEN SYSTEM='DEV1';
ELSE IF SMF70STN='ZUT1PRD1' THEN SYSTEM='PRD1';
IF SMF70STN='ZUT1ACP1' THEN SMF70STN='ACP1';
ELSE IF SMF70STN='ZUT1DEV1' THEN SMF70STN='DEV1';
ELSE IF SMF70STN='ZUT1PRD1' THEN SMF70STN='PRD1';
IF SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';
ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';
ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';
IF SYSNAME='ZUT1ACP1' THEN SYSNAME='ACP1';
ELSE IF SYSNAME='ZUT1DEV1' THEN SYSNAME='DEV1';
ELSE IF SYSNAME='ZUT1PRD1' THEN SYSNAME='PRD1';
);
%INCLUDE SOURCLIB(ASUM70PR);
Thanks to Ed Wieszczek, Zions Bank, USA.
Change 36.025 Support for zVM64 Level 40061701 and 1702 INCOMPATIBLE.
VMACVMXA Changes to MTRSYS 1.04 for SKIP calculation and MTREND
Feb 6, 2018 1.11 logic required for new instance where the rest of
the record contains only nulls.
Thanks to Graham Harris, RBS, ENGLAND.
Change 36.024 Support for ThruPutManager Release/Version 18.02 COMPAT,
VMACTPMX PTF Level TMT7113, adds new variable JXJBSTXT to dataset
Feb 1, 2018 TYPETPMX, with label 'JXJBSSYSAFF*TEXT'.
Long labels and variables with blank labels corrected.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.023 Yet another ID 42 ST 5 INPUT STATEMENT EXCEEDED due to
VMAC42 yet another invalid LENSR of 232 that should be 160.
Jan 29, 2018 NOW: IF LENSR IN(232,240,320,400,480) THEN LENSR=160;
See Change 35.302 and 35.305 original invalid LENSRs.
IBM APAR OA54663 has been opened to fix the reported
problem. (Note IBM calls it "reported", apparently
until they have accepted and fixed the issue!)
Thanks to Bradley A. Foxhall, BNY, USA.
Change 36.022 Support for Liberty 8.9.1.0 SMF 120 Subtype 100 (COMPAT)
VMAC120 added two new fields to dataset TY120100:
Jan 29, 2018 SM120RULEXSIZE='RULESET*SIZE IN*NUMBER*OF RULES*/
SM120RULEXPNUM='RULESET*NUMBER OF*PARAMETERS*/
-Unknown Subtype logic added to print a hex dump if found.
Thanks to Paul Volpi, UHC, USA.
Thanks to Jack Hyde, UHC, USA.
Change 36.021 Allocation utility VMXGALOC is enhanced so that if your
VMXGALOC have specified DB2KEEP=0 or CICSKEEP=0 or SPINKEEP=0, the
Jan 25, 2018 directories are not created. This is primarily for
specialized tailoring where you want to send output data
to different directories than the normal PDB processing,
as SPIN CICSTRAN and DB2 are neither needed or desirable
with those arguments (DAILYDSN being a good example).
Change 36.020 ASCII version of JCLDAYDS that uses the SAS FTP engine to
ASCIIDSN process TMC and DCOLLECT data.
Jan 25, 2018
Change 36.019 Change to output dataset label to reflect the correct
TRNDDSNS source of the data.
Jan 25, 2018
Change 36.018 Obscure DB2 GTF file ASCII-only conversion utility to
UDB2GTFA assemble 256 byte pieces had the COL=OUTCOL that should
Jan 25, 2018 have been COL=OUTLOC, causing no output records. Was NOT
reported, accidentally discovered. But nasty to find.
Change 36.017 INVALID SMF 119 SUBTYPE 81 RECORD has IST1219DS offset
VMAC119 of 2899 and IST1219DS length of 2164 but the record is
Jan 25, 2018 only 3076 bytes long, causing INPUT STATEMENT EXCEEDED.
Test added to print MXGERROR and delete the record while
opening a problem with IBM support.
Thanks to David Campbell, Suntrust, USA.
Change 36.016 Enhancement to create optional SMFHEADER dataset with
TYPEID selected variable from the SMF header when READSMF=YES
VMXGINIT is used. These two macros (default blank) enable:
Jan 24, 2018 %LET SMFHEADERDATASET1=
PDB.SMFHEADER (KEEP=SYSTEM SMFTIME ID SUBTYPE) ;
%LET SMFHEADERDATASET2=
%QUOTE( OUTPUT PDB.SMFHEADER; ) ;
%ANALID(READSMF=YES,PRINT=YES,PDBOUT=PDB);
Thanks to Randy Hewitt, DXC, USA.
Change 36.015 Variable CPUID $EBCDIC8 ERROR when TYPEBETA and TYPE70
VMACBETA records were processed together - CPUID is a numeric but
Jan 24, 2018 VMACBETA had an incorrect/old BETA93 reference.
Thanks to Lothar Koppe, Provinzial, GERMANY.
Change 36.014 ANALHSM Report 3 Title was overlaid if BYVAL was used.
ANALHSM
Jan 22, 2018
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.013 Documentation only. APAR OA27291 corrects ABEND S0C4 if
NEWSLTRS USEZOSV1R9RULE(NO), the default, is used with Netview
Jan 22, 2018 NvDM at z/OS 1.10 or higher, in DIAGxx member of parmlib.
Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.
Change 36.012 The created GMTOFF30 value could be .01 seconds more or
VMAC30 .01 less than the exact hourly offset when SMF30IST was
Jan 22, 2018 not the same second as INTBTIME, complicated by the two
different resolutions, .01 in SMF30IST/SMFSTAMP8/local,
.000001 in the higher resolution INTBTIME/TODSTAMP/GMT,
the only source of the GMT delta in SMF 30s. This change
impacts variables ACTDLYTM EXECTM INTBTIME INTETIME and
SYNCTIME with the PROC COMPARE difference less than .01.
And note that if you have not specified SYNC in SMFPRMxx,
the TYPE30_V/SMFINTRV datasets are useless for any type
of interval totals.
Change 36.011 -MXG 35.09-36. Using %PDBAUDIT(LIBNAMES='Not _ALL_",
PDBAUDIT overriding the internal _ALL_ default, the program
Jan 19, 2018 failed with a syntax error pointing to a Paren.
-If LIBNAMES=PDB was used, and //PDB DD is tape, the
program fails with PDB.PDBAUDIT NOT FOUND, because the
option EXCLUDESEQ=YES is the default to NOT READ tape
PDB libraries. Now, if your PDBAUDIT= is on tape, and
EXCLUDESEQ=YES, the program will tell you that you must
change that to NO, so the program will report on the
contents of the tape Data Library, but there is no output
of the PDB.PDBAUDIT dataset to that tape, as that could
destroy existing datasets on the sequential mode tape.
It is NOT recommended that you build your PDB on tape
because of performance issues: tapes have no directory
so the full tape has to be read to determine its contents
for PDBAUDIT, and worse for BUILDPDB, where datasets are
written AND read-from the //PDB, each reference has to
start at the beginning of the tape and read all data
to get to that dataset.
-If you do want your daily PDB on tape, you should write
to temp DASD for the //PDB, to eliminate the rereads, and
then PROC COPY from //PDB to tape after all your reports
were created from the temp DASD PDB. And, since this PDB
for BUILDPDB is NOT on tape, PDB.PDBAUDIT will be created
and output to the temp PDB so it is included in the copy.
-Note that if you do use EXCLUDESEQ=NO with PDB on tape,
there are no observation counts in the PDBAUDIT reports.
Thanks to Peter Ten Eyck, American National, USA.
Change 36.010 TYPE73 dataset variable CHFXRATE should have been divided
VMAC73 SMF73PTI, the corrected elapsed time, and not by DURATM.
Jan 18, 2018
Thanks to Steve Olenik, IBM, USA.
Change 36.009 Message: INVALID TYPE 0 RECORD with LENGTH=70 was deleted
VMAC0 but that length is now valid when SMF0TBUF was added, but
Jan 18, 2018 its length was not added to the test for valid lengths.
The test for each valid TYPE 0 record length is needed
because, many times, sysprogs installing a product that
writes SMF records, incorrectly fail to set a record ID
and the product writes type 0 records, which were not
valid IPL records, and thus were deleted by MXG, with
the message. I failed to add 70 to the test.
-And, this site had records that were LENGTH=52 that are
not IPL records, accidentally written. Do you recognize
what product has values like these in that record?:
CHAR ;... 3....E09ZBLOK. .. 3....LIDPOST BLKLDPSTLOADED 52
ZONE 5003DF0101CFFECDDD0503DF0101DCCDDEE4CDDDCDEEDDCCCC44
NUMR E000B3181F509923622800B3181F394762302323472336145400
Thanks to Bruce Sloss, PNC, USA.
Change 36.008 Variable TTAPLDAT in dataset TYP11902 was mis-aligned due
VMAC119 to INPUT that should have been INPUT @OFF11905 TTAPLDAT.
Jan 15, 2018
Thanks to Bob Davidson, LloydsBanking, ENGLAND.
Change 36.007 Scott Barry posted the UTILBPV program to examine the BVP
UTILBPV cylinder value to minimize wasted space in the Cylinder
Jan 15, 2018 Managed Area using EAV Volumes, using your DCOLLECT data.
Datasets larger than the BPV value are written to the
Cylinder-Managed Space, while dataset smaller than BPV
are written to the Track-Managed Space.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.006 -CICS/TS 5.3 new CPU variables in Statistics CICM dataset:
VMAC110 MNGCPUT ='TOTAL*CPU*TIME'
Jan 15, 2018 MNGTONCP='TOTAL*CPU*TIME*ON CP'
MNGOFLCP='TOTAL*CPU*TIME*OFFLOAD*ON CP'
-Variable MNGWLMCC now tests the correct bit.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.005 -TYPE115 header variable QWHSDURN in SMF 115 subtype 231
VMACDB2H has a value that requires a divide by 4096, while that
VMAC115 same field in all other SMF 115 subtypes is microseconds.
Jan 18, 2018 -Header variable QWHSTIME and QWHSDURN are added to all
Feb 2, 2018 datasets that have the 52-byte DB2 QWHS header segment:
MQMLOG MQMBUFER MQMCHIN MQMDSP MQMADP MQMSSL MQMDNS
TYPE115201 TYPE115215, subtypes 1, 201, 215, and 213.
-Variable QIS1EXPF is INPUT and kept in TYP115201 dataset.
-The BY lists for 1155/115A/115L/115N were revised and now
duplicates are removed (the 1155 and 1156 have MANY dupes
normally).
-Variables QSSTCN64/QSSTCR64, ABOVE THE BAR CONTRACTIONS
and SHORT ON STORAGE counts added to MQMLOG dataset.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.004 Correction for DB2 V11 IFCID 376 INPUT STATEMENT EXCEEDED
VMAC102 STOPOVER ERROR because the code incorrectly expected the
Jan 14, 2018 V12 truncated offsets that are now unread with DB2 V11.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.003 -TYPE70TR TRG dataset misalignment was corrected when data
VMAC7072 records were received from IBM, but with these questions:
VMAC89 Split 70 records have a 70 TRG segment in each record,
Jan 17, 2018 and the second record's TRG data is identical.
-TYPE72TR TRG dataset has negative values for R723TSUCP:
IBM RMF replies: Negative values can occur in certain
cases. When transaction processor usage is reported to
WLM through IWM4RPT or IWM4MNTF services, the consumed
service units are accounted to the transaction service or
report classes, and deducted from the region's service
and report classes. If the number of transactions is very
small and a single transaction reports high processor
times, it can occur that processor times become negative.
R723CETSX is natively in "squared microseconds" but is
converted to "squared millisecs" to match R723CETS units.
-TYPE89 documentation had offset at 64 with length 80, but
actual offset/length are 36/52, causing the original MXG
code to not INPUT the TRG TRO/TCO segments, so datasets
TYPE80TI, TYPE89R1, and TYPE89R2 had zero observations.
-With these changes, Tenant Resource Group, TRG datasets
have been validated with data.
Change 36.002 See Change 36.135.
VMACPOEX
Jul 20, 2018
Change 36.001 TYPETCP (SMF 118) APISTART datetime was on GMT, the only
VMACTCP field with SMFSTAMP informat not on local time zone.
Jan 9, 2018 Labels with MBYTES changed to BYTES since they all use
the MGBYTES format that prints the suffix letter.
Thanks to Randy Hewitt, DXC Technology, USA.
LASTCHANGE: Version 36.
=========================member=CHANGE35================================
/* COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA */
Annual MXG Version 35.36 was dated Jan 8, 2018, thru Change 35.309
MXG Version 35.35 was dated Jan 3, 2018, thru Change 35.303
MXG Version 35.12 was dated Dec 26, 2017, thru Change 35.298
EA test MXG Version 35.12 was dated Dec 20, 2017, thru Change 35.294
MXG Version 35.11 was dated Dec 1, 2017, thru Change 35.279
MXG Version 35.10 was dated Nov 6, 2017, thru Change 35.255
First MXG Version 35.10 was dated Nov 6, 2017, thru Change 35.254
MXG Version 35.09 was dated Oct 2, 2017, thru Change 35.217
First MXG Version 35.09 was dated Oct 2, 2017, thru Change 35.215
MXG Version 35.08 was dated Aug 24, 2017, thru Change 35.186
MXG Version 35.07 was dated Aug 2, 2017, thru Change 35.171
MXG Version 35.06 was dated Jun 30, 2017, thru Change 35.151
MXG Version 35.05 was dated May 15, 2017, thru Change 35.121
MXG Version 35.04 was dated May 1, 2017, thru Change 35.104
\XG Version 35.03 is dated Mar 27, 2017, thru Change 35.072
First MXG Version 35.03 was dated Mar 22, 2017, thru Change 35.069
MXG Version 35.02 was dated Feb 10, 2017, thru Change 35.035
MXG Version 35.01 was dated Jan 20, 2017, thru Change 35.014
ANNUAL MXG Version 34.34 was dated Jan 3, 2017, thru Change 34.284
ANNUAL MXG Version 34.34 was dated Jan 3, 2017, thru Change 34.284
MXG Newsletter SIXTY-NINE was dated Jan 3, 2018.
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 35.36 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 35.36.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest
and is updated with new notes frequently. All Newsletters are online
at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
All MXG changes are also online at http://www.mxg.com, in "Changes".
========================================================================
I. MXG Version 35.36 dated Jan 8, 2018, thru Change 35.309.
==Major CHANGES added in MXG 35.36, dated Jan 8, 2018 thru 35.309.
ERROR Protection:
Many 35.308 SAS Defect 9.4 M5 z/OS PROC SQL NOERRORSTOP protect.
SAS Note 61672 will address, this circumvents need.
ERROR Correction:
TYPE42 35.305 Third incorrect SRLEN STOPOVER correction.
ANALDB2R 35.307 Broken DO Syntax, 35.11-35.35, if PDBOUT=PDB is used.
UTILBLDP 35.306 SUPPRESS=74 variable DEVN NOT FOUND ERROR.
VGETxxxx 35.309 Protection for DATASET=PDB.dataset syntax.
==Major CHANGES added in MXG 35.35, dated Jan 3, 2018 thru 35.303.
New Products Support
MDIJCL 35.299 Support for Luminex MDI box to run MXG on Linux.
Error Corrections
TYPE42 35.302 Incorrect SRLEN in SMF 42 Subtype 5 APAR STOPOVER.
TYPERMFV 35.300 CPUPHYAD format could fail causing ABEND.
==Major CHANGES added in MXG 35.12, dated Dec 26, 2017 thru 35.298.
New Products Support
TYPE7072 35.285 Support for Container Pricing, new TYPE72TR dataset.
TYPEBETA 35.297 Support for BETA 93 Version 610 (update) 620 (added).
TYPE0203 35.283 Support for APAR OA52828, SMF Temporary Buffer size.
TYPEQACS 35.288 Support for QAPMDISK with LENGTH=695.
TYPE42 35.289 TYPE42 APARs OA52132, OA52133, OA61734 now tested.
Error Corrections
TYPERMFV 35.287 MXG 35.10/35.11 RMF III ZRBASI ASICPUTA was WRONG.
Enhancements
TYPEDB2 35.280 Exit Members EXDB2STS and _EDB2STS are now valid.
RMFINTRV 35.282 New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.
TYPE70 35.282 New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.
UTILEXCL 35.293 &MXGCIEXC "exit" to correct USER CMODHEAD typos.
UTILCMPR 35.292 Utility compares numeric variables in OLD/NEW dataset
==Major CHANGES added in MXG 35.11, dated Dec 1, 2017 thru 35.279.
New Products Support
TYPE42 35.274 Support for APAR OA53110 new TYPE42 variables.
TYPE74 35.273 Support for APAR OA50761 Virtual Flash memory.
TYPE89 35.271 Support for Container Pricing in SMF 89.
TYPE70 35.270 Support for Container Pricing in SMF 70.
TYPE113 35.279 Support for Dec 2017 z14 CPU MF formula update.
Error Corrections
TYPERMFV 35.259 35.10: ZRBASI deaccumulation was not correct.
TYPEDB2 35.267 DB2 Netezza IDAA variables Q8STxxxx corrected.
TYPEDB2 35.277 New IFCID=225 QWA225PRISTG_PAGE variable added.
VMACSMF 35.266 SMF ID=2 SYSTEM=DUMY 14 byte records protected.
CICINTRV 35.264 CICDS Dispatch dataset DISP+WAIT GE Interval DURATM.
TYPEBVIR 35.260 BVIR History updated for 3.3 media codes and BVIR302.
TYPEPOEX 35.257 Protection for truncated Power Exchange SMF record.
TYPETMS5 35.278 Correction for TMS Stacked Tape Files wrong values.
Enhancements
TYPE102 35.262 New DB2 zPARMS variables created in T102S106 dataset.
TYPETPMX 35.261 Execution time for TYPETPMX halved by restructure.
TYPERMFV 35.259 New ZRBLCPLPAR dataset with per-LPAR totals.
TYPERMFV 35.259 IBM 4HR MSU (CPUAVB4H) in ZRBCPU per) interval.
VMXGSET 35.256 Example to read "concatenated" PDBs with PROC SQL.
==Major CHANGES added in MXG 35.10, dated Nov 6, 2017 thru 35.255.
New Products Support
TYPERMFV 35.249 Support for z/OS 2.3 RMF III CPUG3 ZRBCPU changes.
TYPE113 35.246 SMF113/HIS formula for z14 L3P/RNI/SM1132SP changed.
TYPEPOEX 35.242 Support for Power Exchange Version 10.1.1.
TYPE42 35.240 Support for APARS OA52132/OA52133/OA61734 UNTESTED.
Error Corrections
TYPE119 35.220 Zero observations in TYP11920 dataset.
TYPE119 35.245 SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED.
TYPEDB2 35.229 PDB.DB2STATB/STSBP protection for large gaps in data.
TYPEDB2 35.248 Four QWA225 and QWB225 variables now kept/input.
FORMATS 35.243 MOBILE WORK CSV files for CICS/TS 5.3 missing prod.
ANAL118 35.241 Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.
TYPEXAM 35.218 XAMSYPUP dataset variables are now correctly aligned.
TYPEXAM 35.223 zVPS/XAM extra SYTCUP with totals is now decoded.
TYPEVMXA 35.221 zVM MONWRITE VXPRCPUP dataset corrected.
Enhancements
GRAFCEC 35.230 Replaces GRAFLPR, CPU/zIIP/4HR MSU graphs.
UTILBLDP 35.225 New EXPDBVAR/EXPDBCDE/EXPDBOUT to create subset.
BUILDPDB 35.234 New EXPDBKEP lets you KEEP=/DROP= vars in JOBS/STEPS+
TYPE80A 35.231 RACFDIRECTED allows DELETE of RACF records DTP=44.
DEDUP701 35.236 Duplicate 70 Subtype 1 records can cause bad results.
TYPERMFV 35.235 RMF III ZRBCPU enhanced with decodes of CPC_HOMEFLAG.
TYPE116 35.219 MQMACCT variable NETSNAME new format decoded.
UTILEXCL 35.228 Support for 20 user character fields in CICSTRAN.
==Major CHANGES added in MXG 35.09, dated Oct 2, 2017 thru 35.225.
MXG 35.09+ is required for:
z14 processor, ONLY the SMF 113 records were incompatibly changed.
z/OS 2.3 SMF 2 and 90 records incompatibly changed.
z/VM 6.1.17.1 MONWRITE records incompatibly changed.
Error Corrections
TYPE0203 35.190 SMF type 2 subtype 2 (SMF Signature enabled) STOPOVER
TYPEVMXA 35.203 z/VM 6.4.17.1 INCOMPATIBLE fields.
TYPENMON 35.208 Nigel's Monitor changed HH:MM to N MINS, INCOMPAT.
TYPE90A 35.199 z/OS 2.3 type 90 subtype 38 INPUT STATEMENT EXCEEDED
New Products Support
TYPE113 35.310 Support for z14 SMF type 113 (INCOMPATIBLE).
TYPEBETA 35.209 Support for BETA 93 Version 610 (INCOMPATIBLE).
TYPEBE97 35.196 Support for BETA 97 Extended 610 Header (INCOMPATIBL)
TYPE102 35.204 Support for new IFCID 376 variables in T102S376.
TYPERMFV 35.191 Support for z/OS 2.3 ZRBASI and ZRBUWD new fields.
TYPEXAM 35.195 Support for zVPS XAM XAMPUP segment.
TYPE6156 35.207 TYPE6156 enhancement adds FIRSTGEN and LASTGEN.
BUILD005 35.206 New %LET SPINSTC=365 keeps STC Account fields longer.
TYPE30 35.205 Documentation of what is counted in SMF 30 EXCPs.
TYPECIMS 35.197 IMF variables STRTTIME/ENDTIME now in microseconds.
Many 35.194 Unrequested log messages MXGDEBUG: VMXGOPTR
BLDSMPDB 35.200 New daily/weekly/monthly optional paths.
TYPE74 35.193 Alignment for sync I/O variables.
TYPE116 35.192 MQMQUEUE INTS/STRT populated in subtype 2 records.
==Major CHANGES added in MXG 35.08, dated Aug 24, 2017 thru 35.186.
Error Corrections
TYPE74 35.182 MXG 34.07 INPUT STATEMENT EXCEEDED RMF 74 SUBTYPE 8.
TYPE92 35.180 SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED RECORD.
TYPEVMXA 35.174A MONWRITE VXBYUSR _MT1 and _PRO (SMT times) corrected.
TYPEROSC 35.177 PDB.ROSCOE, ROSIGNON Logon Time, CONNECTM, corrected.
New Products Support
TYPE119 35.173 Support for SMF 119 Subtype 11 Zert record.
TYPE102 35.183 IFCIDs 389,404,413,414,477 support.
TYPEBBMQ 35.176 Support for BBMQ QSDSTYPE='DISTRIBUTED SYSTEM TYPE'.
BUILDPDB 35.174 CPITCITM/CPISRITM Init, CPITCTTM/CPISRTTM added.
==Major CHANGES added in MXG 35.07, dated Aug 2, 2017 thru 35.171.
New Products Support
TYPEmany 35.166 Support for z/OS 2.3, many additions.
TYPEVMXA 35.165 New variables added to VXMTRMEM dataset.
TYPEXAM 35.164 New variables added to XAMSYS dataset.
TYPEZDP 35.162 Support for Dell/EMC Mainframe Enabler zDP
TYPEMVCI 35.161 Support for BMC Mainview/CICS Version 7.1.
TYPEAXWY 35.150 Support for AXWAY Version 3.1.3, incomplete.
IMACICWU 35.158 Support for Mainview/CICS 7.1 SMF 110 BMCMVCIC.
TYPEBE97 35.152 Support for Beta 97 Subtype 22 for version 430/610.
Error Corrections
ASUMUOW 35.157 Variable DB2TCBTM removed from CPUUOWTM.
TYPETPX 35.155 STOPOVER when IP Port was changed from 4 to 5 digit.
ASMRMFV 35.154 STOPOVER using TYPERMFV if UWD records are created.
TYPE7002 35.153 IBM RMF CRYPTO report TOTAL EXEC is AVERAGE EXEC.
==Major CHANGES added in MXG 35.06, dated Jun 30, 2017 thru 35.151.
Error Corrections
ASMRMFV 35.148 Must specify both SVP and RCD for RMF III CPUTM
TYPERMFV 35.148 RMF III CPUTM wrong if RCD without SVP selected.
TYPEVMXA 35.145 zVM SMT INTERVAL vars were incorrectly DIF()'d.
TYPE74 35.146 TYPE749 Corrections, vars R749FPGBYTx, and R749Dxxx.
TYPE103 35.134 Dataset TYPE103D vars T103DBYT/T103DREQ corrected.
TYPEVMXA 35.131 Variable CALENMT incorrect, new CALSHARE variable.
TYPE30_6 35.127 Negative values for Early Address Spaces corrected.
TYPE30_6 35.127 Negative values for Early Address Spaces corrected.
VMAC38 35.136 NETVIEW ID=38 unexpected S38CCALR length corrected.
New Products Support
TYPE42 35.137 APAR OA44319 improves accuracy for I/O durations.
TYPE991 35.123 New z/OS 2.2 variables added to TYPE991 dataset.
TYPEVMXA 35.132 Support for zVM 6.4 APAR VM66026 new variables.
TYPEBETA 35.139 BETA93 and BETA97 Subtype 25 restructure support.
TYPEXAM 35.147 Support for XAM new VSIDSK and XAMPRC segments.
Enhancements
UTILBLDX 35.149 New BUILDJCL=YES creates IFASMFDP code to select SMF.
SIGNIFICANT CPU SAVINGS for Ad Hoc SMF read when only
a few SMF records are wanted from a large file.
See Change Text. Will replace UTILBLDP next version.
ASUM70PR 35.150 Option %LET CECONLY=YES creates ASUMCEC/ASUMCELP only
ASUM70PR 35.144 MXGERROR:MISSING TYPE 70 RECORDS message.
TYPE113 35.141 SMF 113 Formula for RNI updated for z13.
IMACINIT 35.128 Note: OPTIONS NOCAPSOUT recommended for ODS users.
ASMRMFV 35.135 RMF III Enhancements, Filtering.
UTILBLDP 35.143 Options SUPPRESS enhanced, NEVER corrected.
==Major CHANGES added in MXG 35.05, dated May 15, 2017 thru 35.121.
Error Corrections
TYPEDB2 35.111 DB2 12.1 INVALID QLAC, CONTINUOUS DELIVERY CAUSED.
THIS IS IMPORTANT: LOOK FOR INVALID QLAC ERROR ON
YOUR SAS LOG - OBSERVATIONS ARE NOT OUTPUT.
THE FIELDS WERE INSERTED BY APAR PI74456.
TYPE7072 35.113 35.04 only. TYPE79 SHARE weights wrong, ASUMCELP ok.
VMXGPRNT 35.120 WPS only, MXG 35.04 Only, Blank Label ERROR.
VMXGFIND 35.117 Multiple input PDBs were read, only one was output.
JCLTEST9 35.116 35.04 only. //MVJEIN DD in wrong step.
VGETSORT 35.112 35.04 only. ERROR Truncated SORTBY (name GT 32).
TYPE129 35.109 Variables SM1209EX/EY/EZ/FA were dropped.
ANALID 35.108 ANALID report TITLE for BUILDPDB can be tailored.
New Products Support
TYPEIAM 35.107 Support for IAM Version 9.0.
Enhancements
TYPE110 35.105 CICS duration fields are now formatted TIME16.6.
==Major CHANGES added in MXG 35.04, dated May 1, 2017 thru 35.104.
Error Corrections
TYPE7072 35.093 MXG 35.03 only. PLATBUSY/PCTOF HDW TYPE70/RMFINTRV.
TYPEVMXA 35.079 z/VM 6.3 SMT in VXSYTPRP, VXAPLSO0 corrections.
TYPEXAM 35.074 Velocity XAM SYTCPU invalid errors at vendor.
TYPEDB2 35.081 DB2ACCTP, truncated QPACLOCN/COLN/PKID/ASCH/AANM
New Products Support
TYPEMVJE 35.094 Support for BMC Mainview for Java Environment.
TYPEVMXA 35.092 Updated support for z/VM 6.4 (INCOMPAT, SYTLCK).
Enhancements
ANALFTP 35.087 New ANALFTP analysis provided five new reports.
ANALCNCR 35.091 New example count/plot concurrent TELNET sessions.
IHDRNDM 35.089 New NDM-CDI IHDRNDM exit for NDMRTYPE selection.
BUILDPDB 35.088 Running MXG on ASCII, free SMF alloc at read end.
TYPEOPSS 35.090 Support for CA's OPSS Product User SMF Record.
==Major CHANGES added in MXG 35.03, dated Mar 27, 2017 thru 35.072.
VMAC1415 35.072 First MXG 35.03. Debug HEX DUMPS on log, no ERROR.
Not serious, but easily corrected with this update.
==Major CHANGES added in MXG 35.03, dated Mar 22, 2017 thru 35.069.
Significant Correction/Documentation
TYPE7072 35.064 SMT Mode corrections, "Inflated" CPUZIPTM in MT=2
ONLY IMPACTS 72 and 30 - TYPE 70 DATA JUST FINE!
New Products Support
TYPE110 35.069 Support for CICS/TS 5.4 BETA 11 CICSTRAN new vars.
TYPESVIE 35.059 Support for CA SYSVIEW for IMS 14, missing values.
TYPEIMS 35.058 Support for IMS LOG 67D0 DIAGNOSTIC DC Log Record.
TYPEMVIP 35.055 Support for Mainview for IP PTF BPN2331 adds flag.
TYPE120 35.051 Support for Liberty 17.0.0.1 SMF 120 ST 12 new data.
TYPEOPC 35.048 Support for IWS/TWS/OPC Version 9.3 ST 66 was ST 23.
TYPE102 35.047 Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.
TYPE102 35.046 Support for IFCID 125 Truncated fields.
TYPEVMXA 35.040 Support for Velocity ZWRITE z/VM MONWRITE records.
TYPEXAM 35.063 Support for XAMSYS wrong length, XMTCPSYS NAMENODE.
TYPEMVCI 35.062 Support for Mainview CICS CMRDETL file VER 6700.
TYPE30 35.066 APAR OA59593 adds INELIGHONOR flag to SMF 30s.
Enhancements
TYPEDCOL 35.064A Multi-Volume DCOLDSET fields retained & populated.
ASUMCELP 35.061 Variable SMT_NUM added to PDB.ASUMCELP with MT mode.
TYPE120 35.060 SMF 120 ST 11 TYP120BL CP and zIIP variables added.
GRAFCAPS 35.042 Example report of Resource Group CPU use and CAPPING.
ASUM70PR 35.061 Enhancement adds SMT_NUM to PDB.ASUMCELP dataset.
TYPE120 35.060 Enhancement adds TOTAL/CP ONLY/ZIP CPU to TYP120BL.
ASMRMFV 35.054 RMF Monitor III Enhancement for OPD data filtering.
ASUM70PR 35.050 Error message if PDB.ASUMCELP does not have all 70s.
Corrections
VMXGSUM 35.056 Correction for KEEPMNTH= (very rarely used) option.
TYPERMFV 35.044 ZRBCP SMT vars missing, new CPC_CECNAME variable.
TYPE1415 35.040A IBM APAR OA51325 corrects missing UCB segment.
CICINTRV 35.038 MXG correction for ITRM to NOT delete CICINTRV
==Major CHANGES added in MXG 35.02, dated Feb 10, 2017 thru 35.035.
Execution Errors Corrected:
VMXGSUM 35.022 COMPBL too few arg, VARIABLE QWACBSC ALREADY...
Rare and obscure, only three reports, but nasty
if encountered deep in your daily run, so please
"drop in" 35.02, which is a very good LEVEL SET.
VMXGSUM 35.020 MXG 35.01. Ignore MXGWARN VMXGSUM BACKLEVEL msg.
UTILEXCL 35.023 MXG 35.01.Old Dictionary Records were not used.
TYPEVMXA 35.025 Using _VMINPUT. z/VM variable VMDUSER was 1 byte.
Variables corrected:
TYPEDB2 35.027 DB2STATS QISTxxxx Storage multiplied by 4K vs 1K.
TYPE78 35.021 TYPE78PA variables R782LSMO/GMFO/GFRR are wrong.
GRAFWRKX 35.018 WARNING but ZIPTM, IFATM, and ZIETM were not plotted.
TYPE120 35.024 Subtype 9 variables SMF1209EV,FI,EW no longer kept.
VMXGALOC 35.033 Month begin/logic revised, MNTHKEEP zero protected
TYPE42 35.031 Variable S42DSIOS added to TYPE42DS.
TYPEDB2 35.030 DB2STAT4 _REAL variables way too large.
New Products Support
TYPE102 35.017 New DB2 ZPARMS added to T102S106 dataset.
TYPE117 35.015 Support for SMF 117 GTZ record.
TYPE125 35.015 Support for SMF 125 GTZ record, untested.
TYPE80A 35.029 RACFTYPE=6 seg increased in length, message, no fail.
TYPERMFV 35.028 New RMF III ZRBENC "long names" now input and kept.
IMACDBNZ 35.027 Support for DB2ACCT NETEZZA Q8AC "Accumu" variables.
TYPEBBMQ 35.034 Support for BBMQ BMC Utility BBM9MD73 restructure.
Enhancements
UTILRMFI 35.026 Enhanced reporting if SRVCVLASS=SYSOTHER detected.
TYPETPX 35.035 Protection for invalid TPX subtype 7 record.
==Major CHANGES added in MXG 35.01, dated Jan 20, 2017 thru 35.015.
POTENTIALLY SERIOUS Error Corrected:
RMFINTRV 35.006 Duplicate RMFINTRV if Multiple Capacity Groups exist.
Culprit was MXG's addition of variable SMF70GNM to PDB.RMFINTRV
back in MXG 34.01 in Feb, 2016, but only reported now by only
two sites. THERE IS NO ERROR MESSAGE ON THE LOG.
PROC FREQ DATA=PDB.RMFINTRV; TABLES SMF70GNM;
will show if you are exposed. %INCLUDE SOURCLIB(RMFINTRV);
with //PDB DD DISP=OLD with this Change will rebuild
PDB.RMFINTRV correctly for each mis-built PDB data library.
Errors Corrected:
UTILEXCL 35.004 ERROR PDB.CICSDICT not FOUND - USE THIS UTILEXCL.
TYPE115 35.011 For local time zones with +GMT, GMT115TM wrong.
TYPE120 35.007 Liberty SMF 120 st 12 SM120CCC/CCD Year 2027.
TYPEPOEX 35.002 INVALID SMF Records caused STOPOVER ABEND.
TYPEOSEM 35.010 OSEM User SMF INPUT EXCEEDED, invalid, circumvented.
New Products Support
TYPE71 35.009 Support for APAR OA48913 with 2GB Memory Frames
Enhancements
TYPERMFV 35.005 Dataset ZRBLCP obs created for ONLINE LCPUADDRs.
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes.
All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M5 (9.4M5), "M5",
or "SAS 9.4 (TS04.01M5P09132017)" if the OPTION VERSIONLONG is
enabled.
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
that will be corrected in SAS Note 61672 defect. See Change 35.309
for more details on using NOERRORSTOP for your own PROC SQLs.
SAS V9.4 M5 Is RECOMMENDED, but MXG executes without error
using SAS Version 9.4 M0-M4 or SAS Version 9.3 M0-M2.
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 DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
or you can continue to use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 35.36 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and
Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,
but MXG users execute MXG on MANY (ALL??) SAS platforms, including
AIX, Linux, and other 'nix' variants, on many different hardware
platforms, and since they all work we don't need to list them. If
SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.
and other errors with 3.00 or 3.01 have been corrected in the
current WPS version.
WPS Version 3.01.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was
INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to
read the SMT-format RMF records (which are written if you have zIIP
engines AND have enabled the new PROCVIEW CORE option for
Multi-Threading, even if only one thread is enabled).
The new zEDC compression hardware requires MXG 33.07 to support the
new metrics.
For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.
Availability dates for the IBM products and MXG version required for
error-free processing of that product's data records:
Product's
Availability MXG Version
Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8
MVS/ESA 4.2 Mar 29, 1991 9.9
MVS/ESA 4.2.2 Aug 15, 1991 9.9
MVS/ESA 4.3 Mar 23, 1993 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30, 1996 14.05
OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02
OS/390 2.4.0 Sep 28, 1997 15.06
OS/390 2.5.0 Feb 24, 1998 15.06
OS/390 2.6.0 Sep 24, 1998 16.04
OS/390 2.7.0 Mar 26, 1999 16.09
OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
z/OS 1.1 on 2064s Mar 30, 2001 19.01
z/OS 1.1 with correct MSU Mar 30, 2001 19.02
z/OS 1.2 Oct 31, 2001 19.04
z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05
z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.4 Tolerate Sep 27, 2002 20.03
z/OS 1.4 Support Sep 27, 2002 20.06
z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02
z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04
z/OS 1.5 Mar 31, 2004 21.21
z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10
z/OS IRD TYPE70PR Mar 11, 2004 *24.10
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10
z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10
z/OS IFA data in RMF 79s Sep 30, 2005 23.10
z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03
z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06
z/OS More than 32 LPARs Jan 30, 2006 *24.24
z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24
z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02
z/OS IRD errors corrected May 15, 2006 24.03
z/OS ASUMCEC errors corrected May 15, 2006 *24.24
z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24
z/OS zIIP Processor Support Jun 22, 2006 *24.24
z/OS Dedicated zIIP Support Mar 8, 2008 *26.01
z/OS Dedicated zAAP Support Mar 8, 2008 26.01
z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24
z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10
z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10
z/OS new z10 variables Mar 5, 2008 26.01
z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05
z/OS 1.11 Sep 2, 2009 27.08
z/OS 1.11 New 30 variables Apr 14, 2010 *28.02
z/OS 1.12 Aug 17, 2010 *28.05
z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03
z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06
z/OS 1.13 Sep 30, 2011 29.03
z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08
z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01
z/OS 2.1 - Most Records support Jul 23, 2013 30.05
z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07
z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03
z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03
z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10
z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08
z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09
REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09
z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02
z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02
z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07
z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07
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*
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 Records INCOMPAT Oct 2, 2017 35.09
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
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
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.13
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
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
ACF2 6.2 16.04
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
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2 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 35.36.
1. Incompatibilities introduced in MXG 35.36:
a- Changes in MXG architecture made between 35.36 and prior versions
that can introduce known incompatibilities.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
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 35.36 after MXG 34.34:
Dataset/
Member Change Description
Many 35.308 SAS Defect 9.4 M5 PROC SQL NOERRORSTOP circumvention.
Many 35.166 Support for z/OS 2.3 (many new variables), COMPAT.
Many 35.194 Unrequested log messages MXGDEBUG: VMXGOPTR
ANAL118 35.241 Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.
ANALCNCR 35.091 New example count/plot concurrent TELNET sessions.
ANALDB2R 35.307 Broken DO Syntax in 35.11-35.35 if PDBOUT=PDB is used
ANALFTP 35.087 New ANALFTP analysis provided five new reports.
ANALID 35.108 ANALID report TITLE for BUILDPDB can be tailored.
ASMRMFV 35.054 RMF Monitor III Enhancement for OPD data filtering.
ASMRMFV 35.135 RMF III Enhancements, Filtering.
ASMRMFV 35.148 Must specify both SVP and RCD for RMF III CPUTM
ASMRMFV 35.154 STOPOVER using TYPERMFV if UWD records are created.
ASUM70PR 35.050 Error message if PDB.ASUMCELP does not have all 70s.
ASUM70PR 35.061 Enhancement adds SMT_NUM to PDB.ASUMCELP dataset.
ASUM70PR 35.144 MXGERROR:MISSING TYPE 70 RECORDS message.
ASUM70PR 35.150 Option %LET CECONLY=YES creates ASUMCEC/ASUMCELP only
ASUMCELP 35.061 Variable SMT_NUM added to PDB.ASUMCELP with MT mode.
ASUMUOW 35.157 Variable DB2TCBTM removed from CPUUOWTM.
BLDSMPDB 35.167 VGETSORT revisions for PDB name, internal.
BLDSMPDB 35.200 New daily/weekly/monthly optional paths.
BUILD005 35.206 New %LET SPINSTC=365 keeps STC Account fields longer.
BUILDPDB 35.088 Running MXG on ASCII, free SMF alloc at read end.
BUILDPDB 35.174 CPITCITM/CPISRITM Init, CPITCTTM/CPISRTTM added.
BUILDPDB 35.234 New EXPDBKEP lets you KEEP=/DROP= vars in JOBS/STEPS+
CICINTRV 35.038 MXG correction for ITRM to NOT delete CICINTRV
CICINTRV 35.264 CICDS Dispatch dataset DISP+WAIT GE Interval DURATM.
DEDUP701 35.236 Duplicate 70 Subtype 1 records can cause bad results.
FORMATS 35.243 MOBILE WORK CSV files for CICS/TS 5.3 missing prod.
GRAFCAPS 35.042 Example report of Resource Group CPU use and CAPPING.
GRAFCEC 35.230 New graphs CPU/zip Hours/4HR MSU, replaces GRAFLPAR.
GRAFCEC 35.230 Replaces GRAFLPR, CPU/zIIP/4HR MSU graphs.
GRAFWRKX 35.018 WARNING but ZIPTM, IFATM, and ZIETM were not plotted.
IHDRNDM 35.089 New NDM-CDI IHDRNDM exit for NDMRTYPE selection.
IMACDBNZ 35.027 Support for DB2ACCT NETEZZA Q8AC "Accumu" variables.
IMACICWU 35.158 Support for Mainview/CICS 7.1 SMF 110 BMCMVCIC.
IMACINIT 35.128 Note: OPTIONS NOCAPSOUT recommended for ODS users.
JCLTEST9 35.116 35.04 only. //MVJEIN DD in wrong step.
MDIJCL 35.299 Support for Luminex MDI box to run MXG on Linux.
RMFINTRV 35.006 Duplicate RMFINTRV if Multiple Capacity Groups exist.
RMFINTRV 35.282 New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.
SMFINTRV 35.067 New START15INT/30INT/HRINT interval Starttimes.
TYPE0203 35.190 SMF type 2 subtype 2 (SMF Signature enabled) STOPOVER
TYPE0203 35.283 Support for APAR OA52828, SMF Temporary Buffer size.
TYPE102 35.017 New DB2 ZPARMS added to T102S106 dataset.
TYPE102 35.046 Support for IFCID 125 Truncated fields.
TYPE102 35.047 Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.
TYPE102 35.204 Support for new IFCID 376 variables in T102S376.
TYPE102 35.262 New DB2 zPARMS variables created in T102S106 dataset.
TYPE102 35.262 Support for new DB2 zPARMS added by RSU1708 and 1709.
TYPE103 35.134 Dataset TYPE103D vars T103DBYT/T103DREQ corrected.
TYPE110 35.105 CICS duration fields are now formatted TIME16.6.
TYPE113 35.141 SMF 113 Formula for RNI updated for z13.
TYPE113 35.246 SMF113/HIS formula for z14 L3P/RNI/SM1132SP changed.
TYPE113 35.310 Support for z14 SMF type 113 (INCOMPATIBLE).
TYPE115 35.011 For local time zones with +GMT, GMT115TM wrong.
TYPE116 35.192 MQMQUEUE INTS/STRT populated in subtype 2 records.
TYPE116 35.219 MQMACCT variable NETSNAME new format decoded.
TYPE117 35.015 Support for SMF 117 GTZ record.
TYPE119 35.173 Support for SMF 119 Subtype 11 Zert record.
TYPE119 35.220 Zero observations in TYP11920 dataset.
TYPE119 35.245 SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED.
TYPE120 35.007 Liberty SMF 120 st 12 SM120CCC/CCD Year 2027.
TYPE120 35.024 Subtype 9 variables SMF1209EV,FI,EW no longer kept.
TYPE120 35.051 Support for Liberty 17.0.0.1 SMF 120 ST 12 new data.
TYPE120 35.060 Enhancement adds TOTAL/CP ONLY/ZIP CPU to TYP120BL.
TYPE120 35.060 SMF 120 ST 11 TYP120BL CP and zIIP variables added.
TYPE125 35.015 Support for SMF 125 GTZ record, untested.
TYPE129 35.109 Variables SM1209EX/EY/EZ/FA were dropped.
TYPE1415 35.040A IBM APAR OA51325 corrects missing UCB segment.
TYPE30 35.066 APAR OA59593 adds INELIGHONOR flag to SMF 30s.
TYPE30 35.205 Documentation of what is counted in SMF 30 EXCPs.
TYPE30_6 35.127 Negative values for Early Address Spaces corrected.
TYPE42 35.031 Variable S42DSIOS added to TYPE42DS.
TYPE42 35.137 APAR OA44319 improves accuracy for I/O durations.
TYPE42 35.240 Support for APARS OA52132/OA52133/OA61734 UNTESTED.
TYPE42 35.274 Support for APAR OA53110 new TYPE42 variables.
TYPE42 35.289 TYPE42 APARs OA52132, OA52133, OA61734 now tested.
TYPE42 35.305 Third incorrect SRLEN STOPOVER correction.
TYPE6156 35.207 TYPE6156 enhancement adds FIRSTGEN and LASTGEN.
TYPE70 35.270 Support for Container Pricing in SMF 70.
TYPE70 35.282 New PLATxxxyyy xxx=zip/ifl/icf yyy=cpus/busy added.
TYPE7002 35.153 IBM RMF CRYPTO report TOTAL EXEC is AVERAGE EXEC.
TYPE7072 35.064 SMT Mode corrections, "Inflated" CPUZIPTM in MT=2
TYPE7072 35.093 Variables PLATBUSY/PCTOFHDWQ TYPE70/RMFINTRV wrong.
TYPE7072 35.113 35.04 only. TYPE79 SHARE weights wrong, ASUMCELP ok.
TYPE7072 35.285 Support for Container Pricing, new TYPE72TR dataset.
TYPE71 35.009 Support for APAR OA48913 with 2GB Memory Frames
TYPE74 35.146 TYPE749 Corrections, vars R749FPGBYTx, R749Dxxx.
TYPE74 35.182 MXG 34.07 INPUT STATEMENT EXCEEDED RMF 74 SUBTYPE 8.
TYPE74 35.193 Alignment for sync I/O variables.
TYPE74 35.273 Support for APAR OA50761 Virtual Flash memory.
TYPE78 35.021 TYPE78PA variables R782LSMO/GMFO/GFRR are wrong.
TYPE80A 35.029 RACFTYPE=6 segment increased in length, error msgs.
TYPE80A 35.231 RACFDIRECTED allows DELETE of RACF records DTP=44.
TYPE80A 35.231 RACFDIRECTED allows delete of multiple RACF records.
TYPE89 35.271 Support for Container Pricing in SMF 89.
TYPE90A 35.199 z/OS 2.3 type 9 subtype 38 INPUT STATEMENT EXCEEDED
TYPE92 35.180 SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED RECORD.
TYPE991 35.123 New z/OS 2.2 variables added to TYPE991 dataset.
TYPEAXWY 35.150 Support for AXWAY Version 3.1.3, incomplete.
TYPEBBMQ 35.034 Support for BBMQ BMC Utility BBM9MD73 restructure.
TYPEBBMQ 35.176 Support for BBMQ QSDSTYPE='DISTRIBUTED SYSTEM TYPE'.
TYPEBE97 35.152 Support for Beta 97 Subtype 22 for version 430/610.
TYPEBE97 35.196 Support for BETA 97 Extended 610 Header (INCOMPATIBL)
TYPEBETA 35.139 BETA93 and BETA97 Subtype 25 restructure support.
TYPEBETA 35.209 Support for BETA 93 Version 610 (INCOMPATIBLE).
TYPEBETA 35.297 Support for BETA 93 Version 610 (update) 620 (added).
TYPEBVIR 35.260 BVIR History updated for 3.3 media codes and BVIR302.
TYPEBVIR 35.260 Support for new media/devices and BVIR302 correction.
TYPECIMS 35.197 IMF variables STRTTIME/ENDTIME now in microseconds.
TYPEDB2 35.016 DB2STATS QISTxxxx Storage multiplied by 4K vs 1K.
TYPEDB2 35.030 DB2STAT4 _REAL variables way too large.
TYPEDB2 35.081 DB2ACCTP, truncated QPACLOCN/COLN/PKID/ASCH/AANM
TYPEDB2 35.111 DB2 12.1 INVALID QLAC, CONTINUOUS DELIVERY CAUSED.
TYPEDB2 35.229 PDB.DB2STATB/STSBP protection for large gaps in data.
TYPEDB2 35.248 Four QWA225 and QWB225 variables now kept/input.
TYPEDB2 35.267 DB2 Netezza IDAA variables Q8STxxxx corrected.
TYPEDB2 35.277 New IFCID=225 QWA225PRISTG_PAGE variable added.
TYPEDB2 35.280 Exit Members EXDB2STS and _EDB2STS are now valid.
TYPEDCOL 35.064A Multi-Volume DCOLDSET fields retained & populated.
TYPEIAM 35.107 Support for IAM Version 9.0.
TYPEIMS 35.058 Support for IMS LOG 67D0 DIAGNOSTIC DC Log Record.
TYPEMVCI 35.062 Support for Mainview CICS CMRDETL file VER 6700.
TYPEMVCI 35.161 Support for BMC Mainview/CICS Version 7.1.
TYPEMVIP 35.055 Support for Mainview for IP PTF BPN2331 adds flag.
TYPEMVJE 35.094 Support for BMC Mainview for Java Environment.
TYPENMON 35.208 Nigel's Monitor changed HH:MM to N MINS, INCOMPAT.
TYPEOPAV 35.163 Support for Dell/EMC Mainframe Enabler PAV Optimizer
TYPEOPC 35.048 Support for IWS/TWS/OPC Version 9.3 ST 66 was ST 23.
TYPEOPSS 35.090 Support for CA's OPSS Product User SMF Record.
TYPEOSEM 35.010 OSEM User SMF INPUT EXCEEDED, invalid, circumvented.
TYPEPOEX 35.002 INVALID SMF Records caused STOPOVER ABEND.
TYPEPOEX 35.242 Support for Power Exchange Version 10.1.1.
TYPEPOEX 35.257 Protection for truncated Power Exchange SMF record.
TYPEQACS 35.288 Support for QAPMDISK with LENGTH=695.
TYPERMFV 35.005 Dataset ZRBLCP obs created for ONLINE LCPUADDRs.
TYPERMFV 35.028 New RMF III ZRBENC "long names" now input and kept.
TYPERMFV 35.044 ZRBCP SMT vars missing, new CPC_CECNAME variable.
TYPERMFV 35.191 Support for z/OS 2.3 ZRBASI and ZRBUWD new fields.
TYPERMFV 35.235 RMF III ZRBCPU enhanced with decodes of CPC_HOMEFLAG.
TYPERMFV 35.259 35.10: ZRBASI deaccumulation was not correct.
TYPERMFV 35.259 IBM 4HR MSU (CPUAVB4H) in ZRBCPU per) interval.
TYPERMFV 35.259 MSU Count variables added to ZRBASI/ZRBCPU/ZRPLCP.
TYPERMFV 35.259 New ZRBLCPLPAR dataset with per-LPAR totals.
TYPERMFV 35.287 MXG 35.10/35.11 RMF III ZRBASI ASICPUTA was WRONG.
TYPERMFV 35.300 The CPUPHYAD format could fail creation with ABEND.
TYPEROSC 35.177 PDB.ROSCOE, ROSIGNON Logon Time, CONNECTM, corrected.
TYPESVIE 35.059 Support for CA SYSVIEW for IMS 14, missing values.
TYPETMS5 35.278 Correction for TMS Stacked Tape Files wrong values.
TYPETPMX 35.261 Execution time for TYPETPMX halved by restructure.
TYPETPMX 35.261 Execution time reduction.
TYPETPX 35.035 Protection for invalid TPX subtype 7 record.
TYPETPX 35.155 STOPOVER when IP Port was changed from 4 to 5 digit.
TYPEVMXA 35.025 Using _VMINPUT. z/VM variable VMDUSER was 1 byte.
TYPEVMXA 35.040 Support for Velocity ZWRITE z/VM MONWRITE records.
TYPEVMXA 35.079 z/VM 6.3 SMT in VXSYTPRP, VXAPLSO0 corrections.
TYPEVMXA 35.092 Additional support for z/VM 6.4 (INCOMPAT, SYTLCK).
TYPEVMXA 35.093 MXG 35.03 only. PLATBUSY/PCTOF HDW TYPE70/RMFINTRV.
TYPEVMXA 35.131 Variable CALENMT incorrect, new CALSHARE variable.
TYPEVMXA 35.132 Support for zVM 6.4 APAR VM66026 new variables.
TYPEVMXA 35.145 zVM SMT INTERVAL vars were incorrectly DIF()'d.
TYPEVMXA 35.165 New variables added to VXMTRMEM dataset.
TYPEVMXA 35.174A MONWRITE VXBYUSR _MT1 and _PRO (SMT times) corrected.
TYPEVMXA 35.203 z/VM 6.4.17.1 INCOMPATIBLE fields.
TYPEVMXA 35.221 zVM MONWRITE VXPRCPUP dataset corrected.
TYPEXAM 35.063 Support for XAMSYS wrong length, XMTCPSYS NAMENODE.
TYPEXAM 35.074 Velocity XAM SYTCPU invalid errors at vendor.
TYPEXAM 35.164 New variables added to XAMSYS dataset.
TYPEXAM 35.195 Support for zVPS XAM XAMPUP segment.
TYPEXAM 35.218 XAMSYPUP dataset variables are now correctly aligned.
TYPEXAM 35.223 zVPS/XAM extra SYTCUP with totals is now decoded.
TYPEZDP 35.162 Support for Dell/EMC Mainframe Enabler zDP
UTILBLDP 35.143 Options SUPPRESS enhanced, NEVER corrected.
UTILBLDP 35.225 New EXPDBVAR/EXPDBCDE/EXPDBOUT to create subset.
UTILBLDP 35.306 SUPPRESS=74 variable DEVN NOT FOUND ERROR.
UTILBLDX 35.149 New BUILDJCL=YES uses IFASMFDP to save CPU time.
UTILCMPR 35.292 Utility compares numeric variables in OLD/NEW dataset
UTILEXCL 35.004 MXG 34.34 PDB.CICSDICT not FOUND - GET NEW UTILEXCL.
UTILEXCL 35.023 MXG 35.01.Old Dictionary Records were not used.
UTILEXCL 35.228 Support for 20 user character fields in CICSTRAN.
UTILEXCL 35.293 &MXGCIEXC "exit" to correct USER CMODHEAD typos.
UTILRMFI 35.026 Enhanced reporting if SRVCVLASS=SYSOTHER detected.
VGETSORT 35.112 35.04 only. ERROR Truncated SORTBY (name GT 32).
VGETxxxx 35.309 Protection for DATASET=PDB.dataset syntax.
VMAC38 35.136 NETVIEW ID=38 unexpected S38CCALR length corrected.
VMACSMF 35.266 SMF ID=2 SYSTEM=DUMY 14 byte records protected.
VMXGALOC 35.033 Month begin/logic revised, MNTHKEEP zero protected
VMXGFIND 35.117 Multiple input PDBs were read, only one was output.
VMXGPRNT 35.120 WPS only, MXG 35.04 Only, Blank Label ERROR.
VMXGSET 35.256 Example to read "concatenated" PDBs with PROC SQL.
VMXGSUM 35.020 MXG 35.01. Disregard MXGWARN VMXGSUM BACKLEVEL msg.
VMXGSUM 35.056 Correction for KEEPMNTH= (very rarely used) option.
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at http://www.mxg.com.
Inverse chronological list of all Changes:
NEXTCHANGE
====== Changes thru 35.309 are in MXG 35.36 dated Jan 13, 2018=========
Change 35.309 All of these macros have both a DDNAME and a DATASET
VGETFMT parameter but if you specified DATASET=PDB.dataset they
VGETLABL would all fail since they looked for WORK.PDB.dataset.
VGETLEN This change looks at the code and if DDNAME is null looks
VGETVAR at dataset and uses the first 'word' delimited by '.' of
Jan 8, 2018 DATASET as the DDNAME and the second for the DATASET. If
there is no '.' then DDNAME is set to &MXGWORK.
Change 35.308 SAS defect in SAS 9.4 M5 PROC SQL, only M5 on z/OS, when
ASUMUOW PROC SQL is executed after OPTION OBS=0 was set, caused
Jan 6, 2018 "SQL SET NOEXEC OPTION" error message and ERRORABEND.
Error occurred in default ASUMUOW, but ONLY if you did
NOT enable IMACUOW to create observations, as then, MXG
sets OBS=0 prior to this failing PROC SQL (which had no
prior error message than the NOEXEC and which is still
under investigation by SAS Support: SAS NOTE nnnnn).
The circumvention is to add NOERRORSTOP to this PROC SQL
and to the several hundred other PROC SQLs in 51 members,
and do it now to hopefully avoid the need for a SAS fix.
Most of the SAS examples of PROC SQL use NOERRORSTOP and
no MXG written PROC SQL has ever had a syntax error, so
this circumvention will likely be permanent.
Option ERRORSTOP is the SAS Default for batch, and it
determines whether PROC SQL stops executing if it
encounters an error; option NOERRORSTOP instructs PROC
SQL to execute the statements and to continue checking
the syntax after an error occurs.
Change 35.307 ANALDB2R fails with broken DO syntax due to Change 35.263
ANALDB2R (MXG 35.11) which incorrectly set the count of SORTBY=
Jan 6, 2018 arguments, resulting in an error in the data steps, if
option PDBOUT=PDB is used.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 35.306 UTILBLDP with SUPPRESS=74 variable DEVN NOT FOUND ERROR.
UTILBLDP If you specified SUPPRESS=74 the sort of the TYPE74CA
Jan 6, 2018 dataset failed with BY variable DEVN not found.
When UTILBLDP found RMF datasets that are needed for
RMFINTRV are SUPPRESSED, we chose to still create them in
WORK so that RMFINTRV would find them and not fail.
But a change to SUPPRESS logic nulled MACRO _CDE74 and
only 16 variables were kept (those that were INPUT in the
other _CDEnnnn macros), and the _STY74 failed.
This change reinstates the logic that nulls the _Sxxxx
macro for suppressed RMF records so sorts will not fail,
but if you also want RMFINTRV to be valid, but don't want
the high volume TYPE74's processed, then you should use
ZEROOBS=74 so the datasets will be created but with zero
OBS, so RMFINTRV will be happy.
Change 35.305 -Jan 04: MXG 35.35 didn't protect LENSR=480 length, caused
VMAC42 STOPOVER if you happen to have that length/APAR.
Jan 4, 2018 -Jan 04, IBM confirmed their incorrect values and will now
set SRLEN=160, and note that that does NOT include the
SYNC segment's 80 bytes when present.
-Change 35.302 in MXG 35.36 was the original change.
-Change 36.023 in MXG 36.01 added invalid LENSR=232.
Change 35.304 New variables in TYPE71 in z/OS 2.3:
VMAC71 SMF71L8M ='MIN 1MB*FRAMES*IN CSTORE'
Jan 4, 2018 SMF71L8X ='MAX 1MB*FRAMES*IN CSTORE'
SMF71L8A ='AVG 1MB*FRAMES*IN CSTORE'
SMF71L9M ='MIN 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71L9X ='MAX 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71L9A ='AVG 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71L10M='MIN 1MB*FRAMES*IN-USE BY*MEM OBJECTS'
SMF71L10X='MAX 1MB*FRAMES*IN-USE BY*MEM OBJECTS'
SMF71L10A='AVG 1MB*FRAMES*IN-USE BY*MEM OBJECTS'
====== Changes thru 35.303 are in MXG 35.35 dated Jan 3, 2018=========
Change 35.303 One z/OS SAS 9.4 M5 site gets SQL SET NOEXEC OPTION that
VMXGUOW terminates the job, currently under investigation by SAS
Jan 4, 2018 support, but adding NOERRORSTOP option to the PROC SQL
does circumvent the error, so it has been added to the
one failing PROC SQL in hopes thats the only one needed.
This note will be revised when more is known.
Change 35.302 SMF 42 st 5/6 with OA54112 now has three SRLEN values of
VMAC42 of 240 and 400, and 480 from OA52132/OA52133/OA61745 in
Jan 2, 2018 Change 35.289, and all three are wrong.
Jan 3, 2018 The actual length of the SR segment in each record is
Jan 4, 2018 variable, with 160 bytes if there is no SYNC segment, or
240 bytes when the SYNC segment is present. All three
are now protected. The error caused STOPOVER ABEND.
-New variable S42SNCONC='CONCURRENT*SYNC I/O*READ+WRITE'
added to TYPE42SR and TYPE42DS datasets.
-Jan 03: another incorrect SRLEN value of 320 protected in
MXG 35.36.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 35.301 If in your ASUMUOW you defined _LDB2ACC as something
VMXGUOW other than DB2ACCT.DB2ACCT (like DB2.DB2ACCT) and the
Dec 30, 2017 DDNAME did not exist in your LIBNAME or DD statements
ASUMUOW would ABEND with a LIBREF not found. Now the
code looks for this condition, gives you an MXGWARN
message and sets _LDB2ACC to _NULL_ so that ASUMUOW
will run.
Change 35.300 The CPUPHYAD format could fail to be created with error
VMACRMFV messages of overlapped values, when there were multiple
Dec 31, 2017 values of CPUPHYAD (CEC Speed), as when you change the
number of engines for an LPAR; that error caused the
TYPERMFV job to ABEND USER 999.
Thanks to MP Welch, Bank of America, USA.
Change 35.299 Luminex now offers a small Linux appliance called an MDI
MDIADHOC (Mainframe Data Integration) that provides another way to
MDIJCL move MXG jobs off of zOS and onto an ASCII platform. Jobs
MDIJCL1 are still submitted from zOS, so your scheduling system
MDIJCL2 is still in control, but the actual processing of the SMF
MDIJCL3 data occurs on the LINUX platform, and the output PDB's
MDIJCL4 live on storage attached to the MDI. Reports can be sent
MDIPDB back to zOS or routed on your network wherever the MDI
MDIPDB1 can attach. Each job uses 2-3 virtual tape devices, for
MDIPDB2 the SMF input, the SASLOG, and the SASLIST. One site had
MDIPDB3 1TB of SMF, split when SMF was dumped into three outputs,
MDIPDB4 DB2, CICS, for each of 12 LPARS, so 36 concurrent jobs
Dec 31, 2017 processed that data in a bit less than two hours on a
Jan 6, 2018 single MDI.
These sample members provide examples of JCL and code
to run jobs on the MDI. The JCL is very case sensitive
and casing for program names must match the case as
stored in your USERID.SOURCLIB. Also the names and case
of the LOG and LIST datasets in the LUMXPROC must match
the program name.
MDIJCL /MDIPDB runs a basic BUILDPDB adding the 42
and 6156 data to the PDB using
UTILBLDP and BLDSMPDB wirh AUTOALOC
MDIJCL1/MDIPDB1 runs a basic BUILDPDB adding the 42
and 6156 data to the PDB using
UTILBLDP and BLDSMPDB wirh AUTOALOC
and suppressing CICS and DB2 data
MDIJCL2/MDIPDB2 runs VMXGALOC with READONLY=YES
(which suppresss the aging of the
directories) and then runs TYPS110
and CICINTRV.
MDIJCL3/MDIPDB3 runs VMXGALOC with READONLY=YES
(which suppresss the aging of the
directries) and then runs READDB2.
MDIJCL4/MDIPDB4 runs VMXGALOC with READONLY=YES
(which suppresss the aging of the
directries) and after MDIJCL2 and
MDIJCL3 have run will run ASUMUOW.
MDIADHOC JCL for adhoc reporting allows you to
write your program on z/OS and run the
MDI.
Thanks to Chuck Hopf, Independent Consultant, USA.
Thanks to Earl Kline, Luminex, USA
Thanks to Paul Massengill, Luminex, USA
Thanks to Daniel Saunders, Luminex, USA
Thanks to David Feimer, Luminex, USA
====== Changes thru 35.298 are in this MXG 35.12 dated Dec 26, 2017=====
Change 35.298 While all MXG Variables are upper case, mixed case names
VGETFMT are allowed, so you can easily create variable names with
VGETLABL lower case characters, but the listed macros all failed
VGETLEN to find those variable names. The macros are revised to
VGETVAR UPCASE both sides of the compare without changing the
Dec 23, 2017 returned variable name.
Change 35.297 Support for BETA 93 Version 610 (update) and 620 (added).
EXTYBETK -BETA1 blank values for BETADCR corrected and new vars:
EXTYBETL I001PTYPE='PROTOCOL*TYPE'
EXTYBETM I001IPADDR='IP*ADDRESS'
EXTYBETN I001HOST ='HOST*NAME'
FORMATS I001PORT ='HOST*NAME'
VMACBETA I001QUEUE ='HOST*NAME'
VMXGINIT I001FFPARM='HOST*NAME'
Dec 23, 2017 -Support for 620 new subtype 59 creates three datasets and
subtype 22 record is now decoded and creates BETA22VAL:
TYBETK BETA59 SUBTYPE 59 STC START/STOP
TYBETL BETA59RFF SUBTYPE 59 SFF JOB STATS
TYBETM BETA59SFF SUBTYPE 59 SFF JOB STATS
TYBETN BETA22VAL SUBTYPE 22 VALUES
Change 35.296 A WHERE clause in PROC SQL is case sensitive, and if you
VGETLABL create your own variable NAMEs with low case characters,
VGETFMT your variable will NOT be found; only upper case variable
VGETLEN names are found. MXG does not create low case names, and
Dec 20, 2017 cannot detect them in the WHERE clause. No code changed.
Change 35.295 Support for 164-byte DBCTL segment for CICSTRAN dataset.
IMACICDB
Dec 20, 2017
Thanks to Ervin Claxon, CSX Technology, USA.
====== Changes thru 35.294 are in this MXG 35.12 dated Dec 20, 2017=====
Change 35.294 SMF 116 records with MQMSSSID mismatched to QWHSIDMQ
VMAC116 printed MISMATCHED message on the log for every mismatch;
Dec 19, 2017 now, only the first three are printed.
Thanks to Denise Williers, Wipro, USA.
Change 35.293 &MXGCIEXC is a new "exit" for UTILEXCL wherein you can
UTILEXCL correct mispellings in USER CMODHEAD field that cause the
VMXGINIT DUPLICATE CONN report (same offset has two names, usually
Dec 19, 2017 caused by a typo by the CICS SYSPROG who does the DFHCT
assembly of that Monitor Control Table). This change
circumvents the need to reassemble. You would use:
//SYSIN DD *
%LET MXGCIEXC=
%QUOTE(
IF CMODHEAD='PSB ACTV' THEN DO;
PUTLOG _N_= CMODNAME= CMODHEAD=
SMFPSRVR= MCTSSDRL= MCTSSDCN=;
CMODHEAD='PSB ACTI';
END; );
%INCLUDE SOURCLIB(UTILEXCL);
_BLDDICT _BLDEXCL _RPTEXCL
Thanks to Denise Williers, Wipro, USA.
Change 35.292 A utility to Compare numeric variables values in OLD and
UTILCMPR NEW versions of the same SAS dataset, using PROC MEANS to
Dec 30, 2017 compare the value of each statistic of each variable.
%UTILCMPR(IN1=OLD.ZRBASI,IN2=NEW.ZRBASI);
Change 35.291 GCHART AXIS statements were made compatible with WPS
GRAFCEC 03.03.02.00.0222553, and some code was simplified and
GRAFLPAR logic added to STOP if no obs in RMFINTRV and to not
GRAFWRKX plot eligible times if there were none.
GRAFWRKC The WPS graphs are printed in different order, all for a
Dec 15, 2017 particular metric, whereas SAS prints all for an LPAR.
While GRAFLPAR is supported, it is obsolete and GRAFCEC
should be used instead, as it has superior reports.
-As WPS does not support SGPLOT, GRAFWRKC plots had to be
duplicated using the GBARLINE and GCHART procedures and
INCODE= added for data selection.
Change 35.290 Clear of _HSMPLEX macro added at end so that you can
ASUMHSM execute ASUMHSM multiple times in a single job.
Dec 13, 2017
Change 35.289 Support for TYPE42 APARs OA52132, OA52133, and OA61734,
VMAC42 originally coded in Change 35.240, has now been revised.
Dec 12, 2017 A Subtype 5 STOPOVER was caused by new records with the
SRLEN=480 but with actual SR Segment length of 160, or
240 if the new SYNC segment is present, but the actual
length of the SYNC segment is 80 bytes with APAR only
documenting 72. Finally, records with SRLEN=208 and no
SYNC segment are written with only 160 bytes documented.
Change 35.288 Support for new TYPECONF GKEYPM variable and new length
VMACQACS of QAPMDISK of 695 to align those records, although no
Dec 11, 2017 new fields are input in this iteration, awaiting doc.
Thanks to Larry E. Hanus, DST Systems, USA.
Change 35.287 -MXG 35.10 and 35.11 RMF III ZRBASI deaccumulate was WRONG
VMACRMFV DESIGN: should NOT replace ASICPUTA with ASICPUTA_LF, and
Dec 15, 2017 WRONG IMPLEMENTATION: insufficient QA tests, causing the
Dec 21, 2017 value in both variables to be frequently wrong, and if
there were multiple CEC Speeds (CPUPHYAD values) the MSU
value in ZRBASICPUMSU=ZRBASI*CPU MSU*COUNT was wrong.
-This change restores the original ASICPUTA value and the
deaccumulated higher resolution value is in ASICPUTA_LF
so YOU can choose to use the variable of YOUR choice.
-This change also adds variable CPC_CECNAME to ZRBLCP and
ZRBLCPLPAR datasets, and creates a format for CPUPHYAD
lookup (by SYSPLEX SYSTEM) from ZRBCPU to pass CPUPHYAD
into the ZRBASI dataset for MSU calculations.
-Duplicate ASI records for the same task in an interval do
exist, as when a task changes it's JOB name, and they are
visible in RMF III reports, but the deaccumulate can be
a missing value as IBM has not provided a way to identify
which was the first observation and which was the second.
In addition, records with seconds of CPUTCBTA value and
microseconds for CPUTCBTA_LF have been observed, so the
value of using CPUTCBTA_LF needs to be examined in your
data. These issues are open with RMF development, and
this text will be updated when more is known.
-Dec 21: Invalid INPUT for PHYCPUAD message had no impact
but was corrected; was printed when no ZRBCPU matched.
Thanks to MP Welch, Bank of America, USA.
Change 35.286 MXG variable IOTMNOCA, uncaptured IO Connect Time in 30s,
BUILD005 was incorrectly calculated in BUILDPDB and SMFINTRV using
BUIL3005 SMF30AIC-IOTMTOTL instead of -IOTMDASD causing negative
SMFINTRV values. But SMF30AIC is the connect time for the ASID
Dec 6, 2017 and Dependent Enclaves, but does NOT include FICON chans
which could also cause negative values.
Thanks to Randy Hewitt, DXC Technology, USA.
Change 35.285 Support for Container Pricing in RMF 72 records creates
EXTY72TR new TYPE72TR dataset for Tenant Resource Group that are
IMAC7072 added by APAR OA52694. TYPE72TR has the same variables
VMAC7072 that are in TYPE72GO with new variables for TRG
VMAC79 R723GGTI='TENANT*IDENTIFIER'
VMXGINIT R723GGTN='TENANT*NAME'
Dec 7, 2017 R723GGKY='TENANT*SOLUTION*ID'
R723GGTF='TENANT*RESOURCE*GROUP?'
and these variables added to both TYPE72GO and TYPE72TR:
R723CPA_ACTUAL ='PHYSICAL*CPU*ADJUSTMENT*FACTOR'
R723CPA_SCALING='SCALING*FACTOR*FOR*R723_ACTUAL'
-Flag variables added to TYPE792 and TYPE795 dataset
R792FLG32='R792RGRP*IS A*TRG?'
R795FLG6='R795RGRP*IS A*TRG?'
Change 35.284 -MXG 35.11 inserted statements to create ZRBCPUxxxMSU vars
VMACRMFV incorrectly inside MACRO _EZRBCPU and _EZRBLCP definition
Dec 6, 2017 causing UNINIT variable if you had tailored EZRBCPU.
Dec 8, 2017 -Missing values for ZRBCPUZIPMSU were corrected. The new
Dec 9, 2017 ZRBLCPLPAR dataset requires the CPUG3 CPCDB, and SSHG3
tables, or ASMRMFV Table IDs of CPU and CPC, since SSH is
always selected.
Thanks to MP Welch, Bank of America, USA.
Change 35.283 Support for APAR OA52828 which allows customization of
VMAC0203 the size of the SMF Temporary Buffer used to hold SMF
VMAC7 data during IPL processing.
VMAC23 TYPE0 dataset new variable
Dec 5, 2017 SMF0TBUF='SMFTBUFF*PARAMETER*SPECIFIED*MEGABYTES'
TYPE7 dataset new variable
SMF7TBLS='BYTES LOST*DURING SMF*INITIALIZATION';
TYPE23 dataset new variable
SMF23MBU='MAX BYTES*STORED IN*SMFTBUFF'
Change 35.282 A new set of variables added to TYPE70 and RMFINTRV to
VMAC7072 capture the number and usage of IIP, IFL, and ICF CPS
VMXGRMFI for the platform (CEC).
Dec 5,2017 PLATZIPCPUS - The number of IIPs on the CEC
PLATZIPBUSY - The total % busy of all the IIPs
PLATIFLCPUS - The number of IFLs on the CEC
PLATIFLBUSY - The total % busy of all the IFLs
PLATICFCPUS - The number of ICFs on the CEC
PLATICFBUSY - The total % busy of all the ICFs
Change 35.281 TACI802 dataset variable FINTIME was not converted from
VMACMVIP GMT to LOCAL Time zone.
Dec 4, 2017
Thanks to Paul Volpi, UHC, USA.
Change 35.280 The Exit member EXDB2STS and _EDB2STS macro are now used
VMACDB2 to give control of the output of PDB.DB2STATS; previously
Dec 6, 2017 defined but not used.
Thanks to Scott Barry, SBBWorks Inc., USA.
====== Changes thru 35.279 are in this MXG 35.11 dated Dec 1, 2017=====
Change 35.279 Support for Dec 2017 z14 CPU MF formula update.
ASUM113 The EXTND158 counter was moved from L3P to L4LP.
VMAC113 -John's updated formulas are available at
VMACVMXA
Nov 30, 2017
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000066
Change 35.278 Correction for TMS Stacked Tape Files; these variables
TYPETMS5 were not retained from the first DSNB record into the
VMACTMS5 "CHANGED" records so they were incorrect:
Nov 30, 2017 RFILSEQ RLRECL RBLKSIZE RRECFM RSTPNAME RFILPERC;
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.277 Support for IFCID=225 new fields in DB2STAT4 dataset:
VMACDB2 QWA225PRISTG_PAGE /**DBM1*PRVT ELIG*PGSTEAL*/
Nov 28, 2017 QWB225PRISTG_PAGE /**DIST*PRVT ELIG*PGSTEAL*/
Dec 6, 2017 IBM DSECT notes these fields contain:
Number of Private discarded pages eligible for Page
Steal. Currently backed frames which are still charged
to DB2, minus this count, is the true REAL Storage
usage at this time.
I can not find the "currently backed frames" fields and
have asked IBM for help; this note will be updated when
the correct fields are known so the usage variable can
be created.
IBM DB2 Support response Nov 30:
All IFCID225 fields are described in the dataset
'DSNB10.SDSNIVPD(DSNWMSGS)'. It does not look like we
capture that statistic. The values are captured from
RMF and are included with DB2 statistics records to
assist with reporting. Anything not contained will
still be available in RMF.
-Dec 6: UNINIT PRISTGDPAGE and correct spell as _PAGE.
Change 35.276 Support for CICSTRAN User field RFSEMP01/RFSDATA creates
IMACICWX seven variables, RFSEMP01F1-RMSEMP01F7.
IMACAAAA
UTILEXCL
VMAC110
Nov 27, 2017
Change 35.275 Addition of TYPE70TR dataset required protection in the
ANALRMFR PDB=SMF part of the program to prevent the
Nov 26, 2017 ERROR: No dataset open to look up variables.
when the _STY70TR was executed without prior build.
Change 35.274 Support for APAR OA53110 adds new variables:
VMAC42 S42DSRRU='AVG RESPONSE*RANDOM*READ*CACHE'
Nov 22, 2017 S42DSRSU='AVG SERVICE*RANDOM*READ*CACHE'
SMF42IFW='AVERAGE*FAST-WRITE WAITS*PER MINUTE'
SMF42IHR='AVERAGE*HIT*RATIO'
Change 35.273 Support for APAR OA50761 adds new R7410FLG='Y' if the
VMAC74 resource is Virtual Flash Memory.
Nov 22, 2017
Change 35.272 Change 34.151 set SYSLAST to the value of OUTDATA so that
VMXGSUM subsequent PROC steps would automatically find the output
Nov 22, 2017 of VMXGSUM as the last dataset created, but if you added
any dataset options like (KEEP or (INDEX then while the
dataset was correctly created, an error message was
generated that either told you the dataset name was
invalid or that it exceeded 42 bytes depending on the SAS
version you were running. NOTE: there must be a space
between the dataset name and any options you choose to
specify.
Thanks to Robert Gilbert, BNP Paribas Fortis, BELGIUM.
Change 35.271 Support for Container Pricing in SMF 89 records creates
EXTY89R1 New variables in TYPE89 and TYPE892:
EXTY89R2 SMF89COREMODECP='CPUS*ACTIVE*ON CP*CORE'
EXTY89TI SMF89COREMODEZAAP='CPUS*ACTIVE*ON ZAAP*CORE'
IMAC89 SMF89COREMODEZIIP='CPUS*ACTIVE*ON ZIIP*CORE'
VMAC89 New variables in TYPE892:
VMXGINIT SMF89CURREGS ='INSTANCES*OF CURRENT*REGISTRATIONS'
Nov 27, 2017 SMF89TRGREGS ='INSTANCES*OF CURRENT TRG*REGISTRATIONS'
SMF89DELTAREGS='INTERVAL*DELTA*CURRENT*REGISTRATIONS'
SMF89DELTATRG ='INTERVAL*DELTA*TRG*REGISTRATIONS'
New dataset TYPE89TI 'INTERSECTION TENANT RESOURCE GROUP'
PRODOWNR= 'SMF89TCPO PRODUCT*OWNER'
PRODNAME= 'SMF89TCPN PRODUCT*NAME'
PRODVERS= 'SMF89TCPV PRODUCT*VERSION'
PRODQUAL= 'SMF89TCPQ PRODUCT*QUALIFIER'
PRODID = 'SMF89TCPI PRODUCT*ID'
SMF89TIPO 'INTERSECTING*PRODUCT*OWNER'
SMF89TIPN 'INTERSECTING*PRODUCT*NAME'
SMF89TIPV 'INTERSECTING*PRODUCT*VERSION'
SMF89TIPQ 'INTERSECTING*PRODUCT*QUALIFIER'
SMF89TIPI 'INTERSECTING*PRODUCT*ID'
SMF89_TRG 'TENANT*RESOURCE*GROUP'
SMF89TCFG 'TENANT*USAGE*ENTRY*FLAGS'
SMF89TCCT 'TENANT*PRODUCT*INTERSECT*CP TCB TIME'
SMF89TCZT 'TENANT*PRODUCT*INTERSECT*ZIIP TIME'
New dataset TYPE89R1 'TENANT RESOURCE GROUP DATA'
SMF89TIPO='INTERSECTING*PRODUCT*OWNER'
SMF89TIPN='INTERSECTING*PRODUCT*NAME'
SMF89TIPV='INTERSECTING*PRODUCT*VERSION'
SMF89TIPQ='INTERSECTING*PRODUCT*QUALIFIER'
SMF89TIPI='INTERSECTING*PRODUCT*ID'
SMF89_TRG='TENANT*RESOURCE*GROUP'
SMF89TCFG='TENANT*USAGE*ENTRY*FLAGS'
SMF89TCCT='TENANT*PRODUCT*INTERSECT*CP TCB TIME'
SMF89TCZT='TENANT*PRODUCT*INTERSECT*ZIIP TIME'
New dataset TYPE89R2 'TENANT RESOURCE GROUP DATA'
SMF89TIPO='INTERSECTING*PRODUCT*OWNER'
SMF89TIPN='INTERSECTING*PRODUCT*NAME'
SMF89TIPV='INTERSECTING*PRODUCT*VERSION'
SMF89TIPQ='INTERSECTING*PRODUCT*QUALIFIER'
SMF89TIPI='INTERSECTING*PRODUCT*ID'
SMF89_TRG='TENANT*RESOURCE*GROUP'
SMF89NRTRG'CURRENT*TRG*REGISTRATIONS'
Change 35.270 Support for Container Pricing in RMF 70 records creates
EXTY70TR new TYPE70TR dataset with these Tennant Resource Group
VMAC7072 variables in APAR OA52694:
VMXGINIT TRG_NAME ='TENANT*RESOURCE*GROUP*NAME'
Nov 22, 2017 TRG_DESC ='TENANT*RESOURCE*GROUP*DESCRIPTION'
TRG_TNTID ='TENANT*IDENTIFIER'
TRG_TNTNAME='TENANT*NAME'
TRG_SBID ='TENANT*SOLUTION*ID'
TRG_SUCP ='TENANT*CP*MSU*UNITS'
TRG_SUIFA ='TENANT*ZAAP*MSU*UNITS'
TRG_SUSUP ='TENANT*ZIIP*MSU**UNITS'
TRG_SULAC ='TENANT*CP 4HR*AVERAGE*MSU'
Change 35.269 Support for CICS User field USERPRC1/WANLUPRC.
IMACAAAA
IMACICWV
PRODTEST
UTILEXCL
VMAC110
Nov 21, 2017
Change 35.268 SAS 9.1.3 SP4 (SAS (R) 9.1 (TS01.01M3P02022006) failed
SAS* with ERROR: OBTAIN FAILED FOR FILE SMF, RC=24. because
Nov 19, 2017 the new parm EATTR=OPT was enabled for non-VSAM datasets,
so they can reside on EAV volumes, but that was not
supported until SAS 9.2
Thanks to Jeffery Kirsch, Compuware, USA.
Change 35.267 -DB2 Netezza IDAA variables Q8STDSKB and Q8STDSKU were
VMACDB2 both wrong; Q8STDSKU was incorrectly multiplied and DSKB
Nov 17, 2017 was missing that multiplication.
-Variables Q8STINSC/UPDC/DELC/DRPC/CRTC/CMTC/RBKC/OPNC
WERE ALL WRONGLY SET EQUAL TO Q8STACPU.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.266 SMF ID=2 SYSTEM=DUMY "SMF Signature Enabled" records that
VMACSMF are only 14 bytes were still created after APAR OA50483
Nov 17, 2017 was installed, causing INPUT STATEMENT EXCEEDED error, as
MXG expected these records to contain additional data in
either a subtype 1 or 2 record. Now, MXG tests for the
length=14 and deletes these 'DUMY' records, silently.
The APAR reported the exposure was only when Logstream
data is read, and infrequently.
In IBM's unstated defense, the "subtypes are valid" bit
wasn't turned on, justifying the original 14 byte length,
but MXG had keyed off that unique system name of DUMY.
If you see the DUMY in a hex dump, you can circumvent
with MACRO STOPOVER MISSOVER % as your first //SYSIN.
to prevent the ABEND until you have this VMACSMF update.
Thanks to Paul Volpi, UHC, USA.
Thanks to Brian D. Peterson, UHC, USA.
Thanks to Donald R. Striegel, UCH, USA.
Change 35.265 MXG 35.10. BPHITRAT always missing in DB2STATB because
VMACDB2 line 4057 (BPHITRAT=.;) should have been deleted. You
Nov 14, 2017 can recalculate in your reporting using
IF QBSTGET GT 0 THEN BPHITRAT=
(QBSTGET-(QBSTRIO+QBSTSPP+QBSTDPP+QBSTLPP))/QBSTGET;
ELSE BPHITRAT=.;
Thanks to Rick Southby, Insurance Australia Group, AUSTRALIA.
Change 35.264 CICS interval statistics in the Dispatcher Records, CICDS
VMAC110 dataset, have the sum of DSGTDT+DSGTWT, DISP+WAIT time
VMXGCICI that is greater than the interval DURATM, with DSGTWT as
Nov 14, 2017 much as 5900 seconds for a 3600 second interval (and the
DSGTDT in those segments are milliseconds or less); that
sum was used calculate STARTIME and DURATDS. Now, DURATM
is stored in DSGTWT and used for calculations, and then
DSGTWT=DURATM-DSGTDT recalculates the possible wait time.
See Change 36.076.
-The message "ERROR: IF YOU USE CICINTRV..." when MXG
detected the condition (DURATM GT INTERVAL REQUESTED)
is change to "MXGWARN:..." as few actually use CICINTRV.
-This data has only been seen from ancient CICS/TS 4.2.
Thanks to Ed Wieszczek, Zions Bank, USA.
Change 35.263 If you didn't specify a SORTBY= parameter for the ACCOUNT
ANALDB2R report, it could fail trying to resolve a macro variable
Nov 10, 2017 that did not exist.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 35.262 New DB2 zPARMS added include
FORMATS QWP4MUDI='MORE*UNION*DISTRIBUTION' which is decoded by
VMAC102 a new format
Nov 22, 2017 QWPRSTACS='STATCKGSRT'
QWP4BSACP='ALTERNATE*CP'
QWP4UDBSG='UTIL*DBBSG'
QWP4ULBSG='UTIL*LGBSG'
QWP4CYFR ='COPY*FAST*REPLICATION'
QWP4DDLM ='DDL*MATERIAL*IMMED*PEND'
QWP4CDSTL='CACHDYN*BOTH*CAPTURE*LOAD*NONE'
QWP4ZHYPL='ZHYPERLINK*ENABLE*DISABLE*BDATABASE'
Change 35.261 Execution run time for TYPETPMX halved by restructuring
VMACTPMX the 700 WHEN clauses into 13 subgroups of first letter of
Nov 8, 2017 the WHEN argument text value.
Thanks to Kurt Gramling, TSYS, USA.
Change 35.260 BVIR History file updated for formats for 3.3 media codes
FORMATS and BVIR302 fields were corrected.
VMACBVIR
Nov 9, 2017
Thanks to Spain.
Change 35.259 -RMF III Interval MSU variables in ZRBASI/ZRBCPU/ZRBLCP
VMACRMFV with these counts of Million Service Units
Nov 8, 2017 ZRBASICPUMSU='ZRBASI*CPU MSU*COUNT'
Nov 12, 2017 ZRBCPUCPUMSU='ZRBCPU*CPU MSU*COUNT'
Nov 18, 2017 ZRBCPUZIPMSU='ZRBCPU*ZIP MSU*COUNT'
Nov 24, 2017 ZRBLCPCPUMSU='ZRBLCP*CPU MSU*COUNT'
Nov 30, 2017 where the Software MSU Coefficient CPUPHYAD is used by
ZRBCPUCPUMSU=CPUPHYSI*CPUPHYAD/1000000;
So, an LPAR in a CEC with CPUPHYAD=20000, with the CPU
Partition Dispatch time of 15 seconds in an interval,
would have an MSU Count = (15*20000)/1000000 =0.3 MSU.
If the interval duration was one minute, the IBM ACT
"Actual" MSU on the RMF III CPC report, a projection
of this interval's value to an hourly total as if all
intervals were this value, would be 60*0.3=18 MSU per
hour, which is the value in this new variable:
ZRBLCPCPUMSUHR='ZRBLCP*IBM ACT MSU*PROJECTED*HRLYMSU'
-Dataset ZRBLCP contains data on ALL LPARS in a SYSPLEX,
reading data from only one SYSTEM in that SYSPLEX, but it
has an obs for each LCPUADDR in each LPAR. This change
creates new ZRBLCPLPAR dataset when ZRBLCP is sorted,
with the LPAR totals for each LCPUPRTY engine for each
interval, but there is no 4HR AVG MSU variable in ZRBLCP.
To create ZRBLCPLPAR the CPUG3, CPCDB and SSHG3 tables
are needed.
-The actual IBM 4HR MSU (CPUAVG4H) is in ZRBCPU dataset
at one minute or even 30 second intervals, but you have
to read the data from every system to populate ZRBCPU for
all LPARs.
-MXG 35.10, the deaccumulation of the six ZRBASI variables
(actually added by z/OS 2.2) was not sufficiently tested
and could have incorrect values in these variables:
ASICPUTA_LF ASITCBTA_LF ASIIOCNT_S ASITRCA_S ASITET ASITRT
for jobs that have duplicate names with different ASID-NR
and only if you used TYPSRMFV or _SZRBASI to sort ZRBASI.
The new-in-35.10 MXG deaccumulation of CPU_LF fields by
_SZRBASI failed to include the ASID number, PERIOD, and
JCTJOBID to deaccumulate those six variables.
The ZRBASI dataset created by TYPERMFV was not in error.
-As documented in Change 35.249, the value in ASICPUTA is
is larger with 35.10 because the higher resolution CPU in
ASICPUTA_LF is stored in ASICPUTA, with ASICPUTA_ORIG
keeping the original lower value.
-Nov 30: LPARNAME in ZRBCPU is now always populated.
Change 35.258 35.09-35.10, Macro Language error, missing double periods
ANALID in line ANALID: &PDBMXG..SMFRECNT DOES NOT EXIST;
Nov 7, 2017
Change 35.257 Power Exchange User SMF INPUT STATEMENT EXCEEDED ERROR;
VMACPOEX the record should have 21 POEX segments but has only 3,
Nov 7, 2017 and the last segment is only 90 versus 95 bytes.
This change will be updated when the vendor's records are
correct. This was from 9.6.1, but I've recently read
that version's records with no errors.
Thanks to Tracey Davidson, USBank, USA.
Change 35.256 No code change, but a new example using PROC SQL to read
VGETDDS "concatenated" PDB data libraries.
VMXGSET // EXEC MXGSASV9
Nov 7, 2017 //PDB1 DD
//PDB2 DD
%VGETDDS(DDNAMES=PDB: );
DATA MYVIEW/VIEW=MYVIEW;
%VMXGSET(DATASET=MNTHJOB);
PROC SQL;
SELECT YEAR(DATEPART(JINITIME)) AS MYYEAR LABEL= 'YEAR',
MONTH(DATEPART(JINITIME)) AS MYMONTH LABEL = 'MONTH',
SYSTEM, JOB, TYPETASK ,
ACCOUNT1, SUM(NORMCPU) AS TOTALNORMCPU ,
JOB FROM MYVIEW
WHERE JOB LIKE 'MYJOB%'
AND MONTH(DATEPART(JINITIME)) = 09
GROUP BY JOB, SYSTEM ;
Thanks to Paul W Schreiber, AT&T, USA.
====== Changes thru 35.255 are in this MXG 35.10 dated Nov 6, 2017=====
Change 35.255 -MXG 35.10, Change 35.240 DIVIDE BY ZERO error when the
VMAC42 IOCCOUNT=0 in TYPE42SR, now protected, but had no impact
Nov 6, 2017 on the TYPE42SR dataset, DCMEPCT still missing.
Nov 14, 2017 -Subtype 5 INPUT STATEMENT EXCEEDED when 68 bytes were
added for the SYNC segment, but SYNC Offset was zero.
Thanks to Jim Horne, Lowe's Companies, Inc., USA.
Thanks to Stan Adriaensen, AXA-Tech, BELGIUM.
====== Changes thru 35.254 are in this MXG 35.10 dated Nov 6, 2017=====
Change 35.254 Variables QW0225_ECSA_aaaa and QW0225_ESQA_aaaa were
VMACDB2 incorrectly multiplied by 4096.
Nov 5, 2017
Thanks to Rick Southby, IAG, AUSTRALIA.
Change 35.253 Some of the macro variables coming back from PROC SQL
PDBAUDIT are longer than the 262 character literal length since
Nov 5, 2017 the spaces count and could generate spurious messages
particularly in the QA stream.
Change 35.252 MXGWARN message variable JESNR missing value and blank
VGETJESN TYPETEST is suppressed for records with SUBSYS='SMS' and
Nov 4, 2017 JCTJOBID='INIT'; variable values are unchanged as those
records for tasks in initiation have neither.
VGETJESN already suppressed warning for JCTJOBID='MSTR'.
Change 35.251 Support for CICS/TS 5.4 Statistics STID=21, adds BMS 3270
EXCICASG counters to the CICVT (VTAM) dataset, new STID=149 record
VMAC110 creates new CICASG Statistics for the AS Domain.
VMXGINIT
Nov 3, 2017
Thanks to Perry Lim, Union Bank, USA.
Change 35.250 Support for Thruput Manager fields JBAACT JBDEA JLIMT and
VMACTPMX REQUIRED.
Nov 4, 2017
Thanks to Kurt Gramling, TSYS, USA.
Change 35.249 -Support for z/OS 2.3 RMF III CPUG3 record dataset ZRBCPU
VMACRMFV changed CPUHOOFF offset value caused some variables to
Nov 3, 2017 be wrong, notable the Capacity Group Name and adjacent.
-Variable ASICPUTA in ZRBASI dataset will be larger with
this change, as IBM has added new accumulated ASICPUTA_LF
(long float) field with higher resolution, which is now
deaccumulated and REPLACES ASICPUTA's original value.
New variable ASICPUTA_ORIG contains the original value.
The ASICPUTA_LF was 18% larger than ASICPUTA_ORIG.
-These accumulated fields are also now deaccumulated:
ASITET ASITRT ASITCBTA_LF ASIIOCNT_S ASITRCA_S
Thanks to Kurt Gramling, TSYS, USA.
Change 35.248 Variables QWA225SS and QWB225SS are now kept in DB2STATS,
VMACDB2 and two new-in-DB2 V12 REAL2G variables are input/kept.
Nov 1, 2017 QWA225SS='DBM1*31-BIT*IN-USE*SYSTEM*AGENTS'
QWB225SS='DIST*31-BIT*IN-USE*SYSTEM*AGENTS'
QWA225HVPAGESINREAL2G='DBM1*HVPAGES*IN*REAL2G'
QWB225HVPAGESINREAL2G='DIST*HVPAGES*IN*REAL2G'
Thanks to Rick Southby, IAG, AUSTRALIA.
Change 35.247 Removed a debugging statement and corrected an 'uninit'
ANALDB2R variable message
Oct 30, 2017 -If you used INTERVAL=, BEGTIME=, or ENDTIME= and did not
specify a SORTBY= the default is BY QWHSSSID QWHCPLAN and
QWHCAID, so datetime variable QWACBSC is not carried
forward and no accounting report was created; this could
also cause duplicate variables in SORTBY list if QPACPKIC
PACKTYPE or QWHSTCK were in the tailored SORTBY list.
Change 35.246 -SMF 113/HIS formulas for the z14 were updated by IBM with
ASUM113 L3P changed, which is also impacted the RNI value which
VMAC113 uses L3P.
VMACVMXA -The z13 code set the SM1132SP Speed value to 5000 because
Oct 27, 2017 the value was wrong, but that code was removed for the
z14, as those records contain the expected 5208 MHz.
-John's updated formulas are available at
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TC000066
Thanks to John P. Burg, IBM, USA.
Thanks to Nick Varley, SYNCSORT, USA.
Change 35.245 SMF 119 Subtype 81 INPUT STATEMENT EXCEEDED because MXG
VMAC119 expected full 4096 length for DIRU and DORU fields; now
Oct 27, 2017 DILEN and DOLEN length of text are used for $VARYING4096.
Thanks to David Campbell, Sun Trust, USA.
Change 35.244 New parameters TRNDKEEP and SPINKEEP added to let you
VMXGALOC control how many copies of each are retained.
Oct 27, 2017
Change 35.243 MOBILE WORK CSV files for CICS/TS 5.3+ were missing the
FORMATS CICS Product Number; format MGIBMCI needed a new entries
Nov 1, 2017 with 70='5655-Y04' and 71='5655-Y04'.
Other related formats were also updated.
Thanks to Patrick J. Holloman, Navy Federal Credit Union, USA.
Change 35.242 Support for Power Exchange Version 10.1.1.
VMACPOEX
Oct 25, 2017
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 35.241 -Typo, NEDNC=SMFTIME should be NENDC=SMFTIME.
ANAL119 -Uninit variables and incorrect date corrected 12/31.
Oct 23, 2017
Dec 31, 2017
Thanks to Jon Whitcomb, Great Lakes Educational Loan Service, USA.
Thanks to Earl Kline, Luminex, USA.
Change 35.240 Support for APARs OA52132, OA52133, and OA61734, some of
VMAC42 which fields were listed in the z/OS 2.3 SMF Manual.
Oct 23, 2017 CODE HAS NOT BEEN TESTED WITH NEW RECORDS.
See Change 35.288.
Change 35.239 MXG 34.09. RMFINTRV fails with macro GOT70PR not resolved
VMXGRMFI when the PDB did not contain the expected PDB.TYPE70PR.
Oct 22, 2017
Thanks to Tracy Davidson, USBank. USA.
Change 35.238 A typo BASEWEEJ should have been BASEWEEK - only affected
VMXGALOC the aging off of old WEEK directories.
Oct 22, 2017
Change 35.237 Internal utility; if the LIBNAME being searched was empty
VGETSORT a spurious message about an invalid DO loop was printed.
Oct 20, 2017
Change 35.236 Duplicate SMF 70 Subtype 1 records can cause bad results
DEDUP701 due to the Split 70s duplicates, added SMT merges and the
Oct 20, 2017 multiple datasets that create TYPE70 that prevent the use
of the normal NODUP in the final sort to remove dupes.
Hash logic from ANALDUPE is executed in the IMACFILE exit
as SMF is read, examining only SMF 70 subtype 1, deleting
duplicates prior to their input and reporting the first
three DUPES on the log if any were found.
You enable the 70 subtype 1 duplicate removal with
//SYSIN DD *
%let macfile=%quote(%include sourclib(dedup701););
Thanks to MP Welch, Bank of America, USA.
Thanks to Garth Bloomfield, DXC Technology, AUSTRALIA.
Thanks to Peter Gray, DXC Technology, AUSTRALIA.
Change 35.235 RMF III ZRBCPU is enhanced with CPC_HOMEFLAG decoded:
VMACRMFV CPCCAPAVAIL='CAPACITY*VALUES*AVAILABLE?'
Oct 20, 2017 CPCVARYCPU ='VARYCPU*OPTION*SET?'
CPCLPARMGT ='WLM*LPAR*MANAGEMENT*ENABLED?'
CPCMTMETRIC='MULTI*THREADING*METRICS*AVAILABLE?'
CPCABSMSU ='ABSMSU*CAPPING*OPTION*SET?'
Thanks to MP Welch, Bank of America, USA.
Change 35.234 BUILDPDB/BUILDPD3 exit EXPDBKEP lets you KEEP= or DROP=
BUILD005 all variables in JOBS/STEPS/SMFINTRV/NJEPURGE/PRINT.
BUIL3005 Macros _KDBJOBS/_KDBSTEPS/_KDB30UV/_KDBNJEP/_KDBPRIN
EXPDBKEP were defined but were not referenced. You put all your
Oct 21, 2017 definitions in EXPDBKEP in your USERID.SOURCLIB using
MACRO _DBJOBS KEEP= A B C D . . %
or
MACRO _DBJOBS DROP= A B C D . . %
and then you instantiate them in BUILDPDB SYSIN using
%LET MACKEEP= %QUOTE( %INC SOURCLIB(EXPDBKEP); );
%INCLUDE SOURCLIB(BUILDPDB);
Thanks to Thomas Orlando, UBS, SWITZERLAND.
Change 35.233 Protection for truncated SMF 80 Extended Relocate segment
VMAC80A with 12 fields expected but only 10.5 fields are in the
Oct 19, 2017 SMF record. MXGERROR for the first three instances.
Record may have been truncated by ftp processing.
Change 35.232 Documentation. The zIIP CPU time for BMC Utilities is
TYPE30 not recorded in SMF 30 records for the JOB/ASID of the
Oct 19, 2017 Batch Utility job, but is in the 30s for BMC's XBM
Started Task. IBM Utilities do record zIIP CPU time in
the SMF 30 for the batch job.
Change 35.231 Macro variable RACFDIRECTED allows DELETE of RACF records
VMAC80A using the SMF80DTP/RACFTYPE=44 relocate segment, using
VMXGINIT segments with the subkeyword/EV44TXT='ORIGINATED_FROM'.
Oct 18, 2017 MXG now populates variables NODE80A USERID and DIRECTED
Dec 7, 2017 with values of DIRECTED_BY_AT, DIRECTED_BY_ONLY_AT or
DIRECTED_AUTOMATICALLY. You would use this syntax:
%LET RACFDIRECTED=
%QUOTE( IF NODE80A IN ('NODE1','NODE2') AND
USERID IN ('USERID1','USERID2')
THEN DELETE; ) ;
%INCLUDE SOURCLIB(TYPS80A);
-Dec 7: NODE was changed to NODE80A to avoid a conflict if
TYPE80A and TYPE6 were used together. The three fields
are created for the test but are not kept.
Thanks to Kerry J. Sommers, John Deere, USA.
Thanks to Joan T. Keemle, John Deere, USA.
Thanks to Francois Vancoppenolle, P&V Group, BELGIUM.
Change 35.230 -GRAFCEC adds graphs of CPU and zIIP hours and the 4HR MSU
GRAFCEC Avg consumption. GRAFCEC now creates all of the charts
GRAFLPAR previously produced by GRAFLPAR, plus some new ones, thus
Oct 17, 2017 GRAFLPAR obsolete. And GRAFCEC now allows multiple input
libnames. Dataset ASUMCELP must exist in the first data
library and must have non-zero obs, or GRAFCEC will die
with a dataset not found error.
-GRAFLPAR error if you specified PDB=PDB PDB1 and using
SAS/GRAPH, it failed trying to write the graphics catalog
to two libnames. Catalog will only be written to the
first of the two or more libnames specified by PDB=.
But note GRAFLPAR is now obsolete, replaced by GRAFCEC.
Thanks to Daniel Mckinzie, Zions Bank, USA.
Change 35.229 -Revised logic for DB2 Statistics Datasets deaccumulation
VMACDB2 now protects for lost/skipped intervals of input data for
Oct 23, 2017 for these datasets:
DB2STATB DB2STSBP DB2GBPST DB2NETZA
DB2STAT5 DB2STAT0 DB2STAT1 DB2STATR.
Large gaps (like missing a day) with repeated values in
QWHSISEQ caused large DURATM which caused BEGTIME to be a
different date. Since DB2 SMF 100 stat records can only
be written at one minute intervals, MXG now detects a gap
of more than 120 second as the start of a new interval,
and it is DIF()'d but not output.
However, neither BEGTIME nor ENDTIME are on the minute
DURATM values of a few seconds up to 100 seconds have
been observed, hence the test value of 120 seconds.
-DB2STATS Variables QISEDPSL QISEDPSC QISEDPSM QISEDPSF
were incorrectly input with DB2 V11; the test GE 32 is
corrected to GE 232 for their input.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.228 Support for up to 20 user character fields in CICSTRAN,
IMACICAU USERCHAR1-USERCHAR20, increased from only nine fields.
IMACICBU
IMACICCU
IMACICDU
IMACICEU
IMACICFU
IMACICGU
IMACICHU
IMACICIU
IMACICJU
IMACICKU
IMACICLU
UTILEXCL
VMAC110
Oct 11, 2017
Change 35.227 If you specified RMFINTRV=NO many bad things could have
UTILBLDP happened. First, if you did not also suppress one or
Oct 17, 2017 more of the records used by BUILDPDB, then RMFINTRV=NO
was ignored because the code looking for it was inside
of the SUPPRESS= logic. If you DID suppress something
then you could have hit a problem with a missing %
sign on a MACRO.
-User ABENDS are replaced by messages on the OUTFILE to
tell you there was an error that terminated UTILBLDP.
-if you suppress type 26 without specifying J2 or J3
it will now generate an error
-if you useradd 102 without specifying the subtype
it will now generate an error
Thanks to Trevor Holland, ANZ, AUSTRALIA.
Change 35.226 Unused Change Number.
Change 35.225 WARNING: VARIABLE YSTEM NEVER REFERENCED because SYSTEM
VMACTMO2 was missing the first S.
Oct 10, 2017
Thanks to Derek Purves, FDIC, USA.
Change 35.225 -New UTILBLDP Parameters EXPDBVAR/EXPDBCDE/EXPDBOUT added
UTILBLDP to enable more tailoring and specifically to make it easy
Oct 8, 2017 to create a new dataset with a subset of variables and
obs from an existing MXG dataset, like this example to
create new CICSTRIM dataset with a subset of CICSTRAN
variables, and output only for selected CICS APPLIDs:
USE EXPDBVAR TO BUILD A SUBSET OF CICSTRAN DATA FOR
REPORTING PURPOSES
%UTILBLDP(OUTFILE=INSTREAM,
BUILDPDB=YES,
OUTFILE=INSTREAM,
EXPDBVAR=
CICSTRIM (KEEP=APPLID TRANNAME STRTTIME ENDTIME
CPUTM ELAPSTM TASKNR USER ABCODE),
EXPDBOUT=
PROC SORT DATA=CICSTRIM OUT=PDB.CICSTRIM;
BY ENDTIME APPLID TRANNAME TASKNR;,
MACKEEPX=
MACRO _ECICTRN
IF (RTYPE= 'E3'X OR RTYPE = 'T')
AND APPLID
IN('CICSZFN3','CICSAUD3','CICSDBS')
THEN OUTPUT CICSTRIM;
OUTTPUT _WCICTRN; %
);
Change 35.224 The _N110 "Product Null Macro" to suppress all CICS data
VMAC110 sets for tailoring had new datasets added which caused
Oct 8, 2017 only one dataset listed per line; that statement now has
two datasets per line, half as many lines/bytes.
Change 35.223 The extra zVPS/XAM SYTCUP segment with totals was not
VMACXAM included in the SYTNLPS count of segments, and there is
Oct 7, 2017 no LENDATA value for each subsegment, so MXG assumed 20
for LENDATA and detected the extra subsegment when SEGLEN
was NE 20*SYTNLPS, but the 35.09 correction statement
SYTNLPS=SYTNLPS+1 was mistyped as SYTNLPS=SYTNLPS=1; so
only one obs per LPAR was output in XAMSYT dataset.
But other MXG corrections have increased the obs count,
depending on past MXG Version (eg. 35.06 to 35.09).
There will be one obs for each LCPUADDR in each LPARNAME,
and an extra "total" obs with LCPUADDR='60'x (doc '40'x)
for each Engine Type in each LPARNAME, but these "total"
obs all have zero values in 4303 and 4313 releases.
There are also a pair of original LPARNAME='Totals'
subsegments at the start of each SYTCUP segment that are
not output by MXG.
Thanks to Paul Volpi, UHC, USA.
Thanks to David A. Sadler, UHC, USA.
Change 35.222 Unused Change Number
Change 35.221 Many zVM VXPRCPUP dataset variables values were not
VMACVMXA divided by 65536, two variables needed deaccumulation.
Oct 4, 2017 The segment SSIZE is 96 but only 72 are documented.
Thanks to Pat Hansen, ADP, USA.
Thanks to Mike Chaves, ADP, USA.
Change 35.220 MXG 35.09. Zero observations in TYP11920 dataset due to
VMAC119 a debugging asterisk left where it shouldn't have been in
Oct 4, 2017 line 2942 of VMAC119.
Thanks to Paul Volpi, UHC, USA.
Change 35.219 MQMACCT variable NETSNAME is created from QWHCTOKN if it
VMAC116 is populated, or from QWHCNID in not, but the format of
Oct 4, 2017 the raw data is different; heuristics were revised to
recognize two formats found in this site's data, with
values AAAAAAAA.BBBBBBBB if QWHCTOKN is populated or
values CCCCCCCC.L when QWHCTOKN is not populated.
NETSNAME is also kept in MQMACCT1 and MQMQUEUE but it
should not have been, as it is always blank for those two
datasets. And NETSNAME is not populated in MQMACCT
observations from BATCH/TSO Attach.
Thanks to Jim Poletti, Edward D Jones, USA.
Thanks to Art Morelock, Edward D Jones, USA.
Change 35.218 XAMSYPUP dataset's INPUT is now correctly aligned once it
VMACXAM was explained that PL/1 "3 rsrvd(4) Char(4)" is SAS +16.
Oct 3, 2017
====== Changes thru 35.217 are in this MXG 35.09 dated Oct 2, 2017=====
Change 35.217 Cosmetic, but format $MGSMFID had undetected-by-SAS
ANALID unbalanced quotes that impacted SMF ID=80 descriptions in
FORMATS the ANALID SMF Report (default is on in BUILDPDB).
Oct 2, 2017 Also option UNIFORM was added to the SUMMARY PROC PRINTs.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.216 New macro that lets you 'join' variables from DB2ACCT
JOINDB2 to the corresponding DB2ACCTP observations. Written
Oct 2, 2017 specifically to capture QWACWLME since the DB2ACCTP
records do not contain the QWAC segments but will
copy as many variables as you like from DB2ACCT to
DB2ACCTP. NOTE: QWACWLME only exists in DDF records
and that is by IBM's design.
====== Changes thru 35.215 are in this MXG 35.09 dated Oct 2, 2017=====
Change 35.215 TRENDINT defaulted to WEEK rather than the value of the
VMXGRMFI INTTRND macro variable as documented. Also the TRNDRMFI
TRNDRMFI member was updated to include the TRENDINT parameter so
Oct 2, 2017 that you can more easily see how to modify the interval.
Thanks to Steve Carlson, UCOP, USA.
Change 35.214 Modified for efficiency. If you specify ROLLSORT=NO
UTILROLL it now uses PROC APPEND instead of a data step which had
Sep 30, 2017 to read both the input (ROLLTO) and output (ROLLFROM)
datasets.
Change 35.213 z/VM variable VMDUFACT in dataset PDB.VXBYUSR should not
VMACVMXA have been deaccumulated as it is an end of interval count
Sep 28, 2017 of frames.
Thanks to Graham Harris, RBS, ENGLAND.
Change 35.212 Support for SMF 30 User Key CSA Audit Enhancements adds
VMAC30 new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and
Sep 28, 2017 the TYPE30_5 datasets. This code change has been in MXG
Feb 28, 2018 35.09 and later, but this change text replaced previous
"Reserved Change" on Feb 28, 2018. This field was added
by APAR OA53355, but will only be needed thru z/OS 2.3,
as User Key Common Storage usage support ends there.
This is Health Check ZOSMIGV22R3_NEXT_VSM_USERKEYCOMM.
These APARs required no additional code changes:
OA53434 Corrects ASM DSECT Lengths, no MXG impact
OA53289 Corrects value of SMF30HVR from zero to valid.
OA45767 APAR that added the extra triplet caused OA53434
Change 35.211 Documentation. Variables QWACWLME QWACBSC QWACESC should
VMACDB2 not have been kept in DB2ACCTP after IBM moved the DB2
Sep 27, 2017 Package Data (IFCID 129) to its own ID=101 Subtype=1
record, which does not contain a QWAC segment.
Thanks to Glen Bowman, Wakefern, USA.
Change 35.210 Support for z14 SMF 113 records (INCOMPAT, EXTENDED array
ASUM113 now has 128 entries). Default LABELs are now for z14.
VMAC113 To change the default labels for z13, you would use:
Sep 27, 2017 //SYSIN DD *
Oct 1, 2017 %LET MACKEEP= MACRO _XLA113 _XLA113D % ;
%INCLUDE SOURCLIB(TYPS113,ASUM113);
To create correct labels with both z13 and z14 data, you
must create separate datasets:
//SYSIN DD *
%INCLUDE SOURCLIB(VMACF113);
DATA PDB.ASUM1131Z13;
LABEL _XLA113D ;
SET PDB.ASUM1131;
IF SM113VN2=4;
DATA PDB.ASUM1131Z14;
LABEL _XLA113E ;
SET PDB.ASUM1131;
IF SM113VN2=5;
RUN;
Many of the RNI and other equations were changed for z14.
-You can use OPTIONS OBS=99; _RPT113; RUN; to print those
calculated variables values from PDB.ASUM1131, the data
set you should use, as it contains interval data. The
original ASUM113 data set was accumulated and obs were
lost in deaccumulation.
Thanks to Elie Sawaya, RBC, CANADA.
Change 35.209 -Support for BETA 93 Version 610, altered header fields
FORMATS and three new variables are added to dataset BETA0:
VMACBETA BETAPABS='MAX*PABS'
Sep 29, 2017 BETASPAG='FIRST SPLIT*OVER GT*1 PAB'
Nov 22, 2017 BETABMOD='PAB PAGE*BREAK*MODE'
-New values added to $MGBETAT format for BETA0.
-Support for subtype 51 RDATA1 and RDATA2 fields and
all segments are read and output - previously the first
segment was repetitively output.
See Change 36.074 for Subtype 51 update.
Thanks to Andreas Menne, Finanz Infoirmatik, GERMANY.
Change 35.208 Nigel's Monitor for AIX and LINUX changed BBBP Endtime
VMACNMON was always "HH:MM" text, but new "N MINS" tripped MXG
Sep 27, 2017 variables BBBPENDING051, UPHOURS, and BBBPENDING052,
UPTIME.
Thanks to Steve McCulloch, TMS/CDS Group, CANADA.
Change 35.207 Enhancement for GDG datasets to add FIRSTGEN and LASTGEN
VMAC6156 values of GATGEN to know the range of Generation values.
Sep 25, 2017 No change, but variables GATEXTNO GATVER GATGEN GATWRAP
are from each GAT segment, so they should not have been
kept as they contain only the value of the last cell.
Thanks to Satish Kodavatiganti, John Deere, USA.
Change 35.206 If you need ACCOUNTn fields for long-running STCs in your
BUILD005 PDB.SMFINTRV dataset, you had to set SPINCNT in IMACSPIN
BUIL3005 longer than the number of days between IPLs; if you had a
VMXGINIT smaller value, then only that number of days of the
Sep 25, 2017 PDB.SMFINTRV would have the ACCOUNTn fields populated.
This change creates optional macro variable &SPINSTC to
enable this change and to keep that many day's SPIN30_1
for STCs in the SPIN library for STC accounting, and you
can then set a much smaller value for the spining of you
other jobs. Use %LET SPINSTC=365; to keep a year's data.
A large SPINCNT used to be important when you had lots
of held print output, since BUILDPDB waits for the
PURGE (26) record to know all SMF records for the job
have been created. But now, with output typically sent
to a spool handler, almost all jobs PURGE right after
they terminate on z/OS, so now, you can set a small
SPINCNT (1 or 2) and only SPIN the jobs that were in
execution when SMF was dumped, or that run for more
than a full day or two.
Thanks to Gennady Katsnelson, IBM Global Technology Services, USA.
Change 35.205 Documentation of what is counted in SMF 30 EXCP counts,
TYPE30 from a posting to IBM-Main:
Sep 25, 2017 The EXCP count fields count whatever the IOS Driver
decided to pass into SMF in the IFASMFEX exit that
accumulates the type 30 EXCP fields.
For example:
-For SAM, EXCP (an IOS driver) lets SAM do the calls
to IEASMFEX.
-For non-SAM use of EXCP, EXCP calls IEASMFEX with
a count of 1 so for non-SAM use of EXCP, it is the
count of EXCPs
-And IEWFETCH (an IOS driver which fetches load modules)
counts the number of SSCH for non-VIO data sets, and
uses EXCP for VIO data sets. So either way, it is the
number of channel programs executed.
Thanks to Jim Mulder z/OS Diagnosis,Design,Development,Test IBM Corp
Change 35.204 Support for DB2 APARs PI71903 and PI84045 adds these
VMAC102 new variables to IFCID 376 T102S376 dataset:
Sep 28, 2017 QW0376SC='SCHEMA*NAME'
Oct 11, 2017 QW0376PR='SPECIFIC*NAME'
Dec 7, 2017 QW0376INC='INCOMPAT*PARMS'
QW0376SQL='SQL*TEXT';
Dec 7: Offsets for VL/VN corrected, no data for these
new fields yet.
Thanks to Lori A. Masulis, FMR, USA
Thanks to Steve McKee, FMR, USA.
Change 35.203 z/VM 6.4.17.1 INCOMPATIBLE, fields inserted in SYTCUP and
EXSYTLCX SYTLCK, and new VXSYTLCX data set created.
VMACVMXA -In SYTLCK when there are no shared/exclusive lock entries
VMXGINIT (CALNMSXE=0) there are 8 bytes inserted where that second
Sep 28, 2017 array should not have existed.
-In SYTCUP, SKIP logic was not correct with new data.
Thanks to Dr. Wolfgang Kueller, IT Solutions, AUSTRIA
Change 35.202 Typo TEN should have been TUE. Most likely not an issue
VMXGALOC since that section of code was only used to CLEAR any
Sep 18, 2017 exising LIBNAMEs before allocating new ones (which in
any case would happen when a new LIBNAME statement was
issued).
Thanks to Steve Bagshaw, Marks & Spencer, ENGLAND.
Change 35.201 Modified to limit the number of LIBNAMEs reported where
PDBAUDIT the path name is the same. First looks for a PATH where
Sep 18, 2017 the LIBNAME is PDB and deletes any other LIBNAMEs with
that path then sorts on PATH and LIBNAME eliminating
all but the first occurrence of each PATH so that there
are not a lot of duplicate lists. Needed for MXG QA.
-A new parameter PATHLIST= added with a default value
of NO. Change to YES to create report of the LIBNAMES
by PATH. Useful if you are running with AUTOALOC=YES.
Change 35.200 New BLDSMPDB parameters support writing daily, weekly,
VMXGALOC monthly and trend "PDB's" to different paths (drives or
VGETALOC directories). All default to the BASEDIR if left blank.
BLDSMPDB BASEWEEK= sets the location of weekly database
Sep 13, 2017 BASEMONTH= sets the location of monthly database
BASETREND= sets the location of TREND database
If you choose to use these new destinations for your
output of BLDSMPDB, be aware and use caution since the
old destination's files will NOT be aged off, nor will
they be allocated for monthly/weekly processing. You will
need to copy old data from the old path to the new path.
Change 35.199 z/OS 2.3 type 90 subtype 38 INPUT STATEMENT EXCEEDED due
VMAC90A to incorrect offset and field length in the GA SMF manual
Sep 17, 2017 for SMF90T38_UTOKENUSERID which is 16 not 8 and at offset
112 and not 118. Subtype 38/39 datetimes are now local.
Thanks to Bernie Ethridge, Fiserv, USA.
Thanks to Paul Naddeo, Fiserv, USA.
Change 35.198 z/VM 6.2.11 SYTLCK "BROKEN RECORD" error because SKIP was
VMACVMXA not calculated correctly.
Sep 11, 2017
Thanks to Kare Martin Torsvik, EVRY, NORWAY.
Change 35.197 IMF CIMSTRAN dataset datetime variables all now have
VMACCIMS microsecond resolution; MXG had overlooked the MIJUs.
Sep 16, 2017 ACTARRV ARRVTIME STRTTIME TRNETIME ENDTIME TRNSTCKE
Oct 26, 2017 INPQUETM, SERVICTM and RESPNSTM are now calculated from
those datetimes for microsecond resolution.
Thanks to Randy Hewitt, DXC Technology, USA.
Change 35.196 Support for BETA 97 extended header (INCOMPATIBLE) V 610.
EXTYB97D All variables in all datasets are now INPUT and correct.
IMACBE97 New dataset BE979751D is created from Subtype 51 with the
VMACBE97 database field details.
VMXGINIT
Sep 15, 2017
Thanks to Andreas Menne, Finanz Infoirmatik, GERMANY.
Change 35.195 Support for PRCPUP segment in zVPS XAMSYS records creates
EXXAMPUP new dataset DDDDDD DATASET DESCRIPTION
IMACXAM XAMPUP XAMSYPUP PRCPUP DATA
VMACXAM -The test for invalid SYTCUP segment was revised when the
VMXGINIT old test incorrectly reported an invalid segment.
Sep 15, 2017
Change 35.194 Unrequested log messages containing MXGDEBUG: VMXGOPTR
ANAL116 were printed if you %LET MXGDEBUG= to a non-blank value.
ANALDB2R The LENGTH(&MXGDEBUG) test was removed from VPUTMSG and
ASUMDB2A relocated to each calling member, with revised logic:
ASUMDB2R %IF %UPCASE(&MXGDEBUG) NE VMXGSUM1 %THEN %DO;
ASUMNTIN %VMXGOPTR(OPTNAME=NOTES,NEWVALUE=NONOTES);
TESTTRND %END;
TRNDNTIN The MXGDEBUG macro variable is primarily for internal MXG
VGETALOC testing and it exists in only a few members; the enable
VMACDB2 values are documented in each member's test statements.
VMXG70PR With this correction. MXGDEBUG=VMXGSUM1 was used for MXG
VMXGALOC QA which exposed these overlooked corrections:
VMXGDSN -ASUMDB2A QXHJINT typo was observed and removed.
VMXGOPTR -VMXG70PR LPMSUHR was missing.
VMXGRMFI -ANAL116 had a superfluous ID=ENDDT argument, removed.
VMXGSUM -VGETALOC/VMXGALOC protected for blank MXGDEBUG.
VPUTMSG -VMXGSUM many calls to VPUTMSG revised so VMXGSUM1 now
Sep 10, 2017 is also enabled if 2/3/4 are requested.
-VMACDB2 did not keep SHIFT in DB2ACCTR dataset.
-VMXGRMFI had spurious SMF70GMN SMF70GMU MXGDEBUGs.
-ASUMNTIN did not keep one variable
-TESTTRND builds PDB.CICS from ASUMCICX, clearing the
first PDB.CICS created by ASUMCICS which had different
kept variables and is not the recommended CICS summary.
-ASUMDB2R needs KEEPALL=YES for missing variable notes.
-TRNDNTIN needed a variable added to KEEP list.
Thanks to Donald Blaszka, WiPro, USA.
Change 35.193 Alignment correction for SMF74SBR/SBW/SQR/SQW sync I/O
VMAC74 variables, and new SMF74SQRRATE/SMF74SQWRATE sync rates.
Aug 30, 2017
Change 35.192 Variables WTASINTE/WTASINTS/WTASSTRT in MQMQUEUE dataset
VMAC116 are missing values in obs created from SMF 116 Subtype 2
Aug 29, 2017 (continuation) records, but now INTS/STRT are populated
by WQTTTIME and INTE is populated by SMFTIME.
Thanks to Raymond J. Smith, OPTUM, USA.
Change 35.191 -Support for z/OS 2.3 ZRBASI and ZRBUWD new fields are now
VMACRMFV validated so the bypass execution tests (-99 EQ 99) are
Sep 5, 2017 are now removed.
-Variable GEIFLG2 is now INPUT and kept in ZRBGEI dataset.
-Unpopulated Extended Length EDE segment overlaid original
INPUT of variables EDEPCKG EDEPROC EDEUSER EDETRXN EDEACC
with blank values.
-Overlooked OPD variables now INPUT and kept:
OPDDCTIIP='DELTA*TCB TIME*FOR*ZIIP'
OPDCTIIP='PROCESS*SYSTEM*USER COMPUTE*ON ZIIP'
Thanks to Kurt Gramling, T-SYS, USA.
Change 35.190 SMF type 2 subtype 2 (SMF Signature enabled), ERROR INPUT
VMAC0203 EXCEEDED RECORD LENGTH due to MXG INPUT mis-alignment.
VMACSMF -Dataset TYPE0202 now keeps those signature variables, and
Aug 28, 2017 dataset TYPE0203 reverts to the way it originally was,
keeping only the header variables.
-BUT: the type 2 subtype 1/2 records have SYSTEM='DUMY'
in the SMF header! Since that is not a real system name,
and because it could confuse any SMF Audit or analysis,
MXG's handling of the _SMF header in VMACSMF now detects
type=2 subtype=1/2 and SYSTEM='DUMY' and changes SYSTEM
to the actual SYSTEM (SMF2IRSID/SMF2GRSID) name.
Thanks to Daniel Erikols, Svenska Handelsbanken, SWEDEN.
Change 35.189 Variables QPAC_PIPE_WAIT and QPAC_PIPE_COUNT are INPUT
VMACDB2 and kept in dataset DB2ACCTP.
Aug 25, 2017
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.188 If default was set to "work" rather than "WORK" the case
VMXGDEL mismatch caused datasets to be deleted,
Aug 25, 2017
Change 35.187 Variable SM123USERNM was not kept, spelled SM123TARURI in
VMAC123A the KEEP= list.
Aug 23, 2017
Thanks to Patricia Hansen, ADP, USA.
====== Changes thru 35.186 are in this MXG 35.08 dated Aug 24, 2017=====
Change 35.186 New variables MKFLAGA/MKRLSOPT/MKLRTIME are created and
VMACEDGS kept in EDGSKREC dataset; variable MKSTORE2 is no longer
Aug 23, 2017 valid, as it now contains the time part of MKLRTIME.
Aug 25, 2017 MKLRTIME='LAST*REFERENCE*DATETIME'
MKFLAGA ='FLAG-A'
MKRLSOPT='RELEASE OPTIONS'
-Aug 25: MKLRTIME was missing value because 2-byte field
before the new date value was not documented, but the
hex record and doc offset showed 2 bytes were inserted.
Thanks to Marybeth Delphia, CPA Texas, USA.
Change 35.185 Change 35.167 forced you to have a PDB libname when you
BLDSMPDB may not have needed one. There are 4 executions of
Aug 22, 2017 VGETSORT within BLDSMPDB with differing needs.
If running with RUNWEEK=YES the LIBNAME pointed to by
WEEKSTRT is used
If running with RUNWEEK=WTD the LIBNAME pointed to by
PDB is used
If running with RUNMNTH=YES the LIBNAME pointed to by
WEEK1 is used
If running with RUNMNTH=MTD the LIBNAME pointed to by
PDB is used
Change 35.184 Test for LIBNAME count was removed as unneeded and it
PDBAUDIT caused termination of the QA test job with 35 libraries,
Aug 23, 2017 and PDB.PDBAUDIT and SPIN.SPINAUDIT datasets not created.
The original error it was supposed to prevent was found
to be unrelated the LIBNAME count.
Change 35.183 Five IFCIDS create new datasets, but only T102S389 and
EX102389 T102S477 have the IFCID-specific variables; the three
EX102404 others identify the event, but keep only the thirty-six
EX102413 variables from the DB2 Header and Product segments.
EX102414 DDDDDD DATASET DESCRIPTION
EX102477 102389 T102S389 ALL INDEXES WITH FTPS
IMAC102 102404 T102S404 AUTHORIZATION COMPATIBILITY
VMAC102 102413 T102S413 BEGIN WAIT FOR PIPE SUSPEND
VMXGINIT 102414 T102S414 END WAIT FOR PIPE SUSPEND
Aug 22, 2017 102477 T102S477 ALOC/DEALOC FAST TRAVERSE BLOCK
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 35.182 MXG 35.07. INPUT STATEMENT EXCEEDED RMF 74, Change 35.166
VMAC74 tested SMF748LL instead of SMF748CL for the INPUT of the
Aug 17, 2017 new field, which "worked" when there were link segments,
but this record had only the control segment and non-zero
R748CRTN Return Code.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 35.181 Support for four new SYTSTSCP variables added:
VMACXAM
Aug 16, 2017
Change 35.180 MXG 35.07. SMF 92 Subtype 50 INPUT STATEMENT EXCEEDED due
VMAC92 to MXG typo of 44 vs 4 in the INPUT, but also the 16-byte
Aug 18, 2017 STCKE format SMF92T50 was not decoded correctly. IBM also
changed the format of SMF92RVN from NUM2. to PIB2., which
caused INVALID DATA FOR SMF92RVN error messages.
Change 35.179 Utility reads SMF and writes records for wanted JOBnames.
UWRITSMF
Aug 16, 2017
Change 35.178 Support for APAR OA49692 which adds variables to the BCP
VMAC98 SMF type 98 record:
Aug 14, 2017
SM98SIG_AVG_CPUBUSY_CP='AV CP PCT*CPU BUSY*HIGH MTTW*/
SM98SIG_AVG_CPUBUSY_ZAAP='AV ZAAP PCT*CPU BUSY*HIGH MTTW*/
SM98SIG_AVG_CPUBUSYR_ZIIP='AV ZIIP PCT*CPU BUSY*HIGH MTTW*/
SM98SIG_AVG_FDISPSPERWAKEUP_CP='AV CP FOREIGN*DISPATCHES*HIGH MTTW*/
SM98SIG_AVG_FDISPSPERWAKEUP_ZAAP='AV ZAAP FOREIGN*DISPATCHS*HIGH MTTW*/
SM98SIG_AVG_FDISPSPERWAKEUP_ZIIP='AV ZIIP FOREIGN*DISPATCHS*HIGH MTTW*/
SM98SIG_TOP_CPU_CP='CP CPU WITH*LARGEST*MTTW VALUE*/
SM98SIG_TOP_CPU_ZAAP='ZAAP CPU WITH*LARGEST*MTTW VALUE*/
SM98SIG_TOP_CPU_ZIIP='ZIIP CPU WITH*LARGEST*MTTW VALUE*/
SM98SIG_2ND_CPU_CP='CP CPU*2ND LARGEST*MTTW VALUE*/
SM98SIG_2ND_CPU_ZAAP='ZAAP CPU*2ND LARGEST*MTTW VALUE*/
SM98SIG_2ND_CPU_ZIIP='ZIIP CPU*2ND LARGEST*MTTW VALUE*/
SM98SIG_TOP2_MTTW_CP_TIMETOD='AV MTTW VALUE*FOR TOP*CP CPUS*/
SM98SIG_TOP2_MTTW_ZAAP_TIMETOD='AV MTTW VALUE*FOR TOP*ZAAP CPUS*/
SM98SIG_TOP2_MTTW_ZIIP_TIMETOD='AV MTTW VALUE*FOR TOP*ZIIP CPUS*/
SM98AVG_FDISPSPERWAKEUP_CP='AV FOREIGN*DISPATCHES*CP CPUS*/
SM98AVG_FDISPSPERWAKEUP_ZAAP='AV FOREIGN*DISPATCHES*ZAAP CPUS*/
SM98AVG_FDISPSPERWAKEUP_ZIIP='AV FOREIGN*DISPATCHES*ZIIP CPUS*/
Change 35.177 PDB.ROSCOE dataset Logon Time ROSIGNON was incorrectly
VMACROSC set to the ROSTIME, Roscoe ASID Step Initiate Time, also
Aug 11, 2017 causing thee CONECTTM calculation to be incorrect.
Thanks to Janne Jarvinen, CGI, FINLAND.
Change 35.176 Support for new BBMQ QSDSTYPE='DISTRIBUTED*SYSTEM*TYPE'
FORMATS variable added (compatibly) to BBMQQUES dataset with new
VMACBBMQ $MGBBMQT format decoding A=AS400, W=Windows, U=Unix.
Aug 10, 2017
Change 35.175 Support for these APARs required no MXG code changes:
VMAC30 OA53289 Corrects value of SMF30HVR from zero to valid.
Aug 9, 2017 OA53434 Corrects ASM DSECT Lengths, no MXG impact
OA45767 APAR that added the extra triplet caused OA53434
Change 35.174 The original CPITCBTM/CPISRBTM "step initiator" CPU times
BUILD005 are totals, but CPITCITM CPISRITM are the "init" time of
BUIL3005 day, at step initiation, and CPITCTTM CPISRTTM are the
Aug 8, 2017 "term" time of day so those CPU times can be assigned to
the correct time of day (ALOCTIME or TERMTIME). All four
are now kept in both PDB.STEPS and PDB.JOBS.
that separated the original CPITCBTM/CPISRBTM
are now correctly input and are negatively deaccumulated
Thanks to David E. Kibitelsky, Broadridge, USA.
Change 35.174A zVM VXBYUSR dataset variables _MT1 and _PRO (SMT times)
VMACVMXA are now correctly input and are negatively deaccumulated
Aug 5, 2017 with -DIF() while many CALxxxxx accumulated variables are
positively DIF'ed, with no clue in the doc if the accum
is descending or ascending, except to look at data.
Change 35.173 Support for SMF 119 Subtype 11 for ZERT data creates two
EXT11911 new datasets
EXT119DN DDDDDD DATASET DESCRIPTION
FORMATS T11911 TYP11911 ZERT ENCRYPTION SUBTYPE
IMAC119 T119DN TYP119DN ZERT DISTINGUISHED NAME
VMAC119 -There is no GMT offset in Subtype 11 records; for the
VMXGINIT SAEVENT 03x and 04x Termination records, SAETIME is used
Aug 4, 2017 and for 01x and 02x Connection records, SASTIME is used
Aug 20, 2017 with SMFTIME and fuzzy logic to reset SASTIME/SAETIME to
Aug 30, 2017 the local time zone.
-Only records with TLS or SSH protocol have been tested
with data; no IP-Filter nor IPSEC records have been read.
-Aug 30: INPUT EXCEEDED. Line 2775 in VMAC119 should be:
SMF119SC_TLS_CCERT_SER_LEN &PIB.1.
instead of &PIB.1. This was not in MXG 35.08.
Thanks to Thomas Liu, Australia New Zealand Banking Group, AUSTRALIA
Change 35.172 New ThruputManager fields INCLA1 JXJOU JXSTA1 JXSTA2 are
VMACTPMX supported.
Aug 3, 2017
Thanks to Scott Wiig, USBank, USA.
====== Changes thru 35.171 are in this MXG 35.07 dated Aug 2, 2017=====
Change 35.171 zVM SMT Equivalent Time _MT1 variables in VXBYUSR dataset
VMACVMXA now divided by /4096 to convert value to seconds.
Aug 2, 2017
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.170 MXG spuriously reported MISSING TYPE 70 RECORDS for VM
VMXG70PR LPARs on IFLs. Now both MXGCIN and VMSYSTEM are used to
Aug 2, 2017 remove those unwanted observations.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.169 The incorrectly spelled variable QPSTDTW was kept in both
VMAC115 MQMBUFER and TY115215, but the correctly spelled QPSTDWT
Jul 31, 2017 was only valid in MQMBUFER, and was missing in TY115215.
Now both variables are valid in both datasets.
Thanks to Doris Bentrez, IBM, USA.
Change 35.168 Two errors both would show up when PDB= pointed at more
ANALDB2R than one LIBNAME. First the VGETOBS looking for the
Jul 28, 2017 DB2 datasets would fail looking at multiple libnames.
Once that was fixed ANALDB2R only used the first in the
list of LIBNAMES - now it will use them all.
Change 35.167 BLDSMPDB uses VGETSORT to determine the contents of
BLDSMPDB your LIBNAMES and the sort sequences (or lack) of
Jul 28, 2017 all of the datasets. It inconsistently used differing
libnames to make that determination which could miss
newly added datasets or changed sort orders. It will
now use the BASEPDB (usually PDB) LIBNAME in all cases
so that it will find the most recent examples.
-New option added to RUNWEEK. RUNWEEK=FORCE will force
the running of the weekly processing. Point FORCEDAY
to the last date in the week if running with AUTOALOC.
-If you are running on ASCII with AUTOALOC=YES we do
not recommend using WTD or MTD processing as it can
make ABEND recovery difficult if the WTD or MTD
processing was done prior to the ABEND.
We also do NOT recommend modifying default SORTEDBY
value from NO to YES since a change in sort orders
(as unusual as it might be) could cause problems.
Change 35.166 Support for z/OS 2.3 changes, many new variables, COMPAT.
EXTY9208 -Support for SMF Record Types 127-2047, with ID 0-127 and
EXTY9250 1152-2047 reserved for IBM use, and ID 127-1151 for USER
EXTY9251 SMF record types. The SMF header was extended by using
EXTY9252 never-used ID=126 record type to identify this record has
EXTY9253 the extended header. Note that new SMF exit IEFU86 is
EXTY9254 taken for ALL SMF records, with or without the extended
EXTY9255 header, and existing SMF exits IEFU83/84/85 are called
EXTY9256 ONLY for records with standard header.
EXTY9257 -Dataset TYPE1415 new variables:
EXTY9258 SMF14DEF='ENCRYPTION*FLAG*BYTE'
EXTY9259 SMF14DET='ENCRYPTION*TYPE'
IMAC92 SMF14DKL='DASD*DATA SET*KEY*LABELS'
VMAC1415 Fields exist only if Encryption Subtype 9 exists.
VMAC42 -Dataset TYPE4227 new variables:
VMAC62 SMF42RDSC_OLD='SMF42RDSC*OLD DSCB*DATA*FIELD'
VMAC7072 SMF42RDSC_NEW='SMF42RDSC*NEW DSCB*DATA*FIELD'
VMAC71 SMF42RKEY_OLD='SMF42RKEY*OLD DSCB KEY*DATASET*NAME'
VMAC92 SMF42RKEY_NEW='SMF42RKEY*NEW DSCB KEY*DATASET*NAME'
VMACSMF The _ETY4227 output macro was relocated correctly so it
VMXGINIT is outside the LN2 DO group, causing observations to
VMAC73 now be created that were not previously output.
VMAC74 Tested.
VMAC75 -Dataset TYPE62 new variables:
VMAC76 SMF62DEF='ENCRYPTION*FLAG*BYTE'
VMAC77 SMF62DET='ENCRYPTION*TYPE'
VMAC78 SMF62DKL='DASD*DATA SET*KEY*LABEL'
VMAC79 -Dataset TYPE71 new variables, APAR OA52452 added.
VMACRMFV SMF71RFL='SMF71RFL*FLAGS'
Jul 18, 2017 SMF71NNF='AVG NON-NUC*FRAMES*COMPRISING*STORAGE'
Jul 28, 2017 SMF71LSI='AVG SYS-INIT*DEMOTIONS*LARGE*TO 4K'
SMF71LRI='AVG REQ-INIT*DEMOTIONS*LARGE*TO 4K'
SMF71MHW='HWM 1MB*FRAMES*USED FOR*FIXED 1MB'
SMF71PIS='AVG 4KB*PAGEINS*FROM SCM'
SMF71POS='AVG 4KB*PAGEOUTS*TO SCM'
SMF71PI1='AVG 1MB*PAGEINS*FROM SCM'
SMF71PO1='AVG 1MB*PAGEINS*FROM SCM'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF71DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF71DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
Tested.
-Dataset TYPE72GO new variable:
R723GMLM='MEMORY*LIMIT*SPECIFIED?'
R723GMML='MEMORY*LIMIT*GB of*resgroup'
R723CTETX='TOTAL*TRANSACTION*ELAPSED*TIME'
R723CXETX='TOTAL*TRANSACTION*EXECUTION*TIME'
R723CETSX='SUM*ELAPSED*TIME*SQUARED'
R723CQDTX='TOTAL*QUEUE*DELAY*TIME'
R723CADTX='TIME*BATCH JOBS*INELIGIBLE*TO RUN'
R723CCVTX='TIME*BATCH JOBS*SPENT*IN JCL CVTR'
R723CIQTX='TIME*BATCH JOBS*INELIGIBLE*IN JOBQ'
Tested; 35.06 only kept first two variables.
-Dataset TYPE7204 new variable:
R724ETX='TOTAL*EXECUTION*TIME*GROUP'
R724QTX='TOTAL*QUEUE*TIME*GROUP'
R724OR7A='MEMORY*POOL*SHORTAGE'
Tested.
-Dataset TYPE73 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF73DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF73DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
Tested.
-Dataset TYPE74 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF74DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF74DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
SMF74ATD='I/O DELAYS*PAV*ALIAS*THROTTLING'
Tested.
-Dataset TYPE74CA new variable:
R745XSCS='SUBCHANNEL*SET*ID'
Tested.
-Dataset TYPE748 new variable:
R748CFSC='SUBCHANNEL*SET*ID*PHYS CONFIG'
R748CSCS='SUBCHANNEL*SET*ID OF*FAILING*DEVICE'
Tested/Corrected Change 35.182.
-Dataset TYPE75 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF75DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF75DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
SMF75SCS='SUBCHANNEL*SET*ID'
Tested.
-Dataset TYPE76 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF76DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF76DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
Tested.
-Dataset TYPE77 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF77DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF77DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
Tested.
-Dataset TYPE78 new variables:
ZARCHMDE='SYSTEM*IS IN*Z/ARCH MODE?'
IFAAVAIL='AT LEAST*ONE ZAAP*INSTALLED'
ZIPAVAIL='AT LEAST*ONE ZIIP*INSTALLED'
SMF78DAT1='ENHANCED*DAT*FACILITY 1*AVAILABLE'
SMF78DAT2='ENHANCED*DAT*FACILITY 2*AVAILABLE'
No Observations to test.
-TYPE78CF dataset had zero observations with VMAC78 from
MXG 34.06 - corrected by 34.223 (34.07), 35.021 (35.02)
or 35.166 (in MXG 35.07).
-Dataset TYPE791 update:
R791SRC new MP Swap Reason Memory Pool Shortage
No Observations to test.
-Dataset TYPE796 new variables:
R796SCS='SUBCHANNEL*SET*ID'
No Observations to test.
-Dataset TYPE79B new variables:
R79BSCS='SUBCHANNEL*SET*ID'
No Observations to test.
-TYPE92xxx datasets not tested, no data.
-NEW dataset TYPE9208: ZFS FILE SYSTEM MIGRATED
SMF92GLUGNU='LOCAL*OR*REMOTE*MOUNT?'
SMF92GSN='FILE*SYSTEM*OWNER?'
SMF92GTM='DATETIME*OF*MIGRATION'
SMF92GMO='OFFSET OF*MOUNT*PARM*SECTION'
SMF92GFT='FILE*SYSTEM*TYPE*MNTENTFSTYPE'
SMF92GFM='FILE*SYSTEM*MODE*MNTENTFSMODE'
SMF92GDN='FILE*SYSTEM*DEVICE NUMBER*MNTENTFSDEV'
SMF92GDD='DDNAME*SPECIFIED*ON MOUNT*MNTENTFSDDNAME'
SMF92GTN='FILE*SYSTEM*TYPE NAME*MNTENTFSTNAME'
SMF92GFN='MIGRATION*TARGET*FILE*SYSTEM*NAME'
SMF92GON='MIGRATION*SOURCE*FILE*SYSTEM*NAME'
SMF92GBL='FILE*SYSTEM*BLOCK*SIZE'
SMF92GST='TOTAO*SPACE*IN FILE*SYSTEM'
SMF92GSU='ALLOCATED*SPACE IN*FILE*SYSTEM'
SMF92GFG='FIRST*BINARY*FLAG'
SMF92GF2='SECOND*BINARY*FLAG'
-NEW dataset TYPE9250: ZFS FILE SYSTEM EVENTS
SMF92FSN='FILE*SYSTEM*NAME'
SMF92VOL='VOLSER*FIRST*EXTEND'
SMF92CCHH='CCCCHH*OF FIRST*EXTEND'
SMF92EVENT='FILE*SYSTEM*NAME'
SMF92SIZ='FORMATTED*SIZE OF*FILE*SYSTEM'
SMF92T50=' STKE *FILE*SYSTEM*EVENT'
SMF92CODE='FAILED*OPERATIONS*ERROR*CODE'
SMF92RSN='REASON*CODE'
SMF92OVS='PRIOR*VOLUME*SERIAL'
SMF92OCH='CCCCHH*OF PRIOR*VOLUME*SERIAL'
SMF92LRT='LOGFILE*RECOVERY*TIME'
SMF92LRP='LOG*PAGES*PROCESSED'
SMF92LRR='LOG*RECORDS*PROCESSED'
SMF92LRD='LOG*BLOCKS*MODIFIED'
SMF92LRE='REDO*DATA*RECORDS*PROCESSED'
SMF92LRF='FILL*RECORDS*PROCESSED'
SMF92LRN='NEW BLOCK*SECURITY*RECORDS*PROCESSED'
SMF92SYS='SYSTEM*NAME*REPORTING*EVENT'
-NEW dataset TYPE9251: COUNTS/RESPONSE TIME ZFS CALLS
SMF92CCT='EVENT*DATETIME'
SMF92VCC='CALLS TO*FILE SYS*OWNED LOCALLY*OR R/O'
SMF82VCX='CALLS*REQUIRED*TRANSMIT*FOR LOCAL'
SMF92VCR='CALLS TO*FILE SYS*OWNED*REMOTELY'
SMF92VCRX='CALLS*REQUIRED*TRANSMIT*FOR REMOTE'
SMF92VCT='AVG TIME*PER CALL*LOCALLY*OWNED'
SMF92VCRT='AVG TIME*PER CALL*REMOTELY*OWNED'
SMF92VCN='CALLS TO*FILE SYS*LOCAL OR*REMOTE'
-NEW dataset TYPE9252: STATISTICS FOR ZFS USER FILE CACHE
SMF92UCT =' STCKE DATETIME*WHEN*STATISTICS'
SMF92UCSCH='TIMES*DIRTY DATA**SKED FOR*WRITE TO DISK'
SMF92UCSET='CALLS*TO CHANGE*ATTRIBUTES*OF A FILE'
SMF92UCFSY='CALLS*TO SYNC*ALL DIRTY DATA*SYNC WAIT'
SMF92UCUNM='CALLS*TO PURGE*USER CACHE'
SMF92UCRD ='CALLS*TO READ*FROM FILE*IN USER CACHE'
SMF92UCRDA='ASYNC*READ-AHEADS*SCHEDULED*SEQUENTIALLY'
SMF92UCWR ='CALLS*TO WRITE*TO FILE*IN USER CACHE'
SMF92UCGET='CALLS CACHE*TO OBTAIN ATTRIBUTES'
SMF92UCFL ='CALLS CACHE*TO FLUSH*ALL DATA FOR*FILE SYS'
SMF92UCDEL='WRITES*OF DIRTY DATA*AVOIDED'
SMF92UCRDF='READ CALL*TO FILE CACHE*FOUND*A CACHE MISS'
SMF92UCWRF='WRITE CALL*TO FILE CACHE*FOUND*A CACHE MISS
SMF92UCRIO='READ I/OS*TO DISK*USER FILE CACHE'
SMF92UCWRS='NORMAL*WRITE I/OS*SKED*BY FILE CACHE'
SMF92UCWRE='WRITE I/OS*SKED*ERROR FOUND'
SMF92UCWRR='WRITE I/OS*SKED*RECLAIM-STEAL'
SMF92UCRWR='TASK WAITS*FOR SKED READ*FROM DISK'
SMF92UCWW ='TASK WAITS*FOR WRITE*FILE*PENDING I/O'
SMF92UCWWF='TASK WAITS*FOR PENDING I/O*FOR FSYNC CALLS'
SMF92UCWWE='TASK WAITS*FOR I/O*ERROR*PROCESSING'
SMF92UCWWR='TASK WAITS*FOR I/O*RECLAIM-STEAL*PROCESSING
SMF92UCRST='TIMES*RECLAIM-STEAL*PROCESSING*WAS INVOKED'
SMF92UCCS ='CACHES*SPACES*LRU QUEUES* AND PAGEPOOLS'
SMF92UCPCS='PAGES*IN EACH*CACHE SPACE'
SMF92UCSS ='SIZE OF*INDIVIDUAL*FILE SEGMENT'
SMF92UCPGS='SIZE OF*A PAGE*IN THE USER*FILE CACHE'
SMF92UCPGT='TOTAL PAGES*IN THE USER*FILE CACHE'
SMF92UCPGF='FREE PAGES*IN THE USER*FILE CACHE'
SMF92UCSGC='ALLOCATED*SEGMENT*STRUCTURES*IN FILE CACHE'
SMF92UCDSL='LENGTH*PER-CACHE*SPACE RECORD'
-NEW dataset TYPE9252X:CACHE SPACE NAME SEGMENT
SMF92DSNAM='NAME OF*THE CACHE SPACE'
SMF92DSAS ='SEGMENTS*ALLOCATED'
SMF92DSFR ='FREE PAGES*IN CACHE LIST'
-NEW dataset TYPE9253: STATISTICS FOR ZFS METADATA CACHE
SMF92MCT ='DATETIME*WHEN*STATISTICS*WRITTEN'
SMF92MCB ='BUFFERS IN THE METADATA CACHE.'
SMF92MCLK='SEARCH CALLS*FOR BUFFER*IN METADATA CACHE'
SMF92MCHT='SEARCH CALLS*CACHE HITS'
SMF92MCWP='CALLS TO*UPDATE*METADATA CACHE*BUFFER.'
SMF92MCPW='PARTIAL*BUFFERS*WRITTEN'
SMF92MCBS='BYTES IN*METADATA*CACHE BUFFER.'
-NEW dataset TYPE9254: STATISTICS FOR ZFS LOCKING AND SLEE
-NEW dataset TYPE9255: GENERAL ZFS DISK IO STATISTICS
-NEW dataset TYPE9256: TOKEN MANAGER
-NEW dataset TYPE9257: ZFS USE OF MEMORY
-NEW dataset TYPE9258: TRANSMIT/RECEIVES BETWEEN ZFS MEMBE
-NEW dataset TYPE9259: PER-FILE SYSTEM USAGE
-RMF III UPDATES for z/OS 2.3:
-ASMRMFV Recent versions will execute without error to
create RMFBSAM output, but these new variables are output
with this VMACRMFV update:
-Dataset ZRBASI new variable:
ASISTAFL ASI2GMEMOBJ ASI2GPGSBKD
-Dataset ZRBDVT new variables:
DVTSSID ='SUBCHANNEL*SET'
DVTDEVN2='DEVICE*NUMBER*DVTDEVNR'/
DVTENIDX4='INDEX OF*THIS*DVTG3*ENTRY'/
DVTPREVI4='INDEX OF*PREVIOUS*DVTG3*ENTRY'
-Dataset ZRBGEI new variables:
GEIGRMO ='FIXED*MEMOBJ*BACKED IN*2GB FRAMES'
GEIGRPR ='2GB FRAMES*FIXED IN*CSTORE'
GEIGFUSE='2GB FRAMES*USED IN*FIXED*MEMOBJ'
GEIGSIZ ='2GB FRAMES*CAN BE*USED 2GB MEMOBJ'
-Dataset ZRBUWD new variables:
UWDDEVNR4=DEVICE*TABLE*DVTG3*INDEX'
Change 35.165 Variables added to VXMTRMEM dataset:
VMACVMXA RSAPIN0B ='PINNED*PAGES*CLASS 0*BELOW 2G'
Jul 28, 2017 RSAPIN0A ='PINNED*PAGES*CLASS 0*ABOVE 2G'
Aug 2, 2017 RSAPIN1B ='PINNED*PAGES*CLASS 1*BELOW 2G'
RSAPIN1A ='PINNED*PAGES*CLASS 1*ABOVE 2G'
RSAPINWP ='PINNED*PAGE COUNT*CAUSES WARNING'
RSAPINFP ='TOTAL*PINNED*PAGE*COUNT'
RSAIOUSD ='BYTES*IOAT*SUBPOOL'
RSAIOSIZE='SIZE (MB)*IOT*SUBPOOL'
RSAIOWRNP='WARNING*PCT*IOAT*USED'
SYSHPIOM ='MAX*CONCURNT*PG*RQSTS'
SYSHPFLG ='HYPERPAV*PAGING*FLAGS'
RSAAGEFL ='GLOBAL*AGING*LIST*FLAGS'
Variables added to VXSYTRSG dataset:
RSAPIN0B ='SYS TOT*PINNED*PAGES*CL 0 LT 2G'
RSAPIN0A ='SYS TOT*PINNED*PAGES*CL 0 GT 2G'
RSAPIN1B ='SYS TOT*PINNED*PAGES*CL 1 LT 2G'
RSAPIN1A ='SYS TOT*PINNED*PAGES*CL 1 GT 2G'
RSAPINWP ='PCT PINNED*CAUSED*WARNING'
RSAPINFP ='PCT PINNED*CAUSED*FAILURE'
RSAPINWC ='TIMES*WARNING*PCT*EXCEEDED'
RSAPINFC ='TIMES*FAILURE*PCT*EXCEEDED'
RSAIOUSD ='BYTES*USED*IOAT*SUBPOOL'
RSAIOWRNP='PCT*IOAT*SUBPOOL*VS SIZE'
RSAIOWRNC='TIMES*IOAT*SUBPOOL*WARNING'
RSAIOFALS='TIMES*IOAT*SUBPOOL*NOT AVAIL'
RSAIOFAIL='TIME*NOT AVAIL*IOAT AND*AVAILLIST'
Variables corrected in VXBYUSR dataset, all
were missing the divide by 4096.
Thanks to Patricia Hansen, ADP, USA.
Thanks to Mike Chaves, ADP, USA.
Change 35.164 Variables added to XAMSYS dataset:
VMACXAM RSACKMB2G='CP FRAMES*LT 2G*FOR DUMP'
Jul 26, 2017 RSACKMA2G='CP FRAMES*GT 2G*FOR DUMP'
RSAPIN0B ='PINNED*PAGES*CLASS 0*BELOW 2G'
RSAPIN0A ='PINNED*PAGES*CLASS 0*ABOVE 2G'
RSAPIN1B ='PINNED*PAGES*CLASS 1*BELOW 2G'
RSAPIN1A ='PINNED*PAGES*CLASS 1*ABOVE 2G'
RSAPINWP ='PINNED*PAGE COUNT*CAUSES WARNING'
RSAPINFP ='TOTAL*PINNED*PAGE*COUNT'
RSAIOUSD ='BYTES*IOAT*SUBPOOL'
RSAIOSIZE='SIZE (MB)*IOT*SUBPOOL'
RSAIOWRNP='WARNING*PCT*IOAT*USED'
SYSHPIOM ='MAX*CONCURNT*PG*RQSTS'
SYSHPFLG ='HYPERPAV*PAGING*FLAGS'
RSAAGEFL ='GLOBAL*AGING*LIST*FLAGS'
Thanks to Patricia Hansen, ADP, USA.
Thanks to Mike Chaves, ADP, USA.
Change 35.163 Support for Dell EMC Mainframe Enablers for z/OS V8.2 for
EXPAVO01 their z Systems PAV Optimizer, PAVO product's user SMF
EXPAVE01 record creates two new datasets:
IMACPAVO DDDDDD DATASET DESCRIPTION
TYPEPAVO TYPAVO TYPEPAVO PAVO OPTIMIZER DATA
TYPSPAVO TYPAVE TYPEPAVE PAVO EVENT
VMACPAVO
VMXGINIT This support is incomplete and in active development;
Aug 25, 2017 please contact SUPPORT@MXG.COM for current status.
Change 35.162 Support for Dell EMC Mainframe Enablers for z/OS V8.2 for
EXZDPVDG their z Systems Data Protector, zDP product's user SMF
IMACZDP record creates new TYPEZDP dataset:
TYPEZDP DDDDDD DATASET DESCRIPTION
TYPSZDP ZDPVDG TYPEZDP ZDP DATA
VMACZDP
VMXGINIT
Jul 24, 2017
Change 35.161 Support for BMC Mainview/CICS Version 7.1 (CICS/TS 5.4)
FORMATS adds many new fields and updated formats.
VMACMVCI
Jul 23, 2017
Change 35.160 Support for AXWAY Version 3.1.3; the documentation does
VMACAXWY not match the actual data records and some fields are not
Jul 21, 2017 input, pending feedback from the vendor.
Thanks to Michael Reines, Decadis, GERMANY.
Change 35.159 VGETSORT now adds formats to the output for the sorted by
VGETSORT variables for each dataset. For each found member, there
Jul 28, 2017 will be a MACRO variable FMTx corresponding to the SRTx
variable that will contain the formats of the variables
in the SORTEDBY list. Where there is no specified format
CHAR is substituted.
Change 35.158 Support for Mainview/CICS Optional SMF 110 BMCMVCIC field
IMACICWU in dataset CICSTRAN.
UTILEXCL
VMAC110
Jul 18, 2017
Change 35.157 MXG 35.01-35.06. Variable DB2TCBTM was removed from the
VMXGUOW CPUUOWTM value in PDB.ASUMUOW back in Change 32.014, but
Jul 18, 2017 was put back in the equation in 35.01, in error, so it
is again removed from the equation, per text of 32.104.
Thanks to Rick Southby, Insurance Australia Group, AUSTRALIA
Change 35.156 ERROR: VARIABLE DTOKEN/IMSRECCH NOT FOUND because they
VMACIMS were in the BY list for the IMS06 dataset sort but were
Jul 16, 2017 not kept; now they are kept in IMS06.
Thanks to Randy Hewitt, DXC, USA.
Change 35.155 TPX STOPOVER because the change in length of IP Port from
VMACTPX 4 to 5 digits was not fully protected. Variable
Jul 16, 2017 TPXIPPRT in datasets TPXTRMON/TPXTRMOF and variable
TPXIPADR in dataset TPXAPLOF values are now correct.
CA's record length change was in Feb, 2016, RO85818.
Thanks to Paul Naddeo, FISERV, USA.
Change 35.154 -MXG 35.06 only, STOPOVER abend during TYPERMFV execution
ASMRMFV processing RMF III with option UWD (Use/Wait table) after
Jul 11, 2017 Change 35.148. Message RMFV006I may show incorrect RMF
Jul 21, 2017 Monitor III table selections, but processing of the
actual selected tables still occurred. Message RMFV006I
could show NOZEROCPU when the default ZEROCPU setting was
in effect for the ASI table. Only ASMRMFV was changed.
-With this change if the NOSVP table option is in effect
then the RCD option will be forced to NORCD.
-Invalid RMFV012I and/or RMFV013I Sample RANGE and
SELECTED messages when RMF III data originates from a
time zone with time stamps later than the current TOD in
the time zone where ASMRMFV is executing.
Thanks to Betty Wong, Bank of America, USA
Thanks to Roger Lowe, Northern Territory Government, AUSTRALIA.
Change 35.153 The IBM RMF CRYPTO report shows a TOTAL EXEC TIME with a
VMAC7072 value of 0.120 but that is actually the AVERAGE EXEC TIME
Jul 7, 2017 per call, and the unstated units are milliseconds, so the
actual average value was 120 microseconds. In TYPE7002
dataset, the actual average value was 120 microseconds.
MXG Variable CRYCTE is the calculated average value,
0.000120 seconds, which is 120 microseconds. When printed
with TIMW13.3 format, only three decimals were displayed
(0:00:00.000), so crypto duration variables are now
formatted TIME14.6 to display as 0:00:00.000120 to show
microseconds.
Thanks to Martha A. Knapik, Progressive, USA.
Thanks to Douglas Wells, Progressive, USA.
Change 35.152 Support for BETA 97 Subtype 22 record for both version
EXTYB97Q 430 and 610, although only 430 records have been read.
EXTYB97R New dataset BETA9722REL is created with the relocate
FORMATS segments for Subtype 22 records.
VMACBE97
VMXGINIT
Jul 9, 2017
====== Changes thru 35.151 are in this MXG 35.06 dated Jun 30, 2017=====
Change 35.151 BMC CMF TYPE74 subtype 8 records requires BMC PTF BQM1335
TYPE74 after IBM SuperPav support is installed, even if you are
Jun 28, 2017 NOT using SuperPAVs. After IBMSuperPAV PTFs, the ESS Rank
data are incorrect. No code was changed in MXG.
Thanks to Jerry Ellis, Liberty Mutual, USA.
Change 35.150 Option %LET CECONLY=YES; creates PDB.ASUMCEC keeping only
VMXG70PR the 68 CEC-Level variables, dropping 2794 LPAR-specific
Jun 28, 2017 variables (generally useless, with unique variable names
for 60 LPARs) and creates PDB.ASUMCELP (no changes, but
with one observation per LPAR, it is THE dataset to use
to report LPAR data, with ONE set of variable names.)
NOTE: ALL LPARS in the CEC are summed into ASUMCEC.
Only the first 60 have sets of kept unique names.
The ASUM70PR/ASUM70LP and ASUM70GC/ASUM70GL datasets are
not created when %LET CECONLY=YES; is placed in your
//SYSIN prior to the INCLUDE of ASUM70PR.
Change 35.149 New BUILDJCL=YES option creates JCL for two step job with
UTILBLDP PGM=IFASMFDP control statements to select ONLY the SMF
Jun 30, 2017 records needed for your UTILBLDP selections.
Sep 30, 2017 On Sep 30, UTILBLDX from this change became UTILBLDP as
had been planned in the original text of this change,
and UTILBLDX was removed from MXG 35.09.
-comparison of CPU savings:
Using IFASMFDP to select SMF records can save CPU time,
especially for Ad Hoc jobs that select a relatively small
number of SMF records. Tests with a 15 GigaByte SMF file
with 25 million records was used, but only 1.4 Million of
those records (1 GB) were actually decoded and output.
But they had to be read and that costs CPU time:
MM:SS
READ ALL RECORDS 14:56
USE MXG MACFILE EXIT TO SKIP UNWANTED 12:43
IFASMFDP READ ALL SELECT/WANTED 0:10
READ SELECTED/WANTED 2:25
-Using MACFILE, _SMF decodes the full header and then
deletes unwanted. Decoding DATETIME variables is the
most expensive INFORMAT so I inserted an exit to skip
the unwanted immediately after the ID was input and
prior to any DATETIME field, but the savings were much
less than hoped for and much less than using IFASMFDP.
MM:SS
READ ALL with _SMF THEN DELETE UNWANTED 6:29
READ ALL, DELETE AFTER ID READ 4:45
-BUILDJCL for extreme cases provides extreme results:
Selecting 194 SMF 115 records in a file of 300 million
records (1 MB from 137 GB) dropped the CPU time from
25 min to only 46 seconds, elapsed from 28 to 13 min.
Change 35.148 RMF III CPUTM in datasets ZRBRCDS and ZRBRCDR is wrong if
ASMRMFV ASMRMFV selected RCD records but didn't select SVP table.
ADOCRMFV Creation of CPUTCBTM/CPUSRBTM from Service Units requires
VMACRMFV the SVPCPU and SVPSRB coefficients. ASMRMFV now selects
Jun 27, 2017 SVP records when RCD is selected. Additionally, variable
CPUTM is set missing if there are no SVP data.
SO YOU MUST HAVE BOTH RCD AND SVP TABLES IN ASMRMFV.
-However, if the SVP table is selected, then the RCD table
is NOT forced. The SVP table is now also moved to the
BASIC option table selection group from the MOST option
table selection group because the RCD was always part of
the BASIC option table group.
-Minor performance improvement to UWD table processing
logic.
-Several documentation Sections are updated to support the
above changes:
Section 0 "Contents"
Section 4 "RMF III Table Selection Parameters"
Section 13 "Filtered Records"
Section 26 "ASMRMFV and MXG PDB Data
Thanks to MP Welch, Bank of America, USA.
Change 35.147 Support for new segments create two new datasets:
EXVSIDSK DDDDDD DATASET DESCRIPTION
EXXAMPRC VSIDSK XMVSIDSK VSIDISK Data
IMACXAM XAMPRC XAMSYPRC LIMPOOL Data
VMACXAM
VMXGINIT
Jun 28, 2017
Thanks to Patricia Hansen, ADP, USA.
Thanks to Mike Chaves, ADP, USA.
Change 35.146 -TYPE749 vars R749FPGBYTR and R749FPGBYTS were incorrectly
VMAC74 multiplied by 256; the two input variables had already
Jun 23, 2017 been converted to bytes.
-TYPE749 variables decoded from SMF74DO offset were wrong;
the +17 added to SMF74DO should have been +16.
R749DMAR R749DMAW R749DFMT R749DBYR R749DBYT
R749DFMT R749DPKR R749DPKT R749DWUP R749DWUM
R749DFMT R749DBYX R749DFMT
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.145 Some zVM VXSYTPRP new SMT variables were incorrectly
FORMATS tested for error conditions with GT 8000000Nx values
VMACVMXA that no longer existed after their INPUT, causing large
Jun 25, 2017 values in occasional observations. They are now INPUT
with IB4 or IB4.3 INFORMATS so the first-bit-value causes
a negative value, and the error tests are now LT 0 to
detect and delete them. The MGVXAER format was revised
decode the negative values to print the error messages on
the SAS log (for the first 3 of each error type).
-Some INTERVAL variables were incorrectly deaccumulated
that also caused occasional large values.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.144 These error messages, introduced in Change 35.050:
ASUM70PR MXGERROR:DATASETS ASUMCEC ASUMCELP ARE NOT VALID. YOU ARE
VMXG70PR MXGERROR:MISSING TYPE 70 RECORDS FOR ONE OR MORE SYSTEMS.
Jun 23, 2017 MXGERROR:SMF70LAC VALUES FOR THOSE SYSTEMS/CECS ARE INVALID
MXGERROR:SEE CHANGE 35.144 TO CORRECT.
impact the important ASUMCEC and ASUMCELP CEC-level data.
Datasets ASUM70PR and ASUM70LP are impacted, but they
are SYSTEM-Level and are NOT recommended for analysis.
The messages will result if you did NOT process type 70
records from ALL OF YOUR z/OS SYSTEMS in the CEC; for
that case, you need to read all 70 SMF records.
They can also result if your z/OS configuration uses z/OS
SYSTEM names that are set in your SYS1.PARMLIB's IEASYSxx
and are NOT the same as the SMF SYSTEM ID: for example,
if you set SYSTEM names in IEASYSxx to the LPARNAME.
-This change creates a new INCODE70 argument that can be
set externally by macro variable &INCODE70FORPR, so you
can change those SYSTEM name to LPARNAME. Note, this is
only done internally in ASUM70PR code; there is no SYSTEM
variable in ASUMCEC/ASUMCELP. To use INCODE70FORPR, you
first need run this program and look at the output of
PROC FREQ DATA=PDB.TYPE70PR;
TABLES LPARNAME*SMF70STN/NOROW NOCOL NOCUM NOPERCENT;
to verify that LPARNAME equals SMF70STN for ALL systems.
IF THAT IS TRUE, then you need to use either INCODE70= in
your tailored ASUM70PR member (in your USERID.SOURCLIB),
or set the value prior to your ASUM70PR include, using:
%LET INCODE70FOR70PR=%QUOTE(
IF SYSTEM NE LPARNAME THEN SYSTEM=LPARNAME;
);
-Newly added, once you have verified the preceding is TRUE
you can let MXG do the heavy lifting and specify:
%LET INCODE70FOR70PR=ENABLEAUTO;
and MXG will generate the needed code to correct.
Don't hesitate to contact support@mxg.com for help.
See Change 36.027 for an example when LPARNAME is not
equal to SMF70STN.
Change 35.143 -The UTIILBLDP option SUPPRESS is enhanced to recognize
UTILBLDP CICS to be the same as 110.
Jun 21, 2017 -If you specified SORTOUT=NEVER (not really recommended,
intended only for internal testing) it didn't work right:
only the datasets where sort IS required were NOT sorted,
(i.e. DIF() required for deaccumulate members) and all
other datasets WERE sorted. Now, NEVER sorts NOTHING,
and SORTOUT=NO option now sorts ONLY those members that
must be sorted for DIF().
Change 35.142 Format MG080QU has been updated with new z/OS 2.2 values
FORMATS for decoding variable RACFQUAL='EVENT*CODE*QUALIFIER'
Jun 16, 2017
Thanks to Lindsay Oxenham, Australia Defence Department, AUSTRALIA.
Change 35.141 John Burg's 2017 formula for RNI for the z13 was changed
ASUM113 from the 2.6 factor introduced in Change 33.033 in 2015
VMAC113 to the new value of 2.3. John's paper can be found at:
VMACVMXA http://www-03.ibm.com/support/
Jun 15, 2017 /techdocs/atsmastr.nsf/WebIndex/TC000066
Thanks to David Cogar, WellsFargo, USA.
Change 35.140 Support for short sub-sub-type ZPRTR1PL=188.
VMACZPRO
Jun 15, 2017
Change 35.139 -Support for restructured BETA93 Subtype 25 (VMACBETA)
VMACBETA and for restructured BETA97 Subtype 25 (VMACBE97) which
VMACBE97 adds new BE97DTKN DTOKEN variable.
Jun 21, 2017 -Variable BETALEXT has length $16 in VMACBETA subtypes
Jun 26, 2017 21 and 25, but the first INPUT for subtype 0 and other
earlier subtype are length $12, so the kept length was
only 12. Now, LENGTH BETALEXT $16 is set so the kept
variable length is the maximum 16 bytes.
Thanks to Thomas Wigger, Finanz Informatik, GERMANY.
Thanks to Dieter Haak, Finanz Informatik, GERMANY.
Thanks to Robert Gilbert, BNP Paribas Fortis, BELGIUM.
Change 35.138 TPX corrections to TPXIPPRT and TPXTRMON dataset.
VMACTPX The '07'x records are only LENGTH=101, so the TPXAPLON
Jun 9, 2017 data set is still missing TPXIPADR and TPXIPPRT fields.
Thanks to Scott Wiig, USBank, USA.
Change 35.137 Datasets TYPE42DS, TYPE42SR & TYPE42VT with APAR OA44319
VMAC42 have increased accuracy for these I/O duration variables:
Jun 6, 2017 RESPTIME AVGCONTM AVGPNDTM AVGDISTM AVGCUQMS S42CONTM and
AVGIOQMS.
Thanks to Ron Hawkins, Hitachi, USA.
Change 35.136 Correction for NETVIEW ID=38 record with S38CCALR length
VMAC38 less than expected length of 8 bytes. Record is valid,
Jun 14, 2017 MXG expected fixed length of 8 characters.
Thanks to Stuart Wildey, Morgan Stanley, ENGLAND.
Change 35.135 -Enhancements for 4 numeric data filters for RMF Monitor
ADOCRMFV III ASI (Address Space Information) table.
ASMRMFV -A pair of data filters are added to filter ASI entries
VMACRMFV based on the ASICPUTA (Total TCB+SRB time) field for each
Jun 6, 2017 MINTIME interval. These filters are effective only if
the ASI table is selected.
New Parameter Alias(es)
------------- ------------------------------------------
ZEROCPU ZCPU Default
NOZEROCPU NOZCPU, NZCPU
-ZEROCPU is the default and results in all ASI entries
being output to the RMFBSAM file and thus all becoming
observations in the MXG PDB data set ZRBASI (depending
on other ASI filters that may be in use).
The default provides a compatible behavior with prior
ASMRMFV versions.
-NOZEROCPU results in all ASI entries with ASICPUTA=0
being filtered (depending on other ASI filters that may
be in use) and thus these do NOT become observations in
the MXG PDB data set ZRBASI. The data volume to generate
the PDB can be significantly reduced.
In a test group of 21 RMF Monitor III VSAM data sets
78.3% of all ASI entries had ASICPUTA=0. Actual results
may vary.
-While the NOZEROCPU setting might seem to be ALWAYS
desirable there are other considerations:
1) Filtering zero CPU time ASI entries will result in
time series gaps for some Address Spaces in some MINTIME
intervals in charts, plots, or reports.
If such gaps are not acceptable, use the default ZEROCPU
parameter instead. However, there will be a higher
number of PDB ZRBASI data set observations as in prior
ASMRMFV versions.
2) Zero CPU time conditions are NOT always due to pure
idleness for an Address Space.
RMF Monitor III detected delays such as Processor,
Enqueue, Operator Reply, and Operator Mount separately or
in combination can prevent accumulation of any CPU time
for an Address Space in a single MINTIME interval.
The NOZEROCPU parameter used alone with the NOKEEPDELAYS
default will filter out these entries so that further
investigation of a zero CPU time Address Space in a
MINTIME interval based on delays is impossible.
-With the above use of NOZEROCPU in mind an additional
pair of data filters are added to further filter ASI
entries based on the ASISWAIN (Number of Single State
Samples Delayed by ANY Resource) field for each MINTIME
interval.
This filter pair is effective only if the NOZEROCPU
parameter is in effect.
New Parameter Alias(es)
------------- ------------------------------------------
KEEPDELAYS KDELAYS, KDLYS, KEEPD
NOKEEPDELAYS NOKDELAYS, NOKDLYS, NOKEEPD Default
-With NOZEROCPU and NOKEEPDELAYS in effect all ASI entries
with ASICPUTA=0 are filtered regardless if any delays
occurred or not during a MINTIME interval (if not already
filtered by other ASI filters).
-With NOZEROCPU and KEEPDELAYS in effect only ASI entries
with both ASICPUTA=0 AND ASISWAIN=0 (zero delays) in a
MINTIME interval are filtered (if not already filtered
by other ASI filters).
In a test group of 21 RMF Monitor III VSAM data sets with
NOZEROCPU and KEEPDELAYS 75.8% of all ASI entries had
ASICPUTA=0 and ASISWAIN=0 and so were filtered.
This was only 2.5% less data filtered than with NOZEROCPU
used alone. Once again actual results may vary.
-NOZEROCPU and KEEPDELAYS are likely the best compromise
settings between ASI data reduction and retention of
delay information. Neither are defaults.
However, for maximum data reduction use NOZEROCPU alone
if subsequent delay analysis is not required.
-If ZEROCPU/NOZEROCPU is specified multiple times the last
occurrence takes effect.
-If KEEPDELAYS/NOKEEPDELAYS is specified multiple times
the last occurrence takes effect, but both are ignored
if ZEROCPU is in effect.
-The following chart shows ASI entries output to the
RMFBSAM file and thus also to the subsequent observations
in MXG PDB ZRBASI data set based on the settings of
ZEROCPU/NOZEROCPU, KEEPDELAYS/NOKEEPDELAYS:
---------------------------------------------------------
| NOKEEPDELAYS | KEEPDELAYS
| (Default) |
---------------------------------------------------------
ZEROCPU |All ASI entries output |All ASI entries output
(Default)| |
---------------------------------------------------------
NOZEROCPU|Only ASI entries output|Only ASI entries output
|with ASICPUTA NE 0 |with ASICPUTA NE 0
| |OR ASISWAIN NE 0
---------------------------------------------------------
-ASIAND/ASIOR does NOT apply to ZEROCPU/NOZEROCPU and
KEEPDELAYS/NOKEEPDELAYS filters. These are evaluated
independently of other ASI filters.
-The order of ASI filter application is:
1) ASISUBSYS= <----
2) ASIWORKLOAD= |
3) ASIRESGROUP= |
4) ASISRVCLASS= |--< ASIAND/ASIOR applies only
5) ASIRPTCLASS= | to these filters 1) to 8)
6) ASIJOBCLASS= |
7) ASIJOBNAME= |
8) ASIJESID= <----
9) ZEROCPU/NOZEROCPU
10) KEEPDELAYS/NOKEEPDELAYS
-The MXG00 record version is raised to x'09' from x'08'.
New fields added to the MXG00 record include:
ZEROCPU/NOZEROCPU and KEEPDELAYS/NOKEEPDELAYS settings
-Update message RMFV006I to show new output filters
ZEROCPU/NOZEROCPU/KEEPDELAYS/NOKEEPDELAYS.
-Several documentation Sections are updated to support
the above changes:
Section 0 "Contents"
Section 2 "Terminology"
Section 4 "RMF III Table Selection Parameters"
Section 5 "Input Data Selection Parameters"
Section 6 "Report Control Parameters"
Section 7 "Output Data Control Parameters"
Section 12 "Messages"
Section 13 "Filtered Records"
Section 31 "Summary"
Change 35.134 Variables T103DBYT and T103DREQ are accumulated fields
VMAC103 that are now correctly deaccumulated in TYPE103D dataset.
Jun 5, 2017 Variables T103DDNS and T103DKEE are always zero in test
data, so it is unknown if they also are accumulated.
Thanks to Joe Faska, DTCC, USA.
Change 35.133 Test program COMPALL updated for new SMF products. This
COMPALL utility compiles all of the SMF processing programs to
Jun 5, 2017 ensure no CHAR/NUM conflicts in temporary variables.
Can not be run on z/OS because it requires 3292MB which
is more than the largest z/OS Private Area available.
Change 35.132 Support for zVM 6.4 APAR VM66026 adds new variables;
VMACVMXA -Variable CUIDSSID='SUBSYSTEM*ID*SSID' is added to dataset
Jun 3, 2017 VXMTRDEV, VXIODVON, and VXIODDEF.
-Variables added to VXIODVON
PREFPATH RDEVHPPL CUIDSSID EQIDUID EQIEQID DEVCHAR
EDEVATTR
-Variables added to VXIODDEV
RDEVNOAL RDEVYSAL RDEVIOQT RDEVIOQS CUIFCXPE RDEVWRAL
RDEVRDAL RDEVWXAL RDEVEXAL
Change 35.131 zVM variable CALENTMT was incorrectly divided by 16, and
VMACVMXA new variable CALSHARE='Hiperdispatch*Processor*SHARE is
Jun 1, 2017 now created as CALSHARE=CALENTMT/65536;
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.130 Changes in VMXGSUM invocation in little used and mostly
ASUM* obsolete members so that WPS can handle QA stream:
MNTH* ASUMHPAI ASUMHPCS ASUMHPSU ASUMHPUX ASUMMWUX
TRND* MNTH70 MNTH70PR MNTH71 MNTH72 MNTH72GO MNTHCICS MNTHJOBS
May 31, 2017 TRND70 TRND70SH TRND71 TRND72 TRND72GO
Change 35.129 Support for 7th, 8th, and 9th CICS User field.
UTILEXCL
IMACIC7D
IMACIC8D
IMACIC9D
IMACIC7U
IMACIC8U
IMACIC9U
May 31, 2017
Change 35.128 Documentation Note. ZFS and ODS users may need to change
IMACINIT the MXG default CAPSOUT option to NOCAPSOUT since those
May 26, 2017 system need to support both cases. I don't think it is
safe for me to change the option as it could impact the
existing users on z/OS where it was originally needed.
But you can add OPTIONS NOCAPSOUT: in the IMACINIT
member of your tailoring library if you determine it can
be changed with no impact.
Change 35.127 Dataset TYPE30_6 could have negative values for Early
VMAC30 Address Spaces (ASIDs that start prior to JES init that
May 26, 2017 have missing READTIME and JESNR) because of multiple
of the same JOB name, but adding variable ASID to the
BY list in MACRO _BTY30U6 corrects these errors.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.126 Variable SMF30SLM is decoded into these new variables in
BUILD005 TYPE30_4 and PDB.STEPS in BUILDPDB and BUILDPD3:
BUIL3005 SMF30SLMRB='REGIONBELOW*NONEXTENDED*REGION?'
VMAC30 SMF30SLMRA='REGIONABOVE*EXTENDED*REGION?'
May 26, 2017 SMF30SLMSB='SYSRESVBELOW*NONEXTENDED*REGION?'
SMF30SLMSA='SYSRESVABOVE*EXTENDED*REGION?'
SMF30SLMML='MEMLIMIT*ACTED ON*MEMLIMIT?'
SMF30SLMBY='IEFUSI*BYPASSED*ALL*SMFLIM?'
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.125 See Change 35.166.
Change 35.124 Running WPS with more than 20 libnames caused WPS to fail
PDBAUDIT so now with WPS if there are more than 20 LIBNAMES after
May 22, 2017 removing the LIBNAMES not related to PDBAUDIT, MXG shuts
down with a message that only the first 20 were used.
Change 35.123 Support for z/OS 2.2 updates to TYPE991 dataset adds many
VMAC99 new variables.
May 22, 2017
Thanks to David Cogar, WellsFargo, USA.
Change 35.122 Two new parameters added:
ANALCAPD COMPANY= lets you override MXG in title statements
May 22, 2017 OUTDATA= lets you preserve the dataset with actuals and
rolling 4 hour MSU values for further analysis.
-GRAPHICS code is enabled for WPS at 3.3 or higher.
====== Changes thru 35.121 are in this MXG 35.05 dated May 15, 2017=====
Change 35.121 ERROR: MACRO KEYWORD DO APPEARS AS TEXT because the quote
ANALAVAI after "DO'" and several other syntax errors corrected.
May 13, 2017
Thanks to Hai Huynh, Freddie Mac, USA.
Change 35.120 WPS only, MXG 35.04, Change 35.085. A variable with no
VMXGPRNT label generated unintended text with multiple quotes
May 16, 2017 Varname1='Label*(varname)''(next vrname)'
which is valid text for a SAS label, defined as the text
after an equal sign up to the text before the next token
that is followed by an equal sign, but this syntax was
was not accepted by WPS as a label, causing an ERROR.
The circumvention is to create a LABEL='NOLABEL' for
variables that do not have a label.
-VMXGPRNT is used in ANAL113, ANAL116, VMXGFIND, VMXGPRAL
VMXGPRA1, VMXGPRNT, VMXGSRCH, and JCLPDB members.
Change 35.119 READDB2 had a hard coded limit of 450 for IFCID, and 499
READDB2 had been added in TYPE102s. Now limit is 999.
May 11, 2017
Thanks to Lynn Hong, UCLA, USA.
Change 35.118 Notes on the use of VIEWs in DATA steps that create more
Document than one DATASET.
May 11, 2017 -Only one DATASET can be a view in a DATA step (and the
BUILDPDB program already has one).
-Any of the datasets can be the view, but that view MUST
be the first dataset referenced (read/sorted), or none
of the other datasets will exist.
-Views can dramatically reduce elapsed and CPU times and
I/O counts and durations, for instance for a DATA step
followed by a SORT, where the VIEW eliminates the write
and read of the dataset that is created without a VIEW.
The VIEW doesn't have any impact on the resources used
by the SORT.
-This example started as TYPE120 with the lower case
lines added. WORK needs to be cleared in case there was
a dataset of the same name, whether it was a view or a
dataset. The /view=typ1209r enables the view and names
the one dataset, and the _st1209r "data set sort macro"
is invoked first, and then made blank so the _S120
"product sort macro" can sort the other datasets:
proc datasets ddname=work mt=all kill;
%INCLUDE SOURCLIB(VMACSMF,VMAC120,IMACKEEP);
DATA
_VAR120 /view=typ1209r
_SMF
_CDE120
run;
_st1209r
run;
macro _st1209R %
_S120;
RUN;
The DATA/SORT took 6 hours, the VIEW/SORT took 2.
Thanks to Joe Faska, DTCC, USA.
Thanks to Michael Oujesky, DTCC, USA.
Change 35.117 -VMXGFIND did not correctly build the output dataset names
VMXGFIND when multiple input PDBs were to be read; while all were
May 11, 2017 read, only one was output.
Thanks to David A. Sadler, Optum, USA.
Change 35.116 35.04 only. The TYPSMVJE test was in TESSUSR1 but should
JCLTEST9 have been in TESSOTHR member, so TESSUSR1 step failed
May 16, 2017 because //MVJEIN DD was not found in that step's JCL.
Add //MVJEIN DD DUMMY to the TESSUSR1 step.
TYPSQACS replaced TESSQACS in //TESTQAPM step.
Thanks to Tony Ferullo, MIB, Inc., USA.
Thanks to Rod Feak, MIB, Inc., USA.
Change 35.115 Reserved Change Number.
Change 35.114 New variables added to TYPE749 PCIE data found in SMF
VMAC74 manual refresh:
May 10, 2017 R749FLAG='VALIDITY*FLAG'
R749NET1='1ST*PORT*PNET ID'
R749NET2='2ND*PORT*PNET ID'
R749DBYX='BYTES*TRANSMITTED*BY PCIE*FUNCTION'
Change 35.113 MXG 35.04 only, TYPE70 SHARE weights wrong, although the
VMAC7072 PDB.ASUMCELP values were correct and recommended for the
May 10, 2017 analysis of LPAR weights.
Thanks to Andrew Petersen, CSC, AUSTRALIA.
Change 35.112 -MXG 35.04 Only, only with variable names longer than 32
VGETSORT bytes. ERROR Truncated SORTBY variable name not found.
May 9, 2017 The LENGTH for the new SORT variables is $32 now.
May 11, 2017 VGETSORT is used in BLDSMPDB, UTILROLL and MULTIPDB.
-VGETSORT: Cosmetic, UNINIT variable NOBS message because
it was not in the KEEP list, but had no impact.
Change 35.111 DB2 12.1, INVALID QLAC SEG ERROR, LENQLAC=218, new
VMACDB2 field QLACPRLV was inserted by DB2 CONTINUOUS DELIVERY,
VMACDB2H but was unknown to MXG as there was no notification by
May 9, 2017 IBM that a field was inserted. MXG detected the change,
May 11, 2017 printed the ERROR message, and deleted the record, so
some observations in DB2ACCT were not output. The error
led to the discovery of an updated DB2 MACLIB with this
text in DSNDQLAC member:
e26995 Continuous Delivery.
Product functional/build level. QLACPRLV. s28617
but a search for s28617 discovered nothing. Only a
search for the new field, QLACPRLV found it was added.
But there were no other references to the s28617 nor
e26995 tokens in the other MACLIB members.
Of course, now that I know this new field name, Google
found both fields referenced in APAR PI74456:
"IFCID 3 accounting information will now provide the
partner's functional/service/build level in a new
QLACPRLV field."
"IFCID 365 location statistics information will now
provide the partner's functional/service/build level
in a new QLSTPRLV field."
The real issue raised with DB2 support and unanswered
as of this writing is: HOW AM I SUPPOSED TO KNOW that
fields were inserted by Continuous Delivery.
These header fields are now kept in DB2ACCT:
QWHS_MOD_LVL='MOD LEVEL FOR*CONTINUOUS*DELIVERY'
QWHS_REC_INCOMPAT='INCOMPATIBLE*CHANGE*VALUE'
QWHS_REC_COMPAT='COMPATIBLE*CHANGE*VALUE'
QWHS_REC_VALIDITY='CHECK*NEEDED FOR*INCOMPAT*COMPAT'
The current MOD_LVL is V12R1M100 and MXG's COMPAT and
INCOMPAT count of changes is zero before and after this
INCOMPAT change. It is unclear how these fields could
be used, since they are after the record was changed.
Thanks to Dennis Gaetner, Fiduciagad, GERMANY.
Thanks to Sieghart Seith, Fiduciagad, GERMANY.
Change 35.110 Processing //PRISMAPR DD caused ERROR: UNDETERMINED I/O
VMACPRPR FAILURE because the DCB attributes were set for SMF, but
May 9, 2017 PRISMAPR input records are FB/256/27904.
Thanks to Gene Heikkinen, Blue Cross Minnesota, USA.
Change 35.109 Variables SM1209EX/EY/EZ/FA were accidentally dropped by
VMAC120 Change 35.024 from dataset TYP120R; you can correct with
May 5, 2017 MACRO _KT1209R SM1209EX SM1209EY SM1209EZ SM1209FA %
in your IMACKEEP tailoring member until you update MXG.
Thanks to Larry A. Gray, Lowes, USA.
Change 35.108 The ANALID report's TITLE can be changed with the TITLE=
ANALID argument, if you invoke %ANALID yourself, but BUILDPDB's
VMXGINIT invocation is internal, so this new macro variable
May 5, 2017 %LET MXGTITLEANALID=SMF RECORDS AUDIT REPORT;
Thanks to Robert Chavez, Florida Power and Light, USA.
Change 35.107 Support for IAM Version 9.0.
VMACIAM
May 4, 2017
Change 35.106 Adds an array of system IDs SYS1-SYS10 and creates new
VMXGUOW variables SYSTEMCICS (system of origin of the 110) and
May 4, 2017 SYSTEMDB2 (system where the 101 was found) to the
PDB.ASUMUOW dataset.
Change 35.105 The CICS duration fields are now formatted TIME16.6
VMAC110 to show the full resolution to the microsecond. FORMATS
May 4, 2017 only impact the printed/displayed value of the variable.
====== Changes thru 35.104 are in this MXG 35.04 dated May 1, 2017=====
Change 35.104 Support for EDGR/RMM APAR OA46947 which prints asterisks
VMACEDGR for RVCOMPRAT and RVPHYUSED when values can't be derived.
May 2, 2017 Only warning and hex dumps were printed; the output data
sets were correctly built; this change suppressed the
log messages when the values are asterisks.
Thanks to Craig Collins, State of Wisconsin, USA.
Change 35.103 If you specified "defer=yes" in lower case and the input
VMXGSET was on tape you got a 413 ABEND because the compare to
Apr 28, 2017 defer= was comparing to upper case. Not reported, found.
Change 35.102 -z/VM 6.3 and 6.4, BROKEN CONTROL RECORD ERROR because the
VMACVMXA INPUT STSI $VARYING255 STSILEN @; failed when STSILEN was
Apr 28,2017 greater than 255; increased to 512 in VXMTRTOP.
-Also 6.3, VXIODVSW code didn't protect the undocumented
extra 4 bytes. And these new variables are now created:
LANFORW ='LAN*FORWARDING*FLAGS'
OASPORTN ='OSA*PORT*NUMBER'
ACCTYPE ='ACCESS*LIST*TYPE*FLAG'
-New variables in VXSTSYG dataset:
RCCSCAPF='BFP*ZIP*CAPABILITY'
RCCCCAPF='BFP*CP*CAPABILITY'
RCCNCAPF='NOMINAL*CP*CAPABILITY'
SSI1PCPS='CP CORE*SPEED*CYCLE*PER MICRO'
SSI1SCPS='ZIP CORE*SPEED*CYCLE*PER MICRO'
-New variables in VXSTSYG dataset:
RSAWRTHROTS='TIMES*LIMITED*PAGING*BANDWIDTH'
RSAPRTHROTS='TIMES*PARTIAL*WRITE*THROTTLE'
RSANDMREC='GLOBAL*RECLAIM*TASK*INITIATED'
RSANDMRND='NDMBKS*RETURNED*GLOBAL*RECLAIM'
-New variables in VXSTORSP dataset:
PLSNDMRQ='FROM*RECYCLE'
PLSNDMLO='NDMBK REQS*RECYCLE*LOCAL*SUPPLIED'
PLSNDMGL='NDMBK REQS*RECYCLE*GLOBAL*SUPPLIED'
PLSNDMG2L='NDMBKS MOVED*GLOBAL*TO LOCAL'
PLSNDMDX='TIMES*TASK*RETURNED*CHAIN*TO LOCAL'
PLSNDMRET='NDMBKS*RETURNED*TO LOCAL'
PLSNDML2G='NMDBKS*MOVED*LOCAL TO*GLOBAL'
PLSNDMREL='NMDBKS*RETURNED*TO FREE'
PLSNDMREC='TIME*LOCAL*RECLAIM*INITIATED'
PLSNDMRND='NDMBKS*RETURNED*TO FREE*LCL RECLAIM'
PFXCLPLCNT='FRAMES*CLEARED*LOCAL*AVAIL*PLUS'
PLSCLALLO='CLEARED*LOCAL*AVAILABLE*LLOW THRESH'
PLSCLALHI='CLEARED LOCAL AVAILABLE*LHIGH THRESH'
PLSCLALADDED='FRAMES*ADDED TO*CLEARED*LOCAL'
PLSCLALFWREMOVED='FRAMES*ADDED TO*PROCESSED*LIST'
PLSCLALTRIMMED='FRAMES*TRIMMED*CLEARED*LOCAL'
PLSFPPFENTERED='TIMES*FPP FAULT*ENTERED*FOR GUEST'
PLSFPPFSUCCESS='TIMES*FPP FAULT*SUCCESSFUL'
PLSCPPFENTERED='TIMES*FPP FAULT*ENTERED*FOR CP'
PLSCPPFSUCCESS='TIMES*FPP FAULT*SUCCESSFUL*FOR CP'
PLSCPPFMDC='TIMES*FPP FAULT*EXITED*CACHE'
PLSCLALREQUESTS1='TIMES*FRAME REQ*CLEARED*AVAIL LIST'
PLSCLALUNFILLED1='TIMES*REQUEST*FOUND LAL*EMPTY'
PLSCLALREPLENOD='TIMES*REQUEST*FOUND CLA*EMPTY*DEMAND'
PLSCLALUNFILLED2='TIMES*REQUEST*FOUND CLA*EMPTY*BEFORE'
PLSCLALREQUESTS2='TIMES*REQUEST*FROM*CLA LIST'
PLSCLALUNFILLED3='TIMES*REQUEST*FOUND CLA*EMPTY*BEFORE3'
PLSBGCTM='CPU TIME*BACKGROUND*REPLEN*CL GAL'
PLSCGALREQUESTS='TIMES*WANTED*MOVE FRAMES*CGAL TO CLLA'
PLSCGALFRAMESR='FRAMES*WANTED*MOVE*CGAL TO CLLA'
PLSCGALMOVED='FRAMES*MOVED*CGAL TO CLLA'
PLSCGALNOLOCK='TIMES NOT*MOVED*CGAL TO CLLA*LOCK'
PLSCGALUNFILLEDN='FRAMES NOT*MOVED*CGAL TO CLLA*FILL'
PLSCGALWANTING='TIMES*CGLA*INSUFFICIENT*FRAMES'
PLSCGALUNFILLEDW='FRAMES NOT*MOVED*CGAL TO CLAL*DW'
PLSULALCNT='FRAMES ON*UNCLEARED*LAL'
PLSULALLO='UNCLEARED*LOCAL*AVAILABLE*LIST LOW TH'
PLSULALHI='UNCLEARED*LOCAL*AVAILABLE*LIST HI TH'
PLSULALREQUESTS1='FRAME REQ*UNCLEARED*LAL'
PLSULALUNFILLED1='TIMES REQ*UNCLEAR LAL*BEFORE*ATTEMPT'
PLSULALREPLENOD='TIMES REQ*UNCLEAR LAL*AND*ATTEMPT'
PLSULALUNFILLED2='TIMES REQ*UNCLEAR LAL*BEFORE*FILLED'
PLSSWPROCLCNT='FRAMES*ON THE*SOFTWARE*PROCESSED LIST'
Thanks to James T. Barton, Veterans Administration, USA.
Change 35.101 New parameter OUTCODE= lets you insert some code just
VMXGGETM prior to the end of VMXGGETM. Should be complete data
Apr 28,2017 or PROC STEPS.
Thanks to Craig Collins, State of Wisconsin, USA.
Change 35.100 SYSLOG code has been updated; the old code was 2016.
SYSLOG
May 2, 2017
Thanks to Karl Lasecki, Chemical Abstracts Service, USA.
Change 35.099 ANALID relocate.
Change 35.098 RMF III Filter enhancements.
ADOCRMFV -Enhancements for character data filtering for RMF Monitor
ASMRMFV III CPU (Processor Data Control Block), CPC (CPC Data
VMACRMFV Control Block), improved message RMFV029* DEAD SPACE
Apr 26, 2017 controls, better error message formats and content, and
other usability and performance gains.
-1 new character filter is added to support CPU entry
selection from this table to the RMFBSAM output file.
This filter is effective only if the CPU or CPC table is
selected and applies to BOTH tables.
New Keyword Aliases
------------ ------------------------------------------
CPUSYSTEM= CPUSYSID=, CPUSID=
Since this is the only filter for this table there are NO
CPUAND/CPUOR parameters.
Syntax and usage mirrors that used for the existing
SYSTEM= parameter for selection by SMF Sysid using ranges
and/or patterns.
-1 new filter is added to support CPC entry selection
from this table to the RMFBSAM output file. This filter
applies ONLY to the CPC (not the CPU) table.
New Keyword Aliases
------------ ------------------------------------------
CPCSYSTEM= CPCSYSID=, CPCSID=
Since this is the only filter for this table there are NO
CPCAND/CPCOR parameters.
Syntax and usage mirrors that used for the existing
SYSTEM= parameter for selection by SMF Sysid using ranges
and/or patterns.
-TUTORIAL:
The new CPCSYSTEM= parameter may appeal to large
installations running multiple z/OS LPARs on a CEC
(Central Electronic Complex) and using RMF Monitor III
gathering data on several of them.
RMF Monitor III creates the CPCDB (Central Processing
Complex Data Block) table for each instance of RMF
Monitor III on a given CEC except if the LPAR is a z/VM
guest.
The CPCDB (aka CPC) has LPAR settings and Logical
Processor data for every image on the CEC whether it be
a z/OS LPAR or not.
There is no RMF III option to turn off CPC data
collection, so this parameter is an alternative.
As long as the RMF Monitor III MINTIME, CYCLE, and SYNC
options are identical redundant CPC tables for every RMF
Monitor III native (non-guest) LPAR on the CEC are
created at every MINTIME interval.
The MXG PDB build will create a ZRBLCP observation for
each Logical Processor for each LPAR for every MINTIME
interval. For installations with several RMF Monitor III
LPARs on a CEC this can result in a lot of extra, but not
useful duplicate SAS ZRBLCP observations.
See new documentation Section 30 "CPC Data Relief
Technique" for more details on use of CPCSYSTEM=.
It is a user responsibility to set up CPCSYSTEM= for each
CEC configuration properly and to track any LPAR SYSID
changes as they occur. An incorrect CPCSYSTEM=
specification will result in loss of data in the MXG
ZRBLCP SAS data set should the SYSID no longer exist
or be misspelled.
-CSR (Common Storage Remaining) processing now moves CSR
entries in blocks for as many entries that fit to the
RMFBSAM output buffer when NO CSR character data filters
are used.
When these filters were added in MXG Change 34.373
processing changed to move one CSR entry at a time to the
output buffer. However, this is an unnecessary overhead
if no CSR filtering is in effect. The earlier processing
technique is restored for this case.
A test with 21 RMF Monitor III sample data sets at the
35.098 level showed about a 1% CPU reduction for CSR
processing with no filters used compared to the 34.373
level. This will vary with the number of CSR entries
and RMF III VSAM data sets processed.
-The MXG00 record version is raised to x'08' from x'07'.
New fields added to the MXG00 record include:
CPUSYSTEM= and CPCSYSTEM= Range/Pattern maximums
CPUSYSTEM= and CPCSYSTEM= Range/Pattern table sizes
% of available TIOT entries used
ASMCPCRX='MAXIMUM*CPCSYSTERM*RANGES'
ASMCPCPX='MAXIMUM*CPCSYSTERM*PATTERNS'
ASMCPURX='MAXIMUM*CPUSYSTERM*RANGES'
ASMCPUPX='MAXIMUM*CPUSYSTERM*PATTERNS'
ASMSHSPL='WARNING*LIMIT*PCT SPACE*USE'
ASMCPCRS='SIZE*CPCSYSTEM*RANGE*TABLE'
ASMCPCPS='SIZE*CPCSYSTEM*PATTERN*TABLE'
ASMCPURS='SIZE*CPUSYSTEM*RANGE*TABLE'
ASMCPUPS='SIZE*CPUCSYSTEM*PATTERN*TABLE'
-TIOT entries used percentage is added to the RMFV000I
message. TIOT usage information is grouped on a single
report line.
-Support for ILIMIT= (alias ILIM=) and SLIMIT= (alias
SLIM=) keywords is added to control appearance of
the RMFV029* DEAD SPACE message (*=I,W,E,S).
Previous versions of ASMRMFV could issue this message for
exhausted RMF III indexes even when the VSAM data set
usage was relatively high. In this case re-allocating
the VSAM data set to make it smaller is not productive.
ILIMIT= specifies a percentage in the range of 0 to 100
as a threshold for RMF III VSAM Data Set Header (DSH)
indexes usage. The default is 100.
SLIMIT= specifies a percentage in the range of 0 to 100
as a threshold for RMF III VSAM Data Set space usage.
The default is 95.
The defaults of ILIMIT=100 and SLIMIT=95 with INDEXES and
SPACE options in effect mean that if all 1110 sample
indexes are exhausted in the Data Set Header (DSH)
record, but the RMF Monitor III VSAM data set is 95% or
more utilized no DEAD SPACE condition is flagged.
See the documentation for RMFV029* for how the settings
of NOINDEXES/INDEXES, NOSPACE/SPACE, ILIMIT=, and SLIMIT=
parameters interact.
Users who find RMFV029* a nuisance rather than an aid
can suppress it completely with ILIMIT=0 and SLIMIT=0.
ILIMIT= and SLIMIT= values in effect are displayed in
message RMFV037I.
Section 22 RMF III VSAM Data Set Index Usage and Sizing
is updated to discuss use of ILIMIT= and SLIMIT= options.
-There are now 4 distinct levels for messages that can
have variable severity based on the settings of the
various existing *ERR= condition keywords:
*ERR Message Return
Setting Suffix Meaning Code
------- ------ ------------------------- ---------
IGNORE I Ignore error/continue No change
WARN W Warn error/continue 0004
ERROR E Issue error/may continue 0008
ABEND S Issue error/Abend U0998 N/A (1)
(1) Abends have a distinct Reason Code but no Return
Code.
In past ASMRMFV versions 'E' suffixed messages
inconsistently may or may not have resulted in an Abend.
-Distributed *ERR settings remain as:
Keyword DEFAULT CONTROLS
--------- ------- -------------------------
ALLOCERR= WARN DYNAMIC ALLOCATION ERRORS
ATTRERR= WARN DATA SET ATTRIBUTE ERRORS
CATERR= WARN CSI CATALOG LOOKUP ERRORS
DEADERR= WARN VSAM DEAD SPACE ERRORS
DSIGERR= WARN DSIG ID (DSH) ERRORS
DSNERR= WARN CSI DSNAME LOOKUP ERRORS
DUPERR= WARN DUPLICATE DSNAME ERRORS
EMPTYERR= IGNORE EMPTY VSAM DATA SET ERRORS
PATTERR= ABEND PATTERN AND/OR RANGE ERRORS
READERR= ABEND VSAM READ I/O ERRORS
TABERR= WARN RMF III TABLE VALIDATE ERRORS
TYPEERR= WARN DATA SET TYPE ERRORS
RCERR= WARN REPORT CLASS FIND ERRORS
RGERR= WARN RESOURCE GROUP FIND ERRORS
SCERR= WARN SERVICE CLASS FIND ERRORS
WLERR= WARN WORKLOAD FIND ERRORS
-ASMRMFV will now generate the correct message format for
variable severity messages during assembly based on the
defaults above. This avoids unnecessary tailoring during
ASMRMFV initiation. Any user overrides of the above
settings will still require tailoring of related
messages by ASMRMFV during start up.
-Internal error message generation interface updated for
following messages:
RMFV004E, RMFV005*, RMFV007S, RMFV034S, RMFV035*,
RMFV056* (*=I,W,E,S)
Improvements for these messages include:
3 separate error messages subroutines replaced by one
for code path length reduction.
Extraneous blanks in these error messages eliminated
for better legibility.
Clearer and less cryptic error descriptions.
-RMFV006E message had incorrect timestamp when FROMDATE=
exceeded TODATE=
-RMFV007S message missing DDNAME when RMFBSAM DD was not
present.
-RMFV007S message will now show N/A when a Reason Code is
not available for a failed function or service.
-Improve logic of DOW= keyword processing when using a
range, i.e. DOW=day1:day2 to examine the last half of
the day of week range if an error is found in the first
half. Also leading and trailing colons are stripped
before length checking.
-Former documentation Section 30 Summary is now Section 31
and former Section 31 Bibliography is now Section 32.
-Several documentation Sections are updated to support
the above changes:
Section 0 "Contents"
Section 5 "Input Data Selection Parameters"
Section 6 "Report Control Parameters"
Section 8 "Error Handling Parameters"
Section 12 "Messages"
Section 13 "Filtered Records"
Section 16 "Return Codes"
Section 25 "Ranges and Patterns"
Section 30 "CPC Data Relief Technique"
Section 31 "Summary"
Section 32 "Bibliography"
Change 35.097 Four IMF variables that are INPUT with TODSTAMP8 are now
VMACCIMS formatted DATETIME25.6 to display full microseconds. The
Apr 25, 2017 other datetimes are limited to DATETIME21.2 resolution.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 35.096 New UTILROLL utility combines all SAS datasets from one
UTILROLL or more SAS data libraries (think "hourly" PDB runs) into
JCLROLL1 another LIBNAME (think "daily" PDB), either concatenating
JCLROLL2 the new data, or interleaving to preserve the sort order.
VGETSORT If the ROLLTO LIBNAME is empty or the dataset being added
Apr 24, 2017 added to does not exist the code will ignore the ROLLTO
LIBNAME and use only the ROLLFROM to create the ROLLTO
datasets.
-VGETSORT could return bad information if there was
a variable name longer than 8 bytes. Length was
increased to 32 and NOBS ENG were added to the output.
Change 35.095 APPL PCT variables are created in TYPE72GO to match the
VMAC7072 RMF Workload report values:
Apr 24, 2017 APPLCP ='APPL PCT*OF 1 CPU*CPU TIME*ON CP'
APPLAAPCP='APPL PCT*OF 1 CPU*ZAAP ELIG*ON CP'
APPLIIPCP='APPL PCT*OF 1 CPU*ZIIP ELIG*ON CP'
APPLAAP ='APPL PCT*OF 1 CPU*CPU TIME*ON ZAAP'
APPLIIP ='APPL PCT*OF 1 CPU*CPU TIME*ON ZIIP'
with this code:
IF R723MCF GT 0 THEN
APPLCP= 100*CPUTM/(DURATM*R723MCF);
IF R723MCFI GT 0 THEN DO;
APPLAAPCP=100*CPUIFETM/(DURATM*R723MCFI);
APPLAAP= 100*(256*CPUIFATM/R723NFFI)/(DURATM*R723MCFI);
END;
IF R723MCFS GT 0 THEN DO;
APPLIIPCP=100*CPUZIETM/(DURATM*R723MCFS);
APPLIIP= 100*(256*CPUZIPTM/R723NFFS)/(DURATM*R723MCFS);
END;
Thanks to Ray Bole, IBM Global Services, USA.
Change 35.094 Support for BMC Mainview for Java Environment creates
EXMVJE01 DDDDDD MXG MXG
EXMVJE02 DATASET DATASET DATASET
EXMVJE04 SUFFIX NAME LABEL
EXMVJE07
EXMVJE08 MVJE01 MVJE01 JMX MEMORY SUMMARY
EXMVJE12 MVJE02 MVJE02 JMX THREAD SUMMARY
IMACMVJE MVJE04 MVJE04 JMX CLASS LOADING SUMMARY
TYPEMVJE MVJE07 MVJE07 JMX GARBAGE COLLECTION SUMMARY
TYPSMVJE MVJE08 MVJE08 JMX MEMORY POOLS
VMACMVJE MVJE12 MVJE12 JMX CPU USAGE
VMXGINIT
Apr 25, 2017
Change 35.093 MXG 35.03 only, variable PLATBUSY in TYPE70/RMFINTRV and
VMAC7072 PCTOFHDW in RMFINTRV were incorrect after Change 35.064
Apr 22,2017 revised the SHARE calculations.
Thanks to Paul Naddeo, FISERV, USA.
Thanks to Robin Hanley, FISERV, USA.
Thanks to David Bixler, FISERV, USA.
Change 35.092 Support for z/VM 64 (INCOMPATIBLE).
VMACVMXA -Dataset VXSYTCUG new variables
Apr 20,2017 SSI2MTIF='MULTITHREADING*CONFIGURATION'
SSI2MTGF='MULTITHREAD*GENERAL*PROC*CONFIG'
SSI2MTID='MULTITHREAD*MAX*TID'
LCUTCTOD='DATETIME*WHEN CORE*INFO*FETCHED'
-Dataset VXMTRSYS new variable
CALFLAG3-'MISCELLANEOUS*FLAGS*/
-Datasets VXUSEACT and VXUSELOF new variables
VMDTTIME_MT1='TOTAL*MT-1*EQUIVALENT*TIME'
VMDVTIME_MT1='RUN*MT-1*EQUIVALENT*TIME'
VMDVTMP_MT1 ='EQUIV*MT-1*VTIME*ON PRIMARY'
VMDTTTP_MT1 ='EQUIV*MT-1*VTIME+SIM*PRIMARY'
VMDVTMS_MT1 ='EQUIV*MT-1*VTIME*ON SECNDRY'
VMDTTMS_MT1 ='EQUIV*MT-1*VTIME+SIM*SECNDRY'
VMAVTMP_PRO ='TOTAL*MT-1*PRORATED*CORE*PRI'
VMATTMP_PRO ='RUN*MT-1*PRORATED*CORE*PRI'
VMAVTMS_PRO ='TOTAL*MT-1*PRORATED*CORE*SEC'
VMATTMS_PRO ='RUN*MT-1*PRORATED*CORE*SEC'
PROBITS='PRORATED*CORE*TIME*BITS'
-Datasets VXPRCPUP new variables
WHIOCAPV='MAX*CORES*PERMITTED'
WHIOCTVR='CALCULATED*T/V*RATIO'
WHIOPTVR='CEILING*PROJECTED*T/V*RATIO'
SRXTVCNF='CONFIDENCE*PERCENTAGE'
CALTVALG='CEILING*PROJECTION*ALGORITHM'
WHIOTVCT='CEILING*PROJECTION*VALID*SAMPLES*/
WHIOGCPV='MAXIMUM*AGGREGATE*CORES'
-Datasets VXIODVSW new variables
VQSAFLAG ='LACP*CONFIGURATION'
NIDLAPRE ='PREVIOUS*LOAD*BALANCE'
NIDLACUR ='CURRENT*LOAD*BALANCE'
NID_TOTPFCNT='PREVIOUS*LOAD*BALANCE*FRAMES'
-New segments IODPAD,IODPON,MTRPCI are not yet supported.
-These 6.4 segments don't exist in my test data so these
changes have NOT been validated yet:
PRCCUP SYTCUG SYTCUM SYTCUP
Thanks to Diana L. Bodner, Progressive, USA.
Change 35.091 -Sometimes failed with a two level dataset name (unknown
ANALCNCR cause). VGETOBS logic modified. Now will run SGPLOT
Apr 22, 2017 if your SAS version is GE 9.3.
-New example to count/plot concurrent TELNET sessions from
the TYP11921 dataset.
Change 35.090 -Support for CA'S OPSS Product USER SMF Record.
VMACOPSS These datasets are created:
Apr 22, 2017
May 9, 2017 DDDDDD MXG MXG
DATASET DATASET DATASET
SUFFIX NAME LABEL
OPSS01 TYPOPSS1 SS TERMINATION SUMMARY
OPSS02 TYPOPSS2 SS OSF SERVER TERMINATION
OPSS03 TYPOPSS3 SS AOF RULE DISABLEMENT
OPSS04 TYPOPSS4 SS GLOBAL VARIABLE
OPSS05 TYPOPSS5 SS SQL STATISTICS
OPSS06 TYPOPSS6 SS IMS BMP STATISTICS
OPSS07 TYPOPSS7 SS OSF TRANSACTION
OPSS08 TYPOPSS8 SS EPI STATS
Thanks to Bruce Sloss, PNC, USA.
Change 35.089 The NDM-CDI new IHDRNDM exit member allows selection of
IHDRNDM which NDM Record Types are output with this logic:
VMACNDM //SYSIN DD *
VMXGINIT %LET MACNDMH= %QUOTE( IF NDMRTYPE='CT';) ;
Apr 19, 2017 %INCLUDE SOURCLIB(TYPSNDM);
Change 35.088 -Running MXG on ASCII to read SMF using ftp access method
BUILDPDB can free the SMF allocation when SMF read is completed
Apr 15, 2017 with this tailoring in your //SYSIN:
%LET EPDBOUT=%QUOTE(
FILENAME SMF CLEAR;
);
If your SMF data is a GDG, this will unblock the base GDG
name as soon as possible.
-If running MXG on z/OS, add FREE=CLOSE to the //SMF DD to
also free the allocation when the read is complete.
Change 35.087 New ANALFTP analysis of FTP has five report examples:
ANALFTP GENERATE REPORTS FROM PDB
Apr 14, 2017 GENERATE REPORTS FROM SMF
GENERATE REPORTS FROM SMF AND STORE DATA IN PDB
GENERATE REPORTS FROM SMF LOOKING FOR A USER
GENERATE REPORTS FROM SMF LOOKING FOR A DATASET
Reports are from TYPE119 records; see also ANAL119 and
ANALCNCR for additional reports.
Change 35.086 New variable FSBYTERATE='TRANSMISSION*BYTE*RATE' is added
VMAC119 to TY119070 dataset.
ANALFTP
Apr 13, 2017
Change 35.085 Possible exposure with too long a code line generated by
VMXGPRNT VMXGPRAL print with variable name and label as heading.
Apr 13, 2017 With 32 character variable name and 40 character label,
the line generated could be 109 characters, exceeding the
z/OS limit of 72 (S=72,S2=72). Two lines are now created
and the label truncated (no more than 5 lost) to trim if
needed.
Change 35.084 UTILCOPY failed if it found no datasets to copy with an
UTILCOPY undefined macro variable NUMMEM. Now it tells you that
Apr 10, 2017 it did not find anything to copy.
Change 35.083 DB2 Trace IFCID=316 dataset T102S316 variable QW0316TS is
VMAC102 now correctly converted to a datetime value.
Apr 10, 2017
Change 35.082 Reserved Change Number
Apr 2, 2017
Change 35.081 DB2ACCTP dataset, these "truncated" variables
VMACDB2 QPACLOCN QPACCOLN QPACPKID QPACASCH QPACAANM
Apr 2, 2017 were increased to $128 LENGTH, but the longer length text
was not input when QPACOFFn was non-zero due to incorrect
circumvention for prior invalid length in Change 31.015.
Thanks to Rachel Holt, Fidelity Systems, USA.
Change 35.080 *New z/OS 2.2 Changes found in Jan 2017 SMF Manual.
VMAC30 -VMAC30.
Apr 1, 2017 New variable SMF30JF1='JOB/SESS*ID'
*This change is incomplete.
Change 35.079 Some accumulated z/VM 6.3 SMT fields in VXSYTPRP dataset
VMACVMXA weren't deaccumulated, and the below new unaccumulated
Mar 31, 2017 counters contain an error code '80'x in first bit when
Apr 5, 2017 the counter cannot be populated that is now decoded and
Apr 11, 2017 the first two instances of each error is printed on the
FORMATS SAS log, although there is nothing you can do for these
these error conditions, and the variable is set to a
missing value for these intervals.
SYTPRP_CAL_CAPBYTYPE SYTPRP_CAL_MAXCAPBYTYPE
SYTPRP_CAL_MTUTILBYCORE SYTPRP_CAL_MTUTILBYTYPE
SYTPRP_CAL_PRODBYCORE SYTPRP_CAL_PRODBYTYPE
-Dataset VXAPLSL0 was "hosed" because my loop was
DO CPUNR=1 TO NRCPUS, but first CPU is CPUNR=0, and
the CPUNR at the end of the segment had been overlooked.
-PFXPRKWT is now deaccumulated.
-The VXAPLSLx dataset only has observations output when
there was activity by the Linux machine; the LINXTIME is
the "wake up" time in this interval and is used to create
DELTALINXTM=MRHDRTOD-LINXTIME with the maxiumum duration
of an interval that that VMDUSER could have been active.
-These variables added to VXMTRSYS:
RCCCCAPF RCCSCAPF SYSMTFLG RCCMTRSM RCCMTCFM RCCMTPMT
RCCMTTDW RCCMTFRS RCCCOMXT RCCCOALL
CAL_RCCACMNT1-4='CPUTYPE-1-4*ACTIVATED*THREADS'
CAL_CPUTYPE1-4='CPUTYPE-1-4*CPU*TYPE'
CAL_RCCSYMNT1-4='CPUTYPE-1-4*MAXIMUM THREADS*SOFTWARE'
CAL_RCCHWMNT1-4='CPUTYPE-1-4*MAXIMUM*THREADS*HARDWARE'
CAL_RCCCOMNT1-4='CPUTYPE-1-4*REQUESTED*THREADS'
CAL_RCCCRMNT1-4='CPUTYPE-1-4*REQUESTED*THREADS'
CAL_RCCSMMNT1-4='CPUTYPE-1-4*SPECIFIED*THREADS'
-These variables added to VXSYTCUP:
LCXCMTIT='MT*IDLE*TIME'
LCXCHPCP='LPAR GROUP*ABS CAPACITY*CAP VALUE'
CALGCAPV='ABSOLUTE*CAP*AMOUNT'
-Variable RDEVCTRG is removed from the DIDIO test to
create VXIODDEV because it is always non-zero and the
only non-zero field for non-DASD records.
-The SMT Busy Time calculation was revised to
LCXCMTBY=(2*LCUCACTM)-LCXCMTIT
Thanks to Graham Harris, RBS, ENGLAND.
Change 35.078 If you specified SORTEDBY=YES and you run the daily and
BLDSMPDB weekly/monthly processing in the same SAS execution of
Mar 31, 2017 BLDSMPDB the SORTEDBY= was ignored because VMXGSUM used
the same MACRO variable name making it a GLOBAL macro
variable to VMXGSUM and overriding the BLDSMPDB used
parameter. NO data was lost - just not in the order
you may have expected. Circumvented by holding the
value in a LOCAL macro variable and the reinstating
it after DAILY processing is completed.
Change 35.077 Comments only. Some enhanced comments in examples
UTILBLDP and a redundant WANTSMF in one example was removed.
Mar 31, 2017
Thanks to John Compton, WPS, ENGLAND.
Change 35.076 Some long RMF III variables have '00'x null characters
VMACRMFV instead of blanks at the end; they are converted to
Mar 29, 2017 blanks.
Change 35.075 TYPE1415 records have subtype 5 segments for TAPE and all
FORMATS datasets with a Data Class. For records without subtype 5
VMAC1415 the below flag variables are now set to 'FF'x and will
Mar 29, 2017 print "NOT AVAILABLE" with new $MGNOTAV format:
SMF14BFG SMF14FLGS SMF14FLG2 DEB2XUPF EADSCBOK
DCBEEX31 XTIOTYES
Variable SMF14ALIAS will be blank and SMF14LBS will be a
missing value.
Thanks to Michael Oujesky, DTCC, USA.
Change 35.074 -INVALID SYTCPU segment messages with SEGLEN=48 and NRCPS
EXXAMPRC 30 (SEGLEN should be 684) are valid and a problem is open
EXXMVPID with Barton.
FORMATS -New VSIPID Process Segment creates XMVISPID dataset.
IMACXAM -New PRCCPU LIMPOOL Segment creates XAMSYPRC dataset, but
VMACXAM values for FLAGSPRC have '60'x for both limited cpuaffon.
VMXGINIT
Mar 28, 2017
Change 35.073 DB2ACCT variables QWACALOG and QWACALCT are now always
VMACDB2 missing values; they have been reserved for years, but
Mar 28, 2017 MXG code had still INPUT them causing confusion.
Thanks to Peter Gray, HPE Australia, AUSTRALIA.
====== Changes thru 35.072 are in this MXG 35.03 dated Mar 27, 2017=====
Change 35.072 -MXG 35.03. VMAC1415, hex dumps but no error, because
VGETJESN line 962 in VMAC1415 IF VOLSER NE VOLSER1 THEN LIST;
VMAC1415 left from debugging needs to be deleted.
Mar 24, 2017 -WARNING TYPETASK NOT DECODED, JCTJOBID=A0000022 expected
Mar 27, 2017 either 'ASCH' or 'OMVS' in to be stored in TYPETASK from
variable SUBSYS, but this task has SUBSYS blank. Now, if
SUBSYS is blank, TYPETASK='APPC' is stored.
Thanks to Paul Naddeo, Fiserv, USA.
Change 35.071 Reserved Change Number.
Mar 23, 2017
Change 35.070 New fields are added to zPROTECT SMF records:
VMACZPRO New variable in ZPROT05:
Mar 23, 2017 ZPRRAUSR='ALTERNATE*USERID'
New variable in ZPROT16:
ZPRTMINP='MIN*REQUEST*PERFORMANCE*TIME'
ZPRTMAXP='MAX*REQUEST*PERFORMANCE*TIME'
ZPRTAVGP='MEAN*REQUEST*PERFORMANCE*TIME'
ZPRTAUSR='ALTERNATE*USERID'
ZPRNPROT='PROTECT*OPERATIONS'
ZPRNACCE='ACCESS*OPERATIONS'
====== Changes thru 35.069 are in this MXG 35.03 dated Mar 22, 2017=====
Change 35.069 Support for CICS Version TS/5.4 Beta 11 adds three new
UTILEXCL variables to CICSTRAN:
VMAC110 LPARNAME='LPAR*NAME'
Mar 21, 2017 MPSRACT='TIMES WHEN*POLICY*EVALUATED*AND TRIGGERED'
MPSRECT='TIMES WHEN*POLICY*RULES WERE*EVALUATED'
Thanks to Andy Wharmby, IBM CICS Hursley, ENGLAND.
Change 35.068 Support for MQ Version 9.1 SMF 115 new Subtype 201 record
EXTY115Y creates new dataset:
FORMATS dddddd dataset description
IMAC115 TY115Y MQ115201 MQ SUBTYPE 201 PAGESET STATS
VMAC115 Mar 27: FORMATS MG115EX and MG115PS added.
VMXGINIT
Mar 20, 2017
Mar 27, 2017
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.067 -Standalone execution failed because &PDBMXG.SMFINTRV
SMFINTRV needed to be &PDBMXG..SMFINTRV, but MXG invocations in
Mar 14, 2017 BUILDPDB/BUILDPD3 were correct so no error there.
Apr 18, 2017 -Three new interval START datetimes are created so you
can directly summarize to that interval by your choice of
START15INT='FIFTEEN*MINUTE*INTERVAL*START'
START30INT='THIRTY*MINUTE*INTERVAL*START'
STARTHRINT='HOUR*INTERVAL*START'
Apr 11: Revised. Those three variables are now created
by VMXGDUR, with the DEFAULT SMFINTSYNC59 "SYNC59" option
defaulting to YES, to be consistent with RMFINTRV.
If your records are NOT "SYNC59", i.e., are written :00
use %LET SMFINTSYNC59=NO; in your //SYSIN.
Unlike other "INTRV" programs that invoke VMXGDUR to
create new summary datasets, SMFINTRV does NOT summarize
TYPE30_V records; instead it only combines the multiple
SMF 30 records (MULTIDD='Y' steps with LOTS of DDs) into
one observation per interval with all EXCPs totaled.
If you do want to summarize PDB.SMFINTRV across intervals
the ANALSMFI program provides that example.
Change 35.066 APAR OA59593 adds new flag variable
BUIL3005 SMF30CAS_INELIGHONOR='ELIG WORK*IS NOT*OFFLOADED*TO CP?'
BUILD005 to SMF 30 TYPE30_V/TYPE30_4/TYPE30_V datasets to identify
VMAC30 jobs whose eligible work was NOT offloaded to CPs for
Mar 19, 2017 help. The variable is also added to PDB.SMFINTRV and
PDB.STEPS datasets.
Change 35.065 Almost "cosmetic": READDB2 could create dataset DB2STATR
READDB2 even though you did not request it, due to Change 34.265
Mar 14, 2017 that overlaid a token for DB2NETZA. No obs were output.
Change 35.064 SMT Mode corrections and enhancements.
VMAC7072 -ZIPACTTM in PDB.ASUMCELP is the best source of per-LPAR
Mar 13, 2017 hardware zIIP CPU busy, created in BUILDPDB/ASUM70PR.
This change adds SMT_NUM to PDB.ASUMCELP to identify the
SMT mode.
-Variable ZIPACTTM in PDB.TYPE70 could be too small for
an LPAR when in SMT_NUM=2; in rare cases the last LPAR's
was not included.
-Correction for ZIPACTTM in TYPE70 also caused
PLATBUSY LPARSHAC LPARSHAR TOTSHARC TOTSHARE
ZIPSHARC ZIPSHARE LZIPSHAC LZIPSHAR
to also be corrected/changed values in compares.
-TYPE70/TYPE70PR variables CPUID SMT_CORE_ID LCPUADDR and
(new) SMT_THREAD are now formatted numeric HEX2. to
to match RMF reporting formats.
-In the ASID TYPE30 and Service Class TYPE72GO data, the
recorded MT=2 CPUZIPTM/ZIPUNITS values are "inflated"
above the actual hardware zIIP time, and the hardware
equivalent can not be calculated using R723MCFS, the
Maximum Multi-Threading Capacity Factor.
LPAR with 7 zIIP engines in SMT_NUM=2 MT=2 mode:
UPTIME: 1:45 ZIPACTTM: 1:31 72-CPUZIPTM: 2:05 hh:mm
105 min 91 min 125 min
"Above Inflation Factor" 125/91=1.37
Interval R723MCFS =1.17871
"MCSF Equivalent zIIP CPU= 125/1.17871 = 106 min
but that is as large as the UPTIME of 105 minutes.
And IBM's range of R723MCFS values is 1.1 to 1.4,
with a theoretical max of 2.0.
So: what to do? Maybe Nothing. This is what is recorded
now in SMF 30/72 records in MT=2 mode (AND ONLY in ASID
and SRVCLASS records): NO INFLATED VALUES IN RMF 70 SMF
data that are used for zIIP capacity metrics. So, while
the values are too large, their interval sum can be used
to determine the proportion of the MT=2 zIIP usage for
each workload, job, or service class.
Apr 10: IBM SMT folks have examined these data and have
confirmed my conclusions that the values are inflated.
August: IBM confirmed that at very high or very low util
the SMT values are inflated; it's unclear if that will
ever change.
Daniel Rosa's available online 2015 SHARE paper "IBM z
Systems z13 Simultaneous Multi-Threading R(Evolution)"
discusses the MT=2 metrics.
Jul 30, 2018: The CAPZIPRT can exceed 100% due to this
inflation of 30/72 CPUZIPTM when SMT Mode is enabled.
Change 35.064A Multi-Volume DCOLDSET records populate some fields only
VMACDCOL in the first (DCDVOLSQ=1) record. When TYPSDCOL program
Mar 10, 2017 is used, these fields are retained from the first record
and are now output in PDB.DCOLDSET.
-Records with DCDVOLSQ=0 were created in WORK.TYPEDCOL
but were then not output in the first record logic, but
now they are output to PDB.DCOLDSET.
Change 35.063 -XAMSYS records with SYTCUP SEGLEN=148 but SYTNLPS=2 or 3
VMACXAM are wrong, protected by changing SYTNLPS to 5 while the
Mar 10, 2017 problem is opened with Barton now to resolve.
-XMTCPSYS dataset variable NAMENODE was blank because the
128-byte CONTACT was reduced to 64, then NAMENODE, then
64 bytes are inserted to keep the original SEGLEN.
Thanks to Matthew L. Rennebohm, State of Wisconsin, USA.
Change 35.062 Support for Mainview for CICS CMRDETL file VER 6700
VMACMVCI changes that caused INPUT STATEMENT EXCEEDED error.
Mar 6, 2017
Thanks to DJ Chen, AST/Southwood Shared Resource Center, USA.
Change 35.061 Enhancement for PDB.ASUMCELP (per-LPAR CEC data) adds the
VMXG70PR variable SMT_NUM to identify the SMT Mode of zIIPs, from
Mar 7, 2017 the PDB.TYPE70EN dataset, and protection if that dataset
was not copied to the PDB data library. SMT_NUM will be a
missing value for PHYSICAL and IFL-Only LPARS, or LPARS
with no zIIPs.
Change 35.060 Enhancement for SMF 120 Subtype 11 TYP120BL new variables
VMAC120 containing TOTAL, CP ONLY, and ZIP ONLY CPU times:
Mar 5, 2017 SM120BCPUTM='TOTAL*CPUTIME*USED*BCA1-BBZ1'
SM120BCPCPUTM='CP ONLY*CPUTIME*USED*BCA2-BBZ2'
SM120BZIPCPUTM='ZIP ONLY*CPUTIME*USED'
are calculated, thanks to the IBM WebSphere Developer who
educated me that the 16-byte binary TIMEUSED format used
in this record for the START and END Accumulated CPU data
contains two 8-byte CPU times: the TOTAL CP+ZIIP in the
first 8 bytes and the CP ONLY CPU time in the second 8.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.059 Support for CA SYSVIEW for IMS 14.0 update in 2014 Change
VMACSVIE 32.170 has now been tested with actual data, and these
Mar 4, 2017 variables had missing values that are now corrected.
Mar 27, 2017 IMTR_CLK_SUBQ06_TIME IMTR_CLK_MPP_CPU IMTR_CLK_SMB_ENQ
IMTR_CLK_CNT_ENQ IMTR_CLK_MXG_END IMTR_CLK_CNT_GU
IMTR_CLK_UOW_END IMTR_CLK_UOW_START
IMTR_CLK_SCHEDULE_TIME
-Mar 23: Several TODSTAMP variables were not converted
from GMT to local time zone.
Thanks to Denise Williers, Wipro, USA.
Change 35.058 Support for IMS LOG 67D0 DIAGNOSTIC RECORD for DC '02'x
EX67D002 created new IMS67D002 dataset. Note that both D0TIME and
FORMATS IMSSTCK are both GMT because there is no GMT offset in
IMACIMS the 67D0 log record.
VMACIMS
VMXGINIT
Mar 2, 2017
Thanks to Rosa Maria Martinez Alonso, Bustia, SPAIN.
Change 35.057 Reserved Change.
Mar 1, 2017
Change 35.056 -If you used KEEPMNTH= (very rare) an MDY() could fail.
VMXGSUM -If your INCODE= contains a DATA step, the CLASSNWAY
Mar 1, 2017 option failed, but now a DATA step's existence in the
INCODE is parsed, and if found, SUMBYCLASS is reset.
Change 35.055 Support for Mainview for IP PTF BPN2331 that adds
VMACMVIP variable TNDSTATX='CONNECTION*STATE*ACTIVE*CLOSED?'
Mar 1, 2017 variable to the I490 dataset.
Change 35.054 -RMF Monitor III enhancement for OPD (OMVS Process Data)
ADOCRMFV table character data filtering and usability.
ASMRMFV -These filters are intended for building ad hoc MXG RMF
VMACRMFV III PDBs for studies avoiding the overhead of generating
Mar 1, 2017 a full OPD table-based PDB. They control which OPD table
entries are output to the RMFBSAM file.
-Five new filters are added to support OPD entry selection
from this table to the RMFBSAM output file. These
filters are effective only if the OPD table is selected.
They are applied in the order shown when multiple
different keywords are used.
New Keyword Aliases
------------ ------------------------------------------
OPDPROCNAME= OPDPROCNA=, OPDPROCNM=, OPDPROC=, OSDPROC=
OPDPN=
OPDJOBNAME= OPDJOBNA=, OPDJOBNM=, OPDJOB=, OPDJN=
OPDUSERNAME= OPDUSERNA=, OPDUSERNM=, OPDUSER=, OPDUN=
OPDAND None
OPDOR None
The order of OPD filter application is:
1) OPDPROCNAME=
2) OPDJOBNAME=
3) OPDUSERNAME=
-TUTORIAL:
Ranges of the form keyword=first:last may be used with
any of the above keywords except OPDAND and OPDOR.
The colon character ':' is required for a paired range
specification. All entries GE the first value and LE the
last value are selected for output to the RMFBSAM file.
The first value may not exceed the last value in EBCDIC
collating sequence or an error is flagged.
Single unpaired values may be specified for a range
simply as keyword=first and in this case the colon ':' is
omitted.
Patterns may also be used with any of the above keywords
except OPDAND and OPDOR and include one or more Wild Card
characters to match the respective OPD data field.
A pattern contains one or more special Wild Card
characters as follows:
Wild
Card Matches
---- ------------------------------------------------
* 0 or more characters
% 1 Non-blank character
+ 1 Numeric character (0-9)
_ 1 Alphabetic character or _ (a-z, A-Z, _)
. 1 National character (@, #, $)
! 1 Special character (not a-z, A-Z, 0-9, @, #, $)
? A blank string if used by itself
? 1 Blank character (X'40') if used with any other
characters
Ranges may not be wild carded. If wild carded the range
value becomes a pattern instead and is processed as such.
See Section 25 "Ranges and Patterns" in the ADOCRMFV
member or ASMRMFV source code for more details on usage
of ranges and patterns.
-OPDPROCNAME= selects OPD tables by 1-8 character z/OS JCL
Procedure Name. Proc Name characters are validated to
those allowed by JCL syntax. Both ranges and patterns
with wild cards may be specified. Up to 16 ranges and 16
patterns are supported. The default is OPDPROCNAME=ALL.
NOTE: There is only ONE OSDPROC field per OPD table. If
the OPDPROCNAME= value does not match, then the ENTIRE
OPD table with all entries is excluded. Use OPDPROCNAME=
with care and discretion and only if the OSDPROC contents
are well understood. Almost always OSDPROC is simply
'OMVS'.
-OPDJOBNAME= selects OPD entries by 1-8 character z/OS
Job Name. Job Name characters are validated to those
allowed by JCL syntax. Both ranges and patterns with
wild cards may be specified. Up to 32 ranges and 32
patterns are supported. The default is OPDJOBNAME=ALL.
Job Names must be 1-8 characters in length and may
include any characters A-Z, #, $, or @. Numeric digits
(0-9) may be used only after the first character.
-Examples for OPDJOBNAME= :
OPDJN=PROD1234:PROD5678 selects only address spaces with
a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a
range. Note use of the keyword alias OPDJN for coding
convenience.
OPDJOBNAME=.* is a pattern that selects only address
spaces with a Job Name that begins with a national
character.
OPDJOBNAME=*++ is a pattern that selects only address
spaces with a Job Name that ends with 2 numeric digits.
OPDJOBNAME=ABC:ABC88888 is a range that selects only
address spaces with a Job Name that is GE 'ABC ' and
LE 'ABC88888'.
-OPDUSERNAME= selects OPD entries by 1-8 character z/OS
User Name. User Name characters are validated to those
allowed by JCL syntax. Both ranges and patterns with
wild cards may be specified. Up to 32 ranges and 32
patterns are supported. The default is OPDUSERNAME=ALL.
User Ids must be 1-8 characters in length (1-7 characters
for TSO Ids) and may include any characters A-Z, #, $, or
@. Numeric digits (0-9) may be used only after the first
character.
-Examples for OPDUSERNAME= :
OPDUSERNAME=JOE8888 selects only address spaces with a
login User Name of 'JOE8888'.
OPDUSERNAME=JOE:JOE8888 selects only address spaces with
a login User Name that is GE 'JOE' and LE 'JOE8888'.
OPDUSERNAME=.* selects only address spaces with a login
User Name that begins with a national character (@, #,
$).
OPDUSERNAME=*++ selects only address spaces with a login
User Name that ends with 2 numeric digits (00-99).
-OPDAND (default) indicates that selection results from
the two different OPD filter keywords are logically
ANDed.
-OPDOR indicates that selection results from the two
different OPD filter keywords are logically ORed.
Example 1 with OPDAND in effect:
OPDJOBNAME=ABC* OPDUSERNAME=SAM*
only selects Address Spaces in the RMF Monitor III
OPD table that have a Job Name starting with 'ABC'
AND a User Name beginning with 'SAM'.
Otherwise the Address Space is filtered and will NOT
appear in the result MXG PDB.
The logical AND results in more restrictive
filtering because 2 conditions must be met for an
OPD entry to be selected.
Example 2 with OPDOR in effect:
OPDJOBNAME=ABC* OPDUSERNAME=SAM*
selects Address Spaces in the RMF Monitor III OPD table
that have a Job Name starting with 'ABC' OR a User Name
beginning with 'SAM'.
If the Address Space does not match either selection it
is filtered and will not appear in the result MXG PDB.
The logical OR results in less restrictive filtering than
Example 1 above because any of the 2 conditions results
in data selection of an OPD entry.
-The JOBNAME= (alias JOB=) keyword for multi-table
selection is expanded to include job names from the OPD
table as well as the ASI and CSR tables. This is a
convenience feature to avoid having to code the Job Name
parameter three times when the same job names from all
three tables are of interest.
-The ASI, CSR, and OPD tables must all be selected for the
JOBNAME= multi-table selection keyword to function
completely. Otherwise only entries from selected tables
are filtered.
Note that most RMF III tables do not contain common
character data fields, but in this case the ASI, CSR, and
OPD tables all do contain a Job Name.
JOBNAME= Examples:
JOBNAME=ABC88888 selects only address spaces with a Job
Name of 'ABC88888' in either ASI, CSR, or OPD tables and
is equivalent to coding:
ASIJOBNAME=ABC88888
CSRJOBNAME=ABC88888
OPDJOBNAME=ABC88888
JOBNAME=ABC:ABC88888 selects only address spaces with a
Job Name that is GE 'ABC' and LE 'ABC88888' in either
ASI, CSR, or OPD tables and is equivalent to coding:
ASIJOBNAME=ABC:ABC88888
CSRJOBNAME=ABC:ABC88888
OPDJOBNAME=ABC:ABC88888
JOBNAME=.* selects only address spaces with a Job Name
that begins with a national character in either ASI, CSR,
or OPD tables and id equivalent to coding:
CSRJOBNAME=.*
OPDJOBNAME=.*
-Some RMFV001I Execution Environment messages have been
reformatted to include DFSMS/MVS version, CPC Name, LPAR
Name (if not a VM Guest), or VM Userid (if a VM Guest).
TIOT statistics are now grouped on the same message line.
-The Creation date was not valid when non-VSAM data set
was incorrectly provided as a RMF III data set. CRDATE
is removed from the RMFV008I message in this case.
-The MXG00 record version is raised to x'07' from x'06'.
New fields added to the MXG00 record are:
IPL timestamp in LOCAL and GMT time
IPL volume serial
TIOT size in K and bytes
TIOT maximum and used entries
CPC Name, LPAR Name, and VM UserId
DFSMS/MVS level
-Several documentation Sections are updated to support
the above changes:
Section 5 "Input Data Selection Parameters"
Section 12 "Messages"
Section 13 "Filtered Records"
Section 25 "Ranges and Patterns"
Section 30 "Summary"
-VMACRMFV was updated to add new variables to ZRBASM:
ASMDFLVL='EXECUTION*DFSMS/MVS*LEVEL'
ASMOPNRX='MAXIMUM*OPDPROCNAME*RANGES'
ASMOPNPX='MAXIMUM*OPDPROCNAME*PATTERNS'
ASMOJNRX='MAXIMUM*OPDJOBNAME*RANGES'
ASMOJNPX='MAXIMUM*OPDJOBNAME*PATTERNS'
ASMOUNRX='MAXIMUM*OPDUSERNAME*RANGES'
ASMOUNPX='MAXIMUM*OPDUSERNAME*PATTERNS'
ASMOJNRS='SIZE*OPDJOBNAME*RANGE*TABLE'
ASMOJNPS='SIZE*OPDJOBNAME*PATTERN*TABLE'
ASMOPNRS='SIZE*OPDPROCNAME*RANGE*TABLE'
ASMOPNPS='SIZE*OPDPROCNAME*PATTERN*TABLE'
ASMSPGAO='SPG*MULTI*FILTER*LOGIC*I/O?'
ASMSINDD='SYSIN/SYSINA*DCB*DDNAME'
ASMVFREE='FREE=CLOSE*OPTION?'
ASMSINMG='SYSIN*MEMBER*OR*GENERATION'
ASMOUNRS='SIZE*OPDUSERNAME*RANGE*TABLE'
ASMOUNPS='SIZE*OPDUSERNAME*PATTERN*TABLE'
ASMIPLTL='LAST IPL*LOCAL*TIME'
ASMIPLTG='LAST IPL*GMT*TIME'
ASMTIOTB='MAXIMUM*TIOT SIZE*BYTES'
ASMTIOTK='MAXIMUM*TIOT SIZE*IN K'
ASMTIOTX='MAXIMUM*TIOT*ENTRIES'
ASMTIOTU='CURRENT*TIOT*ENTRIES*IN USE'
ASMCPCNM='CPC*NAME'
ASMLPARN='LPAR*NAME'
ASMVMUID='VM*USERID'
ASMIPLVL='IPL*VOLUME*SERIAL*NUMBER'
Change 35.053 SYSOTHER checking is enhanced. Test for CPUTM NE 0 added
VMXGRMFI to SYSOTHER detection, since if the CPUTM is 0 it cannot
Feb 28, 2017 impact totals, but workload names and descriptions are
identified so you can find the culprit, since nothing
should ever fall thru to Service Class SYSOTHER.
Change 35.052 DATETIME syntax was revised per change 35.022, although
TRNDVMXA the new VMXGSUM correctly supported the old syntax with
Feb 28, 2017 no error.
Change 35.051 Support for Liberty 17.0.0.1 SMF 120 Subtype 12 COMPAT
VMAC120 enhancements, adds these variables to TYP12012 dataset:
Feb 28, 2017 SM120CDO='REFERENCE*TYPE' MG120CD format decodes:
1='1:READER'
2='2:PROCESSOR'
3='3:WRITER'
4='4:CHECKPOINT'
5='5:BATCHLET'
6='6:PARTITION_MAPPER'
7='7:PARTITION_REDUCER'
8='8:PARTITION_COLLECTOR'
9='9:PARTITION_ANALYZER'
10='10:DECIDER'
SM120CDU='PHYSICAL*CPU*ADJUSTMENT*RCTPCPUA'
SM120SU_SEC='CPU*RATE*ADJUSTMENT*RMCTADJC'
SM120CDW='REPOSITORY*TYPE*JPA* OR MEM'
SM120CDX='JOB*STORE*REF*ID'
SM120CDY='SM120CDY*FLAGS'
Next six variables are only valid in step end record
SM120CDZ='STEP*START*LIMIT'
SM120CEA='CHUNK*STEP*CHECKPOINT*POLICY' decodes:
0='0:ITEM'
1='1:CUSTOM'
SM120CEB='CHUNK*STEP*ITEM*COUNT'
SM120CEC='CHUNK*STEP*TIME*LIMIT'
SM120CED='CHUNK*STEP*SKIP*LIMIT'
SM120CEE='CHUNK*STEP*RETRY*LIMIT'
Change 35.050 PDB.ASUMCELP REQUIRES SMF 70s from ALL SYSTEMs to be read
VMXG70PR to correctly populate all variables. Each SMF 70 record
Feb 27, 2017 contains a "This System" segment that populates TYPE70,
and an "LPAR Segment" for each LPAR, for TYPE70PR, so the
LPAR data can be reported & summarized from a SMF 70 from
only one system, but then all the "This System" variables
are wrong, notably, SMF70LAC, the IBM 4HR AVG MSU, which
will contain ONLY the MSU from the one "This System".
This change compares TYPE70 and TYPE70PR to detect if
there are missing TYPE70 or TYPE70PR data, printing a
a PROC FREQ with missing systems identified, and printing
a log message that SMF70LAC will be wrong.
Change 35.049 Support for MAINVIEW FOR IMS 5.3 a/k/a IMF or CIMS which
VMACCIMS COMPATIBLY added these variables to the CIMSTRAN dataset:
Mar 12, 2017 TRNMSYS ='MQ*REMOTE*SYSTEM*NAME'
TRNDSYS ='DB2*REMOTE*SYSTEM*NAME'
TRNFLTRD='SOME*CALLS*NOT TRACED*FILTERS?'
TRNPRELD='PGM*WAS*PRELOADED'
TRNINFL ='TRN WAS*CAUGHT*INFLIGHT'
Was reserved change number until Sep 23, 2018
Change 35.048 Support for IWS Version 9.3, a/k/a TWS and was OPC, which
VMACOPC replaces subtype 23 with new subtype 66 with the original
Feb 24, 2017 variables plus these four new variables
TRLDURS23='DURATION'
TRLOID23 ='OPERATION*ID'
TRLOLDST23='OLD*STATUS'
TRLREADY23='START*DATETIME*WAIT*OPR'
The new subtype 66 record is output in the OPC23 dataset
so your reports won't have to be changed.
Thanks to Teuvo Virsu, TIETO,
Change 35.047 Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS.
VMAC102
Feb 24, 2017
Change 35.046 Support for IFCID 125 Truncated Package Collection and
FORMATS Package Name fields, and new variables for Runtime
VMAC102 Adaptive Index in T102S125 dataset:
Feb 20, 2017 QW0125TI='INDEX*PROBING*RIDS IN*INDEX'
QW0125QI='INDEX*PROBING*RIDS*IN*KEYRANGE'
QW0125_TRSN='REASON*LEG*WAS*TERMINATED?'
QW0125_PRSN='REASON*LEG*NOT*PROBED?'
QW0125_ORSN='REASON*LEG*WAS*REORDERED?'
QW0125_FRSN='REASON*LEG*WAS*MARKED FULL?'
Change 35.045 ANALDB2R variable QWHSRELN format expanded from 3.1 to
ANALDB2R 4.1 to print full 10.1 Release value in reports.
Feb 20, 2017
Change 35.044 -The new ZRBCPU SMT Multithreading variables were always
VMACRMFV missing due to an invalid MXG test for LENLEFT.
Feb 20, 2017 -New variables found in the Dec 2016 Programmers Guide:
Dataset ZRBCPU:
CPC_CECNAME='CPC*CEC*NAME'
LPARHWGR='LPAR*HW*GROUP*NAME'
Dataset ZRBLCP:
LCPUHWLW='HW*GROUP*CAP*LIMIT'
LPARHWGR='LPAR*HW*GROUP*NAME'
-APAR OA58688 adds these new fields.
Thanks to MP Welch, Bank of America, USA.
Change 35.043 SMF74NID, the Network ID, contains 26 EBCDIC and 2 hex
VMAC74 bytes that don't "print pretty". Variable SMF74NIDTWO
Feb 20, 2017 keeps those two bytes, formatted $HEX4. for printing.
Thanks to Pierre Pascal Joulin, Societe Generale, FRANCE.
Change 35.042 Sample code that creates charts of resource group CPU
GRAFCAPS usage and capping.
Feb 17, 2017
Change 35.041 DCOLLECT format MGDCOSG adds new 6='6:COPYPOOL' value to
FORMATS map that value in variable DSGFTYPE.
Feb 17, 2017
Thanks to J. Alan Gray, CareFirstBlueCrossBlue Shield, USA.
Thanks to Stanley M. Helms, CareFirstBlueCrossBlue Shield, USA.
Change 35.040A IBM APAR OA51325 corrects invalid SMF 15 record missing
VMAC1415 the UCB segment causing VOLSER to be truncated to two
Feb 17, 2017 characters. No code change to support the corrections.
Change 35.040 Support for Velocity Software ZWRITE file z/VM MONWRITE
VMACVMXA records which have a new BEGINMTR value for each (hour)
VMXGINIT period, which caused the first interval of each (hour) to
Feb 15, 2017 be lost, because normal MONWRITE records have a single
BEGINMTR value for each file. But the ZWRITE records are
contiguous in spite of changed BEGINMTR, so this support
is enabled with %LET MXGZWRITE=YES; in SYSIN which
will set BEGINMTR only from the first instance so only
the very first interval is lost per day.
// EXEC MXGSASV9
//VMINPUT DD DSN=YOUR.ZWRITE.MONWRITE.DATA,DISP=SHR
//PDB DD DSN=YOUR.ZWRITE.PDB,DISP=OLD
//SYSIN DD *
%LET MXGZWRITE=YES;
%INCLUDE SOURCLIB(VMACVMXA,IMACKEEP);
_TESTVM /*READS VMINPUT */
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.039 MQMQUEUE variable WQQTYPE is mapped by MG116QT format
FORMATS VALUE MG116QT
VMAC116 1='1:LOCAL'
Feb 15, 2017 2='2:MODEL'
3='3:ALIAS'
6='6:REMOTE'
7='7:CLUSTER'
-GMTOFF116 calculation revised correcting occasional
missing values in WQCLOSTI, WQOPENTI, and WQTTTIME.
(WQCLOSTI can be validly missing).
-APAR PI70580 corrects invalid WQBASENA variable values,
which seem to occur in every second segment in each
SMF record, but other segment's values are valid.
Thanks to Raymond Smith, Optum TECH, USA.
Thanks to Pietro Rosella, Canadian National Rails, CANADA
Change 35.038 MXG 34.04 added PROC DELETE DATA=:CIC after PDB.CICINTRV
CICINTRV had been created, intending to delete ONLY CICS Stats
VMXGCICI datasets to free up //WORK space for subsequent use, but
Feb 14, 2017 if CICINTRV was intentionally left in //WORK, it was then
unintentionally deleted by that colon modifier, and ITRM
expected it to be left in WORK as it had been previously.
Since no one had actually asked for this cleanup, it has
been removed from VMXGCIC. But, added at the bottom of
the CICINTRV member, inside a comment block, is the code
to delete all of those CICS Stats, if you do wish to.
Thanks to Don Barnard, North Carolina State Government, USA.
Thanks to Chris Weston, SAS Institute ITRM, USA.
Change 35.037 ASUMDB2P expected variables QPACDBRM/QPACPACK would be
ANALDB2R populated, but those bits were removed in DB2 V10, so now
ASUMDB2P PACKTYPE is blank.
Feb 14, 2017 -ANALD2R was not correctly rolling up the control break
totals in the Accounting SHORT report.
Change 35.036 VMXGSUM will now tell you with an MXGNOTE when it cannot
VMXGSUM use CLASS NWAY and why it cannot. There are two cases:
Feb 11, 2017 - Use of DESCENDING in the SUMBY
- same dataset name for input and output and no OUTCODE
specified
It will also now display the final setting of SUMBYCLASS.
Thanks to Tim Hare, Southwood Shared Resource Center, USA.
====== Changes thru 35.035 are in this MXG 35.02 dated Feb 10, 2017=====
Change 35.035 Protection for Invalid TPX Subtype 7 record with Segment
VMACTPX TPX07LEN=93 but only 44 bytes remain in the record. MXG
Feb 10, 2017 silently deleted the record, because of prior invalid 07x
Feb 14, 2017 causing zero obs in TPXAPLON Logon dataset. The first 44
are now INPUT, and the remainder conditionally input.
-Feb 14: Correction for undocumented 8 byte insert
in '06' and a blank in TPXSNAME.
-Feb 14: Each pair of subtype 01 TPXSTART records have the
same SMF time, but the second record is a continuation of
the first record, which is not supportable; a problem
report will be opened with TPX Support.
-TPX PTFS R088919 and R085818 correct some errors, while
CA Fix TR95030 corrects the bad subtype 1 records which
turned out to subtype 2 records with wrong subtype.
Thanks to Scott Wiig, USBank, USA.
Thanks to Paul Volpi, UHC, USA.
Change 35.034 Support for the BBMQ large segment record structure that
VMACBBMQ are created by the BMC BBM9MD73 utility program that
Feb 10, 2017 extracts the records from the history file for TYPEBBMQ
to then process. Both old and new format records are
supported with this change and there were no changes to
the MXG datasets.
Change 35.033 Logic to determine the begin/end of month was robusted
VMXGALOC and non-zero length MNTHKEEP will always display the
Feb 9, 2017 MONTH Libname value.
Change 35.032 Documentation Only. DCOLLECT records can contain the JOB
VMACDCOL and STEP and the TIME of the Creating JOB for DISP=NEW
Feb 9, 2017 datasets, but the EATTR option must be specified either
in the DATACLASS definition or with a DD statement.
Thanks to Paul Newton, IBM RDP Dallas, USA.
Change 35.031 Variable S42DSIOS='RW TO*METRO*MIRROR*SECONDARY' is added
VMACDB2 to dataset TYPE42DS, having been overlooked.
Feb 9, 2017
Thanks to Stephen Hoar, Lloyds Banking, ENGLAND
Change 35.030 DB2 statistics dataset DB2STAT4 QW0225_LMWRITE_REAL and
VMACDB2 _QW0225_LMCTYRL_REAL were incorrectly very large due to
Feb 7, 2017 a 4-byte misalignment.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.029 RACF SMF70DTP/RACFTYPE=6 segment was increased in length
VMAC80A from 124 to 136 but had not been protected for a change.
Feb 7, 2017 Three additional keyword variables ADDLKEY1-ADDLKEY3
are added to TYPE8010 and TYPE8013 datasets.
Thanks to Coen Wessels, GTS Infrastructure, SWITZERLAND.
Change 35.028 Support for RMF III dataset ZRBENC new "long name" fields
ASMRMFV that were added by z/OS 2.1 but not captured by ASMRMFV.
VMACRMFV Variables EDEPCKG EDEPROC EDEUSER EDETRXN ECEACCT were
Feb 6, 2017 increased in length and these new variables are kept:
EDESCHEDENV ='SCHEDULING*ENVIRONMENT*NAME'
EDESCHEDENVLN ='S E NAME LENGTH'
EDESUBSYSCOLLECT ='SUBSYSTEM*COLLECTION*NAME'
EDEPCKGLN ='PACKAGE*NAME*LENGTH'
EDEPROCLN ='PROCEDURE*NAME*LENGTH'
EDECLIENTIPADDR ='CLIENT*IP*ADDRESS'
EDECLIENTIPADDRLN ='CLIENT*IP*ADDRESS*LENGTH'
EDEUSERLN ='CLIENT*USERID*LENGTH'
EDETRXNLN ='CLIENT*TRANSACTION*NAME*LENGTH'
EDECLIENTWRKSTATION ='CLIENT*WORKSTATION'
EDECLIENTWRKSTALN ='CLIENT*WORKSTATION*LENGTH'
EDEACCTLN ='CLIENT*ACCOUNT*LENGTH'
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.027 Support for DB2 NETEZZA DB2ACCT Q8AC Accumulated fields:
IMACDBNZ Q8ACINSC='INSERT*STATEMENTS*SENT TO IDAA*FROM DB2'
Feb 6, 2017 Q8ACUPDC='UPDATE*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACDELC='DELETE*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACDRPC='DROP*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACCRTC='CREATE*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACCMTC='COMMIT*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACRBKC='ROLLBACK*STATEMENTS*SEND TO IDAA* FROM DB2'
Q8ACOPNC='OPEN*STATEMENTS*SEND TO IDAA*FROM DB2'
Q8ACROWI='ROWS*INSERTED*TO IDAA*BY DB2'
Q8ACROWU='ROWS*UPDATED*ON IDAA*BY DB2'
Q8ACROWD='ROWS*DELETED*ON IDAA*BY DB2'
Q8ACROWC='ROWS*RETURNED*BY IDAA*TO DB2'
These variables are output in DB2ACCT, but they appear
to be defective, as they are supposed to be ACCUMULATED
but the 2012 and 2013 test data I have has breaks in the
expected monotonic increase, so if you are interested in
these fields, please send current SMF 101 data so I can
investigate if the accumulation is now valid.
Change 35.026 If MXG detects Service Class Name of SYSOTHER, error msgs
UTILRMFI are printed when SMF 72 records are processed. SYSOTHER
Feb 1, 2017 should never happen; it is the fall thru service class
when WLM can't classify work and runs at the lowest DPRTY
in MTTW mode, and thus should NOT ever happen! Now, when
UTILRMFI is run to examine the problem, it will also read
the PDB.SMFINTRV or PDB.TYPE30_4 dataset to find what
tasks were classified into SYSOTHER, reporting JOB name,
READTIME, JESNR, and SRVCLASS and RPTCLASS. If there are
type 30 records they will be reported but there may not
be any, if no tasks actually went to the service classes,
or the workload is one where there is no type 30 record
(e.g., DDF). All workloads in your WLM classification
rules should have a default service class SPECIFIED:
-Unclassified work will default to one of two places
- Started Tasks default to SYSSTC
- All other work defaults to SYSOTHER
Neither is a good choice. SYSSTC runs at very high DP
and SYSOTHER runs at very LOW DP. While very low may be
appropriate for workloads you do not know, very high is
almost certainly not.
-Reports 1 thru 3 already exist.
-Report 4 is added to give you the job names, read times
jes numbers, service and report class where the service
class is SYSOTHER, from 30_4 and SMFINTRV.
-Report 5 is added to show you any DB2ACCT records that
may have landed in SYSOTHER as they may not be in a type
30 record.
-Report 6 is added to show you all tasks falling into
SYSSTC, from 30_4, SMFINTRV and 30_6.
-Report 7 is added as a table of CPU consumption by
service class and system, from TYPE72GO.
-Report 8 is added as a table of CPU consumption
by report class and system from TYPE72GO.
Change 35.025 Using the _VMINPUT macro to read VB z/VM MONWRITE data
VMACVMXA incorrectly set the length of VMDUSER to only one byte.
Feb 1, 2017
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 35.024 SMF 120 Subtype 9 variables SM1209EV/EW/SM1209FI are not
VMAC120 kept. In TYP1209U detail dataset, they are output either
Feb 3, 2017 in new variables SM1209xxEJBDET or SM1209xxWEBDET, and in
datasets TYP1209R and TYP1209N they are summed and output
in SM1209xxEJB and SM1209xxWIB variables.
The TIME format was removed from the EW count variables.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.023 MXG 35.01. If UTILEXCL executed with //PDB DD DISP=OLD,
UTILEXCL only the NEW dictionary records read from SMF are used
Jan 29, 2017 to create the IMACEXCL, and old dictionary records are
lost; only the new records are output in PDB.CICSDICT.
(The step DATA _LCICDIC; SET _WCICDIC; to add the LABEL
was changed to SET _LCICDIC to correct this error.)
Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA
Change 35.022 ANCIENT syntax of DATETIME in SUMBY in user tailored
VMXGSUM invocation of VMXGSUM (pre MXG Version 21 example!) can
Jan 29, 2017 cause VMXGSUM, which is used EXTENSIVELY internally in
MANY MXG members, to fail, sometimes with only a message
WARNING: VARIABLE QWACBSC ALREADY EXISTS ON WORK.MXGSUM3
or it can ABEND with ERROR FUNCTION COMPBL TOO FEW ARGS.
Only three sites reported the error with MXG 35.01/34.34.
Primary exposure was this syntax,
SUMBY= . . .DATETIME . . . ,
ID= . . . QWACBSC . . . ,
DATETIME= QWACBSC,
which caused the output dataset variables QWACBSC and
DATETIME have missing values.
The correct syntax replaces DATETIME in the SUMBY= :
with the DATETIME= variable, and removes the DATETIME=
variable from the ID= argument,
This error was exposed in MXG 34.05 in Change 34.151 for
the CLASSNWAY update that is also corrected. But, even
though unlikely, this change detects the old syntax with
DATETIME in SUMBY= argument, changes to correct syntax,
and tells you what was done for you in a log note.
If you had DATETIME in the SUMBY= list and also did NOT
explicitly use the DROPDT=NO option, then DATETIME
variable is kept in the output dataset.
-Unrelated, this change adds the FLORCEIL parameter to
VMXGSUM so you can create interval start or end times as
you can do in VMXGDUR. Setting FLORCEIL=CDIL sets the END
time or FLORCEIL=FLOOR sets the START time, and the label
indicates START or END.
-Note: this internal MXG Change could be INCOMPATIBLE with
programs that worked perfectly previously; send your code
VMXGSUM invocation and we will update your code.
Thanks to Paul Volpi, UHC, USA.
Change 35.021 MXG 35.01, TYPE78PA variables R782LSMOxx and R782GFMOxxx
VMAC78 and R782GFFRxxx are incorrect; R782LSMOMIN should have
Jan 27, 2017 been INPUT before R782LSMONTME, but statement was lost
causing R782LSMOMIM UNINIT message.
Thanks to Paul Naddio, FISERV, USA.
Change 35.020 MXG 35.01. Spurious MXGWARN: VMXGSUM BACKLEVEL MXG 3434
VMXGSUM note has no impact; the VMXGDUM in 35.01 is correct, but
Jan 25, 2017 the VMXGVERS call was not updated with '35.01' text.
Change 35.019 -Support for changed SYTCPU with SYTNLPS=1 SEGLEN=48
VMACXAM that caused INVALID SEGMENT record, XAMSYT dataset.
Jan 26, 2017 -Support for new SYTLC3 segment in XAMSYS records
Mar 2, 2017 was added on March 2, adding these new variables:
CALLCKID='CALL*CHECKID'
INDEX ='TO MATCH*HISTORY DATA'
SECONDS ='SECONDS'
CALXSCNT='TOTAL*SPIN*TIMES*EXCLUSIVE'
CALXTIME='TOTAL*SPIN*TIME'
CALSSCNT='SPIN*TIMES*SHARED'
CALSTIME='SPIN*TIME*SHARED*MODE'
CALCADSH='CAD*INSTRUCTIONS*OBTAIN*LOCK'
CALCADEX='CAD*INSTRUCT*OBTAIN*EXCL LOCK'
-Support for new HSTME2 segment in XAMTCP was added
on March 2, changing only the length of DESCR to
60 bytes.
Thanks to Patricia Hansen, ADP, USA.
Change 35.018 An extraneous character in the SU_SEC format raised a
GRAFWRKX WARNING but did not cause an error, but ZIPTM, IFATM, and
Jan 26, 2017 ZIETM were not being properly summed, causing the ZIP ZAP
and ZIE graphs to be suppressed.
-ODS PROCLABEL statements added to make the index 'pretty'
when creating HTML or PDF output.
Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.
Change 35.017 New DB2 ZPARMs are added to T102S106 Dataset:
VMAC102 QWP4MNSU='MATERIALIZE*NODET*SQLTUDF?'
Jan 25, 2017 QWP4DSINUN='DISALLOW*SELINTO*UNION?'
QWP4MTAD='MOVE*TO*ARCHIVE*DEFAULT'
Thanks to Lai Fai Wong, Bank of America, USA.
Change 35.016 DB2STATS dataset, these seven storage variables
VMACDB2 QISTWSTG QISTDGTTSTG QISTDGTTCTO QISTDGTTMXU
Jan 24, 2017 QISTWFSTG QISTWFCTO QISTWFMXU
were multiplied by 4096 (page size) instead of by 1024
to convert KB to bytes for MGBYTES. format.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 35.015 Support for SMF 117 written by GTZ (conflicts with 117
VMAC117 from Message Broker), now GTZ record is ID=125.
Jan 20, 2017 -If you use TYPE117, it will delete any GTZ records and
tell you that they were NOT Message Broker records.
-To process the 117s from GTZ, use this in //SYSIN DD
until you have the APAR that writes them as 125's:
%LET MACFILE=
%QUOTE(IF ID+117 THEN DO;
INPUT @15+OFFSMF SM117SSI $EBCDIC4. @;
IF SM117SSI='GTZ ' THEN ID=125;
END;
);
and tell MXG to process both 117 and 125 records.
====== Changes thru 35.014 are in this MXG 35.01 dated Jan 20, 2017=====
Change 35.014 A variable with DATETIME embedded in the name caused an
VMXGSUM branch in the code building the SUMBY string and caused
Jan 19, 2017 the SORT to fail with a variable not found.
Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA
Change 35.013 If you used AUTOALOC=YES with RUNMNTH=MTD on the second
BLDSMPDB day of the month, the previous month may have been
Jan 18, 2017 deleted.
Change 35.012 Old protection for APAR OA24074 caused ZERO DIVIDE ID=70
VMAC7072 if CPUUPTM and CPUPATTM were identical, now protected.
Jan 18, 2017
Thanks to Job Varkey, Verisk Analytics, USA.
Thanks to Cesar V. Cocco, Verisk Analytics, USA.
Change 35.011 For local time zones with +GMT, variable GMT115TM was
VMAC115 one hour too large, fortunately impacting only variables
Jan 17, 2017 QJSTIOMAXIOT1-4 and QJSTIOMAXSUST1-4 in MQMLOG dataset.
Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA
Change 35.010 OSEM User SMF INPUT STATEMENT EXCEEDED, invalid record
VMACOSEM with length of last segment not provided if there was
Jan 26, 2017 more than one segment. The year 2000 vendor DSECT does
Apr 3, 2018 show a '00'x terminates the record, so that is now used
to detect the length of the last segment.
Code sent in Mar, 2018 but VMACOSEM updated in 36.04.
Thanks to Nilton D Junior, IBM, BRAZIL.
Change 35.009 Support for APAR OA48913 metrics for 2GB Memory Frames.
VMAC71 -New variables in TYPE 71:
Jan 13, 2017 SMF71GAA='AVG 2GB FRAMES*IN LFA*NOT IN-USE'
SMF71GAM='MIN 2GB FRAMES*IN LFA*NOT IN-USE'
SMF71GAX='MAX 2GB FRAMES*IN LFA*NOT IN-USE'
SMF71GFA='AVG TOTAL*2GB FRAMES*CAN BE USED'
SMF71GFM='MIN TOTAL*2GB FRAMES*CAN BE USED'
SMF71GFX='MAX TOTAL*2GB FRAMES*CAN BE USED'
SMF71GOA='AVG FIXED 2GB*OBJECTS*ALLOCATED'
SMF71GOM='MIN FIXED 2GB*OBJECTS*ALLOCATED'
SMF71GOX='MAX FIXED 2GB*OBJECTS*ALLOCATED'
SMF71GRA='AVG 2GB PAGES*FIXED*IN CSTORE'
SMF71GRM='MIN 2GB PAGES*FIXED*IN CSTORE'
SMF71GRX='MAX 2GB PAGES*FIXED*IN CSTORE'
SMF71GUA='AVG 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
SMF71GUH='HWM*2GB FRAMES*USED'
SMF71GUM='MIN 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
SMF71GUX='MAX 2GB FRAMES*IN LFA*IN-USE*BY FIXED MEMOBJ'
-New variables in TYPE78PA:
R782GFMOMIN ='MIN FIXED*MEMOBJ*BACKED IN*2GB FRAMES'
R782GFMONTME='TIME STAMP*OF MIN*MEMOBJ*BACKED*IN 2GB'
R782GFMOMAX ='MAX FIXED*MEMOBJ*BACKED IN*2GB FRAMES'
R782GFMOXTME='TIME STAMP*OF MAX*MEMOBJ*BACKED*IN 2GB'
R782GFMOAVG ='AVG FIXED*MEMOBJ*BACKED IN*2GB FRAMES'
R782GFFRMIN ='MIN 2GB PAGES*FIXED*IN CSTORE'
R782GFFRNTME='TIME STAMP*OF MIN*PAGES*FIXED*IN CSTORE'
R782GFFRMAX ='MAX 2GB PAGES*FIXED*IN CSTORE'
R782GFFRXTME='TIME STAMP*OF MAX*PAGES*FIXED*IN CSTORE'
R782GFFRAVG ='AVG 2GB PAGES*FIXED*IN CSTORE'
Change 35.008 TYPE42 variable S42CSID, the SSID is now formatted HEX4.
VMAC42 as are the other SSID variables in TYPE42 datasets.
Jan 12, 2017
Thanks to Michael Friske, FMR, USA.
Change 35.007 Liberty SMF 120 subtype 12 TYP12012 dataset variables
VMAC120 SM120CCC and SM120CCD had year 2027 plus 1 day later
Jan 12, 2017 because MXG added the DEL6070 seconds between 1960-1970
TWICE. Variable SM120CCB, also on the 1970 epoch, was
correct as DEL6070 (315619200) was only added ONCE.
Thanks to Steve McKee, FMR, USA.
Change 35.006 Duplicate RMFINTRV obs were created if multiple Capacity
VMXGRMFI Group Names existed in the TYPE70PR data; MXG did not
Jan 10, 2017 select the obs with SYSTEM=SMF70STN and inadvertently
Jan 25, 2017 output duplicated records; Most values were exact dupes,
but SMF70GNM SMF70GMU TOTMEMR values were different.
-This error was introduced in MXG 34.01, Change 34.029.
-Protected archaic DURSET and DETAIL interval Jan 25.
Thanks to Joachim Sarkoschitz, DATEV, DENMARK.
Thanks to Frank Fischer, Concordia, GERMANY.
Change 35.005 RMF III dataset ZRBLCP observations were created for each
VMACRMFV LCPUADDR in the LPAR, only if the LCPU Dispatch Time was
Jan 10, 2017 non-zero, but that test is changed to output LCPUADDRs
that are ONLINE (by testing LCPUONL), so that ZRBLCP has
an observation for every ONLINE LCPU Address, to match
the RMF CPC screen data.
Thanks to MP Welch, Bank of America, USA.
Change 35.004 MXG 34.34. Debugging PROC CONTENTS statements were left
UTILEXCL that caused DATASET PDB.CICSDICT NOT FOUND errors, if the
Jan 10, 2017 //PDB DD had DISP=NEW, Lines 891, 892, and 898 need to be
deleted, but that only exposed a second error causing the
same error message; the PROC APPEND had transposed the _W
and _L tokens - Base must be _L and NEW must be _W.
Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.
Change 35.003 Cosmetic. Variables ADSRXXXX, ADSRYYYY, ADSR5ST are now
VMACEREP converted to EBCDIC..
Jan 6, 2017
Change 35.002 Another INVALID SMF RECORD Informatica POWER EXCHANGE
VMACPOEX caused STOPOVER ABEND because POEXLEN=52 but there are
Jan 6, 2017 are only 32 bytes left in the record; its missing the
last five counters for the Client POEXCLIE dataset.
Datetime variables POEXSTRX/POEXENDX are now kept.
Thanks to Scott Wiig, USBank, USA.
Change 35.001 The year end interval with STARTTIME=31DEC2016:23:55:00
VMACNMON incorrectly had ENDTIME=01JAN2016:00:00 because MXG used
Jan 4, 2017 the AAA record's DATECH value to get the year, but that
was the date of the start of the monitor. Now, the DATE
in the ZZZZ record is used.
Thanks to Florent Boulesteix, INOVANS partenaire CAAGIS, FRANCE.
LASTCHANGE: Version 35.
=========================member=CHANGE34================================
/* COPYRIGHT (C) 1984-2016 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG Version 34.34 is dated Jan 3, 2017, thru Change 34.284
MXG Newsletter SIXTY-EIGHT is dated Jan 3, 2017.
MXG Version 34.10 was dated Dec 25, 2016, thru Change 34.280
MXG Version 34.09 was dated Dec 16, 2016, thru Change 34.279
MXG Version 34.08 was dated Nov 25, 2016, thru Change 34.269
MXG Version 34.07 was dated Oct 7, 2016, thru Change 34.232
MXG Newsletter SIXTY-SEVEN was dated Oct 7, 2016.
First MXG Version 34.07 was dated Oct 5, 2016, thru Change 34.230
MXG Version 34.06 was dated Aug 18, 2016, thru Change 34.198
MXG Version 34.05 was dated Jul 25, 2016, thru Change 34.173
MXG Version 34.04 was dated Jun 23, 2016, thru Change 34.144
MXG Version 34.03 was dated May 10, 2016, thru Change 34.114
MXG Version 34.02 was dated Apr 5, 2016, thru Change 34.083
Final MXG Version 34.01 was dated Mar 21, 2016, thru Change 34.062
Third MXG Version 34.01 was dated Mar 14, 2016, thru Change 34.058
Second MXG Version 34.01 was dated Mar 14, 2016, thru Change 34.057
First MXG Version 34.01 was dated Mar 7, 2016, thru Change 34.048
ANNUAL: MXG Version 33.33 was dated Jan 18, 2016, thru Change 33.327
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 34.34 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 34.34.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest
and is updated with new notes frequently. All Newsletters are online
at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
All MXG changes are also online at http://www.mxg.com, in "Changes".
========================================================================
I. MXG Version 34.34 dated Jan 3, 2016, thru Change 34.284
This is the MXG "ANNUAL VERSION" for 2017.
Major CHANGES added in MXG 34.34, dated Jan 3, 2016 thru 34.284.
TYPEIDML 34.282 Support for IDMS Log (INCOMPAT, third record).
TYPEDB2 34.281 DB2 IDAA variable Q8STDSKU format/label corrected.
Major CHANGES added in MXG 34.10, dated Dec 25, 2016 thru 34.280.
TYPEVMXA 34.280 z/VM Linux Appl VXAPLSLM/N/P/0 deaccum corrected.
TYPEVMXA 34.280 z/VM VXBYUSR had some obs with negative values.
Major CHANGES added in MXG 34.09, dated Dec 16, 2016 thru 34.278.
CRITICAL CHANGE:
TYPE110 34.274 Support for CICS/TS 5.4 BETA 6 (INCOMPAT CICSTRAN).
ENHANCEMENTS
TYPETMD2 34.275 Support for ASG/TMON for DB2 IDAA SA and SB records.
TYPE115 34.272 Support for MQ SMF 115 Subtype 231 DSP/ADP/SSL/DNS
ANALDCO1 34.271 New ANALDCO1 provides simple DCOLLECT reports.
ASMRMFV 34.273 Internal Performance improvement for RMF III support
Major CHANGES added in MXG 34.08, dated Nov 25, 2016 thru 34.269.
CRITICAL CHANGE:
TYPE7072 34.239 SMT Corrections to TYPE70PR "OTHER SYSTEM" LPARs.
TYPETPX 34.269 Support for INCOMPATIBLE TPX PTF R085512/R085513.
CHANGES:
TYPEDB2 34.248 DB2 Netezza IDAA Q8STxxxx in new DB2NETZA dataset.
ANAL9914 34.255 z13 Topology Report typo corrected.
CICINTRV 34.254 CICS Dispatcher DSGSRBT SRB Time Kept in CICINTRV.
VMXGALOC 34.253 UPCASE removed for BASExxx path for Linux casing.
TYPE119 34.252 TYP11950 dataset only contained first KEY.
TYPEVMXA 34.249 z/VM Linux Appldata VXAPLSLM/SLN/SLP corrections.
TYPE42 34.245 SMF 42 TYPE42L1 dataset misaligned at SMF42HUA.
ANALDB2R 34.265 ANALDB2R 33.33-34.07 could require temp //PDB DD.
ENHANCEMENTS
TYPE110 34.260 Support for SMF 110 Subtype 2 STID=32 creates CICLDY.
TYPETMO2 34.257 Support for TMON/CICS Version 4.1 (COMPATIBLE)
TYPE80A 34.251 Support for TOP SECRET RDT Table decoding.
TYPERACF 34.247 Support for RACF APAR OA43999 RACF UNLOAD database.
TYPE117 34.243 Support for SMF 117 Version 2 (INCOMPATIBLE) format.
TYPEZCOS 34.241 Support for AutoSoftCapping Version V4 (COMPATIBLE).
TYPETHAL 34.261 Support for Thales Security Records with/wo subtype
IMACCADI 34.263 Support for CAA/DISPATCH type 6 change (INCOMPAT)
ASMRMFV 34.262 ASMRMFV enhancement for Parameters.
VGETJESN 34.240 Hex zeros in JCTJOBID in SMF 42 ST 27 protected.
ANAL3CPC 34.238 Example RMF III CPC data report.
TYPESTC 34.237 New variables added to STCVSM11 dataset.
Major CHANGES added in MXG 34.07, dated Oct 7, 2016 thru 34.232.
CRITICAL CHANGE:
TYPE7072 34.232 First 34.07. CRITICAL ARRAY EXCEEDED ERROR fixed.
DO NOT USE Oct 5 34.07 for TYPE 70 processing.
Major CHANGES added in MXG 34.07, dated Oct 5, 2016 thru 34.229.
ENHANCEMENTS
TYPEDB2 34.229 Support for DB2 V12. (COMPATIBLE).
TYPE70 34.228 Support for APAR OA48688, ABSOLUTE MSU LPAR CAP.
TYPE1415 34.224 Support for APAR OA50256 for TYPE1415/SMF14DSVER.
TYPE74 34.223 Support for APAR OA49415 for SuperPAV support.
TYPE78 34.223 Support for APAR OA49415 for SuperPAV support.
TYPE42 34.222 Support for APAR OA51097 for subtype 19 fields.
TYPE6156 34.219 Support for SMF Type 65 GDGCOMPL/GDCNOEXT/GDGLIMIT
TYPE98 34.216 Support for SMF 98 High Freq Thruput Stats record.
TYPEPROS 34.215 Support for PRO/SMF (previously X37) Version 7.8.
TYPE30 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE42 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE74 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE79 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE90A 34.214 Support for new subtypes 38 and 39 in SMF 90.
TYPE119 34.213 Support for SMF 119 Subtype 81 Intrusion Detection.
TYPE80A 34.206 Support for Top Secret Release R15 &R16 (INCOMPAT).
TYPECDHW 34.202 Support for Connect Direct Simultaneous Session CDHW
DB2COUNT 34.209 "DB2 is filling my SMF, how do I find out who/why?"
RMFINTRV 34.207 VMXGRMFI with INTERVAL=DATE s/b INTERVAL=DATESHIFT.
TYPE110 34.203 READTIME in all "CICS EXCLUDED" messages for DICT.
TYPE115 34.200 MQMLOG enhanced with new variables, protection added.
CORRECTIONS
TYPE29 34.221 Support for new SMF Type 29 IMS JAVA/GC validated.
TYPEBVIR 34.217 BVIR301 and BVIR302 datasets were wrong, too few obs.
ASUM4HRS 34.218 Four Hour Average analysis was incorrect initialized.
Major CHANGES added in MXG 34.06, dated Aug 18, 2016 thru 34.198.
CRITICAL ERROR CORRECTED:
TYPE78 34.196 SMF 78 ST 3 INPUT EXCEEDED if APAR O44525 installed.
MXG 33.07-MXG 34.05. Circumvention in Change text.
ENHANCEMENTS:
TYPE99 34.194 Support for SMF 99 Subtype 1 Hardware Absolute CAP.
TYPE124 34.187 Support for SMF 124 I/O Supervisor IOS (z/OS 2.2).
TYPEMVIP 34.186 Support for Mainview for IP RTIN 34x TAC9I220 dataset
TYPE110 34.183 Partial Support for CICS/TS 5.4 OPEN BETA.
TYPE80A 34.178 Support for RACF 80 TOKDANAM new values.
ASMRMFV 34.191 Enhanced RMF III data filtering reduces data volume.
ASMRMFV 34.198 RMF III Relative Time filtering, e.g, last hour.
TYPERMFV 34.192 RMF III variable GMTOFF kept in all ZRB datasets.
TYPETMO2 34.195 TMON/CICS new vars TASZIPTM/TASELGTM recalc TASCPUTM.
ERRORS CORRECTED:
TYPEHSM 34.193 Invalid HSM VSR/DSR with '62'x vs 'S' protected.
TYPE119 34.189 MXG 34.05 ONLY, INPUT EXCEEDED more than 3 Homeaddr.
TYPE74 34.181 Defective BMC CMF type 74 subtype 4 SMF74ML=0 bypass.
TYPEATF 34.180 Omegamon XE ATF times are now on local time zone.
TYPE80A 34.176 RACFTYPE=6 RACFEVNT=19 skipped segment message.
TYPEVMXA 34.175 zVM 6.3.16.1 inserted in PRCPUP, PROBABL DATA LOSS.
Major CHANGES added in MXG 34.05, dated Jul 25, 2016 thru 34.173.
ENHANCEMENTS:
TYPE120 34.170 Support for WebSphere Liberty Batch SMF 120 Subty 12.
TYPE120 34.163 Support for WAS Liberty V16.0 SMF 120 Subtype 11.
TYPE120 34.148 Support for ODM Version 8.8 SMF 120 subtype 100.
TYPE119 34.168 Support for SMF 116 Subtype 6 Home IP Address segment
TYPE87 34.166 Support for SMF Type 87 Subtype 2 ENQ/DEQ records.
TYPE117 34.157 Support for SMF 117 Integration BUS V10 INCOMPATIBLE.
TYPEIDMS 34.164 Support for IDMS Version 19 (INCOMPAT with R084146).
BUILDPDB 34.162 Support for z/OS 2.2 JES2 8-char JOBCLAS8 in BUILDPDB
BLDSMPDB 34.153 Change 33.031 missed two instanced of LOWCASE().
ERRORS CORRECTED:
TYPEVMXA 34.169 zVM HIS macros for PRCMFC PRCMFM now work correctly.
CHECKSTN 34.167 Detection/Protection of duplicate SMF70STN values.
VMXGALOC 34.160 Revised for Linux, case sensitive directory names.
TYPERMFV 34.156 INVALID DATA for ASIQSCANxxx, incorrect informat.
ASMRMFV 34.152 The RMF III DOW filter was not working.
VMXGSUM 34.151 SYSLAST is now correctly set to last output dataset.
BUILDPDB 34.147 Large SPIN.SPIN6 due to PRINTWAY records cleared.
Major CHANGES added in MXG 34.04, dated Jun 25, 2016:
ENHANCEMENTS:
VMXGSUM 34.137 New MXGSUMCLASS option can save CPU time, TEST IT!!
ASMRMFV 34.133 RMF III GMT offset feature for multiple time zones
selects data for the data center hardware time zone.
This is a new feature, so please test first.
TYPE102 34.123 Support for DB2 IFCID 365 and 376 corrections.
ANALCSQX 34.122 Concurrent MQ Apps logged on from SYSLOG CSQX msgs
TYPESYSL 34.121 Formal support of SYSLOG with all normal MXG tokens.
TYPE30 34.118 MXG created variable CPUZIPTM_CPUIFATM_INST wrong.
TYPEEDGR 34.116 RMM datasets enhanced with SYSTEM and EDGRTIME.
TYPEDCOL 34.115 DCDTIMEC Data Set Create Time not populated note.
ERRORS CORRECTED:
BLDSMPDB 34.131 ERROR: Invalid date constant " .":d, FORCEDAY= fix
ANALRANK 34.127 NOT SORTED if only one variable was examined
VMXGCNFG 34.119 CPU Loop after program ended, if //SOURCLIB DD.
Major CHANGES added in MXG 34.03, dated May 10, 2016:
ERRORS CORRECTED:
TYPEDB2 34.108 DB2 Sim Buff Pool DB2STSBP QBSP variables corrected.
ASUMCELP 34.106 z13 SMT_MODE SMT_NUM=2, NRZIPCPU finally correct.
TYPERMFV 34.100 ZRBASI ASILPGSZ, ZRBGEI many GEIxxxxx corrected.
TYPEVMXA 34.099 zVM 6.3 circumvent, 5.20 HWCLEN=384, new PRCAPMCT=11.
VMACRMFV 34.092 MXG 34.01-34.02. ZRBCPU variables CPCGRPxx wrong.
TYPEIMS 34.087 MXG 34.02, IMS 12.1, IMS 07 misalign, DLRAZAAP fixed.
MOBWRKI2 34.084 ERROR: FILE WORK.SUMSTSBP.DATA DOES NOT EXIST fixed.
ASMRMFV 34.095 Some ASMRMFV log dates off by one day, output fine.
ENHANCEMENTS:
TYPE72PD 34.111 New TYPE72PD RMF WLM POLICY DEFINITIONS dataset.
TYPE123A 34.105 Support for SMF 123 Liberty z/OS Connect EE Audit.
TYPE117 34.103 Support for IBM Integ Bus V 90005 SMF 117 INCOMPAT
READDB2 34.102 Support for IFCID=58's second dataset T102SA58.
IHDRRMFV 34.092 Support for IHDRRMFV "Header" Exit selection member.
TYPE80A 34.086 Support for TYPE8069 R_PKISERV GENCERT event SMF 80.
TYPEVMXA 34.085 Support for z/VM VXSYTEMP third section, plus more.
TYPEIMS 34.091 Support for IMS Log 16x Sign On/Sign Off log record.
TYPESAMS 34.089 Support for SAMS VANTAGE User LSPOOLPO INCOMPAT.
ANALUOW 34.110 Parameter INCODE= added for tailoring/selection.
ANAL9914 34.107 SMT Topology Report typo, reports all systems.
GRAFWRKC 34.101 Improved CPU and MSU and Group Capacity SGPLOTs.
Major CHANGES added in MXG 34.02, dated Apr 5, 2016:
ERRORS CORRECTED:
MOBSRK05 34.075 MOBILWORK SCRT/MWRT FATAL ERROR IF CLOCK CHANGE OCCURS.
YOU NEED THE UPDATED MOBWRK05 or MXG 34.02 and must run
between April 2 and 9th for the March report.
TYPEIMST 34.083 IMS56FA, ARRVTIME wrong if GMT offset NE ENDTIME GMT.
TYPE110 34.065 CICS/TS 5.3, MNSEGCL=5 TSQUEUE INPUT EXCEEDED ERROR.
TYPE7072 34.072 R723DNST NOT EQUAL TO R723RTYP message eliminated.
TYPE85 34.067 z/OS 2.2 OAM SMF 85 INPUT STATEMENT EXCEEDED fixed.
RMFINTRV 34.078 RMFINTRV 33.33 and 34.01 had errors in MSU72/MSUSOFT/
TYPESTC 34.081 Oracle/STC User SMF record GMTOFFTM "slightly" wrong.
ENHANCEMENTS:
TYPEVMXA 34.080 Support for z/VM SMT MODE, caused BROKEN REC ERROR.
TYPE102 34.072A Support for SMF 102 IFCID 58 Added segment.
TYPE73 34.068 Support for SPLIT RMF 73 records, optional _STY73EX
TYPEBBMQ 34.064 Circumvention BBMQ Short E6 records, datetimes fixed.
TYPE0203 34.074 SMF2IHASHMETH/SMF2ISIGTYPE were blank, bad bit test.
TYPE74 34.073 Dataset TYPE749 (PCIE) is enhanced with new vars.
TYPEVMXA 34.066 z/VM VXBYUSR enhanced, option forces USER 8709 ABEND.
TYPE42 34.070 I/O Connect Time S42CONNTM is calculated.
Major CHANGES added in FOURTH MXG 34.01, dated Mar 21, 2016:
TYPE7072 34.060 ITRM. VMXG70PR. "&PDB" must be "&PDBMXG" twice.
Major CHANGES added in THIRD MXG 34.01, dated Mar 14, 2016:
Critical ERROR that caused the re-date:
VMXGINIT 34.052 WPS ONLY, 1st 34.01, RUN: in VMXGINIT FAILS INIT.
Circumvent by deleting that line with the colon.
New Products Support
TYPE120 34.055 Proper Support of 120 ST 9 TYP1209R/TYP1209N datasets
ST 9 is either a REQUEST or ASYNC Event, only those
two datasets are valid, with separate variable sets.
TYPE102 34.053 BMC APPTUNE defective FIX BPU3604, INPUT EXCEEDED.
Errors Corrected:
TYPE60 34.056 TYPE 60 variable SMF60ELP misaligned.
TYPE42 34.054 Variable SMF42LAN was not converted to EBCDIC.
TYPETMO2 34.049 TMON V4.0 microsec/tod change missed 15 variables.
(None were in the important MONITASK dataset.)
Major CHANGES added in MXG 34.01, dated Mar 7, 2016:
New Products Support
TYPERMFV 34.047 Support for z/OS 2.2 RMF III data records (COMPAT).
TYPE102 34.032 Support for DB2 Trace IFCIDS 311 and 321.
TYPE29 34.221 Support for SMF 29 IMS JAVA CPU and Garbage Collect
TYPEATF 34.041 Support for ATF V531 Enhanced Summarization Phase 2.
TYPEBBMQ 34.026 Support for MVMQ PTF BPL2558, times are microseconds.
TYPENDM 34.017 Support for NDM-CDI SE Session End record.
TYPEPKSZ 34.020 Support for PK-ZIP INCOMPATIBLE increase field length
TYPEVMXA 34.005 Support for zVM HIS (SMF 113) VXPRCMFC z/13 data.
TYPEDVS 34.014 Support for Rocket Software DVS User SMF record.
TYPEDCOL 34.042 Support for FLAG4 MegaByte format size variables.
Errors Corrected:
ITRM 34.011 Possible MXG 33.33 issues with ITRM documented.
TYPE113 34.027 TYPE113 CPU Speed SM1132SP wrong on Sub-Capacity z13.
TYPECIMS 34.007 Correction for IMF 5100 incorrect values, no ABEND.
TYPESTC 34.019 Corrections/enhancements for Oracle STC SMF record.
UTILRMFI 34.006 UTILRMFI report was dropped accidentally in 33.024
VGETOBS 34.001 OPTION CHARCODE caused ERROR: CHAR OPERAND.
PDBAUDIT 34.003 FILE _TMPLIB.XTY70CP.DATA does not exist.
TYPE71 34.043 New variables SMF71CPx,SMF714Kx,SMF71PLx were wrong.
Enhancements
ANALGRCA 34.015 New analysis of Group Capacity
GRAFWRKC 34.044 New Capacity Group report of CEC resources by LPAR.
RMFINTRV 34.029 Capacity Group variables SMF70GNM/GMU added
TYPEHSM 34.002 New datetime and duration variables in HSMFSRST.
TYPE116 34.008 New Variables added to MQMACCTQ
TYPE7072 34.010 TYPE72GO MSUxxxxx variables labeled/documented.
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes.
All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M3 (9.4M3) printed
as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for
"SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled),
for SAS 9.4 Maintenance Level M3 and m2.
SAS V9.4 M3 Is RECOMMENDED, but MXG executes without error using
SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.
SAS V9.4 M2 is USABLE. SAS 9.4 M2 is at LEVEL A SAS Support
SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support
SAS V9.3 SAS 9.3 TS1M2 is USABLE. SAS 9.3 TS1M1 works.
But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
see CHANGE 29.169, IS REQUIRED:
The %MACRO compiler error is in processing %LET
statements. While only two MXG members failed
repeatedly in MXG QA tests on z/OS, there were random
%LET errors in ASCII QA tests, so ANY use of %LET
statement on ANY platform are vulnerable to this
error, as the %MACRO compiler is SAS portable code,
used on all platforms. So this is NOT just an MXG
error, but impacts ALL SAS programs.
SAS9.3 is LEVEL A support from SAS.
SAS V9.2 Was recommended, prior to 9.3, and was error-free with
MXG 26.03. SAS Hot Fix for SAS Note 37166 is required to
use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2
Decompression Infile Exit, but SAS V9.2 does execute ok.
9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.
SAS V9.1.3 must be at Service Pack 4. Additionally, on z/OS 1.10
only, 9.1.3 requires SAS Hot Fix for SN-35332.
9.1.3 is support level C by SAS Institute, Sep 30, 2013.
SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.
SAS V8.2 IS SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS
with SAS 8.2.
SAS 8.2 is Level C Support from SAS as of Dec 31, 2011.
JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used
***************************************************************
As documented in Change 27.356, for SAS V9.2 or later):
The standard SAS JCL Procedure can be used for MXG with SAS V9.2+
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
or you can continue to use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 34.07 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and
Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,
but MXG users execute MXG on MANY (ALL??) SAS platforms, including
AIX, Linux, and other 'nix' variants, on many different hardware
platforms, and since they all work we don't need to list them. If
SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.
and other errors with 3.00 or 3.01 have been corrected in the
current WPS version.
WPS Version 3.01.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was
INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to
read the SMT-format RMF records (which are written if you have zIIP
engines AND have enabled the new PROCVIEW CORE option for
Multi-Threading, even if only one thread is enabled).
The new zEDC compression hardware requires MXG 33.07 to support the
new metrics.
For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.
Availability dates for the IBM products and MXG version required for
error-free processing of that product's data records:
Product's
Availability MXG Version
Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8
MVS/ESA 4.2 Mar 29, 1991 9.9
MVS/ESA 4.2.2 Aug 15, 1991 9.9
MVS/ESA 4.3 Mar 23, 1993 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30, 1996 14.05
OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02
OS/390 2.4.0 Sep 28, 1997 15.06
OS/390 2.5.0 Feb 24, 1998 15.06
OS/390 2.6.0 Sep 24, 1998 16.04
OS/390 2.7.0 Mar 26, 1999 16.09
OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
z/OS 1.1 on 2064s Mar 30, 2001 19.01
z/OS 1.1 with correct MSU Mar 30, 2001 19.02
z/OS 1.2 Oct 31, 2001 19.04
z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05
z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.4 Tolerate Sep 27, 2002 20.03
z/OS 1.4 Support Sep 27, 2002 20.06
z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02
z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04
z/OS 1.5 Mar 31, 2004 21.21
z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10
z/OS IRD TYPE70PR Mar 11, 2004 *24.10
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10
z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10
z/OS IFA data in RMF 79s Sep 30, 2005 23.10
z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03
z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06
z/OS More than 32 LPARs Jan 30, 2006 *24.24
z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24
z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02
z/OS IRD errors corrected May 15, 2006 24.03
z/OS ASUMCEC errors corrected May 15, 2006 *24.24
z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24
z/OS zIIP Processor Support Jun 22, 2006 *24.24
z/OS Dedicated zIIP Support Mar 8, 2008 *26.01
z/OS Dedicated zAAP Support Mar 8, 2008 26.01
z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24
z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10
z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10
z/OS new z10 variables Mar 5, 2008 26.01
z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05
z/OS 1.11 Sep 2, 2009 27.08
z/OS 1.11 New 30 variables Apr 14, 2010 *28.02
z/OS 1.12 Aug 17, 2010 *28.05
z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03
z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06
z/OS 1.13 Sep 30, 2011 29.03
z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08
z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01
z/OS 2.1 - Most Records support Jul 23, 2013 30.05
z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07
z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03
z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03
z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10
z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08
z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09
REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09
z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02
z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02
z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07
z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07
z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04
z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07
z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24
z9EC CPUs - CPUTYPE '2094'x:
with 64-bit z/OS - no change required *24.24
with 32-bit z/OS only: Aug 26, 2006 24.06
z9BC CPUs - CPUTYPE '2096'x:
with 64-bit z/OS - no change required 24.01
with 32-bit z/OS only: Jul 27, 2006 *24.24
z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11
z10 HiperDispatch/Parked Time Mar 3, 2008 *26.10
z196 (INCOMPAT IF GT 64 ENG) Aug 17, 2010 28.05
zEC12 Nov 14, 2012 30.07
z13 non-SMT Mode May 27, 2014 32.05
z13 SMT Mode Change 33.217 Sep 15, 2015 *33.09
z13 SMT Mode NRZIPCPU 34.106 May 10, 2016 34.03
CICS/CTG V9 Transaction Gateway ?? ?? 2013 31.31
CICS/ESA 3.2 Jun 28, 1991 9.9
CICS/ESA 3.3 Mar 28, 1992 10.01
CICS/ESA 4.1 Oct 27, 1994 13.09
CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07
CICS-Transaction Server V1R1 Sep 10, 1996 14.07
CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06
CICS-TS V1R2 CICS/TS 1.2 Oct 27, 1997 15.06
CICS-TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04
CICS-TS V2R1 CICS/TS 2.1 Mar 15, 2001 18.11
CICS-TS V2R2 CICS/TS 2.2 Feb 9, 2002 19.19
CICSTRAN subtype 1 support only *19.19
CICSTRAN subtype 2 completed *19.08
CICS-TS V2R3 CICS?TS 2.3 Dec 19, 2003
Using UTILEXCL to create IMACEXCL: 21.04
Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04
CICS-TS V2R3 CICS/TS 2.3 Aug 13, 2004 22.04
CICS-TS V3R1 CICS/TS 3.1 Jan 18, 2005 22.22
CICS-TS for Z/OS Version 3.1 Mar 15, 2005
Using UTILEXCL to create IMACEXCL: 22.13
Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22
CICS-TS V3R2 CICS/TS 3.2 Dec 6, 2007 25.11
CICS-TS for Z/OS Version 3.2 Jun 29, 2007 25.03
CICS-TS/3.2 Compressed Records Nov 3, 2007 25.11
CICS-TS/4.1 (CICSTRAN INCOMPAT) Mar 13, 2009 27.01
CICS-TS/4.1 (STATISTICS ST=2) Sep 18, 2009 27.08
CICS-TS/4.2 CICSTRAN/STATISTICS Jun 24, 2011 29.03
CICS-TS/4.2 CICSRDS MNSEGCL=5 Jun 24, 2011 *29.05
CICS-TS/4.2 INVALID STID=116 Jan 31, 2012 *30.01
CICS-TS/5.1 (INCOMPATIBLE) Dec 14, 2012 *30.08
CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013 *30.30
CICS-TS/5.1 MNSEGCL=5 INCOMPAT Jun 17, 2013 *31.03
CICS-TS/5.2 COMPATIBLE CICSTRAN Jun 13, 2014 *31.03
CICS-TS/5.2 INCOMPAT Statistics Jun 13, 2014 *32.03
CICS-TS/5.3 INCOMPAT CICSTRAN Apr 29, 2015 33.04
CICS-TS/5.3 RESOURCE SEGCL=5 Sep 31, 2015 33.09
CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015 33.11
CICS-TS/5.3 GA date Dec 11, 2015 33.33
CICS-TS/5.3 MNSEGCL=5 INPUT ERR Mar 21, 2016 34.02
CICS-TS/5.4 OPEN BETA Aug Aug 11, 2016 34.06
CICS-TS/5.4 OPEN BETA Nov Nov 11, 2016 34.09
DB2 2.3.0 Oct 28, 1991 10.01
DB2 3.1.0 Dec 17, 1993 13.02
DB2 4.1.0 Tolerate Nov 7, 1995 13.07
DB2 4.1.0 Full support Sep 11, 1996 14.07
DB2 5.1.0 Tolerate Jun 27, 1997 14.14
DB2 5.1.0 Full support Jun 27, 1997 15.02
DB2 6.1.0 initial support Mar 15, 1999 16.09
DB2 6.1.0 all buffer pools Mar 15, 1999 18.01
DB2 6.1.0 parallel DB2 Mar 15, 1999 19.19
DB2 7.1.0 parallel DB2 Mar 31, 2001 19.19
DB2 7.1.0 corrections Mar 31, 2001 20.06
DB2 8.1 Tolerate, no packages Mar 31, 2004 20.20
DB2 8.1 New Data Packages wrong Mar 31, 2004 21.08
DB2 8.1 Support with Packages Mar 31, 2004 *23.09
DB2 8.1 with all zIIP Variables Sep 30, 2006 24.08
DB2 8.1 +PK47659 Sep 12, 2008 26.08
DB2 9.1 See Change 25.265. Dec 7, 2007 25.11
DB2 9.1 Full Support +PK/56356 Sep 12, 2008 26.08
DB2 10.1 Tolerate Oct 1, 2010 28.06
DB2 10.1 New vars + Compressed Nov 1, 2010 *28.07
DB2 10.1 Invalid Header pre APAR Jan 12, 2011 *28.28
DB2 10.1 IFCID=225 INCOMPAT Sep 23, 2011 *29.07
DB2 10.1 QWHCCV for QWHCATYP=8 Oct 3, 2011 *30.07
DB2 10.1 DBID/OBID decode Jan 21, 2013 *30.30
DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013 *31.04
(ONLY IMPACTS DB2STATS)
DB2 11.1 TOLERATE DB2 V11.1 Jun 21, 2013 30.30
DB2 11.1 DB2STATS QLST CORRECT Jun 21, 2013 31.04
DB2 11.1 SUPPORT NEW VARIABLES Jun 21, 2013 31.08
DB2 11.1 IRLM NEW SEGMENT Jun 21, 2013 32.10
DB2 12.1 COMPATIBLE Oct 5, 2016 34.07
DFSMS/MVS 1.1 Mar 13, 1993 11.11
DFSMS/MVS 1.2 Jun 24, 1994 12.02
DFSMS/MVS 1.3 Dec 29, 1995 13.09
DFSMS/MVS 1.4 Sep 28, 1997 15.04
DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04
DFSMS/MVS 1.5 ??? ??, 1999 16.04
DFSORT SMF V1R5 Mar 1, 2006 24.02
MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02
MQ Series 1.2.0 May 26, 1998 16.02
MQ Series 2.1.0 Oct 2, 1999 17.07
MQ Series 5.2 Dec 16, 2000 18.10
MQ Series 5.3 Dec 16, 2002 21.05
MQ Series 6.0 Feb 14, 2006 23.23
Websphere MQ Series 7.0 ??? ??, 2009 *28.06
Websphere MQ Series 7.1 MAR 12, 2011 29.03
Websphere MQ Series 8.0 Jun 24, 2011 29.05
NETVIEW 3.1 type 37 ??? ??, 1996 14.03
NPM 2.0 Dec 17, 1993 12.03
NPM 2.2 Aug 29, 1994 12.05
NPM 2.3 ??? ??, 1996 15.08
NPM 2.4 Nov 18, 1998 17.01
NPM 2.5 Feb ??, 2000 18.02
NPM 2.6 Nov ??, 2001 19.06
RMDS 2.1, 2.2 Dec 12, 1995 12.12
RMDS 2.3 Jan 31, 2002 19.11
TCP/IP 3.1 Jun 12, 1995 12.12
TCP/IP 3.4 Sep 22, 1998 16.04
WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04
WebSphere 6.0 Feb 18, 2006 23.23
WebSphere 7.0 Oct 7, 2010 28.06
WebSphere 8.0 Jul 17, 2011 29.05
DOS/VSE POWER V6.3.0 Dec 19, 1998 16.08
VM/ESA 2.0 Dec 23, 1992 10.04
VM/ESA 2.1 Jun 27, 1993 12.02
VM/ESA 2.2 Nov 22, 1994 12.06
VM/ESA 2.3 Jun 1, 1998 16.08
VM/ESA 2.4 Mar 1, 2001 19.03
z/VM 3.1 Mar 1, 2001 19.03
z/VM 3.1 DATABYTE=0 May 2, 2002 20.02
z/VM 4.2 ?? May 2, 2002 20.02
z/VM 4.4 Jan 22, 2005 22.22
z/VM 5.1 Jan 22, 2005 22.22
z/VM 5.2 Jan 22, 2006 24.01
z/VM 5.3 TOLERATE Jun 7, 2007 25.05
z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08
z/VM 5.4 (COMPATIBLE) Sep 12, 2008 *27.01
z/VM 6.1 (NO CHANGES) Jul 7, 2008 27.01
z/VM 6.2 Dec 2, 2011 29.04
z/VM 6.3 INCOMPATIBLE Jul 23, 2013 31.05
z/VM 6.3 z/13 Jan 23, 2016 33.33
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.13
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
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
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
ACF2 6.2 16.04
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
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2 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 34.34.
1. Incompatibilities introduced in MXG 34.34:
a- Changes in MXG architecture made between 34.34 and prior versions
that can introduce known incompatibilities.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
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 34.34 after MXG 33.33:
Dataset/
Member Change Description
ANAL3CPC 34.238 Example RMF III CPC data report.
ANAL9914 34.107 SMT Topology Report typo, reports all systems.
ANAL9914 34.255 z13 Topology Report typo corrected.
ANALCSQX 34.122 Concurrent MQ Apps logged on from SYSLOG CSQX msgs
ANALDB2R 34.265 ANALDB2R 33.33-34.07 could require temp //PDB DD.
ANALDCO1 34.271 New ANALDCO1 provides simple DCOLLECT reports.
ANALGRCA 34.015 New analysis of Group Capacity
ANALRANK 34.127 NOT SORTED if only one variable was examined
ANALUOW 34.110 Parameter INCODE= added for tailoring/selection.
ASMRMFV 34.095 Some ASMRMFV log dates off by one day, output fine.
ASMRMFV 34.133 RMF III GMT offset collects multiple time zones data.
ASMRMFV 34.152 The RMF III DOW filter was not working.
ASMRMFV 34.191 Enhanced RMF III data filtering reduces data volume.
ASMRMFV 34.262 ASMRMFV enhancement for Parameters.
ASMRMFV 34.273 Internal Performance improvement for RMF III support
ASUM4HRS 34.218 Four Hour Average analysis was incorrect initialized.
ASUMCELP 34.106 z13 SMT_MODE SMT_NUM=2, NRZIPCPU finally correct.
BLDSMPDB 34.131 ERROR: Invalid date constant " .":d, FORCEDAY= fix
BLDSMPDB 34.153 Change 33.031 missed two instanced of LOWCASE().
BUILDPDB 34.147 Large SPIN.SPIN6 due to PRINTWAY records cleared.
BUILDPDB 34.162 Support for z/OS 2.2 JES2 8-char JOBCLAS8 in BUILDPDB
CHECKSTN 34.167 Detection/Protection of duplicate SMF70STN values.
CICINTRV 34.254 CICS Dispatcher DSGSRBT SRB Time Kept in CICINTRV.
DB2COUNT 34.209 "DB2 is filling my SMF, how do I find out who/why?"
GRAFWRKC 34.044 New Capacity Group report of CEC resources by LPAR.
GRAFWRKC 34.101 Improved CPU and MSU and Group Capacity SGPLOTs.
IHDRRMFV 34.092 Support for IHDRRMFV "Header" Exit selection member.
IMACCADI 34.263 Support for CAA/DISPATCH type 6 change (INCOMPAT)
ITRM 34.011 Possible MXG 33.33 issues with ITRM documented.
JCLTESxx 34.259 Some JCLTESxx members still included gone TYPEQAPM.
MOBWRK05 34.075 SCRT/MWRT REPORT WILL ABEND IF CLOCK CHANGE INCLUDED
MOBWRKI2 34.084 ERROR: FILE WORK.SUMSTSBP.DATA DOES NOT EXIST fixed.
PDBAUDIT 34.003 FILE _TMPLIB.XTY70CP.DATA does not exist.
READDB2 34.102 Support for IFCID=58's second dataset T102SA58.
RMFINTRV 34.029 Capacity Group variables SMF70GNM/GMU added
RMFINTRV 34.078 33.33 and 34.01 had errors in MSU72/MSUSOFT/etc.
RMFINTRV 34.207 VMXGRMFI with INTERVAL=DATE s/b INTERVAL=DATESHIFT.
TYPE0203 34.074 SMF2IHASHMETH/SMF2ISIGTYPE were blank, bad bit test.
TYPE102 34.032 Support for DB2 Trace IFCIDS 311 and 321.
TYPE102 34.053 BMC APPTUNE defective FIX BPU3604, INPUT EXCEEDED.
TYPE102 34.072A Support for SMF 102 IFCID 58 Added segment.
TYPE102 34.123 Support for DB2 IFCID 365 and 376 corrections.
TYPE110 34.065 CICS/TS 5.3, MNSEGCL=5 TSQUEUE INPUT EXCEEDED ERROR.
TYPE110 34.183 Partial Support for CICS/TS 5.4 OPEN BETA.
TYPE110 34.203 READTIME in all "CICS EXCLUDED" messages for DICT.
TYPE110 34.260 Support for SMF 110 Subtype 2 STID=32 creates CICLDY.
TYPE110 34.274 Support for CICS/TS 5.4 BETA 6 (INCOMPAT CICSTRAN).
TYPE113 34.027 TYPE113 CPU Speed SM1132SP wrong on Sub-Capacity z13.
TYPE115 34.200 MQMLOG enhanced with new variables, protection added.
TYPE115 34.272 Support for MQ SMF 115 Subtype 231 DSP/ADP/SSL/DNS
TYPE116 34.008 New Variables added to MQMACCTQ
TYPE117 34.103 Support for IBM Integ Bus V 90005 SMF 117 INCOMPAT
TYPE117 34.157 Support for SMF 117 Integration BUS V10 INCOMPATIBLE.
TYPE117 34.243 Support for SMF 117 Version 2 (INCOMPATIBLE) format.
TYPE119 34.168 Support for SMF 116 Subtype 6 Home IP Address segment
TYPE119 34.189 MXG 34.05 ONLY, INPUT EXCEEDED more than 3 Homeaddr.
TYPE119 34.213 Support for SMF 119 Subtype 81 Intrusion Detection.
TYPE119 34.252 TYP11950 dataset only contained first KEY.
TYPE120 34.055 Proper Support of 120 ST 9 TYP1209R/TYP1209N datasets
TYPE120 34.148 Support for ODM Version 8.8 SMF 120 subtype 100.
TYPE120 34.163 Support for WAS Liberty V16.0 SMF 120 Subtype 11.
TYPE120 34.170 Support for WebSphere Liberty Batch SMF 120 Subty 12.
TYPE123A 34.105 Support for SMF 123 Liberty z/OS Connect EE Audit.
TYPE124 34.187 Support for SMF 124 I/O Supervisor IOS (z/OS 2.2).
TYPE1415 34.224 Support for APAR OA50256 for TYPE1415/SMF14DSVER.
TYPE29 34.221 Support for SMF 29 IMS Java CPU and Garbage Collect
TYPE29 34.221 Support for new SMF Type 29 IMS JAVA/GC validated.
TYPE30 34.118 MXG created variable CPUZIPTM_CPUIFATM_INST wrong.
TYPE30 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE42 34.054 Variable SMF42LAN was not converted to EBCDIC.
TYPE42 34.070 I/O Connect Time S42CONNTM is calculated.
TYPE42 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE42 34.222 Support for APAR OA51097 for subtype 19 fields.
TYPE42 34.245 SMF 42 TYPE42L1 dataset misaligned at SMF42HUA.
TYPE60 34.056 TYPE 60 variable SMF60ELP misaligned.
TYPE6156 34.219 Support for SMF Type 65 GDGCOMPL/GDCNOEXT/GDGLIMIT
TYPE70 34.228 Support for APAR OA48688, ABSOLUTE MSU LPAR GROUP CAP
TYPE7072 34.010 TYPE72GO MSUxxxxx variables labeled/documented.
TYPE7072 34.072 R723DNST NOT EQUAL TO R723RTYP message eliminated.
TYPE7072 34.232 First 34.07. CRITICAL ARRAY EXCEEDED ERROR fixed.
TYPE7072 34.239 SMT Corrections to TYPE70PR "OTHER SYSTEM" LPARs.
TYPE71 34.043 New variables SMF71CPx,SMF714Kx,SMF71PLx were wrong.
TYPE72PD 34.111 New TYPE72PD RMF WLM POLICY DEFINITIONS dataset.
TYPE73 34.068 Support for SPLIT RMF 73 records, _S73 required.
TYPE74 34.073 Dataset TYPE749 (PCIE) is enhanced with new vars.
TYPE74 34.181 Defective BMC CMF type 74 subtype 4 SMF74ML=0 bypass.
TYPE74 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE74 34.223 Support for APAR OA49415 for SuperPAV support.
TYPE78 34.223 Support for APAR OA49415 for SuperPAV support.
TYPE79 34.214 Support for new variables in Sep 2016 SMF manual.
TYPE80A 34.086 Support for TYPE8069 R_PKISERV GENCERT event SMF 80.
TYPE80A 34.176 RACFTYPE=6 RACFEVNT=19 skipped segment message.
TYPE80A 34.178 Support for RACF 80 TOKDANAM new values.
TYPE80A 34.206 Support for Top Secret Release R15 & R16 (INCOMPAT).
TYPE80A 34.251 Support for TOP SECRET RDT Table decoding.
TYPE85 34.067 z/OS 2.2 OAM SMF 85 INPUT STATEMENT EXCEEDED fixed.
TYPE87 34.166 Support for SMF Type 87 Subtype 2 ENQ/DEQ records.
TYPE90A 34.214 Support for new subtypes 38 and 39 in SMF 90.
TYPE98 34.216 Support for SMF 98 High Freq Thruput Stats record.
TYPE99 34.194 Support for SMF 99 Subtype 1 Hardware Absolute CAP.
TYPEATF 34.041 Support for ATF V531 Enhanced Summarization Phase 2.
TYPEATF 34.180 Omegamon XE ATF times are now on local time zone.
TYPEBBMQ 34.026 Support for MVMQ PTF BPL2558, times are microseconds.
TYPEBBMQ 34.064 Circumvention BBMQ Short E6 records, datetimes fixed.
TYPEBVIR 34.217 BVIR301 and BVIR302 datasets were wrong, too few obs.
TYPECDHW 34.202 Support for Connect Direct Simultaneous Session CDHW
TYPECIMS 34.007 Correction for IMF 5100 incorrect values, no ABEND.
TYPEDB2 34.108 DB2 Sim Buff Pool DB2STSBP QBSP variables corrected.
TYPEDB2 34.229 Support for DB2 V12. (COMPATIBLE).
TYPEDB2 34.248 DB2 Netezza IDAA Q8STxxxx in new DB2NETZA dataset.
TYPEDB2 34.281 DB2 IDAA variable Q8STDSKU format/label corrected.
TYPEDCOL 34.042 Support for FLAG4 MegaByte format size variables.
TYPEDCOL 34.115 DCDTIMEC Data Set Create Time not populated if.
TYPEDVS 34.014 Support for Rocket Software DVS User SMF record.
TYPEEDGR 34.116 RMM datasets enhanced with SYSTEM and EDGRTIME.
TYPEHSM 34.002 New datetime and duration variables in HSMFSRST.
TYPEHSM 34.193 Invalid HSM VSR/DSR with '62'x vs 'S' protected.
TYPEIDML 34.282 Support for IDMS Log (INCOMPAT, third record).
TYPEIDMS 34.164 Support for IDMS Version 19 (INCOMPAT with R084146).
TYPEIMS 34.087 MXG 34.02, IMS 12.1, IMS 07 misalign, DLRAZAAP fixed.
TYPEIMS 34.091 Support for IMS Log 16x Sign On/Sign Off log record.
TYPEMVIP 34.186 Support for Mainview for IP RTIN 34x TAC9I220 dataset
TYPENDM 34.017 Support for NDM-CDI SE Session End record.
TYPEPKSZ 34.020 Support for PK-ZIP INCOMPATIBLE increase field length
TYPEPROS 34.215 Support for PRO/SMF (previously X37) Version 7.8.
TYPERACF 34.247 Support for RACF APAR OA43999 RACF UNLOAD database.
TYPERMFV 34.092 MXG 34.01-34.02. ZRBCPU variables CPCGRPxx wrong.
TYPERMFV 34.100 ZRBASI ASILPGSZ, ZRBGEI many GEIxxxxx corrected.
TYPERMFV 34.156 INVALID DATA for ASIQSCANxxx, incorrect informat.
TYPERMFV 34.192 RMF III variable GMTOFF kept in all ZRB datasets.
TYPESAMS 34.089 Support for SAMS VANTAGE User LSPOOLPO INCOMPAT.
TYPESTC 34.019 Corrections/enhancements for Oracle STC SMF record.
TYPESTC 34.081 Oracle/STC User SMF record GMTOFFTM "slightly" wrong
TYPESTC 34.237 New variables added to STCVSM11 dataset.
TYPESYSL 34.121 Formal support of SYSLOG with all normal MXG tokens.
TYPETHAL 34.261 Support for Thales Security Records with/wo subtype
TYPETMD2 34.275 Support for ASG/TMON for DB2 IDAA SA and SB records.
TYPETMO2 34.049 TMON V4.0 microsec/tod time change missed 15 vars.
TYPETMO2 34.195 TMON/CICS new vars TASZIPTM/TASELGTM recalc TASCPUTM.
TYPEVMXA 34.005 Support for zVM HIS (SMF 113) VXPRCMFC z/13 data.
TYPEVMXA 34.066 z/VM VXBYUSR enhanced, option to USER 8709 ABEND.
TYPEVMXA 34.080 Support for z/VM SMT MODE, caused BROKEN REC ERROR.
TYPEVMXA 34.085 Support for z/VM VXSYTEMP third section, plus more.
TYPEVMXA 34.099 zVM 6.3 circumvent, 5.20 HWCLEN=384 new PRCAPMCT=11.
TYPEVMXA 34.169 zVM HIS macros for PRCMFC PRCMFM now work correctly.
TYPEVMXA 34.175 zVM 6.3.16.1 inserted in PRCPUP, PROBABL DATA LOSS.
TYPEVMXA 34.249 z/VM Linux Appldata VXAPLSLM/SLN/SLP corrections.
TYPEVMXA 34.280 z/VM Linux Appl VXAPLSLM/N/P/0 deaccum corrected.
TYPEVMXA 34.280 z/VM VXBYUSR had some obs with negative values.
TYPEZCOS 34.241 Support for AutoSoftCapping Version V4 (COMPATIBLE).
UTILRMFI 34.006 UTILRMFI report was dropped accidentally in 33.024
VGETJESN 34.240 Hex zeros in JCTJOBID in SMF 42 ST 27 protected.
VGETOBS 34.001 OPTION CHARCODE caused ERROR: CHAR OPERAND.
VMXGALOC 34.160 Revised for Linux, case sensitive directory names.
VMXGALOC 34.253 UPCASE removed for BASExxx path for Linux casing.
VMXGCNFG 34.119 CPU Loop after program ended, if //SOURCLIB DD.
VMXGINIT 34.052 WPS ONLY, First 34.01, RUN: in VMXGINIT FAILS INIT.
VMXGSUM 34.137 New MXGSUMCLASS option can save CPU time, TEST IT!!
VMXGSUM 34.151 SYSLAST is now correctly set to last output dataset.
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at http://www.mxg.com.
Inverse chronological list of all Changes:
NEXTCHANGE
====== Changes thru 34.284 were in this MXG 34.34 dated Jan 3, 2017====
Change 34.284 Primarily used internally by MXG. If it was being used
VMXGOPTR to restore an option to its original setting but had not
Jan 2, 2017 been previously invoked to set the option and the option
required an = (LINESIZE=xxx) it failed lacking the name
of the option and the = so LINESIZE resolved to:
OPTIONS 132;
Change 34.283 -PDBAUDIT failed if the last "PDB" data library happened
PDBAUDIT to be Sequential Format (tape), with the error message:
Dec 31, 2016 WARNING: APPARENT SYMBOLIC REFERENCE LIBCOUNT NOT RES....
Jan 1, 2016 -Could also fail if zero LIBNAMES were selected, with an
error "INVALID OPTION 132".
Thanks to Steve Gear, Integrysgroup, USA.
Change 34.282 Support for IDMS Log records (INCOMPATIBLE, as a third
VMACIDML record per event was added with additional fields).
Dec 29, 2016 Only the IDMLOG02 TASK dataset, has been validated with
Jan 4, 2017 data records, but IDMLOG03 TRANSACTION dataset should be
valid. Unfortunately, there is no GMT offset value in the
log records, so you will need to set the value with
//SYSIN DD *
%LET MACKEEP= MACRO _GMTIDML -4 % ;
for the minus 4 hour GMT offset for US EST.
Thanks to Torstein Netland, CSC, NORWAY.
Change 34.281 IDAA variable Q8STDSKU is disk utilization not bytes, so
VMACDB2 the format and length were removed and the label changed.
Dec 27, 2016 And variables Q8STCCPU_64 Q8STWCPU_64 are also percents.
Jan 13, 2017
Thanks to Tim King, BCBSSC, USA.
Thanks to Terry Johnson, BCBSSC, USA.
====== Changes thru 34.280 were in this MXG 34.10 dated Dec 25, 2016====
Change 34.280 z/VM Linux Appl Datasets VXAPLSLM,SLN,SLP,SL0 deaccum now
VMACVMXA uses new SYNCCNT1=1 OR SYNCCNT2=1 variable's values to
Dec 18, 2016 recognize a reset in accumulated values has occurred. The
Dec 28, 2016 ancient MXG heuristic of a negative time delta to detect
a wrap of the accumulated field (plus first-dot tests)
is insufficient for these four datasets, and caused very
large values or negative values in some variables.
Also, the interval is deleted if SYNCCNT1 NE SYNCCNT2, as
that means the record was updated on the Linux side while
z/VM was still collecting the data, which could then be
inconsistent.
-Dataset VXBYUSR had observations with DELTATM=-9999 that
should not have been output, causing some negative values
in other variables.
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.279 Documentation of ANCIENT z/OS, z/VM APAR OA35675 (2011).
TYPE7072 Support for z/OS under z/VM new RMF VMGUEST option with
Dec 18, 2016 APAR OA35675, populates the Partition Dispatch CPU Time
in two "simplified" Partition Data sections in TYPE 70
RMF records, one with LPARNAME='PHYSICAL' with the z/VM
CPU consumption (IBM RMF Reports LPARNAME *VMSYSTEM*),
and one with LPARNAME='VMSYSTEM' with the z/OS Partition
CPU Dispatch time. Note that SMF70ONT, Online Time is
NOT Populated. From z/VM, this bit on is STILFE.
-MXG Version 29 added variable VMSYSTEM=Y, true for Bit 5
in 2011, but only from the SMF Manual; it was a post by
Martin today that educated me to the actual impact!
Thanks to Martin Packer, IBM, EUROPE!!
====== Changes thru 34.278 were in this MXG 34.09 dated Dec 16, 2016====
Change 34.278 If you specified 0 OBS for 26J2 or 26J3 and did NOT
UTILBLDP specify SPINCNT=something then SPINCNT is set to 0 to
Dec 13, 2016 keep jobs from sitting in SPIN until the SPINCNT is
reached.
Change 34.277 New RMF III ASI fields in z/OS 2.2 suffixed with _LF are
VMACRMFV Long Floating point and with _S are Short Binary informat
Dec 9, 2016 but that was not known and they were incorrectly input.
Some of these fields contain (HATED!) accumulated values,
which have NEVER been in RMF III, and are hated because
the deaccumulation requires two more passes of the data.
But for the important CPU accumulated fields, there is
already an interval variable (e.g., ASICPUTA), so no
deaccumulation was previously necessary. But the higher
microsecond resolution of ASICPUTA_LF, records 20-40%
more CPU time than ASICPUTA, with 1 millisecond.
-However, the several fields that are accumulated are not
always monotonically increasing, so further analysis is
in progress and this text will be revised and MXG will
provide optional deaccumulation if adequate heuristics
can be tested.
Change 34.276 ASCII only, BLDSMPDB would fail to create a weekly and/or
BLDSMPDB monthly PDB if a prior error has set OBS=0, with no clue.
Dec 8, 2016 Now, BLDSMPDB will tell you there were zero observations,
in a WARNING message.
-WTD and MTD processing may have gone to the incorrect
directory - ASCII only and only with AUTOALOC=YES
-New parameter ERASESPIN will delete everything in the
SPIN libname when set to yes - primarily for MXG support
-Checks added to ensure that PDB SPIN TREND WEEK WTD MONTH
and MTD libnames are allocated as needed by the other
parameters used. In the case of WTD/MTD if they are not
found but WEEK/MONTH are a warning is issued and the
libnames that were found are substitute
Change 34.275 Support for ASG/TMON for DB2 IDAA SA and SB records
EXTMD2SA creates three new datasets:
EXTMD2SB DDDDDD DATASET DESCRIPTION
EXTMD2SX TMD2SA TMD2SA IDAA SA Summary
IMACTMD2 TMD2SB TMD2SB IDAA SB Summary
VMACTMD2 TMD2SX TMD2SBD IDAA SB Detail
VMXGINIT
Dec 12 2016
Thanks to Daniel Hamiel, NedBank, SOUTH AFRICA.
Thanks to Mike Lotter, NedBank, SOUTH AFRICA.
Change 34.274 Support for CICS/TS 5.4 Beta 6 INCOMPAT, new CICSTRAN
EXCICMQR fields inserted.
FORMATS -New variables added to CICSTRAN:
IMAC110 ASFREECT='EXEC CICS*FREE CHILD*COUNT'
UTILEXCL ASFTCHCT='EXEC CICS*FETCH*COMMANDS'
VMAC110 ASFTCHCN='ASYNC API*FETCH*WAIT*COUNT'
VMXGINIT ASFTCHTM='ASYNC API*FETCH*WAIT*DURATION'
Dec 15, 2016 ASNATCN='ASYNC API*RUN DELAYEDCOUNT'
ASRMATTM='ASYNC API*RUN DELAYED*DURATION'
ASRUNCT ='EXEC CICS*RUN*TRANSID*COUNT'
ASTOTCT ='ASYNC API*COMMANDS*COUNT'
PTCOUNT ='PREVIOUS*TRANSACTION*COUNT'
PTSTART ='PREVIOUS*TRANSACTION*START*DATETIME'
PTTRAN ='PREVIOUS*TRANSACTION*TRANSID'
PTTRANNO='PREVIOUS*TRANSACTION*sequence*number'
-New CICMQR MQ Monitor statistics dataset from STID=148
is created.
Change 34.273 Internal restructure of ASMRMFV for possible performance
ADOCRMFV improvements and better design for maintenance.
ASMRMFV -Mitigate Store In Instruction Stream (SIIS) conditions
Dec 6, 2016 and other improvements.
-Updating data imbedded in an instruction stream or
modifying instructions results in additional CPU overhead
maintaining the data and instruction caches.
-ASMRMFV is changed to isolate and align all data used in
subroutines on 256 byte cache boundary lines. This
increases the size of the ASMRMFV load module about 7% to
about 272K.
-IBM Service Call macros for OPEN, CLOSE, RDJFCB, and so
on are split into Execute and List forms because standard
macro expansions update parameters in the instruction
stream.
-Limited volume testing showed about a 1% CPU Time
reduction that may vary in actual production use.
-The MODCB Service Call function is no longer used to
alter the VSAM ACB and RPL control blocks. ASMRMFV only
makes trivial changes to these during processing and
Execute and List forms of MODCB generated a lot of
instructions.
-The MODCBERR subroutine used to process MODCB errors
is deleted.
Change 34.272 Support for the MQ SMF 115 Subtype 231 DSP/ADP/SSL/DNS
EXTY115A segments, each of which creates new dataset:
EXTY115D DDDDDD DATASET DESCRIPTION
EXTY115L TY115D MQMDSP MQM DISPATCHER
EXTY115N TY115A MQMADP MQM ADAPTER
IMAC115 TY115L MQMSSL MQM SSL
VMAC115 TY115N MQMDNS MQM DNS
VMXGINIT Their unique variables that were previously incorrectly
Dec 2, 2016 kept in dataset MQMCHIN have been dropped.
-Each segment contains QCTCPTM and QCTELPT, CPU & Elapsed
time; many observations have CPU Time slightly larger
than Elapsed time (largest 15 with QCTCPTM 364 seconds).
IBM Explains:
CPU start and end times are taken directly from the
TCB to minimize performance impact. This field is only
updated when the TCB is undispatched, so if the TCB
has been dispatched for a while when the TCB CPU time
is taken at the start of the request, this value
could be a bit low, which could mean that the TCB CPU
interval calculation returns a value which is slightly
high. This is as-designed, and the data is still
useful. When elapsed time and CPU time are similar,
or when CPU time appears greater than elapsed time,
the task is getting all the CPU it needs, and you can
interpret elapsed time as an approximation for CPU
time. When elapsed time is significantly larger than
CPU time, then the task is having to wait for CPU or
for some internal wait, and that difference may be of
interest.
-APAR PI46585 is required to correct negative or invalid
values in QCTWTTM, QCTLSTM, and QCXTLGTM in these new
ADP/DSP/SSL/DNP datasets.
-The subtype 215 record replaced the subtype 2 record when
OPMODE(NEWFUNC) is specified; the buffer manager data
that was output in dataset MQMBUFER is now instead output
in dataset TY115215.
Thanks to Carol Arnold, Brown Brothers Harriman, USA.
Thanks to Kevin Colish, Brown Brothers Harriman, USA
Thanks to Richard Harran, IBM MQ Support, ENGLAND.
Change 34.271 New ANALDCO1 provides simple DCOLLECT reporting, using
ANALDCO1 the datasets created by JCLDAYDS. See examples in the
Nov 30, 2016 comments.
Change 34.270 -With PDB=RAWDATA and PDBOUT=WORK, a dataset not found was
VMXGDSN created when summarizing data that had been cleaned up
Nov 30,2016 prior to running the code to read tape data.
-Enhanced to allow you to suppress TAPEDATE by using new
TAPEDATA=null string.
====== Changes thru 34.269 were in this MXG 34.08 dated Nov 25, 2016====
Change 34.269 Support for INCOMPATIBLE TPX PTF R085512 and R085513 that
VMACTPX increased Port Number from 4 to 5 digits.
Nov 23, 2016
Thanks to Johanne Goulet, Government of Quebec, CANADA.
Thanks to Christian Roy, Government of Quebec, CANADA.
Change 34.268 Truncated POEX record with only 54 bytes caused STOPOVER.
VMACPOEX Now, the OFFSET just read is compared with LENGTH and the
Nov 22, 2016 first bad record is reported in the log and all deleted.
Thanks to Scott Wiig, USBank, USA.
Change 34.267 Support for RACF OIMID Token creates TOKOIMIC variable
VMAC80A and support for RACF LTL Token creates TOKMLTL variable
Nov 21, 2016 in TYPE80TK dataset.
Thanks to Mark Tomlinson, Lloydsbanking, ENGLAND.
Change 34.266 WPS Only. %MACRO VMXGPRNT invocation with text on col 72
ANAL113 caused error with WPS 3.00 (03.00.02.00.29316 but was
Nov 20, 2016 parsed correctly with WPS 3.02 (03.00.03.00.016221).
The error had ASIC03 for what should have been BASIC03.
Shortening the line did not eliminate the error.
Change 34.265 ANALDB2R could require //PDB DD because updates to READB2
ANALDB2R for DB2SBP and DB2NET had incorrect tokens that should be
READDB2 WORK. MXG code is now corrected, but circumvent with:
Nov 20, 2016 //PDB DD UNIT=SYSDA,SPACE=(CYL,(500,500),DISP=(,PASS)
on temp DASD, since they were not intended to be kept.
Thanks to John Ordman, Wipro, USA.
Change 34.264 -The section of code creating the prior TREND database was
VMXGALOC incorrect and failed to create the directory on the first
Nov 23, 2016 VMXGALOC execution resulting in an error.
-A FORCEDAY test did not have both side's UPCASEd.
Thanks to Job Varkey, VERISK, USA.
Thanks to Patricia J. Jones, DST, USA.
Change 34.263 SMF 6 CA/Dispatch records were increased to LENGTH=371,
IMACCADI adding two new fields CADIDES2 CADICHAR INCOMPATIBLY due
VMAC6 to MXG tests for LENGTH=347 to detect the V10 vs V11 data
Nov 18, 2016 records; those tests for LENGTH and SMF6LEN are unneeded
now and are removed.
Thanks to Glen Bowman, Wakefern, USA.
Change 34.262 -Support for z/OS 2.1+ PARMDD= EXEC statement JCL
ADOCRMFV parameter, enhanced SYSIN DD support, other improvements
ASMRMFV and fixes.
Nov 19, 2016 -PARMDD= is a new JCL parameter available with z/OS 2.1
and up. PARMDD= specifies a ddname of a file containing
parameters to be passed to the invoked program coded with
PGM=.
-If the ddname does not exist within the JCL step a
JCL error occurs with the message:
IEF689I JOB jobname FAILED PARMDD DID NOT OPEN
-The ddname may reference a physical sequential file,
PDS/PDSE member, or subsystem DD * or DD DATA data set.
-Unlike the 100 character PARM= parameter limit the
PARMDD= file may contain up to 32760 characters after
data assembly. If this limit is exceeded a JCL error
occurs.
-During data assembly of the PARMDD=ddname file trailing
blanks are stripped from each record and entirely blank
records are discarded by z/OS.
-Also during data assembly PARMDD=ddname fixed records are
checked for sequence numbers and also stripped if found.
There is no sequence number checking for variable
records.
-Any data stripped from a PARMDD=ddname file does NOT
count towards the 32760 character limit.
-The PARM= and PARMDD= parameters on the JCL EXEC
statement are mutually exclusive. If both are coded,
a JCL error occurs with message:
IEFC009I KEYWORD PARMDD IS MUTUALLY EXCLUSIVE WITH
KEYWORD PARM ON THE EXEC STATEMENT
-The PARMDD= parameter supports any RECFM of F, FB, V, or
VB. RECFM=U and Spanned records are not supported.
-The PARMDD=ddname file may have an LRECL up to 32760 for
fixed length records or 32756 for variable length
records.
-The PARMDD=ddname file may be concatenated with other DDs
in accord with usual concatenation rules.
-These are all valid examples of PARMDD=ddname usage:
//stepname EXEC PGM=ASMRMFV,PARMDD=ddname
//ddname DD DISP=SHR,DSNAME=dsname
//stepname EXEC PGM=ASMRMFV,PARMDD=ddname
//ddname DD DISP=SHR,DSNAME=dsname(member)
//stepname EXEC PGM=ASMRMFV,PARMDD=ddname
//ddname DD *
//stepname EXEC PGM=ASMRMFV,PARMDD=ddname
//ddname DD DATA
-For further details see Section 29 "PARMDD=ddname
Support" in the ASMRMFV source or ADOCRMFV members.
-Similar to PARMDD=ddname usage the ASMRMFV SYSIN DD (or
alternate ddname) now supports RECFM FB, F, VB, or V.
RECFM=U and Spanned records are not supported. Prior to
this change only RECFM=FB or RECFM=F was allowed.
-The ASMRMFV SYSIN DD (or alternate ddname) LRECL may
range up to 32760 for fixed length records or 32756 for
variable length records. Prior to this change only
LRECL=80 was allowed.
-A new built-in alternate ddname for SYSIN named SYSINA
may be provided in JCL and will be used instead of SYSIN
if found. It is not necessary to code the SYSIN=SYSINA
ASMRMFV parameter to use this alternate. However, any
other alternate ddnames require SYSIN= in the PARM= field
or PARMDD=ddname file.
-The order of ddname selection precedence for SYSIN is::
1) The SYSIN=ddname parameter in either the JCL PARM=
field or PARMDD=ddname file if present.
2) The //SYSINA DD in JCL if present.
3) The //SYSIN DD in JCL if present.
-A new built-in alternate ddname for SYSPRINT named
SYSPRINA may be provided in JCL and will be used instead
of SYSPRINT if found. If both SYSPRINA and SYSPRINT are
present SYSPRINT is ignored. There is NO SYSPRINT=ddname
parameter because the ASMRMFV log must be opened well
before any parm processing.
-When processing a PARMDD=ddname or SYSIN (or alternate)
files with data exceeding 100 characters in length, the
data is displayed in the existing RMFV002I message in 100
character sections.
-The first and last RMFV002I sections are always shown,
but any intermediate blank sections are not displayed.
The rightmost column for each section display shows the
number of characters remaining to be shown.
-SYSTSIN and SYSPRINA are added reserved ddnames when
SYSIN=ddname is specified.
-RECFM and LRECL are validated for all SYSIN (or
alternate) data sets.
-After MXG Change 34.226 the SYSIN OPEN subroutine
incorrectly attempts to obtain the DSCB for a //SYSIN DD
DUMMY statement. This results in Abend U0998 Reason Code
0018 and has been corrected.
-MXG Change 34.226 incorrectly altered VSAM TESTCB macro
results test for an VSAM RRDS type data set causing a
VSAM KSDS to be accepted as valid as an RMF III data set.
This caused an I/O error on the first read with Abend
U0998 Reason Code 0029 and has been corrected.
-RMFV008I DATASET LAST OPEN and RMFV009I ORIGIN messages
can be missing from ASMRMFV log for some RMF III data
sets after MXG Change 34.133 and this is also corrected.
-Message RMFV056S is now issued when PATTERR=ABEND instead
of RMFV056E as this is considered a severe error.
-SYSIN=ddname processing now correctly issues message
RMFV004E instead of RMFV056E.
-Incorrect test for '*/' end of imbedded comment string
fixed.
-Expand RMFV005E message to contain first 100 characters
of a bad parameter up from 80 as maximum that will fit
within the 126 character WTO text limit. If the
parameter in error exceeds 100 characters only the first
100 characters are shown.
-Correct SRST search handling for parameter strings
exceeding 256 bytes in length.
-Add short problem description text to RMFV005E message
if displayed parameter length will allow.
-Change '=' character search in keyword parameter
processing in PARMS subroutine to use SRST instruction
for better performance.
-FINAL subroutine setting Return Code 0016 when only
warnings for RED Invalid Processor and SPG Internal
error exist is fixed to issue Return Code 0008.
-RMFV018S SYNAD I/O error message loop can result after a
subsystem DD * data set for SYSIN (or an alternate)
specifies an LRECL other than 80 in JCL. z/OS apparently
continues to call the SYNAD routine for the same error
repeatedly with a WRONG LENGTH RECORD indication. The
problem has been circumvented.
-RMFV007S message was not always showing Reason Code of
blanks when the Reason Code is not available for the
service in error.
-Documentation Section 17 is retitled to "U0998 Abend
Reason Codes".
-Documentation Section 19 "Output LRECL" is retitled as
"Input and Output" LRECL.
-Former documentation Section 29 Summary is now Section
30.
-Former documentation Section 30 Bibliography is now
Section 31.
-New documentation Section Section 29 "PARMDD=ddname
Support" added.
-Updated following documentation sections for alternate
SYSIN/SYSPRINT and PARMDD=ddname support:
Section 3 "Execution JCL"
Section 5 "Input Data Selection Parameters"
Section 6 "Report Control Parameters"
Section 9 "JCL and SYSIN Parameter Usage"
Section 10 "Parameter Syntax Rules"
Section 11 "Parameter Coding Examples"
Section 12 "Messages"
Section 15 "Program and IBM Limitations"
Change 34.261 Support for Thales Security Record Version x.y INCOMPAT.
VMACTHAL This update supports records with and without subtypes.
Nov 17, 2016 For mapping by record ID, you must define these macros
with YOUR SMF record Ids, either in your IMACKEEP member
or in a %LET MACKEEP= argument in your //SYSIN:
%LET MACKEEP=
%QUOTE(
MACRO _IDTHALS 195 % /*SMF ID FOR SUMMARY RECORD*/
MACRO _IDTHALN 196 % /*SMF ID FOR SNAPSHOT RECORD*/
MACRO _IDTHALC 199 % /*SMF ID FOR CDS RECORD*/
MACRO _IDTHALE 198 % /*SMF ID FOR EXCEPTION RECORD*/
MACRO _IDTHALV 197 % /*SMF ID FOR SECURITY RECORD*/
MACRO _IDTHALR 194 % /*SMF ID FOR RESPONSE*/
);
To process records with SUBTYPES, you need these macros
either in IMACKEEP or with %LET MACKEEP= in //SYSIN:
%LET MACKEEP=
%QUOTE(
MACRO _IDTHALX 200 % /*SMF RECORD ID FOR NO SUBTYPES*/
MACRO _SUBTHAL
IF SUBTYPE GT . THEN DO;
IF SUBTYPE=0 THEN ID=_IDTHALC;
ELSE IF SUBTYPE=4 THEN ID=_IDTHALE;
ELSE IF SUBTYPE=8 THEN ID=_IDTHALV;
ELSE IF SUBTYPE=12 THEN ID=_IDTHALS;
ELSE IF SUBTYPE=16 THEN ID=_IDTHALN;
ELSE IF SUBTYPE=32 THEN ID=_IDTHALR;
END;
%
);
Thanks to Randy Schlueter, FirstData, USA.
Change 34.260 Support for SMF 110 Subtype 2 STID=32 creates new dataset
EXCICLDY DDDDDD DATASET DESCRIPTION
FORMATS CICLDY CICLDY CICS LOADER PRIVATE LIBRARY
IMAC110 that is added in CICS/TS 5.4 OPEN BETA.
VMAC110
VMXGINIT
Nov 18, 2016
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 34.259 Three JCL Test examples still had Includes of TYPSQAPM
JCLTEST9 which was replaced by TYPSQACS for the AS/400.
JCLTESS9
JCLTES92
Nov 14, 2016
Thanks to Earl Kline, Luminex, USA.
Change 34.258 Variable SMT_CORE_FLAG='LPARBUSY*VALID?' with value Y/N
VMAC7072 is now kept in TYPE70EN dataset.
Nov 14, 2016
Thanks to Jim Horne, Lowe's Companies, Inc., USA.
Change 34.257 Support for TMON/CICS Version 4.1 (COMPATIBLE, no change
EXMONCSE to the existing MXG datasets) and support for the CS CTG
EXMONCSW records create three new datasets:
EXMONCSX DDDDDD DATASET DESCRIPTION
IMACTMO2 TMOCSE MONICSE LANDMARK CS-CSE SEGMENT
VMACTMO2 TMOCSW MONICSW LANDMARK CS-CSW SEGMENT
VMXGINIT TMOCSX MONICSX LANDMARK CS-CSX SEGMENT
Nov 13, 2016
Change 34.256 -DB2STATS variables QISEDPSC QISEDPSF QISEDPSL QISEDPSM
Many QVASBRPT QVASBRP QVASACEB QVASACEF QJSTDPXN QJSTDPXT are
Nov 11, 2016 kept and labeled and QWHCJOBSTEP is labeled.
-TYPE117 variables SM117NOR,SM117RSQ are labeled.
-TYPEIAM variables IAMACFL0-7,IAMACIN0-1,IAMCRIN0-8 and
IAMBOPCR IAMBUFCR IAMCOREO IAMCOREX IAMDDL IAMDSNL and
IAMRLSFP are labeled.
-TYPE42 variables SMF42FSH/FSI/FSJ/FSK correctly labeled.
-TYPE64 variable SMF64UTY extra asterisk removed in label.
-TYPE71 variables SMF71C3A/CPM/CPX extra asterisk removed.
-TYPE73 variables SMF73HEN and EXTENDSEG are now labeled.
-TYPE74 variables R748RAI is labeled in TYPE748R dataset.
-TYPE99 variables S99EE_CP_CHIPID S99EE_CP-BOOKID labeled.
Thanks to Chris Weston, SAS ITRM, USA.
Change 34.255 The z13 Topology Report had a typo Z!3 instead of Z13 and
ANAL9914 variable SYSTEM was added to the second report.
Nov 10, 2016
Thanks to Trevor Holland, ANZ, AUSTRALIA.
Change 34.254 CICS Dispatcher CICDS dataset variable DSGSRBT, SRB time
CICINTRV is now kept in the CICINTRV dataset.
Nov 9, 2016
Thanks to Randy Schlueter, FirstData, USA.
Change 34.253 Change 34.160 removed UPCASE function for BASExxx path
VMXGALOC names, but that segment was inadvertently deleted and is
Nov 9, 2016 restored. Impacted only Linux due to case sensitivity.
Change 34.252 SMF 119 Subtype 50 Dataset NUM11905 is NOT the count of
VMAC119 KEY segments, but is ALWAYS One, causing MXG to output
Nov 8, 2016 the first KEY. (And LEN11905 is the TOTAL length of all
KEY segments plus the 4 bytes for LEN/KEY itself).
The number of KEY segments is NOT provided, but MXG now
uses LENLEFT to find and INPUT and output to TYP11950 for
each KEY.
Thanks to Andreas von Imhof, Rabobank, THE NETHERLANDS.
Thanks to Ronald Kristel, Rabobank, THE NETHERLANDS.
Change 34.251 SMF 80 Top Secret records, format $MG080TS maps all of
FORMATS RDT table entries for variable TSFLCLAS.
VMAC80A Member VMAC80A has the SAS program in comments to update
Nov 9, 2016 the $MG080TS table.
Nov 15, 2016 Variable TSRESNAME contains the Resource Name.
Dec 6, 2016
Change 34.250 SMF 120 Subtype 100 ODM records had the order of two
VMAC120 variables, SM120RULEXFSUM/SM120RULEXCALLS reversed.
Nov 2, 2016
Thanks to Paul Volpi, UHC, USA.
Change 34.249 z/VM Linux Appldata datasets VXAPLSLM,VXAPLSLN,VXAPLSLP
EOAPLSLM had occasional large values; the logic to de-accumulate
EOAPLSLN was not reset for FIRST.VMDUSER. For these datasets that
EOAPLSLP are written for each interval for each user whether or
VMACVMXA not any resources were consumed, MXG only outputs an obs
Nov 1, 2016 when an interval had activity, and now the DURATM will
contain the actual duration since the last interval that
was output.
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.248 DB2 Netezza IDAA Q8STxxxx variables were incorrectly
CLEARDB2 output in DB2STAT1/DB2STATS, which is a one instance per
EXDB2NET interval dataset, but there can be multiple Q8ST segments
EXDB2NET per interval (only the first segment was output).
IMACDB2 Now, ALL Q8STxxxx variables in DB2STATS/DB2STAT1 are set
READDB2 to a missing value, and the new DB2NETZA is created with
VMACDB2 one observation for each Q8ST segment.
VMXGINIT
Nov 1, 2016
Thanks to Erling Andersen, SMT, DENMARK.
Change 34.247 Support for APAR OA43999 RACF Database UNLOAD adds these
VMACRACF new variables to RACF0200 dataset:
Oct 28, 2016 USBD_PWD_ALG='ALGORITHM*USED TO*PROTECT*PASSWORD*/.
USBD_LEG_PWDHIST_CT='LEGACY*PASSWORD*HISTORY*ENTRIES*/
USBD_XPW_PWDHIST_CT='KDFAES*PASSWORD*HISTORY*ENTRIES*/
USBD_PHR_ALG='ALGORITHM*USED TO*PROTECT*PASSPHRASE*/.
USBD_LEG_PHRHIST_CT='LEGACY*PASSPHRASE*HISTRY*ENTRIES*/
USBD_XPW_PHRHIST_CT='KDFAES*PASSPHRASE*HISTRY*ENTRIES*/
and these overlooked RACF0200 variables are now created:
PWDENV_EXISTS='PASSWORD*PKCS#7*ENVELOPE*CREATED?'
PWD_ASIS ='EVALUATE*PASSWORD*ENTERED*CASD?'
PHRDATE ='EVALUATE*PASSWORD*ENTERED*CASD?'
PHRGEN ='PASSPHRASE*GENERATION*NUMBER'
CERT_SEQN ='PASSPHRASE*GENERATION*NUMBER'
Dataset RACF0560 missing values messages eliminated .
Thanks to Karl Lasecki, Chemical Abstracts Service, USA.
Change 34.246 RMF III dataset ZRBASI variable ASIDP did not exist in
VMACRMFV z/OS 1.13 nor z/OS 2.1, but the MXG test for ASIVERG3
Oct 27, 2016 used GE '16'x, causing ASIDP to contain characters. IBM
didn't document that the ASI record version was changed
to '1A'x (discovered only in 2.2 data records). Now,
ASIDP is missing in 1.13 or 2.1 and populated in 2.2.
Thanks to Randy Hewitt, HPE Enterprise Services
Change 34.245 MXG 33.08-34.07. SMF 42 dataset TYPE42L1 had misaligned
VMAC42 fields starting with SMF42HUA, causing these variables
Oct 27, 2016 to be wrong: SMF42HUA-SMF42HUG, SMF42HCA-SMF42HCX and
and SMF42HEH-SMF42HEK.
Thanks to Ann Knapik, Progressive Insurance, USA.
Thanks to David Buckmiller, Progressive Insurance, USA.
Thanks to William Keezer, Progressive Insurance, USA.
Thanks to Chris Weston, SAS ITRM, USA.
Change 34.244 A large number of regions could cause ARRAY EXCEEDED
UTILEXCL errors and/or invalid DCN/DRL test values in IMACEXCL if
Nov 9, 2016 an existing PDB.CICSDICT was appended with dictionary
Dec 14, 2016 records with the same SMF times. The MAX NREC value is
now created from PDB.CICSDICT and used for the new NREC
to separate those identical records.
-The Nov 9 change increased arrays from 1999 to 2999 but
the correction eliminated the need for the increase, and
on site encountered a record too long to sort with the
Host sort on z/OS; using the SAS Sort circumvented but
the arrays were reset to 1999 on Dec 14.
Thanks to Erling Andersen, SMT, DENMARK.
Change 34.243 Support for SMF 117 IBM Integration Bus Version 2 format
VMAC117 record (INCOMPATIBLE) that inserted two 26-byte datetime
Oct 22, 2016 fields that do NOT match the existing start/end times.
IBM Support is being contacted.
Change 34.242 If you specified multiple datasets in the INDATA= and
VMXGSUM one of those datasets was also the OUTDATA= and there
Oct 22, 2016 was no OUTCODE= specified AND YOU had told VMXGSUM to
use CLASSNWAY rather than a BY, VMXGSUM would fail with
an error message that you could not open the output
dataset because it was part of SASDSVX. Now if VMXGSUM
sees that the INDATA is not the same as the OUTDATA but
the OUTDATA is part of the INDATA and the length of
OUTCODE is 0 it turns off CLASSNWAY.
Change 34.241 Support for AutoSoftCapping Version V4 (COMPATIBLE) adds
VMACZCOS -Dataset ZCOS01 New Variables
Oct 21, 2016 ZCOS01CMAX='CPCMAX'
ZCOS01CMIN='CPCMIN'
-Dataset ZCOS02 New Variables
ZCOS02PMAX='MSUMAX'
ZCOS02PMIN='MSUMIN'
-Dataset ZCOS04CP New Variables
ZCOS04CMAX='CPCMAX'
ZCOS04CMIN='CPCMIN'
-Dataset ZCOS04GP New Variables
ZCOS04MODE='MODE*MESSAGES*ACTIVE*REPORT?'
-Dataset ZCOS04PL New Variables
ZCOS04ACAP='ABSOLUTE*CAP*TO SET'
-These subtype 4 variables are no longer available and are
blank:
ZCOS04CCAP ZCOS04CAIP ZCOS04CPIP ZCOS04PAIP
ZCOS04PORT ZCOS04CFAM ZCOS04CMOD ZCOS04CSID
Change 34.240 New SMF 42 Subtype 27 had JCTJOBID containing HEX zeros
VGETJESN which VGETJESN did not like, printing WARNING TYPETASK
Oct 19, 2016 NOT DECODED. TEST for nulls in JCTJOBID and SUBSYS of
'SMS' protects this subtype and possible future ones.
Thanks to Joe Babcock, General Motors, USA.
Change 34.239 TYPE70PR data for "OTHER SYSTEM" LPARs could have wrong
VMAC7072 LCPUADDR/SMF70CIN values, which could impact the Dispatch
Oct 20, 2016 (CPU) time and other fields in ASUMCELP/ASUMCEC datasets,
if "THIS SYSTEM" is in SMT MODE, but ONLY if there were
NO type 70 records for this "OTHER SYSTEM". Each RMF 70.
record has the details for THIS SYSTEM (70) and for THIS
LPAR (70PR), but only incomplete data in TYPE70PR for
each of the "OTHER LPARs" on the CEC this LPAR reports.
For ASUMCELP/ASUMCEC/TYPE70PR to be perfect, you must
read SMF 70 records for ALL SYSTEMS, so there will be a
"THIS SYSTEM" obs for every LPAR with complete data, and
if you do your own reporting from PDB.TYPE70PR you then
must select the "THIS SYSTEM" obs in TYPE70PR using:
IF PARTISHN=LPARNUM OR LPARNAME='PHYSICAL';
When you don't have 70s for all LPARS, the PDB.ASUMCELP
dataset has only "OTHER SYSTEM" incomplete data, where
these variables always have missing values:
SMF70LAC SMF70PAT SMF70WTS SMF70WTU SMF70WTI SMF70WLA
and where these variables have incorrect values:
LPARCPUS LPARDUR SMF70ONT LPCTBY LPCTOV SMF70WST
PCTZIPBY ZIPCPUS ZIPUPTM ZIPPATTM ZIPWSTTM.
Variable PARTISHN was not kept in PDB.ASUMCELP, but to
select only the "THIS SYSTEM" from PDB.ASUMCELP, use
IF SMF70PAT GT . OR ZIPPATTM GT .;
-Note that in the ASUMCELP dataset, MXG's NRCPUS should be
the number of CP engines ONLINE AND NOT PARKED, the true
capacity available, in the "THIS SYSTEM" LPAR obs. But in
"OTHER SYSTEM" obs, NRCPUS is the number of ONLINE CPs,
because the Parked time is not in the OTHER SYSTEM data.
(In RMF Partition Reports, IBM only reads THIS SYSTEM
so they have to use the ONLINE count, incorrectly,
to calculate the LPAR CPU utilization.)
-ARRAY statements with braces changed to parenthesis to
avoid character translation issues from ASCII to EBCDIC.
Thanks to Peter Sisak, T-SYSTEMS, GERMANY.
Thanks to Gabor Markon, T-SYSTEMS, GERMANY.
Thanks to Lorinc Homor, T-SYSTEMS, GERMANY.
Change 34.238 Example RMF III CPC data report.
ANAL3CPC
Oct 19, 2016
Change 34.237 New variables added to STCVSM11 dataset:
VMACSTC STC11NHW='BYTES*WRITTEN*HOST*INTERFACE'
Oct 12, 2016 STC11NHR='BYTES*WRITTEN*RTD*INTERFACE'
STC11NRR='BYTES*WRITTEN*IP*INTERFACE'
STC11NRW='BYTES*READ*HOST*INTERFACE'
STC11NIR='BYTES*READ*HTD*INTERFACE'
See Change 36.084 which corrected these variables.
Change 34.236 -If you have multiple SYSPLEX values on a single CEC or
VMXG70PR multiple capacity groups then ASUM70LP/ASUMCELP could
Oct 12, 2016 have invalid value unless you read all of the data from
all of the LPARs involved in the CEC. VMXG70PR now will
detect these conditions, WARN you about them and drop
the observations that are bad. There are two distinct
cases involved.
-If the LPAR is not part of the same plex as the system
that wrote the 70PR record then that OBS is dropped since
the weights will reflect the weights from the LPAR that
created the TYPE70PR record.
-If the LPAR is not found in the TYPE70 data you will get
a WARNING that there is missing data and some may be
erroneous for those LPARs that are missing but the OBS
are kept.
Change 34.235 Cosmetic. Variables DSGNAME and DVLSTGRP had '00'x pad
VMACDCOL characters if the name was less than eight bytes that are
Oct 11, 2016 now changed to blanks, and variable DSGCSMSS is labeled.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 34.234 MQ Series TYPE116 variable WQUSECNT, USE_COUNT, can be a
VMAC116 negative value (-1) to represent a CLOSE with (+1) OPEN,
Oct 11, 2016 so the INFORMAT &IB.4. is now used instead of &PIB.4.
Oct 19, 2016 Variable WTASPRCT is now correctly divided by 4096.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 34.233 TYPEXCOM format MGXCMST was not found due to a blank in
FORMATS the VALUE statement.
Oct 10, 2016
Thanks to Jim Horne, Lowe's Companies, Inc., USA.
======= Changes thru 34.232 were in this MXG 34.07 dated Oct 7, 2016===
Change 34.232 MXG 34.07 first iteration ERROR:ARRAY SUBSCRIPT OUT OF
VMAC7072 RANGE due to insufficient testing with enough data in
Oct 7, 2016 the TYPE70 Processing. My apology.
Thanks to Robert B. Richards, OPM, USA.
Change 34.231 MXG 34.07 first iteration lost an "@;" causing STOPOVER.
VMAC87 Datetimestamps are now converted to local, $CHARx fields
Oct 6, 2016 fields are properly $HEXxx formatted and SMF70DUR valid.
Thanks to Keith McWhorter,IBM Global Technology Services, USA.
======= Changes thru 34.230 were in this MXG 34.07 dated Oct 5, 2016===
Change 34.230 Corrections for CDHW support, INVALID DATA messages from.
VMACCDHW unprotected PD and PK fields.
Oct 5, 2016 -Oct 24. The INPUT of JULDATE was deleted causing missing
Oct 24, 2016 and/or wrong values.
Change 34.229 Support for DB2 V12 QWHS_MOD_LVL,_REC_INCOMPAT,REC_COMPAT
VMACDB2H variables INPUT in DB2 Header but not kept, and adjacent
VMACDB2 variable QWHCJOBSTEP that is kept, only in DB2ACCT.
VMAC102 -New variables added to DB2STATS:
Oct 5, 2016 Q9STCTDA='DISPLAY*ACCEL*COMMANDS'
Q9STCTSA='START*ACCEL*COMMANDS'
Q9STCTXA='STOP*ACCEL*COMMANDS'
Q9STLEN altered to match data, 220 read, Q9STLEN=256.
-New Contiguous Buffer Pool variables in DB2STATB
QBSTAGET='OVERFLOW*TOTAL*RANDOM*GETPAGES'
QBSTASGE='OVERFLOW*TOTAL*SEQUENTIAL*GETPAGES'
QBSTASYN='OVERFLOW*TOTAL*SYNC READ*RANDOMS'
QBSTASSE='OVERFLOW*TOTAL*SYNC READ*SEQUENTIAL'
-QJSTLEN test changed to 256 from 268, +116 VS avail128.
-LENQISE test GE 232 changed from 32.
-New variables in T102S053 and T102S058:
QW0053SECTN='RDI*SECTION*NUMBER'
QW0058SECTN='RDI*SECTION*NUMBER'
-New variables in T102S199, microsecond resolution.
QW0199S1='AVERAGE*SYNC*I/O*DELAY'
QW0199S2='MAXIMUM*SYNC*I/O*DELAY'
QW0199A1='AVERAGE*ASYNC*I/O*DELAY'
QW0199A1='MAXIMUM*ASYNC*I/O*DELAY'
-Five new DSNDQXST variables are kept in DB2ACCT and in
DB2STATS:
QXREFTBL ='REFRESH TABLES'
QXTRNOWN ='TRANSFER*OWNERSHIP*AVAILABLE'
QXRSDMAD ='DM NOT CALLED RAI PREDETERMINE'
QXR1BOAD ='FETCHED ONE BLOCK AN NEVER MORE '
QXSTSFND ='PREPARE SATISFIED FROM SYSDYNQRY'
-New fields are added to the end of QW0018 segment
QW0018SK='DATA ROWS SKIPPED*INCOMPATIBLE*LOCK HELD'
QW0018FI='DATA ROWS INSERTED*VIA*FAST INSERT'
QW0018FS='DATA ROWS*COULD NOT*USE FAST INSERT'
QW0018FA='DATA FAST INSERT*PIPE*REFILLS'
QW0018FW='DATA DB2 WAITS*FOR FAST*INSERT'
QW0I18SK='INDEX ROWS SKIPPED*INCOMPATIBLE*LOCK HELD'
QW0I18FI='INDEX ROWS INSERTED*VIA*FAST INSERT'
QW0I18FS='INDEX ROWS*COULD NOT*USE FAST INSERT'
QW0I18FA='INDEX FAST INSERT*PIPE*REFILLS'
QW0I18FW='INDEX DB2 WAITS*FOR FAST*INSERT'
-The below TYPE 102 IFCID updates can't be made until test
SMF data is available; DB2 DSECTS do not document the
internal format (TODSTAMP?/SMFSTAMP?/DB2INTERNAL?) nor
the epoch date, showing then as only CHAR8 in the DSECT.
-New IFCIDS: 389 380 404 413 414 477
-Changed IFCIDS: 018 125 316 401 53 58 with these notes:
IFCID 018 Statistics Class 1 Insert Algorithm 2
IFCID 058 Statistics Class 1 Insert Algorithm 2
IFCID 316/401 new wait times for Child/Page/L-Locks/P-
IFCIDs 53/58 statement level section for PREPARE
Change 34.228 Support for APAR OA48688, ABSOLUTE MSU LPAR GROUP CAPPING
VMAC7072 -TYPE70 new variable SMF70ABSMSU='Y' from SMF70HHF bit if
Oct 4, 2016 active for this partition.
-TYPE70PR new variables
CAPLIMCH='HARDWARE GROUP CAPACITY LIMIT CHANGED?'
SMF70HGWGRNAME='HARDWARE GROUP OF THIS PARTITION'
SMF70HWGR_CAP_LIMIT='HARDWARE*GROUP*ABSLIMIT'
Change 34.227 The $MGSMFID used by ANALID to describe SMF records is
ANALID enhanced to identify which product creates the record and
FORMATS with better descriptions, and a footnote added that the
Oct 1, 2016 MXG member IMACAAAA contains the MXG Product Suffix XXXX
each SMF Record Type, so you know what TYPEXXXX member to
use to process that SMF record. (Each IMACxxxx member has
the list of datasets that will be created for each XXXX.)
Thanks to MP Welch, Bank of America, USA.
Change 34.226 -Support for alternate SYSIN ddname input, user control
ADOCRMFV of VSAM CLOSE=FREE for RMF III data sets, and other
ASMRMFV improvements.
Oct 3, 2016 -A new keyword SYSIN=ddname allows ASMRMFV to input
parameters from a file with a ddname other than SYSIN.
This may be useful if ASMRMFV is executed under another
program such as SAS.
-The ddname must be a valid ddname for use in JCL and must
be present in the execution JCL or an error is flagged.
-SYSIN=ddname may ONLY appear in the JCL PARM= field NOT
in the SYSIN stream itself. Otherwise an error is
flagged.
-The SYSIN=ddname value must NOT be a reserved DDNAME used
by z/OS, JES2/JES3, or other important programs. If such
a ddname is used an error is flagged. For a full list of
these ddnames see documentation Section 5 "Input Data
Control Parameters" by SYSIN=ddname.
-The OPEN of the DCB for SYSIN or an alternate ddname now
validates that DSORG=PS, RECFM=FB or RECFM=F, and
LRECL=80 are attributes for the input file to prevent I/O
errors and other undesirable behavior. If these criteria
are not met ASMRMFV abends during parameter processing.
-VFREE (alias VF) and NOVFREE (alias NOVF) are a pair of
new parameters that control how RMF Monitor III VSAM data
sets are processed when closed.
-VFREE deallocates each RMF III data set thus releasing
the SHR enqueue for each data set as processed before the
entire ASMRMFV step ends while NOVFREE keeps the enqueues
for all RMF III data sets until the complete step end.
-For step program names ASMRMF* or IKJEFT* (*=any valid
program name characters), the default is VFREE. NOVFREE
is the default for other step program names.
-VFREE/NOVFREE has been tested successfully under z/OS 2.2
but may not necessarily have effect in other z/OS
releases.
-A new RMFV037I message displays the status of Input
Control parameters SYSIN=ddname and VFREE/NOVFREE.
-The RMFV035* message did not fully support the
TABERR=WARN option. All table errors were counted as
Severe Errors rather than as Warnings.
-When the only table errors are SPG Internal Problem
errors the final return code will now be 0008 instead of
0016.
-SPG Internal Problem errors occur when a coded Storage
Group name is misspelled or is nonexistent in the RMF III
SGSPACE start up parameter. These are NOT fatal to the
MXG PDB build process. There simply are no observations
in the result ZRBSPG SAS data set in the PDB. The
SGSPACE Storage Group name(s) must be corrected for
ZRBSPG to have observations.
-TIOT ddname search performance is improved.
-There is a new Abend Reason Code 40 for a GETDSAB service
failure.
-Additional descriptive problem text is added for OPEN,
CLOSE, and RDJFCB service failure RMFV007S messages.
-ASMRMFV could Abend S0C4 if a non-VSAM data set was coded
with an RMFV*, RMFC*, or RMFD* DDNAME and then opened as
a VSAM data set. Now this condition will be detected and
an error flagged.
-A new additional RMFV008I message will now display the
PDS member name or GDG relative generation if coded in
JCL for a file.
-The MXG00 record version is raised from X'05' to X'06'
and a new Input Options section is added.
-SYSIN=ddname and VFREE/NOVFREE features are not supported
by ASMRMFV versions prior to MXG Change 34.226. If
specified a parameter error will be flagged.
-Documentation Section 20 is retitled as "FREE=CLOSE for
VSAM Data Sets".
-Following documentation sections are
updated:
Section 5 "Input Data Control Parameters"
Section 8 "Error Handling Parameters"
Section 12 "Messages"
Section 14 "Skipped Records"
Section 16 "Return Codes"
Section 17 "Abend Reason Codes"
Section 20 "FREE=CLOSE for VSAM Data Sets"
Section 29 "Summary"
Change 34.225 If you used ANALHSM and do not have SAS/GRAPH and are on
ANALHSM SAS 9.2 or earlier, some graphic statements that should
Sep 30, 2016 have been bypassed caused error messages,
Change 34.224 Support for APAR OA50256 for TYPE1415 corrects SMF14DSVER
FORMATS field's values, from which MXG variable SMF14DSTYPE using
VMAC1415 the $MG014EF format, updated by this change. There was
Sep 30, 2016 no change made to VMAC1415; listed here for impact only.
Change 34.223 Support for APAR OA49415 for SuperPAV Support, adds data:
VMAC74 -Added to TYPE74 dataset:
VMAC78 2016 SUPERPAV='SUPERPAV*MODE?'
Sep 30, 2016 SMF74AGC='CONTROLLER*ALIAS*MANAGEMENT*GROUP*NUMBER'
SMF74AGS='ASSOCIATED*ALIAS*MANAGEMENT*GROUP*NUMBER'
-Added to TYPE78IO dataset:
R783GFLX='IOQ*GLOBAL*FLAGS*EXTENDED'
-Added to TYPE78CF dataset:
R783AMGC &PIB.1./*CONTROLLER*ALIAS*MGMT*GROUP*NUMBER*/
R783AMGS &PIB.4./*ASSOCIATED*ALIAS*MGMT*GROUP*NUMBER*/
-Added to TYPE78CU dataset:
R783XANC='ALIAS*NEEDED*TO START*AN I/O'
R783XAUC='ALIAS*USED*TO START*AN I/O'
R783XNHC='ALIAS*NEEDED*NONE*AVAILABLE'
R783XABC='ALIAS*BORROWED*FROM*PEER LCU'
R783XCBC='CONCURRENTLY*BORROWED*ALIAS'
R783XHBC='HWM*CONCURRENTLY*BORROWED*ALIAS'
R783XALC='ALIAS*LOANED*TO A*PERR LCU'
R783XCLC='CONCURRENTLY*LOANED*ALIAS'
R783XHLC='HWM*CONCURRENTLY*LOANED*ALIAS'
R783CNAG='BORROW*ATTEMPTS*NONE*AVAILABLE'
R783XCQD='CUM I/O*QUEUED*WHERE*ALIAS*NEEDED'
R783XCIU='CUM ALIAS*DEFINED*AND IN USE'
Change 34.222 Support for APAR OA51097 that documents new fields that
VMAC42 weren't in the SMF manual for SMF type 42 subtype 19.
Sep 30, 2016 Variables added to TYPE42X2 dataset:
SMF42JUC='LOW FIXED 4K PAGES IN USE'
SMF42JUD='HIGH FIXED 4K PAGES IN USE'
SMF42JUE='AVG FIXED 4K PAGES IN USE'
SMF42JUF='MAX FIXED STORAGE'
SMF42JUG='PCT REAL*CAN BE USED*FOR FIXED'
Variables added to TYPE42X4 dataset:
SMFA2JUC='LOW FIXED 4K PAGES IN USE'
SMFA2JUD='HIGH FIXED 4K PAGES IN USE'
SMFA2JUE='AVG FIXED 4K PAGES IN USE'
SMFA2JUF='MAX FIXED STORAGE'
SMFA2JUG='PCT REAL*CAN BE USED*FOR FIXED'
Change 34.221 Support for new SMF Type 29 IMS JAVA CPU and Garbage Coll
EXTY29GC creates new datasets
EXTY29JA DDDDDD MXG MXG
IMAC29 DATASET DATASET DATASET
TYPE29 SUFFIX NAME LABEL SUBTYPE
TYPS29
VMAC29 TY29GC TY29GC IMS JVM GARBAGE COLLECTION 2
VMXGINIT TY29JA TY29JAVA IMS JVM CPU USAGE 2
Sep 30, 2016 These members were added in MXG 34.01 Change 34.039 but
only now has VMAC29 been corrected and validated with
data records.
Thanks to Tony Curry, BMC, USA.
Change 34.220 WARNING R749PCIPAKTR in DROP KEEP RENAME never referenced
VMAC74 because it should have been spelled R749PCIPAKT. Warning
Sep 27, 2016 is printed only when the MXG OPTION DKROCOND=NOWARN is
changed to WARN; MXG expects/exploits DKROCOND=NOWARN as
it permits variable names in the KEEP= list that are not
output if their optional code is not enabled (especially
in CICSTRAN with its many possible optional variables.
Thanks to Andrew Krink, Northern Territory Government, AUSTRALIA.
Change 34.219 -Variables GDGCOMPL and GDGNOEXT and GDGLIMIT kept.
VMAC6156 -New undocumented catalog record '07' has two fields that
Sep 24, 2016 are input and kept for investigation.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 34.218 Arrays were incorrectly being initialized causing the
ASUM4HRS 4HR Averages to not be calculated and the resultant value
Sep 24, 2016 for each interval was the interval's value rather than
the average value. Note that if you request 4 Hours then
there will be no average calculated until the 5th Hour.
You may have to read TWO day's SMF to populate the 4 Hour
Average for all hours of today.
Thanks to Tony P. Steward, CSC, ENGLAND.
Change 34.217 -Dataset BVIR30 variables USDCACHE and USDFLASH were INPUT
VMACBVIR but were not kept.
Sep 22, 2016 -Datasets BVIR301 and BVIR302 were both wrong, having too
Sep 26, 2016 few observations and keeping wrong variables. BVIR301
now has one observation for each CACHEPARTNR (0 thru 7)
and BVIR302 one for each CONTAINER and Performance Group.
Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
Change 34.216 Support for SMF 98 High Frequency Throughput Statistics
EXTY9801 HFTS record creates nine new datasets. The TYPE9801 data
EXTY98EE set contains all of the segments that occur only once per
EXTY98LD record; the eight TYPE98SD-TYPE98SL data sets contain the
EXTY98LL segments that can occur more than once per record:
EXTY98LS
EXTY98PB DDDDDD MXG MXG
EXTY98SD DATASET DATASET DATASET
EXTY98SL SUFFIX NAME LABEL
EXTY98WU
FORMATS TY9801 TYPE9801 TYPE 98 HFTS SUBTYPE 1
IMAC98 TY98SD TYPE98SD HFTS SPINLOCK DETAIL
TYPE98 TY98LS TYPE98LS HFTS LOCK SUSPEND SUMMARY
TYPS98 TY98LD TYPE98LD HFTS LOCK SUSPEND DETAIL
VMAC98 TY98LL TYPE98LL HFTS LOCK LOCAL CML DETAIL
VMXGINIT TY98PB TYPE98PB HFTS PRIORITY BUCKET
Sep 20, 2016 TY98EE TYPE98EE HFTS CONSUME EXECUTION EFFICIENCY
Aug 17, 2016 TY98WU TYPE98WU HFTS CONSUME WORK UNITS
TY98SL TYPE98SL HFTS CONSUME SPIN LOCK SUMMARY
Thanks to Nicholas Jones, IBM, USA.
Thanks to Daniel V. Rosa, IBM, USA.
Change 34.215 Support for PRO/SMS (previously X37) Version 7.8 RSL1607
VMACPROS which INCOMPATIBLY replaced 60 bytes after PROCSTEP with
Sep 22, 2016 102 bytes, causing misalignment of all subsequent fields
but only impacting the PRORECOV dataset.
Thanks to Robert Chavez, Florida Power and Light, USA.
Change 34.214 New SMF fields documented in new Sept 2016 SMF Manual:
VMAC30 -VMAC30, datasets TYPE30_V/TYPE30_4/TYPE30_5/TYPE30_6:
VMAC42 new variable SMF30SLM='MEMLIMIT*ACTION*TAKEN*FLAGS'
VMAC74 -VMAC42, dataset TYPE42S1: was wrong, 16-bytes skipped.
VMAC79 new variable SMF42FY3='VALID*COUNTS*FLAGS'
VMAC90A Initially, I thought IBM had inserted 16 bytes but they
VMXGINIT have been there at least since z/OS 1.13. But, when I
EXTY9038 thought I was going to have to test for version, users
EXTA9038 found these values in their data:
EXTB9038
EXTY9039 PRODUCT SUBTYPES PRODLVL
Sep 18, 2016
CA PDSMAN 24 7.7.0
MVS/OS390 10 HDZ1D10
MVS/OS390 10 HDZ2220
Z/OS18 15/17/18/19 DFSMVS18
DFSMS/MVS 1/5/6 HDZ1D10
DFSMS/MVS 1/5/6 HDZ2220
DFSMS/MVS 4 1.3.0
MVS/DFP 2 HDZ1D10
MVS/DFP 2 HDZ2220
Z/OS DFSMS 9 1.12.0
Z/OS DFSMS 20/21/24 V01R13M0
Z/OS DFSMS 20/21/24/25 V02R02M0
Z/OS DFSMS 27 HZD2220
-VMAC42, dataset TYPE42S2 new variables:
SMF42FSH='COMP1*CLASS4*LOCKS'
SMF42FSI='COMP1*CLASS4*TRUE*CONTENTION'
SMF42FSJ='COMP1*CLASS4*FALSE*CONTENTION'
SMF42FSK='COMP1*CLASS4*RELEASE*LOCKS'
-VMAC42, dataset TYPE42S3 new variables:
SMFA2FPHA='COMP1*CLASS4*LOCKS'
SMFA2FPIA='COMP1*CLASS4*TRUE*CONTENTION'
SMFA2FPJA='COMP1*CLASS4*FALSE*CONTENTION'
SMFA2FPKA='COMP1*CLASS4*RELEASE*LOCKS'
-VMAC74, dataset TYPE74CA new variable
R745CFDV='FAILING*DEVICE'
-VMAC77, dataset TYPE77 new variables
SMF77CSC='CONTENTION*STATUS*CHANGE*EVENTS'
SMF77NOD='NO*SEPARATE*CONTENTION*DETAIL'
-VMAC79, variables R79ETCMW/R79ECTRD could be missing
values, test for APAR additions revised.
-VMAC90A, Support for new datasets from new subtypes:
TY9038 TYPE9038 38:SET IEFOPZ
TYA038 TYPE9038A 38A:OLD NEW DSNAME
TYB038 TYPE9038B 38A:DD JOBNAME
TY9039 TYPE9039 39:SET SMFLIM
Change 34.213 Support for the SMF 119 Subtype 81 Intrusion Detection
EXT11981 Service creates new dataset
FORMATS DDDDDD DATASET DESCRIPTION
IMAC119 T11981 TYP11981 INTRUSION DETECTION SERVICE
VMAC119
VMXGINIT
Sep 16, 2016
Thanks to Nathan Loewenthal, CitiGroup, USA.
Change 34.212 The ANALID report value for MVSLEVEL was incorrectly read
VMACSMF when the VSAM SMF file was input; an +OFFSMF was needed.
Sep 16, 2016
Thanks to MP Welch, Bank of America, USA.
Change 34.211 Support for SMF 80 TOKDANAME='TOKMFILEPROCMAX' adds new
VMAC80A variable TOKMFILEPROCMAXNR.
Sep 15, 2016
Thanks to Robert Chavez, Florida Power and Light, USA.
Change 34.210 Some USS RACF Event values (28 thru 58 decimal) were not
FORMATS decoded in MG080EV and $MGSMFID formats.
Sep 15, 2016
Thanks to MP Welch, Bank of America, USA.
Change 34.209 "DB2 is filling my SMF, how do I find out who/why" may be
DB2COUNT answered with DB2COUNT program that reads SMF 101 records
Sep 13, 2016 creating a stripped down PDB.DB2ACCT with the identity
variables and PROC FREQs to provide counts of who/why and
then ANALDB2T reports on the top resource consumers.
Change 34.208 -These compression Rate variables were labeled "MB PERSEC"
VMAC74 but they contained bytes. Now they are in MB Per Second:
Sep 11, 2016 R749PCIDMAR/MAW R749FPGCOBS/DCBS R749PCIBYTR/BYTT
R749FPGBYTS. And R749FPGBYTR Average Request is now KB.
-Variable R749FPGBPRT is now equated to R7491BPC for the
Buffer Pool utilization.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 34.207 VMXGRMFI summarization with large INTERVAL= DATE or SHIFT
VMXGRMFI or even TWOHOUR could produce incorrect results with no
Sep 14, 2016 error messages. The value of SHIFT could be incorrect,
which could cause the date to be one day wrong. Only
user-created invocation of VMXGRMFI are exposed; none of
the MXG-supplied VMXGRMFI members have large intervals.
-The exposure is when the requested INTERVAL spanned a
shift boundary or did not align perfectly with the shift
times; to get FOURHOUR FOURHOUR summary you must have
SHIFT boundaries of at 0/4/8/12/16/20.
-Using INTERVAL=SHIFT produced wrong results if your
interval spans a shift boundary, but it is likely that
what you really wanted was by DATE and SHIFT, so VMXGRMFI
has new INTERVAL=DATESHIFT/WEEKSHIFT/MONTHSHIFT/
MONTHSHIFT/QUARTERSHIFT/SEMIANNSHIFT/ANNUALSHIFT. These
new options set the INTERVAL=DATE/WEEK/etc., and add
variable SHIFT to the end of the SUMBY list. In
addition, new &RMFIBY macro variable with default
RMFIBY=SYSPLEX SYSTEM SYSNAME STARTIME
is created to allow more extensive tailoring if needed.
If you use this interval structure (xxxxSHIFT) you must
also use the same RMFIBY to put the resulting data
through TRENDing to preserver the SHIFT value.
-SHIFT added to the RMFWKLRV dataset.
-SHIFT is blank for INTERVAL= that span shifts (DATE, etc)
since there is no value possible with multiple shifts.
-Two PROC SORTs were replaced by MEANS with CLASS..
-If Reporting Classes are used for Workload Definitions,
the WKLDDESC='REPORTING CLASS' value is set for that
variable because they don't have WLM WORKLOAD values.
-Messages that SRVCLASS='SYSOTHER' was found in TYPE72GO
input are now always printed; this is NOT due to MXG but
is a fall-thru service class used by IBM when your WLM
rules failed to classify work, and should never exist.
Thanks to Andre Gustavo Moretto, IBM Global at Delta, USA.
Change 34.206 -Support for Top Secret R15. Changed was RACFVRSN='F0'x.
VMAC80A Without change, dataset TYPE80TS had zero observations.
Sep 7, 2016 -Support for Top Secret R16. Added RACFVRSN='10'x test on
Oct 5, 2016 Oct 5.
Nov 5, 2016 -Format $MG080TS created to map Resource Code to Class by
FORMATS reading the RDT.TXT table. A program to re-create that
format is in comments at the end of this VMAC80A.
Thanks to Carl D. Ellis, Wells Fargo, USA.
Change 34.205 SMF 6 UNDECODED KEYS and INPUT EXCEEDED STOPOVER error
IMAC6ESS because MXG only expected 4 USERLIB segments. ESSULIB5/6
VMAC6 are now input and kept and more than 6 now protected.
Sep 6, 2016
Thanks to Sabrina Mandelatz, ProvinzialRheinlandVersicherung, GERMANY
Change 34.204 -Variable SHIFT is added to RMFWRKLV DATASET in VMXGRMFI.
VMXGRMFI -TRND70PR incorrectly used variable name DATETIME when it
TRND70PR should have used STARTIME in the SUMBY list, which worked
Sep 2, 2016 accidentally.
Oct 2, 2016 -STARTIME removed from ID statement Oct 2.
Thanks to Andre G. Moretto, Delta Air Lines, USA.
Change 34.203 Cosmetic. All "CICS EXCLUDED FIELDS FOUND" messages now
VMAC110 contain the READTIME value of that APPLID, which is when
Sep 2, 2016 the CICS Dictionary Record is written, so you know what
SMF data to select for UTILEXCL
Change 34.202 Support for Connect Direct Simultaneous Session CDHW SMF
EXCDHWSS creates new dataset
IMACCDHW DDDDDD DATASET DESCRIPTION
TYPECDHW CDHWSS CDHWSSES CD SIMULTANEOUS SESSIONS
TYPSCDHW
VMACCDHW
VMXGINIT
Aug 29, 2016
Thanks to Scott Wiig, USBank, USA.
Thanks to David Magoon, USBank, USA.
Change 34.201 Support for CDI-NDM Version 5.2 (INCOMPATIBLE).
VMACNDM Incomplete, not moved to 34.07, no data yet.
Aug 29, 2016
Thanks to Michael Oujesky, DTCC, USA.
Change 34.200 -SMF 115 dataset MQMLOG is enhanced with new variables
VMAC115 QWHSDURN='INTERVAL*DURATION'
VMACDB2H PCTLOGBY='PERCENT*LOG*BUSY'
Aug 24, 2016 QWHSTIME='MQ*INTERNAL*START*DATETIME'
Sep 13, 2016 -Sep 13: Protection for old versions with QWHSLEN=36 added
Sep 16, 2016 and missing values calculations eliminated.
Sep 22, 2016 -Sep 16: Variables added to MQMLOG dataset:
Sep 24, 2016 QJSTSLPTU ='PHYSICAL*WRITER*SLEEP*DURATION'
Oct 11, 2016 QJSTIOSQU1='SSQ*IO TIME*1ST HALF'
QJSTIOSQU2='SSQ*IO TIME*2ND HALF'
-Sep 22: QJST busy time is now created and calculated as
QJSTBUSY=100*(QWHSDURN-QJSTSLPTU)/QWHSDURN;
-Sep 24: GMT115TM is now correctly calculated and used to
shift the QJSTIOMAXxxxx datetimestamps to LOCAL zone.
-Oct 11: Labels improved for vars QJSTBUSY, QJSTSLPTU.
Thanks to Carolina W. Sumilang, DTCC, USA.
Thanks to Joseph J. Faska, DTCC, USA
Change 34.199 -RMF III dataset ZRBDVT variable DVTLCUNR was always zero
VMACRMFV and DVTSAMPP was trashed, due to mis-alignment in MXG.
Aug 24, 2016 -Variable DVTSSID='SUBCHANNEL*SET' is now INPUT and KEPT.
Aug 30, 2016 -Variable GEIAHUIC is now INPUT as Floating Point.
-Variable GEIFLG1 is now INPUT and KEPT.
======= Changes thru 34.198 were in MXG 34.06 dated Aug 18, 2016========
Change 34.198 -Enhancement for Relative Time filtering for FROMTIME=
ADOCRMFV and TOTIME= parameters using the current Time of Day
ASMRMFV (TOD) timestamp.
Aug 18, 2016 -The TOD value as shown in the ASMRMFV RMFV001I log
Aug 20, 2016 message and obtained as execution begins is the basis for
Relative Time calculations.
-Relative Times are specified as either hour or minute
offsets from the current TOD. The default is hours if
the unit is not explicitly coded.
-Improved handling of midnight crossover condition when
Relative Time offset exceeds current TOD Time.
-All of the following formats are supported for FROMTIME=
Relative Times:
FROMTIME=*- FROMTIME=- FROMTIME=*-
FROMTIME=*-0 FROMTIME=-0
FROMTIME=*-00 FROMTIME=-00
FROMTIME=*-0H FROMTIME=-0H
FROMTIME=*-00H FROMTIME=-00H
FROMTIME=*-0M FROMTIME=-0M
FROMTIME=*-00M FROMTIME=-00M
FROMTIME=*-000M FROMTIME=-000M
FROMTIME=*-0000M FROMTIME=-0000M
h is hours (0-9) hh is hours (00-24)
m is minutes (0-9) mm is minutes (00-99)
mmm is minutes (000-999) mmmm is minutes (0000-1440)
-The maximum hour offset supported is 24 hours.
The maximum minute offset supported is 1440 minutes.
-'H' suffix is optional for hour offsets.
'M' suffix is required for minute offsets.
-The default offset is 0 hours for these formats:
FROMTIME=* FROMTIME=*- FROMTIME=-
-The following forms for FROMTIME= all result in the
current TOD being used as a data selection start
time:
FROMTIME=*- FROMTIME=- FROMTIME=*-
FROMTIME=*-0 FROMTIME=-0
FROMTIME=*-00 FROMTIME=-00
FROMTIME=*-0H FROMTIME=-0H
FROMTIME=*-00H FROMTIME=-00H
FROMTIME=*-0M FROMTIME=-0M
FROMTIME=*-00M FROMTIME=-00M
FROMTIME=*-000M FROMTIME=-000M
FROMTIME=*-0000M FROMTIME=-0000M
-These forms are of no practical use when FROMDATE=*
(current date) is also coded because the selection start
time will result in little if any data being actually
output.
-The use of Relative Time with FROMTIME= does not change
the FROMDATE= value whether defaulted or coded. These
two parameters remain independent.
-The Relative Time process for FROMTIME= follows these
steps:
-1. The hour or minute time offset requested is deducted
from the time portion of the current TOD clock value.
-2. If the result of the time offset deduction is negative
and the active FROMDATE= value also the current date,
then the FROMTIME= value is forced to 00:00:00.000000
(midnight).
-3. If the result of the offset deduction is negative and
the active FROMDATE= value is NOT the current date, then
the portion of hours or minutes that exceeds the elapsed
time for the current date crosses midnight. See example
below for more detail.
-To summarize the midnight crossing support where '*'
represents the current date:
FROMTIME=
FROMDATE= Time Offset Result
--------- ------------- ------------------
* LE Current TOD Midnight cross N/A
* GT Current TOD FROMTIME 00:00:00.000000
Not * LE Current TOD Midnight cross N/A
Not * GT Current TOD Midnight crossed
The midnight cross time is calculated as:
Current time - FROMTIME time offset + time in 1 day
-4. The FROMTIME= value for an hours offset is truncated
to the start of the hour while the FROMTIME= value for a
minutes offset is truncated to the start of the minute.
This is a practical aid to prevent data selection
from beginning at an odd time.
-To summarize the Relative Time results for
FROMTIME=:
TIME TRUNCATED
OFFSET UNIT FROMTIME=
----------- ---------------
Default (Hours) HH:00:00.000000
H (Hours) HH:00:00.000000
M (Minutes) HH:MM:00.000000
-Examples for FROMTIME= Relative Time usage follow.
For these examples assume the current TOD is:
DATE=2016.251 01SEP2016 THU TIME=09:26:56.776233
-Example 1: FROMDATE=* FROMTIME=*-3
is a 3 hour TOD Relative Time offset for the current day
results in:
FROM DATE=2016.251 01SEP2016 THU TIME=06:00:00.000000
TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999
Note that a pure offset of 3 hours only would have
resulted in a FROMTIME= of 06:26:56.776233 which is an
awkward time stamp for the start of data selection. So
the start of the hour is provided.
-Example 2: FROMDATE=* FROMTIME=*-10
is a 10 hour TOD Relative Time offset and results in:
FROM DATE=2016.251 01SEP2016 THU TIME=00:00:00.000000
TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999
since the Relative Time offset extends beyond midnight
into the prior day and FROMDATE= is the current date,
the FROMTIME= was forced to midnight.
-Example 3: FROMDATE=*-1 FROMTIME=*-10
is a 3 hour current TOD Relative Time offset with a
FROMDATE= of yesterday and results in:
FROM DATE=2016.250 31AUG2016 WED TIME=23:00:00.000000
TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999
since FROMDATE= is NOT the current date, the FROMTIME=
offset is allowed to cross midnight by 1 hour in this
example. To achieve the cross midnight time behavior
FROMDATE= must NOT be the current date.
-To use the midnight crossing feature effectively a user
must anticipate a midnight crossover based on the size of
the Relative Time FROMTIME= offset being used and when
ASMRMFV is going to be run. Usually FROMDATE=*-1 is
coded rather than FROMDATE=* if the midnight time
crossover is expected.
-However, any FROMDATE= value that is not the current date
may be used and the midnight crossing will still occur.
-Example 4: FROMDATE=* FROMTIME=*-30M
is a 30 minute current TOD Relative Time offset and
results in:
FROM DATE=2016.251 01SEP2016 THU TIME=08:56:00.000000
TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999
-Example 5: FROMDATE=* FROMTIME=30M
is a parameter error because at least the '-' character
must follow FROMTIME= to indicate a Relative Time.
ASMRMFV will abend.
-All of the following formats are supported for TOTIME=
Relative Times:
TOTIME=*
TOTIME=*- TOTIME=-
TOTIME=*-h TOTIME=-h
TOTIME=*-hh TOTIME=-hh
TOTIME=*-hH TOTIME=-hH
TOTIME=*-hhH TOTIME=-hhH
TOTIME=*-mM TOTIME=-mM
TOTIME=*-mmM TOTIME=-mmM
TOTIME=*-mmmM TOTIME=-mmmM
TOTIME=*-mmmmM TOTIME=-mmmmM
-The meanings for h, hh, m, mm, mmm, mmmm, H, and M are
the same as for the FROMTIME= parameter.
-Hour and minute offset limits are the same as for
FROMTIME= Relative Times.
-'H' suffix is optional for hour offsets
'M' suffix is required for minute offsets
-The default offset is 0 hours for these formats:
TOTIME=* TOTIME=*- TOTIME=-
-The following forms for TOTIME= all result in the
current TOD being used as a data selection end time:
TOTIME=*- TOTIME=- TOTIME=*-
TOTIME=*-0 TOTIME=-0
TOTIME=*-00 TOTIME=-00
TOTIME=*-0H TOTIME=-0H
TOTIME=*-00H TOTIME=-00H
TOTIME=*-0M TOTIME=-0M
TOTIME=*-00M TOTIME=-00M
TOTIME=*-000M TOTIME=-000M
TOTIME=*-0000M TOTIME=-0000M
-However, when TODATE=* is also used it is unnecessary to
code these forms because the default TOTIME= is:
DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999
-The use of Relative Time with TOTIME= does not change the
TODATE= value whether defaulted or coded. These two
parameters remain independent.
-The Relative Time process for TOTIME= follows these
steps:
-1. The hour or minute time offset requested is deducted
from the time portion of the current TOD clock value.
-2. If the result of the offset deduction is negative and
the active TODATE= value is also the current date, then
the TOTIME= value is forced to 00:00:59.999999.
-3. If the result of the offset deduction is negative and
the active TODATE= value is NOT the current date, then
the portion of hours or minutes that exceeds the elapsed
time for the current date crosses midnight. See example
below for more detail.
-To summarize the midnight crossing support where
'*' represents the current date:
TOTIME=
TODATE= Time Offset Result
--------- ------------- ------------------
* LE Current TOD Midnight cross N/A
* GT Current TOD TOTIME 00:00:59.999999
Not * LE Current TOD Midnight cross N/A
Not * GT Current TOD Midnight crossed
The midnight cross time is calculated as:
Current time - TOTIME time offset + time in 1 day
-4. The TOTIME= value for an hours offset is truncated to
the start of the hour while the TOTIME= value for a
minutes offset is truncated to the start of the minute
depending on the time offset unit. In either case
00:00:59.999999 is added to the result.
-TOTIME= values are set with 59.999999 seconds as the last
part of the time stamp so that any data time stamped
within the minute is sure to be selected. TOTIME= in
ASMRMFV has always been inclusive of the entire end
minute.
-5. However, if the time offset is zero then the final
time value is only adjusted to the end of the minute
whether the time offset unit is in hours or minutes.
-To summarize the adjustment with non-zero TOTIME=
offsets:
TIME FINAL
OFFSET UNIT TOTIME=
----------- ---------------
Default (Hours) HH:00:59.999999
H (Hours) HH:00:59.999999
M (Minutes) HH:MM:59.999999
-To summarize the adjustment with a zero TOTIME=
offset:
TIME FINAL
OFFSET UNIT TOTIME=
----------- ---------------
Default (Hours) HH:MM:59.999999
H (Hours) HH:MM:59.999999
M (Minutes) HH:MM:59.999999
-Examples for TOTIME= Relative Time usage follow.
For these examples assume the current TOD is:
DATE=2016.251 01SEP2016 THU TIME=09:26:56.776233
-Example 1: TODATE=* TOTIME=*-3
is a 3 hour current TOD Relative Time offset and results
in:
FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000
TO DATE=2016.251 01SEP2016 THU TIME=06:00:59.999999
-Example 2: TODATE=* TOTIME=*-10
is a 10 hour current TOD Relative Time offset and results
in:
FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000
TO DATE=2016.251 01SEP2016 THU TIME=00:00:59.999999
since the Relative Time offset extends beyond midnight
into the prior day and TODATE= is the current date, then
the TOTIME= was forced to midnight + 00:00:59.999999 .
-Example 3: TODATE=*-1 TOTIME=*-10
is a 10 hour current TOD Relative Time offset with a
TODATE= of yesterday and results in:
FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000
TO DATE=2016.250 31AUG2016 WED TIME=23:00:59.999999
since TODATE= is NOT the current date, the TOTIME= offset
is allowed to cross midnight by 1 hour in this example.
To achieve the cross midnight time behavior TODATE= must
NOT be the current date.
-To use the midnight crossing feature effectively a user
must anticipate a midnight crossover based on the size of
the Relative Time TOTIME= offset being used and when
ASMRMFV is going to be run. Usually TODATE=*-1 is coded
rather than TODATE=* if the midnight time crossover is
expected.
-However, any TODATE= value that is not the current date
may be used and the midnight crossing will still occur.
-Example 4: TODATE=* TOTIME=*-30M
is a 30 minute current TOD Relative Time
offset and results in:
FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000
TO DATE=2016.251 01SEP2016 THU TIME=08:56:59.999999
-Example 5: TODATE=* TOTIME=30M
is a parameter error because at least the '-' character
must follow TOTIME= to indicate a Relative Time. ASMRMFV
will abend.
-Documentation Section 5 "Input Data Selection Parameters"
is updated to explain use of Relative Times for FROMTIME=
and TOTIME= parameters.
-The Relative Time feature is not supported by earlier
ASMRMFV versions prior to MXG Change 34.198. If
specified a parameter error will be flagged.
Change 34.197 More Support for BE93 Version 6.1.0 (INCOMPATIBLE) due to
VMACBETA changed BETAFLAG that contains '81'x, but the MXG test
Aug 19, 2016 for the extended header existence tested for '80'x, and
there were new fields inserted in the subtype=1 record
causing misalignment and invalid values in BETA1 dataset.
Thanks to Sabrina Mandelatz, Provinzial Rheinland Versicher, GERMANY
Change 34.196 -SMF 78 ST3 INPUT STATEMENT EXCEEDED when APAR OA44525
VMAC78 zHPF Extended Distance II is installed, MXG 33.07-34.05,
Aug 18, 2016 because MXG Change 33.156 for that APAR incorrectly had
INPUT R783TMWM/R783TRDM in the DCS segment for TYPE78CF,
but that APAR had added those fields in the ASS segment.
MXG properly INPUTs them and keeps them in TYPE78CU
instead of TYPE78CF. The STOPOVER ABEND that results
can be circumvented adding MACRO STOPOVER MISSOVER %
statement at the top of your //SYSIN, and/or you can
request just the VMAC78 member from support@mxg.com
-Added May 2017: This change caused a massive increase in
the number of observations in TYPE78CF; prior code read
only output the first CU (8 obs/record) but there are 356
obs typically in each record.
-Unrelated, APAR OA49415 added new fields now in TYPE78CU:
R783AMGC='ALIAS*MGMT*GROUP*NUMBER*PHYSICAL CU'
R783AMGS='ALIAS*MGMT*GROUP*NUMBER*THIS LCU'
Thanks to Gadi Ben-Avi, MALAM, ISREAL.
Change 34.195 TMON/CICS new variables TASZIPTM and TASELGTM created and
VMACTMO2 kept in MONITASK dataset, and TASCPUTM is corrected to
Aug 15, 2016 contain ONLY the CP CPU time (previously it had the sum
of CP and zIIP time).
And, only for TMON 3.4, TASCPOT/TASCPUT were not divided
by 4096.
Change 34.194 Support for SMF 99 Subtype 1 additional segments create
EXTY99SL new datasets:
EXTY99ST DDDDDD DATASET DESCRIPTION
EXTY99PT TY99SL TYPE99SL SOFTWARE LICENSING
EXTY99PI TY99ST TYPE99ST SOFTWARE LICENSING TABLE
EXTY99ZE TY99PT TYPE99PT CP PRIORITY TABLE
EXTY99PS TY99PI TYPE99PI ZAAP PRIORITY TABLE
VMAC99 TY99ZE TYPE99ZE ZIIP ENTITLEMENT
VMXGINIT TY99PS TYPE99PS ZIIP PRIORITY TABLE
Aug 13, 2016 The new TYPE99SL dataset has the new Hardware Absolute
Group Capping metrics added by APAR OA47752.
-Variable S99BUNUS in TYPE99BG can now be negative MSU
when capped.
Thanks to Scott Wiig, USBank, USA.
Thanks to Tony P. Steward, CSC, ENGLAND.
Change 34.193 HSM SMF VSR records with '62'x instead of the "S" in VSR
VMACHSM test field printed "INVALID HSM RECORD" messages and the
Aug 12, 2016 (six out of 100) records were skipped. Now, if DSRVSR
Jan 3, 2017 is NOT DSR but starts with a V, the record will be read
as a VSR record, while IBM HSM Support investigates.
-Turns out this had nothing to do with HSM, but was an
error that touched man SMF records, if you used LOGGER
and had a MAXBUFSIZE that was NOT 65532. APAR OA51823.
Thanks to Scott Wiig, USBank, USA.
Change 34.192 RMF III variable GMTOFF is now kept in each ZRB dataset
VMACRMFV to aid in processing data from multiple timezones. It is
Aug 11, 2016 INPUT from each SSH record and retained for all of the
following records in that interval.
(Only the first SSH record is output in ZRBSSH by logic
in member EXZRBSSH).
Thanks to MP Welch, Bank of America, USA.
Change 34.191 -Enhancement for character data filtering for RMF Monitor
ADOCRMFV III SPG (Storage Group and Volume Data) table and other
ASMRMFV usability improvements.
VMACRMFV -These filters are intended for building ad hoc MXG RMF
Aug 11, 2016 III PDBs for studies to avoid the overhead of generating
a full SPG table based PDB. They control which SPG table
entries are output to the RMFBSAM file.
-Please see the new documentation Section 28 "Collection
of DASD Usage with RMF Monitor III" in the ADOCRMFV
member or ASMRMFV source member for the requirements and
setup of DASD usage measurement in the SPG table. There
are multiple Storage Group name entries in the SPG each
with many Volume Data entries when collection is active.
-Four new filters are added to support SPG entry selection
from this table to the RMFBSAM output file. These
filters are effective only if the SPG table is selected.
New Keyword Aliases
------------- -----------------------------------------
SPGSTORGROUP= SPGSTORGRP=, STORGRUP=, SPGGRP=, SGPSNM=,
SPGSG=
SPGVOLSER= SPGVOLI=, SPGVOL=, SPGSER=, SPGV=
SPGAND None
SPGOR None
The order of SPG filter application when both keywords
are present is:
1) SPGSTORGROUP= (or any alias for SPGSTORGROUP=)
2) SPGVOLSER= (or any alias for SPGVOLSER=)
Selection results from repeats of the same SPG filter
keyword (or any of its aliases) are always logically
ORed.
-TUTORIAL:
Ranges of the form keyword=first:last may be used with
any of the above keywords except SPGAND and SPGOR.
The colon character ':' is required for a paired range
specification. All entries GE the first value and LE the
last value are selected for output to the RMFBSAM file.
The first value may not exceed the last value in EBCDIC
collating sequence or an error is flagged in message
RMFV056E.
Single unpaired values may be specified for a range
simply as keyword=first and in this case the colon ':' is
omitted.
Patterns may also be used with any of the above keywords
except SPGAND and SPGOR and include one or more Wild Card
characters to match the respective SPG data field.
A pattern contains one or more special Wild Card
characters as follows:
Wild
Card Matches
---- -------------------------------------------------
* 0 or more characters
% 1 Non-blank character
+ 1 Numeric character (0-9)
_ 1 Alphabetic character or _ (a-z, A-Z, _)
. 1 National character (@, #, $)
! 1 Special character (not a-z, A-Z, 0-9, @, #, $)
? A blank string if used by itself
? 1 Blank character (X'40') if used with any other
characters
Ranges may not be wild carded. If wild carded the range
value becomes a pattern instead and is processed as such.
See Section 25 "Ranges and Patterns" in the ADOCRMFV
member or ASMRMFV source code for more details on usage
of ranges and patterns.
-SPGSTORGROUP= (or any of its aliases) selects SPG Storage
Group name entries from 1-8 characters. Storage Group
names are defined for System Managed Storage (SMS) and
are 1-8 alphabetic characters including A-Z, 0-9, $, @,
#, *, or %. The first character must be alphabetic
(A-Z). Both ranges and patterns with wild cards may be
specified. Up to 64 ranges and 64 patterns are
supported. The default is SPGSTORGROUP=ALL.
-In all of the following examples assume the following
Storage Group names and Volume Serials are defined to SMS
in this highly simplified configuration and that RMF
Monitor III is actively measuring them:
Storage Volume
Group Serials
-------- ---------------------------
PRODPOOL PRD001 PRD002 PRODAA PRODBB
TESTPOOL TST001 TST002 TESTAA TESTBB
WORKPOOL WRK001 WRK002 WORKAA WORKBB
-Examples for SPGSTORGROUP= :
SPGSTORGROUP=PRODPOOL:TESTPOOL is a range that selects
only Storage Groups with a name GE 'PRODPOOL' and LE
'TESTPOOL'. All the volume serials in these pools will
be selected. No volumes in WORKPOOL are selected.
SPGSG=P* is a pattern that selects only Storage Group
names that begin with 'P'. Only volumes from the
PRODPOOL are selected. Note use of the keyword alias
SPGSG= for coding convenience.
STORGRUP=A* is a pattern that selects only Storage Groups
with a name that begins with an 'A'. No Storage Groups
will be selected in this example. Note use of an alias.
SPGGRP=*L is a pattern that selects only Storage Groups
with a name that ends with 'L'. All Storage Groups will
be selected in this example. This is the default if no
filter keywords are coded. Note use of an alias.
See Section 25 "Ranges and Patterns" in the ADOCRMFV
member or ASMRMFV source code for more details on usage
of ranges and patterns.
-SPGVOLSER= (or any of its aliases) selects SPG entries by
Volume Serial number. Both ranges and patterns with wild
card characters may be specified. Up to 64 ranges and 64
patterns are supported. The default is SPGVOLSER=ALL.
Any valid 1-6 character Volume Serial with or without
pattern characters may be specified. Per JCL syntax a
Volume Serial Number is 1 through 6 alphanumeric,
national ($,#,@), or special characters.
NOTE: Since just about any keyboard character is valid in
a Volume Serial please take extra care when coding to
avoid unintended results in the MXG PDB data set ZRBSPG.
NOTE: Data filtering by Volume Serial only is much less
efficient than filtering by Storage Group because every
volume in every Storage Group must be matched against the
ranges and patterns provided. There are usually many
more volumes than Storage Groups. Use of SPGSTORGROUP=
instead is recommended if feasible.
NOTE: If one or more SPGVOLSER= filters is coded and a
Storage Group has zero volume data entries the Storage
Group is filtered as this is considered a mismatch.
-Examples for SPGVOLSER=
SPGVOLSER=PRODBB selects the volume serial PRODBB only.
However, ASMRMFV will search every Storage Group until it
is found.
SPGV=TST000:TST999 selects all volume serials GE
'TST000' and LE 'TST999'. In this example volumes TST001
and TST002 will be selected. Note use of an alias.
SPGSER=WORK* selects all volume serials starting with
'WORK' followed by up to 2 more characters. In this
example volumes WORKAA and WORKBB will be selected. Note
use of an alias.
SPGVOL=*+++ selects all volume serials ending in 3
digits. In this example volumes PRD001, PRD002, TST001,
TST002, WRK001, and WRK002 are all selected. Note use of
an alias.
SPGVOLI=P*A selects all volume serials starting with 'P'
that have a final character 'A' with up to 4 intervening
characters. In this example only volume PRODAA is
selected. Note use of an alias.
-SPGAND (default) indicates that selection results from
the two different SPG filter keywords (and any of their
respective aliases) are logically ANDed.
-SPGOR indicates that selection results from the two
different SPG filter keywords (and their respective
aliases) are logically ORed. SPGOR must be coded if
desired.
-Examples of SPGAND/SPGOR:
-With SPGAND (default) in effect:
SPGSTORGROUP=WORKPOOL SPGVOLSER=WRK*
only selects volumes in the WORKPOOL Storage Group AND
that have a volume serial number that starts with 'WRK'.
SPGSTORGROUP= may appear redundant since only one pool
has WRK* volumes, but it keeps ASMRMFV from matching many
Volume Serials in other Storage Groups if only SPGVOLSER=
were present.
SPGSTORGROUP=WORKPOOL SPGVOLSER=WRK* SPGVOLSER=WORK*
only selects volumes in the WORKPOOL Storage Group AND
that have a volume serial number that starts with either
'WRK' or 'WORK'. In this example omitting SPGVOLSER=
would have produced the same result and is redundant.
SPGVOLSER= in this case adds unnecessary overhead.
STORGRUP=PRODPOOL SPGSG=TESTPOOL
only selects volumes that are in either the PRODPOOL
or TESTPOOL Storage Groups. Note the use of aliases.
SPGSTORGROUP=WORKPOOL SPGVOLSER=PRD*
selects NO volumes in this example using SPGAND because
the PRD* volumes are in the PRODPOOL AND not in the
WORKPOOL. There will be zero observations in the ZRBSPG
data set in the result MXG PDB.
SPGAND (default) logical ANDing provides more restrictive
SPG entry filtering than SPGOR.
-With SPGOR in effect:
SPGSTORGROUP=WORKPOOL SPGVOLSER=WRK*
only selects volumes that are in the WORKPOOL Storage
Group OR that have a volume serial number that starts
with 'WRK'. In this example omitting SPGVOLSER= would
produce the same result and is redundant. SPGVOLSER=
adds unnecessary overhead in this case with SPGOR because
ASMRMFV will search all other Storage Groups trying to
match that volume serial.
SPGSTORGROUP=WORKPOOL SPGVOLSER=WRK* SPGVOLSER=WORK*
only selects volumes that are in the WORKPOOL Storage
Group OR that have a volume serial number that starts
with either 'WRK' or 'WORK'.
All volumes in WORKPOOL will be selected so that the
SPGVOLSER= keywords are redundant in this example.
SPGVOLSER= adds unnecessary overhead in this case with
SPGOR because ASMRMFV will search all other Storage
Groups trying to match those volume serials.
STORGRUP=PRODPOOL SPGSG=TESTPOOL
only selects volumes that are in either the PRODPOOL
or TESTPOOL Storage Groups. Note the use of aliases.
This example produces the same result as with SPGAND
because two keywords (or any of their aliases) for the
same selection are always logically ORed.
SPGSTORGROUP=WORKPOOL SPGVOLSER=PRD*
selects all volumes in the WORKPOOL Storage Group OR
any volumes that start with 'PRD' in the PRODPOOL
Storage Group.
This is a MUCH different result with SPGOR than if SPGAND
is in effect. With SPGAND no volumes are selected.
ASMRMFV will search all Storage Groups for a match with
the SPGVOLSER= value.
The logical OR with SPGOR results in less restrictive
filtering because any of the 2 conditions in this example
results in data selection of a SPG volume data entry.
-Support for a new multi-table selection filter VOLSER=
(aliases VOLUME=, VOLI=, SER=, VOL=) to allow selection
by Volume Serial from both the RMF Monitor III DVT and
SPG tables with one keyword.
This is a convenience feature to avoid having to code the
Volume Serial parameter twice when the same volume from
both tables is of interest. Both the DVT and SPG tables
must be selected for this multi-table selection keyword
to function completely. Otherwise only entries from the
one selected table are filtered.
Note that most RMF III tables do not contain common
character data fields, but in this case the DVT and SPG
do.
-Example of VOLSER= :
VOLSER=ABC* is equivalent to coding
DVTVOLSER=ABC*
SPGVOLSER=ABC*
-ASMRMFV now supports keywords up to 14 characters in
length up from 12.
-Support +13 / -13 hour offset or +780 / -780 minutes
GMTOFFSET= value for locations near International Date
Line using Daylight Saving Time such as New Zealand.
-MXG00 record version is now X'05' from X'04' and includes
new range and pattern table statistics for SPG filtering.
New ASMxxxxx variables added to ASM00 dataset.
-Add new items to Section 2 "Terminology" :
Enclave, Report Class, Resource Group, Service Class,
Storage Group, and Workload.
-Former Section 27 "Summary" is now Section 29.
-Update documentation for SPGSTORGROUP=, SPGVOLSER=,
and GMTOFFSET= support:
Section 5 "Input Data Selection Parameters"
Section 8 "Error Handling Parameters"
Section 9 "JCL and SYSIN Parameter Usage"
Section 12 "Messages"
Section 13 "Filtered Records"
Section 15 "Program and IBM Limitations"
Section 25 "Ranges and Patterns"
Section 29 "Summary"
-New documentation Section 27 "GMT Offset Support" better
explains use of the GMTOFFSET= keyword added by MXG
Change 34.133 .
-New documentation Section 28 "Collection of DASD Usage
with RMF Monitor III" details the requirements and setup
of DASD usage measurement in the SPG table.
-New documentation Section 30 "Bibliography" lists IBM
manuals and numbers for the Resource Measurement Facility
(RMF) for z/OS 2.2 back to z/OS 1.10.
-Count information messages and include in final RMFV999I
message with documentation update.
Change 34.190 COSMETIC. INVALID ARGUMENT TO FUNCTION DATEJUL(1900000)
VMACTPMX and a hex dump was printed if the DUE OUT time values are
Aug 10, 2016 all zeros. Had no impact on the output TPMX datasets.
Thanks to Scott Wiig, USBank, USA.
Change 34.189 MXG 34.05 ONLY. INPUT STATEMENT EXCEEDED if more than 3
VMAC119 ADDL HOME ADDR fields exist; Change 34.168 update didn't
Aug 10, 2016 protect more than 3. Since this site had 4, now there
are 4 fields kept, and the more than 4 is protected.
Thanks to Scott Wiig, USBank, USA.
Change 34.188 WPS ONLY, and only with user tailoring. The ARRAY CAI
VMAC7072 statement did not specify $1 to set the array to CHAR;
Aug 10, 2016 if the user dropped variable CAI0, WPS failed because it
couldn't identify the type. While this is an internal
WPS issue that will be resolved, adding $1 to the ARRAY
statement removes the exposure.
Change 34.187 Support for SMF 124 I/O Supervisor Information (z/OS 2.2)
FORMATS DDDDDD DATASET DESCRIPTION
EXTY1241 TY1241 TYPE1241 I/O Supervisor Information
IMAC124 The SM124RETTIME field is an invalid value, with the four
TYPE124 byte packed decimal date value first and then the time,
TYPS124 reversed from the standard SMFSTAMP format with time and
VMAC124 then the date. MXG code detects/corrects either format.
VMXGINIT
Aug 15, 2016
Thanks to Scott Barry, SBBWorks Inc., USA
Change 34.186 Support for Mainview for IP RTIN='34'x, TAC9I220 dataset.
FORMATS DDDDDD DATASET DESCRIPTION
IMACMVIP VMIP34 TAC9I220 PIUTRACE
VMACMVIP (Note that IMACMVIP controls which RTIN values are read.)
Aug 15, 2016
Change 34.185 Unused Change Number.
Change 34.184 New percentage variables added to RMF III ZRBSPG dataset:
VMACRMFV SPGFREEP='PERCENT*OF VOLUME*FREE'
Aug 5, 2016 SPGUSEDP='PERCENT*OF VOLUME*USED'
Change 34.183 Support for CICS/TS 5.4 OPEN BETA.
VMAC110 -New variables added to CICSTRAN DCN=416 DRL=3588.
Aug 7, 2016 but no dictionary records were produced at startup so the
new CICSTRAN fields are unknown, and it is also unknown
if new fields were inserted or appended. Current MXG
code falls thru and uses 5.3 INPUT code for 5.4 records
but that is WRONG if there were INSERTS.
-Type 110 Subtype 2 STID 108 statistics CICTCPIP new vars:
SORTCPIPSMAXPERSIST='MAXIMUM*PERSISTENT*CONNECTIONS'
SORTCPIPSNONPERSIST='NON*PERSISTENT*CONNECTIONS'
SORTOTALCONNS ='TOTAL*CONNECTIONS'
SORNONPATMAXPERSIST='MADE*NON-PERSISTENT*MAXPERSIST*REACHED'
SORNONPATTASKLIMIT ='NEW NON*CONN MADE*TASK LIMIT*EXCEEDED'
SORDISCATTASKLIMIT ='DISCONNECTS*TASK LIMIT*EXCEEDED'
SORDISCATMAXUSES ='DISCONNECTS*MAX USERS*EXCEEDED'
SORCURRBACKLOG ='CURRENT*BACKLOG*Q-DEPTH'
SORCONNSDROPPED ='CONNECTIONS*DROPPED'
SORCONNLASTDROPPED ='DATETIME*LAST*CONNECTION*DROPPED'
SORCURRMAXBACKLOG ='BACKLOG*CURRENTLY*IN USE'
SORREQUESTS ='REQUESTS*PROCESSED'
Change 34.182 MIMPRID=2 Record sample count variable MIMCFNBR=0, but
VMACMIM numerous fields are divided by Sample Count, so their
Aug 3, 2016 divide caused DIVIDE BY ZERO messages and missing values
in those variables. Temporarily, those divides are now
inside a IF MIMCFNGR GT 0 DO group so the numbers are
not set missing, while vendor contact is pursued.
Change 34.181 -Defective BMC CMF type 74 subtype 4 records with SMF744ML
VMAC74 zero (no SCM segments) but with non-zero R744RISC (SCM
Aug 3, 2016 segment expected) caused R744Mxxx SCM variables to be
Aug 11, 2016 INPUT when there was no data. Now, SCM segment is INPUT
only when both R744RISC and SMF744MN are non-zero.
This has been reported as a defect to the vendor; one
record has the triplet populated with no segments and the
next record has the data but the triplet count is zero.
-SCM Variables R744MRBT and R744MWBT are now converted to
bytes from KB and formatted MGBYTES. like other SCM byte
containing variables.
-Missing values notes for R749PCIxxx variables eliminated
by wrapping conditional INPUTs with DO Group and moving
the multiply inside the appropriate DO Group.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Thanks to Paul Volpi, UHC, USA.
Change 34.180 -Omegamon XE ATF datetimestamps are now on the LOCAL zone
VMACATF and variable ATFTU2L, the GMT Offset, is now kept in all
Jul 29, 2016 ATF datasets.
Sep 5, 2016 -To correlate the MXG variables with the CSV files from
Oct 14, 2016 IMS Performance Analyzer, these variables are now kept
in all ATF datasets ATFCORI/ATFCORP/ATFCORT to match the
IBM AESCORID/AESCORPPST/AESCORTIME and variable ATFCREKEY
is concat of AESCREID/AESREOASN/AESRECOMN/ATFCRE.
-Summary variables ATFSUD2N/D2E/D2C from IMSATFD2 into the
IMSATFA0 dataset incorrectly included ITEM CODE 9, the
TOTALs, which were double accounted.
-Oct 14. ATFSTART corrected to local time zone.
Thanks to Robert Gilbert, BNPParibasFortis, FRANCE.
Change 34.179 -Updated CHECKSTN, failed only in JCLTES92 in ASUM113 QA
CHECKSTN test, because PDB.TYPE70PR was presumed to exist; now the
VMXGINIT program verifies it exists, or prints note on the log if
Jul 28, 2016 it can't be executed, and why not.
-The CHECKSTN program was added to the ASUM113 program to
report if duplicates exist in your TYPE70PR data, but you
you can suppress its execution with in your //SYSIN with
%LET MXGSTNCK=NO;
Thanks to Anon, Anon, USA.
Change 34.178 Support for RACF 80 TOKDANAM values CRSGUID, SISMIDDL,
VMAC80A SISCCNO, SISDMPID, SISCOMPY, SISECVT, SISFIRST, SISLAST.
Jul 27, 2016 creates new variables
TOKMCSRGUID/TOKMSISMIDDL/TOKMSISCCNO/TOKMEMPID/
TOKMSISCOMPY/TOKMSISECVT/TOKMSISFIRST/TOKMSISLAST
in dataset TYPE80TK.
Thanks to Michael Oujesky, DTCC, USA.
Change 34.177 Cosmetic. TMON/CICS History file with TMONPROD='D' have
VMACTMO2 LENMONI=0. causing "SHORT RECORD" warnings on the log,
Jul 27, 2016 but these records with TMMDREC='DD' are not the records
wanted, so they are now deleted prior to the length text.
Thanks to Rodger Foreman, Transunion, USA.
Change 34.176 RACFTYPE=6 COMMAND RACFEVNT=19:PERMIT with RACFDLN=12
VMAC80A caused invalid segment skipped message because MXG only
Jul 27, 2016 expected 11.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 34.175 zVM 6.3.16.1 added 4 bytes to PRCPUP segment but MXG did
VMACVMXA not protect correctly, causing PROBABLY DATA LOSS ERROR
Jul 26,2016 on the SAS log. SKIP logic is corrected and the dataset
VXPRCPUP is now output for each segment; previously, only
the last segment was output with the Park/Unpark metrics.
Thanks to Joseph J. Faska, DTCC, USA
Change 34.174 New NOTYPE= parameter lets you specify a list of SMF IDs
VMXGGETM to not be copied. They will be counted in the input but
Jul 26,2016 not in the output counts. Column percentages were added
to the output report. VMXGGETM creates an SMF output file
selecting N records of each SMF ID.
======= Changes thru 34.173 were in MXG 34.05 dated Jul 25, 2016========
Change 34.173 Support for IAM Shorter Record INPUT STATEMENT EXCEEDED.
VMACIAM Change 34.008A in MXG 34.01 added support for V9.2 with
Jul 25, 2016 segment lengths of 292 and 264 bytes for IAMIAINL and
IAMIASTL, but V9.0 has shorter 204/148 segment lengths
that are now detected and protected.
Thanks to Paul Naddeo, Fiserv, USA.
Thanks to Bernie Ethridge, Fiserv, USA.
Change 34.172 See Change 34.216.
Change 34.171 The "IHDR" member for BMC MAINVIEW FOR IP did not contain
IHDRMVIP the MACMVIH macro variable, which also needed to be
VMXGINIT defined in the %GLOBAL statement in VMXGINIT.
Jul 24, 2016
Change 34.170 Support for WebSphere Liberty Batch SMF 120 subtype 12.
EXT12012 Creates new dataset:
VMAC120 dddddd dataset description
VMXGINIT T12012 TYP12012 WAS LIBERTY BATCH
Jul 23, 2016
Change 34.169 The zVM HIS macros _TPRCMFC/_TPRCMFM/_XPRCMFC/_XPRCMFM
VMACVMXA must also create VXMTRPRP to populate the PFXCPT array.
Jul 19, 2016 The _Tdddrrr macros read VMINPUT and the _Xdddrrr macros
read the MWINPUT file to create each VXdddrrr dataset.
Thanks to Scott Barry, SBBWorks Inc., USA
Change 34.168 Support for SMF 119 Subtype 6 Home IP Address section
VMAC119 adds these first three instances to dataset TYP11906:
Jul 16, 2016 IFADDLIN1='IFADDINTFNAME*1'
IFADDLIH1='IFADDINTFHOME*1'
IFADDLIN2='IFADDINTFNAME*2'
IFADDLIH2='IFADDINTFHOME*2'
IFADDLIN3='IFADDINTFNAME*3'
IFADDLIH3='IFADDINTFHOME*3'
Thanks to Wolfgang Kueller, S-Itsolutions, AUSTRIA
Change 34.167 Protect for duplicate SMF70STN values in TYPE70PR data.
ASUM113 ONLY NEEDED IF YOU HAVE LPARs WITH THE SAME SYSTEM NAME.
CHECKSTN
VMAC7072 -New SOLUTION FOR THE ASUM113 PROBLEM:
VMXGINIT The text below shows SMF70STN can not be used to match
Jul 16, 2016 TYPE1131 data with TYPE70PR data, but an alternative to
Jul 25, 2016 identify which TYPE70PR obs belong to this SMF record:
Jul 28, 2016 IF PARTISHN(SMF70PTN)=LPARNUM(SMF70LPN) in TYPE70PR,
that LPAR is the LPAR of this SMF 70 record, which is
then selected to be merged with TYPE1131s. BUT YOU
MUST have BOTH 70s and 113s, and ONLY from one LPAR,
for ASUM113 to create valid PDB.ASUM1131 dataset.
-NO SOLUTION FOR THE ASUM70PR PROBLEM:
If you have duplicate SMF70STN values with CHECKSTN,
there is NO SOLUTION to use ASUM70PR to combine the
multiple LPAR's TYPE70PR data; those duplicates cause
PCTCPUBY to be incorrect (over 100%) with other metrics
also wrong. YOU MUST PROCESS EACH DUPLICATED LPAR's
SMF/RMF data into a SEPARATE PDB FOR EACH OF THE LPARs.
-The new CHECKSTN program can be run to read PDB.TYPE70PR
to produce a report ONLY if duplicate SMF70STN values for
different LPARNAMEs are found in your data:
// EXEC MXGSAS94
//PDB DD DSN=YOUR.TYPE70PR.PDB,DISP=SHR
//SYSIN DD *
%INCLUDE SOURCLIB(CHECKSTN);
-Original Change text, prior to Jul 25:
IN GENERAL, MXG CAN NOT HANDLE MULTIPLE SYSTEM NAMES THAT
ARE FOR UNIQUE SYSTEMS TO BE COMBINED. YOU MUST CREATE
SEPARATE PDB DATA LIBRARIES FOR EACH SYSTEM AND THEY CAN
NOT BE MERGED/COMBINED.
The SMF70STN (LPAR's SYSTEM name) is needed in ASUM113
as it is the only mapping from the z/OS SMF SYSTEM name
to that systems LPARNAME, and must be used there so the
TYPE70PR LPAR utilization variables can be added to the
PDB.ASUM1131 dataset. But RMF data with the same SMF70STN
for different LPARNAMEs has occurred and that corrupts
the PDB.ASUM1131 dataset with incorrect values and
creating multiple LPARNAMEs when there was only one
system's SMF 113 records.
The original solution required you to tell MXG the real
SYSTEM name of those LPARNAMEs that are duplicated, using
the new "exit" MXGSTNFX macro variable:
%LET MXGSTNFX=
%QUOTE( IF LPARNAME='EJQ1' THEN SMF70STN='EJQ1';
ELSE IF LPARNAME='EJQ2' THEN SMF70STN='EJQ2';
);
That statement can be put in "USERID.SOURCLIB(IMACKEEP)"
so it is always used when TYPE70s are processed, or it
can be the top of the SYSIN for a specific job.
But it may not be required with the PARTISHN fix.
Thanks to Jim Poletti, EdJones, USA.
Change 34.166 Support for SMF Type 87 Subtype ENQ/DEQ records.
EXTY8702 Code has been syntax checked, await subtype 2 records to
VMAC87 validate the updated code.
VMXGINIT
Jul 14, 2016
Change 34.165 -RMF Type 74 dataset TYPE74SL variable R748LFBC was input
FORMATS as RB4. but it is a binary value, now input as PIB4.
VMAC74 R748LFBC /*FI CHAN*BIT*ERROR*RATE*/
Jul 13, 2016 -Format MG0748L had value decimal 7 for 10GB Ethernet but
that may have been a guess for the undocumented value
that is now documented as 10x or 16 decimal.
Thanks to Scott Barry, SBBWorks Inc., USA
Change 34.164 Support for IDMS Version 19 (which is INCOMPATIBLE only
VMACIDMS when you install IDMS PTF R084146)! There was no change
Jul 13, 2016 in the V19 SMF record's format, but R084146 changed the
value of SMFHDR to 1900, which caused this error message:
UNKNOWN IDMS RECORD PMHRTYPE=201
FOUND AND SKIPPED. SMFHVER=1900 _N_=2 START COL=25
because MXG had one test for SMFHVER='1800' that needed
to be changed to GE '1800' to read records with the PTF.
Thanks to William Marshall, Ensono, USA.
Change 34.163 Support for SMF Type 120 Subtype 11 Liberty 16.0.0.2 that
EXT120BL created three new datasets:
EXT120BC dddddd dataset description
EXT120BU T120BL TYP120BL Liberty Server Request Network
FORMATS T120BC TYP120BC Liberty Classify Segments
VMAC120 T120BU TYP120BU Liberty User Segments
VMXGINIT For the User segment, SM120BDH is $CHAR32 with $HEX64
Jul 13, 2016 format, and can be decoded in EXT120BU and _KT120BU can
be tailored to add the new variables you created.
Unfortunately, NONE of these new fields have IBM-provided
field names; MXG had to create names beginning SM120Bxx
to be somewhat consistent with previous IBM name choices.
You will have to use the variable label to actually map
back to the marginal documentation of these new records.
-Subtype 11 datasets TYP12011 and TYP120BU both have zero
observations now, with internal record version 2 records.
Thanks to David Follis, IBM, USA
Thanks to Steve McKee, FMR, USA.
Change 34.162 Support for z/OS 2.2 JES2 8-character JOBCLAS8 variable,
BUILD005 which is now added to the JES2 PDB.JOBS and PDB.STEPS
VMAC26J2 datasets, so both the 1-char JOBCLASS and the 8-char
Jul 11, 2016 JOBCLAS8 variables are kept. JOBCLAS8 variable has been
Jul 24, 2016 kept in SMF 30s, from either JES2 or JES3, but TYPE26J2
Jul 29, 2016 is now updated to also keep JOBCLAS8 variable.
Note that JES3 PDB.JOBS and PDB.STEPS, changes variable
JOBCLASS to 8-characters.
Jul 24: UNINIT JOBCLAS8 in SPIN.SPIN26J2 corrected.
Jul 28: JOBCLAS8 added to TYPE26J2 dataset.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 34.161 -Missing values for variables WQTTTIME/WQOPENTI/WQCLOSTI
VMAC116 in dataset MQMQUEUE were created from (only) subtype=2
Jul 11, 2016 records. IBM does NOT provide a GMT offset field in 116,
but MXG heuristically created the offset value in the
subtype 1 (where the WTASINTE interval end can be used
with SMFTIME), but there is no similar end time field
in subtype 2 records. Now, GMT116OFF is created and
retained and used for subtype 2 records. The name was
changed to not impact other SMF records with GMTOFF.
-Missing values were created for variable WTASPRET for
old WTASVER LT 8 records; the /4096 was always executed
but is now only calculated for GE 8 records.
Change 34.160 -VMXGALOC did not check for the valid YYMMDD format in the
VMXGALOC DATEFMT= parameter and could then fail with an invalid
Jul 11, 2016 format error. If you used YYMMDD6 or YYMMDD8 it worked.
-VMXGALOC previously upcased directory names, anticipating
possible name comparisons with upper case source text;
this was fine for Windows, but only worked on Linux if
the directory name was all upper case, because names on
Linux are case-sensitive (i.e., directory A is NOT a).
The upcase was removed, but on Linux you must use the
exact casing of the directory name in your BASEDIR=.
-The BASEDIR= directory must exist, or VMXGALOC will shut
itself down, setting MXGRTRN to ABEND, and printing an
additional message on Linux with the name you supplied to
remind you casing is required there.
Thanks to Joe Varkey, Verisk Analytics, USA.
Change 34.159 If you did not use the ODSTYPE parameter ANALAVAI failed,
ANALAVAI looking for a macro variable created by VMXGODSO, which
Jul 11, 2016 was not executed. Now checks the value of ODSTYPE and if
it is NO or NULL, suppresses VMXGODSC.
Change 34.158 Cosmetic. If you specified BUILDPDB=NO, the display of
UTILBLDP parameters you entered showed the internal default list
Jul 11, 2016 MXGINCL of members to be included. Those members were
NOT included with BUILDPDB=NO, but the displayed list
was not accurate. Now only the USED (i.e., non-blank)
members included are displayed on the log.
Change 34.157 Support for SMF 117 IBM Integration Bus Version 10.0.0.5
VMAC117 which INCOMPATIBLY removed fields in the FLOW segment.
Jul 10, 2016 But MXG didn't keep some identity variables from FLOW in
the other three datasets. Previously known as Websphere
Message Broker.
Thanks to Betty Wong, Bank of America, USA.
Change 34.156 RMF III NOTE: INVALID DATA FOR ASIQSCANxxxxx because some
VMACRMFV variables with PIB informat were input with RB informat.
Jul 10, 2016
Change 34.155 New type 42 subtypes that contain a JOB variable did not
IMACJBCK include the IMACJBCK Job Name Check macro that allows you
VMAC42 to select observations to be output. IMACJBCK has been
Jul 9, 2016 added for these TYPE42xx datasets: 4220/4221/422A/4222/
4223/424A/4224/4225/4227/4237/42VS. In case you were not
aware, these comments document IMACJBCK selection:
SPECIFIC JOB CAN BE SELECTED. WHEN INVOKED, ALL OF THESE
VARIABLES HAVE BEEN READ AND ARE VALID FOR TESTING:
ID JOB READTIME SMFTIME SYSTEM
NOT ALL RECORDS WITH JOB NAME HAVE A JESNR FIELD, BUT
6 25 26 30 32 42 59 91
RECORDS HAVE INPUT JESNR WHEN THIS EXIT IS INVOKED.
FOR SMF 30 RECORDS, NRCPU=0 IF THIS IS A MULTIDD='Y'
RECORD. AND %LET MACJBCK can be used instream.
Thanks to Michael Oujesky, DTCC, USA.
Change 34.154 Reserved Change Number.
Change 34.153 Change 33.031 missed two instances of the LOWCASE()
BLDSMPDB function that should have been converted to UPCASE().
Jul 6, 2016
Thanks to Richard Krueger, Sentry, USA.
Change 34.152 -DOW= filter was not working and all days of the week were
ASMRMFV selected instead.
Jul 5, 2016 -Message RMFV014W ALL DATA SETS BYPASSED was not shown
when applicable.
Thanks to Randy Hewitt, HPE Enterprise Services
Change 34.151 When VMXGSUM finished SYSLAST was not pointing at the
VMXGSUM output dataset created but rather at an intermediate
Jul 1, 2016 dataset created. Now when VMXGSUM is done SYSLAST is set
to the output dataset created so that you can then do a
PROC whatever without a dataset name.
Change 34.150 FORMAT MGCICUU for CICS variable WBRUSAGE has two new
FORMATS values of 4:ATOM and 5:JVMSERVER.
Jun 30, 2016
Thanks to Wayne Bell, UNIGROUP, USA.
Change 34.149 Reserved Change.
Change 34.148 Support for ODM Version 8.8.0.1 SMF type 120 subtype 100
VMAC120 adds variables to TY120100 dataset:
Jun 30, 2016 SM120RULEXETYP='RULESET*ENGINE*TYPE'
SM120RULEXEVER='RULESET*ENGINE*VERSION'
SM120RULEXFBOM='RULESET*IS*BOMS*SUPPORT*ENABLED?'
SM120RULEXFDEB='RULESET*IS*DEBUG*ENABLED?'
SM120RULEXFMON='RULESET*IS*MONITORING*ENABLED?'
SM120RULEXFTRC='RULESET*IS*TRACE*ENABLED?'
While the SMF 120 record is created by WebSphere, the
subtype 100 was given to ODM and is not from WAS.
Thanks to Paul Volpi, UHC, USA.
Change 34.147 BUILDPDB processing of PRINTWAY/INFOPRINT product SMF 6
BUILD005 records that have no matching 30s nor 26s were left in
VGETJESN SPIN.SPIN6 until SPINCNT expired when they were finally
VMAC6 output to PDB.PRINT dataset. There are two types of
Jun 28, 2016 PRINTWAY records. MXG decodes them setting variables
BASIC: TYPETASK/SUBSYS/SUBSYS6 are set to 'TCP'.
EXTENDED: TYPETASK/SUBSYS/SUBSYS6 are set to 'TCPE'
and the logic in BUILDPDB outputs all 'TCP ' records to
PDB.PRINT, while 'TCPE' records that didn't match today
are held in SPIN.SPIN6 to match the other records from
those jobs.
Trivia: JCTJOBID for BASIC contains PSnnnnnn which
is not documented and is different than PSFnnnnn for
type 6 records created by PDF.
Thanks to Paul Maradin, HP Advanced Solutions, USA.
Thanks to Grayg Mitrou, HP Advanced Solutions, USA.
Change 34.146 FORMATS MGSRDFC/M/G/S decode SRDCONST/MODE/GROUP/CONSI.
FORMATS
VMACSRDF
Jun 28, 2016
Thanks to Joseph J. Faska, DTCC, USA
Change 34.145 -IFCID 106 new variables QWPBSQLL and QWP4DDLTO parms are
VMAC102 input and kept in dataset T102S106.
VMACDB2H -QWHSRELN value could be truncated and print 10.0999999.
Jun 27, 2016 Now it is forced to print as 10.1.
Jul 3, 2016 -QWPRRENAMETABLE decoded from QWP4MISB and kept.
Thanks to Scott Barry, SBBWorks Inc., USA
Thanks to Lai Fai Wong, Bank of America, USA.
======= Changes thru 34.144 were in MXG 34.04 dated Jul 25, 2016========
Change 34.144 -RMFINTRV message MSU variables are UNINITIALIZED has no
VMXGRMFI actual impact; LENGTH was defined in R72HOUR but those
VMXGSUM variables are not initialized until the MERGE RMF70HOUR.
Jun 23, 2016 Relocated the LENGTH statement to eliminate messages.
-VMXGSUM with NOSORT=YES printed note that MXGSUM2 could
not be deleted, but it doesn't exist with that option, so
also no actual impact. Note no longer printed.
Change 34.143 ZVPS 4.2.3 variable CPUUTIL in dataset XAMSYS was likely
VMACXAM zero because new SYTCUV segment also input CPUUTIL for
Jun 21, 2016 each CPU and the last value was kept in XAMSYS. Now,
from SUBSUM segment is renamed at input and renamed back
at XAMSYS output.
Thanks to Douglas C. Walter, CitiCorp, USA.
Thanks to Brent Turner, Citigroup, USA.
Change 34.142 Change 34.010 did not set the lengths for the new
VMXGRMFI variables created and could result in multiple length
Jun 21, 2016 error messages when running TRNDRMFI.
Change 34.141 WARNING: MEMNAME HAS DIFFERENT LENGTHS is eliminated.
VMXGSRCH
Jun 20, 2016
Change 34.140 Housekeeping. BUILD001 intentionally leaves all of the
ANALID CICS Statistics Data Sets in //WORK after the SMF DATA
ASUMTAPE step, so they are available to be copied by EXPDBOUT if
BUIL3005 desired, and so that CICINTRV can be created in BUILD004,
BUILD005 by VMXGCICI, but now those datasets are deleted after the
PDBAUDIT PDB.CICINTRV has been created. Other members similarly
SPUNJOBS left unneeded datasets in //WORK that are deleted now, to
VMAC113 minimize the required disk space.
VMAC73
VMAC74
VMACDB2
VMXGCICI
Jun 19, 2016
Change 34.139 The highest memory usage in BUILDPDB was in the VMXGSUM
BUILD005 step that created INTVSIOS, but that dataset is already
BUIL3005 sorted, so the option to use CLASSNWAY is suppressed and
Jun 17, 2016 NOSORT=YES is specified to bypass the sort and PROC MEANS
is executed with a BY statement which reduced memory from
242MB to 195MB, and now the DATA step is largest, also
requiring 195MB for this tailored BUILDPDB execution.
Change 34.138 Cosmetic. Variable OVOLSER was 20 bytes ending with a
TYPETMS5 period in byte 20 unless Site Tailoring for Multiple CA/1
Jun 16, 2016 catalogs was used (Change 27.111). Period is now gone.
Thanks to Doug Medland, IBM Global Services, CANADA.
Change 34.137 Major revision to VMXGSUM that could save CPU time.
ASUMCACH This change creates a new parameter, CLASSNWAY with the
VMXGINIT default value of &MXGSUMCLASS, which itself has default
VMXGSUM value of blank, so that you can enable the new logic with
Jun 17, 2016 only %LET MXGSUMCLASS=YES; in //SYSIN, which changes
the current summarization logic to use the CLASS/NWAY
feature of PROC MEANS, instead of the original default.
-The default VMXGSUM logic can be a four step process with
an optional DATA step created (if INCODE=, NORMx=, or
INTERVAL=x arguments are used) to feed the PROC SORT that
feeds the PROC MEANS which may be followed by another
optional DATA step (if NORMx= or OUTCODE= are used).
-The MXGSUMCLASS=YES revision alters the default logic to
remove the SORT and instead invokes the CLASS and NWAY
options on the PROC MEANS, which can greatly reduce the
amount of CPU time consumed since the SORT is eliminated
(in one simple test the zOS CPU time went from 68 seconds
to 28 seconds!
-But, it is VERY possible for the use of CLASS to require
a significant increase in the virtual storage (REGION)
required, in return for reduced CPU time.
-The original MXG design was required because when first
created, virtual memory was an extremely limited resource
and the algorithm minimized memory required. But now,
with memory no longer so restricted nor expensive, using
MXGSUMCLASS option lets test and observe the trade off
to see which options is of benefit to your invocation.
-Executing MXG on z/OS using MXGSUMCLASS=YES:
It is possible you could save some CPU time but the
cost is an increase in high memory usage - more than
doubled in some tests and the CPU time saved will be
primarily in ASUM* TRND* ANAL* GRAF* members run after
BUILDPDB (BUILD005 only has 3 VMXGSUMs, but VMXGCICI
for PDB.CICINTRV has many that may or may not be helped.)
MXGSUMCLASS=YES did fail once because the utility files
used filled the //WORK space, so that specific case in
ASUMCACH has disabled MXGSUMCLASS to circumvent.
The amount of CPU time saved is a complex function of
the complexity of the data - the number of OBS, BY
groups, and count of intersects - each impact memory
utilization so that you must test across several day's
data since the results can vary from day to day as the
complexity changes.
-%LET MXGSUMCLASS=YES; applies to ALL VMXGSUM invocations
after that statement in that job step. You can change any
VMXGSUM invocation after that to revert to the original
logic by adding CLASSNWAY=NO to that VMXGSUM invocation.
-Executing on ASCII thus far has not shown a significant
benefit with MXGSUMCLASS but 'your mileage may vary'.
-These are test results from zOS running SAS 9.3 and using
UTILBLDP with inclusion of many of the ASUMxxxx members,
all of which are VMXGSUM invocations:
%UTILBLDP(USERADD=42 6156,OUTFILE=INSTREAM,BUILDDB=YES);
%INCLUDE INSTREAM;
JOB CPU % CPU CPU
CPU % CHG READING READING PROCESSING
TEST TIME CPU DATA DATA DATA
BY USED 1:17:53.66 . 0:46:28.06 59.65 0:31:25.60
CLASS USED 1:10:19.36 9.72 0:47:12.14 67.12 0:23:07.22
% CPU % CPU
PROCESSING CHANGE TOTAL % CHANGE TOTAL
TEST DATA PROCESSING EXCP EXCP IO TIME
BY USED 40.35 . 1478119 . 0:28:39.67
CLASS USED 32.88 26.43 1199259 18.87 0:17:11.95
HIGH % CHANGE
% CHANGE MEMORY HIGH
TEST IO TIME USED MEMORY
BY USED . 280M .
CLASS USED 39.99 242M 13.38
And here are some further tests comparing BUILDPDB on zOS
and Windows 10. The same input data was used in both
but the DB2/CICS data was compressed so on zOS the CICS
SMF INFILE exit was used but on Windows more CPU time was
consumed to read the data. zOS is running SAS 9.3 and
Win 10 is running 9.4.
Test BUILDPDB Only zOS NWAY zOS BY Win NWAY Win BY
Data step elapsed 0:10:35 0:10:59 0:07:07 0:07:03
Data step CPU 0:08:51 0:08:53 0:07:09 0:07:02
Data Step MAX K Memory 173496 173496 320388 320388
Job elapsed Time 0:14:30 0:14:54 0:08:35 0:08:32
Job CPU 0:11:25 0:11:30 0:08:13 0:08:08
Job MAX K High 173496 173500 449928 449928
Step with HIGH memory DATA STEP DATA STEP SORT SORT
DB2ACCTP DB2ACCTP
Test with ASUMs Win 10 NWAY Win 10 BY
Data step elapsed 0:07:28 0:07:08
Data step CPU 0:07:15 0:07:09
Data Step MAX K Memory 320388 320388
Job elapsed Time 0:10:02 0:10:58
Job CPU 0:09:24 0:09:54
Job MAX K High 727880 449928
Step with HIGH memory ASUMCACH SORT
DB2ACCTP
DB2ACCTP
TECHNOTE: Using MXGSUMCLASS=YES on zOS
Thus far this applies only to zOS. There are no known exposures on
ASCII. Members that have failed:
BUILD005/BUIL3005 - automatically suppressed on zOS
ASUMCACH - automatically suppressed on zOS
ASUMCICS
ASUMCICX
ASUMDB2A
ASUMDB2P
There are two failure modes.
1) UTILITY files fill up work and cannot expand
2) Memory failures as memory expands
The problems will occur if you have many OBS (at least tens of
millions possibly hundreds) and many BY groups which create a large
number of intersections.
If you have a failure, bring the member that failed into your
USERID.SOURCLIB.
The simplest change is to add CLASSNWAY=NO to the parameter list of
the VMXGSUM invocation. That will revert to the original logic for
VMXGSUM of DATA STEP/SORT/MEANS/DATA STEP but also means you will
not be saving any time.
A more complex option is to modify the parameters. For each BY
group MEANS must build a counter for each of the variables in any
of the SUM MEANS MAX etc parameters. That can quickly add up to a
lot of space. So you can either reduce the complexity by reducing
the variables in the BY list or by reducing the number of variables
being SUMMed MEAned MAXed etc.
An example using ASUMCICX (only a partial copy):
MACRO _BSUCICS APPLID OPERATOR USER TERMINAL STRTTIME TRANNAME
SYSTEM SHIFT %
Are OPERATOR USER TERMINAL really necessary in your summarized
data? In many cases TERMINAL is an IP address that is largely
meaningless. OPERATOR and USER may be the same. Reducing the
number of variables in the BY list can help.
%VMXGSUM(INVOKEBY=ASUMCICX,
KEEPALL=&KEEPALL,
INDATA= _LSUUOW ,
OUTDATA= _LSUCICS ,
DSNLABEL=SUCICS: CICSTRAN &SUCIINTV SUMMARY,
DATETIME=STRTTIME,
SUMBY= _BSUCICS ,
DURATM =INTERVAL,
INTERVAL=&SUCIINTV,
SYNC59=NO,
NEWSHIFT=Y,
MAX= RESPMAX,
SUM= DSPDIOCN DSPDIOTM FCAMCNT IRESPTM RESPBKT1-RESPBKT8
TASCPUTM TRMCHRCN WTDISPCN WTDISPTM WTFCIOCN WTFCIOTM
WTIRIOCN WTIRIOTM WTJCIOCN WTJCIOTM WTRLIOCN WTRLIOTM
WTTDIOCN WTTDIOTM WTTSIOCN WTTSIOTM SSQELAP CPUTM
CLASS3TM CLASS3WT DB2CONCN DB2CONTM DB2IDLE DB2RDYCN
DB2RDYTM DB2REQCT DB2SRBTM DB2TCBTM DB2TRAN DB2WAICN
DB2WAITM MROTRAN,
In the SUM= list do any of your reports depend on all of these
variables? If not eliminate those variables. Do any of your CICS
transactions use DB2? If not eliminate the DB2 variables.
The key to getting the advantage of reduced CPU and elapsed time on
zOS with these members is reducing the complexity.
Change 34.136 Support for up to six USERCHAR fields, and revisions
UTILEXCL to support USER fields that are in the middle of the
IMACIC3U segment, which were not correctly handled.
IMACIC4U
IMACIC5U
IMACIC6U
IMACIC3D
IMACIC4D
IMACIC5D
IMACIC6D
Jun 8, 2016
Change 34.135 Additional Q8ST variables are INPUT if they exist:
VMACDB2 Q8STINSC='INSERT*STATEMENTS*SENT TO*IDAA FROM DB2'
Jun 7, 2016 Q8STUPDC='UPDATE*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STDELC='DELETE*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STDRPC='DROP*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STCRTC='CREATE*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STCMTC='COMMIT*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STRBKC='ROLLBACK*STATEMENTS*SENT TO*IDAA FROM DB2'
Q8STOPNC='OPEN*STATEMENTS*SENT TO*IDAA FROM DB2'
Change 34.134 VMXGCOPY copies from multiple inputted SAS Data Libraries
VMXGCOPY to one output Data Library with member selection, etc.
Jun 7, 2016 If your parameters were lower case nothing was found to
copy since the values passed back for LIBNAME and MEMNAME
are uppercase and the compare was always false. To make
it worse it also failed with a bad macro variable name
reference because the variable was not constructed when
nothing was found.
Thanks to Tim Hare, Southwood Shared Resource Center, USA.
Change 34.133 -Support for GMT Offset in MINTIME Sample Set filtering,
ASMRMFV improved MXG00 table data, and other minor enhancements.
ADOCRMFV -The GMT offset feature scales RMF MONITOR III Sample Set
JCLCRMFV begin (SSHTIBEG) and end (SSHTIEND) timestamps to a
JCLDRMFV common user specified GMT time offset ranging from -12 to
JCLRMFV +12 hours or -720 minutes to +720 minutes.
VMACRMFV IMPORTANT: This support does NOT modify any timestamps
Jun 11, 2016 in the output RMFBSAM file. The SSHTIBEG and SSHTIEND
time stamps are modified temporarily ONLY during the
FROMDATE=/TODATE= FROMDATE=/TODATE= filter processing.
-The purpose of the support is to allow an installation to
input RMF III data sets from different time zones and
build a PDB with data relative to a specific time zone.
-Although GMT (Greenwich Mean Time) is technically an
obsolete term replaced by the modern UTC (Coordinated
Universal Time) term, GMT still appears extensively in
RMF documentation and within MXG itself. So the term GMT
is still used for historical consistency.
-The new ASMRMFV keyword to specify a GMT offset is
GMTOFFSET=. Aliases are GMTOFF=, GMT=, GMTOFFSET,
GMTOFF, and GMT.
-When the '=' is missing then GMTOFFSET=0 is implied. The
'=' is required to specify a non-zero GMT offset value.
-Any of the following formats are supported for GMTOFFSET=
(and aliases GMTOFF=,GMT=) :
h -h +h
hh -hh +hh
hH -hH +hH
hhH -hhH +hhH
where h ranges from 0 to 9 and hh from 00 to 12. Values
over 12 are flagged as errors and will abend ASMRMFV. An
h or hh value of zero means scale timestamps to GMT time.
Unsigned h or hh values imply a positive GMT offset. A
'-' sign is required to specify a negative offset.
The capital 'H' suffix is optional and is provided just
to make the unit measure clear if desired.
-Positive GMT offsets are for time zones east of GMT up to
the International Date Line including most (if not all)
of Europe, Africa, Asia, Australia, and many island
groups.
-Negative GMT offsets are for time zones west of GMT up to
the International Date Line including North and South
America and some island groups.
-A few time zones have GMT offsets that are not integer
hour values such as India, some Australian zones, and
some island groups. For example, India is GMT+5:30.
-For the support of these non-integer offset time zones
any of the following formats are supported for GMTOFFSET=
(and aliases GMTOFF=, GMT=) in minutes:
mM -mM +mM
mmM -mmM +mmM
mmmM -mmmM +mmmM
where m ranges from 0 to 9, mm from 00 to 99, and mmm
from 000 to 720 (12 hours). Values over 720 are flagged
as errors and will abend ASMRMFV. An m, mm, or mmm value
of zero means scale timestamps to GMT time. Unsigned m,
mm, or mmm values imply a positive GMT offset. A '-'
sign is required to specify a negative offset.
Any user can still specify this form even for integer
hour offsets by converting the hours x 60 to get minutes.
For example, GMT=-4 and GMT=-240M are equivalent.
The 'M' suffix is REQUIRED for a GMT minutes offset. If
omitted the value will be handled as an hour value
instead.
-NOTE: When using GMTOFFSET= the FROMDATE=/TODATE= and
FROMTIME=/TOTIME= filter values MUST be coded based on
the REQUESTED offset time zone. This is NOT necessarily
the Local Time for the time zone where ASMRMFV is
executing.
-GMTOFFSET= processing follows these steps for each RMF
Monitor III MINTIME Sample Set:
1) The Sample Set begin (SSHTIBEG) and end (SSHTIEND)
timestamps are first converted to GMT time using the
SSHSTDIF GMT offset field from the Sample Set Header
(SSH) present for each Sample Set. Then they are set
into temporary timestamp fields for filtering.
2) If GMTOFFSET=0 is in effect, then no further changes
are applied to the temporary timestamps and filtering
continues with the timestamps in GMT Time. They are
compared to the FROMDATE=/TODATE= and FROMTIME=/TOTIME=
option settings.
3) If GMTOFFSET= is non-zero then the temporary timestamp
fields are further altered with the negative or positive
offset value. These altered timestamps are referred to
as Adjusted Time in ASMRMFV documentation and messages.
They are compared to the FROMDATE=/TODATE= and
FROMTIME=/TOTIME= option settings.
4) As noted earlier any selected Sample Set tables are
output to the RMFBSAM file with their original timestamps
unchanged.
-Examples of GMTOFFSET= use follow. In all cases it is an
installation responsibility to transfer the multi time
zone RMF Monitor III data sets to the ASMRMFV execution
site prior to processing. The RMF provided ERBV2S and
ERBS2V Clists are one method to create and retrieve a
sequential copy of an RMF Monitor III VSAM data set.
-Example 1: A London based company wants build an RMF III
PDB for yesterday with RMF III VSAM data sets input from
several different time zones in Europe and Asia for their
peak hours of 09:00 to 15:00. They want to see what
other activity is occurring elsewhere during this time.
ASMRMFV statements:
FROMDATE=YESTERDAY TODATE=YESTERDAY
FROMTIME=0900 TOTIME=1500 GMT
-Example 2: A New York corporation wants build an RMF III
PDB for two days ago in June with RMF III VSAM data sets
input from several different time zones in the United
States for the prime time hours of 08:00 to 17:00. They
need to see if some moving some workloads might result in
fewer delays. They are using Daylight Saving Time and
their time zone is at GMT=-4.
ASMRMFV statements:
FROMDATE=*-2 TODATE=*-2
FROMTIME=0800 TOTIME=1700 GMTOFF=-4
-NOTE: For sites using GMTOFFSET= processing and Daylight
Saving Time the GMT offset changes during the fall
transition to Standard Time and the GMT offset increases
by 1 hour. In the example above it becomes GMTOFF=-5.
One advantage of using pure GMT offsets is that time
changes such as this are not an issue because RMF III
keeps the GMT offset for each Sample Set. RMF III does
not have any awareness of Daylight Saving Time and so it
is a user responsibility to code GMTOFFSET= correctly
before and after a time change.
-Example 3: An India enterprise wants build an RMF III PDB
for the last five days with RMF III VSAM data sets input
from several different time zones in Asia and Europe for
their early morning hours of midnight to 07:00. India
Time is at GMT+05:30 hours. They want to see if some
workload balancing might be possible across multiple data
centers to reducing processing delays or take advantage
of available CPU cycles.
ASMRMFV statements:
FROMDATE=*-5 TODATE=*-1 WINDOW
FROMTIME=0000 TOTIME=0700 GMT=+330M
-Most ASMRMFV timestamp messages are revised or added to
now display the GMT time when GMTOFFSET is used. These
include:
RMFV001I Current Time and Last IPL Time
RMFV008I Input data set Last Open Time
RMFV012I Sample Set Found Begin and End Times
RMFV013I Sample Set Selected Begin and End Times
RMFV017I RMF and z/OS Version Found Time
RMFV023W Sample Set Date/Time - Service Policy missing
RMFV032E Sample Set Date/Time - Program service failure
RMFV039I Sample Set Date/Time - SHOWSAMP option info
RMFV070* Sample Set Date/Time - Service Class Find error
RMFV071* Sample Set Date/Time - Report Class Find error
RMFV072* Sample Set Date/Time - Workload Name Find error
RMFV073* Sample Set Date/Time - Resource Group Find error
RMFV076I Sample Set Date/Time - SHOWASI option info
RMFV078I Sample Set Date/Time - Prior Service Policy use
(* = E, W, or I depending on error settings)
-In addition all above messages (except RMFV001I and
RMFV008I) display the Adjusted Time if GMTOFFSET is
non-zero. So it is possible to get up to three messages
for each timestamp display when GMTOFFSET= is in effect:
Local Time, GMT Time, and Adjusted Time. These provide
an audit trail and verify program operation is correct.
-New parameter SHOWGMT (aliases SHGMT, SG) will display
GMT versions of timestamp messages even if GMTOFFSET is
not in effect. SHOWGMT is forced if GMTOFFSET is in
effect. Updated message RMFV037I displays SHOWGMT
setting.
-New parameter NOSHOWGMT (aliases NOSHGMT, NOSG) will
suppress GMT versions of timestamp messages. NOSHOWGMT
is the default so there should be little need to code
this option.
-New parameter SHOWASI (alias SHASI) displays some ASI
entry data when selected. This is intended primarily for
debugging as it will produce voluminous output in the
ASMRMFV log. This function formerly required a
re-assembly and re-link to be enabled. Updated RMFV037I
message shows status of this setting.
-New parameter NOSHOWASI (alias NOSHASI) suppresses ASI
data display. This is the default and should not need to
be coded.
-New RMFV006I message shows GMTOFFSET status and offset
value.
-New RMFV014I message displays when all tables have been
excluded due to filtering that were not originally
excluded by an entire data set bypass condition. For
example, this can occur when using range and/or pattern
filters to select specific jobs that did not run in the
selected time range.
-New aliases added SHSAMP for SHOWSAMP and NOSHSAMP for
NOSHOWSAMP (default)
-New aliases added SHMATCH for SHOWMATCH and NOSHMATCH for
NOSHOWMATCH (default).
-New aliases added SHZERO for SHOWZERO (default) and
NOSHZERO for NOSHOWZERO.
-New aliases added SHALL for SHOWALL and NOSHALL for
NOSHOWALL (default).
-Add sections to MXG00 ASMRMFV Initialization table for
table capacities, table sizes, buffer/workarea settings,
multiple filter logic options, filter options, GMT offset
settings, report options, output options, error options,
and table selection options. Updated BUILD00 subroutine.
Nearly all ASMRMFV parameter options are now saved except
contents of range and pattern tables. These fields
become variables in the ZRBASM data set in the MXG PDB.
-Raise MXG00 record version to X'04' from X'03'.
-Code path improvements for SHOWTS and STCKCONV
subroutines.
-Some data set names and volume serial numbers were
incorrect in the MXG00 ASMRMFV Initialization table.
-The CAT and CPC tables were not included in example
discussions in the JCLRMFV, JCLCRMFV, and JCLCRMFV
members.
-Documentation updates to:
Section 2 Terminology (Timestamps)
Section 5 Input Data Selection Parameters
Section 6 Report Control Parameters
Section 12 Messages
Section 13 Filtered Records
Section 15 Program and IBM Limitations
Section 26 ASMRMFV and MXG PDB Data Relationships
Section 27 Summary
Thanks to MP Welch, Bank of America, USA.
Change 34.132 Unused.
Change 34.131 ERROR: Invalid date constant " .":d with BLDSMPDB was
BLDSMPDB caused by a typo, the lack of an underscore on the old
Jun 1, 2016 style _TODAY macro, causing LASTWEEK to be miscalculated.
Impacts MONTHLY job, but FORCEDAY=01JUN16 circumvents.
Thanks to Jim Hayes, Huntington Bank, USA.
Change 34.130 New variable GEICSARE, Unallocated Common Area Left, is
VMACRMFV now input and kept in RMF III dataset ZRBGEI, formatted
May 31, 2016 with MGBYTES.
Thanks to Dave Cogar, Wells Fargo, USA.
Change 34.129 Variable R723MCPG, the number of periods in this service
VMAC7072 class, is now kept in dataset TYPE72PD.
May 30, 2016
Thanks to Jim Horne, Lowe's Companies, Inc., USA.
Change 34.128 Zen CSM records ZOSAPOOL dataset new ZOSA_POOL_TYPE is
VMACZOSA 'E' for ECSA Pool or 'D' for DataSpace Pool.
May 27, 2016
Thanks to Jerome Vitner, Experian, USA.
Change 34.127 If only one variable was being examined, a NOT SORTED
ANALRANK error could occur due to an insufficiently specified
May 24, 2016 BY list.
Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.
Change 34.126 TYPETMS5 observations for tapes created by old versions
VMACTMS5 of DFDSS contained zeros for BLKSIZE but PGM='ADRDSSU'
May 23, 2016 tapes are always BLKSIZE=65520, so MXG sets that value
for these old tapes.
Thanks to Jim Agrippe, Cleveland Clinic, USA.
Change 34.125 Documentation only. Mainview for IMS IMF/CIMS maintenance
VMACCIMS PUT 1502 PTFs BQI2154, BPK2892 were supposed to correct
May 23, 2016 corrects zIIP CPU times where zIIP Eligible time TRXZIOCP
was greater than the CPU time on CP, TRXZONCP, but does
not appear to correct the problem as of this date.
Change 34.124 MXG Format MGD044K for DB2 Trace Dataset T102S044 updated
FORMATS with new values.
May 18, 2016
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 34.123 -Support for IFCID 365 populates T102S365 dataset.
VMAC102 -Support for IFCID 376 corrects QW0376VN so only QW0376VL
May 18, 2016 bytes are input. Variable QW0376TS is an invalid 8-byte
Jun 1, 2016 value: '1982A5641F29CA5A'x and '0E5F1F1D09F14040'x
are not valid TODSTAMP nor 10-byte DB2 time fields.
Thanks to Lai Fai Wong, Bank of America, USA.
Change 34.122 ANALCSQC counts concurrent MQ Applications from SYSLOG in
ANALCSQX this tailored use of TYPSSYSL that selects only logon
May 17, 2016 +CSQX500I and logoff +CSQX501I MSGID to create a session
event observation, which ANALCNCR then processes to count
and plot concurrent sessions for each quarter hour.
Thanks to Tom M. Kane, AT&T, USA.
Change 34.121 Formal support for SYSLOG (including multi-line messages)
EXSYSLOG with all MXG dataset tokens, to replace SYSLOG member, in
FORMATS particular, so EXSYSLOG/_ESYSLOG dataset exit exists so
IMACSYSL only desired MSGID are output. TYPESYSL exists but only
TYPESYSL creates raw data in WORK.SYSLOG; TYPSSYSL must be used as
TYPSSYSL it invokes the _SSYSLOG sort macro that combines multi
VMACSYSL messages into one observation and writes out PDB.SYSLOG.
VMXGINIT
May 17, 2016
Change 34.120 ERROR: SPIN.SPINPDBAUDIT.DATA HAS TOO LONG A MEMBER NAME
PDBAUDIT occurs if your //SPIN DD was created with SAS Version 6,
May 17, 2016 which allowed only 8-character SAS dataset/member names.
You need to create a new VERSION 9 format data library by
copying the current //SPIN DD data to a NEW V9 SPIN DSN:
// EXEC MXGSASV9
//SPIN DD DSN=YOUR.OLD.SPIN,DISP=SHR
//SPINNEW DD DSN=YOUR.NEW.SPIN,DISP=(,CATLG),SPACE...
//SYSIN DD *
PROC COPY IN=SPIN OUT=SPINNEW MT=DATA;
and then delete OLD and then rename NEW to OLD.
You probably also need to examine all of your re-used SAS
data libraries (PDB,MON,TUE,...WEEK,MONTH, i.e., those
with DISP=OLD that are re-written each time), to see if
any were also created with SAS V6, with the output of
PROC CONTENTS DATA=PDB._ALL_ NODS DETAILS
to see what ENGINE created each of those data libraries.
While MXG has had long dataset names for some time, this
is the first instance in the "mainline" SMF processing
code members used in BUILDPDB, and was introduced in MXG
33.07 in the new PDBAUDIT report of your PDB libraries.
(SAS 6.08 dates back to 1992, so this site's
SPIN dataset has stood the test of time!!)
Thanks to Jeanne Vetter, Dell Services, USA.
Change 34.119 There is a known SAS exposure that can cause a CPU loop
VMXGCNFG after a program has finished, in SAS termination, if you
May 17, 2016 try to dynamically allocate a DD that was already in JCL.
If you use the CONFIG= CONFIMXG option as your MXG JCL
//MXGSTEP EXEC SAS,CONFIG=MXG.SOURCLIB(CONFIMXG)
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),
it does dynamically allocate the SOURCLIB and LIBRARY DD,
but the restriction was only documented. This change
prevents the loop by testing for their allocation, and
causing the job to USER ABEND 777 before the SAS program
actually starts.
Change 34.118 MXG created variable CPUZIPTM_CPUIFATM_INST was wrong and
VMAC30 usually negative because the three component variables
May 15, 2016 should have been added to get the IFA/ZIP Instructions.
Thanks to Paul Volpi, UHC, USA.
Change 34.117 CPU and SU_SEC values for z13 processors added to the
GRAFWRKX formats so that you can model these newer systems with
May 12, 2016 your existing data. This is a very simplistic model
that will only convert the CPU time from the current
model to whatever model you specify with NEWMODEL=.
Change 34.116 Enhancement for RMM/EDGHSKP/TYPEEDGR adds new variables
VMACEDGR SYSTEM and EDGRTIME to all datasets, retained from the
May 13, 2016 Header record.
Thanks to Linda Berkeley, USPS, USA.
Change 34.115 Variable DCDTIMEC, Data Set Create Time in DCOLDSET is
VMACDCOL only populated if
May 11, 2016 - the dataset is on an EAV volume (more than 65K CYL)
- the volume is the first volume for the dataset
(DCDTIMEC is zero in the DSCB for other volumes)
- for non-VSAM, EATTR=OPT must be specified (JCL or
Data Class), because EATTR=NO is the default for
non-VSAM, EATTR=OPT is the default for VSAM.
The DCDTIMEC comes from the FORMAT 9 DSCB control block
(in the VTOC), created for EAS-eligible datasets on EAV
that have EATTR=OPT, except that these datasets
do not have FORMAT 8/9 DSCBs.
Thanks to Donna Roff, FISA NYC GOV, USA.
======= Changes thru 34.114 were in MXG 34.03 dated May 10, 2016========
Change 34.114 Enhancement to TCP analysis %ANALTCP program that allows
ANALTCP selection by user name remote IP address for FTP, API, or
ANAL119 Telnet datasets from SMF 118 (TCP) or 119.
Jun 8, 2016
Thanks to Dave Ireland, USDA, USA.
Change 34.113 Support for COMPUWARE Hiperstation SIEM User SMF record.
EXSIEM01 Also called Hiperstation Application Audit.
EXSIEM02 New datasets are created from these subtypes:
EXSIEM03 dddddd dataset description
IMACSIEM SIEM01 SIEM3270 SIEM 3270 Session 01
TYPESIEM SIEMA1 SIME3270A SIEM 3270 Screen Lines 01
TYPSSIEM SIEM02 SIEMTCP SIEM TCP 02
VMACSIEM SIEM03 SIEMMQ SIEM MQ 03
May 9, 2016 Currently, only subtype 1 is created and supported.
May 19, 2016 -May 19. Variable SIEMLPAR NOT FOUND corrected.
Change 34.112 MXG 34.01,34.02. DCOLLECT dataset DCOLBKUP variables
VMACDCOL UBDSIZE and UBRECSP were incorrectly multiplied by the
May 9, 2016 original *1024 that should have been removed when the
tests for UBFLAG4 was added in Change 34.042.
Thanks to Thomas Peiper, TIETO SWEDEN AB, SWEDEN.
Change 34.111 New TYPE72PD, RMF WLM POLICY DEFINITIONS dataset is now
EXTY72PD created for every service and reporting class.
IMAC7072
VMAC7072
VMXGINIT
May 6, 2016
Thanks to Scott Barry, SBBWorks, Inc, USA.
Change 34.110 Parameter INCODE= added so you can add selection SAS
ANALUOW code on all variables and not just time and transaction
May 3, 2016 name. Logic added to detect that no data was found and
terminate ANALUOW
Thanks to Dave Ireland, USDA, USA.
Change 34.109 DB2 Package Dataset DB2ACCTP does not contain QX......
VMACDB2 variables. QX variables exist only in DB2ACCT and the
May 4, 2016 DB2STATB datasets (initially from DB2STAT1).
Thanks to Jane S. Stock, USPS, USA.
Change 34.108 DB2 Simulated Buffer Pool DB2STSBP/DB2STATS variables
VMACDB2 QBSPIUS, QBSPSUS (current) and QBSPHSU, QBSDPHUS (hwmark
May 3, 2016 pages) should not have been deaccumulated.
Variable QBSPREADS is now correctly deaccumulated.
And variable QBSTRHS in DB2STATB is now deaccumulated.
Thanks to Lai Fai Wong, Bank of America, USA.
Change 34.107 -A typo, SYSTYPE instead of &SYSTYPE caused unresolved
ANAL9914 macro because no observations were created. The correct
May 3, 2016 syntax for the report for SYSTEM=SYS1 and SYSTYPE=Z13 is
May 4, 2016 %ANAL9914(SYSTEM=SYS1,SYSTYPE=Z13);
May 5, 2016 -No longer restricted to a single system unless you use
the SYSTEM= parameter; by default reports on all SYSTEMS.
Cleans up after itself and produces NOTES to tell you
when there is a problem.
Thanks to Luis A. Mendoza, TRANSUNION, USA.
Change 34.106 z13 in SMT_MODE with SMT_NUM=2, variable NRZIPCPU, count
VMAC7072 of zIIP engines in the CEC, can be wrong in datasets
VMXG70PR PDB.TYPE70, PDB.ASUMCELP, and PDB.ASUMCEC, but is correct
Apr 30, 2016 in PDB.TYPE70PR, and variable ZIPCPUS, zIIPs online to an
LPAR, was also correct in those datasets.
-Note that IBM's CPC Report counts ONLINE ZIPs per LPAR,
but MXG's ZIPCPUS='ONLINE*AND*NOT*PARKED'
-Do NOT use the PDB.ASUM70PR nor PDB.ASUM70LP datasets;
they are by SYSTEM and thus selection is required, and
they don't have correct data on system's whose SMF data
was not read; those LPARs are in PDB.ASUMCELP.
Thanks to Elie Sawaya, Royal Bank of Canada, CANADA.
Change 34.105 Support for SMF 123 Liberty z/OS Connect EE Audit Record:
EXTY123A DDDDDD DATASET DESCRIPTION
IMAC123A TY123A TYPE123A z/OS CONNECT EE AUDIT
TYPE123A -In 2009, IBM used SMF 123 for S/390 Parallel Query Server
TYPS123A which is still in TYPE123, although I presume that record
VMAC123A is no longer created.
VMXGINIT
Apr 30, 2016
May 19, 2016
Thanks to Victoria Lepak, Aetna, USA.
Thanks to Don Bagwell, Aetna, USA.
Change 34.104 Support SMF 112 OMEGAMON CICS recorded version 530, which
VMACOMCI was not listed in the test for valid versions.
Apr 28, 2016
Thanks to Bob Duchesneau, Northwestern Mutual, USA.
Change 34.103 Support for IBM Integration Bus, Version 9.0.0.5 SMF 117
VMAC117 INCOMPATIBLE changes to the FLOW record.
Apr 28, 2016
Thanks to Ben Thompson, Northern Territory Government, AUSTRALIA.
Change 34.102 -For IFCIDs that create more than one T102Sxxx dataset,
READDB2 READDB2 needs IFCID-specific logic, but the new T102SA58
VMAC102 dataset for IFCID=58 was overlooked.
Apr 28, 2016 -Support for T102SA58 dataset in Change 34.072 was correct
only for DB2 V12 with a longer new segment; this change
supports and validates the shorter DB2 10.1 record.
-No "Truncated" name fields existed in test records so the
support for those longer 0058 names awaits test data.
Thanks to Phil Grasser, Norfolk Southern, USA.
Change 34.101 Revision to the graphics code to add a solid black line
GRAFWRKC indicating where the group cap lies on both the percent
Apr 28, 2016 CPU and the MSU charts. This required summarization of
the data so that there was only a single OBS per by
group and uses the VLINE parameter of SGPLOT. The graphs
only work if you are running SAS 9.3 or higher. If not
a message will be on the log and a PROC TABULATE will
be run instead.
Change 34.100 -ZRBASI dataset variable ASILPGSZ was incorrect.
VMACRMFV -ZRBGEI dataset variables below are now correctly divided
Apr 28, 2016 by SSHSMPNR:
May 5, 2016 GEISASL GEIRSTRF GEILCPR GEILCMO GEILF4K GEILP4K
May 16, 2016 GEILPFRI GEILPFCI GEILCMU GEILCPU GEILFPF GEILSMO
GEIRFREM GEISUSE GEILPAG GEILFUSE GEILPUSE GEIRSTRF,
and variable GEIRSHR is now kept in dataset ZRBGEI.
Thanks to Matthew Chappell, QLD Dept Transport Main Roads, AUSTRALIA
Change 34.099 zVM 6.3 z13 SMT-Mode MONWRITE support and correction.
VMACVMXA -PRCMFM (5.20) HIS SMT-Mode-Only was not as presumed. I
Apr 23, 2016 had thought the new HIS record would be like the new z/OS
Apr 26, 2016 SMF 113 Subtype 1, with interval data instead of the
May 9, 2016 accumulated fields. But the new PRCMFM is unrelated to
existing HIS counters in PRCMFC, and reports only the new
MT-diagnostic counters, with only two (MTDIA448-MTDIA449)
documented, and three others (MTDIA452,MTDIA453,MTDIA456)
are populated, but IBM has claimed them proprietary so
their content is not documented.
But all five are kept in VXPRCMFM dataset.
-PRCAPM (5.10) CRYPTO record has undefined Crypto Type 11
that is now supported after IBM z/VM Support UPDATED the
documentation today at
http://www.vm.ibm.com/PUBS/MON630/MRPRCAPM.HTML
Thanks to Wolfgang Kueller,s IT Solutions, AUSTRIA.
Change 34.098 If the same POLICY-NAME is used in different SYSPLEX, the
ANALACTM report did not print the WLM definitions because of the
Apr 23, 2016 filter criteria. This revision adds SYSPLEX variable to
protect for this unwise choice.
Thanks to Scott Barry, SBBWorks, Inc, USA.
Change 34.097 RESERVED CHANGE NUMBER.
Change 34.096 Cosmetic. Using WANTONLY=DB2ACCT,IFCIDS=ACCOUNT, READDB2
CLEARDB2 unexpectedly also created the WORK.DB2STSBP dataset; the
READDB2 READDB2 code to suppress it was not added to the MACKEEP,
Apr 21, 2016 and a typo in CLEARDB2 had changed _WDB2SBP to _WDB2SBR.
Change 34.095 -Gregorian dates were not displayed correctly in ASMRMFV
ASMRMFV message log due to incorrect leap year testing in
ADOCRMFV FINDGREG code. Dates of the form ddmmmyyyy were listed
Apr 20, 2016 as one day later than actual. Day of the week values in
Apr 27, 2016 these messages were also one day later than actual.
May 11, 2016 Julian dates of the form yyyy.ddd are correct.
-NOTE: RMFBSAM output data was NOT affected only the dates
in ASMRMFV log messages. ASMRMFV does not modify dates
in the RMFBSAM output file.
-A S0C4 Abend could occur when an VSAM I/O Read Error
happened processing the Sample Set Header (SSH) RMF III
table. This Abend was also possible processing the Data
Set Header (DSH) and Service Policy (SVP) tables.
-Several buffer handling improvements for performance are
added and described below.
-Three initial buffer size adjustments are changed to
reduce FREEMAIN/GETMAIN overhead when an increase is
needed during processing. These are applied to the 32752
RMF III VSAM Record Size to avoid buffer expansions.
Buffer Prior x Record Size New x Record Size
------------- ------------------- -----------------
Decompression 2 160
Sample 1 2
Service Policy 1 18
-Decompression buffer expansions are particularly CPU
expensive because the IBM ERB3RDEC decompression program
must decompress the data first to find out if it fits in
the buffer. If not, the buffer must be expanded and the
decompression repeated on the subsequent call.
-The increases in buffer sizes are offset by new logic
that only applies the adjustments to the first buffer
acquisition. Any subsequent expansions now only request
the actual memory needed, but should be rare. In prior
ASMRMFV versions the adjustment was applied to every
GETMAIN so the buffer areas became unnecessarily large
when several expansions of the same buffer were needed.
-In testing with 12 various RMF Monitor III data sets
buffer memory used was actually slightly less than the
current production ASMRMFV level. Your actual results
will vary. REGION=300M was used for these jobs.
ASMRMFV 33.274 ASMRMFV 34.095
LSR 16000K LSR 16000K
INDEX 32K INDEX 32K
SAMPLE 2207K SAMPLE 3198K
DECOMP 7521K DECOMP 5118K
SVP 96K SVP 1151K
====== ======
*ALL* 25855K *ALL* 25499K
Expands 6 Expands 0
-The assembler symbols &MULTD, &MULTS, and &MULTP remain
tailorable in ASMRMFV by the user as before. These set
the initial buffer size multipliers for the
Decompression, Sample, and Service Policy buffers
respectively. Any change to these values requires an
assembly and link of ASMRMFV.
-The BUFFERS parameter in ASMRMFV provides a listing after
each RMF Monitor III data set processed to show buffer
usage and expansions. Ideally expansions should be zero.
The default is NOBUFFERS and the display is suppressed.
-NOASIX parameter causes ABEND S0C4 or RMFV075W messages;
tests for this parameter were incomplete, but it is an
emergency parameter to suppress ASI extension data,if ASI
data needed to be bypassed. NOASIX causes data loss and
was intended to be used only when recommended by support.
Next ASMRMFV will correct; this is just a don't use note!
Thanks to Randy Hewitt, HPE Enterprise Services, USA.
Thanks to Randy Shumate, Reed Elsevier Technology Services, USA.
Change 34.094 PDB.JOBS observations with ABEND='JCL' were created for
BUILD005 purge records that were for job transmission. Now,
Apr 18, 2016 IF JSTRTIME=. AND SYSEXEC LE ' ' AND SYSTRANS GT ' '
Apr 19, 2016 the TYPE26J2 purge observation is output in PDB.NJEPURGE
instead of PDB.JOBS.
-Variable INTRDR is now kept in PDB.JOBS.
Thanks to Ian Porter, NISSAN-NEDC, ENGLAND.
Change 34.093 New parameter GRAPHS= with a default of YES added so that
GRAFWRKX you can specify TABULATE=YES without creating any graphs.
Apr 16, 2016 Tabulate was cleaned up so that there is only a single
table generated rather than a table for each variable.
Change 34.092 -Support for IHDRRMFV "Header" Exit member to select which
IHDRRMFV RMF III records are to be read by TYPERMFV from RMFBSAM.
IMACRMFV Your selection code can be put in member IHDRRMFV in your
VMACRMFV "USERID.SOURCLIB(IHDRRMFV)" tailoring library, or you can
VMXGINIT use the macro variable MACRMFVH "instream" to select:
Apr 13, 2016 //SYSIN DD *
Apr 15, 2016 %LET MACRMFVH= %QUOTE(IF ERBDTYPE='ASIG3'; );
Apr 21, 2016 %INCLUDE SOURCLIB(TYPERMFV);
would only populate the ZRBASI dataset.
-Removed incorrect second INPUT of CPCGRPNM/CPCGRPLM that
could cause STOPOVER INPUT STATEMENT EXCEEDED ERROR.
-These ZRBASI variables are now input as PIB versus RB:
ASI_LVSHR4KB ASI_LVSHR1MGBYTES ASI_FREEMAINEDFRAMES
Thanks to Randy Hewitt, Hewlett Packard, USA.
Change 34.091 Support for IMS Log 16x Sign On/Sign Off record creates
EXIMS16 new IMS16 dataset.
FORMATS dddddd dataset description
IMAC16 IMS16 IMS16 IMS SIGN ON / SIGN OFF
VMACIMS
VMXGINIT
Apr 15, 2016
Thanks to Gene Heikkinen, Blue Cross Minnesota, USA.
Change 34.090 TYPE115 Macro _WTY115X wasn't listed in _N115 null macro.
VMAC115 TYPECIMS Macro _WIMFMQ wasn't listed in _N116 null macro
VMACCIMS UTILBLDP, cosmetic, extra blank lines were printed in the
UTILBLDP code that clears the old style macros.
Apr 13, 2016 A new QA report will detect _Nxxxx omissions.
Thanks to Andre G. Moretto, IBM Global Technology Services/Delta, USA
Change 34.089 Support for SAMS VANTAGE User LSPOOLPO record INCOMPAT
VMACSAMS changes. These new variables in SAMSLSPC dataset:
Apr 14, 2016 SAMSBYFR ='FREE*BYTES'
SAMSCLFR ='MAXIMUM*FREE*EXTENT IN*TRACKS'
SAMSDSCBPCT='PERCENT*USED*DSCBS'
SAMSEAV ='EXTENDED*ADDRESS*VOLUME?'
SAMSFREEC ='TOTAL*FREE*SPACE IN*CYLINDERS'
SAMSHASG='GLOBAL*HASH*VALUE'
SAMSHASL='LOCAL*HASH*VALUE'
SAMSLPAR='LPAR WHERE VANTAGE RUNS'
SAMSMFEB ='MAX FREE*EXTENT*IN BYTES'
SAMSSHR ='DASD*VOLUME*SHARE*STATUS'
SAMSSUBS='SUBSYSTEM WHERE VANTAGE*RUNS'
SAMSSYSP='SYSPLEX WHERE VANTAGE RUNS'
SAMSTCYLS ='TRKMGDSPACE*TOTAL*FREE*CYL'
SAMSTEXTNT='TRKMGDSPACE*FREE*EXTENTS'
SAMSTINDEX='TRKMGDSPACE*FRAGMENTATION*INDEX'
SAMSTMCYLS='TRKMGDSPACE*MAX EXT*CYL PORTION'
SAMSTMTRKS='TRKMGDSPACE*MAX EXT*ADDL TRKS'
SAMSTTRKS ='TRKMGDSPACE*ADDITIONAL*FREE*TRKS'
SAMSTVTRKM='TRKMGDSPACE*TOTAL TRACKS'
SAMSTVTRKS='TOTAL*TRACKS ON*VOLUME'
and variable SAMSRSVD, a reserved field, is not kept.
-SAMSPOOL record was also INCOMPATIBLY changed but no
new variables were created.
Thanks to Emmanuelle Tanguy, ARKEA, FRANCE.
Change 34.088 Unused Change Number.
Change 34.087 -MXG 34.02, IMS 12.1, IMS 07 record was misaligned due to
VMACIMS 8 overlooked added bytes, and incorrect input of DLRAZAAP
Apr 12, 2016 that was added in IMS 13.1, not 12.1.2
-Zero divide fix if MXGRDTM=0 (fast read on ASCII).
-Variable LINTSY2 is formatted $HEX16.
Thanks to Paul Volpi, UHC, USA.
Change 34.086 Support for TYPE8069 RACFEVNT 8069 R_PKISERV GENCERT
EXTY8069 event, including protection for truncated TP2=322 and
IMAC80A doc errors for TP2=343 and TP2=351.
VMAC80A
VMXGINIT
Apr 8, 2016
Thanks to Joseph J. Faska, DTCC, USA
Thanks to William M. Vender, DTCC, USA.
Change 34.085 Support for these new z/VM VXSYTEMP dataset variables
FORMATS from the extended (third) segment:
VMACVMXA NCM_TCT_FCOP='FICON*OPERATIONS'
Apr 8, 2016 NCM_TCT_DFCOP='DEFERRED*FICON*OPERATIONS'
Apr 12, 2016 NCM_SCT_FCOP='SUMM COUNT*FICON*OPERATIONS'
Apr 14, 2016 NCM_TCT_FCXTM='FICON*TRANS-MODE*OPERATIONS'
Apr 21, 2016 NCM_TCT_DFCXTM='DEFERRED*FICON*TRANS-MOD*OPS'
Apr 24, 2016 NCM_SCT_FCXTM='SUMM COUNT*FICON*TRANS-MODE'
Apr 26, 2016 -Variables PCTLPABY and PCTCPCBY are now correctly
May 4, 2016 calculated AFTER the deaccumulation.
May 16, 2016 -Format $MGVXACH is updated for new Channel Types.
May 23, 2016 -Dataset VXSTOVDK variable QDIIOCNT is now deaccum'd.
-Dataset VXSYTLCK variables CALS/CALX/SYN deaccum'd.
-Dataset VXAPLSL0 is now properly deaccumulated; note that
only observations with TICKS GT 0 are output.
-Dataset VXSYTLCK variable CALSSCNT is DIF()d and SYNATT4S
second DIF() corrected to SYNFTG4S.
-Dataset VXBYUSR variables that are now deaccumulated:
VMUYPLTL0-5,VMUSTLT0-5,VMUVMTL0-5,VEBALERT/HDWAI/SVSCT/
TPIAI/TVSCT/VEBVIRAI,VMDUFOCT/UOFTM/SLCNT
-Dataset VXIODVSW is now deaccumulated with sort order
corrected.
-Some deaccumulated datasets had observations output with
DELTATM value negative; those are now correctly deleted
(they are the first instance so no deaccum is possible).
-Dataset VXMTREND now has DELTATM=. as it is not accumed.
-Dataset VXIODDEV variable VIUTIMIN's TIME12.2 reinstated.
These variables had missing values and missing labels:
RDEVSKSM64 RDEVWXCT RDEVRXCT SCMIDTIM SCMPDTIM PAVIDTIM
PAVPDTIM
-May 16: Variable ASMSSCH in dataset VXSTOASP is only two
bytes, so its accumulation wraps at a value of 65536; MXG
had incorrectly used FFFFFFFFx, causing large values.
But variable SCGSSCH is four bytes and would be safer.
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.084 The MOBWRKI2 is now updated for the new DB2STSBP data,
MOBWRKI2 preventing ERROR: FILE WORK.SUMSTSBP.DATA DOES NOT EXIST.
Apr 7, 2016
Thanks to Jan Tielemans, KBC, BELGIUM.
======= Changes thru 34.083 were in MXG 34.02 dated Apr 5, 2016========
Change 34.083 IMS56FA ARRVTIME value is wrong for transactions that
VMACIMS arrived from a system whose GMT offset is not the same as
Apr 5, 2016 this system. Now, the GMT delta between the two systems
is added to ARRVTIME when there is a difference so that
all datetime values are local to this IMS system.
Note that you must use TYPSIMST ("S" for SORT) program to
invoke the _SIMS56G for the Chain correction. Use the
JCL example in the TYPSIMST member's comments.
-The INPQUETM is a zero value if the ENDTIME of the prior
transaction in a chain is LATER than the STRTTIME of this
transaction. Why this happens is not understood yet.
-The _IMSVERS macro is NOT USED for the IMS56FA processing
because the actual version is in the 56FA record and is
used by MXG to control version differences, so multiple
IMS version's 56FA records can be processed together.
The MXG NOTE/WARN messages about _IMSVERS are removed.
Macro _IMSVERS is used ONLY for 07/08/0A/31/35/36/40/59
IMS log records, but only the 07/08 records need 10.1 or
11.1 or 12.1 to be specified and processed separately.
Thanks to Michael J. Lamdin, Verizon, USA.
Thanks to David A. Bernhardt, Verizon, USA.
Thanks to Matthew E Bogart, Verizon, USA.
Thanks to Mark Albert, Verizon, USA.
Thanks to Stephen P. Nathan, IBM, USA.
Change 34.082 DB2 Trace IFCID 196 variables QWn196HY (0-8), QW0196WY,
VMAC102 are formatted $HEX4 and INPUT $CHAR2 and QW0196W9 is
Apr 5, 2016 formatted $HEX16.
Apr 16, 2016 -Some _S102348-_S102355 dataset sort macros had repeated
PROC SORTs, but there were no errors, just wasted time.
Change 34.081 -Oracle/STC User SMF records GMTOFFTM could be "slightly"
VMACSTC wrong with a slightly larger (seconds to a minute) and a
Apr 4, 2016 non-integer value for a few observations, depending on
the SMFTIME delta to the earlier STC timestamp; the GMT
algorithm used in VMACSTC was unique and now uses the
normal calculation.
-Some VMXGTIME calls were revised, and dataset STCVSM28
has new variable REPDURTM=DURATION*OF*REPLICATION added.
Thanks to Rudolf Sauer, T-Systems, GERMANY.
Change 34.080 -z/VM 6.3.15.2 SMT MODE, BROKEN CONTROL RECORD ERROR due
VMACVMXA to new fields added to SYTCUP segment that now create:
Apr 5, 2016 LCXPMTST='PARTITION*MULTITHREADING*STATUS'
LCXHGPNM='LPAR*GROUP*NAME'
-Unrelated, CECSER was not populated in VXMTRSYS because
that 1.4 record is written before the 1.5 record that has
the CECSER is written. If you use TYPSVMXA to invoke
sorting of all datasets, this update will populate CECSER
into the VXMTRSYS dataset. Or you could use
%INCLUDE SOURCLIB(TYPEVMXA);
_SMTRSYS
_SMTRPRT
RUN;
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.079 RMF III ZRBASI dataset new variables are created/decoded:
FORMATS ASICX='ADDRESS*SPACE*TYPE'
VMACRMFV VALUE $MGRMFCX
Apr 3, 2016 'S '='S:STARTED TASK'
'T '='T:TSO'
'B '='B:BATCH'
'A '='A:ASCH'
'O '='O:OMVS'
'? '='?:UNKNOWN'
'E '='E:ENCLAVE'
'SO'='S:STARTED TASK WITH OMVS PROCESS'
'TO'='T:TSO WITH OMVS PROCESS'
'BO'='B:BATCH WITH OMVS PROCESS'
'AO'='A:ASCH WITH OMVS PROCESS'
'OO'='O:OMVS WITH OMVS PROCESS'
'?O'='?:UNKNOWN WITH OMVS PROCESS'
'EO'='E:ENCLAVE WITH OMVS PROCESS'
;
ASICR='WLM*CRITICAL*STATUS'
VALUE $MGRMFCR
'C '='C:CPU CRITICAL'
'S '='S:STORAGE CRITICAL'
'SC'='SC:BOTH CRITICAL'
;
Change 34.078 -MXG 34.01. TYPE72GO variable MSUSOFT was wrong, because
VMAC7072 the correct calculation in Change 34.010 was overridden
VMXGRMFI by the un-removed original calculation (TCBPART/SRBPART).
Apr 2, 2016 -MXG 33.33. RMF72 had MSU72, MSUINTRV, MSUPERHR variables
incorrectly containing Software MSU, while MSU4HRAV did
have the correct Hardware MSU. MXG 34.01 changed those
three variables to correctly contain Hardware MSU, and
created three new variables with Software MSU, but the
MSU4HRAV was changed to Hardware MSU. This 34.02 change
corrects MSU4HRAV also to contain Hardware MSU. The
MSU4HRAV in RMFINTRV is only the Software MSU captured
in the TYPE72GO Service Class records; the IBM Four Hour
Average Software MSU actually used for software costs is
in the TYPE70LAC variable in PDB.TYPE70.
-RMFINTRV MSU variables for Software MSU all have an "S":
Software: MSUSOFT MSUINTRVS MSUPERHRS MSU4HRAV
Hardware: MSU72 MSUINTRV MSUPERHR n/a
-MSUSOFT will be missing if ONLY type 72 records are read;
70s always precede 72s and CECSUSEC is retained from that
type 70 to calculate MSUSOFT.
Thanks to Randy Shumate, Reed Elsevier, USA.
Change 34.077 Support for optional CICSTRAN variable USERCT01.
IMACICWT
UTILEXCL
VMAC110
Apr 1, 2016
Thanks to Niels Ole Kjeldsen, KMD, DENMARK.
Change 34.076 Support for dataset TYPE80TK new variables TOKMREVOKED,
VMAC80A TOKMREVREAS and TOKMFIREACCS/
Mar 31, 2016
Thanks to Roger X Baker, GLIC, USA
Thanks to Frank Bauer, GLIC, USA.
Change 34.075 -THIS IS A FATAL ERROR AND SCRT/MWRT REPORT WILL ABEND,
MOBWRK05 if you included data with the CLOCK CHANGE hours. Your
Mar 31, 2016 MARCH REPORT MUST RUN BETWEEN APR 2-9 WITH this update.
When the clock is changed for winter/summer/daylight time
two rows were created in MWRT_LOOKUP89 that caused
"REPEATS OF BY VALUES" messages. This change keeps only
the first row and eliminates the message.
Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Thanks to Rudi Claes, KBC, BELGIUM.
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.074 The bit tests for the new TYPE0201 and TYPE0202 datasets
VMAC0203 for decoding variables SMF2IHASHMETH and SMF2ISIGTYPE
Mar 31, 2016 were missing the final "B", causing blank values.
Thanks to Robert Sample, TOMY, USA.
Change 34.073 Dataset TYPE749 (PCIE) is enhanced with new calculated
VMAC74 variables used in RMF reports.
Mar 30, 2016
Thanks to Michael Friske, FMR, USA.
Change 34.072A Support for SMF 102 IFCID 58 Added Segment creates new
EX102A58 DDDDDD DATASET DESCRIPTION
IMAC102 102A58 T102SA58 Added END SQL STATEMENT EXEC
VMAC102 See Change 33.102 (in MXG 34.03) which corrected VMAC102
VMXGINIT and validated the new data.
Mar 30, 2016
Change 34.072 RMF 73 Subtype 3 ERROR R723DNST NOT EQUAL TO R723RTYP is
VMAC7072 for the seldom-used TYPE72DL, in only one record, which
Mar 30, 2016 had one WRS pair with RTYP='CB' and RDNN=6 with six DSNTs
Mar 31, 2016 that matched, but the RTYP='DB2' pair also had RDnn=6 but
there were no segments with DSNT='DB2'. Other RTYP='DB2'
records have RDNN=0. While I believe the record is wrong,
and should have RDNN=0, IBM noted that all of the sample
counts in R723RW01-R723RW15 are zero and there could be
no name table entries, so MXG now circumvents by only
reading the name table when there are samples recorded.
(Variables R723RN01-R723RN15 are blank if no table.)
-But this investigation exposed a logic error in MXG
reading the name table; the OFFDSN was NOT incremented,
so only the first segment was being input, repeatedly,
which is now corrected.
Thanks to Lorena Ortenzi, UniCredit Group, ITALY
Thanks to Paolo Uguccioni, UniCredit Group, ITALY
Change 34.071 Cosmetic. Label for R749DBYR and R749DBYT were corrected.
VMAC42
Mar 29, 2016
Thanks to Michael Friske, FMR, USA.
Change 34.070 I/O Connect time S42CONNTM=AVGCONMS*IOCOUNT/1000 is now
VMAC42 calculated and kept in TYPE42DS, TYPE42SR and TYPE42VT
Mar 27, 2016 datasets, formatted TIME13.3.
Change 34.069 -Variable RNI is now kept in TYPE1131.
ASUM113 -The SORTED BY list had SM113STM SM113CPU transposed.
VMAC113 -Dataset TYPE1131 _KTY1131 "variable keep" macro now
Mar 24, 2016 works for both TYPE1131 and ASUM1131.
Thanks to Scott Barry, SBBWorks, Inc, USA.
Change 34.068 z/OS 2.2 SMF 73 INPUT EXCEEDED due to Split 73 record not
VMAC73 supported. VMAC73 now detects split records, but IBM
Mar 24, 2016 plans a 2ndQ APAR that redesigns the 73 split so that
Mar 31, 2016 self-contained records are written (EIX=HEN), and that
May 4, 2016 design is already supported in the existing 73 code.
These are the variables populated from the extended seg:
SMF73ECP SMF73EOC SMF73EOD SMF73EOS SMF73ETC SMF73ETD
SMF73ETS CHFRATE CHFACTV CHFDFER CHFXRATE CHFXACTV
CHFXDFER
So, if you don't have the APAR and want those variables
added, you would use n the _STY73EX macro.
%INCLUDE SOURCLIB(VMAC73,VMACSMF,IMACKEEP);
DATA _VAR73; _SMF ; _CDE73; _STY73EX;
The TEMP73EX dataset is created with the split segments
from the second (split) record (when EIX GT HEN) and the
new _STY73EX replaces the _STY73 dataset sort macro to
sort and merge TEMP73EX into TYPE73. This split record
had 158 valid channels but only 105 fit in the first 32K
record (because IBM writes 256 channel segments in every
every record, including offline, so the other 53 Extended
Channel segments were in the second record.
-May 4: APAR OA50254 eliminates the split 73 records and
each record will be self-contained with matching channel
path data sections and extended channel path sections.
Thanks to Joachim Sarkoschitz, DATEV, GERMANY
Change 34.067 z/OS 2.2 OAM SMF 85 INPUT STATEMENT EXCEEDED because MXG
VMAC85 tested R85PVRM for specific versions but not for '2020'.
Mar 24, 2016 However, that ancient test is no longer needed for the
subtypes 78,79, and 88 since all records now have the
missing early fields that needed that test, so new z/OS
versions' won't need VMAC85 to be updated for R85PVRM.
Thanks to Joachim Sarkoschitz, DATEV, DENMARK.
Change 34.066 -zVM MONWRITE dataset VXBYUSR is enhanced with these three
VMACVMXA memory variables, VMDUFACTC, VMDUFIBRC and VMDCTPNS.
Mar 21, 2016 -New: You can specify %LET MXGABND=8709; so that the
BROKEN CONTROL RECORD ERROR will now also cause the job
to ABEND with a USER 8709 abend code, so the error can't
be overlooked. (This error usually occurs when a back
level of MXG tries to read data from a new zVM version.)
Thanks to Graham Harris, RBS, ENGLAND.
Change 34.065 CICS/TS 5.3 MNSEGCL=5 INPUT STATEMENT EXCEEDED error due
VMAC110 to MXG read of 128 bytes but the segment is only 120.
Mar 21, 2016 You have to have enabled TSQUEUE Resource Class data to
populate dataset CICSRDQU to encounter this error.
Thanks to Bob Duchesneau, Northwestern Mutual, USA.
Change 34.064 -Circumvention for BBMQ Short E6 records. The last segment
VMACBBMQ in every E6 record is 4 bytes shorter than ENTL, but the
Mar 21, 2016 four bytes are unused, so this heuristic detects the last
Mar 28, 2016 record condition and the last segment is now output in
the BBMQQUES dataset (which will have more observations.)
-Circumvention for incorrect ENTL for E4 which caused the
BBMQLMGR to be trashed. ENTL=1336 in header but only 1275
exist.
-BY lists updated for NODUP removal for BBMQBUFF, BBMQCHAN
BBMQLMGR and BBMQPAGE, although no duplicates have ever
been created, just to be consistent.
-Mar 28: Datetimes were incorrectly set to GMT in 34.01.
now corrected to local.
Thanks to Jim Swinarski, Credit-Suisse, USA.
Change 34.063 ERROR START GREATER THAN END creating DBID/OBID format is
ANALDB2R corrected with this rewrite of VMFMT102 and the dropping
VFMT102 of the system and timestamps from the keys to the format.
Mar 22, 2016 The FORMATs are now the same whether you use POINTINTIME
Mar 31, 2016 or the T102S105/107 records but POINTINTIME will always
be more accurate since it is a snapshot of what DB2 sees
while the 105/107 records will only reveal databases
that have been opened.
Thanks to Jutta Gleixner-Schmid, Allianz, GERMANY
==== Changes thru 34.062 were in FINAL MXG 34.01 dated Mar 21, 2016====
Change 34.062 Cosmetic. With MXGREADSMF=LOGGER or =BOTH, log messages
VMACSMF "LAST RECORD" and the SMF Summary box of times/bytes read
Mar 17, 2016 were not printed. Superfluous code was removed.
Thanks to Chris Weston, SAS ITRM, USA.
Change 34.061 Support for BMC MAINVIEW FOR IP, creates these three
EXMVIP2C datasets of primary interest:
EXMVIP2F DDDDDD MXG MXG
EXMVIP03 DATASET DATASET DATASET RECORD
FORMATS SUFFIX NAME LABEL SUBTYPE
IMACMVIP
VMACMVIP MVIP2C TAC9I490 TN3270PERF 2C
VMXGINIT MVIP2F TAC9I350 SAWDATA 2F
Feb 26, 2016 MVIP03 TAC9I820 TACCONS 03
Mar 15, 2016
May 7, 2016 Note that IMACMVIP is tailored to only create these
May 30, 2016 three datasets.
Jun 1, 2016 Labels added Jun 1.
Aug 2, 2016 The MXG support for Mainview for IP requires the BMC
utility program BBM9MD73 to "dump" the BMC VSAM file
to a valid VB file that MXG can process.
Aug 2: SWSTOPTX corrected to local time.
CHANGE 34.060 ITRM ONLY, MXG 34.01 ONLY, CRITICAL ERROR because &PDB
VMXG70PR was used instead of &PDBMXG in two places; &PDBMXG has
Mar 15, 2016 always been the intended default macro variable for the
default "PDB" destination, and is required by ITRM.
Thanks to Chris Weston, SAS ITRM, USA.
CHANGE 34.059 Short type 119 subtype 41 with only one triplet populated
VMAC119 caused INPUT STATEMENT EXCEEDED. The record does not
Mar 14, 2016 contain any subtype 41 data. The first three instances
print a DELETED message on log.
==== Changes thru 34.058 were in THIRD MXG 34.01 dated Mar 14, 2016=====
CHANGE 34.058 MXG 34.01: CRITICAL: TYPE72GO only PERIOD 1 was output.
VMAC7072 Change 34.010 added MSU72 but used DO _I_= inside a DO
Mar 14, 2016 that already used DO _I_, which terminated the first DO.
Thanks to Randy Shumate, Reed Elsevier, USA.
=== Changes thru 34.057 were in SECOND MXG 34.01 dated Mar 14, 2016=====
CHANGE 34.057 Documentation only. Member JCLINSTT example has steps to
JCLINSTL FTP download, Unterse, and create USERID and FORMATS; new
JCLINSTT JCLINSTL example has only USERID and FORMATS create, if
VMXGCNFG you have already downloaded and untersed the new version.
Mar 11, 2016 Example DSNAMES are MXG.MXGVVNN.SOURCLIB/FORMATS in these
members and in the ftp instruction email text.
The install instructions stress that if you now depend on
the SAS NLSCOMPATMODE option to handle local characters
(British Pound, French accents, umlauts, etc.) you will
have to change your JCL for MXG to use your site's SAS
JCL procedure, with the CONFIMXG option, because SAS has
stated their intention to remove that option in a future
version.
See examples and comments in member VMXGCNFG.
//MXGSTEP EXEC SAS,CONFIG=MXG.SOURCLIB(CONFIMXG)
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
Thanks to Tom MacCabe, Dominion Resources Services, Inc., USA.
CHANGE 34.056 TYPE 60 dataset variable SMF60ELP was misaligned, VVRKEY
VMAC60 was not converted to EBCDIC text, and these address space
Mar 11, 2016 size/address variables are formatted MGBYTES
VVRDSHA VVRDSHU VVRHARBA VVRHURBA
VVRXEBA1-VVRXEBA5 VVRAMASP
Thanks to Michael Friske, FMR, USA.
CHANGE 34.055 TYPE 120 ST 9 new TYP1209R (REQUEST) and TYP1209N (ASYNC,
EXT1209N Non-Request) datasets completely replace four existing
EXT1209R TYP1209x datasets. The subtype 9 is either a REQUEST or
IMAC120 ASYNC event, and the two new datasets contain only the
VMAC120 variables that are appropriate for that event. These two
VMXGINIT new datasets eliminate the need to populate the A/C/E/S
Mar 11, 2016 datasets, which can be created with zero observations
Mar 16, 2016 by tailoring each _Edddddd "dataset output macro" to
Mar 21, 2016 replace the OUTPUT statement with a blank, either in your
Apr 11, 2016 //SYSIN for jobs that create TYPE120 datasets with
%LET MACKEEP=
MACRO _ET1209A % MACRO _ET1209C %
MACRO _ET1209E % MACRO _ET1209S %
;
or you can put the two macro lines in your IMACKEEP
member in your USERID.SOURCLIB tailoring PDS/directory.
Mar 21:
-The TYP1209U CPU detail dataset contains up to 20 obs
per event, and variable REQASYNC identifies the event,
and added variables identify the source of that event.
The CPU detail dataset metrics are summarized into the
TYP1209N or TYPE1290R dataset.
-The 1209C and 1209S segments have three or 12 obs per
event, so new variables SM1209ES1-SM1209ES3 and
SM1209EO1-SM1209E12 are created with those IDENTITY and
CLASSIFICATION values, eliminating any need for
TYP1209C/TYP1209S datasets. And new variable REC1209SEGS
identifies which segments were populated in each
TYP1209R/TYP1209N/TYP1209U observation.
-The order of segment processing was revised.
-The value of SM1209CI can be negative: That means that
the request didn't finish. The TCB CPU time at the start
is held, and the TCB CPU time at the end is subtracted to
get the SM1209CI value. If the servant abended or some
other bad thing happened and the request never finished,
there was no 'end time', so you get a negative value.
It's actually an indicator that something went wrong!
Apr 11: Labels for the CPU variables are clarified:
SM1209DA='ENCLAVE*TOTAL*CPUTIME'
SM1209DB='ENCLAVE*ZAAP*CPUTIME'
SM1209DC='ENCLAVE*ZAAP*ELIGIBLE*ON CP'
SM1209DD='ENCLAVE*ZIIP*ELIGIBLE*ON CP'
SM1209DE='ALWAYS*ZERO*QUALIFIED*CPU TIME'
SM1209DF='ENCLAVE*ZIIP*TIME*ON ZIIP'
SM1209HG='ENCLAVE*TOTAL CPUTIME'
SM1209HH='ENCLAVE*ZAAP*CPUTIME'
SM1209HI='ENCLAVE*ZAAP*ELIGIBLE*ON CP'
SM1209HJ='ENCLAVE*ZIIP*ELIGIBLE*ON CP'
SM1209HK='ALWAYS*ZERO*QUALIFIED*TIME'
SM1209HL='ENCLAVE*ZIIP TIME*ON ZIIP'
Thanks to Joesph Faska, DTCC, USA.
Thanks to Betty Wong, Bank of America, USA.
CHANGE 34.054 Variable SMF42LAN was not converted to EBCDIC after the
VMAC42 INPUT SMF42LAN $VARYING64. causing unprintable text.
Mar 10, 2016
CHANGE 34.053 BMC APPTUNE FIX BPU8604 caused INPUT STATEMENT EXCEEDED
VMAC102 error for subtype 8005x because the R8 triplet has R8N=1,
Mar 10, 2016 R8O=1512 with R8L=0 in a record that is only 1511 bytes
long. That INPUT is now skipped when the R8L is zero,
pending a correction from BMC.
Thanks to Rudi Claes, KBC, BELGIUM.
CHANGE 34.052 WPS Only, First MXG 34.01 Only. A typo RUN: with colon
VMXGINIT in line 3667 of VMXGINIT must be deleted as it caused
Mar 10, 2016 WPS to fail to initialize. I would have normally caught
this in my QA with that ABEND, but my SETINIT expired and
I had a condition code rather than an ABEND overlooked.
CHANGE 34.051 Change 33.240 updated MACRO _IO30TM but had replicated
IMAC30IO IOTM3390 causing WARINING: VARIABLE IOTM3390 EXISTS.
Mar 10, 2016 Delete the second IOTM3390.
Thanks to Randy Shumate, Reed Elsevier, USA.
CHANGE 34.050 Variables SM1209CM, SM1209CR, SM1209CS were incorrectly
VMAC120 kept in datasets TY1209C, TY1209S, and TY1209U, and were
Mar 9, 2016 used incorrectly in the _ST1209C and _ST1209U BY lists,
so combining multiple PDBs build with and without this
change could fail with a NOTSORTED error on either.
This Change was included in 34.055, above.
Thanks to Joesph Faska, DTCC, USA.
CHANGE 34.049 Support for ASG/TMON Version 4.0 for CICS, REQUIRED.
VMACTMO2 Version changed all duration fields from microsecond to
Mar 9, 2016 todstamp units, but these 15 variables were not divided
by 4096 (the other 399 were), so these variables will
have values larger by that 4096 factor.
CICOVHTM FILEIOTM TAARQRTM TAARQWTM TAAWTTTM TAAWTWRT
TADSPCPU TADSPDTM TADSPSTM TADSPWRT TATCBSTM TATCBSTM
TATCBSTM TIIWTWRT TMCGADT
Fortunately, none of these duration variables are in the
primary MONITASK dataset.
Thanks to Miguel Machin, CAREFIRST, USA
Thanks to Alan Gray, CAREFIRST, USA.
=== Changes thru 34.048 were in FIRST MXG 34.01 dated Mar 7, 2016======
CHANGE 34.048 Support for BE93 Version 6.1.0 (INCOMPATIBLE, header was
VMACBETA relocated). No new variables nor datasets.
Mar 7, 2016
Thanks to Rudolf Sauer, T-SYSTEMS INTERNATIONAL GmbH, GERMANY.
CHANGE 34.047 Support for z/OS 2.2 RMF III data records.
VMACRMFV -No change is needed for the ASMRMFV program that reads
Mar 6, 2016 the Compressed VSAM file to create the RMFBSAM data file.
-New variables in ZRBASI dataset:
ASICPUTA_LF ='CPU*TIME'
ASIDCTIA_S ='CHANNEL*CONNECT*TIME'
ASIDP ='DISPATCHING*PRIORITY'
ASIFRXA_LF ='FIXED*FRAMES*ABOVE'
ASIFRXB_LF ='FIXED*FRAMES*BELOW'
ASIFRXH_LF ='FIXED*FRAMES*HIGH'
ASIIOCNT_S ='EXCPS'
ASIQSCANRES ='QSCAN*RESOURCES*RETURNED'
ASIQSCANRESSQ1 ='QSCAN*ASIQ*SCANRES*SSQ1'
ASIQSCANRESSQ2 ='QSCAN*ASIQ*SCANRES*SSQ2'
ASIQSCANSPECREQ='QSCAN*SPECIFIC*REQUESTS'
ASIQSCANTIME ='QSCAN*REQUESTS*ISSUED'
ASIQSCANTIMESQ1='QSCAN*ASIQ*SCANTIME*SSQ1'
ASIQSCANTIMESQ2='QSCAN*ASIQ*SCANTIME*SSQ2'
ASITCBTA_LF ='TCB*TIME'
ASITRCA_S ='TRANSACTIONS'
ASITRT ='TRANSACTION*RESIDENT*TIME'
ASI_FREEMAINEDFRAMES='FREEMAINED*FRAMES'
ASI_HVSHRPAGEVALIDATIONS='PAGE*VALIDATONS*HI SHARE'
ASI_LVSHR1MGBYTES='HWM*HIGH*VIRTUAL*SHARED'
ASI_LVSHR1MNMOMB='SHARED*1M*MEMORY*OBJECTS'
ASI_LVSHR4KB ='SHARED*BYTES*HI VIRT'
-New variables in ZRBCPU dataset:
CPC_ATD_AAP ='AVERAGE*THREAD*DENSITY*AAP'
CPC_ATD_CP ='AVERAGE*THREAD*DENSITY*CP '
CPC_ATD_IIP ='AVERAGE*THREAD*DENSITY*IIP'
CPC_CAPF_AAP ='MT CORE*CAPACITY*FACTOR*AAP'
CPC_CAPF_CP ='MT CORE*CAPACITY*FACTOR*CP '
CPC_CAPF_IIP ='MT CORE*CAPACITY*FACTOR*IIP'
CPC_MAXCAPF_AAP='MT CORE*MAXIMUM*CAPACITYAAP'
CPC_MAXCAPF_CP ='MT CORE*MAXIMUM*CAPACITYCP '
CPC_MAXCAPF_IIP='MT CORE*MAXIMUM*CAPACITYIIP'
CPC_MODE_AAP ='MT CORE*MODE*AAP'
CPC_MODE_CP ='MT CORE*MODE*CP '
CPC_MODE_IIP ='MT CORE*MODE*IIP'
CPC_PROD_AAP ='MT CORE*PRODUCTIVITY*AAP'
CPC_PROD_CP ='MT CORE*PRODUCTIVITY*CP '
CPC_PROD_IIP ='MT CORE*PRODUCTIVITY*IIP'
CPU_PARK_CP ='PARKED*TIME*CP'
CPU_PARK_IFA ='PARKED*TIME*IFA'
CPU_PARK_ZIP ='PARKED*TIME*ZIP'
CPU_ONLINE_CP ='ONLINED*TIME*CP'
CPU_ONLINE_IFA ='ONLINE*TIME*IFA'
CPU_ONLINE_ZIP ='ONLINE*TIME*ZIP'
-New variables in ZRBGEI dataset:
GEILSMO ='MEM OBJ*HI VERT*BACKED IN*1MB FRAMES'
GEIRFREM='FREEMAINED*FRAMES*ALL ASIDS'
CHANGE 34.046 ASUMCACH now works without RMF III data and supports tape
ASUMCACH or disk. When the PDB is on tape, TYPE74 is copied to
Mar 5, 2016 //WORK to prevent having two open tape datasets.
Change 34.045 JES2 SMF 26 z/OS 1.13 TRIPLET segment before PRINT caused
VMAC26J2 INPUT STATEMENT EXCEEDED ERROR on z/OS, or a FLOATING
Mar 5, 2016 POINT EXCEPTION on ASCII. The unexpected order
misaligned the input of offset variable SMF26OJC to have
a value of 3,806,577,725, which then caused the error
when INPUT @SMF26OJC was executed with that large value.
The SMF manual has always shown all 7 segments at offset
50, so it's the order in the SMF manual that has
previously defined their order in the record. This
change heuristically detects the order of those two
segments.
-Change 33.046 added support for the SMF26JCR field in MXG
33.02 last year, and that new code failed on the reversed
records at this one site, where all records on some
systems were reversed, and all records on other systems
had the correct segment order.
Thanks to Rich Kuehn, Global eXchange Services, Inc., USA.
Change 34.044 New Capacity Group reports of CEC resources consumed by
ANALGRCA LPARS within a capacity group by RMFINTRV workloads,
GRAFWRKC reporting percent CPU, total CPU time, estimated hourly
Mar 6, 2016 software MSU, and memory consumption by workloads and
then by LPAR.
ANALGRCA and GRAFWRKC both report on Group Capacity.
A good place to start is gragwrkc - it will take your
RMFINTRV dataset and build a picture by CEC and Capacity
Group of %CPU busy, CPU time, estimated hourly MSU, and
memory with a pair of graphs for each, the first by your
RMFINTRV workloads, the second by LPAR within the
Capacity Group. You can narrow down the squeaky wheel
to a workload and/or lpar, and then you can use ANALGRCA
to fine tune the analysis.
ANALGRCA will do much the same thing but lets you zero-in
on what is pushing you to the cap or to a threshold you
specify. The threshold can be an absolute number of MSU
or a percentage of the total group capacity. It will look
at the LPARS in the group using ASUMCELP, the workloads
using RMFINTRV, and the SMFINTRV dataset to look at
tasks. There are parameters to specify the date to
examine, the interval to use (but it must be the same as
the cecintrv in asumcelp.) and for workload and job level
data only those intervals that exceeded the threshold are
used in reporting.
CHANGE 34.043 MXG 33.33. Change 33.316 missed the four reserved bytes,
VMAC71 causing SMF71CPx, SMF714Kx, & SMF71PLx to be misaligned.
Mar 2, 2016
Thanks to Rick Southby, Insurance Australia Group, AUSTRALIA.
CHANGE 34.042 Support for DCOLLECT FLAG4 bits that indicate each
VMACDCOL size variables are now in MegaBytes, previously in
Mar 7, 2016 KiloBytes, in DCOLBKUP and DCOLMIGS datasets.
Mar 8, 2016 -Mar 8. UBALLSP and UMALLSP 024* changed to 1024*.
Mar 22, 2016 -Mar 22. All ten UBFLAG and UMFLAG bit tests corrected.
May 8, 2016 -May 8: Change 34.112 corrected UBDSIZE high by 1024.
Thanks to Scott Barry, SBBWorks, Inc., USA.
CHANGE 34.041 Support for ATF V531 Enhanced Summarization Phase 2
FORMATS inserted these new variables:
VMACATF ATFPGMSW ='PROGRAM*SWITCHES'
Mar 6, 2016 ATFXSNOTN='OTHER*ITEMS**VAR'
Mar 9, 2016 ATFXSNOTL='OTHER*ITEMS**LENGTH'
Apr 5, 2016 ATFXSUOW ='TRANSACTION*UOW'
and the DLI-DB/DLI-TM/DBD/DB2/MQ/OTHERA/OTHERB segments
have new GROUP BUCKET NUMBERs and/or ITEM CODES that are
decoded in new FORMATS.
-Mar 9: (after 34.01) Short 8-byte DBD supported, DLI DB
and DLI TM and OTHER-A segments have been validated.
-Apr 5: Variables ATFXSRSP ATFXSACP ATFXSIQT were wrongly
divided by 4096 twice.
CHANGE 34.040 TYP11921 variable NTHOSTTN is increased from $8 to $64 to
VMAC119 support host names that are fully qualified TCP/IP domain
Mar 2, 2016 name.
Thanks to Stephen S. Hoar, Lloyds Banking, ENGLAND.
Thanks to Gary Nash, Lloyds Banking, ENGLAND.
CHANGE 34.039 Support for new SMF Type 29 IMS JAVA CPU and Garbage Coll
EXTY29GC creates new datasets
EXTY29JA DDDDDD MXG MXG
IMAC29 DATASET DATASET DATASET
TYPE29 SUFFIX NAME LABEL SUBTYPE
TYPS29
VMAC29 TY29GC TY29GC IMS JVM GARBAGE COLLECTION 2
VMXGINIT TY29JA TY29JAVA IMS JVM CPU USAGE 2
Mar 2, 2016 See Change 34.221 which revised and validated with data.
CHANGE 34.038 New variables created in TYPE1209 dataset:
VMAC120 SM1209HE='ENCLAVE*JOINED OR*CREATED?'
Mar 1, 2016 SM1209HF='ENCLAVE*SCHEDULED?'
Thanks to Joseph Faska, DTCC, USA.
CHANGE 34.037 Using %LET MXGREADSMF=BOTH caused ERROR 181-185 VARIABLE
VMACSMF SMFINFILE already exists. Code revised to use LOGINFILE
Feb 28, 2016 variable for the INFILE LOGGER.
Thanks to Chris Weston, SAS ITRM, USA.
CHANGE 34.036 TYPE30_5 dataset can have ABEND='SYSTEM' CONDCODE=0000 if
FORMATS a step had a SYSTEM or USER ABEND, but the last step did
VMAC30 not ABEND (e.g., a FLUSH step followed the ABEND). Since
Mar 1, 2016 the type of ABEND is unknown in the TYPE30_5 JOB record,
MXG now sets ABEND='ABEND' instead of ABEND='SYSTEM' in
TYPE30_5. However, in PDB.JOBS, MXG populates both ABEND
and CONDCODE from the LAST step that ABENDed, so you will
not see ABEND='ABEND' except in TYPE30_5. And, since it
is really STEPS that ABEND, and not JOBS, you should use
the PDB.STEPS or TYPE30_4 for ABEND analysis.
Thanks to Linda S. Berkley, USPS, USA.
CHANGE 34.035 These SYNCSORT variables are now kept, formatted $HEX2:
VMACSYNC SYNRETRY='RETRY*FLAG'
Feb 25, 2016 SYNMISCF='SMFFLAG3*MISC*FLAG'
Thanks to Bruce Bordonaro, Pershing, USA.
CHANGE 34.034 Reserved Change Number.
Feb 28, 2016
CHANGE 34.033 Change 31.118 added new fields in the EXGRXEXT (Extended
VMACEDGR Record), but those fields are also in the basic dataset
Feb 28, 2016 records EDGRDEXT and the volume records EDGRVEXT, and
this change adds them to those two datasets.
Thanks to Thomas Giordano, Australian Defence Department, AUSTRALIA.
CHANGE 34.032 Support for DB2 Trace IFCIDS 311 and 321.
VMAC102
Feb 24, 2016
CHANGE 34.031 Cosmetic. If your _IMSVERS does not match the version in
VMACIMS the IMS56FA record, the previous MXGNOTE is now MXGWARN.
Feb 24, 2016 and the text is clearer when they do match.
CHANGE 34.030 TYPE42D4 DATASET variables SMFA2GTAA & SMFA2GTAB are now
VMAC42 correctly INPUT and kept, replacing incorrectly spelled
Feb 22, 2016 SMFA2GSA and SMFA2GSB, with the CA and CI Splits.
Thanks to Michael Friske, FMR, USA.
CHANGE 34.029 Variables SMF70GNM and SMF70GMU added to PDB.RMFINTRV to
VMXGRMFI enable reporting of workloads by Capacity Group.
Feb 22, 2016
Change 34.028 MXG 33.33. ASUM70PR Change 33.306 required PDB.TYPE70 to
VMXG70PR exist in the //PDB data library, so the group capacity
Feb 22, 2016 metrics could be created, but it was not documented that
that the TYPE70 dataset was required. Normally TYPE70 is
in the PDB with the TYPE70PR dataset, but if TYPE70 was
not found in the //PDB library, the ASUM70PR failed.
Now VMXG70PR verifies that TYPE70 exists and uses it if
found, or does not read it if not found, which causes the
new Group Variables to not exist in the ASUM output.
Or, with 33.33 you can circumvent the error using this
code ahead of your ASUM70PR include:
%LET MACKEEP=%QUOTE( MACRO _LTY70 NEWPDB.TYPE70 % );
Change 34.027 MXG set the TYPE1131 CPU Speed SM1132SP to 5000 for z13
VMAC113 because early records contained either 5208 for CP or had
Feb 22, 2016 ZERO for the IP speed. But that is now wrong with the new
Feb 29, 2016 sub-capacity z13s (Speed=3173), so the logic now forces
the 5000 value only if the record contains zero or 5208.
Thanks to Andrew Hebden, Barclays, ENGLAND.
Change 34.026 Support for MVMQ (BBMQ) PTF BPL2558 which was to change
VMACBBMQ all duration fields from TODSTAMP to microseconds, but
Feb 22, 2016 BMC now reports that pre and post that PTF, the values
Mar 10, 2016 have always been in seconds with microsecond fractions.
Mar 22, 2016 MXG was dividing by 4096 presuming TODSTAMP, which is
known to have always been wrong and is now corrected.
Apparently, the primary use has been counts and events
and not durations, as no one noticed!
-Mar 10: Cosmetic typo QSCLOSETTIME to QSCLOSTTIME.
-Unrelated, but observed, that all character date/times
were on GMT zone; new datetime numeric variables replace
them and are set to the local time zone.
Change 34.025 Dataset TYPE70EN, variable PCTMVSBY=100 was incorrectly
VMAC7072 calculated when SMF70PAT, Parked Time, was close to the
Feb 12, 2016 DURATM, but did not exactly match. A 1 second delta is
now required to calculate a non-zero PCTMVSBY=0.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 34.024 Dataset TYPE72GO, variable RESPSTD, Standard Deviation of
VMAC7072 Response time was 2% larger than IBM Value; the 1.04875
Mar 1, 2016 conversion factor is corrected to 1.024.
Thanks to Richard Stuchell, VISA, USA.
Change 34.023 Parameter list was alphabetized and the parameters used
UTILBLDP are displayed on the log. A check was added to the list
Feb 12, 2016 of parameters where an = should not exist as that is
normally an indication that a comma was left off of one
of the parameters.
Change 34.022 -DB2STAT2 statistics dataset new variables:
VMACDB2 QDBPFRAM='FRAMESIZE'
Feb 11, 2016 QDBPVPMI='VPSIZEMIN'
Feb 28, 2016 QDBPVPMA='VPSIZEMAX'
Mar 23, 2017 QDBPSPSZ='SIMULATED*BUFFER*POOL*SIZE'
QDBPSPST='SIMULATED*SEQ*THRESHOLD'
-DB2ACCTP Package dataset, new flag variable
QPACINCO='INCOMPATIBLE*FUNCTION?'
-Documentation: In DB2ACCTP, if QPACRUSM='Y', these fields
are listed by IBM as invalid:
QPACCRNT QPACINSP QPACPAC QPACPKNM QPACCOLN QPACPKID
QPACCONT QPACSCB QPACSCE QPACBJST QPACEJST QPACASCH
QPACAANM QPACAAFG QPACINCO
-Added Mar 23, 2017:
Existing Rollup flag variable DB2PARTY='R' is also set
if QPACRUSM, the new Rollup Summary flag variable is set.
When DB2PARTY='R', the four datetime variables above
QPACBJST QPACEJST QPACSCB QPACSCE
are always zero for BJST/EJST and missing for SCB/SCE.
Those were the individual package event datetimes that
are lost with DB2 ROLLUP summarization.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 34.021 CICSTRAN variable TRANFLAG creates variables from each
FORMATS byte, some are decoded with new formats:
VMAC110 TRANFLAGTF='TRANFLAG*TRANSACTION*FACILITY*NAME'
Feb 12, 2016 VALUE $MGCICTF
'0'='BIT0:NONE'
'1'='BIT1:TERMINAL'
'2'='BIT2:SURROGATE'
'3'='BIT3:DESTINATION'
'4'='BIT4:3270 BRIDGE'
;
TRANFLAGID='TRANFLAG*TRANSACTION*IDENTIFICATION'
VALUE $MGCICTI
'0'='BIT0:SYSTEM TRANSACTION'
'1'='BIT1:MIRROR TRANSACTION'
'2'='BIT2:MIRROR TRANSACTION DPL'
'3'='BIT3:ONC RPC ALIAS TRANS'
'4'='BIT4:WEB ALIAS TRANSACTION'
;
TRANFLAGWL='WLM*STATUS'
VALUE $MGCICWL
'0'='BIT0:WLM REPORT'
'1'='BIT1:WLM NOTIFY COMPLETION'
'2'='BIT2:WLM NOTIFY'
;
TRANFLAGIN='INDOUBT*STATUS'
VALUE $MGCIC8I
'0'='BIT0:INDOUBT WAIT=NO'
'1'='BIT1:INDOUBT ACTION=COMMIT'
'2'='BIT5:INDOUBT FAILURE'
;
TRANFLAGUO='UOW*STATUS'
VALUE $MGCIC8U
'0'='BIT2:UOW INDOUBT ACTION'
'1'='BIT3:UOW SHUNT'
'2'='BIT4:UOW UNSHUNT'
'3'='BIT5:INDOUBT FAILURE'
;
TASKDATALOC='TASKDATALOC*BELOW?'
TASKDATAKEY='TASKDATAKEY*CICS?'
TASKISOLATE='TASKISOLATE*NO?'
TASKDYNAMIC='TASKDYNAMIC*YES?'
Thanks to Perry Lim, Union Bank, USA.
Change 34.020 PK-ZIP SMF records INPUT STATEMENT EXCEEDED error due to
VMACPKSZ one field expanded from 2 to 4 bytes.
Feb 10, 2016
Thanks to Dorothy Yeung, Toyota, USA.
Change 34.019 -STC Variables STC26MST & STC26MET were on GMT time zone,
FORMATS now corrected to local to match other datetimes.
VMACSTC -STC variables STCxxADR were $HEX8 formatted, but that
Feb 9, 2016 is removed as they contain EBCDIC text, not HEX.
Feb 11, 2016 -STC variables STCxxRID are now HEX4 formatted, as they
Feb 24, 2016 contain numeric hex values.
-New format $MGSTCMV maps values in variable STC16MVC.
-New variables decode bits of SMF17DFL:
STC17DRX='RETENTION*PERIOD*REDUCED?'
STC17DAR='AUTO*RECALL?'
STC17DMF='FULL*MVS?'
STC17DYV='RTD*VARY*COMMAND?'
STC17DSW='MVC OR*RTD*REQUIRED?'
STC17DRT='RETAIN*PERIOD*APPLIED?'
and RID variables show 0-F as their range.
-STC11TOL has a third value now supported.
-STC11CSP is relabeled CHANNEL TYPE and formatted.
-Some labels with "MVS" are corrected to "MVC".
Thanks to Randy Hewitt, Hewlett Packard, USA.
Change 34.018 Reserved Change Number.
Change 34.017 Support for NDM-CDI SE Session End record creates
EXNDMSE DDDDDD DATASET DESCRIPTION
IMACNDM NDMSE NDMSE NDM SESSION END
VMACNDM
VMXGINIT
Feb 8, 2016
Thanks to Gerard Bosker, RaboBank, THE NETHERLANDS.
Change 34.016 New variables in MAR 02 record.
VMACMAR TO DO: Subtype 7. Await data in March.
Feb 6, 2016
Change 34.015 New analysis of Group Capacity.
ANALGRCA Inputs are PDB.RMFINTRV,PDB.SMFINTRV,PDB.ASUMCELP.
Feb 6, 2016 See Change 34.044 for GRAFWRKC and a comparison.
Change 34.014 Support for Rocket Software DVS User SMF record ST 1 & 2.
EXDVS01 New datasets created
EXDVS02 DDDDDD DDATASET DESCRIPTION
IMACDVS DVS01 DVS01 DVS CLIENT SYSTEM RECORD
TYPEDVS DVS02 DVS02 DVS INTERVAL SUMMARY RECORD
TYPSDVS -The DVS01 interval dataset is written for each Connection
VMACDVS ID, variable DVS1CNID.
VMXGINIT -Mar 3: The two lines in the LENGTH statement extended
Feb 5, 2016 beyond 72 characters; on z/OS only, those variables
Mar 3, 2016 were kept in 4 instead of 8 stored bytes, so there would
have been some truncation of datetime values, worst case
255 seconds.
Change 34.013 DB2 dataset T102S166 for IFCID 166 variable QW0166SI is a
VMAC102 statement identifier input $CHAR8 and format $HEX16, but
Feb 4, 2016 it is the statement number, so new variable QW0166SINR is
the numeric statement number; labels clarified.
Thanks to Akhil Vasudevan, Capital One, USA.
Change 34.012 MSU chart modified to reflect an estimated hourly MSU
GRAFWRKX value so that you can see which workloads are making
Feb 2, 2016 the largest contributions to the rolling 4 hour avg.
Change 34.011 -MXG 33.33 with ITRM can cause these errors:
ITRM ERROR: File WORK.SUMSTSBP.DATA does not exist.
Feb 2, 2016 because the new DB2STSBP dataset is now added into the
PDB.DB2STATS dataset, but the new _SDB2SBP sort macro
was not known in ITRM ("NEW"!).
-The correction is easy for BUILDPDB:
ITRM 2.7: Originally reported in 33.301 and MXG 33.33 GA:
ITRM users MUST add this statement
%LET EPDBOUT= _SDB2SBP;
inserted between %CMPROCES... and %CPSTART....
ITRM 3.4-3.6: New in this change:
ITRM users MUST add
%LET EPDBOUT= _SDB2SBP ;
at the top of their SYSIN input.
-For TYPSDB2 program, instead of BUILDPDB, create a new
TYPSDB2 member in your USERID.SOURCLIB "tailoring"
library with these statements:
%INCLUDE SOURCLIB(VMACSMF,VMACDB2,IMACKEEP);
DATA
_VARDB2
_SMF
_CDEDB2
_SDB2SBP
_SDB2
-ITRM 3.7, when released later this year, eliminates this
exposure by invoking the _SDB2 macro which MXG protects.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 34.010 -TYPE72GO variable MSU72, HARDWARE MSU, was re-labeled and
GRAFWLM variable MSUSOFT corrected and also re-labeled:
VMAC7072 MSU72 ='CAPTURED*HARDWARE*MSU 72*COUNT*NOT A RATE'
VMXGRMFI MSUSOFT ='CAPTURED*SOFTWARE*MSU 72*COUNT*NOT A RATE'
Feb 4, 2016
HARDWARE MSU: ORIGINAL MSU SU_SEC BASED - LARGER
SOFTWARE MSU: NEW MSU SMF70CPA/CECSUSEC BASED, for
SOFTWARE PRICING.
MSUSOFT can be a missing value if no prior RMF 70 for
this system was found, since it needs SMF70CPA from the
same-system's RMF 70 to calculate in the RMF 72 code.
-These MSU variables are created in RMFINTRV and TRNDRMFI
with per interval values:
MSUINTRV ='TOTAL*HARDWARE*MSU 70*COUNT*NOT A RATE'
MSUPERHR ='TOTAL*HARDWARE*MSU 70*EXTENDED*HOURLY RATE'
MSUINTRVS='TOTAL*SOFTWARE*MSU 70*COUNT*NOT A RATE'
MSUPERHRS='TOTAL*SOFTWARE MSU 70*EXTENDED*HOURLY RATE'
-New Workload XXXXMSU variables (BATMSU,CICSMSU) and
XXXXMSUS (BATMSUS,CICSMSUS) variables for each workload
are created with these labels:
BATMSU ='BATCH*CAPTURED*HARDWARE*MSU 72*COUNT'
BATMSUS ='BATCH*CAPTURED*SOFTWARE*MSU 72*COUNT'
-New chart of estimated hourly MSU used by IMPORTANCE in
GRAFWLM (need all three of these updated members).
Change 34.009 -BASECICS and BASEDB2 parameters added to match VMXGALOC
VGETALOC logic and allow for different directories to hold the
Feb 2, 2016 often large CISTRAN/DB2ACCT datasets.
-The message that a LIBNAME could not be found is now
suppressed unless MXGEXIMSG is YES.
Change 34.008 -WebSphere variable WTASCTSR was 4096*E6 too large, as it
VMAC115 was input as PIB8 instead of PIB8.6 and was missing the
VMAC116 2016 the required divide by 4096 to convert to seconds.
Jan 29, 2016 -New variables added to MQMACCTQ dataset.
Feb 12, 2016 WTASPBHW='PUBLISH*HIGH*WATER*MARK'
WTASPBTT='PUBLISH*TOTAL*ELAPSED*TIME'
WTASPRCT='PREPARE*CPU*TIME'
WTASPRET='PREPARE*ELAPSED*TIME'
WTASPRN ='PREPARES'
WTASSMRB='MESSAGE*BLOCKS*READ FROM*SMDS'
WTASSMRP='PAGES*OF DATA*READ FROM*SMDS'
WTASSMRS='SMDS*READS SAVED*DATA IN*BUFFER'
WTASSMWB='MESSAGE*BLOCKS*WRITTEN TO*SMDS'
WTASSMWP='PAGES*OF DATA*WRITTEN TO*SMDS'
WTASSMWT='WAIT TIME*FOR SMDS I/O*COMPLETION'
WTASTPCT='TOPIC*CPU*TIME'
WTASTPET='TOPIC*ELAPSED*TIME'
WTASTPN ='TOPIC*COUNT'
Variable WTASCTSR is corrected in value and formatted
as TIME16.6.
-Type 115 dataset TYPE115S variable QESDBFPT was wrong;
it contained QESDBFBT instead of BFPT.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 34.007 Change 33.153 for IMF/MAINVIEW FOR IMS for IMF 5100 was
VMACCIMS not correct, because new variables only in 5200 were read
Jan 26, 2016 when they should not have been. Logic revised for 5100.
Thanks to Betty Wong, Bank of America, USA.
Change 34.006 -Change 33.024 incorrectly overlaid UTILRMFI with UTILWORK
UTILRMFI when the SYSOTHER message was added, which eliminated the
UTILWORK report.
Jan 25, 2016 -UTILRMFI generates reports using your RMFMINTRV WORKnn
definitions, finding any duplications, by comparing the
SMF30s and RMF72s CPU times.
-UTILWORK generates a skeleton RMFINTRV member based on
SERVICE class or REPORTING class.
Thanks to Michael Gebbia, Eddie Bauer, USA.
Change 34.005 -Support for zVM HIS (SMF 113) PDB.VXPRCMFC accumulated.
VMAC113 -Support for zVM HIS (SMF 113) PDB.VXPRCMFM intervaled.
VMACVMXA Dataset VXPRCMFC is the old SMF 113 subtype 2 accumulated
Jan 30, 2016 and VXPRCMFM is the newer SMF 113 subtype 1 intervaled,
Feb 8, 2016 and only VXPRCMFM will be updated by IBM in the future.
Feb 25, 2016 -SMF 113 EXTND counter labels for z13 were incorrect; the
Feb 27, 2016 values and equations were correct, and now both VMAC113
Feb 29, 2016 (z/OS) and VMACVMXA (z/VM) have the same labels, which
default to the labels for the z13 counters.
(See Change 31.172 to change _XLA113 to earlier CPUs.)
-All zVM MONWRITE VXdddddd datasets now have SYSTEM kept
(most did), and all now have CECSER to identify both the
software and hardware identifications.
-RNI for zEC12 was updated to use 2.3 factor in VMACVMXA.
-All calculated variables for the zEC12 were wrong; while
VMAC113 was updated, VMACVMXA was not for VN2=3 data.
-Support for Multiple CECs/SYSTEMs zVM data changed the
sort order of all datasets by inserting CECSER SYSTEM
ahead of BEGINMTR: BY CECSER SYSTEM BEGINMTR other vars.
Thanks to David Cogar, Wells Fargo, USA.
Thanks to Carl D. Ellis, Wells Fargo, USA.
Change 34.004 End Comment was missing around JCL example, caused 180
FDRCRYPT syntax error.
Jan 20, 2016
Thanks to Michael Gebbia, Eddie Bauer, USA.
Change 34.003 A tailored BUILDPDB created a libname with view that
PDBAUDIT caused an error when a PROC SQL read DICTIONARY.TABLES
Jan 28, 2016 and returned a LIBNAME of _TMPLIB that didn't exist:
ERROR: FILE _TMPLIB.XTY70CP.DATA DOES NOT EXIST.
The error was in PROC SQL FROM DICTIONARY.TABLES and was
difficult to diagnose as there are NO other references on
the log to either that libname or that dataset name. This
similar example causes an obscure LIBREF not found error:
LIBNAME FRED (SASUSER);
DATA FRED.DATA;
A=1;
RUN;
PROC SQL;
CREATE VIEW WORK.WILMA AS SELECT * FROM FRED.DATA;
QUIT;
LIBNAME FRED CLEAR;
PROC SQL;
CREATE TABLE TABLES AS SELECT *
FROM DICTIONARY.TABLES WHERE LIBNAME='WORK';
QUIT;
The error message is that libref FRED is not assigned,
but if you weren't the author of this code, you wouldn't
have had a clue that you needed a libref called FRED.
-This MXG change excludes MEMTYPE EQ 'VIEW' from PROC SQL
since only real data libraries are wanted in PDBAUDIT.
-PDBAUDIT already skips reports on known SAS LIBNAMES,
since its purpose is to audit YOUR data libraries;
these additional LIBNAMES are also now skipped:
APFMTLIB CTRLLIB ITMACR MAILLIB
STMFMT STPSAMP ZOSRSTG1
-The PDBAUDIT report can be skipped if you chose, using
%LET MXGPDBAUDIT=NO;
in your SYSIN input.
Change 34.002 HSMFSRST dataset contains three dates (READ,REQUEST,SMF)
ASUMHSM but four times (REQUEST, ALLOC, START, END) have no date,
VMACHSM and if an HSM event spanned one or more days, those
Jan 20, 2016 time values couldn't be used to calculate durations. This
change creates these four new DateTime variables
FSRTIMRDT='DATETIME*REQUEST*ISSUED'
FSRTIMSDT='DATETIME*REQUEST*STARTED'
FSRTIMADT='DATETIME*ALLOCS*COMPLETED'
FSRTIMEDT='DATETIME*REQUEST*ENDED'
from those four times, using END-SMF, then ALLOC-END and
START-ALLOC deltas to detect when a prior event happened
on the prior day and correct the date part.
And these two new durations are now created:
FSRQUEUETM='FSR*QUEUE*TIME*REQ TO*START'
FSRSERVICTM='FSR*SERVICE*TIME*START*TO END'
- The comparison of TIMEPART(SMFTIME)-FSRTIME, an 8-byte
and a 4-byte stored variable produced non-zero deltas
on the order of E-08, so the ROUND(delta,.01) function
was needed to prevent false positives.
-ASUMHSM was updated to use the new datetime variables.
Thanks to Randy Hewitt, Hewlett Packard, USA.
Change 34.001 If the OPTION CHARCODE is enabled, text (??) in VGETOBS
VGETOBS is incorrectly parsed causing CHARACTER OPERAND ERROR:
Jan 19, 2016 MXGNOTE: VGETOBS LAST UPDATED MAR 17, 2015 CHANGE 33.063
ERROR: CHARACTER OPERAND WAS FOUND IN THE %EVAL FUNCTION
THE CONDITION WAS: %LENGTH(&VGETDSN) = 0
ERROR: THE MACRO VMXGWORL WILL STOP EXECUTING.
Changing the text to ( ?? ) resolves the parse. The SAS
default is NOCHARCODE, and the only MXG code that needs
CHARCODE, member FORMATS, resets to NOCHARCODE, and that
program is only run once to update formats for new MXG.
Using CHARCODE in FORMATS allows one member to create the
MXG formats on both ASCII and EBCDIC platforms, but the
rest of MXG code is only validated with NOCHARCODE.
Thanks to Francois Vancoppenolle, PVGroup, BELGIUM.
LASTCHANGE: Version 34.
=========================member=CHANGE33================================
/* COPYRIGHT (C) 1984-2016 MERRILL CONSULTANTS DALLAS TEXAS USA */
Annual MXG Version 33.33 is dated Jan 18, 2016, thru Change 33.327
First MXG Version 33.33 was dated Jan 11, 2016, thru Change 33.321
MXG Version 33.13 was dated Dec 23, 2015, thru Change 33.311
First MXG Version 33.13 was dated Dec 21, 2015, thru Change 33.309
MXG Version 33.12 was dated Dec 1, 2015, thru Change 33.286
First MXG Version 33.12 was dated Nov 27, 2015, thru Change 33.284
MXG Version 33.11 was dated Nov 2, 2015, thru Change 33.260
MXG Version 33.10 was dated Oct 20, 2015, thru Change 33.250
MXG Version 33.09 was dated Sep 15, 2015, thru Change 33.217
MXG Version 33.08 was dated Aug 20, 2015, thru Change 33.195
First MXG Version 33.08 was dated Aug 17, 2015, thru Change 33.189
MXG Newsletter SIXTY-SIX was dated Aug 17, 2015.
MXG Version 33.07 was dated Jul 22, 2015, thru Change 33.172
First MXG Version 33.07 was dated Jul 17, 2015, thru Change 33.170
MXG Version 33.06 was dated Jun 11, 2015, thru Change 33.141
MXG Version 33.05 was dated May 19, 2015, thru Change 33.128
Second MXG Version 33.05 was dated May 12, 2015, thru Change 33.124
First MXG Version 33.05 was dated May 12, 2015, thru Change 33.123
MXG Version 33.04 was dated Apr 29, 2015, thru Change 33.112
MXG Version 33.03 was dated Mar 31, 2015, thru Change 33.085
Second MXG Version 33.03 was dated Mar 29, 2015, thru Change 33.084
First MXG Version 33.03 was dated Mar 27, 2015, thru Change 33.083
MXG Version 33.02 was dated Feb 27, 2015, thru Change 33.047
First MXG Version 33.01 was dated Feb 20, 2015, thru Change 33.044
ANNUAL: MXG Version 32.32 was dated Jan 6, 2015, thru Change 32.309
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 33.33 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 33.33.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest
and is updated with new notes frequently. All Newsletters are online
at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
All MXG changes are also online at http://www.mxg.com, in "Changes".
========================================================================
I. MXG Version 33.33 re-dated Jan 18, 2016, thru Change 33.327.
Major CHANGES added in MXG 33.33, dated Jan 18, 2016:
TYPE110 33.326 MXG 32.10-First MXG 33.33. Increased CPU in SMF 110s
from 300 to 500 seconds for 22GB SMF 110s, corrected.
TYPEVMXA 33.327 Data set VMBYUSR missing many observations.
VMXGALOC 33.325 Correction for WEEK1 allocation.
TYPEXAM 33.324 zVPS variable CALENTMT changed from numeric, conflict
Major CHANGES added in MXG 33.33, dated Jan 11, 2016:
TYPEXAM 33.320 Support for zVPS z13 SMT mode new variables.
TYPE70EC 33.318 Data Set SORT70EC NOT SORTED, configuration changed.
TYPE42 33.316 New variables compatibly added by z/OS 2.2.
TYPE64 33.316 New variables compatibly added by z/OS 2.2.
TYPE71 33.316 New variables compatibly added by z/OS 2.2.
TYPE74 33.316 New variables compatibly added by z/OS 2.2.
TYPE99 33.308 New variables compatibly added by z/OS 2.2.
SMFSRCH 33.307 Support for multiple text strings in LOOKFOR=.
ASUMCELP 33.306 Variables SMF70GNM, SMF70GMU, SMF70WLA added.
ANALACTM 33.312 Correction for more than one service policy.
Major CHANGES added in MXG 33.13, dated Dec 23, 2015:
UTILBLDP 33.311 Execution stops if BUILDPDB=YES, with &SPINUOW error.
Major CHANGES added in First MXG 33.13, dated Dec 21, 2015:
Critical Change for ITRM USERS (MXG 33.12+):
ITRM 33.301 ITRM users MUST add %LET EPDBOUT= _SDB2SBP;
inserted between %CMPROCES... and %CPSTART....
ERROR: File WORK.SUMSTSBP.DATA does not exist.
Critical Change for z/OS 2.2 MXGTMNT/TAPE MOUNT MONITOR:
ASMTAPEE 33.207 ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.
IBM changes cause ABEND S0E0-28, must reassemble.
New Products Support
TYPEIMS 33.298 Support for IMS 14.1 log records (COMPATIBLE)
TYPE74 33.305 z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC,
(new Storage Class Memory data).
TYPE78 33.305 z/OS 2.2 new variables in TYPE78PA.
TYPEVMXA 33.299 Support for zVM 6.3 MONWRITE z13 SMT MODE.
Errors Corrected:
TYPEDB2 33.303 Multiple DB2 100 Subtype 1 created multiple DB2STATS.
TYPE102 33.294 SMF 102 IFCIDs 81E5-8160,8051x INPUT EXCEEDED DRROR
Enhancements
ANALIDDY 33.290 ANALIDDY tabulates ANALID SMF data by date, used to
investigate SMF dumping problems.
Major CHANGES added in MXG 33.12, dated Dec 1, 2015:
Reason for this new version:
TYPE7072 33.280 PDB.TYPE70 z13 SMT mode ZIPCPUS value may be wrong.
New Products Support:
TYPEDB2 33.279 Support for DB2 Simulated Buffer Pool PDB.DB2STSBP.
MOBWRK02 33.279 Support for DB2 Simulated Buffer Pool dataset.
TYPE102 33.264 Support for APPTUNE 11.2 INCOMPATIBLE change in 8005.
TYPE119 33.262 Support for SMF 119 subtypes 2, 5, 6, 7, 41-44, 97.
Errors corrected:
TYPE102 33.273 DB2 SMF 102 IFCID=109 INVALID DO LOOP CONTROL ERROR.
TYPE1415 33.270 Variable SMF14ALIAS misspelled so it was not kept.
TYPE120 33.267 SMF 120 dataset TYP120JI only output first instance.
TYPEXAM 33.266 MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND.
TYPETPMX 33.265 ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong.
Enhancements:
JCLASMXG 33.275 Assemble/Link Edit all five MXG ASM programs install.
ASMRMFV 33.274 ASMRMFV Updates.
MXGLOG 33.162 MXGLOG write enabled by //MXGLOG or FILENAME MXGLOG,
automatically.
Major CHANGES added in MXG 33.11, dated Nov 2, 2015:
Reason for this new version:
TYPE110 33.257 CICS/TS 5.3 BETA CICSTRAN new field added INCOMPAT
This should be the last REQUIRED MXG update for CICS/TS 5.3.
New Products Support:
TYPEXAM 33.259 Support for zVPS Release 4230 for z13 SMT mode.
Enhancements:
TYPEIMST 33.252 Variable SYSTEM can be added to TYPE56FA with SYSPARM
Major CHANGES added in MXG 33.10, dated Oct 20, 2015:
New Products Support:
TYPE121 33.231 Support for JZOS Java Runtime Performance SMF 121.
TYPEATF 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A2.
TYPE6 33.233 Support for APAR OA46136 adds IPADDR in PSF SMF 6.
TYPEVMXA 33.242 Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode.
TYPERACF 33.238 Support for RACF IRRDBU00 Record Type 1560.
TYPEEDA 33.237 Support for EDA V7706 (INCOMPATIBLE, data inserted).
TYPETPMX 33.232 Support for Thruput Manager VARNAME=$ORIGIO.
TYPEDOS 33.248 Support for zVSE/Power Version 9 Release 2 accounting
Enhancements:
ANALCAPD 33.225 Major revision to analysis of Capping, now by LPAR.
ASMRMFV 33.222 RMF III DVT Character data Filtering saves DASD.
ANAL2642 33.230 Example to select TYPE26 and match with TYPE42.
ANAL1430 33.230 Example to select TYPE14 and match with TYPE30.
VMACUCB 33.245 DEVCLASS=41 decode identifies specific CTC type.
TYPE80A 33.243 RACF Type 80 record "subtypes" (RACFEVNT) for ANALID.
IMAC30IO 33.240 EXCPxxxx and IOTMxxxx can be dropped for nonexistent.
TYPE7072 33.239 New _KTY70DR to drop variables from TYPE70 dataset.
TYPE102 33.236 All DB2 zPARM QWP4xxxx fields are now correct.
TYPE42 33.230 Summed vars S42READS,S42WRITES added to TYPE42DS.
Error Corrections:
TYPE74 33.234 TYPE74HO false duplicates were being removed.
TYPENDM 33.229 NDM PT records INPUT EXCEEDED, INCOMPAT inserts.
TYPE22 33.227 Dataset TYPE22PB RECONFIG PCIE had zero observations.
TYPE74 33.228 SMF 74 St 9 z/OS 2.1 z/13 INPUT STATEMENT EXCEEDED.
TYPE103 33.223 Short SMF 103 Subtype 13 INPUT EXCEEDED error.
TYPE102 33.250 SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED.
Major CORRECTIONS added in MXG 33.09, dated Sep 15, 2015:
ASMTAPEE 33.207 ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.
IBM changes cause ABEND S0E0-28, must reassemble.
TYPE7072 33.217 z13, SMT Mode, error: LPARCPUS=0 in PDB.TYPE70PR.
TYPE110 33.198 CICS/TS 5.3 BETA, MNSEGCL=5, INPUT STATEMENT EXCEEDED
IBM inserted new data. Datasets CICSRDS/RDFI/RDQU.
TYPETMO2 33.210 More TMON/CICS Version 3 and Version 4 corrections.
MONITASK in V3.3 fixed, MONISYST in V3.3 and 4.0.
ASG APAR corrects two obscure fields in 4.0.
TYPE7072 33.216 Support for APAR OA47042 WLM MOBILE Resources in RMF.
TYPECDC 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2
TYPEAXWY 33.199 Support for AXWAY SMF record, INCOMPATIBLE, inserts.
TYPE120 33.213 Support for WASODM Operational Decision Manager 8.7.
TYPEMGCR 33.212 Support for MEGACRYPTION Version 6, INCOMPATIBLE.
TYPE30 33.206 z/OS 2.2 Job Correlation SMF30COR input/kept.
BUILDPDB 33.204 Variable IOTMNODD was never calculated in PDB.JOBS.
TYPEXAM 33.202 Velocity ZVPS 5.4 XAMSYT had zero observations.
TYPE113 33.197 Variable LPBUSY created in ASUM113 like TYPE113.
TYPEDB2 33.205 DB2ACCTP variables QPACPKID/LOCN/ may be truncated.
TYPEBVIR 33.196 TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected.
TYPE70 33.200 TYPE70xx datasets now have VARYed interval data kept.
Major CORRECTIONS added in MXG 33.08, dated Aug 20, 2015:
CRITICAL, REQUIRED CHANGES (that caused redate/refresh of 33.08):
TYPETMO2 33.195 TMON/CICS Version 4 was still wrong in 1st 33.08.
Major enhancements added in FIRST MXG 33.08, dated Aug 18, 2015:
CRITICAL, REQUIRED CHANGES:
TYPE7072 33.186 z13 INCOMPATIBLE ERROR, SMT-MODE, if VARY CP online.
The VARY put the new CP after the IIPs which broke
MXG logic so the new engine was not seen, causing the
CPU metrics to be wrong for all intervals after the
VARY, requiring redesign of the MXG SMT logic.
TYPETMO2 33.188 TMON/CICS Version 4.0, REQUIRED, MXG coding error.
TYPESYNC 33.184 Support for SYNCSORT Release 1.4 (INCOMPAIBLE).
NEW SUPPORT ITEMS:
TYPExxxx 33.189 Support for z/OS 2.2 COMPATIBLE, but many additions.
TYPEMAR 33.183 Support for MAR Hitachi Command Suite Mainframe
VMAC115 33.180 Support for MQ Version 8 subtype 215 record
TYPEBBMQ 33.175 New IHDRBBMQ "Infile Header Exit" for selection.
ASMRMFV 33.182 New filters for RMF III ASI Filtering reading RMFVSAM
CORRECTIONS:
TYPE74 33.185 zEDC TYPE749 zero divide fixed, R749DFMT formatted.
TYPE70PR 33.174 IFL Processor count corrected to number in LPAR.
TYPE7072 33.179 TYPE70EN z13 SMT Mode, blank LPARNAME, SMF70MTTT fix.
TYPE113 33.173 z13 SM1132SP incorrectly forced, should be 5000 MHz.
OTHER ENHANCEMENTS:
TYPE102 33.187 Dataset T102S106 zPARM variables added.
TYPE30 33.185 zEDC variables labels now INFLATE/DEFLATE.
RMFINTRV 33.181 Enhancement to ADD variables to be kept in RMFINTRV.
JCLPDB9 33.178 JCL Example for BUILDPDB, ANALxxxx members revised.
Major enhancements added in MXG 33.07, dated Jul 20, 2015:
TYPE120 33.171 Many SMF 120 ST 9 UNEXPECTED MULTIPLE SEGMENT on log
Major enhancements added in MXG 33.07, dated Jul 17, 2015:
TYPE74 33.155 TYPE74ST now has SCM variables, TYPE74MO is no more.
TYPE78 33.156 Support for APAR OA44525, zHPF Extended Distance II.
TYPE115 33.151 Support for MQ V8.0 MQCHIN, ERROR.VMAC115.OFFQCCT.
TYPE116 33.151 Support for MQ V8.0 MQCHININ, ERROR.VMAC116.LENQWHS.
TYPE119 33.144 Support for Type 119 new subtypes 94 and 95.
TYPECZA 33.166 Support for Correlog z/OS Agent User SMF record.
MXGLOGDO 33.162 "MXGLOG" option to send MXG Messages to MXGLOG.
TYPE22 33.146 New TYPE22PB dataset created for Reconfigured PCIE.
SMFSRCH 33.159 Support for compressed SMF in SMFSRCH LOOKFOR
ANALID 33.159 Support for compressed SMF for DB2 Version/Subtype.
ANALQBAT 33.147 Analysis of Batch Queue Times SMF30HQT/JQT/RQT/SQT.
TYPEXAM 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected.
TYPEBVIR 33.145 BVIR VTS Grid dataset BVIR33 wrong for second plus.
TYPENDM 33.143 INPUT STATEMENT EXCEEDED NDM-CDI PT record.
IMAC6ESS 33.158 Type 6 ESS zero len segment INPUT STATEMENT EXCEEDED.
Major enhancements added in MXG 33.06, dated Jun 11, 2015:
TYPERMFV 33.140 RMF III RCD records INCOMPATIBLY CHANGED for z13.
TYPE7072 33.138 z13 in SMT Mode zIIP variables in TYPE70xx datasets,
especially TYPE70EN, could be missing, or DUPLICATE
RECORD message could be printed. REQUIRED FOR SMT.
The MXG SMT support has come in several iterations as
new sequences of data exposed untested logic but this
appears to finally resolve the one-to-many merge.
If you testing SMT on z13, please email MXG Support
with subject: SMT UPDATES so we can inform you if
there are any further required changes for SMT mode.
Aug 17, 2015: MXG 33.08 is NOW required for SMT mode.
See Change 33.186.
TYPE30 33.132 Support for zEDC metrics in TYPE30 is now correct.
ANAL9914 33.139 z13 Processor Topology Report from SMF TYPE9914 data.
SMFSRCH 33.131 SMFSRCH enhancements, ANALID, LOOKFOR list, AND/OR.
TYPEAA 33.137 Support for Compuware ABEND-AID USER SMF Record.
TYPECIMS 33.136 Support for MainView for IMS 5.2 (a/k/a IMF).
TYPEOSEM 33.133 ZOSEM User SMF - INPUT STATEMENT EXCEEDED error.
TYPETMS5 33.129 Support for TMS new TRTCH values for TS1140.
ASUM113 33.130 Missing values in SMF70xx merged into PDB.ASUM113.
ANALDB2R 33.134 Number reports mis-reported,ANALID added, headings.
Major enhancements added in MXG 33.05, dated May 19, 2015:
Sites with z13 in SMT-mode or sites with zEDC need this refresh:
TYPE7072 33.128 Zero OBS in TYPE70 for non-SMT if SMT SMF read first
TYPE74 33.127 zEDC TYPE749 dataset was finally revised correctly.
Aug 17,2015 added: MXG 33.08 required for SMT mode.
Major enhancements added in MXG 33.05, dated May 12, 2015:
TYPE7072 33.121 z13 SMT-mode TYPE70/TYPE70PR data is WRONG 33.03-04.
ONLY SMT-mode type 70 records were wrong.
TYPETANZ 33.123 Support for Tandem ZMS Style records.
TYPEZCOS 33.116 Support for ZCOST AutoSoftCapping Version V3.0.00
SMFSRCH 33.117 SMFSRCH corrections, TYPE30_D now populated.
TYPEBBMQ 33.115 Mainview for Mq BBMQBUFF variables corrected.
TYPECIMS 33.114 IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN.
TYPE102 33.113 Some T102S106 DB2 zPARM values were misaligned/wrong.
TYPE120 33.120 New IHDR120 header exit created for TYPE120 tailoring
IMACICMX 33.119 The optional IMACICMX for length=384 had missing END.
Major enhancements added in MXG 33.04, dated Apr 29, 2015:
TYPE110 33.112 Support for CICS/TS 5.3 OPEN BETA (INCOMPATIBLE).
Note: IBM Changed CICS 5.3 Default to STGPROT=YES
Note: MXG 33.08-plus is required. Change 33.192.
TYPETMO2 33.099 TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG.
TYPEBBMQ 33.090 Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT)
TYPE42 33.108 Support for APARs OA45944,OA45897 new SMF 42 metrics.
TYPE74 33.087 Support for RMF 74 Subtype 9 zEDC Accelerator.
TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE).
TYPEQACS 33.101 Support for iSeries 7.2 (COMPATIBLE, new LRECLs).
TYPEXAM 33.086 Support for Velocity Software zVPS XAM Version 5.4.
TYPENMON 33.104 Support for NMON CPUnr with three digits.
TYPE110 33.106 CICSEXCE variable EXCMTYPE decodes Exception type.
UTILCVRT 33.105 Alternate table needed for no TRANSCODE PROC CPORT.
ASMRMFV 33.100 Protect invalid ASI table index in UWD, 0C4 ABEND.
TYPE7072 33.096 z13 with SMT PROCVIEW=CORE, SMT-NUM not kept.
TYPENMON 33.092 Some NMON BBBPnnnn variables were mis-assigned.
Major enhancements added in MXG 33.03, dated Mar 29, 2015:
TYPE7072 33.071 FULL z13 SUPPORT. MXG 33.03 IS REQUIRED FOR SMT MODE,
i.e., for PROCVIEW CORE. FOR non-SMT, PROCVIEW CPU,
the many changes were COMPATIBLY made.
Aug 17,2015: See Change 33.186, MXG 33.08 IS NOW REQUIRED FOR SMT.
For SMT PROCVIEW CORE Mode, MXG Change 33.046 in 33.02
updated the TYPE70 dataset, but this Change 33.071 in MXG
33.03 is required to update the new SMT metrics correctly
in the TYPE70PR dataset, to get the CPUID, LCPUADDR, and
CORE_ID from the four segments that don't have the same
number of segments: OFFCPUD and SMF70COS have 20 for the
6 online CPs, 4 offline CPs, and 5 zIIPs with CPU_NUM=2,
while SMF70BDN/LPARCPUX has only 18 segments (with the
CORE_NUM needed to look-up the LCPUADDR), and there are
only 14 Core_ID values.
This was a complex update to a CRITICAL MXG MEMBER, with
500+ lines of code inserted lines into the 27,000 lines.
The SMT Mode data has been validated with RMF records,
with a wide range of LPAR configurations. When in SMT
mode, please examine the new data carefully and contact
support@mxg.com if you have questions.
Note: If you read the changed SMT mode RMF 70s with an
old MXG, RMFINTRV may have NEGATIVE CPUOVHTM values and
the %PCTCPUBY values may be over 100%.
TYPE99 33.053 Support for z13 updates to type 99 subtype 14.
TYPE113 33.052 z13 Support for HIS SMF 113, many new equations.
UTILEXCL 33.049 New reports, trans without dictionary, READTIME.
VMXGINIT 33.062 %LET MXGDEBUG=FULL; shows OPTIONS, enables diags.
TYPEDOL 33.060 DCOLLECT Cluster/Multi-VOL now have Class variables.
TYPE102 33.067 DB2 Trace IFCID=220 misaligned, ILLEGAL ARGUMENT.
TYPE105 33.061 GDPS SMF 105 INPUT STATEMENT EXCEED if no XVMX seg.
ANALDB2R 33.069 SAS 9.3 does not have dictionary for DESTINATIONS.
TYPEDB2 33.068 Variable Q8STCCPU not kept after Change 30.133.
TYPETHAO 33.059 Support for Thales Security Resource Mgr RF1100.
FTPING 33.056 OPTIONS OBS=0 fails read with ftp access method.
ANALHSM 33.050 Graphics part had a NOT SORTED condition.
TYPETPMX 33.070 TOKENID INCLAI, three $LIST_L and $RESTAR added.
Many 33.078 All %MACROs from SASAUTOS are replaced by %SYSFUNC()
Major enhancement added in MXG 33.02, dated Feb 27, 2015:
Many 33.046 Support z/OS on z13 RMF/SMF APARs for z/OS 2.1+
MXG 33.01 CHANGES noted one z13 site had NEGATIVE CPUOVHTM,
but that was ONLY IF z/OS on z13 is in MULTI-THREADING MODE.
MXG was unaware of IBM's restructuring the RMF type 70 SMF
record's calculation of CPU BUSY time for the new MT mode,
but this MAJOR CHANGE restructured TYPE70 processing in MXG
to order by CORE_ID and CPU_NUM rather than CPUID/LCPUADDR.
If you have ANY non-MXG programs that read RMF 70s to get the
CPU BUSY time, they MUST BE REWRITTEN for MT Mode records.
A Technical Newsletter note on Multi_Threading is planned;
this original note then stated an initial opinion of mine:
"although relatively few sites have workloads that will be
able to exploit that architecture, which can increase thruput
but elongate individual tasks elapsed time", but I've changed
my opinion about "relatively few sites": ANY SITE with zIIPs
or IFLs are VERY LIKELY to find SMT to be a benefit.
Major enhancement added in MXG 33.01, dated Feb 23, 2015:
Many 33.023 Support z/OS on z13 RMF/SMF APARs (z/OS: COMPATIBLE)
However: One site's z13 stress test shows TYPE70 CPU time MUCH LESS
than TYPE72 Service Class CPU time (which matches 30s) for
many intervals, but valid data before and after the test,
causing NEGATIVE CPUOVHTM messages on the log and RMFINTRV
observations will have negative CPUOVHTM (uncaptured CPU).
NOTE: THIS ERROR WAS CORRECTED IN MXG 33.02, SEE ABOVE NOTE.
TYPEVMXA 33.016 Support for zVM 6.3 on z13 (INCOMPATIBLE).
TYPEMWLX 33.037 Support for HP MeasureWare for Linux -
VMAC30 33.005 Support for APAR OA45767 adds zEDC statistics.
TYPEBBMQ 33.030 Support for BMC Mainview for MQ 5.2 (REQUIRED)
TYPENTMU 33.028 Support for EDS User SMF Record from NETMENU program.
TYPEXPTR 33.040 Support for SystemWare XPTR 5.2 subtype 140, ex-st-40
SMFSRCH 33.041 SMFSRCH redesigned to read the SMFOUT with UTILBLDP.
ASUM70PR 33.032 New SMF70WTI/WTS/WTU added to ASUM70LP/ASUMCELP
MOBWRKSU 33.039 Summarization of Mobile Work CSV file combines split.
TYPEDB2 33.025 QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB.
RMFINTRV 33.024 ANY work in service class SYSOTHER, new log messages.
ASMRMFV 33.021 ASMRMFV skips RCD if no Reporting Classes defined.
TYPEQACS 33.020 iSeries change in record length can force USER ABEND.
TYPE60 33.038 Type 60 with no VVR INPUT STATEMENT EXCEEDED again.
TYPE80A 33.036 RACF SMF 80 record, TOKxxxxx fields increased length
TYPEIMS 33.034 Variables SYSABEND,USRABEND decoded in IMS56FA.
TYPEVMXA 33.043 zVM VXUSEACT/VXUSEINT NOT SORTED ERROR.
UTILBLDP 33.042 Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes.
All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Versions
The current version nomenclature is SAS 9.4 TS1M3 (9.4M3) printed
as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for
"SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled),
for SAS 9.4 Maintenance Level M3 and m2.
SAS V9.4 M3 Is RECOMMENDED, but MXG executes without error using
SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.
SAS V9.4 M2 Is RECOMMENDED. SAS 9.4 M2 is at LEVEL A SAS Support
SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support
SAS V9.3 SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works.
But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
see CHANGE 29.169, IS REQUIRED:
The %MACRO compiler error is in processing %LET
statements. While only two MXG members failed
repeatedly in MXG QA tests on z/OS, there were random
%LET errors in ASCII QA tests, so ANY use of %LET
statement on ANY platform are vulnerable to this
error, as the %MACRO compiler is SAS portable code,
used on all platforms. So this is NOT just an MXG
error, but impacts ALL SAS programs.
SAS9.3 is LEVEL A support from SAS.
SAS V9.2 Was recommended, prior to 9.3, and was error-free with
MXG 26.03. SAS Hot Fix for SAS Note 37166 is required to
use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2
Decompression Infile Exit, but SAS V9.2 does execute ok.
9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.
SAS V9.1.3 must be at Service Pack 4. Additionally, on z/OS 1.10
only, 9.1.3 requires SAS Hot Fix for SN-35332.
9.1.3 is support level C by SAS Institute, Sep 30, 2013.
SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.
SAS V8.2 IS SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS
with SAS 8.2.
SAS 8.2 is Level C Support from SAS as of Dec 31, 2011.
JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used
***************************************************************
As documented in Change 27.356, for SAS V9.2 or later):
The standard SAS JCL Procedure can be used for MXG with SAS V9.2+
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
or you can continue to use the MXGSAS93 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 33.03 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows Seven and
Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4,
but MXG users execute MXG on MANY (ALL??) SAS platforms, including
AIX, Linux, and other 'nix' variants, on many different hardware
platforms, and since they all work we don't need to list them. If
SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 3.1.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
However, for the z13 processor on z/OS, the new SMT-MODE RMF 70 was
INCOMPATIBLY CHANGED, and MXG 33.09 is REQUIRED (PCTCPUBY WRONG!), to
read the SMT-format RMF records (which are written if you have zIIP
engines AND have have enabled the new PROCVIEW CORE option for
Multi-Threading, even if only one thread is enabled).
The new zEDC compression hardware requires MXG 33.07 to support the
new metrics.
For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes.
Availability dates for the IBM products and MXG version required for
error-free processing of that product's data records:
Product's
Availability MXG Version
Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8
MVS/ESA 4.2 Mar 29, 1991 9.9
MVS/ESA 4.2.2 Aug 15, 1991 9.9
MVS/ESA 4.3 Mar 23, 1993 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30, 1996 14.05
OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02
OS/390 2.4.0 Sep 28, 1997 15.06
OS/390 2.5.0 Feb 24, 1998 15.06
OS/390 2.6.0 Sep 24, 1998 16.04
OS/390 2.7.0 Mar 26, 1999 16.09
OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
z/OS 1.1 on 2064s Mar 30, 2001 19.01
z/OS 1.1 with correct MSU Mar 30, 2001 19.02
z/OS 1.2 Oct 31, 2001 19.04
z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05
z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.4 Tolerate Sep 27, 2002 20.03
z/OS 1.4 Support Sep 27, 2002 20.06
z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02
z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04
z/OS 1.5 Mar 31, 2004 21.21
z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10
z/OS IRD TYPE70PR Mar 11, 2004 *24.10
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10
z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10
z/OS IFA data in RMF 79s Sep 30, 2005 23.10
z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03
z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06
z/OS More than 32 LPARs Jan 30, 2006 *24.24
z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24
z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02
z/OS IRD errors corrected May 15, 2006 24.03
z/OS ASUMCEC errors corrected May 15, 2006 *24.24
z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24
z/OS zIIP Processor Support Jun 22, 2006 *24.24
z/OS Dedicated zIIP Support Mar 8, 2008 *26.01
z/OS Dedicated zAAP Support Mar 8, 2008 26.01
z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24
z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10
z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10
z/OS new z10 variables Mar 5, 2008 26.01
z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05
z/OS 1.11 Sep 2, 2009 27.08
z/OS 1.11 New 30 variables Apr 14, 2010 *28.02
z/OS 1.12 Aug 17, 2010 *28.05
z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03
z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06
z/OS 1.13 Sep 30, 2011 29.03
z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08
z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01
z/OS 2.1 - Most Records support Jul 23, 2013 30.05
z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07
z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03
z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03
z/OS 2.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
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
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 OPEN BETA Sep 31, 2015 33.08
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.??
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
DFSMS/MVS 1.1 Mar 13, 1993 11.11
DFSMS/MVS 1.2 Jun 24, 1994 12.02
DFSMS/MVS 1.3 Dec 29, 1995 13.09
DFSMS/MVS 1.4 Sep 28, 1997 15.04
DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04
DFSMS/MVS 1.5 ??? ??, 1999 16.04
DFSORT SMF V1R5 Mar 1, 2006 24.02
MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02
MQ Series 1.2.0 May 26, 1998 16.02
MQ Series 2.1.0 Oct 2, 1999 17.07
MQ Series 5.2 Dec 16, 2000 18.10
MQ Series 5.3 Dec 16, 2002 21.05
MQ Series 6.0 Feb 14, 2006 23.23
Websphere MQ Series 7.0 ??? ??, 2009 *28.06
Websphere MQ Series 7.1 MAR 12, 2011 29.03
Websphere MQ Series 8.0 Jun 24, 2011 29.05
NETVIEW 3.1 type 37 ??? ??, 1996 14.03
NPM 2.0 Dec 17, 1993 12.03
NPM 2.2 Aug 29, 1994 12.05
NPM 2.3 ??? ??, 1996 15.08
NPM 2.4 Nov 18, 1998 17.01
NPM 2.5 Feb ??, 2000 18.02
NPM 2.6 Nov ??, 2001 19.06
RMDS 2.1, 2.2 Dec 12, 1995 12.12
RMDS 2.3 Jan 31, 2002 19.11
TCP/IP 3.1 Jun 12, 1995 12.12
TCP/IP 3.4 Sep 22, 1998 16.04
WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04
WebSphere 6.0 Feb 18, 2006 23.23
WebSphere 7.0 Oct 7, 2010 28.06
WebSphere 8.0 Jul 17, 2011 29.05
DOS/VSE POWER V6.3.0 Dec 19, 1998 16.08
VM/ESA 2.0 Dec 23, 1992 10.04
VM/ESA 2.1 Jun 27, 1993 12.02
VM/ESA 2.2 Nov 22, 1994 12.06
VM/ESA 2.3 Jun 1, 1998 16.08
VM/ESA 2.4 Mar 1, 2001 19.03
z/VM 3.1 Mar 1, 2001 19.03
z/VM 3.1 DATABYTE=0 May 2, 2002 20.02
z/VM 4.2 ?? May 2, 2002 20.02
z/VM 4.4 Jan 22, 2005 22.22
z/VM 5.1 Jan 22, 2005 22.22
z/VM 5.2 Jan 22, 2006 24.01
z/VM 5.3 TOLERATE Jun 7, 2007 25.05
z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08
z/VM 5.4 (COMPATIBLE) Sep 12, 2008 *27.01
z/VM 6.1 (NO CHANGES) Jul 7, 2008 27.01
z/VM 6.2 Dec 2, 2011 29.04
z/VM 6.3 INCOMPATIBLE Jul 23, 2013 31.05
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.13
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
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
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
ACF2 6.2 16.04
ASTEX 2.1 14.04
NETSPY 4.7 14.03
NETSPY 5.0 14.03
NETSPY 5.2 16.05
NETSPY 5.3 18.03
NETSPY 6.0 20.10 20.305
NETSPY 7.0 20.10 20.305
SAR/VIEW R11 23.07 23.196
BMC, was Boole & Babbage
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 31.08
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2 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 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 33.33.
1. Incompatibilities introduced in MXG 33.33:
a- Changes in MXG architecture made between 33.33 and prior versions
that can introduce known incompatibilities.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
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.
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 33.33 after MXG 32.32:
Dataset/
Member Change Description
ANAL1430 33.230 Example to select TYPE14 and match with TYPE30.
ANAL2642 33.230 Example to select TYPE26 and match with TYPE42.
ANAL9914 33.139 z13 Processor Topology Report from SMF TYPE9914 data.
ANALACTM 33.312 Correction for more than one service policy.
ANALCAPD 33.225 Major revision to analysis of Capping, now by LPAR.
ANALDB2R 33.069 SAS 9.3 does not have dictionary for DESTINATIONS.
ANALDB2R 33.134 Number reports mis-reported,ANALID added, headings.
ANALHSM 33.050 Graphics part had a NOT SORTED condition.
ANALID 33.159 Support for compressed SMF for DB2 Version/Subtype.
ANALIDDY 33.290 ANALIDDY tabulates ANALID SMF data by date.
ANALQBAT 33.147 Analysis of Batch Queue Times SMF30HQT/JQT/RQT/SQT.
ASMRMFV 33.021 ASMRMFV skips RCD if no Reporting Classes defined.
ASMRMFV 33.100 Protect invalid ASI table index in UWD, 0C4 ABEND.
ASMRMFV 33.182 New filters for RMF III ASI Filtering reading RMFVSAM
ASMRMFV 33.222 RMF III DVT Character data Filtering saves DASD.
ASMRMFV 33.274 ASMRMFV Updates.
ASMTAPEE 33.207 ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2.
ASUM113 33.130 Missing values in SMF70xx merged into PDB.ASUM113.
ASUM70PR 33.032 New SMF70WTI/WTS/WTU added to ASUM70LP/ASUMCELP
ASUMCELP 33.306 Variables SMF70GNM, SMF70GMU, SMF70WLA added.
BLDSMPDB 33.031 Wrong Start Week date with FORCEDAY and low case.
BUILDPDB 33.204 Variable IOTMNODD was never calculated in PDB.JOBS.
FTPING 33.056 OPTIONS OBS=0 fails read with ftp access method.
IMAC30IO 33.240 EXCPxxxx and IOTMxxxx can be dropped for nonexistent.
IMAC6ESS 33.158 Type 6 ESS zero len segment INPUT STATEMENT EXCEEDED.
IMACICMX 33.119 The optional IMACICMX for length=384 had missing END.
ITRM 33.301 ITRM users MUST use %LET EPDBOUT= _SDB2SBP.
JCLASMXG 33.275 Assemble/Link Edit all five MXG ASM programs install.
JCLPDB9 33.178 JCL Example for BUILDPDB, ANALxxxx members revised.
MANY 33.046 SUPPORT for z13 processor in MULTITHREADING MODE.
MOBWRK02 33.279 Support for DB2 Simulated Buffer Pool dataset.
MOBWRKSU 33.039 Summarization of Mobile Work CSV file combines split.
RMFINTRV 33.024 ANY work in service class SYSOTHER, new log messages.
RMFINTRV 33.181 Enhancement to ADD variables to be kept in RMFINTRV.
SMFSRCH 33.041 SMFSRCH redesigned to read the SMFOUT with UTILBLDP.
SMFSRCH 33.117 SMFSRCH corrections, TYPE30_D now populated.
SMFSRCH 33.131 SMFSRCH enhancements, ANALID, LOOKFOR list, AND/OR.
SMFSRCH 33.159 Support for compressed SMF in SMFSRCH LOOKFOR
SMFSRCH 33.307 Support for multiple text strings in LOOKFOR=.
TYPE102 33.067 DB2 Trace IFCID=220 misaligned, ILLEGAL ARGUMENT.
TYPE102 33.113 Some T102S106 DB2 zPARM values were misaligned/wrong.
TYPE102 33.126 BMC APPTUNE 102 INPUT EXCEEDED if DATA SHARING.
TYPE102 33.187 Dataset T102S106 zPARM variables added.
TYPE102 33.236 All DB2 zPARM QWP4xxxx fields are now correct.
TYPE102 33.250 SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED.
TYPE102 33.264 Support for APPTUNE 11.2 INCOMPATIBLE change in 8005.
TYPE102 33.273 DB2 SMF 102 IFCID=109 INVALID DO LOOP CONTROL ERROR.
TYPE102 33.294 SMF 102 IFCIDs 81E5-8160,8051x INPUT EXCEEDED DRROR
TYPE103 33.223 Short SMF 103 Subtype 13 INPUT EXCEEDED error.
TYPE105 33.061 GDPS SMF 105 INPUT STATEMENT EXCEED if no XVMX seg.
TYPE110 33.106 CICSEXCE variable EXCMTYPE decodes Exception type.
TYPE110 33.198 CICS/TS 5.3 BETA, MNSEGCL=5, INPUT STATEMENT EXCEEDED
TYPE110 33.257 CICS/TS 5.3 CICSTRAN (final) new field added INCOMPAT
TYPE110 33.326 MXG 32.10-First MXG 33.33. Increased CPU in SMF 110s
TYPE113 33.052 z13 Support for HIS SMF 113, many new equations.
TYPE113 33.173 z13 SM1132SP incorrectly forced, should be 5000 MHz.
TYPE113 33.197 Variable LPBUSY created in ASUM113 like TYPE113.
TYPE115 33.151 Support for MQ V8.0 MQCHIN, ERROR.VMAC115.OFFQCCT.
TYPE116 33.151 Support for MQ V8.0 MQCHININ, ERROR.VMAC116.LENQWHS.
TYPE119 33.144 Support for Type 119 new subtypes 94 and 95.
TYPE119 33.262 Support for SMF 119 subtypes 2, 5, 6, 7, 41-44, 97.
TYPE120 33.120 New IHDR120 header exit created for TYPE120 tailoring
TYPE120 33.213 Support for WASODM Operational Decision Manager 8.7.
TYPE120 33.267 SMF 120 dataset TYP120JI only output first instance.
TYPE121 33.231 Support for JZOS Java Runtime Performance SMF 121.
TYPE1415 33.270 Variable SMF14ALIAS misspelled so it was not kept.
TYPE22 33.146 TYPE22PB dataset created for Reconfigured PCIE.
TYPE22 33.227 Dataset TYPE22PB RECONFIG PCIE had zero observations.
TYPE30 33.132 New zEDC metrics in TYPE30 are now correct.
TYPE30 33.185 zEDC variables labels now INFLATE/DEFLATE.
TYPE30 33.206 z/OS 2.2 Job Correlation SMF30COR input/kept.
TYPE42 33.108 Support for APARs OA45944,OA45897 new SMF 42 metrics.
TYPE42 33.230 Summed vars S42READS,S42WRITES added to TYPE42DS.
TYPE42 33.316 New variables compatibly added by z/OS 2.2.
TYPE6 33.233 Support for APAR OA46136 adds IPADDR in PSF SMF 6.
TYPE60 33.038 Type 60 with no VVR INPUT STATEMENT EXCEEDED again.
TYPE64 33.316 New variables compatibly added by z/OS 2.2.
TYPE70 33.200 TYPE70xx datasets now have VARYed interval data kept.
TYPE7072 33.071 z13 SUPPORT. MXG 33.03 REQUIRED ONLY FOR SMT MODE
TYPE7072 33.096 z13 with SMT PROCVIEW=CORE, SMT-NUM not kept.
TYPE7072 33.121 z13 SMT-mode TYPE70/TYPE70PR data is WRONG 33.03-04.
TYPE7072 33.125 SMF70CAN/CTN restored, CPUWAIT-LPARBUSY for zIIPs.
TYPE7072 33.128 Zero OBS in TYPE70 for non-SMT if SMT SMF read first
TYPE7072 33.138 z13 in SMT Mode, TYPE70EN had missing values for ZIP.
TYPE7072 33.179 TYPE70EN z13 SMT Mode, blank LPARNAME, SMF70MTTT fix.
TYPE7072 33.186 z13 INCOMPATIBLE ERROR, SMT-MODE, when VARY CP online
TYPE7072 33.217 z13 in SMT MODE ONLY: LPARCPUS=0 in PDB.TYPE70PR
TYPE7072 33.239 New _KTY70DR to drop variables from TYPE70 dataset.
TYPE7072 33.280 PDB.TYPE70 z13 SMT mode ZIPCPUS value may be wrong.
TYPE7072 33.318 Data Set SORT70EC NOT SORTED corrected with sort.
TYPE70EC 33.318 Data Set SORT70EC NOT SORTED, configuration changed.
TYPE70PR 33.174 IFL Processor count corrected to number in LPAR.
TYPE71 33.316 New variables compatibly added by z/OS 2.2.
TYPE74 33.087 Support for RMF 74 Subtype 9 zEDC Accelerator.
TYPE74 33.127 zEDC TYPE749 dataset was finally revised correctly.
TYPE74 33.155 TYPE74ST now has SCM variables, TYPE74MO is no more.
TYPE74 33.185 zEDC TYPE749 zero divide fixed, R749DFMT formatted.
TYPE74 33.228 SMF 74 St 9 z/OS 2.1 z/13 INPUT STATEMENT EXCEEDED.
TYPE74 33.234 TYPE74HO false duplicates were being removed.
TYPE74 33.305 z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC.
TYPE74 33.316 New variables compatibly added by z/OS 2.2.
TYPE78 33.156 Support for APAR OA44525, z HPF Extended Distance II.
TYPE78 33.305 z/OS 2.2 new variables in TYPE78PA.
TYPE80A 33.036 RACF SMF 80 record, TOKxxxxx fields increased length
TYPE80A 33.243 RACF Type 80 record "subtypes" (RACFEVNT) for ANALID.
TYPE99 33.053 Support for z13 updates to type 99 subtype 14.
TYPE99 33.308 New variables compatibly added by z/OS 2.2.
TYPEAA 33.137 Support for Compuware ABEND-AID USER SMF Record.
TYPEATF 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A2.
TYPEAXWY 33.199 Support for AXWAY SMF record, INCOMPATIBLE, inserts.
TYPEBBMQ 33.030 Support for BMC Mainview for MQ 5.2 (REQUIRED)
TYPEBBMQ 33.090 Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT)
TYPEBBMQ 33.115 Mainview for Mq BBMQBUFF variables corrected.
TYPEBBMQ 33.175 New IHDRBBMQ "Infile Header Exit" for selection.
TYPEBVIR 33.145 BVIR VTS Grid dataset BVIR33 wrong for second plus.
TYPEBVIR 33.196 TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected.
TYPECDC 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2
TYPECIMS 33.114 IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN.
TYPECIMS 33.136 Support for MainView for IMS 5.2 (a/k/a IMF).
TYPECZA 33.166 Support for Correlog z/OS Agent User SMF record.
TYPEDB2 33.025 QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB.
TYPEDB2 33.068 Variable Q8STCCPU not kept after Change 30.133.
TYPEDB2 33.142 Variables QWACATWT and QWACPQCT corrected.
TYPEDB2 33.205 DB2ACCTP variables QPACPKID/LOCN/ may be truncated.
TYPEDB2 33.279 Support for DB2 Simulated Buffer Pool PDB.DB2STSBP.
TYPEDB2 33.303 Multiple DB2 100 Subtype 1 created multiple DB2STATS.
TYPEDOL 33.060 DCOLLECT Cluster/Multi-VOL now have Class variables.
TYPEDOS 33.248 Support for zVSE/Power Version 9 Release 2 accounting
TYPEEDA 33.237 Support for EDA V7706 (INCOMPATIBLE, data inserted).
TYPEID 33.045 ANALID report printed '110.001' vice '110.1.1'.
TYPEIMS 33.034 Variables SYSABEND,USRABEND decoded in IMS56FA.
TYPEIMS 33.298 Support for IMS 14.1 log records (COMPATIBLE)
TYPEIMST 33.252 Variable SYSTEM can be added to TYPE56FA with SYSPARM
TYPEMAR 33.183 Support for MAR Hitachi Command Suite Mainframe
TYPEMGCR 33.212 Support for MEGACRYPTION Version 6, INCOMPATIBLE.
TYPEMWLX 33.037 Support for HP MeasureWare for Linux -
TYPENDM 33.143 INPUT STATEMENT EXCEEDED NDM-CDI PT record.
TYPENDM 33.229 NDM PT records INPUT EXCEEDED, INCOMPAT inserts.
TYPENMON 33.092 Some NMON BBBPnnnn variables were mis-assigned.
TYPENMON 33.104 Support for NMON CPUnr with three digits.
TYPENTMU 33.028 Support for EDS User SMF Record from NETMENU program.
TYPEOSEM 33.133 ZOSEM User SMF - INPUT STATEMENT EXCEEDED error.
TYPEQACS 33.020 iSeries change in record length can force USER ABEND.
TYPEQACS 33.101 Support for iSeries 7.2 (COMPATIBLE, new LRECLs).
TYPERACF 33.238 Support for RACF IRRDBU00 Record Type 1560.
TYPERMFV 33.140 RMF III RCD records INCOMPATIBLY CHANGED for z13.
TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE).
TYPESYNC 33.184 Support for SYNCSORT Release 1.4 (INCOMPAIBLE).
TYPETANZ 33.123 Support for Tandem ZMS Style records.
TYPETHAO 33.059 Support for Thales Security Resource Mgr RF1100.
TYPETMO2 33.099 TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG.
TYPETMO2 33.188 TMON/CICS Version 4.0, REQUIRED, MXG coding error.
TYPETMO2 33.210 More TMON/CICS Version 3 and Version 4 corrections.
TYPETMS5 33.129 Support for TMS new TRTCH values for TS1140.
TYPETPMX 33.070 TOKENID INCLAI, three $LIST_L and $RESTAR added.
TYPETPMX 33.232 Support for Thruput Manager VARNAME=$ORIGIO.
TYPETPMX 33.265 ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong.
TYPEVMXA 33.043 zVM VXUSEACT/VXUSEINT NOT SORTED ERROR.
TYPEVMXA 33.242 Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode.
TYPEVMXA 33.299 Support for zVM 6.3 MONWRITE z13 SMT MODE.
TYPEVMXA 33.327 Data set VMBYUSR missing many observations.
TYPEXAM 33.086 Support for Velocity Software zVPS XAM Version 5.4.
TYPEXAM 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected.
TYPEXAM 33.202 Velocity ZVPS 5.4 XAMSYT had zero observations.
TYPEXAM 33.259 Support for zVPS Release 4230 for z13 SMT mode.
TYPEXAM 33.266 MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND.
TYPEXAM 33.320 Support for zVPS z13 SMT mode new variables.
TYPEXAM 33.324 zVPS variable CALENTMT changed from numeric, conflict
TYPEXPTR 33.040 Support for SystemWare XPTR 5.2 subtype 140, ex-st-40
TYPEZCOS 33.116 Support for ZCOST AutoSoftCapping Version V3.0.00.
UTILBLDP 33.042 Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found
UTILBLDP 33.159 BUILDPDB=NO incorrect for type 102 2 byte subtypes.
UTILCVRT 33.105 Alternate table needed for no TRANSCODE PROC CPORT.
UTILEXCL 33.049 New reports, trans without dictionary, READTIME.
UTILEXCL 33.255 ARRAY EXCEEDED when more than 999 connectors.
VGETDDS 33.208 z/OS Only. Multiple tape mounts with DDNAMES=PDB:.
VMAC115 33.180 Support for MQ Version 8 subtype 215 record
VMAC30 33.005 Support for APAR OA45767 adds zEDC statistics.
VMACUCB 33.245 DEVCLASS=41 decode identities specific CTC type.
VMXGALOC 33.325 Correction for WEEK1 allocation.
VMXGINIT 33.062 %LET MXGDEBUG=FULL; shows OPTIONS, enables diags.
VMXGINIT 33.162 "MXGLOG" option to send MXG Messages to MXGLOG.
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at http://www.mxg.com
Inverse chronological list of all Changes:
NEXTCHANGE
====== Changes thru 33.327 were in MXG 33.33 dated Jan 18, 2016=========
Change 33.327 Dataset VMBYUSR was missing many observations because the
VMACVMXA timestamp in MRHDRTOD in VXUSEACT did not exactly match
Jan 15, 2016 the MRHDRTOD in VXUSEINT which are key MERGE variables.
Circumvention was to merge with the FLOOR(MRHDRTOD).
Thanks to Joseph J. Faska, DTCC, USA.
Change 33.326 -MXG 32.10-MXG 33.33. Increase in CPU time for SMF 110
VMAC110 record processing, 300 to 500 seconds, 22 GB, due to
Jan 15, 2016 multiple executions of RESOLVE function where only one
was needed, to populate character variable CICXLTR, which
is only used to enhance error messages if EXCLUDED fields
are found.
-Too many warning messages were printed if Compressed CICS
data was read on z/OS without the CICSIFUE INFILE exit,
and too many "ok on ASCII" messages were printed.
Thanks to Perry Lim, Union Bank, USA.
Change 33.325 -Change 32.220 added new BASECICS and BASEDB2 parameters
BLDSMPDB that let you send DB2 and/or CICS datasets to a different
VMXGALOC drive, but did not tell you that if you did not use them,
UTILBLDP those datasets were written to BASEDIR. Default is now
Jan 17, 2016 a NULL string so that behavior is unchanged and the log
Jan 18, 2016 now notes where CICSTRAN and DB2ACCT are allocated.
-Change 32.262 incorrectly set the WEEK WEEK1 libnames to
be the current week when RUNWTD was NO and when RUNWTD
was YES the WTD LIBNAME was not allocated. Fortunately,
the only exposure is that if a user wanted to run a
report with WEEK1, it would have been empty since the
week had not been run to populate it.
-UTILBLDP failed to include ASUMDBSS because an AND in the
macro was misspelled as AMD and the compiler does not see
it as a syntax error.
-BLDSMPDB debugging statements left in code.
Thanks to Richard Krueger, Sentry, USA.
Change 33.324 zVPS variable CALENTMT was changed from numeric to char
VMACXAM causing a conflict if OLD and NEW datasets were combined.
Jan 13, 2016 CALENTMT is restored to CHAR, new variable CALENTMTN has
the actual numeric CPU ENTITLEMENT value.
Thanks to David A. Sadler, OPTUM, USA.
Change 33.323 New fields added to Thruput Manger are supported:
VMACTPMX CONTR ='CONTR'
Jan 12, 2016 JCL_SJB ='JCL_SJB'
JCL_SJC ='JCL_SJC'
JCL_SJG ='JCL_SJG'
JAL_T ='JAL_T'
There is a defective entry with ' ST_L' that should be
'LIST_L' that prints an error message that it was skipped
while we investigate with the vendor.
Change 33.322 The new JOB Correlation Token SMF30COR and SMF26JCR are
VMAC26J2 populated with 64 bytes of '00'x for OMVS and most STCs,
VMAC30 which then print as 64 unprintable characters. The '00'X
Jan 12, 2016 are translated to blanks. But it is unclear why this new
token is created; the READTIME JOB JESNR uniquely match
and only require 24 bytes, and are in many more SMF
records than just these two.
====== Changes thru 33.321 were in MXG 33.33 dated Jan 11, 2016=========
Change 33.321 -Change 33.297 failed if OPTIONS USER=PDB is used, because
VMAC7072 the PROC DATASETS (to change a label) coded a LIB=WORK
Jan 9, 2016 which failed when USER=PDB. The LIB=&MXGWORK argument
Aug 31, 2017 now finds the dataset (replacing a WORK.TEMP70EN fix.)
-BUT: IN GENERAL MXG DOES NOT SUPPORT OPTIONS USER=PDB,
"out of the box": both BUILDPDB and UTILBLDP can fail
or can NOT fail but produce missing values when USER=PDB
is used, and it typically requires additional tailoring
for a specific purpose, especially when accumulated data
requires DIF(), and may require a second execution of
%VMXGINIT. Contact support@mxg.com if you have a need.
-Aug 2017: Note that using WORK=PDB in CONFIG has the same
exposure and thus that is also not supported.
Thanks to Scott Wiig, USBank, USA.
Change 33.320 Support for zVPS z13 SMT Mode adds these variables:
VMACXAM -Dataset XAMCPUTO:
Jan 7, 2016 CALENTMT='ENTITLEMENT'
CORID ='CORE*ID'
PFXPOLAR='POLARIZATION'
RCCTOPDI='DSVBK*INDEX'
TID ='THREAD*ID'
-Datasets XAMCPUBY, XAMIFLBY, XAMIFLTO, XAMCPUTO:
AVGTDBYCORE='AVG*TD*BY CORE'
AVGTDBYTYPE='AVG*TD*BY TYPE'
BUSYTIMEBYCORE='BUSY*TIME*BY CORE'
BUSYTIMEBYTYPE='BUSY*TIME*BY TYPE'
CAPBYTYPE='CAP*BY TYPE'
INTERVALTIMEBYCORE='INTERVAL*TIME*BY CORE'
INTERVALTIMEBYTYPE='INTERVAL*TIME*BY TYPE'
MAXCAPBYTYPE='MAX*CAP*BY TYPE'
MTUTILBYCORE='MT*UTIL*BY CORE'
MTUTILBYTYPE='MT*UTIL*BY TYPE'
PF2CADCT ='COUNT CAD*FOR*SPINLOCK*NODLAY'
PF2TSCAD ='COUNT CAD*DURING*TSGET*REQSTS'
PF2TSCNT ='COUNT*TSGET*REQUESTS'
PF2TSGTM ='ELAPSED*CONSUMED*BY TSGET'
PFXPRKWT ='PARKED*WAIT TIME*TOT UNIT'
PRODBYCORE='PROD*BY CORE'
PRODBYTYPE='PROD*BY TYPE'
SAMPLEDCORESBYTYPE='SAMPLED*CORES*BY TYPE'
SAMPLES='SAMPLES'
Change 33.319 The OPTION NONOTES statement added for the MXGLOG option
VMXGINIT must be reset to NOTES prior to the %MACRO statement. In
Jan 8, 2016 some cases the NONOTES remained incorrectly in effect,
Jan 22, 2016 which could suppress the INFILE SMF information and the
"dataset has nnn obs" notes on the SAS log. The Exposure
was limited to 33.07-33.13, and only with a tailored MXG
execution with a VIEW driven by a PROC SORT.
Jan 23: The OPTION NOTES was mis-located, suppressing the
printing of NOTE: Fileref=SOURCLIB and the DSNAMEs.
Thanks to Scott Wiig, US Bank, USA.
Change 33.318 Data Set SORT70EC NOT SORTED was corrected with an extra
VMAC7072 PROC SORT. It appears a change in the configuration was
Jan 5, 2016 made during the interval that caused the not sorted data.
Thanks to Paul Volpi, UHC, USA.
Change 33.317 Documentation of APARs corrections; NO CHANGES WERE MADE.
VMAC1415 -TYPE1415 APAR OA47899 corrects SMF 14/15 written at EOV
VMAC92 that did not contain the Type 1 Compressed Format data
VMAC74 set section.
VMAC80A -TYPE92 APAR OA49128 corrects invalid value in SMF92CTO.
VMAC116 -TYPE74 APAR OA48860 corrects SMF74DTS,SMF74DCT that are
Jan 3, 2016 not set correctly for a device after HYPERSWAP.
-TYPE80A APAR PI52900 for CICS/TS 5.2, adds CICS NETNAME
to SMF 80 record when DFHSN1102 SIGNON FAILS.
-TYPE116 APAR PI53551 MQ z/OS V8 Class 3 data may be
incorrect for CICS and CHIN Thread Control Blocks.
-Users of IBM CICS PA V5.1/5.2 NEED APAR PI43779 to
correct report files, especially LIST, that have file
blocking of ONE, wasting DISK space and CPU time.
Change 33.316 -The many new variables added in z/OS 2.2 in Change 33.189
VMAC42 are now kept.
VMAC64 -TYPE64 new variables
VMAC71 SMF64SSR='SECONDARY*SPACE*REDUCTION?'
VMAC74 SMF64FCC='BEGINNING*CCHH'
Dec 30, 2015 SMF64TCC='BENDING*CCHH'
SMF64VSN='VOLUME*SERIAL*NUMBER'
SMF64CUU='DEVICE*NUMBER'
SMF64IND='SPINDLE*IDENTIFICATION'
SMF64UTY='*UNIT*TYPE'
-TYPE71 new variables
SMF714KA='AVB*1MB FIXED*USED*4K REQ'
SMF714KM='MIN*1MB FIXED*USED*4K REQ'
SMF714KX='MAX*1MB FIXED*USED*4K REQ'
SMF71C2A='AVG*HIGH VIRTUAL*COMMON*1MB FIXED'
SMF71C2M='MIN*HIGH VIRTUAL*COMMON*1MB FIXED'
SMF71C2X='MAX*HIGH VIRTUAL*COMMON*1MB FIXED'
SMF71C3A='*AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'
SMF71C3M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'
SMF71C3X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'
SMF71CPA='AVB*HI VIRT*COMMON*INUSE'
SMF71CPM='*MIN*HI VIRT*COMMON*INUSE'
SMF71CPX='*MAX*HI VIRT*COMMON*INUSE'
SMF71PLA='AVB*1MB PGBL*BACKED*1MB PGBL'
SMF71PLM='MIN*1MB PGBL*BACKED*1MB PGBL'
SMF71PLX='MAX*1MB PGBL*BACKED*1MB PGBL'
SMF71S2A='AVG*OBJECTS*SHARED MEM*BACK 1MB'
SMF71S2M='MIN*OBJECTS*SHARED MEM*BACK 1MB'
SMF71S2X='MAX*OBJECTS*SHARED MEM*BACK 1MB'
SMF71S3A='AVG*FRAMES*SHARED HIGH*4K*ON SCM'
SMF71S3M='MIN*FRAMES*SHARED HIGH*4K*ON SCM'
SMF71S3X='MAX*FRAMES*SHARED HIGH*4K*ON SCM'
SMF71S4A='AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'
SMF71S4M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'
SMF71S4X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'
-TYPE74 new variable
R748RAI ='RANK*ADAPTER*PAIR*ID'
Change 33.315 z/OS 2.2 JOB='*MASTER*' JCTJOBID='MSGR' SUBSYS='SMS' was
VGETJESN not expected, caused WARNING TYPETASK NOT DECODED, now
Dec 27, 2015 is protected, with TYPETASK='STC' now set.
Change 33.314 Unused Change Number.
Change 33.313 Documentation. Type 30 EXCP/IOTM NODD/TODD/TOTL variables
TYPE30 in the "raw" TYPE30_4/TYPE30_5/TYPE30_V datasets created
Dec 24, 2015 directly from SMF, are wrong or misleading for jobs with
MULTIDD='Y' continuation records (they contain only EXCP
and IOTM fields). The variables ARE VALID in the datasets
PDB.JOBS/PDB.STEPS/PDB.SMFINTRV, built by BUILDPDB or the
ONLYINTV program, where MXG logic combines the MULTIDDs
and then correctly populates those variables.
For MULTIDD='Y' jobs, the first record can be a FLUSH
that contains NO DD segments, so NUMDD=0 and the TODD
variables are missing values. The TOTL in the MULTIDD
records is missing, since that field is the total for
the step, and that is only in the first SMF 30 record.
And since NODD=TOTL-TODD, the NODD is also missing.
And since they can be individually wrong, the sum of
these variables in those "raw" TYPE30xx datasets is
unusable.
Change 33.313 Cosmetic. Comments enhanced.
BLDSMPDB
Dec 23, 2015
Change 33.312 If you had more than a single service policy in your data
ANALACTM the report of the WLM service definition was not sorted
Dec 23, 2015 by the policy name resulting in reports printed by the
importance level instead of the service policy.
====== Changes thru 33.311 were in MXG 33.13 dated Dec 23, 2015=========
Change 33.311 -UTILBLDP with IMACKEEP= fails execution with syntax error
UTILBLDP due to invalid comment termination in the generated code
Dec 23, 2015 that referenced &SPINUOW macro variable.
Thanks to Jim Horne, Lowe's, USA.
Change 33.310 MXG's ANALZPCR is no longer usable, nor needed, since IBM
ANALZPCR zPCR will now read a "printed" IBM RMF CPU report to
Dec 21, 2015 create the zPCR input in External File Format V2.0 that
is required for zPCR V8.7.
====== Changes thru 33.309 were in First MXG 33.13 dated Dec 21, 2015===
Change 33.309 Variable QCSTDNRT, previously reserved, is now input and
VMAC116 formatted as a time, with NS*RESOLUTION*TIME' in
Dec 21, 2015 dataset MQCHININ.
Thanks to Robert Miles Standish, UBS, USA.
Change 33.308 Support for z/OS 2.2 new variables SMF 99 ST 14 added
VMAC99 S99E_AN_CI ='CPU/CORE*CONTAINER*INFO*/
Dec 21, 2015 S99E_AN_CI_FLAGS='CI_FLAGS'
Dec 22, 2015 S99E_AN_CI_NL ='CPU/CORE*TOPOLOGY*INFO'
S99E_AN_CI_NL1 ='CONTAINER*ID OF*NESTING*LEVEL 1'
S99E_AN_CI_NL2 ='CONTAINER*ID OF*NESTING*LEVEL 2'
S99E_AN_CI_NL3 ='CONTAINER*ID OF*NESTING*LEVEL 3'
S99E_AN_CI_NL4 ='CONTAINER*ID OF*NESTING*LEVEL 4'
S99E_AN_CI_NL5 ='CONTAINER*ID OF*NESTING*LEVEL 5'
S99E_AN_CI_NLINUSE='HIGHEST*NESTING*LEVELUSED'
S99E_AN_INFO ='AFFINITY*NODE*INFO'
S99E_AN_TOPO ='CPU/CORE*TOPOLOGY*INFORMATION'
S99E_CP_BOOKID ='BOOK*ID'
S99E_CP_CHIPID ='CHIP*ID'
to dataset TYPE99EN, and these variables to TY99EP:
S99E_CP_BOOKID ='BOOK*ID'
S99E_CP_CHIPID ='CHIP*ID'
-Each subtype 14 dataset now has all of the header
variables kept.
Thanks to Erling Andersen, SMT, DENMARK.
Change 33.307 -SMFSRCH was supposed to support multiple text strings in
SMFSRCH LOOKFOR=, with ANDOR=, but it only supported one string;
VMXGSRCH multiple strings caused nothing to be found.
Dec 21, 2015 Now, multiple LOOKFOR= strings are supported, but only
Dec 29, 2015 with "OR" logic, i.e., any LOOKFOR= string will be found.
It's impractical to support multiple ANDed stings with
LOOKFOR=, but the SELECTION= alternative to LOOKFOR=
provides complete control including ANDs of strings.
-VMXGSRCH messages when a VALUE= was found now print the
VALUE= that was searched, or when a VARS= is used, then
all of the matching variables names are listed, instead
of a blank line.
Change 33.306 The Group Capacity Variables SMF70GNM (Group Name) and
VMXG70PR SMF70GMU (MAXIMUM LICENSE UNITS) are kept in the Per-LPAR
Dec 20, 2015 CEC-Level dataset PDB.ASUMCELP (built automatically in
Dec 22, 2015 BUILDPDB by the include of member ASUM70PR).
Jan 8, 2015 -SMF70WLA is added to ASUMCELP for the systems whose SMF
70's were read.
-Variable ZIPCPUS was ROUNDed to two decimal places, to
print pretty, as the calculated value often was x.99999,
and debugging _PRN70PR macro was added to VMXG70PR.
Change 33.305 -Support for z/OS 2.2 RMF 74 Subtype 10 SCM Storage Class
EXTY7410 Memory statistics creates new datasets:
EXTY74SC
IMAC74 dddddd dataset description
VMAC74 TY7410 TYPE7410 SCM EADM AGGREGATE STATS
VMAC78 TY74SC TYPE74SC SCM CONFIGURATION MEASUREMENT
Dec 18, 2015 -New z/OS 2.2 variables (COMPATIBLE) in TYPE78PA:
R782LSMOMIN ='MIN FRAMES*ARE USED*SHARED*MEMOBJ='
R782LSMONTME='TIME STAMP*OF MIN*SHARED*MEMOBJ='
R782LSMOMAX ='MAX FRAMES*ARE USED*SHARED*MEMOBJ='
R782LSMOXTME='TIME STAMP*OF MAX*SHAREDMEMOBJ='
R782LSMOAVG ='AVG FRAMES*ARE USED*SHARED*MEMOBJ='
Change 33.304 Dataset TYP120xx variable SM120RULEXSUM was a typo for
VMAC120 SM120RULEXFSUM and now, SM120RULEXSUM doesn't exist.
Dec 16, 2015
Thanks to Homayoun Riazi, OPTUM, USA.
Change 33.303 "Duplicate" obs were created in PDB.DB2STATS when DB2
VMACDB2 used more than 24 buffers in an interval, because DB2
Dec 16, 2015 creates (unexpected) multiple SMF 100 subtype 1 records
for that interval, but the QWHSSTCK time is not exactly
the same, and QWHSSTCK must be used because DB2 stats
records don't contain an interval start time value. There
were no actual duplicated data, but additional obs with
the same SMFTIME and only buffer metrics were created in
the PDB.DB2STATS statistics summary dataset.
Now, the data is ordered by QWHSISEQ and the QWHSSTCK of
the first instance is stored in both PDB.DB2STATB and in
the new PDB.DB2STSBP buffer datasets, and the corrected
QWHSSTCK is used to create PDB.DB2STATS.
Thanks to Rachel Holt, Fidelity Systems, USA.
Thanks to Lori Masulis, Fidelity Systems, USA.
Change 33.302 Support for two optional CICS user fields:
IMACICWR CMODHEAD CMODNAME Variable
IMACICWS OMEGCICS OMEGCICS OMEGCICS $EBCDIC104.
IMACAAAA USER STARPOL STARPOL $EBCDIC92.
UTILEXCL
VMAC110
Dec 15, 2015
Change 33.301 ITRM 33.12+ ERROR: WORK.SUMSTSPB.DATA does not exist.
ITRM -ITRM users of MXG 33.12+ MUST use EPDBOUT macro variable
Dec 11, 2015 to correctly sort the new DB2STSBP Simulated Buffer Pool
with this %LET statement inserted:
%CMPROCES . . .
%LET EPDBOUT= _SDB2SBP ;
%CPSTART . . .
-If you have not installed the ITRM Hot Fix 45583/41019,
you already have an EPDBOUT= _SDB2ST4 _SDB2225, so your
circumvention would be:
%LET EPDBOUT=_SDB2ST4 _SDB2225 _SDB2SBP ;
Thanks to Richard Schwarz, IBM, USA.
Change 33.300 New variables added to DB2ACCTx and DB2STATx datasets by
ASUMDB2A DB2 Version 11 are added to existing summary datasets.
ASUMDB2B The new dataset DB2STSBP summary is added in VMXGDBSS.
ASUMDB2G
ASUMDB2P
VMXGDBSS
Dec 11, 2015
Dec 14, 2015
Thanks to Wayne Bell, UNIGROUP, USA.
Change 33.299 Support for zVM 6.3 MONWRITE z13 SMT Mode; fields were
VMACVMXA inserted (INCOMPATIBLE) in SYTPRP after Change 33.242.
Dec 11, 2015 zVM 6.3.15.1 records have been validated. These
records have been validated. These variables are added
to VXSYTPRP dataset:
PF2CADCT ='UNDELAYED*CAD*INSTRUCTIONS'
PF2TSCAD ='CAD*INSTRUCTIONS*EXECUTED'
PF2TSCNT ='TSGET*REQUESTS'
PF2TSGTM ='TSGET*REQUEST*ELAPSED*TIME'
PFXPOLSR ='CORE*POLARIZATION'
SYTPRP_CAL_PLSIPTEI='IPTE 1/2*ACQUISITIONS'
SYTPRP_COREXTCT='COUNT*MT*COUNTERS*EXTRACTED'
SYTPRP_COREXTTT='DURATION OF*EXTRACT*MT*COUNTERS'
SYTPRP_PFXCPUCH='TIMES WHEN*SIEIHCPU FFFF*SWITCHES'
SYTPRP_PFXPRGCT='TIMES WHEN*SIEIHCPU FFFF'
SYTPRP_PLSIIA ='IPTE 2*ACQUISITIONS'
SYTPRP_PLSIIADD='TIMES WHEN*ACQUIRED*AS SHARE'
SYTPRP_PLSIIHDSSQCH='SSQ TIME*CONTINUOUS*HELD'
SYTPRP_PLSIIWTSSQCH='SSQ TIME*CONTINUOUS*HELD'
SYTPRP_PLSIIHLD='DURATION*CONTINUOUS*HELD'
SYTPRP_PLSIINHLD ='INTERVAL*COUNT*CONTINUOUS*HELD'
SYTPRP_PLSIIWTM='WAIT TIME*IPTE*INTERLOCK*ACQUISITION'
SYTPRP_PLSPTLCA='CALLS SET*PENDING*NON-LOCAL'
SYTPRP_PLSPTLCD='CALLS SET*PENDING*HOST TLB'
SYTPRP_PLSPTLCL='CALLS TO*PURGE*LOCAL*TLB'
Change 33.298 Support for IMS 14.1 log records (COMPATIBLE).
VMACIMS The IMS56FA dataset added two new variables
Dec 10, 2015 DLRDIR='DL/I*IR*CALLS'
DLRDMR='DL/I*MR*CALLS'
in existing reserved bytes.
Change 33.297 -Label for PCTCPUBY was corrected for PDB.TYPE70EN, which
VMAC7072 had incorrectly been "LPAR*CPU*BUSY".
VMXGWORL -VMXGWORL enhanced to parse the result into two macro vars
Dec 10, 2015 &MXGWORLLIB and &MXGWORLDSN so that PROC DATASETS, which
requires them separately, could be used to change labels.
Change 33.296 If you specified IMACKEEP= to retain the IMACKEEP that is
UTILBLDP generated, invalid syntax for _TIMEDIF/_SPINUOW/_SPINCNT
Dec 9, 2015 could be generated; the NULL value default should have
suppressed the generation of these macros; now it does.
The ECHO=YES default will now display the IMACKEEP text.
Thanks to Richard Krueger, Sentry, USA.
Change 33.295 Cosmetic. Prints messages when there are datasets in OLD
VMXGCOMP that are not in NEW, or vice versa.
Dec 8, 2015
Change 33.294 INPUT EXCEEDED ERROR for SMF 102 records written by BMC's
FORMATS Mainview for DB2, IFCIDs 815Ex-8160x - Accounting Rollup
VMACDB2H and IFCID 80F1x - Data Collector, which were unknown and
Dec 9, 2015 unsupported in MXG. These records contain unique SMF 102
Dec 18, 2015 header segments that do not match MXG expectations that
caused the error. But since no one has actually asked
for these subtypes, this change circumvents the problem
Decimal IFCIDS deleted are 33009,33118,33119,and 33120.
by skipping these subtypes in SMF 102 processing in MXG.
-The ANALID report (VMACID,FORMATS) is updated to be aware
of and describe these 102 subtypes in its reports.
Change 33.293 MACRO _TIMEDIF % set instead of MACRO _TIMEDIF 0 % caused
UTILBLDP a 22-322 Syntax Error.
Dec 5, 2015
Change 33.292 When printing of the found datasets is requested, the
VMXGFIND heading has the LIBNAME and MEMNAME printed.
Dec 5, 2015
Change 33.291 Support for BMC Mainview for CICS Version 7.0 (COMPAIBLE)
VMACMVCI adds these new variables for CICS/TS 5.3 to CMRDETL:
Dec 6, 2015 T6E70XCT='70*EXTENSIONS*LENGTH'
T6EDSAWC='ALLOCATE*THREAD*WAIT*COUNT'
T6EDSAWF='ALLOCATE*THREAD*WAIT*FLAG'
T6EDSAWT='ALLOCATE*THREAD*WAIT*TIME'
T6EEIBTR='INTERNAL*PROCESSING*FIELD'
T6EJSRPL='JSON*RESPONSE*MSG LENGTH'
T6EJSRQL='JSON*REQUEST*MSG LENGTH'
T6ELSTN_ACPTOK ='SUCCESSFUL*ACCEPTS'
T6ELSTN_CHILDTK='CHILD*SUBTASKS*STARTED'
T6ELSTN_DISPROG='DISABLED*PROGRAM'
T6ELSTN_DISTRAN='DISABLED*TRANSACTION'
T6ELSTN_GVSKTFL='GIVESOCKET*FAILURES'
T6ELSTN_REJAUTH='REJECTED*NOT AUTH'
T6ELSTN_REJSECU='REJECTED*SECURITY'
T6ELSTN_REJTDIO='REJECTED*TD*I/O'
T6ELSTN_REJTDLN='REJECTED*TD*LENGTH'
T6ELSTN_REJTDNS='REJECTED*TD*NO SPACE'
T6ELSTN_TACPTOK='TERM*SUCCESSFUL*ACCEPTS'
T6ELSTN_TCHILDTK ='TERM*CHILD*SUBTASKS*STARTED'
T6ELSTN_TDISPROG ='TERM*DISABLED*PROGRAM'
T6ELSTN_TDISTRAN ='TERM*DISABLED*TRANSACTION'
T6ELSTN_TGVSKTFL ='TERM*GIVESOCKET*FAILURES'
T6ELSTN_TREJAUTH ='TERM*REJECTED*NOT*AUTH'
T6ELSTN_TREJSECU ='TERM*REJECTED*SECURITY'
T6ELSTN_TREJTDIO ='TERM*REJECTED*TD*I/O'
T6ELSTN_TREJTDLN ='TERM*REJECTED*TD*LENGTH'
T6ELSTN_TREJTDNS ='TERM*REJECTED*TD*NO SPACE'
T6ELSTN_TUNDTRAN ='TERM*UNDEFINED*TRANSACTION'
T6ELSTN_UNDTRAN='UNDEFINED*TRANSACTION'
T6ENCGET='COUNTER*DCOUNTER*REQUESTS'
T6ETOTL_TINITT ='TOTAL*INIT*TIME'
T6ETOTL_TOTHRT ='TOTAL*OTHER*TIME'
T6ETOTL_TREADT ='TOTAL*READ*TIME'
T6ETOTL_TSLCTT ='TOTAL*SELECT*TIME'
T6ETOTL_TWRITT ='TOTAL*WRITE*TIME'
T6ETRUE_ATTACH ='DYNAMIC*SUBTASK*COUNT'
T6ETRUE_INITCKC='INIT*CALL*COUNT'
T6ETRUE_INITCKF='INIT*CALL*FLAG'
T6ETRUE_INITCKT='INIT*CALL*CLOCK'
T6ETRUE_OPENAPI='OPEN*API*COUNT'
T6ETRUE_OTHRCKC='OTHER*CALL*COUNT'
T6ETRUE_OTHRCKF='OTHER*CALL*FLAG'
T6ETRUE_OTHRCKT='OTHER*CALL*CLOCK'
T6ETRUE_READCKC='READ*CALL*COUNT'
T6ETRUE_READCKF='READ*CALL*FLAG'
T6ETRUE_READCKT='READ*CALL*CLOCK'
T6ETRUE_REUS ='REUSABLE*COUNT'
T6ETRUE_SLCTCKC='SELECT*CALL*COUNT'
T6ETRUE_SLCTCKF='SELECT*CALL*FLAG'
T6ETRUE_SLCTCKT='SELECT*CALL*CLOCK'
T6ETRUE_TATTACH='TERM*DYNAMIC*SUBTASK*COUNT'
T6ETRUE_TCBLIM ='TCB*LIMIT*REACHED*COUNT'
T6ETRUE_TINIT='TASK TERM*TOTAL INITS'
T6ETRUE_TOPENAPI ='TERM*OPEN*API*COUNT'
T6ETRUE_TOTHR='TASK TERM*TOTAL OTHERS'
T6ETRUE_TREAD='TASK TERM*TOTAL READS'
T6ETRUE_TREUS='TERM*REUSABLE*COUNT'
T6ETRUE_TSLCT='TASK TERM*TOTAL SELECTS'
T6ETRUE_TTCBLIM='TERM*TCB*LIMIT*COUNT'
T6ETRUE_TWRIT='TASK TERM*TOTAL WRITES'
T6ETRUE_WRITCKC='WRITE*CALL*COUNT'
T6ETRUE_WRITCKF='WRITE*CALL*FLAG'
T6ETRUE_WRITCKT='WRITE*CALL*CLOCK'
T6ETSGSC='SHARED*TS*GETS'
T6ETSPSC='SHARED*TS*PUTS'
In addition, these existing file segments that have no
extended data now create these variables:
PSEUDOFILE='PSEUDO*FILE*NAME'
PSEUDOFILT='PSEUDO*FILE*DURATION'
PSEUDOFILC='PSEUDO*FILE*COUNT'
ADABASFILE='ADABAS*FILE*NAME'
ADABASFILT='ADABAS*FILE*DURATION'
ADABASFILC='ADABAS*FILE*COUNT'
SAPFILE='SAP*FILE*NAME'
SAPFILT='SAP*FILE*DURATION'
SAPFILC='SAP*FILE*COUNT'
DATACOMFILE='DATACOM*FILE*NAME'
DATACOMFILT='DATACOM*FILE*DURATION'
DATACOMFILC='DATACOM*FILE*COUNT'
IDMSFILE='IDMS*FILE*NAME'
IDMSFILT='IDMS*FILE*DURATION'
IDMSFILC='IDMS*FILE*COUNT'
SUPRAFILE='SUPRA*FILE*NAME'
SUPRAFILT='SUPRA*FILE*DURATION'
SUPRAFILC='SUPRA*FILE*COUNT'
S2KFILE='S2K*FILE*NAME'
S2KFILT='S2K*FILE*DURATION'
S2KFILC='S2K*FILE*COUNT'
GENFILE='GEN*FILE*NAME'
GENFILT='GEN*FILE*DURATION'
GENFILC='GEN*FILE*COUNT'
Change 33.290 The ANALID report tabulates all SMF data in the SMF file;
ANALIDDY the new ANALIDDY tabulates the SMF data by DATE of the
TYPEIDDY SMFTIME so day-to-day counts can be compared.
VMACID The syntax for the new report is:
VMACIDDY
Dec 4, 2015 %ANALIDDY(READSMF=YES,PRINT=YES,PDBOUT=WORK);
Dec 5, 2015
Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.
Change 33.289 z/OS only. If you used BLDSMPDB to build a MONTHLY PDB:
BLDSMPDB -If the 1st of the month fell on a Sunday then the code
Dec 3, 2015 miscalculated the start of the last weekly and caused
the last few days of the month to be missing.
-If the 1st of the month did not match the start of the
week then the last few days were duplicated because the
logic looked for daily data GE then the start of the
week and should have looked for GT.
Change 33.288 Reserved Change.
Change 33.287 -The PDB.CICDS CICS Dispatcher Statistics dataset now has
ADOC110 variable DSxPCT='AA TCB*PERCENT*USAGE', the IBM estimate
VMAC110 of each CICS TCB's percentage usage.
Dec 3, 2015 -ADOC110 now documents the new TCBs added in CICS/TS 2.2.
====== Changes thru 33.286 were in MXG 33.12 dated Dec 1, 2015=========
Change 33.286 Six TYP1194L variables LxLCLLNKID and LxRMTLNKID were
VMAC119 incorrectly changed from numeric to character in first
Dec 1, 2015 33.12. They were corrected in final Dec 1 refresh.
All six are formatted with HEX8 format for consistency.
Thanks to Jim Horne, Lowe's, USA.
Change 33.285 Cosmetic, eliminate non-impacting warning that numeric
ASUMTALO variable AVGDRIVE has different lengths in ASUMTALO and
TRNDTALO TRNDTALO, because an ancient statement in member ASUMTALO
Nov 30, 2015 specified LENGTH AVGDRIVE 4 while TRNDTALO invoked
VMXGSUM which sets LENGTH DEFAULT=&MXGLEN that is the
correct syntax to set stored length 5 on EBCDIC or 6 on
ASCII, which are the required lengths for SAS variables
that fully support 4-byte input fields. Observed in QA.
====== Changes thru 33.284 were in MXG 33.12 dated Nov 27, 2015=========
Change 33.284 Warning message in TYPE26J2 that the MXG created variable
VMAC26J2 INREASON is blank is removed; not all purge records have
Nov 27, 2015 enough information to populate the created variable, e.g.
JCL error in INTRDR populates only READTIME, JPURTIME and
SYSREAD.
Thanks to Jim Horne, Lowe's, USA.
Change 33.283 -INVALID DATA for WORD5UP in BBBP ENDING UPTIME because
VMACNMON the expected HH:MM format is sometimes 'HH HRS' when the
Nov 26, 2015 value is 'HH:00'. The HRS text is now removed so the 11
hour value is valid eliminating the error message.
-NMON records missing data and the LF delimiter exist and
they cause strange errors.
-One record with TYPE of DISKBSIZEAAA is clearly missing
data and an LF before the AAA, which is a new record
TYPE. This record caused an INVALID ARRAY error because
MXG tested for TYPE=:'DISKBKSIZE', starting with, for
possible numeric suffixes often used in NMON.
-Another record had only CPAAA, causing an UNKNOWN TYPE
log message.
-A third TYPE=LPAR has 22 valid fields but was missing
the LF separator and had a valid AAA record concat.
This record caused an INVALID INPUT error because MXG
expected numbers in the up to 24 fields in TYPE LPAR.
-Because NMON is character data, all numeric fields are
created with INPUT() functions, but now, with these bad
data records, the INPUT functions are now protected with
the ?? token to suppress the ERROR, PUT _ALL_, and LIST
log messages.
-Disk error messages "NRCOUNTERS NE DSKSEQNR" that were
cited as due to bad data in Change 31.164 are corrected.
They were due to new DISKBUSY1/DISKREAD1/etc objects that
NMON created when there were more than 150 devices that
were NOT supported until now.
Thanks to Steve McCulloch, TMX/CDS Group, CANADA.
Change 33.282 SMF 90 records contain the ENCRYPTED/MASKED UTOKEN value
FORMATS as documented in Change 33.189, which noted IBM does plan
VMAC90A to change to the UNMASKED value, but the encryption logic
Nov 25, 2015 is only an Exclusive OR with '55'x and mapping the result
Nov 27, 2015 into a one byte character which is then INPUT as $EBCDIC,
Dec 1, 2015 so the TOKxxxxx variables in the TYPE90A dataset are now
plain text values if the field was MASKED.
-The 80-byte SMF90T37UTOKEN is decoded into its TOKxxxxx
variables, now set to LENGTH $8 (they are INPUT() with a
SUBSTR() which defaults to length of the input variable),
and so it is no longer kept.
-New FORMAT MGHEXNM was needed to map the XOR value to the
character hex value for the output.
-Dec 1: Error +; was corrected.
Thanks to Peter Relson, IBM z/OS Development, USA.
Change 33.281 A valid WARNING was printed from an SQL step due to a
VMXGSIZE WHERE clause. Logic reordered to eliminate the warning.
Nov 24, 2015
Change 33.280 PDB.TYPE70 for z13 in SMT mode could have the wrong count
VMAC7072 in ZIPCPUS, ZIP70PAT, and ZIPUPTM because SMF70PAT was
Nov 21, 2015 incorrectly added to ZIP70PAT when SMF70ONT is missing.
Thanks to Joachim Sarkoschitz, DATEV, GERMANY.
Change 33.279 -Support for DB2 Simulated Buffer Pool statistics segment,
ANALDB2R creates new PDB.DB2STSBP dataset with per pool data, and
ASUMDBSS four sets of QBnSxxxx interval totals in PDB.DB2STATS and
EXDB2SBP ASUMDBSS creates new ASUMDBSP summary dataset.
IMACDB2 -MOBILEWORK programs QAMOB and MOBWRK02 required updates
MOBWRK02 to support/protect this new dataset
QAMOB -Buffer Hit Ratios for the SBP are created but set to a
READDB2 missing value, pending data for validation.
VMACDB2 -ANALDB2R compile fakers for QWxxxxDB were corrected.
VMXGDBSS -The names of tokens/datasets for SBP mirror STB:
VMXGINIT DB2STB DB2SBP
Nov 18, 2015 DB2STSTB DB2STSBP
Nov 22, 2015 DB2STAB DB2STSB
Nov 23, 2015 ASUMDBSB ASUMDBSP
Nov 26, 2015 MACSTAB MACSTSB
Dec 18, 2015 D2BPSIN D2SBPIN
D2SBPIN D2SBPOU
-There is no count of pages-not-in-the-pool so there is no
buffer hit ratio for the simulated buffer pool that I can
calculate. Variable QBSPREADS is the total number of
requests that caused a read.
Thanks to Lai Fai Wong, Bank of America, USA.
Change 33.278 If you used INTERVAL=MONTH, MXGDURTM was missing for the
VMXGDUR 31-day months, except December, when it was non-missing
Nov 18, 2015 but was 41 days of seconds, because the statement
IF MONTH IN(1.3.5.7.8.10,12) THEN MXGDURTM=41*86400;
should have been
IF MONTH IN(1,3,5,7,8,10,12) THEN MXGDURTM=31*86400;
periods are not allowed, but do NOT create a SAS error.
This is old, present in MXG 30.09 but not in MXG 26.26.
Thanks to Chris Weston, SAS Institute ITRM, USA.
Change 33.277 If you tried to use Example TWO to create ASUMUOW, an
IMACUOW error resulted due to a misplaced percent sign; Example
Nov 19, 2015 THREE did not tell you how to create "MYDATA", and while
Example FIVE did work, it was inconsistent with others.
Thanks to Chris Weston, SAS Institute ITRM, USA.
Change 33.276 RMF III variables GEILF4K and GEILP4K in dataset ZRBGEI
VMACRMFV were reversed in their INPUT order; GEILF4K precedes
Nov 16, 2015 GEILP4K now.
Thanks to Kurt Gramling, Total Systems.
Change 33.275 Assemble/Link Edit all five MXG ASM programs for install.
ASMRMFV The existing single ASM/LKED members are restructured so
CICSIFUE the ASM code is isolated from the JCL so the new JCLASMXG
EXITCICS member will create all five loadlib members in one job.
JCLASMXG ASMRMFV - Used in JCLRMFV to process RMF III VSAM file,
MNVWIFUE output RMFBSAM read by TYPERMFV.
MXGTMNT (Individual ASM/LKED is in JCLASM3/ASMRMFV)
TMONEXIT CICSIFUE - Used in TYPEDB2/TYPE110/TYPE112 to decompress
Nov 16, 2015 IBM SMF records 100, 101, 102, 110, and 112
Nov 23, 2015 SMF records.
Nov 27, 2015 (Individual ASM/LKED is in EXITCICS)
MNVWIFUE - Used in TYPEBBMQ to read compressed BBMQVSAM
and in TYPECMFV to read BMC MainView data.
(Individual ASM/LKED is in ASMMNVW)
MXGTMNT - The MXG Tape Mount Monitor Program, read by
TYPETMNT
(Individual ASM/LKED is in ASMTAPEE)
TMONEXIT - Used in TYPETMO2 to decompress MONICICS
TMON/CICS data.
(Individual ASM/LKED is in EXITMON6)
The original documentation comments are in appendices
at the end of JCLASMXG.
Thanks to MP Welch, Bank of America, USA.
Change 33.274 -Enhancement for character data filtering for RMF Monitor
ADOCRMFV III CSR (Common Storage Remaining) table and other
ASMRMFV usability improvements.
Nov 16, 2015 -These filters are intended for building ad hoc MXG RMF
III PDBs for studies avoiding the overhead of generating
a full CSR table based PDB. They control which CSR table
entries are output to the RMFBSAM file.
-Four new filters are added to support CSR entry selection
from this table to the RMFBSAM output file. These
filters are effective only if the CSR table is selected.
They are applied in the order shown when multiple
different keywords are used.
New Keyword Aliases
------------ -----------------------------------------
CSRJOBNAME= CSRJOBNA=, CSRJOBNM=, CSRJOB=, CSRJN=
CSRJESID= CSRJESNO=, CSRJESNUM=, CSRJESNR=, CSRJID=
CSRAND None
CSROR None
-TUTORIAL:
Ranges of the form keyword=first:last may be used with
any of the above keywords except CSRAND and CSROR.
The colon character ':' is required for a paired range
specification. All entries GE the first value and LE the
last value are selected for output to the RMFBSAM file.
The first value may not exceed the last value in EBCDIC
collating sequence or an error is flagged.
Single unpaired values may be specified for a range
simply as keyword=first and in this case the colon ':' is
omitted.
Patterns may also be used with any of the above keywords
except CSRAND and CSROR and include one or more Wild Card
characters to match the respective CSR data field.
A pattern contains one or more special Wild Card
characters as follows:
Wild
Card Matches
---- -------------------------------------------------
* 0 or more characters
% 1 Non-blank character
+ 1 Numeric character (0-9)
_ 1 Alphabetic character or _ (a-z, A-Z, _)
. 1 National character (@, #, $)
! 1 Special character (not a-z, A-Z, 0-9, @, #, $)
? A blank string if used by itself
? 1 Blank character (X'40') if used with any other
characters
Ranges may not be wild carded. If wild carded the range
value becomes a pattern instead and is processed as such.
See Section 25 "Ranges and Patterns" in the ADOCRMFV
member or ASMRMFV source code for more details on usage
of ranges and patterns.
-CSRJOBNAME= selects CSR entries by 1-8 character z/OS
Job Name. Job Name characters are validated to those
allowed by JCL syntax. Both ranges and patterns with
wild cards may be specified. Up to 64 ranges and 64
patterns are supported. The default is CSRJOBNAME=ALL.
-Examples for CSRJOBNAME= :
CSRJN=PROD1234:PROD5678 selects only address spaces with
a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a
range. Note use of the keyword alias CSRJN for coding
convenience.
CSRJOBNAME=.* is a pattern that selects only address
spaces with a Job Name that begins with a national
character.
CSRJOBNAME=*++ is a pattern that selects only address
spaces with a Job Name that ends with 2 numeric digits.
CSRJOBNAME=ABC:ABC88888 is a range that selects only
address spaces with a Job Name that is GE 'ABC ' and
LE 'ABC88888'.
-CSRJESID= selects CSR entries by 8 character JES Job
Identification. Both ranges and patterns with wild cards
may be specified. Since a JES Id is one subsystem
character followed by 7 digits or three subsystem
characters followed by 5 digits not all pattern
characters may be used with this keyword.
See Section 25 "Ranges and Patterns" in the ADOCRMFV
member or ASMRMFV source code for more details on usage
of ranges and patterns.
-For convenience any leading zeros in the numeric portion
of the JES Id may be omitted and will be filled in
automatically. Up to 64 ranges and 64 patterns are
supported. The default is CSRJESID=ALL.
-Examples for CSRJESID= :
CSRJID=J0000100:J0001123 is a range that selects all
address spaces with batch JES Id numbers GE 100 and LE
1123. Note use of keyword alias CSRJID for coding
convenience.
CSRJID=J100:J1123 is a range that selects the same
address spaces as above with the leading zeros omitted
for coding convenience.
CSRJESID=JOB12345:JOB32001 is a range that selects all
address spaces with batch JES Id numbers GE 12345 and LE
32001 for installations with 5 digit JES Id numbers as a
range.
CSRJESID=J1* is a range that selects all address spaces
with a JES ID that begins with 'J1'. This would include
J1000000 through and including J1999999.
-CSRAND (default) indicates that selection results from
the two different CSR filter keywords are logically
ANDed.
-CSROR indicates that selection results from the two
different CSR filter keywords are logically ORed.
-Examples of CSRAND/CSROR:
With CSRAND (default) in effect:
CSRJESID=J10* CSRJOBNAME=XYZ*
are two patterns that select ONLY jobs whose JES ID
begins with 'J10' AND Job Name begins with 'XYZ'.
CSRAND provides more restrictive CSR entry selection.
With CSROR in effect:
CSRJESID=J10* CSRJOBNAME=XYZ*
are two patterns that select jobs whose JES ID begins
with 'J10' OR Job Name begins with 'XYZ'. CSROR provides
less restrictive CSR entry selection.
-Selection results from repeats of the same CSR filter
keyword are always logically ORed.
-The order of CSR filter application is:
1) CSRJOBNAME=
2) CSRJESID=
-New support for the concept of multi-table selection with
filters JOBNAME= (alias JOB=) and JESID= (alias JID=) to
allow selection by Job Name and/or JES Identification
jobname from both the RMF Monitor III ASI and CSR tables
with one keyword.
-This is a convenience feature to avoid having to code the
Job Name or JES ID selection parameters twice when the
same jobs from both tables are of interest.
-Both the ASI and CSR tables must be selected for these
multi-table selection keywords to function completely.
Otherwise, only entries from the one selected table are
filtered.
Note that most RMF III tables do not contain common
character data fields, but in this case the ASI and CSR
do.
-Example of JOBNAME= :
JOBNAME=ABC* or JOB=ABC* is equivalent to coding
ASIJOBNAME=ABC*
CSRJOBNAME=ABC*
-Example of JESID= :
JESID=JOB01000:JOB01999 or JID=JOB01000:JOB01999
is equivalent to coding
ASIJESID=JOB01000:JOB01999
CSRJESID=JOB01000:JOB01999
NOTE: If a job has ended before the selected MINTIME
intervals it will ONLY appear in the MXG ZRBCSR data set
and NOT the MXG ZRBASI data set.
-Reduced processing overhead for CSR tables.
-RMFV056* (*=I,W,E) message is no longer issued twice when
a single unpaired range value is in error.
-All invalid characters detected in a pattern are now
shown in multiple RMFV056* (*=I,W,E) messages. Before
only the first character in error was displayed. This
could result in repeated runs of ASMRMFV just to find all
the invalid characters in a pattern.
-The error message generation process has been rewritten
for improved efficiency, consistency, clarity, and
usability.
For example, the problem data area in RMFV004* and
RMFV056* messages that shows the text in error is
expanded from 24 to 63 characters. Also all length
errors are displayed in the same format.
-Added new documentation Section 26 "ASMRMFV and SAS PDB
Relationships" that explains which RMF III tables
correspond to which eventual MXG SAS datasets. If the
required RMF III table is not selected in ASMRMFV the MXG
dataset will have zero observations.
All ASMRMFV users should review this useful information.
-Old documentation Section 26 "Summary" is now Section 27.
-The PATTERR= parameter was not effective because it was
not processed until all parameters were read. This was
too late because pattern error handling must occur during
the actual parameter process as patterns are being
scanned.
-PATTERR= parameter handling now occurs immediately when
found in the JCL PARM field or SYSIN DD stream including
severity tailoring of message RMFV056* (*=I,W,E).
-The default value for PATTERR= is now PATTERR=ABEND.
Before the default was PATTERR=WARN. An incorrect
pattern value could result in a waste of processing
resources building an MXG PDB that did not contain the
data desired and so that default was inappropriate.
-The documentation is updated to make it clear that
PATTERR= applies to BOTH pattern AND range errors. There
is no RANGEERR= parameter.
-DISK is now supported as a value alias for the DEVTYPE=
keyword in DVT table filtering so that DEVTYPE=DISK may
be used. Any truncation of 'DISK' as a character value
(DIS,DI,D) is also allowed.
-DVTT= was missing in documentation as an alias for
DEVTYPE= although it was always supported.
-First message RMFV001I now also displays the system GMT
offset as GMT OFFSET=-hh:mm:ss or GMT OFFSET=+hh:mm:ss as
extracted from the z/OS Communication Vector Table (CVT)
in addition to the existing current date and time of
ASMRMFV beginning execution.
-A new RMFV001I message shows the ASMRMFV beginning
execution date and time in GMT.
-A MAXDSNAMES= value exceeding maximum supported &DSNMAX
value was not flagged as an error.
-Message RMFV034S did not correctly display the number of
used table entries when a range or pattern table was
exhausted.
-Several documentation Sections are updated to support
the above changes:
Section 5 "Input Data Selection Parameters"
Section 8 "Error Handling Parameters"
Section 12 "Messages"
Section 13 "Filtered Records"
Section 17 "Abend Reason Codes"
Section 25 "Ranges and Patterns"
Section 26 "ASMRMFV and SAS PDB Relationships" (NEW)
Section 27 "Summary"
Change 33.273 DB2 SMF 102 Trace IFCID=109 INVALID DO LOOP CONTROL ERROR
VMAC102 was caused by unexpected/invalid QWT02R10/L/N triplet
Nov 12, 2015 with all zeros; which is the only segment in the 109 with
QW0109RC, the Bind Return code, so I presumed it was the
purpose for the record and did not test for the existence
of a non-zero count. Now, I do test, and still output an
observation, which will have QW0109RC a missing value.
Thanks to Karl-Olaf, JN Data, DENMARK.
Change 33.272 Cosmetic change to eliminate numeric conversion messages.
ASUMTALO
VMXGRMFI
Nov 11, 2015
Change 33.271 TYPETMO2 processing of compressed records did not print
VMACTMO2 the warning message if the internal MXG decompression is
Nov 11, 2015 used on z/OS instead of the EXITMON6 Infile Exit.
Change 33.270 Variable SMF14ALIAS, the Alias Data Set Name in TYPE1415,
VMAC1415 added by z/OS 2.2 and MXG 33.01, was spelled SMR14ALIAS
Nov 10, 2015 in the KEEP= list so it was not kept. With MXG 33.01+
use MACRO _KTY1415 SMF14ALIAS % in your IMACKEEP to
keep the variable until you drop in the next MXG Version.
Field was added by APAR PI69296.
Thanks to Robert Obee, IMS Health, USA.
Change 33.269 UTILBLDP changes the default to ECHO=YES, so that the
UTILBLDP generated code is automatically printed on the SAS log,
Nov 9, 2015 so we can examine the output without requesting a rerun
to enable ECHO, if there is a problem in execution.
Change 33.268 -Support for SEVEN USER-USER fields in CICSTRAN, and
IMACICVY several other unique fields.
IMACICVZ To enable these user fields, you need to specify
IMACICWA %LET NREXCLUSER=7;
IMACICWB %INCLUDE SOURCLIB(UTILEXCL);
IMACICWC _BLDDICT
IMACICWD _BLDEXCL
IMACICWE _RPTEXCL
IMACICWF -Variable JOB is added to CICSTRAN.CICSTRAN (the JOB name
IMACICWG of the CICS region).
IMACICWH
IMACICWI
IMACICWJ
IMACICWL
IMACICWM
IMACICWN
IMACICWP
IMACICWQ
UTILEXCL
VMAC110
VMXGINIT
Nov 11, 2015
Thanks to Jens Ove Stogaard, NORDEA, SWEDEN.
Change 33.267 SMF 120 dataset TYP120JI only output the first instance;
VMAC120 the offset for the INPUT was not updated by the length.
Nov 6, 2015
Thanks to Elie Sawaya, Royal Bank of Canada, CANADA.
Change 33.266 MXG 33.11 only. ERROR: VARIABLE SYTPN NOT FOUND, only if
VMACXAM _SXAM is used to sort the zVPS datasets; SYTPN should not
Nov 6, 2015 be in the new _BXAMCU2 and _BXAMCUV "By List" macros as
it does not exist in those two new datasets.
Thanks to Matthew Brooks, OPM, USA.
Thanks to Robert Richards, OPM, USA.
Thanks to Leslie W. Mitchell, OPM, USA.
Change 33.265 ThruputManager dataset TPMSLM variables TPMSLXGF/TPMSLXGN
VMACTPMX are TODSTAMP8. STCK datetimes, so their incorrect INPUT
Nov 6, 2015 with &PIB.8.6 and subsequent divide by 4096 was invalidly
creating dates in 2076, since that is a duration value
(same as MSEC8) rather than a datetime value.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.264 Support for APPTUNE 11.2 INCOMPATIBLE changes to the 8005
VMAC102 IFCID record. Some truncated 8005 records are created
Nov 5, 2015 that MXG detects and reports the first instance, and the
Nov 23, 2015 vendor reports a correction will be provided. Datasets
T1028004, T1028005, and T102800B have been data-tested.
Thanks to Rudi Claes, KBC, BELGIUM.
Change 33.263 Support for User CICS field BTMASK.
IMACAAAA
IMACICVX
UTILEXCL
VMAC110
Nov 4, 2015
Change 33.262 Support for SMF 119 subtypes 41-44 (previously, zero obs)
FORMATS and for the below fields added in z/OS 2.1 or earlier
VMAC119 that had been overlooked.
Nov 6, 2015 -Subtype 2, dataset TYP11902:
TTLCLSMCLINKID='LOCAL*SMC-R*LINK*ID '
TTRMTSMCLINKID='REMOTE*SMC-R*LINK*ID'
TTSMCREASON ='SMC-R*LINK*FAILURE*REASON*CODE'
TSMCFLAGS ='SMC-R*FLAG'
FORMAT $MG119RC is created to decode the Reason Code.
-Subtype 5, dataset TYP11905:
TSSMCRACTIVEOPENED ='ACTIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'
TSSMCRACTLNKOPENED ='ACTIVE*SMC-R*LINKS*OPENED'
TSSMCRCONNCLOSED ='CLOSED*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'
TSSMCRCURRESTAB ='TCP*CONNECTIONS*ACROSS*SMC-R LINKS'
TSSMCRCURRESTABLNKS='CURRENT*ACTIVE*SMC-R*LINKS'
TSSMCRINRSTS ='SMC-R*INBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE'
TSSMCRINSEGS ='SMC-R*INBOUND*WRITE*OPERATIONS'
TSSMCRLNKACTTIMEOUT='SMC-R*LINK*ACTIVATION*TIMEOUTS'
TSSMCRLNKSCLOSED ='SMC-R*LINKS*CLOSED'
TSSMCROUTRSTS ='SMC-R*OUTBOUND*WRITE*OPERATIONS*ABNORMAL*CLOSE'
TSSMCROUTSEGS ='SMC-R*OUTBOUND*WRITE*OPERATIONS'
TSSMCRPASLNKOPENED ='PASSIVE*SMC-R*LINKS*OPENED'
TSSMCRPASSIVEOPENED='PASSIVE*TCP*CONNECTIONS*ACROSS*SMC-R LINKS'
TSTCEPHPORTAVAIL ='AVAILABLE*TCP*EPHEMERAL*PORTS'
TSTCEPHPORTEXH ='BIND*FAILS*NO TCP*EPHEMERAL*PORTS'
TSTCEPHPORTINUSE ='TCP*EPHEMERAL*PORTS*CURRENTLY*IN USE'
TSTCEPHPORTMXUSE ='MAXIMUM*TCP*EPHEMERAL*PORTS*USED'
TSUDPBFA='BIND*FAILS*NO*UDP*EPHEMERAL'
TSUDPAVA='AVAILABLE*UDP*EPH*EPHEMERAL'/
TSUDPUSE='INUSE*UDP*EPH*EPHEMERAL'
TSUDPMAC='MAXIMUM*UDP*EPH*EPHEMERAL'/
TS6CEALO='ECSA*CURRENT'
TS6CENIU='ECSA*FREE'
TS6CPALO='PRIVATE*CURRENT'
TS6CPNIU='PRIVATE*FREE'
TS6SMCFC='SMCR*FIXED*CURRENT'/
TS6SMCFM='SMCR*FIXED*MAX'
TS6SMCSC='SMCR*SEND*CURRENT'
TS6SMCSM='SMCR*SEND*MAX'
TS6SMCRC='SMCR*RECV*CURRENT'
TS6SMCRM='SMCR*RECV*MAX'
-Subtype 6, dataset TYP11906:
IFQDXNET='PHYSICAL*NETWORK*ID'
-Subtype 7, dataset TYP11907:
FFSESSID='FTP*ACTIVITY*SESSION*ID'
-Subtypes 41-44, all datasets are now populated.
-Subtypes 97. Variable SSH_FSPATH2 now INPUT and kept;
The three variables SSH_FSPATH/FSPATH1/FSPATH2 should
have been named FCPATH to match their IBM field names.
-Variables EXTWTRNM,JESUBSYS,JOB,LOCLINFO,READTIME are
not kept in datasets TYP11941/42/43/44/4L, where they
don't exist and should never have been kept.
Thanks to James T. Sherpey, Bank of America, USA.
Thanks to David M. Wrobel, Bank of America, USA.
Thanks to Jennifer D. Ayers, West Virginia State Government, USA.
Change 33.261 Internal code change, to make user tailoring easier.
VMAC7072 In dataset TYPE72GO, only two variables are kept for the
Nov 4, 2015 calculated percentage variables, PCTxxxxx and VALDSAMP,
since the numerator value R723yyyy can be re-calculated
in the EXTY72GO exit and KEPT in the _KTY72GO macro in
your tailored IMACKEEP. But by changing the variable
name in the INPUT to the R723yyyy field name and using it
for the PCTxxxxx calculation, those R723yyyy variables
can be added to TYPE72GO with only _KTY72GO tailoring, so
the EXTY72GO tailoring is not required. The code for the
TYPE72MN dataset was similarly revised internally.
Thanks to Erling Andersen, SMT, DENMARK.
====== Changes thru 33.260 were in MXG 33.11 dated Nov 2, 2015=========
Change 33.260 ANALSMDU report analyzes an SMF file for duplicate data
ANALSMDU showing if/when duplicate data exists in separate dump
Nov 2, 2015 groups, with record numbers so duplicates can be removed,
and tabulating if duplicate data exists in individual SMF
dumps.
Thanks to Lizette Koehler, Albertsons/Safeway Stores, USA.
Change 33.259 Support for zVPS Release 4230 for z13 is SMT mode
EXXAMCUV creates two new datasets:
EXXAMCU2 dddddd dataset description
IMACXAM XAMCU2 XAMCU2
VMACXAM XAMCUV XAMCUV
VMXGINIT
Oct 30, 2015
Change 33.258 Support for CICS USER field TORM.
UTILEXCL
VMAC110
Oct 30, 2015
Thanks to Don Deckard, Wal*Mart, USA.
Thanks to Cheryl Jordan, Wal*Mart, USA.
Change 33.257 This change is REQUIRED for CICS/TS 5.3. The final new
UTILEXCL CICS/TS 5.3 field, as always inserted, INCOMPATIBLY,
VMAC110 DSAPTHWT, is now supported, supported, creating variables
Oct 29, 2015 DSAPTHCN='WAIT COUNT*FOR DSA*PATH'
DSAPTHTM='WAIT TIME*FOR*DSA*PATH'
Field was added in Beta 14.
Thanks to Anthony Hirst, Wells Fargo, USA.
Change 33.256 CICS Count of TCB Change Mode Requests was originally in
VMAC110 IBM CMODIDNT=248 CHMODECT, a four byte counter, but that
Oct 29, 2015 was replaced in CICS/TS 1.3 with CMODIDNT=247 DSCHMDLY
which is an 8-byte wait duration plus update counter that
created these two variables that are now re-labeled:
DSCHMDCN='DSCHMDLY*COUNT*TCB*CHANGE MODE*REQUESTS'
DSCHMDTM='DSCHMDLY*DURATION*CHANGE MODE*REQUESTS'
Change 33.255 UTILEXCL failed with ARRAY EXCEEDED when more than 999
UTILEXCL connectors exist; arrays increased to 1999.
Oct 27, 2015
Thanks to Erling Andersen, SMT, DENMARK.
Change 33.254 MXG 33.09-33.10. Using WORK=SASWORK caused TYPE7072 code
VMAC7072 to fail; temporary datasets TYPE70EC and TYPE70EN did not
VMXGINIT have &Wdddddd/&Pdddddd in their _Wdddddd/_Ldddddd tokens,
Oct 26, 2015 so they were written to //WORK instead of //SASWORK, no
Oct 31, 2015 error, but inconsistent. Change 33.217 for z/13+SMT 70's
revised MXG code for TYPE70EC/EL/EN datasets had replaced
_WTY70EN with DATA TYPE70EN (the same when WORK=WORK),
but the VMXGDEL deleted DATASET WORK.TYPE70EN when it
should not have. There is nothing illegal about setting
Options WORK=SASWORK, and it was previously supported,
but it had not been recommended by MXG, and is unneeded
since //WORK can be multi-volume.
Thanks to Scott Bickel, Kansas State Government, USA.
Change 33.253 Added processing of TYPE32 records to tabulate TSO MSU
SAGANAL for each COMMAND in new Report 32. Report 19, PROC PLOT
Oct 30, 2015 was removed from _RPTALL as it was only used in testing.
Nov 3, 2015 New Report 32 tabulates HOURLY TSO MSU for NAT commands.
Change 33.252 IMS Transaction dataset TYPE56FA does not contain SYSTEM,
TYPEIMST the MVS SYSTEM ID, but you can pass the SYSTEM name into
VMACIMS SAS from each JOB's JCL using the SYSPARM() statement:
Oct 22, 2015 // EXEC MXGSAS94,OPTIONS='SYSPARM="SYSA"'
or the SYSTEM can be set with SYSPARM in your //SYSIN
OPTIONS SYSPARM="SYSA";
Then, inside MXG first-time logic that creates ZDATE and
ZTIME, retrieves that value with SYSTEM=SYSPARM(); and
variable SYSTEM is RETAINED and OUTPUT in each dataset.
-SHIFT was added to all IMS datasets based on IMSSTCK.
Only VMACIMS was changed; TYPEIMST is just for reference.
-For years, the only JCL for SYSPARM that worked had EIGHT
quotes before and FIVE after the text, and I have a 2013
example, but that syntax now fails with SAS 9.4, and SAS
now documents the much cleaner double quote syntax.
Both IMS and BVIR require you to supply the SYSTEM thru
SYSPARM=, and other members use SYSPARM to enable debug.
All of the JCL examples with OPTIONS=SYSPARM= now use the
double quotes for both instream and in JCL.
-Variable ZTIME is added to all IMS datasets that have the
ZDATE variable now.
Thanks to David A Bernhardt, Verizon, USA.
Change 33.251 CICSTRAN variable OSTART=ORIGINATING*TASK*START*DATETIME
UTILEXCL was on GMT; MXG overlooked the need to convert it to the
VMAC110 local time zone.
Oct 20, 2015
Thanks to David Shaw, M & T Bank, USA.
Thanks to Douglas Donoho, M & T Bank, USA.
====== Changes thru 33.250 were in MXG 33.10 dated Oct 20, 2015=========
Change 33.250 -SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED RECORD LENGTH
VMAC102 because QWT02R2L is two bytes shorter than the actual
Oct 18, 2015 DB2 10.1 records.
-SMF 102 IFCID 220 INVALID ARGUMENT appears to be a truly
invalid record, with DSNAME where DDNAME should be. The
error is circumvented by validating the DHMS arguments
while the record is investigated. Variable QW0220OT is
the datetime stamp being calculated from characters, and
will be missing for invalid input, without the error.
Thanks to Joe Babcock, General Motors, USA.
Change 33.249 Decoding of DEVCLASS=41 now identifies specific CTC type:
VMACUCB DEVTYPE DEVICE Description
Oct 15, 2015 previous CTC
05X CTC-OSA OSA
06X CTC-OSAD OSA DIAG DEV
07X CTC-IQD HIPERSOCKETS
09X CTC-OSAN OSA ZBX NETWK
0AX CTC-OSAM OSA ZBX MGMT NETWK
32X CTC-FIC FICON
other CTC
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.248 Support for zVSE/Power Version 9 Release 2 Accounting.
TYPEDOS Only minor changes were required, including protection
Oct 13, 2015 for SEGCNT larger than the number of device segments in
the record (caused STOPOVER).
Change 33.247 -If you use UTILEXCL and have more than four "triplets":
VMAC110 WARNING: THE QUOTED STRING CURRENTLY BEING PROCESSED HAS
Oct 14, 2015 BECOME MORE THAN 262 CHARACTERS message is printed.
This warning has NO impact. Change 33.203 added the text
in MACRO _CICXLTR (the list of "triplets" in IMACEXCL) to
MXG diagnostic PUT statements about EXCLUDED fields. Each
triplet test is one line of text so four triplets exceed
a SAS internal limit of 262 character for quoted text in
PUT statements in macro resolution. Change 33.203 used
$LENGTH CICXLTR $32000;
%LET CICXLTR=%QUOTE(_CICXLTR);
CICXLTR=SYMGET('CICXLTR');
to store the text in macro variable &CICXLTR, and then
used "&CICXLTR" to print the text in the PUT statement,
but that's the macro resolution causing the warning!
Now, by using
CICSXLTR=RESOLVE('_CICXLTR');
to directly store the old-style macro text into the data
step variable CICSXLTR, that variable can be used in the
PUT statement, with no macro resolution needed and hence
no warning message. Sites with SAS 9.1 may need to
change RESOLVE to COMPRESS. Contact support@mxg.com.
This shows how easy it is to store the text contents of
an old-style substitution macro into a variable.
-CICS/TS 5.3, close comment missing for TSQIOSCN in the
INPUT statement, causing new-in-5.3 variables in CICSRDQU
Resource dataset TSQGESTM/GESCN/PUSTM/PUSCN/GESBY/PUSBY
to be wrong.
-CICS/TS 5.2 MNSEGCL=5 records with MNR5LENT=96 caused
STOPOVER because MXG expected 104 (5.3 value).
Change 33.246 -Using UTILBLDP with BUILDPDB=YES, if you suppressed type
UTILBLDP 6, 26, or 30, the job failed in BUILD005 when it tried
ZTILBLDP to process the non-existent datasets. Now, if any of the
Oct 20, 2015 datasets are not created, then BUILD005 is suppressed,
and warning message is printed.
-A second execution of UTILBLDP in the same SAS Session
failed with old-style macro errors that are now resolved
and UTILBLDP can be re-executed as often as needed.
-The changes to support second execution were extensive
and thus extensively tested, but, just in case, the prior
UTILBLDP from MXG 33.09 is stored in ZTILBLDP.
Thanks to Michael Reines, Decadis, GERMANY.
Change 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A0 records:
EXATFA0 dddddd dataset description
IMACATF ATFA0 IMSATFAO ATF IMS LCODE A0
TYPEATF ATFDB IMSATFDB ATF IMS DBD
TYPSATF ATFDL IMSATFDL ATF IMS DLI DB
TYPEATFI ATFDT IMSATFDT ATF IMS DLI TM
TYPSATFI ATFD2 IMSATFD2 ATF IMS DB2
VMACATF ATFMQ IMSATFMQ ATF IMS MQ
VMACIMS ATFOA IMSATFOA ATF IMS OTHER A
VMXGINIT ATFOB IMSATFOB ATF IMS OTHER B
Oct 19, 2015 -Application Trace Facility is a component of Omegamon XE
Nov 17, 2015 for IMS v531. Detail trace data from intercepts capture
application execution for IMS related threads, including
DB2 and MQ API calls from an IMS application. The detail
data, possibly millions of intercepts per transaction, is
summarized into new IMS LOG A0 record. It's unlikely to
trace everything always, so this is not a replacement for
the IMS 56FA Log Record (TYPEIMST) for IMS chargeback and
response/resource reporting, but there is more data in
ATF - notably the DBD information - than in the 56FA, so
if selectively enabled for trouble children, it might be
a useful source for IMS trouble shooting.
-TYPEATFI reads IMSLOG format records, TYPEATF reads the
alternate destination, ATFLOG, if that option is chosen.
-MXG member TYPEIMS7 is updated to process ATF records if
found along with all other IMS Log records.
-The IBM default is A0, but that can be changed with the
MACRO _IDATF using %LET MACKEEP= tailoring in //SYSIN.
-ATF replaces the old ITRF component of Omegamon/XE.
-This is the support for Phase I. Additions are coming.
-Nov 17: INPUT @LOCVARSEG+ATFXSNzzO syntax is REQUIRED
because ATFXSNzzO offset can be zero, and the SAS syntax
INPUT @A+B is NOT the same as INPUT @B+A and the first
variable MUST ALWAYS BE NON-ZERO. When in doubt, use
LOC=A+B; INPUT @LOC.
Change 33.244 Unused Change Number.
Change 33.243 RACF Type 80 records don't have variable SUBTYPE because
ANALID the RACFEVNT value is used instead, but now, RACFEVNT is
FORMATS INPUT in the SMF Header processing and stored in SUBTYPE
UTILBLDP so that the ANALID report will tabulate (and describe,
VMACSMF using the updated SMFID format) each type 80 subtype.
Oct 10, 2015 And, UTILBLDP selection by SUBTYPE (WANTSMF=80.02) is now
supported for ID=80 records.
NEVER USE TYPE80/TYPS80, ALWAYS USE TYPE80A/TYPS80A.
Change 33.242 Support for z/VM 6.3.15.0 VXSYSPRT (0.02) z13 SMT mode.
VMACVMXA New SMT-related variables added to the end of the record.
Oct 10, 2015 But: See Change 33.299, REQUIRED.
Change 33.241 A SUM statement is added to the audit report of datasets
PDBAUDIT in your BUILDPDB that reports the total number of pages,
Oct 9, 2015 variables, size, and bytes in each PDB data library.
Change 33.240 TYPE30xx device summary variables for non-existent device
IMAC30IO types (EXCP3350/IOTM3350) can be dropped from all TYPE30s
Oct 9, 2015 and PDB.JOBS and PDB.STEPS by tailoring IMAC30IO to save
disk space (one PDB reduced 400MB from 2500MB to 2100MB).
A new example in comment block can be enabled to keep
only the variables for current device types.
Change 33.239 Some TYPE70 variables can't be DROPped using _KTY70 with
VMAC7072 DROP= because the TYPE70 dataset is not created directly
Oct 8, 2015 as SMF is read (when _KTY70 is used for TYPE70SP). TYPE70
is created from TYPE70SP and TYPE70PR with multiple DATA
DATA steps and Split Record processing. Using _KTY70
also has a risk of dropping a variable needed in the data
steps that follow. This change creates _KTY70DR, a null
old-style MACRO that can be used to drop any variables in
TYPE70 dataset, safely. This syntax in your //SYSIN:
%LET MACKEEP= MACRO _KTY70DR DROP= IF: VF: APPC: % ;
drops all variables starting with IF, VF, or APPC.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.238 Support for RACF Flat File of IRRDBU00 record type 1560
EXRA1560 creates new dataset
IMACRACF DDDDDD DATASET DESCRIPTION
VMACRACF RA1560 RACF1560 GENERAL RESOURCE CERTIFICATE INFORMATION
VMXGINIT CERTN_NAME ='GENERAL*RESOURCE*NAME'
Oct 8, 2015 CERTN_CLASS_NAME ='GENERAL*RESOURCE*PROFILE*CLASS'
CERTN_ISSUER_DN ='ISSUERS*DISTINGUISHED*NAME'
CERTN_SUBJECT_DN ='SUBJECTS*DISTINGUISHED*NAME'
CERTN_SIG_ALG ='CERTIFICATE*SIGNATURE*ALGORITHM'
Thanks to Robert Miles Standish, UBS, USA.
Change 33.237 Support for EDA v7706 (INCOMPATIBLE, two existing 8-byte
VMACEDA user fields were expanded in place to 20 bytes). There
Oct 6, 2015 is no version field in their record; the length of the
record for each subtype is now used to create EDAVERS to
read either the new or old version records transparently.
Thanks to Valentine Wudarczyk, BNYMellon, USA.
Change 33.236 DB2 zPARM QWP4xxxx fields marked (S)-SERVICEABILITY were
VMAC102 not always kept, but IBM is now using these three fields
Oct 14, 2015 QWP4INLP='INLISTP'
QWP4MXOS='MAX*OPT*STOR'
QWP4SHDE='SUPPRESS*HINT*SQLCODE*DYN'
QWP4XMLO='XML*PROCESSING*OPTIONS'
The first two were kept but unlabeled. Now all (S) are
kept and labeled in T102S106 dataset. The first six have
actual labels, the others have their name as LABEL.
QWP4ACCS QWP4ADMT QWP4INLP QWP4MXOS QWP4SHDE QWP4XMLO
QWP4AST QWP4CDE1 QWP4COC1 QWP4COC2 QWP4CTHR QWP4CUT
QWP4FLKT QWP4LTDM QWP4MQTH QWP4MS4A QWP4MXCE QWP4MXOC
QWP4MXOE QWP4MXTB QWP4PLIM QWP4RMTI QWP4SCLC QWP4SCTM
QWP4SELD QWP4SPC QWP4SPS QWP4STHR QWP4TJTH QWP4TTRS
QWP4ULB2 QWP4ULFR QWP4ZUT
-Variables QWP4ACCS and QWP4DFID character values were not
correct when test was EBCDIC, and QWP4OZTM is now numeric
datetimestamp instead of $CHAR8. hex value.
Thanks to Lai Fai Wong, Bank of America, USA.
Change 33.235 Documentation. RED ALERT APAR OA48941 IS REQUIRED BY ALL
VMAC74 z/OS SITES and MUST BE INSTALLED PRIOR TO DEC 15 2015 to
Oct 6, 2015 prevent failure at IPL if the APAR is NOT installed.
The error is in Unicode Service Conversation iconv()
calls which is NOT USED IN MXG. but TELNET and many other
programs are impacted.
Change 33.234 Change 33.155 added R744SNAM to TYPE74HO dataset, which
VMAC74 accidentally corrected an unreported error in the NODUP
Oct 4, 2015 sort to create PDB.TYPE74HO: false duplicates were being
deleted, so the prior PDB.TYPE74HO dataset was incorrect.
The number of obs correctly increased with this change.
And R744CNAM and R744SNAM are added to the end of the
_BTY74HO BY List to formally correct the NODUP sort.
Thanks to Paul Volpi, UHC, USA.
Change 33.233 Support for APAR OA46136 that adds File Transfer Section
VMAC6 with IP Address and Port Number to PSF-created SMF 6.
Oct 1, 2015 No change was required; fields automatically INPUT/KEPT
when the section exists.
Change 33.232 Support for Thruput Manager VARNAME=$ORIGIO NOT FOUND
VMACTPMX message creates new ORIGIO='ORIGINAL*INSYSID' variable
Sep 30, 2015 in the TYPETPMX dataset.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.231 Support for JZOS Java Runtime Performance Stats SMF 121
EXTY121 creates three new datasets:
EXTY121G dddddd dataset description
EXTY121G TY121 TYPE121 JZOS JAVA RUNTIME STATISTICS
FORMATS TY121G TYPE121G JZOS JAVA RUNTIME GARBAGE COLLECTION
TYPE121 TY121T TYPE121T JZOS JAVA RUNTIME THREADS
TYPS121 and new FORMAT $MG121TC for thread category.
VMXG121
VMXGINIT
Oct 8, 2015
Change 33.230 -Example ANAL1430 selects TYPE1415 (non-VSAM) and TYPE64
ANAL1430 (VSAM) records by DSNAME, then merges BY READTIME JOB to
ANAL2642 select the the TYPE30_4 (Step end) for that JOB to get
VMAC42 the RACFUSER field that opened that dataset.
Sep 30, 2015 HOWEVER, this example in ANAL1430 can ONLY capture those
datasets that were CLOSED, and ONLY if that JOB had a
step terminate record in the SMF file.
-Example ANAL2642 selects TYPE26J2 (Job Purge) by SUBMUSER
and selects TYPE42DS (Interval Dataset Activity) by DSN
to report each JOB and DSNAME for that SUBMUSER.
-Type 42 subtype 6 TYPE42DS dataset has new variables
S42READS=SUM(S42AMDRB,S42AMSRB,S42AMZRG,S42DSHRD);
S42WRITES=SUM(S42AMDBW,S42AMSWB,S42AMZWB,S42DSHWR);
the sum of direct and sequential BLOCKS, directory reads/
writes, and zHPF reads and writes.
Thanks to Alyona Bertneski, JPMorgan, USA.
Change 33.229 Support for NDM PT records with zIIP CPU times (INCOMPAT)
VMACNDM inserted these three new variables in NDMPT dataset:
Sep 28, 2015 PTECP0='CPU TIME*SPENT ON*CP'
PTECP1='CPU TIME*SPENT ON*ZIIP'
PTECP2='ZIIP*QUALIFIED*PART OF*PTECP0'
The inserted data caused INPUT STATEMENT EXCEEDED ERROR.
The prior PT record format's UNC and UNN variables were
cleaned up.
Thanks to David Guess, Blue Cross Blue Shield of South Carolina, USA.
Change 33.228 z/OS 2.1 z/13 SMF 74 St 9 INPUT STATEMENT EXCEEDED for a
VMAC74 record with R749DEVN='Hardware Accelerator' but without
Sep 25, 2015 expected Hardware Accelerator and Hardware Compression
segments that MXG INPUT because of that DEVN value. The
record is valid as it contains zeros in the two triplet's
NUMBER OF fields, SMF749FN,SMF7491N, so MXG logic now
knows to test those fields prior to the input of the
SMF749FO,SMF7491O segments, while the reason for their
absence is being investigated.
Thanks to David Marone, SGS-BP, ITALY.
Change 33.227 Dataset TYPE22PB 'RECONFIGURED PCIE PFIDS' had zero obs
VMAC22 due to misalignment in the MXG INPUT statement. See also
Sep 23, 2015 Change 33.146.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.226 Documentation. ERROR: THE GIF DRIVER CAN NOT FIND ANY
MXGSAS92 FONTS and PHYSICAL FILE MVS:SYS3.SAS.SASMONO.TTF.. DOES
Sep 23, 2015 NOT EXIST occurred on z/OS when the old MXGSAS92 PROC
was used for SAS 9.4, instead of using MXGSAS94 PROC.
This DD statement was added and is required for SAS 9.4
// DD DSN=&SASHLQ..CONFIG(COMMON),DISP=SHR
in the //CONFIG DD concatenation.
Change 33.225 Major Revision to this Analysis of Capping now uses the
ANALCAPD PDB.ASUMCELP dataset with data for each LPAR, rather than
Sep 20, 2015 using only the PDB.ASUMCEC summary dataset for the CEC,
with new parameters to allow for selection by LPAR and/or
to set different cap values for different LPARs:
INCODE= a stub of code for selecting data
CEC= one or more CEC serials separated by spaces
LPAR=one or more LPAR/cap values separated by spaces
The plot shows the "Overflow MSU", an estimate of how
long it would take at the cap to get the same number of
MSUs consumed when the rolling 4 hour avg was over the
cap. So the total MSU consumed above the cap based on
the rolling average pro-rated across the four hour
average keeping the system at the cap until all of the
excess MSUs are consumed.
Change 33.224 Cosmetic. Unexpected Unit Address SMFWKUAD='000000'X
VMACSYNC (which normally is a 3-byte EBCDIC like '181'/'F1F8F1'x)
Sep 18, 2015 for a SYNCSORT SORTWK DD segment caused ILLEGAL ARGUMENT
message when it was used to create SYNCDV and SYNCUN with
SYNCDV=INPUT(SMFWKUDA,HEX6.) syntax, as the HEX6 informat
doesn't support the null value. This DD segment also has
" 0 " for the value in VOL variable. Null now protected.
Thanks to Joseph J. Faska, DTCC, USA.
Change 33.223 Short SMF 103 Subtype 13 record caused INPUT STATEMENT
VMAC103 EXCEEDED Error. The segment is documented to contain 56
Sep 18, 2015 bytes plus a name field, but the record contains only 48
bytes. Circumvention: Use the Name-Length Field and its
location to determine if this is 48 or 56 length. Input
normal for 56. For short 48 record, the two 8-byte fields
are changed to 4 so the NAME field aligns, causing Bytes
and Requests are zero in the short records, but the
short record will be output with valid server name.
Thanks to Shabida Khan, Royal Bank of Canada, CANADA.
Change 33.222 -Major enhancement for character data filtering for RMF
ADOCRMFV Monitor III DVT (Device Table) entries and other
ASMRMFV improvements.
Sep 18, 2015 -These filters are intended for building ad hoc MXG RMF
Sep 21, 2015 III PDBs for studies avoiding the overhead of generating
a full DVT table based PDB. They control which DVT table
entries are output to the RMFBSAM file.
-Four filters are added to support DVT entry selection
from this table to the RMFBSAM output file. These
filters are effective only if the DVT table is selected.
They are applied in the order shown when multiple
different keywords are used.
New Keyword Aliases
------------ --------------------------------------
DVTDEVNUM= DVTDEVNO= DVTDEVNR= DVTDEV= DVTN=
DVTVOLSER= DVTVOLI= DVTVOL= DVTSER= DVTV=
DVTAND None
DVTOR None
-TUTORIAL:
Ranges of the form keyword=first:last may be used with
any of the above keywords except DVTAND and DVTOR.
The colon character ':' is required for a range
specification. All entries GE the first value and LE
the last value are selected for output to the RMFBSAM
file.
The first value may not exceed the last value or an error
is flagged.
Ranges may not be wild carded. If wild carded the range
value becomes a pattern instead.
Single values may be specified for a range simply as
keyword=first and in this case the colon ':' is omitted.
Patterns may also be used with any of the above keywords
except DVTAND and DVTOR and include one or more wild
card characters to match the respective DVT data field.
Wild
Card Matches
---- ------------------------------------------------
* 0 or more characters
% 1 Non-blank character
+ 1 Numeric character (0-9)
_ 1 Alphabetic character or _ (a-z, A-Z, _)
. 1 National character (@, #, $)
! 1 Special character (not a-z, A-Z, 0-9, @, #, $)
? A blank string if used by itself
? 1 Blank character (X'40') if used with any other
characters
See Section 25 in the ADOCRMFV member for more details on
usage of ranges and patterns.
-DVTDEVNUM= (and any of its aliases) selects DVT entries
by Device Number. Both ranges and patterns with wild
card characters may be specified. Up to 64 ranges and
64 patterns are supported. The default is DVTDEVNUM=ALL.
Any valid 4 hex character device number with or without
pattern characters in the range of 0000-FFFF may be
specified.
For ranges the Device Number is treated as a binary
number in arithmetic comparisons.
For patterns the Device Number is converted to hex
characters (0-F) prior to pattern matching.
NOTE: Due to the nature of hexadecimal characters not all
characters and/or patterns may be used with DVTDEVNUM=.
See documentation for details.
-Examples for DVTDEVNUM=
DVTDEVNUM=0A00 selects the device with address 0A00 only.
DVTDEVNUM=0A00:0FFF selects all devices with addresses GE
0A00 and LE 0FFF.
DVTDEVNUM=A00:FFF selects the same devices as above with
the leading zeros omitted for coding convenience.
All leading zeros may be omitted if desired when ranges
are used. Leading zeros may NOT be omitted when
patterns are used unless they are included in the
pattern.
DVTDEVNUM=0*F and DVTDEVNUM=*F produce quite different
results.
DVTDEVNUM=B* selects all devices with addresses from B000
through and including BFFF.
DVTDEVNUM=10* selects all devices with addresses from
1000 through and including 10FF.
DEVDEVNUM=C*FE selects all devices with addresses C0FE,
C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE,
CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE.
DEVDEVNUM=C+FE selects all devices with addresses C0FE,
C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, and C9FE
as '+' is a digit (0-9) pattern character.
DVTDEVNUM=C%FE selects all devices with addresses C0FE,
C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE,
CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE as '%' is a
placeholder pattern character.
DVTDEVNUM=C_FE selects all devices at addresses CAFE,
CBFE, CCFE, CDFE, CEFE, and CFFE as '_' is an alphabetic
pattern character.
-DVTVOLSER= (and any of its aliases) selects DVT entries
by Volume Serial Number. Both ranges and patterns with
wild card characters may be specified. Up to 64 ranges
and 64 patterns are supported. The default is
DVTVOLSER=ALL.
Any valid 1-6 character Volume Serial with or without
pattern characters may be specified. Per JCL syntax a
Volume Serial Number is 1 through 6 alphanumeric,
national ($,#,@), or special characters.
NOTE: Since just about any keyboard character is valid in
a Volume Serial please take extra care when coding to
avoid unintended results in the MXG PDB.
-Examples for DVTVOLSER=
DVTVOLSER=C99999 selects the volume serial C99999 only.
DVTVOLSER=C00000:C99999 selects all volume serials GE
'C00000' and LE 'C99999'.
DVTVOLSER=10* selects all volume serials starting with
'10' followed by up to 4 more characters.
DVTVOLSER=H+++++ selects all volume serials starting with
'H' followed by 5 digits.
DVTVOLSER=K*A selects all volume serials starting with
'K' that have a final character 'A' with up to 4
intervening characters.
-DVTAND (default) indicates that selection results from
DVTDEVNUM= and DVTVOLSER= DVT filter keywords are
logically ANDed. DVTAND is effectively ignored if DVT
records are NOT selected
Results for selected Devices for the same DVTxxxxxx=
keyword are ALWAYS logically ORed.
NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and
ZEROIO/NOZEROIO are applied independent of the use of
DVTAND.
-DVTOR indicates that selection results from DVTDEVNUM=
and DVTVOLSER= DVT filter keywords are logically ORed.
DVTOR is effectively ignored if DVT records are NOT
selected
Results for selected Devices for the same DVTxxxxxx=
keyword are ALWAYS logically ORed.
NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and
ZEROIO/NOZEROIO are applied independent of the use of
DVTOR.
-Examples with DVTAND in effect: DVTDEVNUM=CA00:CAFF
DVTVOLSER=SMF* only selects device entries in the DVT
table that have a Device Number GE CA00 and LE CAFF AND
that have a Volume Serial Number that starts with 'SMF'.
DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* DVTVOLSER=PAG* only
selects device entries in the DVT table that have a
Device Number GE CA00 and LE CAFF AND that have a Volume
Serial Number that starts with either 'SMF' or 'PAG'.
-Examples with DVTOR in effect: DVTDEVNUM=CA00:CAFF
DVTVOLSER=SMF* selects device entries in the DVT table
that have a Device Number GE CA00 and LE CAFF OR that
have a Volume Serial Number that starts with 'SMF'.
DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* DVTVOLSER=PAG*
selects device entries in the DVT table that have a
Device Number GE CA00 and LE CAFF OR that have a Volume
Serial Number that starts with 'SMF' or 'PAG'.
The logical OR results in less restrictive filtering
because any of the 3 conditions results in data
selection of a DVT entry.
NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and
ZEROIO/NOZEROIO are applied independent of the use of
DVTOR.
-The order of DVT filter application is:
1) DEVTYPE=
2) DVTDEVNUM=
3) DVTVOLSER=
4) ZEROIO/NOZEROIO
-Section 5 "Input Data Selection Parameters" in
documentation is updated with discussion of all the new
DVT selection keywords and aliases.
-Section 26 "Summary" in documentation is updated for the
new DVT keywords.
-Message RMFV034I did not display correctly on a Device
Number match with DVTDEVNUM= and SHOWMATCH options in
effect.
-Version entry for z/OS 2.2 in RMF release table was not
Correct.
Change 33.221 RMF III data with CPUHOLEN GT 480 and CPUVERG3 EQ 5 ABEND
VMACRMFV INPUT STATEMENT EXCEEDED RECORD LENGTH error when IBM
Sep 17, 2015 changed CPUHOLEN to 740 but did not update CPUVERG3.
Change 33.220 Mini-tutorial on how the INFORMAT in an INPUT function
SAGANAL caused the MSU values to be off by a factor of 100 (an
Sep 17, 2015 error that was immediately obvious!). SAGANAL builds
format $SYS2CAP that maps SMF70CPA to TIME+SYSTEM, and
then retrieves a value with this INPUT function that
uses the 10.2 INFORMAT to "read" the $SYS2CAP value:
SMF70CPA=INPUT(PUT(TIMESYS,$SYS2CAP.),10.2);
which worked, but only accidentally, because all previous
$SYS2CAP values contained a decimal. But if the value in
$SYS2CAP was an integer, the .2 in the 10.2 INFORMAT told
SAS to divide by 100. Removal of the .2 that never should
have been there corrects the error.
Change 33.219 MXG 33.09 Only. VARIABLE MAXCCPUC IS UNINITIALIZED msg,
VMACBVIR typo, caused MAXDCUPC to be a missing value in BVIR10.
Sep 17, 2015
Change 33.218 MXG-created variable WTTOTIOTM (DBMS/IO TOTAL OTHER WAIT)
ADOC110 did not include these recently-added wait variables:
VMAC110 DSCHMDTM FCVSWTTM VCXCWTTM ISALWTTM TCALWTTM TDELWTTM
Sep 16, 2015 TDILWTTM
====== Changes thru 33.217 were in MXG 33.09 dated Sep 15, 2015=========
Change 33.217 z13 in SMT Mode ONLY: LPARCPUS=0 in PDB.TYPE70PR.
VMAC7072 This is the last reported issue with MXG code for z13 in
Sep 13, 2015 SMT mode, and both SMT=1 and SMT=2 data have been tested.
So this change in MXG 33.09 is REQUIRED for z13 SMT mode.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.216 Support for APAR OA47042 adds MOBILE RESOURCES in RMF 70
VMAC7072 and 72 for MOBILE PRICING that eliminates the need to
Sep 11, 2015 process the CICS and IMS transaction records, by using
new WLM Service Definition Qualifier types of Connection
Type (CT) and/or Client Transaction Name (CTN) to set the
new WLM Classification "Reporting Attribute" that can be
set to NONE/MOBILE which WLM uses to identify mobile work
in these new variables.
-Dataset TYPE70 new variables:
SMF70LACM='MOBILE*LONGTERM*AVERAGE*MSU/HR'
SMF70LACA='CAT A*LONGTERM*AVERAGE*MSU/HR'
SMF70LACB='CAT B*LONGTERM*AVERAGE*MSU/HR'
-Dataset TYPE72GO new variables:
R723TSUCP ='TOTAL*GP*SERVICE*MSU/HR'
R723TSUSP ='TOTAL*ZIIP*SERVICE*MSU/HR'
R723TSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR'
R723MSURCP='MOBILE*GP*SERVICE*MSU/HR'
R723MSURSP='TOTAL*ZIIP*SERVICE*MSU/HR'
R723MSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR'
R723ASUCP ='CAT A*GP*SERVICE*MSU/HR'
R723ASUSP ='CAT A*ZIIP*SERVICE*MSU/HR'
R723ASUOCP='CAT A*ELIGIBLE*SERVICE*MSU/HR'
R723BSUCP ='CAT B*GP*SERVICE*MSU/HR'
R723BSUSP ='CAT B*ZIIP*SERVICE*MSU/HR'
R723BSUOCP='CAT B*ELIGIBLE*SERVICE*MSU/HR'
These metrics may be available for z/OS 2.2 and z/OS 2.1
later this year.
Note that R723TSUCP=SUM(CPUUNITS,SRBUNITS);
Change 33.215 Documentation change only. Added an example of using
VMXGSUM VGETDDS to drive the input to VMXGSUM.
Sep 9, 2015
Change 33.214 If UTILBLDP was executed twice in the same session, and
UTILBLDP the USERADD= option was used, the second execution failed
Sep 10, 2015 because the _IDxxxx "SMF Record Macros" were not cleared.
Thanks to Michael Reines, Decadis, GERMANY.
Thanks to Ron Hawkins, HDS, USA.
Change 33.213 Support for WASODM Operational Decision Manager 8.7.1 SMF
VMAC120 Type 120 Subtype 100 (MXG Dataset TY120100) INCOMPATIBLE.
Sep 10, 2015 The record was completely restructured internally, and
Oct 8, 2015 these ruleset statistics now exist in SM120HDV=3 records:
SM120RULEXBAD ='RULESET*FAILED*EXECUTION*COUNT'
SM120RULEXCALLS='RULESET*NUMBER*OF*CALLS'
SM120RULEXCMAX ='RULESET*MAX*CPU*JAVA TIME'
SM120RULEXCMIN ='RULESET*MIN*CPU*JAVA TIME'
SM120RULEXCPU ='RULESET*TOTAL*CPU*JAVA TIME'
SM120RULEXFSUM ='RULESET*SUM OF*FIRED*RULES'
SM120RULEXNUM ='RULESET*SUCCESSFUL*EXECUTION*COUNT'
SM120RULEXPATH ='RULESET*EXECUTION*PATH'
SM120RULEXTIME ='RULESET*TOTAL*ELAPSED*JAVA TIME'
SM120RULEXTMAX ='RULESET*MAX*ELAPSED*JAVA TIME'
SM120RULEXTMIN ='RULESET*MIN*ELAPSED*JAVA TIME'
-SM120HDV=1 records (in Versions 8.5.1.0 and 8.6.0.0) and
SM120HDV=2 records (in Versions 8.5.1.2) contain only
these counters: SM120RULEXNUM SM120RULEXBAD SM120RULEXSUM
-Records with no Extension segment are now output; these
appear to be interval records when there was no activity.
New variable SM120EXNNR identifies if the record has an
extension, and if so, which one.
-The prior TY120100 dataset was incorrectly/wrongly built
with the number of observations in WORK.TY120100 higher
than the number of input records, and the number of obs
in PDB.TY120100 too few (and wrong).
Thanks to Scott Barry, SBBWorks Inc., USA.
Thanks to Paul Volpi, UHC, USA.
Change 33.212 Support for MEGACRYPTION Version 6 SMF records,
VMACMGCR (MGCRLEV='2') which incompatibly increased the length of
Sep 8, 2015 the MGCRBYTE and MGCRKS fields from 4 to 8 and 40 to 60.
Thanks to Randy Schlueter, First Data Corporation, USA
Change 33.211 New variables are added in DB2 Trace Dataset T102S199.
VMAC102 QW0199SC='LAST TIME*DATABASE*STATISTICS*UPDATED'
Sep 8, 2015 QW0199ID='MORE*RECORDS*OR*LAST?'
QW0199SD='SHADOW*COPY?'
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 33.210 More TMON/CICS Version 3 AND Version 4 corrections.
VMACTMO2 -MONITASK for Version 3 was wrong in MXG 33.08, with
Sep 11, 2015 misalignment starting at variable CICOVHTM.
-MONITASK Version 4 requires ASG PTF TH03803 to correct
invalid values in variables TASTCPUC and TASTCPOC.
-The MONISYST dataset was misaligned and has been updated
and validated with both 3.3 and 4.0 records.
Thanks to Francois Vancoppenolle, PV Group, BELGIUM.
Change 33.209 Cosmetic changes from ITRM Validation.
VMAC102 -VMXG70PR: Temporary variable N60PLUSLPAR no longer kept
VMAC110 in PDB.ASUM70PR and PDB.ASUMCEC datasets.
VMAC119 -VMAC110: Variables DS7START,DS7LSTRT now labeled.
VMAC50 -VMAC102: The nineteen QWn196Ha variables added by 31.236
VMAC7072 are now labeled/formatted/Length consistently.
VMAC74 -VMACNDM: Offset variable NDMGPE1D is no longer kept in
VMAC75 NDMRT dataset.
VMAC76 Variables NDMZLIBR/LIBS PTRESTRECORD labeled.
VMAC77 -VMACSTC: STC14TOD and STC27TPX variables are labeled.
VMAC99 -VMAC119: Variables SMF119SM_ and SMF119FT_ are labeled.
VMACNDM -VMAC50: Variable TY40EXTL labeled.
VMACSTC -VMAC7072: Temp variables R725QSR1/QSR2/QST1/QST2 are not
VMACXCOM kept since they were already used to create the
VMXG70PR SSQ variables R725QSRQ R725QSTQ.
Sep 6, 2015 -VMAC74-7: Variables SMF74/75/76/77/GIE are labeled.
-VMAC99: Variables S99CMTFLGS1/2 label typo corrected.
-VMACXCOM: Many XCOxxxxx variables are labeled.
Thanks to Chris Weston, SAS Institute, USA.
Change 33.208 z/OS ONLY. If you use VGETDDS with DDNAMES=PDB: syntax
VGETDDS (to read all DDNAMEs starting with PDB), and those DDs
Sep 6, 2015 are on tape, VGETDDS mounted all of the tapes twice, once
to detect is is a SAS dataset and then once to actually
read the data. Now, once VGETDDS finds that a PDBn DD
points to a tape device, it will presume all the others
are also tape, and thus eliminate the double mounts. But,
if a DDNAME that matches the test is NOT a SAS dataset
the job ABENDs with ERROR:LIBRARY PDBn IS NOT IN A VALID
FORMAT FOR ACCESS METHOD V9SEQ or if UNIT=AFF is used but
DEFER=YES was NOT, then a SYSTEM 413 ABEND occurs trying
to open all tape devices at the same time.
-The typically unneeded MXGNOTE messages are now skipped
with the MXGEXIMSG option.
Change 33.207 z/OS 2.2: REQUIRES ML-55 of MXGTMNT, for ABEND S0E0-28.
ASMTAPEE In z/OS 2.2, IBM's CSRPOOL service, called by MCSOPMSG in
Sep 8, 2015 ASMTAPEE, puts diagnostic data into GR0, AR0, and AR15,
none of which are expected to be preserved, but R15 was
used by ASMTAPEE, because it was unused and available.
Now ASMTAPEE clears AR15 to eliminate the ABEND exposure.
Change 33.206 z/OS 2.2 Job Correlation Variables SMF30COR is now INPUT
BUILD005 kept in TYPE30xx datasets, and also output in PDB.JOBS,
VMAC30 PDB.STEPS, and PDB.SMFINTRV. Variable SMF26JCR was INPUT
Sep 4, 2015 and kept in TYPE26J2 previously, but now it is also kept
in PDB.JOBS and PDB.NJEPURGE datasets with BUILDPDB.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.205 DB2ACCTP variables QPACPKID/QPACLOCN/QPACASCH/QPACAANM
VMACDB2 and QPACCOLN could be truncated even though they have
Sep 2, 2015 valid extended name segments. The LENGTH test for the
new PAR QUERY fields wrongly INPUT them when they did not
exist, causing the DELFIX circumvention to incorrectly be
invoked, causing the extended segments to not be input.
Thanks to Tom Adams, State Farm, USA.
Thanks to Shankar Chatterjee, State Farm, USA.
Change 33.204 Variable IOTMNODD was never calculated in PDB.JOBS/STEPS,
BUIL3005 and the value in IOTMTODD was actually IOTMNODD. The
BUILD005 three calculations of IOTMTODD= should be IOTMNODD=.
Sep 2, 2015
Thanks to Rick Southby, Insurance Australia Group Limited, AUSTRALIA.
Change 33.203 Cosmetic. EXCLUDED FIELDS FOUND messages now print your
VMAC110 site's IMACEXCL testing values, so you can see if this is
Sep 1, 2015 for a new dictionary triplet that needs a UTILEXCL rerun.
This was originally added in Change 29.262, but somehow,
the needed quotes and ampersand "&CICXLTR" syntax got
changed to CICXLTR, which printed nothing.
Change 33.202 Velocity ZVPS 5.4 dataset XAMSYT has zero observations
VMACXAM because Change 33.157's recalculated SYTNLPS was zero.
Aug 29, 2015 The actual SYTNLPS+1 in the non-Total record is now used
Sep 2, 2015 and the false INVALID SYTCUP SEGMENT message is removed.
Sep 11, 2015 -Unexpected CPID='GPs' value is now output in XAMCPUTO as
there were no records with CPID='Total".
Thanks to Douglas C. Walter, CitiCorp, USA.
Thanks to Brent Turner, Citigroup, USA.
Change 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE VERSION 10.2.1
VMACCDC adds many new variables to the CDI, CDO, CDW, DLR, DSL,
Aug 30, 2015 DTC, OSC, SCT, SDT, TCT, and new TDT segments. However,
the SCT and TCT data does not match the documentation and
both SCTCPU and TCTCPU are invalid with this iteration.
Thanks to Phil Grasser, Norfolk Southern, USA.
Change 33.200 -TYPE70xx datasets have always contained ONLY data for the
VMAC7072 engines that were ONLINE at interval end, and that had
Aug 28, 2015 NOT been VARYed ONLINE (i.e., CAI='01'X). Engines that
were IPL's (CAI='03'X) were NOT output, because the data
in those startup intervals was inconsistent in early MVS.
However, those partial interval's data is not only valid,
it is actually now required to prevent wrong or missing
values for CECSER in TYPE70/TYPE70PR/TYPE70EN datasets,
and to capture the IPL interval's resources.
-TYPE70EN variable CPUBSYTM is now correctly set missing
for zIIP/zAAP engines, since it is a CP engine metric.
-More observations are now output, so PROC COMPARE will
see differences in these variables:
TYPE70: CECSER CPUACTTM CPUMVSTM CPUWAITM PCTCPUBY
PCTMVSBY PCTRDYWT PLCPRDYQ SHORTCPS
TYPE70PR: CECSER
TYPE70EN: CECSER CPUBSYTM CPUMVSBY
Change 33.199 The AXWAY SMF record was INCOMPATIBLY changed by an
VMACAXWY increase of a field length.
Aug 31, 2015
Thanks to Rachel Holt, FMR, USA.
Change 33.198 -CICS/TS 5.3 BETA, Resource Class (MNSEGCL=5) could cause
VMAC110 INPUT STATEMENT EXCEEDED INPUT because only 112 bytes of
Aug 27, 2015 the MNR5LENT=120 bytes were read.
Change 33.197 -Variable LPBUSY in TYPE113 is the TOTAL BUSY for all CPs
ASUM113 and can exceed 100% with multiple engines, but variable
VMAC113 LPARBUSY in ASUM113 is the CPU BUSY OF ONE ENGINE. New
Aug 24, 2015 variable LPBUSY is now created in ASUM113 with TOTAL BUSY
to provide both perspectives on percent busy.
-Variable SRBSTATE is now created in ASUM113 to complement
the existing PRBSTATE variable.
Thanks to David Cogar, Wells Fargo, USA.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.196 BVIR variable's values are revised to match IBM reports.
VMACBVIR TVCSIZE is now internally in bytes, formatted MGBYTES,
Aug 30, 2015 and the label corrected.
AVGCPUSE is now percent (95.5) instead of 0.95 fraction.
AVGDEFTH is now correct, was 1000 too large.
Thanks to Patricia J. Jones, DST Systems, USA.
====== Changes thru 33.195 were in MXG 33.08 dated Aug 20, 2015=========
Change 33.195 TMON/CICS Version 4.0 Support was still wrong, with an
VMACTMO2 extra 8 bytes INPUT that shouldn't have been, so that
Aug 20, 2015 MXG 33.08 dated Aug 20 is NOW required for version 4.0.
-Variables TASTCPUC and TASTCPOC in dataset MONITASK have
invalid data values, await PTF from ASG.
Thanks to Francois Vancoppenolle, PV Group, BELGIUM.
Thanks to Dirk Thys, PV Group, BELGIUM.
Change 33.194 -The modern CLRMFV Clist is incompatible with the archival
ZCLRMFV ZASMRMFV program because RMF III files are allocated with
Aug 19, 2015 RMFC prefixed DDNAMEs and the archival version of
ZASMRMFV is not aware of these. This results in message:
RMFV015E +++ERROR: NO VALID RMF III INPUT FILES FOUND+++
-A new Clist ZCLRMFV for use with ZASMRMFV only is created
with this change that will only allocate RMF III data
sets with RMFV DDNAME prefixes.
Thanks to Tom Drager, Aurora Health Care
Change 33.193 ANALDSET abend IEC145I 413-04 with DDNAME=ADDPROG because
ANALDSET the DATA step inserted by Change 32.187 broke the logic
Aug 19, 2015 for UNIT=AFF by trying to read and write to and from the
same tape device.
Thanks to Randy Hewitt, HP Canada, CANADA.
Change 33.192 -CICS/TS 5.3 Beta added two new variables to CICSTRAN that
UTILEXCL caused UTILEXCL to report UNKNOWN WBJSNRQL and WBJSNRPL
VMAC110 fields, but the IMACEXCL it created has a syntax error,
Aug 18, 2015 And, since the two fields were INSERTED, the MXG INPUT
without IMACEXCL caused subsequent fields to be invalid
as they were misaligned. Now, 70/378/3376 are expected
values for 5.3 default SMFPSRVR, MCTSSDCN, and MCTSSDRL.
(Other values will generate the RUN UTILEXCL messages.)
-The CICSRDQU records have new reserved fields inserted,
that caused misalignment.
=====================================================
CICS/TS 5.3 IS STILL IN BETA, with final GA is Sep 31,
so IBM is still free to make other changes.
=====================================================
Thanks to Paul C. Gordon, Bank of America, USA.
Change 33.191 UTICBLDP error message COMPBL HAS TOO MANY ARGUMENTS was
UTILBLDP due to an unneeded second COMPBL invocation for MACKEEPX.
Aug 18, 2015 The second execution was removed, but the error was also
triggered by comments with "* comment text ;" syntax, and
using " /* comment text */ " syntax also circumvented the
error. In general, that second syntax is more robust,
but in this case, placing the comments OUTSIDE the MACRO
circumvents the need to parse either comment syntax.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.190 While the WORK.TY115215 dataset is created by TYPE115,
VMAC115 using TYPS115 did not create PDB.TY115215 because the
VMXGINIT _STY115X dataset sort macro for TY115215 was not added
Aug 17, 2015 in the _S115 "product" sort macro for SMF type 115s.
This caused dataset TY115215 to not be listed in DOCVER.
====== Changes thru 33.189 were in MXG 33.08 dated Aug 17, 2015=========
Change 33.189 Support for z/OS 2.2 (COMPATIBLE, but LOTS NEW STUFF):
BUILD005 -TYPE0203: Support for new ID=2 SUBTYPE=1 and 2 records
EXTY4227 create two new datasets in VMAC0203:
EXTY9037 DDDDDD DATASET DESCRIPTION
FORMATS TY0201 TYPE0201 TYPE 2 SUBTYPE 1 SIGNATURE GROUP
IMAC42 TY0202 TYPE0202 TYPE 2 SUBTYPE 2 SIGNATURE INTERVAL
IMAC90A -TYPE1415: Change 33.026 added support for LONG WANTED new
VMAC0203 variables SYSPLEX JESNR JCTJOBID TYPETASK, but the pre-
VMAC104 GA SMF Manual had the order of SYSPLEX/JCTJOBID while
VMAC106 the actual order is JCTJOBID/SYSPLEX and the typo will
VMAC1415 be corrected for the Sub-type 3 record.
VMAC30 -Sub-type 5, length is 72 but 70 in SMF Manual; two bytes
VMAC42 are skipped
VMAC6156 -SMF14ALIAS now created.
VMAC74 -SMF14DSVER value is '01'x but bits 0, 1, 2, are listed
VMAC90A in the SMF Manual. Await IBM answer.
VMAC99 -JOB variable has un-printable characters in the 14/15s,
VMACCTLG but valid characters are in JOB variable in 30s, in pre-
VMXGINIT GA data. Await IBM answer. SMF14ESL=26 STY=5 (old
Mar 8, 2015 length) protected.
Jun 8, 2015 -TYPE26J2: New IBM JCTJOBID=:'G' value will set the MXG
Jul 21, 2015 TYPETASK='JOBG', only in TYPE26J2 Purge Records for a
Jul 24, 2015 JOBGROUP's logging job's purge, which is the only place
Aug 4, 2015 that 'G' value is externalized in SMF records.
Aug 17, 2015 -TYPE30 : New ABEND='EVICT' value set in TYPE30 for jobs
Mar 1, 2016 evicted with $EJ,STEP,HOLD.
-TYPE42: Change 33.026 added support for new TYPE4227
dataset provide the VTOC AUDIT LOG with these variables:
JCTJOBID ='SMF42RNJO*JOB NUMBER'
JESNR ='JES*NUMBER'
TYPETASK ='TYPE*OF*TASK;
SMF42RIND ='SMF42RIND*RECORD*INDICATOR'
SMF42RSEEK='SMF42RSEEK*VTOC*TRACK*ID'
SMF42RSRCH='SMF42RSRCH*VTOC*RECORD*ID'
SMF42RCMDS='SMF42RCMDS*CCW*COMMAND*CODES'
SMF42RUPSW='SMF42RUPSW*CALLERS*ADDRESS'
SMF42RUTOK='SMF42RUTOK*USER*SECURITY*TOKEN'
SMF42RRSV ='SMF42RRSV*DEVICE*IS*RESERVED?'
SMF42RKEY ='SMF42RKEY*DSCB KEY*DATASET*NAME'
SMF42RDSC ='SMF42RDSC*DSCB*DATA*FIELD'
SMF42RACT ='SMF42RACT*ACTIVITY*TYPE'
with these possible activities in SMF42RACT that are
decoded by $MG042VT format:
'D***'='D***:DFSMS ACTIVITY'
'DCVF'='DCVF:CVAFDIR'
'DCRE'='DCRE:DADSM DATASET CREATE'
'DEXT'='DEXT:DADSM DATASET EXTEND'
'DPAR'='DPAR:DADSM DATASET PARTIAL RELEASE'
'DREN'='DREN:DADSM DATASET RENAME'
'DDEL'='DDEL:DADSM DSCB SCRATCH'
'DUPD'='DUPD:DADSM DSCB UPDATE'
'DFRG'='DFRG:DFSMSDSS DEFRAG'
'DCON'='DCON:DFSMSDSS CONSOLIDATE'
'DDMP'='DDMP:DFSMSDSS DUMP'
'DRST'='DRST:DFSMSDSS RESTORE'
'IOBE'='IOBE:IOBE NOT PROVIDED'
'USER'='USER:IOBEUSER NOT SPECIFIED'
-TYPE42: Support subtype 5/6 APAR OA44322/OA44319 CMR+
and new microsecond metrics was added in Change 32.113.
-TYPE74: Change 32.305 added support for new TYPE 74
variables: R744MNEL R744MNEC R744NSRK
-TYPE90A: Updated for new Type 90 subtype 37 to create
new TYPE9037 dataset that reports any changes to APF
status. The RACF UTOKEN has '55'X values in SMF data
because it's value is "MASKED", i.e., encrypted, while
MXG expected the "UNMASKED" values that are in UTOKEN in
other SMF records (42, 80, 119). The existing SMF 90
subtypes 29 and 31 also contain the MASKED UTOKEN, but
IBM Development has stated their intention to change to
UNMASK the UTOKEN in all three of those 90 subtypes.
HOWEVER: SEE CHANGE 33.282 - MXG now "unencrypts".
The RACROUTE REQUEST=TOKENMAP can do the "unmasking",
and can be used even on a system that was not the one
on which the SMF record was created, but that can only
be used on z/OS; even there it would take SIGNIFICANT
effort to issue a RACROUTE from within a SAS data step.
But since the data length is 80 bytes either way, and
the data is not secret, it really needs to be UNMASKED
to be of value, so IBM's future correction is welcome.
-TYPE90A: Two variables added to TYPE9037 dataset.
Formats added to TYPE9037 variables.
-TYPE99 : Five variables added to TYPE9912 dataset.
-TYPE104: Platform Types that create SMF Type 104 records
are expanded and format updated:
VALUE MG104PT
0='0:AIX ON SYSTEM P'
1='1:LINUX ON SYSTEM X'
2='2:LINUX ON Z SYSTEM'
3='3:WINDOWS ON SYSTEM X'
-TYPE106: Support for new ID=106 SUBTYPE=1 and 2 records
create two new datasets in VMAC106
DDDDDD DATASET DESCRIPTION
TY1061 TYPE1061 BCPII HWISET API CALLS
TY1062 TYPE1062 BCPII HWICMD API CALLS
Mar 1, 2016: Incorrect length for SMF6ASDL, corrected
to input 4 bytes.
-VMACCTLG and VMAC6156 were updated Nov 27, 2014.
Support for GDGE, GDG Extended GDGLIMIT=999 in z/OS 2.2.
New variable GATEXTND='E' flags the extended mode, new
variables GATLIMTE/GATCNTE are INPUT but also kept in the
existing GATLIMIT/GATCNT to preserve existing reports.
Some overlooked flag variables in the 05 Catalog Segment
are now decoded and kept in datasets TYPE6156 (from SMF
(type 61, 65, 66) and TYPECTLG (from the IDCAMS EXPORT
CATALOG flat file). These are all the 05 fields now:
GATALLOC='GATALLOC*FIFO OR*LIFO?'
GATCNT ='GDG*COUNT'
GATDELET='DELETE*WHEN*LIMIT*EXCEEDED*0=OLD*1=ALL?'
GATEXTND='GATEXTND*EXTENDED*OR CLASSIC?'
GATEXTNO='GATEXTNO'
GATGEN ='GATGEN '
GATLIMIT='MAXIMUM*GDS*ENTRIES*IN GDG*BASE'
GATLIMTE='EXTENDED*GAT*GATLIMIT'
GATPURGE='GATPURGE*YES OR*NO?'
GATSCRTH='SCRATCH*FORMAT 1*DSCB*0=NO*1=YES?'
GATVER ='GATVER '
GATWRAP ='GATWRAP '
GDGATTR ='GDGATTR'
-BUILD005 protects for TYPETASK='JOBG' in JCTJOBID.
Change 33.188 TMON/CICS Version 4.0, these four MONITASK variables were
VMACTMO2 divided by 4096, TWICE:
Aug 13, 2015 TASTCPUT TASTCPOT TACNTRTM TACNTWTM
and these MONIAMQ variables were NOT divided because the
test was GT 4 and it should have been GE 4.
TAAMQOPT TAAMQCLT TAAMQGTT TAAMQPTT TAAMQP1T
TAAMQIQT TAAMQSTT
This change is REQUIRED to support TMON/CICS Version 4.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.187 DB2 T102S106 didn't keep variables QWP4RSMX and QWP4ACAN
VMAC102 and these zparms were not input.
Aug 14, 2015 QWP1CSMF='SMFCOMP'
Aug 20, 2015 QWP1FLG2='QWP1FLG2*FLAG*BITS'
QWP1LOGT='LOG*CHECKPOINT*TYPE'
QWP4ABVC='QWP4ABVC*SERVICEABILITY'
QWP4ACAN='QWP4ACAN*SERVICEABILITY'
QWP4CGAA ='GET_ACCEL_ARCHIVE*0=NO*1=YES*/
QWP4CQAC ='QUERY*ACCELERATION'
QWP4EXQRY ='QWP4EXQRY'
QWP4FCPPRC='FLASHCOPY*PPRC'
QWP4QACO ='QUERY*ACCEL*OPTIONS'
QWP4RFRP ='REC_FASTREPLICATION'
QWP4RLPR ='REORG*LIST*PROCESSING'
QWP4RPSN ='REORG*PART*SORT*NPSI'
QWP4RSMX='QWP4RSMX*SERVICEABILITY'
QWP4STMN ='REALSTORAGE*MANAGEMENT'
QWP4WFRD ='MAX RID*BLOCKS*TEMP STG*PER RID LIST'
QWP4_BIF_COMPAT='BIF*COMPATIBILITY'
QWP9DDFCIP='DDF COMPAT*IDENTITY*PRIOR VERSION*NNR'
Thanks to Lai Fai Wong, Bank of America, USA.
Change 33.186 -An INCOMPATIBLE z13 ERROR, only in SMT-MODE, and only if
VMAC7072 a CP engine is varied online, is now corrected. When a
Aug 16, 2015 a z13 in SMT mode varied a new CP online, MXG did not see
the new engine, causing PDB.TYPE70 and PDB.TYPE70EN to
be wrong, with incorrect PCTCPUBY and NRCPUS=. and no
dispatch times for the new CP engine in PDB.TYPE70.
An IBM error is only partially responsible: after the
VARY, the value for SMF70CIX in the PR/SM LP Data Section
is incorrect (1, for CP, instead of 6, for zIIP) in both
of the zIIP sections for the second zIIP engine, causing
MXG to identify those zIIPs as CP Engines, mismatching
the engines in the CPU Data Section. That error is
circumvented by revising MXG to use the SMF70TYP value
from the CPU data section (which is clearly what IBM had
to use in their RMF reports). A second error was MXG's:
the new CP Engine PR/SM section was located AFTER those
zIIP sections, but MXG's original SMT logic was correct
only when all CPs preceded the zIIPs. That incorrect
MXG logic was revised to now be order independent.
-TYPE70PR does NOT contain SMT variables, those data are
only output in PDB.TYPE70EN since they can only be
populated from "this" system's TYPE70 records.
Thanks to Douglas C. Walter, CitiCorp, USA.
Thanks to Brent Turner, Citigroup, USA.
Change 33.185 -Labels for TYPE30 ZEDC variables with _INF_/_DEF_ are now
FORMATS spelled out as INFLATE and DEFLATE.
VMAC30 -TYPE74 subtype 9 DIVIDE BY ZERO caused by R749FRQC=1 is
VMAC74 eliminated by changing test to R749FRQC GT 1 since more
Aug 11, 2015 than one instance is required to calculate STD (Standard
Aug 17, 2015 Deviation) statistic.
Aug 20, 2015 New variable PCTCRDBY added to TYPE749 dataset for card
Aug 30, 2015 busy percentage.
-TYPE74 variables used to create SSQ (Sums of Squares) are
no longer kept since the STD variables are calculated.
-Variable R749DFMT is now labeled 'PCIE*FUNCTION*TYPE' and
is decoded by MG074DF format to describe which sets of
variables are populated:
0='0:DMA COUNTERS'
1='1:ETHERNET INTERFACE'
2='2:WORK UNITS'
However, records with SMF749DL=16 do not contain R749DFMT
so R749DFMT will be missing, causing all of these sets of
variables to have missing values:
0: R749DMAR R749DMAW R749DBYR R749DBYT R749DPKR
1: R749DBYR R749DBYT R749DPKR R749DPKT
2: R749DWUP R749DWUM
SMF749DL=40 is required for PCIE Function Type Data to
actually exist.
-Aug 17: INVALID type 30 zEDC segments (SMF30USO points
to the middle of the EXCP Section, or points beyond the
end of the record) were just confirmed by IBM support,
and occur because the SMF30USN count is not being reset
to zero in the "Continuation", MXG MULTIDD='Y' records.
The MXG Logic now only inputs the SMF30USO segment when
MULTIDD=' ', i.e., only for the base/original record.
Aug 25: IBM APAR OA48717 will correct the invalid zEDC
triplet information in the TYPE30 record.
-Aug 20: zEDC Compression Ratios for Inflate/Deflate are
created and kept in all TYPE30 datasets.
-Aug 30: zEDC Compression Ratios for Inflate/Deflate are
created and kept in TYPE749 datasets.
Thanks to Joseph J. Faska, DTCC, USA.
Change 33.184 Support for SYNCSORT Release 1.4 (INCOMPATIBLE). Change
VMACSYNC 33.102A added support for Release 2.1, which has the same
Aug 11, 2015 SMF data, so this change now tests SYNCVAL GE 1.4 to now
populate READTIME and many other variables that are wrong
without this change.
Thanks to Joseph J. Faska, DTCC, USA.
Change 33.183 Support for MAR Hitachi Command Suite Mainframe Analytics
EXMAR01 Recorder, user SMF records creates these dataset:
EXMAR02
EXMAR03 DDDDDD MXG MXG
EXMAR04 DATASET DATASET DATASET
EXMAR05 SUFFIX NAME LABEL
EXMAR06
IMACMAR MAR01 MARST01 LOST SMF INFORMATION
TYPEMAR MAR02 MARST02 LDEV INFORMATION
TYPSMAR MAR03 MARST03 MPB INFORMATION
VMACMAR MAR04 MARST04 PRGP INFORMATION
VMXGINIT MAR05 MARST05 PORT INFORMATION
Aug 11, 2015 MAR06 MARST06 MP USAGE TO TWENTY
Change 33.182 -Major enhancement for character data filtering for ASI
ADOCRMFV RMF Monitor III table entries and other improvements.
ASMRMFV -These filters are intended for building ad hoc MXG RMF
Aug 1, 2015 III PDBs for studies avoiding the overhead of generating
a full ASI table based PDB. They control which ASI table
entries are output to the RMFBSAM file.
-10 new filters are added to support ASI entry selection
from this table to the RMFBSAM output file. These
filters are effective only if the ASI table is selected.
They are applied in the order shown when multiple
different keywords are used.
New Keyword Aliases
------------ --------------------------------------
ASISUBSYS= ASISUB= TYPETASK=
ASIWORKLOAD= ASIWKLD= ASIWNM= ASIWL=
ASIRESGROUP= ASIRESGRP= ASIGNM= ASIRG=
ASISRVCLASS= ASISCLASS= ASICNM= ASISC=
ASIRPTCLASS= ASIRCLASS= ASIRNM= ASIRC=
ASIJOBCLASS= ASIJCLAS= ASICLASS= ASIJC=
ASIJOBNAME= ASIJOBNA= ASIJOBNM= ASIJOB= ASIJN=
ASIJESID= ASIJESNO= ASIJESNUM= ASIJESNR= ASIJID=
ASIAND None
ASIOR None
-TUTORIAL:
Ranges of the form keyword=first:last may be used with
any of the above keywords except ASIAND and ASIOR. The
colon character ':' is required for a range
specification.
However, single values may be specified for a range
simply as keyword=first and in this case the colon ':'
can be omitted.
All ASI entries GE the first value and LE the last value
are selected for output to the RMFBSAM file. Ranges may
not be wild carded only patterns. The first value in a
range may not be GT the last value or an error is noted.
Patterns may also be used with any of the above keywords
except ASIAND and ASIOR and include one or more wild card
characters to match the respective ASI data field.
Wild
Card Matches
---- -------------------------------------------------
* 0 or more characters
% 1 Non-blank character
+ 1 Numeric character (0-9)
_ 1 Alphabetic character or _ (a-z, A-Z, _)
. 1 National character (@, #, $)
! 1 Special character (not a-z, A-Z, 0-9, @, #, $)
? A blank string if used by itself
? 1 Blank character (X'40') if used with any other
characters
See Section 25 in the ADOCRMFV member for more details on
usage of ranges and patterns.
-ASISUBSYS= selects ASI entries by host Subsystem Name:
APPC, JOB, OMVS, STC, TSU, UNKN.
More than one subsystem may be requested. Ranges and/or
patterns may also be used, but are generally unnecessary
given the limited possible choices. Only those IBM
subsystems defined in the ASI table are supported.
Subsystem names are validated. The default is
ASISUBSYS=ALL.
For ease in coding and recall there are several value
aliases allowed with ASISUBSYS=.
Subsystem
Name Supported Values
--------- -----------------------------------------
APPC A, AP, APP, APPC, AS, ASC, ASCH
JOB J, JO, JOB, JOBS, B, BA, BAT, BATC, BATCH
OMVS O, OM, OMV, OMVS
STC S, ST, STC, STA, STAS, STASK, STASKS
TSU T, TS, TSO, TSU, TSUS
UNKN U, UN, UNK, UNKN, UNKNO, UNKNOW, UNKNOWN,
UNKNOWNS
-Examples for ASISUBSYS=
ASISUBSYS=JOB selects only Batch jobs.
ASISUBSYS=J:S selects Batch jobs, OMVS address spaces,
and Started Tasks because these all fall into the range.
ASISUBSYS=JOB ASISUBSYS=TSO selects Batch job and
TSO user address spaces.
-ASIWORKLOAD= selects ASI entries by 8 character WLM
Workload Name. Both ranges and patterns with wild card
characters may be specified. Up to 64 ranges and 64
patterns are supported. The default is ASIWORKLOAD=ALL.
-Examples for ASIWORKLOAD=
ASIWL=PROD:TEST selects all WLM Workloads GE 'PROD' and
LE 'TEST' using a range. Note use of keyword alias
ASIWL.
ASIWORKLOAD=PROD* selects only address spaces with a WLM
Workload Name that begins with 'PROD' as a pattern.
ASIWORKLOAD=TEST+++ selects only address spaces with a
WLM Workload Name that begins with 'TEST' followed by 3
digits as a pattern.
ASIWORKLOAD=? selects only address spaces with a blank
WLM Workload Name as a pattern.
ASIWORKLOAD=%* selects only address spaces with a
non-blank WLM Workload Name as a pattern.
-ASIRESGROUP= selects ASI entries by 8 character WLM
Resource Group Name. Both ranges and patterns with wild
card characters may be specified. Up to 32 ranges and 32
patterns are supported. The default is ASIRESGROUP=ALL.
-Examples for ASIRESGROUP=
ASIRG=CAP10:CAP20 selects all WLM Resource Groups GE
'CAP10' and LE 'CAP20' as a range. Note use of keyword
alias ASIRG.
ASIRESGROUP=CAP__ selects only address spaces with a WLM
Resource Group Name that begins with 'CAP' followed by 2
alphabetic characters as a pattern.
ASIRESGROUP=CAP%%% selects only address spaces with a WLM
Resource Group Name that begins with 'CAP' followed by 3
characters as a pattern
ASIRESGROUP=? selects only address spaces with a blank
WLM Resource Group Name as a pattern.
ASIRESGROUP=%* selects only address spaces with a
non-blank WLM Resource Group Name as a pattern.
-ASISRVCLASS= selects ASI entries by 8 character WLM
Service Class Name. Both ranges and patterns with wild
cards may be specified. Up to 64 ranges and 64 patterns
are supported. The default is ASISRVCLASS=ALL.
-Examples for ASISRVCLASS=
ASISC=BATHIGH:BATLOW selects all WLM Service Classes GE
'BATHIGH' and LE 'BATLOW' as a range. Note the use of
keyword alias ASISC.
ASISRVCLASS=*HIGH selects only address spaces with a WLM
Service Class Name that ends with 'HIGH' as a pattern.
ASISRVCLASS=*+* selects only address spaces with a WLM
Service Class Name that contain only one numeric
character as a pattern.
ASISRVCLASS=? selects only address spaces with a blank
WLM Service Class Name as a pattern.
ASISRVCLASS=%* selects only address spaces with a
non-blank WLM Service Class Name as a pattern.
-ASIRPTCLASS= selects ASI entries by 8 character WLM
Report Class Name. Both ranges and patterns with wild
cards may be specified. Up to 64 ranges and 64 patterns
are supported. The default is ASIRPTCLASS=ALL.
-Examples for ASIRPTCLASS=
ASIRC=DB2:TSO selects all WLM Report Classes GE 'DB2' and
LE 'TSO' as a range. Note the use of keyword alias
ASIRC.
ASIRPTCLASS=LOW.%%% selects only address spaces with a
WLM Report Class Name that begins with with 'LOW',
followed by a national character, and then followed by 3
more characters as a pattern.
ASIRPTCLASS=MED++* selects only address spaces with a WLM
Report Class Name that begins with 'MED', followed by 2
digits, and then possibly other characters as a pattern.
ASIRPTCLASS=? selects only address spaces with a blank
WLM Report Class Name as a pattern.
ASIRPTCLASS=%* selects only address spaces with a
non-blank WLM Report Class Name as a pattern.
-ASIJOBCLASS= selects ASI entries by JES Job Class.
Both ranges and patterns with wild cards may be
specified. Up to 32 ranges and 32 patterns are
supported. The default is ASIJOBCLASS=ALL.
-Examples for ASIJOBCLASS=
ASIJC=A:D selects only address spaces with a JES Job
Class of A, B, C, or D as a range. Note use of the
keyword alias ASIJC.
ASIJOBCLASS=+ selects only address spaces with a numeric
JES Job Class of 0-9 as a pattern.
ASIJOBCLASS=? selects only address spaces with a blank
JES Job Class as a pattern.
ASIJOBCLASS=%* selects only address spaces with a
non-blank JES Job Class as a pattern.
-ASIJOBNAME= selects ASI entries by 8 character z/OS Job
Name. Job Name characters are validated to those allowed
by JCL syntax. Both ranges and patterns with wild cards
may be specified. Up to 64 ranges and 64 patterns are
supported. The default is ASIJOBNAME=ALL.
-Examples for ASIJOBNAME=
ASIJN=PROD1234:PROD5678 selects only address spaces with
a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a
range. Note use of the keyword alias ASIJN.
ASIJOBNAME=.* selects only address spaces with a Job Name
that begins with a national character as a pattern.
ASIJOBNAME=*++ selects only address spaces with a Job
Name that ends with 2 numeric digits as a pattern.
-ASIJESID= selects ASI entries by 8 character JES Job
Identification. Both ranges and patterns with wild cards
may be specified. Since a JES Id is one character
followed by 7 digits or three characters followed by 5
digits not all pattern characters may be used with this
keyword. For convenience any leading zeros in the
numeric portion of the JES Id may be omitted and will be
filled in automatically. Up to 64 ranges and 64 patterns
are supported. The default is ASIJESID=ALL.
-Examples for ASIJESID=
ASIJID=J0000100:J0001123 selects all address spaces
with batch JES Id numbers GE 100 and LE 1123 as a
range. Note use of keyword alias ASIJID.
ASIJID=J100:J1123 selects the same address spaces as
above with the leading zeros omitted for coding
convenience.
ASIJESID=JOB12345:JOB32001 selects all address spaces
with batch JES Id numbers GE 12345 and LE 32001 for
installations with 5 digit JES Id numbers as a
range.
ASIJESID=J1* selects all batch address spaces with a
JES ID that begins with '1' as a pattern.
-ASIAND (default) indicates that selection results from
two or more different ASI filter keywords are logically
ANDed.
-ASIOR indicates that selection results from two or more
different ASI filter keywords are logically ORed.
-Examples of ASIAND/ASIOR:
With ASIAND in effect
ASISUBSYS=BATCH ASIJOBNAME=XYZ*
selects ONLY batch jobs whose those job names begin with
'XYZ'. ASIAND (default) provides more restrictive ASI
entry selection.
With ASIOR in effect
ASISUBSYS=BATCH ASIJOBNAME=XYZ*
selects ALL batch jobs OR any job names beginning with
'XYZ' even if they ran under another subsystem. ASIOR
provides less restrictive ASI entry selection.
-Selection results from repeats of the SAME ASI filter
keyword are always logically ORed.
-New parameter SYSAND (default) indicates that selection
results from the SYSPLEX= and SYSTEM= filter keywords for
the Data Set Header (DSH) table when both are specified
are logically ANDed.
-New parameter SYSOR indicates that selection results from
the SYSPLEX= and SYSTEM= filter keywords for the Data Set
Header (DSH) table when both are specified are logically
ORed. SYSOR must be coded when needed.
-Examples of SYSAND/SYSOR:
With SYSAND in effect
SYSPLEX=PROD SYSTEM=SYSP
selects ONLY RMF III data sets originating from the PROD
sysplex AND the SYSP LPAR. SYSAND (default) provides
more restrictive RMF III data set selection.
With SYSOR in effect
SYSPLEX=PROD SYSTEM=SYSP
selects ALL RMF III data sets originating from the PROD
sysplex OR any data sets for the SYSP LPAR even if SYSP
is part of a different Sysplex. SYSOR provides less
restrictive RMF III data set selection.
-Selection results for multiple SYSPLEX= values are always
logically ORed.
-Selection results for multiple SYSTEM= values are always
logically ORed.
-The '_' pattern character now matches lower case in
addition to upper case alphabetic characters in a source
string.
-The '_' pattern character will now match an underscore in
a source string. While this character is not technically
alphabetic, the underscore is sometimes used in some WLM
names for better legibility.
-A new pattern character '?' will allow selection of
completely blank source strings when used only by itself.
When '?' is used with other characters in a pattern a
single imbedded blank in a source string is matched.
-Example of ? pattern character:
ASIRPTCLASS=? selects all ASI entries that do not have a
WLM Report Class assigned or that could not be found by
ASMRMFV. That field in the ASI entry must be completely
blank to select that entry.
-A new pattern character '!' will match special characters
in a source string. For this purpose special characters
are those bytes in the EBCDIC code table that are NOT
alphabetic (a-z, A-Z), numeric (0-9), national (@,#,$),
or blank (X'40') and have been assigned to a character.
-Example of ! pattern character:
X'5C' is assigned the EBCDIC asterisk '*' and would match
the ! pattern character. However, X'00' does not match
this pattern character because no EBCDIC character is
assigned to this byte.
ASIJOBNAME=!MASTER! selects the *MASTER* address space.
Coding ASIJOBNAME=*MASTER* in this case instead may
produce different results because the '*' is a pattern
character itself representing zero to many characters.
So any job name with 'MASTER' imbedded would be selected.
-Section 5 "Input Data Selection Parameters" is updated
with discussion of all the new ASI selection keywords and
aliases.
-A new Section 25 "Ranges and Patterns" has been added to
the documentation to explain use of these features in
detail.
-A new Section 26 "Summary" is added to replace the old
Section 25 and includes a summary of the new ASI keywords
and all pattern characters.
-New parameter SHOWALL (alias SA) indicates that the
settings for all possible filter keywords that take range
and/or pattern values are to be displayed in the ASMRMFV
log in message RMFV006I even when no filters have
actually been specified for a particular keyword. These
display as keyword=ALL.
-New parameter NOSHOWALL (alias NOSA) indicates that only
filter keywords that have actual range and/or pattern
values specified are to be displayed in the ASMRMFV log
in message RMFV006I. This option helps reduce the size
of the ASMRMFV log. NOSHOWALL is the default.
-Section 6 "Report Control Parameters" is updated to add
SHOWALL/NOSHOWALL parameters.
-Several messages are slightly changed either to
accommodate longer ASMRMFV keywords for the ASI filter
selection or to display their settings.
Change 33.181 Enhancement for RMFINTRV/TRNDRMFI to ADD variables to be
VMXGRMFI kept. While the existing VMXGRMFI program provides many
Jul 30, 2015 arguments (R70ID, R70MAX, R70SUM, etc) that can be used
in your tailored %VMXGRMFI call, those arguments require
you to list ALL of the variables to be kept. This change
adds the ADD70ID=, ADD70MAX=, etc., arguments that only
list the variables to be added.
Thanks to Joachim Sarkoschitz, DATEV, GERMANY.
Change 33.180 Support for MQ Version 8 subtype 215 record which creates
VMAC115 DDDDDD DATASET DESCRIPTION
VMXGINIT TY115X TY115215 TYPE 115 ST 215 BUFFER STATS
Jul 30, 2015 -New variables QPSTFLAG0 and QPSTFLAG1 added to TY115215
and MQMBUFER datasets.
Change 33.179 -z13 in SMT Mode could have blank LPARNAME in TYPE70EN and
VMAC7072 MXG variable SMF70MTTT (misnamed, IBM field is SMF70MTIT)
Jul 29, 2015 is now deaccumulated in PDB.TYPE70EN.
Aug 4, 2015 -For SMT Mode, for complete detail per-engine data, use
the PDB.TYPE70EN dataset instead of PDB.TYPE70.
-This change also populated SMF70WTI/WTS/WTU in TYPE70PR
with zeros or real values that were previously missing.
-Aug 4. Corrected SORT error due to delete with TYPE7072.
Change 33.178 Many of the ANAL* members in JCLPDB9 were old (some had
JCLPDB9 not been touched in decades) or archaic and in some cases
Jul 29, 2015 had been replaced by more robust and up to date members.
These are ONLY included as examples; it is NOT likely
that you would execute ALL of these example ANALxxxx
reports in your production BUILDPDB.
ANALCONT - replaced by VMXGPRAL
ANALMPL - replaced by ANALINIT
ANALTURN - replaced by ANALINIT
ANALAVAL - removed since successful execution requires
user tailoring
ANALESV - obsolete
GRAFWRKX - added
GRAFCEC - added
All report members now have comments describing them
Commented ODS statement added to route output to PDF
Change 33.177 -A new parameter PRINT was added. A value of ALL/DETAIL
ANALRANK generates a report for each of the variable named in the
ANALPROG VARS parameter, and a summary report with the rankings
Jul 28, 2015 of ALL variables is produced.
A value of DETAIL generates only the individual named
variable report.
A value of SUMMARY only generates the summary report.
SUMMARY is assumed if PRINT is left blank.
-A third example generates a report similar to ANALPROG.
Change 33.176 Unused Change.
Change 33.175 Support for IHDRBBMQ "Infile Header Exit" for TYPEBBMQ
IHDRBBMQ and associated macro variable &MACBBMH permits selection
VMACBBMQ of data to be output after the BBMQ Header has been read.
VMXGINIT
Jul 27, 2015
Change 33.174 The number of IFL processors in an LPAR was incorrectly
VMXG70PR set to the number of IFLS on the CEC and IFL busy was
Jul 21, 2015 also incorrect since it was based on the CEC not on the
LPAR.
Change 33.173 For the z13, SM1132SP was forced because the value in the
ASUM113 z13 SMF 113 records is not correct, but SM1132SP=5000 is
VMAC113 the correct value, not 5. This impacted only EFFGHZ and
Jul 22, 2015 LPARBUSY values.
Thanks to David Cogar, Wells Fargo, USA.
====== Changes thru 33.172 were in MXG 33.07 dated Jul 22, 2015=========
Change 33.172 -If you specified USERADDS=NOUSERID and IDs over 128 were
ANALID found, an EOF test that built the macro variable that was
Jul 22, 2015 used in UTILBLDP was never executed.
-A superfluous RETURN; caused an error if you specified
SMFAUDIT=NO.
Change 33.171 MXGLOG code failed to wrap a PUT with a DO group, causing
VMAC120 potentially MANY of these log messages to be printed"
Jul 20, 2015 ***SMF 120 SUBTYPE 9 UNEXPECTED MULTIPLE SEGMENT.
_N_=2 SYSTEM=XX SMFTIME=19JUL2015:00:04:54.20 SM1209AK=1
Thanks to Jim Horne, Lowe's, USA.
====== Changes thru 33.170 were in MXG 33.07 dated Jul 17, 2015=========
Change 33.170 The test to identify IPV6 IP address was incorrect.
VMACCTCP
Jul 16, 2015
Change 33.169 The z13 protection for zero divide for TLB1CYCL,PTEPCTMI,
ASUM113 TLB1MSRT still used the zEC12 EXTND133+EXTND140 values
Jul 16, 2015 but the z13 changed the divisor to EXTND129+EXTND134,
which should have been also been used for the zero test.
Luckily, the incorrect test was non-zero so the correct
values were calculated.
Thanks to David Cogar, Wells Fargo, USA.
Change 33.168 The SMF 30 INSTRUCTION count variables require HIS to be
VMAC30 enabled, or all _INST counters will be missing values.
Jul 15, 2015 These two new variables are now created to identify why.
SMF30_INSTCAPTDISRUPTION='NO*INSTRUCTION*COUNTERS'
SMF30_INCOMPLETE_DATA='INSTRUCTION*COUNTERS*INCOMPLETE'
From Bob Rodgers SHARE 2014 SYSPROG Goody Bag notes:
- To get instruction counts in Counter Data Section,
HIS must activate the CPU Measurement Facility to
collect at least the basic counter set.
- MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B) is minimal
- MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B,E) is recommended
- SMFPRMxx must contain the keyword SMF30COUNT
Thanks to Alfred Holz, Express-Scripts, USA.
Change 33.167 MXGDB2B1 report checked for a macro variable that could
ANALDB2R only be defined if you are on SAS 9.4 or higher. A %LET
Jul 13, 2015 was added to instantiate the variable to protect ancient
versions.
Change 33.166 Support for Correlog z/OS Agent SMF User record created
EXTYCZA new dataset.
IMACCZA dddddd dataset Description
TYPECZA TYCZA TYPECZA Correlog z/OS AGENT
TYPSCZA
VMACCZA
VMXZGINIT
Jul 29, 2015
Change 33.165 Subtype 24 XPTR records decoded
VMACXPTR
Jul 9, 2015
Change 33.164 -If you specified READDB2 with IFCIDS=ALL and PDBOUT=WORK
READDB2 some IFCIds (22 and 217) that create multiple datasets
VMAC102 failed in their sort of those additional datasets looking
Jul 8, 2015 for a PDB LIBNAME. In addition if you specifically
requested (for example) IFCIDS=I22 it would fail looking
for _C102I22 since the code to create that dataset is in
_C102022. READDB2 now converts I22 to 22 U17 v17 T17 to
217.
-The _S102 "sort all 102s" macro now skips 202/225/230/239
and 369 because they are NOT 102s and instead are created
in 100.2, 100.4, 100.3, 101.1, and 100.5 ID/Subtypes.
Change 33.163 CICSTRAN variable PHSTARTM was incorrectly INPUT as PIB4
VMAC110 time of day, and PHSTARCN was input as a counter, but now
UTILEXCL PHSTARTM is INPUT TODSTAMP8, formatted DATETIME21.2, and
Jul 7, 2015 converted to local zone; PHSTARCN should never have been
created so it no longer is.
Thanks to David Shaw, M&T Bank, USA.
Thanks to Doug Donoho, M&T Bank, USA.
Change 33.162 "MXGLOG" option to send MXG Messages to MXGLOG filename.
VMXGINIT Macros %MXGLOGDO, %MXLOGPUT and MXLOGEND are defined in
VMACSMF VMXGINIT. If an //MXGLOG DD or FILENAME MXGLOG is used,
Jul 10, 2015 MXG will automatically enable and send MXG messages to
Jul 12, 2015 the MXGLOG file on z/OS; on ASCII you send those messages
Jul 14, 2015 to FILENAME MXGLOG 'c:\mxg\mxglog.txt'; but note that the
Nov 23, 2015 file is written with MOD, so you may need to clear the
file with DATA _NULL_; FILE MXGLOG;
Status: These members' messages are updated:
VMAC0 VMAC0203 VMAC10 VMAC113 VMAC115
VMAC116 VMAC120 VMAC21 VMAC22 VMAC23 VMAC26J2
VMAC30 VMAC42 VMAC6 VMAC6156 VMAC7 VMAC7072
VMAC71 VMAC73 VMAC74 VMAC75 VMAC76 VMAC77
VMAC78 VMAC89 VMAC8911 VMACDB2 VMACID VMACTMNT
VMACSMF VMXG70PR
These include all members in the default BUILDPDB.
The last change-date wasn't updated in these members, as
the changes did not impact the output datasets.
The syntax of the messages written to MXG log will be
MXGLOG::MXGtype.member.nnn
where type is INFO, WARNING or ERROR,
member is the member name that creates the message
nnn is a sequence number in that member name.
Thanks to MP Welch, Bank of America, USA.
Change 33.161 Support for MOBILEWRK to read BMC's IMF/CIMSTRAN FA IMS
MOBWRKI3 log records to create CIMSTRAN and use in MOBWRKI3, or
MOBWRKI4 to use existing CIMSTRAN dataset(s) in MOBWRKI4.
MOBILWRK Only comments updated in MOBILWRK.
Jul 6, 2015
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 33.160 Reserved Change Number, now Unused.
Change 33.159 Support for ANALID and VMXGSRCH to decompress DB2 or CICS
ANALID records, on z/OS when EXITCICS/CICSIFUE exit is not used,
DB2DECOM or on ASCII, where EXITCICS cannot be installed.
MXGDECOM -For ANALID, the DB2 Product section, containing IFCID and
SMFSRCH SUBTYPE and DB2 Version, is compressed, so those values
UTILBLDP are missing. Optional new SMFDECOMP=DB2 argument invokes
VMAC110 the MXG internal code to decompress 101 and 102 records
VMACDB2 so those values can be reported. (Not needed for CICS as
VMACSMF its version/subtype is the uncompressed area.)
VMXGINIT -For SMFSRCH, compressed CICS 110 and DB2 101/102 records
Jul 17, 2015 couldn't be searched. New SMFDECOMP=BOTH or DB2 or CICS
argument will invoke the MXG decompression code so those
records can be searched for the LOOKFOR text.
-WARNING: The internal Code decompression requires A LOT
more CPU time than the EXITCICS exit. A 5GB DB2 SMF file
required 34 CPU minutes with the internal algorithm, but
only 13.5 CPU minutes using EXITCICS. That is why YOU
must choose to enable the SMFDECOMP decompression.
-You can also force decompression of CICS and/or DB2 data
when only the _SMF (decode SMF header macro) is used:
%LET MXGDECOMP= BOTH or DB2 or CICS ;
%INCLUDE SOURCLIB(VMACSMF);
DATA; _SMF;
The decompressed record will be in variable _INFILE_.
-UTILBLDP is invoked by SMFSRCH to create all datasets in
the selected SMF records; testing exposed an incorrectly
built macro for type 102 when BUILDPDB=NO and the IFCID
was only 2 characters long.
-The decompression %MACROs MXGDECOM and DB2DECOM are now
defined in those members and the redundant definitions
in VMACSMF, VMAC110 and VMACDB2 are removed, since the
AUTOCALL facility will resolve them when referenced.
Change 33.158 Type 6 ESS zero length segment caused INPUT STATEMENT
IMAC6ESS EXCEEDED STOPOVER error condition when the segment was
Jul 3, 2015 the last ESS segment. GEPARMKY=0016x and 0027x have been
observed with zero segment length, which would seem to be
an IBM error (to be investigated with IBM Support) but
protection is added to prevent the STOPOVER error.
In testing this change with on-hand SMF 6 records from
other users four new ESS segments are now decoded:
ESSCKPTPAGE ESSOVERLAYB ESSOVERLAYF ESSDUPLEX
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH occurs if the online
VMACXAM engine count is changed, because XAM does NOT change the
Jul 1, 2015 value in SYTNLPS, which always contains the number of
INSTALLED engines (and the same is true of variable NCPUS
from the SUBSUM segment). This change recalculates the
number of engines into SYTNLPS based on SEGLEN, which XAM
does update, and which is then used to input the actual
online CP segments.
Thanks to Patricia Hansen, ADP, USA.
Thanks to Mike Chaves, ADP, USA.
Change 33.156 Support for APAR OA44525, zHPF Extended Distance II.
VMAC78 -New variables added to TYPE78CF dataset:
VMAC79 R783CTMW='TRANSPORT*MODE*WRITE*COUNT'
Jun 30, 2015 R783CTRD='1ST XFER*READY*DISABLED*WRITE COUNT'
R783TMWM='XPORT*WRITE*COUNT*DCM CHANNELS'
R783TRDM='1ST XFER*READ*DISABLED*DCM CHANNELS'
-New variables added to TYPE79EF dataset:
R79ECTRD='1ST XFER*READY*DISABLED*WRITE COUNT'
R79ETMWM='XPORT*WRITE*COUNT*DCM CHANNELS'
R79ETRDM='1ST XFER*READ*DISABLED*DCM CHANNELS'
PCTPTHBY='PERCENT*CHPID PATH*BUSY'
Change 33.155 -TYPE74ST dataset now has Storage Class Memory variables
VMAC74 that were incorrectly output in TYPE74MO dataset, which
Jul 5, 2015 should never have been created and no longer is.
Oct 4, 2015 -Text added Oct 4, 2015:
Variable R744SNAM=STRUCTURE NAME was added to TYPE74DU
and TYPE74HO datasets, but not noted in the change text,
nor was it added to the _BTY74HO BY List, but in Oct it
was observed that the addition of R744SNAM to TYPE74HO
caused a CORRECT INCREASE in number of observations in
PDB.TYPE74HO (even though the WORK.TYPE74HO had the same
number of observations). Because R744SNAM was not kept,
the previously NODUP sort was incorrectly removing obs
that were not duplicates, and its addition accidentally
prevented their removal. Change 33.234 now updates the
BY list to explicitly include R744SNAM.
-MXG Internal Note on no longer creating a dataset: The
macro variables PTY74MO/WTY74MO in VMXGINIT, and all
the _xTY74MO old-style macro tokens must still be
defined in VMAC74, just in case they were used in user
tailoring. Member EXTY74MO also must exist to protect
tailored code, and the_STY74MO token was removed from
_STY74 to prevent a dataset not found condition.
Thanks to Sandy Stromberg, OPTUM, USA.
Change 33.154 BY statement was missing on SGPLOT and GPLOT so title1
ANALCAPD had #BYVAL1 rather than the value of CECSER.
Jun 25, 2015
Change 33.153 IMF version 5100 record caused INPUT STATEMENT EXCEEDED
VMACCIMS ERROR due to MXG misalignment of the Trace Table that
Jun 24, 2015 caused TRNEXTEN=1 when it should have been zero.
Change 33.152 ANALWHO (WHO deleted/modified my Dataset) is revised to
ANALWHO check and see if any data was found and now confirms
Jun 24, 2015 in an MXGNOTE that observations were NOT found.
The REPORT data that is created is now deleted before
ending. JOB parameter is added to allow you to specify
a specific job name to seek.
Thanks to Dave Ireland, USDA, USA.
Change 33.151 ERROR.VMAC115.OFFQCCT. INVALID SECTION TRIPLET.
VMAC115 ERROR.VMAC116.LENQWHS. INVALID PRODUCT SECTION TRIPLET.
VMAC116 are corrected. Change 32.172 created new MQ V8.0
Jun 24, 2015 datasets MQCHIN and MQCHININ, but documented that the
Jun 30, 2015 code had not been tested with data. Now it has been.
-The MQCHIN 115 records ADP, SSL, and DSN segments are
significantly longer than documented and don't agree
with their contents in CSQDQCTA; this will be pursued
with IBM MQ Support.
-The MQCHININ 116 dataset is only output if there was
activity; that logic is in _ETY116A if you do want to
output all segments.
-Jun 30: WTASCTSR is now correctly aligned and non-zero.
Thanks to Robert Miles Standish, UBS, USA.
Thanks to Thomas Orlando, UBS, USA.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.150 Variable PCTDLZIP='ZIP*DELAY*PERCENT' is created in the
VMAC7072 TYPE72GO dataset.
Jun 22, 2015
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 33.149 Dataset TYPE115 variable QESDBFPT was not divided by
VMAC115 4096.
Jun 22, 2015
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.148 -SMFSRCH can't search for text in compressed DB2 or CICS
SMFSRCH SMF records unless the EXITCICS INFILE exit is installed
Jun 22, 2015 on z/OS.
-At present, on ASCII, SMFSRCH can not search compressed
records because the internal decompression algorithm is
executed AFTER the _INFILE_ has been populated. This is
under investigation for a possible solution.
-If SMFSRCH found type 102 records with an IFCID LT 100,
it incorrectly called UTILBLDP with a token of 102.83,
which should have been 102.083. Now fixed.
-SMFSRCH will now suppress processing of 102 records if a
subtype of 0 is found, since this means the data is
compressed, and you are not using the EXITCICS exit.
-If a subtype GE 8000 is found the subtype is then
converted to BMC.
CHANGE 33.147 Analysis of batch queue times using SMF30HQT SMF30JQT
ANALQBAT SMF30RQT and SMF30SQT variables rather than values that
Jun 20, 2015 are calculated as in ANALINIT. This is a member which
you need to tailor in your USERID.SOURCLIB. There are
changes you must make (look for CHANGE HERE in the
member.) It requires are least SAS 9.3 since it uses
ODS and creates PDF output.
Change 33.146 There are two SECID='0B'x SMF Type=22 records. RECIND=9
EXTY22PB records create the existing TYPE22_B with the I/O Config
IMAC22 changes. New TYPE22PB dataset is created from SECID='0B'x
VMAC22 that do not have RECIND=9, with Reconfigured PCIE.
VMXGINIT function identifiers.
Jun 19, 2015
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 33.145 BVIR VTS Grid dataset BVIR33 was incorrect for the second
VMACBVIR and subsequent Grid-Cluster Containers.
Jun 18, 2015 Variable TMDLYCPY is now kept in BVIR33, overlooked.
Jul 7, 2015 Variables MAXAHCT AVEAHCT MAXBHCT AVEBHCT are now kept in
BVIR20.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Thanks to Mike Creech, Black Knight Financial Services, USA.
Change 33.144 Support for SMF Type 119 new Subtypes 94 and 95 create
EXT11994 dddddd dataset description
EXT11995 T11994 TYP11994 SSH Client Connect Start
FORMATS T11995 TYP11995 SSHD Server Connect Start
IMAC119 The $MG110AM/CI/MA/CO formats were updated with new
VMAC119 values.
VMXGINIT
Jun 23, 2015
Thanks to Hyrum Smith, Schwab, USA.
Change 33.143 -INPUT STATEMENT EXCEEDED NDM-CDI PT RECORD, shortened by
VMACNDM 4 bytes, variable PTUNCH34 now $EBCDIC30 vs 34.
Jun 15, 2015 -Truncated fields for CT record - MXG Message is correct,
vendor contacted.
Change 33.142 Variable QWACATWT was missing the divide by 4096 and the
VMACDB2 variable QWACPQCT should have been input &PIB.4.
Jun 15, 2015
Thanks to Scott Barry, SBBWorks Inc., USA.
====== Changes thru 33.141 were in MXG 33.06 dated Jun 11, 2015=========
Change 33.141 Documentation only. The EXITCICS/CICSIFUE INFILE exit
EXITCICS WILL NOT work with VSAM SMF input, on SAS log shown as
Jun 11, 2015 DSNAME=SYS1.MAN1,
VOLUME=Z21SMF,DISP=SHR,UNIT=3390,
TYPE=NONINDEXED,SPANNED=YES,
RECORDSIZE=(.,32767),AMP=('AMORG'),RECORDS=0
Maybe the DSNAME=SYS1.MAN1 is a clue, but it is the AMP=
parameter that identifies the SMF file as a VSAM file.
The SAS log also reported:
MXGNOTE: SMF EXIT CICS IS IN USE.
ERROR: ERROR DETECTED BY INFILE/FILE EXIT: .
FATAL: UNRECOVERABLE I/O ERROR DETECTED IN THE
EXECUTION OF THE DATA STEP PROGRAM.
Thanks to Greg Meyer, ISUZU, USA.
Change 33.140 RMF III RCD records INCOMPATIBLY changed for z13 causing
VMACRMFV invalid values in SVCLCNM and other variables in RBRCDR.
Jun 11, 2015 The change apparently was RMF APAR OA44101 supporting
Jun 16, 2015 Simultaneous MultiThreading (SMT) on the IBM z13 server
that extended the Resource Collection Data Period Data
(RCDPD) array entries in the RMF Monitor III RCD table.
-Test IF RCDPLSC GE 0 corrected to IF RCDPLSC GT 0. When
RCDPLSC=0, there is no LC Service Class Extension. Have
NOT ACTUALLY seen RCDPLSC=0, so this is for safety and
not an actual error.
Thanks to Michael Kampert, Schwab, USA.
Change 33.139 Contributed Processor Topology Report for z13, using SMF
ANAL9914 Type 99 Subtype 14 records. Syntax for SYS1 report, Z13:
Jun 9, 2015 %ANAL9914(SYSTEM=SYS1,SYSTYPE=Z13)
Thanks to Raymond J. Smith, OPTUM, USA.
Change 33.138 -z13 in SMT Mode, TYPE70EN had missing or mis-aligned
VMAC7072 values when there was a second zIIP engine.
Jun 9, 2015 -z13 in SMT Mode, PCTMVSBY was incorrect by a few percent
Jun 11, 2015 because LPARBUSY time was incorrectly subtracted.
-z13 in SMT Mode zIIP variables in TYPE70xx datasets,
could be missing, or DUPLICATE RECORD message could be
printed. REQUIRED FOR SMT. The MXG SMT support has come
in several iterations as new sequences of data exposed
untested logic but this appears to finally resolve the
one-to-many merge. If you are testing SMT on z13, please
email MXG Support with subject: SMT UPDATES so we can
inform you if there are any further required changes for
SMT mode.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Thanks to Scott Wiig, US Bank, USA.
Thanks to Douglas C. Walter, CitiCorp, USA.
Thanks to Brent Turner, Citigroup, USA.
Change 33.137 Support for Compuware ABEND-AID USER SMF Record creates
FORMATS new ABENDAID dataset with many details on each intercept.
EXABNAID
IMACAA
TYPEAA
TYPSAA
VMACAA
VMXGINIT
Jun 5, 2015
Change 33.136 Support for MainView for IMS 5.2 (a/k/a IMF, CONTROL/IMS)
FORMATS for COMPATIBLE changes.
VMACCIMS -New variables added to CIMSTRAN:
Jun 3, 2015 TRNDLCMX='MAX*DC*CALL*TIME'
TRNDLDMX='MAX*DB*CALL*TIME'
TRNESSMX='MAX*ESS*CALL*TIME'
TRNDLWMX='MAX*WAIT*NOT-IO*TIME'
TRNDLDTH='DLI DB*OR*ESS CALLS*GE THRESHOLD'
TRNDLCTH='DLI*DC* GE*THRESHOLD'
TRNDLDER='DLI*CALL*ERRORS'
TRNESSER='ESS*CALL*ERRORS'
TRN1STCP='SCHD*FIRST*DLI*CPU'
-New values added to variables SMQFLAG, PROGTYPE
FLGSPCHR.
Change 33.135 Support for Optional CICS User CMODNAME=VMX CMODHEAD=VMX
IMACICVP segments.
IMACICVQ
IMACICVR
IMACICVT
IMACICVU
IMACAAAA
UTILEXCL
VMAC110
Jun 9, 2015
Change 33.134 -ANALDB2R mis-reported the number of reports produced
ANALDB2R when accounting reports were requested but no data met
READDB2 the selection criteria.
May 26, 2015 -READDB2 applied selection criteria inappropriately to
the 105 106 and 107 IFCIDS which are subsystem specific.
-ANALID parameter added to ANALDB2R to pass to READDB2 so
that you can see what records were in the input data.
-Page headings on PMSPR01 were incorrect for the first
page of the second and subsequent DB2 subsystems reports.
-If the input to PMLOL02 and PMLOK03 was a SAS dataset on
tape, the T102S172 dataset was missing from the PROC COPY
that moves the data to DASD (zOS only) since there must
be concurrent dataset open for these reports
Thanks to Judy Xu, WiPro, USA.
CHANGE 33.133 ZOSEM User SMF INPUT STATEMENT EXCEEDED because MXG had
VMACOSEM expected an 8-byte Resource field length. Since this
May 21, 2015 resource looks like it might be a DSNAME, the resource
array variables are expanded to 44 bytes.
Thanks to John Schoenbeck, IBM Global Services, USA.
CHANGE 33.132 These eight new TYPE30 variables with zEDC metrics were
VMAC30 misaligned because the triplet was incorrectly input:
May 21, 2015 SMF30_US_COMPRREQ SMF30_US_COMPRREQ_PROB
Jan 4, 2016 SMF30_US_QUEUETIME SMF30_US_EXECTIME
SMF30_US_DEF_UNCOMPRIN SMF30_US_DEF_COMPROUT
SMF30_US_INF_COMPRIN SMF30_US_INF_DECOMPROUT
These variables now also have "ZEDC" in their label.
-Jan 2016: APAR OA48268 corrects invalid values in the
first four variables above, especially when SMF data
is from logstream processed by IFASMFDL.
Thanks to Scott Barry, SBBWorks, Inc., USA.
CHANGE 33.131 -SMFSRCH failed if the SMF file contained only one USER
SMFSRCH record type and you had specified that nnn type value in
UTILBLDP your USERADD=XXXX/nnn argument. The USERADD= erroneously
May 22, 2015 had nnn which generated a call to INCLUDE VMACnnn.
May 25, 2015 -SMFSRCH now invokes %ANALID report to tabulate the SMF
records, subtypes, versions, etc., that were selected;
any undefined user records selected are identified.
-SMFSRCH LOOKFOR= supports multiple strings with ANDOR
choice, and new SELECTION= argument lets you write your
own IF statement for the selection.
-UTILBLDP needed revision to delete the ID VIEW that was
introduced with the addition of %ANALID. If ID is found
in a non-BUILDPDB context the _SID sort is suppressed and
the ID VIEW is deleted.
-ASCII only, SMFSRCH. LENGTH from INFILE statement is now
used in place of LENGTH=LENGTH(_INFILE_) for the written
length, after an SMF 79 record with a blank last byte was
truncated, and detected by an MXG ERROR message, causing
the SAS documentation TO BE READ, that stated that the
LENGTH() function returns the length of the string, but
EXCLUDING any trailing blanks.
Thanks to Mike Obrien, Bank of America, USA.
CHANGE 33.130 Missing values in SMF70xxx variables in PDB.ASUM1131 and
ASUM113 (now archaic PDB.ASUM113 from no longer supported subtype
May 20, 2015 2 Type 113s) if the SMF SYSTEM variable in Type 70 does
not match SMF70STN in the PR/SM LCPUADDR segments. This
logic has been used since always to read from TYPE70PR
IF SYSTEM=SMF70STN;
SYSTEM=SYSNAME; (IBM SMF70SNM - From IEASYSXX)
to use the SYSNAME for the merge with TYPE113.
In this new data with SYSTEM NOT matching SMF70STN, it
was observed that SMF70STN matched SYSNAME, but now, the
original SYSTEM is unchanged:
IF SYSTEM=SMF70STN OR SYSNAME=SMF70STN;
IF SYSTEM=SMF70STN THEN SYSTEM=SYSNAME;
/* ELSE LEAVE THE SMF 70 ORIGINAL SYSTEM FOR MATCH */
-Do not use Subtype 2 SMF 113 with accumulated data; they
may not always match up with 70PR because 113 data is
lost. Always use Subtype 1 INTERVAL HIS data. IBM has
stated they will NOT update Subtype 2 records.
Thanks to Virginie Peigney, CA-SILCA, FRANCE.
CHANGE 33.129 Support for TMS new TRTCH values for Device Type TS1140,
VMACTMS5 EE4/EE4M/EE4X and EF4/EF4M/EF4X.
May 20, 2015
Thanks to Scott Barry, SBBWorks, Inc., USA.
====== Changes thru 33.128 were in MXG 33.05 dated May 19, 2015=========
CHANGE 33.128 z13 with one or more LPARs enabled for SMT-mode will have
VMAC7072 zero observations in the TYPE70 dataset from all NON-SMT
May 19, 2015 mode systems, UNLESS, ACCIDENTALLY, the SMT-mode systems
are all at the end of your input SMF file. The SMTSEGNR
variable that identifies this is an SMT-mode record was
incorrectly retained.
Thanks to Scott Wiig, US Bank, USA.
CHANGE 33.127 Dataset TYPE749 zEDC PCIE and Hardware Accelerator FIXED.
VMAC74 Change 33.124 replaced with logic to match all segments.
May 18, 2015 This change is required for valid TYPE749 data.
May 22, 2015 May 22: STD and AVG variables created for Queue/Execute
durations, which are now formatted TIME16.6.
Thanks to David Cogar, Wells Fargo, USA.
Thanks to Carl D. Ellis, Wells Fargo, USA.
CHANGE 33.126 APPTUNE SMF 102 INPUT STATEMENT EXCEEDED if DATA SHARING
VMACDB2H (32) header is present. The product section for APPTUNE
May 19, 2015 records is not at the end of the SMF 102 but instead is
at the beginning of the record. Change 32.148 revised the
header input logic, to support unexpected out-of-order
headers, but the LENLEFT calculations used record LENGTH.
Now for APPTUNE 102s (QWHSIID GE 8000x), the ENDPROD is
used to determine the LENLEFT for all header segments.
Thanks to Jan Tielemans, KBC, BELGIUM.
CHANGE 33.125 Further SMT-related changes.
VMAC7072 -CPUWAITM now subtracts LPARBUSY from CPUWAITM for zIIPs.
May 16, 2015 earlier code had the subtraction for CPs, with no impact.
-SMF70CAN/SMF70CTN variables are again kept in TYPE70PR.
Thanks to Jim Horne, Lowe's, USA.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
====== Changes thru 33.124 were in MXG 33.05 dated May 12, 2015=========
CHANGE 33.124 MXG support for 74-9 zEDC was revised again, when it was
VMAC74 discovered that only the first card was output, and that
May 13, 2015 the number of PCIE pairings of the PO/DO segments is not
May 18, 2015 the same as the number of Hardware Accelerator FO/10
segments. Original change text here removed, See 33.127.
-Variable R749LAID was removed; there is no adapter id.
-These new variables were added from the DO segments
R749DBYR R749DBYT R749DFMT R749DPKR R749DPKT
R749DWUP R749DWUM
-May 18: See Change 33.127, which is REQUIRED.
Thanks to David Cogar, Wells Fargo, USA.
Thanks to Scott Barry, SBBWorks, Inc., USA.
====== Changes thru 33.123 were in MXG 33.05 dated May 12, 2015=========
CHANGE 33.123 Support for Tandem ZMS Style of records; the previous MXG
VMACTANZ support was for what are now "Legacy Style" records.
May 12, 2015
Thanks to Mark Goforth, First National of Nebraska, USA.
CHANGE 33.122 Reserved Change.
CHANGE 33.121 z13 SMT-mode TYPE70/PR data IS WRONG in MXG 33.03-33.04.
VMAC7072 In ONLY RMF 70 records written in SMT-mode, the datasets
May 12, 2015 TYPE70, TYPE70PR, RMFINTRV, ASUM70PR, ASUM70LP, ASUMCEC,
and ASUM70PR can have incorrect values. MXG 33.03 support
for z13 SMT-mode records continued to use LCPUADDR from
the PHYSICAL to merge with CPUID in the CPUD segment and
the results matched initial RMF reports, but now I find
that the LCPUADDR won't always match the CPUID value!
And, one mismatch destroys the merge, trashing both the
TYPE70 and TYPE70PR datasets.
The code had to be redesigned to sort and merge on the
physical sequence to pair up the two segments to create
the per-LCPUADDR TYPE70PR dataset and populate TYPE70.
IBM RMF Support confirmed that "LCPUADDR/SMF70VPA in the
PHYSICAL segment is retrieved from the Diag 204 interface
and is generated by the hardware/firmware when the core
is brought into the configuration. It does not match the
logical core id in SMF70VPA which is provided by z/OS in
the PR/SM logical processor data section(s) of the home
partition"
The example had an LCPUADDR=7 in PHYSICAL for a zIIP, but
there was no corresponding CPUID=7 in the CPUD segment.
I was also confused when a box with 5 CP cores and 5 zIIP
cores in PHYSICAL had SIX unique CORE_IDs, but that was
because the home partition had 4 logical CP cores and 2
logical zIIP cores, which results in the 8 CPU data
sections, with 6 unique CORE_IDs.
CHANGE 33.120 New member IHDR120 for the SMF TYPE=120 WebSphere record
IHDR120 in %INCLUDEd after the header and Product segments have
VMAC120 been INPUT, and the "instream" macro variable MAC120H is
VMXGINIT defined so that you can select/tailor after those header
May 6, 2015 variables have been input.
CHANGE 33.119 The optional IMACICMX member for Omegamon with CMRDATA of
IMACICMX length 384 was missing a final END; statement, causing a
May 6, 2015 syntax error if UTILEXCL told you to tailor IMACICMX.
CHANGE 33.118 -The RESULTS window now lists the report number and short
SAGANAL title for all reports produced by PROCs that support the
May 7, 2015 CONTENTS= option to label the result. (Procs FREQ, MEANS,
and CONTENTS do not support that feature.)
-Report 31 added with top ten MSU hours for CICS DFHSIP.
-Number of variables kept reduced to 68 from 1533; syntax
CPU: and CPI: for TYPE30 kept TYPE70PR CPU: variables.
CHANGE 33.117 -MXG 33.04. SMFSRCH found no records if USERADDS= was not
SMFSRCH specified. Logic added for USERADDS=NOUSERID was wrong.
UTILBLDP Logic corrected, but USERADDS=XXXX/nnnn (even if _IDXXXX
May 6, 2015 is already defined in IMACKEEP) will circumvent.
-It was also possible to skip all user record selection
due to an ENDOFFILE test that is removed.
-The TYPE30_D dataset (each DD in SMF 30) is not populated
by MXG default, and although the only text is the DDNAME,
since SMFSRCH is to find and print all SMF records found,
new TY30UD argument is defined in UTILBLDP (default is
blank), and TY30UD=YES default is set in SMFSRCH, so that
dataset TYPE30_D will be populated if type 30 records are
selected, or you can use TY30UD=NO in your SMFSRCH call
to prevent any observations to be created in TYPE30_D.
-ECHO=YES specified in SMFSRCH to always print the MXG
created by UTILBLDP on the log.
-In testing, an exposure was observed: multiple uses of
the file INSTREAM caused text to be overridden, which did
not cause an error, but some sites have made INSTREAM to
be a permanent dataset, and this exposure could lead to
errors for those sites.
The //INSTREAM DD was intended to be temporary and used
internally as the destination for writing SAS code that
is then executed with %INCLUDE INSTREAM. These members
no longer use INSTREAM; instead, each writes/reads from
FILENAME TMXGxxxx CATALOG 'WORK.MXGTEMP.TMXGxxxx.LOG';
in the WORK file so no DD is required, and no conflict!
A few members (notably UTILBLDP) do externalize INSTREAM,
and they were not changed.
ANALCOMP VMXGPRAL VMXGPRNT QAWPS8 QA94648 SAGANAL
PRINTLOG ONLYJOBS ASUMMSUS ANALRRTM ANALPGM ANALCOMP
Thanks to MP Welch, Bank of America, USA.
CHANGE 33.116 Support for ZCOST AutoSoftCapping Version V3.0.00 adds
EXZCO02S subtypes and data. These are the datasets MXG creates:
EXZCO02W DDDDDD Dataset Description
EXZCO04C ZCO01 ZCOS01 ZCOST CPC
EXZCO04G ZCO02 ZCOS02 ZCOST LPAR
EXZCO04L ZCO02S ZCOS02S ZCOST SERVICE CLASS PERIOD
EXZCO04P ZCO02W ZCOS02W ZCOST WLM INPORTANCE
EXZCO04R ZCO03 ZCOS03 ZCOST SYSPLEX/CPC
VMACZCOS ZCO04G ZCOS04GP ZCOST GENERAL PARMS
VMXGINIT ZCO04C ZCOS04CP ZCOST CPC PARMS
May 5, 2015 ZCO04L ZCOS04LP ZCOST LPAR PARMS
May 28, 2015 ZCO04P ZCOS04PG ZCOST GENERAL PERIOD PARMS
ZCO04R ZCOS04PL ZCOST LPAR PERIOD PARMS
This support was completed in MXG 33.06.
CHANGE 33.115 Mainview for MQ BBMQBUFF dataset EFFICIENCY variables are
VMACBBMQ now correctly input as RB4 instead of PIB. Variables are
Apr 29, 2015 SBPIAWPE SPBRAWPE SBPSAWPE.
CHANGE 33.114 BMC IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN;
VMACCIMS it was incorrectly in the CIMSDBDS dataset KEEP=list.
Apr 29, 2015 "zAAP" in Label changed to 'ZIP' (Feb 2006):
CPUZIPTM='CPU TIME*ON ZIP*ENGINES'
TRXZAOCP='CPU TIME*ZIP ELIGIBLE*RAN ON CP'
Thanks to Betty Wong, Bank of America, USA.
CHANGE 33.113 Some T102S106 variables (DB2 zPARM flags and values) were
FORMATS misaligned, not INPUT, or had wrong/no decoding format.
VMAC102 Align: QWP2DMIN,QWP2DSEC
Apr 30, 2015 Format: Use $MGD361U for QWP4SECA1_TYPE, QWP4SECA2_TYPE
Format: New $MGD106P for QWPBDL, QWPBSDL
Input: QWP4S1IL for DB2 V10, was only V11 and wrong.
Thanks to Lai Fai, Bank of America, USA.
====== Changes thru 33.112 were in MXG 33.04 dated Apr 29, 2015=========
CHANGE 33.112 -Support for CICS/TS 5.3 OPEN BETA (INCOMPATIBLE) AND:
UTILEXCL NOTE THAT 5.3 now sets STGPROT=YES as the IBM DEFAULT, to
VMAC110 INTENTIONALLY cause an ABEND for storage overlays caused
Apr 29, 2015 by dubious programming techniques where a task has
May 1, 2015 modified storage owned by another task. These ABENDs
will need application programmer design changes; the APP
should have been fixed long ago - IBM is looking forward!
-New variables (INCOMPATIBLE) inserted in CICSTRAN dataset
NCGETCN ='NAMED*COUNTER*SERVER*REQUESTS'
TSGETSCN='SHARED*TEMP*STORAGE*GETS'
TSPUTSCN='SHARED*TEMP*STORAGE*PUTS'
May 1: Original Note wrong here, NO ERROR in TSTOTCN.
-New variables inserted in CICSRDQU dataset (MNSEGCL=5):
TSQGESTM='SHARED*TSQUEUE*GET*TIME'
TSQGESCN='SHARED*TSQUEUE*GET*COUNT'
TSQPUSTM='SHARED*TSQUEUE*PUT*TIME'
TSQPUSCN='SHARED*TSQUEUE*PUT*COUNT'
TSQGESBY='SHARED*TSQUEUE*GET*BYTES'
TSQPUSBY='SHARED*TSQUEUE*PUT*BYTES'
-"WRITING OF PERFORMANCE DATA IS MORE EFFICIENT WHEN
FIELDS ARE NOT EXCLUDED." was noted in a comment.
CHANGE 33.111 -The ANALID report that tabulates SMF record types is
ANALID enhanced to optionally invoke %UTILBLDP to create MXG
SMFSRCH code to build all possible MXG datasets from ALL records
UTILBLDP in the input SMF file, and to optionally run the program,
VMXGPRAL -This change originally documented macro variables UTILBLD
VMXGINIT VMXGPRA but they were removed in Change 33.117, unused.
Apr 27, 2015 -VMXGPRAL revised to print the LIB.DSNAME + LABEL without
May 27, 2015. extra blanks and periods.
Thanks to MP Welch, Bank of America, USA.
CHANGE 33.110 -Support for TS7700 HYDRA Version 3.2A (COMPATIBLE)
EXBVR302 creates new BVIR302 dataset with the Extended HSM Cache
FORMATS Partition Container Statistics from subtype 30 record.
IMACBVIR -Variables added to BVIR01 dataset:
VMACBVIR THRUPUT AHEADCNT BEHNDCNT
VMXGINIT -Changed records have BVIRVERS=6.
Apr 24, 2015
Thanks to Tim Campbell, TELUS, CANADA.
CHANGE 33.109 -Support for TYPE 23 zEDC variables SMF23BBC/SMF23BAC has
VMAC23 been corrected and validated. Those two variables plus
Apr 23, 2015 SMF23PFT SMF23PFM SMF23PFH SMF23CWN SMF23NCN are now
correctly aligned and are now output in dataset TYPE23LS
and removed from dataset TYPE23.
-Two new fields were documented in the z/OS 2.1 SMF Manual
but IBM has confirmed they only exist in z/OS 2.2:
SMF23BBC='ZEDC*UNCOMPRESSEDSED*BYTES*TOTAL'
SMF23BAC='ZEDC*COMPRESSED*BYTES*TOTAL'
Thanks to Scott Barry, SBBWorks, Inc., USA.
CHANGE 33.108 Support for APARs OA45944 and OA45897 which adds new data
VMAC42 for contention counts for record locks, component1 and
Apr 23, 2015 component2 locks:
-New variables in dataset TYPE42S1:
SMF42FUA ='ACCUMULATION*WAITERS FOR*RECORD LOCK'
SMF42FUB ='RECORD LOCKS*HASHED TO*SAME ENTRY(/
SMF42FUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42FUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42FUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42FUG ='LOCKS*HASHED TO*SAME*ENTRY'
-New variables in dataset TYPE42S2:
SMF42FVA ='ACCUMLATION*WAITERS*FOR RECORD*LOCK'
SMF42FVB ='RECORD LOCKS*HASHED TO*SAME ENTRY'
SMF42FVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42FVE ='ACCUMULATION*WAITERS*FOR UPGRADELOCK'
SMF42FVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42FVG ='LOCKS*HASHED TO*SAME*ENTRY'
-New variables in dataset TYPE42S3:
SMFA2FUA ='ACCUMULTION*WAITERS*FOR RECORD*LOCK'
SMFA2FUB ='LOCKS*HASHED*TO SAME*ENTRY'
SMFA2FOD ='ACCUMULTION*WAITERS*FOR DIWA*LOCK'
SMFA2FOE ='ACCUMULTION*WAITERS*FOR UPGRADE*LOCK'
SMFA2FOF ='ACCUMULTION*WAITERS*FOR COMP2*LOCK'
SMFA2FOG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42S4:
SMFA2FVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMFA2FVB ='LOCKS*HASHED*TO SAME*ENTRY'
SMFA2FVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMFA2FVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMFA2FVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMFA2FVG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42D1:
SMF42GUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42GUB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42GUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42GUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42GUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42GUG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42D2:
SMF42GVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42GVB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42GVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42GVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42GVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42GVG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42D3:
SMF42GUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42GUB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42GUD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42GUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42GUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42GUG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42D4:
SMF42GVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42GVB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42GVD ='ACCUMULATION*WAITERS*FOR DIWA*LOCK'
SMF42GVE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42GVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42GVG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42L1:
SMF42HUA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42HUB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42HUD ='ACCUMULATION*WAITERS*FOR DIWA2*LOCK'
SMF42HUE ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42HUF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42HUG ='LOCKS*HASHED*TO SAME*ENTRY'
-New variables in dataset TYPE42L2:
SMF42HVA ='ACCUMULATION*WAITERS*FOR RECORD*LOCK'
SMF42HVB ='LOCKS*HASHED*TO SAME*ENTRY'
SMF42HVC ='ACCUMULATION*WAITERS*FOR DIWA2*LOCK'
SMF42HVD ='ACCUMULATION*WAITERS*FOR UPGRADE*LOCK'
SMF42HVF ='ACCUMULATION*WAITERS*FOR COMP2*LOCK'
SMF42HVG ='LOCKS*HASHED*TO SAME*ENTRY'
CHANGE 33.107 -DB2PM-like reports PMACC02/4 class 3 delay section was
ANALDB2R missing TCP/IP LOB and the global contention corrected
Apr 26, 2015 from only parent locks to include all contention delays.
-In PMAUD02 there were uninitialized variables corrected.
-The z/OS external sort can not be used if the length of
an observation is greater than 32760 bytes, and many of
the DB2 102 records contain 32K SQL Text variables.
For the AUDIT reports, the SQL text is reduced to 80
bytes, since that is all IBM's DB2PM reports, and the
full text is still in the T102Snnn dataset.
-If you asked for AUTHCHG in the AUDIT= parameter and
there were any IFCID 83 records the selection criteria
were not applied and that caused missing timestamps in
the report headers.
-If there were 0 OBS in the IFCID 142 dataset then a
a work file was not cleaned up.
Thanks to Neil Ervin, Wells Fargo, USA
Change 33.106 New variable EXCMTYPE in CICSEXCE (Exception) dataset
FORMATS is created to describe the exception event:
VMAC110 1='DATABASE REQUEST POLICY RULE'
Apr 22, 2015 2='FILE REQUEST'
3='PROGRAM REQUEST'
4='START REQUEST'
5='STORAGE REQUEST'
6='SYNCPOINT REQUEST'
7='TD QUEUE REQUEST'
8='TIME REQUEST'
9='TS QUEUE REQUEST'
10='WAIT FOR CF LOCKING REQUEST'
11='WAIT FOR CF NON-LOCKING REQUEST'
12='WAIT FOR UDSA'
13='WAIT FOR EUDSA'
14='WAIT FOR CDSA'
15='WAIT FOR ECDSA'
16='WAIT FOR SDSA'
17='WAIT FOR ESDSA'
18='WAIT FOR RDSA'
19='WAIT FOR ERDSA'
20='WAIT FOR GCDSA'
21='WAIT FOR GUDSA'
22='WAIT FOR GSDSA'
23='WAIT FOR TEMPORARY STORAGE'
24='WAIT FOR STRING FOR FILE'
25='WAIT FOR STRING FOR LSRPOOL'
26='WAIT FOR STRING FOR DFHTEMP'
27='WAIT FOR BUFFER FOR LSRPOOL'
28='WAIT FOR BUFFER*FOR DFHTEMP'
Thanks to Bahman Nejad, Union Bank, USA.
Thanks to Perry Lim, Union Bank, USA.
Change 33.105 Using PROC CPORT to copy z/OS data libraries to ASCII can
IMACFMTS corrupt values in character variables with $HEX format if
UTILCVRT those variables did not have the TRANSCODE=NO attribute
Apr 21, 2015 set, or they were built with an ancient SAS version prior
to that attribute. If you have downloaded PDBs and see
$HEX variables are wrong (check CPUTYPE in TYPE70), the
UTILCVRT program can be used to convert those $HEX vars
back to their correct values. Maybe. The default mapping
table is the $MGAS2EB format in FORMATS, using a table
created in 2009 for PROC CPORT translation, replacing an
earlier table created from IND$FILE. However, now using
the CPORT table under both Windows and Linux does NOT map
characters correctly; the alternative $MGAS2EB table from
IND$FILE must be used. That alternative format is defined
in Example 2 in a comment block in the IMACFMTS member.
Copy IMACFMTS to your USERID.SOURCLIB, remove the comment
block in Example 2, and run the FORMATS step of JCLINSTL
(%INCLUDE SOURCLIB(FORMATS); with DISP=OLD on //LIBRARY)
and the alternative table values will be used.
Thanks to Warren Cravey, Fidelity, USA.
Thanks to Rachel Holt, Fidelity, USA.
Change 33.104 NMON CPU records can now contain three digits, CPU001, so
VMACNMON the logic to create CPUNR now decodes two or three digits
Apr 21, 2015 for CPUnnn, PCPUnnn and SCPUnnn.
Thanks to Raissa Moussu, METROLOGFIE AIX EN PROVENCE, FRANCE.
Change 33.103 VMXGPRAL (PRINT/MEAN/FREQ ALL datasets &ALL variables in
VMXGPRAL a "PDB" data library, with both Label and Variable Name)
Apr 15, 2015 enhanced for FREQ with TABLE= option to choose what
variables are tabulated. TABLES=_CHAR_, will only show
the character variables. Without the TABLES= argument,
all variables will be tabulated.
Thanks to MP Welch, Bank of America, USA.
Change 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE, test for
VMACSYNC SYNCLVL for ancient Release 3.7 conflicted) causing many
Apr 15, 2015 variables to be missing values with no error message,
notably, CPUZIPTM is a missing value without this change.
Thanks to Roger Foreman, Transunion, USA.
Change 33.102 DB2 V10 INVALID DATA FOR QLACCPUR and QLACDBAT when field
VMACDB2 QLACLOCN was relocated because it's longer than 8 bytes,
Apr 14, 2015 but the length of the relocated field in XLENLOCN is NOT
in LENLOCN causing misalignment when XLENLOCN GT 20.
Thanks to Betty Wong, Bank of America, USA.
Change 33.101 Support for iSeries 7.2 (COMPATIBLE with new LRECLS).
VMACQACS Comments in VMACQACL list LRECLs and 7.2 records tested.
Apr 13, 2015 -New variables in QAPMDISK:
DSLVLMP ='LEVEL OF*MIRRORED*PROTECTION'
DSLSCNDS='LOG*SENSE*COMMANDS*ISSUED'
DSLSRT ='LOG*SENSE*RESPONSE*TIME'
-New variables in QAPMJOBM (QAPMJOBMI):
JBTNAME ='THREAD*NAME'
JBSLTCNT ='SHORT*LIFESPAN*ENTRY*COUNT'
JBSACPU ='ACCUMULATED*JOB*SCALED*CPU TIME'
JBINDCPU ='THREAD*UNSCALED*CPU TIME*USED'
JBSINDCPU ='THREAD*SCALED*CPU TIME*USED'
JBCPUWC ='PROCESSOR*ELAPSED*TIME'
JBVPDLY ='VIRTUAL*PROCESSOR*DELAY*TIME'
JBSEIZECNT ='SIEZE*COUNT'
JBPSLCKCNT ='PROCESS*SCOPED*LOCK*COUNT'
JBTSLCKCNT ='THREAD*SCOPED*LOCK*COUNT'
JBPSRCDLCK ='PROCESS*SCOPED*DATABASE*LOCK*COUNT'
JBTSRCDLCK ='THREAD*SCOPED*DATABASE*LOCK*COUNT'
JBNFOGDT ='OFF-GROUP*DISPATCH*TIME'
JBNFOGMA ='OFF-GROUP*PAGE*FRAMES'
JBPGEZSTL ='PAGES*MARKED*EASY TO*STEAL'
JBSQLCLK ='SQL*CLOCK*TIME'
JBSQLCPU ='THREAD*UNSCALED*SQL*TIME'
JBSQSCPU ='THREAD*SCALED*SQL*CPU TIME'
JBSQLDBR ='SQL*SYNCHRONOUS*DATABASE*READS'
JBSQLNDBR ='SQL*SYNCHRONOUS*NONDATABASE*READS'
JBSQLDBW ='SQL*SYNCHRONOUS*DATABASE*READS'
JBSQLNDBW ='SQL*SYNCHRONOUS*NONDATABASE*READS'
JBSQLADBR ='SQL*ASYNCHRONOUS*DATABASE*READS'
JBSQLANDBR ='SQL*ASYNCHRONOUS*NONDATABASE*READS'
JBSQLADBW ='SQL*ASYNCHRONOUS*DATABASE*WRITES'
JBSQLANDBW ='SQL*ASYNCHRONOUS*NONDATABASE*WRITES'
JBAGCRT ='ACTIVATION*GROUPS*CREATED'
JBPGMSACT ='PROGRAM*ACTIVATIONS*CREATED'
JBCURTMP ='CURRENT*TEMPORARY*STORAGE'
JBPEAKTMP ='PEAK*TEMPORARY*STORAGE'
JBMAXTMP ='MAXIMUM*TEMPORARY*STORAGE'
JBTMPPGA ='4K UNITS*ALLOC*TEMPORARY*STORAGE'
JBTMPPGD ='4K UNITS*DEALLOC*TEMPORARY*STORAGE'
JBHSQLSTMT ='HIGH*LEVEL*SQL*STATEMENTS'
JBTICC ='THREAD*INSTRUCTION*COUNT*CHARGED'
JBTICU ='THREAD*INSTRUCTION*COUNT*USED'
JBTTMBU ='THREAD*VIRTUAL*TIME'
JBPICC ='PROCESS*HDW INSTR*COUNT*CHARGED'
JBPRRSCPTY ='PROCESSOR*RESOURCE*PRIORITY'
-New variables in QAPMJOBO (QAPMJOBOS):
JBFSOPN 'FILE*SYSTEM*OPENS''
JBFSDC 'FILE*SYSTEM*DIRECTORY*CREATES'
JBFSNDC 'FILE*SYSTEM*NON-DIRECTORY*CREATES*
JBFSDD 'FILE*SYSTEM*DIRECTORY*DELETES'
JBFSNDD 'FILE*SYSTEM*NON-DIRECTORY*DELETES*
JBSPLFC 'SPOOLED*FILES*CREATED*BY THIS JOB*
JBSBMJOBS'JOBS*SUBMITTED*OR SPAWNED.'
JBSQLSTMT'SQL*STATEMENTS'
JBLWTSQL 'SQL*RELATED*DATABASE*WRITES*(LOGIC
JBLRDSQL 'SQL*RELATED*DATABASE*READS*(LOGICA
JBDBUSQL 'SQL*RELATED*DATABASE*MISCELLANEOUS
JBPASCMP 'SQL*PAS*COMPRESSIONS*ALL THREADS'
JBPKGCMP 'SQLPKG*COMPRESSIONS'
JBCTHD 'CONNECTED*THREAD*IDENTIFIER'
JBCJNAM 'CONNECTED*JOB*NAME'
JBCJUSR 'CONNECTED*JOB*USER'
JBCJNBR 'CONNECTED*JOB*NUMBER'
-New variables in QAPMPOLB (QAPMPOOLB):
POPGS4 ='POOL*4K*PAGES'
POPGS64 ='POOL*64K*PAGES'
PODBF4 ='POOL*DATABASE*4K*PAGE*FAULTS'
PODBF64 ='POOL*DATABASE*64K*PAGE*FAULTS'
PONDBF4 ='POOL*NONDATABASE*4K*PAGE*FAULTS'
PONDBF64 ='POOL*NONDATABASE*64K*PAGE*FAULTS'
PODBPG4 ='POOL*DATABASE*4K*PAGES*READ'
PODBPG64 ='POOL*DATABASE*64K*PAGES*READ'
PONDPG4 ='POOL*NONDATABASE*4K*PAGES*READ'
PONDPG64 ='POOL*NONDATABASE*64K*PAGES*READ'
POUNAL4 ='UNALLOCATED*4K*PAGES'
POUNAL64 ='UNALLOCATED*64K*PAGES'
POAGED4 ='POOL*4K*PAGES*AGED/
POAGED64 ='POOL*64K*PAGES*AGED'
POSTLN4 ='POOL*4K*PAGES*STOLEN'
POSTLN64 ='POOL*64K*PAGES*STOLEN'
POUNUSE4 ='POOL*4K*PAGES*UNUSED'
POUNUSE64 ='POOL*64K*PAGES*UNUSED'
POSYNC4 ='POOL*4K*PAGE*SYNC I/O'
POSYNC64 ='POOL*64K*PAGE*SYNC I/O'
POASYNC4 ='POOL*4K*PAGE*ASYNC I/O'
POASYNC64 ='POOL*64K*PAGE*ASYNC I/O'
POPGOUT4 ='POOL*4K*PAGE*OUTS'
POPGOUT64 ='POOL*64K*PAGE*OUTS'
POPGABLE4 ='POOL*4K*PAGES*PAGEABLE'
POPGABLE64='POOL*64K*PAGES*PAGEABLE'
POATMPT4 ='POOL*4K*ALLOCATION*ATTEMPTS
POATMPT64 ='POOL*64K*ALLOCATION*ATTEMPTS
POAPS4 ='POOL*4K*AFFINITY*SUCCESSES
POAPS64 ='POOL*64K*AFFINITY*SUCCESSES
POAPMIG4 ='POOL*4K*AFFINITY*MISSES
POAPMIG64 ='POOL*64K*AFFINITY*MISSES
POAPMOG4 ='POOL*4K*AFFINITY*MISSES*OFFGROUP'
POAPMOG64 ='POOL*64K*AFFINITY*MISSES*OFFGROUP'
POCRTPG64 ='POOL*4K*PAGES*CREATED'
POBRKPG64 ='POOL*64K*PAGES*BROKEN*UP'
POPOSIZB ='POOL*SIZE*KB'
POUNALB ='UNALLOCATED*POOL*SPACE*KB'
-New variables in QAPMSYST (QAPMSYSTEM):
SYVPID ='VIRTUAL*SHARED*POOL ID'
SYVPCAP ='VIRTUAL*SHARED POOL*ENTITLED*CAPACITY'
SYPPLU ='PHYSICAL*SHARED POOL*CPU TIME*USED'
SYPPLA ='PHYSICAL*SHARED POOL*CPU TIME*AVAILABLE'
SYPTHV ='HYPERVISOR*CPU*TIME'
SYPTINT ='INTERRUPT*CPU*TIME'
SYPTWS ='WAITTASK*TIME'
SYPTDN ='DONATED*CPU*TIME'
SYSSPTU ='SCALED*CPU*TIME*USED'
SYUCAPF ='PARTITION*UNCAPPED*FLAG'
SYDONF ='PARTITION*DONATION*FLAG'
SYPTWAIT ='VIRTUAL*PROCESSOR*THREAD WAIT*EVENT TIME'
SYPTREADY ='VIRTUAL*PROCESSOR*THREAD WAIT*READY TIME'
SYPTLATEN ='VIRTUAL*PROCESSOR*THREAD DISPATCH*LATENCY'
SYPTACT ='VIRTUAL*PROCESSOR*THREAD*ACTIVE TIME'
SYPTIDLE ='VIRTUAL*PROCESSOR*THREAD*IDLE TIME'
SYPTINTR ='VIRTUAL*PROCESSOR*THREAD*INTERRUPT TIME'
SYFRMCPU ='PROCESSOR*FIRMWARE*TIME USED'
SYFRMSCPU ='PROCESSOR*SCALED*FIRMWARE*TIME USED'
SYPFOLDSW ='PROCESSOR*FOLDING*SWITCH*STATE'
SYPFOLDST ='PROCESSOR*FOLDING*STATE'
SYEMMAJCDE='ENERGY*MANAGEMENT*MAJOR CODE'
SYEMMINCDE='ENERGY*MANAGEMENT*MINOR CODE'
SYEMATTR ='ENERGY*MANAGEMENT*ATTRIBUTES'
SYEMPWRLMT='ENERGY*MANAGEMENT*POWER DRAW*LIMIT WATTS'
SYSQLCPU ='UNSCALED*SQL*CPU TIME*USED'
SYSQLSCPU ='SCALED*SQL*CPU TIME*USED'
SYOSTMP ='CURRENT*TEMPORARY*STORAGE*ALLOCATED*NONDB'
SYDBTMP ='CURRENT*TEMPORARY*STORAGE*ALLOCATED*DB'
SYAJOBTMP ='CURRENT*TEMPORARY*STORAGE*CHARGED*ACTIVE'
SYEJOBTMP ='CURRENT*TEMPORARY*STORAGE*CHARGED*EMDED'
SYUSERTMP ='CURRENT*USER*TEMPORARY*STORAGE'
SYPSLPU ='PHYSICAL*SHARED POOL*SCALED*CPU TIME*USED'
SYTRUNIC ='HARDWARE*INSTRUCTIONS'
SYTRUNVTB ='NON-IDLE*PROCESSOR*VIRTUAL*TIME'
SYTITUIC ='INTERRUPT*INSTRUCTION*COUNT'
SYTFRMIC ='FIRMWARE*INSTRUCTION*COUNT'
Thanks to Raymond J. Smith, United Health Group, USA.
Change 33.100 -Protect RMF III for invalid ASI table index in UWD table
ASMRMFV entry that caused ABEND S0C4 in FINDAS when the invalid
Apr 12, 2015 index value was really bad, i.e., it exceeded the number
of entries in the ASI table and an attempt was made to
access data from well beyond the ASI table's end.
Thanks to Randy Schlueter, First Data Corporation, USA
Change 33.099 MXG 32.13-MXG 33.03. TMON/CICS Version 3.4 AND EARLIER.
VMACTMO2 -Dataset MONITASK CPU time (TASCPUTM) and ALL DURATION
Apr 11, 2015 variables are WRONG, TOO SMALL, by a factor of 4096.
In TMON Version 4, all durations were changed from the
original microseconds to TODSTAMP, which requires the
division by 4096, but the MXG code inserted for MONITASK
was mis-located and applied to all TMON versions.
-Less critical, and wrong ONLY with Version 4 records: ALL
duration variables in all OTHER MONIxxxx datasets were
NOT divided by 4096, so they are TOO LARGE by 4096.
Thanks to Andrew Petersen, CSC, AUSTRALIA.
Change 33.098 NMON (AIX/LINUX) CPU variables in PDB.NMONCPUD and in the
VMACNMON PDB.NMONINTV were revised and missing values corrected.
Apr 10, 2015 The individual CPUNR data in PDB.NMONCPUD from the three
CPUnn, PCPUnn, and SCPUnn records are the variables
prefixed with CPUNxxxx,PCPUNxxxx,SCPUNxxxx with suffixes
BUSY,IDLE,SYS,USER,WAIT.
The interval CPU_ALL, PCPU_ALL, and SCPU_ALL record's
in PDB.NMONINTV are prefixed PCPUxxxx,APCPUxxxx,ASCPUxxxx
with the same suffixes (plus variable APCPUENTCAP).
The BUSY variables are calculated for all observations.
Thanks to Florent Boulesteix, INOVANS partenaire CAAGIS, FRANCE.
Change 33.097 -SMFSRCH utility (select SMF records containing text and
SMFSRCH create all MXG datasets from those selected records) adds
Apr 9, 2015 new PRINT= option with YES/NO/nnn to print all, none, or
the first nnn observations of each dataset. The PRINTIT=
argument's YES or NO are still supported, but the PRINT=
argument is the more common spelling in MXG macros.
-Set USERADDS=NOUSERID, and all matching SMF types are
reported, but the 128-255 USER SMF records are skipped,
This avoids an abend if not all of your USER records are
mapped in IMACKEEP, MACKEEP, OR USERADDS= argument.
Thanks to MP Welch, Bank of America, USA.
Change 33.096 -z13 with SMT PROCVIEW=CORE, dataset TYPE70PR, variable
VMAC7072 SMT_NUM, the count of threads for each core, wasn't kept.
Apr 12, 2015 -TYPE70PR variable SMF70MTTT, MULTI-THREADING*IDLE*TIME,
which is actually SMF70MTIT mis-spelled, is accumulated,
requiring an additional sort and DIF() to deaccumulate.
As is ALWAYS the case when IBM writes ACCUMULATED values,
the value for the first instance of each LCPUADDR in each
LPAR will be a missing value. Some cases when the next
accumulated value was slightly smaller than the prior are
also set to missing value, but if they occur in your data
a PMR should be raised with IBM support. The label for
SMF70MTTT now contains 'SMF70MTIT' to compensate.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 33.095 Optional SUMMARY=SMFBYTES/SMFRECNT argument will produce
ANALID a report sorted by DESCENDING &SUMMARY to print largest
Apr 3, 2015 first.
Change 33.094 Format MGSMFID did not describe SMF 115 records subtypes
FORMATS 5, 6, and 7.
Apr 3, 2015
Thanks to Paul Bennett, Euroclear, BELGIUM.
Thanks to Edmond Dierickx, Euroclear, BELGIUM.
Change 33.093 MXG 33.03. Disabled debug statement *PUTLOG +2 'DEBUG..;
VMAC7072 was followed by an unmatched */, but there was no syntax
Apr 3, 2015 error, because SAS recognized the asterisk as the start
of another comment, that ended with the semicolon of the
next statement, HOLICFTM=ICFACTTM;, so that statement was
absorbed and not executed. Fortunately, only ICF time in
some unusual circumstances, when the time had to be held,
might have been impacted.
Thanks to MP Welch, Bank of America, USA.
Change 33.092 -Some BBBPnnn variables were mis-assigned values: BBBP040
VMACNMON and BBBP049 because the BBBP40 'MAXIMUM CAPACITY' text
Apr 8, 2015 overlapped with BBBP49 'MAXIMUM CAPACITY OF POOL'. All
text tests are expanded to prevent the overlap.
-The MERGE of CPUD/CPUNP/CPUNS datasets had DUPLICATE
MERGE VARIABLES when the number of CPUs (observations)
in those datasets were not equal. Since CPUD has the
the primary CPU metrics, the MERGE was split into two
steps, first the three CPUD/CPUNP/CPUNS with CPUNR added
to the BY list, and now OUTPUT only if CPUD is present,
whether or not the other two datasets are present for
this CPUNR. Then the second step MERGES the output with
SNAPMAP to create PDB.NMONCPUD with the CPU metrics for
each CPUNR.
-Diagnostic tests for DISKBUSY counter errors corrected.
Thanks to Raissa Moussu, METROLOGFIE AIX EN PROVENCE, FRANCE.
Change 33.091 Support for CICS User fields USERAGT, ORIGUOW, and
IMACAAAA ORIGTGID.
IMACICVM
IMACICVN
IMACICVO
UTILEXCL
VMAC110
Apr 2, 2015
Thanks to Rob Hollingum, HSBC, ENGLAND.
Change 33.090 Mainview for MQ PTFs corrected the Offset ENTO value from
VMACBBMQ the always incorrect prior value of 28 for BBMQQUES 'E6'
Apr 2, 2015 to the correct value of 32, but this is an INCOMPATIBLE
change which mis-aligned MXG input, because MXG has known
to skip over those four bytes. Logic revised to support
either value since the records are otherwise unchanged.
BPL2458(MVMQ51) and BPL2459(MVMQ52) were the PTFs.
Thanks to Jim Swinarski, Credit-Suisse, USA.
Change 33.089 Not Used.
Change 33.088 Some duration variables in RMF III ZRBxxxx datasets still
VMACRMFV had TIME12.2 format but have millisecond resolution, so
Apr 1, 2015 they are all changed to TIME13.3 to show all decimals.
Change 33.087 -RMF Type 74 Subtype 9 zEDC Hardware Accelerator support.
VMAC74 The TYPE749 dataset was created with RMF 2.1 support back
Apr 1, 2015 in Change 31.153, but that INPUT was inhibited, awaiting
May 4, 2015 test records, and this update has been validated with
May 6, 2015 zEDC PCIE type 74 subtype 9 records.
-May 4: Variables R7491IIS and R74i1IOS corrected to add
II2 and IO2 instead of II1 and IO1.
-May 6: Variables R7491BPS and R7491BPC were incorrectly
multiplied in conversion to bytes - way too large.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 33.086 Support for Velocity Software zVPS a/k/a XAM Version 5.4.
VMACXAM Status April 9:
Apr 7, 2015 -All updates have been made with these exceptions:
EXXAMIFL Segments not documented, have data records, skipped:
EXXAMIFT TCP: LINMEM LINCPU LINITF
VMXGINIT DEV: IODSZI
Apr 9, 2015 New Segments, no data, not skipped, will print msg.
Apr 23, 2015 TCP:ORASYS ORAPGA ORASGA ORAWTS
VSECFG VSESYS VSECPU JVMSYS
-INFILE XAMCPU changes:
NEW dataset XAMIFLBY for individual IFL engine stats.
NEW dat