* copyright (C) 1984-2019 merrill consultants dallas texas usa

TYPE74 33.305 z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC.

TYPE74 33.316 New variables compatibly added by z/OS 2.2.

TYPE78 33.156 Support for APAR OA44525, z HPF Extended Distance II.

TYPE78 33.305 z/OS 2.2 new variables in TYPE78PA.

TYPE80A 33.036 RACF SMF 80 record, TOKxxxxx fields increased length

TYPE80A 33.243 RACF Type 80 record "subtypes" (RACFEVNT) for ANALID.

TYPE99 33.053 Support for z13 updates to type 99 subtype 14.

TYPE99 33.308 New variables compatibly added by z/OS 2.2.

TYPEAA 33.137 Support for Compuware ABEND-AID USER SMF Record.

TYPEATF 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A2.

TYPEAXWY 33.199 Support for AXWAY SMF record, INCOMPATIBLE, inserts.

TYPEBBMQ 33.030 Support for BMC Mainview for MQ 5.2 (REQUIRED)

TYPEBBMQ 33.090 Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT)

TYPEBBMQ 33.115 Mainview for Mq BBMQBUFF variables corrected.

TYPEBBMQ 33.175 New IHDRBBMQ "Infile Header Exit" for selection.

TYPEBVIR 33.145 BVIR VTS Grid dataset BVIR33 wrong for second plus.

TYPEBVIR 33.196 TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected.

TYPECDC 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2

TYPECIMS 33.114 IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN.

TYPECIMS 33.136 Support for MainView for IMS 5.2 (a/k/a IMF).

TYPECZA 33.166 Support for Correlog z/OS Agent User SMF record.

TYPEDB2 33.025 QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB.

TYPEDB2 33.068 Variable Q8STCCPU not kept after Change 30.133.

TYPEDB2 33.142 Variables QWACATWT and QWACPQCT corrected.

TYPEDB2 33.205 DB2ACCTP variables QPACPKID/LOCN/ may be truncated.

TYPEDB2 33.279 Support for DB2 Simulated Buffer Pool PDB.DB2STSBP.

TYPEDB2 33.303 Multiple DB2 100 Subtype 1 created multiple DB2STATS.

TYPEDOL 33.060 DCOLLECT Cluster/Multi-VOL now have Class variables.

TYPEDOS 33.248 Support for zVSE/Power Version 9 Release 2 accounting

TYPEEDA 33.237 Support for EDA V7706 (INCOMPATIBLE, data inserted).

TYPEID 33.045 ANALID report printed '110.001' vice '110.1.1'.

TYPEIMS 33.034 Variables SYSABEND,USRABEND decoded in IMS56FA.

TYPEIMS 33.298 Support for IMS 14.1 log records (COMPATIBLE)

TYPEIMST 33.252 Variable SYSTEM can be added to TYPE56FA with SYSPARM

TYPEMAR 33.183 Support for MAR Hitachi Command Suite Mainframe

TYPEMGCR 33.212 Support for MEGACRYPTION Version 6, INCOMPATIBLE.

TYPEMWLX 33.037 Support for HP MeasureWare for Linux -

TYPENDM 33.143 INPUT STATEMENT EXCEEDED NDM-CDI PT record.

TYPENDM 33.229 NDM PT records INPUT EXCEEDED, INCOMPAT inserts.

TYPENMON 33.092 Some NMON BBBPnnnn variables were mis-assigned.

TYPENMON 33.104 Support for NMON CPUnr with three digits.

TYPENTMU 33.028 Support for EDS User SMF Record from NETMENU program.

TYPEOSEM 33.133 ZOSEM User SMF - INPUT STATEMENT EXCEEDED error.

TYPEQACS 33.020 iSeries change in record length can force USER ABEND.

TYPEQACS 33.101 Support for iSeries 7.2 (COMPATIBLE, new LRECLs).

TYPERACF 33.238 Support for RACF IRRDBU00 Record Type 1560.

TYPERMFV 33.140 RMF III RCD records INCOMPATIBLY CHANGED for z13.

TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE).

TYPESYNC 33.184 Support for SYNCSORT Release 1.4 (INCOMPAIBLE).

TYPETANZ 33.123 Support for Tandem ZMS Style records.

