COPYRIGHT (C) 1984-2023 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES 39.39
=========================MEMBER=CHANGE39================================
/* COPYRIGHT (C) 1984-2022 MERRILL CONSULTANTS DALLAS TEXAS USA */
E.A. MXG VERSION 39.39 is dated Dec 30, 2021, thru Change 39.225..
MXG VERSION 39.09 was dated Dec 2, 2021, thru Change 39.213.
MXG VERSION 39.08 was dated Oct 15, 2021, thru Change 39.199.
MXG VERSION 39.07 was dated Sep 20, 2021, thru Change 39.190.
MXG VERSION 39.06 was dated Aug 12, 2021, thru Change 39.167.
MXG VERSION 39.05 was dated Jul 16, 2021, thru Change 39.149.
MXG VERSION 39.04 was dated Jun 1, 2021, thru Change 39.116.
MXG VERSION 39.03 was dated May 3, 2021, thru Change 39.092.
MXG VERSION 39.02 was dated Apr 4, 2021, thru Change 39.066.
First MXG VERSION 39.02 was dated Apr 1, 2021, thru Change 39.063.
MXG VERSION 39.01 was dated Feb 17, 2021, thru Change 39.028.
First MXG VERSION 39.01 was dated Feb 16, 2021, thru Change 39.026.
ANNUAL MXG VERSION 38.38 was dated Jan 4, 2021, thru Change 38.234.
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 39.39 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 39.39.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains old Technical Notes. many of which are still
valid, but the last was in 2018. Now, TECHNOTES and FLASHes are in
CHANGES/CHANGESS. which are also online.
The Final MXG Newsletter SIXTY-NINE was dated Jan 3, 2018.
Member CHANGES contains the changes made in this current MXG version.
Member CHANGESS contains all changes that have ever been made to MXG.
CHANGESS and NEWSLTRS are also online at http://www.mxg.com,
========================================================================
I. MXG VERSION 39.39 DATED Jan 5, 2022 THRU CHANGE 39.225.
==MAJOR CHANGES ADDED IN MXG 39.39, DATED Jan 5, 2022 THRU 39.225.
NEW SUPPORT
ASUMMQAC 39.220 Summarization of MQMACCT (SMF116).
TRNDMQAC 39.220 Trending of MQMACCT (SMF116).
UTILWORK 39.219 Create Workload Definitions for RMFINTRV
VMXGINIT 39.214 Support for SAS Viya INCOMPAT Version Format Change
==MAJOR CHANGES ADDED IN MXG 39.09, DATED Dec 2, 2021 THRU 39.213.
NEW SUPPORT
TYPEDB2 39.200 Support for DB2 zHyperlink new data.
TYPE90A 39.206 FORMAT MG090CM for CMDMVS new values decoded.
TYPESVIE 39.207 Sysview SV27DB2/SV27PROG/SV27TRAN updated.
FNDMXGJB 39.210 Find probable MXG Job execution SAS/SOURCLIB/LIBRARY.
TYPERACF 39.212 Support for RACF Unload 0207 and 05B0 records.
ENHANCEMENTS
ANALDB2R 39.209 DB2 DBID/OBID Decoded if there is an IFCID 105.
TYPEDB2 39.208 DB2STATB/S variables AGET/ASGE/ASSE/ASYN deaccumed.
DODSCRDT 39.204 CREATEDATE Year 1772 in 2028 corrected.
ERRORS CORRECTED
TYPE82 39.203 SMF 82 Subtype 24 INPUT STATEMENT EXCEEDED corrected.
TYPETLC 39.202 Protect BMC Control-D CSV invalid quotes protected.
TYPE50 39.201 MXG 39.08-39.08 Error if no //INSTREAM DD.
TYPE6156 39.213 Protection for TYPE6156 record with short segment.
==MAJOR CHANGES ADDED IN MXG 39.08, DATED Oct 15, 2021 THRU 39.199.
ERROR CORRECTED:
TYPE6156 39.196 MXG 39.07 INPUT EXCEEDED, SMF6XSTCKE incorrect..
TYPE30 39.194 AVGWKSET,CPUTOTTM,CPUUNITS could be too large.
TYPE50 39.198 TYPE50 OSA Express Accel TY50PKAC misspelled.
NEW SUPPORT:
TYPESVIE 39.199 Support for MainView IMS Updates/Enhancements
FORMATS 39.197 SMF 119 $MG119CF NEG-CIPHER decoded for ZERT.
TYPERMFV 39.192 RMF III for z/OS 2.5 plus new tables supported.
ENHANCEMENTS
BLDSMPDB 39.195 USEVMXGSET adds OPEN=DEFER for z/OS save drives.
SELSMF 39.192 Select and write SMF records from each system.
ICETOOL 39.191 Select records on z/OS for ASCII execution example.
==MAJOR CHANGES ADDED IN MXG 39.07, DATED Sep 20, 2021 THRU 39.190.
FLASH
WPS ONLY 39.171 WPS Errors in 4.3.1 fixed in 4.3.3.
NEW SUPPORT:
TYPE110 39.176 Support for CICS/TS 6.1 CICSTRAN/UTILEXCL.
TYPEDB2 39.188 Support for CICS-DB2 ATTACH APAR PH31440 fields.
TYPEVELO 39.179 Support for Dino VelociRaptor SMF records.
TYPEPRF 39.178 Support for Dell PRF Monitor MFE SMF records.
TYPECTLC 39.175 Support for BMC CONTROL-D CSV audit file.
TYPE1415 39.173 Support for SMF14DSENCARCHKEY encrypted flat.
TYPERMFV 39.168 Support for RMF III z/OS 2.5 existing tables.
TYPE30 39.186 Support for APAR OA61368 new RAXFLAGS bits.
ENHANCEMENTS
TYPE110 39.180 Enhanced MXGABND can set Condition Code.
BUILD005 39.181 Variables BOOSTACTIVE/BOOSTCLASS in PDB.STEPS.
IMACABND 39.180 MXGABND can set a condition code instead of ABEND.
TYPENDM 39.173 New format $MGNDMCP decodes NDMCPEA Cipher values.
ERRORS CORRECTED
TYPE90A 39.170 Conflict with variable SMF9040ID, char vs numeric.
==MAJOR CHANGES ADDED IN MXG 39.06, DATED Aug 12, 2021 THRU 39.167.
NEW SUPPORT:
TYPE1153 39.163 Support for SMF ID=1153 JES 2 Monitor.
TYPEQSEL 39.158 Support for Quick Select product's SMF records.
TYPEVIRS 39.154 Support for VIRTEL AUDIT VIRSTATA SMF records.
TYPE83 39.153 Support for new datasets and variables.
==MAJOR CHANGES ADDED IN MXG 39.05, DATED Jul 16, 2021 THRU 39.153.
ERRORS CORRECTED
VMAC110 39.145 SMF 110 Subtype 1 MNSEGCL=5 (NOT CICSTRAN) ABEND 5.3.
VMXGALOC 39.148 ERROR: Libref TREND not assigned.
ANALMSUS 39.140 Using READSMF=YES and PDBOUT=WORK ERRORed
VFMT102 39.139 ANALDB2R failed FORMAT NOT FOUND if no subtype 104.
VMXGRMFI 39.136 Special Characters in Class Names not supported
ANALDB2R 39.135 Superfluous %END z/OS only ABEND after Change 39.080
VMACNDM 39.133 NDM HW/H2 records do not match DSECT, IBM SR open.
UTILBLDP 39.129 ERROR: Old-style macro name _ID102 xxx must contain.
VMAC71 39.128 Variables PAGBLAV and PAGEBLMX were reversed.
VMAC16 39.123 INVALID ENDTIME in TYPE16 z/SORT records.
ASMRMFV 39.122 ASMRMFV failed with back-level ASM UI60362 (2020).
VMXGALOC 39.120 MXGERRORs if FIRSTRUN=YES was not used first time.
UTILCPLG 39.118 ASCII Copy Log to File utility doesn't if blanks.
VMAC30 39.117 JOBCLAS8='STC' erroneously set one byte JOBCLASS='S'.
IBM ERRORS CORRECTED
VMAC7072 39.138 If Configuration changed NRCPUs LCPUPDTM invalid.
VMAC92 39.125 STCKE GMTOFF92 wrong, IBM date was +60 years 2081!
ENHANCEMENTS
VMACSVIE 39.141 Updates to SYSVIEW IMS datasets SV34TRAN & SV35TRAN
MONTHPDB 39.146 New generic example for Monthly PDB.
VMAC110 39.147 CICSTRAN OADATA1X created for SMF 123A merge.
FORMATS 39.132 FORMAT values added for Recovery Boost Start/End.
VMAC50 39.131 Updates and Corrections for VTAM Tuning.
VMAC123A 39.127 Liberty SMF 123 SYSNAME was CVTSNAME.
VGETALOC 39.124 Enhanced support and Linux example in the member.
VMACHSM 39.119 Support for HSM ZEDC Compression in HSMFSRST.
==MAJOR CHANGES ADDED IN MXG 39.04, DATED Jun 1, 2021 THRU 39.116.
ERRORS CORRECTED
TYPEDCOL 39.093 Correction to sizes in DCOLLECT DATASETS.DATASETS.
VMACDB2H 39.099 Correction of DB2 GMT Offset to include Leap Seconds.
NEW SUPPORT
VMAC123A 39.102 Support for z/OS Connect EE SMF 123 Subtype 2 record.
VMACBVIR 39.108 Support for BVIR Version R5.x 8.50.x.x
VMAC0 39.103 Support for more than 4TB of Real Storage.
VMACDB2 39.099 Support for DB2 Netezza/IDAA Accelerator new data.
ASMRMFV 39.100 ASMRMFV Field Data Filter for CRYG3 Crypto table.
ENHANCMENTS
TYPE89 39.096 New SMF89SOLUTIONID for Tailored Fit Pricing SOLUT.
ASUM70PR 39.097 New NOTALLLPARS=YES suppresses missing LPAR message.
VMAC110 39.104 New %LET MACEXCL=IMACEXCL supports multiple IMACEXCL.
VMACSMF 39.109 More examples using _SMF for record selection.
==MAJOR CHANGES ADDED IN MXG 39.03, DATED May 3, 2021 THRU 39.092.
ERRORS CORRECTED
ASUMUOW 39.085 Variable TRANNAME in PDB.ASUMUOW only one character.
ANALDB2R 39.080 ANALDB2R can fail if PMAUD02 requested but no data.
VMXGRMFI 39.077 VMXGRMFI(PDB=SMF) could fail, UTILBLDP now used.
UTILEXCL 39.078 MXG 39.02. EXCLUDED FIELDS ERROR typo $CHAR54 vs 64.
NEW SUPPORT
TYPEHSM 39.086 Support for HSM UNIX CLOUD statistics variables.
TYPERMFV 39.079 Support for RMF III CRYG3 Cryptographic Hdw Table.
TYPERMFV 39.071 RMF III Percents in System Info and CPC Summary.
TYPE102 39.091 Support for new variables in IFCID=402.
TYPE80A 39.090 Support for RACF Pass Ticked Eval, TYPE8081 PTEVAL.
TYPE84 39.076 Support for Phoenix JES3plus SMF 84 subt correction.
TYPE106 39.075 Support for new SMF 106 subtypes HWIREST API data.
TYPERMRV 39.074 Support for RMF III Feb 2021 Updates, BOOST, etc.
TYPEDB2 39.070 Support for DB2 APAR PH31684 zSORT and NETEZZA.
TYPE42 39.075 SMF Manual update new variable in TYPE42DS.
VMXGALOC 39.068 New parm to leave WORK uncompressed, PDB compressed.
TYPEXAM 39.089 Velocity XAM storage variables MXGBYTE formatted.
ASUM70PR 39.072 ZIPOVHTM and PCTZIPOV added to four outputs datasets.
==MAJOR CHANGES ADDED IN MXG 39.02, DATED Apr 4, 2021 THRU 39.066.
ABEND CORRECTED
TYPE16 39.057 INPUT EXCEEDED SMF 16 ZSORT APAR PH32395 cannot use
Sort Exits E15/E35 with zSORT. Also caused 0C4 in
Broadcom's CA7 SASSHISS program. See Change text.
ASMRMFV 39.060 HLASM UI73933 worked, UI60352 didn't, corrected.
TYPECDC 39.023 Short Infosphere records caused INPUT EXCEEDED.
NEW SUPPORT
TYPENDCD 39.033 Support for NDM-CDI SMF (default 133) APAR PH35087.
TYPE90A 39.028 Support for SMF 90 subtype 41, CVTLOS value changed.
TYPECLTA 39.026 Support for IBM TAPE CLOUD CONNECTOR SMF record.
ENHANCEMENT
ASMRMFV 39.039 Field Data Filter can reduce size of RMFBSAM file.
VMACSMF 39.025 Example _SMF for selection, CICS Dictionary records.
TYPE110 39.053 z/OS EE Connect CICSTRAN vars OADATA1/2/3 decoded.
CORRECTIONS
TYPE120 39.036 Negative CPU WebSphere SMF 120 TYP120BL APAR PH35442.
TYPEBETA 39.031 BETA 93 subtype 5 shortened, many variables gone.
TYPE0 39.059 GMT Offset CVTTZ in TYPE0 was off by 1 second.
==MAJOR CHANGES ADDED IN MXG 39.01, DATED Feb 17, 2021 THRU 39.028.
ABEND CORRECTED:
ANAL9914 39.018 Some ANAL9914 invocations mismatched %DO-%END logic.
VMACDB2 39.017 DB2 NETEZZA IDAA 100-1 INPUT STATEMENT EXCEEDED.
ASMRMFV 39.013 MXG 34.06-38.38 ABEND if STOREGROUP GT 1361 vols.
CORRECTIONS
UTILWORK 39.020 UTILWORK creates RMFINTRV code member, enhanced.
VMXG70PR 39.021 Override PSU70PR/LP/GC/GL DD's may not work.
VGETJESN 39.002 WARNING TYPETASK NOT DECODED SUBSYS=SAR
VMACXAM 39.022 Variables missing values in XAMSYS corrected.
VMXGPRNT 39.019 SP_REMV='Y' truncated some labels.
ANALMSUS 39.015 The JOB report now includes all TASKTYPEs.
ANALID 39.004 ANALID did not identify CICS Compressed Records.
VMAC102 38.010 DB2 IFCID 172 dataset T102s172 variables corrected
VMAC80A 39.003 TYPE80TK observation count is smaller now.
VGETJESN 39.002 TYPETASK not decoded for SUBSYS='SAR'.
TECHNOTES
TECHNOTE 39.012 z/OS SAS ODS may need to increase MEMLEAVE option.
TECHNOTE 39.008 z/OS SAS ODS can use zIIPs, Java error may prevent.
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:
DO NOT USE 4.03.01 nor 4.04.00, INVALID CPU BUSY in TYPE70.
Error was introduced in 4.03.01 and 4.04.00. See Change 39.171.
Must be at 4.03.02.00.8569+ or 4.04.00.03.3277+/
WPS Version 4.01 USER 4037 ABEND, See Change 37.116.
WPS Version 4.0 reportedly fixed version 3 problems.
WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266.
and other errors with 3.00 or 3.01 have been corrected in the
current WPS version.
WPS Version 3.01.1 maintenance level 731 required for PDB to tape
WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS.
WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5.
WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors.
WPS Version 3.0 requires MXG 31.09 (see Change 31.251).
WPS Version 2.4 required MXG 27.09 (see Change 27.239).
WPS Version 2.3.5 required MXG 27.05.
See NEWSLETTERS for WPS Support Statement.
WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID"
when the LIBNAME PDB does not exist; there would also have been a
prior log message NOTE: Library PDB does not exist as the clue.
IV. MXG Version Required for Hardware, Operating System Release, etc.
MXG is usually NOT sensitive to z/OS Hardware changes, but:
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.
z/OS 2.4 Compatible from SMF Manual Apr 2021 39.075 39.03.
z/OS 2.4 Compatible RMF III PGMR Apr 1 2021 39.074 39.03.
z/OS 2.5 Compatible from SMF Aug 12,2021 39.06.
z/OS 2.5 Compatible RMF III Aug 12,2021 39.08.
z/OS 2.5 RMF III 4 new tables Aug 12,2021 39.08.
z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04
z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07
z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24
z9EC CPUs - CPUTYPE '2094'x:
with 64-bit z/OS - no change required *24.24
with 32-bit z/OS only: Aug 26, 2006 24.06
z9BC CPUs - CPUTYPE '2096'x:
with 64-bit z/OS - no change required 24.01
with 32-bit z/OS only: Jul 27, 2006 *24.24
z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11
z10 HiperDispatch/Parked Time Mar 3, 2008 *26.10
z196 (INCOMPAT IF GT 64 ENG) Aug 17, 2010 28.05
zEC12 Nov 14, 2012 30.07
z13 non-SMT Mode May 27, 2014 32.05
z13 SMT Mode Change 33.217 Sep 15, 2015 *33.09
z13 SMT Mode NRZIPCPU 34.106 May 10, 2016 34.03
z13 SMT MT=2 CPUZIPTM TYPE70 Mar 21, 2016 35.03
z14 SMF 113 INCOMPAT, ABEND Oct 2, 2017 35.11
z14 113 LPARBUSY missing value Aug 8, 2018 36.07
z14 ZR1 New SMF70MAXPU variable May 8, 2018 36.04
z15 New SMF 113 fields INCOMPAT Nov 18, 2020 37.08
z15 z/VM MFC counters, INCOMPAT Mar 23, 2020 38.02
z15 ANAL9914 Support CH 39.006 Jan 14, 2021 39.01
CICS/CTG V9 Transaction Gateway ?? ?? 2013 31.31
CICS/ESA 3.2 Jun 28, 1991 9.9
CICS/ESA 3.3 Mar 28, 1992 10.01
CICS/ESA 4.1 Oct 27, 1994 13.09
CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07
CICS-Transaction Server V1R1 Sep 10, 1996 14.07
CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06
CICS/TS V1R2 CICS/TS 1.2 Oct 27, 1997 15.06
CICS/TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04
CICS/TS V2R1 CICS/TS 2.1 Mar 15, 2001 18.11
CICS/TS V2R2 CICS/TS 2.2 Feb 9, 2002 19.19
CICSTRAN subtype 1 support only *19.19
CICSTRAN subtype 2 completed *19.08
CICS-TS V2R3 CICS?TS 2.3 Dec 19, 2003
Using UTILEXCL to create IMACEXCL: 21.04
Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04
CICS/TS V2R3 CICS/TS 2.3 Aug 13, 2004 22.04
CICS/TS V3R1 CICS/TS 3.1 Jan 18, 2005 22.22
CICS-TS for Z/OS Version 3.1 Mar 15, 2005
Using UTILEXCL to create IMACEXCL: 22.13
Reading un-Excluded CICS with TYPE110, no IMACEXCL: 22.22
CICS/TS V3R2 CICS/TS 3.2 Dec 6, 2007 25.11
CICS/TS for Z/OS Version 3.2 Jun 29, 2007 25.03
CICS/TS 3.2 Compressed Records Nov 3, 2007 25.11
CICS/TS 4.1 (CICSTRAN INCOMPAT) Mar 13, 2009 27.01
CICS/TS 4.1 (STATISTICS ST=2) Sep 18, 2009 27.08
CICS/TS 4.2 CICSTRAN/STATISTICS Jun 24, 2011 29.03
CICS/TS 4.2 CICSRDS MNSEGCL=5 Jun 24, 2011 *29.05
CICS/TS 4.2 INVALID STID=116 Jan 31, 2012 *30.01
CICS/TS 5.1 (INCOMPATIBLE) Dec 14, 2012 *30.08
CICS/TS 5.1 for valid TASZIP/ELG Jan 21, 2013 *30.30
CICS/TS 5.1 MNSEGCL=5 INCOMPAT Jun 17, 2013 *31.03
CICS/TS 5.2 COMPATIBLE CICSTRAN Jun 13, 2014 *31.03
CICS/TS 5.2 INCOMPAT Statistics Jun 13, 2014 *32.03
CICS/TS 5.3 INCOMPAT CICSTRAN Apr 29, 2015 33.04
CICS/TS 5.3 RESOURCE SEGCL=5 Sep 31, 2015 33.09
CICS/TS 5.3 CICSTRAN INCOMPATIBL Oct 29, 2015 33.11
CICS/TS 5.3 GA date Dec 11, 2015 33.33
CICS/TS 5.3 MNSEGCL=5 INPUT ERR Mar 21, 2016 34.02
CICS/TS 5.4 OPEN BETA Aug Aug 11, 2016 34.06
CICS/TS 5.4 OPEN BETA Nov Nov 11, 2016 34.09
CICS/TS 5.4 GA Jun 17, 2017 35.03
CICS/TS 5.5 GA (INCOMPAT) Jan 29, 2018 36.11
CICS/TS 5.6 GA (INCOMPAT) Jun 1, 2020 38.07
CICS/TS 5.6 NEW DATA (COMPAT) Oct 5, 2020 38.09
CICS/TS 6.1 INSERTS (INCOMPAT) Sep 20, 2020 39.07
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 INCOMPAT ABEND Feb 14, 2019 37.02
z15 z/VM MFC counters, INCOMPAT Mar 23, 2020 38.02
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Mar 96, 2004 *26.01
IMS log 10.1 Mar 06, 2007 *26.01
IMS log 11.1 Apr 1, 2010 *28.02
IMS log 12.1 Jan 23, 2012 *29.29
IMS log 13.1 (NOT 56FA) May 25, 2013 31.03
IMS log 13.1 (56FA RECORD) May 27, 2014 32.05
IMS log 14.1 COMPATIBLE Dec 19, 2015 33.07
IMS log 15.1 NO CHANGES Mar 1, 2018 35.07
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
AS400 4.4.0 Sep 27, 1999 17.07
AS400 4.5.0 Jul 27, 2000 18.07
AS400 5.2.0 - Most records Jul 23, 2003 21.03
AS400 5.2.0 - QAPMMIOP Jul 23, 2003 22.04
AS400 5.3.0 Jan 22, 2005 22.22
AS400 5.4.0 Aug 26, 2006 24.06
AS400 6.1.0 Jun 29, 2008 26.05
Note: Asterisk by the version number means the Version number
was changed (to the MXG version required), after an earlier
MXG version was listed as supporting this product release,
usually because an APAR modified the product's data records.
Or a coding error in MXG could be the reason for the change!
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
NTSMF 2.4.4 Aug 9, 2002 20.04
NTSMF 2.4.5 INCOMPAT Apr 1, 2003 21.02
NTSMF 2.4.7 Sep 30, 2004 22.08
NTSMF 3.1.4 Mar 15, 2009 27.01
NTSMF 4.0 Mar 15, 2011 29.03
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 20.04
The Monitor for DB2 Version 4.0 22.10
The Monitor for DB2 Version 5.0 30.02
The Monitor for CICS/ESA 1.2 - 12.12
The Monitor for CICS/ESA 1.3 - 15.01
The Monitor for CICS/ESA 2.0 - 15.06
The Monitor for CICS TCE 2.1 - 20.04
The Monitor for CICS TCE 2.2 - 20.335, 21.134 21.04
The Monitor for CICS TCE 2.3 including CICS/TS 3.1 22.08
The Monitor for CICS TCE 3.2 (almost all) 25.11
The Monitor for CICS TCE 3.2 (almost all) 27.01
The Monitor for CICS TCE 3.3 (for CICS/TS 4.1,4.2) 29.07
TMON/CICS 3.4 (for CICS/TS 5.1) 30.30-32.12
(Do not use 32.13,32.32,33.01,33.02,33.03 for 3.4)
TMON/CICS 3.4 (for CICS/TS 5.1 - Change 33.099) 33.04
TMON/CICS 4.0 (for CICS/TS 5.2 - Change 33.195) *33.09
TMON/CICS 4.1 (for CICS/TS 5.3 - Change 34.257 34.08
The Monitor for MVS/ESA 1.3 - 12.05
The Monitor for MVS/ESA 1.5 - 12.05
The Monitor for MVS/ESA 2.0 - 15.09
The Monitor for MVS/ESA 3.0 - 19.19
TMON/MVS Version 4.4 32.04
Candle
Omegamon for CICS V200 User SMF 12.05
Omegamon for CICS V300 User SMF 13.06
Omegamon for CICS V400 User SMF 16.02
Omegamon for CICS V400 type 110 segments 16.02
Omegamon for CICS V500 User SMF 18.01
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for IMS V300 (ITRF) 14.04
Omegamon for IMS V550/V560 (ITRF) 25.05
Omegamon for MVS V300 13.05
Omegamon for MVS V400 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for VTAM V400 15.15
Omegamon for VTAM V500 18.08
Omegamon for SMS V100/V110 12.03
CA
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 39.39.
1. Incompatibilities introduced in MXG 39.39:
a. Changes in MXG architecture made between 39.39 and prior versions
that can introduce known incompatibilities.
IF YOU HAVE MEMBER E2TY70 IN YOUR USERID.TAILORING SOURCE LIBRARY,
YOU MUST CHANGE _LTY70 to _WTY70 in that member. CHANGE 38.105.
The error before this correction will be:
ERROR: DATA SET "PDB.TYPE70" was not specified on the DATA stmt.
2. Installation and re-installation procedures are described in detail
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTT for
SAS Version 9.
MXG Definitions with regard to MXG Software Changes:
COMPATIBLE A change in a data record which did not alter either
COMPAT the location or the format of all of the previously-
kept MXG variables is COMPATIBLE, and you can continue
to run the old version of MXG software, which will read
the new records without error, but none of any new data
fields or any new record subtypes will be created/kept
until you install the MXG Version with this change.
INCOMPAT A change in a data record that causes the current MXG
version to fail, visibly or invisibly, with or without
error conditions or messages, and the output datasets
may contain wrong values and incomplete observations,
and/or observations may have been lost.
You MUST install the new MXG Version with this change
to process data records that have been INCOMPATIBLY
changed by their vendor.
TOLERATE In other words, the old MXG Version TOLERATES the new
data records, if they are COMPATIBLY changed.
EXPLOIT Once you use the new MXG Version to read the changed
records, all of the new fields, subtypes, etc, that are
described in this change will be created in the MXG
datasets, so the new MXG Version EXPLOITS the new data,
and you have full support of the new data records.
An MXG Version never "expires" nor "goes out of Support". When
you put in a new product/subsystem/Release/APAR that incompatibly
changed its records then you must install the current MXG Version
or at least be using the minimum level of MXG that is currently
documented in the preceding list in section IV.
COSMETIC Some Changes will start with COSMETIC. This indicates
that that change only alters a displayed value or may
be a spelling error in a label, but it is "cosmetic"
in that it ONLY affected the display, and the output
data sets created are NOT impacted by this change.
VI. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
See also member INDEX, but it may be overwhelming.
VII. Changes Log
--------------------------Changes Log---------------------------------
You MUST read each Change description to determine if a Change will
impact your site. All changes have been made in this MXG Library.
Member CHANGES always identifies the actual version and release of
MXG Software that is contained in that library.
The CHANGES selection on our homepage at http://www.MXG.com
is always the most current information on MXG Software status,
and is frequently updated.
Important changes are also posted to the MXG-L ListServer, which is
also described by a selection on the homepage. Please subscribe.
The actual code implementation of some changes in MXG SOURCLIB may be
different than described in the change text (which might have printed
only the critical part of the correction that need be made by users).
Scan each source member named in any impacting change for any comments
at the beginning of the member for additional documentation, since the
documentation of new datasets, variables, validation status, and notes,
are often found in comments in the source members.
Alphabetical list of important changes in MXG 39.39:
Dataset/
Member Change Description
ANAL9914 39.018 Some ANAL9914 invocations mismatched %DO-%END logic.
ANALDB2R 39.135 Superfluous %END z/OS only ABEND after Change 39.080
ANALDB2R 39.209 DB2 DBID/OBID Decoded if there is an IFCID 105.
ANALID 39.004 ANALID did not identify CICS Compressed Records.
ANALMSUS 39.015 The JOB report now includes all TASKTYPEs.
ANALMSUS 39.140 Using READSMF=YES and PDBOUT=WORK ERRORed
ASMRMFV 39.013 MXG 34,06-38.38 ABEND if storegrop 1361 vols.
ASMRMFV 39.039 Field Data Filter can reduce size of RMFBSAM file.
ASMRMFV 39.060 HLASM at UI73933 works, UI60352 doesn't assemble.
ASMRMFV 39.100 ASMRMFV Field Data Filter for CRYGE Crypto table.
ASMRMFV 39.122 ASMRMFV failed with back-level ASM UI60362 (2020).
ASUM70PR 39.097 New NOTALLLPARS=YES suppresses missing LPAR message.
ASUMMQAC 39.220 Summarization of MQMACCT (SMF116).
BUILD005 39.181 Variables BOOSTACTIVE/BOOSTCLASS in PDB.STEPS.
DODSCRDT 39.204 CREATEDATE Year 1772 in 2028 corrected.
FNDMXGJB 39.210 Find probable MXG Job executionsSAS/SOURCLIB/LIBRARY.
FORMATS 39.132 FORMAT values added for Recovery Boost Start/End.
IMACABND 39.180 MXGABND can set a condition code instead of ABEND.
MONTHPDB 39.146 New generic example for Monthly PDB.
TECHNOTE 39.012 z/OS SAS ODS may need to increase MEMLEAVE option.
TRNDMQAC 39.220 Trending of MQMACCT (SMF116).
TYPE0 39.059 GMT Offset CVTTZ in TYPE0 was off by one second.
TYPE0 39.103 Support for more than 4TB of Real Storage.
TYPE102 38.010 DB2 IFCID 172 dataset T102s172 variables corrected
TYPE110 39.053 z/OS EE Connect CICSTRAN vars OADATA1/2/3 decoded.
TYPE110 39.104 New %LET MACEXCL=IMACEXCL supports multiple IMACEXCL.
TYPE110 39.145 INPUT STATEMENT EXCEEDED MNSEGCL=5 CICS 5.3.
TYPE110 39.147 CICSTRAN OADATA1X created for SMF 123A merge.
TYPE110 39.176 Support for CICS/TS 6.1 CICSTRAN/UTILEXCL.
TYPE1153 39.163 Support for SMF ID=1153 JES 2 Monitor.
TYPE120 39.036 Negative CPU WebSphere SMF 120 TYP120BL APAR PH35442.
TYPE123A 39.102 Support for z/OS Connect EE SMF 123 Subtype 2 record.
TYPE123A 39.127 Liberty SMF 123 SYSNAME was CVTSNAME.
TYPE1415 39.173 Support for SMF14DSENCARCHKEY encrypted flat.
TYPE16 39.057 Protection for truncat SMF 16, ZSORT triplet no data.
TYPE16 39.123 INVALID ENDTIME in TYPE16 z/SORT records.
TYPE30 39.117 JOBCLAS8='STC' erroneously set one byte JOBCLASS='S'.
TYPE30 39.186 Support for APAR OA61368 new RAXFLAGS bits.
TYPE50 39.131 Updates and Corrections for VTAM Tuning.
TYPE50 39.201 MXG 39.08-39.08 Error if no //INSTREAM DD.
TYPE71 39.128 Variables PAGBLAV and PAGEBLMX were reversed.
TYPE80A 39.003 TYPE80TK observation count is smaller now.
TYPE82 39.203 SMF 82 Subtype 24 INPUT STATEMENT EXCEEDED corrected.
TYPE83 39.153 Support for new datasets and variables.
TYPE89 39.096 New SMF89SOLUTIONID for Tailored Fit Pricing SOLUT.
TYPE90A 39.028 Support for SMF 90 subtype 41, CVTLOS value changed.
TYPE90A 39.170 Conflict with variable SMF9040ID, char vs numeric.
TYPE90A 39.206 FORMAT MG090CM for CMDMVS new values decoded.
TYPE92 39.125 STCKE GMTOFF92 wrong, IBM date was +60 years 2081!
TYPEBETA 39.031 BETA 93 subtype 5 shortened, many variables gone.
TYPEBVIR 39.108 Support for BVIR Version R5.x 8.50.x.x
TYPECDC 39.023 Short Infosphere records caused INPUT EXCEEDED.
TYPECLTA 39.026 Support for IBM TAPE CLOUD CONNECTOR SMF record.
TYPECTLC 39.175 Support for BMC CONTROL-D CSV audit file.
TYPEDB2 39.017 DB2 NETEZZA IDAA 100-1 INPUT STATEMENT EXCEEDED.
TYPEDB2 39.099 Support for DB2 Netezza/IDAA Accelerator new data.
TYPEDB2 39.200 Support for DB2 zHyperlink new data.
TYPEDB2 39.208 DB2STATB/S variables AGET/ASGE/ASSE/ASYN deaccumed.
TYPEDB2H 39.099 Correction of DB2 GMT Offset to include Leap Seconds.
TYPEDCOL 39.093 Correction to sizes in DCOLLECT DATASETS.DATASETS.
TYPEHSM 39.119 Support for HSM ZEDC Compression in HSMFSRST.
TYPENDCD 39.033 Support for NDM-CDI SMF (default 133) APAR PH35087.
TYPENDM 39.133 NDM HW/H2 records do not match DSECT, IBM SR open.
TYPENDM 39.173 New format $MGNDMCP decodes NDMCPEA Cipher values.
TYPEPRF 39.178 Support for Dell PRF Monitor MFE SMF records.
TYPEQSEL 39.158 Support for Quick Select product's SMF records.
TYPERMFV 39.168 Support for RMF III z/OS 2.5 existing tables.
TYPESMF 39.025 Example _SMF for selection, CICS Dictionary records.
TYPESMF 39.109 More examples using _SMF for record selection.
TYPESVIE 39.141 Updates to SYSVIEW IMS datasets SV34TRAN & SV35TRAN
TYPESVIE 39.207 Sysview SV27DB2/SV27PROG/SV27TRAN updated.
TYPETLC 39.202 Protect BMC Control-D CSV invalid quotes protected.
TYPEVELO 39.179 Support for Dino VelociRaptor SMF records.
TYPEVIRS 39.154 Support for VIRTEL AUDIT VIRSTATA SMF records.
TYPEXAM 39.022 Variables missing values in XAMSYS corrected.
UTILBLDP 39.129 ERROR: Old-style macro name _ID102 xxx must contain.
UTILCPLG 39.118 ASCII Copy Log to File utility doesn't if blanks.
UTILWORK 39.020 UTILWORK creates RMFINTRV code member, enhanced.
UTILWORK 39.219 Create Workload Definitions for RMFINTRV
VFMT102 39.139 ANALDB2R failed FORMAT NOT FOUND if no subtype 104.
VGETALOC 39.124 Enhanced support and Linux example in the member.
VGETJESN 39.002 WARNING TYPETASK NOT DECODED SUBSYS=SAR
VMXG70PR 39.021 Override PSU70PR/LP/GC/GL DD's may not work.
VMXGALOC 39.120 MXGERRORs if FIRSTRUN=YES was not used first time.
VMXGALOC 39.148 ERROR: Libref TREND not assigned.
VMXGINIT 39.214 Support for SAS Viya INCOMPAT Version Format Change
VMXGPRNT 39.019 SP_REMV='Y' truncated some labels.
VMXGRMFI 39.136 Special Characters in Class Names not supported
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 39.225 ARE IN MXG 39.39 DATED Dec 30, 2021 =========
Change 39.225 Correction to TY50HIPP, TY50HIPB and TY50PKCN overflow
VMAC50 additions.
Dec 30, 2021
Thanks to Tom White, Bank of America, USA.
Change 39.224 -Support for RMF III APAR OA61811 (SMF) OA62502 (RMF) new
VMACRMFV ERBRCDG3 variables in ZRBRCDS and TYPE72GO datasets:
VMAC7072 RCDENCTRXNUM='TRANS*PROCESSED*WITHIN*ENCLAVES'
Dec 27, 2021 RCDENCTRXCALLS='TIMES*REPORTED*WHEN*DELETING'
May 16, 2022 RCDENCTRXET='EXECUTION*TIME FOR*RCDENCTRXNUM'
RCDENCTRXETS='SUM OF*SQUARED*FOR*RCDENCTRXNUM'
-Variable R723CETSX corrected in May;; it has been
twice prior to this change MXG 39.39.
Thanks to Ralph J. Romano, OPTUM, USA.
Change 39.223 Support for SMF TYPE 42 APARS OA61495 OA61393 OA31392
VMAC42 adds new bit flags to the SUBTYPE=27 TYPE4227 dataset:
Dec 27, 2021 SMF42REOS2'='EOS*OVERWRITE*SUCCESSFUL'
SMF42REOS3'='DADSM*UNMAP*ATTEMPTED'
SMF42REOS4'='DADSM*UNMAP*SUCCESSFUL'
Change 39.222 Support for Axway AMPLIFY Transfer CFT 3.6 V24 SMF data..
VMACAXWY
Dec 24, 2021
Thanks to Steve McKee, Fidelity, USA.
Change 39.221 -Support for Velocity TYPEXAM new MDISK2 segment which is
VMACXAM output to XAMDMINI dataset with some fields larger than
Dec 29, 2021 the original MDISK segment (still supported).
-Support for Velocity TYPEXAM new SEKSE2 segment which is
output to XMSEKSEK dataset.
Thanks to Arthur Koerner, CITIBANK,USA.
Change 39.220 ASUM and TRND members for MQMACCT (SMF116) dataset.
ASUMMQAC QWHSSTCK is used to set the interval, but is a UTC/GMT
TRNDMQAC value. See the comments in the members.
Dec 17, 2021
Change 39.219 UTILWORK creates RMFINTRV workload definitions from your
UTILWORK TYPE72GO data, with a Workload for each Service Class.
Dec 17, 2021 You can use Reporting Class, but UTILWORK will detect
if the sum of Reporting Class CPUTM is less than the
sum of Service Class CPUTM (which happens when not all
of your workloads are in a Reporting Class), and UTILWORK
will revert to using Service Classes.
Read the extensive comments in UTILWORK.
Change 39.218 Correction for DBID/OBID update
ANALDB2R
VFMT102
Dec 16, 2021
Change 39.217 If you suppressed DB2ACCT the sometimes large datasets
UTILBLDP went to work. Now all DB2ACC datasets and their sorts
Dec 15, 2021 are suppressed with SUPPRESS=DB2ACCT.
Change 39.216 Typo OUTEETAL corrected to OUTDETAL.
ANALTAPE
Dec 15, 2021
Change 39.215 SAS Version 9.3 TS3M1,"ERROR 71-185 MAX function call
VMACSVIE does not have enough arguments" for this statement that
Dec 10, 2021 was introduced in MXG 39.04
MAXTIME=MAX(IMTR_ESS_REQ_MAX);
but SAS 9.4 does NOT raise that error! Correct statement
MAXTIME=MAX(MAXTIME,IMTR_ESS_REQ_MAX);
This error occurred in TESTUSR1.
Thanks to Pete Osborne, HSBC, ENGLAND.
Change 39.214 -Support for SAS Viya INCOMPATIBLE Version format change
GRAFDB2B from '9.4' to 'V.03.05', i.e., from numeric to character.
RMFINTRV ERROR:"A character operand . . . in the %EVAL function
VGETENG where a numeric operand is required, condition was V."
VMXGINIT MXG uses the &SYSVER macro variable to determine the SAS
VMXGODSC version, which always has been a numeric value. Because
VMXGRMFI &SYSVER is a Read-Only macro variable, new &SSYSVER is
VMXGSUM created in VMXGINIT and set to 9.4 for Viya and set to
VMXGUOW &SYSVER for the rest. All references to &SYSVER were
Dec 15, 2021 changed to &SSYSVER (54 members).
-VGETENG, the %EVAL was removed.
RMFINTRV/VMXGRMFI workload names permit 32 characters.
-VMXGSUM had code to set the length of variable names to 8
to be in KEEP list for V6 compatibility, but there are
many long length variables that could have been truncated
and causing Variable Not Found errors, length is now 32.
-We do not test MXG under SAS Viya, but so far, this is
the sole problem that has been encountered.
SAS Viya provides a CAS Server (Cloud Analytic Server)
which automatically multi-threads across as many
servers as you define, but some SAS statements can NOT
be multi-threaded, and that includes both INFILE and
INPUT statements, which are re-directed to a single-
threaded workspace server, and which limits the value
of Viya to MXG.
Thanks to Christian Lechtenberg, CONCORDIA, GERMANY
====== CHANGES THRU 39.213 ARE IN MXG 39.09 DATED Dec 2, 2021 ========
Change 39.213 Protection for TYPE6156 Catalog record segment with the
VMAC6156 2 byte length field populated but no data following,
Dec 2, 2021 causing an INPUT STATEMENT EXCEEDED ERROR.
Thanks to Bruce Hewson, CITIBANK, SINGAPORE.
Change 39.212 Support for RACF Unload Record Types 0207 and 05B0 are
VMACRACF now populated; previously only the header was output.
Dec 1, 2021
Thanks to Karl Laseki, American Chemical Society, USA.
Change 39.211 The TMS warning message DENSITY IS MISSING is removed and
VMACTMS5 variable DEN=0 is set when it is not available.
Nov 30, 2021
Change 39.210 Find probably MXG job executions, i.e., PROGRAM=:'SAS'
FNDMXGJB and both SOURCLIB and LIBRARY DDnames.
Nov 22, 2021
Change 39.209 The decoding of DB2 DBID/OBID from SMF 102 IFCID 105
VFMT102 has been a long time challenge, with mostly partial
ANALDB2R success, but now, all IDs are correctly decoded if there
Nov 17, 2021 is an IFCID 105 record. New parameter PRINTFMTS=YES will
PROC PRINT the input values to the $MGDB2DB and $MGDB2OB
formats.
Thanks to Chuck Hopf, Independent MXG Consultant, USA.
Change 39.208 DB2STATB variables QBSTAGET/QBSTASGE/QBSTASSE/QBSTASYN
VMACDB2 were not deaccumulated, causing the DB2STATS variables
Nov 17, 2021 QBnAGET/QBnASGE/QBnASSE/QBnASYN for the four sets of
buffer pool counters to also be incorrect.
Thanks to Johnny Meek, Fidelity FMR, USA.
Change 39.207 -Sysview dataset SV27DB2 variable PROGRAM (Package name)
FORMATS was changed from ASCII to EBCDIC, at least in V16. New
VMACSVIE variable PROGRAM_EB will contain the EBCDIC value.
Nov 23, 2021 -FORMAT MGD145S was updated for new values and applied
to variable STATETYPE_DB2 in SV27DB2 dataset.
-Variables TRANNUM,OTRANNUM,LASTTRANNUM are correctly
now INPUT as &PD.4 in SV27TRAN dataset.
-Forty pairs of _TIME, _COUNT variables added to SV27TRAN
dataset and alignment corrected.
-New fields were added to SV27PROG dataset.
Thanks to Martyn Jones, CPTGLOBAL, ENGLAND.
Change 39.206 FORMAT MG090CM for TYPE90A variable CMDMVS (SUBTYPE) is
FORMATS updated for CMDMVS values 35-41 to describe why each
Nov 15, 2021 record is created.
Thanks to Jim S. Horne, Lowe's, USA.
Change 39.205 Cosmetic. Variable BPHITRAT was correctly added to the
VMACDB2 PDB.DB2STATB in Change 39.160, created in the _SDB2STB
Nov 3, 2021 deacccumlate DATA step, but it was incorrectly added to
the _VDB2STB list of variables created in the SMF pass,
where is not is created. The only impact was a note
on the log, and only if your AUTOEXEC/CONFIGxx options
did not contain the MXG default OPTIONS DKROCOND=NOWARN,
which overrides the SAS WARN default. The variable was
removed from that KEEP= list. MXG exploits DKROCOND to
allow variables to exist in the KEEP= list even when they
are not created, for example for the optional CICSTRAN
variables, so they can be added when you tailor IMACICxx
members and not have to touch the KEEP= list..
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 39.204 The %MACRO DODSCRDT creates CREATEDATE from INFILEs but
DODSCRDT YEAR=INPUT(SUBSTR(&DSCB,10,1),?? IB1.)+1900;
Nov 2, 2021 will create YEAR=1772 in 2028 because the IB1. input will
see '80'x with the sign bit on. INPUT PIB1. corrects, and
the ?? was not required, since any byte value is valid.
Thanks to Declan Vibert, Worldprogramming, ENGLAND.
Change 39.203 SMF 82 Subtype 24 INPUT STATEMENT EXCEEDED RECORD LENGTH
VMAC82 because MXG expected label length of 64, but at least
Nov 2, 2021 since 2019, the length is shown as 72. This update
protects both lengths.
Thanks to Nick Varley, Precisely, USA.
Change 39.202 Protection for invalid BMC Control-D CSV records that
VMACCTLC did not have a pair of double quotes, and subsequent
Oct 23, 2021 records that did not have a valid datetime.
Change 39.201 MXG 39.06-39.08, ERROR: PHYSICAL FILE DOES NOT EXIST if
VMAC50 you have added SMF 50 (VTAM) processing to your BUILDPDB,
Oct 22, 2021 AND if your JCL does NOT have an //INSTREAM DD. Full text
ERROR: PHYSICAL FILE DOES NOT EXIST userid.INSTREAM.DATA
Debugging statement referencing INSTREAM was not removed.
The //INSTREAM DD is in all of the MXGSASxx JCL examples:
//INSTREAM DD UNIT=SYSDA,SPACE=(CYL,(1,20)),
// RECFM=FB,LRECL=80,BLKSIZE=0
and it is used in several MXG programs when MXG creates
SAS code "in stream" and then %INCLUDE INSREAM; is used
to execute that code.
Thanks to Wayne A. Schumack, USBank, USA.
Change 39.200 Support for DB2 zHyperlink new data.
VMACDB2 -Dataset DB2ACCTB and DB2ACCTP new variables.
Oct 21, 2021 QBACIOC ='READS*WITH DISK*CACHE HITS'
QBACSYI ='SYNC I/O*READS WITH*ZHIPERLINK'
QBACSYIT='CPU TIME*FOR SUCCESS*ZHYPERLINK*READS'
QBACSWU, QBACHRE, QBACHRF, QBACHWR, QBACHWF Reserved
-Dataset DB2ACCT new variables
QB1CIOC/SYI/SYIT QB2CIOC/SYI/SYIT QB3CIOC/SYI/SYIT
QB4CIOC/SYI/SYIT
-Dataset DB2STATB new variables.
QBSTNSG ='FAILED*CONDITIONAL*SEQUENTIAL*GETPAGE'
QBSTSYIO='SUCCESS*READ I/O*USING*ZHYPERLINK'
QBSTSIOC='READ I/O*DISK CACHE*NO ZHL'
-Dataset DB23STATS
QB1TNSG/SYIO/SYC QB2TNSG/SYIO/SYC QB3TNSG/SYIO/SYC
QB4TNSG/SYIO/SYC
Thanks to Scott Barry, SBBTechLLC, USA.
====== CHANGES THRU 39.199 ARE IN MXG 39.08 DATED Oct 15, 2021 ========
Change 39.199 Support for Broadcom SYSVIEW 16.0 and PTF LU02954.
VMACSVIE -IMS SV34TRAN variables IMTR_TRN_ENQPCB/ABCODE/CPUTIME are
Oct 12, 2021 now always INPUT; previously they were erroneously input
only for Fast Path Transactions. And new variables are
added in SV34TRAN:
IMTR_CNT_LOCK_HWM/LOCK_TOTAO/DB2SQL IMTR_CLK_IFP_CPU
IMTR_CLK_UNKN IMTR_CLK_DB2 IMTR_CLK_MQ IMTR_CLK_WOLA
IMTR_CLK_LAST_DLI
and added in SV35TRAN:
IMRA_DB_CALL_TIME IMRA_MSG_CALL_TIME
IMRA_IFP_ROUTECODE IMRA_IFP_TRANCODE
IMRA_IFP_TRANCOUNT IMRA_IFP_MSGIWAIT
IMRA_RGN_OCCUPYRATIO IMRA_RGN_STARTSQ6
IMRA_RGN_ACCUMSQ6 IMRA_LOCK_HWM IMRA_LOCK_TOTAL
IMRA_LAST_DLI IMRA_MAX_DLI_DB IMRA_MAX_DLI_DC
IMRA_MAX_ESS
In addition, the variables output in dataset SV34DAC now
create a set of variables in SV34TRAN, one per DLI call
type:
IMTR_DAC_DBGU IMTR_DAC_DBGN IMTR_DAC_DBGNP
IMTR_DAC_DBGHU IMTR_DAC_DBGHN IMTR_DAC_DBGHNP
IMTR_DAC_DBISRT IMTR_DAC_DB IMTR_DAC_DBREPL
IMTR_DAC_TOTDB_CALLS IMTR_DAC_MSGGU IMTR_DAC_MSGGN
IMTR_DAC_MSGISRT IMTR_DAC_MSGPURGE IMTR_DAC_TEST_ENQ
IMTR_DAC_TEST_ENQ_WT IMTR_DAC_TEST_DEQ
IMTR_DAC_QCMD_ENQ IMTR_DAC_QCMD_ENQ_WT
IMTR_DAC_QCMD_DEQ IMTR_DAC_UPDT_ENQ
IMTR_DAC_UPDT_ENQ_WT IMTR_DAC_UPDT_DEQ
IMTR_DAC_EXCL_ENQ IMTR_DAC_EXCL_ENQ_WT
IMTR_DAC_EXCL_DEQ IMTR_DAC_MSG_CMD IMTR_DAC_MSG_GCMD
IMTR_DAC_MSG_CHNG IMTR_DAC_MSG_AUTH IMTR_DAC_MSG_SETO
IMTR_DAC_APSB_CALLS IMTR_DAC_DPSB_CALLS
IMTR_DAC_GMSG_CALLS IMTR_DAC_ICMD_CALLS
IMTR_DAC_RCMD_CALLS IMTR_DAC_CHKP_CALLS
IMTR_DAC_XRST_CALLS IMTR_DAC_ROLB_CALLS
IMTR_DAC_ROLS_CALLS IMTR_DAC_SETS_CALLS
IMTR_DAC_SETU_CALLS IMTR_DAC_INIT_CALLS
IMTR_DAC_INQY_CALLS IMTR_DAC_LOG_CALLS
IMTR_DAC_DLI_DB_DEQ IMTR_DAC_VSAM_READS
IMTR_DAC_VSAM_WRITES IMTR_DAC_OSAM_READS
IMTR_DAC_OSAM_WRITES IMTR_DAC_TOTAL_IO
IMTR_DAC_ESAF_NORM IMTR_DAC_FLD_CALLS
IMTR_DAC_POS_CALLS IMTR_DAC_RLSE_CALLS
IMTR_DAC_SAVE_CALLS IMTR_DAC_RSTR_CALLS
IMTR_DAC_COPY_CALLS IMTR_DAC_ICAL_CALLS SYSTEM SMFTIME
In addition, the variables output in dataset SV34SUMM now
create a set of three IMTR variables in SV34TRAN, one set
for each DC Monitor Event type, and variables output in
dataset SV35EVNT create a set of three IMRA variables in
SV35TRAN one for each DC Monitor Event type:
IMTR_EVNT_BALG_DEQUEUE_COUNT
IMTR_EVNT_BALG_DEQUEUE_MTIME
IMTR_EVNT_BALG_DEQUEUE_TTIME
IMTR_EVNT_CHECKPOINT_COUNT IMTR_EVNT_CHECKPOINT_MTIME
IMTR_EVNT_CHECKPOINT_TTIME
IMTR_EVNT_DEDB_LOCK_IWAIT_COUNT
IMTR_EVNT_DEDB_LOCK_IWAIT_MTIME
IMTR_EVNT_DEDB_LOCK_IWAIT_TTIME
IMTR_EVNT_DEDB_OTHRD_IWAIT_COUNT
IMTR_EVNT_DEDB_OTHRD_IWAIT_MTIME
IMTR_EVNT_DEDB_OTHRD_IWAIT_TTIME
IMTR_EVNT_DEDB_READ_IWAIT_COUNT
IMTR_EVNT_DEDB_READ_IWAIT_MTIME
IMTR_EVNT_DEDB_READ_IWAIT_TTIME
IMTR_EVNT_DLA_DB_COUNT IMTR_EVNT_DLA_DB_MTIME
IMTR_EVNT_DLA_DB_TTIME IMTR_EVNT_DLA_MSG_COUNT
IMTR_EVNT_DLA_MSG_MTIME IMTR_EVNT_DLA_MSG_TTIME
IMTR_EVNT_DMB_LOAD_IWAIT_COUNT
IMTR_EVNT_DMB_LOAD_IWAIT_MTIME
IMTR_EVNT_DMB_LOAD_IWAIT_TTIME
IMTR_EVNT_DMB64_LOAD_IWAIT_COUNT
IMTR_EVNT_DMB64_LOAD_IWAIT_MTIME
IMTR_EVNT_DMB64_LOAD_IWAIT_TTIME
IMTR_EVNT_ESS_CALL_COUNT IMTR_EVNT_ESS_CALL_MTIME
IMTR_EVNT_ESS_CALL_TTIME IMTR_EVNT_IFP_ACTIVITY_COUNT
IMTR_EVNT_IFP_ACTIVITY_MTIME
IMTR_EVNT_IFP_ACTIVITY_TTIME
IMTR_EVNT_IFP_BUFFER_ACT_COUNT
IMTR_EVNT_IFP_BUFFER_ACT_MTIME
IMTR_EVNT_IFP_BUFFER_ACT_TTIME
IMTR_EVNT_IFP_MSG_IWAIT_COUNT
IMTR_EVNT_IFP_MSG_IWAIT_MTIME
IMTR_EVNT_IFP_MSG_IWAIT_TTIME
IMTR_EVNT_HSAM_IWAIT_COUNT IMTR_EVNT_HSAM_IWAIT_MTIME
IMTR_EVNT_HSAM_IWAIT_TTIME
IMTR_EVNT_ICAL_DLI_CALLS_COUNT
IMTR_EVNT_ICAL_DLI_CALLS_MTIME
IMTR_EVNT_ICAL_DLI_CALLS_TTIME
IMTR_EVNT_MSDB_WRITE_IWAIT_COUNT
IMTR_EVNT_MSDB_WRITE_IWAIT_MTIME
IMTR_EVNT_MSDB_WRITE_IWAIT_TTIME
IMTR_EVNT_OSAM_IWAIT_COUNT IMTR_EVNT_OSAM_IWAIT_MTIME
IMTR_EVNT_OSAM_IWAIT_TTIME
IMTR_EVNT_PI_ENQUEUE_IWAIT_COUNT
IMTR_EVNT_PI_ENQUEUE_IWAIT_MTIME
IMTR_EVNT_PI_ENQUEUE_IWAIT_TTIME
IMTR_EVNT_PSB_LOAD_IWAIT_COUNT
IMTR_EVNT_PSB_LOAD_IWAIT_MTIME
IMTR_EVNT_PSB_LOAD_IWAIT_TTIME
IMTR_EVNT_PSB64_LOAD_IWAIT_COUNT
IMTR_EVNT_PSB64_LOAD_IWAIT_MTIME
IMTR_EVNT_PSB64_LOAD_IWAIT_TTIME
IMTR_EVNT_QMGR_IWAIT_COUNT IMTR_EVNT_QMGR_IWAIT_MTIME
IMTR_EVNT_QMGR_IWAIT_TTIME
IMTR_EVNT_SCHEDULER_IWAIT_COUNT
IMTR_EVNT_SCHEDULER_IWAIT_MTIME
IMTR_EVNT_SCHEDULER_IWAIT_TTIME
IMTR_EVNT_STORAGE_IWAIT_COUNT
IMTR_EVNT_STORAGE_IWAIT_MTIME
IMTR_EVNT_STORAGE_IWAIT_TTIME
IMTR_EVNT_SYNC_CALLOUT_COUNT
IMTR_EVNT_SYNC_CALLOUT_MTIME
IMTR_EVNT_SYNC_CALLOUT_TTIME
IMTR_EVNT_VSAM_IWAIT_COUNT IMTR_EVNT_VSAM_IWAIT_MTIME
IMTR_EVNT_VSAM_IWAIT_TTIME
IMTR_EVNT_VSO_AREA_CASTOUT_COUNT
IMTR_EVNT_VSO_AREA_CASTOUT_MTIME
IMTR_EVNT_VSO_AREA_CASTOUT_TTIME
IMTR_EVNT_VSO_PRELOAD_COUNT
IMTR_EVNT_VSO_PRELOAD_MTIME
IMTR_EVNT_VSO_PRELOAD_TTIME
Adding IMTR_DAC and IMTR_EVNT and IMRA_EVNT variables
will DOUBLE the size of the SV34TRAN (1658 per obs vs
812) and of the SV35TRAN (1147 vs 661), and they are
still available in the much smaller SV34DAC/SV34SUMM
and SV35EVNT datasets. Typically only a handful of
those variables will be populated in the transaction
observations, but they still take space. They can be
removed and only the IMS datasets written to //PDB with
%LET MACKEEP=
MACRO _IDSVIE 255 %
MACRO _KSV34TR DROP= _DR34DA _DR34EV %
MACRO _KSV35TR DROP= _DR35EV %
_NSVIE
MACRO _WSV34TR SV34TRAN %
MACRO _WSV34DA SV34DAC %
MACRO _WSV34DL SV34DLI %
MACRO _WSV34SU SV34SUMM %
MACRO _WSV34ES SV34ESS %
MACRO _WSV35TR SV35TRAN %
MACRO _WSV35EV SV35EVNT %
MACRO _SSVIE
_SSV34TR _SSV34DA _SSV34DL _SSV34SU _SSV34ES
_SSV35TR _SSV35EV
%
;
%INCLUDE SOURCLIB(TYPSSVIE);RUN;
If you do not want to sort any of the datasets, and
want the two TRAN datasets written to separate DDs
with the smaller datasets going to PDB, you can use:
%LET MACKEEP=
MACRO _IDSVIE 255 %
MACRO _KSV34TR DROP= _DR34DA _DR34EV %
MACRO _KSV35TR DROP= _DR35EV %
;
%LET WSV34TR=SV34TRAN;
%LET WSV35TR=SV35TRAN;
%LET WSV34DA=PDB;
%LET WSV34DL=PDB;
%LET WSV34SU=PDB;
%LET WSV34ES=PDB;
%LET WSV35EV=PDB;
%INCLUDE SOURCLIB(TYPESVIE);RUN;
Thanks to Don Cleveland, Anthem BCBS, USA.
Thanks to James Robbins, Broadcom, USA.
Change 39.198 TYPE50 OSA Express Accelerated Packets was added by
VMAC50 Change 39.198, but was incorrectly spelled. The correct
Oct 8, 2021 spelling is TY50PKAC.
Thanks to Tom White, Bank of America, USA.
Thanks to Jim Sherpey, Bank of America, USA.
Change 39.197 Format $MG119CF only decoded a handful of the 357 Hex
FORMATS values, many for ZERT, for dataset TYP119111 variable
Oct 7, 2021 S11912SC_TLS_NEG_CIPHER and S119SS_TLS_NEG_CIPHER in
TYP11912TLS dataset. The doc is located in the TLS Cipher
Suite registry at http://www.iana.org/assignments/
tls-parameters/tlsparameters.xhtml
Thanks to Heimir Hauksson, Barclays, ENGLAND.
Change 39.196 MXG 39.07. Change 39.183 added SMF6XSTCKE to TYPE6156,
VMAC6156 but the insert caused an INPUT STATEMENT EXCEEDED. The
Oct 7, 2021 code is bypassed until test data is received. You can use
%LET MACFILE= %QUOTE(IF ID IN (61,65,66)) THEN DELETE;
to circumvent, but request the new VMAC6156 from Support
Thanks to Jim S. Horne, Lowe's, USA.
Change 39.195 New parameters USEVMXGSET=YES & DEFER=YES adds OPEN=DEFER
BLDSMPDB to the SET statement when building weekly PDB. Use only
VSETMNTH when running on zOS and tape drives are at a premium and
Nov 26, 2021 daily PDBs are on tape. As always when using OPEN=DEFER
only variables that exist in the first dataset are
carried forward, so the first DDNAME should be the day of
the week pointed to by the WEEKSTART argument.
Thanks to Robert Olah, ENSONO, USA.
Change 39.194 Change 39.137 MXG39.05 CPUTOTTM incorrectly higher than
VMAC30 CPUTM because the calculation of SRVTCBTM which affects
Sep 30, 2021 CPUTOTTM was being done before the removal of ZIPUNITS.
Variables AVGWKSET CPUTOTTM CPUUNITS were corrected, but
the CPUTM, which is a direct value in the SMF record, has
always been correct. The CPUTOTTM based on Service Units
was created because at one time some folks incorrectly
thought the service unit based metric was significantly
more accurate than the recorded time.
Thanks to Stephen Hoar, Lloyds Banking, ENGLAND
Thanks to Mark Tomlinson, Lloydsbanking, ENGLAND.
Change 39.193 SELSMF program is similar to UTILGETM/VMXGGETM, to select
SELSMF and write SMF records of each type, but it adds SYSTEM
Oct 6, 2021 and for DB2 and CICS, the RELEASE to the criteria, and
writes the first 50 records for each selection. You can
also use MACFILE to choose which IDs you want to select;
see the example in comments.
Thanks to John Donoghue, AIB, IRELAND.
Change 39.192 -Dataset ZRBRCD added wait fields RCDWTY1-RCDWT15.
ADOCRMFV -Dataset ZRBSCL added R741Dxxx variables originally added
ASMRMFV to TYPE 74 Subtype 10 Monitor I by Change 38.089.
IMACRMFV -z/OS 2.5 MXG RMF Monitor III support.
VMACRMFV -New MXG Support for 4 more RMF III tables:
Oct 8, 2021 CPUDB IQDG3 LOKG3 VRIG3
*** New Support ***
-Support for the RMF Monitor III CPU Data Block Table
(CPUDB) recently documented with z/OS 2.5 . The CPUDB
table has existed at least since z/OS 2.1.
-The CPUDB selection option is CPV (alias N). The CPUDB
filtering option is NOCPV (aliases -CPV, -N). CPUDB is
also selected if the BASIC select group option is used.
-The CPUDB is a companion table to the CPCDB and CPUG3
tables. If any one is selected all 3 are selected. If
any one is filtered all 3 are filtered.
-Support for the RMF Monitor III I/O Queuing Performance
Data Table (IQDG3) table recently documented with z/OS
2.5 . The IQDG3 table has existed at least since z/OS
2.1.
-The IQDG3 selection option is IQD (alias Q). The IQDG3
filtering option is NOIQD (aliases -IQD, -Q). IQDG3 is
also selected if the MOST group selection option is used.
-The IOQ parameter in the RMF III startup member defaults
to IOQ(DASD). Other device classes are also supported
for IOQ by RMF III. See the RMF User's Guide (z/OS 2.3
and earlier) or the Data Gatherer User's Guide (z/OS 2.4
and up) for more details. NOIOQ will suppress the
generation of IQDG3 table.
-Support for the RMF Monitor III Lock Performance Data
Table (LOKG3) table recently documented with z/OS 2.5 .
The LOKG3 table has existed at least since z/OS 2.1.
-The LOKG3 selection option is LOK (alias #). The LOKG3
filtering option is NOLOK (aliases -LOK, -#). LOKG3 is
also selected if the MOST group selection option is used.
-The LOCK parameter in the RMF III startup member defaults
to NOLOCK. NOLOCK will suppress the generation of LOKG3
table and related MXG data sets. Specify LOCK to
generate the LOKG3 table.
-Support for the RMF Monitor III VSAM RLS Information
Data Table (VRIG3) table recently documented with z/OS
2.5 .
-The VRIG3 selection option is VRI (alias $). The VRIG3
filtering option is NOVRI (aliases -VRI, -$). VRIG3 is
also selected if the MOST group selection option is used.
-The VRIG3 collection parameter in the RMF III startup
member defaults to VSAMRLS and data is grouped by storage
class. In addition, up to 50 VSAM data set sphere masks
may be specified. See the RMF User's Guide (z/OS 2.3 and
earlier) or the Data Gatherer User's Guide (z/OS 2.4 and
up) for more details. NOVSAMRLS will suppress the
generation of VRIG3 table and related MXG data sets.
*** Enhancements ***
-Auto Selection of any field in the CPCDB and CPUG3 table
when using an IF= expression for FDF will now Auto Select
all 3 CPU companion tables (CPCDB/CPUDB/CPUG3). Auto
Selection occurs when an IF= expression references a
field name in a table that has not been explicitly
selected.
-These documentation sections in member ADOCRMFV are all
updated:
2 Terminology
4 RMF III Table Selection Parameters
12 Messages
13 Filtered Records
15 Program and IBM Limitations
23 RMF III Options That Effect Data
26 ASMRMFV and MXG PDB Data Relationship
31 Field Data Filtering (FDF)
32 Data Dictionary Descriptions
57 Summary
58 Bibliography
Change 39.191 An example z/OS ICETOOL job that selects MVIMS xF9 & xFA
ICETOOL log records to reduce the size of the IMSLOG file to be
Sep 21, 2021 read with the ftp access method for ASCII MXG execution.
Thanks to Sir Hari Kolusu, IBM DFSORT, USA.
====== CHANGES THRU 39.190 ARE IN MXG 39.07 DATED Sep 20, 2021 =======
Change 39.190 -ASMRMFV Field Data Filter (FDF) support for the RMF III
ADOCRMFV CPC data control block (CPCDB) and the Processor Data
ASMRMFV Control Block (CPUG3).
VMACRMFV -The Field Data Filter (FDF) feature of RMF III was added
Sep 19, 2021 in MXG Change 37.089 and supports filtering of raw or MXG
derived RMF data values when ASMRMFV reads the RMF III
VSAM file, reducing the size of the created RMFBSAM file
and the size of the result MXG PDB.
-RMF III table entries can be filtered by FDF based on one
or more numeric/character/bit fields using AND/OR logic.
FDF is intended for advanced MXG users building ad hoc
PDBs of RMF III data for studies and investigations.
-A z/OS LPAR is a z/VM guest if this message appears in
the ASMRMFV log:
RMFV009I ORIGIN : CPCNAME=VMGUEST
-NOTE: For LPARs running as z/VM guests the CPC LPAR and
Logical Processor Sections in the CPCDB table are created
by RMF III as binary zeros and cannot be filtered with
FDF. MXG PDB variables sourced from the CPC LPAR and
Logical Processor sections will have SAS missing values
in the result PDB.
In this case only the sparse CPCDB header will be written
to RMFBSAM. Any FDF filters for fields in either of
these two sections will be bypassed. They are NOT
counted as IGNORE in message RMFV080I.
-NOTE: For z/OS LPARs running as z/VM guests RMF III
creates the Home LPAR section in the CPCDB table as all
binary zeros and these fields cannot be filtered with
FDF. MXG PDB variables sourced from the Home LPAR
section will have SAS missing values in the result PDB.
In this case any FDF filters for fields in the Home LPAR
section will be counted as IGNORE in message RMFV080I.
-FDF VNT (Variable Name Table) derived floating point
variables with ASISASSC as a divisor were using a fixed
point binary divisor instead of a short floating point
divisor.
- FDF VNT entry for derived variable R745IORATE had
incorrect data type of FP instead of FPAVG.
-Further reduction of ASMRMFV assembly output with
NODXREF, NOESD, NORLD, USING(NOMAP) added to *PROCESS
statements.
-Expand RMFV092E table error message from 2 to 4 lines to
show more RMF III information at time of the error.
-FDF calculations for CRYG3 table MXG derived variables
CRYTIME0-CRYTIME5 were incorrect.
-FDF calculations for CRYG3 table MXG derived variables
CRYUTIL0-CRYUTIL5 were incorrect.
-FDF calculations for DVTG3 table for 6 MXG derived
variables DVTAVG* were incorrect. These were being
handled as floating point while the source fields are
fixed binary.
-FDF IF evaluation code not correctly checking for PCI
format code when comparing a variable that has one.
-FDF IF evaluation code tests for STOP/NOSTOP and
SYNC/NOSYNC for FDF SSHG3 table were incorrect.
-XCFSTAT variable was missing from XCFG3 FDF VNT table.
-Message RMFV017I now displays z/OS 2.5 when processing
RMF Monitor III data from that release.
-New filter options ZEROLP/NOZEROLP added for CPCDB table
processing. The default is NOZEROLP.
- ZEROLP says to output to RMFBSAM all LPAR sections and
their respective Logical Processors Sections from the
CPCDB table even if zero Logical Processors were defined
for an LPAR. This was the behavior of prior ASMRMFV
versions.
-NOZEROLP says to only output to RMFBSAM LPAR sections
from the CPCDB table that have a non-zero number of
Logical Processors defined. NOZEROLP is the default.
-ZEROLP/NOZEROLP option added to message RMFV006I.
-ASMRMFV no longer outputs zero Logical Processor Sections
to RMFBSAM for those undefined for a specific LPAR. The
CPCDB table reserves 240 Logical Processor Sections for
each LPAR. The actual number defined will be far less.
-In a test using a single RMF III VSAM data set with the
default NOZEROLP in effect output to RMFBSAM for the
CPCDB table was reduced by 8MB. Actual results may vary.
-In ASMRMFV detail and summary reports TOTAL BYTES OUTPUT
in message RMFV104I did not match ALL total of detail or
summary lines in message RMFV105I by a consistent value
of 3400 bytes less.
-First RMF and Z/OS Version numbers added to MXG01 record.
-Last RMF and Z/OS Version numbers added to MXG02 record.
-Data Dictionaries in the ADOCRMFV member have been
updated or added for all FDF supported RMF III tables.
-Many Data Dictionary entries now have additional notes
describing the entry in addition to similar text already
present in the corresponding section documentation.
-Following Sections are updated or added in the ADOCRMFV
documentation member:
Section Contents
------- --------
0 Contents
7 Output Data Control Parameters
12 Messages
15 Program and IBM Limitations
26 ASMRMFV and MXG PDB Data Relationships
31 Field Data Filtering (FDF)
32 Data Dictionary Descriptions
33 Filtering The ASIG3 Table
34 Filtering The CATG3 Table
35 Filtering The CFIG3 Table
36 Filtering The CPCDB Table
37 Filtering The CPDG3 Table
38 Filtering The CPUG3 Table
39 Filtering The CRYG3 Table
40 Filtering The CSRG3 Table
41 Filtering The DSIG3 Table
42 Filtering The DVTG3 Table
43 Filtering The ENCG3 Table
44 Filtering The ENTG3 Table
45 Filtering The GEIG3 Table
46 Filtering The OPDG3 Table
47 Filtering The PCIG3 Table
48 Filtering The SCMG3 Table
49 Filtering The SPGG3 Table
50 Filtering The SSHG3 Table
51 Filtering The XCFG3 Table
52 Filtering The ZFXG3 Table
57 Summary
58 Bibliography
Change 39.189 Variable SMF70TYP is now KEPT in TYPE70PR, eliminating an
VMAC7072 UNINITIALIZED variable message that had no impact but was
Sep 16, 2021 un-needed.
Change 39.188 Support for CICS-DB2 ATTACH APAR PH31440 "accounting"
FORMATS fields to DB2ACCT dataset:
VMACDB2 QMDAAEYE $EBCDIC36. /*QMDAAEYE*EYE*CATCHER*/
Sep 16, 2021 QMDAADT1 $EBCDIC64. /*QMDAADT1*1ST*ADAPTER*/
QMDAADG2 $EBCDIC64. /*QMDAADT1*2ND*ADAPTER*/
QMDAADG3 $EBCDIC64. /*QMDAADT1*3RD*ADAPTER*/
Note: LENQMDA=260,24 undoc bytes after DG3 PH31447.
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 39.187 New TYPE80TK values create new variables
VMAC80A TOKHUKID TOKCRITIC TOKZERTI TOKTECHNIK TOKORGA
Sep 15, 2021 TOKMASTERID TOKBMKS TOKCREATED TOKABPFZ TOKINTERVAL
TOKINFO TOKVERANTW1-TOKVERANTW4
Thanks to Harald Seifert, HUK-COBURG, GERMANY.
Change 39.186 Support for APAR OA61368 which populates two bits in the
VMAC30 RAXFLAGS which are new variables in TYPE30 datasets:
Sep 13, 2021 SMF30_RAXFLAG5='RAX5*ATTEMPT*EARLY*RUCSA?'
SMF30_RAXFLAG6='RAX6*ALLOW*EARLY*RUCSA?'
Change 39.185 IMACKEEP included so that you can customize and tailor
ASUMCICS without touching the ASUM member.
Sep 8, 2021
Change 39.184 -Support for NDM-CDI PTF UI76063 that sets a flag bit if
VMACNDM NDMNODEF='S' (CDZ was acting as SNODE) the PNODE/SNODE
Sep 4,2021 values were wrong and had been corrected for Version 6 or
for Version 5.2, if the bit is NOT on, then MXG has made
the correction. MXG sets NDMFLAG'N' for the NDM change
or NDMFLAGX='M' if MXG reversed the PNODE and SNODE, in.
the CT, FI, and MC records.
-Support for PTF UI76043 which corrects the NDMCPU Time
("TIMEUSED" field) which was wrong (too large) in 6.0.
Thanks to Tom White, Bank of America, USA.
Change 39.183 New variable SMF6XSTCKE, the SMF datatime in STCKE is
VMAC6156 added to TYPE6156 dataset.
Sep 4, 2021 See Change 39.196.
Change 39.182 The UTILEXCL tailoring MACRO _ECICDIC contained a LABEL
UTILEXCL statement that restricted the use of that exit; the LABEL
Sep 3, 2021 variables were moved to the existing LABEL statement at
the top of the code block.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.181 Variables BOOSTACTIVE and BOOSTCLASS are added to the
BUILD005 PDB.STEPS dataset, and BOOSTCLASS is only populated if
BUIL3005 BOOSTACTIVE is populated in SMF 30 and SMF 89 records.
FORMATS Format MG090EV was expanded and typo corrected.
VMAC30
VMAC89
Aug 30, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.180 Enhanced MXGABND can set Condition Code instead of ABEND,
IMACABND The use of %LET MXGABND=nnn in your tailoring was added
VMAC110 and documented in Change 23.184 to cause an ABEND for
Aug 28, 2021 some error messages, but this caused BUILDPDB to ABEND
due to an SMF 110 EXCLUDED fields errors. This change
lets you choose to set a Condition/Return Code so that
you can identify there was a problem, but BUILDPDB will
complete and you can find the ERROR message in the log.
You can test for the Condition Code in a new step and
send a message that a change was detected.
In addition, the ABEND will only occur on z/OS; on ASCII
the ABEND kills the current session which is nasty to
debug! Currently the IMACABND is only implemented in
the SMF 110 processing. To change, you would tailor
IMACABND per its comments into your "USERID" PDS.
Thanks to Dawn Clarke, ENSONO, USA.
Change 39.179 Support for Dino VelociRaptor SMF records,
EXVELO01 DDDDDD DATASET DESCRIPTION
EXVELO02 VELO01 VELOST01 VSAM OPTIMIXATION
EXVELO04 VELO02 VELOST02 QSAM BUFFER OPTIMIZATION
FORMATS VELO04 VELOST04 QSAM BLOCKSIZE OPTIMIZATION
IMACVELO
TYPEVELO
TYPSVELO
VMACVELO
VMXGINIT
Aug 27, 2021
Thanks to Kihun Cha, Navy Federal, USA
Change 39.178 Support for Dell PRF Monitor MFE Version 8.5 SMF data.
EXPRFDBK DDDDDD DATASET DESCRIPTION
EXPRFDEV PRFSYM PRFSYMME SYMMETRIX
EXPRFDMF PRFDBK PRFDBKEN BACKEND
EXPRFDOP PRFDOP PRFDOPEN OPEN SYSTEM
EXPRFDPO PRFDMF PRFDMFRA MAINFRAME
EXPRFDSR PRFDSR PRFDSRDF SRDF
EXPRFSYM PRFDPO PRFDPORT PORTS
EXPRFTDV PRFDEV PRFDEVIC DEVICE
FORMATS PRFTDV PRFTTDAT TDAT DEVICE
IMACPRF
TYPEPRF
TYPSPRF
VMACPRF
VMXGINIT
Sep 1, 2021
Change 39.177 JES3 ONLY, and only if you tailored UTILBLDP BUILDPDB=NO
VMAC110 and USERADD=25 26J3 with INCLAFTR=BUIL3005. The 25 caused
Aug 24, 2021 the WORK.TYPE25 data set to be created and sorted to the
PDB.TYPE25 (done for all USERADD=) but also WORK.TYPE25
was deleted, but BUIL3005 expected WORK.TYPE25, causing
ERROR: DATA SET WORK.TYPE25 WAS NOT FOUND. Removing the
%VMXGDEL in _S25 macro leaves WORK.TYPE25 to correct.
Change 39.176 Support for CICS/TS 6.1 (INCOMPATIBLE, field inserted).
VMAC110 One new field, SOTLSLVL='INBOUND*TLS*LEVEL*SELECTED'
UTILEXCL is added to dataset CICSTRAN. Because the CICSTRAN
Aug 23, 2021 record is a concatenation of control blocks, when IBM
adds a field at the end of a control block, it still
shifts all subsequent fields, requiring an MXG Update.
This change is only for CICSTRAN; other new fields for
other datasets will be added when test data is available.
Change 39.175 Support for BMC CONTROL-D CSV FILE, a log for audit of
EXCTLCSV the webserver. The INFOLE name is BMCCSVIN to create:
IMACCTLC DDDDDD DATASET DESCRIPTION
TYPECTLC CTLCSV CTLDCSV CONTROL-D CSV
TYPSCTLC
VMACCTLC
VMXGINIT
Aug 22, 2021
Thanks To Craig Collins, State of Wisconsin, USA.
Thanks to Maggie Buday, State of Wisconsin, USA.
Change 39.174 TYPE41VF dataset, variables SMF41YAG and SMF41MAG contain
VMAC41 "high" values of 0FFFFFFFF which indicate that no
Aug 19, 2021 trimming occurred, but confused calculations, so those
values are now set to a missing value.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.173 New Format $MGNDMCP for variable NDMCPEA decodes the
FORMATS CIPHER Suite values.
VMACNDM VALUE $MGNDMCP
Aug 19, 2021 '01'X='01X:NULL_MD5'
'02'X='02X:NULL_SHA'
'03'X='03X:RC4_MD5_EXPORT'
'04'X='04X:RC4_MD5_US'
'05'X='05X:RC4_SHA_US'
'06'X='06X:RC2_MD5_EXPORT'
'09'X='09X:DES_SHA'
'0A'X='0AX:TRIPLE_DES_SHA_US'
'2F'X='2FX:AES_128_SHA'
'3C'X='3CX:???????????'
'3D'X='3DX:???????????'
'35'X='35X:AES_256_SHA'
'9C'X='9CX:???????????'
'9D'X='9DX:???????????'
'E7'X='E7X:???????????'
'EF'X='EFX:???????????'
OTHER=?< $HEX2. ?>
Change 39.172 Support for SMF14DSENCARCHKEY flag that indicates that
VMAC1415 the encrypted dataset is being accessed with an archived
VMAC62 key that only supports decrypt operations in TYPE1415.
Aug 18, 2021 Support for SMF62ARCKEY flag that encrypted data set is
being accessed with an archive key that only supports
decryption.
Change 39.171 WPS ONLY. A problem has been found with the use of the
FLASH INPUT statement reading values into temporary array
Aug 18, 2021 members with informats, resulting with incorrect values
(zero or a missing value) for these "TYPE70" variables:
NRZIPCPU NRPHYCPS AVCPSCPU AVICFCPU
AVIFACPU AVIFLCPU AVZIPCPU NRCPSCPU
PLATBUSY PLATCPUS PLATZIPBUSY PLATZIPCPUS
PLATIFLBUSY PLATIFLCPUS PLATICFBUSY PLATICFCPUS
PARTNCPU PARTNICF PARTNIFL PARTNZIP
as their INPUT includes S70CTN(_I_) &PIB.2. array syntax.
The error was introduced in wps-4.03.01, but earlier
versions (4.00, 4.01, 4.02, and 4.03.00 are unaffected.
The error was fixed in these releases:
WPS 4.04.00.03.3277 15-Aug-2021 (MB)
First maintenance version of WPS 4.4 containing the fix
WPS 4.04.00.03.3369 7-Sep-2021 (EA3)
Current EA version of 4.4, containing the fix.
WPS 4.03.02.00.8569 13-Aug-2021 (MB)
First maintenance version of WPS 4.3 containing the fix
WPS 4.03.03.00.8595 2-Sep-2021 (GA)
Current GA version of WPS 4.3, containing the fix.
Change 39.170 Variable SMF9040ID was defined as a character thru 39.03,
VMAC90A but was decoded as numeric in 39.05, so combining old and
Aug 11, 2021 new TYPE9040 data sets raised a conflict. Now, SMF9040ID
is no longer created and TYPE9040IDNR is numeric and is
decoded. You may need to copy your old TYPE9040 dataset
and drop variable TYPE9040ID before you run that WEEKBLD.
Thanks to Jim S. Horne, Lowe's, USA.
Change 39.169 Unused Change Number.
Change 39.168 -Improvements and corrections to PROCSVP subroutine
ASMRMFV segmentation of SVPG3 table when longer than 32756 bytes.
VMACRMFV -PROCSVP subroutine always moves 32760 bytes to output
EXZRBV15 buffer for unsegmented SVPG3 tables even if not needed.
EXZRBV16 -ZOSTABLE updated to 797 for RMF version for z/OS 2.5.
EXZRBIQD -Debugging PUTLOGs (added in 39.06) for SVP removed.
IMACRMFV -ASMRMFVF and ASMZOSVF fields added to MXG01 record with
VMXGINIT first RMF and first z/OS version in each RMF III VSAM
Aug 22,2021 file, and ASMRMFVL and ASMZOSVL fields added to MXG02
record with last RMF and last z/OS version. Those fields
and the ASMRMFV Version and Create Date are printed on
the log of the TYPERMFV execution.
-There are three new RMF III tables added by z/OS 2.5,
IODG3, LOKG3, VRIG3, and old table CPUDB is documented,
to be supported when we have we have an interested user
with those tables enabled.
-MXG 39.06 supports all existing tables in z/OS 2.5.
-New variables in /OS 2.5 manual added to ZRBRCDS dataset.
RCDTETX='TOTAL*TRANSACTION*ELAPSED'
RCDXETX='TOTAL*TRANSACTION*EXECUTION'
RCDQDTX='QUEUE*DELAY*TIME'
RCDADTX='RESOURCE*AFFINITY*DELAY*TIME'
RCDCVTX='JCL*CONVERSION*DELAY'
RCDIQTX='INELIGIBLE*QUEUE*TIME'
RCDRTDM='MIDPOINT*OF RESPONSE*TIME'
RCDPRS ='PAGE*RESIDENCY*TIME'
RCDCIOU='TOTAL*I/O*USINGS'
RCDCIOD='DASD*I/O*DELAY*SAMPLES'
RCDCIDL='IDLE*SAMPLES'
RCDCUNK='UNKNOWN*SAMPLES'
RCDPADJSCF='SCALING*FACTOR*FOR*RCDPADJ'
RCDPADJ='PHYSICAL*CPU*ADJUST*FACTOR*FOR CP'
====== CHANGES THRU 39.167 WERE IN MXG 39.06 DATED Aug 12, 2021 ========
Change 39.167 PDBOUT= parameter added so that you can retain the
ANALINIT datasets created.
Aug 10, 2021
Change 39.166 COMPALL is a test programs that compiles all MXG programs
TECHNOTE that process SMF records in a single step, to detect any
COMPALL cases where temporary variables (not kept) in products
COMPIBM have conflicting attributes (especially NUM and CHAR).
Aug 10, 2021 It also reports the resources needed for this irrational
program. Windows 10 required 3693 MiB, but failed on
z/OS where only 1588 MiB was available. The 940,00
lines of code required 3 minutes elapsed, 30 CPU seconds.
COMPIBM tests only the IBM created SMF records, and that
program did complete on z/OS where it needed 903 MiB.
Change 39.165 Format $MGSMFID is updated for SMF ID=1153 and 1154 types
FORMATS and comments in IMACSMFF revised since IBM owns 0-127 and
IMACSMFF 1152-2047 and 128-1151 are now the available USER types.
Aug 9, 2021
Thanks to MP Welch, BOA, USA.
Change 39.164 NMONUARG records containing only the PID and FULLCOMD
VMACNMON were previously deleted, but now THCOUNT=1 is set so the
Aug 2, 2021 record is output.
Change 39.163 Support for JES2 Monitor SMF Type 1153 record replacement
EX1153J2 for Type 84 Subtype 21 JES2 Monitor in z/OS 2.5. Three
EX1153JM data sets are created:
EX1153JR DDDDDD DATASET LABEL SUBTYPE
IMAC1153 11532 J11532 JES2 PRODUCT + GENERAL n/a
TYPE1153 1153JM J1153JM JES2 MEMORY 1
TYPS1153 1153JR J1153JR JES2 RESOURCES 1
VMAC1153 This is the first IBM record with Extended SMF Header
VMACSMF which has the "normal" SMF ID=126 in original header,
VMXGINIT and the real ID in the extended header. IBM owns the
Aug 9, 2021 IDs 0-127 & 1152-2047 while 128-1151 are for users.
Change 39.162 Some variables had a length of 8 that should have been
VMXGRMFI set to 5 on zOS or 6 on ASCII.
Aug 1, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.161 INHERIT KEEPLEN are now always invoked in PROC MEANS in
VMXGSUM VMXGSUM to preserve input variable attributes.
Aug 1, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.160 Data set DB2STATB now has BPHITRAT kept and the equation
VMACDB2 was revised based on IBM DB2 12 Performance Guide.
Jul 30, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.159 New variable in RMF III dataset ZRBGEI added:
VMACRMFV GEIFLG22='RUCSA*IS*DEFINED?'
Jul 30, 2021
Change 39.158 Support for Quick Select SMF records creates 5 datasets:
EXQSEL00 dddddd dataset description
EXQSEL01 QSEL00 QSELSM00 QSELSM START
EXQSEL02 QSEL01 QSELSM01 QSELSM THREAD
EXQSEL03 QSEL02 QSELSM02 QSELSM QSEL STOP
EXQSELPG QSEL03 QSELSM03 CACHE DEALLOCATION
FORMATS QSELPG QSELSMPG PROGRAMS
IMACQSEL
TYPEQSEL
TYPSQSEL
VMACQSEL
VMXGINIT
Jul 29, 2021
Change 39.157 ONLY if you installed MXG's IEFU84 SMF Exit to put the
IEFU84 INITNUMB and INITNAME fields in the SMF 30 records,
Jul 28, 2021 WPS did not correctly handle 'NOT IN' when the (...)
text had both character and hex strings, causing blank
in INITNAME and bad INITNUMB. The WPS Error was fixed
in WPS version 4.3.2 Build 8525
("wps-4.3.2.0.8525-ga-maintenance-zos").
Change 22.136 describes MXG's IEFU84 SMF Exit.
Thanks to Steve Bagshaw, ITMetrics, ENGLAND.
Change 39.156 WPS does not yet support compress on a LIBNAME statement.
VMXGALOC Now, if compress=yes is specified, it is set to null.
Jul 28, 2021
Change 39.155 DB2 removed Hiperpools and Buffer Pools in DATA SPACES in
VMACDB2 DB2 V8.1, but QDBPHPSZ appears to be reused by IBM, so it
Jul 28, 2021 is now set missing for 8.1 or later.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.154 Support for VIRTEL AUDIT VIRSTAT SMF record creates:
EXVIRSTB DDDDDD DATASET DESCRIPTION
EXVIRSTC VIRSTB VIRSBIN VIRTEL BINARY HTTP INBOUND
EXVIRSTH VIRSTC VIRSTAT VIRTEL VIRSTAT CLASSIC FORMAT
IMACVIRS VIRSTH VIRSHTTP VIRTEL HTTP INBOUND.
TYPEVIRS -VIRSTIME and VIRSDURCALL corrected Aug 17, 2021.
TYPSVIRS
VMACVIRS
VMXGINIT
Jul 28, 2021
Aug 17, 2021
Thanks to Maggie Buday, State of Wisconsin, USA.
Thanks to Craid Collins, State of Wisconsin, USA.
Change 39.153 -New variables in TYPE83LD dataset:
EXTY8308 LDAP_TARGET_MESSAGE_ID LDAP_DISCONNECT_CAUSE
EXTY8311 -Five Relocate Segments have multiple observations that
EXTY8312 create these new datasets with the list of attributes:
EXTY8313 TYP83208 LDAP ADD ATTR
EXTY8320 TYP83211 LDAP MOD ATTR DEL
IMAC83 TYP83212 LDAP MOD ATTR ADD
VMAC83 TYP83213 LDAP MOD ATTR REP
VMAC83 TYP83220 LDAP SEARCH ATTRS
VMXGINIT -Those datasets may not be useful and they can be quite
Jul 26, 2021 large. If you determine you don't need them, insert
this statement in //SYSIN and they will all have zero
observations and will take no space.
%LET MACKEEP=
MACRO _ETY8308 %
MACRO _ETY8311 %
MACRO _ETY8312 %
MACRO _ETY8313 %
MACRO _ETY8320 %;
Thanks to Nathan Loewenthal, CITIGROUP, USA.
Change 39.152 New parameter TRNDOUTCODE allows you to insert SAS code
VMXGRMFI before the OUTPUT TRNDRMFI is executed.
Jul 22, 2021
Change 39.151 New variables that were not kept in CIMSTRAN now are:
VMACCIMS TRNMISCH TRNOTEIP TRNOVHD TRNW5GSP
Jul 22, 2021
Thanks to Sieghart Seith, FICUCIA, GERMANY.
Change 39.150 The read and write bucket count pairs are now correctly
VMACRMFV read in a pair of 4-byte READ PCIRDREADVARnn and 4-byte
Jul 19,2021 WRITE PCIRDWRITCNTnn for each of the 15 counters pair.
====== CHANGES THRU 39.149 ARE IN MXG 39.05 DATED Jul 16, 2021 ========
Change 39.149 The rarely used DB2STATB DB2 Buffer Pool dataset has been
VMACDB2 wrong for some time for 8-byte DIF()d counters, just now
Jul 15, 2021 reported.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.148 A missing ; on the LIBNAME TREND statement caused this
VMXGALOC ERROR: Libref TREND is not assigned.
Jul 16, 2021 -If you invoked VMXGALOC from IMACINIT with READONLY
set to NO a CC=8 was generated and a scary sounding
message was on the log. Now no CC is set, the
message is suppressed unless MXGDEBUG=VMXGALOC is
used and READONLY is set to YES.
Thanks to Ervin Claxon, CSX, USA
Change 39.148 A missing ; on the LIBNAME statement caused this error:
VMXGALOC ERROR: Libref TREND is not assigned.
Jul 15, 2021 -If you invoked VMXGALOC from IMACINIT with READONLY
set to NO a CC=8 was generated and a scary sounding
message was on the log. Now no CC is set, the
message is suppressed unless MXGDEBUG=VMXGALOC is
used and READONLY us set to YES.
-If you dont want to run weekly and/or monthly, WEEKKEEP=0
and MNTHKEEP=0 will suppress the creation and allocation
of WEEKS and MONTHS.
Change 39.147 -CICSTRAN variable OADATA1 is decoded into datetime+text,
VMAC110 but the hex value is needed to match TYPE123A records so
Jul 15, 2021 new variable ADATA1X is the $CHAR64 input $HEX128 format,
-If you have an tailored IMACEXCL in USERID.SOURCLIB, you
need to find MACRO _VCICTRN ABCODE and add OADATA1X:
MACRO _VCICTRN KEEP= ABCODE OADATA1X
A later change will add OADATA1X when UTILEXCL creates a
new IMACEXCL.
Variable ISIOWTTM is now correctly formated TIME12.2
Thanks to Al Hirst, Wells Fargo, USA.
Change 39.146 -MONTHBL3 the JES3 monthly for BUILDPD3, had two instances
MONTHBL3 of _MNTHBLD and the second was missing an IF statement
MONTHPDB that dropped OBS where ZDATE was less than the start of
Jul 12, 2021 the last week, resulting in some duplicate OBS in
monthly datasets.
-New MONTHPDB member is an example generic monthly job
that is easier to tailor since you can specify what
datasets to keep and which to drop. It is also simpler to
rerun if needed without the need to edit MXG MACROS.
Change 39.145 SMF 110 Subtype 1 MNSEGCL=5 (NOT CICSTRAN) ABEND CICS 5.3
VMAC110 INPUT STATEMENT EXCEEDED if CICSRDPL Resource DPL Detail
Jul 11, 2021 optional dataset is enabled with CICS/TS 5.3. The CICRDD
segment in this back-level CICS was only 32 bytes but MXG
expected 40, and apparently no other 5.3 site had turned
on the optional DPL segment. The circumvention is to put
%LET MACFILE=
%QUOTE(IF ID=110 AND SUBTYPE=1 AND MNSEGCL=5
THEN DELETE; ) ;
in your //SYSIN.
And if you are unable to easily EDIT your job's SYSIN,
you can override the //SYSIN in your JCL with:
// EXEC MXGSASxx
//SYSIN DD *
%LET MACFILE=
%QUOTE(IF ID=110 AND SUBTYPE=1 AND MNSEGCL=5
THEN DELETE; ) ;
// DD DSN=YOUR.NORMAL SYSIN,DISP=SHR
Thanks to Bryan Willers, Sirius, USA.
Thanks to Ned Day, Sirius, USA
Change 39.144 The z/OS NOCAPSOUT option prints SASLOG messages in mixed
CONFIGXX case, which we need for debugging. With ODS, USS, LINUX
Jul 9, 2021 commands in SYSLOG messages, we need to see the exact
text that was executed Even though it is the default,
it is set in CONFIGs to override a SAS CAPSOUT option.
Change 39.143 Format $MGSMFID did not describe SMF 123 Subtype 2,
FORMATS Liberty z/OS Connect Endpt.
Jul 9, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.142 Model 204 requires a separate SMF record ID for each3of
VMACM204 the four macros defined in VMACM204 lines 26-37.
Jul 8, 2021 Some character hex variables are now formatted $HEX.
Thanks to Linda Berkeley, DISA Mainframe, USA.
Change 39.141 Updates to SYSVIEW IMS datasets SV34TRAN and SV35TRAN.
VMACSVIE Many new fields have been added, with some corrections.
Jul 14, 2021
Change 39.140 If you specified READSMF=YES and PDBOUT=WORK an error
ANALMSUS resulted:
Jul 8, 2021 ERROR: UPDATE VIEWS ARE NOT SUPPORTED.
caused by using the same name on output and on input in a
data step where a VIEW was specified.
Thanks to Roger Lowe, NT.GOV, AUSTRALIA.
Change 39.139 Change 39.092 erroneously bypassed the creation of the
VFMT102 FORMAT and QA failed with a FORMAT NOT FOUND. Now the
Jul 6, 2021 FORMAT is created even when zero OBS are detected.
Change 39.138 A new RMF Interval is started when the processor speed is
VMAC7072 changed, but changing only the number of CPUs does NOT,
Jul 7, 2021 and the TYPE70 had a negative value for LCPUPDTM in the
PHYSICAL LPARNAME, but when read as a positive binary.
those leading 'FFFF...'x became 256E09 corrupting all of
the CPU reporting for PHYSICAL. MXG now protects by
detecting the LCPUPDTM is greater than the DURATM and
setting it to zero. A service report is open with IBM
RMF Data Gathering and an APAR is expected.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.137 Change 29.025 dealt with small negative CPUUNITS and set
VMAC30 CPUUNITS=0 if CPUTCBTM was 0, and AVGWKSET was only
Jul 1, 2021 calculated if CPUUNITS were non-zero. By relocating the
SRVTCBTM to use the original CPUUNITS, and then using
MAX(CPUTCBTM,SRVTCBTM) for the AVGWKSET more obs were
populated.
Thanks to Stephen Hoar, LLoyds Banking, ENGLAND.
Change 39.136 SAS does not permit special characters in variable names,
RMFINTRV except for the underscore. If you have service classes
UTILWORK names with a special character and use UTILWORK to build
VMXGRMFI your RMFINTRV code, VMXGRMFI fails with syntax errors.
Jul 1, 2021 because the service class/report class name is used as
the first part of the variable name; class BAT#PROD
becomes BAT#PRODCPU etc. MXG now detects the bad names
flags them with error messages, and changes them to a
name of BADNAMEx where x is the number of bad names that
were detected. RMFINTRV file is created, but CC=5 is
set as a warning.
Thanks to Miguel Fernandez, BNYMELLON, USA.
Change 39.135 Change 39.080 caused an ABEND on zOS, but not on ASCII,
ANALDB2R because of a superfluous %END statement error, even
PMAUD02 though the error message said the statement would be
Jun 29, 2021 ignored. This behavior was due to the differing values
for ERRORABEND, which is NOT enabled in ASCII AUTOEXECs,
but is enabled in the z/OS CONFIG members.
Specifying NOERORRABEND the same job ran with CC=8.
Thanks to Wayne A. Schumack, USBank, USA.
Change 39.134 Unused Change Number
Change 39.133 Support for Record 'DB' created new NDMDB dataset.
EXNDMDB NDMRTYPE "HW" and "H2" records do not match the DSECT; at
VMACNDM present these records are skipped until documentation
VMXGINIT matches data. NDMRTYPE "SF" is also skipped as it
Jun 25, 2021 only contains a timestamp of no value.
Jul 16, 2021 -Updated Jul 16 and DB record validated.
-Since version 26, NDM has a truncated NDMCERT field that
no one has complained about, so I have suppressed the
ERROR message until a user actually needs NDMCERT and
wants to pursue with NDM Support.
Thanks to Robert Chavez, Florida Power and Light, USA.
Thanks to Rob D'Andrea, NATWEST, ENGLAND.
Change 39.132 Support for Recovery Boost Start/End values in MG090EV
FORMATS format for variable SMF9040E, and and Requestor_ID values
VMAC90A 2021 in MG090ID format for variable SMF9040ID.
Jun 22, 2021 In Error, SMF9040ID was changed to numeric from char.
Aug 16, 2021 in dataset TYPE9040. See Change 39.170.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.131 Updates and corrections for SMF TYPE 50 VTAM Tuning.
VMAC50 New variables in dataset TYPE502R and TYPE502W
Jun 22, 2021 INPIOS ='INBOUND*PIUS*(IPIU)'
OUTPIOS ='INBOUND*PIUS*(OPIU)'
TSWEEP ='TIMER*SWEEPS*(TSWEEP'
QSWEEP ='QUEUE*SWEEPS*(QSWEEP)'
NRWRIREC ='NUMBER*OF WRITE*RECORDS'
NRREAREC ='NUMBER*OF READ*RECORDS'
Change 39.130 If you did not specify PDBOUT= or used PDBOUT=WORK a
READDB2 message was generated telling you that the output would
Jun 21, 2021 go to WORK. Message is now suppressed if PDBOUT=WORK.
Change 39.129 If you asked for 102.xxx or ID you could get this error
UTILBLDP when UTILBLDP built the code to clear the substitution
Jun 21, 2021 macros
ERROR: Old-style macro name _ID102.xxx must contain...
Change 39.128 TYPE71 variables PAGBLAV and PAGBLMX were reversed.
VMAC71
Jun 16, 2021
Thanks to Greg Goshia, Westfield, USA.
Change 39.127 The Liberty SMF Type 123 Subtype 2 4-byte variable SYSTEM
VMAC123A INPUT from the SMF Header was overwritten by the 8-byte
Jun 17, 2021 SYSNAME/CVTSNAME field that I had incorrectly also INPUT
into SYSTEM. Now the SYSTEM and SYSNAME are correct.
Thanks to Al Hirst, Wells Fargo, USA.
Change 39.126 The PRINT=YES option only printed 20 observations instead
VMXGFIND of printing all observations of each datasets.
Jun 15, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.125 The STCKE GMTOFF92 was wrong; the STCKE returned value
VMAC92 is 60 years larger than current, causing invalid times
Jun 14, 2021 for those datetime variables.
Change 39.124 Enhanced to support specification of multiple basedirs.
VGETALOC See the Linux example in the member.
Jun 11, 2021
Change 39.123 -INVALID DATA FOR ENDTIME in TYPE16 record had only the
VMAC16 the time part populated. IBM support pointed out that the
Jun 21, 2021 ICERSUB=3 is a "Short Record Unsuccessful Execution" and
"Depending on the severity of an unsuccessful run,
information might not be provided in some fields in the
SMF record. There were 17 records with 3, but only one
with invalid ENDTIME, and now the dump and error message
are suppressed if that variable is invalid.
-IBM variable ICESZRNU identifies why zSORT was NOT USED,
and a zero value is supposed to mean zSORT WAS used, but
these records with a zero also have ICEFLBY5='N' flag
that zSORT was NOT used. Now, MXG sets IZESZRNU=-1 for
these records that did NOT use zSORT. But only one site
had this issue, a second site only had ICESZRNU=0 only
for zSORT use.
-The zSORT segments were never being INPUT because the
variable LENLEFT was not populated. Variable
Thanks to Rob D'Andrea, NATWEST, ENGLAND.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.122 -ASMRMFV VAR macro code was inadvertently regressed, still
ASMRMFV using the ISHEX macro function that is not supported for
VMACRMFV back level ASM Assembly program. UI47658 is current,
Jun 11, 2021 failure was with UI60352 Dec 18, 2020.
-INPUT STATEMENT EXCEEDED on CPUG3 record, CPCUDBOFF was
a missing value which was only set for CPUVERG=6.
-Additional ASMRMFV validation checks for RMF III SSHG3
table for SSHTIBEG LT SSHTIEND and SSHSMPNR (number of
MINTIME samples) non zero, and will delete the interval
if not satisfied. We have seen only one instance.
Change 39.121 A rerun within the same SESSION failed because we did not
UTILBLDP reset the MACRO _IDs, with ERROR: Old-style macro name
Jun 6, 2021 must contain only letters, digits and underscores.
Change 39.120 VMXGALOC is only for ASCII execution where it allocates
VMXGALOC and manages all of the MXG SAS PDB Data Libraries. IF
Jun 4, 2021 you did not specify FIRSTRUN=YES the first time you ran
it, many libraries were not allocated causing MXGERRORs.
The FIRSTRUN=YES logic should have been used only for
the copy functions and should not have been used to
control the allocation of new PDBs. Now the directory's
existence is tested and allocated if doesn't exist.
Change 39.119 -Support for HSM ZEDC Compression adds variables to the
FORMATS HSMFSRST dataset.
VMACHSM FSR_ZEDC_COMPRESS_PPRCNT='PERCENT*SAVED*BY ZEDC'
Jun 8, 2021 FSR_USER_DATASIZE='FSR*USER*UNCOMPRESSED*DATASIZE'
FSR_COMP_DATASIZE='FSR*COMP*COMPRESSED*DATASIZE'
FSR_COMP='ZEDC*OMPRESSED*BEFORE*MIGRATION?
FSR_ZEDC='ZEDC*COMPRESSED*DURING*MIGRATION?'
FSRFMB='FSRBYTR*AND*FSRBYTW*CONVERTED*TO BYTES?'
-USER_DATASIZE/COMP_DATASIZE are valid when FSR_COMP='Y'.
and the PRCNT is valid when FSR_ZEDC='Y'
Thanks to Michael Friske, FMR, USA.
Change 39.118 UTILCPLG utility will copy the SAS log to a file, when
UTILCPLG MXG executes as a batch job, but the log was not copied
Jun 3, 2021 if there were spaces in the directory names. Wrapping
the names in " resolved the error.
Change 39.117 If the eight byte JOBCLAS8 is populated and the one-byte
BUIL3005 JOBCLASS is blank, MXG moved the first byte of JOBCLAS8
VMAC30 into JOBCLASS. But IBM now sets JOBCLAS8='STC' causing
Jun 1, 2021 MXG to set JOBCLASS='S' when there was no such job class.
Now, the original one-byte JOBCLASS is not changed.
Thanks to Robert Chavez, Florida Power and Light, USA.
====== CHANGES THRU 39.116 ARE IN MXG 39.04 DATED Jun 1, 2021 ========
Change 39.116 Support for z/OS 2.5 SMF Manual Changes are all included
May 28, 2021 in MXG 39.04 and there were no INCOMPATIBLE changes.
Change 39.115 If USEBANDS=YES, an annoying note that STAGGERTHIN was
GRAFCEC not valid and THIN was used. STAGGERTHIN was removed.
May 25, 2021
Change 39.114 An INVALID IMAC6ESS GEPARMKY 0027x caused message that
IMAC6ESS the segment was invalid, but the reporting site does not
May 24 2021 use those TYPE6 ESS variables and was unwilling to pursue
with IBM Support. New message ask for you to contact MXG
Support.
Change 39.113 TYPE6 variable SMF6URI is added to the PDB.PRINT
BUILD005 dataset.
BUIL3005
May 21 2021
Thanks to Ervin Claxon, CSX, USA.
Change 39.112 Formats $MGIBMPR and $MGIBMIM add new product name
FORMATS 5655-TM4. These formats are used in SCRT in TYPE89 and
May 26, 2021 and caused NO MWP for IMS Workload.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 39.111 If you are moving from zOS to ASCII and had a hard-coded
VMACSMF SMFEXIT=CICS in an IMAC**** member you could get:
May 23, 2021 NOTE 138-205:
Line generated by the macro variable "SMFEXIT".
82249 cics
----
23
ERROR 23-2: Invalid option name CICS.
when reading SMF data. The SMFEXIT only works on z/OS.
-Remove the %LET SMFEXIT=CICS; statement from the IMAC.
-Documentation Only, VMACSMF was not changed.
Change 39.110 Documentation update for SUPPRESS.
UTILBLDP
May 19, 2021
Change 39.109 More Details for SMF Record Selections, Change 39.025.
VMACSMF showed how _SMF and %LET MACFILE can be used for SMF
May 18, 2021 record selection with a CICS Dictionary example, but the
also creates these "PRODUCT" variables that can be used
for selection, You must set %LET MXGDECOMP=DB2; in SYSIN
to decode Compressed DB2 records using _SMF.
DB2: SUBSYSTEM COMPRESSFLAG ACCUMACFLAG DB2IFCID
QWHSRELN
CICS: SMFPSRVR SUBSYSTEM MNSEGCL MCTSSDCN MCTSSDRL
COMPRESSFLAG
30: SUBSYSTEM
RMF: PRODCMF MVSLEVEL PRODVERSION
80: SUBTYPE=RACFEVNT
MQ: SUBSYSTEM SM115REL PRODVERSION
6: SUBSYSTEM
26: SUBSYSTEM
Change 39.108 Support for BVIR Version R5.x, 8.50.x.x:
VMACBVIR -New variables in BVIR30 for BVIRVERS GE 8:
May 24, 2021 TMPTHROT='TEMP*PREMIG*THROTTLE*THRESHOLD'
TMPPRIOR='TEMP*PREMIG*PRIORITY*THRESHOLD'
Eight Byte input for TVCSIZE USDCACHE USDFLASH
-New variables in BVIR302 for BVIRVERS GE 7:
EHSMRECA='DATA*RESIDENT*IN CACHE'
EHSMNOTY='DATA*UNPREMIGRATED'
EHSMAWRE='DATA*AWAITING*REPLICATION'
EHWMSZPK='DATA*TOTAL SIZE*PREFER*KEEP'
EHWMSZPR='DATA*TOTAL SIZE*PREFER*REMOVE'
EHWMSZPV='DATA*TOTAL SIZE*PINNED*VOLUMES'
EHWMSZRV='DATA*TOTAL SIZE*RESIDENT*WAITING'
EHWMSOBI='OBJECTS*IN TVC*ASSIGNED*PREFGROUP'
-New variables in BVIR11 for BVIRVERS GE 7:
ATMDLCQA='AVERAGE*TIME*DELAYED*COPY*QUEUE*AGE'
ATMDTOCA='DATA XFER*TO THIS*CACHE*FROM DS8K'
ATMDTODI='DATA XFERYFROM THIS*CACHE*TO DS8K'
-New EXTENDED GRID CONTAINER awaits data to decode.
-New PARTSIZE/MIGRSIZE array awaits data to decode
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.107 Long ago there was a 32K limit to the size of macro
VMXGSUM variables and VMXGSUM flagged a warning if INCODE
May 14, 2021 exceeded 30000 bytes (spaces count). Now if SAS is V9 or
higher the limit is 65534.
Change 39.106 This error occurs if you have an old VMAC7072 in USERID
VMAC7072 from MXG Versions 36 or 37. You must always remove any:
May 14, 2021 VMACxxxx or VMXGyyyy members from your USERID tailoring
because your old member will prevent the current member
from being used:
NOTE: Line generated by the macro variable "WTY70".
186016 WORK
____
455
ERROR 455-185: Data set was not specified on the DATA statement
Change 39.105 Infile options EOV=BVIREOV and JFCB=BVIRJFCB are added to
VMACBVIR the BVIRHIST infile to permit creation of the variable
May 12, 2021 SYSTEM. Option END=ENDOFINP already exists.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.104 VMXGINIT sets new macro variable %LET MACEXCL=IMACEXCL;
VMAC110 and VMAC110 is now %INCLUDE SOURCLIB(&MACEXCL); so that
VMXGINIT you can have multiple IMACEXCx member names if needed.
May 13, 2021
Change 39.103 Support for more than 4TB of Real Storage. MXG Variable
VMAC0 REALSIZE (SMF0RST) 1K Blocks is only valid up to 4T-1 and
May 11, 2021 new variable SMF0RS4K counts 4K blocks online at IPL.
z/OS 2.5 plans to allow up to 16 Terabytes of memory.
Change 39.102 Support for z/OS Connect EE SMF 123 Subtype 2 record adds
VMAC123A new variable SM123S2_TRACKING_TOKEN in dataset TYPE1232.
May 11, 2021
Change 39.101 Unused Change Number.
May 11, 2021
Change 39.100 -New ASMRMFV Field Data Filter (FDF) support for the RMF
ADOCRMFV III Cryptographic Hardware Data Table (CRYG3}.
ASMRMFV -The Field Data Filter (FDF) feature of RMF III was added
VMACRMFV in MXG Change 37.089 and supports filtering of raw or MXG
May 11, 2021 derived RMF data values when ASMRMFV reads the RMF III
VSAM file, reducing the size of the created RMFBSAM file
and the result MXG PDB.
-RMF III table entries can be filtered by FDF based on one
or more numeric/character/bit fields using AND/OR logic.
FDF is intended for advanced MXG users building ad hoc
PDBs of RMF III data for studies and investigations.
-The minimum hardware level required to run ASMRMFV is
raised from a z9 to a z10 machine. IBM end of support
for the z10 was December 2019. This allows ASMRMFV to
use more efficient and fewer machine instructions.
-MXG can provide an archival stabilized ASMRMFV level for
continuing z9 users if needed. This level does NOT have
FDF CRYG3 support and will NOT be further enhanced.
-ADOCRMFV now contains ASMRMFV support status information
for all IBM processor families.
-Improved Table Error Diagnostics (ITED) are added for all
supported RMF III tables. When an RMF III table error
is detected (which should be rare) instead of only
counting the table skip, a dynamically tailored RMFV092E
message will also be issued with further details.
Return Code 0008 will result for RMF III table errors
rather than Return Code 0004 as previously. These merit
contact with MXG Technical Support to resolve the
problem.
-There is an internal ASMRMFV limit of 10 RMFV092E
messages for each RMF III VSAM data set processed. If
reached new message RMV093I is issued and further
RMFV092E messages are suppressed for that data set.
-When AUTOSEL (default) is in effect ASMRMFV now shows the
field name that trigged that automatic RMF III table
selection in message RMFV082I.
Example:
RMFV002I SYSIN : IF=(ASIJOBNA EQ 'MXGJU')
RMFV082I -->NOTE : RMF III ASI TABLE AUTO SELECTED BY
ASIJOBNA <--
-When AUTOSEL (default) in in effect use of any of the
following additional ASMRMFV parameters (and their
respective aliases) will now cause the corresponding RMF
III table to be selected without having to also
explicitly code the corresponding table selection:
Parameter Auto Selects
--------- ---------------
ASIAND ASIG3
ASIOR ASIG3
CSRAND CSRG3
CSROR CSRG3
DVTAND DVTG3
DVTOR DVTG3
OPDAND OPDG3
OPDOR OPDG3
SPGAND SPGG3
SPGOR SPGG3
DEVTYPE= DVTG3
CPCSYSTEM= CPCDB CPUG3
CPUSYSTEM= CPUG3 CPCDB
-Data Dictionaries in the ADOCRMFV member have been
updated or added for these FDF supported RMF III tables:
ASIG3 CFIG3 CRYG3 GEIG3.
-Many tables and charts in ADOCRMFV have been converted to
boxed figures for improved legibility.
-Following Sections are updated or added in the ADOCRMFV
documentation member:
Section Contents
------- --------
0 Contents
2 Terminology
3 Execution JCL
4 RMF III Table Selection Parameters
5 Input Data Selection Parameters
8 Error Handling Parameters
9 JCL and SYSIN Parameter Usage
12 Messages
13 Filtered Records
32 Data Dictionary Descriptions
33 Filtering The ASIG3 Table
34 Filtering The CFIG3 Table
39 Filtering The CRYG3 Table
40 Filtering The GEIG3 Table
53 ASMRMFV Execution and Methods Overview
54 PDB Build Examples With Direct JCL Method
55 PDB Build Examples With TSO Clist Method
56 PDB Build Examples With Dynamic Method
57 Summary
58 Bibliography
-Variable LCPUHWLW='HDW*GROUP*CAPACITY*LIMIT' in ZRBLCP
dataset was misspelled as LCPUHWCA in the INPUT.
-Dataset ZRBCPU variable CPCVALAVL added and CPCABSMSU
is correctly labeled:
CPCABSMSU='ABSMSU*CAPPING*OPTION*SET?'
CPCVALAVL='CAPACITY*VALUES*AVAILABLE?'
-The 96 CPUSTAnn variables in dataset ZRBCPU have been
reserved since z/OS 1.2. They are removed.
Change 39.099 Support for DB2 Netezza/IDAA Accelerator new data fields,
VMACDB2 and correction to DB2 GMT Offset calculation . DB2 does
VMACDB2H not provide a GMT Offset, forcing MXG to use the delta
VMACSMF between SMFTIME-TODSTAMP with fuzzy logic, because SMF is
May 23, 2021 in hundredths while TODSTAMPs are in microseconds, but
MXG logic did NOT account for the 26 leap seconds that
are in all TODSTAMPs, but not in SMFTIMEs, that made the
converted local time 26 seconds later than actual. Now,
the 26 seconds are subtracted from QWHSSTCK before the
GMT corrected calculation and QWHSSTCK is correctly
converted to local time zone to match SMF, and the
GMT Offset is now integer hours.
-Leap Seconds are periodically added (6 since 1997) and
when the next one is scheduled, I'll use the date to
subtract the 27th.
-I've discovered both TODSTAMP and MSEC variables can show
8 decimal digits, with DATATIME28.8 or TIME20.8 formats,
but SAS Support says both only have 6 decimals are valid.
-Protection for invalid offset added in VMACSMF.
Thanks to Marc Di Edwardo, Memorial Sloan Kettering, USA.
Change 39.098 With PDB=SMF the display of VMXGRMFI options was
VMXGRMFI suppressed.
May 11, 2021 -If you specified imacwork=no in lower case it
was not recognized and you could get the out of
balance message. Now IMACWORK USECNTRL USEREPRT
are upcased before any compares are made.
Thanks to Robert Chavez, Florida Power and Light, USA.
Change 39.097 New parameter NOTALLLPARS=NO defaults to running the PROC
VMXG70PR FREQ that tells you which LPARs are missing from the PDB.
May 7, 2021 Specifying NOTALLLPARS=YES suppresses these messages for
when you don't have the RMF data from all LPAR's.
Change 39.096 New variable SMF89SOLUTIONID, the SOLUT= system parameter
VMAC89 is added to datasets TYPE89 and TYPE892. This is the
May 6, 2021 Tailored Fit Pricing Solution ID.
Change 39.095 Typos in comments. For CMODIDNT='393' DEC=394 corrected
UTILEXCL to DEC=393, and WBURIRND corrected to WBURIRCV.
May 6, 2021
Thanks to Charles Piggott, RUV, GERMANY.
Change 39.094 Debugging macro variable DCOLEXIT is defined in VMXGINIT
VMACDCOL and &DCOLEXIT is added to the INFILE so that you can use
VMXGINIT %LET DCOLEXIT=FIRSTOBS=250 OBS=300;
May 5, 2021 to control what records are read. If you instead used
OPTIONS FIRSTOBS=250 OBS=300;
the DATA step will correctly read those selected records,
but the following SORTs and STEPs will fail because they
FIRSTOBS=1 OBS=MAX.
Change 39.093 -DCOLLECT DAILYDSN/VMXGDSN creation of DATASETS.DATASETS
VMXGDSN has been wrong since Change 37.065 in MXG 37.03. In the
May 5, 2021 creation of DATASETS, the original code output the pair
of DATA/INDX obs from DCOLDSET for VSAM files, setting
SPACE1=DCDALLSP (Allocated Space) for each obs.
-That change replaced that pair of obs with one obs from
DCOLCLUS, DSNAME=Cluster Name and with SPACE1=DCAHARBA
as the size of each VSAM cluster, But the total DASD
space is significantly smaller after that change.
-This change follows IBM recommendation to use DCAHARBC,
instead of DCAHARBA and to continue to discard the VSAM
DATA/INDX space from DCOLDSET.
-After this change, the obs count in DATASETS is smaller,
and the VSAM sizes increased to pre-37.065 change.
DASD Space is DCDALLSP - VSAM-DCDALLSP + DCAHARBC
-See also Change 15.108.
Thanks to Terry Chao, Office of Chief Technology Officer, USA.
====== CHANGES THRU 39.092 ARE IN MXG 39.03 DATED May 3, 2021 ========
Change 39.092 Some ANALDB2R reports attempt to map database and object
VFMT102 names using this format but if there were no subtype 105
Apr 29, 2021 records the format could could not be built and a format
not found error could result. Now tells you there was no
data and sets NOFMTERR.
Change 39.091 Support for new variables DB2 IFCID 402 T102S402 dataset:
VMAC102 QW0402OW ='IDLE*THREAD*THRESHOLD*EXCEEDED'
May 2, 2021 QW0402TC ='CURRENT*ACTIVE*THREAD*COUNTER'
QW0402TS ='CURRENT SUSPENDED THREAD COUNTER.
QW0402TH ='HWM*THREAD*COUNTER*SINCE*DDF START'
QW0402CC ='CURRENT*CONNECTIONS*COUNTER'
QW0402CH ='HWM*CONNECTIONS*COUNTER*SINCE START'
QW0402TN1_OFF ='OFFSET*TO FIRST*TOKEN*VALUE'
QW0402TN2_OFF ='OFFSET*TO SECOND*TOKEN*VALUE'
QW0402TN1_LEN ='LENGTH OF FIRST*TOKEN FIELD'
QW0402TN1_VAR ='FIRST*TOKEN*VALUE'
QW0402TN2_LEN ='LENGTH OF*SECOND*TOKEN*FIELD'
QW0402TN2_VAR ='SECOND*TOKEN*VALUE'
-QWHCEUTX='END*USER*TRANSACTION*NAME was added _V102CMN
so it will be kept in ALL T102Snnn Trace Datasets.
Thanks to Manoel DeSouza, FMR, USA.
Thanks to Jonathan D. Brown, FMR, USA
Change 39.090 Support for RACF Pass Ticket Evaluation (8081 PTEVAL)
EXTY8081 creates new TYPE8081 dataset.
FORMATS
IMAC80A
VMAC80A
VMXGINIT
Apr 28, 2021
Thanks to Jim Guzlecki, REFINITIV, USA.
Change 39.089 Velocity XAM storage variables are in pages, but were not
VMACXAM converted to bytes nor formatted with the MGBYTES format.
Apr 27, 2021 These are now internally in bytes, MGBYTES formatted:
RSASTORE SYSTORS SYSVRSZ SYSVRFRE SYSTRCPC
HCPMM1S HCPMM4S RSAPGABL RSANONPG RSAOFFLN
RSARIOSZ CALSCMAX SYSSCMEX RSAGSTOR RSAGOFFL
RSALGFRM SXSSIZE PFXSTLEN PFXFTLEN RSAFNOTI
FIXEDSTO SYSGSTBY SYSGSTRS RSACKMB2G RSACKMA2G
RSAPIN0B RSAPIN0A RSAPIN1B RSAPIN1A RSAPINWP
RSAPINFP
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.088 Report to Count Character Variables with FREQ=FREQ did
ANALJOBN not print anything because there was no TABLES statement,
Apr 27, 2021 causing VMXGPRAL to fail, exposing Change 39.087.
Change 39.087 If there were no variables not in the BYLIST a syntax
VMXGPRAL error occurred pointing at /MISSING.
Apr 27, 2021
Thanks to Rahul Raj, ENSONO, USA.
Change 39.086 Support for HSM UNIX CLOUD Statistics variables added to
FORMATS HSMFSRST dataset for FSRTYPE 25 and 26.
VMACHSM FSRUNIXF='UNIX*SEGMENT*PRESENT?'
Apr 29, 2021 FSRTYPE ='FSR*FUNCTION*TYPE'
FSRCLNML='CLOUD*CONNECTION*NAME*LENGTH'
FSRCLNR ='CLOUD*NETWORK*CONNECTION*NAME'
FSRCLCNT='DFHSMHSM*CONTAINER*NAME*USED'
FSRCLOBN='OBJECTS*CREATED'
FSRPFXNM='PREFIX*OF*OBJECT'
FSR2_UNML/*UNIX*FILENAME*LENGTH'
FSR2_FLGS/*UNIX*FILENAME*FLAGS'
FSR2_UNAM/*UNIX*FILENAME'
FSRFMB ='FSRBYTR*AND*FSRBYTW*WERE IN*MB?'
FSRFXPLC='EXPIRED*FROM*CLOUD?'
-HSM Variable FSRTYPE has additional values that are now
decoded by format MGMSMFU:
24='24:CLASS TRANSITION'
25='25:MIGRATION TO CLOUD'
26='26:RECALL FROM CLOUD'
-Records with FSRTYPE=24 are not output until test data
is available to validate it's contents.
Thanks to Macarena Alonso Alvar, Silk Aplicaciones SLU, SPAIN.
Change 39.085 PDB.ASUMUOW variable TRANNAME should have LENGTH $4 but
VMXGUOW contained only 1 character if MQ data records preceded
Apr 24, 2021 the other records, and SPIN.SPINUOW had observation(s).
Thanks to John Holiday, Queensland Government, AUSTRALIA
Change 39.084 We all know that IO delays can be a problem but we may
TECHNOTE not consider terminal delays to be part of the problem.
Apr 23, 2021 Now that everyone is working from home running SAS in
the foreground (interactive) can be profoundly affected.
Working with a customer on a Linux install we noticed
that SAS initialization took over 1 minute for 1 user
but only 45 seconds for another and locally on my PC a
couple of seconds. Running BUILDPDB against a 6GB SMF
dataset in the foreground took 13 minutes but running
in the background (a batch job) the same program and
the same SMF data ran in 90 seconds. The moral of the
story is IO still matters and LOGS and OUTPUTs back
to your online session are IO and matter.
Change 39.083 Format $MGSMFID did not describe SMF 83 Subtype 7, MFA,
FORMATS Multi-Factor Authentication
Apr 23, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.082 Variable QDSTNCQC was misspelled as QDSTNQWC.
VMACDB2
Apr 23, 2021
Thanks to R. Indumathy, FMR, USA.
Change 39.081 A few non-impacting %PUT "DEBUG" messages were replaced
READDB2 with a conditional test that &MXGDEBUG was enabled.
Apr 21, 2021
Change 39.080 ANALDB2R could fail if PMAUD02 report was requested and
ANALDB2R there were no observations, due to misplaced GOTO.
Apr 20, 2021
Change 39.079 Support for RMF III CRYG3 Cryptographic Hardware Table
EXZRBCRY creates new dataset ZRBCRY.
FORMATS
IMACRMFV
VMACRMFV
VMXGINIT
Apr 28, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.078 -MXG 39.02. ERRORs EXCLUDED FIELDS - SECOND RECORD error
UTILEXCL using the IMACEXCL created by UTILEXCL; there was a typo
IMACICCU $CHAR54 instead of $CHAR64 that caused misalignment.
Apr 15, 2021 -The %INCLUDE inside IMACICCU should be IMACICCD.
Thanks to Negri Gianvittorio, SAS, ITALY
Thanks to Mark Wittie, FMR, USA.
Thanks to Kelly Ballamis, Zions Bank, USA.
Change 39.077 Changes in TYPE70 processing caused PDB=SMF to fail.
VMXGRMFI Logic to read the RMF SMF data needed for RMFINTRV was
Apr 15, 2021 replaced with a %UTILBLDP invocation.
Thanks to Michael Friske, FMR, USA.
Change 39.076 Support for Phoenix JES3plus SMF 84 error correction that
VMACSMF was reported in APAR OA58963 but not corrected by IBM.
VMAC84 The 84 subtype was not in 19-20 so IBM SMF utilities
Apr 15, 2021 could not use SUBTYPE for record selection, The APAR was
closed as a permanent restriction for JES3, but JES2 will
write a new record with ID=126 and four-digit ID=1153
that has subtype in the expected location. For JES3,
JES3plus relocates the subtype to expected location.
This MXG update correctly inputs the SUBTYPE in the
_SMF header macro for all possibilities.
Change 39.075 Updates from SMF Manual dated Apr 5, 2021.
VMAC42 -TYPE42DS New variable: (APAR OA59611)
Apr 12, 2021 S42SNTWJ='SYNC ZHL*WRITES*DISABLED*NEW LAYER'
-TYPE106 New Datasets
TY1063 TYPE1063 BCP ST-1 HWIREST API
TY1064 TYPE1064 BCP ST-2 HWIREST API
Change 39.074 RMF III z/OS 2.4 Updates from Feb 2021 Programmer Guide:
VMACRMFV -Dataset ZRBLCP new variables:
Apr 11, 2021 CPC_BOOSTACTIVE='BOOST*ACTIVE*INTERVAL'
CPC_BOOSTCLASS ='BOOST*CLASS'
-Dataset ZRBCFI new variables
CFISTSC1='INDEX OF*FIRST CFICONNS'
CFISTMRC='NUMBER OF*CFICONNS*ENTRIES'
CFISTMTM='SUMMED*QUEUE*TIME'
-Dataset ZRBASI new variables
ASIORMP ='STORE/OUTR*DELAY*SAMPLES*SR7'
ASIRUCSAA ='RUCSA*ALLOCATION'
ASIERUCSAA ='ERUCSA*ALLOCATION'
-Dataset ZRBGEI new variables
GEIGLUSE='1GB FRAMES*IN USE*MEM OBJECTS'
GEIGLTOT='1GB FRAMES*IN CENTRAL*STORAGE'
Thanks to MP Welch, Bank of America, USA.
Change 39.073 Format $MGMARET for TYPEMAR printed 3990 instead of 3390.
FORMATS
Apr 12, 2021
Thanks to Lloyd Christensen, Hitachi Vantara, USA.
Change 39.072 ZIPOVHTM and PCTZIPOV variables added to ASUMCELP ASUMCEC
VMXG70PR ASUM70PR and ASUM70LP datasets.
Apr 13, 2021
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 39.071 RMF III percentages on System Information and CPC Summary
VMACRMFV reports are identified/revised/created:
Apr 8, 2021 -Dataset ZRBCPU.
These variables are on RMF System Information report.
PCTCPUBY='AVG CPU*PHYSICAL*PERCENT*BUSY';
PCTLOGBY='AVG CPU*LOGICAL*PERCENT*BUSY';
PCTLOGBY/CPUG3_LOGITI. MVS view of logical processor
utilization based on wait time for the processor.
This is "Avg CPU UTIL%" on System Information report.
PCTCPUBY/CPUG3_PHYSTI PR/SM view of physical processor
utilization based on dispatch times.
This is "Avg MVS UTIL%" on System Information report.
-Dataset ZRBLCPLPARS new variables; you must use TYPSRMFV
or invoke _SRMFV to create dataset PDB.ZRBLCPLPARS.
These variables are on the CPC Summary report;
CPUPCTEF='PHYSICAL*EFFECTIVE*PERCENT*BUSY'
CPUPCTBY='PHYSICAL*TOTAL*PERCENT*BUSY'
LOGPCTEF='LOGICAL*EFFECTIVE*PERCENT*BUSY'
LOGPCTBY='LOGICAL*TOTAL*PERCENT*BUSY'
and ZRBLCPLPARS has an observation for each CPU TYPE.
Thanks to Ervin Claxon, CSX, USA.
Change 39.070 Support for DB2 APAR PH31684, SORT usage counters in
IMACDBNZ three datasets, sort sizes for zSORT in IFCID=96, and
VMAC102 these two new NETEZZA variables in DB2ACCT;
VMACDB2 Q8ACTWDP='TIME*WAITED*FOR DELAY*PROTOCOL'
Apr 6, 2021 Q8ACNWDP='STATEMENTS*WITH*EXPIRED*PROTOCOL'
New variables added to DB2STAT1 DB2STATS DB2ACCT
QXSTSRT ='TIMES*RDS SORT*PERFORMED'
QXSTSRTL='TIMES*RDS SORT*USED SORTL'
QXSTMLSRT='TIMES*SORT*FEEDBACK*USED'
QXSTMLSDFND='PREPARE*STABILIZED'
New variables added to T102S096 for IFCID=96:
QW0096RU='QW0096RU*SERVICEABILITY'
QW0096PN_OFF='OFFSET TO PROGRAM NAME'
QW0096PC_OFF='OFFSET TO PACKAGE COLLECTION ID'
QW0096DZ='SORT*DATA AREA*SIZE WITH*SORTL'
QW0096KZ='SORT KEY*SIZE WITH*SORTL'
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 39.069 Some XAMSYS variables were in the KEEP= list for XAMUSR
VMACXAM but they should have been kept in XAMSYT.
Apr 5, 2021
Change 39.068 -Some users have found savings of time using COMPRESS=NO
VMXGALOC as datasets in work have to be repeatedly compressed and
Apr 5, 2021 decompressed. A parameter was added to allow the PDBs
Apr 9, 2021 being created to be compressed while leaving work at the
value specified in your AUTOEXEC. COMPRESS=YES is now the
default value added to every LIBNAME statement issued by
VMXGALOC. Specify COMPRESS=blank or anything other than
YES to disable.
-On Linux only, if you did not specify a BASEYEAR you
could get a SUBSTR OUT OF RANGE error.
Thanks to Arnold Kim, UPS, USA.
Change 39.067 New value '20X:REMOUNT' added to $MG092FM format for
FORMATS variable SMF92MFG in dataset TYPE9201 and SMF92UFG in the
Apr 5, 2021 dataset TYPE9205. ICN 1830.
====== CHANGES THRU 39.066 ARE IN MXG 39.02 DATED Apr 4, 2021 ========
Change 39.066 New parameter USEBANDS= added with a default of NO, will
GRAFCEC creates 'band' charts rather than bar charts.
Apr 4, 2021
Change 39.065 Change 39.029 incorrectly coded PROC FORMAT for the
GRAFWRKX formats $TMPSUEC and $TMPNRCPI that set SU/Sec and NRCPU.
Apr 4, 2021
Change 39.064 The Apr 1 Change 39.060 for HLASM back level protection
ASMRMFV was revised. USE ONLY ASMRMFV DATED APR 2 IN LINE2.
Apr 2, 2021
Thanks to Otto Burgess, OPM.GOV, USA.
Thanks to Robert Richards, OPM.GOV, USA.
====== CHANGES THRU 39.063 ARE IN MXG 39.02 DATED Apr 1, 2021 ========
Change 39.063 Dataset IMS56FA variable DLRDMR is now kept, DLRSMR typo.
VMACIMS
Apr 1, 2021
Thanks to Nick Varley, Precisely, ENGLAND.
Change 39.062 JCL and source to run BUILPDB creating the PDB on a tape
JCLTAPDB and at the same time sending CICSTRAN to tape and all of
BLDTAPDB the DB2 accounting datasets to a third tape dataset.
Mar 31, 2021
Change 39.061 Change 37.260 added JOB_IDENTIFIER but MXG did not change
VMACIDMS the +50 to +42 to preserve alignment.
Mar 30, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.060 Some versions of the HLASM Assembly program fail on the
ASMRMFV ISHEX function, with error message ASMA089E when the
Apr 2, 2021 function appears in a macro definition. Single character
parsing is now used to validate hex characters.
UI73993 Feb 17, 2021 works, UI60352 Dec 19, 2018) failed.
Thanks to Otto Burgess, OPM, USA.
Thanks to
Change 39.059 The GMT Offset in CVTTRZ in TYPE0 was off by one second;
VMAC0 the CEIL and FLOOR functions were reversed.
Mar 30, 2021
Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Change 39.058 Second period for DATA=&PDBMXG..STEPS was missing.
ANALABND
Mar 28, 2021
Change 39.057 INPUT EXCEEDED for defective SMF 16 record with ZSORT
VMAC16 triplet populated, but no ZSORT data, APAR PH32395:
Apr 1, 2021 UI90068 WHEN ZSORT=Y IS IN EFFECT. ERROR DESCRIPTION:
The ZSORT feature does not support SORTs that are program
invoked and using E15 and/or E35 EXITS for input and
output. In this case ZSORT needs to be disabled and use
the traditional sorting techniques, otherwise program
failures like ABEND0C4 may occur. This APAR will improve
this check. One site's data populated ICEFLBY5='Y' that
ZFSORT was invoked, but the offset pointed to the end
of the record where there was no data. A second site
had ten-digit decimal offsets in the ZSORT triplet but
ICEFLBY5 was not y.
-The BroadCom CA-7 SASSHISS program ABENDED with 0C4 as
noted in this document:
https://knowledge.broadcom.com/external/article/209582/
sasshis5-c0c4-abend-was-issued.html
Thanks to Rob D'Andrea, NATWEST. ENGLAND.
Change 39.056 New parameters WEEKINCODE= MNTHINCODE= let you insert
BLDSMPDB code just after the SET statements for weekly and monthly
Mar 28, 2021 processing. An example was added to the comments using
WEEKINCODE to validate the data using ZDATE and to
determine using RMFINTRV if data is not complete (less
than 24 hours in a day) or outside the bounds of the
week. Will issue a WARNING message if problems are found,
print a report of what was found for each day of the
week, and optionally can set cc=4;
Thanks to Denise Willers, ENSONO, USA.
Change 39.055 AUDITAFTER= default value changed to YES. This means that
UTILBLDP PDBAUDIT will run after everything in your INCLAFTR
Mar 28, 2021 parameter rather than after BUILDPDB. The first time you
run you will see a lot of new datasets that are not
really new but were created by MXGINCL and INCLAFTR
members after BUILDPDB ran.
Change 39.054 Variable LOSTRECS/SMF7NROX was conditionally input but
VMAC7 the field is always present, and subsequent variables
Mar 26, 2021 (SMF7LSN,SMF7TBLS) were not input.
Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Change 39.053 The CICSTRAN data for z/OS EE Connect Adapter and for MQ
VMAC110 related tasks create variables OADATA1/OADATA2/OADATA3
Mar 31, 2021 with these different values:
For MQ Related Task
OADATA1=QMGR=MSQ1
OADATA2=INITQ=CICSS001.INITQ
OADATA3=QNAME=MQS1.MQIN.TEST.REPORT
OADID =ID=IBM WebSphere MQ for z/OS V9
For z/OS Connect Related Task
OADATA1 BAQvllPLXTNKX A580 TODSTAMP.
The v field contains 01x= a version number?,
the ll field contains length of data following,
PLXTNKX is the SYSPLEX and A580 is the SYSTEM and
the TODSTAMP (converted with MCTMNTAD to LOCAL)
is always earlier than the SMF time.
But those binary values in the z/OS Connect OADATA1
cause problems if you try to move the data to EXCEL.
So the z/OS Connect record is decoded and the datetime
is now a text field:
OADATA1='BAQ PLXTNKX A580 15MAR2021:11:10:54.217948.
Thanks to Simon Foley, CPT Global, AUSTRALIA.
Thanks to Martyn Jones, CPT Global, ENGLAND.
Change 39.052 TABULATEs consolidated so that for each category you get
ANALINIT one page rather than a page per jobclass. Formats added
Mar 26, 2021 to PROC PRINTs.
Change 39.051 JCLSPGDG example creates GDGs for all MXG "PDB" datasets.
JCLSPGDG The limit for the number of generations in a GDG was 255,
Mar 21, 2021 but in z/OS 2.2, the new EXTENDED option allows up to 999
generations. So you can start a Daily PDB with GDG=1 on
Jan 1, with a limit of 366 and have the GDG number
match the julian date!
Thanks to MP Welch, Bank of America, USA.
Change 39.050 Error Messages from PROC PLOT for all values missing were
JCLPDB94 caused by incorrect OR/AND logic. JCL94PDB now executes
ANALRMFI with CC=0.
ANALMPL
Mar 20, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.049 Format $MGSMFID describes SMF record type and subtype for
FORMATS ANALID reports; the format was missing 116.010.
Mar 18, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.048 The example PDS allocation for MXG.SOURLIB had only 1199
JCLINSTT directory blocks. Without PDS Statistics, 459 blocks are
JCLINSTL used, with PDS statistics, 1607 are needed so examples
Mar 17, 2021 now allocate 1999 blocks so you can have statistics.
Thanks to Jerry Terpstra, Bank of Montreal, CANADA.
Change 39.047 If you tried to run without running _SUOWSPN you got
VMXGUOW errors with SPUNCNT undefined and if you set _LASCICS
ASUMUOW to CICSTRAN.CICSTRAN and bypassed _SUOWCIC you got an
Mar 17, 2021 undefined macro reference. Both problems are fixed.
_SUOWSPN is not needed since the data has to be in the
correct order when it is created. It is commented out
in both the examples and the executable code. It will
not hurt to run it but it will save some time to skip
this sort.
Change 39.046 If you asked for 106 records and did not add T102106=YES
READDB2 the T102S106 dataset was not created. Now if 106 is in
Mar 14, 2021 the IFCIDS and T102106 NE NO it will be built and sorted
into the PDBOUT= LIBNAME.
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.045 If all values to be charted were missing, a blank page
GRAFWRKX was created and if all were 0 a meaningless chart of a
Mar 13, 2021 flat line at 0 on the Y-axis was created. Now charts only
values GT 0.
Change 39.044 Since the second part of the WORKX= was set to SRVCLASS,
UTILWORK which is then used as the label for variables created by
Mar 14, 2021 VMXGRMFI, unless you wrote the WLM policy SRVCLASS may
not be sufficient to identify what the workload
represents. Now, UTILWORK uses the first 20 bytes of the
service class description, except when the service class
is SYSTEM SYSSTC or SYSOTHER.
Change 39.043 Support for z/OS Connect SMF 123 Subtype 2 record creates
ANAL123A New Data Set:
EXTY123C DDDDDD DATASET DESCRIPTION
IMAC123A TY123C TYPE123C z/OS CONNECT API REQUEST
VMAC123A Member ANAL123A will merge the TYPE123C REQUEST dataset
VMXGINIT observation with the corresponding CICSTRAN obs to create
Mar 23, 2021 dataset PDB.CICS123.
Change 39.042 CICS optional CMODHEAD=USER AND CMODNAME=USER incorrectly
IMACICXA pointed to IMACICDU but that should be IMACICXA.
UTILEXCL
Mar 10, 2021
Thanks to Mark Wittie, FMR, USA.
Change 39.041 -If you want to change the destination library to other
ASUM70PR than PDB, VMXG70PR failed with error messages that your
VMXG70PR TYPE70 and TYPE70PR datasets were not found. Now, it
Mar 24, 2021 uses VMXGWORL to try to find it, or if you specify
PDB=yourdd, that will be used.
-If you specified PDB=PDB and the datasets did not exist
a dataset not found error resulted. PDB=libname always
overrides the results of VMXGWORL.
Change 39.040 Defective SMF 1415 records with NUCB=6 but only 5 UCBs
VMAC1415 have invalid SMF14STY values due to that misalignment,
Mar 9, 2021 causing blank values for STEPNAME PROGRAM JCTJOBID and
JESNR is a missing value. All of these records are for
DSNAME='SYS1.HASPACE' and new SMFSTY14='1234567890' is
created to list the subtypes in each record; the value
0 at the end are those with invalid subtypes.
A CASE/PMR is in progress with IBM to correct.
Change 39.039 -The Field Data Filter (FDF) feature of RMF III was added
ASMRMFV in MXG Change 37.089 and allows you to filter raw RMF
ADOCRMFV data values when ASMRMFV reads the RMF III VSAM file,
Mar 8, 2021 reducing the size of the created RMFBSAM file and the
result PDB.
-You can filter RMF III table entries based on one or more
numeric, character, or bit string fields using AND/OR
logic. This feature is intended for advanced MXG users
building ad hoc data PDBs of RMF III data.
-ASMRMFV now supports some MXG Derived Variables from bit
string settings. This relieves some of the cumbersome
lookup and error prone use of bit strings in FDF IF
expressions. Not all bit settings are assigned to a PDB
variable when an MXG PDB build is run. ASMRMFV mimics the
derivation that occurs during the build.
-Bit string MXG Derived Variables are added for RMF III
tables: ASIG3, CATG3, DVTG3, ENCG3, GEIG3, SCMG3, SPGG3.
Other tables supported by FDF do not have bit string
related variables.
-Example: Select Address Spaces using the CPU Protection
bit from the ASIG3 table:
Rather than code the IF bit string expression:
IF=(ASIMSTS EQ B'..1.....')
Now this user friendly alternative is possible:
IF=(ASICPUPR EQ 'Y')
-Data Dictionaries have been updated for all 17 FDF
supported RMF III tables. Derived Variable support is
available where the characters "MASK" appear in a Data
Dictionary entry.
-Many Data Dictionary entries now include one or two NOTEs
to add further information about a Fieldname.
-DEV is now valid as a prefix for some Fieldnames for the
RMF III DVTG3 table. This shortens some long Fieldnames
that formerly all required a DVT prefix.
-Error message RMFV092S is now issued with an error code
should a rare table validation error occur for either the
CATG3 table or SMF 74.5 record within the CATG3 table.
-New Section 32 Data Dictionary Descriptions is added to
the ADOCRMFV member. This provides a central reference
location for this information rather than repeating it
for every FDF supported RMF III table.
-New Section 34 Filtering The Cache Data Information Table
(CATG3) is added to the ADOCRMFV member for the new
support.
-TIP:
When filtering with FDF on the first n characters of a
character field there are two ways to accomplish this
as shown in the examples below:
1) Use a pattern match (* in compare value string)
IF=(ASIJOBNA EQ 'PROD*')
2) Use a shortened compare length (: after operator)
IF=(ASIJOBNA EQ: 'PROD')
Either method will select jobs starting with 'PROD' for
output to the RMFBSAM file.
However, the SECOND method is MUCH MORE efficient.
With Method 1 ASMRMFV must call the internal MATCH
subroutine for EVERY job to evaluate the pattern. With
Method 2 ASMRMFV sets the compare length ONCE (in this
case to a value of 4) for all job name comparisons.
TUTORIAL:
MXG Derived Variable ASICX for the RMF III ASIG3 table
can be useful with ASMRMFV for data selection by Address
Space Type when building a filtered PDB.
Possible ASICX values are:
A ASCH Task AO ASCH Task OMVS Related
B Batch Job BO Batch Job OMVS Related
S Started Task SO Started Task OMVS Related
T TSO User TO TSO User OMVS Related
O OMVS Task
To select Started Tasks only use:
IF=(ASICX EQ 'S') or IF=(ASICX = 'S')
To select OMVS related Started Tasks only use:
IF=(ASICX EQ 'SO') or IF=(ASICX = 'SO')
To select all Started Tasks use:
IF=(ASICX EQ: 'S') or IF=(ASICX =: 'S')
Note that 2 IF expressions are NOT needed.
To select all Started Tasks and all Batch Jobs use:
IF=(ASICX EQ: 'S') or IF=(ASICX =: 'S')
IF=(ASICX EQ: 'B') or IF=(ASICX =: 'B')
Note in this case 2 IF expressions are needed.
-Following Sections are updated or added in the ADOCRMFV
documentation member:
Section Contents
------- --------
0 Contents
2 Terminology
12 Messages
13 Filtered Records
31 Field Data Filtering (FDF)
32 Data Dictionary Descriptions
33 Filtering The ASIG3 Table
34 Filtering The CATG3 Table
35 Filtering The CFIG3 Table
36 Filtering The CPDG3 Table
37 Filtering The CSRG3 Table
38 Filtering The DSIG3 Table
39 Filtering The DVTG3 Table
40 Filtering The ENCG3 Table
41 Filtering The ENTG3 Table
42 Filtering The GEIG3 Table
43 Filtering The OPDG3 Table
44 Filtering The PCIG3 Table
45 Filtering The SCMG3 Table
46 Filtering The SPGG3 Table
47 Filtering The SSHG3 Table
48 Filtering The XCFG3 Table
49 Filtering The ZFXG3 Table
51 PDB Build Examples With Direct JCL Method
52 PDB Build Examples With TSO Clist Method
53 PDB Build Examples With Dynamic Method
54 Summary
55 Bibliography
Change 39.038 Dataset TYPE74CA variable CSSCLN wasn't kept, variable
VMAC74 CSSCOPYST was not INPUT nor kept.
Mar 6, 2021
Change 39.037 Many variables containing percentages were not formatted
VMAC30 with 5.1.
VMAC7072
VMAC74
Mar 2, 2021
Change 39.036 APAR PH35442 corrects Negative CPU time in WebSphere SMF
VMAC120 120 TYP120BL dataset. There were many SMF 120 Subtype 11
Feb 28, 2021 records that had ZERO values for the GMT OFFSET
(SM120BBT), for the TOTAL CPU CLOCK AT REQUEST END
(SM120BCA1), for the CP ONLY CPU CLOCK AT REQUEST END
(SAM1230BCA2), and these zero values cause negative
values in the calculated delta start-to-end times.
Variables SM120BCPUTM SM120BCPCPUTM SM120BZIPCPU were
wrong. Note also that because the GMT OFFSET is 0 in
these records, while the other non-zero records actual
GMT OFFSET is 1, these zero records have their END
DATETIME (SM120BBX) one hour earlier than the SMFTIME!
Change 39.035 Variables ASICR and ASICX were not kept in ZRBASI.
VMACRMFV
Feb 28, 2021
Change 39.034 The LABELs for the pair of SINCE CREATION and SINCE OPEN
VMAC64 variables were reversed; the ACCxxxxx are SINCE CREATION.
Feb 24, 2021
Thanks to Jorge Fong, DOITT NYC GOVERNMENT, USA
Change 39.033 Support for new NDM-CDI SMF record (default 133) creates
EXNDCDHW new dataset:
IMACNDCD DDDDDD DATASET DESCRIPTION
TYPENDCD NDCDHW NDCDCDHW CDzOS High Water Mark
TYPSNDCD You will have to set the MACRO _IDNDCD to 133 or your
VMACNDCD chosen record type. APAR PH35087 is needed to correct
VMXGINIT errors in the initial record contents.
Feb 23, 2021
Thanks to Luis Mendoza, Black Knight, USA.
Change 39.032 No error has been reported with VMXG70PR in MXG 39.01 but
VMXG70PR the DROP/KEEP/INPUT exposure is eliminated.
Feb 22, 2021
Change 39.031 The BETA 93 subtype 50 record was shortened and many
VMACBETA variables no longer exist in dataset BETA50.
Feb 22, 2021
Thanks to Andreas Menne, Finanz Informatik, GERMANY
Change 39.030 Variables added to dataset TYPE3804:
FORMATS S38GMODE ='FUNCTION*STATUS'
VMAC38 S38GDOM ='NETVIEW*DOMAIN'
Feb 22, 2021 and new format MG038GM decodes variable S38GMODE.
Thanks to Stephen Hoar, LLoyds Banking, ENGLAND.
Change 39.029 The $TMPSUEC and $TMPNRCPI FORMATS were updated for all
GRAFWRKX z14 and z15 processors.
Feb 22, 2021
====== CHANGES THRU 39.028 ARE IN MXG 39.01 DATED Feb 17, 2021 ========
Change 39.028 Support for SMF 90 subtype 41 when CVTLSO is changed.
EXTY9041 DDDDDD DATASET DESCRIPTION
IMAC90A TY9041 TYPE9041 CVTLSO CHANGED
VMAC90A
VMXGINIT
Feb 17, 2021
Change 39.027 If you had sorted the CICS stats data to tape (this is
VMXGCICI strongly not recommended) VMXGCICI would first fail with
Feb 17, 2021 an undefined macro variable and when that was corrected
would fail with multiple datasets open in a sequential
data library. While this is NOT a recommended practice it
will now work.
Thanks to Lu Ming, CPF, SINGAPORE.
====== CHANGES THRU 39.026 ARE IN MXG 39.01 DATED Feb 16, 2021 ========
Change 39.026 Support for IBM TAPE CLOUD CONNECTOR SMF record creates;
VMACCLTA DDDDDD DATASET DESCRIPTION
EXCLTA01 CLTA01 CLOUTAP1 CLOUD TAPE STAGE TO DISK
EXCLTA02 CLTA02 CLOUTAP1 CLOUD TAPE COPY TO CLOUD
EXCLTA03 CLTA03 CLOUTAP1 CLOUD TAPE DELETE FROM CLOUD
EXCLTA04 CLTA04 CLOUTAP1 CLOUD TAPE DELETE PROFILE
EXCLTA05 CLTA05 CLOUTAP1 CLOUD TAPE RESTORE FROM CLOUD
IMACCLTA
TYPECLTA
TYPSCLTA
FORMATS
Feb 13, 2021
Change 39.025 Documentation and EXAMPLES for SMF record selections.
VMACSMF In _SMF, which process just the SMF Header, there are
Feb 12, 2021 these subsystem variables created and available in the
IMACFILE/&MACFILE exit to select only wanted records.
RMF 70-79 PRODCMF MVSLEVEL
RMF 78.2 VSTORE
DB2: 100 101 102 SUBSYSTEM COMPRESSFLAG QWHSRELN
PRODVERSION ACCUMACFLAG
SUBTYPE=IFCID FOR SMF 102.
CICS: 110 SMFPSRVR SUBSYSTEM MNSEGCL MCTSSDCN
MCTSSDRL
SMF 30 SUBSYSTEM
SMF 80 SUBTYPE=RACFEVENT
SMF 115,116 SUBSYSTEM SM115REL PRODVERSION
SMF 6 SUBSYSTEM
SMF 36 SUBSYSTEM
1. Duplicate RMF/CMF records CANNOT BE PROCESSED, YOU
MUST SELECT THE DESIRED RECORDS, AND YOU WOULD USE
//SYSIN DD
%LET MACFILE= %QUOTE(IF PRODCMF=:'RMF';); or
%LET MACFILE= %QUOTE(IF PRODCMF=:'CMF';);
This may be required with z/OS 2.5 with CMF, because
z/OS BASE will write RMF 70 records (so sites without
RMF will have 70s for SCRT reports).
2. To detect if you have records from both products,
//SMF DD
//SYSIN DD *
%INCLUDE SOURCLIB(VMACSMF);
DATA _NULL_;
_SMF;
RETAIN CURRPROD;
IF CURRPROD=' ' THEN CURRPROD=PRODCMF;
ELSE IF PRODCMF NE CURRPROD THEN DO;
PUT / '***POTENTIAL ERROR. SEE CHANGE 39.025.'/
' CMF AND RMF RECORDS ARE BOTH FOUND. ' SMFTIME=
ID= SYSTEM=
/+2 PREVSYS= 'PREVPROD=' CURRPROD 'NEWPROD='
PRODCMF +1 PREVTIME= 'ID=' PREVID PREVSYS=;
CURRPROD=PRODCMF;
END;
3. You can create a file of only CICS dictionary records:
//SMF DD DSN=SMF,DISP=SHR
//SMFOUT DD DSN=NEWDICTS,DISP=(,CATLG). .
//SYSIN DD *
%INCLUDE SOURCLIB(VMACSMF);
%LET MACFILE= %QUOTE(
IF ID=110 AND SUBTYPE=1 AND MNSEGCL=1;
FILE SMFOUT DCB=SMF;
PUT _INFILE_;
FILE LOG;
);
RUN;
%INCLUDE SOURCLIB(VMACSMF);
RUN;
DATA _NULL_;
_SMF;
RUN;
4. You can create a file of 1000 CICSTRAN records from
CICS/TS 5.6 with:
//SMF DD DSN=SMF,DISP=SHR
//SMFOUT DD DSB=NEWTRAN,DISP=(,CATLG) . . ..
//SYSIN DD *
%INCLUDE SOURCLIB(VMACSMF);
%LET MACFILE= %QUOTE(
IF ID=110 AND SUBTYPE=1 AND MNSEGCL=3 AND
SMFPSRVR=73;;
FILE SMFOUT DCB=SMF;
PUT _INFILE_;
FILE LOG;
NFOUND+1;
IF NFOUND GT 1000 THEN STOP;
);
RUN;
%INCLUDE SOURCLIB(VMACSMF);
RUN;
DATA _NULL_;
_SMF;
RUN;
Change 39.024 Three new ESS (IEFDOKEY) variables are added to TYPE6:
IMAC6ESS ESSPAGEL='DPAGELBL'
VMAC6 ESSSYSAR='SYSAREA'
Feb 9, 2021 ESSDUPLX='DUPLEX'
Thanks to Jerry Ellis, Liberty Mutual, USA.
Change 39.023 TYPECDC (Infosphere change data capture) records with
VMACCDC only the 92-byte header and no data caused INPUT
Feb 9, 2021 STATEMENT EXCEEDED error. Short records are deleted.
Thanks to Jan Tielemans, KBC, BELGIUM.
Change 39.022 Variables NCPCAPABIZE OVERCOMMIT STORAGESIZE XSTORESIZE
VMACXAM in dataset XAMSYS were misaligned and had missing values.
Feb 8, 2021
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.021 Override PSU70PR/LP/GC/GL DD's may not have worked.
VMXG70PR Depending on how you tried to change the destination,
Feb 12, 2021 with those macro variable DDnames with %LET may not
have been used, and those datasets could have been
written to &PDBMXG (normally PDB) instead of your %LET.
This change corrects to match the documentation.
Change 39.020 UTILWORK creates an RMFINTRV member with your Workloads.
IMACWORK New parameters enhance the useability of UTILWORK.
UTILWORK -IMACWORK=NO suppresses the use of IMACWORK.
Feb 6, 2021 With IMACWORK=YES, you can not have a WORKxx name that
matches an entry in IMACWORK; RMFINTRV will detect the
conflict and terminate.
SYSTEM= if you have multiple systems and you want to
define workloads differently SYSTEM=YES will add the
SYSTEM ID to each workload.
SYSPLEX= if you have multiple sysplex and you want to
define workloads differently, SYSPLEX=YES will add the
SYSPLEX ID to each workload.
In addition the first section of each workload (which
resolves to variable names) is now set to the SRVCLASS
since the restriction on 8 byte names is history.
Finally, the RMFINTRV member created is now printed
on the SASLOG.
Change 39.019 Using SP_REMV='Y', some labels were truncated because the
VMXGPRNT variable LABELR was not set to $80 nor blank padded.
Feb 2, 2021
Thanks to Scott Barry, SBBTechLLC, USA.
Change 39.018 -Some invocations of ANAL9914 caused mismatched %DO-%END
ANAL9914 errors because of a DO instead of a %DO statement. Logic
Feb 4, 2021 was rearranged, conditional execution of SGPANEL removed
and reordering of %VMXGOPTR executions.
-REPORT=JIM is not useable under WPS at this time; REPORT=
RAY is now forced for WPS.
Thanks to Virginie Peigney, CA-GIP, FRANCE.
Change 39.017 DB2 NETEZZA IDAA 100-1 INPUT STATEMENT EXCEEDED due to
VMACDB2 these new DB2 V12 fields and wrong LENREAD calculation.
Jan 31, 2021 You can use %LET MACKEEP= MACRO STOPOVER MISSOVER % ;
in SYSIN to circumvent the ABEND.
This change has not been tested with non-zero values;
only records with all values zero have been read so
none of the accumulated fields are deaccumed.
Please use member SENDDATA to send your SMF 100-1's.
-Variables added to DB2STAT1,DB2STATS,DB2NETZA:
Q8STTMUD='TOTAL MEM*AVAIL*USER DATA*IN MB'
Q8STTMPS='TOTAL MEM AVAIL*SQL/DML*IN MB'
Q8STCQLS='CURRENT*QUEUE*LENGTH'
Q8STOFLW='SORT*OVERFLOWS IN*ACCELERATOR*BACKEND'
Q8STABHR='ACCELERATOR*BUFFERPOOL*HIT RATIO'
Q8STANUI='CURRENT*IN RATE*ACCEL AND DB2*IN KB/S'
Q8STANUO='CURRENT*OUT RATE*ACCEL AND DB2*IN KB/S'
Q8STTSA ='DISK SPACE*IN MB FOR*TEMPORARY*DATA'
Q8STLSA ='DISK SPACE*IN MB FOR*LOG DATA'
Q8STTDPS='SUCCESSFUL*QUERY*REQUESTS*DELAY*PROTO'
Q8STEDPS='QUERY*REQUESTS*EXPIRED*DELAY*PROTOCOL'
Q8STTDPA='SUCCESSFUL*QUERY*REQUESTS*ALL DLYPRO'
Q8STEDPA='QUERY*REQUESTS*EXPIRED*WAITFORDATA'
Q8STVLCS='REPLICATION*VELOCITY*DB2 LOG SEC*PER SEC'
Q8STLRCP='CPU TIME*INT.S.S*ASYNC*LOG READER'
Q8STLRZI='ZIIP TIME*INT.S.S*ASYNC*LOG READER'
Q8STLRZE='ZIIP ELIGIBLE TIME*INT.S.S*ASYNC*LOG'
-Variables added to DB2STAT1,DB2STATS:
QISTLRCP='QISTLRCP*CPU*TIME'
QISTLRZI='QISTLRZI*ZIIP*TIME'
QISTLRZE='QISTLRZE*ZIIP*ELIGIBLE*TIME'
Thanks to Negri Gianvittorio, SAS, ITALY.
Thanks to Alberto Sturla, Banca Carige S.p.a, ITALY
Change 39.016 INCODE and OUTCODE parameters were not displayed with the
VMXGSUM other parameters, so logic that could cause zero obs was
Jan 30, 2021 not shown.
Change 39.015 Job report collected only TYPETASK=JOB so if the problem
ANALMSUS child was an STC it was missed. Now all OBS are used and
Jan 30, 2021 TYPETASK is added to the report.
Thanks to Mike Martin, NCSECU, USA.
Change 39.014 Parameters added to enhance flexibility and allow you to
EMAIL attach files rather than doing a PROC PRINT.
Jan 30, 2021 There are new examples in the member.
New parameters:
ATTACH- list of datasets to attach to email
BODY= text for body of email
the above only apply when attaching a file,
which is mutually exclusive with printing a
dataset. with printing a dataset,
These apply when printing a dataset:
LINESIZE=100
PAGESIZE=100
WHERE= a where clause for the PROC PRINT
Change 39.013 -MXG 34.06-38.38 ASMRMFV ABEND if a Storage Group has over
ASMRMFV 1,361 volumes. Change 34.191 introduced the potential 0C4
Jan 29, 2021 in subroutine PROCSPG when processing RMF III SPGG3 Table
(Storage Group and Volume Data) table, but we had no test
data with that large number of volumes.
Thanks to Victor Li, ATOS, HONG KONG
Thanks to Paul Leung, ATOS, HONG KONG
Change 39.012 z/OS SAS ODS may need an increase in the MEMLEAVE option
TECHNOTE (set in your CONFIGxx member) and MUST use REGION=0M. One
Jan 24, 2021 case SAS Tech Support recommended 1500M and that worked!
This note was originally to be Change 38.235.
Change 39.011 SAGANAL could fail when there unmatched RMF 70 and SMF 30
SAGANAL intervals, so data with SMFTIME GT the last 70 interval
Jan 30, 2021 are deleted.
Change 39.010 DB2 IFCID 172 T102S172 dataset variables QW0172Q4/Q8 are
VMAC102 INPUT $CHAR8 FORMAT $HEX16., QW0172HZ/WZ are INPUT &PIB.8
Jan 21, 2021 and Labels for QW0172HZ/WZ added Holder/Waiter.
Thanks to Jack Hyde, OPTUM, USA.
Thanks to Peter Vikeras, OPTUM, USA.
Change 39.009 TYPE70 PLATxxxxBUSY variables were incorrectly calculated
VMAC7072 adding the PHYSICAL LCPUPDTM to each calculation, but the
Jan 21, 2021 PLAT variables do NOT report this LPAR's utilization as
they calculate the utilization on ALL ENGINES IN THE CEC.
Thanks to Mark Tomlinson, Lloyds Bank, ENGLAND.
Change 39.008 zOS only. SAS ODS Graphics always uses Java, and Java can
TECHNOTE run on zIIP engines with significant CP CPU savings, but
Jan 18, 2021 a JVM file must be APF Authorized when your Java SYSPROG
installed Java. This z/OS message is printed in JOBLOG
(NOT SASLOG) and the JVM still executed correctly and
ended with CC=0, but the zIIP engines are not used:
JVMJ9VM082E Unable to switch to IFA processor
- issue "extattr +a 099 libj9ifa26.so"
"The JVM failed to switch to an IFA (Integrated Facility
for Applications) processor because the JVM library file
libj9ifa%s.so requires APF authorization."
One job running GRAFWRKX and GRAFCEC creating a PDF file
went from 484 CP secs to 107 CP + 146 ZIP = 253 secs.
The zIIP time is not reported by SAS, but the CPU time on
the SAS log is the sum of CP and zIIP can be much larger
than elapsed when zIIPs are used.
Change 39.007 Variable INTRVSYN (is RMF Sync with SMF?) was blank in
VMAC7072 datasets TYPE70xx and TYPE72xx, MXG38.05-38.38.
Jan 15, 2021
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.006 ANAL9914 Topology Report tests for &CECTYPE=Z15 added to
ANAL9914 support the z/15 processors, and the default is now Z15.
Jan 14, 2021
Thanks to Virginie Peigney, CA-GIP, FRANCE.
Thanks to Jim S. Horne, Lowe's Companies, USA.
Change 39.005 Change 38.215 dropped these 4 variables from ASUMCELP.
VMXG70PR IFA70ACS IFA70BPS IFL70ACS IFL70BPS which are now kept.
Jan 8, 2021 IFA values will always be missing or 0.
Thanks to Douglas C. Walter, CITIGROUP, USA.
Change 39.004 ANALID report did not identify CICS Compressed records;
VMACSMF VMACSMF incorrectly bypassed the test to set 'C'.
Jan 8, 2021
Thanks to MP Welch, Bank of America, USA.
Change 39.003 -Support for new variables TOKRABOID TOKKSTNPLTS in
VMAC80A dataset TYPE80TK.
Jan 10, 2021 -Dataset TYPE80TK will have fewer observations; each
token outputs an observation, but now there is a single
observation for each record with all tokens.
Thanks to Andreas von Imhof, RABOBANK, THE NETHERLANDS.
Change 39.002 ***WARNING - TYPETASK NOT DECODED SUBSYS=SAR. TYPE 6 SAR
VGETJESN records do not have a JCTJOBID which is used to create
Jan 5, 2021 TYPETASK. IF SUBSYS='SAR' THEN TYPETASK='SAR'; added.
Thanks to Joey TU, Los Angeles Department of Water and Power, USA
Thanks to Jon Hoang, Los Angeles Department of Water and Power, USA
Change 39.001 Cosmetic. DATEFMT=DATE7., was added to arguments.
VGETDDS
Jan 5, 2021
Thanks to Kenneth W. Pressley, Salt River Project, USA.
LASTCHANGE: Version 39.