COPYRIGHT (C) 1984-2020 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES ALL
=========================MEMBER=CHANGE38================================
/* COPYRIGHT (C) 1984-2020 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG VERSION 38.10 is dated Nov 23, 2020, thru Change 38.213.
MXG VERSION 38.09 was dated Nov 4, 2020, thru Change 38.196.
First MXG VERSION 38.09 was dated Nov 2, 2020, thru Change 38.194.
MXG VERSION 38.08 was dated Sep 28, 2020, thru Change 38.163.
MXG VERSION 38.07 was dated Aug 22, 2020, thru Change 38.141.
MXG VERSION 38.06 was dated Jul 25, 2020, thru Change 38.123.
Second MXG VERSION 38.06 was dated Jul 25, 2020, thru Change 38.122.
First MXG VERSION 38.06 was dated Jul 24, 2020, thru Change 38.120.
MXG VERSION 38.05 was dated Jul 15, 2020, thru Change 38.112.
MXG VERSION 38.04 was dated May 25, 2020, thru Change 38.081.
MXG VERSION 38.03 was dated May 7, 2020, thru Change 38.071.
MXG VERSION 38.02 was dated Mar 23, 2020, thru Change 38.048.
MXG VERSION 38.01 was dated Feb 17, 2020, thru Change 38.027.
Annual MXG VERSION 37.37 was dated Jan 6, 2020, thru Change 37.272.
The Final MXG Newsletter SIXTY-NINE was dated Jan 3, 2018.
New TECHNOTES previously in NEWSLTRS are now in CHANGESS.
Instructions for ftp download can be requested by using this form:
http://www.mxg.com/Software_Download_Request
Your download instructions will be sent via return email.
Contents of member CHANGES:
I. Current MXG Software Version 38.10 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 38.10.
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, although there are
no new NEWSLTRS updates; they are now found in CHANGESS as TECHNOTEs.
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 38.10 DATED NOV 23, 2020, THRU CHANGE 38.213.
==MAJOR CHANGES ADDED IN MXG 38.10, DATED Nov 23, 2020 THRU 38.213.
ABEND CORRECTED
TYPE110 38.205 SMF 110 ST 1 MNSEGCL=5 INPUT STATEMENT EXCEEDED.
TYPE42 38.204 TYPE 42 ST 5 incorrect MXG logic INPUT EXCEEDED.
NEW SUPPORT:
ASUM113 38.201 New z/15 EXTND256-EXTND287 were not kept in ASUM1131.
TYPEBETA 38.200 Support for BETA93 and BETA97 new data and updates.
TECHNOTE 38.199 Compressed SMF 110 expensive without EXITCICS on z/OS
ASMVVDS 38.197 Updates to read VVDS records and output to file/SMF.
==MAJOR CHANGES ADDED IN MXG 38.09, DATED Nov 4, 2020 THRU 38.196.
ABEND CORRECTED
UTILBLDP 38.195 UTILBLDP with SUPPRESS=110 and BUILDPDB NE 'NO'
ABENDED with ERROR:WORK.CICSEXCE.DATA not found.
==MAJOR CHANGES ADDED IN MXG 38.09, DATED Nov 2, 2020 THRU 38.194.
NEW SUPPORT:
TYPE110 38.168 Support for CICS/TS 5.6 STID=43, 46, and new STID=61.
TYPE16 38.164 Support for APAR PH03207 for DFSORT ZSORT stats.
ASMRMFV 38.188 Support for RMF III EXECVEL and PERFINDX variables.
ASMRMFV 38.181 New Field Data Filter support for CFIG3 table.
TYPE102 38.179 Support for DB2 ZPARM MFA_AUTHCACHE_UNUSED_TIME.
TYPE38 38.178 Support for z NetView 6.3 Subtype 4 Command stats.
ANALAVAI 38.183 Enhanced reporting on availability.
ERRORS CORRECTED:
UTILEXCL 38.180 Optional "Candle" CICS segment kept wrong variables.
TYPE50 38.177 VSAM Tuning data sets were misaligned.
==MAJOR CHANGES ADDED IN MXG 38.08, DATED Sep 28, 2020 THRU 38.163.
VMAC30 38.163 Support for APAR OA59813 for BOOSTCLASS='RECO'.
TYPE74 38.152 Support for APARs OA58724/58729 new Monopoly in ST=4.
UTILBLDP 38.157 BUILDMXG fails if you didn't specify OUTFILE=.
TYPE119 38.156 Tokens for TYP11924/11925 were not in _N119.
ANAL119 38.150 Errors corrected if you didn't have //IPHOSTS file.
ANALSIIS 38.149 SM113TM replaced by TIMESTMP for better match up.
READDB2 38.147 DB2GBPAT now recognized, ACCTSORT=NO now works.
VMXGDUR 38.145 If interval LT actual duratm, warning is printed.
VMXG70PR 38.142 Support for ASUM70WK to keep full hours.
VMXGPRAL 38.159 MXG 38.07 only, 180 Syntax Error citing SP_NOBS.
TYPERMFV 38.124 Many dupes in ZRBXCG/XCP/XCS datasets.
TYPERMFV 38.162 Datasets ZRBCHP and ZRBSCM had zero observations.
PDBAUDIT 38.161 Value of PDBAUDIT incorrectly set, revised.
==MAJOR CHANGES ADDED IN MXG 38.07, DATED Aug 22, 2020 THRU 38.141.
TYPE26J2 38.137 Support for APAR OA57466 new TYPE26J2 compress data.
ASMRMFV 38.128 Field Data Filter FDF Support adds XCFG3, FDF fix.
TYPE7072 38.126 SMF sysplex data with SMF Logger INTERLEAVES ALL SMF.
TYPERMFV 38.124 Many dupes in ZRBXCG/XCP/XCS datasets.
==MAJOR CHANGES ADDED IN MXG 38.06, DATED Jul 25, 2020 THRU 38.123.
VMXGCICI 38.123 Tailored CICxxxxx statistics in PDB and WORK failed.
TYPE110 38.122 Some CICS Statistics datasets (CICxxxxx) were sorted
because %INCLUDE SOURCLIB(SCICSORT) after line 6281
was accidentally deleted.
==MAJOR CHANGES ADDED IN MXG 38.06, DATED Jul 24, 2020 THRU 38.120.
TYPE110 38.114 New CICSRDUR/URIMAP, CICSRDWB/WEBSVC datasets.
TYPEDB2 38.117 Support for DB2 APAR PH16111 IFCID 365 SMF 100.
TYPE102 38.117 Support for DB2 APAR PH16111 IFCID 365 SMF 102.
TYPEMVCI 38.116 Support for BMC Mainview for CICS 7.1 (COMPATIBLE).
==MAJOR CHANGES ADDED IN MXG 38.05, DATED Jul 15, 2020 THRU 38.112.
ABEND CORRECTED:
TYPE7072 38.103 MXG 38.03/38.04 TYPE7072 fails if //PDB on TAPE.
ASCII 38.091 MXG on Windows, AV Products, LOCK NOT AVAILABLE
SAS 38.087 ERROR: Utility File Open Failed PROC MEANS/SUMMARY.
TYPE83 38.090 SMF 83 ST 3 INPUT STATEMENT EXCEEDED.
NEW SUPPORT:
TYPE110 38.084 Support for CICS/TS 5.6 (INCOMPAT, FIELDS INSERTED).
TYPE7072 38.107 Support for APAR OA59330 new variables in TYPE7002.
MANY 38.105 Support for May 2020 SMF Manual Changes zOS 2.4.
TYPETPMX 38.102 Support for Thruput Manager TMT7123/TMT7124 Jul 2020.
TYPE85 38.100 Support for SMF 85 OAM Cloud Tier.
TYPE74 38.098 Support for SMF 74 CMF from BMC PTF BQM12658/59.
TYPE78 38.097 Support for APAR OA56684 TYPE78IO EADM/SCM variables.
TYPEDB2 38.096 Support for APAR PI98851 new variables DB2STATS.
TYPE30 38.093 Support for APAR OA59126, dataspaces variables.
TYPE74 38.089 Support for new EADM variables in TYPE7410.
TYPESARR 38.088 Support for CA View SARR SMF Subtypes 34 and 35.
ANALINIT 38.083 Enhanced JOB EXEC/QUEUED/HELD/etc analysis
TYPE110 38.099 CICS Statistics Records revisions.
ASMRMFV 38.082 ASMRMFV FDF Support for new tables.
CMF+RMF 38.095 Variable CMFPROD to select CMF vs SMF if both are on.
UCICSCNT 38.085 Enhanced counts/bytes for SMF 110 including STIDs.
==MAJOR CHANGES ADDED IN MXG 38.04, DATED MAY 25, 2020 THRU 38.081.
ABEND CORRECTED:
BLDSMPDB 38.081 MXG 38.03 only. BLDSMPDB WEEKLY JOB ABENDS, typo.
Line 667 has 1 %END; remove the "1".
Only on z/OS and only if WEEK is a GDG.
ERRORS CORRECTED:
TYPE30_6 38.072 Revised deaccumulate for accumulated subtype 6.
TYPEDB2 38.075 Support for APAR PH14037 DB2ACCTP QPACPKID truncated.
No MXG Change, IBM APAR corrected wrong offset.
ANAL119 38.073 Cleanup and removal of a typo.
NEW SUPPORT:
FORMATS 38.080 Support for z15 T02 values in $MGRMIPS format.
TYPE42 38.079 Support for APAR OA59541 for Type 42 Subtype 27.
TYPE102 38.077 SMF102 IFCID 143/144 increase length QW014xUR.
==MAJOR CHANGES ADDED IN MXG 38.03, DATED MAY 16, 2020 THRU 38.071.
EXPOSURE CORRECTED:
AUTOINST 38.054 ASCII Unique INSTREAM create for Concurrent Sessions.
-ALL ASCII SITES SHOULD PUT %AUTOINST IN IMACINIT.
ERRORS CORRECTED
TYPE123A 38.061 Datetime values were 2080 instead of 2020, MXG error.
TYPECMFV 38.063 CMF VSAM INVALID DATA messages, wrong informat.
TYPECIMS 38.058 CIMS/IMF CIMSDBD/DB2/MQ Zero Obs 37.37-38.02
VMXGOPTR 38.056 ANALHSM caused Error "SAS Option Name OPTIONS 1".
TYPE70 38.055 PCTMVSBY incorrect after 37.123. (NOT PCTCPUBY!!!).
ASMRMFV 38.064 Support for APAR OA58759, caused Condition Code 4.
TYPEXCOM 38.069 XCOM input did not skip the 461 bytes added in 12.0.
New Support
TYPE119 38.068 Support for Comm Server SMF 119 Subtype 11 ZERT data.
TYPE110 38.060 SET MONITOR FREQ hourly CICSTRAN for long runners.
UTILROLL 38.065 UTILROLL example to combine PDBs created every 4hr.
TYPEDB2 38.062 Support DB2 APAR PI92652,PI82191 and DPAGE support.
TYPESVIE 38.057 Support for SYSVIEW Subtype 2 record one min detail.
TYPEXAM 38.059 zVPS XAMCUV LCPUID=96 Totals records now deleted.
VMACSMF 38.051 SAS FTP Access Method &MXGABND=1 set to print errors.
TYPE42 38.067 Yet another TYPE42 invalid LENSR in subtype 5 42's.
==MAJOR CHANGES ADDED IN MXG 38.02, DATED MAR 23, 2020 THRU 38.048.
ERRORS CORRECTED
VMACSMF 38.033 SMF Signature Type 2 St 1/2 MANY BACK2BACK LOG msgs
TYPE112 38.040 OMEGAMON TEMS St 38 INVALID ARGUMENT LENGTH CHANGED.
TYPE73 38.038 Variable SHIFT was not populated.
New Product Support
TYPEVMXA 38.048 z/VM MONWRITE 6.4.19.1 z15 INCOMPATIBLE.
Many Log Messages, PRCMFC/PRCMFM empty, rest okay.
TYPE70 38.031 Support for APAR OA56683 SMFBOOST System Recovery
TYPE62 38.041 Support for APAR OA57105, adds JOBID SYSPLEX.
TYPE64 38.041 Support for APAR OA57105, adds JOBID SYSPLEX.
TYPETPMX 38.039 Support for new INREI and JCLJJ in TYPETPMX.
Enhancements
TYPE116 38.037 MQMACCTQ/MQMACCT/MQCFSTAT/MQMQUEUE/ revisions.
TYPE113 38.035 TYPE113 Counters EXTND247/252/264/265 now labeled.
TYPEVMXA 38.019 z/VM VXAPLSLM variable SHARERAM zero if not RHEL8.
TYPE89 38.034 APAR OA59002 corrects TYPE89 var SMF89UZT values.
==MAJOR CHANGES ADDED IN MXG 38.01, DATED Feb 17, 2020 THRU 38.027.
ERRORS CORRECTED
CONFIMXG 38.004 MXG 37.37 only, 1024 should be OPEN_ED=1047.
TYPE80A 38.017 INPUT EXCEEDED due to a HOME segment with no data.
ANALID 38.010 ERROR "OPTORG4" if you changed SMFAUDIT to NO.
UTILBLDP 38.008 Error after Change 37.149 if first USERADD is IDMS.
New Product Support
FORMATS 38.020 Support for SMF73CPT 33/34 connection types.
TYPE102 38.019 Support for DB2 APAR PH18739 var QW0389IT in T102S389
TYPEIMS 38.014 Support for APAR PH14569/PH21001 IMS 22 log record.
TYPEBETA 38.013 Support for BETA (93) and BETA97 Version 7.1.0
TYPEBE97 38.013 Support for BETA (93) and BETA97 Version 7.1.0
TYPE42 38.011 Support for APAR OA57718, zHyperLink TYPE42DS stats.
TYPEIAM 38.006 Support for IAM 9.3 Spin 3 INCOMPATIBLE inserts.
FORMATS 38.003A R744HOPM $MG074HO new '50x:CL5 10GBIT/S CEE ROCE'.
TYPEIDMS 38.003 IDMSTAS UOW/NETNAME added, TASUFLD1-3 corrected.
TYPETMS5 38.002 Variables BYTEPRC and BESKEY added to TMS/DSNBRECD.
BUILDIMS 38.001 All selections now work, new INPUTCLNR variable.
New Analysis/Reporting
ANAL95TH 38.018 PROC TABULATE 95th pct response stats CICSTRAN/JOBS.
ANALATNC 38.005 Report Code for Latent Demand analysis, examples of
reports: https://www.mxg.com/downloads/analatnc
DOCVLONG 38.012 Creates a DOCVLONG with all DOCVER data on one line.
ANALSIIS 38.009 Analysis of Store Into Instruction Stream enhanced.
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 TS1M7 (9.4M7),
"M7", or with options VERSIONLONG;
"SAS 9.4 (9.04.01M7P080520)" on z/OS
9.4 (TS04.01M7P08052020)" on ASCII.
SAS V9.4 M7 is RECOMMENDED, but MXG executes without error
using SAS Version 9.4 M0-M2 or M4-M6 or SAS Version 9.3 M0-M2.
SAS V9.4 M5 is REQUIRED with z/OS 2.3 with Eight-Byte USERIDs
for Interactive TSO (DMS) SAS Sessions. SAS Note 61339.
Only on z/OS, SAS 9.4 "M5" requires MXG 35.36+ because it adds the
NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect
described in SAS Note 61672. But SAS apparently does not plan for
a defect correction since the MXG Circumvention solves for MXG and
the text of 61672 simply describes the circumvention needed because
MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect.
See Change 35.309 for more details on using NOERRORSTOP for your
own PROC SQLs.
SAS V9.4 M3 is NOT RECOMMENDED. See Change 36.128 SAS Note 61906
that reports 40% Increase in CPU time with M3.
SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support.
SAS V9.3 SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok.
But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828,
see CHANGE 29.169, IS REQUIRED:
The %MACRO compiler error is in processing %LET
statements. While only two MXG members failed
repeatedly in MXG QA tests on z/OS, there were random
%LET errors in ASCII QA tests, so ANY use of %LET
statement on ANY platform are vulnerable to this
error, as the %MACRO compiler is SAS portable code,
used on all platforms. So this is NOT just an MXG
error, but impacts ALL SAS programs.
SAS9.3 is LEVEL A support from SAS.
SAS V9.2 Was recommended, prior to 9.3, and was error-free with
MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to
use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2
Decompression Infile Exit. but SAS V9.2 does execute on
that platform.
9.2 is LEVEL B Support from SAS, as of Sep 30, 2013.
SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at
Support level C by SAS Institute, Sep 30, 2013.
SAS V9.1.3 is NOT supported by SAS on Windows SEVEN.
SAS V8.2 SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS!
with SAS 8.2.
SAS 8.2 is Level C Support from SAS as of Dec 31, 2011.
JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used
***************************************************************
As documented in Change 27.356, for SAS V9.2 or later):
The standard SAS JCL Procedure can be used for MXG with SAS V9.2+
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
But CONFIMXG is required for sites with NLS issues, and you must
use JCLCONFI to create/update the MXG.FORMATS catalog if you use
CONFIG='MXG.SOURCLIB(CONFIMXG)'.
For no NLS, you can use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 36.11 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows TEN and
Linux on 64-bit hardware, but MXG users execute MXG on MANY
(ALL??) SAS platforms, including AIX, Linux, and other 'nix'
variants, on many different hardware platforms, and since they all
work we don't need to list them. If SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 4.1 USER 4037 ABEND, See Change 37.116.
WPS Version 4.0 reportedly fixed version 3 problems.
WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.
and other errors with 3.00 or 3.01 have been corrected in the
current WPS version.
WPS Version 3.01.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
The z15 and z15 T02 processors INCOMPATIBLY changed the SMF 113
records by inserting 32 new EXTEND and 4 CRYPTO counters, causing
ARRAY SIZE EXCEEDED with BUILDPDB which processes the SMF 113s.
Support for counter changes for both models was in MXG 37.08.
If you use MIPS in reports, the format $MGRMIPS provides the
MIPS/MSU value for each processor; the z15 values were updated
in MXG 37.08, and the z15 TO2 values were updated in MXG 38.04.
These MXG programs use $MGRMIPS: ASUMMIPS GRAFCEC GRAFWLM
GRAFWRKX and TYPERMFV (RMF III).
The z/14 also inserted SMF 113 fields, supported in MXG 36.07.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
And z/VM on the z15 requires MXG 38.02, PRCMFC/MFM COUNTERS caused
HARDWARE COUNTER messages, PRCMFC/PRCMFM no obs. Change 38.048.
The z13 processor INCOMPATIBLY CHANGED, the new SMT-MODE RMF 70, and
MXG 34.03 was REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF
(which are written if you have zIIP engines AND have enabled the new
PROCVIEW CORE option for Multi-Threading, even if only one thread is
enabled).
The new zEDC/EADM compression hardware requires MXG 38.05 to support
new metrics.
Availability dates for the IBM products and MXG version required for
error-free processing of that product's data records:
Product's
Availability MXG Version
Product Name Date Required
MVS/ESA 4.1 Oct 26, 1990 8.8
MVS/ESA 4.2 Mar 29, 1991 9.9
MVS/ESA 4.2.2 Aug 15, 1991 9.9
MVS/ESA 4.3 Mar 23, 1993 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30, 1996 14.05
OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02
OS/390 2.4.0 Sep 28, 1997 15.06
OS/390 2.5.0 Feb 24, 1998 15.06
OS/390 2.6.0 Sep 24, 1998 16.04
OS/390 2.7.0 Mar 26, 1999 16.09
OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
z/OS 1.1 on 2064s Mar 30, 2001 19.01
z/OS 1.1 with correct MSU Mar 30, 2001 19.02
z/OS 1.2 Oct 31, 2001 19.04
z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05
z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02
z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03
z/OS 1.4 Tolerate Sep 27, 2002 20.03
z/OS 1.4 Support Sep 27, 2002 20.06
z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02
z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04
z/OS 1.5 Mar 31, 2004 21.21
z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10
z/OS IRD TYPE70PR Mar 11, 2004 *24.10
z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10
z/OS 1.6 - No IFAs Sep 30, 2004 *22.09
z/OS 1.6 - With IFAs Sep 30, 2004 *22.11
z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10
z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10
z/OS IFA data in RMF 79s Sep 30, 2005 23.10
z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03
z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06
z/OS More than 32 LPARs Jan 30, 2006 *24.24
z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24
z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02
z/OS IRD errors corrected May 15, 2006 24.03
z/OS ASUMCEC errors corrected May 15, 2006 *24.24
z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24
z/OS zIIP Processor Support Jun 22, 2006 *24.24
z/OS Dedicated zIIP Support Mar 8, 2008 *26.01
z/OS Dedicated zAAP Support Mar 8, 2008 26.01
z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24
z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10
z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10
z/OS new z10 variables Mar 5, 2008 26.01
z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10
z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05
z/OS 1.11 Sep 2, 2009 27.08
z/OS 1.11 New 30 variables Apr 14, 2010 *28.02
z/OS 1.12 Aug 17, 2010 *28.05
z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03
z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06
z/OS 1.13 Sep 30, 2011 29.03
z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08
z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01
z/OS 2.1 - Most Records support Jul 23, 2013 30.05
z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07
z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03
z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03
z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10
z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08
z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09
REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09
z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02
z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02
z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07
z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07
z/OS 2.3 Many new variables Sep 24, 2017 35.166 35.09*
z/OS 2.3 RMF III Support Sep 24, 2017 35.190 35.09*
z/OS 2.3 type 2 st 2 STOPOVER Sep 24, 2017 35.190 35.09*
z/OS 2.3 type 90 st 38 STOPOVER Sep 24, 2017 35.199 35.09*
z/OS 2.4 Compatible from SMF Manual Sep 2019 37.166 37.07.
z/OS 2.4 Compatible from SMF Manual May 2020 38.105 38.05.
z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04
z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07
z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24
z9EC CPUs - CPUTYPE '2094'x:
with 64-bit z/OS - no change required *24.24
with 32-bit z/OS only: Aug 26, 2006 24.06
z9BC CPUs - CPUTYPE '2096'x:
with 64-bit z/OS - no change required 24.01
with 32-bit z/OS only: Jul 27, 2006 *24.24
z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11
z10 HiperDispatch/Parked Time Mar 3, 2008 *26.10
z196 (INCOMPAT IF GT 64 ENG) Aug 17, 2010 28.05
zEC12 Nov 14, 2012 30.07
z13 non-SMT Mode May 27, 2014 32.05
z13 SMT Mode Change 33.217 Sep 15, 2015 *33.09
z13 SMT Mode NRZIPCPU 34.106 May 10, 2016 34.03
z13 SMT MT=2 CPUZIPTM TYPE70 Mar 21, 2016 35.03
z14 SMF 113 INCOMPAT, ABEND Oct 2, 2017 35.11
z14 113 LPARBUSY missing value Aug 8, 2018 36.07
z14 ZR1 New SMF70MAXPU variable May 8, 2018 36.04
z15 New SMF 113 fields INCOMPAT Nov 18, 2020 37.08
z15 z/VM MFC counters, INCOMPAT Mar 23, 2020 38.02
CICS/CTG V9 Transaction Gateway ?? ?? 2013 31.31
CICS/ESA 3.2 Jun 28, 1991 9.9
CICS/ESA 3.3 Mar 28, 1992 10.01
CICS/ESA 4.1 Oct 27, 1994 13.09
CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07
CICS-Transaction Server V1R1 Sep 10, 1996 14.07
CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06
CICS-TS V1R2 CICS/TS 1.2 Oct 27, 1997 15.06
CICS-TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04
CICS-TS V2R1 CICS/TS 2.1 Mar 15, 2001 18.11
CICS-TS V2R2 CICS/TS 2.2 Feb 9, 2002 19.19
CICSTRAN subtype 1 support only *19.19
CICSTRAN subtype 2 completed *19.08
CICS-TS V2R3 CICS?TS 2.3 Dec 19, 2003
Using UTILEXCL to create IMACEXCL: 21.04
Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04
CICS-TS V2R3 CICS/TS 2.3 Aug 13, 2004 22.04
CICS-TS V3R1 CICS/TS 3.1 Jan 18, 2005 22.22
CICS-TS for Z/OS Version 3.1 Mar 15, 2005
Using UTILEXCL to create IMACEXCL: 22.13
Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22
CICS-TS V3R2 CICS/TS 3.2 Dec 6, 2007 25.11
CICS-TS for Z/OS Version 3.2 Jun 29, 2007 25.03
CICS-TS/3.2 Compressed Records Nov 3, 2007 25.11
CICS-TS/4.1 (CICSTRAN INCOMPAT) Mar 13, 2009 27.01
CICS-TS/4.1 (STATISTICS ST=2) Sep 18, 2009 27.08
CICS-TS/4.2 CICSTRAN/STATISTICS Jun 24, 2011 29.03
CICS-TS/4.2 CICSRDS MNSEGCL=5 Jun 24, 2011 *29.05
CICS-TS/4.2 INVALID STID=116 Jan 31, 2012 *30.01
CICS-TS/5.1 (INCOMPATIBLE) Dec 14, 2012 *30.08
CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013 *30.30
CICS-TS/5.1 MNSEGCL=5 INCOMPAT Jun 17, 2013 *31.03
CICS-TS/5.2 COMPATIBLE CICSTRAN Jun 13, 2014 *31.03
CICS-TS/5.2 INCOMPAT Statistics Jun 13, 2014 *32.03
CICS-TS/5.3 INCOMPAT CICSTRAN Apr 29, 2015 33.04
CICS-TS/5.3 RESOURCE SEGCL=5 Sep 31, 2015 33.09
CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015 33.11
CICS-TS/5.3 GA date Dec 11, 2015 33.33
CICS-TS/5.3 MNSEGCL=5 INPUT ERR Mar 21, 2016 34.02
CICS-TS/5.4 OPEN BETA Aug Aug 11, 2016 34.06
CICS-TS/5.4 OPEN BETA Nov Nov 11, 2016 34.09
CICS-TS/5.4 GA Jun 17, 2017 35.03
CICS-TS/5.5 GA (INCOMPAT) Jan 29, 2018 36.11
CICS-TS/5.6 GA (INCOMPAT) Jun 1, 2020 38.07
CICS-TS/5.6 NEW DATA (COMPAT) Oct 5, 2020 38.09
DB2 2.3.0 Oct 28, 1991 10.01
DB2 3.1.0 Dec 17, 1993 13.02
DB2 4.1.0 Tolerate Nov 7, 1995 13.07
DB2 4.1.0 Full support Sep 11, 1996 14.07
DB2 5.1.0 Tolerate Jun 27, 1997 14.14
DB2 5.1.0 Full support Jun 27, 1997 15.02
DB2 6.1.0 initial support Mar 15, 1999 16.09
DB2 6.1.0 all buffer pools Mar 15, 1999 18.01
DB2 6.1.0 parallel DB2 Mar 15, 1999 19.19
DB2 7.1.0 parallel DB2 Mar 31, 2001 19.19
DB2 7.1.0 corrections Mar 31, 2001 20.06
DB2 8.1 Tolerate, no packages Mar 31, 2004 20.20
DB2 8.1 New Data Packages wrong Mar 31, 2004 21.08
DB2 8.1 Support with Packages Mar 31, 2004 *23.09
DB2 8.1 with all zIIP Variables Sep 30, 2006 24.08
DB2 8.1 +PK47659 Sep 12, 2008 26.08
DB2 9.1 See Change 25.265. Dec 7, 2007 25.11
DB2 9.1 Full Support +PK/56356 Sep 12, 2008 26.08
DB2 10.1 Tolerate Oct 1, 2010 28.06
DB2 10.1 New vars + Compressed Nov 1, 2010 *28.07
DB2 10.1 Invalid Header pre APAR Jan 12, 2011 *28.28
DB2 10.1 IFCID=225 INCOMPAT Sep 23, 2011 *29.07
DB2 10.1 QWHCCV for QWHCATYP=8 Oct 3, 2011 *30.07
DB2 10.1 DBID/OBID decode Jan 21, 2013 *30.30
DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013 *31.04
(ONLY IMPACTS DB2STATS)
DB2 11.1 TOLERATE DB2 V11.1 Jun 21, 2013 30.30
DB2 11.1 DB2STATS QLST CORRECT Jun 21, 2013 31.04
DB2 11.1 SUPPORT NEW VARIABLES Jun 21, 2013 31.08
DB2 11.1 IRLM NEW SEGMENT Jun 21, 2013 32.10
DB2 12.1 COMPATIBLE Oct 5, 2016 34.08
DB2 12.1 NETEZZA CORRECTIONS Oct 5, 2016 34.08
DB2 12.1 QLAC INSERTS DB2ACCT May 15, 2017 35.05*
DFSMS/MVS 1.1 Mar 13, 1993 11.11
DFSMS/MVS 1.2 Jun 24, 1994 12.02
DFSMS/MVS 1.3 Dec 29, 1995 13.09
DFSMS/MVS 1.4 Sep 28, 1997 15.04
DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04
DFSMS/MVS 1.5 ??? ??, 1999 16.04
DFSORT SMF V1R5 Mar 1, 2006 24.02
MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02
MQ Series 1.2.0 May 26, 1998 16.02
MQ Series 2.1.0 Oct 2, 1999 17.07
MQ Series 5.2 Dec 16, 2000 18.10
MQ Series 5.3 Dec 16, 2002 21.05
MQ Series 6.0 Feb 14, 2006 23.23
Websphere MQ Series 7.0 ??? ??, 2009 *28.06
Websphere MQ Series 7.1 MAR 12, 2011 29.03
Websphere MQ Series 8.0 Jun 24, 2011 29.05
Websphere MQ Series 9.1 Mar 20, 2017 35.03
NETVIEW 3.1 type 37 ??? ??, 1996 14.03
NPM 2.0 Dec 17, 1993 12.03
NPM 2.2 Aug 29, 1994 12.05
NPM 2.3 ??? ??, 1996 15.08
NPM 2.4 Nov 18, 1998 17.01
NPM 2.5 Feb ??, 2000 18.02
NPM 2.6 Nov ??, 2001 19.06
RMDS 2.1, 2.2 Dec 12, 1995 12.12
RMDS 2.3 Jan 31, 2002 19.11
TCP/IP 3.1 Jun 12, 1995 12.12
TCP/IP 3.4 Sep 22, 1998 16.04
WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04
WebSphere 6.0 Feb 18, 2006 23.23
WebSphere 7.0 Oct 7, 2010 28.06
WebSphere 8.0 Jul 17, 2011 29.05
DOS/VSE POWER V6.3.0 Dec 19, 1998 16.08
VM/ESA 2.0 Dec 23, 1992 10.04
VM/ESA 2.1 Jun 27, 1993 12.02
VM/ESA 2.2 Nov 22, 1994 12.06
VM/ESA 2.3 Jun 1, 1998 16.08
VM/ESA 2.4 Mar 1, 2001 19.03
z/VM 3.1 Mar 1, 2001 19.03
z/VM 3.1 DATABYTE=0 May 2, 2002 20.02
z/VM 4.2 ?? May 2, 2002 20.02
z/VM 4.4 Jan 22, 2005 22.22
z/VM 5.1 Jan 22, 2005 22.22
z/VM 5.2 Jan 22, 2006 24.01
z/VM 5.3 TOLERATE Jun 7, 2007 25.05
z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08
z/VM 5.4 (COMPATIBLE) Sep 12, 2008 *27.01
z/VM 6.1 (NO CHANGES) Jul 7, 2008 27.01
z/VM 6.2 Dec 2, 2011 29.04
z/VM 6.3 INCOMPATIBLE Jul 23, 2013 31.05
z/VM 6.3 z/13 Jan 23, 2016 33.33
z/VM 6.4 SYTLCK Incompat Apr 26, 2016 34.04
z/VM 6.40061802 ABEND Jan 17, 2019 37.02
z/VM 7.1 ABEND Feb 14, 2019 37.02
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.07
IMS log 15.1 NO CHANGES Mar 1, 2018 35.07
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
The Monitor for DB2 Version 4.0 22.10
The Monitor for DB2 Version 5.0 30.02
The Monitor for CICS/ESA 1.2 - 12.12
The Monitor for CICS/ESA 1.3 - 15.01
The Monitor for CICS/ESA 2.0 - 15.06
The Monitor for CICS TCE 2.1 - 20.04
The Monitor for CICS TCE 2.2 - 20.335, 21.134 21.04
The Monitor for CICS TCE 2.3 including CICS/TS 3.1 22.08
The Monitor for CICS TCE 3.2 (almost all) 25.11
The Monitor for CICS TCE 3.2 (almost all) 27.01
The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2) 29.07
TMON/CICS 3.4 (for CICS/TS 5.1) 30.30-32.12
(Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)
TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099) 33.04
TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195) *33.09
TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257 34.08
The Monitor for MVS/ESA 1.3 - 12.05
The Monitor for MVS/ESA 1.5 - 12.05
The Monitor for MVS/ESA 2.0 - 15.09
The Monitor for MVS/ESA 3.0 - 19.19
TMON/MVS Version 4.4 32.04
Candle
Omegamon for CICS V200 User SMF 12.05
Omegamon for CICS V300 User SMF 13.06
Omegamon for CICS V400 User SMF 16.02
Omegamon for CICS V400 type 110 segments 16.02
Omegamon for CICS V500 User SMF 18.01
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for IMS V300 (ITRF) 14.04
Omegamon for IMS V550/V560 (ITRF) 25.05
Omegamon for MVS V300 13.05
Omegamon for MVS V400 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for VTAM V400 15.15
Omegamon for VTAM V500 18.08
Omegamon for SMS V100/V110 12.03
CA
ACF2 6.2 was 16.04 but ABEND, ACSMFREL=0 May 2018 36.05
ASTEX 2.1 14.04
IDMS 18 32.05
IDMS 19 (INCOMPAT after PTF R084146 Change 34.164) 33.05
NETSPY 4.7 14.03
NETSPY 5.0 14.03
NETSPY 5.2 16.05
NETSPY 5.3 18.03
NETSPY 6.0 20.10 20.305
NETSPY 7.0 20.10 20.305
SAR/VIEW R11 23.07 23.196
BMC, was Boole & Babbage
APPTUNE V11R2 SMF 102 33.11 33.264
IMF 3.1 (for IMS 5.1) 12.12
IMF 3.2 (for IMS 6.1 only) 15.09
IMF 3.2 (for IMS 5.1 and 6.1+) 16.04
IMF 3.3 (for IMS 7.1 and 8.1) *22.08
IMF 4.1 (for IMS 9.1) *26.02
IMF 4.4 (for IMS 9.1) *31.08
IMF 4.5 (for IMS 11.1) (No change since 4.4) 31.08
IMF 4.6 a/k/a Mainview IMS *31.08
IMF 5.1 a/k/a Mainview IMS *34.01
IMF 5.2 a/k/a Mainview IMS 34.01
IMF 5.3 a/k/a Mainview IMS 35.03
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2, 5.3, 5.4 33.01
Mainview for CICS Version 6.5 (CICS/TS 5.1) 30.30
Mainview for CICS Version 6.4 (CICS/TS 4.2) 30.04
Mainview for CICS Version 6.1 26.26
Mainview Auto Operator data file 28.28
Mainview for DB2 THRDHIST file 20.20
Mainview for TCP/IP 20.20
Mainview for IP 34.??
Mainview for Batch Optimizer 19.19
Memorex/Telex
LMS 3.1 12.12A
Oracle V9, V10 24.06
SYNCSORT
2.1 33.05
1.4 33.08
Amdahl
APAF 4.1, 4.3 16.08
Velocity Software
XAMAP 3.4 22.10
XAMAP 3406 24.03
XAMAP 3.7 27.10
XAMAP 4.1 Now Renamed to ZVPS 4.1 29.07
XVPS 4.2 31.06
ZVPS 5.4 *33.07
V. Incompatibilities and Installation of MXG 38.10.
1. Incompatibilities introduced in MXG 38.10:
a. Changes in MXG architecture made between 38.10 and prior versions
that can introduce known incompatibilities.
IF YOU HAVE MEMBER E2TY70 IN YOUR USERID.TAILORING SOURCE LIBRARY,
YOU MUST CHANGE _LTY70 to _WTY70 in that member. CHANGE 38.105.
The error before this correction will be:
ERROR: DATA SET "PDB.TYPE70" was not specified on the DATAA stmt.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
An MXG Version never "expires" nor "goes out of Support". When
you put in a new product/subsystem/Release/APAR that incompatibly
changed its records then you must install the current MXG Version
or at least be using the minimum level of MXG that is currently
documented in the preceding list in section IV.
COSMETIC Some Changes will start with COSMETIC. This indicates
that that change only alters a displayed value or may
be a spelling error in a label, but it is "cosmetic"
in that it ONLY affected the display, and the output
data sets created are NOT impacted by this change.
VI. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
See also member INDEX, but it may be overwhelming.
VII. Changes Log
--------------------------Changes Log---------------------------------
You MUST read each Change description to determine if a Change will
impact your site. All changes have been made in this MXG Library.
Member CHANGES always identifies the actual version and release of
MXG Software that is contained in that library.
The CHANGES selection on our homepage at http://www.MXG.com
is always the most current information on MXG Software status,
and is frequently updated.
Important changes are also posted to the MXG-L ListServer, which is
also described by a selection on the homepage. Please subscribe.
The actual code implementation of some changes in MXG SOURCLIB may be
different than described in the change text (which might have printed
only the critical part of the correction that need be made by users).
Scan each source member named in any impacting change for any comments
at the beginning of the member for additional documentation, since the
documentation of new datasets, variables, validation status, and notes,
are often found in comments in the source members.
Alphabetical list of important changes in MXG 38.10:
Dataset/
Member Change Description
ANAL95TH 38.018 PROC TABULATE 95th pct response stats CICSTRAN/JOBS.
ANALATNC 38.005 Report Code for Latent Demand analysis, examples at
https://www.mxg.com/downloads/Latent_Demand
ANAL119 38.073 Cleanup and removal of a typo.
ANAL119 38.150 Errors corrected if you didn't have //IPHOSTS file.
ANALAVAI 38.183 Enhanced reporting on availability.
ANALID 38.010 ERROR "OPTORG4" if you changed SMFAUDIT to NO.
ANALINIT 38.083 Enhanced JOB EXEC/QUEUED/HELD/etc analysis
ANALSIIS 38.009 Analysis of Store Into Instruction Stream enhanced.
ANALSIIS 38.149 SM113TM replaced by TIMESTMP for better match up.
ASCII 38.091 MXG on Windows, AV Products, LOCK NOT AVAILABLE
ASMRMFV 38.064 Support for APAR OA58759, caused Condition Code 4.
ASMRMFV 38.082 ASMRMFV FDF Support for new tables.
ASMRMFV 38.128 Field Data Filter FDF Support adds XCFG3, FDF fix.
ASMRMFV 38.181 New Field Data Filter support for CFIG3 table.
AUTOINST 38.054 ASCII Unique INSTREAM needed for Concurrent Sessions.
BLDSMPDB 38.081 MXG 38.01 only. BLDSMPDB WEEKLY JOB ABENDS, typo.
BUILDIMS 38.001 All selections now work, new INPUTCLNR variable.
CMF+RMF 38.095 Variable CMFPROD to select CMF vs SMF if both are on.
CONFIMXG 38.004 MXG 37.37 only, 1024 should be OPEN_ED=1047.
DOCVLONG 38.012 Creates a DOCVLONG with all DOCVER data on one line.
FORMATS 38.003A R744HOPM $MG074HO new '50x:CL5 10GBIT/S CEE ROCE'.
FORMATS 38.020 Support for SMF73CPT 33/34 connection types.
FORMATS 38.080 Support for z15 T02 values in $MGRMIPS format.
MANY 38.105 Support for May 2020 SMF Manual Changes zOS 2.4.
READDB2 38.147 DB2GBPAT now recognized, ACCTSORT=NO now works.
SAS 38.087 ERROR: Utility File Open Failed PROC MEANS/SUMMARY.
TYPE102 38.019 Support for DB2 APAR PH18739 var QW0389IT in T102S389
TYPE102 38.077 SMF102 IFCID 143/144 increase length QW014xUR.
TYPE102 38.117 Support for DB2 APAR PH15111 for IFCID 365. SMF 102.
TYPE102 38.179 Support for DB2 ZPARM MFA_AUTHCACHE_UNUSED_TIME.
TYPE110 38.060 Long Running CICS Trans, SMF 110 every hour.
TYPE110 38.060 SET MONITOR FREQ hourly CICSTRAN for long runners.
TYPE110 38.084 Support for CICS/TS 5.6 (INCOMPAT, FIELDS INSERTED).
TYPE110 38.099 CICS Statistics Records revisions.
TYPE110 38.114 New CICSRDUR/URIMAP, CICSRDWB/WEBSVC datasets.
TYPE110 38.114 New CICSRDUR/URIMAP, CICSRDWB/WEBSVC datasets.
TYPE110 38.168 Support for CICS/TS 5.6 STID=43, 46, and new STID=61.
TYPE112 38.040 OMEGAMON TEMS St 38 INVALID ARGUMENT LENGTH CHANGED.
TYPE113 38.035 TYPE113 Counters EXTND247/252/264/265 now labeled.
TYPE116 38.037 MQMACCTQ/MQMACCT/MQCFSTAT/MQMQUEUE/ revisions.
TYPE119 38.068 Support for Comm Server SMF 119 Subtype 11 ZERT data.
TYPE119 38.156 Tokens for TYP11924/11925 were not in _N119.
TYPE123A 38.061 Datetime values were 2080 instead of 2020, MXG error.
TYPE16 38.164 Support for APAR PH03207 for DFSORT ZSORT stats.
TYPE30 38.093 Support for APAR OA59126, dataspaces variables.
TYPE30_6 38.072 Revised deaccumulate for accumulated subtype 6.
TYPE38 38.178 Support for z NetView 6.3 Subtype 4 Command stats.
TYPE42 38.011 Support for APAR OA57718, zHyperLink TYPE42DS stats.
TYPE42 38.067 Yet another TYPE42 invalid LENSR in subtype 5 42's.
TYPE42 38.079 Support for APAR OA59541 for Type 42 Subtype 27.
TYPE50 38.177 VSAM Tuning data sets were misaligned.
TYPE62 38.041 Support for APAR OA57105, adds JOBID SYSPLEX.
TYPE64 38.041 Support for APAR OA57105, adds JOBID SYSPLEX.
TYPE70 38.031 Support for APAR OA56683 SMFBOOST System Recovery
TYPE70 38.055 PCTMVSBY incorrect after 37.123. (NOT PCTCPUBY!!!).
TYPE7072 38.103 MXG 38.03/38.04 TYPE7072 fails if //PDB is on TAPE.
TYPE7072 38.106 Support for APAR OA59330 new variables in TYPE7002:
TYPE7072 38.126 SMF sysplex data with SMF Logger INTERLEAVES ALL SMF.
TYPE73 38.038 Variable SHIFT was not populated.
TYPE74 38.089 Support for new EADM variables in TYPE7410.
TYPE74 38.098 Support for SMF 74 CMF from BMC PTF BQM12658/59.
TYPE74 38.152 Support for APARs OA58724/58729 new Monopoly in ST=4.
TYPE78 38.097 Support for APAR OA56684 TYPE78IO EADM/SCM variables.
TYPE80A 38.017 INPUT EXCEEDED due to a HOME segment with no data.
TYPE83 38.090 SMF 83 ST 3 INPUT STATEMENT EXCEEDED.
TYPE85 38.100 Support for SMF 85 OAM Cloud Tier.
TYPE89 38.034 APAR OA59002 corrects TYPE89 var SMF89UZT values.
TYPEBE97 38.036 Support for BETA (93) and BETA97 Version 7.1.0
TYPEBETA 38.036 Support for BETA (93) and BETA97 Version 7.1.0
TYPECIMS 38.058 CIMS/IMF CIMSDBD/DB2/MQ Zero Obs 37.37-38.02
TYPECMFV 38.063 CMF VSAM INVALID DATA messages, wrong informat.
TYPEDB2 38.062 Support DB2 APAR PI92652,PI82191 and DPAGE support.
TYPEDB2 38.075 Support for APAR PH14037 DB2ACCTP QPACPKID truncated.
TYPEDB2 38.096 Support for APAR PI98851 new variables DB2STATS.
TYPEDB2 38.117 Support for DB2 APAR PH16111 SMF 100 Locations.
TYPEIAM 38.006 Support for IAM 9.3 Spin 3 INCOMPATIBLE inserts.
TYPEIDMS 38.003 IDMSTAS UOW/NETNAME added, TASUFLD1-3 corrected.
TYPEIMS 38.014 Support for APAR PH14569/PH21001 IMS 22 log record.
TYPEMVCI 38.116 Support for BMC Mainview for CICS 7.1 (COMPATIBLE).
TYPERMFV 38.124 Many dupes in ZRBXCG/XCP/XCS datasets.
TYPESARR 38.088 Support for CA View SARR SMF Subtypes 34 and 35.
TYPESVIE 38.057 Support for SYSVIEW Subtype 2 record one min detail.
TYPETMS5 38.002 Variables BYTEPRC and BESKEY added to TMS/DSNBRECD.
TYPETPMX 38.039 Support for new INREI and JCLJJ in TYPETPMX.
TYPETPMX 38.102 Support for Thruput Manager TMT7123/TMT7124 Jul 2020.
TYPEVMXA 38.019 z/VM VXAPLSLM variable SHARERAM zero if not RHEL8.
TYPEVMXA 38.047 z/VM MONWRITE 6.4.19.1 z15 INCOMPATIBLE.
TYPEXAM 38.059 zVPS XAMCUV LCPUID=96 Totals records now deleted.
TYPEXCOM 38.069 XCOM input did not skip the 461 bytes added in 12.0.
UCICSCNT 38.085 Enhanced counts/bytes for SMF 110 including STIDs.
UTILBLDP 38.008 Error after Change 37.149 if first USERADD is IDMS.
UTILBLDP 38.157 BUILDMXG fails if you didn't specify OUTFILE=.
UTILEXCL 38.180 Optional "Candle" CICS segment kept wrong variables.
UTILROLL 38.065 UTILROLL example to combine PDBs created every 4hr.
VMACSMF 38.033 SMF Signature Type 2 St 1/2 MANY BACK2BACK LOG msgs
VMACSMF 38.051 SAS FTP Access Method &MXGABND=1 set to print errors.
VMXG70PR 38.142 Support for ASUM70WK and ASUM70P3 to keep full hours.
VMXGDUR 38.145 If interval LT actual druatm, warning printed.
VMXGINIT 38.046 SAS Option REUSE=YES is forced to REUSE=NO DEFAULT.
VMXGOPTR 38.056 ANALHSM caused Error "SAS Option Name OPTIONS 1".
TYPE110 38.205 SMF 110 ST 1 MNSEGCL=5 INPUT STATEMENT EXCEEDED.
TYPE42 38.204 TYPE 42 ST 5 incorrect MXG logic INPUT EXCEEDED.
ASUM113 38.201 New z/15 EXTND256-EXTND287 were not kept in ASUM1131.
TYPEBETA 38.200 Support for BETA93 and BETA97 new data and updates.
TECHNOTE 38.199 Compressed SMF 110 expensive without EXITCICS on z/OS
ASMVVDS 38.197 Updates to read VVDS records and output to file/SMF.
See member CHANGESS for all changes ever made to MXG Software, or
the CHANGES frames at https://www.mxg.com.
Inverse chronological list of all Changes:
NEXTCHANGE
====== CHANGES THRU 38.213 ARE IN MXG 38.10 DATED Nov 23, 2020 ========
Change 38.213 New DB2STAT1 (IFCID=0002) variables:
VMACDB2 QISTINPR ='IAG2*PIPE*RENABLE*ATTEMPTS'
Nov 21, 2020 QISTINPE ='IAG2*PIPE*RENABLE*SUCCESS'
QISTCONDLKF='CONDITIONAL*LOCK*FAILURES'
QISTRETRYLK='UNCONDITIONAL*LOCK*RETRIES'
Change 38.212 In the TYPE70EN dataset, when the engine was parked for
VMAC7072 the full interval, PCTCPUBY and PCTMVSBY could be small
Nov 20, 2020 negative values due to resolution differences in DURATM
with 2 decimals and SMF70PAT with 6. Now, the negative
value is replaced with zero.
Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
Change 38.211 New variables added in Oct 25, 2020 SMF Manual:
VMAC7072 -Dataset TYPE72TR new variables
VMAC89 R723GMLT='GGMN/GGMX*ARE IN*MSU/HR?'
VMAC78 R723GMLZ='ZIP*INCLUDED*GGMN*GGMX?'
Nov 20, 2020 -Dataset TYPE892 new variables
BOOSTACTIVE BOOSTCLASS (were in TYPE89 but not TYPE892)
-Dataset TYPE78VS new variables
R782FLG='RUCSA*IS*DEFINED?'
R782RUCA='RUCSA*ADDRESS*BELOW*16M'
R782RUCS='RUCSA*SIZE*BELOW*16M'
R782ERUCA='RUCSA*ADDRESS*ABOVE*16M'
R782ERUCS='RUCSA*SIZE*ABOVE*16M'
Change 38.210 New variables added to TYPE9040 dataset SMF 90 ST 40:
VMAC90A SMF9040ID='ID OF*START*REQUESTOR'
Nov 19, 2020 SMF9040DU='RECOVERY*PROCESS*BOOSTS*DURATION'
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.209 zERT variable SMF119SC_TLS_PROT_VER format $MG119PX now
FORMATS decodes '0304'x as TLSV1.3.
Nov 19, 2020
Thanks to Thomas Liu, ANZ, AUSTRALIA.
Change 38.208 Variable RESPAVG is added to ASUMCICS/ASUMCICT/TRNDCICS
ASUMCICS as it already existed in ASUMCICX. Variable IRESPTM is
ASUMCICT the SUM of all transaction response times.
TRNDCICS
Nov 18, 2020
CHANGE 38.207 If you are rolling up interval data to weeks and your
TECHNOTE week does not start on Monday you can use the STARTDAY
VMXGDUR macro variable to start weeks on the day of the week
TRND**** you choose by inserting this line in IMACINIT or any
Nov 18, 2020 code where you are using VMXGDUR to summarize data to
a week (all of the TRND**** members).
%LET STARTDAY=day 1 of MON TUE WED THU FRI SAT SUN
Change 38.206 Format MG116CT for TYPE116 variable QCSTCHTY in dataset
FORMATS MQCHININ had 9='9:DLUSSCR' typo, now is 9='9:CLUSSDR'.
Nov 18, 2020
Thanks to Rob Hollingum, HSBC, ENGLAND.
Thanks to Matt Crawford, HSBC, ENGLAND.
Change 38.205 SMF 110 St 1 MNSEGCL=5 Resource Record extra 14 bytes
VMAC110 caused INPUT STATEMENT EXCEEDED RECORD LENGTH error.
Nov 18, 2020 WHILE (LENLEFT GT 0) changed to WHILE (LENLEFT GT 140).
You can circumvent with this added to your //SYSIN:
%LET IHDR110= %QUOTE(IF MNSEGCL=5 THEN DELETE;) ;
Thanks to Martha A. Knapik, Progressive, USA.
Thanks to Craig S. Bigler, Progressive, USA
Thanks to Diana L. Laskovich, Progressive, USA.
Change 38.204 Type 42 St 5 MXG logic to correctly calculate SRLEN was
VMAC42 exposed to INPUT STATEMENT EXCEEDED LENGTH error because
Nov 17, 2020 SRLEN=160 is valid, but the optional SYNC segment length
Nov 19, 2020 is included in SRLENGTH=OFFVOL-OFFSR which misled to
the incorrect recalulation, which is now bypassed.
Thanks to Andrew Petersen, DXC, AUSTRALIA.
Change 38.203 CHANGE 37.267 added an ERROR:INCORRECT ENCODING message
VMXGINIT on the log, but the code was inserted before &OPSYS was
Nov 17, 2020 populated, so the message was never printed.
Thanks to John Compton, World Programming, ENGLAND
Change 38.202 Variable DCDCTYPE='COMPRESSION*TYPE' was not kept in the
VMACDCOL DCOLDSET dataset.
Nov 16, 2020
Thanks to Heimir Hauksson, Barclays, ENGLAND.
Change 38.201 The new z/15 TYPE 113 counters EXTND256-EXTND287 were not
ASUM113 kept in the PDB.ASUM1131 dataset. Only EXTND264/EXTND265
Nov 11, 2020 are described, and neither is used in any calculations.
but now, all will exist, and be populated if on z z/15.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 38.200 Support for BETA 93 and BETA 97 new data and corrections:
EXTYBETO -New variables added to dataset BETA50:
EXTYBETU BETAINDI='IP*ADDRESS*INDICATOR'
FORMATS BETAIFLGS='ADDRESS*TYPE*INDICATOR'
VMACBE97 BETAHOSTPORT='HOST*PORT'
VMACBETA BETASERVPORT='SENDING*PORT OF*SERVER'
VMXGINIT BETAIPHOST ='HOST*IP*ADDRESS'
Nov 17, 2020 BETAIPCLIENT='WEB*BROWSER*CLIENT*IP'
BETAIPSERV ='WEB*APP SERVER*IP'
BETAIPSERVI ='WEB*INTERNAL*FORMAT'
BETALUSED='LDD*TABLE*USED?'
BETALJOBN='MASK USED*JOB*NAME*FIELD'
BETALSTPD='MASK USED*STEP*NAME*FIELD'
-Two new BETA 93 datasets from subtype 43
DDDDDD DATASET DESCRIPTION
TYBETO BETA43 ST43 ARCHIVE DATE CHANGE
TYBETU BETA43DS ST43 CHANGE DATASETS
-Corrections to BETA93 subtypes 50 and 55.
-Corrections to BETA97 subtypes 0, 22, 51 and 55.
Thanks to Andreas Menne, Finanz Informatik, GERMANY
Change 38.199 Processing compressed SMF 110 Records without the INFILE
TECHNOTE decompression exit (EXITCICS) is VERY expensive on z/OS.
Uncompressed records were 7.4GB, compressed were 1.5GB.
STEPNR CPUTM SELAPSTM EXCP EXCP
3390 TAPE
EXTRACT ONLY 110.1 0:03:14.74 0:03:33.51 5291 703214
DFH$MOLS 0:01:34.43 0:03:01.77 221 692328
READ UNCOMPRESSD 0:11:51.52 0:20:12.10 4171 1282837
READ COMP NO EXIT 5:09:48.94 7:00:33.55 4176 832236
READ COMP USE EXIT 0:12:32.82 0:27:51.71 4181 832236
Change 38.198 GOUT suppressed when running WPS since WPS does not
GRAFCEC support graphic catalogs.
GRAFWRKX
Nov 6, 2020
Change 38.197 -Updates to ASMVVDS program that reads VVDS records with
ASMVVDS output to a sequential flat file and/or output as SMF
JCLASMXG records.
Nov 4, 2020 -Default setting of 0 for @UCB31 (UCBs below 16MB) line
changed to a setting of 1 (UCBs above 16MB) which is more
appropriate for modern z/OS systems.
-Two assembly errors are also fixed.
-NOTE: ASMVVDS must be APF authorized. That requires parm
of AC(1) in program binder step and the load library must
also be authorized.
-See ASMVVDS source member for full installation and usage
instructions.
-Sample JCL for assembly and linkedit of ASMVVDS was added
to member JCLASMXG (which Assembles all MXG ASM program).
Thanks to Victor Li, Atos, Hong Kong
====== CHANGES THRU 38.196 ARE IN MXG 38.09 DATED Nov 4, 2020 ========
Change 38.196 New parameter COMPANY added with default of MXG to allow
GRAFWLM you to insert your COMPANY NAME in titles. The Parameter
NOV 4, 2020 list was sorted into alphabetic order..
Change 38.195 ERROR: WORK.CICSEXCE.DATA does not exist if SUPPRESS=110
UTILBLDP and BUILDPDB NE 'NO' were specified in your invocation;
Nov 4, 2020 the null _SCICEXC, _SCICSYS, _INTCICS macros were not
created, causing the ABEND.
Thanks to Jim S. Horne, Lowe's Companies, USA.
====== CHANGES THRU 38.194 ARE IN MXG 38.09 DATED Nov 2, 2020 ========
Change 38.194 Support for dataset TYPE80TK new variables:
VMAC80A TOKMACCOUNT TOKMP9ACTION TOKMTSSTATUS BUILDING TOKMDEPT
NOV 2, 2020 TOKMEMPNO TOKMLANG TOKMPRINTER TOKMPROVINCE
TOKMUSERTYPE TOKMLDAPPROF
Thanks to Gaetan Martel, INTACT, CANADA.
Thanks to Serte-TI Belanger, INTACT, CANADA.
Change 38.193 Correction for IDMSTAS variables TASUFLD1-TASUFLD3 input;
VMACIDMS the extra 8-bytes do not exist in TASTTYPE='40'x records.
OCT 31, 2020
Thanks to Dennis Jamiel, Travelport, USA.
Thanks to Marcos Villasenor, Travelport, USA.
Change 38.192 Support for ThruPut Manager TMT7124 update, which adds.
VMACTPMX these variables to dataset TYPETPMX:
OCT 30, 2020 TPMTMNOM='NUMBER*OF THIS*RECORD'
TPMTMNON='TOTAL*NUMBER OF*RECORDS'
TPMTMAPP='KNOWN APPLICATIONS'
TPMTMELR='ELAPSED*TIME ON*READER'
TPMTMCAC='CATALOG*CPU*TIME'
TPMTMCAE='CATALOG*ELAPSED*TIME'
TPMTMDJC='DAL/JAL*CPU TIME''
TPMTMDJE='DAL/JAL*ELAPSED*TIME''
TPMTMSSC='DTMSSREQ*CPU TIME'
TPMTMSSE='DTMSSREQ*ELAPSED*TIME'
TPMTMUXC='USER EXIT*CPU TIME'
TPMTMUXE='USER EXIT*ELAPSED*TIME'
TPMTMJ2C='JES2 INTERFACE*CPU TIME'
TPMTMJ2E='JES2 INTERFACE*ELAPSED*TIME'
TPMTMTLC='TAPE*LIBRARY*CPUT TIME'
TPMTMTLE='TAPE*LIBRARY*ELAPSED*TIME'
TPMTMANA='ANALYSER*START*DATETIME'
Change 38.191 Support for CICS optional HUMTRAN field INPUT $EBCDIC8.
UTILEXCL Change 38.115 had added support for $16 and $24 INPUTs.
OCT 29, 2020 Variable HUMTRAN is length $24 with either INPUT.
Thanks to Dave Baker, HCA Healthcare, USA.
Thanks to Lisa Gascoigne, HCA Healthcare, USA.
Change 38.190 The report of all job activity only printed the first 500
ANALJOBE lines of the report; now all lines are printed.
OCT 28, 2020
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 38.189 Format $MG119SP decodes variable SMF119SC_SASECPROTOS:
FORMATS VALUE $MG119SP /*$MG119SC FORMAT FOR VMAC119*/
VMAC119 '00'X='00X:NO PROTECTION'
Oct 28, 2020 '80'X='80X:TLS/SSL'
'40'X='40X:SSH'
'20'X='20X:IPSEC'
;
Thanks to Joe Faska, DTCC, USA.
Change 38.188 -New MXG variables EXECVEL (Execution Velocity) and
ADOCRMFV PERFINDX (Performance Index) are added to PDB data set
ASMRMFV ZRBRCDT (RMF III RESPTIME SERVICE CLASSES).
VMACRMFV -New MXG variable EXECVEL (Execution Velocity) added to
Oct 27, 2020 PDB data set ZRBRCDX (RMF III RESPTIME REPORTING
CLASSES).
-If for some reason a Response Time Distribution Array was
not present in the RCDG3 RMF III table the corresponding
Service Class or Report Class period would not be output
to the PDB.
-Rarely RMF III may generate an SSHG3 (Sample Set Header)
table where the sample begin datetime and sample end
datetime are the same. Effectively this is a null table
with zero samples. With this condition an Abend S002 in
ASMRMFV is possible.
-ASMRMFV will now detect this condition, then issue a new
RMFV023W message:
**WARNING: SAMPLE START/STOP DATE TIMES ARE IDENTICAL.
ENTIRE SAMPLE SET WILL BE SKIPPED***
and the entire SSHG3 table will be skipped and output to
the RMFSKIP DD file (if present).
-This condition may be due to the timing sequence in a
system shutdown process. Both RMFGAT and RMF Started
Tasks should be completely terminated before the process
continues.
-Warning message RMFV022W was not formatted correctly.
-Warning message RMFV023W was duplicated.
-Section 12 Messages in ADOCRMFV updated to include the
new RMFV023W message.
-TUTORIAL 1:
Execution Velocity is a WLM measurement based on system
states which are continuously collected by sampling.
System states describe when a work request uses a system
resource (a using state) and when it must wait for it
because it is used by other work (a delay state).
# Using Samples
Execution Velocity = --------------------------- * 100
# Using + # Delay Samples
Execution Velocities thus range from 0 to 100.
A value of 100 means the unit of work is running with no
WLM DETECTED delays. A value of 0 means the that unit of
work is not running at all either because it has no
access to the resources needed or it is idle.
The Execution Velocity formula does not include the
unknown state. This state includes delays not tracked by
WLM, such as locks or enqueues. So an Execution Velocity
of 100 does not necessarily mean the work unit is running
totally unencumbered.
-TUTORIAL 2:
Performance Index (PI) is a calculation of how well work
is meeting its WLM defined goal.
For work with response time goals, the Performance Index
is the actual response divided by the goal response.
For work with velocity goals, the Performance Index is
the goal velocity divided by actual velocity.
A Performance Index of 1.0 indicates the Service Class
period is exactly meeting its goal. A Performance Index
greater than 1 indicates the Service class period is
missing its goal. A Performance Index of less than 1.0
indicates the Service Class period is beating its goal.
Work with a Discretionary goal is defined to have a fixed
Performance Index of .81 . Service Classes for System
address space have no Performance Index as they do not
have goals.
Each Service Class period has a Sysplex and a Local
Performance Index.
The Sysplex Performance Index represents the performance
of a Service Class period across all systems in the
Sysplex. The RMF III SYSSUM report shows this assuming
it has access to all RMF III VSAM data sets for the
Sysplex in the time period being reported.
The Local Performance Index represents only the
performance on a single local system. PERFINDX in MXG
is a Local Performance Index.
Thanks to Rodger Foreman, Black Knight, Jacksonville, FL, USA
Thanks to Len Shenfield, ADP, Roseland, NJ, USA
Change 38.187 -If you suppressed CICSSTAT that also unintentionally
UTILBLDP suppressed ASUMUOW and ASUMCICX. Now if you want to
Oct 27, 2020 suppress ASUMUOW ASUMDBAA or ASUMDBSS you can add them to
the SUPPRESS= parameter by name. In the case of ASUMUOW
this also suppresses ASUMCICX but if you did not supress
CICSTRAN then ASUMCICS is substituted. These four members
CICSSTAT ASUMUOW ASUMDBAA and ASUMDBSS are all resource
intensive, and if you don't use them you can save those
resources by suppressing them.
-If you suppressed ID and used BUILDPDB=JES3 you got an
error message that the type of VIEW could not be
determined. There were many other spots which looked only
for YES or NO that were fixed. The value of BUILDPDB is
now validated and if it is not blank, NO, YES, or JES3
UTILBLDP will end with error messages.
Change 38.186 MXG estimate of DOWNTM prior to an IPL used the PREVTIME
VMAC0 of the last record, but what was needed was the PREVTIME
VMAC90A of the ID=0 record, and the IPLTIME of the ID=0 is now
Oct 26, 2020 retained in TMP0TIME and used for the IPLTIME in the
DOWNTM calculation in the ID=90 ST=10 IPL SRM record.
-Processing ID=0 record, the GMTOFF was off by one second.
Thanks to Tore Hansson, IBM Services, NORWAY.
Change 38.185 MXG 38.03 Change 38.051 set MXGABND=1 for missing SMFTIME
VMACSMF value when using the SAS FTP Access Method, because we
VMXGINIT have seen that associated with an FTP "hang" until it was
Oct 21, 2020 cancelled, and by forcing an ABEND you can avoid the hang
and if you've pointed the LOG option to a file, you can
see if there were other error conditions. But MXGABND is
is macro variable used in many members so you can choose
an ABEND instead of ERROR messages (like TYPE110, where
some sites want an ABEND alert when EXCLUDED FIELDS are
detected). In this case, the CPUTM GT ELAPSED condition
in TYPE110 tested MXGABND GT 0 and cause an unwanted
ABEND. Now, macro variable SMFMISS is created and can be
used to cause the abend when SMFTIME is missing using the
FTP access method, using %LET SMFMISS=NNN; in your SYSIN
to cause ABORT ABEND NNN instead of the ERROR and a hang.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 38.184 MXG 38.08. ERROR: File WORK.PDBTYPE70.DATA does not exist
VMXG70PR if you tailor and invoke %VMXG70PR with no PDB= argument.
Oct 19, 2020 We recommend you always use %INCLUDE SOURCLIB(ASUM70PR);
instead of putting a tailored VMXG70PR in USERID because
IBM changes may require incompatible changes in VMXG70PR,
but we can protect ASUM70PR from the need for change.
In general, if there is an ASUMxxxx that invokes VMXGxxxx
its always safer to use the ASUMxxxx member.
Thanks to Otto A. Burges, OPM, USA.
Change 38.183 -The detail report did not correctly report outages. The
ANALAVAI beginning was the beginning of the interval when it came
Oct 29, 2020 back up and the ending was the time when that interval
Nov 4, 2020 ended.
-A new month-to-date summary report was added and the
availability is now calculated as the
(uptime-outagetime + scheduledtime)/86400*100;
-Changed Parameter values:
CYCLE=M1 has not been changed but a null value will
let you accumulate many months of data.
- New Parameters:
MINOUTAGE=5 number of outage seconds to ignore
OUTCODE= a stub of code just after PCTAVAIL is
calculated
SCHEDULED= stub of code allowing you to specify
scheuled outages for each app.
see doc and examples in member.
Update in MXG 38.09 dated Nov 4, 2020:
If you were not very careful building schedules and
outages, duplicate obs could skew percentages. SORTS with
NDDUP added to eliminate duplicate obs. Also outages were
not carried into month totals resulting in availability GT
100%.
An Example of invoking %ANALAVAI:
When building schedules it is critical that you always
output either outages or scheduled for each app with a
schedule.
%ANALAVAI(
COMPANY=YOUR COMPANY,
SCHEDULED=
IF APP IN('SYSA','SYSB','SYSC')
AND WEEKDAY(DATE) = 1 THEN DO;
IF APP IN('SYSB','SYSA')
AND BEGSKED GE '03:00'T
AND ENDSKED LE '03:30'T
THEN OUTPUT SCHEDULED;
IF APP='SYSC'
AND BEGSKED GE '03:00'T
AND ENDSKED LE '04:00'T
THEN OUTPUT SCHEDULED;
ELSE OUTPUT OUTAGES; *critical statement;
END;
ELSE IF APP = 'PRODCICS' THEN DO;
IF WEEKDAY(DATE) NE 7
AND BEGSKED GE '23:15'T
AND ENDSKED LE '06:05'T
THEN OUTPUT SCHEDULED;
ELSE IF BEGSKED GE '23:15'T
AND ENDSKED LE '07:05'T
THEN OUTPUT SCHEDULED;
ELSE OUTPUT OUTAGES; *critical statement;
END;
ELSE IF APP = 'ADABAS' THEN DO;
IF WEEKDAY(DATE) EQ 1
AND BEGSKED GE '23:15'T
AND ENDSKED LE '02:05'T
THEN OUTPUT SCHEDULED;
ELSE OUTPUT OUTAGES; *critical statement;
END;
ELSE OUTPUT OUTAGES; *required final statement;
,
APP1=SYSB/SYSC IS UP/JES2,
APP2=SYSA/SYSA IS UP/JES2,
APP3=SYSC/SYSC IS UP/JES2,
APP4=SYSA/ADABAS/ADABAS,
APP5=SYSC/PRDCICS/CICSPTOR CICSPAOR CICCSPFOR,
DDIN=PDB,
ODSTYPE=,
TYPERUN=BUILDR
);
RUN;
Thanks to Shantanu.Gupta, ENSONO, USA.
Thanks to Ankush Dudhbavare, ENSONO, USA.
Thanks to Rahul Raj, ENSONO, USA.
Change 38.182 -If you specified BUILDPDB=NO with SUPPRESS=x you got an
UTILBLDP invalid compare on several FLAGxx macro variables used to
Oct 21, 2020 keep track of suppressed items for BUILDPDB. SUPRESS= is
ignored when BUILDPDB is set to NO as the only records
read are those in USERADD=. Comments updated for MXGINCL.
-If you specified OUTFILE=XYZ and XYZ did not exist you
got an unreolved macro reference. On zOS you must have a
DD or a filename statment for the OUTFILE= parameter
unless you use the recommended INSTREAM.
-Comments added to handle products with multiple SMF IDs.
Thanks to Thomas Liu, ANZ. NEW ZEALAND.
Change 38.181 -New ASMRMFV Field Data Filter (FDF) support for the RMF
ADOCRMFV III Coupling Facility Information Table (CFIG3).
ASMRMFV -New Section 33 Filtering The CFIG3 Table added to
Oct 16, 2020 documentation member ADOCRMFV. Following section
numbers all incremented by 1.
-FDF filtering is supported for the Header, Coupling
Facility, Structure, and Structure Extension sections in
the RMF III CFIG3 table.
-After a Structure Extension section in CFIG3 with no
connections occurs, ASMRMFV did not output following
connection entries for subsequent Structure Extensions in
the same Coupling Facility to RMFBSAM.
-TUTORIAL:
The result of a FDF IF=/ORIF=/ANDIF= expression compare
is one of the following:
TRUE FALSE IGNORE
An expression is IGNOREd when:
1) The input RMF III data is for a release that does not
support the Fieldname. This is the most common reason.
IBM may have discontinued the Fieldname, moved it to
another offset with a different Fieldname, or added it in
a higher RMF release than the data being processed.
2) The RMF III table section containing the Fieldname is
absent. Not every section is always present in every RMF
III table. Some sections depend on RMF III startup
options.
NOTE: In the case of the CFIG3 table the Structure
Extension, Connections, and/or Storage Class Memory
sections may not exist. In some cases the Structure
and/or Channel Path sections may not exist. The CFIG3
does not exist at all for LPARs running as z/VM guests.
3) The known offset for Fieldname is beyond the length of
the table section being processed. This could be an
internal ASMRMFV or RMF III error.
4) ASMRMFV treats an IGNORE condition as a TRUE condition
and the data is NOT filtered.
-Example:
The Fieldname CFISTMAE is part of the Structure Extension
section in the CFIG3 table. But if NOCFDETAIL is in
effect in the RMF Monitor III start options, then the
Structure Extension section will not exist for that LPAR.
Assume there are 35,020 structures in the RMF III VSAM
file for the CFIG3 table. Recall that the table is
generated for each RMF III MINTIME interval.
The IF expression is:
RMFV002I SYSIN : IF=(CFISTMAE GT 0)
RMFV088I IF= : CFISTMAE GT 0 X'00000000'
The result will be:
RMFV080I COMPARES: TRUE= 0 FALSE= 0 IGNORE= 35,520
TOTAL= 35,520
Change 38.180 These optional "Candle" CICS segments' variables were not
UTILEXCL correctly kept in the _VCICTRN created by UTILEXCL:
Oct 14, 2020 CANFLAGS CANGMTOF CANUSRWK CANSUPRN CANSUPRT CANDCOMN
CANDCOMT CANRES01. The names in the "Link to IMACICxx:"
were in the wrong "xx:" labels.
Thanks to Shantanu Gupta, ENSONO, USA.
Change 38.179 Support for DB2 ZPARM MFA_AUTHCACHE_UNUSED_TIME value in
VMAC102 seconds in variable QWP4MFAT in T102S106 dataset.
Oct 14, 2020
Thanks to Lai Fai Wong, Bank of America, USA.
Change 38.178 Support for Z NetView 6.3 subtype 4 Command Statistics
EXTY3804 creates new dataset TYPE3804 which contains these
VMAC38 S38DCMDN ='COMMAND*NAME'
VMXGINIT S38DALTN ='COMMAND*ALTERNATE*NAME'
Oct 19, 2020 S38DPRNT ='PARENT*NAME'
S38DTSK ='NETVIEW*TASK*NAME'
S38DSTCK ='START*DATETIME'
S38DETCK ='END*DATETIME'
S38DSTCK ='CPU*TIME'
S38DSTG ='STORAGE*HWM'
S38DIOC ='TOTAL*I/O'
S38DAUSR ='AUTHORIZED*USER*NAME'
S38DELAP='ELAPSED*DURATION'
Thanks to Mark Tomlinson, Lloydsbanking, ENGLAND.
Change 38.177 VTAM Tuning SMF 50 record datasets 502R/502W/504R/504W
VMAC50 were misaligned.
Oct 16, 2020
Thanks to Thomas Doster, IBM, USA.
Thanks to Kristen Lamastr, IBM,USA.
Change 38.176 User tailoring %LET PDBMXG=yourdd; failed with PDB NOT
VMXG70PR FOUND if there was no PDB=LIBNAME argument, or ASUM70GC
Oct 9, 2020 and ASUM70GL were written to PDB instead of "yourdd" if
the PDB libname exists. MXG 38.08 only.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 38.175 MXG 38.08 only. Change 38.170 added support for suppress
UTILBLDP 115 and 116 records, but if you suppressed ID and did not
Oct 8, 2020 set VWVMACID to null you could get an error message from
SAS that the type of VIEW could not be determined, but
only with older SAS versions.
Change 38.174 The Change 38.056 "Error: Unrecognized SAS option name"
ANALID only occurred if ID was suppressed, now that's protected.
Oct 9, 2020
Change 38.173 The ANALID format for SMF 72.4 and 72.5 is changed from
FORMATS RMF I to RMF III because the data gatherer source for
Oct 6, 2020 both of those records written by RMF I is RMF III.
Thanks to Randy Hewitt, DXC Technology
Change 38.172 Variable ZCOSTIME is now numeric with DATETIME20. format.
VMACZCOS
Oct 6, 2020
Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
Change 38.171 The title for the report for DEVMNTMX and DEVMNTAV was
ANALBVIR reversed and is now "INST MIN MAX AVG THRUPUT"/
Oct 5, 2020
Thanks to John Donoghue, AIB, IRELAND
Change 38.170 This utility to create tailored BUILDPDB input code adds
UTILBLDP MQ option to SUPPRESS= so both the 115 and 116 records
Oct 3, 2020 can be skipped.
Change 38.169 Corrected a JCL error in the IBM DFH$MOLS CICS program
DFH$MOLS that decompresses SMF 110 (SUBTYPE 1 ONLY) records.
Oct 2, 2020
Change 38.168 Support for new CICS/TS 5.6 Statistics Variables added to
EXCICXSG STID=43 (CICDQR), eliminate spurious message STID=46 that
SCICSORT new fields were added,and new CICXSG dataset from STID=61
VMAC110 SMF 110 Subtype 2 records.
VMXGINIT
Oct 5, 2020
Change 38.167 Labels for TYPE64 SINCE*OPEN and SINCE*CREATION were
VMAC64 reversed. Variables ACCLEVEL ACCNEXTS ACCNRECS ACCDELET
Oct 1, 2020 ACCINSRT ACCUPDAT ACCRETRV ACCUNUCI ACCISPLT ACCASPLT and
ACCEXCPS are SINCE*OPEN and variables INDXLVLS NREXTNTS
RECORDS DELETES INSERTS UPDATES RETRVALS UNUSEDCI
CISPLTS CASPLITS and EXCPS are SINCE CREATION.
Thanks to Michael Friske, FMR, USA.
Change 38.166 New utility that will help you decide if you should run
UTILUOW ASUMUOW and whether you should use CASE1 or CASE2 from
Oct 1, 2020 IMACUOW if you do decide to run it. ASUMUOW is used to
create the ASUMUOW observations for each UOW in an MRO
by combining the CICSTRAN observations from TOR/AOR/DOR
so you have the valid TRANNAME for the CSMI transactions.
If there is little use of MRO, then it is not worth the
CPU expense. And if there is MRO usage, you need to chose
CASE1 or CASE2 for your IMACUOW tailoring.
Change 38.165 Error "Attempt to open two sequential members" if PDBOUT
READDB2 is on tape (which we DO NOT RECOMMEND) and ACCTSORT=NO
Sep 30, 2020 is specified with READDB2. A circumvention that creates
only the below account datasets is to use TYPSDB2:
%cleardb2;
%let mackeep=%quote(
macro _sdb2acp data _lDb2acp; set _wdb2acp; %
macro _sdb2acr data _lDb2acr; set _wdb2acr; %
macro _sdb2acg data _lDb2acg; set _wdb2acg; %
macro _sdb2acw data _lDb2acw; set _wdb2acw; %
macro _sdb2pat data _lDb2pat; set _wdb2pat; %
);
%include sourclib(typsdb2);
But if your READDB2 did selection (like SSID), that PDB
could have a lot more observations, and any other IFCID
in the original READDB2 would not be created.
An alternative is to use READDB2 but point PDBOUT to a
temporary disk data library, and then PROC COPY to the
tape data library, so all selections are supported.
But the temp disk data library could be quite large,
and might require multi-volumes.
Change 38.164 Support for APAR PH03207 for DFSORT ZSORT statistics that
FORMATS are added to TYPE16 dataset:
VMAC16 ICECOLLK ='ACTIVE*COLLKEY*VALUE'
Sep 29, 2020 ICETCBT ='TOTAL*TCB*TIME'
ICEFLBY5 ='ZSORT*WAS*USED?'
ICEZSRNU ='ZSORT*NON*USAGE*CODE'
ICEZSFLG ='ZSORT*FLAGS'
ICEZSPH1 ='ZSORT*PH1*ELAPSED'
ICEZSPH3 ='ZSORT*PH3*ELAPSED'
ICESSTC1 ='ZSORT*PH1*TCB TIME'
ICESSTC3 ='ZSORT*PH3*TCB TIME'
ICEZSDIA ='ZSORT*DIAGNOSTIC*AREA'
ICEZSDIV ='ZSORT*DIAGNOSTIC*VERSION'
Thanks to Sri H Kolusu, IBM DFSORT, USA.
====== CHANGES THRU 38.163 ARE IN MXG 38.08 DATED Sep 28, 2020 ========
Change 38.163 Support for APAR OA59813 which adds RECOVERY BOOST so new
VMAC30 value BOOSTCLASS='RECO' is added to IPL or SHUT values.
VMAC7072
VMAC89
VMAC90A
VMAC99
Sep 23, 2020
Change 38.162 Datasets ZRBCHP and ZRBSCM had zero observations because
VMACRMFV the test for valid length needed -1 subtracted
Sep 22, 2020
Change 38.161 Macro always looked for PDB rather than the value of
PDBAUDIT PDBAUDIT as it should have. Now it looks for PDBAUDIT and
Sep 21, 2020 if not found on zOS looks in EXTFILES and issues a
LIBNAME statement and if that is successful starts over.
On z/OS, if not successful, or if the LIBNAME's engine is
sequential, or on ASCII, if the LIBNAME is not found,
PDBAUDIT is set to WORK.
Thanks to Randy Hewitt, DXC Technology
CHANGE 38.160 Initial support for dataset DB2NETZA new variables:
VMACDB2 Q8STTMUD='MEMORY*AVAILABLE*USER DATA*MB'
Sep 18, 2020 Q8STTMPS='MEMORY*AVAILABLE*FOR SQL REQ*MB'
Q8STCQLS='CURRENT*QUEUE*LENGTH'
Q8STOFLW='SORT*OVERFLOWS*IN*BACKEND8'
Q8STABHR='ACCELERATOR*BUFFER*HIT*RATIO'
Q8STANUI='INBOUND*TRANSFER*RATE*KB/SEC'
Q8STANUO='OUTBOUND*TRANSFER*RATE*KB/SEC'
Q8STSA ='DISK SPACE*TEMPORARY*DATA*MB'
Q8STLSA ='DISK SPACE*LOG DATA*MB'
Q8STTDPS='SUCCESSFUL*QUERY*REQUESTS*THIS DB2'
Q8STEDPS='QUERY*REQUESTS*EXPIRED*THIS DB2'
Q8STTDPA='SUCCESSFUL*QUERY*REQUESTS*ALL DB2'
Q8STEDPA='QUERY*REQUESTS*EXPIRED*ALL DB2'
Q8STVLCS='REPLICATION*VELOCITY*LOG SEC*PERSEC'
Q8STLRCP='CPU TIME*INTEGRATED*SYNC'
Q8STLRZI='ZIIP TIME*INTEGRATED*SYNC'
Q8STZRZE='ZIIP TIME*ELIGIBLE'
Please contact support@mxg.com before using, because only
test data with one record was available, so the fields
that are accumulated could not be identified/validated.
This update was NOT in MXG 38.08/09/10, need test data.
CHANGE 38.159 MXG 38.07 only, 180 Syntax Error citing SP_NOBS=&NOBS,
VMXGPRAL due to an incorrect and undocumented &VARLST change.
Sep 16, 2020
Thanks to MP Welch, Bank of America, USA.
CHANGE 38.158 Format $MGSMFID didn't map SMF 119 subtypes 11, 12, 81,
FORMATS and 101-104, but those records were already supported in
Sep 16, 2020 VMAC119, although 101-104 subtypes are not written and
are only available thru an API.
Thanks to MP Welch, Bank of America, USA.
CHANGE 38.157 OUTFILE= defaults to BUILDMXG though the more common
UTILBLDP usage is INSTREAM and INSTREAM exists in all of the MXG
Sep 14, 2020 PROCs and AUTOEXECs. But if you fail to specify an
OUTFILE or the one you specified does not exist your job
would fail with FILE NOT FOUND errors. Now it is detected
and tells you what the problem was but it will still
ABEND and cause errors in your job.
Thanks to Arnold Kim, UPS, USA.
Thanks to George Carlquist, UPS, USA
Change 38.156 Dataset tokens for datasets TYP11924 and TYP11945 were
VMAC119 not in the _N119 list of all datasets.
Sep 14, 2020
Change 38.155 Debugging Option DKROCOND=WARN found many non-references
ANALDB2R that were typo's and did cause some variables to not be
IMACICVH kept, This was a long time on my to-do-list, now done.
IMACICWV -VMAC71 DELTATM is not created in WORK.TYPE71 but is added
UTILEXCL in the _S71 Sort Step, removed from KEEP= list for WORK.
VMAC110 -VMACCMFV variables starting with PRRE_G in CMFV82.
VMAC116 -VMACMVAO variables HHMM and YYYYMMDD were typos.
VMAC120 -VMAC85 R850SUB was spelled R50SUB.
VMAC71 -VMAC89 variable PRODMOD was spelled PROCMOD.
VMAC85 -VMAC92 variable SMF92DTY in TYPE9217, typo, not kept.
VMAC89 -VMAC99 typos in S99EEHMxx, S99SLET, S99CVCM in TYPE99SL.
VMAC92 -VMAC110 variable SSMVSSTM typo for SMMVSSTM, now kept.
VMAC99 -VMAC110 WBJCNRPL typo in CICSTRAN.
VMACCMFV -IMACICVH was not in PRODTEST with comment removed.
VMACMVAO -IMACICWV still had comment block in PRODTEST.
VMXGUOW -UTILEXCL variable SSMVSSTM typo for SMMVSSTM, now kept.
Sep 13, 2020 -VMAC110 variable MNGAPPLS typo for MNGAPPNS, now kept.
VMAC112 -VMAC110 SORTCPIPSMAXPERSIST underscores removed.
VMACWSF -VMAC110 IMSTM NRIMS removed from KEEP.
VMACCTCP -VMAC112 T112JOB replaced OMCIJOB, T112NUMB/OBJTYPE gone.
-VMAC116 WTSAWQCT typo for WTASWQCT.
-VMAC120 GMTOFFDOM typo for SM120GMT.
-ANALDB2R Variable QWHSSSID not on S102S083.
-VMXGUOW SPURIOUS WARNs are printed if MXGEXIMSG=YES.
-VMACWSF ACCCHOST typo ACCHOS, S1ODS typo ACCS1ODS.
-VMACCTCP CTCP32CA/B/C/D gone, CTCPSUBS typo SUBSYS.
Change 38.154 Labels for variables D06xxxxx in VMACIMS and GAVxxxxx in
VMAC99 VMAC99 had unbalanced quotes, which cause no error but
VMACIMS labels were not correct.
Sep 11, 2020
Change 38.153 Syntax revisions to prevent spurious log messages about
ASUMPRTR ancient DATETIME syntax.
TRNDPRTR
Sep 11, 2020
Thanks to Wayne Bell, UNIGROUP, USA.
Change 38.152 Support for APARs OA58729/OA58724 which added these new
VMAC74 Resource Monopoly fields in dataset TYPE74ST subtype 4:
Sep 11, 2020 R744SMRC='REQUESTS*DELAYED*MONOPOLY'
R744SMTM='SUMMED*QUEUE*TIME*FOR*MONOPOLY'
R744SMSQ='SUMMED*SQ OF*QUEUE TIME*MONOPOLY'
R744SMTO='OPS*QUEUED*MONOPOLY*AVOID'
R744SMHT='HI OPS*QUEUED*MONOPOLY*AVOID'
R744SMMN='MIN OPS*QUEUED*MONOPOLY*AVOID'
R744SMMX='MAX OPS*QUEUED*MONOPOLY*AVOID'
R744SMHN='MIN HI OPS*QUEUED*MONOPOLY*AVOID'
R744SMHX='MAX HI OPS*QUEUED*MONOPOLY*AVOID'
Thanks to Kurt Gramling, T-SYS, USA.
Change 38.151 Unused Change Number.
Change 38.150 If you did not have a //IPHOSTS or FILENAME IPHOSTS,
ANAL119 errors including divide by zero occurred. Now, if it
Sep 6, 2020 doesn't exist, an MXGWARN message is printed and the
processing continues creating the zero obs dataset.
Change 38.149 TYPE113 SM113TM was not an interval time and this would
ANALSIIS only occasionally match to SMFINTRV records. Now a new
Sep 6, 2020 interval TIMESTMP is calculated. SYNC59=YES added to the
parameter list.
Thanks to Pierre Pascal Joulin, SocGen, FRANCE.
Change 38.148 VGETOBS calls were revised.
VMXGSUM
Sep 10, 2020
Change 38.147 -IFCIDS=DB2GBPAT was not recognized; now is.
READDB2 -ACCTSORT=NO was not suppressing SORTS.
Sep 12, 2020
Change 38.146 After _N7072, MACRO _WTY70 TYPE70 % was added.
SAGANAL
Sep 4, 2020
Change 38.145 If you are rolling up interval data and specify an
VMXGDUR interval LT the actual duration in the data the results
Sep 10, 2020 may not be what is expected. VMXGDUR now detects this
when the input data contains a DURATM variable and puts
an MXGNOTE on the log.
Change 38.144 Line 55 had "SAAV" text that was accidentally found in
TESTIBM2 MXG 38.05-38.07.
Aug 31, 2020
Thanks to Altino Pimentel, Express-Scrips, USA.
Change 38.143 -Variable CFISCVER in ZRBSCM is replaced by CFISCVERCH as
VMACRMFV that variable should have been input as $CHAR8, but was
Aug 28,2020 incorrectly INPUT as a datetime, and name must be changed
to prevent errors if merging old and new ZRBSCM.
-Variables CFISCMAX,CFISCFAU,CFISCIAU,CFISIUS were not
multiplied by 4096 to store bytes instead of KB.
Change 38.142 -When creating PDB.ASUMCELP and PDB.ASUMCEC datasets with
ASUM70PR CECINTRV=HOUR, from PDB.TYPE70/PDB.TYPE70PR with QTRHOUR
ASUM70WK intervals, the ASUMCELP/ASUMCEC has 23 valid hourly obs,
VMXG70PR with two additional obs, one from the last interval of
Aug 25, 2020 yesterdaq with (DURATM 15 min) and one from the last hour
of today (DURATM 45 min). To report only full hours, you
can select obs with IF DURATM GT 3400; in your reports.
-This new ASUM70WK program reads your WEEK.TYPE70/70PR to
create two weekly hourly WEEK.ASUMCEHR and WEEK.ASUMLPHR
(like CEC/CELP) with all intervals one hour. The two
partial intervals are not output, but they are from the
SMFDUMP time on the weekends and presumably unimportant.
-Enhancements were needed in VMXG70PR.
-The PDB= argument for the libname of input datasets was
incorrectly ignored, and the &PTY70 and &PTY7072 tokens
were used. Now it will be used, but VMXG70PR checks for
the existence of TYPE70 & TYPE70PR if PDB= is nonblank,
and terminates if either has zero obs or isn't there.
-New PDBOUT= argument names the output LIBNAME for the
two new datasets, if argument is non-blank.
-OUTCODE70PR= Your SAS code that will let you control
what observations are output to ASUM70PR.
-OUTCODE70LP= Your SAS code that will let you control
what observations are output to ASUM70LP.
-OUTCODECEC = Your SAS code that will let you control
what observations are output to ASUMCEC/ASUMCEHR
-OUTCODECELP= Your SAS code that will let you control
what observations are output to ASUMCELP/ASUMLPHR
-OUTCODE70GL= Your SAS code that will let you control
what observations are output to ASUM70GL.
-OUTCODE70GC= Your SAS code that will let you control
what observations are output to ASUM70GC.
-The ASUM70WK defaults to PDB=WEEK, PDBOUT=WEEK, and
the two OUTCODEs use IF DURATM GT 3400; to only create
full hourly data for the week.
%VMXG70PR (PDB=WEEK,INTERVAL=QTRHOUR,CECINTRV=HOUR,
OUT70LP=WEEK.ASUMLPHR,
OUTCODE70PR=IF DURATM GT 3400;,
OUTCELP=WEEK.ASUMCEHR,
OUTCODECELP=IF DURATM GT 3400;,
OUTCEC=_NULL_,
OUT70PR=_NULL_,
OUT70GL=_NULL_,
OUT70GC=_NULL_
);
====== CHANGES THRU 38.141 ARE IN MXG 38.07 DATED Aug 22, 2020 ========
Change 38.141 -Processing CICS Statistics records in BUILDPDB can be
EXCICLDR very CPU/Elasped intensive for very little daily value.
EXCICSDR The SMF 110 Subtype 2 records are tactical data for the
EXCICSMD resolution of CICS problems, which happen so rarely that
EXCICSMT it would be better to only process them with TYPS110-2 if
EXCICTCR and when your CICS folks actually have need of that data.
EXCICXMR IBM CICINTRV dataset default 3 hour interval is also not
SCICSORT much use for tactical analysis. To suppress processing
VMXGCICI of the statistics records in BUILDPDB/TYPE110
Aug 21, 2020 you can insert this at the top of your //SYSIN
Aug 21, 2020 %LET MACFILE=
%QUOTE( IF ID=110 AND SUBTYPE=2 THEN DELETE;);
With UTILBLDP, SUPPRESS=CICSSTAT will suppress sorts and
CICINTRV and all of the Statistics datasets will have
obs so they take no space, but will exist os subsequent
reports won't fail.
And if you ONLY want CICSTRAN with no other account nor
statistics datasets, add this and the MACFILE to SYSIN.
%LET MACKEEP= %QUOTE
(_N110 _S110 MACRO _WCICTRN CICSTRAN.CICSTRAN % );
%INCLUDE SOURCLIB(TYPE110);
(and always have a blank between percent and paren).
-For sites that do use those data, there are large counts
of observations created during intervals of no activity
that increased CPU, elapsed time and disk space needed.
For example CICXMR created 1,173,518 obs in WORK.CICXMR
but only 4061 obs were output in PDB.CICXMR. With this
change, these seven datasets are only output in WORK if
there was activity: FCR LDR SDR SMD SMT TCR XMR, but that
test can be tailored to create all obs in the EXCICxxx.
-%INCLUDE SOURCLIB(UCICSCNT) will report how many obs were
written to SMF and not output for each STID. MXG member
IMAC110 documents the CICxxxxx dataset for each STID.
-This change significantly reduced the CPU and elapsed
time for a 5GB SMF file with lots of "idle" hours, with
lots of regions, ET from 17:24 to 6:21, CPU 517 to 258.
There were 104 Regions and the data was from a Monday.
Thanks to Vijay Singh, IBM, NEW ZEALAND.
Change 38.140 Variable CMM, CMM BALOON is added to XMUCDSYS dataset.
VMACXAM
Aug 20, 2020
Thanks to Raymond J. Smith, OPTUM, USA.
Change 38.139 Change 38.037, in MXG 38.02 MQMQUEUE these variables
VMAC116 QWHCNID QWHCOPID QWHCTASK QWHCTNO QWHCTRN
Aug 17, 2020 were in the Change text, but were dropped from the KEEP
list; the KEEP list now includes them.
Thanks to Pietro Rosella, Canadian National Railway, CANADA.
Change 38.138 Unused Change Number
Change 38.137 Support for APAR OA57466 which adds variables to TYPE26J2
VMAC26J2 SMF26BYU='TOTAL JOB*UNCOMPRESSED*BYTES'
Aug 15, 2020 SMF26BYC='TOTAL JOB*COMPRESSED*BYTES'
SMF26CCT='COMPRESSED*DATASETS'
SMF26ECT='ENCRYPTED*DATASETS'
Change 38.136 If you rerouted CICXMG to PDB all sorts of strangeness
VMXGCICI occurred since VMXGCICI was looking for CICXMR rather
Aug 13, 2020 than CICXMG.
Thanks to Nilton de Oliveira Mello Junior, IBM, Brazil.
Change 38.135 -Change 38.128 wasn't released, but a severe error message
ASMRMFV RMFV016S >>>SEVERE: RMF III TABLE ID MISMATCH -
Aug 13, 2020 EXPECTED: CPUG3 ACTUAL: CPUG3 (C3D7E4C7F3X)<<<
incorrectly appears. A table id validation test branch
was incorrect.
Change 38.134 -Example added to output ALL Service/Report Classes even
ASUMMIPS those with CPUTM=0, which are not normally output.
Aug 11, 2020
Thanks to Nestor D Rossi, BANCOGALICiA, ARGENTINA.
Change 38.133 -Support for IMS LOG Record 67D0 Subtype 6 creates new
BUILDIMS dataset IMS67D006.
EX67D006 -BUILDIMS requires REPORT=YES (to avoid a MAJOR rewrite)
IMACIMS so it is now always forced.
VMACIMS
VMXGINIT
Aug 14, 2020
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 38.132 DCOLLECT ABEND B37 (SPACE). New UNIX fields were added in
EXDCOBKU Change 38.102 (MXG 38.05), adding 1231 bytes to each obs,
IMACDCOL in DCOLBKUP, Unix or Not. The variables are now removed
VMACDCOL from DCOLBKUP and new DCOLBKUU dataset is now created for
VMXGINIT Unix dataset information.
Aug 7,2020
Thanks to Bill Davis, Transamerica, USA.
Change 38.131 Unused Change Number
Change 38.130 Support for Thruput Manager IZWS fields.
VMACTPMX
Aug 5, 2020
Thanks to Kurt Gramling, T-SYS, USA.
Change 38.129 -Writing SMF with SYNC=59 has NEVER BEEN RECOMMENDED, it
VMXG70PR was required with MICS, and while MXG summarization can
Jul 30, 2020 take it into account, there is intrinsic inaccuracy as
Aug 13, 2020 only SYNC=0 will provide exact 00,15:30:45 intervals.
The hourly summarization in VMXG70PR forces those exact
interval start to the exact value, but other RMF datasets
will still have 59:14:29:44 starts. This change creates
the new OUTCODE70PR argument for VMXG70PR, which you can
add in your ASUM70PR member's invocation of VMXG70PR:
%VMXG70PR (PDB=PDB,INTERVAL=QTRHOUR,CECINTRV=HOUR,
OUTCODE70PR= STARTIME=STARTIME-60;
SMF70GIE=SMF70GIE-60;);
-A blank TITLE was added at the end to prevent carry.
Thanks to Linda Berkeley, DISA Mainframe, USA.
Change 38.128 -ASMRMFV Field Data Filter (FDF) support for the RMF III
ADOCRMFV XCF Activity Data Table (XCFG3) and an IMPORTANT FDF FIX.
ASMRMFV -The Field Data Filter (FDF) feature of RMF III was added
Jul 30, 2020 in MXG Change 37.089 and allows you to filter raw RMF
reducing the size of the created RMFBSAM file. You can
filter table entries based on one or more numeric and/or
character fields, and is intended for advanced MXG users
building ad hoc data collection of RMF III data.
-ASMRMFV FDF can fail to correctly translate X'00'
characters to X'40' blank characters for RMF III field
names in FDF expressions that can contain nulls. This can
cause filter comparisons to be FALSE instead of TRUE.
-The example JCLRMFV/JCLCRMFV/JCLDRMFV members have been
integrated into Sections 48, 49, 50 in ADOCRMFV, with new
FDF examples; the old members are pointers to ADOCRMFV.
- J is now an alias for SCM table selection.
- -J is now an alias for SCM table exclusion.
-See Change 38.135 correction; 38.128 was never released.
-Following updated or added in the ADOCRMFV documentation
member:
Section Contents
------- -------------------------------
0 Contents
2 Terminology
3 Execution JCL
5 Input Data Selection Parameters
32 Filtering The ASIG3 Table
33 Filtering The CPDG3 Table
34 Filtering The CSRG3 Table
35 Filtering The DSIG3 Table
36 Filtering The DVTG3 Table
37 Filtering The ENCG3 Table
38 Filtering The ENTG3 Table
39 Filtering The GEIG3 Table
40 Filtering The OPDG3 Table
41 Filtering The PCIG3 Table
42 Filtering The SCMG3 Table
43 Filtering The SPGG3 Table
44 Filtering The SSHG3 Table
45 Filtering The XCFG3 Table
46 Filtering The ZFXG3 Table
47 ASMRMFV Execution and Methods Overview
48 PDB Build Examples With Direct JCL Method
49 PDB Build Examples With TSO Clist Method
50 PDB Build Examples With Dynamic Method
51 Summary
-TUTORIAL:
This level of ASMRMFV introduces the concept of
Independent Data Sections when using FDF.
An Independent Section is an ASMRMFV term for a RMF III
data section containing data unrelated to other sections
in the same RMF Monitor III table. Examples of this are
the Group Data, Path Data, and System Data Sections of
the XCFG3 table.
ASMRMFV does not support logical FDF ANDing of filters
from two different Independent Sections because the data
is not logically related.
ASMRMFV FDF processes each Independent Section
separately. If ANDIF= expressions for 2 fields in two
different Independent Sections occur FDF will bypass any
IF expressions for fields not contained in the section
being currently processed.
Data dictionary sections in ADOCRMFV for tables now
identify the Section when Independent Sections are
applicable an RMF III table.
Change 38.127 Using ANAL119 with PDB=SMF without a PDBOUT=, 0 OBS were
ANAL119 found for the FTP report. Now if PDBOUT= is null PDB is
Jul 30, 2020 set to &MXGWORK.
Thanks to Jennifer D. Ayers, West Virginia Government, USA.
Change 38.126 When SMF Logger outputs sysplex data for multiple systems
VMAC7072 records are interleaved, so it is no longer possible to
VMXGINIT retain TYPE70 variables like CECSER/CPCMODEL from the 70
Jul 29, 2020 into the TYPE72GO dataset, where they are frequently
missing values. This change revises the _STY72GO dataset
sort macro to sort and merge the two datasets to populate
CECSER and CPCMODEL whenever possible (if a 70 ends an
SMF dataset, the subsequent 72 read tomorrow won't have a
matching 70 even with the new sorting logic).
-All of the 7072 processing programs that sort and create
PDB datasets, like BUILDPDB/BLDSMPDB/UTILBLDP/TYPS7072
already invoke the _STY72GO macro so this change will be
transparent. However, if you use only TYPE7072 to write
only to //WORK, you will need to use this syntax to sort
and create the correctly populated TYPE72GO dataset:
%INCLUDE SOURCLIB(TYPE7072);
%LET PTY70=WORK;
%LET PTY72GO=WORK;
_STY72GO;
RUN;
-And new macro variable &SSTY72GO is added in _STY72GO so
you can insert code to create new variables from the
CECSER/CPCMODEL variables into your TYPE72GO dataset.
Thanks to Kurt Gramling, T-SYS, USA.
Change 38.125 Change 38.117 test for QLSTVRSN='000001' was changed to
VMACDB2 'F0F0F0F0F0F1'x to detect new data on EBCDIC or ASCII.
VMAC102
Jul 26, 2020
Change 38.124 -RMF III datasets ZRBXCG, ZRBXCP and ZRBXCS had many dupes
VMACRMFV because the offset was not updated and so only the first
Jul 26, 2020 segment was read and re-read and output XCFxDATN times.
Jul 30, 2020 Caused incorrect ZRBXCG INVALID TRIPLET messages.
-Dataset ZRBZFS variable ZFX_FS_AGGRREADKBYTES corrected.
====== CHANGES THRU 38.123 WERE IN MXG 38.06 DATED Jul 25, 2020 ========
Change 38.123 Change 38.121 overlooked one dataset causing the refresh
VMXGCICI on Saturday morning.
Jul 25, 2020
Change 38.122 Some CICS Statistics datasets (CICxxxxx) were incorrectly
VMAC110 sorted because the %INCLUDE SOURCLIB(SCICSORT) statement
Jul 25, 2020 was accidentally deleted.
Change 38.121 If you tailored CICS statistics datasets and some were in
VMXGCICI WORK and some were in PDB, a dataset not found error due
Jul 25, 2020 to MXG expecting all in one place. Individual locations
now are tested, and the sorts commented out.
====== CHANGES THRU 38.120 WERE IN MXG 38.06 DATED Jul 24, 2020 ========
Change 38.120 Variables decoded from SMF30SLM weren't kept in SMFINTRV:
VMAC30 SMF30SLMRB SMF30SLMRA SMF30SLMSB SMF30SLMSA SMF30SLMML
Jul 24, 2020 SMF30SLMBY
Thanks to Randy Hewitt, DXC Technology
Change 38.119 Type 92 subtype 16 records are the same as subtype 11 so
VMAC92 both subtypes are now output in TYPE9211 and SMF92STP is
Jul 23, 2020 kept to identity which subtype was output.
Thanks to Nathan Lowenthal, CITIGROUP, USA.
Change 38.118 -ASMRMFV FDF message RMFV088I can be incorrectly formatted
ASMRMFV showing the hex value of a number in an IF expression
JCLASM3 as zeros. Processing is not impacted. The message only
Jul 21, 2020 appears when FDF is used.
-After Change 38.082 to reduce SYSOUT output from an
ASMRMFV assembly condition code 0002 can occur after an
assembly. The XREF(SHORT) option in the JCLASM3 sample
member is no longer required. ASMRMFV will override this
value to NOXREF, so no JCL change is required.
Thanks to Randy Hewitt, DXC Technology
Change 38.117 Support for DB2 APAR PH16111 adds location variables to
VMACDB2 the QLST segment,in IFCID 365 in dataset T102S365 and in
VMAC102 SMF 100 Subtype 1 datasets DB2STAT0/DB2STATS/DB2STATR.
Jul 21, 2020
Thanks to Harald Seifert, Huk-Coberg, GERMANY.
Change 38.116 Support for BMC Mainview for CICS Version 7.1 (COMPAT).
VMACMVCI -New variables in dataset CMRDETL:
Jul 20, 2020 T6EXSVPT='TOTAL*PASSWORD*VERIFY*TIME'
T6EXSVPN='TOTAL*PASSWORD*VERIFY*COUNT'
T6EXSVPF='TOTAL*PASSWORD*VERIFY*FLAG'
T6EXSVBT='TOTAL*BASIC AUTH*VERIFY*TIME'
T6EXSVBN='TOTAL*BASIC AUTH*VERIFY*COUNT'
T6EXSVBF='TOTAL*BASIC AUTH*VERIFY*FLAG'
T6EXSVKT='TOTAL*KERBEROS*VERIFY*TIME'
T6EXSVKN='TOTAL*KERBEROS*VERIFY*COUNT'
T6EXSVKF='TOTAL*KERBEROS*VERIFY*FLAG'
T6EXSVJT='TOTAL*JSON JWT*VERIFY*TIME'
T6EXSVJN='TOTAL*JSON JWT*VERIFY*COUNT'
T6EXSVJF='TOTAL*JSON JWT*VERIFY*FLAG'
T6ESMMWT='TOTAL*Z/OS SOS*WAIT*TIME'
T6ESMMWN='TOTAL*Z/OS SOS*WAIT*COUNT'
T6ESMMWF='TOTAL*Z/OS SOS*WAIT*FLAG'
-Complete revision of MXG Code for CMRFPROG.
T6EPGTELCN='PROGRAM*ELAPSED*COUNT'
T6EPGTELTM='PROGRAM*ELAPSED*TIME'
T6EPGCNT='PROGRAM*SUMMARIZATION=1'
T6EPGNM ='PROGRAM*NAME1'
Change 38.115 Support for Optional CICS Field HUMTRAN with multiple
UTILEXCL INPUT lengths of $16 and $24. The length of variable
VMAC110 HUMTRAN is $24.
VMXGINIT
Jul 16, 2020
Change 38.114 New CICS datasets SMF 110 Subtype 1 MNSEGCL=5 Resource
EXCICRDU class datasets:
EXCICRDW DDDDD Dataset Description
IMAC110 CICRDU CICSRDUR URIMAP Resource
VMAC110 CICRDW CICSRDWB WEBSVC Resource
VMXGINIT
Jul 16, 2020
Change 38.113 SMF records that EXCLUDE ABCODEC, field 114, have a four
UTILEXCL byte field but MXG can't detect the absence of field 114.
VMXGINIT The default UTILEXCL creates the $EBCDIC8. input, but for
Jul 15, 2020 the SMF 110s use %LET MXGCICSABCODELN=4; in SYSIN.
Thanks to Bradley Leis, TELUS, CANADA.
====== CHANGES THRU 38.112 WERE IN MXG 38.05 DATED Jul 15, 2020 ========
Change 38.112 Support for DFSMS APAR OA59510 OA59830 collects UNIX file
VMACDCOL Backup information in DCOLLECT, new DCOLBKUP variables
Jul 14, 2020 UBUNIX ='UNIX*FILE*BACKUP?'
UBUNIXDIR='UNIX*FILE OR*DIRECTORY?'
UBENCRYPTA='DATASET*ENCRYPTION'
UBENCRPT='ENCRYPTION*TYPE*0100-AES256*FFFF-NO'
UBENCRPL='ENCRYPTION*KEY*LABEL'
UBPATHL='LENGTH*OF THE*FILENAME'
UBUPATHN='UNIX*PATH*NAME'
Change 38.111 TYPE1415 Space Allocation Unit is set to SPACE='AVG' for
VMAC1415 AVGREC when JFCBCTRI='90'x and based on values in SMF
Jul 13, 2020 that matches the job's JCL. Previously these records had
SPACE='TRK' because the '80'x bit was detected.
Thanks to Bruce Sloss, PNC, USA.
Thanks to Walt Unterbrink, PNC, USA.
Change 38.110 -38.05 Early Adopter, test IF LENPDGS GE 2296 in line 2094
VMAC71 should be IF LENPDGS GE 2440.
Jul 12, 2020
Change 38.109 -38.05 Early Adopter, period missing in VMAC98 line 876.
VMAC98 Should be $CHAR16. (with the period).
Jul 12, 2020
Change 38.108 -RMF III dataset ZRBENC PROC SORT removed more duplicates
VMACRMFV than intended; the _BZRBENC sort list needed the two
Jul 16, 2020 added variables at the end:
MACRO _BZRBENC SYSPLEX SYSTEM SSHTIBEG EDEUSER ENCTOKEN%
-Variable SSHGOSYN='GATHERER*SYNC*OPTION?' is added to all
datasets.
-Data sets ZRBXCG, XRBXCP, ZRBSCS have added variables
SSHRMFVN SSHSMPNR
XCFVER XCFSID XCFPART XCFREL XCFSYSN CSFSTAT XCFESTAT
Thanks to Kurt Gramling, TSYS, USA.
Change 38.107 Some macro variables were unresolved because they needed
ANAL119 to %GLOBALed.
Jul 11, 2020
Thanks to Jennifer D. Ayers, West Virginia Government, USA.
TECHNOTE - z/OS ONLY
Jul 8, 2020
The PDB library written by BUILDPDB CAN'T BE ON TAPE, neither
REAL TAPE or VIRTUAL TAPE or V9SEQ libraries on DASD.
We have NEVER recommended the PDB be written directly to TAPE
because BUILDPDB reads and writes to and from //PDB, multiple
times, and since sequential datasets have no directory, each
action requires a rewind to the beginning of the dataset and a
read until it finds the desired dataset, increasing run time.
And PROC DATASETS fails with ERROR: Proc Datasets is not able
to process a sequential library. Consider using PROC CONTENTS
or PROC COPY instead.
If you want your PDB on TAPE, point //PDB to Temporary DASD,
then PROC COPY to TAPE dataset at the end.
The more insidious issue is the potential for lost data.
Assume that you want to create a SAS data library with
datasets A B C D and then find that you need to rewrite
dataset B to add a variable. You can do it but you would then
lose datasets C and D PERMANENTLY. If you try to access them
you will get a DATASET x NOT FOUND error.
SAS Technical Support documentation for sequential libraries:
Due to the nature of sequential devices, SAS allows only two
types of operations with members of a sequential bound
library:
-reading an existing member and writing a new copy
-writing a new copy of a member to the library.
The following types of operations are not
supported for sequential access bound libraries.
-Having multiple members in the library open at same time
-Updating the contents or attributes of a member of the
library
-Renaming or deleting a member of the library.
-Using BLKSIZE GT 32760 with SAS 9.4M1 or earlier which did
not support LBI. Error is ABEND 013 Return E1.
-PROC DATASETS is not able to process a sequential dataset.
CAUTION
SAS deletes all members of a sequential bound library that are
subsequent to the library member that you replace.
By default, when writing a member of a sequential bound
library, SAS scans the entire library from the beginning to
determine whether a member having the specified name already
exists in the library. If such a member already exists in the
library, then the new copy of the member is written starting
at the position in the library data set where the old copy of
the member began, and all subsequent members of the library
are deleted. If the specified member does not already exist in
the library, it is appended to the end of the library. This
behavior is not influenced by the REPLACE system option
because NOREPLACE is not supported by the TAPE engine.
When the FILEDISP=NEW data set option is specified for a
member to be written to a sequential access bound library, SAS
replaces all of the members that previously existed in the
library, even if they were protected by an ALTER password. The
ALTER password is not checked even for the member being
replaced.
When the COPY procedure is used to write members to a
sequential access bound library, the rules regarding member
replacement (discussed in the previous topic) apply only to
the first member being processed by a COPY statement or PROC
COPY invocation. All other members involved in the COPY
operation are appended to the end of the library data even if
they already exist in the library. Therefore, it is possible
to cause a library to contain two copies of the member, only
the first of which is recognized. You should plan all COPY
operations carefully so that you avoid this outcome.
Some specialized SAS procedures repeatedly process a group of
observations that have the same value for a specific variable.
This situation requires SAS to interrupt its sequential access
pattern and reposition to a previous location in the library
data set. However, SAS does not support repositioning to a
location on a previous volume of a multi-volume tape data set.
When this situation occurs, SAS issues the following error
message:
ERROR: A POINT operation was attempted on sequential library
SEQLIB.
A volume switch has occurred on this library since the last
NOTE operation, making the POINT results unpredictable.
Should this situation occur, you can avoid the limitation by
copying the member to a library on disk.
When using the LIBNAME statement to dynamically allocate SAS
libraries on tape, it is not possible to simultaneously
allocate multiple MVS data sets on the same tape volume.
Therefore, it is necessary to use the SAS LIBNAME CLEAR
statement to deassign the library before you attempt to assign
another MVS data set on the tape.
The mode in which SAS opens the library data set is primarily
governed by the type of access that is being performed. When
reading a member, listing the members in the library, or
retrieving information about the library, the library data set
is opened for INPUT. When writing a member, the library data
set is opened for INOUT (unless DISP=NEW and the data set has
not been previously opened. In that case, OUTIN is used). SAS
does not write to a library that is allocated with DISP=SHR or
LABEL=(,,,IN), issuing an ERROR message instead. Before
opening the library data set, SAS first checks the RACF
authorization, but only for libraries that reside on disk, and
only if NOFILEAUTHDEFER is in effect.
Thanks to Jill Ackerman, SAS Technical Support, USA.
Change 38.106 Support for APAR OA59330 new variables in TYPE7002:
VMAC7072 R702FPTI='INSTRUCTIONS*TO TRANSLATE*USING FPE'
Jul 7, 2020 R702FXEC='CALLS TO*ENCIPHER*USING*FFX'
R702FXEB='BYTES*ENCIPHERED*USING*FFX'
R702FXEI='INSTRUCTIONS*TO ENCIPHER*USING*FFX'
R702FXDC='CALLS TO*DECIPHER*USING*FFX'
R702FXDB='BYTES*DECIPHERED*USING*FFX'
R702FXDI='INSTRUCTIONS*TO DECIPHER*USING*FFX'
R702FXTC='CALLS TO*TRANSLATE*USING*FFX'
R702FXTB='BYTES*TRANSLATEED*USING*FFX'
R702FXTI='INSTRUCTIONS*TO TRANSLATE*USING*FFX'
R702DQGC='CALLS TO*GENERATE*QSA DIGITAL*SIGNATURE'
R702DQVC='CALLS TO*VERIFY*QSA DIGITAL*SIGNATURES'
Change 38.105 Support for May 2020 SMF Manual Changes (still-40).
EXTY9040 -TYPE02 Records
FORMATS -Subtype 1 new variables in TYPE0201
VMAC0203 SMFGFLG2='RESERVED?'
VMAC25 SMFGFLG2='APAR OA55526*APPLIED?'
VMAC30 SMFGFLG2='SELF*DEFINING*SECTION?'
VMAC42 There is a new Self Defining Section "triplet" for the
VMAC7072 new ARECSIGN section, I need data to decode.
VMAC71 -Subtype 2 new variables in TYPE0201
VMAC89 SMFIFLG24='RESERVED?'
VMAC90A SMFIFLG25='NOT DOCUMENTED?'
VMAC98 SMFIFLG26='APAR*OA55526*APPLIED'
VMAC99 SMFIFLG27='SELF*DEFINING*SEGMENT?'
VMAC106 There is a new Self Defining Section "triplet" for the
VMXGINIT new ARECSIGN section, I need data to decode.
Jul 3, 2020 -TYPE 25 SMF Records
-Label changed for TYPE25 SMF25NTF.
-TYPE 30 SMF Records
-ZEDC section
-z15 changes:
SMF30_US_COMPRREQ only counts authorized request
SMF30_US_DEF_COMPROUT, INF_DECOMPROUT, DEF_COMPRATIO
are now always zero.
-Variables added to TYPE30_V/_4,_5,_6:
BOOSTACTIVE='BOOST*ACTIVE*ZIP*SPEED*BOTH'
BOOSTCLASS='BOOST*CLASS*IPL*SHUTDOWN'
-TYPE 42 Records
Variable S42VTUNC count is zero with APAR OA55709.
There is no volume metrics section when there are no
SSCH instructions for this volume, and no system I/O
section when no system I/O to this volume, and no
background activity section when there no background
activity.
-TYPE 70 records
-Subtype 1
New variable SMF70CPC_TYPE (8561) to TYPE70 dataset.
-Subtype 2
New FORMATS value 0Dx:CEX7C for R7023CT/R7024CT/R7025CT
crypto type in TYPE7002/TYPE70X2/TYPE7Y3 datasets.
-TYPE 71 SMF Records
New variables in TYPE71 dataset:
SMF71M6C='MIN FRAMES*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71X6C='MAX FRAMES*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71A6C='AVG FRAMES*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71M6F='MIN FIXED*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71X6F='MAX FIXED*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71A6F='AVG FIXED*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71M6B='MIN 24-BIT*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71X6B='MAX 24-BIT*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71A6B='AVG 24-BIT*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71M6A='MIN AUXSLOTS*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71X6A='MAX AUXSLOTS*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71A6A='AVG AUXSLOTS*BACK*64-BIT*SHARED*PAGE GROUPS'
SMF71M6S='MIN SCM BLOCKS*BACK*64-BIT*SHARED*PAGE GROUPS
SMF71X6S='MAX SCM BLOCKS*BACK*64-BIT*SHARED*PAGE GROUPS
SMF71A6S='AVG SCM BLOCKS*BACK*64-BIT*SHARED*PAGE GROUPS
SMF71M6T='MIN 64-BIT*SHARED*PAGE GROUPS'
SMF71X6T='MAX 64-BIT*SHARED*PAGE GROUPS'
SMF71A6T='AVG 64-BIT*SHARED*PAGE GROUPS'
-TYPE 72 SMF RECORDS
-Variables BOOSTACTIVE and BOOSTCLASS added to TYPE72GO.
(In 70, BOOSTINFO flags partial boost, but there is no
field for partial boost in 72).
-TYPE 89 SMF Records
-Variables BOOSTACTIVE and BOOSTCLASS added to TYPE89,
but there are no bits for full boost, only partial.
-TYPE 90A SMF Records
- New subtype 40, SET BOOST, creates TYPE9040 dataset.
-TYPE 98 SMF Records (Last updated 2017!)
-Variables added to TYPE9801 dataset:
SMF98_CVTLSO= 'LEAP*SECOND*OFFSET'
SMF98_ECVTLDTOCH ='ETOD*LOCAL*OFFSET*CHAR'
SMF98_ECVTLSOCH ='ETOD*LEAP*SECOND*OFFSET*CHAR'
-The Workload Interaction Correlator WICDATA records
require more documentation from each exploiter and
won't be decoded without actual data records:
"These mappings are incomplete and depend on the
particular data to be recorded for each exploiter.
Use the mapping produced by the subtype holder."
-TYPE 99 SMF Records
-Variable added to TYPE99_1 - BOOSTINFO
-Variables TOD added to TYPE99EH subtype 14.
S99EVCMHWLEVEL='HW*LEVEL'
S99EEVCMDURRTOD='CURRTOPO_TOD'
-Await a USER with need+data for new subtypes 9 and 10
and updates to subtype 12.
-TYPE 106 SMF Records
-New FORMAT MG106CT values for SMF6ACTP=CONNECT*TYPE.
-TYPE 124 SMF Records
- Await a USER with need+data for new subtypes 2-5.
Change 38.104 Dataset XAMUSR variable USERTYPE='ACCT' is now set if the
VMACXAM value in the record was A.
Jun 30, 2020
Thanks to Randy Hewitt, DXC Technology, USA.
Change 38.103 -MXG 38.03/38.04 TYPE7072 fails if PDB is on TAPE, with
E2TY70 ERROR: DATASET PDB.TYPE70PR NOT FOUND (after it had been
VMAC7072 created, and there was no DELETE statement on the log).
Jun 30, 2020 -Changing from TAPE to DASD accidentally circumvents the
error that was introduced in Change 38.055.
-But this correction in VMAC7072 is INCOMPATIBLE requiring
you to see IF YOU HAVE MEMBER E2TY70 in your tailoring
'USERID.SOURCLIB' library, as you must change _LTY70 to
_WTY70 in that member. Fortunately, I doubt any site
has actually ever used that obscure exit member, and with
this change, the MXG default is _WTY70.
-But we have NEVER recommended the PDB library be on
tape for the BUILDPDB process for several reasons:
-tapes have no directory, so the full tape has to be
read from the start to find each dataset, and
-BUILDPDB has many datasets that are written to and
then read from the PDB library, causing many rewinds
which increases the job run time.
Thanks to Silambarasan Shanmugam, IBM, INDIA.
Change 38.102 Support for Thruput Manager TMT7123/TMT7124 JUL 2020.
VMACTPMX Compatible Changes:
Jun 26, 2020 -New variables in dataset TPM10:
TPMCMSTA='TENANT*4HRA*MSU PER*HOUR'
TPMCMSTI='TENANT*INT USE*MSU PER HOUR'
-New variables in dataset TPMSLM
TPMSLJF2='MISCELLANEOUS*FLAGS*2'
TPMSLJF3='MISCELLANEOUS*FLAGS*3'
TPMSLJFM='MISCELLANEOUS*FLAGS*M'
These flags are decoded in the comments.
-See Change 38.132 which creates DCOLBKUU for Unix.
Change 38.101 The TYPE42DS original default display FORMAT TIME13.3 for
VMAC42 duration variables to display milliseconds is changed to
Jun 26, 2020 TIME13.6 to display the full microsecond resolution that
has been in the stored values for decades (MVS/ESA?).
Thanks to John Burg, IBM, USA.
Thanks to Mark Rader, IBM, USA.
Thanks to Kathleen C McManus, Aetna, USA.
Change 38.100 Support for OAM Cloud Tier
EXTY8500 -New variables in TYPE85AC dataset:
FORMATS R85INST ='INSTANCE*ID'
IMAC85 R85CLDID='ID OF*ENTRY IN*CLOUDID*PROVIDER'
VMAC85 R85CINST='CLOUD*INSTANCE*ID'
VMXGINIT -Many new variables added to TYPE85ST:
Jun 23, 2020 R85PEWO R85PERO R85PEDO R85PDWB R85PDRB R85PDDB
Aug 14, 2020 R85POWB R85PORB R85PODB R85PTWB R85PTRB R85PTDB
R85BOWB R85BORB R85BODB R85BTWB R85BTRB R85BTDB
R85B2OWB R85B2ORB R85B2ODB R85B2TWB R85B2TRB R85B2TDB
R85RCLB R85PUWB R85PURB R85PUDB R85PEWB R85PERB
R85PEDB R85BOAO R85B2OAO R85BTAO R85B2TAO R85BOAB
R85B2OAB R85BTAB R85B2TAB R85PCWB R85PCRB R85PCDB
R85PCWO R85PCRO R85PCDO
-New variables in TYPE85SO dataset:
R85DSL ='DISK*SUBSYSTEM*RECOVERED*OBJECT'
R85TCLID='ID OF*ENTRY IN*CLOUDID*TABLE'
-New variable in TYPE85IB dataset:
R85SCLID='ID OF*ENTRY IN*CLOUDID*TABLE'
-New variable in TYPE85RE dataset:
R85CLDID='ID OF*ENTRY IN*CLOUDID*TABLE'
-New dataset TYPE8500 for new subtypes 100,101,102,103
dddddd dataset description
TY8500 TYPE8500 LCS CLOUD WRITE READ DELETE
with new cloud variables
R850CID ='ID OF*ENTRY IN*CLOUDID*TABLE'
R850SGN ='OBJECT*STORAGE*GROUP*NAME'
R850COLN='COLLECTION*NAME'
R850OBJN='OBJECT*NAME'
R850INST='INSTANCE*ID'
R850FLGS='PROCESSING*FLAGS'
R850OLEN='OBJECT*LENGTH'
R850OOFF='OBJECT*OFFSET'
R850LIQT='LCS*INPUT*WORK*QUEUE*TIME'
R850LDQT='LCS*DISPATCHER*QUEUE*TIME'
R850LEQT='LCS*EXECUTION*QUEUE*TIME'
R850LCLT='LCS*CLOUD*ACCESS*TIME'
R850RC ='LCS*RETURN*CODE*TIME'
R850RS ='LCS*REASON*CODE*TIME'
and R850SUB identifies the Subtype/Event
Thanks to Scott Rowe, SSA, USA.
Change 38.099 Sorts of CICS stats sometimes calculated negative DURATM
VMAC110 values for CICS statistics datasets. We also found that
SCICSORT some no longer needed to be deaccumulated. The sort order
UTILBLDP was changed to correct the DURATMs and the DIF logic was
VMXGCICI removed. In addition, only the records which contained
Jul 3, 2020 activity are now output. VMXGCICI was revised to remove
sorts and DIFs that were being done and many steps were
eliminated since it is now a single VMXGSUM execution.
-The CICLDR dataset was missing obs and incorrectly
and accidentally had a number of LDGxxxxx variables
that are now removed. Note that the new logic will
only output observations that had activity. For LDR,
there were 1,098,909 WORK.CICLDR observations but
only 2982 obs were in PDB.CICLDR that actually had
any activity.
-CICFCR dataset now only contains obs with activity,
with 15195 WORK.CICFCR and only 214 PDB.CICFCR.
-Protection for new MNSEGCL=5 5th and 6th triplets for
URIMAP and WEBSVC prevents a STOPOVER, but the two new
datasets were not created until Change 38.114.
Change 38.098 BMC SMF 74 CMF records variable R744STRC was zero, now
VMAC74 corrected by PTF BQM1658 for 6.1, BQM1659 for 6.2.
Jun 23, 2020 Note that MXG can not process both CMF and RMF records
in the same SMF Input file. See Change 38.095.
Change 38.097 Support for APAR OA56684 adds variables in TYPE78IO:
VMAC78 QWOSREAL='REAL*STORAGE*ON LPAR*IN MB'
Jun 30, 2020 QWOSFLG1='80X IF*QWOSREAL*IS VALID'
R783GFLX='ALIAS*MANAGEMENT*GROUPS*AVAILABLE?'
R783GFLX1='EADM*COMPRESSION*FACILITY*AVAILABLE?'
R783GFLX2='SCM*MEASUREMENT*AVAUILABLE?'
R783ISCB='TIMES*BUSY*SCM*OPERATIONS'
R783IECB='TIMES*BUSY*COMPRESS/DECOMPRESS'
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.096 Support for APAR PI98851 adds two variables to DB2STATS:
VMACDB2 QWOSREAL='REAL*STORAGE*ON LPAR*IN MB'
Jun 18, 2020 QWOSFLG1='80X IF*QWOSREAL*IS VALID'
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.095 Variable CMFPROD is now created for all SMF 70-79 records
VMACSMF and will be RMF or CMF-CPM or CMF-IPM and must be used
Jun 17, 2020 TO SELECT CMF or RMF if BOTH ARE WRITING SMF 70-79 data.
MXG can NOT correctly process that duplicated data in
one job. You would use this logic in //SYSIN:
%LET MACFILE= %QUOTE(IF CMFPROD=:'RMF';); or
%LET MACFILE= %QUOTE(IF CMFPROD=:'CMF';);
Change 38.094 SPINCOPY tests for macro variables were UPCASED to
BUILD005 protect for user typing LIBNAME in lower case.
BUIL3005
Jun 15, 2020
Change 38.093 Support for APAR OA59126 which adds two variables to
VMAC30 TYPE30_V,. TYPE30_4, and TYPE30_5 datasets:
Jun 12, 2020 SMF30NRDS='HWM*IN USE*DATA SPACES*DSPSERV'
SMF30DSCC='DATA*SPACES*CREATED*PROBLEM*STATE'
Change 38.092 Labels added.
VMACXAM
Jun 12, 2020
Change 38.091 Running MXG on Windows SAS, the Carbon Black AV product
TECHNOTE caused:
Jun 10, 2020 -ERROR: A lock is not available for WORK.OPTVAR.DATA.
This is extremely random and can occur anywhere in the
SAS job. It may also occur with other anti-virus types
of software as noted in SAS NOTE 36803. SAS suggests
that the following types of datasets be excluded from
monitoring. Disabling Carbon Black resolved the error.
or updating the Anti-Virus program to exclude these file
suffixes is recommended by SAS,
SASWORK
.lck
.sd2
.sc2
.SPDS
.sas*
.utl
ERROR: A lock is not available for WORK.OPTVAR.DATA when
executing MXG on WINDOWS (could be another file name).
The SAS Support reply:
-The lock on the file means the file is locked by another
processes when SAS tries to lock it. That other process
is often a third party application. SAS opens data sets
to update them but closes them at the end of the PROC or
DATA STEP. It is when the data set is closed that the 3rd
party applications open the files (i.e. lock them) and
prevent the next PROC or DATA STEP from opening the data
set. In some cases for a fraction of a second.
-In most cases, a good workaround is to set FILELOCKWAIT
at the top of your sasv9.cfg.
-You can find the location of your sasv9.cfg with
PROC OPTIONS OPTION=CONFIG; RUN;
-How to edit the sasv9.cfg:
The default SAS configuration file(sasv9.cfg) on Windows
is almost always protected by User Account Control (UAC)
because it is in c:\program files. Run notepad (or other
plain text editor like Notepad++) as an administrator to
edit the configuration file so that you can save changes.
-Wikipedia has a good definition of UAC here:
http://en.wikipedia.org/wiki/User_Account_Control
-Click the start circle or go to the start screen so you
can search for notepad in white box type notepad to
search for it(do not open yet)
-Right click on notepad|notepad++ and choose "Run as
Administrator".
-In notepad click File | Open.
-Change the file type you are looking for to all files
*.*
-Browse to the configuration path referenced above and
open the sasv9.cfg
-Make the change and save the sasv9.cfg. (you can leave
it open)
-You do not need to restart your machine and you can do
this live on a system. Any SAS session already running
will not have the setting but all future SAS sessions
will have the setting(s).
-ONLY USE A PLAIN TEXT EDITOR, DO NOT USE MICROSOFT WORD
TO EDIT THE SASV9.CFG
-After you start a new session of SAS you can check
that you have the setting by submitting:
PROC OPTIONS OPTION=FILELOCKWAIT;RUN;
-An alternative: copy sasv9.cfg to another directory, and
add to your SAS startup command:
-config 'newdir\sas.cfg'
Thanks to Kelly Ballamis, Zions Bancorporation NA, USA.
BUT TEN YEARS AGO, MXG NEWSLETTER FIFTY-FIVE, Jan 20, 2010 Reported:
8. Exposure on Windows to FAIL/ABEND with LOCK NOT AVAILABLE ERROR.
SAS Technical Support confirms that execution of SAS under Windows
has ALWAYS been exposed to a LOCK NOT AVAILABLE error because any
file's lock can be "grabbed" by another process at any time, even
a SAS dataset file in the WORK data library! MXG creates a dataset
WORK.ZZdddddd with PROC SORT, reads it with SET ZZdddddd and then
PROC DELETE DATA=ZZdddddd. But in several QA runs under Windows 7,
SAS lost its file lock after the DATA step closed successfully,
causing the PROC DELETE to fail, terminating the QA job:
-"Lock held by another process" is probably caused by a backup
program, antivirus program, encryption, or an indexing
application like Google Desktop that is accessing or touching
the SAS temporary files while they are in use by SAS. If a
backup program or virus scan is running on an interval, that
would explain why the problem is intermittent.
-To fix the lock, add the file extensions used by SAS to the
exclude list of the interfering application; you should exclude
.lck , .sd2, .sc2 , .SPDS, and .Sas*
where the .SAS* wild card excludes these extensions:
.sas7bdat /* DATA */ .sas7bfdb /* FDB */
.sas7butl /* UTILITY */ .sas7bitm /* ITEMSTOR */
.sas7bput /* PUTILITY */ .sas7baud /* AUDIT */
.sas7bcat /* CATALOG */ .sas7bbak /* BACKUP */
.sas7bpgm /* PROGRAM */ .sas7bdmd /* DMDB */
.sas7bndx /* INDEX */ .sas7bods /* SASODS */
.sas7bvew /* VIEW */ .sas /* SAS program file */
.sas7bacs /* ACCESS */
.sas7bmdb /* MDDB */
Caution: careful when excluding non-temporary SAS data sets from
a backup. SAS Recommends that backups occur when SAS is not
running.
Caution two: other applications can use those suffixes:
SC2 - windows scheduler
SD2 - sound designer
LCK - database control
SPDS - ACROBAT
-If the problem application is not a backup program or virus scan
then the cause is still probably a third party program. A way to
determine which program(s) are causing the lock is to use
utility from Microsoft Sysinternals called Process Monitor. You
can download Process Monitor for free from Microsoft at
http://technet.microsoft.com/en-us/sysinternals/
bb896645.aspx?PHPSESSID=d926
Open Process Monitor, click filter and make these 3 changes:
1)Path "begins with" "%temp%\SAS Temporary Files"
(Click ADD) (use your work path name, if different).
2)Process Name is Sas.exe then Exclude (click Add)
3)Process Name is Explorer.exe then Exclude (click Add)
Click Apply and OK.
Then clear the log.
Then start SAS and run the SAS program that creates the lock
error. What Process Name(s) are listed in Process Monitor?
This particular filter doesn't always find the problem.
Usually the best advice is to ask your internal support team
for help using this tool to find the problem
We have not yet been able to identify what process grabbed the
file lock, because the lock conflict is intermittent.
BUT: The pathname of the WORK data library was NOT the
SAS Default, it did not contain the text "TEMP" nor "SAS
Temporary".
We have changed that pathname to the SAS default, and
there has not (YET!) been a lock conflict, so we
presume/assume that the process causing the conflict
automatically excluded scanning of directories with
"TEMP" in their name.
Change 38.090 -SMF 83 Subtype 3 INPUT STATEMENT EXCEEDED because RELO
VMAC83 218 length 1415 exceeded $VARYING1024 guess for maximum.
Jun 10, 2020 LDAP document still shows length 256 for 218.
-RELO segments 113/114 are now supported, new variables
LDAP_POLICY_UPDATED and LDAP_FLGS.
-User observed last update was in 2013, "I did notice the
code had a significant vintage!"
Thanks to Graham Harris, RBS, ENGLAND.
Change 38.089 -Variable R7410FLG (TYPE IS*VIRTUAL*FLASH*MEMORY?) was not
VMAC74 set to 'Y' when true ('80'x), due to typo R710FLG='Y'.
Jun 9, 2020 -Support for these new EADM variables in TYPE7410.
Jun 23, 2020 R7410DFLG='EADM*COMPRESSION*IS*AVAILABLE?'
R7410DOCC='COMPRESSION*OPERATIONS'
R7410DOCD='DECOMPRESSION*OPERATIONS'
R7410DISC='1MB*INPUT*BLOCKS*COMPRESSION'
R7410DOSC='1MB*OUTPUT*BLOCKS*COMPRESSION'
R7410DISD='1MB*INPUT*BLOCKS*DECOMPRESSION'
R7410DOSD='1MB*OUTPUT*BLOCKS*DECOMPRESSION'
This was added by APAR OA56684.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.088 Support for CA VIEW SARR SMF Subtypes 34 and 35 create
EXSARR36 four new datasets:
EXSARR35 DDDDDD Dataset Description
EXSARI36 SARR35 SARRU35 REPORT ARCHIVAL DATE CHANGE
EXSART36 SARR36 SARRU36 CHANGE ARCHIVAL DATE ACTIVITY
VMACSARR SART36 SARRT36 TAPES ACCESSED
VMXGINIT SARI36 SARRI36 INDEXEX ACCESSED
Jun 9, 2020
Thanks to Steven W. Erikkila, USBANK, USA
Change 38.087 ERROR: Utility file open failed using PROC MEANS/SUMMARY
AUTOEXEC with a CLASS statement that includes many variables.
AUTOEXEU -To circumvent the problem, include the NWAY option in the
AUTOEXQA PROC MEANS/ PROC SUMMARY statement. SAS Note 17594 notes:
AUTOEZOS -Without the NWAY option, the procedure tries to create
CONFIG94 with a CLASS statement that includes many variables.
CONFIGEZ being created. This results in the error message above.
CONFIGT9 -Other circumventions include adding the NOTHREADS option
CONFIGVM to the PROC MEANS or PROC SUMMARY statement and/or using
CONFIMXG a BY statement instead of a CLASS statement, or in your
TECHNOTE AUTOEXEC file or CONFIG file.
Jun 8, 2020 -NOTHREADS option was already in CONFIGV9/9N/V9/T9 due to
Change 22.207 and is added in CONFIMXG/CONFIG94/EZ/VM,
and to AUTOEXEC/EXQA/EZOS/EXEU, for the circumvention of
this error.
-NOTE: THE LISTED MEMBERS ARE EXAMPLES: YOUR AUTOEXxx
and/or CONFIGxx are likely changes and will be in your
USERID.SOURCLIB dataset.
Change 38.086 Unused Change Number.
Change 38.085 UCICSCNT analyzes counts and bytes written for SMF 110
FORMATS records by SUBTYPE, APPLID, STID. and MNSEGCL. PROC FREQ
UCICSCNT and DATA steps were replaced with PROC TABULATE, and
Jun 3, 2020 duration added to the final report to see the frequency
of records. Both the average and maximum values are
reported but the MAX is more likely to reflect the actual
DFHSIT record interval for CICS statistics records.
In addition the number of bytes in the subtype segments
and the percentage of the total bytes is included.
-FORMAT $MGCICVER was added to decode the CICS Version.
-An INCODE= exit is added for tailoring, and examples
were added.
-The four Resource Records and the two Identity records,
Subtype 1 MNSEGCL 5 and 6, were not counted, nor were
Subtype 4 Exception records.
CICS RECORD SUBTYPES AND CORRESPONDING MXG DATASETS CREATED:
0=JOURNAL SEGMENT
CICSJOUR (DEFAULT IF UNKNOWN JOURNAL).
CICSSAP (IF IMACICSA ENABLED FOR SAP).
CICSSMED (IF IMACICSM ENABLED FOR SHAREDMED).
1=MONITOR/TRANSACTION
MNSEGCL=1 DICTIONARY RECORD - USED ONLY BY UTILEXCL.
MNSEGCL=2 CICSACCT (NO LONGER, ONLY EXISTED PRE ESA)
MNSEGCL=3 PERFORMANCE CLASS: CICSBAD, CICSTRAN
MNSEGCL=4 EXCEPTION: CICSEXCE
MNSEGCL=5 RESOURCE
COUNTER DATASET
MNR5NUMI CICSRDS CICS RESOURCE DATA CLASS
MNR5NUMF CICSRDFI CICS RESOURCE FILE DETAIL
MNR5NUMT CICSRDQU CICS RESOURCE TSQUEUE DETAIL
MNR5NUMD CICSRDPL CICS RESOURCE DPL DETAIL
MNSEGCL=6 IDENTITY
COUNTER DATASET
MNI6NUMI CICSIDNT CICS IDENTITY TRANSACTION INFO
MNI6NUMD CICSIDND CICS IDENTITY REALM/DISTING
2=STATISTICS ALL OTHER CICXXXXX
3=TS DATA SHARING STATS: CICXQ1,CICXQ2,CICXQ3,CICXQ4
STID: 121 122 123 124
4=CF DATA TABLE STATS: CICFS6D,CICSF7D,CICFS8D,CICFS9D
STID: 126 127 128 129
5=NAMED COUNTER STATS: CICNS4D,CICNS5D
STID: 124 125
Thanks to Luis Mendoza, BKFS, USA.
Change 38.084 Support for CICS/TS 5.6 (INCOMPATIBLE, FIELDS INSERTED).
VMAC110 -New Variables in CICSTRAN:
UTILEXCL SMMVSSCN='SHORT ON*STORAGE*COUNT'
Jun 1, 2020 SMMVSSTM='SHORT ON*STORAGE*DELAY*TIME'
XZZFYPTM='PASSWORD*VERIFICATION*TIME'
XSVFYPCN='PASSWORD*VERIFICATION*COUNT'
XSVFYKTM='KERBEROS*VERIFICATION*TIME'
XSVFYKCN='KERBEROS*VERIFICATION*COUNT'
-New Variables IN CICMNG:
MNGRMI='RMI*OPTION?' (Y/N)
MNGAPPNS='APPLICATION*NAMING*SUPPORT?' (Y/N)
MNGFREQ='FREQUENCY*HHMMSS'
MNGMCTNM='MCT*PROGRAM*NAME'
Change 38.083 Updated and enhanced parameters allow you to select the
ANALINIT reports of interest. Substantial doc improvements, using
May 28, 2020 PDB.JOBS.
Change 38.082 -New ASMRMFV Field Data Filter (FDF) support for the RMF
ADOCRMFV III Enclave Data Table (ENCG3) and an IMPORTANT FIX.
ASMRMFV -The Field Data Filter (FDF) feature of RMF III was added
May 29, 2020 in MXG Change 37.089 and allows you to filter raw RMF
data values when ASMRMFV reads the RMF III VSAM file,
reducing the size of the created RMFBSAM file. You can
filter table entries based on one or more numeric and/or
character fields, and is intended for advanced MXG users
building ad hoc data collection of RMF III data.
Section 31 in ADOCRMFV documents the FDF implementation.
-ASMRMFV can issue incorrect error message RMFV086E FIELD
NAME IS INVALID for a FDF IF expression. Some Variable
Name Table (VNT) entries were missing a required flag
byte thus causing the search for the expression field
name to fail. But some expressions worked fine.
-This is a PERVASIVE problem with the FDF feature and any
MXG users needing to use FDF for RMF III data filtering
should use this version of ASMRMFV, as it impacts all use
of FDF with MXG 37.03 or later.
-ASMRMFV now supports RMF III table fields up to 512
characters in length such as the EDEACCT field in the
ENCG3 table.
-Message RMFV088I is upgraded to support to the new
extended field lengths. There can be several continuation
RMFV088I messages until all character data has been
displayed as well as the equivalent value as hex digits
(0-9, A-F).
-However, when EBCDIC characters are used in an IF
expression as the user provided value ASMRMFV has an
internal limit of 64 hex digits shown in the RMFV088I
message. This is to prevent long repetitive strings of
X'40' hex digits in RMFV088I. The character value is
displayed in full.
-TUTORIAL:
The ENCG3 Enclave Data Table contains some very large
character fields from 32 up to 512 bytes that have
bearing on how an IF expression for these is coded.
When a character string is used in an IF expression all
possible characters are shown in RMFV088I messages
including trailing blanks.
For large fields such as the 512 byte EDEACCT field this
can result in many RMFV088I continuation messages in the
ASMRMFV log showing only repetitive trailing blanks.
Use the ':' (colon) operator modifier in the IF
expression to control the number of RMFV088I messages and
improve the efficiency of the compare process as well.
In this case only the number of characters in the IF
expression are shown in RMFV088I and only those
characters are used in the compare process.
As an example in ASMRMFV SYSIN instead of coding:
IF=(EDEACCT EQ C'ABC') 512 characters shown in RMFV088I
and all 512 are compared.
Use:
IF=(EDEACCT EQ: C'ABC') 3 characters shown in RMFV088I
and only 3 characters compared.
-Assembler options NOXREF and NORXREF added internally to
reduce ASMRMFV assembly output by 41,000 lines or 22%.
-ASMRMFV now automatically uppercases user specified
values in IF expressions for:
Service Class Names
Report Class Names
Workload Names
Resource Group Names
For example:
IF=(ASICNM EQ 'hot batch')
becomes:
IF=(ASICNM EQ 'HOT BATCH')
The WLM ISPF application does not accept lower case
for these names and neither will ASMRMFV. Descriptions
for these names may be mixed case for WLM or ASMRMFV.
-PROCENC subroutine was outputting one less ENCG3 entry in
a RMFBSAM record when there was still room in the output
buffer for one more.
-ADOCRMFV member's documentation has been updated for:
Section Contents
------- --------
0 Contents
5 Input Data Selection Parameters
12 Messages
13 Filtered Records
26 ASMRMFV and MXG PDB Data Relationships
31 Field Data Filtering (FDF)
37 Filtering The ENCG3 Table
40 Filtering The OPDG3 Table
42 Filtering The SCMG3 Table
46 Summary
====== CHANGES THRU 38.081 WERE IN MXG 38.04 DATED MAY 25, 2020 ========
Change 38.081 MXG 3803 only. The WEEKLY BLDSMPDB failed due to a typo
BLDSMPDB in line 667, which has 1 %end;
May 25, 2020 Remove that 1.
The error only occurs if BLDSMPDB is run on z/OA AND only
if WEEK points to a GDG.
Thanks to Jim S. Horne, Lowe's, USA.
Change 38.080 Support for z15 T02 8562 processor's (156 models) values
FORMATS in $MGRMIPS format, used in ASUMMIPS,GRAFCEC,GRAFWLM,
May 24, 2020 GRAFWRKX and VMACRMFV(RMFIII) to map the MIPS per MSU.
If you use those programs to report MIPS, you need 38.04.
Change 38.079 Support for APAR OA59541 for TYPE42 Subtype 27, adds new
FORMATS variables;
VMAC42 SMF42REOS='ERASE*ON*SCRATCH?'
May 28, 2020 SMF42RZRTY='ZHPF*CHANNEL*PROGRAM*FAILED?'
SMF42RCTCAH='TRANSPORT*COMMAND*AREA*HEADER*7FX'
SMF42RCTCAL='TCA*LENGTH'
SMF42RCFDCW='FIRST*DEVICE*COMMAND*WORD'
SMF42RCDSCB='DSCBS*WRITTEN'
SMF42RCLRAB='LOCATE*RECORD*AUXILARY*BYTE'
SMF42RCLRIC='LOCATE*RECORD*IMBEDDED*OP CODE'
SMF42RCLRC ='LOCATE*RECORD*COUNT'
SMF42RCLROP='LOCATE*RECORD*OPERATION'
SMF42RCLROPOR='ORIENTATION'
SMF42RCLROPOB='OPERATION*CODE'
SMF42RCLRAB0='TRANSFER*LENGTH*FACTOR?'
SMF42RCLRAB7='READ* COUNT*CCW?'
SMF42RCLRIC='LOCATE*RECORD*IMBEDDED*OP CODE'
Format $MG042VT was updated for new values, and new
MG042OR and MXG042OB are created.
Change 38.078 zVPS PLSDSPCN LABEL contained an unintended & character.
VMACXAM
May 22, 2020
Change 38.077 DB2 SMF 102 IFCID 143/144 fields QW0143UR/QW0144UR were
ANALDB2R increased to 10 bytes, 6 reserved bytes and new QW0143SI
VMAC102 and QW0144SI were inserted before QW014xUR in VMAC102,
May 22, 2020 and the format for QW0143UR/144UR in ANALDB2R updated.
Thanks to Terry Chao, DC Government, USA.
Change 38.076 Comments revised for the MIPFACTR which is now set from
GRAFWRKX the CPFCNAME using the $MGRMIPS format.
May 20, 2020
Change 38.075 DB2 APAR PH14037/UI65711 corrects the offset in DB2ACCTP
VMACDB2 records for QPACLOCN/QPACCOLN/QPACPKID/QPACASCH/QPACAANM
May 20, 2020 variables, which caused them to still be truncated. The
error was introduced by APAR PH05989/UI61107. There was
no change to MXG code, the IBM APAR corrected the offset.
Change 38.074 PDBAUDIT in BUILDPDB audits the daily PDB size metrics,
PDBAUDIT including the SAS compression percent PCOMPRESS, which
May 19, 2020 can be a negative value, whenever compressing a dataset
would have increased its size, and is reported by SAS:
"Compressing dataset PDB.STCVSM15 increased by 11.43 pct"
These datasets always have a small number of variables.
Thanks to Randy Hewitt, DXC Technology, USA.
Change 38.073 Significant cleanup of ANAL119 after a typo was found in
ANAL119 37.37 version (extraneous 3 preceding a RUN.) IPHOSTS DD
May 16, 2020 is no longer required but will be used if it is present
and all data steps are skipped if the input datasets are
not found.
Thanks to Tom Kelman, ATOS, USA.
Change 38.072 Type 30 Subtype 6 records have accumulated values but not
VMAC30 all INST counts were deaccumulated, CPUASRTM correction
May 15, 2020 was subtracted from raw rather than DIF'd values causing
a spurious warning message, and minimum SMF time .01 sec
was only a few hundred CPUUNITS which caused some small
negative values when CPUASRTM was non-zero.
The subtype 6 interval records are written instead of 2/3
for Early ASIDs, STCs that start before JES is up, like
ALLOCAS CAMASTER CONSOLE GRS JES2AUX PCAUTH RASP
SMSPDSE SMSPDSE1 TRACE
Thanks to Harald Seifert, Huk-Coberg, GERMANY.
====== CHANGES THRU 38.071 WERE IN MXG 38.03 DATED MAY 7, 2020 ========
Change 38.071 SAGANAL option SYNC59 was incorrectly flooring ENDTIME,
SAGANAL but now uses VMXGDUR to set the Interval Started. SYNC59
May 6, 2020 adds 1 minute and uses that hour, so with 15 min interval
data written at SYNC59, these are the hour intervals into
which the 15 min interval data is assigned.
Original 15:59 16:14 16:29 16:44 16:59 17:14
SYNC 0 hour 15 16 16 16 16 17
SYNC 59 hour 16 16 16 16 17 17
Using SYNC59 for SYNC59 data matches common sense.
Change 38.070 CICS Statistics 110-2 with SMFSTRQT='EOD' End of Day data
VMAC110 have invalid large values, with the same value repeated
May 2, 2020 for dozens of unique events in time sequence that would
normally be accumulated values with zero deltas when they
are deaccumulated, BUT EOD are NOT accumulated data. Each
obs is a separate event, and most values are wrong. In
addition, when EOD obs go thru MXG deaccum, obs are lost.
Intervals of 24 hours are not very useful for analysis.
EOD was accidentally set, and you can sum INT data to get
daily totals if that's what you need.
So, I can not make a business case that the EOD interval;
is needed, and with a circumvention, I'm not going to
pursue a PMR that would waste IBM and Customer time.
-When EOD records go thru Deacculation, many observations
are lost; I experimented with CICXML to bypass deaccum
for EOD, which did preserve observations, but I'm not.
going to implement that for other statistics datasets.
DO NOT USE EOD FOR SMFSTRQT STATISTICS REQUEST TYPE.
Change 38.069 XCOM input did not skip the 461 bytes added in 12.0.
VMACXCOM
May 1, 2020
Thanks to Peter J. Gray, DXC, AUSTRALIA.
Change 38.068 Support for Comm Server SMF 119 Subtype 11 ZERT revised
EXT119ZE to create new TYP119ZE dataset for each Zert instance,
IMAC119 which can have more than one obs per record, and remove
VMAC119 those variables from TYP11911 which has only one obs per
VMXGINIT SMF 119 subtype 11 record.
Apr 30, 2020 Updates to 73/74 for ICN1762 for IKET are not done, may
need data.
Change 38.067 Yet another TYPE42 invalid LENSR in Subtype 5 records has
VMAC42 revised the logic to compare the delta between offsets
Apr 30, 2020 with NRSR*LENSR, and if they do not, recalculate length
by dividing the delta by the NRSR, and if the CALCSRLEN
is an integer, use the new length for LENSR, or delete.
This was from old customer data and may not be a current
value, but this should finally eliminate exposures.
Thanks to John Compton, World Programming, ENGLAND
Change 38.066 Dataset ASUMCAPT was not labeled.
VMXGCAPT
Apr 24, 2020
Thanks to Randy Hewitt, DXC, USA.
Change 38.065 UTILROLL will rollup all observations in all datasets in
UTILROLL a data library into all datasets in another data library.
Apr 29, 2020 New examples added to combine PDBs created every four
hours into a daily PDB library, and to copy multiple days
back to WORK for reporting. Modified to use PROC SQL to
get the engine of the output libname on z/OS so it works
for tape or sequential PDBs. Also added FORCE to the
PROC APPEND to prevent warnings and added SORTEDBY and
ALLDATA datasets created by the macro to ROLLDROP.
Change 38.064 -After New Function APAR OA58759 of 3/26/2020 for RMF the
ASMRMFV ERB3RDEC decompression load module does not contain an
Apr 24, 2020 expected FMID. As a result ASMRMFV issues warning message
RMFV091W that the module is not from IBM. Processing
continues normally, but Return Code 0004 is set.
-ASMRMFV will now also check for an 'IBM' character string
in ERB3RDEC before issuing RMFV091W. The RMFV091W message
was also incorrectly formatted.
Change 38.063 Variables WKRSENCP/WKRSENCV/WKRIENCP/WKRIENCV caused
VMACCMFV INVALID DATA messages because they were INPUT as &RB.4.
Apr 24, 2020 (which worked fine when the fields were zeros) but they
are non-zero and are input with &PIB.4 informat.
Thanks to John Kim, TELUS, CANADA.
Change 38.062 -DB2STAT0 variable QW0225_WARN was incorrectly treated as
VMACDB2 bytes, and it is SERVICEABILITY.
Apr 22, 2020 -Support for APAR PI92652 that adds I/O Interrupt CPU time
variables QWSxIIPT variables in dataset DB2STAT4.
-Support for APAR PI82191 that adds 3 _DPAGE variables to
dataset DB2STAT4, which per the APAR text, are now also
subtracted to correct the three _REAL variables. The
APAR text listed a fourth PVTSTG_DPAGE field, but it
does NOT exist in the records with segment length 320.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.061 Support for z/OS Connect EE SMF 123 Version 2 Records
EXTY1232 create new dataset:
IMAC123A DDDDDD DATASET Description
VMAC123A TY123A TYPE123A Z/OS CONNECT EE AUDIT V1
VMXGINIT TY1232 TYPE1232 z/OS CONNECT EE AUDIT V2
Apr 30, 2020 The new version 2 record creates new TYPE1232 dataset
Jul 15, 2020 because of many new variables.
-Member TYPE123A creates TYPE123A and TYPE1232 for EE.
-Member TYPE123 is archaic, for the S/390 Parallel Query
Server SPQS SMF 123 Record datasets DB2SPQS/DB2SPQAB.
-Jul 15 typo spelling SM123SORRCVD corrected.
Thanks to Adam Banbury, PNC, USA.
Thanks to Robert Carter, PNC, USA.
Thanks to Robert Richards, PNC, USA.
Change 38.060 CICSTRAN observations are written at task termination,
VMAC110 so long running transactions won't have observations,
Apr 9, 2020 but the CICS SET MONITOR command FREQUENCY argument will
create interval CICSTRAN observations, which can be
identified with RTYPE='F'. RTYPE formatted values:
'C'='C:TERMINAL CONVERSE'
'D'='D:USER EMP DELIVER REQUEST'
'F'='F:FREQUENCY REQUEST'
'M'='M:SEMI-PERMANENT MIRROR SUSPEND'
'S'='S:SYNCPOINT'
'T'='T:TASK TERMINATION'
Thanks to Rob Hollingum, HSBC, ENGLAND
Thanks to Renata Hoyland, HSBC, ENGLAND
Change 38.059 -zVPS XAMCUV records with LPARNAME='TOTAL' weren't output
EXXAMCUV because they duplicate the detail record's values. zVPS
FORMATS now sets LCUCPUID=96 for all total records, so the test
VMACXAM to NOT output in EXXAMCUV now tests to skip the 96's.
Apr 8, 2020 This test is located in the Data Set Exit member so that
you can always override my decision to not OUTPUT them.
-Variables LCUCPUID LCXCPTYP are added to the _BXAMCUV BY
list for dataset XAMCUV.
-XAMCUV records have LCXCPTYP=1 for CP/GP engine instead
of zero, so the MGXAMTY format now maps that value also.
Thanks to John Holiday, Queensland Government, AUSTRALIA.
Change 38.058 CIMS/IMF datasets CIMSDBD,CIMSDB2,CIMSMQ had zero obs
VMXGINIT in 37.37-38.02 because the three SELECTDBD/DB2/SELECTMQ
Apr 21, 2020 macro variables added for BUILDIMS were only %GLOBALed
in VMXGINIT where they should have been %LET to defaults.
The three statements have been added to VMXGINIT, but you
can insert these three statements in your //SYSIN for
your CIMS/IMF processing jobs and they will be populated.
%LET SELECTDBD=%STR(OUTPUT _WIMFDBD;) ;
%LET SELECTDB2=%STR(OUTPUT _WIMFDB2;) ;
%LET SELECTMQ =%STR(OUTPUT _WIMFMQ;) ;
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 38.057 Support for SYSVIEW Subtype 2 record creates new datasets
IMACSVIE PDB.SV02INT - Interval Data - One Obs per Minute.
VMACSVIE Merge of 263 datasets, 1440 Obs daily.
VMXGINIT PDB.SV02MQ - MQ Interval Data - One obs per MQ Subsys
Apr 20, 2020 Merge of 25 datasets, 2880 Obs daily.
PDB.SV02LP - LPAR Interval Data - one per ARGEIGHT,
individual LCPUADDR 0000-000B, and ALL
CP,IFA,IIP,SP, 24480 obs THIS LPAR.
PDB.SV02CP - CPUPLPAR for all LPARs, 47520 obs.
PDB.SV02WL - WLM Service/Reporting Class 250560 obs.
PDB.SV02PLOT - Control Variables, one obs/record.
Thanks to Nagaraj Pudokotia, ATOS, INDIA.
Thanks to Martyn Jones, CPTGLOBAL, ENGLAND.
Change 38.056 -If you tried to reset an option with VMXGOPTR to ORIGINAL
ANALHSM that hadn't previously been set using VMXGOPTR, the code
VMXGOPTR generated here was "OPTIONS 1;" which caused ERROR 13-12:
Apr 6, 2020 Unrecognized SAS option name 1, and execution terminated.
-Now: VMXGOPTR detects that that option had not been set,
stores the current value and does not execute OPTIONS.
-ANALHSM was the culprit that exposed the error and was
corrected.
Thanks to Jack Hyde, OPTUM, USA.
Change 38.055 Change 37.123 (MXG 37.04) incorrectly changed variable
VMAC7072 PCTMVSBY which impacted PLCPRDYQ and SHORTCPS in datasets
VMXGRMFI PDB.TYPE70 and PDB.RMFINTRV.
Apr 30, 2020
Thanks to Paul Naddeo, Fiserv, USA.
Thanks to David Bixler, Fiserv, USA
Thanks to Robin Hanley, Fiserv, USA
Thanks to Bernie Ethridge, Fiserv, USA.
Change 38.054 -ALL ASCII SITES SHOULD ENABLE %AUTOINST IN IMACINIT.
AUTOINST -Concurrent ASCII SAS sessions can error due to INSTREAM
IMACINIT file sharing. The same INSTREAM.SAS file is used on ASCII
May 3, 2020 for every session, so multiple concurrent sessions error
because of the unintended file sharing. The new &AUTOINST
%MACRO creates the temporary INSTREAM file in the session
WORK libname, which is not sharable with other sessions.
FILENAME INSTREAM CATALOG 'WORK.TEMP.INSTREAM.SOURCE';
a. Put the %AUTOINST; statement in the member IMACINIT
in your "USERID.SOURCLIB" tailoring library and the
unique file name will always be allocated.
b. Put the %AUTOINST; in AUTOEXEC, replacing the
INFILE INSTREAM statement.
c. Issue the %AUTOINST; in your SYSIN at start.
-ALL ASCII SITES SHOULD PUT %AUTOINST IN IMACINIT.
-z/OS sites can enable %AUTOINST in IMACINIT and then the
INSTREAM filename will always be created if it was not
already allocated.
Change 38.053 Typo, variable not found, QHSSSID should be QWHSSSID.
ANALDB2T
Mar 30, 2020
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 38.052 Spurious WARNING: MISSING %MEND Statement for VMXG344 is
BUILDPDB sometimes printed after prior error conditions; adding
BUILDPD3 the name of the %MACRO to the %MEND eliminates message.
BUILD001
BUIL3001
Mar 29, 2020
Change 38.051 Using the SAS FTP Access Method, &MXGABND=1 is now set so
VMACSMF that errors (e.g. the SMF file is in use) that can cause
Mar 27, 2020 the SAS Session to hang doing nothing, instead will now
terminate with USER ABEND 69.
If the session still hangs, and you have access to the
directory where the SAS log is being written by that
active session, you should be able to get read access to
the active session's log to see if there are messages
before you kill the session.
Thanks to Richard Way, Office Depot, USA.
Thanks to Amlan Mitra, Office Depot, USA.
Change 38.050 Variable QBSTPCO in dataset DB2STATB was always a
VMACDB2 missing value after DB2 Version 9 due to MXG logic
Mar 24, 2020 error for its INPUT.
Thanks to Flavio Lima, US.IBM.COM, USA.
Change 38.049 -New parameter ROLLWEEKS=5 added to let you keep more
BLDSMPDB weeks than the 5 needed to build a month. NOTE: this
Mar 24, 2020 only applies on zOS or ASCII with STATIC libnames.
With GDGs on zOS or AUTOALOC on ASCII ROLLWEEK is
disabled.
-So if you want to keep 6 weeks of rolling weekly
data specify rollweeks=6. If the WEEK6 LIBNAME is
not found an error message is generated.
Thanks to Richard Haynes, Blue Cross Blue Shield of Kansas, USA.
====== CHANGES THRU 38.048 WERE IN MXG 38.02 DATED Mar 23, 2020 ========
Change 38.048 Support for z15 INCOMPATIBLE z/VM MONWRITE 6.4.19.1 due
VMACVMXA to insertion of new EXTND256-EXTND287 counters in dataset
Mar 20, 2020 VXPRCMFC and new variables CORCTLMT CORTLSEQ in VXPRCMFM.
Many ERROR. PRCMFC HARDWARE COUNTER UNEXPECTED messages,
and datasets VXPRCMFC/VXPRCMFM have no observations, but
all the other z/VM MONWRITE datasets are not impacted
Thanks to David Campbell, SunTrust, USA.
Change 38.047 Variables R7023DID/R7024DID, Domain ID, are added to the
VMAC7072 end of the BY List for datasets TYPE7002 and TYPE70X, and
Mar 18, 2020 R7023DID is kept in TYPE7002.
Thanks to Stephen Hoar, Lloyds, ENGLAND.
Change 38.046 Data Set Labels were revised:
VMACDB2 DB2PST: DB2 STATS GLOBAL BUFF POOL
Mar 17, 2020 DB2PAT: DB2 GLOBAL BUFF POOL ATTRIBS
Change 38.045 MXG sets option REUSE=NO to prevent a User change to YES
VMXGINIT in this just-discovered obscure option, that controls how
Mar 17, 2020 free-space is used when new observations are added to an
existing compressed SAS dataset, i.e., whether new obs
are inserted in free space or added at the end, but with
REUSE=YES, and COMPRESS=YES, the POINT= dataset option
ABENDs because it cannot open compressed SAS datasets.
MXG uses POINT= and sets COMPRESS=YES default value.
PROC APPEND disregards REUSE=YES, adding new obs at the
end of the dataset. REUSE is an attribute of the dataset
and cannot be changed for that dataset.
Thanks to Richard Haynes, Blue Cross Blue Shield of Kansas, USA.
Change 38.044 VSAM Extended Addressability datasets values for sizes
VMAC60 VVRDSHA VVRDSHU VVRHARBA VVRHURBA must be multiplied by
Mar 15, 2020 VVRAMCIV, the CISIZE. New variable VVREXTAD='Y' if this
is an Extended Addressability dataset (not to be confused
with Extended Format datasets).
Thanks to Michael Friske, FMR, USA.
Change 38.043 Documentation only. Example 10 show ways to select or
READDB2 exclude data by QWHSSSID SubSystem ID.
Mar 14, 2020
Change 38.042 Your USER SMF record type descriptions are in IMACSMFF in
IMACSMFF your tailoring, which adds them to $MGSMFID when FORMATS
Mar 13, 2020 is run, but the MXG syntax - an eight-character VALUE,
with a leading blank if TYPE is LT 1000 - was not stated.
A seven-character value without blank caused no error,
but those types had no description in ANALID reports.
Thanks to Jeff Harder, Indiana Farm Bureau Insurance, USA.
Change 38.041 Support for APAR OA57105, adds to TYPE62/64
VMAC62 Dataset TYPE62 New Variables
VMAC64 SMF62JOBID ='JOB*ID'
Mar 12, 2020 SMF62SYSPLEX='SYSPLEX'
Variable SMF62DEF removed, did not exist and caused
variables SMF62DET and SMF62DKL to be missing/blank.
Dataset TYPE64 New Variables
SMF64JOBID ='JOB*ID'
SMF64SYSPLEX='SYSPLEX'
Change 38.040 OMEGAMON TEMS Subtype 35 INVALID ARGUMENT THREE because
VMAC112 the text length was increased from MXG's original guess
Mar 14, 2020 of 256 with a length of 261, so the lengths are now 512.
Thanks to Jim Czechanski, Northwestern Mutual, USA.
Change 38.039 Support for new variables INREI and JCLJJ in TYPETPMX.
VMACTPMX
Mar 5, 2020
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.038 Dataset TYPE73 variable SHIFT was not populated; the code
VMAC73 for IMACSHFT was only in the code blocks for TYPE73P/L.
Mar 4, 2020
Thanks to Mark Hiltbruner, State of South Dakota, USA.
Change 38.037 -MQM Header/Correlation variables that are now kept:
VMAC116 Dataset MQMACCTQ
Mar 11, 2020 QWHCAID QWHCCVMQ QWHCCN
QWHCPSB QWHCPST QWHCTASK QWHCTNO QWHCTRN QWHCXTYP
QWHSACE QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN QWHSSTCK
QWHSWSEQ WTCORREL
Dataset MQMACCT
QWHCAID QWHCCN QWHCCVMQ QWHCNID QWHCOPID QWHCPSB
QWHCPST QWHCTASK QWHCTNO QWHCTRN QWHCXTYP QWHSACE
QWHSIDMQ QWHSISEQ QWHSRN QWHSSTCK QWHSWSEQ
Dataset MQCFSTAT
DSECT WTCORREL WTASINTE WQBASENA
Dataset MQCHININ
QWHSACE QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN QWHSSTCK
QWHSWSEQ
Dataset MQMQUEUE
QWHCAID QWHCCCMQ QWHCCN
QWHCPSB QWHCPST QWHCTASK QWHCTNO QWHCTRN QWHCXTYP
QWHSACE QWHSIDMQ QWHSISEQ QWHSMTN QWHSRN QWHSSTCK
QWHSWSEQ
-Alignment of the WTAS INPUT now populates WTAS variables.
-The code segment for SUBTYPE=2 was relocated.
-Dataset MQMACCTQ is only output for SUBTYPE=1.
Thanks to Richard Simpson, CPTGLOBAL, AUSTRALIA.
Thanks to Martyn Jones, CPTGLOBAL, ENGLAND.
Change 38.036 -TYPEBETA variables L030SRCJCSY/JCUS, S055IPSERVI were
VMACBETA incorrectly spelled in the KEEP= list and are now kept
VMACBE97 as L030SRCJCSYS/L030SRCRCUSR/S055IPSEVI.
Mar 1, 2020 -TYPEBE97 variables B9759STY_1HEX B9759STY_2HEX were also
corrected to B9759STY_1_HEX andB975STY_2_HEX.
Change 38.035 TYPE1131 vars EXTND247/252/264/265 now KNOWN COUNTERs.
VMAC113
Feb 28, 2020
Thanks to Harald Seifert, Huk-Coburg, GERMANY.
Change 38.034 APAR OA59002 corrects invalid values in SMF89UZT in the
TECHNOTE TYPE89 dataset.
Feb 27, 2020
Thanks to Nick Varley, SYNCSORT, USA.
Change 38.033 -SMF Signature Type 2 Subtype 1 and 2 can print MANY log
VMACSMF "BACK2BACK HEADER" messages, if you have changed the
Feb 28, 2020 IFASMFDL program default option SIGSTRIP to NOSIGSTRIP.
IFASMFDL is the "SMFDUMP" program for SMF LogStreams, and
that SIGSTRIP default is to "Strip", i.e. NOT WRITE the
SMF Type 2 Subtype 1/2 records to the Output SMF file.
-The MXG _SMF Record Processing logic that writes those
Header/Trailer/First/Last diagnostics messages was not
updated when the VMAC0203 was updated in 2017, and these
new type 2 records caused spurious log messages. Datasets
TYPE0201/TYPE0202/TYPE0203 were correct as the messages
have no impact on output datasets. You can use
==> TO SUPPRESS PRINTING OF ALL SMF DIAGNOSTIC MESSAGES, USE:
==> //SYSIN DD *
==> %LET SMFPUTHD=NO;
or you can restore your IFASMFDL JOB to SIGSTRIP default,
or you can use VMACSMF with Change 38.033+ (MXG 38.02).
-If you are back-level at MXG 36.04, then you will also
also need the DODSCRDT/READRATE/VMXGINIT members.
Macro variable SMFPUTHD was added in MXG 31.31.
-This _SMF header code is ALWAYS USED WHEN MXG READS SMF,
so you will see those diagnostic messages, when TYPE 2,
subtype 1 or 2 records are present, in the SMF file,
even if you didn't request Type 02 record processing.
Change 35.266 notes "Even After OA?????, SYSTEM='DUMY'
Type 02 14 byte records were still found." and they
still are; the first SMF Header Message with NOSIGSTRIP
has "DUMY' and not the actual system, but the "FIRST"
message that follows will have the actual SYSTEM name.
(The APAR number in that APAR change is lost.)
-There were fifty ID=2 ST 1/2 messages per minute, or
about 288,000 SYSOUT print lines per day, which could
could cause a 722 SYSTEM ABEND.
How did I miss this in 2017 when subtype support was
added? The original customer could not ftp SMF data, so
LIST; was used to print a hex dump of each subtype,
which UTILBHEX converted to readable records, so there
were (only) two back to back (expected) ID=2 records.
You must be at MXG 37.06 or later to use this VMACSMF.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 38.032 Many missing values in WSFAUDIT dataset from TYPEWSF are
VMACWSF valid as the record only contains nulls starting in byte
Feb 26, 2020 153. Vendor is to be contacted.
Change 38.031 Support for APAR OA56683 adds SMFBOOST variables (System
FORMATS Recovery Boost) to dataset TYPE70:
VMAC7072 BOOSTACTIVE='BOOST*ACTIVE*FULL*INTERVAL'
Feb 20, 2020 BOOSTINFO ='BOOST*INFO*PARTIAL*INTERVAL'
BOOSTCLASS ='BOOST*CLASS'
and FORMAT MG070SB decodes BOOSTACTIVE and BOOSTINFO as
ZIP or SPEED or BOTH. CLASS is either IPL or SHUTdown.
Thanks to Martin Packer, IBM, EUROPE!
Change 38.030 The example user tailoring for multiple TMS catalogs in
ADOCTMS5 ADOCTMS5 (that you EDIT into your IHDRTMS5) ABEND 992 if
Feb 20. 2020 the CRDDD days value was greater than 366; now an error
message and hex dump of the first 5 eliminates the ABEND.
Change 38.029 z/VM MONWRITE dataset VXAPLSLM (Z/VM LINUX MEMORY)
VMACVMXA variable SHARERAM is zero if Linux is not RHEL8.
Feb 14. 2020
Change 38.028 -FDF (Field Data Filter) support added for the RMF Monitor
ADOCRMFV III ZFXG3 (zFS Performance Data Table). General ASMRMFV
ASMRMFV support for this table already existed.
VMACRMFV -Sysout output lines from ASMRMFV assembly reduced.
Feb 21, 2020 ** IMPORTANT **
Feb 28, 2020 -National character (@#$) pattern filter is now the '^'
caret character NOT the '.' period character. There was
a conflict when an RMF III table field contained a
DSNAME. The caret character may not print with some
SYSOUT character sets.
-This documentation section in member ADOCRMFV is added
for new FDF support:
44 Filtering The ZFXG3 Table
Remaining existing section numbers are incremented by 1.
-FDF GOVAT macro call for ZFXG3 table was incomplete.
Table selection would not occur when needed if ZFXG3 was
not explicitly selected when using FDF.
-VMACRMFV did not populate variable ENCCFL2 in ZRBENC.
====== CHANGES THRU 38.027 WERE IN MXG 38.01 DATED Feb 17, 2020 ========
Change 38.027 -TYPE42D3 and TYPE42D4 datasets had the below variables
VMAC42 incorrectly INPUT as SMF42Gxx instead of SMFA2Gxx so they
Feb 13, 2020 were not kept nor labeled.
Dataset TYPE42D3
SMFA2GUA SMFA2GUB SMFA2GUD SMFA2GUE SMFA2GUF SMFA2GUG
SMFA2GSH SMFA2GSI SMFA2GSJ SMFA2GSK
Dataset TYPE42D3
SMFA2GVA SMFA2GVB SMFA2GVD SMFA2GVE SMFA2GVF SMFA2GVG
SMFA2GTH SMFA2GTI SMFA2GTJ SMFA2GTK
Some SMF42Gxx and SMFA2Gxx variable's label incorrectly
had "*DASD" which was removed.
Thanks to Michael Friske, FMR, USA.
Change 38.026 -New variables STC28CTP and STC28FLG are now INPUT and
VMACSTC kept in dataset STCVSM28, variables STC19CTP and STC28CTP
Feb 13, 2020 are formatted $MGSTCCT to display Cartridge Type.
Thanks to Randy Hewitt, DXC, USA.
Change 38.025 Support for CICSTRAN Optional CPICAOR/CPICAOR user field
IMACICXC that populates USERCHAR.
UTILEXCL
Feb 12, 2020
Change 38.024 -Support for zVM VXPRCAPM dataset Crypto Types 11,12,13
VMACVMXA CEX5S/CEX6S/CEX7S, which printed "UNDECODED CRYPTO TYPE".
Feb 10, 2020 -Variable IODSSCH in VXIODDEV dataset is incorrect for
intervals with more than 65K I/Os, short by 65K counts,
but RDEVSKCT captures all I/Os, so MXG now sets variable
IODSSCH=RDEVSKCT for those intervals.
Thanks to Graham Harris, RBS, ENGLAND.
Change 38.023 RMF ZFX variables ZFX_IO_WAIT_TIME, ZFX_LOCK_WAIT_TIME
VMACRMFV and ZFX_MONITORED_SLEEP_TIME in dataset ZRBZFX can be
Feb 10, 2020 negative values because the ZfS interface bases average
response times on requests since last statistics reset,
which can be very long. zFS development is aware of their
design flaw but have not yet responded with a correction.
Change 38.022 Label for EXTEND164 was changed for the z14 and z15 to:
VMAC113 EXTND164='DIRWRIT*TO L1-I*ON CHIP*L3 INTVNT'
Feb 10, 2020
Thanks to George A. Frey, PNC, USA.
Change 38.021 PROC TIMEPLOT example to show concurrent job executions
ANALJOBS and SGPLOTS of ANALCNCR statistics for all jobs or for
Feb 9, 2020 selected jobs.
%ANALJOBS(PDB=PDB,INCODE=if JOB I: ('SYS','PAY'));
Change 38.020 Support for TYPE73 variable SMF73CPD Connection Types are
FORMATS added to $MG073CD format.
Feb 7, 2020 '33'X='33X:COUPLING EXPRESS SR' /*OSM*
'34'X='34X:COUPLING EXPRESS LR' /*OSM*
Thanks to Ehren Bailey, Progressive Insurance, USA.
Change 38.019 Support for DB2 APAR PH18739 EPIC 1016 that adds a new
VMAC102 variable QW0389IT='NUMBER*OF INDEX*TRANSVERSALS' to
Feb 6, 2020 dataset T102S389, COMPATIBLE, using a reserved field.
Thanks to Harald Seifert, Huk-Coburg, GERMANY.
Change 38.018 SAS levels prior to TS1M6 for ODS PDF should avoid use
TECHNOTE of CONTENTS on the ODS statement. There are several
Feb 5, 2020 errors that can be caused and any graphs may overlay
the contents. For details see:
http://support.sas.com/kb/20/666.html
Change 38.017 -TYPE80A INPUT EXCEEDED ERROR due to a HOME segment that
VMAC80A had no data following, now protected.
Feb 11, 2020 -Support for TYPE80TK fields TOKMARCHIDE,TOKMSISEMAIL,
TOKMARCSISID TOKMIRRDAUTO.
-SMF 80 SHORT EXTENDED RELOCATE FOUND messages were caused
when a field input with $VARYINGnn LEN was increased with
the actual data length LEN that is greater than the nn.
-The TYPE80TOK segments with TOKSUBSY='CSDATA' are "user"
or "customer" fields added by vendors or installations.
One CSDATA record where TOKDANAM=SISLAST was the last in
the record was truncated, with length 16 with only 14
bytes followed. Other SISxxxx segments were the last in
the record and were not truncated. An MXGNOTES is printed
when truncation is detected and protected.
Thanks to Joe Faska, DTCC, USA.
Change 38.016A ANAL95TH uses PROC TABULATE to create 95th percentile,
ANAL95TH mean and max response and resource statistics, with
Feb 5, 2020 two examples of CICSTRAN.CICSTRAN by TRANNAME, one
across all executions and one by TRANNAME for 15 min
intervals, and one for PDB.JOBS by JOBCLASS for hour
intervals, but the syntax can be used for any data.
Thanks to Robert Barth Cross, IBM, USA.
Change 38.016 SGPLOTS referenced &PDBMXG..NATADAPCT which did not
ANALNATR exist. Changed to PDBOUT.NATADAPCT.
Feb 5, 2020
Thanks to Mark Hiltbruner, State of South Dakota, USA.
CHANGE 38.015 See Change 38.061.
CHANGE 38.014A ASCII Execution ERROR: Template 'Styles.MXGxxxx' was
TECHNOTE unable to write to template store when attempting to
Jan 29, 2020 update the FORMAT directory, because a separate SAS
Windows session was using the LIBRARY catalog.
CHANGE 38.014 Support for IMS APAR PH14569(v14) and PH21001 (V15)
VMACIMS which populates the USERID field in IMS 22 log record.
Jan 29, 2020
CHANGE 38.013 Support for BETA93 and BETA97 Version 7.1.
FORMATS -Variables added to BETA9749 dataset:
VMACBETA B9749PGM B9749VER B9749PTF B9749CDT B9749CTM B9749RC
VMACBE97 B9749IC B9749STIME B9749ETIME B9749INFO B9749SELPTM
EXTYB97T B9749SCPUTM B9749SGETIO B9749SPUTIO
EXTYB97U and the accounting fields are correctly aligned now.
EXTYB97V -New dataset BETA9755 variables:
VMXGINIT B9755INDICAT B9755USER B9755IPCLN B9755IPSEV
Feb 13, 2020 B9755IFLGS B9755HOSTIPORT B9755SERVPORT B9755IPHOST
B9755IPCLIENT B9755IPSERV B9755IPSERVI
-New dataset BETA9759 variables:
B9759MAXSUBT B9759CURSUBT B9759STBYTE B9759RQUST
B9759VERSION B9759INTERCNT B9759INTERTIME B9759NTAB1
B9759NTAB2 B9759STY_1 B9759STY_2 B9759ALLCNTW
B9759ALLCNTN B9759ALLCNTS B9759ALLCNTB
-New dataset BETA9759SFF variables:
B9759MJRCPU B9759MJRCPUN B9759MJRSRB B9759MJRSRBN
B9759MJRZIIP B9759MJRZIIPN B9759MJRCPU B9759MJRCPUN
B9759MJRSRB B9759MJRSRBN B9759MJRZIIP B9759MJRZIIPN
-New dataset BETA9759SFF variables:
B9759MNRCPUN B9759MNRSRB B9759MNRSRBN B9759MNRZIIP
B9759MNRZIIPN B9759MNRCPU B9759MNRCPUN B9759MNRSRB
B9759MNRSRBN B9759MNRZIIP B9759MNRZIIPN
-Datasets BETA0, BETA1, BETA55, BETA59 also have new
variables; they are listed in DOCVER38.
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
CHANGE 38.012 The MXG member DOCVER documents all variables in all MXG
DOCVLONG datasets, originally one line per variable, but the long
Jan 25, 2020 variable names and MXG's 72-character z/OS limit caused
two lines to be needed. The DOCVLONG program creates the
"DOCVLONG.TXT" file with one line per variable with new
LRECL=94 to contain all the information. This change
corrected an ERROR if the variable name ended in NUM and
was 13 characters long.
ON Z/OS:
// EXEC MXGSASV9
//INDOCVER DD DSN='MXG.SOURCLIB(DOCVER),DISP=SHR
//DOCVLONG DD DSN='MXG.DOCVLONG,TXT,DISP=(,CATLG),
// DD RECFM=FB LRECL=94 BLKSIZE=34500.
// DD SPACE=(CYL,(40,4))
//SYSIN DD *
%INCLUDE SOURCLIB(DOCVLONG);
ON ASCII:
FILENAME INDOCVER 'D:\MXG\SOURCLIB\DOCVER.SAS';
FILENAME DOCVLONG 'D:\MXG\USERID\DOCVLONG.TXT';
%INCLUDE SOURCLIB(DOCVLONG);
CHANGE 38.011 Support for APAR OA57718 that adds new zHyperlink write
VMAC42 statistics to TYPE42DS dataset.
Jan 23, 2020
Change 38.010 If you changed the default SMFAUDIT=YES option to NO,
ANALID to suppress the SMF Audit Report (BUILDPDB,ANALID),
Jan 24, 2020 inside ANALID, the VMXGOPTR utility could fail
MXGNOTE: END OF ANALID
NOTE: Line generated by the macro variable "OPTORG4".
Change 37.245's setting options with VMXGOPTR in ANALID
were mis-located inside SMFAUDIT=YES block in MXG 37.08,
now relocated in MXG 38.01.
Thanks to John Milne, IBM, AUSTRALIA
Change 38.009 If you specified GRAPHS=YES and your system is old and
ANALSIIS not have the option SYSODSGRAPHICS or you are on z/OS
READRATE where it is 0 until an ODS GRAPHICS command is issued,
Jan 24, 2020 the code defaulted to using PROC PLOT where XAXIS is not
supported. ANALSIIS and READRATE were both modified to
use the version executing to choose SGPLOT vs PLOT, and
XAXIS was removed from the PROC PLOT.
Thanks to Mike Martin, North Carolina NCSECU, USA.
CHANGE 38.008 Change 37.149 was in error if first USERADD= was IDMS.
UTILBLDP
Jan 22, 2020
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.007 The BY LIST for PROC MEANS DATA=_LVMAINT inside INTVBLD
VMACVMXA is changed to BY CECSER SYSTEM, removing BEGINMTR, which
Jan 21, 2020 caused tens of thousands of useless statistics.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.006 Support for IAM 9.3 Spin 3 INCOMPATIBLE due to relocation
VMACIAM and insertion of fields; many new variables in TYPEIAM.
Feb 5, 2020
Thanks to Mike Jacques, BBandT, USA.
Change 38.005 "Expressing Latent Demand as a Single Number" report code
ANALATNC starts by graphing a latency number for all systems by
Feb 5, 2020 interval on a single graph and drills down to individual
systems from there, displaying SMF70U00-15 variables in a
stacked bar graph with the latency number and MVS Busy
for each systems as lines on top of the bar. Latency is a
number based on bucket sizes of the SMF70U: (or SMF70Q:
for older OSes), designed to compress all the buckets to
a single number and allow multiple systems on a single
graph. While interesting, it takes interpretation to make
sense of it, especially since it is logarithmic. I think
IBM may have done this deliberately because the SMF70Q:
variables worked out to exactly 9 using the obvious max
bucket value. I fudged the max bucket value when I went
to SMF70U: variables to make it come out to 10. The main
purpose though is to allow the drill down from a common
start to the system details.
Jim's full paper, and report examples are found at:
https://www.mxg.com/downloads/Latent_Demand
Thanks to Jim S. Horne, Lowe's, USA.
Change 38.004 MXG 37.37 ERROR: INVALID VALUE FOR OPTION ENCODING is
CONFIMXG due to 1024 in CONFIGMXG should be OPEN_ED-1047.
Jan 15, 2020 The JOB fails with 999 ABEND and NO SASLOG is created.
Thanks to Jeff.Harder, Indiana Farm Bureau Insurance, USA.
Change 38.003A FORMAT $MG074OM for dataset TYPE74HO variable R744HOPM
FORMATS has new value '50'x='50x:CL5 10 GBIT/S CEE ROCE'
Jan 15, 2020
Thanks to Scott Barry, SBBTechLLC, USA.
Change 38.003 IDMSTAS dataset now contains UOW and NETNAME variables:
VMACIDMS TASCUOWI='CICS*UOW*ID'
Jan 24, 2020 TASCUOWS='CICS*UOW*SEQ'
TASCNETN='CICS*NETWORK*UOW*ID'
-Variables TASUFLD1-TASUFLD3 are now correctly input for
CICS records (IDM6623 corrected IDM6618).
Thanks to Scott Barry, SBBTechLLC, USA.
Thanks to Paola Rosero, Centre de services partages du Quebec, CANADA
Change 38.002 Variable BYTEPRC='PCT OF*BYTES*WRITTEN' is added to both
VMACTMS5 TMS.TMS and variable BESKEY='TAPE*ENCRYPTION*KEY*INDEX
Feb 7, 2020 is added to TMS.DSNBRECD.
Thanks to Umamaheswara Reddy, JPMCHASE, USA.
Change 38.001 BUILDIMS now works correctly with all selection options.
BUILDIMS See Change 37.221 for details
FORMATS -Variable LTERM in CIMSTRAN dataset from IMF records can
VMACCIMS contain '00'x, which are now translated to blanks.
VMACIMS -New variable INPUTCLNR in dataset CIMSTRAN and LASTCLNR
VMXGINIT in dataset CIMSPROG are created with the decimal class
Jan 20, 2020 number. INPUTCL2 and LASTCLA2 have the HEX values.
====== CHANGES THRU 37.275 WERE IN MXG 38.01 DATED Jan 20, 2020 ========
Change 37.275 SYNCSORT SMF WRKDVTYP and STWKSDEV device type variables
FORMATS values were changed some time in the way past 3350 era,
Jan 9, 2020 but MXG Format MGSYNDV was not updated until now.
Thanks to Randy Hewitt, DXC. USA.
Change 37.274 TYPE1415 Harmless NOTE: DUPLICATE BY VARIABLES, because
VMAC1415 OPENTIME was repeated in _BTY1415 was supposedly fixed
Jan 7, 2020 but wasn't until 38.01.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 37.273 Using TYPE26J2 incorrectly to read JES 3 records caused
VMAC26J2 INPUT STATEMENT EXCEEDED. Change 37.026 had added logic
Jan 7, 2020 to delete those JES3 records when using TYPE26J2/BUILDPDB
but tested for SUBS=3, when SUBS=5 is the JES3 SUBSYS.
LASTCHANGE: Version 38.
=========================MEMBER=CHANGE37================================
/* COPYRIGHT (C) 1984-2020 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG VERSION 37.37 is dated Jan 6, 2020, thru Change 37.272.
MXG VERSION 37.09 was dated Dec 20, 2019, thru Change 37.268.
EarlyA MXG VERSION 37.09 was dated Dec 20, 2019, thru Change 37.267.
MXG VERSION 37.08 was dated Nov 26, 2019, thru Change 37.256.
MXG VERSION 37.07 was dated Oct 22, 2019, thru Change 37.239.
Third MXG VERSION 37.07 was dated Oct 14, 2019, thru Change 37.236.
Second MXG VERSION 37.07 was dated Oct 12, 2019, thru Change 37.235.
First MXG VERSION 37.07 was dated Oct 9, 2019, thru Change 37.234.
MXG VERSION 37.06 was dated Aug 30, 2019, thru Change 37.190.
First MXG VERSION 37.06 was dated Aug 22, 2019, thru Change 37.184.
MXG VERSION 37.05 was dated Jul 8, 2019, thru Change 37.154.
Second MXG VERSION 37.05 was dated Jul 6, 2019, thru Change 37.153.
First MXG VERSION 37.05 was dated Jul 5, 2019, thru Change 37.152.
MXG VERSION 37.04 was dated Jun 5, 2019, thru Change 37.124.
MXG VERSION 37.03 was dated Apr 19, 2019, thru Change 37.091.
MXG VERSION 37.02 was dated Mar 11, 2019, thru Change 37.057.
Updated MXG VERSION 37.01 was dated Feb 3, 2019, thru Change 37.031.
First MXG VERSION 37.01 was dated Feb 1, 2019, thru Change 37.029.
Annual MXG Version 36.36 was dated Jan 4, 2019, thru Change 36.255.
The Last MXG Newsletter SIXTY-NINE was dated Jan 3, 2018.
New TECHNOTES for NEWSLTRS are now in CHANGESS.
Instructions for ftp download can be requested by using this form:
http://www.mxg.com/Software_Download_Request
Your download instructions will be sent via return email.
Contents of member CHANGES:
I. Current MXG Software Version 37.37 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 37.37.
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, although there are
no new NEWSLTRS updates; they are now found in CHANGESS as TECHNOTEs.
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 37.37 DATED Jan 6, 2020, THRU CHANGE 37.272.
==MAJOR CHANGES ADDED IN MXG 37.37, DATED Jan 6, 2020 THRU 37.272.
BUILDIMS 37.271 %BUILDIMS creates all possible IMS data plus report.
CONFIMXG 37.267 DO NOT USE ENCODING=EBCDIC1047, use OPEN_ED-1047.
Data values are corrupted with EBCDIC1047.
ADOCABND 37.270 A TECHNOTE documenting recovery from MXG ABENDS,
TYPE71 37.269 TYPE71 variables SMF72PIS/POS now deaccumulated.,
==MAJOR CHANGES ADDED IN MXG 37.09, DATED Dec 20, 2019 THRU 37.268.
SAS OPTION ISSUE FOR Z/OS ONLY, FOR NONLSCOMPATMODE ISSUES:
which is the z/OS default. EBCDIC1047 corrupts output SAS dataset.
ABENDS CORRECTED
TYPE42 37.261 SMF 42 Subtype 1 TYPE42DS INPUT STATEMENT EXCEEDED.
ASUMMSUS 37.265 ERROR PARM OPTNE NOT DEFINED, typo.
NEW SUPPORT
TYPE99 37.264 SMF 99 Subtype 2 TYPE99_2 new variables added.
TYPEIMS 37.259 IMS SYNCPOINT Log Records IMS5937/5938 keeps all vars
TYPEIDMS 37.260 IDMS dataset IDMSTAS USER Fields were misaligned.
==MAJOR CHANGES ADDED IN MXG 37.08, DATED Nov 26, 2019 THRU 37.256.
TYPE42 37.250 SMF 42 ABEND due to SRLEN=208, now all protected.
VMACSMF 37.249 Using FTP ACCESS from z/OS fails with JFCB issue.
ERRORs CORRECTED
TYPERMFV 37.246 Variables PCIFTET/PCIFTQT in ZRBPCI incorrect.
VMXGSUM 37.245 KEEPALL=NO with INCODE= could cause UNINIT message.
TYPE82 37.241 Several MG082xx formats had wrong hex value.
TYPE102 37.240 Variable QWP4STPGS=STASTPGSAMP/N/Y/S is now INPUT.
NEW SUPPORT
TYPE79 37.242 Support for BMC SMF 70 Subtype 255 creates TYPE70FF.
TYPE70PR 37.243 Vars SMF70LACM/LACA/LACB are now kept in TYPE70PR.
ASMRMFV 37.255 RMF III FDF support for PCIE and SCMG3 tables.
ENHANCEMENT
TECHNOTE 37.247 Example RACF analysis, why USERID was revoked.
TYPE119 37.244 Subtype 3 SMF 119 not written, USERID no SMF access.
DIFFROSC 37.256 New ROSCOE dataset ROSCOMON with all MONITORS.
==MAJOR CHANGES ADDED IN MXG 37.07, DATED Oct 22, 2019 THRU 37.239.
ERROR CORRECTED
TYPE113 37.239 Support for new SMF 113 CRYPTO17-20 for z/15,
caused ABEND: ARRAY SUBSCRIPT OUT OF RANGE,
only if HIS CRYPTO counters are enabled, and.
only on z/15.
==MAJOR CHANGES ADDED IN MXG 37.07, DATED Oct 14, 2019 THRU 37.236.
ERROR CORRECTED
TYPE113 37.236 Support for new SMF 113 EXTND255-287 for z/15.
Caused ABEND: ARRAY SUBSCRIPT OUT OF RANGE,
only on z/15.
==MAJOR CHANGES ADDED IN MXG 37.07, DATED Oct 12, 2019 THRU 37.235.
ERROR:
BLDSMPDB 37.235 CRITICAL ERROR if BLDSMPDB and VMXGALOC are used,
(only on ASCII) due to an extra comma in line 949.
"ERROR:All positional parameters must precede ..."
LIBNAME PDB NOT FOUND.
Remove that comma on line 949 in BLDSMPDB.
==MAJOR CHANGES ADDED IN MXG 37.07, DATED Oct 9, 2019 THRU 37.234.
ERROR
ASUMMIPS 37.228 Warning message DURATM=INTERVAL conflict.
ANALMSUS 37.217 EXCELDEST not protected for length 0 Warning.
CICINTRV 37.210 Warning if CICINTRV INTERVAL requested can't be used.
IMACICDB 37.200 Optional CICS DBCTL var STATCTM1 too large.
ASUMDB2A 37.199 Correct count of THREADS in DB2 ASUMDB2A/B/G/P/R.
TYPEBETA 37.198 BETA 93 Subtypes 12/17/30/31/55 are now output.
TYPEBE97 37.197 BETA 97 Subtype 51 did not input "New Area" fields.
BUILD005 37.195 PDB.PRINT only populated ACCOUNTn in first obs.
VMXGDSN 37.191 RMM/EDGR in VMXDSN had zero obs for TAPES/TAPEDSNS.
VMACEDGR 37.225 RMM/EDGR dataset EDGRXEXT RDPHYSIZE too small.
NEW SUPPORT
TYPESAPZ 37.222 Support for SAP Z Connector USER SMF record.
TYPE123A 37.221 Support for z/OS Connect EE SMF 123 Version 2.
TYPECADK 37.219 Support for CA-DISK/Sterling DMS DSINDEX file.
TYPEFOCU 37.215 Support for FOCUS Version 7.7 USER SMF Record.
TYPE80A 37.213 Support for RACF TYPE80TK TOKDANAM=AUTOLOGIN.
TYPE113 37.212 Support for z15 Processor SMF 113 RNI equation.
ASMRMFV 37.204 Support for RMF III CRYG3 and XCFG3 and more FDF.
TYPETLMS 37.192 Support for TLMS creates two new datasets.
TYPE0203 37.216 Support SMF Type 2 ST 1/2 GSIG/ISIG variable length.
ENHANCEMENT
TYPE42 37.194 TYPE42DS variables S42DSENT/DSCMT identify zEDC.
ANAL82AU 37.214 ANAL82AU combines SERV and USER obs for TYPE82AU.
VMXGALOC 37.224 Note if you added VMXGALOC to your IMACINIT.
==MAJOR CHANGES ADDED IN MXG 37.06, DATED AUG 30, 2019 THRU 37.190.
TYPEAAM 37.186 Support for IBM Tivoli Advanced Allocation SMF
DODSCRDT 37.189 Spurious INVALID VALUE FOR INPUT FUNCTION message
==MAJOR CHANGES ADDED IN MXG 37.06, DATED AUG 22, 2019 THRU 37.184.
ERROR
ASMRMFV 37.178 Possible S0C4 (37.05) or S0C7 (using FDF)
TYPE82 37.165 TYPE8201 variables SMF82ITE/CKD/LML/USR/PKD wrong.
TYPEBETA 37.160 BETA 93 610 (back level) subtype 40/49 wrong.
TYPE72GO 37.179 Variables METGOAL and PCTMETGOL were wrong.
NEW SUPPORT
TYPERMFV 37.167 z/OS 2.4 Updates for RMF MONITOR III datasets
TYPE74 37.166 z/OS 2.4 Updates for TYPE7402 dataset.
TYPE82 37.183 Support for SMF 82 new Audit TYPE82AU & subtypes.
TYPEMAR 37.181 Support for Hitachi MAR Mainframe Analytics 9.1
TYPEIMS 37.176 Support for IMS LOG TYPE '02'x.
ENHANCEMENT
TYPE1131 37.175 New SIISPCT=STORE INTO*INSTRUCTION*STREAM*PERCENT.
TYPE1415 37.172 Variable SMF14DEF='Y' if dataset is encrypted.
TYPE110 37.168 CICS "identity" variables not kept with UTILEXCL.
DODSCRDT 37.161 New z/OS-ONLY CREATDATE variable can be created.
ANALMSUS 37.157 MSU Consumption from TYPE89 and TYPE30 charts etc.
==MAJOR CHANGES ADDED IN MXG 37.05, DATED Jul 8, 2019 THRU 37.154.
ERROR
TYPE110 37.154 SMF 110 Subtype 1 MNSEGCL=5 INPUT EXCEEDED error.
==MAJOR CHANGES ADDED IN MXG 37.05, DATED Jul 6, 2019 THRU 37.153.
ERROR
TYPE120 37.153 SMF 120 Subtype 3 INPUT STATEMENT EXCEEDED error.
==MAJOR CHANGES ADDED IN MXG 37.05, DATED Jul 5, 2019 THRU 37.153.
FLASH: 37.144: MISSING PERIOD 2/3 OBS IN TYPE72GO MXG 36.07 or prior
after IBM RMF Maintenance for SCM and CRYPTO are applied.
There is NO ERROR with MXG 36.08 (Oct 2018) or later. See Text.
NEW SUPPORT
ANALMSUS 37.157 Powerful set of reports of SOFTWARE MSUs consumption.
READRATE 37.142 New analysis of Read Rate MB/Sec reading SMF data.
TYPEVM 37.130 New VM Account datasets supported.
TYPE42 37.135 Eight more invalid LENSR= TYPE42 subtype 5.
TYPE119 37.127 New variables in datasets TYP11902/TYP11994/TYP11995.
TYPE123A 37.125 Variable/format changes z/OS Connect EE 3.0 SMF 123.
ENHANCEMENT
MXGSTEP 37.152 MXGSTEP tailoring identifies MXG executions.
==MAJOR CHANGES ADDED IN MXG 37.04, DATED Jun 5, 2019 THRU 37.124.
ERRORS CORRECTED
TYPE1415 37.116 WPS 4.1 ONLY, U4087 ABEND,OPTIONS NOWPSSCATTERCOMP.
TYPENDM 37.113 NDM-CDI 24 byte short record INPUT EXCEEDED.
TYPETPX 37.107 Misaligned TPXETIME reported as 8a Oct 27, 1935.
TYPE102 37.100 DB2 zPARM T106S102 variables misaligned.
NEW SUPPORT
TYPEBETA 37.114 Support for updated BETA 93 V6R2 (INCOMPATIBLE).
TYPE7072 37.109 Support for z/OS 2.4 SMF Manual 04Mar19 changes.
TYPE120 37.105 Support for SMF 120 WAS and LIBERTY (COMPATIBLE).
TYPEIMS 37.103 Support for IMS Log Records 5607/5610/5904/5950.
TYPE110 37.102 Support for CICS/TS 5.5 new Statistics (COMPAT).
TYPE110 37.102 All _SCICxxx Statistic SORTS deaccumulate.
TYPE29 37.093 Support for IMS ODBM Accounting SMF 29 Subtype 1.
TYPETMPX 37.121 Support for ThruPut Manager Release 18.02 v7r1.0.
ENHANCEMENTS
TYPEWSF 37.111 Final revisions for WSF/EOS WSFAUDIT AUDACT/OBJN.
BLDSMPDB 37.106 Updated features and documentation.
TYPE7072 37.104 Variables CECSER/CPCMODEL added to TYPE72GO.
TYPECIMS 37.095 New variables in TYPEDBDS (IMF from BMC).
TECHNOTES
TECHNOTE 37.110 Difference between TYPExxxx and TYPSxxxx.
TECHNOTE 37.097 APAR OA65762 NEGATIVE SMF30_TIME z/OS 2.2 only.
==MAJOR CHANGES ADDED IN MXG 37.03, DATED Apr 19, 2019 THRU 37.091.
ERRORS CORRECTED
TYPE92 37.085 SMF 92 Subtype 52 INPUT EXCEEDED, TRSN doc 52 bytes.
TYPEVMXA 37.084 z/VM VXPRCAPM dataset vars CMB10C0-X4 wrong values.
TYPEBE97 37.080A Datasets BETA9706/BETA9706D were not output to PDB.
TYPE74 37.078 TYPE748S var R748SIID fmt $HEX4, no dupes now.
TYPE125 37.075 INPUT STATEMENT EXCEEDED, period missing.
TYPEDB2 37.074 QBSTBPIN always incorrectly calculated before DIF.
VMAC82 37.060 INPUT EXCEEDED SMF 82 ST 31, incorrect length.
NEW SUPPORT
TYPERMFV 37.067 Support for RMF III PCI/SCM/ZFX segments 4 datasets.
TYPEHSM 37.076 Support for HSM FSR Record, Unix filename added.
TYPE99 37.082 SMF 99 ST 12 Capacity Incr/Decr individual decodes.
ANALRMF3 37.068 CF Activity Report, Structure Level, in ANALRMF3.
TYPEDCOL 37.069 zEDC Compression type values revised DCOLDSET/DCOLDC.
TYPE102 37.059 Final corrections for IFCIC 319 support.
ENHANCEMENTS
TYPEXAM 37.081 Analyzing VPS USER dataset, must use INTORSUM='SU'.
TYPEWSF 37.083 Logic revised to use OBJT/ACT for Input choice.
TYPERMFV 37.080 SVPCNM and RPRTCLAS added to all RCD datasets.
TYPEBBMQ 37.073 UNEXPECTED RTIN messages, BBMQ Version 5.4 no change.
ANALID 37.063 Report now shows 26.002 or 26.003 for JES2/JES3.
GRAFWLM 37.061 Bar charts of ZIP and ZIP Eligible added.
TYPE30 37.058 Cosmetic: Uninitialized variable CBPERROR no impact.
TECHNOTE 37.072 ODS Stat graphics procs use JAVA, memory intensive.
==MAJOR CHANGES ADDED IN MXG 37.02, DATED Mar 11, 2019 THRU 37.057.
ERRORS CORRECTED
TYPENDM 37.047 NDM-CDI dataset NDMCT var NDMCPU 256 times too large.
READDB2 37.042 MXG 37.01. Blank WANTONLY Cosmetic %SYSFUNC message
TYPE74 37.040 TYPE749 variable R7491DEFCOMPRATIO wrong value.
TYPE42 37.034 Two more ABENDS invalid SMF 42 LENSR 520/592 protect.
TYPE74 37.032 TYPE749 z/EDC Divide by ZERO protection failed.
TYPE7072 37.044 BMC CMF VERSNRMF values 792 and 794 for z/OS 2.3.
NEW SUPPORT
TYPEDCOL 37.041 Support for APAR OA54897, DCDEXFLG not used FOR zEDC.
MANY 37.037 Support for SMF Manual Changes in Jan 14, 2019 Doc.
TYPEAXW 37.033 Support for Axway V3.3.2 2018/06/27 restructure.
UTILMISS 37.053 Utility to remove all variables that are all missing.
TYPEDB2 37.035 DB2 V12 overlooked Package variables in DB2ACCTP.
TYPE102 37.051 IFCID 319 new variables created and kept.
ENHANCEMENT
JCLPDBJB 37.048 Example "BUIDPDB" creates only JOB-related datasets.
TYPERMFV 37.055 CFACT Coupling Facility Structure Activity Report.
ANALMQ 37.039 MQ Reports replicating IBM's MQSMF program.
ANALHSM1 37.038 Combined TYPE6156+HSMFSRST report, thrashing pri-mig?
TYPE70PR 37.046 SMF70BPS/SMF70ACS expanded for each engine type.
TECHNOTE 37.043 Executing MXG on ASCII, WORK needs to be local.
==MAJOR CHANGES ADDED IN MXG 37.01, DATED Feb 3, 2019 THRU 37.030.
ASMRMFV 37.030 ASMRMFV 36.12-37.01 NOZEROCPU filter didn't.
Caused out of space condition. Typically, NOZEROCPU
filters out 3/4 of the ZRBASI records.
==MAJOR CHANGES ADDED IN MXG 37.01, DATED Feb 1, 2019 THRU 37.030.
ABEND Avoidance
TYPEDB2 37:014 ABEND: DB2 SMF 100 ST 1 NETEAZZA/IDAA DB2STATS.
TYPEVMXA 37.012 ABEND: ZVM MONWRITE NEW 40061802 Service Level.
TYPEVMXA 37.028 ABEND: ZVM MONWRITE new z/VM 7.1 (INCOMPAT).
ERRORS CORRECTED
TYPE92 37.002 TYPE9208 INPUT STATEMENT EXCEEDED, manual wrong.
TYPERMFV 37.001 Some RMF III ZRBASI fields blank/wrong in 36.36.
TYPE119 37.003 TYP11952 SMF119ML_IP_IPV4 wrongly compressed TIRIP.
VMXGPRAL 37.006 Unbalanced parens in variable label, non fatal.
TYPE92 37.017 Many non-fatal corrections were made to type 92.
TYPEEDGR 37.015 RMM variable EDGRTIME had missing values.
ANALCNCR 37.013 New Concurrency example counts steps and tapes.
NEW SUPPORT
TYPEBETA 37.007 Support for Beta93 V6.2 Subtypes 1-3.
TYPE102 37.005 Support for DB2 102 Trace IFCID 404.
TYPESTC 37.018 Support for STC HSC Subtype 32 and 33 new datasets.
TYPE26J2 37.026 Local SubSystem TYPE26J2 not output, SMF6SBS NE 2.
VMXGALOC 37.021 New parms YR2KEEP and BASEYEAR for Yearly PDB.
ENHANCEMENT
EMAIL 37.027 Example added to email SAS CondCode from ASCII SAS.
ANALID 37.016 New report showing total/min/max for each SYSTEM.
VMXGUOW 37.011 Enhanced for easy CICSTRAN-only PDB.ASUMUOW.
ANAL89 37.029 Reference line SMF70LAC (4HRAV) added to MSU plots.
TECHNOTES
TECHNOTE 37.004 Reading z/OS DATA with SAS FTP Access needs RCMD
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 TS1M6 (9.4M6), "M6",
or "SAS 9.4 (9.04.01M6P110718)" 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
described in SAS Note 61672. But SAS apparently does not plan for
a defect correction since the MXG Circumvention solves for MXG and
the text of 61672 simply describes the circumvention needed because
MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect.
See Change 35.309 for more details on using NOERRORSTOP for your
own PROC SQLs.
SAS V9.4 M6 is RECOMMENDED, but MXG executes without error
using SAS Version 9.4 M0-M2 or M4-M6 or SAS Version 9.3 M0-M2.
SAS V9.4 M5 is REQUIRED with z/OS 2.3 with Eight-Byte USERIDs
for Interactive TSO (DMS) SAS Sessions. SAS Note 61339.
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
But CONFIMXG is required for sites with NLS issues, and you must
use JCLCONFI to create/update the MXG.FORMATS catalog if you use
CONFIG='MXG.SOURCLIB(CONFIMXG)'.
For no NLS, you can use the MXGSAS94 JCL Procedure example.
***************************************************************
MXG 26.03 thru MXG 36.11 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows TEN and
Linux on 64-bit hardware, but MXG users execute MXG on MANY
(ALL??) SAS platforms, including AIX, Linux, and other 'nix'
variants, on many different hardware platforms, and since they all
work we don't need to list them. If SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 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 z15 did INCOMPATIBLY change the SMF 113 records by adding 32
new EXTEND and 4 CRYPTO counters, and those fields were supported
in MXG 37.07 dated Oct 22, 2019. The z/14 also INCOMPATIBLY changed
the SMF 113 record, and that was supported way back in MXG 36.07.
The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
The z/EC12 with 85+ engines required MXG 30.07.
Support for 255 engines was added in MXG 31.04.
MXG 37.07 supports the new z/OS 2.4 SMF manual fields, COMPATIBLY.
The z13 processor INCOMPATIBLY CHANGED, the new SMT-MODE RMF 70, and
MXG 34.03 was REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF
(which are written if you have zIIP engines AND have enabled the new
PROCVIEW CORE option for Multi-Threading, even if only one thread is
enabled).
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*
z/OS 2.4 Compatible from SMF Manual Sep 2019 37.166 37.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
z13 SMT MT=2 CPUZIPTM TYPE70 Mar 21, 2016 35.03
z14 SMF 113 INCOMPAT, ABEND Oct 2, 2017 35.11
z14 113 LPARBUSY missing value Aug 8, 2018 36.07
z14 ZR1 New SMF70MAXPU variable May 8, 2018 36.04
z15 New SMF fields (COMPAT) Oct 22, 2018 37.07
CICS/CTG V9 Transaction Gateway ?? ?? 2013 31.31
CICS/ESA 3.2 Jun 28, 1991 9.9
CICS/ESA 3.3 Mar 28, 1992 10.01
CICS/ESA 4.1 Oct 27, 1994 13.09
CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07
CICS-Transaction Server V1R1 Sep 10, 1996 14.07
CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06
CICS-TS V1R2 CICS/TS 1.2 Oct 27, 1997 15.06
CICS-TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04
CICS-TS V2R1 CICS/TS 2.1 Mar 15, 2001 18.11
CICS-TS V2R2 CICS/TS 2.2 Feb 9, 2002 19.19
CICSTRAN subtype 1 support only *19.19
CICSTRAN subtype 2 completed *19.08
CICS-TS V2R3 CICS?TS 2.3 Dec 19, 2003
Using UTILEXCL to create IMACEXCL: 21.04
Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04
CICS-TS V2R3 CICS/TS 2.3 Aug 13, 2004 22.04
CICS-TS V3R1 CICS/TS 3.1 Jan 18, 2005 22.22
CICS-TS for Z/OS Version 3.1 Mar 15, 2005
Using UTILEXCL to create IMACEXCL: 22.13
Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22
CICS-TS V3R2 CICS/TS 3.2 Dec 6, 2007 25.11
CICS-TS for Z/OS Version 3.2 Jun 29, 2007 25.03
CICS-TS/3.2 Compressed Records Nov 3, 2007 25.11
CICS-TS/4.1 (CICSTRAN INCOMPAT) Mar 13, 2009 27.01
CICS-TS/4.1 (STATISTICS ST=2) Sep 18, 2009 27.08
CICS-TS/4.2 CICSTRAN/STATISTICS Jun 24, 2011 29.03
CICS-TS/4.2 CICSRDS MNSEGCL=5 Jun 24, 2011 *29.05
CICS-TS/4.2 INVALID STID=116 Jan 31, 2012 *30.01
CICS-TS/5.1 (INCOMPATIBLE) Dec 14, 2012 *30.08
CICS-TS/5.1 for valid TASZIP/ELG Jan 21, 2013 *30.30
CICS-TS/5.1 MNSEGCL=5 INCOMPAT Jun 17, 2013 *31.03
CICS-TS/5.2 COMPATIBLE CICSTRAN Jun 13, 2014 *31.03
CICS-TS/5.2 INCOMPAT Statistics Jun 13, 2014 *32.03
CICS-TS/5.3 INCOMPAT CICSTRAN Apr 29, 2015 33.04
CICS-TS/5.3 RESOURCE SEGCL=5 Sep 31, 2015 33.09
CICS-TS/5.3 CICSTRAN INCOMPATIBL Oct 29, 2015 33.11
CICS-TS/5.3 GA date Dec 11, 2015 33.33
CICS-TS/5.3 MNSEGCL=5 INPUT ERR Mar 21, 2016 34.02
CICS-TS/5.4 OPEN BETA Aug Aug 11, 2016 34.06
CICS-TS/5.4 OPEN BETA Nov Nov 11, 2016 34.09
CICS-TS/5.4 GA Jun 17, 2017 35.03
CICS-TS/5.5 GA (COMPAT) Jan 29, 2018 37.01
DB2 2.3.0 Oct 28, 1991 10.01
DB2 3.1.0 Dec 17, 1993 13.02
DB2 4.1.0 Tolerate Nov 7, 1995 13.07
DB2 4.1.0 Full support Sep 11, 1996 14.07
DB2 5.1.0 Tolerate Jun 27, 1997 14.14
DB2 5.1.0 Full support Jun 27, 1997 15.02
DB2 6.1.0 initial support Mar 15, 1999 16.09
DB2 6.1.0 all buffer pools Mar 15, 1999 18.01
DB2 6.1.0 parallel DB2 Mar 15, 1999 19.19
DB2 7.1.0 parallel DB2 Mar 31, 2001 19.19
DB2 7.1.0 corrections Mar 31, 2001 20.06
DB2 8.1 Tolerate, no packages Mar 31, 2004 20.20
DB2 8.1 New Data Packages wrong Mar 31, 2004 21.08
DB2 8.1 Support with Packages Mar 31, 2004 *23.09
DB2 8.1 with all zIIP Variables Sep 30, 2006 24.08
DB2 8.1 +PK47659 Sep 12, 2008 26.08
DB2 9.1 See Change 25.265. Dec 7, 2007 25.11
DB2 9.1 Full Support +PK/56356 Sep 12, 2008 26.08
DB2 10.1 Tolerate Oct 1, 2010 28.06
DB2 10.1 New vars + Compressed Nov 1, 2010 *28.07
DB2 10.1 Invalid Header pre APAR Jan 12, 2011 *28.28
DB2 10.1 IFCID=225 INCOMPAT Sep 23, 2011 *29.07
DB2 10.1 QWHCCV for QWHCATYP=8 Oct 3, 2011 *30.07
DB2 10.1 DBID/OBID decode Jan 21, 2013 *30.30
DB2 10.1 QLSTxxxx vars corrected Jun 21, 2013 *31.04
(ONLY IMPACTS DB2STATS)
DB2 11.1 TOLERATE DB2 V11.1 Jun 21, 2013 30.30
DB2 11.1 DB2STATS QLST CORRECT Jun 21, 2013 31.04
DB2 11.1 SUPPORT NEW VARIABLES Jun 21, 2013 31.08
DB2 11.1 IRLM NEW SEGMENT Jun 21, 2013 32.10
DB2 12.1 COMPATIBLE Oct 5, 2016 34.08
DB2 12.1 NETEZZA CORRECTIONS Oct 5, 2016 34.08
DB2 12.1 QLAC INSERTS DB2ACCT May 15, 2017 35.05*
DFSMS/MVS 1.1 Mar 13, 1993 11.11
DFSMS/MVS 1.2 Jun 24, 1994 12.02
DFSMS/MVS 1.3 Dec 29, 1995 13.09
DFSMS/MVS 1.4 Sep 28, 1997 15.04
DFSMS/MVS 1.4 HSM Sep 23, 1998 16.04
DFSMS/MVS 1.5 ??? ??, 1999 16.04
DFSORT SMF V1R5 Mar 1, 2006 24.02
MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996 14.02
MQ Series 1.2.0 May 26, 1998 16.02
MQ Series 2.1.0 Oct 2, 1999 17.07
MQ Series 5.2 Dec 16, 2000 18.10
MQ Series 5.3 Dec 16, 2002 21.05
MQ Series 6.0 Feb 14, 2006 23.23
Websphere MQ Series 7.0 ??? ??, 2009 *28.06
Websphere MQ Series 7.1 MAR 12, 2011 29.03
Websphere MQ Series 8.0 Jun 24, 2011 29.05
Websphere MQ Series 9.1 Mar 20, 2017 35.03
NETVIEW 3.1 type 37 ??? ??, 1996 14.03
NPM 2.0 Dec 17, 1993 12.03
NPM 2.2 Aug 29, 1994 12.05
NPM 2.3 ??? ??, 1996 15.08
NPM 2.4 Nov 18, 1998 17.01
NPM 2.5 Feb ??, 2000 18.02
NPM 2.6 Nov ??, 2001 19.06
RMDS 2.1, 2.2 Dec 12, 1995 12.12
RMDS 2.3 Jan 31, 2002 19.11
TCP/IP 3.1 Jun 12, 1995 12.12
TCP/IP 3.4 Sep 22, 1998 16.04
WebSphere 5.0 APAR PQ7463 Aug 19, 2003 21.04
WebSphere 6.0 Feb 18, 2006 23.23
WebSphere 7.0 Oct 7, 2010 28.06
WebSphere 8.0 Jul 17, 2011 29.05
DOS/VSE POWER V6.3.0 Dec 19, 1998 16.08
VM/ESA 2.0 Dec 23, 1992 10.04
VM/ESA 2.1 Jun 27, 1993 12.02
VM/ESA 2.2 Nov 22, 1994 12.06
VM/ESA 2.3 Jun 1, 1998 16.08
VM/ESA 2.4 Mar 1, 2001 19.03
z/VM 3.1 Mar 1, 2001 19.03
z/VM 3.1 DATABYTE=0 May 2, 2002 20.02
z/VM 4.2 ?? May 2, 2002 20.02
z/VM 4.4 Jan 22, 2005 22.22
z/VM 5.1 Jan 22, 2005 22.22
z/VM 5.2 Jan 22, 2006 24.01
z/VM 5.3 TOLERATE Jun 7, 2007 25.05
z/VM 5.3 NEW VARIABLES Sep 12, 2008 26.08
z/VM 5.4 (COMPATIBLE) Sep 12, 2008 *27.01
z/VM 6.1 (NO CHANGES) Jul 7, 2008 27.01
z/VM 6.2 Dec 2, 2011 29.04
z/VM 6.3 INCOMPATIBLE Jul 23, 2013 31.05
z/VM 6.3 z/13 Jan 23, 2016 33.33
z/VM 6.4 SYTLCK Incompat Apr 26, 2016 34.04
z/VM 6.40061802 ABEND Jan 17, 2019 37.02
z/VM 7.1 ABEND Feb 14, 2019 37.02
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.07
IMS log 15.1 NO CHANGES Mar 1, 2018 35.07
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
The Monitor for DB2 Version 4.0 22.10
The Monitor for DB2 Version 5.0 30.02
The Monitor for CICS/ESA 1.2 - 12.12
The Monitor for CICS/ESA 1.3 - 15.01
The Monitor for CICS/ESA 2.0 - 15.06
The Monitor for CICS TCE 2.1 - 20.04
The Monitor for CICS TCE 2.2 - 20.335, 21.134 21.04
The Monitor for CICS TCE 2.3 including CICS/TS 3.1 22.08
The Monitor for CICS TCE 3.2 (almost all) 25.11
The Monitor for CICS TCE 3.2 (almost all) 27.01
The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2) 29.07
TMON/CICS 3.4 (for CICS/TS 5.1) 30.30-32.12
(Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)
TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099) 33.04
TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195) *33.09
TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257 34.08
The Monitor for MVS/ESA 1.3 - 12.05
The Monitor for MVS/ESA 1.5 - 12.05
The Monitor for MVS/ESA 2.0 - 15.09
The Monitor for MVS/ESA 3.0 - 19.19
TMON/MVS Version 4.4 32.04
Candle
Omegamon for CICS V200 User SMF 12.05
Omegamon for CICS V300 User SMF 13.06
Omegamon for CICS V400 User SMF 16.02
Omegamon for CICS V400 type 110 segments 16.02
Omegamon for CICS V500 User SMF 18.01
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for IMS V300 (ITRF) 14.04
Omegamon for IMS V550/V560 (ITRF) 25.05
Omegamon for MVS V300 13.05
Omegamon for MVS V400 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for VTAM V400 15.15
Omegamon for VTAM V500 18.08
Omegamon for SMS V100/V110 12.03
CA
ACF2 6.2 was 16.04 but ABEND, ACSMFREL=0 May 2018 36.05
ASTEX 2.1 14.04
IDMS 18 32.05
IDMS 19 (INCOMPAT after PTF R084146 Change 34.164) 33.05
NETSPY 4.7 14.03
NETSPY 5.0 14.03
NETSPY 5.2 16.05
NETSPY 5.3 18.03
NETSPY 6.0 20.10 20.305
NETSPY 7.0 20.10 20.305
SAR/VIEW R11 23.07 23.196
BMC, was Boole & Babbage
APPTUNE V11R2 SMF 102 33.11 33.264
IMF 3.1 (for IMS 5.1) 12.12
IMF 3.2 (for IMS 6.1 only) 15.09
IMF 3.2 (for IMS 5.1 and 6.1+) 16.04
IMF 3.3 (for IMS 7.1 and 8.1) *22.08
IMF 4.1 (for IMS 9.1) *26.02
IMF 4.4 (for IMS 9.1) *31.08
IMF 4.5 (for IMS 11.1) (No change since 4.4) 31.08
IMF 4.6 a/k/a Mainview IMS *31.08
IMF 5.1 a/k/a Mainview IMS *34.01
IMF 5.2 a/k/a Mainview IMS 34.01
IMF 5.3 a/k/a Mainview IMS 35.03
Mainview for MQ Version 4.4 29.03
Mainview for MQ Version 5.1 30.02
Mainview for MQ Version 5.2, 5.3, 5.4 33.01
Mainview for CICS Version 6.5 (CICS/TS 5.1) 30.30
Mainview for CICS Version 6.4 (CICS/TS 4.2) 30.04
Mainview for CICS Version 6.1 26.26
Mainview Auto Operator data file 28.28
Mainview for DB2 THRDHIST file 20.20
Mainview for TCP/IP 20.20
Mainview for IP 34.??
Mainview for Batch Optimizer 19.19
Memorex/Telex
LMS 3.1 12.12A
Oracle V9, V10 24.06
SYNCSORT
2.1 33.05
1.4 33.08
Amdahl
APAF 4.1, 4.3 16.08
Velocity Software
XAMAP 3.4 22.10
XAMAP 3406 24.03
XAMAP 3.7 27.10
XAMAP 4.1 Now Renamed to ZVPS 4.1 29.07
XVPS 4.2 31.06
ZVPS 5.4 *33.07
V. Incompatibilities and Installation of MXG 37.37.
1. Incompatibilities introduced in MXG 37.37:
a- Changes in MXG architecture made between 37.37 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 37.08 after MXG 36.36:
Dataset/
Member Change Description
ANAL82AU 37.214 ANAL82AU combines SERV and USER obs for TYPE82AU.
ANALCNCR 37.013 New Concurrency example counts steps and tapes.
ANALHSM1 37.038 Combined TYPE6156+HSMFSRST report, thrashing pri-mig?
ANALID 37.016 New report showing total/min/max for each SYSTEM.
ANALID 37.063 Report now shows 26.002 or 26.003 for JES2/JES3.
ANALMQ 37.039 MQ Reports replicating IBM's MQSMF program.
ANALMSUS 37.136 Powerful set of reports of SOFTWARE MSUs consumption.
ANALMSUS 37.157 MSU Consumption from TYPE89 and TYPE30 charts etc.
ANALMSUS 37.217 EXCELDEST not protected for length 0 Warning.
ANALRMF3 37.068 CF Activity Report, Structure Level, in ANALRMF3.
ASMRMFV 37.030 ASMRMFV 36.12-37.01 NOZEROCPU filter didn't.
ASMRMFV 37.178 Possible S0C4 (37.05) or S0C7 (using FDF)
ASMRMFV 37.204 Support for RMF III CRYG3 and XCFG3 and more FDF.
ASMRMFV 37.254 MXG 37.05-37.07 CPC parameter PARMS KEYWORD NULL
ASMRMFV 37.255 RMF III FDF support for PCIE and SCMG3 tables.
ASUMDB2A 37.199 Correct count of THREADS in DB2 ASUMDB2A/B/G/P/R.
ASUMMIPS 37.228 Warning message DURATM=INTERVAL conflict.
BLDSMPDB 37.106 Updated features and documentation.
BUILD005 37.195 PDB.PRINT only populated ACCOUNTn in first obs.
CICINTRV 37.210 Warning if CICINTRV INTERVAL requested can't be used.
DIFFROSC 37.256 New ROSCOE dataset ROSCOMON with all MONITORS.
DODSCRDT 37.161 New z/OS-ONLY CREATDATE variable can be created.
DODSCRDT 37.189 Spurious INVALID VALUE FOR INPUT FUNCTION
EMAIL 37.027 Example added to email SAS CondCode from ASCII SAS.
GRAFWLM 37.061 Bar charts of ZIP and ZIP eligible added.
IMACICDB 37.200 Optional CICS DBCTL var STATCTM1 too large.
JCLPDBJB 37.048 Example "BUIDPDB" creates only JOB-related datasets.
MANY 37.037 Support for SMF Manual Changes in Jan 14, 2019 Doc.
READDB2 37.042 MXG 37.01. Blank WANTONLY Cosmetic %SYSFUNC message
READDB2 37.185 APPARENT SYMBOLIC REFERENCE LDB LDB@ACT, no impact.
TECHNOTE 37.004 Reading z/OS DATA with SAS FTP Access needs RCMD
TECHNOTE 37.043 Executing MXG on ASCII, WORK needs to be local.
TECHNOTE 37.072 ODS Stat graphics procs use JAVE, memory intensive.
TECHNOTE 37.097 APAR OA65762 NEGATIVE SMF30_TIME z/OS 2.2 only.
TECHNOTE 37.110 Difference between TYPExxxx and TYPSxxxx.
TECHNOTE 37.247 Example RACF analysis, why USERID was revoked.
TYPE0203 37.216 SMF Type 2 Subtypes 1/2 GSIG/ISIG variable length.
TYPE102 37.005 Support for DB2 102 Trace IFCID 404.
TYPE102 37.051 IFCID 319 new variables created and kept.
TYPE102 37.059 Final corrections for IFCIC 319 support.
TYPE102 37.100 DB2 zPARM T106S102 variables misaligned.
TYPE102 37.240 Variable QWP4STPGS='STASTPGSAMP/N/Y/S is now INPUT.
TYPE110 37.102 All _SCICxxx Statistic SORTS deaccumulate.
TYPE110 37.102 Support for CICS/TS 5.5 new Statistics (COMPAT).
TYPE110 37.168 CICS "identity" variables not kept with UTILEXCL.
TYPE113 37.212 Support for z15 Processor SMF 113 RNI equation.
TYPE1131 37.175 New SIISPCT=STORE INTO*INSTRUCTION*STREAM*PERCENT.
TYPE119 37.003 TYP11952 SMF119ML_IP_IPV4 wrongly compressed TIRIP.
TYPE119 37.127 New variables in datasets TYP11902/TYP11994/TYP11995.
TYPE119 37.244 Subtype 3 SMF 119 not written, USERID no SMF access.
TYPE120 37.105 Support for SMF 120 WAS and LIBERTY (COMPATIBLE).
TYPE123A 37.125 Variable/format changes z/OS Connect EE 3.0 SMF 123.
TYPE123A 37.221 Support for z/OS Connect EE SMF 123 Version 2.
TYPE125 37.075 INPUT STATEMENT EXCEEDED, period missing.
TYPE1415 37.116 WPS 4.1 ONLY, U4087 ABEND,OPTIONS NOWPSSCATTERCOMP.
TYPE1415 37.172 Variable SMF14DEF='Y' if dataset is encrypted.
TYPE26J2 37.026 Local SubSystem TYPE26J2 not output, SMF6SBS NE 2.
TYPE29 37.093 Support for IMS ODBM Accounting SMF 29 Subtype 1.
TYPE30 37.058 Cosmetic: Uninitialized variable CBPERROR no impact.
TYPE42 37.034 Two more invalid SMF 42 LENSR 520 and 592 added.
TYPE42 37.135 Eight more invalid LENSR= TYPE42 subtype 5.
TYPE42 37.194 TYPE42DS variables S42DSENT/DSCMT identify zEDC.
TYPE42 37.250 SMF 42 ABEND due to SRLEN=208, now all protected.
TYPE7072 37.044 BMC CMF VERSNRMF values 792 and 794 for z/OS 2.3.
TYPE7072 37.104 Variables CECSER/CPCMODEL added to TYPE72GO.
TYPE7072 37.109 Support for z/OS 2.4 SMF Manual 04Mar19 changes.
TYPE70PR 37.046 SMF70BPS/SMF70ACS expanded for each engine type.
TYPE70PR 37.243 Vars SMF70LACM/LACA/LACB are now kept in TYPE70PR.
TYPE72GO 37.179 Variables METGOAL and PCTMETGOL were wrong.
TYPE74 37.032 TYPE749 z/EDC Divide by ZERO protection failed.
TYPE74 37.040 TYPE749 variable R7491DEFCOMPRATIO wrong value.
TYPE74 37.078 TYPE748S var R748SIID fmt $HEX4, no dupes now.
TYPE74 37.166 z/OS 2.4 Updates for TYPE7402 dataset.
TYPE79 37.242 Support for BMC SMF 70 Subtype 255 creates TYPE70FF.
TYPE80A 37.213 Support for RACF TYPE80TK TOKDANAM=AUTOLOGIN.
TYPE82 37.060 INPUT EXCEEDED SMF 82 ST 31, incorrect length.
TYPE82 37.165 TYPE8201 variables SMF82ITE/CKD/LML/USR/PKD wrong.
TYPE82 37.183 Support for SMF 82 new Audit TYPE82AU dataset.
TYPE82 37.241 Several MG082xx formats had wrong hex value.
TYPE92 37.002 TYPE9208 INPUT STATEMENT EXCEEDED, manual wrong.
TYPE92 37.017 Many non-fatal corrections were made to type 92.
TYPE92 37.085 SMF 92 Subtype 52 INPUT EXCEEDED, TRSN doc 52 bytes.
TYPE99 37.082 SMF 99 ST 12 Capacity Incr/Decr individual decodes.
TYPEAAM 37.186 Support for IBM Tivoli Advanced Allocation SMF
TYPEAXW 37.033 Support for Axway V3.3.2 2018/06/27 restructure.
TYPEBBMQ 37.073 UNEXPECTED RTIN messages, BBMQ Version 5.4 no change.
TYPEBE97 37.080A Datasets BETA9706/BETA9706D were not output to PDB.
TYPEBE97 37.197 BETA 97 Subtype 51 did not input "New Area" fields.
TYPEBETA 37.007 Support for Beta93 V6.2 Subtypes 1-3.
TYPEBETA 37.007 Support for Beta93 Version 6.2 subtypes 2 and 3.
TYPEBETA 37.114 Support for updated BETA 93 V6R2 (INCOMPATIBLE).
TYPEBETA 37.160 BETA 93 610 (back level) subtype 40/49 wrong.
TYPEBETA 37.198 BETA 93 Subtypes 12/17/30/31/55 are now output.
TYPECADK 37.219 Support for CA-DISK/Sterling DMS DSINDEX file.
TYPECIMS 37.095 New variables in TYPEDBDS (IMF from BMC).
TYPEDB2 37.035 DB2 V12 overlooked Package variables in DB2ACCTP.
TYPEDB2 37.074 QBSTBPIN always incorrectly calculated before DIF.
TYPEDB2 37.251 DB2 Storage Contraction new vars DELTAAV0/AVA/AVB.
TYPEDB2 37:014 ABEND: DB2 SMF 100 ST 1 NETEAZZA/IDAA DB2STATS.
TYPEDCOL 37.041 Support for APAR OA54879, DCDEXFLG not used FOR zEDC.
TYPEDCOL 37.069 zEDC Compression type values revised DCOLDSET/DCOLDC.
TYPEEDGR 37.015 RMM variable EDGRTIME had missing values.
TYPEFOCU 37.215 Support for FOCUS Version 7.7 USER SMF Record.
TYPEHSM 37.076 Support for HSM FSR Record Unix filename added.
TYPEIMS 37.103 Support for IMS Log Records 5607/5610/5904/5950.
TYPEIMS 37.176 Support for IMS LOG TYPE '02'x.
TYPEMAR 37.181 Support for Hitachi MAR Mainframe Analytics 9.1
TYPEMDM 37.015 RMM variable EDGRTIME had missing values.
TYPENDM 37.047 NDM-CDI dataset NDMCT var NDMCPU 256 times too large.
TYPENDM 37.113 NDM-CDI 24 byte short record INPUT EXCEEDED.
TYPERMFV 37.001 Some RMF III ZRBASI fields blank/wrong in 36.36.
TYPERMFV 37.055 CFACT Coupling Facility Structure Activity Report.
TYPERMFV 37.067 Support for RMF III PCI/SCM/ZFX segments 4 datasets.
TYPERMFV 37.080 SVPCNM and RPRTCLAS added to all RCD datasets.
TYPERMFV 37.167 z/OS 2.4 Updates for RMF MONITOR III datasets
TYPERMFV 37.246 Variables PCIFTET/PCIFTQT in ZRBPCI incorrect.
TYPESAPZ 37.222 Support for SAP Z Connector USER SMF record.
TYPESTC 37.018 Support for STC HSC Subtype 32 and 33 new datasets.
TYPETLMS 37.192 Support for TLMS creates two new datasets.
TYPETPX 37.107 Misaligned TPXETIME reported as 8a Oct 27, 1935.
TYPEVM 37.130 New VM Account datasets supported.
TYPEVMXA 37.012 ABEND: ZVM MONWRITE NEW 40061802 Service Level.
TYPEVMXA 37.028 Support for z/VM 7.1 (INCOMPAT, BROKEN CONTROL).
TYPEVMXA 37.084 z/VM VXPRCAPM dataset vars CMB10C0-X4 wrong values.
TYPEWSF 37.083 Logic revised to use OBJT/ACT for Input choice.
TYPEWSF 37.111 Final revisions for WSF/EOS WSFAUDIT AUDACT/OBJN.
TYPEXAM 37.081 Analyzing VPS USER dataset, must use INTORSUM='SU'.
UTILMISS 37.053 Utility to remove all variables that are all missing.
VMACEDGR 37.225 RMM/EDGR dataset EDGRXEXT RDPHYSIZE too small.
VMACSMF 37.249 Using FTP ACCESS from z/OS fails with JFCB Issue.
VMXGALOC 37.021 New parms YR2KEEP and BASEYEAR for Yearly PDB.
VMXGALOC 37.224 Note if you added VMXGALOC to your IMACINIT.
VMXGDSN 37.191 RMM/EDGR in VMXDSN had zero obs for TAPES/TAPEDSNS.
VMXGOPTR 37.252 Restores ORIGINAL, used to always reset if changed.
VMXGPRAL 37.006 Unbalanced parens in variable label, non fatal.
VMXGSUM 37.245 KEEPALL=NO with INCODE= could cause UNINIT message.
VMXGUOW 37.011 Enhanced for each CICSTRAN-only PDB.ASUMUOW.
CONFIMXG 37.267 DO NOT USE ENCODING=EBCDIC1047, use OPEN_ED-1047.
ASUMMSUS 37.265 ERROR PARM OPTNE NOT DEFINED, typo.
TYPE99 37.264 SMF 99 Subtype 2 TYPE99_2 new variables added.
TYPE42 37.261 SMF 42 Subtype 1 TYPE42DS INPUT STATEMENT EXCEEDED.
TYPEIDMS 37.260 IDMS dataset IDMSTAS USER Fields were misaligned.
TYPEIMS 37.259 IMS SYNCPOINT Log Records IMS5937/5938 keeps all vars
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 37.272 WERE IN MXG 37.37 DATED Jan 6, 2020 ========
Change 37.272 If you did not specify EXCELDEST you could get WARNINGs:
ANALMSUS Argument 2 to macro function %SUBSTR is out of range
Jan 5, 2020 Argument 3 to macro function %SUBSTR is out of range
Change 37.271 %BUILDIMS can create all current MXG IMSLOG datasets and
BUILDIMS REPORT=YES (default) prints counts of bytes/records for
FORMATS each LSUBCODE; REPORT=ONLY will produce only the report.
VMACCIMS Not all IMS Log Records create MXG datasets; many records
VMACIMS are for database recovery with no performance metrics,
VMXGINIT but support will be added upon request and test data.
Jan 5, 2020 // EXEC MXGSASV9
//IMSLOG DD DSN=YOUR.IMS.LOG.DATA,DISP=SHR
//PDB DD DSN=YOUR.IMS.PDB,DISP=(,CATLG),SPACE=....
//SYSIN DD *
%BUILDIMS(REPORT=YES,
WANT= F9 FA 56FA,
IMSVER=14.1,
START= '01JAN2020:08:00:00'DT,
END = '01JAN2020:10:00:00'DT);
Note: REPORT=YES reports all IMS Log Records in input and
is not impacted with WANT/START/END/IMSSYSTEM selections.
See comments in member BUILDIMS for documentation.
Thanks to Randy Hewitt, DXC. USA.
Change 37.270 A TECHNOTE documenting how to recover from MXG ABENDS.
ADOCABND
Jan 1, 2020
Change 37.269 TYPE71 variables SMF71PIS/SMF71POS, 4K TO/FROM SCM are
VMAC71 accumulated fields, so they are correct only when TYPS71
Dec 23, 2019 (or BUILDPDB) is used, since the deaccumulation is done
in the _STY71 Data Set Sort Macro, and will always be
missing values in the first obs from each SYSTEM.
Thanks to Graham Harris, RBS, ENGLAND.
====== CHANGES THRU 37.268 WERE IN MXG 37.09 DATED Dec 20, 2019 ========
Change 37.268 Variable SM116EVT in MQMACCTQ and MQMQUEUE datasets was
VMAC116 not set for Task Terminated; test for '21'x was wrong and
Dec 20,2019 changed to four byte test for '200800000'x for Terminate
and '00080000'x for Initiate.
Thanks to Scott Barry, SBBWORKS, INC, USA.
====== CHANGES THRU 37.267 IN EARLY ADOPTER MXG 37.09 DATED Dec 20, 2019
Change 37.267 z/OS: ENCODING=EBCDIC1047 corrupts data; OPEN_ED-1047 is
CONFIMXG and has been REQUIRED for MXG, and is the z/OS Default.
VMXGINIT With ENCODING=EBCDIC1047 character variables with '15'x
Dec 12, 2019 byte value are changed to '25'x, and byte values of '25'x
are changed to '15'x! Those are the New Line & Line Feed
characters that swap. You can display your options with:
PROC OPTIONS OPTION=ENCODING;
PROC OPTIONS OPTION=LOCALE;
PROC OPTIONS OPTION=NLSCOMPATMODE;
-You can add an ENCODING=OPEN_ED-1047 statement in your
CONFIGV9/CONFIMXG/CONFIGxx tailoring member, or you can
set with // EXEC SAS94,OPTIONS='ENCODING=OPEN_ED-1047'
-Not only can character bit tests and formatted values be
wrong, some numeric TODSTAMP datetime fields are created
from character variables when shorter than 8-bytes, using
DATETIME=INPUT(CHAR6!!'0000'x),TODSTAMP8.);
Changing the second byte from '15'x to '25'x is 30 days.
-VMXGINIT is enhanced to print error message if ENCODING
option is not OPEN_ED-1047.
-And, OPEN_ED-1047 does work with NONLSCOMPATMODE, which
SAS has indicated will become the z/OS default in a
future version, so you can be prepared.
Thanks to Andrew Gadsby, SAS UK, ENGLAND.
Thanks to Andy Knight, SAS UK, ENGLAND.
Thanks to Stephen Hoar, Lloyds, ENGLAND.
Thanks to Mark Tomlinson, Lloyds, ENGLAND
Change 37.266 Parameters DATETIME= and INTERVAL= were not specified in
TRNDDB2P VMXGSUM invocation, causing little or no summarization.
TRNDDB2R
Dec 11, 2019
Thanks to Marybeth Delphia, CPA.TEXAS.GOV, USA.
Change 37.265 If you did not specify PDBOUT the correct dataset(s)
ANALMSUS names were not generated.
Dec 11, 2019 -The use of substitution macros in IMACKEEP made ANALMSUS
fail if you tried to run it twice in a single SAS
session. Those affected macros are now nulled out.
-OPTIONS NOBYLINE was set but there were no BY values
in the TITLE statements - there are now.
-MXG 37.09 ONLY. ERROR KEYWORD PARM OPTNME NOT DEFINED,
now correctly spelled as OPTNAME.
-Eliminated a WARNING about SUBSTR out of range when
EXCELDEST was NULL.
Thanks to Jan Tielemans, KBC, BELGIUM
Change 37.264 SMF 99 Subtype 2 TYPE99_2 dataset did not input the many
VMAC99 variables that had been added in z/OS 2.3.
Dec 15, 2019
Thanks to Betty Wong, Bank of America, USA.
Change 37.263 READDB2 didn't create the T102SSSS and T102S000 datasets
READDB2 when a numeric IFCID was in the IFCIDS= parameter. Now,
Dec 10, 2019 it does unless T102SSS/T102000 are set to NO.
Logic to parse strings for each dataset was simplified
and relocated to a separate macro to simplify ongoing
maintenance.
Change 37.262 Replaced by Change 37.271.
BUILDIMS
Jan 1, 2020
Change 37.261 TYPE42 INPUT STATEMENT EXCEEDED subtype 6 due to a short
VMAC42 S42DSSNL=72 segment when SMF manual had 80, probably due
Dec 7, 2019 one of the APARs in Change 37.250.
-Subtype 5, LENSR=208 records were deleted (Change 37.260)
with log message, but now they are output and the extra
48 bytes are skipped.
Thanks to Richard Haynes, Blue Cross Blue Shield of Kansas, USA.
Change 37.260 IDMS dataset IDMSTAS fields were misaligned because the
VMACIDMS new variable TASBJBID was inserted in the record.
Dec 6, 2019
Thanks to Paola Rosero, Government of Quebec, CANADA
Change 37.259 IMS SYNCPOINT Log Records IMS5937 and IMS5938 only kept a
VMACIMS small number of variables, now all fields in the record
Dec 16, 2019 are kept.
Thanks to Randy Hewitt, DXC. USA.
Change 37.258 Earlier releases of the %SCAN function of the %MACRO
READDB2 COMPILER returned the input string if there was only
Dec 1, 2019 a single string for the delimiter that was used, which
required extra MXG logic to correct, and which could fail
if AAAA was used, with no BBBB, and there was a CCCC but
no space between the two slashes, causing CCCC to be seen
as the BBBB argument, raising a WORD2 macro error. Now,
SAS returns the string correctly so the excess MXG logic
could be removed along with this (rare) exposure.
-If all you requested with WANTONLY was DB2ACCT DB2ACCTW
was also produced.
Thanks to Ervin Claxton, CSX, USA.
Change 37.257 This member will work but is obsolete and has been
TRNDRMFN replaced by TRNDRMFI. The biggest difference is in the
Nov 29, 2019 input dataset. This member uses PDB.RMFINTRV which would
only get a single days PDB as input while the TRNDRMFI
member uses WEEK.RMFINTRV which would be all of the days
of the week.
Thanks to Wayne Bell, UNIGROUP, USA.
====== CHANGES THRU 37.256 WERE IN MXG 37.08 DATED Nov 26, 2019 ========
Change 37.256 ROSCOE new dataset PDB.ROSCOMON contains an observation
DIFFROSC for each of these MONITOR values:
Nov 19, 2019 ALL AMS ATT CON CPL DIS DSF ETS HEX IMP
JCL LIB LOO OTH OUT PUR SOR UTI VTO ZAP
and variable MONITOR contains the monitor acronym.
The Monitors AUD AWS RPS SHU STA VPE are not included,
as they have always had a separate ROSCOxxx dataset.
Thanks to Linda S Berkley, US Army, USA.
Change 37.255 -FDF support added for the RMF Monitor III PCIG3 (PCIE
ADOCRMFV Activity Data Table) and SCMG3 (Storage Class Memory Data
ASMRMFV Table). General ASMRMFV support for these tables already
Nov 19, 2019 existed.
-Improved ASMRMFV FDF handling of 16 byte binary
Fields using Extended Floating Point arithmetic.
-Minor corrections made to ASI, CPD, GEI, OPD, SPG, and
SSHG3 FDF Variable Name Tables.
-Main storage reduction made for FDF Alias and True
Name entries in Variable Name Tables.
-FDF now uses only 1 pattern table for all character
Fieldnames instead of a pattern table for every character
Fieldname when a user character pattern compare occurs.
-Message RMFV088I now shows XFP (Extended Floating Point)
tag for 16 byte quadword fields during FDF processing.
-Floating point fields were not always scaled by FDF
when required prior to comparisons to a user value.
-When the maximum 32K LRECL output length to RMFBSAM would
be exceeded in PROCCPU, PROCCFI, and PROCRCD subroutines
the entire RMF III table will now be skipped. This should
be a very rare event.
-Section 12 Messages updated in ADOCRMFV.
-These documentation sections in member ADOCRMFV are
added for new FDF support:
40 Filtering The PCIG3 Table
41 Filtering The SCMG3 Table
Remaining existing section numbers are incremented by 2.
Change 37.254 -MXG 37.05-37.07. When CPC parameter was specified,
ASMRMFV Message RMFV057I PARMS KEYWORD VALUE IS NULL printed
Nov 16, 2019 and neither CPCDB nor CPUG3 tables were selected.
-PCIG3 table support was not checking the z/OS release.
Only z/OS 2.3 and higher releases are supported.
Inputting a PCI table from a lower release results in an
MXG build failure. PCIG3 tables from older releases will
now be ignored. Applies to MXG Releases 37.03 and up.
Change 37.253 Cosmetic. Labels were blank for these variables/datasets
ASUM70PR STCVSM32 variable SMLSSMF32
VMAC102 ASUMCEC variable CPUICFTM
VMAC113 TYPE1131 EXTND22x variables had COUNTER 225 UNDEFINED
VMAC120 FOCUSMSO variables FOCUMEMA,FOCUMEMB
VMAC26J2 TYPE26J2 variable SUBS
VMAC82 TYPE82 variable SMF82_TAK_KEY_EVENT
VMACSTC TYPE120 variable SMF1209HW
Nov 18, 2019 T102S106 variable QWO4ADM2-QWO4SADM
Thanks to Chris Weston, SAS ITRM Development, USA.
Change 37.252 During QA testing we found that 250 members changed a
VMXGOPTR SAS system option but did not return that option to its
MANY original value, which could impact subsequent programs
Nov 18, 2019 in that SAS job step or SAS Session. Previously, with
NEWVALUE=ORIGINAL, VMXGOPTR reset the option to its
value PRIOR to the LAST VMXGOPTR invocation, but now
it is restored to the original value of the SAS Session
or batch STEP, and all 250 members now have pairs of
VMXGOPTR to change and to then reset options to their
ORIGINAL value.
Example of use of VMXGOPTR with this change with the
original option DSNFERR having value DSNFERR:
%VMXGOPTR(OPTNAME=DSNFERR,NEWVALUE=NODSNFERR);
this code executes with NODSNFERR
%VMXGOPTR(OPTNAME=DSNFERR,NEWVALUE=NODSNFERR);
this code executes with NODSNFERR
%VMXGOPTR(OPTNAME=DSNFERR,NEWVALUE=ORIGINAL);
subsequent code executes with DSNFERR.
With the original VMXGOPTR, the subsequent code was
executed with NODSNFERR, which was wrong.
-The report members also set TITLE and FOOTNOTEs to null
to prevent carry-forward for following program reports.
Change 37.251 New DB2STATS variables DELTAAV0/AVA/ACB are negative when
VMACDB2 storage contraction starts, and the value is the number
Nov 7. 2019 of pages needed. Values for Available, DBM1 and DIST are
created. IBM reports, with this ZPARM (xxxxxxxx) "AUTO",
contraction will begin when paging is detected and DB2
will try to bring a system to a point where paging is
minimal or non-existent. DB2 will enter a full
contraction mode if 100% of REALSTORAGE_MAX is hit, when
message DSNS0003I is issued, and the discard will start,
if PM99575 is applied. DB2STATS variable QSST_RSMAX_WARN
counts the number of times the REALSTORAGE_MAX Warning
was reached in each interval.
Thanks to Sieghart Seith, FICUCIA, GERMANY.
Change 37.250 SMF 42 Subtype 5 APAR OA52133 causes ABEND with LENSR=208
VMAC42 in SMF42SRL and a 208 byte segment, APAR OA54663 corrects
Nov 7, 2019 setting SMF42SRL=160 with only a 160 byte segment. New
length was introduced by the usermod ++APAR for OA52133,
when it was still in development, and before OA54663.
-Below Change Text was insufficient to protect for 208,
and logic was completely revised in Change 37.261, 37.09.
To protect for future invalid lengths to avoid ABENDs,
MXG logic first tests for a delta of 160 bytes between
Storage Class Name fields and uses LENSR=160 if true,
or the SMF42SRL value is tested for a valid delta, and
uses that value if true. Otherwise, the record is
skipped with an MXGNOTE on the log.
Thanks to Hiroshige Koshigoe, FTB CA, USA.
Thanks to Sarel Swanepoel, SARS, SOUTH AFRICA.
Change 37.249A The FTP ACCESS method executing on z/OS to read z/OS data
CHCK4FTP fails because the expected JFCB/DSCB tokens do not exist
Nov 22, 2019 with the SAS FTP Access method.
-Most MXG use of the FTP ACCESS method executes on ASCII
to read z/OS SMF data, which does not have this exposure.
-There are two ways to use z/OS to z/OS ftp:
Using SMF as an example DDNAME/INFILE name:
FILENAME SMF FTP "'MYSMFDATA'" HOST='IP ADDRESS'
USER='USERNAME' PASS='PASSWORD' S370VBS LRECL=32760
RCMD='SITE RDW';
%LET MXGJFCB=;
%LET MXGDSCB=;
%INCLUDE SOURCLIB(BUILDPDB);
or
FILENAME SMF FTP "'MYSMFDATA'" HOST='IP ADDRESS'
USER='USERNAME' PASS='PASSWORD' S370VBS LRECL=32760
RCMD='SITE RDW';
%CHCK4FTP(DDNAME=SMF);
%INCLUDE SOURCLIB(BUILDPDB);
-The %CHCK4FTP(DDNAME=yourdd); in example two validates
that that DDNAME is allocated and then detects the engine
type, and for FTP, MXGJFCB and MXGDSCB macro variables
are blanked to prevent the JFCB/DSCB error.
Thanks to Mike Martin, NC State Employee's Credit Union, USA.
Change 37.249 %DSCRDT now defaults to a null value and is enabled by
DODSCRDT using %INCLUDE SOURCLIB(DODSCRDT); in your //SYSIN.
VMXGINIT -These INFILE names can be enabled for these TYPExxxx:
Nov 26, 2019 TYPExxxx: TYPECTLT TYPEDCOL TYPEEDGR TYPERMFV
INFILE: CONTROLT DCOLLECT EDGHSKP RMFBSAM
TYPExxxx TYPETMS5 TYPEIMS
INFILE: TMC IMSLOG
See change 37.161 for the original addition.
Change 37.248 Unused Change Number.
Nov 4, 2019
Change 37.247 Example analysis to track down why USERID was revoked.
TECHNOTE
Nov 4, 2019
SUMMARY: Userid for an inbound FTP process had the wrong password,
eventually userid was revoked, but the MVS RACF SYSLOG message was
misleading, as it was expected to be a VTAM LU, but it is the value
"A86CF325" in message that matches the RACFTERM:
MVS SYSLOG excerpt
ICH408I USER(FCADOU4 ) GROUP(ADOFTP ) NAME(FTPS ID CDS T4) 546
LOGON/JOB INITIATION - INVALID PASSWORD ENTERED AT TERMINAL A86CF325
IRR013I VERIFICATION FAILED. INVALID PASSWORD GIVEN.
MXG TYPE8001
RACF*USER*NAME [RACFUSER] FCADOU4
EVENT*CODE*QUALIFIER [RACFQUAL] 101:INVALID PASSWORD
RACF/VTAM*TERMINAL*NAME USED [RACFTERM] A86CF325
MXG VMAC80A: INPUT RACFTERM $EBCDIC8. /*@43 SMF80TRM*/
RACF MACROS and INTERFACES Documentation
SMF80TRM 8 EBCDIC Terminal ID of foreground user (zero if not avail)
MXG TYP11902
CONNECTION*ESTABLISHMENT [TTSTIME] 26OCT2019:09:03:17.99
TIMEWAIT OR*LASTACK [TTETIME] 26OCT2019:09:03:18.22
REMOTE*IPV6*ADDRESS [TTRIPV6] 0000:0000:0000:0000:0000:FFFF:A86C:F325
(matches RACFTERM from Type 80, and the MVS RACF ICH408I message)
Change 37.246 Dataset ZRBPCI variables PCIFTET and PCIFTQT were input
VMACRMFV incorrectly as milliseconds (PIB8.3) units, but they are
Oct 31, 2019 both microseconds (PIB8.6), with TIME13.3 print format.
Change 37.245 If you KEEPALL=NO or %LET MXGKEEP=NO and your VMXGSUM
VMXGSUM invocation had an INCODE= you might have gotten an
Oct 30, 2019 UNINIT message on one or more variables in the INCODE
that were not also referenced in one of the parameters.
This change modifies KEEPALL to YES if INCODE is used.
Change 37.244 Observations from Subtype 3 SMF 119 records were not
VMAC119 output because some of the Production UserIds did not
Oct 30, 2019 have read access to the SMF unix Facility, which is
required for SMF record to be written.
Thanks to Aslyona Bertneski, Express-Scripts, USA.
Change 37.243 Variables SMF70LACM SMF70LACA and SMF70LACB are now kept
VMAC7072 in TYPE70PR dataset to aid in SCRT comparisons. They
Oct 28, 2019 have been in TYPE70 since Version 33.
Thanks to Ken Deering, Compuware, USA.
Change 37.242 Support for BMC SMF79 Subtype 255 creates new dataset:
EXTY79FF DDDDDD Dataset Description
FORMATS TY79FF TYPE79FF BMC SMF 79 SUBTYPE 255
IMAC79
VMAC79
VMXGINIT
Oct 28, 2019
Thanks to Randy Hewitt, DXC, USA.
Change 37.241 Several MG082xx format for SMF 82 records had wrong hex
FORMATS value displayed, but the text description was correct.
Oct 27, 2019
Thanks to Ron Rust, Worldpay, USA.
Change 37.240 DB2 Variable QWP4STPGS='STATPGSAMP/N/Y/S' was not INPUT
VMAC102 in T102S106 dataset.
Oct 24, 2019
Thanks to Lai Fai Wong, Bank of America, USA.
====== CHANGES THRU 37.239 WERE IN MXG 37.07 DATED Oct 22, 2019 ========
Change 37.239 Support for z/15 SMF113 records new CRYPTO17-CRYPTO20
VMAC113 counters (ERROR: ARRAY SUBSCRIPT OUT OF RANGE ABEND),
Oct 22, 2019 only if you had enabled the HIS CRYPTO counters.
Thanks to Steven W Erkkila, USBANK, USA.
Change 37.238 Support for NDM-CDI 'S#' record type is now output in
VMACNDM existing NDMAE dataset.
Oct 16, 2019
Thanks to Rob D'Andrea, Royal Bank of Scotland, ENGLANE.
Change 37.237 Cosmetic. STARTIME syntax modified to eliminate notes
ASUM42DS from VMXGSUM internal invocation.
Oct 15, 2019
====== CHANGES THRU 37.236 WERE IN MXG 37.07 DATED Oct 14, 2019 ========
Change 37.236 Support for z/15 SMF 113 records new EXTEND256-EXTEND287
ANALSIIS counters, with corresponding ARRAY size increases, CAUSED
VMAC113 ERROR:ARRAY SUBSCRIPT OUT OF RANGE ABEND. In ANALSIIS,
Oct 14, 2019 SORT order was corrected.
Thanks to Tony Curry, BMC, USA.
====== CHANGES THRU 37.235 WERE IN MXG 37.07 DATED Oct 12, 2019 ========
Change 37.235 CRITICAL ERROR if BLDSMPDB+VMXGALOC is used on ASCII.
BLDSMPDB An ending comma in line 949 of BLDSMPDB caused
Oct 12, 2019 ERROR: All positional parameters must precede keyword.
Remove the comma in line 949 of BLDSMPDB.
====== CHANGES THRU 37.234 WERE IN MXG 37.07 DATED Oct 9, 2019 ========
Change 37.234 DB2 variables added to DB2ACCT and DB2STATS datasets:
VMACDB2 QXSTEHLST='EXECUTION*HISTORY.LOST'
Oct 8, 2019 QXSTHVLST='HV*RECORDING*HISTORY*LOST'
QXRFMIAP='RID*LIST*PROCESSING*NOT USED'
Thanks to Warren Cravey, Fidelity, USA.
Change 37.233 CICS variable ABCODE created by UTILEXCL was the concat
UTILEXCL of ABCODE113!!ABCODE114, but using INPUT ABCODE $EBCDIC8.
Oct 8, 2019 eliminated the need for that statement, which caused
ERROR: The name ABCOD113§§ABCOD114 is not a valid SAS name
when UTILEXCL was run on Linux. A track with SAS will be
opened to resolve that error, because double exclamation
points are used 6900 times in MXG for concatenation, but
this code matches the VMAC110 code and should have been
there some time ago, just for consistency, but now for
circumvention.
Change 37.232 -If CICS Dynamic Transaction Routing, DTR is used, the
VMAC110 CICSTRAN has PROGRAM='########' which historically was
VMXGINIT ONLY used when there was an invalid transaction name
Oct 9, 2019 typed in by the user, which caused many fields to be
missing values, so MXG instead output the transaction
to the CICSBAD dataset. But now, if you enable DTR,
the observation count in CICSTRAN may drop dramatically
by the number of obs output in CICSBAD. There does not
appear to be a flag that identifies DTR was used.
You will need to set
%LET MXGCICSDTR=YES;
to cause MXG to output ALL transactions with '########'
values to CICSTRAN instead of to CICSBAD.
-The original test for CICSBAD also tested TRANFLAG for
a bit that indicated invalid times in the record, but
IBM removed that bit, so that bit test was removed.
-Changes 23.312 and 24.155 document PROGRAM='########';
Thanks to Scott Barry, SBBWORKS, INC, USA.
Change 37.231 z/VM 6.4.18.2 BROKEN CONTROL RECORD in IODVSW extended
VMACVMXA INPUT for SKIP GE 20 was missing the @ at the end.
Oct 7, 2019
Thanks to Rob D'Andrea, Royal Bank of Scotland, ENGLANE.
Change 37.230 If you specified DURATM=INTERVAL with INTERVAL= values of
VMXGSUM TWOMIN THREEMIN or TWENTYMIN the DURATM was not created.
Oct 6, 2019
Change 37.229 Doc only change - corrected spelling and syntax.
ANALCAPD
Oct 5, 2019
Change 37.228 -Format $MGRMIPS is updated for the z/15 processor type
ASUMMIPS 8561 to map the CPCFNAME ('8561-401') to the MIPS per MSU
FORMATS value (267), used in ASUMMIPS and other 'MIPS' calcs.
Oct 5, 2019 -Protection for CPCFNAME not found in $MGRMIPS format now
gracefully terminates with a message from ASUMMIPS.
Change 37.227 QLACRLNU was not added to DB2ACCTB nor DB2ACCTG causing
VMACDB2 UNINIT messages in ASUMDB2B and ASUMDB2G.
Oct 4, 2019
Change 37.226 TYPE 120 dataset TY120100 variables SM120RULEXCALLS (was
VMAC120 always -1) and SM120RULEXFSUM were in the wrong order in
Oct 3, 2019 the INPUT statement.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 37.225 RMM/EDGR dataset EDGRXEXT variable RDPHYSIZE was not
VMACEDGR multiplied by the RDFACTOR(KB/MB/GB) so it was too small.
Oct 1, 2019 The value was correct in the other EDGR datasets.
Thanks to Bradley Leis, TELUS, CANADA.
Change 37.224 If you correctly added VMXGALOC to your IMACINIT so that
VMXGALOC you would always have the current PDBs allocated to each
BLDSMPDB SAS/MXG session and changed the number of PDBs (daily,
Oct 1, 2019 weekly, monthly, etc.) in BLDSMPDB you could possibly
wipe out old directories unintentionally. VMXGALOC now
detects that it has already run and unless the new
INVOKEBY= parameter is set to bldsmpdb sets the READONLY
parameter to YES to prevent deletion of old directories.
VMXGALOC in IMACINIT should always specify READONLY=YES
so this is only insurance that will produce and MXGWARN
message and set condition code 8.
Change 37.223 DB2 IFCID 376 variable QW0376SINR (statement count) was
VMAC102 not kept in 8 bytes, causing small differences in the
Sep 30, 2019 MXG value (222986880) vs IBM (222986962) = 82 smaller.
With stored length of 8 bytes, the values match.
Thanks to Warren Cravy, FMR, USA.
Change 37.222 Support for SAP Z Connector USER SMF Record creates
EXSAPZCO DDDDDD DATASET DESCRIPTION
IMACSAPZ SAPZCO SAPXCO SAP Z CONNECTOR
TYPESAPZ
TYPSSAPZ
VMACSAPZ
VMXGINIT
Sep 30, 2019
Thanks to Nestor D Rossi, BancoGalica, ARGENTINA.
Change 37.221 Reserved Change.
Change 37.220 If you specified SYNC59=NO (the default) the intervals
VMXGDUR always landed (for example with INTERVAL=QTRHOUR) on the
Sep 26, 2019 quarter at 0 15 30 45 minutes. If you wanted to keep the
actual intervals you would have needed to subtract 1
minute. VMXGDUR will now do that for you with the new
USE59 parameter. YES will subtract 60 seconds from the
calculated value and get the QTRHOUR back to 59 14 29 44
minutes. You can implement this globally be inserting in
IMACINIT: %LET SYNCTO59=YES;
The purpose of SYNC59 was always to put the start of
intervals on the hour since that usually makes more sense
on management reports and graphs. But if you choose to
use this on interval data without modifying the FLORCEIL
parameter to CEIL and you use SYNC59=NO you will be
getting the STARTIME of the prior interval rather than
the current interval since 12:59 with the FLORCEIL=FLOOR
set resolves to 12:45:
FLOOR('12:59't/900)*900;
Examples using default of SYNC59=NO
FLORCEIL=FLOOR
TIMESTMP=29AUG18:12:59:00 datetime=29AUG2018:12:45:00
FLORCEIL=FLOOR USE59=YES
TIMESTMP=29AUG18:12:59:00 datetime=29AUG2018:12:44:00
FLORCEIL=CEIL
TIMESTMP=29AUG18:12:59:00 datetime=29AUG2018:13:00:00
FLORCEIL=CEIL USE59=YES
TIMESTMP=29AUG18:12:59:00 datetime=29AUG2018:12:59:00
Thanks to Randy Hewitt, DXC, USA.
Change 37.219 Support for CA-DISK/Sterling DMS file DSNINDEX.
EXCAARCH INFILE is CADISK, creates two new dataset:
EXCADISK DDDDDD DATASET DESCRIPTION
FORMATS CADISK CADISK DSNINDEX ARCHIVED OR BACKED UP.
IMACCADK CAARCH CAARCH ARCHLOGS ARCHIVED DATASETS.
TYPECADK -Invalid LEAP YEAR dates (year 2025, day 366) can't be
TYPSCADK set to a numeric value, variable DSNDS1EDLEAP will now
VMACCADK have the invalid date as character (2026366).
VMXGINIT
OCT 2, 2019
OCT 30, 2019
Thanks to Pierre-Pascal Joulin, SOCGEN, FRANCE.
Change 37.218 DURATM=INTERVAL conflicted with DURATM in the SUM=
ASUMMIPS parameter which raised an MXGWARN message. DURATM
SEP 26, 2019 was removed from the SUM= list.
MXGWARN: DURATM=INTERVAL WAS SPECIFIED BUT THE DURATM
MXGWARN: VARIABLE CONTAINS NON-MISSING VALUES. THIS
MXGWARN: MAY BE AN ERROR CONDITION. VALUE OF DURATM
MXGWARN: IN THE OUTPUT DATA IS: 0:15:00.00
Change 37.217 A test of EXCELDEST was not protected for length of 0
ANALMSUS and generated a WARNING message but still ran albeit
Sep 26, 2019 with condition code 4.
Thanks to Robert Sample, TOMY, USA.
Change 37.216 SMF Type 2 Subtypes 1 and 2 fields SMF2GSIG and SMF1ISIG
TYPE0203 were documented as 512 bytes long, but IBM updated their
Sep 26, 2019 doc that they are variable length fields, so the INPUT
is revised to use the SMF2GSIGLEN and SMF2ISIGLEN fields
to input the variable length data.
Change 37.215 Updates for FOCUS USER SMF record changes version 7.7.
ADOCFOCU -VMACFOCU was changed to accommodate a change by IBI in
FORMATS their SMF records somewhere around version 7.7 of
VMACFOCU WebFOCUS (vendor support wasn't clear about when the
Sep 25, 2019 change happened).
Nov 14, 2019 -User ID fields were changed from 8 to 20 bytes and a
'security provider' value was prepended to each user ID
with a '\' as separator. These changes caused other
fields in the SMF record to be in different columns than
they were previously. Fields were also added for zIIP
time and zIIP-on-CP time.
-There is no version field in the SMF record, so this code
uses the record subtype and the length of the record to
determine which record format to use. There are four
subtypes - 1,2,4, and 5, which are Logon, Logoff, Begin
Query, and End Query, respectively. Old format records
are shorter than new format records, so the code checks
to see if a record is shorter than the new format, and if
it is, uses the old format. Older format records will
have missing or blank values for old variables that no
longer exist in the new records.
-Each user ID variable (Logon User ID, Security User ID,
Pooled User ID) now has a corresponding security provider
variable. The provider will be blank if an older format
record was used.
-zIIP time and zIIP-on-CP time variables are normalized,
according to the vendor. We are not sure of the accuracy
of these fields, and would not count on them for serious
reporting.
-Members ADOCFOCU and VMACFOCU were changed to reflect
these changes. Some labels were changed to reflect that
these records are produced by the vendor's WebFOCUS
product in addition to the FOCUS MSO (Multi-System
Option). In addition two new values are added in the
new MGFOCTY format to reflect subtypes 4 (Begin Query)
and 5 (End Query).
Thanks to Tim Hare, Hare Systems, USA.
Change 37.214 ANAL82AU combines the separate SERV and USER observations
ANAL82AU into one observation with two sets of variable names.
Sep 25, 2019
Thanks to Alexander Bitter, Worldpay, USA.
Thanks to Rib Rust, Worldpay, USA.
Thanks to Brian Bowling, Worldpay, USA.
Change 37.213 Support for RACF 80A TOKDANAM=AUTOLOGIN creates new
VMAC80A variable TOKAUTOLOGIN in TYPE80TK dataset.
Sep 24, 2019
Thanks to Andrew Krink, Northern Territory Government, AUSTRALIA.
Change 37.212 Support for z15 processor SMF 113 RNI equation changed to
ASUM113 RNI=2.9*(0.45*L3P+1.5*L4LP+3.2*L4RP+6.5*MEMP)/100;
VMAC113
Sep 23, 2019
Change 37.211 Updates to TYPERMFV.
IMACRMFV -Variable PCIFTYPHEX added to ZRBPCI dataset.
VMACRMFV -Support for XCFG3 segment creates three datasets
Oct 2, 2019 that contain the same data as RMF I XCF records:
DDDDDD DATASET DESCRIPTION SAME DATA
ZRBXCG ZRBXCG RMF III XCF GROUP TYPE74ME
ZRBXCP ZRBXCP RMF III XCF PATH TYPE74PA
ZRBXCS ZRBXCS RMF III XCF SYSTEM TYPE74SY
Change 37.210 If the default requested INTERVAL=_CICINTRV (HALFHOUR)
CICINTRV doesn't match your actual CICS Statistics interval, or
Sep 20, 2019 isn't an exact integer multiple, MXG printed a warning
that the resultant CICINTRV dataset was invalid, as it
built using your _CICINTRV value.
Now, your _CICINTRV value is compared with the maximum
DURATM in your data, and if your requested _CICINTRV can
be honored it will be; otherwise the interval of your
data is used, and a warning of the change is printed.
Change 37.209 Spurious log messages INVALID VALUE FOR INPUT FUNCTION
DODSCRDT that occur only if INFILE is on TAPE are harmless with no
Sep 19, 2019 impact on the output MXG datasets. Thought removed by the
Aug 30 MXG 37.06 Change 37.189, they weren't until this.
Thanks to Betty Wong, Bank of America, USA.
Change 37.208 ID & 89 added to the list of product suffix found in your
UTILBLDP USERADD= argument that are already in BUILDPDB=YES and
Sep 19, 2019 would have caused an error if honored.
Thanks to Randy Hewitt, DXC, USA.
Change 37.207 -New format MG110XL is created for UCICSCNT report so you
QA9464 can choose the display of the CICS STID variable:
UCICSCNT MG110XN - IBM Description: 2:Storage Manager DSA
UTILVREF MG110XD - MXG Dataset Name 2:CICSMDSA
FORMATS MG110XL - MXG Dataset + Label 2:CICSMDSA:SMS STATS
VMXGINIT The existing default MG110XN format is unchanged.
Sep 18, 2019 In your SYSIN %LET UCICSFMT=MG110XD.; sets your choice.
-New format $MGDSNLAB maps MXG Dataset Name to the Dataset
Label for all MXG datasets.
Thanks to MP Welch, Bank of America, USA.
Change 37.206 BUILDPDB PDB.STEPS & PDB.JOBS are enhanced with variable
BUILD005 CPUZIPTM_CPUIFATM_INST to count zIIP instructions; the
BUIL3005 CP instruction count is already in variable CPU_INST.
Sep 13, 2019
Thanks to Jim Horne, Lowe's Companies, USA.
Change 37.205 TYPE71 LFAREA 1Mb FRAMES can be broken up into smaller
VMAC71 pages, and the number of BrokenUP frames is in the new
Sep 13, 2019 variable SMF71BRKUP='PGBL 1MB*BREAKUP*FRAMES', calculated
as the delta between installed 1MB Pageable frames and
the used 1MB frames.
Thanks to Joe Faska, DTCC, USA.
Thanks to Toni Skrajnar, IBM Support, USA.
Change 37.204 -z/OS 2.4 MXG RMF Monitor III support.
ADOCRMFV -New MXG Support for RMF III XCRG3 table:
ASMRMFV -New ASMRMFV Field Data Filtering (FDF) support for
VMACRMFV 4 more RMF III tables: CPDG3 ENTG3 GEIG3 OPDG3.
Sep 12, 2019 -15 ASMRMFV corrections for conditions found during
Sep 20, 2019
Sep 26, 2019
Oct 3, 2019 *** New Support ***
Oct 8, 2019
-Support for the RMF Monitor III Cryptographic Hardware
Data table (CRYG3) table new with z/OS 2.4 . The CRYG3
table does not exist for prior z/OS releases.
-The CRYG3 selection option is CRY (alias K).
The CRYG3 filtering option is NOCRY (aliases -CRY, -K).
CRYG3 is also selected if the MOST option is used.
-Support for the RMF Monitor III XCF Activity Data table
(XCFG3) which has existed at least since z/OS 1.13 but
was undocumented.
-The XCFG3 selection option is XCF (alias X).
The XCFG3 filtering option is NOXCF (aliases -XCF, -X).
XCFG3 is also selected if the MOST option is used.
-FDF support added for the RMF III Channel Data table
CPDG3. Information on CPD FDF filtering appears in
Section 33 Filtering The CPD Table in the ADOCRMFV
documentation member. There is a data dictionary listing
all the CPDG3 field names supported by FDF.
-FDF support added for the RMF III Enqueue Name table
ENTG3. Information on ENT FDF filtering appears in
Section 37 Filtering The ENT Table in the ADOCRMFV
documentation member. There is a data dictionary listing
all the ENTG3 field names supported by FDF.
-FDF support added for the RMF III OMVS Process Data table
OPDG3. Information on OPD FDF filtering appears in
Section 39 Filtering The OPD Table in the ADOCRMFV
documentation member. There is a data dictionary listing
all the OPDG3 field names supported by FDF.
-FDF support added for the RMF III General Information
table GEIG3. Information on GEI FDF filtering appears in
Section 38 Filtering The GEI Table in the ADOCRMFV
documentation member. There is a data dictionary listing
all the GEIG3 field names supported by FDF.
-Support for new release z/OS 2.4 RMF III fields added to
existing FDF Variable Name Tables.
*** Enhancements ***
-FDF support expanded for up to 256 byte character fields
raised from 8 bytes. But FDF IF expressions for
character field filtering may still not exceed the actual
size of the field or an error is flagged.
-Pattern matching subroutine MATCH now supports up to 256
characters in a pattern.
-FDF now translates X'00' to blank X'40' for selected
character field source data fields similar to what the
VMACRMFV SAS member does during a PDB build.
-Messages RMFV080I and RMFV088I now support character
string displays up to 105 characters. Longer character
strings are either output as a separate message or a '+'
flag is shown in the last byte of the message to indicate
the message has been truncated.
-Messages RMFV080I and RMFV088I now show tags of 'SFP' for
short floating point fields or 'LFP' for long floating
point fields instead of only showing 'FP'.
-Messages RMFV080I and RMFV088I now show the full IF
expression used if space allows.
-The SHOWBYTE subroutine now supports formatting of
storage byte values in kibibytes (kilobytes) 1024 through
yobibytes (yottabytes) 1024**8 in message RMFV088I.
However, current implementation restrictions at this time
limit values to a maximum of 9,223,372,036,854,775,807 or
about 1.22 pebibytes (petabytes).
-These documentation sections in member ADOCRMFV are all
updated for new support, enhancements, z/OS 2.4 and
corrections:
2 Terminology
3 Execution JCL
4 RMF III Table Selection Parameters
5 Input Data Selection Parameters
6 Report Control Parameters
7 Output Data Control Parameters
8 Error Handling Parameters
9 JCL and SYSIN Parameter Usage
12 Messages
13 Filtered Records
15 Program and IBM Limitations
21 Extended ASIG3/ENCG3/RCDG3/UWDG3 Record Support
22 RMF III VSAM Data Set Index Usage and Sizing
23 RMF III Options That Effect Data
24 RMF III Sysplex Master Gatherer
25 Ranges and Patterns
26 ASMRMFV and MXG PDB Data Relationships
31 Field Data Filtering (FDF)
32 Filtering The ASI Table
33 Filtering The CPD Table
34 Filtering The CSR Table
35 Filtering The DSI Table
36 Filtering The DVT Table
37 Filtering The ENT Table
38 Filtering The GEI Table
39 Filtering The OPD Table
40 Filtering The SPG Table
41 Filtering The SSH Table
42 Summary
43 Bibliography
*** Corrections ***
-All of these possible corrections apply to ASMRMFV in
MXG Versions 37.03-37.06.
-The last character of the 3 character day name in message
RMFV041I was truncated.
-Hex characters used in IF expressions for character
fields were not handled correctly.
-FDF IF expression numeric values with both a fraction and
exponent were not correctly scaled in subroutine IFNUM.
-Possible S0C7 Abend with large IF expression numeric
value and a Scale Multiplier in FDF IFNUM subroutine.
-Possible S0C7 Abend in FDF IFNUM subroutine processing
short or long floating point values.
-Possible Abend S0C4 in FDF SETIF subroutine because VNT
extension length was not added to base VNT entry length
to determine when IF entry array expansion was required.
-Incorrect formatting for a fixed binary number with a
fraction in FDF RMFV088I message.
-Incorrect digit shifting for fixed binary numbers in FDF
IF expression coded with a fractional part.
-Abend S0C4 in FDF SETIF subroutine when NOSHOWARR option
(default) was in effect and an IF array expansion
occurred.
-Possible S0C4 Abend in FDF SETIF subroutine when the
fieldname in an FDF IF expression was an alias.
-Incorrect formatting of some fractional numbers by
SHOWDEC subroutine in RMFV088I messages.
-Message RMFV088I after a FDF floating point precision
loss is detected incorrectly showed the original user IF
expression value instead of the true floating point value
actually in effect for comparisons.
-FDF subroutine IFNUM did not shift out any fractions from
the original user value in the IF expression to create an
integer when determining whether a floating point
precision loss had occurred.
-Possible incorrect byte display in FDF RMFV088I message
from SHOWBYTE subroutine for large values.
-Possible S0C1 Abend if a Fieldname entry in a FDF
Variable Name Table incorrectly has an alias equal to
itself.
*** FDF Limits ***
These are the current FDF supported limits for Change
37.204 as FDF IF expression values.
In no case may the IF expression value exceed the size of
the RMF III source field whether numeric or character.
Field Type Value range
---------- -------------------------------------------
Fixed Binary
1 byte 0-255
X'00'-X'FF'
2 byte 0-65,535
X'0000'-X'FFFF'
4 byte 0-4,294,967,295
X'00000000'-X'FFFFFFFF'
8 byte 0-9,223,372,036,854,775,807 *
X'0000000000000000'-X'7FFFFFFFFFFFFFFF' *
* the limit for a 8 byte binary number is imposed by the
need for ASMRMFV to convert the input number to binary.
A grande 64-bit register only holds X'7FFFFFFFFFFFFFFF'
as a high order sign bit is required.
Floating Point **
4 byte 0-9,223,372,036,854,775,807
8 byte 0-9,223,372,036,854,775,807
** the limit for a floating point number is imposed by
the need for ASMRMFV to convert the input number to
binary before conversion to floating point. A grande
64-bit register only holds X'7FFFFFFFFFFFFFFF' as a high
order sign bit is required.
Bit String
1 byte 0-255
X'00'-X'FF' without don't cares
1 byte .......0-1111111. with don't cares
Percentage 0.0-100.0
Time of Day 01JAN2000:00:00:00-17SEP2042:23:53:46 ***
*** The of day limit is imposed by the 64 bit TOD clock
which wraps to all binary ones in September 2042. The
addition of leap seconds may affect this value.
Time ****
4 byte 0-4,294,967,295
X'00000000'-X'FFFFFFFF'
8 byte 0-9,223,372,036,854,775,807
X'0000000000000000'-X'7FFFFFFFFFFFFFFF'
**** Time units depend on the default time unit for the
RMF III field or the explicit time unit coded by the
user. They can range from microseconds to days.
TOD date only 01JAN2000-17SEP2042
TOD Time only 00:00:00-23:59:59
Change 37.203 Unused Change Number.
Sep 11, 2019
Change 37.202 Support for truncated SMF 61 catalog record from z/OS 2.3
VMAC6156 causing INPUT STATEMENT EXCEEDED error.
Sep 9, 2019
Thanks to Mike Jacques, BB&T, USA.
Change 37.201 The MGBYTES format is extended to decode storage units in
FORMATS zettabytes and yottabytes.
Sep 27, 2019
Change 37.200 Optional CICSTRAN DBCTL segment variable STATCTM1 was
IMACICDB 10 times too large (4 usec should be 0.4 usec) due to
Sep 9, 2019 incorrect STCK informat, corrected to TU4.
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.199 -Variables QWACPCTT/QLACRLNU are used to get the correct
VMACDB2 count of THREADS when ROLLUPS (DB2PARTY=R) are in use:
ASUMDB2A DB2ACCT variable QWACPCTT is summed into THREADS in
ASUMDB2B ASUMDB2A unless QLACRLNU is GT 0 and used instead.
ASUMDB2G DB2ACCTP variable QPACRLNU is summed into PACKCNT in
ASUMDB2P ASUMDB2P
ASUMDB2R DB2ACCTB variable QWACPCTT is summed into THREADS in
Sep 7, 2019 ASUMDB2B unless QLACRLNU is GT 0 and used instead.
Sep 16, 2019 DB2ACCTG variable QLACPCTT is summed into THREADS in
ASUMDB2G unless QLACRLNU is GT 0 and used instead.
DB2ACCTR variable QLACRLNU is summed into THREADS
-Previously THREADS in DB2ACCT and COUNT in DB2ACCTP
counted each record; so counts will be larger and
correct in the ASUMs and in ANALDB2R which uses them,
unless the count is one, which does happen.
-This change means that the average values reported in
ANALDB2R will be more accurate but it still precludes
detail problem analysis from rolled up records since
the best you can get is an average value.
Variable QWACPCTT is now kept in DB2ACCTB/DB2ACCTG/
DB2ACCTR so it can be used in those ASUMs.
Change 37.198 BETA 93 Subtypes 12,17,30,31,55 were not input because
VMACBETA they weren't added to the IF SUBTYPE IN list of subtypes,
Sep 11, 2019 and they were not sorted to the PDB data library.
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 37.197 BETA 97 Subtype 51 Dataset BETA9751D did not input the
VMACBE97 "New Area" fields for BETA9751REC='U', UPDATE records.
Sep 11, 2019 An undocumented test to skip U records was removed.
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 37.196 Member IMACTIME and CHANGESS had references to "OKJOB"
IMACTIME that should be OKFLAG for consistency; no impact as the
CHANGESS member is optional and "OKJOB" is in comments.
Sep 5, 2019
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.195 The PDB.PRINT dataset ACCOUNT variables were populated
BUILD005 only in the first observation for each job, and TYPETASK
Sep 5, 2019 had the SUBSYS6 value (PSF/VPS) instead of TYPETASK (JOB)
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.194 Formats added for TYPE42DS variables S42DSENT/S42DSCMT to
FORMATS decode the Encryption Type and Compression TYPEs.
VMAC42 ET=AES-256,CT=None/Generic/Tailored/zEDC.
Sep 3, 2019
Thanks to Luis Mendoza, BKFS, USA.
Change 37.193 Format $MG110EX for dataset CICSEXCE variable EXCMNTYP
FORMATS did not map value '0004'X to 04:POLICY THRESHOLD instead
Sep 3, 2019 printing a confusing '00'X value.
Thanks to Harald Seifert, Huk-Coburg, GERMANY.
Change 37.192 TLMS dataset TYPETLMS from the "B" record is updated and
EXTYTLMC two new TLMS datasets TYPETLMC/TYPETLMD are now created
EXTYTLMD from the "C" and "D" TLMS records:
IMACTLMS DDDDDD DATASET DESCRIPTION
VMACTLMS TYTLMC TYPETLMC MASTER FILE CONTROL RECORD
VMXGINIT TYTLMD TYPETLMD VOLUME MASTER FILE MULTI DATASET
Sep 25, 2019
Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
Change 37.191 RMM/EDGR processing in VMXGDSN had zero obs for TAPES and
VMXGDSN TAPEDSNS MXG 37.03-MXG 37.06; the SORT input dataset was
Sep 2, 2019 incorrectly changed to EDGRDEXT instead of EDGRXEXT.
Thanks to Wayne Bell, UNIGROUP, USA.
Thanks to John Fulton, UNIGROUUP,USA
====== CHANGES THRU 37.190 ARE IN MXG 37.06 DATED AUG 30, 2019 =========
Change 37.190 New macro %MXGFINFO creates dataset EXTFILES with these
MXGFINFO variables for every external filename (INFILE)
Aug 30, 2019 -z/OS: FILEREF DSNAME DEVICE and CREATEDATE
-ASCII FILEREF XPATH and CREATEDATE.
CREATEDATE will be missing if the ftp access method is
used.
Change 37.189 Spurious INVALID VALUE FOR INPUT FUNCTION in first 37.06
DODSCRDT had no impact, except for lots of lines on the log. It
Aug 30, 2019 occurs when the INFILE is on TAPE, because the DSCB that
SAS returns is the VOL2HDR instead of the date-containing
DSCB, so the CREATEDATE variable is always missing for
INFILE on Tape.
Thanks to Jim Horne, Lowe's Companies, USA.
Change 37.188 Example 2 had a Missing "END;" statement
IMACUOW
Aug 29, 2019
Change 37.187 Labels for Tennant TRG_SUCP,TRG_SUIFA,TRG_SUSP variables
VMAC7072 are changed from *MSU* to *HDW MSU* because those values
Aug 29, 2019 are NOT the Software MSU (4HR AV) we normally use when
discussing MSU. This link shows IBM uses the "Hardware"
SU_SEC value to convert those service units to engine
counts:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/
com.ibm.zos.v2r3.izsc100/cserbb200195.htm
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.186 Support for IBM Tivoli Advanced Allocation Management SMF
EXTYAAM1 record; this product replaces the old X37 product.
EXTYAAM3 DDDDDD DATASET DESCRIPTION
FORMATS TYAAM1 TYPEAAM1 SUBSYSTEM ACTIVITY
IMACAAM TYAAM3 TYPEAAM3 PROCESSING ACTIVITY
TYPEAAM Subtype 3 have been data tested; IBM provided additional
TYPSAAM bit values for DNV/DST/ADP and reported SPCF incorrectly
VMACAAM sets '80'x bit causing 'C0'x for TRACKS, to be corrected,
VMXGINIT but MXG's format maps both 'C0'x and '40'x to TRACKS.
Aug 28, 2019 Subtype 3 event records have only SMFTIME & JOB (AAMJBN),
Sep 24, 2019 no READTIME nor JCTJOBID/JESNR, so they can not be easily
interleaved/merged with other JOB-related records.
Thanks to Cha Kihun, Navy Federal, USA.
Thanks to Richard Champouillon, Navy Federal,USA
Change 37.185 Warning: APPARENT SYMBOLIC REFERENCE LDB and LDB@ACG has
READDB2 no impact on the results, DB2ACCTG is correctly sent to
Aug 23, 2019 your LDB2ACG= argument with correct message text.
Thanks to Douglas C. Walter, CITIGROUP,USA.
====== CHANGES THRU 37.184 ARE IN MXG 37.06 DATED AUG 22, 2019 =========
Change 37.184 Delete of temp dataset SRTIRC was relocated so it is
VMXGCICI always deleted (to free WORK space).
Aug 14, 2019
Change 37.183 Support for SMF 82 subtypes 30 and 40-48 new datasets
FORMATS DDDDDD DATASET DESCRIPTION
EXTY82AU TY8230 TYPE8230 KDS ARCHIVE/CRYPTOPERIOD
EXTY8248 TY8240 TYPE8240 CCA SYMMETRIC KEY LIFECYCLE
IMAC82 TY8241 TYPE8241 CCA ASYMMETRIC KEY LIFECYCLE
VMAC82 TY8242 TYPE8242 PKCS#11 KEY LIFECYCLE EVENT
VMXGINIT TY8243 TYPE8243 RCS CONFIGURATION CHANGE (not decoded)
Aug 21, 2019 TY8244 TYPE8244 CKDS KEY USAGE
Aug 27, 2019 TY8245 TYPE8245 PKDS KEY USAGE
Oct 30, 2019 TY8246 TYPE8246 PKCS#11 KEY USAGE
TY8247 TYPE8247 PKCS#11 NOKEY USAGE
TY8248 TYPE8248 WARN MODE
Subtype 43 is not decoded, pending test data records.
Subtypes 40,41,44,45,48 have been tested.
Subtypes 42,46,47 are decoded but not tested.
Thanks to Alexander Bitter, Worldpay, USA.
Thanks to Lethika Panicker, Worldpay, USA.
Thanks to Ron Rust, Worldpay, USA.
Change 37.182 Variable SMF74SCMR was incorrectly spelled SMF74SKCR.
VMAC74
Aug 14, 2019
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.181 Support for Hitachi MAR Mainframe Analytics Recorder 9.1
EXMAR07 creates new MARST07 PARM Section Dataset.
IMACMAR
VMACMAR
VMXGINIT
Aug 13, 2019
Change 37.180 MXG DB2 Formats $MGTMDOB, $MGTMDRM, $MGTMDRE, MGTMDRC are
FORMATS updated with new values.
Aug 13, 2019
Thanks to Randy Hewitt, DXC, USA.
Change 37.179 TYPE72GO variables METGOAL and PCTMETGO were wrong, now:
VMAC7072 IF TRANS GT 0 THEN DO M=1 TO 6;
Aug 9, 2019 METGOAL=SUM(METGOAL,RTSTRN(M));
PCTMETGO=100*METGOAL/TRANS;
END;
ELSE PCTMETGO=.;
Thanks to James Peddycord, Northern Trust, USA.
Thanks to Karl S. Huf, Northern Trust, USA.
Thanks to Arati Khodaskar, IBM Global Services, USA.
Change 37.178 -MXG 37.05 only, possible S0C4 Abend in ASMRMFV PROCSSH
ASMRMFV subroutine when comparing current RMF Version to a z/OS
Aug 9, 2019 2.3 Version number, after Change 37.140.
Aug 20, 2019 -That PROCSSH code was redundant with similar code in the
FINDPOL subroutine that is RMF Version independent and
has been removed to eliminate the S0C4 possibility.
-MXG 37.03-37.05, ONLY if you use FDF IF expressions.
ABEND S0C7 when a hex value is coded for a numeric field
in an FDF IF expression. For example: IF=(ASIDP EQ X'FF')
-Incorrect handling of exponents when coded for a numeric
field in an FDF IF expression causing an incorrect
compare value to be calculated.
For example: IF=(ASI1MBFF GT 1E2)
-Invalid hex value can be shown in RMFV080I and RMFV088I
messages.
Thanks to Kurt Gramling, GTS Tech-Support: CRM, USA
Change 37.177 Variables R745BYTR/BYTW/RTIR/RTIW were never populated by
VMAC74 IBM, as they were replaced by R7451CT1-R7451CT4, but they
Aug 8, 2019 are now populated by those replacement values rather than
being missing values. See Change 23.314.
Thanks to Otto Burgess, OPM, USA.
Change 37.176 Support for IMS LOG '02'x record creates IMS02 dataset or
EXIMS02 prints a message if a multi-segment command record is
VMACIMS found to send your IMSLOG so it can be supported.
VMXGINIT
Aug 7, 2019
Change 37.175 New metric, SIISPCT='STORE INTO*INSTRUCTION*STREAM*PCT'
ANALSIIS is added to TYPE1131 and ASUM1131 datasets, to identify
VMAC113 potential timeframes based on percent of certain I writes
Aug 6, 2019 vs D Writes sourced, to identify when it happens, but NOT
who is causing it.
-ANALSIIS identifies intervals with SIISPCT GT 10 percent
and identifies what programs were running in descending
CPUTM or CPUZIPTM depending on CPU type during that high
SIISPCT interval.
Thanks to Kathy Walsh, IBM zSystems, USA.
Thanks to John Burg, IBM zSystems, USA.
Change 37.174 Non-fatal Divide By Zero when QBSTVPL=0 was corrected.
VMACDB2
Aug 5, 2019
Ron van der Zande, KLM Information Systems, THE NETHERLANDS.
Change 37.173 Support for TPMX $JCL_JJR, variable JCLJJR in TYPETPMX.
VMACTPMX Only 9 lines of "new field" messages are now printed.
Aug 4, 2019
Thanks to Jack Hyde, Optum Technology, USA.
Change 37.172 Dataset Encryption Variable SMF14DEF='Y' identifies data
VMAC1415 sets that are encrypted, and SMF14DET='0100'x to indicate
Aug 4, 2019 AES ('01'x) and 256 Bits ('00'x). INPUT was corrected.
Change 37.171 Variables R723GGTI, R723GGTN, R723GGKY and R723MFLG are
VMAC7072 kept in dataset TYPE72GO, and variable R723GGKY is now
Aug 4, 2019 INPUT correctly as $EBCDIC64 instead of 32.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.170 Variable DESTNATN is added to PDB.TYPE6 dataset.
BUILD005
BUIL3005
Aug 2, 2019
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.169 Variable INITTIME in dataset TYPE30_6 is created using
VMAC30 INITTIME=SMFTIME-ACTIVETM;
Aug 2, 2019 which can then be used to count unique step executions.
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.168 Four CICS "identity" variables weren't kept in CICSTRAN
UTILEXCL when UTILEXCL was used: APPLID JOB SMFPSSPN SMFPSRVR, and
VMAC110 these new "identity" variables MVSLEVEL LOCLINFO MCTSSCRL
Aug 2, 2019 are added to CICSTRAN whether UTILEXCL is used or not.
All could be deleted with
%LET MACKEEP=
MACRO _KCICTRN
DROP=APPLID JOB SMFPSSPN SMFPSRVR
MVSLEVEL LOCLINFO MCTSSCRL
%
:
in your SYSIN.
Thanks to Scott Barry, SBBWorks, INC., USA.
Change 37.167 z/OS 2/4 updates for RMF MONITOR III:
VMACRMFV -VMACRMFV in MXG 37.05 (only) fails with z/OS 4.2 CSR data
Aug 2, 2019 and was corrected in 37.06 by this change (which changed
only line 6871, from /48 to /CSRENTLE).
-New RUCSA variables added to ZRBCSR dataset:
CSRRUCSA ='RUCSA*AMOUNT'
CSRERUCSA='ERUCSA*AMOUNT'
-New RUCSA variables added to ZRBGEI dataset:
GEIRUCSASZ='IPL SIZE*RU CSA*BELOW 16MB'
GEIERUCSAZ='IPL SIZE*RU CSA*ABOVE 16MB'
GEIRUCSAMX='MAX RUCSA*BELOW 16MB'
GEIERUCSAX='MAX RUCSA*ABOVE 16MB'
GEIRUCSASP='ALLOCATED RUCSA*BELOW 16MB'
GEIERUCSAP='ALLOCATED RUCSA*ABOVE 16MB'
GEIRUCSAAV='ACCUM RUCSA*BELOW 16MB'
GEIERUCSAV='ACCUM RUCSA*ABOVE 16MB'
GEIRUCSARE='UNALLOCATED*RUCSA BELOW 16MB'
GEIRUCSAAS='ACCUM RUCSA*BELOW 16MB*BY SYSTEM'
GEIERUCSAS='ACCUM RUCSA*ABOVE 16MB*BY SYSTEM'
GEIBATRUCSA='ACCUM RUCSA*BELOW 16MB*BY BATCH'
GEIBATERUCSA='ACCUM RUCSA*ABOVE 16MB*BY BATCH'
GEIASCRUCSA='ACCUM RUCSA*BELOW 16MB*BY ASCH'
GEIASCERUCSA='ACCUM RUCSA*ABOVE 16MB*BY ASCH'
GEIOMVRUCSA='ACCUM RUCSA*BELOW 16MB*BY OMVS'
GEIOMVERUCSA='ACCUM RUCSA*ABOVE 16MB*BY OMVS'
-New variables with time to LPAR/Group Capping in ZRBCPU:
CPC_TIME_TO_CAPL='TIME TO*LPAR*CAPPING'
CPC_TIME_TO_CAPG='TIME TO*GROUP*CAPPING'
Thanks to Kurt Gramling, TSYS, USA.
Change 37.166 z/OS 2/4 updates:
VMAC74 -Type 74 Subtype 2 additions to dataset TYPE74PA, virtual
VMAC78 storage for the optional Private Address Space data:
Aug 2, 2019 R742PUTM1 ='PATH1*TIME USED*AT PCT UTIL'
R742PUTMS1='PATH1*SQRD TIME USED*AT PCT UTIL'
R742PUCN1 ='PATH1*COUNT USED*AT PCT UTIL'
R742PUSCN1='PATH1*SIGNAL COUNT SENT'
R742PUPCT1='PATH1*PCT UTIL'
R742PUTM2 ='PATH2*TIME USED*AT PCT UTIL'
R742PUTMS2='PATH2*SQRD TIME USED*AT PCT UTIL'
R742PUCN2 ='PATH2*COUNT USED*AT PCT UTIL'
R742PUSCN2='PATH2*SIGNAL COUNT SENT'
R742PUPCT2='PATH2*PCT UTIL'
R742PUTM3 ='PATH3*TIME USED*AT PCT UTIL'
R742PUTMS3='PATH3*SQRD TIME USED*AT PCT UTIL'
R742PUCN3 ='PATH3*COUNT USED*AT PCT UTIL'
R742PUSCN3='PATH3*SIGNAL COUNT SENT'
R742PUPCT3='PATH3*PCT UTIL'
R742PUTM4 ='PATH4*TIME USED*AT PCT UTIL'
R742PUTMS4='PATH4*SQRD TIME USED*AT PCT UTIL'
R742PUCN4 ='PATH4*COUNT USED*AT PCT UTIL'
R742PUSCN4='PATH4*SIGNAL COUNT SENT'
R742PUPCT4='PATH4*PCT UTIL'
R742PNIBTM='PATH TOTAL TIME*NO INBOUND*BUFFER IMPACT'
R742PNIBTS='PATH SQUARED TIME*NO INBOUND*BUFFER IMPACT'
R742PNIBCN='PATH COUNT*NO INBOUND BUFFER'
-Type 78 subtype 2 dataset TYPE78VS Virtual Storage new:
R782RUCA ='RUCSA ADDRESS*BELOW 16MB'
R782RUCS ='RUCSA SIZE*BELOW 16MB'
R782ERUCA='RUCSA ADDRESS*ABOVE 16MB'
R782ERUCS='RUCSA SIZE*ABOVE 16MB'
Thanks to Kurt Gramling, TSYS, USA.
Change 37.165 Dataset TYPE8201 (Initialization) variables SMF82ITE/CKD/
VMAC82 IML/USR/PKD were misaligned by a one byte reserved field.
Jul 29, 2019
Thanks to Matthew T Chappel,CQueensland Dept Transport, AUSTRALIA
Change 37.164 Variable TTTTLSSP in dataset TYP11902 is decoded by new
FORMATS $MG119PT format:.
VMAC119 VALUE $MG119PT /*TTTTLSPP*/
Jul 28, 2019 '0200'X='0200X:SSL V2'
'0300'X='0300X:SSL V3'
'0301'X='0301X:TLS 1.0'
'0302'X='0302X:TLS 1.1'
'0303'X='0303X:TLS 1.2'
Variable TTTTLSNC documents '4X'x='USE TTTTLSNC4 instead'
but values of '0A'x '35'x and '6B'x are found in data
but are not documented.
Thanks to Joe Faska, DTCC, USA.
Change 37.163 Labels for these variables were made consistent
VMAC71
Aug 2, 2019 SMF71L4A='AVG*1MB*PAGEABLE*FRAMES*IN DREF'
SMF71L4M='MIN*1MB*PAGEABLE*FRAMES*IN DREF'
SMF71L4X='MAX*1MB*PAGEABLE*FRAMES*IN DREF'
SMF71L5A='AVG*1MB*AVAILABLE*FRAMES*IN DREF'
SMF71L5M='MIN*1MB*AVAILABLE*FRAMES*IN DREF'
SMF71L5X='MAX*1MB*AVAILABLE*FRAMES*IN DREF'
SMF71L6A='AVG*1MB*PAGEABLE*FRAMES*USED*IN DREF'
SMF71L6M='MIN*1MB*PAGEABLE*FRAMES*USED*IN DREF'
SMF71L6X='MAX*1MB*PAGEABLE*FRAMES*USED*IN DREF'
SMF71L8A='AVG 1MB*PAGEABLE*FRAMES*IN CSTORE'
SMF71L8M='MIN 1MB*PAGEABLE*FRAMES*IN CSTORE'
SMF71L8X='MAX 1MB*PAGEABLE*FRAMES*IN CSTORE'
SMF71L9A='AVG 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71L9M='MIN 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71L9X='MAX 1MB*AVAILABLE*FRAMES*IN CSTORE'
SMF71PLA='AVG*1MB*PAGEABLE*FRAMES*USED*IN CSTORE'
SMF71PLM='MIN*1MB*PAGEABLE*FRAMES*USED*IN CSTORE'
SMF71PLX='MAX*1MB*PAGEABLE*FRAMES*USED*IN CSTORE'
Aug 2, 2019
Thanks to Joe Faska, DTCC, USA.
Change 37.162 ANALSIZE failed due to a missing semicolon in VMXGSIZE.
VMXGSIZE
Jul 25, 2019
Thanks to Richard Haynes, BCBSKS, USA.
Change 37.161 -New z/OS-Only SAS Date Variable CREATEDATE can be created
DODSCRDT for INFILE names of SAS CONTROLT DCOLLECT RMFBSAM TMC
VMACCTLT EDGHSKP IMSLOG OPCLOG, and is that variable is available
VMACDCOL the IHDRxxxx exit for your selection criteria, and/or it
VMACEDGR can be kept using the _Kdddddd dataset KEEP macro.
IHDRTMS5 -You must enable its creation with %LET DSCRDT=YES; in the
VMACIMS SYSIN or %DSCRDT can be added for any z/OS INFILE by
VMACSMF adding JFCB=MXGJFCB DSCB=MXGDSCB to the INFILE statement
VMACRMFV and inserting %DSCRDT after the first INPUT statement:
VMACTMS5 DATA MYSTUFF;
VMXGINIT INFILE MYFILE JFCB=MXGJFCB DSCB=MXGDSCB;
Aug 7, 2019 INPUT ;
Aug 11, 2019 %DSCRDT(JFCB=MXGJFCB);
Nov 26, 2019 SAS automatically prints the Create Date on the SAS log
in its "INFILE IS " message, but DSCRDT can print its
own log message if you use %LET MXGEXIMSG=YES;
SEE CHANGE 37.249 FOR REVISION.
Thanks to Linda S. Berkley, DISA, USA
Change 37.160 Unused Change Number.
Change 37.159 BETA 93 610 Subtype 40 and 49 misaligned, INVALID DATA
VMACBETA messages for variables BETASTME and BETAETME in 49 and
Jul 18, 2019 BETAALT in subtype 40.
Change 37.158 BLDSMPDB adds SPIN: SPUN: to WEEKDROP MNTHDROP if they
BLDSMPDB are not present. New parameters added WEEKBASE MNTHBASE
Jul 15, 2019 that both default to blanks which will then become
yesterday and used to determine which datasets will be
included in the weekly and monthly PDBs. This ensures
that your most current PDB is used to build the
weekly/monthly datasets. So if you decided to add
something on the day before it will be propagated into
the weekly/monthly jobs. The fact that it may not exist
in all of the input PDBs is not a problem. These should
only be used if you wish to force a specific PDB to be
the basis for the weekly/monthly PDBs and if it does not
exist via either a LIBNAME or a DD the job will fail.
Change 37.157 A new macro that will drill down through MSU consumption
ANALMSUS from the TYPE89 records and the type 30 interval data. It
Jul 13, 2019 can produce bar charts, tabular reports, and EXCEL
Aug 27, 2019 spreadsheets as you choose.
Change 37.156 Variables ABEND CONDCODE added to PDB.SMFINTRV and the
VMAC30 TYPE30_V datasets. The values will only be populated from
Jul 13, 2019 the subtype 3 records.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 37.155 Support for CICS Optional field USER/AGENCY.
IMACAAAA
IMACICXB
UTILEXCL
VMAC110
Thanks to Mark Hiltbruner, State of South Dakota, USA.
====== CHANGES THRU 37.154 ARE IN MXG 37.05 DATED Jul 8, 2019 =========
Change 37.154 SMF 110 Subtype 1 MNSEGCL=5 INPUT EXCEEDED ERROR due to
VMAC110 8 byte reserved field inserted in DPL ENTRY segment. Skip
Jul 8, 2019 the records (causing zero obs in CICSRDPL dataset) with:
%LET MAC110H= %QUOTE(IF MNSEGCL=5 THEN DELETE; ) ;
This was added in CICS/TS 5.5 to these (seldom used) CICS
Resource segment.
Thanks to Jack Hyde, Optum Technology, USA.
====== CHANGES THRU 37.153 ARE IN MXG 37.05 DATED Jul 6, 2019 =========
Change 37.153 SMF 120 Subtype 3 INPUT STATEMENT EXCEEDED ERROR due to
VMAC120 incorrect MXG logic that has accidentally worked: there
Jul 6, 2019 were only three ABENDS since Dec 2018. One circumvention
which usually skips over the failing record was tried:
OPTIONS STOPOVER MISSOVER % but because the code error
was a loop on the same INPUT location, MXG created 500
million observations in TYP120SR filling fifteen WORK
volumes before dying with a B37 no more extents error.
The alternative circumvention was to skip that subtype:
%LET MACFILE=%QUOTE(IF ID=120 AND SUBTYPE=3;);
until this update corrected the MXG code error.
I think not related, but site had WebSphere 8.5.5 FP12.
====== CHANGES THRU 37.152 ARE IN MXG 37.05 DATED Jul 5, 2019 =========
Change 37.152 MXGSTEP populates new variable MXGSTEP='Y' in SMF 30's to
MXGSTEP identify job steps that execute MXG programs, populating
Jul 5, 2019 TYPE30_V and TYPE30_4 with (TYPE30) and in PDB.SMFINTRV
and PDB.STEPS with (BUILDPDB), or any MXG program that
processes SMF 30 records, if PROGRAM='SAS' and DDNAMES
SOURCLIB and LIBRARY are in this STEP, as both are
required for MXG Execution.
Thanks to Deepa Rajendran, DXC, SINGAPORE.
Change 37.151 ASUMMIPS now uses the $MGRMIPS format built from the IBM
ASUMMIPS LSPRITR table to lookup CPCFNAME (eg 3906-716) for the
VMXGINIT MIPSFACT (eg 8.34), the MIPS per MSU. Previously you
Jul 4, 2019 had to provide your own MIPSFACT.
Jul 5, 2019
Thanks to Randy Hewitt, DXC, USA.
Change 37.150 Support for DATACOM log file.
EXDCOM
IMACDCOM
TYPEDCOM
TYPSDCOM
VMACDCOM
VMXGINIT
Jul 2, 2019
Thanks to Linda Berkley, DISA, USA.
Change 37.149 If you add ID to USERADD it must be the last entry
UTILBLDP in the list. If you happened to make it first the
Jul 2, 2019 list will be adjusted.
Change 37.148 BLDSMPDB adds SPIN: SPUN: to WEEKDROP MNTHDROP if they
BLDSMPDB are not present. New parameters added WEEKBASE MNTHBASE
Jun 23, 2019 that both default to &WEEKDATE (yesterday) are used to
decide which datasets can be included in the weekly and
monthly PDBs. This ensures that your most current PDB is
used to build the weekly/monthly datasets. So if you
decided to add something on the day before it will be
propagated into the weekly/monthly jobs. The fact that it
may not exist in all of the input PDBs is not a problem.
Change 37.147 CICS Statistics datasets CICMPR and CICSJN were not in
VMAC110 the _N110_, _S110, and _S110ST optional tailoring macros.
Jul 1, 2019
Change 37.146 Macro variable &MACSPIN added to IMACSPIN for "instream"
IMACSPIN tailoring of SPINCNT.
VMXGINIT
Jul 1, 2019
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 37.145 The "PROC PRINT" output with Label and Name column heads
VMXGPRA1 VMXGPRA1 and VMXGPRAL utilities now protect if you have
VMXGPRAL changed the OBS option. Their temp dataset has one obs
Jun 28, 2019 per variable, but if your OBS was too small, some heads
were wrong and missing parens. Now the OBS value is held.
the print is accomplished and your original OBS restored.
Thanks to Scott Wiig, US Bank, USA.
Change 37.144 FLASH: MISSING PERIODS 2/3 TYPE72GO if MXG 36.07 or prior
VMAC7072 is used and IBM RMF APARs for SCM and Crypto are applied.
Jul 1, 2019
There is no error with MXG 36.08 (Sept 2018) or later.
One z/OS 2.3 site reported these were applied:
UA98434 APAR OA56461
UA98529 APAR OA56672
UA98759 APAR OA56826
UA98999 APAR OA56860
and one z/os 2.2 site reported this was applied
UA98433 APAR OA56747
but there may be other maintenance involved.
You can examine your SMF 72 Subtype 3 period data with
PROC FREQ DATA=PDB.TYPE72GO;
TABLES SYSTEM*PERIOD;
TITLE TABLE OF PERIOD VALUES IN SMF 72 SUBTYPE 3;
to see if you are missing values for your periods.
These missing periods will cause the system Capture
Ratio to decrease significantly, and the workload that
normally have period data will have reduced CPU time in
TYPE72GO and RMFINTRV datasets, and reports from them.
Change 37.143 Expanded Storage doesn't exist in all z/OS systems so the
IMAC71 56 ESTORE variables in TYPE71 can be dropped by removing
Jun 28, 2019 the comment block when you EDIT the IMAC71 tailoring
member into your "USERID.SOURCLIB" tailoring library.
You do need to examine any reporting programs that use
the TYPE71 dataset to see if those variables are used.
Thanks to Arnold Kim, UPS, USA.
Change 37.142 New READRATE %MACRO will measure the Read Rate (MiB/Sec)
READRATE of MXG processing SMF data records, printing an interval
VMACSMF trace on the log, a PLOT of READRATE vs RUNTIME, and PROC
VMXGINIT TABULATE report with 1 sec default interval. Additional
options are in the comments in READRATE. Syntax:
Jul 1, 2019 %READRATE(READRATE=1,RESULTS=BOTH);
%INCLUDE SOURCLIB(TYPE30); RUN;
&READRATEREPORT;
Change 37.141 Format MG119CD 17:UCP corrected to 17:UDP.
FORMATS
Jun 26, 2019
Thanks to Jenny Chen, DXC Technology, AUSTRALIA.
Change 37.140 -More RMF Monitor III tables are supported by FDF (Field
ADOCRMFV Data Filter) in ASMRMFV: DSI, SPG, SSH
ASMRMFV -New CDF (Character Data Filters) added for RMF III VSAM
Jun 26, 2019 data set level filtering:
CPCNAME= (aliases CPC=, CECNAME=, CEC=)
LPARNAME= (alias LPAR=)
-LPAR names and CPC names are validated for correct syntax
when these filters are used.
-FDF now supports character patterns for character fields.
Only Equal (= EQ) and Not Equal (^= =^ NE NEQ NOT NOTEQ
NOT=) operators may be used in an IF expression with a
character pattern. A pattern either matches or it does
not. Other FDF operators are flagged as an error.
-New DSIAND/DSIOR parameters which have the same function
as the prior SYSAND/SYSOR parameters which are now
respective aliases.
-RMFV014I message now shows counts for RMF III data sets
bypassed by CPCNAME= and/or LPARNAME= CDF keywords.
-Duplicate counts are no longer shown in RMFV014I message
if DUPDSN option is in effect (no duplicate checking).
-Space analysis messages RMFV030I, RMFV031I are no longer
issued for filtered RMF III VSAM data sets.
-MAXDSNS= added as a further alias of MAXDSNAMES=.
-Always force upper case for these CDF keyword values
because lower case letters are always invalid and
would be flagged as an error otherwise:
CPCNAME= SYSPLEX= LPARNAME= SYSTEM=
ASISUBSYS= ASIJOBCLASS= ASIJOBNAME= ASIJESID=
CSRJOBNAME= CSRJESID= DVTDEVNUM=
OPDJOBNAME= OPDPROCNAME= OPDUSERNAME=
-Support validation for all characters allowed for CDF
Workload Names, Service Classes, Report Classes, and
Resource Groups
-Field descriptions in data dictionary entries in ADOCRMFV
for FDF supported RMF III table expanded for better
clarity.
-TRUENAME Fieldnames in FDF data dictionary entries in
ADOCRMFV documentation now show all possible aliases.
-GMT offset value in Summary First Sample Begin Date/Time
selected message RMFV013I could be incorrect.
-RMFV013I selection messages were incorrectly displayed in
Summary report when all RMF III data sets were filtered.
-CDF keywords and aliases may now be used as Fieldnames
in FDF IF expressions (minus the = suffix).
-Message RMFV014I now includes a counter for FDF filters.
-Negative values are now supported in FDF, but only for
GMT offset fields xxxSTDIF and xxxGMTOFF where xxx is a 3
character RMF table id.
-For example this is a valid IF expression:
IF=(ASISTDIF EQ -5H)
-New second RMFV103I message is added to Detail and
Summary reports to display Sample Set filter reason
counts.
-New options AUTOSEL (alias AUTO) and NOAUTOSEL (alias
NOAUTO) added.
-AUTOSEL is the default and will result in the RMF III
table being automatically selected with any CDF or FDF
filter if the table was not already selected. This is a
convenience feature.
-New message RMFV082I appears when a table is auto
selected. In addition in message RMFV105I Y* will
appear in the SELECT column for auto selected tables.
-NOAUTOSEL provides the prior ASMRMFV behavior and the
unselected table condition generates an error. However,
it may be helpful if JCL with CDF and/or FDF filters is
routinely reused to avoid the PDB build overhead of
automatically selecting a table that is no longer wanted.
-For tables not referenced by CDF and/or FDF it is still
necessary to select the RMF III tables of interest.
-The SPGVOLSER= CDF filter could have incorrect results.
-Following documentation sections in ADOCRMFV are added or
updated:
Section Description
0 Contents
2 Terminology
3 Execution JCL
4 RMF III Table Selection Parameters
5 Input Data Selection Parameters
6 Report Control Parameters
8 Error Handling Parameters
9 JCL and SYSIN Parameter Usage
12 Messages
13 Filtered Records
16 Return Codes
20 FREE=CLOSE For VSAM Data Sets
21 Extended ASI/ENC/RCD/UWD Record Support
25 Ranges and Patterns
26 ASMRMFV and MXG PDB Data Relationships
31 Field Data Filtering (FDF)
32 Filtering The ASI Table
33 Filtering The CSR Table
34 Filtering The DSI Table
35 Filtering The DVT Table
36 Filtering The ENT Table (Future)
37 Filtering The GEI Table (Future)
38 Filtering The OPD Table (Future)
39 Filtering The SPG Table
40 Filtering The SSH Table
41 Summary
Change 37.139 Reserved Change.
Change 37.138 The label for variable QW0199TRS in DB2 102 IFCID 199 was
VMAC102 corrected to 'END TIME*OF*INTERVAL', which is strange as
Jun 24, 2019 the SMFTIME was available for the end time.
Thanks to Xing Su, DXC Technology, AUSTRALIA.
Thanks to Peter J. Gray, DXC Technology, AUSTRALIA.
Change 37.137 -Variables INDXUSEP and POLYUSEP percentages are created
VMACRMFV in dataset ZRBDISH to track index usage. The 1110 is the
Jun 21, 2019 maximum number of sample indexes in a 32K DSI table and
50 is the maximum number of policy indexes.
-Strange RMF III intervals can be created if the values
in SMFPRMxx don't match ERBRMFxx options. A site had
SMF INTVAL(10) SYNCVAL(59) with RMF MINTIME(300) SYNC(0)
for RMF III, which created a 4 minute interval (:55 -:59)
when the RMF III MINTIME expired, a one minute (:59-:00)
interval when the SMF Interval Expired, and a five minute
(:00-:05) when the RMF Interval Expired.
Change 37.136 ANALMSUS is a powerful set of reports of SOFTWARE MSUs
ANALMSUS from ASUMCELP, SMFINTRV, TYPE72GO, TYPE89 records, that
Jun 21, 2019 has many different bar charts, tabular reports, and EXCEL
spreadsheets as you choose, with report examples in the
comments, and with numerous report examples available
online at http://www.mxg.com/downloads/analmsus/
ANALMSUS.PDF
ASUMCELPMSU.XLSX
JOBSMSU.XLSX
MSU89.XLSX
REPORTCLASS.XLSX
SERVICECLASS.XLSX
TYPETASK.XLSX
(Don't be confused with archaic ASUMMSUS member.)
Change 37.135 Type 42 Subtype 5 Invalid LENSR values were individually
VMAC42 detected and LENSR=160 set, but now there are a total of
Jun 21, 2019 22 different values for records, because IBM populates
Jun 24, 2019 the total length and not the 160 first segment length.
But with 22 tests, I'm now forcing LENSR=160 always, as
that will ONLY fail if IBM actually changes that first
segment size in the future, you won't be ABENDing on
each new LENSR value. These are the known invalids:
IF LENSR IN (232,240,320,376,400,480,448,304,520,560,592,
720,640,1040,1120,1200,960,1360,1280,1440,880,800)
THEN LENSR=160;
Thanks to Robert Obee, Ensono, USA.
Change 37.134 CHART option changed to NONE because DSIG option is no
ANALACTM longer supported after SAS 9.3. The four coefficients
Jun 15, 2019 (CPU SRB MSO IOC) are added to WLM definitions report.
Change 37.133 TYPE42HI dataset, variables S42VSXST/S42VSXRT/S42VSXID
VMAC42 added in MXG 37.02 and MXG 37.03 incorrectly as character
Jun 17, 2019 variables with $EBCDIC8 informat. Change 37.019 in 37.04
corrected them to &PIB.4. numeric variables, but if you
build WEEKLY PDBs with some days created by 37.02/03 and
other days by 37.04 or later, you will need to either
DROP those variables from the 02/03 day's PDB, or just
remove the creation of TYPE42HI for that week.
It is always best if a new version of MXG is installed
to run on the first day of your week, so that all of
those daily PDBs will have identical structure.
Thanks to Jim Horne, Lowe's Companies, USA.
Change 37.132 Addition of a semi-colon following &OUTCODEx argument in
ASUM4HRS %VMXGSUM invocations to prevent rare errors.
GRAFCEC
GRAFWLM
VMXGRMFI
VMXGSUM
VMXGSUM
VMXGUOTT
Jun 14, 2019
Change 37.131 ANALCNCR fails with multiple errors if there are 0 OBS in
ANALCNCR the input datasets. Now detected and ANALCNCR ends.
Jun 21, 2019
Change 37.130 -New VM Account datasets supported.
EXVMCAPD dddddd Dataset Description
EXVMCAPE CHGD VMCAPCHD CAPABILITY*CHANGED
IMACVM CHGE VMCAPCHE CAPABILITY*CONTINUATION
TYPEVM -Under investigation with IBM Support:
VMXGINIT -Records with blank RECID (bytes 79-80).
Jun 25, 2019 -VMSESSN records overlap, with ACCTTIME greater than the
STARTIME=ACCTTIME-CONECTTM of the next record for the
User TCPIP, trying to use this data for availability
measurement.
Thanks to William Marshall, Ensono, USA.
Change 37.129 Member INSTALL and the listed members were updated with
INSTALL more consistent names in the examples.
MXGWPSV4 -The WPS V4 JCL Procedure need a new DD for 4.1:
JCLINSTW //MAPS DD DSN=&WPSHLQ..MAPS,DISP=SHR
MXGWPSV3
MXGWPSV4
JCLINSTL
JCLINSTT
CONFIGW4
Jun 12, 2019
Change 37.128 SMF 82 ICSF updates from ICN1633 for a future release:
FORMATS -New variable SMF82CSF in TYPE8201 identifies source of
VMAC82 the startup member name, formatted MG082CS.
Jun 12, 2019 -Variable SMF82UCB, SMF82TKF bits are decoded in TYPE8209.
-Variable SMF82TKF bits are decoded in TYPE8209
-Variable SMF82BOT bits are decoded in TYPE8213.
Change 37.127 -Formats created for TYP11902 dataset variables TTTTLSCS,
FORMATS TTTLSPD, TTTERMCD, TTSMCSTATUS, and values updated in
VMAC119 format $MG119RE for variable T119REAS.
Jun 11, 2019 -New TYP11902 variables:
TTSMCSTATUS='SMC-R*STATUS'
TTIPSECFLAGS='IP*SECURITY*STATUS'
TTLCLSMCBUFSZ='LOCAL RMB*BUFFER*SIZE KB'
TTRMTSMCBUFSZ='REMOTE RMB*BUFFER*SIZE KB'
-New TYP11994/TYP11995 OPENSSH new variables.
SSH_FIPSMODE ='RUNNING*IN*FIPS*MODE?'
SSH_KEXMETHOD ='KEY*EXCHANGE*METIOD*USED'
Thanks to Randy Hewitt, DXC, USA.
Change 37.126 z/VM MONWRITE deaccumulated field deltas are sometimes a
VMACVMXA negative value, especially in user fields like VMDTTIME,
Jun 7, 2019 usually related to a VM system event, but the original
assumption was that the negative value was due to a wrap
of the 4-byte accumulated value, so 4294967296 is added,
a guess at the full word wrap value, but these negatives
are not due to a wrap, and you get a very large value.
This change now sets the variable to a MISSING VALUE when
a negative delta is found, so those spikes won't impact.
Thanks to Terry Chao, DC Government, USA.
Change 37.125 Reserved Change.
====== CHANGES THRU 37.124 ARE IN MXG 37.04 DATED Jun 5, 2019 =========
Change 37.124 Variable ID added to the TYPE60,TYPE6156,TYPE62,TYPE64,
VMAC60 TYPE6367,TYPE68,TYPE69 datasets so a direct merge can be
Jun 5, 2019 made without added data passes.
Thanks to Tony Curry, BMC, USA.
Change 37.123 MXG calculation of TYPE70 variable CPUMVSTM/PCTMVSBY was
VMAC7072 too small because Parked Time was incorrectly subtracted
Jun 5, 2019 from CPUUPTM which already has Parked Time removed.
Variables PLCPRDYQ (Ready Queue Delay Percent) and
SHORTCPS were also too small and corrected. Impact was
typically less than ten percent.
Thanks to Ken Deering, COMPUWARE, USA.
Thanks to Selby Shanly, COMPUWARE, USA.
Change 37.122 Support for two new variables in RACF OFFLOAD RACF0200
VMACRACF dataset, with values of YES or NO:
Jun 3, 2019 USBD_ROAUDIT ='USER*HAS*ROAUDIT*ATTRIBUTE?'
USBD_MFA_FALLBACK='USE*PASSWORD*MFA UNAVAIL?'
Thanks to Karl Laseki, American Chemical Society, USA.
Change 37.121 Support for ThruPut Manager Release 18.02 v7r1.0.
VMACTPMX -New variables added to TPM10 dataset:
May 30, 2019 TPMCMLFL='TPMCMLFL*FLAG*BYTE'
TPMCMLCL='SLM*CAPACITY*LEVEL*1-5'
TPMCMLCP='CAPPED*PERCENT*LAST 5*MINUTES'
TPMCMLCC='CEC*CAPACITY*MSU/HR'
TPMCMLAG='AVG GS*JOBS*LAST*5 MIN'
TPMCMLAP='AVG PCS*JOBS*LAST*5 MIN'
TPMCMLAT='AVG GS+PCS*JOBS*LAST*5 MIN'
TPMCMSNM='LPAR*SET*NAME'
TPMCMSLM='LPAR*SET*LIMIT*MSU/HR'
TPMCMSA4='LPAR*SET*4HRAV*MSU/HR'
TPMCMSI5='LPAR*SET*5MINAV*MSU/HR'
TPMCMSFL='TPMCMSFL*FLAG*BYTE'
TPMCMSCL='LPAR*SET*CMP LIMIT*MSU/HR'
TPMCMSC4='CMP-WIDE*4HRAV*MSU/HR'
TPMCMSCI='CMP-WIDE*5MINAV*MSU/HR'
TPMCMSMA='MOBILE*4HRAV*MSU/HR'
TPMCMSBA='CATEGORY A*4HRAV*MSU/HR'
TPMCMSMI='CATEGORY B*4HRAV*MSU/HR'
TPMCMSMI='MOBILE*INTERVAL*USAGE*MSU/HR'
TPMCMSAI='CATEGORY A*INTERVAL*MSU/HR'
TPMCMSBI='CATEGORY B*INTERVAL*MSU/HR'
-New variable added to TPMSLM dataset
TPMSCLVL='MAXIMUM*CAPACITY*LEVEL'
Change 37.120 Mobile Service Units on GP and IIP ARE included in the
VMAC7072 CPUTM and ZIPCPUTM variables in TYPE72GO and TYPE72TR.
May 28, 2019 The comments in Change 36.253 are wrong and the proposed
CPUTM_ALL=SUM(CPUTM,CPUMOBILCP) is now CPUTM_ALL-CPUTM
and labeled EQUAL*TO*CPUTM. Using a WLM Policy that
classified the entire workload for a service class as
MOBILE, the Service Units were the same in the sum of
R723CCPU and R723CSRB (CPUTCBTM and CPUSRBTM), and in
R723TSUCP and in R723MSUCP (Total GP and Total Mobile).
Thanks to Ken Deering, Compuware, USA.
Thanks to Selby Shanly, Compuware, USA.
Change 37.119 Label for PTECP2 is 'CPU TIME*ZIP*ELIGIBLE' instead of
VMACNDM "QUALIFIED".
May 28, 2019
Thanks to Joe Faska, DTC, USA.
Change 37.118 Sites with NLS issues must use CONFIMXG, but to build the
JCLCONFI new FORMATS catalog, you must use the JCLCONFI example.
May 27, 2019
Change 37.117 The optional CICS DBCTL SMF 110 segment can be 164 or 256
IMACICDB but the order was the 164 first, so if you opened both of
May 23, 2019 the comment blocks, the 256 segment was misaligned. Now,
the 256 segment is first and both blocks can be opened to
support both lengths.
Thanks to Steven W. Erkkila, USBank, USA.
Change 37.116 -WPS U4087 ABEND in WPS 4.1 but not in WPS 4.0 due to the
CONFIGW4 new data copier added in 4.1, can be circumvented with
AUTOEXEW OPTIONS NOWPSSCATTERCOMP; which turns off the facility.
May 22, 2019 -This correction also fixed a CPU Loop in WPS 4.1.
Jun 17, 2019 -CONFIGW4 for z/OS and AUTOEXEW for ASCII have the option
added, but commented out, and for WPS 4.1 you must remove
the comment block. That option did not exist in 4.0.
Jul 3: Corrected in WPS 4.1.2.0.17535.
Change 37.116A Variable OPENTIME was repeated in _BTY1415 By List macro,
VMAC1415 causing NOTE:DUPLICATE BY VARIABLES. Second OPENTIME was
May 22, 2019 removed. Change 35.166 revised the BY list.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 37.115 Wrong SMF record types for the example IFASMFDP step when
UTILBLDP BUILDJCL=YES was specified. 23 should have been 25 and
May 22, 2019 26J2/26J3 should be 26.
Change 37.114 Support for updated BETA 93 V6R2 (INCOMPATIBLE changes).
EXTYBET9 Offset to data was changed for some records.
EXTYBETP New subtypes create new datasets:
EXTYBETQ DDDDDD DATASET Description
EXTYBETR TYBET9 BETA9 RECORDS LIST/REPORT CVRTD
EXTYBETS TYBETP BETA12 PRINT HEADER PAGES
EXTYBETT TYBETQ BETA17 RECORDS MAILING OUTPUT
FORMATS TYBETR BETA30 DSC DATA CONVERTED LISTS
IMACBETA TYBETS BETA31 DSC RESRCS CVRTED LISTS
VMACBETA TYBETT BETA55 LOGOFF REQS WEB ENABLER
VMXGINIT Only BETA12 & BETA55 new datasets have been data tested.
May 22, 2019 Variable SYSUSRJOBCORR is INPUT and KEPT for subtypes
May 27, 2019 that contain it.
Thanks to Andreas Menne, Finanz Informatik-Sicherheitshinweis,GERMANY
Thanks to Martina Ruminski, Fin Informatik-Sicherheitshinweis,GERMANY
Change 37.113 NDM-CDI 24-byte record INPUT EXCEEDED ERROR; the header
VMACNDM length is 28 bytes, so a test for length is added and an
May 19, 2019 error message printed and the record deleted.
Thanks to Kurt Gramling, T-SYS, USA.
Change 37.112 New options CLEARALL=ONLY will clear any normal MXG
VMXGALOC associated LIBNAMEs allocated to your session without
May 19, 2019 trying to allocate new libnames.
Clears these libnames:
PDB SPIN MON TUE WED THU FRI SAT SUN WEEK
WEEK1-WEEK5 WTD MONTH MTD TREND
only if they are allocated.
Change 37.111 Final revisions for WSF/EOS WSFAUDIT variables AUDACT
FORMATS and AUDOBJN and their FORMATS, replaces Change 37.083.
VMACWSF -Dataset WSFACCT will always have zero observations; it
May 14, 2019 was never correct and is replaced by the four datasets
WSFDSN, WSFERD, WSFEVTSC, and WSFEVTPR.
Change 37.110 MXG Members TYPExxxx create output datasets in //WORK,
TECHNOTE MXG Members TYPSxxxx always SORT from WORK to PDB, and
May 11, 2019 the _Sxxxx sort macro all datasets for product xxxx and
deaccumulates those datasets with accumulated fields.
Exception: TYPEDB2 invokes the _SDB2 macro that sorts
all DB2 datasets except for DB2ACCT, and _SDB2
deaccumulates the DB2 datasets listed below
that need deaccumulation. They are also listed
in member DIFFDB2 lists sort/nonsort datasets.
NOTE: DB2ACCTP is sorted by _SDB2, but if you
only want Stats sorted, use _S100.
Exception: TYPE110/TYPE110S _S110 never sort these:
SUBTYPE=1, CICS MONITOR DATASETS:
_SCICTRN - CICSTRAN IS NOT SORTED, HIGH VOLUME
_SCICRDS - CICSRDS IS NOT SORTED, HIGH VOLUME
_SCICRDD - CICSRDPL IS NOT SORTED, HIGH VOLUME
_SCICRDF - CICSRDFI IS NOT SORTED, HIGH VOLUME
_SCICRDQ - CICSRDQU IS NOT SORTED, HIGH VOLUME
_SCICIDN - CICIDNTY IS NOT SORTED, HIGH VOLUME
_SCICIDD - CICIDNDD IS NOT SORTED, HIGH VOLUME
_SCICACC - CICSACCT NOT SORTED, PRE-CICS/ESA ONLY.
_SCICSYS - CICSYSTM NOT SORTED, PRE-CICS/ESA ONLY
PRODUCT DATASETS THAT ARE ACCUMULATED DDDDDD/DATASET
28 028IN7/NPMINPMT
30 TY30U6/TYPE30_6
50 DIF() ONLY FOR INTERVAL DELTA
79 TY791/TYPE791 TY792/TYPE792 TY799/TYPE799
TY79C/TYPE79C
99 TY99BG/TYPE99BG
102 102380/T102S380 102402/T102S402
103 TY1032/TYPE1032 TY103D/TYPE103D
108 TY1083/TYPE1083
110 INTTC/CICTC INTTSR/CICTSR INTDMG/CICDMG
INTVT/CICVT INTAUT/CICAUTO INTLDS/CICLDG
INTDTB/CICDTB INTTCR/CICTCR INTDQR/CICDQR
INTDQG/CICDQG INTTSQ/CICTSQ INTDS/CICDS
INTST/CICST INTFCR/CICFCR INTM/CICM
INTTDG/CICTDG INTSDG/CICSDG INTSMS/CICSMDSA
INTAUS/CICAUSS INTCO3/CICCONMR INTCO1/CICCONSR
INTDL3/CICDLIG INTDL1/CICDLIR INTDBU/CICDBUSS
INTPGG/CICPAUTO INTIRC/CICIRCB INTDMR/CICDMR
INTFEP/CICFEPIP INTFEC/CICREPIC INTFET/CICFEPIT
INTJCR/CICJCR INTLDR/CICLDR INTLS3/CICLSRFR
INTLS1/CICLSRR INTSDR/CICSDR INTSMD/CICSMD
INTSMT/CICSMT INTTC1/CICTCLR INTTDR/CICTDR
INTXMC/CICXMC INTUSG/CICUSG INTXMG/CICXMG
INTXMR/CICXMR
113 TY113/TYPE113 TY1131/TYPE1131
AIX ALL AIX Datasets
DB2 DB2PST/DB2PSTXX DB2NET/DB2NETXX DB2ST5/DB2STAT5
DB2ST0/DB2STAT0 DB2ST1/DB2STAT1 DB2STS/DB2STATS
DB2SBP/DB2STSBP DB2STB/DB2STATB DB2STR/DB2STATR
HSM HSMDSR/HSMDSRST HSMFST/HSMFSRTP HSMFUN/HSMDSRFU
HSMVSF/HSMVSRFU HSMVSR/HSMVSRST
IMS IMS452/4/6/7/8/9/C/D/E/F/O/P/G/H/I/J/K/L/M/N
UNS56B
MPLX MPLXIN/XSE/XGA/XRT/XPE/XPM/XPO
NDM NDMCT
ASI CPUTA_LF,TCBTA_LF,IOCNT_S,TRCA_S,TET,TRT
TCP TYTCPS/TYPETCPS
TPX TPXINT/TPXINTRV
VMXA SYTSYP/SYTPRP/SYTRSG/SYTRSP/SYTXSP/SYTASG/SYTSHS
SYTUSR/SYTCPC/SYTSCG/SYTCOM/SUTUWT/SYTSCP/SYTXSG
SYTCUG/SYTCUP/SYTCUM/SYTCPM/SYTSYG/SYTEPM/SYTLCK
SYTLCX/SCLADL/SCLDDL/SCLAEL/SCLSRM/SCLSTP/STORSG
STORSP/STOSHR/STOASP/STOBPG/STOXSG/STOXSU/STOASS
STOASI/STOSHD/STOVDK/USEDFC/USEATE/USEITE/PRCPRP
PRCIOP/PRCAPM/PRCMFC/PRCPUP/PRCMFM/IODDEV/IODMOF
IODVSW/VMDSES/ISFISA/ISFNOD/APLSRV/APLSLM/APLSLP
APLSL0/APLSLN/APLCMS/APLVMR/APLLXP/APLTC0/APLTC3
APLTC4/APLTC5/APLTC7/APLTC8/APLTC9/APLTCA/APLTCB
SSISCS/SSISMI/SSIXLK/SSIXDI
Change 37.109 Support for z/OS 2.4 SMF Manual 04MAR19 are already in
VMAC7072 place in MXG 37.02+, Change 37.037 from 14JAN19 Manual,
VMAC74 except for
May 10, 2019 -SMF70CPC_TYPE, listed in "Summary of Changes" page xxii,
but the field is not found in in the manual,query raised.
-New SMF70PRTCTV='SMF70OS*PRTCT*IS VALID?' flag in TYPE70.
compatibly added in this change.
Change 37.108 Bit mapping documentation for NDN-CDI CNF1/CNF2 fields:
VMACNDM NDMCNF1 $CHAR1. /*SECURE*COPY*FLAG1*/
May 9, 2019 /* BIT MAPPINGS FOR NDMCNF1 AND CISECNF1
PCEF EQU X'80' PNODE ENCRYPT.DATA
SCSI EQU X'40' SNODE SECURE.SIGNATURE
PCSI EQU X'20' PNODE SECURE.SIGNATURE
CCSI EQU X'10' COPY SECURE.SIGNATURE
SCEF EQU X'08' SNODE ENCRYPT.DATA
SSL EQU X'04' SSL.ENABLED=Y
TLS EQU X'02' TLS.ENABLED=Y
STS EQU X'01' STS.ENABLED=Y */
NDMCNF2 $CHAR1. /*SECURE*COPY*FLAG2*/
/* BIT MAPPINGS FOR NDMCNF2
CSIN EQU X'80' SIGNATURE = CURRENT KEY
PSIN EQU X'40' SIGNATURE = PREVIOUS KEY
TLS EQU X'20' TLSV10 ENABLED
STS EQU X'10' STS.ENABLED
IPV6 EQU X'08' IPV6 ADDRESS
TLS1 EQU X'04' TLSV11 ENABLED
TLS2 EQU X'02' TLSV12 ENABLED
ZFBA EQU X'01' ZFBA WAS USED */
NDMCPEA $CHAR1. /*MERGED*SECURE*ENCRYPT*NUMBER*/
Change 37.107 A change in the length of TPX05LEN misaligned TPXETIME &
VMACTPX TPXATIME; they incorrectly INPUT blanks, which TODSTAMP8
May 9, 2019 reported as 8am on Oct 27, 1935.
Thanks to Craig Bigler, Progressive, USA.
Thanks to Ann Knapik, Progressive, USA.
Change 37.106 A check of SYSFILRC that should have been inside a DO
BLDSMPDB loop checking SMFIN could cause a spurious critical error
May 8, 2019 saying that the allocation of the SMF file failed if some
May 13,2019 other earlier FILENAME statement had failed. FILENAME
May 19, 2019 statements don't tell us when they have a problem until
you try to use them unless you check the SYSFILRC macro
variable for a non-zero value.
-If you run a weekly job independently of a daily job and
are using AUTOALOC=YES and need to rerun the week using
FORCEDAY it pointed at the incorrect day and did not
recognize the start of the week. FORCEDAY should always
be the date of the data being processed so if your week
starts on Monday FORCEDAY should point at Sundays date.
If you are running a weekly or monthly job the code
validating parameters still looks at the value in
BUILDPDB and if it did not match what was expected could
cause a failure. Now you can either omit the parameter
and allow it to default or you can specify BUILDPDB=NO.
-If you run TREND daily and needed to rerun a WEEK, the
trending ran as if it were daily. If you are using
AUTOALOC this just repeats what was already done and
there will be no duplication of data. Now BLDSMPDB checks
to see that RUNDAY is NE NO.
-BLDSMPDB now sets SYSCC=16 if it detects any errors, and
displays that condition code value at the end.
Change 37.105 Support for SMF 120 WAS and LIBERTY COMPATIBLE new data:
VMAC120 -Subtype 11. TYP120BL. SM120BDL='ON IF*CVTZCBP*IS ON?'
May 6, 2019 -Subtype 09. TYP1209N. SM1209HW='ON IF*CVTZCBP*IS ON?'
SM1209HX='WORKER*THREADS*PRESENT'
-Subtype 12. TYP12012. SM120CEJ='ON IF*CVTZCBP*IS ON?'
Change 37.104 Variables CECSER and CPCMODEL are added to TYPE72GO data
VMAC7072 set, retained from prior 70. However, they are set blank
May 6, 2019 if the PREVVSYS system is not the SYSTEM of this record,
May 19, 2019 which could happen if the SMF data was sorted before MXG
or if an SMF Dump happens to start with type 72 records.
Thanks to Andrew Petersen, DXC Technology, AUSTRALIA.
Change 37.103 Support for IMS Log Records 5607/5610/5904/5950 creates
EXIMS567 new datasets:
EXIMS56A DDDDDD DATASET DESCRIPTION
EXIMS594 IMS567 IMS5607 MCS/PICOS
EXIMS595 IMS56A IMS5610 START PHASE 1 SYNCPOINT
IMACIMS IMS569 IMS5609 CCTL DISCONNECT FROM DBCTL
VMACIMS IMS56B IMS5611 END OF PHASE 1 SYNCPOINT
VMXGINIT IMS56F IMS5615 RRS RESTART DONE
May 15, 2019 IMS594 IMS5904 REGION OCCUPANCY RECORD
IMS595 IMS5950 DATA BASE LOG RECORD
Change 37.103A FORMAT $MGFSMFID updated for DB2 102 IFCIDS for ANALID.
ANALID
FORMATS
May 15, 2019
Change 37.102 Support for CICS/TS 5.5 new Statistics, COMPATIBLE, two
EXCICMPR new datasets, and all _SCICxxx sorts now deaccumulate.
EXCICSJN For 5.5, fields were inserted into reserved areas.
FORMATS -New Dataset CICMPR for STID=145 CICS Policy statistics.
IMAC110 MPR_POLICY_NAME ='POLICY*RESOURCE*NAME'
VMAC110 MPR_RULE_NAME ='POLICY*RULE*NAME'
VMXGINIT MPR_POLICY_USERTAG='POLICY*USERTAG'
May 6, 2019 MPR_BUNDLE_NAME ='POLICY*BUNDLE*NAME'
May 18, 2019 MPR_BUNDLE_DIR ='POLICY*BUNDLE*DIR'
Jun 2, 2019 MPR_RULE_TYPE ='RULE*TYPE'
MPR_RULE_SUBTYPE ='RULE*SUB*TYPE'
MPR_ACTION_TYPE ='ACTION*TYPE'
MPR_ACTION_COUNT ='RULE*ACTION*COUNT'
MPR_ACTION_TIME ='RULE*LAST*ACTION*TIME'
-New Dataset CICSJN for STID=150 NODEJSAPP statistics.
SJN_NAME ='NODEJSAPP*NAME'
SJN_LE_RUNOPTS ='NODEJSAPP*LE*RUNOPTS'
SJN_STATE ='NODEJSAPP STAT'/
SJN_DEFINE_SOURCE ='GROUP*INSTALLED*FROM'
SJN_CHANGE_TIME ='CHANGE*CREATE*TIME'
SJN_CHANGE_USERID ='CHANGE*USERID'
SJN_CHANGE_AGENT ='CHANGE*AGENT'
SJN_INSTALL_AGENT ='INSTALL*AGENT'
SJN_INSTALL_TIME ='INSTALL*CREATE*TIME'
SJN_INSTALL_USERID ='INSTALL*USERID'
SJN_CREATION_LCL ='CREATION*TIME*LOCAL'
SJN_PID ='NODEJSAPP*PID'
SJN_BUNDLE_NAME ='BUNDLE*NAME'
SJN_CPU ='TOTAL*CPU*TIME'
SJN_HEAP_CURRENT ='ALLOCATED*HEAP'
SJN_HEAP_RUNTIME ='HEAP*USED BY*RUNTIME'
SJN_HEAP_APP_DATA ='HEAP*USED FOR*DATA'
SJN_HEAP_MAX ='MAX*POSSIBLE*HEAP'
SJN_INVK ='COMPLETED*INVOKES'
SJN_INVK_ERR ='COMPLETED*INVOKES*IN ERROR'
SJN_INVK_CUR ='CURRENT*INVOKES*IN PROGRESS'
SJN_INVK_PEAK ='PEAK*INVOKES IN*PROGRESS'
SJN_NODEHOME ='NODEHOME*PROFILE*ENTRY'
SJN_PROFILE ='PROFILE'
SJN_STARTSCRIT ='ENTRY*JAVASCRIPT'
SJN_STDERR ='STDERR*FILE'
SJN_STDOUT ='STDOUT*FILE'
SJN_TRACE ='TRACE*FILE'
SJN_LOG ='LOG*FILE'
-Dataset CICDB2GL STID=102 new variable
D2GTCBPR='TCB*PROTECTED*CURRENT'
-Dataset CICCONSR STID=52 new variables.
A14EAHWM='MAX*AIDS'
A14EALL expanded to 4 bytes, used reserved area.
-Dataset CICMNG STID=81 new variables
MNGIR ='IDENTITY*RECORDS'
MNGIRS ='IDENTITY*RECORDS*SUPP BY EXIT'
MNGDPLRL='DPL*RESOURCE*LIMIT'
MNGURIRL='URIMAP*RESOURCE*LIMIT'
MNGWEBRL='WEBSVC*RESOURCE*LIMIT'
-Dataset CICXMR STID=11 variable
XMRAENDC='ABEND*COUNT'
-Previously _SCICddd Statistic Dataset Sort Macros only
PROC SORTed from WORK to PDB; there was no deaccumulation
so fields with accumulated values were wrong. Now, all
_SCICddd macros de-accumulate correctly into the PDB.
The _S110 macro sorts account and all statistics datasets
the _S110ST macro sorts only the statistics datasets.
-By DEFAULT, TYPE110 & BUILDPDB do NOT invoke _S110ST. All
datasets are left in work, where you can tailor EXPDBOUT
to sort all or individual datasets. You can use
%LET EPDBOUT= _S110ST ; in your SYSIN to sort the stats
datasets AND deaccumulate to correct errors in CICINTRV.
-But if UTILBLDP is used to create your tailored BUILDPDB,
and if CICS data was requested, then _S110 is invoked, so
your PDB.CICINTRV will be valid as soon as you use 37.04.
-TYPS110 invokes _S110, TYPE110 does not.
-Revised deaccumulation logic needed JOB READTIME added
to the BY list, and logic NOT FIRST.READTIME used to
eliminate large values created when back-to-back regions
had forward times.
-A new _SCICxxx sort macros option MXGCICRQTSORT can be
used to only read and use the SMFSTRQT='INT' interval
records with this statement in your //SYSIN:
%LET MXGCICRQTSORT=%QUOTE(WHERE SMFSTRQT='INT');
This needs testing when you have multiple RQTs.
The MXG default continues to use ALL record types.
-A new macro variable &MXGCICSORTED is set to YES in
_S110 and _S110ST macros so that the logic in VMXGCICI
knows to use the PDB deaccumulated data. You would only
need to set it to YES if you are building CICINTRV in
a separate job from the one that created the stats PDB.
Change 37.101 MXG 37.03, if you used USERADD=102.nnn syntax for DB2
UTILBLDP IFCID subtype, and used BUILDPDB=YES, the generated code
May 6, 2019 was wrong and failed with 455-185 W102nnn error.
Thanks to Tim Hare, Florida Department of Transportation, USA.
Change 37.100 DB2 zPARM T102S106 vars were wrong in V11/V12 because
VMAC102 QWP4CYR input $EBCDIC8 but it is only one byte:
May 3, 2019 QWP4CYFR QWP4DDLM QWP4CDSTL QWP4ZHYPL QWP4STACS
These zPARM variables in DB2 V12 are now supported:
QWP4RTNP ='REORG*TS_NOPAD*DEFAULT?'
QWP4DYNPFSW ='QWP4DYNPFSW'
QWP4PSPN ='PAGESET*PAGENUM*ABSOLUTE*RELATIVE?'
QWP4RDS_DM_BLKFI='QWP4RDS*DM*BLKFI'
QWP4NIDX ='QWP4NIDX'
QWP4IXMC ='INDEX_MEMORY_CONTROL'
QWP4UHMDH ='UTILS*HSM_MSGDS*HLQ'
QWP4DINA ='DEFAULT*INSERT*ALGORITHM'
QWP4MISD ='QWP4MISD'
QWP4FLT ='QWP4FLT'
QWP4IXMT ='QWP4IXMT'
QWP4AUTC ='AUTH*COMPATIBILITY'
QWP4TSCT ='QWP4TSCT'
QWP4ENKL_OFF ='OFFSET*FOR*ENCRYPTION*KEYLABEL'
QWP4CDRL='COMPRESS*DIRLOB'
QWP4SFPR='STATFDBK*PROFILE'
QWP4AUTCSU='SELECT*FOR*UNLOAD'
Thanks to Lai Fai Wong, Bank of America, USA.
Change 37.099 Two formats for CICS Version variable SMFPSRVR displayed
FORMATS 72 instead of 'TS5.5' or '5655-Y04 in MOBILE data.
May 2, 2019
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 37.098 -Possible Abend S0C7 when using the CDF Filter SYSPLEX=
ASMRMFV after ASMRMFV change 36.241. Affects MXG releases
May 1, 2019 36.12-37.03. HAS NOT OCCURRED, exposure was observed.
-Options message RMFV037I incorrectly shows SHOWASI,
but SHOWASI option is not actually in effect. Affects
MXG release 37.03 only.
Change 37.097 APAR OA56762 NEGATIVE SMF30_TIME_ZIIP_ON_CP zOS 2.2 only,
TECHNOTE FLASH caused LARGE CPU time of 42,949,672 seconds because MXG
Apr 30, 2019 input as PIB4 expecting positive values. The INVALID
DATA BIT in SMF30TF2 for this time field WAS NOT ON.
This is variable CPUZIETM='ZIP-ELIGIBLE*CPU TIME*ON CP'
in MXG TYPE30 datasets, and the defect was in eight
subtype 3 interval termination records in this SMF file
Thanks to Jutta Gleixner-Schmid, ALLIANZ. GERMANY.
Change 37.096 RMF III dataset ZRBASI variables ASIFRXB_LF,ASIFRXA_LF
VMACRMFV and ASIFRXH_LF are the sum variables that should have
Apr 26. 2019 been divided by ASISMPCT to report their average value.
The labels are also corrected. Variables CPC_CECNAME
and LPARNAME are added to dataset ZRBBDSIH.
Thanks to Karl Laseki, American Chemical Society, USA.
Change 37.095 New variables added to TYPEDBDS (IMF from BMC):
FORMATS -DBTRIOTM DBTWIOTM DBTFLAG2 DBTFLAG3
VMACCIMS DBTNOI DBTNOO DBTBFSTK DBTBFSTN
VMACIMS -Formats for DBTFLAG2 and DBTFLAG3 created.
Apr 25, 2019 -IMS07 ENDTIME could be missing due to 8 bytes
May 3, 2019 found but not documented; detection/protection
was added.
-Variable BHTOON is added to CIMSTRAN and CIMSDBDS;
it was already kept in CIMSPROG.
-Variable ALPCPTRN was incorrectly formatted $HEX8 and
incorrectly used to create UOWTIME.
-UOWTIME was incorrectly creates like CICS UOWTIME with
only 6-bytes of datetime, but IMS UOWTIME is 8-bytes in
UOWTRANS, now used to create the IMS UOWTIME.
Thanks to Randy Hewitt, DXC, USA.
Change 37.094 CICS 110 Stats CICLSRR dataset accumulated variables that
VMAC110 end with BFF/CRF/CRS/CWF/CWS/FRD/UIW are now correctly
Apr 24. 2019 deaccumulated in _SCICLS1 sort macro when TYPS110 is used
Apr 26, 2019 or it can be added after TYPE110 is included.
See Change 37.102, all CICS Statistics are deaccumulated.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.093 Support for IMS ODBM Accounting SMF Type 29 Subtype 1
EXTY29OD record creates the new TY29ODBM dataset.
VMAC29
Apr 24, 2019
Thanks to Kurt Gramling, T-SYS, USA.
Change 37.092 TRENDINCODE= parameter added to both macros to allow you
VMXGRMFI to limit the trend datasets. You could limit the amount
VMXGDBSS of data retained by specifying (using VMXGDBSS here) by:
Apr 20, 2019 TRENDINCODE=IF DATEPART(BEGTIME) GE TODAY()-732;
to impose a 2 year limit on the data.
====== CHANGES THRU 37.091 ARE IN MXG 37.03 DATED Apr 19, 2019 =========
Change 37.091 -TYPE42 Subtype 5 INPUT EXCEEDED when new MCO/SYO/BGO data
VMAC42 segments exist, MXG miscoded the new segments, MXG 37.02.
VGETUTKN -Hex 00 protection for UTKNPOE/UTKNSCL/SMF42GAO/SMFA2GAO/
Apr 18, 2019 SMF42FAJ/SMF42FBN/SMFA2FAJ/SMFA2FBN/SMF42GAN/SMFA2GAN.
ST 5 Error caught by Early Adopter tester in MXG 37.03EA.
-Jun 17: Variables S42VSXST and S42VSXRT were created in
MXG 37.02-03 incorrectly with $EBCDIC8 informat. This
change corrected them to &PIB.4. numeric variables in
TYPE42HI dataset, but if you build WEEKLY PDBs with some
days 37.02/37.03, and some 37.04 or later, you will need
to DROP those variables from the 02/03-built PDB.
Change 37.090 When BUILDPDB=YES is used with %UTILBLDP, the SMF 113
UTILBLDP records are automatically processed, and ASUM113 is run
Apr 15, 2019 after BUILDPDB. Now, SUPPRESS=113 can be used if you
don't want those datasets.
Change 37.089 -Major enhancements to ASMRMFV and VMACRMFV.
ADOCRMFV -New Field Data Filter (FDF) feature supports field level
ASMRMFV data selection for the RMF III ASI, CSR, and DVT tables.
VMACRMFV -The ANDIF=, ORIF=, IF= keywords are used to specify a
Apr 16, 2019 FDF filter called an IF expression.
-FDF complements the existing Character Data Filter (CDF)
feature. CDF has no numeric data filtering capability.
-If both CDF and FDF filters are used, then CDF filtering
occurs first. Entries filtered by CDF are never passed
to FDF.
-FDF supports character, fixed point, floating point,
percent, bit string, hex string, time, and time of day
fields for filtering depending on the format and content
of each field.
-FDF uses IF expressions with 3 components enclosed in
required matched left/right parentheses in this order:
1. RMF III field name or MXG variable name when
supported
2. Comparison operator
3. Character, numeric, bit string, hex string, percent,
time, or time of day value as appropriate to the
field being filtered.
-See documentation Sections 31-34 for full details on the
use of FDF.
-New RMFV080I-RMFV088I messages added for FDF support.
-New options SHOWARR (alias SHARR) and NOSHOWARR (alias
NSHARR) added to display IF expression memory storage
array activity. Default is NOSHOWARR. see Section 6
Report Control Parameters for more details.
-New options SHOWIF (alias SHIF) and NOSHOWIF (alias
NOSHIF) added to display IF expression compare results
in both Detail and Summary reports in message RMFV080I.
Default is SHOWIF. see Section 6 Report Control
Parameters for more details.
-New option IFERR= controls handling of errors detected
while processing ANDIF=/IF=/ORIF= expressions. Possible
settings are ABEND, ERROR, WARN, IGNORE. Default is
IFERR=ERROR. See Section 8 Error Handling Parameters
For more details.
-Three recently documented RMF Monitor III tables are now
supported for PDB builds: PCI, SCM, and ZFS.
-The PCIE Activity Data Table may be selected with the
PCI, P, MOST, or ALL table select options.
-The Storage Class Memory Data Table may be selected with
the SCM, MOST, or ALL table select options.
-The ZFS Performance Data Table may be selected with the
ZFS, Z, MOST, or ALL table select options.
RMF III data set.
-ASMRMFV will now detect quoted strings and not apply any
translations regardless of UPCASE/NOUPCASE settings.
-ASMRMFV will no longer check for Control Unit Busy or
Switch Port Busy when filtering DVT entries with the
NOZEROIO option. These DVT fields became obsolete and
unused with z/OS 1.4 in September 2002.
-Almost all documentation for ASMRMFV now resides only
in the ADOCRMFV member.
-ADOCRMFV has been reformatted to take advantage of full
72 column width for better legibility.
-Message RMFV033* showed an incorrect value for index
count if an I/O error occurs reading the first or last
MINTIME interval.
-Many documentation sections have been updated and 4 new
sections are added:
Section 31 Field Data Filtering (FDF)
Section 32 Filtering The ASI Table
Section 33 Filtering The CSR Table
Section 34 Filtering The DVT Table
Change 37.088 DB2 102 IFCID 106 truncated variables longer lengths are
VMAC102 now supported:
Apr 15, 2019 QWP4SADM='INSTALLATION*SYSTEM*ADMIN*USERID'
QWP4DFID='SYSTEM*DEFAULT*USERID'
QWP4ADM2='SYSTEM*ADMIN*ID2'
QWP4OPR1='MVS*OPERATOR*ID'
QWP4OPR2='MVS*OPERATOR*ID2'
QWP4REGC='DDL*REG*TABLE*OWNER'
QWP4REGA='DDL*REG*ART*NAME'
QWP4REGO='DDL*REG*ORT*NAME'
QWP4OZUS='ONLINE*ZPARM*USERID*MONITOR'
QWP4FCCD='UTILS*FCCOPYDDN*PARM*DEFAULT'
Thanks to Lai Fai Wong, Bank of America, USA.
Change 37.087 SMF 50 VTAM Tuning record subtypes 02 and 05 don't match
VMAC50 the record documentation and IBM has acknowledged and
Apr 15, 2019 will revise their doc, when this text will be updated.
This change only reverses the order of RDUX/REDE.
Thanks to Svend Zaunick, Finanz Informatik, GERMANY.
Change 37.086 MXG Support for the new Japanese Reiwa era dates is in
TECHNOTE place as MXG does not use any Japanese informats, but
Apr 10, 2019 SAS Note 63973 reports an update is needed to provide
support in NENGO and JNENGO informats/formats.
Change 37.085 SMF 92 Subtype 52 INPUT EXCEEDED. because SMF92TRSN was
VMAC92 documented as 52 EBCDIC on page 846, but there are only
Apr 10, 2019 8 bytes at the end of the record for the name, and the
segment length is 48 to match a final 8-byte field.
But I believed the SMF manual and INPUT 52 without an
extra test to see if the bytes were there.
Thanks to Joe Faska, DTCC, USA.
Change 37.084 Variables CMB10C0-CMB10C4 in VXPRCAPM are wrong because
VMACVMXA their DIF() calls had the wrong variable.
Apr 10, 2019
Thanks to Graham Harris, RBS, ENGLAND.
Change 37.083 -Ignore the first two sections of this original text.
VMACWSF -WSF/EOS revisions corrected misalignment in WSFAUDIT
VMACWSF dataset, but AUDOBJT values of '6C'x and 'B4'x are not
Apr 10, 2019 documented, and the order of AUDACT and AUDOBJT is NOT
Apr 19, 2019 consistent with the documentation, which has always has
May 14, 2019 ACT then OBJT, but for ACT values of '60'x or higher,
I've observed OBJT is first, and the value of OBJT has
to be used to decode the multiple uses of the AUDOBJI
field into the correct variable.
-Also, OBJT values of '6C'x,'B4'x are found but not
documented in the DSECT.
-Dataset WSFACCT will always have zero observations; it
was never correct and is replaced by the four datasets
WSFDSN, WSFERD, WSFEVTSC, and WSFEVTPR.
-May 14, 2019. See Change 37.111.
Change 37.082 SMF 99 ST 12 dataset TYPE99CC Capacity Increase/Decrease
VMAC99 bit variables S99CCCCAPINCR/S99CCCCAPDECR/S99_VCM_D2-4
Apr 9, 2019 are decoded into individual variables:
S99CCCCAPINCR0='ADJUST*CAPACITY*INCREASE?'
S99CCCCAPINCR1='ADJUST*CAPACITY*INCREASE*BY UNPARK'
S99CCCCAPINCR2='UNPARK*REQUEST?'
S99CCCCAPINCR3='UNPARK*ALL*REQUEST?'
S99CCCCAPINCR4='RESERVED'
S99CCCCAPINCR5='UNPARK*CAPACITY*BELOW?'
S99CCCCAPINCR6='CAPPED*UNPARK*HIGH VH*UTILIZATION?'
S99CCCCAPINCR7='RESERVED'
S99CCCCAPDEC00='ADJUST*CAPACITY*DECREASE?'
S99CCCCAPDEC01='ADJUST*CAPACITY*DECREASE*BY UNPARK'
S99CCCCAPDEC02='PARK*REQUEST?'
S99CCCCAPDEC03='PARK*ALL*REQUEST?'
S99CCCCAPDEC04='MVSBUSY*TOO*LOW?'
S99CCCCAPDEC05='VL*EFFECT*TOO LOW?'
S99CCCCAPDEC06='SMALL*VM/VL*EFFECTIVENESS?'
S99CCCCAPDEC07='NO*VM/VL*EFFECTIVENESS?'
S99CCCCAPDEC08='IF*NO*VH*EXISTS?'
S99CCCCAPDEC09='NO DECREASE*LOW*CEC*UTILIZATION?'
S99CCCCAPDEC10='PR/SM*CAPPED*PARK ALL?'
S99CCCCAPDEC11='PR/SM*CAPPED*PARK ALL*HI CEC UTIL?'
S99CCCCAPDEC12='PR/SM*CAPPED*VH UTIL*LOW?'
S99CCCCAPDEC13='PR/SM*CAPPED*VL*EFFECT*TOO LOW?'
S99CCCCAPDEC14='PR/SM*CAPPED*MVS BUSY*TOO LOW?'
S99CCCCAPDEC15='PR/SM*CAPPED*ADJUST*CAPACITY*DECR?'
S99CCCCAPDEC16='PARK ALL*REQUEST*unpark*threshold?'
S99CCCCAPDEC17='PR/SM CAPPED*NO DECR*LOW CEC UTIL?'
Thanks to Jan Tielemans, KBC, BELGIUM
Change 37.081 Velocity VPS USER records are either Interval or Summary
VMACXAM but only the top ten users get Interval records, so when
Apr 5, 2019 analyzing the USER data,you MUST select IF INTORSUM='SU'
to see the total resource usage.
Thanks to Deeresh Naidoo, First Rand Bank of South Africa.
Change 37.080A Datasets BETA9706 and BETA9706D were not output to PDB
VMACBE97 when TYPSBE97 was used to sort from work to PDB.
Apr 4, 2019
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 37.080 Variables SVPCNM Service Class and RPRTCLAS Report class
VMACRMFV are added to all the RCD datasets.
Apr 4, 2019
Thanks to Claudio A. Rodriguez, BancoGFalicia, ARGENTINA
Change 37.079 New variables DBS_DD and DBS_D are created in TYPETPMX.
VMACTPMX Variables SYSTEM,SMFTIME added to ERROR messages.
Apr 2, 2019 Variable $JCL_S decoded and output, Apr 19.
Apr 19, 2019
Thanks to Jack Hyde, OPTUM, USA.
Change 37.078 BY variable R748SIID in dataset TYPE748 format is now
VMAC74 HEX4 (was HEX2), and there are no duplicate observations
Apr 2, 2019 in TYPE748S as R748SIID is unique to each record, due
to that too-short format, false duplicates could have
been deleted in the past.
Thanks to Douglas C. Walter, CITRIBANK, USA.
Change 37.077 Enhanced to sort and remove intervals where a SYSTEM is
SAGANAL on multiple CECs, as when it was moved from one CEC to
Apr 3, 2019 another. New time range report of input SMF 30/70s.
Thanks to Bob Berg, American Family, USA.
Change 37.076 Support for HSM FSR Record addition of Unix filename in
VMACHSM dataset HSMFSRBO variable FSR2_UNAM because FSRDSN is
Apr 2, 2019 only 44 bytes, When FSR2_UNML is greater than 44, FDRDSN
will contain the first part of the name, then ... and
then the last part of the name, while FSR2_UNAM will
contain the full name (up to 128 char).
Thanks to Harald Seifert, Huk-Coburg, GERMANY.
Change 37.075 INPUT STATEMENT EXCEEDED and INVALID DATA for SM125THA
VMAC125 because INFORMAT &PIB.2. was missing the final period.
Mar 30, 2019
Thanks to MP Welch, Bank of America, USA.
Change 37.074 QBSTBPIN was always incorrectly calculated before the
VMACDB2 variables used in the calculation had been DIF()'d
Mar 30, 2019 yielding unrealistically high values. The calculation is
now done in DIFFDB2 after the DIF() calls are done.
Thanks to Randy Hewitt, DXC, USA.
Change 37.073 BBMQ processing reported UNEXPECTED RTINs, when you have
VMACBBMQ multiple BMC products writing to a common history file.
Mar 29, 2019 MXG BBMQ now selects only E1x-E8x, skipping other values
eliminating those log messages. There were no changes
to BBMQ 5.3 records in 5.4.
Thanks to James Wajda, Credit-Suisse, USDA.
Change 37.072 ODS Statistical graphics procedures make extensive use
TECHNOTE of JAVA, which can be very memory intensive on zOS. This
Mar 28, 2019 is any procedure starting with SG or any ODS HTML or ODS
PDF outputs. SAS recommends REGION=512M minimum but the
MXG recommendation is always REGION=0M on the JOB card
on zOS. We have seen REGION usage as high as 900M+ for
jobs running the ANAL9914 Topology report with HTML.
Change 37.071 %MACRO variables INTIME70,INTIME70EN,INTIME70PR can be
VMXG70PR used by ASUM70PR to convert time zones of LPARs to a
VMXGINIT common timezone. This example shifts all times to GMT.
Mar 27, 2019
%LET INTIME70=
%QUOTE(
STARTIME=STARTIME-GMTOFFTM;
SMF70GIE=SMF70GIE-GMTOFFTM;
MACHTIME=MACHTIME-GMTOFFTM;
);
%LET INTIME70EN=
%QUOTE(
STARTIME=STARTIME-GMTOFFTM;
SMF70GIE=SMF70GIE-GMTOFFTM;
);
%LET INTIME70PR=
%QUOTE(
STARTIME=STARTIME-GMTOFFTM;
SMF70GIE=SMF70GIE-GMTOFFTM;
MACHTIME=MACHTIME-GMTOFFTM;
);
%INCLUDE SOURCLIB(ASUM70PR);
This is an initial design, which may be revised.
Thanks to Berthold Willing, AXA, GERMANY.
Change 37.070 Unused Change Number.
Mar 25, 2019
Change 37.069 zEDC Compression types for DCOLLECT datasets revised:
FORMATS Dataset DCOLDSET, variable DCDCTYPE formated values
VMACDCOL 0=0:Not Compressed
Mar 25, 2019 1=1:Generic
2=2:Tailored
3=3:ZEDC
DCDCTYPE replaced DCOLMTYP, now always missing.
Dataset DCOLDC, variable DDCCT format MGDCOCT:
0=0:Generic
1=1:Tailored
2=2:ZEDC
Change 37.068 CF Activity Report Structure Level is moved to ANALRMF3
ANALRMF3 from VMACRMFV. Additional RMF III report examples will
Mar 21, 2019 be added in ANALRMF3.
Change 37.067 Support for RMF III PCI, SCM, ZFX segments create four
EXZRBPCI datasets ZRBPCI, ZRBSCL, ZRBZFX (System Data) and
EXZRBSCL ZRBZFS (File Server Data). ZRBSCL was used for SCM
EXZRBZFX because there already is a ZRBSCM dataset (for CFISSCMS).
EXZRBZFS
IMACRMFV
VMACRMFV
VMXGINIT
Mar 29, 2019
Change 37.066 New TOKEN variables added to TYPE80TK dataset:
VMAC80A TOKMCTOKENKY TOKMCTOKENTM TOKMSISCCNO TOKMEMPLID
Mar 21, 2019
Thanks to Mark Kerr-Delworth, Express ICS, ENGLAND.
Change 37.065 Major rewrite of this macro to eliminate repeating the
VMXGDSN same logic 3 different times. New parameter added to ID
Mar 19, 2019 your HSM managed tape volumes with a default of HSM.
Labels on VOLUMES and TAPE variables corrected to show
that they are actually counts of datasets and not a
count of volumes.
Change 37.064 Doc ONLY. Examples add to suppress 110.1 or 101 or both
UTILBLDP when BUILDPDB=YES.
Mar 20, 2019
Change 37.063 -The ANALID report showed only IDANDSUM=26.000 for either
ANALID JES2 or JES3; now the SUBS (2 for JES2, 5 for JES3) is
VMACID stored in SUBTYPE to create 26.002:JES2 or 26.005:JES3.
Mar 16, 2019 -A non-impacting note about DELETE SMFREC01/02 removed.
Change 37.062 Faulty logic prevented creation of zip eligible chart.
GRAFWRKX
Mar 15, 2019
Change 37.061 Bar charts of ZIP and ZIP eligible added.
GRAFWLM
Mar 15, 2019
Change 37.060 SMF Type 82 subtype 31 INPUT STATEMENT EXCEEDED for
VMAC82 TAG='0204' because MXG incorrectly expected 8 bytes when
FORMATS that TAG only has 8 bytes. FORMAT MG082SN revised to
Mar 20, 2019 include SERVER name.
Thanks to Randy Springs, BB&T, USA.
Change 37.059 Further corrections for IFCID 319 support.
VMAC102
Mar 10, 2019
Change 37.058 Cosmetic: Uninitialized variable CBPERROR.
VMAC30
Mar 11, 2019
====== CHANGES THRU 37.057 ARE IN MXG 37.02 DATED Mar 11, 2019 ========
Change 37.057 Analysis of what your WLM Classification Rules do, using
ANALRULE SMF 30, 101 and 110 to produce three reports for where
Mar 10, 2019 work is sent by SYSTEM and TYPETASK, routing for CICS
transactions by SYSTEM and APPLID, and routing for DDF.
Change 37.056 Unused Change.
Change 37.055 RMF III dataset ZRBCFI, CFACT Coupling Facility Activity
FORMATS Report, which is actually a CF per-Structure report, is
VMACRMFV printed by invoking _CFACT after TYPSRMFV. Macro _CFACT
Mar 9, 2019 is defined at the bottom of VMACRMFV.
Mar 21: MOVED TO NEW ANALRMF3 Report Member. CH 37.068.
Thanks to Ervin Claxon, CSX, USA.
Change 37.054 Using report classes to define workloads in RMFINTRV is a
UTILWORK good way to group workloads but will only work if all
Mar 9, 2019 workloads have a default report class, UTILWORK now
detects this condition and warns that the use of report
classes should not be attempted until this can be
resolved
Change 37.053 New utility contribution, UTILMISS, will create a data
UTILMISS set from an existing dataset, removing all variables that
Mar 8, 2019 have all numeric missing values, and characters blank.
Thanks to Jim Horne, Lowe's Companies, USA.
Change 37.052 Variable CPUERROR in TYPE30 datasets is a two-byte field
VMAC30 but was accidentally made length $4 some time ago due to
Mar 7, 2019 a blank that gave it $HEX8 format which forced length 4.
The correct $HEX4. format is now applied, but LENGTH $4
is also forced, since a change in length will cause PROC
APPEND to fail if the user didn't specify FORCE. These
TYPE30xx datasets are too critical to not protect.
-Flag variables SMF30T32 and SMF30T33 are now kept.
Change 37.051 -IFCID 319 variable QW0319FL is replaced by a variable
VMAC102 for each bit:
Mar 7, 2019 QW0319UR='CALLER*PASSED*USER*REG*NAME?'
QW0319AE='AES*ENCRYPTION*BEING*USED?'
QW0319SC='COMPATIBLE*WITH*TCPALVER?'
QW0319SE='SECURE*CONNECTION?'
-Variable QW0319RI is INPUT and Kept.
-Variables QW0319AE QW0319IY QW0319SC QW0319SE kept.
-New variable QW0319LU='LUNAME*IF*SNA' is created
Thanks to Warren Cravey, FMR, USA.
Change 37.050 UTILBLDP now accepts USERADD=100 or 101 or both, and
UTILBLDP invokes USERADD=DB2, but if only 100 or 101 alone are
Mar 6, 2019 requested, the other record's datasets are _NULL_ed.
UTILBLDP now accepts USERADD=CICS (to read SMF 110)
Change 37.049 Variable ASIQSCANREQ is kept in RMF III ZRBASI dataset.
VMACRMFV
Mar 6, 2019
Change 37.048 Example to "BUILDPDB" only JOB-related Datasets enhanced
JCLPDBJB to support both JES2 and JES3.
Mar 5, 2019
Change 37.047 NDM-CDI dataset NDMCT variable NDMCPU was 256 times too
VMACNDM large and character NDMRIUP6/NDMTYPFK shifted because of
Mar 1, 2019 a 1 byte misalignment in the MXG Input Statement.
Thanks to Mike Creech, BKFS, USA.
Thanks to Roger Foreman, BKFS, USA.
Thanks to Glenn Halligan, BKFS, USA.
Thanks to David Kelley, BKFS, USA.
Change 37.046 Variables SMF70BPS/SMF70ACS for each SMF70CIN engine
VMAC7072 type are variables CP70BPS/IFA70BPS/ZIP70BPS/IFL70BPS
Mar 5, 2019 and CP70ACS/IFA70ACS/ZIP70ACS/IFL70ACS in PDB.TYPE70PR.
and PDB.ASUMCELP (recommended LPAR analysis) and ASUM70LP
(which is BY SYSTEM and has duplicate data.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 37.045 The CTG Version, CTGRVN was added to each of the CTG
VMAC111 datasets created from SMF 111 Records and variables
Mar 5, 2019 CTGIALRQ CTGLCNFA are kept in dataset TY111CXI.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.044 The BMC CMF Product generally updates VERSNRMF only on a
VMAC7072 CMF Release Boundary; values of both 792 (2.2) and 794
VMAC71 (2.3) exist on z/OS 2.3. MXG does NOT use VERSNRMF for
VMAC73 any logic, but this correction for CMF records sets the
VMAC74 VERSNRMF=794 if it was 792 and RMFSRCL Record Level is
VMAC75 81 or 82 depending on subtype.
VMAC76
VMAC77
VMAC78
VMAC79
Mar 1, 2019
Thanks to Joe Faska, DTCC, USA.
Change 37.043 Executing MXG on ASCII under a VM product, or with WORK
TECHNOTE on a network drive, bad things can happen. We SRONGLY
Feb 21, 2019 recommend keeping the WORK file local to the system on
which you are executing SAS.
Two Known Errors:
-This error was found with WORK on a network drive:
ERROR: Unable to obtain valid utility file pathname.
-This error was found under VM with WORK on a network
drive:
ERROR: A lock is not available for WORK.OPTVAR.DATA.
This one can be circumvented by adding
-filelockwait 30
to your SAS command or as an OPTION in SAS.CFG file.
Change 37.042 Change 37.024 did not protect for a blank WANTONLY, but
READDB2 only generated a cosmetic error that %SYSFUNC did not
Feb 19,2019 have right number of arguments.
Change 37.041 DCOLLECT APAR OA54879 reports that DCDEXFLG is NOT USED
VMACDCOL for zEDC compression and is now "DATA SIZES NOT VALID'
Feb 19,2019 and is for non-VSAM Extended Format Data Sets.
Data set sizes that are not valid in either or both of
DCDUDSIZ or DCDCUDSZ variables, which might contain non
zero values, but should not be used.
Thanks to Robert Chavez, FPL, USA.
Change 37.040 Dataset TYPE749 variable R7491DEFCOMPRATIO wrong value
VMAC74 is corrected to
Feb 19,2019 IF R7491IOB GT 0 THEN
R7491INFCOMPRATIO=R7491IIB/R7491IOB;
ELSE R749INFCOMPRATIO=.;
Variables were reversed in the calculation.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 37.039 Three MQ reports matching IBM's MQSMF program. Currently
ANALMQ the reports are a queue summary, a detail report of PUTS,
Feb 14,2019 and a detail report of GETS. The GETS/PUTS reports can
be output to either or both SYSOUT or CSV files.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 37.038 Simple report that combines catalog records (TYPE6156)
ANALHSM1 with HSM activity (HSMFSRST) to generate a report of
Feb 14, 2019 datasets that may be thrashing between primary and
migration.
Thanks to Richard Way, Office Depot, USA.
Change 37.037 Updates found in the Jan 14, 2019 SMF Manual,
FORMATS with more changes to come in 37.03 when validated.
VMAC124 -New Datasets
VMAC41 TYPE42VO='PER-VOLUME STATISTICS'
VMAC42 TYPE42HI='HIGH RESPONSE TIME JOBS'
VMAC7072 -TYPE70 New variables
VMAC74 SMF70_IPL_TIME ='IPL*DATETIME*OF*PARTITION'
VMAC78 SMF70_TRG_M_COUNT='TRG*MEMORY*CONSUMPTION*SAMPLES'
Feb 19, 2019 -TYPE70TR New variable
TRG_MEM ='TENANT*MEMORY*CONSUMPTION*MGBYTES'
-TYPE7002 New variables
R7023SCOPE='80X=CPC SCOPE*40X=SYSTEM*SCOPE'
R7023DID='DOMAIN*ID'
-TYPE70X2 New variables
R7024SCOPE='80X=CPC SCOPE*40X=SYSTEM*SCOPE'
R7024DID='DOMAIN*ID'
-TYPE70Y3 New variables
R7025SCOPE='80X-CPC SCOPE*40X=SYSTEM*SCOPE'
R7025DID ='DOMAIN*ID'
-TYPE749 New Variables
R749LKID='SYNC*I/O*LINK*IDENTIFER'
-TYPE78IO Change
R783DSTX relocated.
-TYPE41 Change
SKIP LOGIC protection for future, no impact now.
-TYPE 42 SUBTYPE 5 New Variables
S42VRID1='DELAYS*TIME*1-10 MICROSEC'
S42VRID3='DELAYS*TIME*100-10000 MICROSEC'
S42VRID4='DELAYS*TIME*1-10 MILLISEC'
S42VRID5='DELAYS*TIME*10-100 MILLISEC'
S42VRID6='DELAYS*TIME*OVER*100 MILLISEC'
S42VRIDM='MAXIMUM*I/O*INTERRUPT*DELAY TIME'
S42VRIDT='DATETIME*OF THE*MAXIMUM'
S42VRIDA='AVERAGE*I/O*INTERRUPT*DELAY TIME'
S42VRBSY='TOTAL*BUSY*TIME'
S42VRRSP='COMMANDS*DELAYED*BASE*RESERVED'
S42VRRSN='CHANNEL*PROGRAMS*WITH*RESERVE'
S42VRRES='DURATION*WHEN*RESERVED'
S42VRREX='LONGEST*CONTINUOUS*RESERVED'
S42VRRSR='AVERAGE*RESPONSE*PROGS WITH*RESERVE'
-TYPE 42 SUBTYPE 6 New Variables
S42SNAVGARDELAY ='AVG APPLICATION*RESUME*DELAY'
S42SNARDELAYCOUNT='AVG APPLICATION*RESUME*DELAYS'
S42DXMXI ='STORAGE*SUBSYSID*FOR S42DSMXR'
-TYPE124 New variable
SM124S1WWPN='WORLDWIDE*PORT*NAME'
Change 37.036 Some IFA variables were not populated in the four output
VMAC7072 datasets created by ASUM70PR; all IFA variable names are
VMXG70PR unchanged, but all "ZAAP" text in labels is now "ZCBP".
Mar 5, 2019
Change 37.035 DB2 V12 overlooked Package Variables now INPUT and KEEP:
VMACDB2 QPACAWLH ='LATCH*WAIT*TIME'
Feb 7, 2019 QPACANLH ='WAITS*TRACE*EVENTS*LATCH'
Mar 5, 2019 QPACRLNU ='THREADS*TO ROLL DATA'
QPACAACC ='WAITS*TRACE*EVENTS*ACCELERATOR'
QPACAACW ='WAIT TIME*ACCELERATOR*REQUESTS'
QPAC_PQS_WAIT ='WAIT TIME*TO SYNC*PARALLEL*QUER'
QPAC_PQS_COUNT ='SUSPENDS*WAITING*SYNC*PARALLEL'
QPAC_PIPE_WAIT ='WAIT TIME*PIPE'
QPAC_PIPE_COUNT ='WAITS*FOR*PIPE'
QPAC_COPYID ='PACKAGE*COPY*ID'
-Macros _N100/N101/_S100/_S101 defined for UTILBLDP.
Change 37.034 Two more SMF 42 subtype 5 ABENDING invalid LENSR=520/592
VMAC42 length values added to the test. APAR OA54668 corrects.
Feb 7, 2019 LENSR IN(232,240,320,376,400,480,448,304,520,560,592,640)
Change 37.033 Support for Axway V3.3.2 2018/06/27 restructured User
VMACAXWY SMF record.
Feb 6, 2019
Thanks to Warren Cravey, FMR, USA.
Change 37.032 TYPE749 z/EDC data, DIVIDE BY ZERO protection failed if
VMAC74 both R7491DCT and R7491ICT were zero; R741BPS had been
Feb 5, 2019 included in the test, but it's always non-zero so the
test now is IF SUM(R7491DCT,R7491ICT) GT 0 THEN
R749FPGBPRT=(1048576*R7491BPC/((R7491DCT+R7491ICT)*R7491BPS));
Thanks to Harald Seifert, Huk-Coburg, GERMANY.
====== CHANGES THRU 37.031 WERE IN MXG 37.01 DATED Feb 3, 2019=========
Change 37.031 Bar charts of MIPS and % CPU added to the analysis work
GRAFWLM by IMPORTANCE, originally based on Peter Enrico's paper.
Feb 3, 2019
Change 37.030 MXG 36.12-37.01 ASMRMFV ASI NOZEROCPU filter stopped
ASMRMFV filtering which could cause a significant increase in the
Feb 3, 2019 size of the RMFBSAM file and the PDB.ZRBASI dataset.
ASICPUTA_LF was added by Change 36.241 to that filter,
but it is an accumulated field that can not be used as it
is always non-zero. NOZEROCPU is supported for z/OS 2.2+
-Section 5 "Input Data Control Parameters" is updated.
====== CHANGES THRU 37.029 WERE IN MXG 37.01 DATED Feb 1, 2019=========
Change 37.029 A reference line of the values for SMF70LAC (overall
ANAL89 rolling 4 hour avg MSU) added to interval MSU charts.
Feb 1, 2019
Change 37.028 Support for z/VM 7.1 (INCOMPAT, BROKEN CONTROL RECORD)
VMACVMXA due to insert in VXPRCDHF plus the change in HCPCPEID
Jan 31, 2019 value for the Service Level test from '40061802 for 6.4
Feb 14, 2019 to '10071802' for 7.1 that failed when tested for 'GE'/
New variable ZVMVERS='07.1.18.1' is created so GE can be
used for IF ZVMVERS GE tests. There were 32 bytes added
to PRCDHF, but the 7.1 DSECT only shows on byte added.
-Heuristic (ZZQUCT+1) test revised, false positive caused
large VMDTTIME value.
Thanks to Graham Harris, RBS, ENGLAND.
Change 37.027 Example added to email the final condition code of a SAS
EMAIL job running in the background on ASCII.
Jan 31, 2019
Change 37.026 If you create your own SUBSYSTEM that handles JES2 output
VMAC26J2 the SUBS value in SMF 26 records is not the expected 0002
Jan 30, 2019 for JES2 (or 0003 for JES3), but instead is a two byte
character field. Previously, MXG TYPE26J2 only output
SUBS=2 execution purge records. Now, if the SUBS is 3,
the JES3 record is deleted with MXGERROR messages that
TYPE26J3/BUILDPD3 must be used for JES3. If the SUBS is
other than 2, the records are presumed to be valid JES2
records, but MXGWARN messages print the SUBSYSTEM name.
Thanks to Randy Hewitt, DXC, USA.
Change 37.025 CICS variable A11ACTCI in CICS Statistics dataset CICDQG
VMAC110 was INPUT but not KEPT.
Jan 29, 2019
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 37.024 Using READDB2 with WANTONLY arguments DB2ST/DB2PST caused
READDB2 ERROR: Char Operand in the %EVAL, due to a superfluous
Jan 29, 2019 AND in an %IF statement that also exposed that PDBOUT=YES
Feb 1, 2019 failed in the PROC SORT of the DB2STATx datasets.
The WANTONLY doc has been updated to note that
WANTONLY DOES NOT SUPPORT DB2STATS DB2STATR DB2GBPST
DB2STATB DB2SDTSBP AND DB2STAT5 DATASETS.
Thanks to Keith C. Shaffer, Cigna, USA.
Thanks to James Cyr. Cigna, USA.
Change 37.023 Unused Change Number.
Change 37.022 The new $MGRMIPS format that maps IBM processor model to
GRAFWRKX MSU and MIPS capacity (created in 37.001) is now used in
GRAFCEC these Graphs, which use PDB.ASUMCELP which has variable
Jan 28, 2019 CPCFNAME so MIPS can be calculated from percent busy:
MIPS=PCTBUSY/100*PUT(CPCFNAME,$MGRMIPS.);
The CPCFNAME is constructed from CPU TYPE and MODEL as
CPCFNAME=PUT(CPUTYPE,$HEX4.)!!'-'!!CPCMODEL;
programmatically, or manually as '3906-420' for that z14.
Thanks to Ervin Claxon, CSX, USA.
Change 37.021 If you run on ASCII with autoaloc=yes and did not put an
VMXGALOC execution of VMXGALOC in your IMACINIT (strongly our
Jan 28, 2019 recommendation) but added a second execution of VMXGALOC
and the parameters did not precisely match those you used
in BLDSMPDB and did not specify READONLY=YES to suppress
the aging off of old directories you could potentially
lose data as it deleted old directories. This change now
looks to see it you specified READONLY as NO and the
current days PDB has already been created it will
generate an MXGNOTE and set READONLY to YES.
-YR2KEEP and BASEYEAR parameters are added to let you
allocate a yearly PDB, Defaults to 0, so it won't be
created or allocated unless you enable it, and you will
need to update your BLDSMPDB to add the dataset names
you want created in the yearly directories. Contact
support@mxg.com if you need help.
Change 37.020 Unused Change Number.
Change 37.019 Documentation note for VMXGUOW/ASUMUOW. If you have a
VMXGUOW tailored CICSTRAN dataset and have dropped any variables,
Jan 25, 2019 you may get an UNITIALIZED message for those variables in
ASUMUOW. While this is an expected and non-critical error
you can remove the error by editing the _KUOWIDC _KUOWCIC
or _Kuowcix macros where the variables appear and simply
remove the variable(s) from the list.
Change 37.018 Support for STC HSC Subtype 32 & 33 create new datasets
EXSTCV32 STCVSM32='RESERVED,INTERNAL USE'
EXSTCV33 STCVSM33='MVCPOOL USAGE'
VMXGINIT
VMACSTC
Jan 27, 2019
Thanks to Randy Hewitt, DXC, USA.
Change 37.017 Many non-fatal corrections were made to type 92:
VMAC92 -Several 16-byte STCKE datetimes inputs were wrong:
Jan 24, 2019 SMF92CCT,SMF92MCT,SMF92CCT,SMF92FSMN
-GMT92OFF had to be relocated around the STCKE INPUT.
-Subtype 50+ have 72 byte data section, 32 for LT 50.
-Subtype 50 variables LRP-LRN only in SMF92EVENT=1,
and INPUT changed from &PIB.4.3 to &PIB.4.0.
-Subtype 50 variables OVS/OCH only in SMF92EVENT=4
-Poor Labels SMF92EVENT/SMF92VOL/SMF92CCHH/SMF92VCN
were enrichened.
-Subtype 50 SMF92OCH corrected format to HEX for CCHH.
-Variable SMF92ADN only kept in TYPE9217 dataset.
-Subtype 59 only the first instance was output.
-Subtype 52 and 54 had incorrect SKIP values.
-Subtype 58 SMF92TRL relocated outside the loop.
-Subtype 59 2 byte filler removed with STCKE fix.
This demonstrates the difficulty in writing new code
with no SMF records to test. SMF 92 code was updated
in Aug 2017 in Change 35.180, expecting a user to send
SMF data if problems were observed, and that didn't
happen until January 2019, with most of the above fixes
mostly done by these two users:
Thanks to John Compton, World Programming Ltd, ENGLAND.
Thanks to Steve Bagshaw, ITMetrics, ENGLAND.
Change 37.016 Report showing total bytes/counts and min/max datetimes
ANALID for each SYSTEM is added as the second report.
Jan 19, 2019
Change 37.015 Variable EDGRTIME had missing values with DATEFORM=E/A/I;
FORMATS RHDTFORM logic moved ahead of EDGRTIME for H record and
VMACEDGR label corrected to EDGRTIME='REPORT*DATE TIME'
Jan 20, 2019
Thanks to Lindsay Oxenham, Department of Defence, AUSTRALIA.
Change 37.014 INPUT EXCEEDED DB2STAT1 SMF 100 Subtype 1 NETEZZA/IDAA
VMACDB2 record because IBM changed the length of OFFQ8ST segment
Jan 18, 2019 but couldn't change LENQ8ST because it is a single field
in the header that should apply to all segments. But the
correct length is now set with LENQ8ST=Q8STNAME_OFF+8;
using the end of the name field for the actual length.
Thanks to Graham Harris, RBS, ENGLAND.
Thanks to Randy Hewitt, DXC, USA.
Change 37.013 New example to count both TAPEDRVS and STEPS, and the
ANALCNCR Concurrency with only one pass of the data.
Jan 20, 2019
Thanks to Randy Hewitt, DXC, USA.
Change 37.012 z/VM Service Level 40061802 INPUT STATEMENT EXCEEDED due
VMACVMXA to VMMTRSYS inserting 60 bytes in the 1.04 record.
Jan 17, 2019
Thanks to Craig S. Bigler, Progressive Insurance, USA.
Change 37.011 Variables QXFETCH/QWACSPEB UNINITIALIZED due to misspell.
VMXGUOW Enhanced to make it easy to only process CICSTRAN data:
Jan 19, 2019 IF _LDB2ACC=_NULL_, DB2 data will not be read.
Jan 25, 2019 IF _INMQ=_NULL_ MQ data will not be read.
Counts of OBS before and after are created and if the
OBS reduction is LT 2, an MXGNOTE advises you to skip
using ASUMUOW which can be very CPU intensive and is
really needed for heavy CICS MRO sites, to consolidate
those multiple CICSTRAN observations into one UOW,
Unit of Work observation.
Thanks to Gary Keeres, Indianapolis Power & Light, USA.
Change 37.010 Reserved Change Number.
FORMATS
VMAC89
Jan 16, 2019
Change 37.009 The $%VGETOBS(DDNAME=&PDBMXG should be (DDNAME=&PDBMXG1
GRAFCEC although no error occurred unless you had set a value
Jan 14, 2019 other than "PDB" for the location of the input PDB.
Thanks to Tom MacCabe, Dominion Energy, USA.
Change 37.008 Enhancement, addition of INCODE= parameter to allow
GRAFWRKX selection by date or system with your inserted code.
Jan 11, 2019 Suppressed a no longer needed graphics catalog note.
Change 37.007 -Support for Beta93 Version 6.2 subtypes 2 and 3, which
VMACBETA both have a lot of undocumented data: subtype 2 docs 140
Jan 22, 2019 but length is 208 and subtype 3 docs 156 with 224 length.
Change 37.006 -If MXGDEBUG has length GT 0 and DSNSTRING or DATASET are
VMXGPRAL zero, debugging messages are created by VMXGPRAL.
VMAC102 -Unmatched parens in data set labels read by VMXGPRAL
Jan 11, 2019 caused non-fatal error messages for datasets with obs:
ERROR: Expected close parenthesis after macro function.
All MXG dataset's labels were examined and VMAC102 for
IFCIDs 84 85 86 87100 101 174 AND 175 were corrected.
Change 37.005 Support for DB2 102 Trace IFCID/SUBTYPE 404 populates
VMAC102 T102S404 (Authorization Compatibility) dataset with
Jan 10, 2019 QW0404xx variables.
Thanks to Warren Cravey, FMR, USA.
Change 37.004 Reading z/OS DATA using the SAS FTP Access method needs
TECHNOTE the RCMD='SITE RDW' argument:
Jan 9, 2019 FILENAME SMF FTP ("'SYS1.SMF'" "'SYS2.SMF'" ... )
USER='XXXXXX' HOST='YYYYYYY' DEBUG
S370VS RCMD='SITE RDW' LRECL=32760
PASS='XXXXXXXX' PASSIVE;
If RCMD is not used, the transfer will time out when
PASSIVE is specified, or will produce a RACF ERROR
if PASSIVE was not specified.
Change 37.003 SMF119 dataset TYP11952 variable SMF119ML_IP_IPV4 was
VMAC119 wrongly compressed of blanks from variable TIRIP instead
Jan 8, 2019 of from SMF119ML_IP_IPV4 in line 4519.
Thanks to Randy Shumate, RELX Group, USA
Change 37.002 -SMF92 Subtype 8 INPUT STATEMENT EXCEEDED because the
VMAC92 documented length of SMF92GDD in the SMF Manual is 4,
Jan 8, 2019 but the length in the record is 8 bytes.
-There were also numerous non-fatal corrections:
-SMF92 Subtype 50, SMF92STHCL missing period, and names
SMF90OIOCCL/SMF82VCX were corrected to SMF92.
Thanks to Miroslav Kubik, IBM Corporation, CZECH REPUBLIC.
Thanks to John Compton, World Programming Ltd, ENGLAND.
Change 37.001 -Improve ability to propagate variables of interest to
ADOCRMFV multiple SAS data sets during RMF III PDB build.
ASMRMFV -RMF III CPCDB table fields CPC_CecMSU, CPC_LparMSU, and
FORMATS CPC_HomeLPName, are added to MXG01 record from the first
VMACRMFV MINTIME interval for each RMF III VSAM dataset at open,
Jan 6, 2019 but those MXG01 values are the values only at start.
Jan 14, 2019 -Format $MGRMIPS is created to map GEIMODEL/GEIIMDL to
Jan 29, 2019 create the CPC_CECMIPS using IBM's LSPRITR table:
Feb 2, 2019 IBM Resource Link: Large Systems Performance Reference
https://www-01.ibm.com/servers/resourcelink/
lib03060.nsf/pages/lspritrzOsv2r2?OpenDocument
-RMF III GEI table fields GEIMODEL and GEIMDL added to
MXG01 record from the first MINTIME interval for each
RMF III VSAM data set, but the MXG01 value is only the
RMF III start. But by RETAINing these fields from the
GEI and CPU records, and by relocating the write of the
GEI, CPU, and CPCDB records before the ASI records for
each interval, the CEC MODEL/Speed and MSU/MIPS capacity
variables CPC_CECNAME CPUCEMSU CPUCEMIPS CPULPMSU
GEIMODEL GEIIMDL and LPARNAME are populated in ZRBASI
and several other datasets.
-NOTE: Not all the fields mentioned above are always
static. Use the RMF III DATASET SWITCH option to force
RMF III to overwrite the oldest data set whenever it is
started if separation of configuration changes by data
set is desired.
-CSVQUERY macro added to show load module size in Change
36.241 for ASMRMFV destroyed pointer to SCT (Step Control
Table). This caused ASMPGM and ASMSTEPN fields in MXG00
record to be garbage and also in message in VMACRMFV.
-Section 12 "Messages" is updated.
-In MXG 36.36 the fields GEIIMDL/GEIMODE were added to
ZRBASI, but they could be incorrect, precipitating
this change in logic in VMACRMFV.
LASTCHANGE: Version 37.
====-====================MEMBER=CHANGE36================================
/* COPYRIGHT (C) 1984-2019 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG ANNUAL VERSION 36.36 is dated Jan 4, 2019, thru Change 36.255.
MXG VERSION 36.12 was dated Dec 25, 2018, thru Change 36.246.
MXG VERSION 36.11 was dated Dec 3, 2018, thru Change 36.236.
MXG VERSION 36.10 was dated Nov 21, 2018, thru Change 36.229.
MXG VERSION 36.09 was 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.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 36.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, although there are
no new NEWSLTRS updates; they are now found in CHANGESS as TECHNOTEs.
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 ANNUAL VERSION 36.36 DATED Jan 4, 2019, THRU CHANGE 36.255.
==MAJOR CHANGES ADDED IN MXG 36.36, DATED Jan 4, 2019 THRU 36.255.
New Product Support
TYPEDB2 36.254 Support for Fast Traversal Index adds variables.
TYPE72GO 36.253 MOBILE Service Units CPU Time not in CPUTM variable.
Incorrect, see Change 37.120.
TYPE102 36.251 Support to populate T102S126 for DB2 102 IFCID 126.
TYPE119 36.250 New variables added to TYP11952 subtype 52 dataset.
ENHANCEMENT
DOCVLONG 36.247 Utility to create DOCVER with all info on one line.
VMXGSUM 36.249 OBS=0 protection adds non-zero SYSCC Error test.
==MAJOR CHANGES ADDED IN MXG 36.12, DATED Dec 25, 2018 THRU 36.246.
TYPERMFV 36.241 CPC_CECNAME added, ASITRT/TET corrected, MSU ACT.
New Product Support
TYPEMGCR 36.240 Support for MegaCryption MEGACR34, subtype 3 and 4.
TYPEBETA 36.246 BETA 93 Version 6.2.0 updates subtypes 0/22/25/50/59
ERROR Correction
TYPEIMS 36.238 MXG 36.11 IMS 14.1 invalid offset ABEND IMS56FA.
TYPEVMXA 36.237 MXG 36.11 old z/VM 6.3 DATA LOSS ABEND MTRSYS 1.04.
VMXGALOC 36.243 Protection for READONLY=YES with FIRSTRUN=NO
BLDSMPDB 36.242 Protection for AUTOALOC=YES and FIRSTRUN=YES
VMXGSUM 36.245 VMXGSUM with user's INCODE GT 32756 chars, ABEND.
ENHANCEMENT
TYPE110 36.244 CICS Variable D2GDB2ID added to CICDB2GL BY list.
==MAJOR CHANGES ADDED IN MXG 36.11, DATED Dec 3, 2018 THRU 36.236.
New Product Support
TYPE110 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT
UTILEXCL 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT
Yes, you need MXG 36.11 for CICS/TS 5.5 because fields were
inserted into SMF 110 CICSTRAN records and using old MXG will
have trashed values due to the misalignment, but MXG could run
and only print error messages, which might be false positives,
or could execute with no errors nor log messages, especially if
you have a tailored IMACEXCL, but your CICSTRAN dataset will
still be invalid.
TYPETMO2 36.236 Support for ASG-TMON CICS for z/OS V4.2 - NO CHANGES.
TYPEMVCI 36.234 Support for BMC's MainView for CICS(v69) COMPATIBLE.
ERROR Correction
TYPEPOEX 36.231 Protection for truncated POEX File Segment records.
TYPE119 36.230 ZERT SMF 119 Subtypes 11 and 12 minor corrections.
Enhancements
ANAL9914 36.232 SMF99 ST 14 Processor Topology Report Enhanced.
==MAJOR CHANGES ADDED IN MXG 36.10, DATED Nov 21, 2018 THRU 36.229.
ERROR Correction
TYPEVMXA 36.221 MONWRITE DEFECT caused large values, LCUPPNUM issue.
TYPE110 36.220 Variable WTOTIOTM could exceed ELAPSTM
TYPE72GO 36.215 Variable MSUSOFT, Software MSU frequently missing.
TYPE102 36.212 Protection for IFCID 376 invalid offsets STOPOVER.
TYPE74 36.211 TYPE749 variables added and corrected.
TYPERMFV 36.201 MXG 36.09, z/OS 2.2 only, ASIxxx text misaligned.
TYPERMFV 36.201 WPS failed ERROR: format '$ CPUPHYAD' invalid
TYPEVMXA 36.198 z/VM VXBYUSR High CPU, records not on same second.
New Product Support
TYPE21 36.218 Support for APARs OA52915 and OA52940, 4 byte counter
TYPEBE97 36.217 Support for new BE97 subtype 6 and subtype 22 update
TYPE7072 36.208 Support for APAR OA56011 for TYPE70 OSPROTECT.
TYPE122A 36.207 Support for zExplorer SMF 122 Subtype 2.
TYPEBETA 36.199 Beta 93 Subtype 51 and subtype 22 updates.
Enhancements
GRAFMSU 36.204 Plots/Tabulate of MSU 4HR usage and capacity.
ANALRMFR 36.203 CPU report with INTERVAL=HOUR was incorrect.
TECHNOTE 36.209 APARs of interest for z/OS.
ASUMCICR 36.226 Major revision to CICS RESPONSE TIME SLA reports.
TYPESTC 36.222 Numerous STC formats were updated with new values.
==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 OA53355 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
described in SAS Note 61672. But SAS apparently does not plan for
a defect correction since the MXG Circumvention solves for MXG and
the text of 61672 simply describes the circumvention needed because
MXG's use of OPTIONS OBS=0 without NOERRORSTOP exposed the defect.
See Change 35.309 for more details on using NOERRORSTOP for your
own PROC SQLs.
SAS V9.4 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.129 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.11 will execute under the previously listed
SAS Versions on all supported platforms
Unrelated to the above SAS Note/Hot Fix, ODS users will want to
use MXG 29.06+, because SAS V9.3 did expose incompatibilities in
MXG code for ODS reporting, that were fixed in MXG Version 29.06.
See Changes 29.159 and 29.169.
And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG,
the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe).
Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors
can occur even though //XXXXXXXX DD is a valid SAS Data Library.
This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does
NOT occur with SAS V9.2, nor with z/OS 1.9. It can be
circumvented by adding a LIBNAME statement that specifies the
ENGINE name. See the Technical Note in Newsletters for SN-35332.
Note that SAS V9.1.3 is now at "Level B" Support from SAS.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"Level C" support from SAS Institute, and there are known errors
in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2;
While many MXG programs (accidentally) will still execute under
V8.2, I cannot guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
If you are absolutely stuck on V8, you need to copy MXG member
V8GETOBS into USERID.SOURCLIB and rename to VGETOBS.
MXG Software has not executed under SAS V6 in many years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
SAS V8 or later, but any of those data libraries can be read or
updated by the SAS Versions that MXG Supports, above.
For SAS Version V9.3:
SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note
SN43828 is REQUIRED. See text of Change 29.159.
With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions
26.03 or later execute under SAS V9.3 on all platforms.
SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and
SAS V9.4 are interchangeable and can be read/written by any of
those versions, provided they are on the same platform.
BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the
same "platform" and attempting to read/use the FORMAT catalog
created on one of those "platforms" on the other "platform"
will error out to remind you of that difference!
SAS V9.4 did change some V9.3 ODS processing defaults and syntax
that might cause errors with MXG 29.05 or earlier; MXG 29.06,
Change 29.160 documents the major revisions made in MXG to fully
support ODS, and MXG 29.06 is STRONGLY recommended for ODS with
SAS V9.3 or SAS V9.4.
For (Archaic) SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, SAS changed the DSNAMES for some of the SAS libraries,
so you do need to use the new MXGSAS92 JCL Procedure for MXG,
but it still uses the CONFIGV9 configuration file.
****************************************************************
However, NEW, and documented in Change 27.356, with SAS V9.2+:
The standard SAS JCL Procedure can be used for MXG:
// EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)'
//MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR
instead of using the MXGSAS92 JCL Procedure example.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
and with NO ERRORS reported.
Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a
new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return
code). That warning is harmless (to MXG code) and all MXG
created SAS datasets were correct, even with that warning.
The ONLY exposure was ONLY on z/OS, and ONLY if condition code
tests are used in your MXG jobstreams.
SAS Version 9.2 requires z/OS 1.7 or later, both officially as
documented by SAS Institute, and actually as V9.2 fails with 0C4
under z/OS 1.4.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
For (back-level!) SAS V9.1 or V9.1.2 on z/OS:
SN-013514 is REQUIRED to be able to read datasets that were
created by V6SEQ (tape) engine.
SN-012437 is REQUIRED to prevent creation of corrupt/unreadable
datasets with tape engines V7SEQ, V8SEQ, or V9SEQ.
Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT
SAFE without those two hot fixes, and if you do NOT have those
two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9.
With MXG 23.02 or later, V9SEQ is the default sequential engine
specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2
you MUST install the two hot fixes listed above.
For SAS Version 8.2, HotFix Bundle 82BX08 (or later) was required
as an absolute minimum level when that SAS Version was last
supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
Sequential Engine Status:
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9.
V8SEQ was always safe under SAS V8.2, but it wasted CPU time
by always compressing when writing in tape format.
V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ
should no longer be used, as it does not support long
length variables.
GENERAL STATEMENT FOR MXG QA TESTS AND SAS VERSIONS:
MXG QA tests are executed with V9.4, on z/OS, on Windows TEN and
Linux on 64-bit hardware, but MXG users execute MXG on MANY
(ALL??) SAS platforms, including AIX, Linux, and other 'nix'
variants, on many different hardware platforms, and since they all
work we don't need to list them. If SAS executes so does MXG.
Prior QA tests have been run with all SAS releases available at
that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880,
and on HP-UX v11.11 model rp5470, confirming full compatibility.
MXG should execute under ALL SUPPORTED SAS VERSIONS on EVERY SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
III. WPS Version requirement information:
WPS Version 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.11.
1. Incompatibilities introduced in MXG 36.36:
a- Changes in MXG architecture made between 36.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 36.36 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.
ANAL9914 36.232 SMF99 ST 14 Processor Topology Report Enhanced.
ANALCAPD 36.042 ERROR: FOUND "IF" when the CEC= option was used.
ANALID 36.081 Support for four-digit SMF Record type reporting.
ANALRMFR 36.203 CPU report with INTERVAL=HOUR was incorrect.
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.
ASUMCICR 36.226 Major revision to CICS RESPONSE TIME SLA reports.
ASUMCICR 36.226 Major revision to CICS RESPONSE TIME SLA reports.
ASUMUOW 36.107 Using ROLLUPS is useless with ASUMUOW, suppress DB2.
BLDSMPDB 36.242 Protection for AUTOALOC=YES and FIRSTRUN=YES
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+
DOCVLONG 36.247 Utility to create DOCVER with all info on one line.
GRAFMSU 36.204 Plots/Tabulate of MSU 4HR usage and capacity.
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.
TECHNOTE 36.209 APARs of interest for z/OS.
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.
TYPE102 36.212 Protection for IFCID 376 invalid offsets STOPOVER.
TYPE102 36.251 Support to populate T102S126 for DB2 102 IFCID 126.
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.
TYPE110 36.220 Variable WTOTIOTM could exceed ELAPSTM
TYPE110 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT
TYPE110 36.244 CICS Variable D2GDB2ID added to CICDB2GL BY list.
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
TYPE119 36.230 ZERT SMF 119 Subtypes 11 and 12 minor corrections.
TYPE119 36.250 New variables added to TYP11952 subtype 52 dataset.
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.
TYPE122A 36.207 Support for zExplorer SMF 122 Subtype 2.
TYPE21 36.218 Support for APARs OA52915 and OA52940, 4 byte counter
TYPE30 36.012 The created GMTOFF30 could be .01 seconds plus/minus.
TYPE30 36.150 Support for APAR OA54589, OSPROTECT, TRUSTED.
TYPE30 36.175 Support for SMF 30 User Key CSA RAXFLAGS OA53355.
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.
TYPE7072 36.208 Support for APAR OA56011 for TYPE70 OSPROTECT.
TYPE70PR 36.039 TYPE70PR variable LPARZIPS, online zips, added.
TYPE70TR 36.003 New 70 Tenant Resource Group TRG updated/validated
TYPE72GO 36.215 Variable MSUSOFT, Software MSU frequently missing.
TYPE72GO 36.253 MOBILE Service Units CPU Time not in CPUTM variable.
TYPE72TR 36.003 New 72 Tenant Resource Group TRG updated/validated
TYPE73 35.010 TYPE73 dataset, variable CHFXRATE slightly wrong.
TYPE74 36.211 TYPE749 variables added and corrected.
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.
TYPEBE97 36.217 Support for new BE97 subtype 6 and subtype 22 update
TYPEBETA 36.015 ERROR when TYPEBETA and TYPE70 used together.
TYPEBETA 36.074 Variables BETALOG reversed, subtype 51 doesn't match.
TYPEBETA 36.199 Beta 93 Subtype 51 and subtype 22 updates.
TYPEBETA 36.246 BETA 93 Version 6.2.0 updates subtypes 0/22/25/50/59
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.
TYPECMFV 36.173 Support for Mainview MVS History Records new datasets
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.
TYPEIMS 36.238 MXG 36.11 protection for IMS 14.1 IMS56FA offset.
TYPEMGCR 36.240 Support for MegaCryption MEGACR34, subtype 3 and 4.
TYPEMVCI 36.234 Support for BMC's MainView for CICS(v69) COMPATIBLE.
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.
TYPEPOEX 36.231 Protection for truncated POEX File Segment records.
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.
TYPERMFV 36.201 MXG 36.09, z/OS 2.2 only, ASIxxx text misaligned.
TYPERMFV 36.201 WPS failed ERROR: format '$ CPUPHYAD' invalid
TYPERMFV 36.241 CPC_CECNAME added, ASITRT/TET corrected, MSU ACT.
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.
TYPESTC 36.222 Numerous STC formats were updated with new values.
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.
TYPETMO2 36.236 Support for ASG-TMON CICS for z/OS V4.2 - NO CHANGES.
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
TYPEVMXA 36.198 z/VM VXBYUSR High CPU, records not on same second.
TYPEVMXA 36.221 MONWRITE DEFECT caused large values, LCUPPNUM issue.
TYPEVMXA 36.237 z/VM 6.3 PROBABLE DATA LOSS ABEND MTRSYS 1.04
TYPEWSF 36.132 Support for EOS Version 160 (INCOMPATIBLE).
TYPEXCOM 36.047 Support for XCOM Version 36.02 (COMPATIBLE).
TYPEZCOS 36.174 Support for AutoSoftCapping ZCOS Version 4.2 INCOMPAT
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.
UTILEXCL 36.220 Variable WTOTIOTM could exceed ELAPSTM.
UTILEXCL 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT
VMXGALOC 36.243 Protection for READONLY=YES with FIRSTRUN=NO
VMXGSUM 36.245 VMXGSUM with user's INCODE GT 32756 chars, ABEND.
VMXGSUM 36.249 OBS=0 protection adds non-zero SYSCC Error test.
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.255 WERE IN MXG 36.36 DATED Jan 4, 2019=========
Change 36.255 T102S083 was incorrectly input to the report twice. One
ANALDB2R report line with the correct AUTH CHG type was printed,
Jan 4, 2019 a report line with type that is blank in PMAUD02 report.
Thanks to Henry Boone, GEICO, USA.
Change 36.254 Support for Fast Traversal Index adds these variables to
VMACDB2 DB2STATS dataset:
Jan 4, 2019 QISTTRAVMIN='FTB*THRESHOLD'
QISTFTBCANT='INDEXES*THAT*MEET*FTP CRITERIA'
QISTFTBCAN='INDEXES*THAT*MEET*TRAVERSE OK'
QISTFTBSIZE='TOTAL*MEMORY*ALLOCATION'
QISTINBNUMP='INDEXES*FTB*EXIST*PREVIOUS'
QISTINBNUMC='INDEXES*FTP*EXIST*CURRENT'
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.253 MOBILE Service Units on CP (GP) and SP (zIIP) engines are
VMAC7072 in TYPE72GO and TYPE72TR datasets, in variables R723MSUCP
Jan 3, 2019 and R723MSUSP, but their CPU times were not created, and
May 28, 2019 the GP CPU time is NOT included in CPUTM. New variables
CPUMOBILECP and CPUMOBILESP are created, but the CP CPU
time is still not added into CPUTM at this time. Instead
CPUTM_ALL=SUM(CPUTM,CPUMOBILCP) is created so the values
can be examined and validated; if you have MOBILE work,
please contact support@mxg.com to discuss how this new
new data can be best presented.
May 28: See Change 37.120; CPUTM_ALL=CPUTM, text wrong.
Thanks to Kare Martin Torsvik, EVRY,
Change 36.252 -Cosmetic cleanup of blank variable labels and spellings:
Many VMACNDM: NDMOPSEQ
Jan 3, 2019 VMAC119: DM_LSVLANID,UC_LTEDATE GMTOFFTM
VMAC74 and VMAC79: DEVNR5HEX
VMAC78: IOPDSTX
VMAC89: SMF89NUM was changed to SMF89_NUM
VMACWSF: ACCSTAT, AUDOBJRN
VMACBETA: BETASSI
Thanks to Chris Weston, SAS ITRM, USA.
Change 36.251 Support for DB2 102 IFCID 126, but all fields are (S) for
VMAC102 "serviceability" with no descriptions, and a 4095 byte
Jan 3, 2019 field that is mixed binary and character, but no info.
The R1O is 41 and R1L is 4096 so 4137 bytes are described
and read, but records have 4448 bytes, 311 undocumented.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 36.250 New variables added to TYP11952 Subtype 52 dataset:
VMAC119 SMF119ML_IP_CONCOUNT=CONNECTION*COUNT'
Jan 3, 2019 SMF119ML_IP_CONFAILCOUNT=CONNECTION*FAILURE*COUNT'
SMF119ML_IP_RCVDBYTES='RECEIVED*BYTES'
SMF119ML_IP_SENTBYTES='SENT*BYTES'
SMF119ML_IP_ESMTP='ESMTP*SUPPORTED?'
Thanks to Randy Shumate, RELX Group, USA
Change 36.249 OBS=0 protection adds test of non-zero SYSCC Error code
VMXGSUM to confirms a prior SAS error had set OBS=0, which can
Jan 1, 2019 cause VMXGSUM to fail, depending on the arguments used,
so VMXGSUM can be gracefully stopped with MXGERRORs that
no dataset was output and to look on the log for ERROR
and correct it.
Change 36.248 CICS variables TASELGTM CPUTONTM CPUTONCN are added to
ASUMCICS the PDB.ASUMUOW dataset from CICSTRAN, and CICS variables
ASUMCICX TASELGTM TASZIPTM CPUTONTM CPUTONCN OFFLCPTM OFFLCPCN are
VMXGUOW added to PDB.CICS created from PDB.ASUMUOW by ASUMCICX,
Dec 31, 2018 or created from CICSTRAN.CICSTRAN by ASUMCICS, but read
the comments in ASUMCICS that suggest ASUMCICX is better.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.247 A utility program to create a copy of the DOCVER file
DOCVLONG with all info on a single line for each MXG variable. MXG
Dec 27, 2018 variable names can be the 32 character max SAS allows, so
DOCVER descriptions are split if the name is 9 or more.
This program creates 94-byte records for each variable.
Thanks to MP Welch, Bank of America, USA.
====== CHANGES THRU 36.246 ARE IN MXG 36.12 DATED Dec 25, 2018==========
Change 36.246 BETA 93 Version 6.2.0 updates for subtype 0/22/25/50/59.
VMACBETA Versions 4.x.x and earlier may not be supported, contact
Dec 21, 2018 MXG Support if you are still at that BETA93 level.
Contact Support if you have other 6.2.0 subtypes so they
can be validated and supported.
Thanks to Robert Gilbert, BNP Paribas Fortis, FRANCE.
Change 36.245 MXG 36.05-36.11, VMXGSUM fails if user option INCODE text
VMXGSUM exceeds 32756. Change 36.109 added detection of "BY" in
Dec 19, 2018 your VMXGSUM INCODE= argument, but 32K is the limit that
is permitted by the %INDEX function. Now, INCODE string
is compressed of blanks to mitigate that length issue and
the test for BY is only executed if resultant length is
LT 32755. MXGWARN messages are written to the log at 30K
length, suggesting the use of INCODE1= option if needed.
Note that the counts of INCODE length can be different
between z/OS and ASCII.
Thanks to Bill Davis, TransAmerica, USA.
Change 36.244 CICS Variable D2GDB2ID is added to the BY List for the
VMAC110 NODUP PROC SORT of dataset CICDB2GL, which may be needed
Dec 17, 2018 for NODUP protection.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.243 If you specified READONLY=YES (which suppresses the aging
VMXGALOC of old directories) and a directory did not exist, it was
Dec 15, 2018 created but not populated. This could cause dataset not
found errors but suppressing that creation could cause
LIBNAME statements to fail. Now, VMXGALOC detects all of
these conditions and only allocates the LIBNAMES that are
found and does not create new ones with READONLY=YES and
FIRSTRUN=NO.
Change 36.242 Using BLDSMPDB with AUTOALOC=YES does two things. First,
BLDSMPDB it allocates all of the directories needed to satisfy the
Dec 15, 2018 parameters you specified - 5 weeks, 1 month, 7 days, etc.
Then at the end of the daily processing it makes a 0 OBS
copy of all of the datasets contained in the PDB. But if
you ran (incorrectly) with FIRSTRUN=YES a second time,
all of those datasets were set to 0 OBS by this process
(intended to prevent DATASET NOT FOUND errors when
running a weekly or a monthly process). Now, with
FIRSTRUN=YES, it first looks to see if there are any
datasets in the libref and if there are any datasets
present, it's assumed you did not really mean it, it
prints a warning message, and bypasses the 0 OBS copy.
Change 36.241 -Variables CPC_CECNAME GEIIMDL GEIMODEL kept in several
ADOCRMFV more ZRBxxx datasets where they are likely to be useful.
ASMRMFV -The original MXG01 record written at CLOSE is now split
EXZRBAS2 into an MXG01 written at VSAM OPEN, so the CPC_CECNAME
IMACRMFV could be captured for all RMF III datasets (it's kept
VMACRMFV kept where it makes sense). and an MXG02 record written
Dec 18, 2018 at CLOSE with those statistics.
Dec 23, 2018 -Datasets ZRBAS1 and new ZRBAS2 decode the MXG01 and MXG02
records.
-ZRBASI variables ASITRT/ASITET are 1024 microsecond units
but weren't multiplied by 1024. ASIDCTIA_S is 128 usec
but wasn't multiplied by 128.
-New ASIPHTCP='ENCLAVE*ON*GP*TIME=ASIPHTMA-ASIPHTZI is
created to complete the CPU Schematic in ZRBASI:
<------------GP------------><----ZIIP---->
<--ASICPUTA--><--ASIPHTCP--><--ASIPHTZI-->
0.083 0.048 37.692
0.131
ASIPHTMA=37.740 ASITRT/ASITET=29.696
-In dataset ZRBLCPLPAR, the CPC Capacity report, the value
under MSU ACT is the variable ZRBLCPCPUMSUHR, but that is
the interval MSU extended to an hour by MSU*3600/DURATM
so it is NOT the 4HR MSU value.
-Incremental improvements and some fixes.
-Positioning for a future new filtering feature.
-FROMTIME= and TOTIME= now support optional seconds for
time values in ASMRMFV. The time format used depends on
the number of digits coded as follows:
# Digits Time Result
-------- ----------------------------
0 RMFV057I NULL VALUE message
1 000M00
2 00MM00
3 0HMM00
4 HHMM00
5 0HMMSS
6 HHMMSS
> 6 RMFV004E ERROR message
Example Full Equivalent Time
--------------- --------------- --------
FROMTIME=1 FROMTIME=000100 00:01:00
FROMTIME=12 FROMTIME=001200 00:12:00
FROMTIME=123 FROMTIME=012300 01:23:00
FROMTIME=1234 FROMTIME=123400 12:34:00
FROMTIME=12345 FROMTIME=012345 01:23:45
FROMTIME=123456 FROMTIME=123456 12:34:56
-Seconds are NOT supported in Relative Time values such as
FROMTIME=*-nnS because this time offset unit from the
current time is too small to be of practical use when
building a PDB. The minimum Relative Time is 1 minute.
-Origin message RMFV009I for each RMF III data set
processed will now include the CPCNAME (aka CECNAME) for
z/OS Release 3.3 and up. If the LPAR is running under
z/VM then the CPCNAME will display as VMGUEST. For lower
z/OS releases the CPCNAME shows as N/A as RMF III does
not track this information at lower levels.
-New information only message RMFV057I KEYWORD VALUE IS
NULL issued when an ASMRMFV keyword has no value
assigned. For example, FROMDATE= . Before this change
the keyword would be ignored with no user notice.
-Warning message RMFV085W is now issued when a filter or
or parameter requires a specific RMF III table, but the
table has not been selected.
Avoid this message by specifying all desired RMF III
tables first before any other parameters that need them.
For example, ASIJOBNAME=MYJOB11 requires the ASI table.
-Improved display format when a single character error is
detected showing both EBCDIC and hexadecimal values for
the character.
-Initialization message RMFV001I now shows the size in
bytes of the step level program used to invoke ASMRMFV
(usually ASMRMFV itself).
-New message RMFV091I is issued when the IBM modules
ERBR3DEC (RMF III Decompression) or IGGCSI00 (Catalog
Search Interface) are loaded into the user region.
Warning message RMFV091W is issued if the module cannot
be identified as an IBM module. In this case this could
be a duplicate naming problem with a third party product.
-MXG table MXG01 has been split into two tables for each
RMF III data set processed. MXG01 contains VSAM data set
Open statistics and MXG02 contains VSAM data set Close
Statistics. These both appear in the ASMRMFV log in
Detail and Summary reports.
-Former message RMFV075W is now message RMFV090W.
RMFV075* is now used for table id mismatch errors.
ASMRMFV errors corrected:
-Error message RMFV005E could be incorrect when more than
one ASMRMFV parameter appeared in one SYSIN record.
-Messages RMFV012I and RMFV013I could show incorrect GMT
offset values for the last sample range and last selected
times.
-Space message RMFV031I always showed an EF (Extended
Function) VSAM type even for non-EF VSAM data sets.
-Message RMFV035* showed an incorrect reason in ASMRMFV
Summary report when an SPG table Internal Error was
detected.
-Except for the DSIG3 table any RMF III table id mismatch
errors now result in an Abend U0998 Reason Code 2. A
table id mismatch is a serious non-recoverable data
error. A DSIG3 error can be recovered by processing the
next RMF III data set but is still very undesirable.
-Each ASMRMFV parameter now has a PLACEMENT section in
documentation to explain where in the input stream it
should appear.
-Numerous documentation updates in:
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 8 "Error Handling Parameters"
Section 12 "Messages"
Section 26 "ASMRMFV and MXG PDB Data Relationships"
Change 36.240 Support for MegaCryption new MEGACR34 dataset with new
EXMGCR34 subtype 3 and 4 replacing old records but keeping all of
IMACMGCR the original fields and adding these new variables:
VMACMGCR MGCRFUNC='FUNCTION*E ENCRYPT*D DECRYPT ?'
VMXGINIT MGCRALGO='ALGORITHM*USED'
Dec 8, 2018 MGCDSSUF='ADRDSSU*DUMP*RESTORE*COPYDUMP'
MGCRDSN1='INPUT*DSN'
MGCRVOL1='INPUT*VOLSER'
MGCRSTY1='INPUT*FILE*TYPE'
MGCRDSN2='OUTPUT*DSN'
MGCRVOL2='OUTPUT*VOLSER'
MGCRSTY2='OUTPUT*FILE*TYPE'
Thanks to Jennifer D. Ayers, West Virginia State Goverment, USA.
Change 36.239 Enhanced to display all used parameters, only on the
VMXG2DTE first execution in a SAS session. On subsequent execute
Dec 7, 2018 DDIN DDOUT PDB DATASET and INITIT are displayed only if
Dec 23, 2018 they are different and others only if present.
Thanks to Tom MacCabe, Dominion Energy, USA
Change 36.238 IMS 14.1 IMS56FA INPUT EXCEEDED RECORD ABEND due to an
VMACIMS invalid offset value of 2500 in DLRRXTOF/TPCEXTOF in a
Dec 7, 2018 record that has only 572 bytes. Previous 14.1 56FA data
Dec 23, 2018 didn't populate that offset to that new TPCX segment, but
the 64-byte segment was present but not input. Since the
segment contains nothing of value, rather than protecting
for an invalid offset, the code for the TPCX segment is
bypassed awaiting data from a site that wants the TPCX
data. This is not worth a PMR at this time.
-You can use this logic in your IMS job's SYSIN safely
since this segment is at the end of the IMS LOG record:
//SYSIN DD *
MACRO STOPOVER MISSOVER %
%INCLUDE SOURCLIB(TYPSIMST);
but you should remove that MACRO statement when you
update MXG.
-New message if 56FA record IMSVERSN value is not equal to
your site's _IMSVERS old-style macro value that you set
in the job's SYSIN - see TYPEIMST/TYPSIMST JCL examples.
But _IMSVERS is NOT USED in the 56FA records; it is used
only in old IMS log records hex 07 08 0A 31 35 36 40 59.
Dec 23, 2018: Variable TPCXLEN re-kept in IMS56FA always
a missing value until IBM populates the segment.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.237 z/VM 6.3 MONWRITE record ABEND at HCPCPEID='30061701:
VMACVMXA PROBABLE DATA LOSS MESSAGE exposed incorrect new SKIP
Dec 6, 2018 logic for 6.4 that failed with 6.3 in MTRSYS, 1.04..
SKIP logic revised to protect old versions.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
====== CHANGES THRU 36.236 ARE IN MXG 36.11 DATED Dec 3, 2018==========
Change 36.236 Support for ASG-TMON CICS for z/OS V4.2, is there now, as
TYPETMO2 there were no changes to the performance records.
Nov 28, 2018
Change 36.235 Support for IBM CICS SMF 110 CICS/TS 5.5 INCOMPATIBLE,
VMAC110 as is ALWAYS the case for CICS because they insert
UTILEXCL fields in existing records. You can use the VMAC110
Nov 30, 2018 with this Change (36.235), if you have records, with no
excluded fields and no optional segments, but if you
have either (the existence of a tailored IMACEXCL member
in your "USERID.SOURCLIB" tailoring proves you do), you
will need to use UTILEXCL from this Change to create a
new IMACEXCL that knows about these new variables that
were INSERTED in Subtype 1 records:
NJSAPPNM='NODE.NJS.APPPLICATION*NAME'
SOCONMSG='FIRST*MESSAGE*PROCESSED'
WBURIOTM='URI*WEBB OPEN*WAIT*TIME'
WBURIOCN='URI*WEBB OPEN*WAIT*COUNT'
WBURIRTM='URI*WEBB RECV*WAIT*TIME'
WBURIRCN='URI*WEBB RECV*WAIT*COUNT'
WBURISTM='URI*WEBB SEND*WAIT*TIME'
WBIRISCN='URI*WEBB SEND*WAIT*COUNT'
WBURVITM='URI*INVOKE*SERVICE*WAIT*TIME'
WBURVICN='URI*IINVOKE*SERVICE*WAIT*COUNT'
Yes, you need MXG 36.11 for CICS/TS 5.5 because fields were
inserted into SMF 110 CICSTRAN records and using old MXG will
have trashed values due to the misalignment, but MXG could run
and only print error messages, which might be false positives,
or could execute with no errors nor log messages, especially if
you have a tailored IMACEXCL, but your CICSTRAN dataset will
still be invalid.
Change 36.234 Support for BMC's MainView for CICS(v69) with support for
VMACMVCI CICS/TS 5.5 COMPATIBLY added these variables to DMRDETL:
Nov 30, 2018 T6E72XCT='72 EXTENSIONS'
T6ESOCNM='FIRST*MSG*PROCESSED'
T6EUROPT='URI*WEB OPEN*WAIT TIME'
T6EUROPF='URI*WEB OPEN*WAIT FLAG'
T6EUROPC='URI*WEB OPEN*WAIT COUNT'
T6EURRPT='URI*WEB RECV*WAIT TIME'
T6EURRPF='URI*WEB RECV*WAIT FLAG'
T6EURRPC='URI*WEB RECV*WAIT COUNT'
T6EURSPT='URI*WEB SEND*WAIT TIME'
T6EURSPF='URI*WEB SEND*WAIT FLAG'
T6EURSPC='URI*WEB SEND*WAIT COUNT'
T6EWSIVT='URI*INVOKE*SERVICE**WAIT TIME'
T6EWSIVF='URI*INVOKE*SERVICE**WAIT FLAG'
T6EWSIVC='URI*INVOKE*SERVICE**WAIT COUNT'
T6ENJAPN='NODE.JS*APPLICATION*NAME'
Change 36.233 Change 36.211 changed the KB definition to 1000 based on
VMAC74 an IBM document that is now confirmed as misleading and
Nov 27, 2018 the multiplier of 1024 is restored for these variables:
R7491BPC R7491BPS R749DCTBYTR R749FPGBYTR
R749FPGBYTS R749FPGCOBS R749FPGDCBS R749ICTBYTR
R749PCIBYTR R749PCIBYTT R749PCIDMAR R749PCIDMAW
-APAR OA55984 corrects high zEDC execution time and SSQ
values when a time stamp wrapped.
Change 36.232 The SMF 99 Subtype 14 Processor Topology Report provided
ANAL9914 by RAY back in Change 33.139 has a new version by Jim
Nov 29, 2018 and the report program is now a %MACRO ANAL9914 so you
can select CECTYPE and SYSTEM and REPORT with
%ANAL9914(CECTYPE=Z14,SYSTEM=SYS1 SYS2,REPORT=JIM);
REPORT=JIM uses PROC SGPANEL (SAS only) for prettiness!
Thanks to Jim Horne, Lowe's Companies, USA.
Thanks to Raymond J. Smith, OPTUM, USA.
Change 36.231 Truncated POEX record caused INPUT STATEMENT EXCEEDED now
VMACPOEX the short record is detected and reported on the log. the
Nov 26, 2018 record had POEXNUM=35 File Segments expected, but the
record only had room for 15.
Thanks to Jack Hyde, UHC, USA.
Change 36.230 -SMF 119 ZERT subtype 12 dataset TYP11912IPOSEC was out of
VMAC119 alignment for these last 4 variables: ENCAPMODE/AUTHPROTO
Nov 26, 2018 were incorrectly input as $CHAR2.
S119SS_IPS_ENCAPMODE S119SS_IPS_AUTHPROTO
S119SS_IPS_AUTHALG S119SS_IPS_ENCALG
-MXG ZERT subtype 11 dataset TYP11911's GMTOFFTM create is
valid with current records, but 2017 records had missing
values that caused incorrect values, because SAETIME was
often missing and on a different time zone.
Thanks to Luis Mendoza, Black Knight, USA
====== CHANGES THRU 36.229 ARE IN MXG 36.10 DATED Nov 21, 2018==========
Change 36.229 If you specified a dataset name in ASCII and did not
UTILBLDP change the value of ECHO= to NO, a syntax error was
Nov 21, 2018 generated when the created code was read back in to be
displayed. If you used a filename (preferred) there was
no error.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.228 The MXGWARN:MISSING TYPE70/TYPE70PR could be printed for
VMAC7072 ICF-only LPARs, because MXGCIN was set to 'VM' in very
VMXG70PR old logic, prior to SMF70CIN being provided by IBM.
Nov 29, 2018 Now, MXGCIN is always set to SMF70CIN in VMAC7072, and
the ICF LPARs with SMF70STN non-blank are skipped in
VMXG70PR.
Thanks to Scott Barry, SBBWorks Inc., USA.
Change 36.227 New IHDRCTLT "Header" Exit created for record selection,
IHDRCTLT and macro variable &MACCTTH created for instream use.
VMACCTLT Missing value messages for dates eliminated.
VMXGINIT
Nov 16, 2018
Thanks to Randal Schlueter, FirstData, USA.
Change 36.226 Major revision to CICS RESPONSE TIME SLA MEMBER.
ASUMCICR
Nov 20, 2018
Change 36.225 Documentation only. Examples clarified.
ANALCAPD
Nov 16, 2018
Change 36.224 Documentation only. Examples added to select specific
UTILBLDP subtypes of records to be added to PDB, Example 2 was.
Nov 16, 2018 missing quotes.
Change 36.223 -PMACC02 could generate an UNITIALIZED variable message
ANALDB2R for PACKTYPE.
Nov 19, 2018 -Variable QB3TDIO was misspelled in PMSTA02 causing
another unitialized message.
Change 36.222 Numerous STC formats were updated with new values for
FORMATS HSC 7.3. Calculation of MSZ with CTP test, and new
VMACSTC $MGSTCRR format added, so please update FORMATS.
Nov 21, 2018
Thanks to Randy Hewitt, HPE, USA.
Change 36.221 MONWRITE defect, LCUPPNUM was NOT changed and an interval
VMACVMXA was skipped when the number of IFL engines was changed
Nov 15, 2018 from 5 to 3. MXG's attempt to detect wrap was invoked
causing large values in LCUCACTM LCUCLPTM LCXCMTIT.
The logic was revised to detect and delete the defective
interval in VXSYTCUP. A PRM will be raised with IBM.
Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
Change 36.220 -Variable WTOTIOTM could exceed ELAPSTM because WTWEIOTM,
UTILEXCL is included in RMISIOTM, and -SUM(WTDISPTM,WTSYIOTM);
VMAC110 are overlapped with the sum of all of the other waits.
Nov 20, 2018 -The WTOTIOTM created in UTILEXCL (when you have EXCLUDED
fields) did not include these wait variables:
DSAPTHTM DSCHMDTM DSMMSCTM DSTCBMTM FCVSWTTM
GNQDELTM ISALWTTM JVMSUSTM MAXJTDTM MAXOTDTM
MAXSTDTM MAXXTDTM PTPWAITM RQPWAITM RQRWAITM
RRMSWATM RUNTRWTM SRVSYWTM SYNCDLTM TCALWTTM
TDELWTTM TDILWTTM
but only one, DSCHMDTM, is populated.
-This is the new code for WTOTIOTM
WTOTIOTM=SUM(
DSPDIOTM,ENQDIOTM,GNQDELTM,WTICIOTM,WTLMIOTM,
WTWCIOTM,RUNTRWTM,SRVSYWTM,RQRWAITM,
RQPWAITM,SYNCDLTM,MAXOTDTM,MAXJTDTM,MAXSTDTM,
MAXXTDTM,RRMSWATM,PTPWAITM,RMISIOTM,JVMSUSTM,
DSTCBMTM,DSMMSCTM,WTDWIOTM,DSCHMDTM,FCVSWTTM,
ISALWTTM,TCALWTTM,TDELWTTM,TDILWTTM,DSAPTHTM);
IF (WTOTIOTM GT SUM(WTDISPTM,WTSYIOTM)) AND
(WTOTIOTM-SUM(WTDISPTM,WTSYIOTM)) GT 0 THEN
WTOTIOTM=WTOTIOTM-SUM(WTDISPTM,WTSYIOTM);
Thanks to Jim Franklin, DXC Technology, USA.
Change 36.219 Misspelling of miscellaneous corrected in 15 of 876 uses,
Many and many other spelling errors have been corrected.
Nov 13, 2018
Thanks to Michael R. Novak, USPS, USA.
Change 36.218 Support for APARs OA52915 and OA52950 for SMF 21 counts
VMAC21 to use the 4-byte 3590 counters instead of the original
Nov 13, 2018 3-byte 3490 counters is already in place since the 4-byte
counters were added. A minor non-impacting change to
the test that sets the 3-byte counters with FFFFFFx to a
missing value was made.
Change 36.218 Reserved Change Number.
Change 36.217 -Support for new subtype 6 BETA97 record, which creates
FORMATS two new datasets:
EXTYB976 DDDDDD Dataset Description
EXTYB97S TYB976 BETA9706 BETA97 ST 06
IMACBE97 TYB97S BETA9706D BETA97 ST 06 DATASET
VMACBE97 -Support for the Relocate data in subtype 22 BETA972REL
VMXGINIT now decodes the expiration date fields to SAS dates and
Nov 9, 2018 the B97RELTY values are decoded..
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 36.216 -ASMRMFV IDERR subroutine upgraded to display MINTIME
ASMRMFV interval when a RMF III table id mismatch occurs as
Nov 8, 2018 RMFV075E messages.
-Extraneous ')' in message RMFV008I when processing a GDG
for RMFBSAM.
-NOSHOWZERO option not showing any table detail lines
except for MXG00.
Thanks to Randall Schleuter, First Data Corporation
Change 36.215 Variable MSUSOFT, the interval Software MSU in TYPE72GO
VMAC7072 for each Service/Reporting Class, can often be a missing
Nov 7, 2018 value due to incorrect logic used to populate the
CECSUSYSTEM and CECSUVALUE arrays from the preceding type
70 to provide SMF70CPA for the MSU calculation. If there
is no preceding 70 from this system, "new" variable
R723CPA is used so MSUSOFT will always be populated. And,
if it is really the 4 Hour Average value you want, member
ASUM4HRS will create that value for any variable in any
dataset!
Thanks to Thomas Heitlinger, FIDUCIAGAD, GERMANY.
Change 36.214 If OPTIONS OBS=0 has been set by SAS due to an error,
VMXGSUM VMXGSUM produced unclear messages and zero obs created.
Nov 7, 2018 Now, OBS=0 is detected and VMXGSUM shut down with error
message that is clear.
Thanks to Glen Bowman, Wakefern, USA.
Change 36.213 Cosmetic. Non-impacting NOTE: _UN98309 UNINITIALIZED is
VMAC110 removed.
Nov 7, 2018
Change 36.212 Protect for DB2 Trace IFCID 376 invalid offset STOPOVER.
VMAC102 One record with two offsets (SC_OFF and SQL_OFF) that
Nov 6, 2018 were larger than the record LENGTH caused the error.
Offset lengths are now compared to LENGTH and if larger,
log messages are printed.
QW0376SC_OFF=48392 LENGTH=5210 IFCID376 SC ERROR
QW0376SQL_OFF=27283 LENGTH=5210 IFCID 376 SQL ERROR
These offsets, added in DB2 V11, are after VERSION but
Version Length is ZERO in all records, and the first
eight bytes of VERSION are nulls, so possibly the
offsets are in those first eight bytes, so I've added
variable VERSION1ST to display their value.
A PMR will be raised with IBM DB2 Support.
Thanks to Glen Bowman, Wakefern, USA.
Change 36.211 -These AVG and STD values were not created in TYPE749:
VMAC74 R7491DISAVG='AVG*INDIVIDUAL*DEFLATE*INPUT*BYTES'
Oct 31, 2018 R7491DISSTD='SSQ*INDIVIDUAL*DEFLATE*INPUT*BYTES''
Nov 3, 2018 R7491DOSAVG='AVG*INDIVIDUAL*DEFLATE*OUTPUT*BYTES'
Nov 28, 2018 R7491DOSSTD='SSQ*INDIVIDUAL*DEFLATE*OUTPUT*BYTES''
R7491IISAVG='AVG*INDIVIDUAL*INFLATE*INPUT*BYTES'
R7491IISSTD='SSQ*INDIVIDUAL*INFLATE*INPUT*BYTES''
R7491IOSAVG='AVG*INDIVIDUAL*INFLATE*INPUT*BYTES'
R7491IOSSTD='SSQ*INDIVIDUAL*INFLATE*INPUT*BYTES''
and these variables are now uncommented and kept
/* SSQ VARIABLES NOW COMMENTED OUT SINCE STD EXIST
R749FSQE R749FSQQ R7491DIS R7491DOS R7491IIS R7491IOS*/
This link https://www.ibm.com/support/knowledgecenter/en/
SSLTBW 2.1.0/com/ibm.zos.v2r1.erbb200/erbb200205.htm
with PCIE Function Activity overview calculations show
that the "MegaBytes" and "KiloBytes" are 1000 and not the
1024 per KiloByte that IBM uses in other 74 subtypes, so
the 1024s in subtype 9 code are changed to 1000.
-Nov 28: Change 36.233 reverted back to 1024 as IBM has
confirmed the KB are 1024 and not 1000.
-R749FPGBPRT is now the in-use buffer percent of memory.
-R749BPC is relabeled AVERAGE*IN-USE*BUFFER*SIZE in bytes.
-R749PCIUTIL was incorrectly calculated.
Thanks to Heimir Hauksson, Barclays, ENGLAND
Anthony T. Sofia, IBM, USA.
Change 36.210 The _N119 "Null Macro" missed TYP11924 and TYP11945 so
VMAC119 they were created when not wanted when _N119 was used.
Oct 31, 2018
Change 36.209 Documentation of APARs of interest for z/OS:
TECHNOTE -APAR OA55602 RMF PP WLMGL TOTAL STORAGE INVALID after
Oct 31, 2018 APAR OA52694; impacted only the TOTAL STORAGE and the
STORAGE SHARED in RMF Report, 1000 times too large.
-APAR OA53459 SMF TYPE 65 IS MISSING THE HLQ FOR THE
GENERATION DATA SET WHEN DELETE GDG FORCE PURGE IS
ISSUED on z/OS 2.2, not on 2.1. 2.3 not mentioned.
-OA52950 3490 CHANNEL (PRE-COMPRESSION) BYTES AND DEVICE
(POST-COMPRESSION) BYTES BEING REPORTED INCORRECTLY.in
RMM (MXG TYPEDGR) and SMF 21 statistics, too high.
-OA54992 SMSVSAM SMF TYPE 42 SUBTYPE 15 RECORDS MAY
INCORRECTLY RECORD ABOVE THE BAR BMF STATISTICS FOR DATA
SETS. Occurs with a data set is assigned to a dataclass
with above the bar usage set to yes, but the data set is
not actually using above the bar buffers, which happens
if RLSABOVETHEBARMAXPOOLSIZE is not set or if the change
was made and the data set hasn't gone through a CLOSE to
refresh the information. LOCAL FIX: Ensure data sets
assigned to data class with above the bar usage are
using above the bar buffers.
-APAR OA56000 SMF RECORD LENGTH FOR SMF TYPE 98 HFTS
RECORDS EXCEEDS THE MAX ALLOWABLE X'7FF4' (32,756).
Subtype 1 are defined as x'8000' (32,768) and these
records have caused CA SMF DIRECTOR product to fail and
reject these records as invalid.
-APAR PI96628 MQ V9: SMF116 RECORDS CONTAIN INVALID
VALUES IN FIELD WTASMSTC, time spent in IXLLSTM call,
and WTASSSTC for CICS and CHINIT connections accessing
shared queues.
-APAR PH99111 WMQ V9.0 SMF116 LATENCY RECORD FIELDS SET
TO ZERO FOR SOME QUEUES. Fields MAXLATNT MINLATNT and
TOTLATNT are zeroed after migrate to Version 9.0, for
some queues.
-APAR OA55594 SMF78 SUBTYPE 3 SUPERVPAV VALUES NOT
REPORTED DUE TO R783DST BIT 7 FLAG NOT BEING SET
R783XIND, causing I/O Queueing Activity Report to be
missing the Alias Management Groups and/or the Logical
Control Units section is missing the Alias Management
Group field. Happens when the first device on a
SuperPAV XPAV Control Units is offline. LOCAL FIX:
Vary the first device on all SuperPAV XPAV Control
Units online.
-APAR OA55292 RMF FICON DIRECTOR STATISTICS REPORT HAS AN
OCCASIONAL VERY LARGE VALUE FOR A PORT BANDWIDTH, READ
OR WRITE. APAR IS OPEN.
Change 36.208 Support for APAR OA56011 which added these two variables
VMAC7072 to the TYPE70 dataset:
Oct 31, 2018 SMF70LACCR='LONGTERM*MSU*DFSMS*DATASET*ENCRYPTION'
SMF70OS_PRTCT='OSPROTECT*VALUE'
Change 36.207 Support for SMF 122 Subtype 2 zExplorer IBM Dependency
EXTY122B Based Build, DBB, Release 1.0.3, which records usage of
IMAC122A the DBB toolkit by z/OS users, creates new dataset.
VMAC122A DDDDDD DATASET DESCRIPTION
VMXGINIT
Oct 30, 2018 TY122B TYPE122B ZEXPLORE DBB DEPEND BASED BUILD
Change 36.206 When the input DD is tape or sequential, VMXGSUM and
VMXGSUM VGETOBS cannot reasonably detect the presence or absence
Oct 28, 2018 of datsets and have always tried to process them but if
DSNFERR was on failed with a dataset not found error.
But, if DSNFERR was set to NODSNFERR it then tried to
process and if the dataset did not exist could generate
UNINITIALIZED variable messages and a 0 OBS output. Now
if VGETOBS detects a sequential LIBNAME and NODSNFERR
MXGNOTEs are produced to let you know what may happen.
Change 36.205 -IBM updated the RMF III SVP table and altered the Service
ASMRMFV Class, Report Class, and Resource Group Information
Oct 26, 2018 Sections.
-The SVP version level was raised from X'03' to X'04.
-Either or both version levels may exist in z/OS 2.3
systems depending on the software currency of z/OS.
-ASMRMFV has been changed to input these Sections using
actual rather than documented lengths.
-The SVP, ASI, ENC, and RCD RMF III tables are all
affected when the SVP version level is X'04'.
-MXG Changes 36.191 and 36.201 support new MXG variables
for the new data in the VMACRMFV member.
-ZEROCPU and ZERODVT parameters were not recognized due
to a length specification error in the parameter table.
Change 36.204 Plots and or TABULATE of MSU capacity GRAFMSU Reports.
GRAFMSU For General purpose CPUs:
Nov 16, 2018 CPC Capacity .
LPAR Rolling 4 hr Avg Usage
LPAR Hourly Usage
LPAR Defined Capacity
LPAR Capacity based on % SHARE
LPAR Capacity based on # CPUs
For IIP and IFA/CBP CPUs:
CPC Capacity .
LPAR Rolling 4hr Avg MSU (Estimated)
LPAR Hourly Usage
LPAR Capacity based on % SHARE
LPAR Capacity based on # CPUs
See doc in the member for examples of usage and see
change 36.156 for examples of wrapping in ODS statements
to create HTML or PDF output.
Change 36.203 CPU report with INTERVAL=HOUR actually was produced at
ANALRMFR number of CPUs*intervals so a CEC with 4 CPUs on a 15
Oct 26, 2018 minute interval showed up with 4 hour intervals. DURATM
is now set to the INTERVAL= specified.
Change 36.202 Used primarily inside of other macros to detect the
VGETOBS existence and other information about SAS datasets. But,
Oct 25, 2018 if you happened to pass incomplete text, like .ASUMCELP
(where it should have been DDNAME.ASUMCELP) you could get
strange errors and an ABEND, due to the period. Now, both
sides are validated, or if only one is, WORK is used as
the DDNAME with the DATASET to become WORK.ASUMCELP.
Change 36.201 -MXG 36.09, z/OS 2.2, only, text classification variables
VMACRMFV (ASICNM ASISCWN AISCRN ASIRNM ASIWNM) in dataset ZRBASI
Oct 26, 2018 could be misaligned. Introduced in Change 36.196.
-Some WPS 4.0 iterations failed with
ERROR: The format name '$ CPUPHYAD' invalid
because WPS didn't like the blank in FMTNAME ' CPUPHYAD'
Removing the blank didn't impact SAS but it healed WPS.
Thanks to Rodger Foreman, Black Knight, USA
Change 36.200 Logic rearranged to put error checking at the top, some
VMXG2DTE additonal error checking added and abort changed to a
Oct 24, 2018 soft landing with error messages.
Thanks to Tom MacCabe, Dominion Energy, USA
Change 36.199 -Beta 93 Subtype 51 variables now output in BETA51 dataset
FORMATS that are also input in BE97 BETA9751D dataset:
VMACBETA BETALCMD='LINE*COMMAND'
Oct 30, 2018 BETARPOS='POINTER*TO*VALUE*AREA'
-BETA 97 subtype 22 variable B97RELTY in dataset BETA9722
has new values decoded by updated FORMAT MGBETET.
-New BETA 97 subtype 6 will create new datasets when test
records are available.
Thanks to Andreas Menne, Finanz Informatik, GERMANY.
Change 36.198 z/VM VXBYUSR High CPU, MRHDRTOD isn't the same second any
VMACVMXA more in VXUSEACT and VXUSEINT datasets, which caused that
Oct 22, 2018 merge to create multiple obs, which caused deaccumulated
VMDTTIME/VMDVTIME to be very large for those intervals.
MXG used MRHDRTOD=FLOOR(MRHRTOD); to truncate to whole
seconds for the merge, as the value was always :00, but
now, the start of the write of the USER records is often
near the end of the 00: second (e.g. 0.999919 microsec)
and the write extends into the :01 second, and sometime
the ACT record is at :00 and INT is at :01, mismatched.
Now, MRHDRTOD=FLOOR(MRHDRTOD)-MOD(FLOOR(MRHDRTOD),10);
is used to force the minute intervals to always be :00 in
the PDB.VXBYUSE MONWRITE dataset.
The MRHDRTOD one minute interval datetime value that is
used to merge VXUSEACT and VXUSEINT datasets to create
VXBYUSR previously happened to always be on the same
second, so using MRHDRTOD=FLOOR(MRHDRTOD) to truncate
that microsecond value to seconds, the merge matched
observations correctly.
However, the newer data shows that there can be a pair of
records with the USEACT record at :00 seconds and the
paired USEINT record at :01 seconds, causing that merge
pair to create multiple observations.
What has happened? The older data shows the start of the
write of the USEACT/USEINT pairs began at 0.885 seconds
after the pop and the write completed after writing all
of them in 478 microsec, in that one second, but the
newer data shows the write didn't start until 0.999 secs
and the 406 microseconds write time ended in the next
second causing ACT at :00 and INT at :01. Some of the
new values don't even start write until the :01 second.
Sept Data:
03:36:30.885294 Minute 36 Second 30 First USEACT
5 microsec
03:36:30.885299 Minute 36 Second 30 Paired USEINT
471 microseconds (write 78 pairs)
03:36:30.885770 Minute 36 Second 30 Last USEACT
2 microseconds
03:36:30.885772 Minute 36 Second 30 Paired USEINT
==> 78 pair written in 478 microseconds for Minute 36.
But new data has pairs with different seconds values:
Oct Data:
09:36:00.999919 Minute 36 Second 00 First USEACT
3 microseconds
09:36:00.999922 Minute 36 Second 00 Paired USEINT
76 microseconds (write 21 pairs)
09:36:00.999998 Minute 36 Second 00 First USEACT
2 microseconds
09:36:01.000000 Minute 36 Second 01 Paired USEINT
324 microseconds (write 65 pairs)
09:36:01.000324 Minute 36 Second 01 First USEACT
1 microseconds
09:36:01.000325 Minute 36 Second 01 Paired USEINT
==> 86 pair written in 406 microsec for minute 36.
Thanks to Graham Harris, RBS, ENGLAND.
====== CHANGES THRU 36.197 ARE IN MXG 36.09 DATED Oct 18, 2018==========
Change 36.197 Support for new TRAD/TRG count variables in TYPE89,
VMAC89 in z/OS 2.4.
Oct 17, 2018 ICN 1662.
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, Lowe's Companies, 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, Lowe's Companies, 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,
Nov 20, 2018 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.
Nov 20: The Informatica fix number for this problem is
PWX-7566 and it will be in code base PWX V10.2.0 Hotfix2
currenly scheduled for Q1 of 2019.
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 -Dec 31: MONTHBL3 was missing a semicolon, found in QA.
Dec 31, 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 IBM macros SMF30RPS,SMF30SDS lengths
not field lengths so it has no impact on MXG.
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 44 new datasets with CMRDETL information.
EXCMFV0C
EXCMFV0D
EXCMFV0F DDDDDD Dataset Description
EXCMFV10
EXCMFV16 CMFV10 CMFV10 Address Space 10 ADRE
EXCMFV17 CMFV16 CMFV16 Lock 16 LKRE
EXCMFV18 CMFV17 CMFV17 VSAN RLS Activity 17 RLRE
EXCMFV20 CMFV18 CMFV18 VSAM RLS LRU 18 RURE
EXCMFV21 CMFV181 CMFV181 DEVICE 83 DLRE
EXCMFV2E CMFV20 CMFV20 COUPLING FACILITY
EXCMFV34 CMFV21 CMFV21 System Summary 21 SLRE
EXCMFV46 CMFV2E CMFV2E Data Set 23 DSRE
EXCMFV47 CMFV34 CMFV34 Unix Process 34 UPRE
EXCMFV48 CMFV46 CMFV46 PROCESS
EXCMFV49 CMFV47 CMFV47 WLM Extended Period 47 MXRE
EXCMFV50 CMFV48 CMFV48 WLM Addr Space/Enclave 48 MTRE
EXCMFV51 CMFV49 CMFV49 WLM Enclave Classify 49 MCRE
EXCMFV52 CMFV50 CMFV50 XCF Path 50 XPRE
EXCMFVES CMFV51 CMFV51 XCF System 51 XSRE
EXCMFV54 CMFV52 CMFV52 XCF Source/Destination 52 XDRE
EXCMFV70 CMFVES CMFVES ES CRITERIA 53 ----
EXCMFV71 CMFV54 CMFV54 WLM Server 54 MWRE
EXCMFV72 CMFV70 CMFV70 System Summary 70 SBRE
EXCMFV73 CMFV71 CMFV71 Device 71 DBRE
EXCMFV74 CMFV72 CMFV72 Address Space 72 ABRE
EXCMFV80 CMFV73 CMFV73 WLM 73 WBRE
EXCMFV81 CMFV74 CMFV74 LPAR 74 LBRE
EXCMFV82 CMFV80 CMFV80 ZFS Aggregate 80 ZSRE
EXCMFVC0 CMFV81 CMFV81 ZFS Cache 81 ZCRE
EXCMFVC1 CMFV82 CMFV82 PCIE Activity 82 PCRE
EXCMFVC2 CMFVC0 CMFVC0 PROCESS C0 PRRE
EXCMFVC4 CMFVC1 CMFVC1 THREAD C1 THRE
EXCMFVCC CMFVC2 CMFVC2 MOUNTED FILE SYSTEM C2 FMRE
EXCMFVCD CMFVC4 CMFVC4 SYSTEM PARAMETERS C4 PMRE
EXCMFVCE CMFVCC CMFVCC PROCESS/TTY CC P1RE
EXCMFVCF CMFVCD CMFVCD VSAM COMMON STORAGE CD P2RE
EXCMFVD0 CMFVCE CMFVCE PROCESS/COMMAND CE P3RE
EXCMFVD1 CMFVCF CMFVCF USS PROCESS CWD CF CFRE
EXCMFVD2 CMFVD0 CMFVD0 MOUNTED FS/MOUNT POINT D0 F1RE
EXCMFVD3 CMFVD1 CMFVD1 MOUNTED FS/MOUNT PARMS D1 F2RE
EXCMFVD4 CMFVD2 CMFVD2 HFS GLOBAL D2 HGRE
EXCMFVFD CMFVD3 CMFVD3 HFS FILESYSTEMS D3 HFRE
EXCMFW18 CMFVD4 CMFVD4 HFS BUFFERS D4 HBRE
IHDRCMFV CMFVFD CMFVFD SCM FD FDRE
IMACCMFV CMFWC0 CMFVC0 PROCESS 18-1 DLRE
VMACCMFV
VMXGINIT -The three files contain these RTIN values:
Oct 30, 2018 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.
-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.
Thanks to Michael Oujesky, DTCC, USA.
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
Nov 11, 2018 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, Lowe's Companies, 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 DCOLDSET:
Aug 25, 2018 DCDCMPTV='COMPRESSION*TYPE*VALID'?
DCDCTYPE='COMPRESSION*TYPE'
See Change 37.064 for revised change. 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.
-Pasted directly from the SAS site to create CSV file:
ods html close;
options obs=15;
ods csvall body='procprintcsvall.csv';
ods markup tagset=chtml body='procprintchtml.html'
(title= 'This Text Identifies Your Content.');
title 'Leading Grain-Producing Countries';
proc print data=grain_production;
run;
ods csvall close;
ods markup tagset=chtml close;
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 Variables added to dataset TYPE70:
VMAC7072 SMF70MDL_CBP SMF70MCR_CBP SMF70NCR_CBP SMF70LAC_CBP
Jul 2, 2018 SMF70CPA_ACTUAL_CBP
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 z/OS 2.4 SMF 30 enhancement adds these fields:
VMAC30 SMF30TIH='HWM*TIOT SPACE*USED'
Jun 11, 2018 SMF30TIS='AVAILABLE*TIOT*SPACE FOR*ENTRIES'
SMF30TIU='CURRENT*TIOT*SPACE*USED'
ICN 1634 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 Companies, 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'
May 20, 2019 DCDKLBL ='ENCRYPTION*KEY*LABEL'
The IBM Documentation does not provide DCDTYPE values to
decode. These fields were added by z/OS 2.3.
-Unfortunately, DCDTYPE was changed from CHAR to NUM in
this change, which will cause ERROR BOTH CHAR AND NUM
if you merge PDBs built with this change with earlier
PDBs. You can use MACRO _KDCODSN DROP=DCDTYPE= % in
your SYSIN in your TYPEDCOL job to eliminate the conflict
to circumvent this badly designed change. May 20/2019.
Thanks to Mike Creech, Black Knight, USA.
Thanks to Robert Hamilton, Fifth Third Bank, 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
Sep 9, 2020 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
-Sep 9 2020: Apparently unused, KEEP list was wrong.
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.
These variables will have missing values in PDB.ASUMCELP;
SMF70CPA SMF70LAC SMF70PAT SMF70WTI SMF70WTS SMF70WTI.
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 Companies, 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);
These are the variables that will have missing values
in PDB.ASUMCECLP and ASUMCEC for those LPARs listed:
SMF70CPA SMF70LAC SMF70PAT SMF70WTI SMF70WTS SMF70WTI.
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.010A Support for z/OS 2.4 SMF 89 Dataset TYPE89R2 new TRG
FORMATS variables SMF89TRGDATATYPE SMF89TRGDATACPU SMF89TRGDATA.
VMAC89 ICN1674.
Jan 16, 2019
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.308
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 61672.
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.
Jun 28, 2019 While GRAFLPAR is supported, it is obsolete and GRAFCEC
should be used instead, as it has superior reports.
Jun 28, 2019: This statement is not true in WPS 4.1.
-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.
Update: See Change 38.033.
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.
Note: See Change 38.034 for revisions.
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.026 for an example when LPARNAME is not
equal to SMF70STN.
See Also Change 37.071 that added INTIME70xx macros.
These are the variables that will have missing values
in PDB.ASUMCECLP and ASUMCEC for those LPARs listed:
SMF70CPA SMF70LAC SMF70PAT SMF70WTI SMF70WTS SMF70WTI.
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 Support for z/OS 2.3 changes. See also Change 35.166.
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 OA48913 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'
Fields not present, LENPDGS/SMF71PDL is 2160 bytes,
but should be 2224.
-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'
No Observations to test.
-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.
-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:
-ASMRMFV Recent versions will execute without error,
but new variables will not be output without the new
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.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 TYPE 749 new var Support for Synchronious I/O zos 2.3
VMAC74 R749SRBF='BYTES*READ*THIS*FUNCTION'
May 10, 2017 R749SWBF='BYTES*WRITTEN*THIS*FUNCTION'
R749DFMT='FORMAT'
R749SSRF='SUCCESSFUL*REQUESTS*THIS'
R749SLRF='LOCAL*REJECTS*THIS'
R749SRRF='REMOTE*REJECTS*THIS'
R749STPF='PROCESSING*TIME*THIS'
R749SRBC='BYTES*READ*ALL*FUNCTIONS'
R749SWBC='BYTES*WRITTEN*ALL*FUNCTIONS'
R749SSRC='SUCCESSFUL*REQUESTS*ALL'
R749SLRC='LOCAL*REJECTS*ALL'
R749SRRC='REMOTE*REJECTS*ALL'
R749STPC='PROCESSING*TIME*ALL'
Note that the type 74 subtype 9 record requires RMF III
to be active on this system, and the ERBRMFxx member of
SYS1.PARMLIB must have PCIE=YES specified, to be created.
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 Revision to SAG reports to capture COMPLETE ONLINE and
SAGANAL NATURAL ONLINE in new variables based on PROGRAM name.
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 Support for z/OS 2.3 RACF 482 segment added to input the
VMAC85 extended LOGSTR text in 1100-byte LOGSTR variable.
Mar 23, 2017 Documented in ICN1560 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 Support for z/OS 2.3 OAM SMF 85 (COMPAT) addition of
VMAC85 these variables to support multiple OAM Systems in z/OS:
Mar 1, 2017 R85POSUB='OAM*SYSTEM*ID'
R85PSSID='DB2*SYSTEM*ID'
Documented in ICN1552 March 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'
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. This is support for BBMQ 5.3.
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.
VMAC125 -If you use TYPE117, it will delete any GTZ records and
Jan 20, 2017 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 1