COPYRIGHT (C) 1984-2008 MERRILL CONSULTANTS DALLAS TEXAS USA
CHANGE 26.07
MXG Version 26.07 is dated Aug 24, 2008, thru Change 26.197
MXG Version 26.06 was dated Aug 6, 2008, thru Change 26.176
Third MXG Version 26.06 was dated Aug 5, 2008, thru Change 26.175
Second MXG Version 26.06 was dated Aug 4, 2008, thru Change 26.173
First MXG Version 26.06 was dated Aug 1, 2008, thru Change 26.172
MXG Version 26.05 was dated Jun 18, 2008, thru Change 26.140
MXG Version 26.04 was dated Jun 4, 2008, thru Change 26.120
MXG Version 26.03 was dated May 11, 2008, thru Change 26.095
First MXG Version 26.03 was dated May 8, 2008, thru Change 26.093
MXG Version 26.02 was dated Apr 22, 2008, thru Change 26.075
MXG Version 26.01 was dated Mar 11, 2008, thru Change 26.037
First MXG 26.01 was dated Mar 10, 2008, thru Change 26.036
MXG Version 25.25 was dated Jan 28, 2008, thru Change 25.309
MXG Newsletter FIFTY-ONE was dated Dec 6, 2007
MXG Newsletter FIFTY was dated Sep 5, 2007
MXG 25.25 was the 2008 "Annual Version", dated January 28, 2008.
Instructions for ftp download are available (by return email), if
you will use this form:
http://www.mxg.com/ship_current_version
Contents of member CHANGES:
Member NEWSLTRS (and the Newsletters frame at http://www.mxg.com) now
contain the current MXG Technical Notes that used to be put in member
CHANGES between Newsletters. New Technical Notes are now added (and
now dated!) in NEWSLTRS/Newsletters with each new MXG Version.
I. Current MXG Software Version 26.07 is available upon request.
II. Incompatibilities and Installation of MXG 26.07.
III. Online Documentation of MXG Software.
IV. Changes Log
=======================================================================
I. MXG Version 26.07, dated Aug 24, 2008.
Major enhancements added in MXG 26.07, dated Aug 24, 2008
TYPE7072 26.071 Support for z/OS 1.10 (INCOMPAT, due to MXG code).
MXG code that protected an earlier IBM error in the number of
triplets caused z/OS 1.10 TYPE72GO to have zero observations,
so MXG 26.07 is REQUIRED to support z/OS 1.10 records. Sorry!
MXGSAS92 26.191 New JCL proc for SAS V9.2 with new z/OS DSNAMES.
VMXGINIT 26.189 SAS V9.2 Hot Fix F9BA07 eliminates new WARNINGs
MXG 26.03 or later provided circumvention for new WARNING messages
that set Condtion Code 4 with SAS V9.2, but SAS Hot Fix F9BA07
now eliminates the need for that MXG circumvention.
TYPE42 26.187 Support for APAR OA2025 adds SMF 42 subtypes, data.
TYPEINSY 26.182 Support for MACRO4 INSYNC SMF user record.
ASMIMSL6 26.190 Support for IMS Log record 0A (CPI-CI Drive PGM).
TYPEIMS7 26.190 Support for IMS Log record 0A (CPI-CI Drive PGM).
ASUMCEC 26.188 HiperDispatch subtracts SMF70PAT from SMF70ONT
ASUMDB2P 26.183 Revised summary/trending of DB2ACCTP example.
TYPERMFV 26.178 RMF III z/OS 1.9 changed length of ASI segment.
Major enhancements added in MXG 26.06, dated Aug 6, 2008
ASMTAPEE 26.148 MXGTMNT ML-43 captures IEF233D mount event, improved.
UNDUPSMF 26.152 Utility removes duplicate SMF records, output is VBS.
RMFINTRV 26.165 New RMFWKLRV: RMFINTRV Workload-only dataset created.
TYPEQACS 26.166 Support for AS/400 Version 6.1.0 (COMPATIBLE).
TYPETPF 26.163 Support for TPF PUT22 changes, and corrections.
TYPEOMCI 26.160 Support for Omegamon CICS User records in SMF 112.
TYPE99 26.155 Support for SMF 99 Subtype 11 Group Capacity Limits.
TYPE28 26.151 Support for APAR OA24416, 'D6'x NPM record.
TYPEMVCI 26.145 Support for BMC Mainview CICS CMRTYPE=109 (ABENDS).
TYPETNG 26.172 Support for NSM VMware Virtual Center 2.5 Servers.
TYPEDCOL 26.142 DCOLDSET identifies 'HFS' and 'PDSE' datasets.
TYPETMS5 26.161 New BESKEY variable identifies encrypted CA-1 tapes.
TYPERMFV 26.150 SPG variables too small due to typo.
TYPEBVIR 26.143 TS7700 Statistical dataset BVIR32 was trashed.
TYPE110 26.141 CICS STID=74 dataset CICIMQ ERROR message removed.
BUILDPD3 26.164 JES3 BUILDPD3 variable JOBCLASS could be blank.
WEEKxxxx 26.157 NOTSORTED condition due to inconsistent BY lists.
TYPE77 26.139 TYPE77 QUEUE1-QUEUE4 were wrong, over 100%.
TYPE70PR 26.154 SMF70LAC missing in PDB.TYPE70PR after offline LPAR.
Major enhancements added in MXG 26.05, dated Jun 18, 2008
TYPESVIE 26.133 Support for CA SYSVIEW, CICS, IMS, MVS in one member.
replaces partial support (2005) TYPESYSV, TYPESYSI.
ASMTAPEE 26.135 ML-42 of MXGTMNT, backs out JOB error in ML-41.
ASUMTAPE 26.122 SYSLOG JOB parse failed with 3 commas in TRANWRD.
TYPETMNT 26.128 Correction for DEFECT in ASMTAPEE ML-41, CRITICAL.
users of MXGTMNT need all three changes above.
ASUMMIPS 26.131 MIPS/MSU analysis adds IFAs/zAAPs and zIIPs MIPS.
TYPEPRPR 26.128 Prisma SMF record change in April was not documented.
TYPENTSM 26.125 Support for BITS NET UTIL, PACER PIPE, USB objects.
TYPENTSM 26.123 Support for new fields in MEMORY, PROCESS objects.
TYPEOMAU 26.121 Support for OMEGAMON Audit Records in CICS record.
TYPE120 26.126 WebSphere allocfails wrong, invalid triplets, st 3.
UTILEXCL 26.130 Documentation for IMACICEZ/E1/E2 tailoring enhanced.
VMACDB2 26.136 Corrections to IFCID 119 and IFCID 225 variables.
Major enhancements added in MXG 26.04, dated Jun 4, 2008
TYPE70 26.112 26.03: TYPE70 CPUMVSTM/PCTMVSBY/SHORTCPS missing.
TYPE74 26.117 TYPE747C was missing most observations, now enhanced.
TYPE42 26.103 INPUT EXCEEDED ID=42 SUBTYPE=15 if more than one S2.
TYPE23 26.116 Support for APAR OA22414 new variables.
TYPETMVS 26.111 Full support for TMVS Release 4.1, INCOMPATIBLE.
TYPEINFO 26.098 Support for Informatics STAT user SMF record.
TYPE80A 26.107 INPUT EXCEEDED due to new ASSIZMAX in TOKDANAM.
TYPE7xxx 26.115 Inconsistent BY list for RMF data are now consistent.
TYPETMNT 26.103 TYPETASK='J ' in TYPETMNT corrected in VGETJEXN.
TYPEVMXA 26.114 MONWRITE BAD CONTORL RECORD, with 6.24 record
MONTHxxx 26.115 Inconsistent BY list for RMF data are now consistent.
WEEKxxxx 26.115 Inconsistent BY list for RMF data are now consistent.
Major enhancements added in MXG 26.03, dated May 11, 2008
==Support for SAS Version 9.2: COMPATIBLE, no ERRORS, new WARNings==
See revised note for Hot Fix F9BA07 in MXG 26.07 Major Enhancements
All recent MXG Versions execute WITHOUT error with SAS Version V9.2.
V9.2 libraries are read/written by SAS V8.2 or V9.1.3, & vice versa.
SAS V9.2 Phase I Foundation Level on z/OS and ASCII SAS was tested.
These MXG Versions WILL print a new SAS V9.2 WARNING, that sets CC=4
(condition/return code), but that warning is harmless (to MXG code),
so all MXG output SAS datasets are correct, even with that warning.
MXG Version 26.03 eliminates this SAS V9.2 WARNING internally, but
also enables OPTION VARLENCHK=NOWARN to suppress the creation of
both the warning and the condition code. (Revised, Change 26.188).
So the ONLY exposure with prior MXG Versions under V9.2 is on z/OS,
and ONLY if condition code tests are used in your MXG jobstreams.
This new-in-SAS V9 "MULTIPLE LENGTHS OF A VARIABLE" warning message
surfaced in MXG delivered code primarily in these two cases:
a.The intended shortening of the LENGTH of a numeric variable, but
only when the LENGTH statement preceeds the SET/MERGE/UPDATE.
This occurs in VMXGSUM where the fixed-length-8 variables output
by PROC MEANS were reduced to 4-bytes, prior to option KEEPLEN.
The VMXGSUM utility is invoked in all MXG summarization, like
ASUMxxxx and TRNDxxxx, many ANALxxxx members, and in summarizing
RMFINTRV and CICINTRV programs included in BUILDPDB.
It is pervasive in MXG.
MXG Version 26.03 relocated its LENGTH statement to eliminate.
b.A JOIN of multiple datasets (SET MON.JOBS TUE.JOBS ...) where
a variable has different lengths in different datasets.
This also occurs in VMXGSUM, when multiple input datasets are to
be combined, like TRENDing, where TREND had shortened LENGTHs
but the "NEWTREND" internally has fixed, pre-KEEPLEN LENGTHs.
MXG 26.03 adds KEEPLEN option to PROC MEANS to eliminate.
MXG Version 26.03 eliminates this SAS V9.2 WARNING internally, but
also enables OPTION VARLENCHK=NOWARN to suppress the creation of
both the warning and the condition code. (Revised, Change 26.188).
Without VARLENCHK=NOWARN, EVEN at 26.03+V9.2 the WARNING can OCCUR:
a. If you have tailoring members in "USERID.SOURCLIB" from old MXG
versions, that need the same code revisions to eliminate.
b. In user-written SAS programs, this could actually be a valid
warning that a variable was truncated.
or, at any time in the furture, the WARNING can still occur:
c. When an MXG Version that changed variable LENGTHs is installed,
subsequent WEEKLY or MONTHLY jobs create the WARNING because
some PDB's have the old length and some have the new length,
when those multiple datasets are joined. Previous to V9.2,
length were changed with no WARNING nor CC. Between MXG 24.24
and 25.25 1206 variable's lengths were changed.
The Hot Fix is F9BA07.
Changes 26.191,26.189,26.090,26.078,26.065,26.060 have V9.2 details.
Note: Originally, MXG 26.02 claimed it supported V9.2, but changes
26.078 and 26.090 are required to eliminate the new WARNING
in MXG-delivered code, but there were no errors in 26.02/9.2.
VMXGSUM 26.090 Support for SAS V9.2 - See 26.078, 26.065, 26.060.
VMXGSUM 26.078 26.02 ONLY - VARIABLE NOT FOUND corrected.
ASUMTAPE 26.083 MAJOR rewrite of ASUMTAPE matches more, adds SPIN.
ASMTAPEE 26.095 ML-41 of MXGTMNT, TYPEARCV Allocation Recovery event
TYPEAFOP 26.086 Support for AF/Operator SMF record.
TYPECTMU 26.089 Support for Control-M log records on unix/open sys.
TYPECTMZ 26.089 Support for Control-M log records on z/OS.
TYPE112 26.088 Support for SMF 112 MQ segment (subsubtype 0200x).
ANALHSM 26.084 New MIGRATE/RECALL/BACKUP HSM report example added.
TYPE30 26.077 Negative CPUUNITS from zAAPs calculations eliminated.
Major enhancements added in MXG 26.02, dated Apr 22, 2008
Doc 26.060 Cosmetic SAS V9.2 differences with SAS V9.1.3.
TYPE7072 26.039 Support for APAR OA27074, corrected Parked Time.
ANALACTM 26.064 Implementation of Rich Olcott's The ACTuals Map.
TYPEACF2 26.051 Support for ACF2 Release 6.2.
TYPEMGCR 26.047 Support for Version 6 of MegaCryption SMF record.
IMAC6ESS 26.046 Support for GPARMKY=0050x ESSPRTA variable.
TYPEIMS7 26.045 Support for IMS Version 10 '08'x Log Record.
TYPECIMS 26.058 IMF dataset TYPECIMS variable INPUTCLS corrected.
Major enhancements added in MXG 26.01, dated Mar 11, 2008
TYPE7072 26.025 Support for APAR OA12774 new z10 RMF data (COMPAT).
MXG 25.25 supports the z10 hardware platform, but
did not know about this new APAR with TYPE70 data.
TYPE7072 26.031 Support/Correction Dedicated zAAPs/Dedicated zIIPs.
TYPE7072 26.006 Support for 64 CP Engines.
TYPE78CU 26.023 MXG 25.07-25.25. Last LCUID not output in TYPE78CU.
TYPE79 26.036 R723RCUT was .062 when it should have been 62.
TYPEIMSA 26.026 Support for new variables in IMS Version 9 and 10.
TYPEHSM 26.028 HSM FSR updated for z/OS 1.8 and 1.8 new variables.
TYPE102 26.011 Support for IFCID 22 APAR PK38803.
TYPEMPLX 26.014 IMPLX Version 4.1 is now supported.
VMXGINIT 26.012 SOURCLIB,SASAUTOS dsnames now printed at MXG INIT.
TYPE110 26.007 CICDS Dispatcher Statistics and PCTREGBY created.
ASUM70PR 26.003 LPARCPUS in ASUM70PR summary is not always integer.
TYPERMFV 26.032 Debugging PUT statement removed.
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes that used to be in CHANGES.
All of these enhancements are described in the Change Log, below.
I. SAS Version requirement information:
MXG 26.07 executes with SAS V8.2 or SAS V9.1.3 or SAS V9.2, on any
supported platform. It has not executed under SAS V6 in years.
The "PDB" libraries (i.e., SAS data libraries) must be created by
one of those listed SAS versions, but any of those data libraries
can be read or updated by any of those versions.
For SAS Version V9.2 (TS1M0):
Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software.
On z/OS, new DSNAMES for SAS libraries are in the new MXGSAS92
JCL procedure example.
All recent MXG Versions execute WITHOUT error with SAS Version
V9.2. V9.2 libraries are read/written by SAS V8.2 or V9.1.3, &
vice versa.
Without SAS Hot Fix F9BA07, MXG versions prior to 26.03 will
print a new SAS V9.2 WARNING, that sets CC=4 (condition/return
code), but that warning is harmless (to MXG code) so all MXG
output SAS datasets are correct, even with that warning. So the
ONLY exposure with prior MXG Versions is only on z/OS, only if
condition code tests are used in your MXG jobstreams.
For SAS V9.1.3 on z/OS with Service Pack 4:
There are no reported errors, and MXG's CONFIGV9 now specifies
V9SEQ instead of V6SEQ. As V6SEQ does not support long length
character variables, it should not 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) is required
to be completely safe. No earlier Version 8's were supported.
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.
MXG 26.07 QA tests were executed on z/OS with SAS V9.1.3 and V9.2
and also both V9.1.3 and V9.2 on Windows XP.
(I can no longer run QA tests with "archaic" SAS Version 8.2.)
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 SAS V9.1.3 or V9.2 on every possible SAS
platform without errors! Each new MXG version is also tested with
the SAS ITSV/ITRM product by the ITRM developers.
I.A. MXG Version Required for Hardware, Operating System Release, etc.
Availability dates for the IBM products and MXG version required for
the processing of that product's data records:
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.07
z/OS 1.9 With HiperDispatch Sep 15, 2008 26.07
z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07
z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04
z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07
z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24
z9EC CPUs - CPUTYPE '2094'x:
with 64-bit z/OS - no change required *24.24
with 32-bit z/OS only: Aug 26, 2006 24.06
z9BC CPUs - CPUTYPE '2096'x:
with 64-bit z/OS - no change required 24.01
with 32-bit z/OS only: Jul 27, 2006 *24.24
z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11
z10 HiperDispatch/Parked Time Mar 3, 2008 *26.02
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 for Z/OS Version 2.1 Mar 15, 2001 18.11
CICS-TS for Z/OS Version 2.2 Jan 25, 2002 19.19
CICSTRAN subtype 1 support only *19.19
CICSTRAN subtype 2 completed *19.08
CICS-TS for Z/OS Version 2.3 Dec 19, 2003
Using UTILEXCL to create IMACEXCL: 21.04
Reading un-Excluded CICS with TYPE110, no IMACEXCL:*22.04
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 for Z/OS Version 3.2 Jun 29, 2007 25.03
CICS-TS/3.2 Compressed Records Nov 3, 2007 25.11
DB2 2.3.0 Oct 28, 1991 10.01
DB2 3.1.0 Dec 17, 1993 13.02A
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 9.1 See Change 25.265. Dec 7, 2007 25.11
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
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
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 Jan 22, 2007 25.04
IMS log 4.1 Jul 4, 1994 12.02
IMS log 5.1 Jun 9, 1996 14.05
IMS log 6.1 ??? ?, 199? 20.03
IMS log 7.1 ??? ?, 200? 20.03
IMS log 8.1 May 21, 2003 21.02
IMS log 9.1 Dec ??, 2004 22.08
IMS log 10.0 Feb 27, 2007 25.01
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
Note: Asterisk before 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
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 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 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
The Monitor for CICS/TS V2.3 for CICS/TS 3.1 22.08
Candle
Omegamon for CICS V200 User SMF 12.05
Omegamon for CICS V300 User SMF 13.06
Omegamon for CICS V400 User SMF 16.02
Omegamon for CICS V400 type 110 segments 16.02
Omegamon for CICS V500 User SMF 18.01
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for IMS V300 (ITRF) 14.04
Omegamon for IMS V550/V560 (ITRF) 25.05
Omegamon for MVS V300 13.05
Omegamon for MVS V400 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for VTAM V400 15.15
Omegamon for VTAM V500 18.08
Omegamon for SMS V100/V110 12.03
CA
ACF2 6.2 16.04
ASTEX 2.1 14.04
NETSPY 4.7 14.03
NETSPY 5.0 14.03
NETSPY 5.2 16.05
NETSPY 5.3 18.03
NETSPY 6.0 20.10 20.305
NETSPY 7.0 20.10 20.305
SAR/VIEW R11 23.07 23.196
BMC, was Boole & Babbage
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) 22.08
Memorex/Telex
LMS 3.1 12.12A
Oracle V9, V10 24.06
Amdahl
APAF 4.1, 4.3 16.08
Velocity Software
XAMAP 3.4 22.10
XAMAP 3406 24.03
XAMAP 3.7 25.04
II. Incompatibilities and Installation of MXG 26.03.
1. Incompatibilities introduced in MXG 26.07:
a- Changes in MXG architecture made between 26.07 and prior versions
that can introduce known incompatibilities.
ASUMTAPE: You must delete SPIN.SPINMOUN before using the revised
ASUMTAPE program. See change 26.083.
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 JCLINST9 for
SAS Version 9.1.3 (JCLINST8 for now-archaic SAS Version 8.2).
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.
III. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
See also member INDEX, but it may be overwhelming.
IV. 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 26.01 after MXG 25.25:
Dataset/
Member Change Description
ANALACTM 26.064 Implementation of Rich Olcott's The ACTuals Map.
ANALHSM 26.084 New MIGRATE/RECALL/BACKUP HSM report example added.
ASMIMSL6 26.190 Support for IMS Log record 0A (CPI-CI Drive PGM).
ASMTAPEE 26.095 ML-41 of MXGTMNT, TYPEARCV Allocation Recovery event
ASMTAPEE 26.095 ML-41 of MXGTMNT, TYPEARCV Allocation Recovery event
ASMTAPEE 26.135 ML-42 of MXGTMNT, backs out JOB error in ML-41.
ASMTAPEE 26.148 MXGTMNT ML-43 captures IEF233D mount event, improved.
ASUM70PR 26.003 LPARCPUS in ASUM70PR summary is not always integer.
ASUM70PR 26.031 Support/Correction Dedicated zAAPs/Dedicated zIIPs.
ASUM70PR 26.041 Default INTERVAL in ASUM70PR restored to QTRHOUR.
ASUMCEC 26.188 HiperDispatch subtracts SMF70PAT from SMF70ONT
ASUMDB2P 26.183 Revised summary/trending of DB2ACCTP example.
ASUMMIPS 26.131 MIPS/MSU analysis adds IFAs/zAAPs and zIIPs MIPS.
ASUMTAPE 26.083 MAJOR rewrite of ASUMTAPE corrects errors, adds SPIN.
ASUMTAPE 26.122 SYSLOG JOB parse failed with 3 commas in TRANWRD.
BUILDPD3 26.164 JES3 BUILDPD3 variable JOBCLASS could be blank.
Doc 26.060 Cosmetic SAS V9.2 differences with SAS V9.1.3.
IMAC6ESS 26.046 Support for GPARMKY=0050x, new ESSPRTAT variable.
MONTHxxx 26.115 Inconsistent BY list for RMF data are now consistent.
Many 26.065 Support for no-WARNING execution under SAS V9.2.
RMFINTRV 26.165 New RMFWKLRV: RMFINTRV Workload-only dataset created.
TYPE102 26.011 Support for IFCID 22 APAR PK38803.
TYPE102 26.096 Variables QW0227FG/PG were always missing.
TYPE110 26.007 CICDS Dispatcher Statistics and PCTREGBY created.
TYPE110 26.052 Protection for SMF 110 St 2 STID 31 short segments.
TYPE110 26.141 CICS STID=74 dataset CICIMQ ERROR message removed.
TYPE112 26.088 Support for SMF 112 MQ segment (subsubtype 0200x).
TYPE119 26.067 ID=119 ST=21 INPUT STATEMENT EXCEEDED, NTHOSTTN short
TYPE120 26.126 WebSphere allocfails wrong, invalid triplets, st 3.
TYPE23 26.116 Support for APAR OA22414 new variables.
TYPE28 26.151 Support for APAR OA24416, 'D6'x NPM record.
TYPE30 26.077 Negative CPUUNITS from zAAPs calculations eliminated.
TYPE42 26.103 INPUT EXCEEDED ID=42 SUBTYPE=15 if more than one S2.
TYPE42 26.187 Support for APAR OA2025 adds SMF 42 subtypes, data.
TYPE70 26.112 26.03: TYPE70 CPUMVSTM/PCTMVSBY/SHORTCPS missing.
TYPE7072 26.025 Support for APAR OA12774 new z10 variables (COMPAT).
TYPE7072 26.031 Support/Correction Dedicated zAAPs/Dedicated zIIPs.
TYPE7072 26.039 Support for APAR OA27074, corrected Parked Time.
TYPE7072 26.0781 Support for z/OS 1.10 (INCOMPAT, due to MXG code).
TYPE70PR 26.154 SMF70LAC missing in PDB.TYPE70PR after offline LPAR.
TYPE71 26.069 TYPE71 HIUICMN,HIUICMX had wrong UIC values.
TYPE74 26.115 RMF BYLIST is SYSPLEX SYSTEM SYSNAME STARTIME.
TYPE74 26.117 TYPE747C was missing most observations, now enhanced.
TYPE77 26.139 TYPE77 QUEUE1-QUEUE4 were wrong, over 100%.
TYPE78CU 26.023 MXG 25.07-25.25. Last LCUID not output in TYPE78CU.
TYPE79 26.036 Variable R793CUT was 0.062, should have been 62.
TYPE80A 26.107 INPUT EXCEEDED due to new ASSIZMAX in TOKDANAM.
TYPE99 26.155 Support for SMF 99 Subtype 11 Group Capacity Limits.
TYPEACF2 26.051 Support for ACF2 Release 6.2.
TYPEAFOP 26.086 Support for AF/Operator SMF record.
TYPEBVIR 26.018 BVIR30 now contains both PG0 and Preference Grp 1.
TYPEBVIR 26.143 TS7700 Statistical dataset BVIR32 was trashed.
TYPECIMS 26.058 IMF dataset TYPECIMS variable INPUTCLS corrected.
TYPECTMU 26.089 Support for Control-M log records on unix/open sys.
TYPECTMZ 26.089 Support for Control-M log records on z/OS.
TYPEDCOL 26.142 DCOLDSET identifies 'HFS' and 'PDSE' datasets.
TYPEHSM 26.028 HSM FSR updated for z/OS 1.8 and 1.8 new variables.
TYPEIMS7 26.026 Support for new variables in IMS Version 9 and 10.
TYPEIMS7 26.045 Support for IMS Version 10 '08'x Log Record.
TYPEIMS7 26.190 Support for IMS Log record 0A (CPI-CI Drive PGM).
TYPEIMSA 26.026 Support for new variables in IMS Version 9 and 10.
TYPEINFO 26.098 Support for Informatics STAT user SMF record.
TYPEINSY 26.182 Support for MACRO4 INSYNC SMF user record.
TYPEITRF 26.034 ITRF x'10' INPUT STATEMENT EXCEEDED with LENGTH=251.
TYPEMGCR 26.047 Support for Version 6 of MegaCryption SMF record.
TYPEMPLX 26.014 IMPLX Version 4.1 is now supported.
TYPEMVCI 26.145 Support for BMC Mainview CICS CMRTYPE=109 (ABENDS).
TYPENMON 26.100 Invalid MEM header record protected.
TYPENTSM 26.123 Support for new fields in MEMORY, PROCESS objects.
TYPENTSM 26.125 Support for BITS NET UTIL, PACER PIPE, USB objects.
TYPEOMAU 26.121 Support for OMEGAMON Audit Records in CICS record.
TYPEOMCI 26.160 Support for Omegamon CICS User records in SMF 112.
TYPEPRPR 26.128 Prisma SMF record change in April was not documented.
TYPEQACS 26.166 Support for AS/400 Version 6.1.0 (COMPATIBLE).
TYPERACF 26.022 TYPERACF supports ASCII execution with EBCDIC ftp.
TYPERMFV 26.032 Debugging PUT statement removed.
TYPERMFV 26.053 Calculations of ASIxxxxx variables to match RMF.
TYPERMFV 26.150 SPG variables too small due to typo.
TYPERMFV 26.178 RMF III z/OS 1.9 changed length of ASI segment.
TYPESRDF 26.059 SPDMXUSE is character, SRDMXUPS is new numeric pct.
TYPESVIE 26.133 Support for CA SYSVIEW, CICS, IMS, MVS in one member.
TYPETMNT 26.103 TYPETASK='J ' in TYPETMNT corrected in VGETJEXN.
TYPETMNT 26.128 Correction for DEFECT in ASMTAPEE ML-41, CRITICAL.
TYPETMS5 26.161 New BESKEY variable identifies encrypted CA-1 tapes.
TYPETMVS 26.111 Full support for TMVS Release 4.1, INCOMPATIBLE.
TYPETNG 26.033 Support for more new VMware Objects in CA NSM.
TYPETNG 26.172 Support for VMware Virtual Center Servers in NSM.
TYPETPF 26.163 Support for TPF PUT22 changes, and corrections.
TYPEVMXA 26.114 MONWRITE BAD CONTORL RECORD, with 6.24 record
UNDUPSMF 26.152 Utility removes duplicate SMF records, output is VBS.
UTILEXCL 26.130 Documentation for IMACICEZ/E1/E2 tailoring enhanced.
VMACDB2 26.136 Corrections to IFCID 119 and IFCID 225 variables.
VMXGCAPT 26.001 Typo VMUM corrected to VWUM.
VMXGINIT 26.012 SOURCLIB,SASAUTOS dsnames now printed at MXG INIT.
VMXGINIT 26.189 SAS V9.2 Hot Fix F9BA07 eliminates new WARNINGs
MXGSAS92 26.191 New JCL Proc for SAS V9.2, new z/OS DSNAMES.
VMXGSUM 26.078 26.02 ONLY - possible VARIABLE NOT FOUND internally.
WEEKxxxx 26.115 Inconsistent BY list for RMF data are now consistent.
WEEKxxxx 26.157 NOTSORTED condition due to inconsistent BY lists.
See member CHANGESS for all changes ever made to MXG Software.
Inverse chronological list of all Changes:
NEXTCHANGE:
====== Changes thru 26.197 were in MXG 26.07 dated Aug 24, 2008=========
Change 26.197 PCTMVSBY in PDB.TYPE70PR is now calculated for all engine
VMAC7072 types (CPs,zIIPs,zAAPs), because SMF70PAT parked time is
Aug 24, 2008 now recorded for the specialty engines. The existence of
SMF70PAT field required heuristic circumvention code when
it was discovered that a fully parked engine did not have
the SMF70PAT exactly equal fo the SMF70ONT Online Time;
my first test for ONT-PAT GT .02 seconds was not enough
and caused PCTMVSBY greater than 100% when data with ONT
of ONT 15.00.01 and PAT of 14:59:97 was found, so that
heuristic was raised to 0.10 seconds. CPUWAITM greater
than DURATM by 0.01 seconds with SMF70PAT nearly DURATM
also required heuristic protection to prevent negative
PCTCPU calculations for individual engines in TYPE70PR.
Change 26.196 Variable DVRCP032 was removed from the KEEP list; there
VMACBVIR are only 31 pools.
Aug 24, 2008
Thanks to Jens Mohring, HUK-COBURG, GERMANY.
Change 26.195 The Multi-System Enclave Remote System dataset TYPE30MR
VMAC30 always had zero observations, because MXG's test for the
Aug 22, 2008 13 bytes remaining should have been 12, so the offset was
always missing and the segment was never read. This also
caused variables CPUMRDTM/CPUMRITM in TYPE30xx, PDB.JOBS,
PDB.STEPS, and PDB.SMFINTRV to always be zero. However,
fortunately, even IBM doesn't expect many (or any?) sites
to actually have these segments, so no one had noticed
their absence.
Thanks to Stephen Hughes, Excellus, USA.
Change 26.194 The MXGWPSV2 JCL procedure example was inconsistent in
MXGWPSV2 the example DSNAMEs, and the JCLINSTW example notes were
JCLINSTW clarified on the JCL Procedure Name to be used.
Aug 24, 2008
Change 26.193 Lots of cosmetic cleanup. Labels added, variables that
Many should not have been kept aren't, formats added, etc.,
Aug 21, 2008 as a result of SAS ITRM Dictionary Build, MXG QA runs,
and user detected inconsistencies. Members touched:
IMACCICS IMAC110 VMAC110 VMAC6156 VMACTPMX VMAC116
VMACSMF VMACHSM VMACCMF VMXGCICI VMAC30 VMXGRMFI
JCLROCS ASUMTAPE CHANGESS VMACSUSE VMXGINIT IMACQAPM
VMAC7072 VMACNTSM VMACTPF
Thanks to Nick Johns, Sainsbury Supermarkets Ltd., ENGLAND.
Thanks to Chris Weston, SAS ITRM Development, USA.
Thanks to Freddie Arie, Merrill Consultants QA Guy, USA.
Change 26.192 Support for APAR OA24074. IBM recalculates PCTMVSBY when
VMAC7072 HIPERDISPATCH has parked an engine(s), by subtracting the
Aug 21, 2008 Parked Time (SMF70PAT) from both the numerator and the
denominator:
Online Time - (Wait + Parked Time)
MVS UTIL(%)=---------------------------------- * 100
Online Time - Parked Time
so MXG's calculation of PCTMVSBY is revised to match IBM.
This was noted in the MXG Newsletter discussion of Parked
time, but was not implemented in code until now.
Thanks to Brian Currah, Independent Consultant, CANADA.
(In 1972, the first person I ever called with a question about an
SMF record's contents was Brian; the late Steve Cullen knew him
to be an SMF guru at GUIDE! And, he knew the answer, then and now!)
Change 26.191 A new MXGSAS92 JCL Procedure for MXG under z/OS SAS V9.2
MXGSAS92 is provided because SAS changed their DSNAMES for CNTL
Aug 22, 2008 and SASMSG datasets:
-If you use the SAS Deployment Wizard (SDW) to install the
SAS V9.2 for z/OS release, the DSNAME of their CNTL
dataset is changed by the addition of a new qualifier
with the SAS Version, year, and julian date of install,
with this syntax
DSN=&SASHLQ..V92DYJJJ.CNTL(BAT&YY.)
or a specific DSNAME, for example, of
DSN=&SASHLQ..V92D8208.CNTL(BATW0)
for an install in 2008 on julian date 208, in the USA.
The MXGSAS92 JCL procedure now has
//CONFIG DD DISP=SHR,DSN=&SASHLQ..V92DYJJJ.CNTL(BAT&YY.)
// DD DISP=SHR,DSN=&MXGHLQ..MXG.SOURCLIB(CONFIGV9)
Get that exact YJJJ value from your SAS Installer.
-Also the SASMSG DSNAME with .SL. no longer exists, so the
SASMSG DD only has these two DDs:
//SASMSG DD DISP=SHR,DSN=&SASHLQ..&XX.&YY..SASMSG
// DD DISP=SHR,DSN=&SASHLQ..EN&YY..SASMSG
Thanks to Tom C. Frohnapfel, AAFES, USA.
Thanks to MP Welch, SPRINT, USA.
Change 26.190 -Support for IMS Log record 0A (CPI-CI Driven Program)
ASMIMSL6 records 0A07x (Terminate) & 0A08x (Start) creates IMS0A78
EXIMS0A7 dataset in both ASMIMSL6/TYPEIMSA and TYPEIMS7 programs.
EXIMS0A8 -For ASMIMSL6/TYPEIMSA log processing:
EXIMSA78 _IMSVERS defined in IMACIMSA now default is IMS 10.0.
IMACIMS Comments in IMACIMSA document how to change DDNAMES and
IMACIMS7 which %LET Wdddddd= or %LET Pdddddd you use for
IMACIMSA each of the six output IMS datasets.
TYPEIMS7 ASMIMSL6 was modified to pass the 0A records and report
TYPEIMSA the total count of those records written.
VMACIMS -For TYPEIMS7 processing:
Aug 23, 2008 _IMSVERS defined in IMACIMS7 now default is IMS 10.0.
Member IMACIMS is NO LONGER USED.
In _IMSUMRY macro CTR array was increased from 55 to 67.
These DDname Macros were previously defined in IMACIMS7:
_IMSTRAN, _IMSBMP, and _IMSWORK
but they are no longer used in IMS processing, as the
simpler Pdddddd and Wdddddd macro variables are now
fully implemented in the MXG IMS processing. Theey are
still defined, in case they exist in your user code.
All TYPEIMS7 output datasets are written to //WORK, but
comments in TYPEIMS7 show how to send its output to
other DDNAMES.
Thanks to Cornelia Dorr, Lufthansa Systems Infratec GmbH, GERMANY.
Thanks to Gero Wohlsperger, Lufthansa Systems, Infratec GmbH, GERMANY
Change 26.189 SAS V9.2 with Hot Fix F9BA07 removed the need for MXG to
VMXGINIT enable the (non-existent, as of now) VARLENCHK option, so
Aug 20, 2008 it was removed. See MXG Newsletter FIFTY-TWO, SAS Note 7
which discusses the Hot Fix for SAS V9.2.
Thanks to MP Welch, SPRINT, USA.
Change 26.188 The datasets ASUM70PR/ASUM70LP/ASUMCEC/ASUMCELP built by
Documentation the ASUM70PR member currently do NOT subtract SMF70PAT,
Aug 19, 2008 Parked Time, from the SMF70ONT, Online Time, so the count
of LPnNRPRC (CP Engines) is not the average online count.
It might not be possible, easily, to modify ASUM70PR to
account for Parked Time in the two System-Level datasets
ASUM70PR and ASUM70LP, because the SMF70PAT only exists
in the per-MVS-system observations in TYPE70PR from the
parked MVS system records.
Howver, the two CEC-Level datasets, ASUMCEC and ASUMCELP
already use only the per-MVS-system observations, so it
appears that you could use the below example to create
two new PARKCEC and PARKCELP datasets in your PDB library
with the SMF70PAT parked time removed from SMF70ONT time,
which then causes the calculation of LPnNRPRC and related
related variables to account for the parked time of each
LPAR:
//REALPDB DD DSN=YOUR.REAL.PDB.DATASET,DISP=SHR
//PDB DD UNIT=SYSDA,SPACE=(CYL,(50,50))
//SYSIN DD *
DATA PDB.TYPE70PR; SET REALPDB.TYPE70PR;
IF SMF70PAT GT 0 THEN SMF70ONT=SMF70ONT-SMF70PAT;
%INCLUDE SOURCLIB(ASUM70PR);
DATA REALPDB.PARKCEC; SET PDB.ASUMCEC;
DATA REALPDB.PARKCELP; SET PDB.ASUMCELP;
Change 26.187 Support for APAR OA25025 for SMF 42 record, adds subtypes
EXTY4224 24 and 25, and to subtypes 20, 21, 24 and 25, the fields
EXTY4225 defined by IBM's ICHRUTKN DSECT are added to the record.
EXTY422A These new datasets are created:
EXTY424A DDDDDD DATASET DESCRIPTION
FORMATS TY422A TYPE422A SUBTYPE 21 DELETE ALIAS
IMAC42 TY4224 TYPE4224 DFSMS MEMBER ADD/REPLACE ST24
VMAC42 TY42A4 TYPE42A4 DFSMS SUBTYPE 24 DELETE ALIAS
VGETUTKN TY4225 TYPE4225 DFSMS MEMBER RENAME ST25
VMXGINIT These MXG variables are created by VGETUTKN:
Aug 19, 2008 UTKNFLG1='UTKNFLG1*MISCELLANEOUS FLAGS'
Bit values, not (yet?) decoded by MXG:
TOKENCR X'80' TOKEN IS ENCRYPTED
TOKLT19 X'20' TOKEN CREATED BY PRE RACF 1.9 CALL
TOKVXPRP X'10' VERIFYX PROPAGATION OCCURRED
TOKUNUSR X'08' NJE UNKNOWN USER
TOKLOGU X'04' LOG USER INDICATOR
TOKRSPEC X'02' RACF SPECIAL INDICATOR
UTKNFLG2='UTKNFLG2*MISCELLANEOUS*FLAGS'
Bit values, not (yet?) decoded by MXG:
TOKDFLT X'80' DEFAULT TOKEN
TOKUDUS X'40' UNDEFINED USER
TOKERR X'10' TOKEN IN ERROR
TOKTRST X'08' PART OF TRUSTED COMPUTER BASE
TOKSUS X'04' SURROGATE USERID
TOKREMOT X'02' REMOTE JOB INDICATOR
TOKPRIV X'01' PRIVILEDGED USER INDICATOR
UTKNFLG3='UTKNFLG3*MISCELLANEOUS*FLAGS'
TOKDGRP X'80' DEFAULT GROUP ASSIGNED
TOKDSEC X'40' DEFAULT SECLABEL ASSIGNED
TOKNETF X'20' NETWORK NAME SPECIFIED
TOKIPV X'10' IP VALUE FOR SERVAUTH POE
TOKWDWN X'08' WRITE-DOWN IS ALLOWED
UTKNGRUP='SESSION*OWNER*GROUPID'
UTKNLEN ='UTOKEN*RTOKEN*LENGTH'
UTKNNETW='REMOTE*NETWORK*NAME'
UTKNPOE ='PORT*OF*ENTRY'
UTKNPOEX='PORT OF ENTRY*CLASS*INDEX'
Decimal values not (yet?) decoded by MXG:
TOKTERM EQU 1 TERMINAL CLASS
TOKCON EQU 2 CONSOLE CLASS
TOKJESI EQU 3 JESINPUT CLASS
TOKAPORT EQU 4 APPCPORT CLASS
TOKSERV EQU 5 SERVAUTH CLASS
UTKNSCL ='SECLABL'
UTKNSGRP='SUBMITTING*GROUPID'
UTKNSNOD='SUBMITTER*NODE'
UTKNSTYP='SESSION*TYPE'
Decimal values decoded by MGUTKNT format:
1=' 1:SYSTEM ADDRESS SPACE'
2=' 2:COMMAND'
3=' 3:CONSOLE OPERATOR'
4=' 4:STARTED PROCEDURE'
5=' 5:MOUNT'
6=' 6:TSO LOGON'
7=' 7:INTERNAL READER BATCH JOB'
8=' 8:EXECUTION BATCH MONITOR'
9=' 9:RJE OPERATOR'
10='10:NJE OPERATOR'
11='11:VERIFYX UNKNOWN USER TOKEN'
12='12:EXTERNAL READER BATCH JOB'
13='13:RJE BATCH JOB'
14='14:NJE BATCH JOB'
15='15:NJE SYSOUT'
16='16:EXTERNAL XBM'
17='17:RJE XBM'
18='18:NJE XBM'
19='19:APPCTP'
20='20:OMVSSRV'
21='21:IPLOOKUP VALUE'
UTKNSUSR='SUBMITTING*USERID'
UTKNUSER='SESSION*OWNER*USERID'
UTKNVERS='UTOKEN*RTOKEN*VERSION*NUMBER'
UTKNXNOD='EXECUTION*NODE'
Change 26.186 WPS did not tolerate a FORMAT statement between an END
VMACVMXA and an ELSE IF statement. The FORMAT statement should
Aug 18, 2008 normally have been prior to that END statment in MXG, so
it was relocated to eliminate the WPS-only error.
Change 26.185 Mostly zero observations in TMDBDB2 dataset, because no
EXTMDDB2 one had use the TYPETMDB code to read the native Landmark
IMACTMDB for DB2 records with TYPETMDB code since 2004. Change
VMACTMDB 22.121 corrected MXG handling of DB2 Rollup records for
Aug 16, 2008 IBM DB2 SMF records, but that change had not been applied
to the Landmark DB2 records. This change removed the DO
group in EXTMDDB2 that deleted most observations, added
the logic that creates DB2PARTY='R' for rollups, and also
removed the _TMDBVER macro that is no longer required, as
only Version 4.0 currently exists.
Thanks to Charles Savikas, DCF, State of Florida, USA.
Change 26.184 Circumvention for defective SMF 101 subtype 0 record from
VMACDB2 Landmark reconstructed SMF records. Their error is in
Aug 13, 2008 the QPAC segment, which caused INPUT STATEMENT EXCEEDED
error because the offsets to the "truncated" name fields
are less than the QPACLEN value, and the offset should
not have been populated, since the name fields are not
"truncated". In addition, these fields prior to those
offsets are trashed, as the record contains character
text where these numbers are input (but since any text
is a valid PIB value, there was no error, only bad data
values in the DB2ACCP dataset):
QPACAWTK QPACAWTM QPACAWTN QPACAWTO QPACAWTQ
QPACARNK QPACARNM QPACARNN QPACARNO QPACARNQ
The MXG circumvention detects the record is created by
Landmark rather than IBM (by the location of the Product
segment, which Landmark puts at the beginning of the
SMF record, while IBM puts it at the end), and the
data starting at QPACAWTK is not input, so the variables
listed above will be missing, rather than wrong, until
a correction is available from Landmark.
Thanks to Howard Curtis, Progress Energy, USA.
Change 26.183 Summary and trending of DB2ACCTP Package Dataset revised.
ASUMDB2P The QBACxxxx and QTXAxxxx variables are always missing in
TRNDDB2P DB2ACCTP (ever since DB2 V7.1, which moved Package Data
Aug 12, 2008 to IFCID 239 (SMF 101 Subtype 0) records, so they have
been removed from both ASUMDB2P and TRNDDB2P summaries.
They can be removed from your DB2ACCTP dataset, but I
can not remove them without risk of causing a failure
if any of your reports reference theem in DB2ACCTP.
You can copy this macro definition into your IMACKEEP
member and they will no longer exist in your DB2ACCTP.
MACRO _KDB2ACP
QBACGET QBACSWS QBACRIO QBACSEQ QBACIMW QBACLPF
QBACDPF QBACNGT QBACSIO
QTXACHG QTXACHUS QTXACLMT QTXACLNO QTXACLUN QTXADEA
QTXADRNO QTXADRUN QTXAFLG1 QTXAILMT QTXAIRLM QTXALES
QTXALEX QTXALOCK QTXANPL QTXANRUN QTXAPREC QTXAQRY
QTXARLID QTXASLAT QTXASLMT QTXASLOC QTXASOTH QTXATIM
QTXAUNLK
%
Thanks to Chuck Hopf, Bank of America, USA.
Change 26.182 Support for MACRO4 INSYNC SMF user record creates new
EXINSYDB datasets:
EXINSYDI DATASET DDDDDD DESCRIPTION
EXINSYDS
EXINSYDU INSYDB2 INSYNC DB2
EXINSYZO INSYDBDI INSYNC DB2 - D OR I
EXINSYZC INSYDBDS INSYNC DB2 - SQL TEXT
EXINSYZF INSYDBDU INSYNC DB2 - U
FORMATS INSYZOS INSYNC ZOS
IMACINSY INSYZOSC INSYNC ZOS FORMAT
TYPEINSY INSYZOSF INSYNC ZOS SELECTION CRITERIA
TYPSINSY This is the first iteration and further investigation is
VMACINSY needed with the vendor, as there are invalid SMF records
VMXGINIT (the number of segments exceeds the physical record size)
Aug 13, 2008 and there are unexpected numerous duplicate records that
need to be investigated).
Thanks to Josep Miquel Oliver, La Caixa, SPAIN.
Change 26.181 Accidentally skipped change number
Thanks to Brent Turner, CitiGroup, USA.
Change 26.180 -The circumvention for invalid UWD record to avoid a USER
ASMRMFV ABEND, by skipping over it, is now permanent.
Aug 8, 2008 -Warning RMFV106W was incorrectly issued, and CPD table
entries could be not-processed, but only if GEI records
were selected. The SSH register pointer was not reloaded
but now are.
Thanks to Jerry Urbaniak, Acxiom, USA.
Change 26.179 The typo in VMAC7072 that had a nine-character variable
VMAC7072 ELSE IFAHONRPR=' ';
Aug 8, 2008 is corrected to
ELSE IFAHONPR=' ';
This does not cause an error with MXG's CONFIGV9, which
sets SAS option VALIDVARNAME=V7 to permit long names, but
if the SAS option VALIDVARNAME=V6 is used, error message
VARIABLE NAMED IFAHONRPR CONTAINS MORE THAN 8 CHARACTERS
is printed. The typo was introduced in MXG 26.03.
Thanks to Brian Cummings, Federal Reserve Information Technology USA
Change 26.178 z/OS 1.9 changed length of RMF III ASI segment, adding
VMACRMFV eight bytes, which caused ASICNM (Service Class Name)
Aug 8, 2008 and subsequent ASI varibles to be wrong. The added
eight bytes are now decoded and ketp in ZRBSI as
ASILMEMO='MEMORY*OBJECTS*ALLOCATED'
ASILPGSZ='LARGE PAGE*BYTES BACKED*IN REAL*STORE'
While ASILPGSZ is in pages in the raw record, MXG has
converted it to bytes and formatted it with MGBYTES to
display that size in KB/MB/etc.
Thanks to Jerry Urbaniak, Acxiom, USA.
Change 26.177 Cleanup of MXG as a result of ITRM Dictionary build:
ASUMTAPE -ASUMTAPE: Dataset HELDMOUN was not deleted from //WORK.
VMXGRMFI -RMFINTRV: New RMFWKLRV dataset had these variables
VMAC85 WKLDCPU WKLDHPT WKLDIFA WKLDIFE WKLDIIP WKLDRCT
VMAC99 WKLDSRB WKLDTCB WKLDZIE WKLDZIP.
Aug 7, 2008 that are now FORMATed TIME12.2;
-TYPE85RE: Variables R85BT R85MT R85RCDY R85TKN R85VT
were unlabeled.
R85BT ='BACKUP*TYPE'
R85MT ='VOLUME*MEDIA*TYPE*OF FROM'
R85RCDY ='DAYS*SPECIFIED*FOR OBJECT*RECALL'
R85TKN ='VOLUME*LOCATION*TOKEN OF*FROM'
R85VT ='VOLUME*TYPE'
-TYPE99: Variable S99BPDTM is FORMATted TIME12.3.
Thanks to Chris Weston, SAS ITRM Development, USA.
====== Changes thru 26.176 were in MXG 26.06 dated Aug 8, 2008=========
Change 26.176 First MXG 26.06 of Aug 6 worked fine on PCSAS but FORMATS
FORMATS failed on z/OS with one specific line in MGTNGVN that is
Aug 6, 2008 to be investigated with SAS Technical Support, but this
iteration split the line and the FORMATS member now does
successfully execute on z/OS and PC SAS.
Thanks to Jerry Urbaniak, Acxiom, USA.
Thanks to Christian Hodel, SWISScom, SWITZERLAND.
Change 26.175 Support for NMON BBBP configuration records creates new
EXNMONBP NMONBBBP dataset. The LSCONF and LPARSTAT-I entries are
IMACNMON stored in variables BBBP001-BBBP047, with their labels
VMACNMON as the identifier of the item.
VMXGINIT
Aug 22, 2008
Thanks to John Keenam, Boeing, USA.
Change 26.174 First MXG 26.06's only. TYPE99_1 DATASET NOT FOUND in
TESTIBM2 JCLTEST8/JCLTEST9 because the TYPE99 code now writes to
VMACNMON //PDB (because the data must be deaccumulated) but the
Aug 5, 2008 TESTIBM2 member had PROC PRINT/PROC MEANS that expected
Aug 6, 2008 those data to be in the //WORK file.
-NMONBBBP By list had ENDTIME, now has STARTIME.
Thanks to Mike Rounceville, Blue Cross Blue Shield of NC, USA.
====== Changes thru 26.173 were in MXG 26.06 dated Aug 4, 2008=========
Change 26.173 Support for Omegamon Tivoli Data Warehouse (TDW) data for
EXSUSELC z/Linux (SUSE 9.3) creates seven new datasets:
EXSUSELE DDDDDD DATASET Description Filename
EXSUSELI SUSELC SUSELCPU SUSE LINUX CPU SUSELCPU
EXSUSELN SUSELE SUSELNET SUSE LINUX NETWORK SUSELNET
EXSUSELP SUSELI SUSELIOE SUSE LINUX IO EXTERNAL SUSELIOE
EXSUSELS SUSELN SUSELNFS SUSE LINUX NFS STATISTICS SUSELNFS
EXSUSELV SUSELP SUSELPRO SUSE LINUX PROCESS SUSELPRO
IMACSUSE SUSELS SUSELSWA SUSE LINUX SWAP RATE SUSELSWA
TYPESUSE SUSELV SUSELVMS SUSE LINUX VM STATS SUSELVMS
TYPSSUSE Comments in member VMACSUSE show how to set up the
VMACSUSE FILENAME statements and then %INCLUDE SOURCLIB(TYPSSUSE);
VMXGINIT
Aug 4, 2008
Thanks to Jim Flanagan, ISO, USA.
====== Changes thru 26.172 were in MXG 26.06 dated Aug 1, 2008=========
Change 26.172 -Support for new NSM data fields NTCACHE, NTLOGICALDISK,
FORMATS NTMEMORY, NTPAGING FILE, NTPHYSICAL DISK, NTPROCESS and
VMACTNG NTSYSTEM datasets.
EXTNT133 -Support for new VMwares objects by Active Dictionary and
EXTNT134 VMware Virtual Center 2.5 Servers, VMware ESX 3.5.5 host
EXTNT135 servers and VM guest servers creates new datasets:
EXTNT136 TNT133 NT133 NSM CA INTERFACE GROUP
EXTNT137 TNT134 NT134 NSM VMWARE VC CLUSTER
EXTNT138 TNT135 NT135 NSM VMWARE VC DATASTORE
EXTNT139 TNT136 NT136 NSM VMWARE VC ESX HOST
EXTNT139 TNT137 NT137 NSM VMWARE VC ESX HOST C
EXTNT140 TNT138 NT138 NSM VMWARE VC ESX HOST D
EXTNT141 TNT139 NT139 NSM VMWARE VC ESX HOST M
EXTNT142 TNT140 NT140 NSM VMWARE VC ESX HOST N
EXTNT143 TNT141 NT141 NSM VMWARE VC EXX HOST P
EXTNT144 TNT142 NT142 NSM VMWARE VC RESOURCE P
EXTNT145 TNT143 NT143 NSM VMWARE VC SERVER
EXTNT146 TNT144 NT144 NSM VMWARE VC VM
EXTNT147 TNT145 NT145 NSM VMWARE VC VM CPU
EXTNT148 TNT146 NT146 NSM VMWARE VC VM DISK
Aug 2, 2008 TNT147 NT147 NSM VMWARE VC VM MEMORY
Aug 4, 2008 TNT148 NT148 NSM VMWARE VC VM NETWORK
Aug 6, 2008 TNT149 NT149 NSM AD EVENTS
Aug 24, 2008 TNT150 NT150 NSM AD PERFORMANCE
TNT151 NT151 NSM AD UTILIZATION
TNT152 NT152 NSM DNS
TNT153 NT153 NSM FILEREPLICACONN
TNT154 NT154 NSM FILEREPLICASET
TNT155 NT155 NSM NTDS
Added Aug 24 in 26.07:
TNT156 NT156 NSM VMWARE VC COMPUTE RE
Thanks to Michael Kynch, International Paper, USA.
Change 26.171 Protection so that ANALDB2R doesn't fail with USER=PDB.
ANALDB2R While USER=PDB is dis-recommended for BUILDPDB, and has
VMXGINIT caused errors with other programs, this change protects.
Aug 2, 2008
Thanks to Herbert Sweeney, Verizon Data Services Inc, USA.
Change 26.170 Circumvention for zero length VBS record in OPC Log file.
VMACOPC
Jul 31, 2008
Thanks to Andrew Davis, Produban, ENGLAND.
Change 26.169 Circumvention for 24 byte PRCAPM segment.
VMACXAM
Jul 29, 2008
Thanks to Tony Curry, BMC, USA.
Change 26.168 Support for DB2 SMF 102 IFCID=342 adds these variables:
VMAC102 QW0342TY ='DATABASE TYPE'
Jul 29, 2008 QW0342AT='AGENT TOKEN'
QW0342CI='CURRENT*INDEX*SPACE*USAGE'
QW0342CT='CURRENT*TABLES*SPACE*USAGE'
QW0342DB='DATABASE*DBID'
QW0342MI='MAXIMUM*INDEX*SPACE*USAGE'
QW0342MT='MAXIMUM*TABLES*SPACE*USAGE'
QW0342PS='TABLE/INDEX*SPACE*PSID'
QW0342PT='PARENT TOKEN'
Thanks to Steven Olmstead, Northwestern Mutual, USA.
Change 26.167 Debugging version for invalid UWD record segments will
ASMRMFVX avoid the USER ABEND and write defective records to the
Jul 29, 2008 //RMFSKIP DD (which needs to be added).
Thanks to Robert Carballo, Office Depot, USA.
Change 26.166 Support for AS/400 Version 6 Release 1 addes 3 variables
VMACQACS to the QAPMDISK dataset:
Jul 29, 2008 DSSECT ='DISK*UNIT*SECTOR*SIZE'
DSIOARN ='STORAGE*ADAPTER*RESOURCE*NAME'
DSSRLN ='DISK*UNIT*SERIAL*NUMBER'
and new variable to QAPMCONF dataset:
GDESXP ='PM*AGENT*DATA*OBTAINED?'
Thanks to David Bixler, FISERV, USA.
Change 26.165 A new "RMF Interval - WORKLOAD " dataset RMFWLKRV is now
EXRMFWKL also created when RMFINTRV is created; the new dataset
VMXGRMFI contains only the workload variables from RMF72, but
Jul 26, 2008 with one observation per workload, and only one set of
variables created, making workload analysis much easier.
The RMFWKLRV dataset has the same interval duration that
you chose for your RMFINTRV dataset; these are the
variables and labels in the new PDB.RMFWKLRV dataset:
DURATM DURATION*OF*INTERVAL
STARTIME START OF*INTERVAL
SYSNAME SYSNAME*FROM*IEASYSXX
SYSPLEX SYSPLEX*FORM*IEASYSXX
SYSTEM SYSTEM*ID
WKLDACTV WORKLOAD*ACTIVE*TIME
WKLDCPU WORKLOAD*CPU*TIME
WKLDDESC WORKLOAD*DESCRIPTION
WKLDEXCP WORKLOAD*EXCP*RATE
WKLDFRTM WORKLOAD*FRAME*TIME
WKLDHPT WORKLOAD*HPT*TIME
WKLDID WORKLOAD*ID
WKLDIFA WORKLOAD*IFA*PROCESSOR*TIME
WKLDIFE WORKLOAD*IFA*ELIGIBLE*PROCESSOR*TIME
WKLDIIP WORKLOAD*IIP*TIME
WKLDIOTM WORKLOAD*IO*CONNECT*TIME
WKLDMEMR WORKLOAD*MEMORY*USAGE
WKLDPGIN WORKLOAD*PAGEIN*RATE
WKLDRCT WORKLOAD*RCT*TIME
WKLDRESD WORKLOAD*RESIDENT*TIME
WKLDRESP WORKLOAD*AVG*RESPONSE
WKLDSERV WORKLOAD*SERVICE*UNITS
WKLDSRB WORKLOAD*SRB*TIME
WKLDSVRT WORKLOAD*SERVICE*RATE
WKLDSWAP WORKLOAD*SWAP*RATE
WKLDTCB WORKLOAD*TCB*TIME
WKLDTRAN WORKLOAD*TRANSACTIONS
WKLDTRRT WORKLOAD*TRANSACTION*RATE
WKLDWKST WORKLOAD*WORKING*SET
WKLDZIE WORKLOAD*ZIP*ELIGIBLE*PROCESSOR*TIME
WKLDZIP WORKLOAD*ZIP*PROCESSOR*TIME
Thanks to Don Goulden, SAS ITRM Development, USA.
Change 26.164 For the JES3 PDB, i.e., BUILDPD3, variable JOBCLASS was
BUIL3005 not kept from the SMF 30 subtype 1 and subtype 5, causing
Jul 26, 2008 it to be blank in some cases. It is now kept in both.
Aug 12, 2008 Additionally, it is now correctly kept as 8-bytes in the
PDB.SMFINTRV dataset, as well as being non-blank.
Thanks to Keving McCandlish, IBM Global Services, USA.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 26.163 Support for TPF PUT22 changes, and corrections to current
VMACTPF code.
Jul 21, 2008 New variables added by PUT22:
Dataset TPFDX:
DXNSDIN DXLMTRKS DXLMRSTT DXTSWB DXMODL DXCRYP
Dataset TPFSX:
SX4KFRMS
Corrections:
-The first SLOTNR was always re-read for all eight slots,
so dataset TPFMG never had data from the 2nd-8th slots.
-STARTIME was not populated for TPFMG dataset.
-The INPUT of SPXDISA1-4 and SPXRTRA1-4 were relocated to
the end of the SPX record; those variables were always
wrong until now.
Thanks to Bob Wilcos, EDS, USA.
Change 26.162 Reserved Change Number.
Jul 21, 2008
Change 26.161 New variable BESKEY='TAPE*ENCRYPTION*KEY*INDEX' is added
TYPETMS5 to ddataset TMS to identify CA-1 encrypted tapes. This is
VMACTMS5 a reference/index into the CA Tape Encryption Data base
Jul 21, 2008 where the actual keys are stored, and it allows TMS to
determine when a key is no longer needed and can be
retired; TMS scans for non-scratch tapes that reference
a key, and if none are found for a specific index, that
key can then be safely retired.
Thanks to Jeff Harder, Indiana Farm Bureau, USA.
Change 26.160 Support for Omegamon User SMF records in SMF 112. The
VMAC112 old records processed by TYPEOMCI are now written as SMF
VMACOMCI ID=112 subtypes 200 (INTR) or 201 (SYSR), while the new
Jul 20, 2008 TYPE112 records are written as subtype 203. Subtypes 200
and 201 were also internally changed (INCOMPIBLY), so
VMACOMCI was updated to read the current records, and
VMACOMCI only reads subtypes 200 and 201, and it will
automatically read ID=112, so there no longer is a need
for you to set a value of 112 in MACRO _IDOMCI. However,
if it is set to 112, or if you are still writing those
records with a different SMF ID, _DOMCI still works. The
VMAC112 change was minor - to only read the 203 subtype,
but that was necessary so both types of 112 code can be
processed by %UTILBLDP or BUILDPDB, to create all of the
datasets from all three subtypes.
I could have moved the OMCI code into VMAC112, but that
would have taken much more time than this restructure, &
the end result is that all three subtypes are supported.
Thanks to Art Cuneo, Blue Cross Blue Shield of Illinois, USA.
Change 26.159 TYPE77 QUEUE1 thru QUEUE4 were wrong and could be GT 100.
VMAC77 The correct denominator TOT77QUE=SUM OF (QUEUE1-QUEUE4)
Aug 13, 2008 is now used to calculate those percentages, and is kept.
The calculation of Average Queue Length now matches IBMs
reports, using AVG77QUE=WAITS/TOT77QUE, where WAITS is
SMF77AQL, the total waiting requests, and new TOT77QUE
is the total number of waiters.
New variable RNAMEHEX is the printable hex value of the
first MINORQCB bytes of RNAME, so those RNAMEs that have
hex values can be seen when printed as plain text.
Thanks to Chuck Hopf, Bank of America, USA.
Change 26.158 Cosmetic, but confusing. PDB.TYPE70 offline zip/zap
VMAC7072 engines had CAIxx='20'x instead of '00'X, had PCTIFBYx
Jul 17, 2008 and PCTZIPBx both 100%, had IFAWAITx and ZIPWAITx both 0,
and IFAWAITM and ZIPWAITM were also both zeros if all of
the zIIP and zAAP engines were offline during interval.
The IFAUPTM and ZIPUPTM were both correct (missing) when
all of these engines were offline. the NRIFAS and
NRZIPCPU variables still count the number of engines
available to this MVS system, even when all are offline.
Thanks to Christine DeClercq, Dexia, BELGIUM.
Change 26.157 Change 26.115 made consistent the BY lists for RMF sorts,
MONTHASC but only for the first three common variables. The
MONTHBL3 TYPE70 sort order was still inconsistent between BUILDPDB
MONTHBLD and WEEKBLD/MONTHBLD. Now, those combining jobs all have
MONTHBLS been updated to match the BUILDPDB order, which is:
MONTHDSK SYSPLEX SYSTEM SYSNAME SMF70GIE GMTOFFTM STARTIME
MONTHWEK
WEEKBL3D
WEEKBL3T
WEEKBLD
WEEKBLDD
WEEKBLDT
Jul 15, 2008
Thanks to Tom Kelman, Commerce Bank of Kansas City, USA.
Change 26.156 Hex variable FSRDORG is decoded in new character variable
VMACHSM FSRDSORG using the same logic used for DCOLLECT, except
Jul 15, 2008 that DCOLLECT provides bits to identify PDSE vs PDS.
Thanks to James J. Byrnes, ???, ???
Change 26.155 Support for SMF 99 Subtype 11 (Group Capacity Limits)
EXTY99BG creates two new datasets:
EXTY99BS DDDDDD DATASET SUBTYPE DESCRIPTION
IMAC99 TY99BG TYPE99BG 99-11 CAPACITY GROUP
VMAC99 TY99BS TYPE99BS 99-11 SERVICE DATA
VMXGINIT
Jul 23, 2008
Thanks to Scott Chapman, American Electric Power,USA.
Change 26.154 If an offline LPARNUM preceeded this PARTISHN, SMF70LAC
VMAC7072 was missing in PDB.TYPE70PR and PDB.ASUM70LP/PDB.ASUMCELP
Jul 10, 2008 and the corresponding LPnLAC in PDB.ASUM70PR/PDB.ASUMCEC.
Thanks to Barry T. Mueller, RiteAid, USA.
Change 26.153 -Using ANALRMFR from MXG 26.01+ with PDB=PDB where that
ANALRMFR input PDB was created with an earlier MXG version caused
Jul 18, 2008 a series of error messages that variables suffixed Y, Z,
ZA ... are missing; those new variables for CPs up to 64
were expected by ANALRMFR; rerun with PDB=SMF to correct.
-ERROR: NO DATA SET OPEN TO LOOK UP VARIABLES corrected;
caused by hardcoded TYPE70SP instead of _WTY70SP.
-Updated to support 64 CP engines.
Thanks to Bill Cheng, Toyota, USA.
Change 26.152 New utility to remove duplicate SMF records from VBS data
UNDUPSMF file.
Jul 9, 2008
Thanks to Lawrence Stahl, IBM Global Services, USA.
Change 26.151 Support for APAR OA24416, which corrects overflow in
VMAC28 GBLCRPSA by adding a four byte "high part" at the end of
Jul 8, 2008 the 'D6'x NPM record.
Change 26.150 A typo caused the values of three SPG variables to be
VMACRMFV one tenth of their true value; the three variables
Jul 6, 2008 SPGTOTSP SPGFRESP SPGLGBLK are now multiplied by the
correct value of 1048576 instead of 104856.
Thanks to Roger Rush, Navistar, USA.
Change 26.149 Protection so that if SMF 21s and TYPETMNT were not added
UTILBLDP ASUMTAPE, ASUMTMNT and ASUMTALO are NOT included, but if
Jul 6, 2008 TYPETMNT is created, the ASUMTMNT and ASUMTALO are.
Thanks to Charles Savikas, State of Florida, USA.
Change 26.148 Enhancement to ASMTAPEE/MXGTMNT's capture of SYSLOG info,
ASMTAPEE now at ML-43 with this change, some revisions to ASUMTAPE
ASUMTAPE processing logic that improves the accuracy of several
VMACTMNT SYSLOG timestamps, and the creation of new SYLVTIME,
Jul 6, 2008 which is then used to improve the accuracy of variables
BEGTMNT, ENDTMNT, TOTMNTTM and TAPMTDTM values, some
variable labels were revised, and a new MXG Technical
Note to document what can still be missed by MXGTMNT.
-ML-43 of ASMTAPEE/MXGTMNT now captures the IEF233D mount
message in its subtype 8 records (output in TYPESYMT).
The IEF233D message is issued for non-ATL, non-VTS first
volume mounts from dynamic allocations that don't specify
the DEFER option. This message should have been in the
initial list (IEF233A, IEC501A, IEC501E) of mount events,
but was never observed until now, perhaps because it is
relatively infrequent.
-ASUMTAPE's logic revises how SYLMTIME, the SYSLOG Mount
time is populated; previously, if there was no SYSLOG
mount event, the time of a SYSLOG verify message was used
to populate SYLMTIME, but now, only mount event messages,
IEF233A, IEF233D, IEC501A, or IEC501E, are used.
-New logic in ASUMTAPE instead creates variable SYLVTIME,
SYSLOG Verify time, using the maximum time value of he
IECTMS6, IECTMS9, or IEC7095I SYSLOG messages.
-And SYLVTIME is now used in the creation of the ENDTMNT
mount event time variable in ASUMTAPE.
-The logic for BEGTMNT, ENDTMNT, TOTMNTTM and TAPMNDTM are
corrected, revised, and re-labeled:
BEGTMNT='BEGIN TIME*OF TAPE*MOUNT EVENT'
IF SYLMTIME GT 0 and TMNTTIME GT 0 THEN
BEGTMNT=MIN(TMNTTIME,SYLMTIME);
ELSE iF SYLMTIME GT 0 THEN BEGTMNT=SYLMTIME;
ELSE IF TMNTTIME GT 0 THEN BEGTMNT=TMNTTIME;
ELSE BEGTMNT=.;
It is the minimum timestamp of the start of
the mount event, from SYSLOG or MXGTMNT.
ENDTMNT='END TIME*OF TAPE*MOUNT EVENT'
IF SYLVTIME GT 0 AND TENDTIME GT 0 THEN
ENDTMNT=MAX(TENDTIME,SYLVTIME);
ELSE IF SYLVTIME GT 0 THEN ENDTMNT=SYLVTIME;
ELSE IF TENDTIME GT 0 THEN ENDTMNT=TENDTIME;
ELSE ENDTMNT=.;
It is the maximum verification time or mount
end, from SYSLOG or MXGTMNT.
TOTMNTTM='TIME IT TOOK*TO MOUNT*TAPE VOLUME'
IF ENDTMNT GT 0 AND BEGTMNT GT 0 THEN
TOTMNTTM=ENDTMNT-BEGTMNT;
It is the duration the job was delayed for
this tape mount.
TAPMTDTM='DURATION*TAPE WAS*MOUNTED*TO DISMOUNT'
IF (SYLKTIME GT 0 OR TY21TIME GT 0) AND
BEGTMNT GT 0 THEN
TAPMTDTM=MAX(SYLKTIME,TY21TIME)-BEGTMNT;
It is the duration that the tape volume was
mounted on the device for this mount event.
-VMACTMNT: New variables, decoded bits from TMNTFLAG,
were added to make debugging a little easier:
TMNTMSGI='MOUNT MESSAGE ISSUED'
TMNTJOBI='JOB*ENDED*EVENT'
TMNTJOBC='JOB*CANCELLED*BY*OPERATOR'
Thanks to Yves Cinq-Mars, IBM Global Services, CANADA.
Change 26.147 Cosmetic. The LPnNRPRC variables that count the number
VMXG70PR of CP engines in the ASUM70PR and ASUMCEC datasets are
Jul 2, 2008 now FORMATted 6.1 to match the LPARCPUS format that was
made in Change 26.003.
Thanks to Stan Dylnicki, Royal Bank of Canada, CANADA
Change 26.146 Support for VXVNDSES dataset for zVM Domain 8 record 1.
FORMATS
VMACVMXA
Jul 2, 2008
Thanks to Sharon Moir, JPMorgan Chase Bank, USA.
Change 26.145 Support for BMC Mainview for CICS CMR record CMRTYPE=109.
VMACMVCI The CMRTYPE=109 records are written for ABENDs; only the
Jul 2, 2008 CMRTYPE=110 records were previously processed by MXG.
Variable CMRTYPE was added to both datasets as well.
Thanks to David Edge, Thompson Reuters, USA.
Change 26.144 The example ftp ihstructions for sending data files were
FTPSMF all corrected; the syntax /yourname.xxx are all now
FTPVB changed to the syntax of just yourname.xxx; that leading
JCLFTP slash tried to write to the root directory, which was not
NEWSLTRS the desired target destination.
SENDDATA
Jul 1, 2008
Thanks to Trevor Ede, EDS, NEW ZEALAND.
Change 26.143 The Virtualization Engine TS7700 Statistical data in the
VMACBVIR MXG BVIR32 dataset was trashed; these 4 one-byte fields
Jun 30, 2008 were not INPUT, causing subsequent variables to be out
of alignment:
DVAVAD00='00*AVAILABLE*PHYSICAL*DEVICES'
DVAVAD01='01*AVAILABLE*PHYSICAL*DEVICES'
DVAVAD02='02*AVAILABLE*PHYSICAL*DEVICES'
DVAVAD03='03*AVAILABLE*PHYSICAL*DEVICES'
Thanks to Josep Miquel Oliver, La Caixa, SPAIN.
Change 26.142 New variables added to DCOLLECT dataset DCOLDSET:
VMACDCOL DCDCKDSI='CHECKPOINT*DS*INDICATED?'
Jun 30, 2008 DCDCPOIT='CHECKPOINTED*DATASET?'
DCDGT64K='GT 64K*TRACK*DATASET?'
and new values created for DCDDSORG for HFS and PDSE;
unfortunately, DCEDSORT is only three bytes, so the text
value for PDSE is set to PDS"
DCDDSORG='HFS' for HFS dataset
DCDDSORG='PDS' for PDSE dataset
These two values are set based on IBM support's reply, as
only the bits are documented in the IDCDOUT DSECT, but not
the logic:
IF DCDPDSE='Y' AND DCDPDSEX=' ' THEN DCDDSORG='PDS'; /*PDSE*/
IF DCDPDSE='Y' AND DCDPDSEX='Y' THEN DCDDSORG='HFS'; /*HFS*/
However, there are several hundred DCOLDSET observations
that have DCDDSORG blank, because the three flag bytes
whose bits are used to define DCDDSORG, MXG variables
DCDSORG1, DCDSORG2 and DCDFLAG3, all contain hex zeroes;
a new query back to DCOLLECT technical support is raised.
These blank values are believed to be from datasets
that were allocated but never opened.
Thanks to Trevor Ede, EDS, NEW ZEALAND.
Change 26.141 CICS STID=74 (SMF 110 Subtype 2 Statistics) length of 228
VMAC110 was incorrectly documented in DFHMQGDS, causing MXG to
Jun 30, 2008 print ERROR (NEW DATA) SKIPPED message on the log. But,
MXG's INPUT was off by 4 bytes (Queue Manager is only 4),
The INPUT is corrected, the extra reserved bytes are now
skipped, that ERROR message is now a WARNING message, and
dataset CICIMQ (CICS MQ STATISTICS) is now corrected.
Thanks to Ray Dunn, CIGNA, USA.
Thanks to Murray Town, Suncorp, AUSTRALIA.
Thanks to MP Welch, SPRINT, USA.
Thanks to David J Schumann, Blue Cross of Minnesota, USA.
====== Changes thru 26.140 were in MXG 26.05 dated Jun 18, 2008=========
Change 26.140 Example analysis of DB2 Package resources from DB2ACCTP.
ANALPKGS
Jun 17, 2008
Thanks to Myles M. Reed, NS Corp, USA.
Change 26.139 MXG's DOCVER and DOCVERnn members are limited to 72 bytes
UTILXRF1 per line, which permitted only 8-byte variable names; MXG
UTILVREF now creates some datasets with variable names longer than
Jun 17, 2008 8-bytes, so the DOCVER and DOCVERnn members are revised;
if the length of the variable is more than 8 bytes, the
variable name is printed on a separate line. SAS itself
limits variable names to 32 characters.
Change 26.138 EKC's EFT/R FIRECALL SMF 80 record was changed, causing
VMAC80A INPUT STATEMENT EXCEEDED RECORD length, because MXG
Jun 17, 2008 didn't expect the changed record.
Thanks to Yaohua Hu, ISO, USA.
Change 26.137 For QA testing; setting TAPENGN to V9SEQ/V8SEQ is now
VMXGINIT only done for MXG under z/OS; MONTHBLD died in QA tests
Jun 17, 2008. because V9SEQ does not exist in ASCII versions of SAS.
Change 26.136 -Variable QW0119GP, CURRENT GET PAGES, added to T102S199.
VMACDB2 -Variable QW0225BB was mis-located in the MXG Input, and
VMAC102 should not have been converted to bytes, it is blocks.
Jun 17, 2008 Both VMACDB2 and VMAC102 process the IFCID=225 segment.
Thanks to Steve Wood, DST Systems Inc., USA.
Change 26.135 ASMTAPEE ML-42 backs out the incorrect JOBname that was
ASMTAPEE added in ML-41. Change 26.128 revised MXG TYPETMNT code
Jun 16, 2008 to use JOB from the SYSLOG message text, while we still
try to find the location of that second JOB name.
Change 26.134 Cosmetic change; test for length remaining for optional
IMACICRD DFHRMI segment for CICS/TS 3.2 added for length 96.
Jun 16, 2008
Thanks to Paul C. Gordon, Bank of America, USA.
Change 26.133 Complete rewrite of MXG support for CA SYSVIEW, replacing
EXSVEV01 the partial support (2005) in TYPESYSV and TYPESYSI.
EXSVEV02 The new support now creates seventy-four datasets:
EXSVEV03
EXSVEV04 DDDDDD Dataset Description
EXSVEV05 token Name
EXSVEV06
EXSVEV07 SVEV01 SV01EV01 SVEV01: SYSVIEW AUDIT 01 NOOP
EXSVEV08 SVEV02 SV01EV02 SVEV02: SYSVIEW AUDIT 02 START
EXSVEV09 SVEV03 SV01EV03 SVEV03: SYSVIEW AUDIT 03 SHUTDOWN
EXSVEV10 SVEV04 SV01EV04 SVEV04: SYSVIEW AUDIT 04 SESSION
EXSVEV11 SVEV05 SV01EV05 SVEV05: SYSVIEW AUDIT 05 SESSION
EXSVEV12 SVEV06 SV01EV06 SVEV06: SYSVIEW AUDIT 06 COMMAND
EXSVEV13 SVEV07 SV01EV07 SVEV07: SYSVIEW AUDIT 07 COMMAND
EXSVEV14 SVEV08 SV01EV08 SVEV08: SYSVIEW AUDIT 08 THRESHOL
EXSVEV15 SVEV09 SV01EV09 SVEV09: SYSVIEW AUDIT 09 STATE MO
EXSVEV16 SVEV10 SV01EV10 SVEV10: SYSVIEW AUDIT 10 MONITOR
EXSVEV17 SVEV11 SV01EV11 SVEV11: SYSVIEW AUDIT 11 ASID ACT
EXSVEV18 SVEV12 SV01EV12 SVEV12: SYSVIEW AUDIT 12 CONSOLE
EXSVEV19 SVEV13 SV01EV13 SVEV13: SYSVIEW AUDIT 13 WEB MQ C
EXSVEV20 SVEV14 SV01EV14 SVEV14: SYSVIEW AUDIT 14 IMS COMM
EXSVEV21 SVEV15 SV01EV15 SVEV15: SYSVIEW AUDIT 15 CICS CEM
EXSVEV22 SVEV16 SV01EV16 SVEV16: SYSVIEW AUDIT 16 DSN SERV
EXSVEV23 SVEV17 SV01EV17 SVEV17: SYSVIEW AUDIT 17 LPA MODI
EXSVEV24 SVEV18 SV01EV18 SVEV18: SYSVIEW AUDIT 18 SVCTABLE
EXSVEV25 SVEV19 SV01EV19 SVEV19: SYSVIEW AUDIT 19 SUBSYS M
EXSVEV26 SVEV20 SV01EV20 SVEV20: SYSVIEW AUDIT 20 PPT MODI
EXSVEV27 SVEV21 SV01EV21 SVEV21: SYSVIEW AUDIT 21 WTOR REP
EXSVEV28 SVEV22 SV01EV22 SVEV22: SYSVIEW AUDIT 22 LOGSTREA
EXSVEV29 SVEV23 SV01EV23 SVEV23: SYSVIEW AUDIT 23 LOGSTREA
EXSVEV30 SVEV24 SV01EV24 SVEV24: SYSVIEW AUDIT 24 PRODUCT
EXSVEV31 SVEV25 SV01EV25 SVEV25: SYSVIEW AUDIT 25 LINKSET
EXSVEV32 SVEV26 SV01EV26 SVEV26: SYSVIEW AUDIT 26 LINKLIST
EXSVEV33 SVEV27 SV01EV27 SVEV27: SYSVIEW AUDIT 27 STORAGE
EXSVEV34 SVEV28 SV01EV28 SVEV28: SYSVIEW AUDIT 28 AMRF ACT
EXSVEV35 SVEV29 SV01EV29 SVEV29: SYSVIEW AUDIT 29 ESRTABLE
EXSVEV36 SVEV30 SV01EV30 SVEV30: SYSVIEW AUDIT 30 TSOTABLE
EXSVEV37 SVEV31 SV01EV31 SVEV31: SYSVIEW AUDIT 31 REGPROD
EXSVEV38 SVEV32 SV01EV32 SVEV32: SYSVIEW AUDIT 32 DUMPDS M
EXSVEV39 SVEV33 SV01EV33 SVEV33: SYSVIEW AUDIT 33 CICSTRAN
EXSVEV40 SVEV34 SV01EV34 SVEV34: SYSVIEW AUDIT 34 CICS THR
EXSVEV41 SVEV35 SV01EV35 SVEV35: SYSVIEW AUDIT 35 CICS STA
EXSVEV42 SVEV36 SV01EV36 SVEV36: SYSVIEW AUDIT 36 MQ QUEUE
EXSVEV43 SVEV37 SV01EV37 SVEV37: SYSVIEW AUDIT 37 USER EVE
EXSVEV44 SVEV38 SV01EV38 SVEV38: SYSVIEW AUDIT 38 MQ CHAN
EXSVEV45 SVEV39 SV01EV39 SVEV39: SYSVIEW AUDIT 39 CICS TS
EXSVEV46 SVEV40 SV01EV40 SVEV40: SYSVIEW AUDIT 40 SET EXTN
EXSVEV47 SVEV41 SV01EV41 SVEV41: SYSVIEW AUDIT 41 SET GRAN
EXSVEV48 SVEV42 SV01EV42 SVEV42: SYSVIEW AUDIT 42 CICS STA
EXSVEV49 SVEV43 SV01EV43 SVEV43: SYSVIEW AUDIT 43 CICS SHU
EXSVPLOT SVEV44 SV01EV44 SVEV44: SYSVIEW AUDIT 44 DATA SET
EXSVTHRE SVEV45 SV01EV45 SVEV45: SYSVIEW AUDIT 45 TASK STA
EXSVSTAT SVEV46 SV01EV46 SVEV46: SYSVIEW AUDIT 46 TASK STO
EXSVCEXC SVEV47 SV01EV47 SVEV47: SYSVIEW AUDIT 47 JES2 JOB
EXSVTSUM SVEV48 SV01EV48 SVEV48: SYSVIEW AUDIT 48 JES2 OUT
EXSVTRAN SVEV49 SV01EV49 SVEV49: SYSVIEW AUDIT 49 JES2 OUT
EXSVPROG SVPLOT SV02PLOT SVPLOT: SYSVIEW PLOT
EXSVFILE SVTHRE SV08THRE SVTHRE: SYSVIEW THRESHOLD EXCEPTI
EXSVTMPS SVSTAT SV09STAT SVSTAT: SYSVIEW STATE EXCEPTION
EXSVTDTA SVCEXC SV24CEXC SVCEXC: SYSVIEW EXCEPTION
EXSVABND SVTSUM SV25TSUM SVTSUM: SYSVIEW CICS TRANS SUMMAR
EXSVEXCE SVTRAN SV27TRAN SVTRAN: SYSVIEW CICS TRANSACTION
EXSVMEMP SVPROG SV27PROG SVPROG: SYSVIEW CICS PROGRAMS
EXSVDLI SVFILE SV27FILE SVFILE: SYSVIEW CICS FILES
EXSVTHRS SVTMPS SV27TMPS SVTMPS: SYSVIEW CICS TEMPORARY ST
EXSVRESM SVTDTA SV27TDTA SVTDTA: SYSVIEW CICS TRANSIENT DA
EXSVDCOM SVABND SV27ABND SVABND: SYSVIEW CICS ABENDS
EXSVEXIN SVEXCE SV27EXCE SVEXCE: SYSVIEW CICS EXCEPTIONS
EXSVWBMQ SVMEMP SV27MEMP SVMEMP: SYSVIEW CICS MONITOR EMPS
EXSVDB2 SVDLI SV27DLI SVDLI: SYSVIEW CICS DL/I
EXSVMEIE SVTHRS SV27THRS SVTHRS: SYSVIEW CICS THRESHOLDS
EXSVINTV SVRESM SV27RESM SVRESM: SYSVIEW CICS RESOURCE MAN
EXSVIMST SVDCOM SV27DCOM SVDCOM: SYSVIEW CICS DATACOM CSF
EXSVIMSP SVEXIN SV27EXIN SVEXIN: SYSVIEW CICS EXEC INTERFA
EXSVMQRR SVWBMQ SV27WBMQ SVWBMQ: SYSVIEW CICS WEBSPHERE MQ
IMACSVIE SVDB2 SV27DB2 SVDB2: SYSVIEW CICS DB2
TYPESVIE SVMEIE SV27MEIE SVMEIE: SYSVIEW CICS MEI EVENT
TYPSSVIE SVINTV SV28INTV SVINTV: SYSVIEW CICS INTERVAL SUM
VMACSVIE SVIMST SV32IMST SVIMST: SYSVIEW IMS TRANSACTION
VMXGINIT SVIMSP SV33IMSP SVIMSP: SYSVIEW IMS PROGRAM SUMMA
Jun 17, 2008 SVMQRR SV48MQRR SVMQRR: SYSVIEW MQ APP REGIONS
Change 26.132 Minor correction; if optional RMFFILT DD was missing but
ASMRMFV RMFSKIP DD was present, ASMRMFV could fail with USER 998
Jun 14, 2008 when attempting to close the nonexistent RMFFILT DDname.
Thanks to Jerry Urbaniak, Acxiom, USA.
Change 26.131 The reports on MIPS/MSU usage for CP engine is enhanced
ASUMMIPS to also report on zIIPs and zAAPs, by adding variables
Jul 18, 2008 CPUIFATM CPUZIPTM NRIFAS NRZIPCPU IFAUSED ZIPUSED MIPSIFA
MIPSZIP with _MIPSIFA and _MIPAZIP macros that define the
factors in the same way as base CP conversion factors.
Thanks to Robert Kuhne, Exelon Corporation, USA.
Change 26.130 Notes for CICS IMACICEZ, IMACICE1, IMACICE2 tailoring.
IMACICEZ These notes originaed in Change 24.033, then 25.xxx and
IMACICE1 are repeated here, as well as in comments in UTILEXCL
IMACICE2 These members are required to be tailored if your CICS
UTILEXCL records contain 'EZA01' or 'EZA01' optional segments:
Jun 14, 2008
-IMACICEZ always has these 5 fields, identified by their
CMODNAME='EZA01' and CMODTYPE='S':
EZA01 S 001 12 ooo INIT
EZA01 S 002 12 ooo READ
EZA01 S 003 12 ooo WRITE
EZA01 S 004 12 ooo SELECT
EZA01 S 005 12 ooo OTHER
The CMODLENG=12 is from CICS/3.2; earlier CICS had only
CMODLENG=8, but IMACICEZ supports both lengths, so you
just remove the comment block to tailor IMACICEZ and it
will process data with either or both lengths.
-IMACICE1 can have up to 13 fields, identified by their
CMODNAME='EZA01' and CMODTYPE='A' (yes, CMODNAME is the
same 'EZA01' as IMACICEZ, but the CMODTYPE is different):
EZA01 A 001 4 ooo TINIT
EZA01 A 002 4 ooo TREAD
EZA01 A 003 4 ooo TWRITE
EZA01 A 004 4 ooo TSELECT
EZA01 A 005 4 ooo TOTHER
EZA01 A 006 4 ooo REUSABLE
EZA01 A 007 4 ooo ATTACHED
EZA01 A 008 4 ooo OPENAPI
EZA01 A 009 4 ooo TCBLIM
EZA01 A 010 4 ooo TREUSABL
EZA01 A 011 4 ooo TATTACHE
EZA01 A 012 4 ooo TOPENAPI
EZA01 A 013 4 ooo TTCBLIM
You will have to examine REPORT THREE (which may have the
last CMODHEAD field 'EZA01' instead of the names shown)
to know how many fields are in your data. If you have the
expected 13 fields, then you just remove the one comment
block. If you have fewer fields, then:
- Change the IF xxxx GE 52 THEN DO; statement so its
test value is 4 times the number of fields, e.g.
with seven fields change the "52" to "28".
- Change the INPUT statement's suffix from EZA01A13 to
the number of fields you have; if there are seven:
INPUT (EZA01A01-EZA01A07) (&PIB.4.) @;
- Delete the LABELs for variables that don't exist.
-IMACICE2 has 22 fields with z/OS 1.7 TCP/IP data, but had
only 11 fields with z/OS 1.4, which are identified by the
CMODNAME='EZA02' and CMODTYPE='A:
EZA02 A 001 4 330 CONN
EZA02 A 002 4 331 STARTED
EZA02 A 003 4 332 INVALID
EZA02 A 004 4 333 DISTRAN
EZA02 A 005 4 334 DISPROG
EZA02 A 006 4 335 GIVESOKT
EZA02 A 007 4 336 SECEXIT
EZA02 A 008 4 337 NOTAUTH
EZA02 A 009 4 338 IOERR
EZA02 A 010 4 339 NOSPACE
EZA02 A 011 4 340 LENERR
EZA02 A 012 4 341 TCONN
EZA02 A 013 4 342 TSTARTED
EZA02 A 014 4 343 TINVALID
EZA02 A 015 4 344 TDISTRAN
EZA02 A 016 4 345 TDISPROG
EZA02 A 017 4 346 TGIVESOK
EZA02 A 018 4 347 TSECEXIT
EZA02 A 019 4 348 TNOTAUTH
EZA02 A 020 4 349 TIOERR
EZA02 A 021 4 350 TNOSPACE
EZA02 A 022 4 351 TLENERR
You will HAVE to look at UTILEXCL REPORT THREE to confirm
if you have 22 or 11 fields, and remove only one of the
two comment blocks in IMACICE2 to tailor it.
-You create REPORT THREE with the _RPTEXCL macro run
with or after your UTILEXCL execution:
//SYSIN DD *
%INCLUDE SOURCLIB(UTILEXCL);
_BLDDICT;
_BLDEXCL;
_RPTEXCL;
Change 26.129 Format TAOTRMCD existed in FORMATS (but did not have the
FORMATS OTHER='UNKNOWN' value statement), and it was not applied
VMACTAO to variable TAOTRMCD in VMACTAO until now.
Jun 12, 2008
Thanks to Steve Clark, DHL IT Services Americas, USA.
Change 26.128 ASMTAPEE ML-41 (MXG 26.03-26.04) IS DEFECTIVE.
VMACTMNT But you do NOT need to replace the MXGTMNT monitor task
Jun 12, 2008 if it is already installed, as this circumvention will
correct the error. You will need to reprocess the SMF
records created with ML-41 with the new VMACTMNT from
this change.
The error impacts the PDB.ASUMTAPE dataset; the TYPETMNT
data is correct with ML-41 monitor. However, to capture
ALL tape mount events, you must use the ASUMTAPE program
and then use PDB.ASUMTAPE dataset (and not PDB.TYPETMNT)
to capture the DFHSM mounts, 2nd mounts and other mounts
that do not go thru the IBM/STC exits; those events are
depend on the subtype 8 SYSLOG records in PDB.TYPESYMT
that ASUMTAPE combines with TYPETMNT and TYPE21 datasets
to capture EVERY mount in PDB.ASUMTAPE.
The error is only in the PDB.TYPESYMT SYSLOG dataset; the
JOB field in the subtype 8 record with ML-41 is in error
as it contains the JCTJOBID value, rather than JOB name,
which causes JESNR to be a missing value in PDB.TYPESYMT,
which then causes ASUMTAPE to fail to match up the SYSLOG
event data with the TYPETMNT and TYPE21 records.
This revision to VMACTMNT captures the JOB name from the
SYSLOG message text, rather than the JOB field, and the
VGETJESN was relocated to use the correct JOB name to
decode the JESNR from JCTJOBID.
Not an error, but it was observed that the PROGRAM name
in the TYPETMNT dataset is always blank; that field was
only capturable when the (now archaic) cross-memory
XMEM=YES option was used, prior to the exit-driven
redesign. Since TYPETMNT has JOB READTIME and JESNR,
the PROGRAM can be acquired from the PDB.STEPS dataset.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 26.128 Prisma SMF record was changed by the vendor, by insertion
VMACPRPR of a text field, subsequently identified as the PRINTER
Apr 11, 2008 between ACCOUNT and SHEETS. The change was made in April
Jun 12, 2008 as Change 26.067, but never made it into CHANGES, and the
change number was reused.
Thanks to Carl Sablon, KBC Bankverzekerinngsholding, BELGIUM.
Thanks to Siegfried Trantes, IDG, GERMANY.
Change 26.126 Support for WebSphere incorrect triplets in subtype 3.
VMAC120 Instead of properly using the triplet SM120SRN field to
Jun 11, 2008 count the number of Server Region Sections, IBM chose to
implement an aberrant design by instead creating 0-n new
triplets (offset, length, count) in the record header!
This "feature" caused MXG to only output the first data
section in dataset TYP120SR. Circumvention code now uses
SM120TRN-2 (number of triplets minus two) to loop across
the Server Regions. This error was detected because the
total number of allocation failures, SM120HIC, was much
smaller than expected, and a detail trace identified that
only one Server Region was being output.
Thanks to Lisa Oulette, Wachovia Information Technology, USA.
Change 26.125 Support for NTSMF new Objects:
EXNTBITS DDDDDD DATASET DESCRIPTION/OBJECT NAME
EXNTPACE NTBITS BITSNET BITS NET UTILIZATION
EXNTUSB NTPACE PACEPIPE PACER PIPE
IMACNTSM NTUSB USB USB
VMACNTSM -Jun 17, 2008: Variable PACEINST was misspelled
VMXGINIT as PACEPIPE in the _BNTPACE macro definition, causing
Jun 17, 2008 the PROC SORT of dataset PACEPIPE to fail.
Jun 11, 2008
Thanks to Lisa E. Van Allen, Boeing, USA.
Change 26.124 INPUT STATEMENT EXCEEDED for short (possibly defective)
VMACITRF type '11'x ITRF record of only 176 bytes; current ITRF
Jun 10, 2008 record should be 304 bytes long. The record contains
only the Input Terminal and Date and Time and the 4-byte
"UNIQUE" hex field; all other fields are nulls or blanks.
The observation is still output in ITRFMSGO dataset, and
short records can be identified/counted by the variables
COT, LOQT, OQT (and others) having missing values.
Thanks to Prashant Joshi, Perot Systems, USA.
Change 26.123 -Support for new fields added to NTSMF MEMORY object:
VMACNTSM FRZRPLBY='FREE AND ZERO*PAGE LIST*BYTES'
Jun 9, 2008 MODFPLBY='MODIFIED*PAGE LIST*BYTES'
Jun 17, 2008 SBCACOBY='STANDBY*CACHE*CORE*BYTES'
SBCANPBY='STANDBY*CACHE*NORMAL*PRIORITY*BYTES'
SBCARSBY='STANDBY*CACHE*RESERVE*BYTES'
-Support for new field added to NTSMF PROCESS object:
WKSETPRV='WORKING*SET*PRIVATE'
Thanks to Roger Zimmerman, Hewitt Associates, USA.
Change 26.122 Incorrect JOB name was parsed from SYSLOG text that had
ASUMTAPE three comma delimiters. The SAS SCAN function treats all
Jun 5, 2008 repeated delimiters as a single delimiter (why, no one at
SAS can explain, but that 'feature' is documented!), so
the use of TRANWRD(text,',,',', ,') ahead of the SCAN()
was suggested, which worked fine with two delimiters.
However, IEF234E messages with 'D 0F80,,,ZY11110,STEP099'
(unexpected, a dismount with no volser nor PVT/PUB/STR on
a 3590 device) were only expanded to 0F80, ,,ZY1110 so
the subsequent SCANs returned wrong values in WORD2-5.
Now, five TRANWRDs are executed to ensure the SCAN parse
properly decodes the JOB and STEP.
Thanks to Paul Naddeo, FISERV, USA.
Thanks to David Bixler, FISERV, USA.
Change 26.121 IBM/Candle/OMEGAMON Audit Records can be buried inside
VMACOMAU CICS records; this change protects so only Audit records
Jun 4, 2008 are processed by TYPEOMAU. Several variables that do not
exist in the Audit records were removed.
Thanks to Joe Faska, Depository Trust, USA.
====== Changes thru 26.120 were in MXG 26.04 dated Jun 4, 2008=========
Change 26.120 The CICSEXCE Exception Report examples have been useless
ANALCICS for years, as the indivdidual wait/counts have not been
Jun 4, 2008 been populated. Only these variables are populated in
the CICSEXCE dataset:
ENDTIME EXCMNBTR EXCMNCPN EXCMNFCN EXCMNNID EXCMNNPX
EXCMNNSX EXCMNRIL EXCMNRIL EXCMNRIX EXCMNRLU EXCMNRPT
EXCMNRTY EXCMNSRV EXCMNTCN EXCMNTRF EXCMNTYP EXCMNURI
EXCMNURI EXWAITTM LUNAME OPERATOR STRTTIME TASEXCNR
TASKNR TCLASS TERMINAL TRANNAME TRANPRI TRANTYPE
USER
A new report totals EXWAITCN and EXWAITM and calculates
the AVGWAITM for each APPLID EXCMNTYP EXCMNRTY EXCMNRIX
has been added to the examples in ANALCICS.
Thanks to Robert Carter, PNC Bank, USA.
Change 26.119 Variable LCU is added to TYPE74CA, by converting CSSSID
VMAC74 from character to numeric, and variables CUSERIAL and
Jun 4, 2008 CUVENDOR are created by substring from R745CCMT.
On IBM RMF reports, they print "CUID"-"CSDEVN" value and
"SSID"-"CSSSID" value (now, "SSID"-"LCU" value).
Thanks to Steven Olmstead, Northwestern Mutual, USA.
Change 26.118 Almost cosmetic; the TEST parameter (which writes MXGTMNT
ASMTAPEE data to a flat file, instead of to SMF) did not work.
Jun 4, 2008 This first ML-42 was never distributed see Change 26.136.
Thanks to Alexander Raeder, ATOSORIGIN, GERMANY.
Change 26.117 Dataset TYPE747C was missing almost all observations; the
VMAC74 output statement was outside the DO loop over CUs. And,
Jun 4, 2008 variable R747SDEV is now KEPT in TYPE747C so it can be
matched up with TYPE747P observations.
Thanks to Fabio Massimo Ottaviani, DTS Italia, ITALY.
Change 26.116 Support for APAR OA22414 adds new variables to TYPE23
VMAC23 SMF Statistics Records:
Jun 4, 2008 SMF231RF='FIRST*REFERENCE*FAULTS'
SMF23NFR='FIX*REQUESTS*BELOW*2GM'
SMF23NGR='GETMAIN*REQUESTS*ISSUED'
SMF23NIO='TOTAL*I/O*OPERATIONS'
SMF23NRF='NON-FIRST*REFERENCE*FAULTS'
SMF23PBG='PAGES*BACKED*DURING*GETMAINS'
SMF23PFX='FRAMES*FIXED*BELOW*2GB'
SMF23SRB='SRB*DISPATCHES'
SMF23TCB='UNLOCKED*TCB*DISPATCHES'
SMF23SFG='STATISTICS*SECTION*FLAG'
The SMF23SFG bits 0 thru 8, if on, indicate that the
value in the corresponding nine variables were limiited
to four bytes internally and could have wrapped if the
value was more than 4x10**9; MXG inputs all nine fields
as eight bytes.
Change 26.115 Inconsistent BY list for RMF data are now consistent.
VMAC7xxx The correct sequence is SYSPLEX SYSTEM SYSNAME ... but
WEEKxxxx SYSNAME was not always present, and in some cases it was
MONTHxxx SYSNAME, in others it was the &MXGSYSN macro variable
Jun 3, 2008 name (needed only way back in Version 23 to protect for
earlier MXG versions).
Unless you have duplicate SYSTEM names in a SYSPLEX, the
SYSNAME is identical to SYSTEM, so its insertion will not
have any impact on the actual sorted order.
(Of course, if you have multiple SYSTEMs with the same
SYSTEM name, then the SYSNAMEs will be different, so
there is a SMALL chance this could cause a NOT SORTED
condition when you combine dailies into weekly/monthly
PDB libraries).
Thanks to Brian Crow, BT, ENGLAND.
Change 26.114 z/VM MONWRITE BAD CONTROL RECORD error because MXG didn't
VMACVMXA protect the 6.24 correctly.
May 30, 2008
Thanks to Sharon Moir, JPMorgan Chase Bank, USA.
Change 26.113 Variable IORATE=DVTSAMPA/DURATM is now created in the
VMACRMFV ZRBDVT dataset.
May 30, 2008
Thanks to Roger Foreman, Acxiom, USA.
Change 26.112 MXG 26.03: TYPE70 variables CPUMVSTM, PCTMVSBY, SHORTCPS
VMAC7072 and PLCPRDYQ are missing if not on a z10 processor; the
May 30, 2008 support added for SMF70PAT (CPUPATTM, parked time) failed
to protect those calculations when CPUPATTM was a missing
value. Fortunately, you can recalculate from PDB.TYPE70:
CPUMVSTM=CPUUPTM-MVSWAITM;
IF CPUUPTM GT 0 THEN PCTMVSBY=100*CPUMVSTM/CPUUPTM;
IF PCTMVSBY GT 0 AND PCTCPUBY GT 0 THEN DO;
SHORTCPS=PCTMVSBY/PCTCPUBY;
PLCPRDYQ=100*(PCTMVSBY-PCTCPUBY)/PCTMVSBY;
IF . LT PLCPRDYQ LT 0 THEN DO;
SHORTCPS=1;
PLCPRDYQ=0;
END;
END;
Thanks to Charles Savikas, DCF State of Florida, USA.
Change 26.111 -Support for TMVS Release 4.1, INCOMPATIBLE due to fields
EXTMVCN inserted in the "JD" records. Many new variables for the
EXTMVCNM zIIP and zAAP engines are created in the Job records.
EXTMVCNP -The code is enhanced to full "standard" structure, with
EXTMVCNS the _Vdddddd macros created, and the _Sdddddd sort macros
EXTMVCO now invoking PROC SORT NODUP to remove duplicates instead
EXTMVCOF of being simple DATA steps.
EXTMVCOH -Redundant variables with STARTIME, ENDTIME and DURATM are
EXTMVCOP removed.
EXTMVCOS -Thirty new datasets are created, for all of the possible
EXTMVCY record types, and all datasets for which I have data
EXTMVCYD records are populated and duplicate-removal-validated.
EXTMVEC -New IHDRTMVS exist allows deletion of unwanted record
EXTMVES types.
EXTMVHC
EXTMVHM
EXTMVHS
EXTMVMC
EXTMVMCL
EXTMVMCV
EXTMVRG
EXTMVX1
EXTMVX3
EXTMVX4
EXTMVXC
EXTMVXD
EXTMVXN
EXTMVXO
EXTMVXP
EXTMVXS
EXTMVXW
IHDRTMVS
IMACTMVS
VMACTMVS
VMXGINIT
Jun 2, 2008
Thanks to Sam Bass, McLane Co., USA.
Change 26.110 A new MXG ERROR message is printed for PDB.RMFINTRV if
VMXGRMFI there are no TYPE72GO observations that match the TYPE70
May 28, 2008 observations. The resultant PDB.RMFINTRV observation has
PCTOVHD and CPUOVHTM and CPUTM missing values.
Thanks to Chuck Hopf, Bank of America, USA.
Change 26.109 Cosmetic. New values for QWACRINV were not formatted by
ADOCDB2 the MGDB2RC format, and value 40 should have been ABNORM.
FORMATS
May 22, 2008
Thanks to Christa Neven, KBC Bankverzekerinngsholding, BELGIUM.
Change 26.108 CICS optional IMS data segment with CMODNAME='USER' and
UTILEXCL CMODHEAD='SCHDPDS' or 'SCHDTIME' or 'CALLDLI' is now
May 22, 2008 recognized and is supported by the existing IMACICDL
member. Previously, all IMS segments had the values of
'PSB WAIT', 'PSB SCHD', 'DB CALL', and 'DB IO' for those
fields, and these unexpected text fields cause MXG to
NOT identify IMACICDL as needed when UTILEXCL ran.
Thanks to Robb Hermes, Sentry Insurance, USA.
Change 26.107 INPUT STATEMENT EXCEEDED with SMF 80 with new ASSIZMAX
VMAC80A value in TOKDANAM; that field is not INPUT as TOKASIZM
May 21, 2008 and kept in all TYPE80xx datasets with extended data.
Thanks to Clayton Buck, UniGroup, USA.
Change 26.106 Enhancement for AF/OPER SMF record support.
VMACAFOP These variables are now INPUT and KEPT in all datasets:
May 19, 2008 AFOMATNR AFOMATTY AFOTRNAM AFOCPUTM AFOEXECN AFOCONSN
The AFOCPUTM is now input as &PIB.4.3.
Thanks to Joe Faska, DTCC, USA.
Change 26.105 The label for variable R723CSUP is clarified to read
VMAC7072 R723CSUP='UN-NORMALIZED*ZIP*SERVICE*UNITS'
May 19, 2008 because it contains the zip service units before their
normalization back to the same scale as the CPUUNITS.
The variable ZIPUNITS contains the normalized service
unikts. ZIPUNITS and R723CSUP are different ONLY if the
CP engine speed is less than the ZIP engin speed.
Thanks to Bret Hoesly, Telephone & Data Systems, Inc., USA.
Change 26.104 Variable SMF70PMU was not divided by NRSAMPLE and its
VMAC7072 label was incorrect. It now is
May 19, 2008 SMF70PMU='AVG BLKED*DISPATCH*UNITS*PROMOTED'
Thanks to Fabio Massimo Ottaviani, DTS Italia, ITALY.
Change 26.103 INPUT STATEMENT EXCEEDED ID=42 SUBTYPE=15 when there were
VMAC42 more than one S2 segment. MXG logic for LENGTH test was
May 19, 2008 corrected.
Thanks to Dan Case, Mayo Clinic, USA.
Change 26.102 TYPETASK='J ' occurred in TYPETMNT/TYPESYMT because the
VGETJESN VGETJESN logic when there is no SUBSYS, and the JCTJOBID
May 19, 2008 contains 7 digits did not set TYPETASK='JOB'.
Thanks to Brian Felix, Wachovia Corporation, USA.
Change 26.101 The ending semicolon in the %VMXGVERS(VMXGFOR,xx.yy);
VMXGFOR statement caused a syntax error; that ending semilcolon
May 17, 2008 is not only not required, in this instance it was wrong:
In the VMXGFOR macro, the last line calls VMXGVERS with
a semi-colon at the end. These types of semi colons are
never required, since the macro processor knows to
execute the macro when the tokenization sees the right
parenthesis. In this particular scenario, what happens
is that that trailing semi colon gets returned to the
input stream to the datastep - in the middle of the proc
sort statement, which is why is complains at DATA= being
a Statement that is not valid or out of order.
Thanks to James Hein, Erie Insurance, USA.
Thanks to Chris Weston, SAS ITRM, USA.
Change 26.100 Invalid MEM header record with a missing comma caused
VMACNMON INPUT STATEMENT EXCEEDED RECORD LENGTH error. The header
May 16, 2008 had only 7 fields, causing the error, but the actual MEM
data records are valid, so the handling of the header is
revised to protect for the invalid record.
Thanks to Angelo Pezzella, SAS Italy, ITALY.
Change 26.099 Variable ELAPSTM is now calculated instead of missing.
VMACORAC
May 16, 2008
Thanks to Bret Hoesly, Telephone and Data Systems, USA.
Change 26.098 Support for Informatics STAT user SMF record.
EXIFOCLI Five datasets are created from the user SMF record:
EXIFODB2 IFOLIS INFOLISN INFORMATICS LISTENER
EXIFOEXC IFOEXC INFOEXCP INFORMATICS EXCEPTION
EXIFOFIL IFOFIL INFOFILE INFORMATICS FILE
EXIFOLIS IFODB2 INFODB2 INFORMATICS DB2
IMACINFO IFOCLI INFOCLIE INFORMATICS CLIENT
TESSUSR1 The datetimestamps of the INFO variables are still on the
TYPEINFO GMT clock, because there is no GMT offset in the records.
TYPSINFO The delta between the END (GMT) and SMFTIME (Local) can
VMACINFO not be used, because END is missing in many records. The
VMXGINIT vendor has been requested to add a GMT offset field so
May 21, 2008 the GMT datetimestamps can be converted to local zone.
Thanks to Elizabeth Griesse, Securian Financial Group, USA.
Change 26.097 Divide-by-zero for denominator CPUCPLEN is now protected.
VMACRMFV
May 13, 2008
Thanks to Betty Wong, Bank of America, USA.
Change 26.096 -Variables QW0227FG and QW0227PG were always missing; the
VMAC102 test for QWT02R1L should have been 17 and not 21.
May 13, 2008 -Variables QW0226DB and QW0026OB are now $HEX4. format.
Thanks to Karthik Vinayagam, Morgan Stanley, USA.
====== Changes thru 26.095 were in MXG 26.03 dated May 11, 2008=========
Change 26.095 -ML-41 of ASMTAPEE the MXG Tape Mount Monitor corrects the
ASMTAPEE JOB Name to use MDBGJBNM in the SMF records it writes for
May 10, 2008 WTO SYSLOG events; some records had HSM instead of VTCSS.
The new ASUMTAPE logic in Change 26.083 corrects the JOB
when it is not the same as SYSLJOB, but this corrects the
SMF records created by MXGTMNT monitor.
-The Allocation Recovery Event subtype created by MXGTMNT
was not correct for the (typical, usually automated) WAIT
event. ML-41 corrects the logic for that subtype, so the
observations in TYPEARCV contains job info and the delay
to that job due to insufficient tape devices, which is
what an Allocation Recovery Event describes.
-Some general performance enhancements were also made.
Thanks to Chuck Hopf, Bank of America, USA.
Change 26.094 ERROR: LIBRARY PDB IS NOT IN A VALID FORMAT FOR ACCESS
CONFIGV9 METHOD SASV6SEQ.
May 9, 2008 occurs if OPTIONS SEQENGINE=V6SEQ or TAPENGN=V6SEQ are
in effect; you can use PROC OPTIONS to display the value
of those options. SEQENGINE is defined in CONFIGV9, and
TAPENGN is defined in VMXGINIT; both default to V9SEQ
(or V8SEQ if still using SASV8), but either option can
be changed with a %LET XXXX=VnSEQ, so searching your MXG
tailoring libraries for V6SEQ should locate that text.
The MXGSASV9 JCL procedure puts the MXG CONFIGV9 member
as the last datasets in the //CONFIG DD, so that any SAS
option I specify in CONFIGV9 will override the default
SAS options specified in its .CFG file. However, there
are only these options that are in both the SAS BATW0 and
the current MXG CONFIGV9 members:
Option SAS Value MXG Value
BUFNO 3 2
BLKSIZE 6144
MEMLEAVE 512K 10M
SEQENGINE TAPE V9SEQ
NLSCOMPATMODE NONNLSCOMPATMODE NLSCOMPATMODE
THREADS THREADS NOTHREADS
====== Changes thru 26.093 were in MXG 26.03 dated May 8, 2008=========
Change 26.093 TESTOTHR step failed because DDNAMES CTMUUNIX, CTMZZOS
JCLTESS9 were not added to support CONTROL-M support.
JCLTEST9
JCLTEST8
JCLTESS8
May 9, 2008
Thanks to Bernd Klawa, Stadwerke-Bielefeld, GERMANY.
Change 26.092 Divide By Zero warning in HyperPav SMF 74 when SMF74PSM
VMAC74 was zero in an interval when the device was Varied. The
May 9, 2008 divide is now protected.
Thanks to Leendert Keesmaat, UBS, SWITZERLAND.
Change 26.091 Mis-alignment of the CS Server by four bytes caused very
VMAC111 large values in some variables in CTG SMF 111 CS Server
May 7, 2008 records. The VMAC111 in 26.03 did not contain this
Jun 3, 2008 change.
Thanks to Ray Dunn, CIGNA, USA.
Change 26.090 Support for SAS Version V9.2: WARNING could still occur
VMXGSUM if OUTCODE= was specified; Change 26.065 COPYed, rather
May 7, 2008 than MOVEd the LENGTH statement to after the SET, so the
WARNING was still printed. As a result, MXG 26.03 is
now the required MXG Version to eliminate the WARNING in
MXG delivered code.
Thanks to Bruce Widlund, Merrill Consultants, USA.
Change 26.089 Support for CONTROL-M logs from both Unix and z/OS.
EXCTM065 Separate programs, TYPECTMU for Unix, TYPECTMZ for ZOS
EXCTM100 read the "flat" log files to create new datasets.
EXCTM101 From Unix data, TYPECTMU/TYPSCTMU reads CTMLUNIX to
EXCTM133 create these datasets:
EXCTM134
EXCTM203 DDDDDD DATASET DESCRIPTION
EXCTM206
EXCTM207 CTM065 CTMU5065 CTL-M UNIX MESSAGE ID 5065'
EXCTM208 CTM100 CTMU5100 CTL-M UNIX MESSAGE ID 5100'
EXCTM209 CTM101 CTMU5101 CTL-M UNIX MESSAGE ID 5101'
EXCTM210 CTM133 CTMU5133 CTL-M UNIX MESSAGE ID 5133'
EXCTM211 CTM134 CTMU5134 CTL-M UNIX MESSAGE ID 5134'
EXCTM212 CTMUOT CTMUOTHR CTL-M UNIX OTHER MESSAGE ID'
EXCTM213 From ZOS data, TYPECTMZ/TYPSCTMX reads CTMLZOS to
EXCTM216 create these datasets:
EXCTM217
EXCTM219 DDDDDD DATASET DESCRIPTION
EXCTM281
EXCTM511 CTM203 SEL203I CTL-M ZOS MESSAGE ID SEL203I,220I,221I
EXCTM65A CTM206 SEL206W CTL-M ZOS MESSAGE ID 206W
FORMATS CTM207 SEL207E CTL-M ZOS MESSAGE ID 207E
IMACCTMU CTM208 SEL208I CTL-M ZOS MESSAGE ID 208I
IMACCTMZ CTM209 SEL209I CTL-M ZOS MESSAGE ID 209I
TYPECTMU CTM210 SEL210E CTL-M ZOS MESSAGE ID 210E
TYPECTMZ CTM211 SEL211W CTL-M ZOS MESSAGE ID 211W
TYPSCTMU CTM212 SEL212W CTL-M ZOS MESSAGE ID 212W
TYPSCTMZ CTM213 SEL213W CTL-M ZOS MESSAGE ID 213W
VMACCTMU CTM216 SEL216W CTL-M ZOS MESSAGE ID 216W
VMACCTMZ CTM217 SEL217W CTL-M ZOS MESSAGE ID 217W
VMXGINIT CTM219 SEL219I CTL-M ZOS MESSAGE ID 219I
May 6, 2008 CTM281 SEL281I CTL-M ZOS MESSAGE ID 281I
CTM511 JOB511I CTL-M ZOS MESSAGE ID 511I
CTM65A CTM64AI CTL-M ZOS MESSAGE ID 65AI
CTMZOT CTMZOTHR CTL-M ZOS OTHER MESSAGE IDS
Thanks to John Toohey, IBM, AUSTRALIA.
Change 26.088 Support for sub-subtype '0200' MQ segment creates two new
EX112MQC datasets from SMF 112 records:
EX112MQT DDDDDD DATASET DESCRIPTION
IMAC112 112MQC T112MQCO OMEGAMON CICS MQ DETAIL
VMAC112 112MQT T112MQCT OMEGAMON CICS MQ TOTALS
VMXGINIT There are also '0001' MQ Segments for which I do not yet
May 5, 2008 have a DSECT, to be added when documentation received.
May 9, 2008 May 9: Still no documentation for 0001 record, and the
0200 documentation is wrong; there are 25 4-byte
counters in the segment, but the DSECT from 2007
documented only 8 pair of 4-byte clock/counters.
For now, first 8 counters have the 8 labels from
the 2007 documentation, the rest a counter number.
Thanks to Ray Dunn, CIGNA, USA.
Change 26.087 Flag variable UBFLAG1 in DCOLBKUP was decoded into these
VMACDCOL variables, but they were not kept until now:
May 5, 2008 UBINCAT UBNOENQ UBBWO UBNQN1 UBNQN2
Thanks to Michael Friske, Fidelity Systems, USA.
Change 26.086 Support for AF/Operator SMF Record creates four datasets:
EXAFOPEX DDDDDD MXG MXG
EXAFOPFI DATASET DATASET DATASET
EXAFOPIM SUFFIX NAME LABEL
EXAFOPMA
IMACAFOP AFOPEX AFOPEXEC AFOP EXEC
TYPEAFOP AFOPFI AFOPFILE AFOP FILE
TYPSAFOP AFOPIM AFOPIMMED AFOP IMMED
VMACAFOP AFOPMA AFOPMATCH AFOP MATCH
VMXGINIT
May 5, 2008
Thanks to David Kaplan, DTCC, USA.
Change 26.085 Variable SMFTIME was not in the BY list for TYPE70PR and
WEEKBLD TYPE72MN in WEEKBLD, but was in the BY list for MONTHBLD.
May 5, 2008 The BY list in WEEKBLD was updated. The absence of the
SMFTIME variable caused a NOT SORTED condition when the
clocks were set back one hour on April 6.
Thanks to Peter Krijger, ANZ National, NEW ZEALAND.
Change 26.084 Enhancements to HSM sample reports addes a new REPORT6, a
ANALHSM time-interval summary of MIGRATE/RECALL/BACKUP activity.
May 2, 2008 about every tape mount event.
Additionally, new filtering parameters are created in the
RPTFILT1-RPTFILT6 macros.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Change 26.083 Major rewrite of ASUMTAPE corrects errors and supports
ASUMTAPE SPIN logic to create PDB.ASUMTAPE with EVERYTHING
May 2, 2008 possible about every tape mount event.
May 8, 2008
May 10, 2008 THIS IS AN INCOMPATIBLE CHANGE:
You MUST delete your old SPIN.SPINMOUN dataset before you
implement this revised ASUMTAPE algorithm.
The previous ASUMTAPE logic always correctly assembled
"complete" tape mount events, and most "incomplete"
mounts but there were cases with only a single SYSLOG
event (notable, from our friends HSM and DMS that do
their own unique thing!) in which the output was not
always correct or complete.
In addition, as documented, ASUMTAPE never implementd the
full "SPIN" logic to hold incomplete events for the next
execution of ASUMTAPE.
The TYPESYMT processing of SYSLOG records was reinvented,
using the SYSTEM JOB JESNR DEVNR sequence, rather than
the insufficient DEVNR DESCENDING EVENTIME sequence that
was incapable of full protection for these end cases.
-May 10: Final logic errors due to LASTDEVN being kept in
SPINSYSL cleaned up match up of "full" vs "SPLIT SPIN" so
observation counts again matched before and after tests.
-The unique DSNAMEs in the input TYPESYMT and TYPETMNT
were compared with the output DSNAMEs in PDB.ASUMTAPE and
many were blank, and some were wrong, as SYSLDSN is only
populated in IEC233A,IEC705I, and IEC501A/IEC501E SYSLOG
messages; the blank values in the other records overlaid
DSNAME. Now, all observations that had DSNAME in TMNT or
SYSLOG have non-blank DSNAME. Some events can never have
a DSNAME (e.g., HSM only-234E KEEP); variable MNTHAVE
identifies which SYSLOG records were found for this mount
event, and can be used to identify those cases where the
DSNAME is always blank.
Thanks to Paul Naddeo, FISERV, USA.
Thanks to Scott Barry, SBBWorks, Inc., USA.
Thanks to Pat Jones, DST, USA.
Change 26.082 The old IEFU84 sample SMF exit failed with z/OS 1.7 and
IEFU84 z/OS 1.9; the addition of $CADDR after $HCCT in the ASM
May 1, 2008 code eliminated the ASMA044E UNDEFINED SYMBOL messages
for symbols C@XMXSRB, and CADDR, thanks to excellent ASM
sleuthing by Dean.
Thanks to Dean Gambill, Lowe's Companies, USA.
Thanks to Jim Horne, Lowe's Companies, USA.
Change 26.081 -The JCLDAYDS had a //PDB DD, but it is never used in the
DAILYDSR DAILYDSN or DAILYDSR programs, so it was removed from
JCLDAYDS that JCL example.
Apr 30, 2008 -The DAILYDSR example for using DFSMS/RMM instead of TMS
did not create the DCOLCLUS dataset from DCOLLECT data.
Thanks to Diane Eppestein, IBM Global Services, USA.
Change 26.080 MXG 26.01 wrongly changed QPACAAFG INPUT to $CHAR2. as I
FORMATS thought it contained hex text. The $EBCDIC2 input is now
VMACDB2 restored, a hex zero value is converted to blanks, and
Apr 29, 2008 its $MGDB2PK format enhanced to decode that blank value:
VALUE $MGDB2PK
' '='BLANK:NOT DEFINED'
'01'='01:STORED PROCEDURE'
'02'='02:USER DEFINED FUNCTION'
'03'='03:TRIGGER EXECUTING'
;
Thanks to Glen Bowman, Wakefern, USA.
Change 26.079 Variable IFAHONOR could be blank when it should ha