TYPETHAO 33.059 Support for Thales Security Resource Mgr RF1100.

TYPETMO2 33.099 TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG.

TYPETMO2 33.188 TMON/CICS Version 4.0, REQUIRED, MXG coding error.

TYPETMO2 33.210 More TMON/CICS Version 3 and Version 4 corrections.

TYPETMS5 33.129 Support for TMS new TRTCH values for TS1140.

TYPETPMX 33.070 TOKENID INCLAI, three $LIST_L and $RESTAR added.

TYPETPMX 33.232 Support for Thruput Manager VARNAME=$ORIGIO.

TYPETPMX 33.265 ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong.

TYPEVMXA 33.043 zVM VXUSEACT/VXUSEINT NOT SORTED ERROR.

TYPEVMXA 33.242 Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode.

TYPEVMXA 33.299 Support for zVM 6.3 MONWRITE z13 SMT MODE.

TYPEVMXA 33.327 Data set VMBYUSR missing many observations.

TYPEXAM 33.086 Support for Velocity Software zVPS XAM Version 5.4.

TYPEXAM 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected.

TYPEXAM 33.202 Velocity ZVPS 5.4 XAMSYT had zero observations.

TYPEXAM 33.259 Support for zVPS Release 4230 for z13 SMT mode.

TYPEXAM 33.266 MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND.

TYPEXAM 33.320 Support for zVPS z13 SMT mode new variables.

TYPEXAM 33.324 zVPS variable CALENTMT changed from numeric, conflict

TYPEXPTR 33.040 Support for SystemWare XPTR 5.2 subtype 140, ex-st-40

TYPEZCOS 33.116 Support for ZCOST AutoSoftCapping Version V3.0.00.

UTILBLDP 33.042 Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found

UTILBLDP 33.159 BUILDPDB=NO incorrect for type 102 2 byte subtypes.

UTILCVRT 33.105 Alternate table needed for no TRANSCODE PROC CPORT.

UTILEXCL 33.049 New reports, trans without dictionary, READTIME.

UTILEXCL 33.255 ARRAY EXCEEDED when more than 999 connectors.

VGETDDS 33.208 z/OS Only. Multiple tape mounts with DDNAMES=PDB:.

VMAC115 33.180 Support for MQ Version 8 subtype 215 record

VMAC30 33.005 Support for APAR OA45767 adds zEDC statistics.

VMACUCB 33.245 DEVCLASS=41 decode identities specific CTC type.

VMXGALOC 33.325 Correction for WEEK1 allocation.

VMXGINIT 33.062 %LET MXGDEBUG=FULL; shows OPTIONS, enables diags.

VMXGINIT 33.162 "MXGLOG" option to send MXG Messages to MXGLOG.

See member CHANGESS for all changes ever made to MXG Software, or

the CHANGES frames at http://www.mxg.com
Inverse chronological list of all Changes:
NEXTCHANGE
====== Changes thru 33.327 were in MXG 33.33 dated Jan 18, 2016=========
Change 33.327 Dataset VMBYUSR was missing many observations because the

VMACVMXA timestamp in MRHDRTOD in VXUSEACT did not exactly match

Jan 15, 2016 the MRHDRTOD in VXUSEINT which are key MERGE variables.

Circumvention was to merge with the FLOOR(MRHDRTOD).

Thanks to Joseph J. Faska, DTCC, USA.
Change 33.326 -MXG 32.10-MXG 33.33. Increase in CPU time for SMF 110

VMAC110 record processing, 300 to 500 seconds, 22 GB, due to

Jan 15, 2016 multiple executions of RESOLVE function where only one

was needed, to populate character variable CICXLTR, which

is only used to enhance error messages if EXCLUDED fields

are found.

-Too many warning messages were printed if Compressed CICS

data was read on z/OS without the CICSIFUE INFILE exit,

and too many "ok on ASCII" messages were printed.

Thanks to Perry Lim, Union Bank, USA.

Change 33.325 -Change 32.220 added new BASECICS and BASEDB2 parameters

BLDSMPDB that let you send DB2 and/or CICS datasets to a different

VMXGALOC drive, but did not tell you that if you did not use them,

UTILBLDP those datasets were written to BASEDIR. Default is now

