COPYRIGHT (C) 1984-2021 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG NEWSLETTER FOURTEEN
****************NEWSLETTER FOURTEEN*************************************
MXG NEWSLETTER NUMBER FOURTEEN April 1, 1989
Technical Newsletter for Users of MXG : Merrill's Expanded Guide to CPE
I. MXG SOFTWARE VERSION 6.6 "CRITICAL CHANGES" page 2
II. ENHANCEMENTS TO MXG WHICH ARE UNDER CONSIDERATION: page 2
III. CHANGE LOG pages 3 thru 14
Changes through Change 7.035 to 7.001
IV. "MVS Performance Management Legends" pages L1 thru L-26
This outstanding article by Steve Sampson is full
of good information about MVS, and especially
about the history of MVS measurement. We are
pleased to be able to share his work with you.
Thanks too to Candle Corporation for permission.
COPYRIGHT (C) 1989 BY MERRILL CONSULTANTS DALLAS TEXAS
MXG IS A REGISTERED TRADEMARK OF MERRILL CONSULTANTS
I. MXG SOFTWARE VERSION 6.6 "CRITICAL CHANGES".
MXG Version 6.6, shipped Jan 21, 1989, has several errors which may
require your immediate attention. At the beginning of the Change Log
section of this newsletter are listed the known "Critical Changes".
YOU MUST READ THAT SECTION IMMEDIATELY.
MXG IMS log processing (TYPEIMS) has been in production at a number of
sites with no problems, yet other users have definitely encountered a
host of problems, and have provided us with their fixes. We are still
validating their discoveries (which are too extensive to distribute in
this newsletter). We know that IMS 1.3 data is not correctly handled
by MXG 6.6, and it appears that some variables are missing and some
time stamps are wrong for some transactions in IMS systems which have
Wait-For-Input and similar environments. Transaction counts and the
CPU and DL/I resources seem to be always correct, but response time
measurements are occasionally wrong, LTERM is sometimes blank, etc.
We will provide these IMS fixes when validated via a pre-release of
MXG that will be available (only upon request) in second quarter 1989.
If you use TYPEIMS for log processing, write us, call (214-351-1966),
fax (214-350-3694), (or overseas contact your local SAS office), and
request to be placed on the "IMS FIX LIST".
II. ENHANCEMENTS TO MXG WHICH ARE UNDER CONSIDERATION:
JES3 Jes Measurement Facility SMF type 84 record.
VM/XA VMPRF product reports may be replicated in MXG.
NETVIEW File Transfer Program Release 1.0 "User" SMF Record.
RMF type 79 SMF record (subtypes 1 and 2 at least).
TMS Catalog full support (upgrade XMACUCC1 to TYPEUCC1).
TLMS Catalog support.
--------------------------Changes Log----------------------------------
You MUST read each Change description below to determine if a Change
will impact your installation. For each impacting change, you should
also read any comments in the beginning of the source members that
are listed under the change number. Notes, comments, and last minute
documentation are sometimes found in comments in the source members.
--------------------------------------------------------------------
Critical changes (i.e., those that avoid error conditions) are marked
by FIX: following the discussion. If you use the member listed in
a critical change, you must install the FIX.
The following changes are critical:
Change Member Description
7.035 IMAC30IO PDB.JOBS numeric variables wrong.
7.009 VMACVMXA Concatenated VM/XA Monitor files
7.008 BUILDPDB JES2 Spool Transfer Purge Records
7.007 MONTHBLD Syntax error
7.006 BUILDPDB PRENTIME inadvertently in DROP list
" WEEKBLD PRENTIME not in BY list
7.005 VMAC102 DB2 Trace 102 STOPOVER on subtype 58 or 87
7.004 VMAC28 NPM type 28 "Unexpected subtype" message
7.003 JCLHSM HSM included nonexistent XMXGHSM member
7.002 VMACCIMS IMF CPUTM calculation incomplete
7.001 TRND...,etc. Trend Data Base finger faults
You can make these changes directly in the MXG.SOURCLIB library.
Alternatively, you may wish to create a new MXG.CHANGLIB library to
hold any changes distributed (as are these) in printed form. You would
store the changed members in MXG.CHANGLIB (which would be concatenated
between your MXG.USERID library and our MXG.SOURCLIB library) until
you receive a replacement version of MXG, at which time you must then
delete all members in the MXG.CHANGLIB library.