Jan 17, 2016 a NULL string so that behavior is unchanged and the log

Jan 18, 2016 now notes where CICSTRAN and DB2ACCT are allocated.

-Change 32.262 incorrectly set the WEEK WEEK1 libnames to

be the current week when RUNWTD was NO and when RUNWTD

was YES the WTD LIBNAME was not allocated. Fortunately,

the only exposure is that if a user wanted to run a

report with WEEK1, it would have been empty since the

week had not been run to populate it.

-UTILBLDP failed to include ASUMDBSS because an AND in the

macro was misspelled as AMD and the compiler does not see

it as a syntax error.

-BLDSMPDB debugging statements left in code.

Thanks to Richard Krueger, Sentry, USA.
Change 33.324 zVPS variable CALENTMT was changed from numeric to char

VMACXAM causing a conflict if OLD and NEW datasets were combined.

Jan 13, 2016 CALENTMT is restored to CHAR, new variable CALENTMTN has

the actual numeric CPU ENTITLEMENT value.

Thanks to David A. Sadler, OPTUM, USA.
Change 33.323 New fields added to Thruput Manger are supported:

VMACTPMX CONTR ='CONTR'

Jan 12, 2016 JCL_SJB ='JCL_SJB'

JCL_SJC ='JCL_SJC'

JCL_SJG ='JCL_SJG'

JAL_T ='JAL_T'

There is a defective entry with ' ST_L' that should be

'LIST_L' that prints an error message that it was skipped

while we investigate with the vendor.
Change 33.322 The new JOB Correlation Token SMF30COR and SMF26JCR are

VMAC26J2 populated with 64 bytes of '00'x for OMVS and most STCs,

VMAC30 which then print as 64 unprintable characters. The '00'X

Jan 12, 2016 are translated to blanks. But it is unclear why this new

token is created; the READTIME JOB JESNR uniquely match

and only require 24 bytes, and are in many more SMF

records than just these two.
====== Changes thru 33.321 were in MXG 33.33 dated Jan 11, 2016=========
Change 33.321 -Change 33.297 failed if OPTIONS USER=PDB is used, because

VMAC7072 the PROC DATASETS (to change a label) coded a LIB=WORK

Jan 9, 2016 which failed when USER=PDB. The LIB=&MXGWORK argument

Aug 31, 2017 now finds the dataset (replacing a WORK.TEMP70EN fix.)

-BUT: IN GENERAL MXG DOES NOT SUPPORT OPTIONS USER=PDB,

"out of the box": both BUILDPDB and UTILBLDP can fail

or can NOT fail but produce missing values when USER=PDB

is used, and it typically requires additional tailoring

for a specific purpose, especially when accumulated data

requires DIF(), and may require a second execution of

%VMXGINIT. Contact [e-mail] if you have a need.

-Aug 2017: Note that using WORK=PDB in CONFIG has the same

exposure and thus that is also not supported.

Thanks to Scott Wiig, USBank, USA.

Change 33.320 Support for zVPS z13 SMT Mode adds these variables:

VMACXAM -Dataset XAMCPUTO:

Jan 7, 2016 CALENTMT='ENTITLEMENT'

CORID ='CORE*ID'

PFXPOLAR='POLARIZATION'

RCCTOPDI='DSVBK*INDEX'

TID ='THREAD*ID'

-Datasets XAMCPUBY, XAMIFLBY, XAMIFLTO, XAMCPUTO:

AVGTDBYCORE='AVG*TD*BY CORE'

AVGTDBYTYPE='AVG*TD*BY TYPE'

BUSYTIMEBYCORE='BUSY*TIME*BY CORE'

BUSYTIMEBYTYPE='BUSY*TIME*BY TYPE'

CAPBYTYPE='CAP*BY TYPE'

INTERVALTIMEBYCORE='INTERVAL*TIME*BY CORE'

INTERVALTIMEBYTYPE='INTERVAL*TIME*BY TYPE'

MAXCAPBYTYPE='MAX*CAP*BY TYPE'

MTUTILBYCORE='MT*UTIL*BY CORE'

MTUTILBYTYPE='MT*UTIL*BY TYPE'

PF2CADCT ='COUNT CAD*FOR*SPINLOCK*NODLAY'

PF2TSCAD ='COUNT CAD*DURING*TSGET*REQSTS'

PF2TSCNT ='COUNT*TSGET*REQUESTS'

PF2TSGTM ='ELAPSED*CONSUMED*BY TSGET'

PFXPRKWT ='PARKED*WAIT TIME*TOT UNIT'

PRODBYCORE='PROD*BY CORE'

PRODBYTYPE='PROD*BY TYPE'

SAMPLEDCORESBYTYPE='SAMPLED*CORES*BY TYPE'

SAMPLES='SAMPLES'
Change 33.319 The OPTION NONOTES statement added for the MXGLOG option

VMXGINIT must be reset to NOTES prior to the %MACRO statement. In

Jan 8, 2016 some cases the NONOTES remained incorrectly in effect,

Jan 22, 2016 which could suppress the INFILE SMF information and the

"dataset has nnn obs" notes on the SAS log. The Exposure

was limited to 33.07-33.13, and only with a tailored MXG

execution with a VIEW driven by a PROC SORT.

Jan 23: The OPTION NOTES was mis-located, suppressing the

printing of NOTE: Fileref=SOURCLIB and the DSNAMEs.

Thanks to Scott Wiig, US Bank, USA.

Change 33.318 Data Set SORT70EC NOT SORTED was corrected with an extra

VMAC7072 PROC SORT. It appears a change in the configuration was

Jan 5, 2016 made during the interval that caused the not sorted data.

Thanks to Paul Volpi, UHC, USA.

Change 33.317 Documentation of APARs corrections; NO CHANGES WERE MADE.

VMAC1415 -TYPE1415 APAR OA47899 corrects SMF 14/15 written at EOV

VMAC92 that did not contain the Type 1 Compressed Format data

VMAC74 set section.

VMAC80A -TYPE92 APAR OA49128 corrects invalid value in SMF92CTO.

VMAC116 -TYPE74 APAR OA48860 corrects SMF74DTS,SMF74DCT that are

Jan 3, 2016 not set correctly for a device after HYPERSWAP.

-TYPE80A APAR PI52900 for CICS/TS 5.2, adds CICS NETNAME

to SMF 80 record when DFHSN1102 SIGNON FAILS.

-TYPE116 APAR PI53551 MQ z/OS V8 Class 3 data may be

incorrect for CICS and CHIN Thread Control Blocks.

-Users of IBM CICS PA V5.1/5.2 NEED APAR PI43779 to

correct report files, especially LIST, that have file

blocking of ONE, wasting DISK space and CPU time.

Change 33.316 -The many new variables added in z/OS 2.2 in Change 33.189

VMAC42 are now kept.

VMAC64 -TYPE64 new variables

VMAC71 SMF64SSR='SECONDARY*SPACE*REDUCTION?'

VMAC74 SMF64FCC='BEGINNING*CCHH'

Dec 30, 2015 SMF64TCC='BENDING*CCHH'

SMF64VSN='VOLUME*SERIAL*NUMBER'

SMF64CUU='DEVICE*NUMBER'

SMF64IND='SPINDLE*IDENTIFICATION'

SMF64UTY='*UNIT*TYPE'

-TYPE71 new variables

SMF714KA='AVB*1MB FIXED*USED*4K REQ'

SMF714KM='MIN*1MB FIXED*USED*4K REQ'

SMF714KX='MAX*1MB FIXED*USED*4K REQ'

SMF71C2A='AVG*HIGH VIRTUAL*COMMON*1MB FIXED'

SMF71C2M='MIN*HIGH VIRTUAL*COMMON*1MB FIXED'

SMF71C2X='MAX*HIGH VIRTUAL*COMMON*1MB FIXED'

SMF71C3A='*AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'

SMF71C3M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'

SMF71C3X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'

SMF71CPA='AVB*HI VIRT*COMMON*INUSE'

SMF71CPM='*MIN*HI VIRT*COMMON*INUSE'

SMF71CPX='*MAX*HI VIRT*COMMON*INUSE'

SMF71PLA='AVB*1MB PGBL*BACKED*1MB PGBL'

SMF71PLM='MIN*1MB PGBL*BACKED*1MB PGBL'

SMF71PLX='MAX*1MB PGBL*BACKED*1MB PGBL'

SMF71S2A='AVG*OBJECTS*SHARED MEM*BACK 1MB'

SMF71S2M='MIN*OBJECTS*SHARED MEM*BACK 1MB'

SMF71S2X='MAX*OBJECTS*SHARED MEM*BACK 1MB'

SMF71S3A='AVG*FRAMES*SHARED HIGH*4K*ON SCM'

SMF71S3M='MIN*FRAMES*SHARED HIGH*4K*ON SCM'

SMF71S3X='MAX*FRAMES*SHARED HIGH*4K*ON SCM'

SMF71S4A='AVG*HIGH VIRTUAL*SHARED*1MB CSTORE'

SMF71S4M='MIN*HIGH VIRTUAL*SHARED*1MB CSTORE'

SMF71S4X='MAX*HIGH VIRTUAL*SHARED*1MB CSTORE'

-TYPE74 new variable

R748RAI ='RANK*ADAPTER*PAIR*ID'
Change 33.315 z/OS 2.2 JOB='*MASTER*' JCTJOBID='MSGR' SUBSYS='SMS' was

VGETJESN not expected, caused WARNING TYPETASK NOT DECODED, now

Dec 27, 2015 is protected, with TYPETASK='STC' now set.
Change 33.314 Unused Change Number.
Change 33.313 Documentation. Type 30 EXCP/IOTM NODD/TODD/TOTL variables

TYPE30 in the "raw" TYPE30_4/TYPE30_5/TYPE30_V datasets created

Dec 24, 2015 directly from SMF, are wrong or misleading for jobs with

MULTIDD='Y' continuation records (they contain only EXCP

and IOTM fields). The variables ARE VALID in the datasets

PDB.JOBS/PDB.STEPS/PDB.SMFINTRV, built by BUILDPDB or the

ONLYINTV program, where MXG logic combines the MULTIDDs

and then correctly populates those variables.

For MULTIDD='Y' jobs, the first record can be a FLUSH

that contains NO DD segments, so NUMDD=0 and the TODD

variables are missing values. The TOTL in the MULTIDD

records is missing, since that field is the total for

the step, and that is only in the first SMF 30 record.

And since NODD=TOTL-TODD, the NODD is also missing.

And since they can be individually wrong, the sum of

these variables in those "raw" TYPE30xx datasets is

unusable.
Change 33.313 Cosmetic. Comments enhanced.

BLDSMPDB

Dec 23, 2015
Change 33.312 If you had more than a single service policy in your data

ANALACTM the report of the WLM service definition was not sorted

Dec 23, 2015 by the policy name resulting in reports printed by the

importance level instead of the service policy.

====== Changes thru 33.311 were in MXG 33.13 dated Dec 23, 2015=========
Change 33.311 -UTILBLDP with IMACKEEP= fails execution with syntax error

UTILBLDP due to invalid comment termination in the generated code

Dec 23, 2015 that referenced &SPINUOW macro variable.

Thanks to Jim Horne, Lowe's, USA.

Change 33.310 MXG's ANALZPCR is no longer usable, nor needed, since IBM

ANALZPCR zPCR will now read a "printed" IBM RMF CPU report to

Dec 21, 2015 create the zPCR input in External File Format V2.0 that

is required for zPCR V8.7.

====== Changes thru 33.309 were in First MXG 33.13 dated Dec 21, 2015===
Change 33.309 Variable QCSTDNRT, previously reserved, is now input and

VMAC116 formatted as a time, with NS*RESOLUTION*TIME' in

Dec 21, 2015 dataset MQCHININ.

Thanks to Robert Miles Standish, UBS, USA.

Change 33.308 Support for z/OS 2.2 new variables SMF 99 ST 14 added

VMAC99 S99E_AN_CI ='CPU/CORE*CONTAINER*INFO*/

Dec 21, 2015 S99E_AN_CI_FLAGS='CI_FLAGS'

Dec 22, 2015 S99E_AN_CI_NL ='CPU/CORE*TOPOLOGY*INFO'

S99E_AN_CI_NL1 ='CONTAINER*ID OF*NESTING*LEVEL 1'

S99E_AN_CI_NL2 ='CONTAINER*ID OF*NESTING*LEVEL 2'

S99E_AN_CI_NL3 ='CONTAINER*ID OF*NESTING*LEVEL 3'

S99E_AN_CI_NL4 ='CONTAINER*ID OF*NESTING*LEVEL 4'

S99E_AN_CI_NL5 ='CONTAINER*ID OF*NESTING*LEVEL 5'

S99E_AN_CI_NLINUSE='HIGHEST*NESTING*LEVELUSED'

S99E_AN_INFO ='AFFINITY*NODE*INFO'

S99E_AN_TOPO ='CPU/CORE*TOPOLOGY*INFORMATION'

S99E_CP_BOOKID ='BOOK*ID'

S99E_CP_CHIPID ='CHIP*ID'

to dataset TYPE99EN, and these variables to TY99EP:

S99E_CP_BOOKID ='BOOK*ID'

S99E_CP_CHIPID ='CHIP*ID'

-Each subtype 14 dataset now has all of the header

variables kept.

Thanks to Erling Andersen, SMT, DENMARK.

Change 33.307 -SMFSRCH was supposed to support multiple text strings in

SMFSRCH LOOKFOR=, with ANDOR=, but it only supported one string;

VMXGSRCH multiple strings caused nothing to be found.

Dec 21, 2015 Now, multiple LOOKFOR= strings are supported, but only

Dec 29, 2015 with "OR" logic, i.e., any LOOKFOR= string will be found.

It's impractical to support multiple ANDed stings with

LOOKFOR=, but the SELECTION= alternative to LOOKFOR=

provides complete control including ANDs of strings.

-VMXGSRCH messages when a VALUE= was found now print the

VALUE= that was searched, or when a VARS= is used, then

all of the matching variables names are listed, instead

of a blank line.

Change 33.306 The Group Capacity Variables SMF70GNM (Group Name) and

VMXG70PR SMF70GMU (MAXIMUM LICENSE UNITS) are kept in the Per-LPAR

Dec 20, 2015 CEC-Level dataset PDB.ASUMCELP (built automatically in

Dec 22, 2015 BUILDPDB by the include of member ASUM70PR).

Jan 8, 2015 -SMF70WLA is added to ASUMCELP for the systems whose SMF

70's were read.

-Variable ZIPCPUS was ROUNDed to two decimal places, to

print pretty, as the calculated value often was x.99999,

and debugging _PRN70PR macro was added to VMXG70PR.
Change 33.305 -Support for z/OS 2.2 RMF 74 Subtype 10 SCM Storage Class

EXTY7410 Memory statistics creates new datasets:

EXTY74SC

IMAC74 dddddd dataset description

VMAC74 TY7410 TYPE7410 SCM EADM AGGREGATE STATS

VMAC78 TY74SC TYPE74SC SCM CONFIGURATION MEASUREMENT

Dec 18, 2015 -New z/OS 2.2 variables (COMPATIBLE) in TYPE78PA:

R782LSMOMIN ='MIN FRAMES*ARE USED*SHARED*MEMOBJ='

R782LSMONTME='TIME STAMP*OF MIN*SHARED*MEMOBJ='

R782LSMOMAX ='MAX FRAMES*ARE USED*SHARED*MEMOBJ='

R782LSMOXTME='TIME STAMP*OF MAX*SHAREDMEMOBJ='

R782LSMOAVG ='AVG FRAMES*ARE USED*SHARED*MEMOBJ='

Change 33.304 Dataset TYP120xx variable SM120RULEXSUM was a typo for

VMAC120 SM120RULEXFSUM and now, SM120RULEXSUM doesn't exist.

Dec 16, 2015

Thanks to Homayoun Riazi, OPTUM, USA.

Change 33.303 "Duplicate" obs were created in PDB.DB2STATS when DB2

VMACDB2 used more than 24 buffers in an interval, because DB2

Dec 16, 2015 creates (unexpected) multiple SMF 100 subtype 1 records

for that interval, but the QWHSSTCK time is not exactly

the same, and QWHSSTCK must be used because DB2 stats

records don't contain an interval start time value. There

were no actual duplicated data, but additional obs with

the same SMFTIME and only buffer metrics were created in

the PDB.DB2STATS statistics summary dataset.

Now, the data is ordered by QWHSISEQ and the QWHSSTCK of

the first instance is stored in both PDB.DB2STATB and in

the new PDB.DB2STSBP buffer datasets, and the corrected

QWHSSTCK is used to create PDB.DB2STATS.

Thanks to Rachel Holt, Fidelity Systems, USA.

Thanks to Lori Masulis, Fidelity Systems, USA.
Change 33.302 Support for two optional CICS user fields:

IMACICWR CMODHEAD CMODNAME Variable

IMACICWS OMEGCICS OMEGCICS OMEGCICS $EBCDIC104.

IMACAAAA USER STARPOL STARPOL $EBCDIC92.

UTILEXCL

VMAC110

Dec 15, 2015
Change 33.301 ITRM 33.12+ ERROR: WORK.SUMSTSPB.DATA does not exist.

ITRM -ITRM users of MXG 33.12+ MUST use EPDBOUT macro variable

Dec 11, 2015 to correctly sort the new DB2STSBP Simulated Buffer Pool

with this %LET statement inserted:

%CMPROCES . . .

%LET EPDBOUT= _SDB2SBP ;

%CPSTART . . .

-If you have not installed the ITRM Hot Fix 45583/41019,

you already have an EPDBOUT= _SDB2ST4 _SDB2225, so your

circumvention would be:

%LET EPDBOUT=_SDB2ST4 _SDB2225 _SDB2SBP ;

Thanks to Richard Schwarz, IBM, USA.

Change 33.300 New variables added to DB2ACCTx and DB2STATx datasets by

ASUMDB2A DB2 Version 11 are added to existing summary datasets.

ASUMDB2B The new dataset DB2STSBP summary is added in VMXGDBSS.

ASUMDB2G

ASUMDB2P

VMXGDBSS

Dec 11, 2015

Dec 14, 2015

Thanks to Wayne Bell, UNIGROUP, USA.
Change 33.299 Support for zVM 6.3 MONWRITE z13 SMT Mode; fields were

VMACVMXA inserted (INCOMPATIBLE) in SYTPRP after Change 33.242.

Dec 11, 2015 zVM 6.3.15.1 records have been validated. These

records have been validated. These variables are added

to VXSYTPRP dataset:

PF2CADCT ='UNDELAYED*CAD*INSTRUCTIONS'

PF2TSCAD ='CAD*INSTRUCTIONS*EXECUTED'

PF2TSCNT ='TSGET*REQUESTS'

PF2TSGTM ='TSGET*REQUEST*ELAPSED*TIME'

PFXPOLSR ='CORE*POLARIZATION'

SYTPRP_CAL_PLSIPTEI='IPTE 1/2*ACQUISITIONS'

SYTPRP_COREXTCT='COUNT*MT*COUNTERS*EXTRACTED'

SYTPRP_COREXTTT='DURATION OF*EXTRACT*MT*COUNTERS'

SYTPRP_PFXCPUCH='TIMES WHEN*SIEIHCPU FFFF*SWITCHES'

SYTPRP_PFXPRGCT='TIMES WHEN*SIEIHCPU FFFF'

SYTPRP_PLSIIA ='IPTE 2*ACQUISITIONS'

SYTPRP_PLSIIADD='TIMES WHEN*ACQUIRED*AS SHARE'

SYTPRP_PLSIIHDSSQCH='SSQ TIME*CONTINUOUS*HELD'

SYTPRP_PLSIIWTSSQCH='SSQ TIME*CONTINUOUS*HELD'

SYTPRP_PLSIIHLD='DURATION*CONTINUOUS*HELD'

SYTPRP_PLSIINHLD ='INTERVAL*COUNT*CONTINUOUS*HELD'

SYTPRP_PLSIIWTM='WAIT TIME*IPTE*INTERLOCK*ACQUISITION'

SYTPRP_PLSPTLCA='CALLS SET*PENDING*NON-LOCAL'

SYTPRP_PLSPTLCD='CALLS SET*PENDING*HOST TLB'

SYTPRP_PLSPTLCL='CALLS TO*PURGE*LOCAL*TLB'
Change 33.298 Support for IMS 14.1 log records (COMPATIBLE).

VMACIMS The IMS56FA dataset added two new variables

Dec 10, 2015 DLRDIR='DL/I*IR*CALLS'